Configuration Item (CI) Fields

The fields of the configuration Item (CI) form are listed below and recommendations for using each of them are provided.

Image

The product image is added to the Image field, based on which the CI is registered (provided that the image was added to the product).

Label

The Label field indicates the label for the CI. The label is created automatically using the prefix of other tags in the same product category; the available number is used as the suffix. Example: MON00002 - this value is set in the Label field for the second CI registered based on the product of the “Monitor” category, if the first CI of this category has the label MON00001. The generated label can be adjusted if necessary, for example, if the product already has a label other than the one generated, or if it is the first product registered for a specific product category. No label is required for software applications.

Name

The name of the CI is entered in the Name field. For organizations that do not yet have CI naming standards, the following is recommended. For hardware, use the following syntax to create names: [Brand] [Model] [Additional information] [Category]. Please note: for the server, additional information must describe its function. Examples: Dell Latitude D620 laptop; IBM System p5 590 production server; HP LaserJet 2500n color printer; Canon CanoScan LiDE90 scanner. For the software, use the following syntax: [Brand] [Software Name] [Version]. Examples: Microsoft Windows 7 Professional SP3; Adobe Reader 9.1.0. For software license certificates, use the following syntax: [Brand] [Software Name] “License Certificate". Example: Microsoft Office Professional 2007 license certificate. For websites, specify the name of the home page in this field.

Product brand

The name of the product manufacturer is displayed in the Product Brand field.

Product Model

In the case of a hardware CI, the Product Model field indicates the product model that was used to register the CI.

Product Category

The Product Category field indicates the product category that was used to register the product. If the CI was created on the basis of a software product in the form of a software license certificate, then the value “Software License Certificate” is set in this field, and not the software category of the product.

System identifier (ID)

In the case of a hardware system, its full network name is indicated in the System Identifier field if a network connection is planned (for example, svr12345.ru). In the case of a database, its unique name is entered in the System Identifier field. In the case of a software system, its unique identifier is entered in the System Identifier field, by which it is known in automatic detection tools (provided it is registered in such tools). If the system is a distribution package, then a unique identifier is entered in the System Identifier field, by which it is known to the distribution software. For a phone or fax, the System Identifier (ID) field indicates the number that can be dialed to contact the CI. For a website, its URL is entered in the System ID field (for example, https://intranet.ru). For an IP or MAC address, enter the address in the System ID field. In all other cases, this field is not used. Please note: if the CI is supported by a system management tool with a web interface, then enter the full URL pointing to the CI in this tool in this field. This will allow Service Desk specialists and analysts to open information about the service in the system management application by clicking on the link.

Status

The corresponding status is selected in the Status field. The following options are available:

Ordered – It has been ordered from an external supplier, but has not yet been delivered.

In development – the process of developing or creating a CI in-house has been announced, but the process has not yet been completed.

Available – CI is not currently in use and is available.

Reserved – The CI is not currently in use, but it is planned to be used for a specific purpose.

Transit – CI is currently in the process of transportation.

Installed – CI is installed in the place where it will be used, but it is not ready for use yet.

Under test – CI is currently being tested or tested. It is not ready for use yet. If, for example, a new version of the software is being tested, then its status should be “Tested". However, if the new version of the software is running on a test server, the status of this server should be “In production”.

Redundancy for continuity – CI can only be used to replace the main CI to which it is connected when recovery is required. Please note: A hardware control system designed to provide continuity cannot be located on the same site as the main control system that it replaces.

Issued – CI is temporarily borrowed by a certain person. This person is indicated in the Users field.

In production – CI is used to provide a service.

Maintenance is underway – CI is temporarily unavailable as preventive maintenance is underway.

Does not work – CI is unavailable. It is currently not being repaired.

Being adjusted – CI is unavailable and is currently being repaired.

In the archive – the database, software, software distribution package, or software license certificate are no longer in use, but must remain available for certain purposes, such as legal ones, as well as for backup.

For deletion is no longer in use and cannot be re–deployed. It is awaiting deletion.

Lost or stolen – CI cannot be found. Its removal or destruction was not planned.

Deleted – the owner of the funds has transferred responsibility for the CI to an external organization and is no longer responsible for the CI. This status is usually established for funds that are physically removed from the territory of the owner of the funds or after their destruction.

Further action

The Further Action field is an additional status classifier and details the subsequent operations performed with configuration units that are in the status For deletion or Deleted. The field is only available for physical assets (created based on a product with a set of rules Physical Asset). The following options are available:

Not required - no further actions are required with the CI that is in the status For deletion or Deleted.

For disposal - available for items with the status For disposal. It involves a further physical process of destruction or decommissioning.

For refund - available for items with the status For deletion. It assumes further testing and full or partial return to operation.

Disposed of - available to users with the status Deleted. It involves a physical process of destruction or decommissioning.

Returned - available for users with the status Deleted. It involves testing and a full or partial return to service.

Service

In the Service field, select service, of which this service is or will be a part. The cost of the service is related to this service.

Service Provider

The organization selected in the Service Provider field of the corresponding service is automatically set in the Service Provider field.

Support Team

In the field The support team is selected by team, which is responsible for supporting the system and maintaining information about it in the configuration management database (CMDB).

Site

In the Site field, select Site, where the CI is located (if it is a hardware CI). In the case of a software package, software distribution, or software/interface configuration, the Site field selects the Site that contains the repository of the "DML - Definitive Media Library" (DML - Definitive Media Library) that stores master copies. If the CI is a software license certificate, then in the Site field, select the Site that contains the repository of the "DML - Definitive Media Library" that stores the certificate.

Location

In the Location field, enter the name or number of the room in which the device is located (if it is a hardware device). In the case of a software package, software distribution, or software/interface configuration, the Location field indicates the name or number of the room where the repository of the "defining media library" (DML - Definitive Media Library), which stores master copies, is located. If the CI is a software license certificate, then the name or number of the room in which the repository of the "defining media library" (DML - Definitive Media Library) storing the certificate is indicated in the "Location" field. For mobile devices, specify “Mobile device".

Notes

Any additional useful information about the product is added to the Notes field. It is possible to use basic text formatting in this field.

Attachments

Field Attachments (add attachment) is a link through which you can add an attachment to the CI. You can add multiple attachments.

Number of processors

The Number of processors field indicates the number of processors installed in the server.

Number of cores

The Number of Cores field indicates the total number of processor cores installed in the server.

Amount of RAM

In the field RAM size indicates the amount of RAM installed (in gigabytes).

Alternative names

The Alternative Names field specifies the aliases of the software versions for cases where detection tools are used to populate the configuration Management database (CMDB).

License type

In the field License type selects the type of license that is covered by the license certificate.

Number of licenses

The Number of Licenses field indicates the number of licenses that the license certificate applies to.

Temporary license

The Temporary license checkbox is set for license certificates that are not permanently valid.

License validity period

In the field License validity period indicates the date until which the temporary software license certificate is valid. The license certificate expires at the end of this day.

Site license

The Site License checkbox is set for license certificates that can only be used in one or more specific locations.

Licensed Sites

In the Licensed Sites field, select all Sites where the software covered by the license certificate can be used.

Service Instances

Using the Service Instances field, you can associate a CI with the service instance it belongs to. The categories “Software” or “Software Distribution Package” can be associated with several instances of different services. Any other category can be associated with only one instance of the corresponding service. The value in the field Support team in this instance of the service must be the same as in the field Support team is in the CI. The Software License Certificate category cannot be associated with service instances.

Users

In the Users field, select the specific persons using this CI. The category “Software” or “Software Distribution Package” cannot be associated with users.

Product

Using the field Product can be linked to product. Another product can be selected if the product category has the same set of rules as the category of the previously selected product.

Configuration Items (CI)

Using the Configuration Items (CI)' fieldit is possible to link CI with other CI. The following types of connections can be established:

Parent – This type can be used to link a software package to the software package or distribution package, module, or application of which it is a part. This type of communication is also used to connect a virtual machine, a distribution package, or a software package to the physical computers on which they are installed. Another use case is the connection of a hardware system with another hardware system, of which it is a component, into which it is installed or to which it is directly connected (without using a network). In the case of an addressable key, this type of communication is used to create a connection with the key to which the address is assigned.

Child – This type can be used to link software packages or distributions to the software modules or applications they consist of. This type is also used to connect a physical computer with virtual machines installed on it, software distribution packages, or CI. Another option is to connect a hardware control panel with its hardware components, with control panels installed in it, and control panels connected to it directly (without using a network). This type is also used to link the addresses assigned to it.

Network connection – using this type, you can connect a hardware CI to all other hardware CIs that have a direct network connection to this CI (for example, a router to a switch).

Redundancy – using this type, you can connect a hardware system with all other hardware systems that provide its redundancy (for example, a server forming a cluster with another server).

Continuity – using this type, it is possible to link a hardware system to another hardware system located on another site and used as a replacement if it is necessary to restore an instance of the service (supported by the first hardware system) to ensure its continuous operation.

Software Dependency – using this type, it is possible to associate a software system with all other software systems, software/interface configurations, and databases that depend on this software system or on which this software system depends. The Certificate of a Software License category cannot be linked to other certificates.

Contracts

In the Contracts field, select contracts related to the CI.

Supplier

In the Supplier field, the supplier from whom the order was received is selected. If the CI was developed internally, select an internal organization that is associated with the space to which the CI belongs. If the CI is leased or borrowed from a supplier, the supplier company is selected in this field.

Serial number

The serial number field indicates the serial number of the CI. If the certificate belongs to the category “Software License Certificate”, the number of the license certificate is indicated in the "Serial number" field. The serial number must be unique for each brand in the R-Service system, meaning the combination of brand and serial number must be unique within the space.

Financial owner

In the Financial Owner field, an internal organization is selected, from the budget of which the CI is paid. If the CI is rented or leased, then the organization that pays the rent or lease is selected in this field.

Asset Identifier (ID)

The Asset Identifier (ID) field indicates the number under which the CI is registered in the financial application (for example, 1C).

Used with

The date on which the CI was commissioned is indicated in the Used since field. As a rule, this is the invoice date or the purchase date.

Warranty period

In the field Warranty period indicates the date until which the warranty is valid for the product. The warranty expires at the end of this day.

Workflow template

In the Workflow Template field a workflow template is selected, which will be used to create a workflow for scheduled maintenance tasks.

Repeat

The Repeat field indicates how often the workflow will be created.

Disabled

The Disabled checkbox in the maintenance section temporarily stops the creation of scheduled workflows.

Each

The Each field indicates whether, after creating a workflow, certain days, weeks, months, or years should be skipped (depending on the value of the Repeat field) before creating the next workflow. For example, if the “Repeat” field is set to "Daily" and the "Every" field is set to 1, then the workflow will be created every day. If the value 2 is set in the Each field, the workflow will be created every other day.

Days of the week

In the field Days of the week selects the days of the week on which the workflow will be created.

Days of the month

The Days of the Month field selects the days of the month in which the workflow will be created.

Month(s)

In the Month(s) field, the month(s) of workflow creation are selected. If the value in the "Day of the month" field is not selected, the workflow will be created in the selected months on the day specified in the "Start Date" field.

Day of the month

In the Day of the Month field, select the day of the month on which the workflow will be created.

Day of the week

In the Day of the Week field, select the day of the week on which the workflow will be created.

In

The time of creation of the workflow is indicated in the In field.

Time zone

In the Time Zone field, select the time zone that applies to the fields In, Start Date and End Date.

Start date

The Start Date field indicates the date on which the replay schedule for the workflow template begins to operate.

End date

The End Date field indicates the date on which the replay schedule for the workflow template ceases to be valid.

Calendar

In the Calendar field, a calendar is selected that determines which events should be skipped because they are scheduled outside the calendar hours.

Workflow Manager

The Workflow Manager field selects the workflow manager that will be selected in the Manager field for new workflows created according to the replay schedule.

Requests

The Requests field lists all the requests that the CI is associated with.

Problems

In the field Problems lists all the Problems that the CI is associated with.

Tasks

The Tasks field lists all the tasks that the CI is associated with.