Configuration Items (CIs)
- The different types of CIs
- Examples
- Notes
- Best Practice
- Characteristics specific to versions 2016 and earlier
- Menu access
- Description of tabs
- Alphabetical order of the tabs
- Details
- Impacting CIs
- Impacted CIs
- Installed Software
- Related Equipment
- Licenses
- Attributes
- Capacities
- Inventory Data
- Discussions
- Attachments
- Related Contracts
- Service Levels
- Unavailability
- Continuity Plan
- Incidents
- Service Requests
- Changes
- Problems
- Known Errors
- Actions
- Events
- History of Changes
- Users
- Roles
- Release Projects
- Catalog
- Related Projects
- Blackout - All
- Blackout - CIs
- Blackout - Change Requests
- Amount Charged Back
- Procedures and Wizards
Definition
A configuration item (CI) is an infrastructure component provided by an organization to its customers. It may be an item of equipment (e.g. servers, routers), an application (e.g. SAP, expense account, payroll software) or a corporate service (e.g. Internet access, email system, customer portal).
EndDefinition
CIs are strategic components critical to the company's business. They are monitored in a specific way in the CMDB because they may have an impact on other items in the event of an incident or request. This impact can be in terms of availability or services provided to users. The items to be managed are specified in the Details tab and correspond to the needs of each company.
Each CI:
- Interacts with other impacting and impacted CIs via blocking or non-blocking relationships. These are highlighted in the CMDB Graph.
- May have blackout periods during which modifications must not be made to the CI, as well as unavailability periods.
- Is managed by groups whose roles are defined in workflows that manage related incidents, requests and events.
The different types of CIs
- Equipment CIs
- These are items of equipment moved to the CMDB via a dedicated wizard.
- They are linked to entries in the Equipment Catalog.
- Application CIs (software/software packages)
- They are created directly in the CMDB
- They are linked to entries in the CI Catalog.
- They can be managed in the Definitive Media Library (DML).
- Service CIs
- They are created directly in the CMDB
- They are linked to entries in the CI Catalog.
- They are also linked to entries in the Service Catalog so they can be monitored in the Service Portfolio.
Examples
- Relationship between equipment and the CMDB:
- Oracle server S131 hosts different applications: SAP, expense account, payroll software, etc.
- Server downtime will lead to the unavailability of these applications. The equipment is therefore managed both in the Equipment Inventory and as a CI in the CMDB.
- To ensure that the payroll application works correctly at the end of each month, a blackout period is defined during the last three days of each month for the Payroll Server CI hosting the application.
Notes
- Equipment CIs:
- Certain information is inherited from the model defined in the Equipment Catalog. If this is the case, then you must specify the information for CMDB management.
- The location and department of the main user will automatically be proposed.
- Workstation monitors are generally not defined as CIs because they do not have any impact on other items in the company.
- Service CIs: They can also be created directly in the Service Catalog.
- You can also create CIs using integration models based on one of the CMDB connectors.
Best Practice
- Modifications made to CI models in the CI Catalog or Equipment Catalog will automatically be updated in existing CIs. Make corrections in CI forms only if there are specific conditions not to be included in the catalog.
- To see all CIs under the responsibility of the main user, open the Employee form and select the CI tab.
- To plan an update, you can use different tools:
- The Collision Detection wizard.
- The Change Schedule, by selecting Transition > Collision Detection > Forward Schedule of Change. This lists all changes, release projects and blackout periods scheduled for a given period.
Characteristics specific to versions 2016 and earlier
- Menu access: Extended CMDB > CI
- CMDB graph access:
- In List mode:
next to the CI - In Form mode: next to the Name field > Display CMDB Graph
- In List mode:
- Graphical interface graphique of the form
TabUpdateRules_2016AndPriorVersions
Click to see the general principles for updating tabs.
| Create a new item | Delete an item or association with a related item |
|---|---|
|
Click
|
Click
|
next to the row you want to delete
Menu access
Asset & Configuration > Configuration Items (CI)
CMDB Graph:
- In List mode: next to the CI
- In Form mode: below the Name field
Description of tabs
TabUpdateRules_After2016Versions
Click to see the general principles for updating tabs.
| Create a new item | Delete an item or association with a related item |
|---|---|
|
Run the New wizard at the top of the tab
|
Move the cursor over the corresponding item and click
|
Alphabetical order of the tabs
QuickAccess
|
|
|
|
|
|
Details
CMDB_Name
Name: Unique ID of the current object.
- For equipment CIs, this is the network identifier.
To make it easier to run the search, enter a name that does not contain significant information, e.g. site name, employee name.
CMDB_CIStatus
CI Status: Status of the current object.
example In Production, End of Life, Ready for Deployment
To propagate impacted CIs with this status, run the CI Status: Update wizard.
CMDB_CurrentVersion
Current Version: Version number of the current object in its environment configuration.
example SAP CI ==> Version 3 is used in the production environment while version 4 is used in the test environment.
To release a new version, run the Version: Update wizard.
CriticalLevel
Critical Level: Value that warns the IT Department of the sensitivity of the current object when processing incidents or requests, indicated by 
displayed in the form. The higher the critical level, the higher the object's processing priority.
CMDB_CINumber
CI Number: Number attributed to the current CI.
- For equipment CIs, this is the asset tag assigned in the inventory.
CMDB_Manager
Manager: Manager of the current object, to whom notifications will be sent.
example You want to alert the relevant managers that the server hosting the SAP, expense account or payroll software is down.
- For equipment CIs, this is the main user of the equipment.
CMDB_SLAAvailabilityTarget
SLA Availability Target: SLA availability target applicable to the current object in order to specify its maximum unavailability period. It is calculated with service hours taken into account.
To view the calculated availability of each CI: CMDB > Availability
SLA
SLA: SLA applicable to all incidents or requests related to the current object, used to calculate processing time for the IT Department.
CMDB_IntegratedDML
Integrated to the DML: Used to indicate if the CI corresponds to a software or software package managed in the Definitive Media Library (DML) (box is checked) or not (box is not checked).
Is a Service (Note: Non-modifiable): Used to indicate if the CI is a service (box is checked) or not (box is not checked).
- Service CIs are listed in the Service Catalog and displayed in the Service Portfolio.
- Update: When the CI is created or using the Manage in the Service Catalog wizard.
Type
Type: Type (full path displayed) associated with the current object.
- The type is inherited from the model defined in the CI Catalog or in the Equipment Catalog for equipment moved to the CMDB.
example CI/Application/Function, Equipment/Servers
Manufacturer
Manufacturer: Brand of the current object.
- The manufacturer is inherited from the model defined in the CI Catalog or in the Equipment Catalog for equipment moved to the CMDB.
- For application CIs, this can be the name of the software publisher.
Model
Model: Model associated with the current object from which certain catalog information is inherited.
- Update: Detected by the automatic discovery tool when the information is in the workstation BIOS.
Location
Location: Location where the current object is physically stored.
Department
Department: Department associated with the current object.
CMDB_DefaultCategoryIncident
Default Category (Incident: Category of the Incident Catalog associated by default with the current object, that is automatically selected when a related incident is created.
- You can modify the category in the quick call.
- If the category is not modified, the workflow associated with the category in the catalog will automatically start.
CMDB_DefaultCategoryService
Default Category (Service): Name of the Service Request Catalog associated by default with the current object, that is automatically selected when a related service request is created.
- You can modify the name in the quick call.
- If the name is not modified, the workflow associated with the name in the catalog will automatically start.
CMDB_DefaultCategoryChanges
Default Category (Changes): Name of the Change Request Catalog associated by default with the current object, that is automatically selected when a related change request is created.
- You can modify the name in the quick call.
- If the name is not modified, the workflow associated with the name in the catalog will automatically start.
Financial Data
CMDB_FinancialDataTab
Data related to the charge back of the CI.
- Supplier: Name of the supplier from whom the current object was purchased or leased.
- Amount Charged Back: Details of the current object's charge back to the relevant cost centers. The share of the total amount allocated to each cost center is based on actual usage of the current object and is performed on a pro rata basis using the number of objects at each cost center.
See the examples
- Monthly Rental Charged Back: Monthly amount charged back by the IT Department for the monthly servicing and maintenance of the current object.
- Scheduled Renewal: Date on which the current object should be renewed.
Impacting CIs
CMDB_ImpactingCITab
List of CIs whose unavailability will lead to the unavailability of the current CI, in cases where there is a blocking relationship.
- You should only specify the CIs that will have a direct impact on the current CI. The CMDB Graph enables you to see all upstream impacting CIs.
- Update: In this tab or use an integration model based on the CMDB - Related Configuration Items (CI) connector
- To update a link, you must first delete it and then create it again.
Impacted CIs
CMDB_ImpactedCITab
List of CIs whose unavailability is due to the unavailability of the current CI.
- You should only specify the CIs that are directly impacted by the current CI. The CMDB Graph enables you to see all downstream impacted CIs.
- Update: In this tab or use an integration model based on the CMDB - Related Configuration Items (CI) connector
- To update a link, you must first delete it and then create it again.
Installed Software
InstalledSoftwareTab
List of software installed on the current object.
- Different reports are used to display the differences between the required configuration and the software actually installed on workstations.
- Update: Use the automatic discovery tool using discovery rules defined for software or in this tab when the software cannot be discovered, e.g. printer drivers. You can also use an integration model based on the Software connector
Related Equipment
RelatedEquipmentTab
List of other equipment locally associated with the current object.
example Screen associated with a server
- Update: In this tab or use an integration model based on the Relationships Equipment Equipment by Asset Tag or Relationships Equipment Equipment by Serial Number connector
Licenses
LicenseTab
List of licenses associated with the current object.
- Update: In this tab, or run the Link to a License wizard, or in License forms > Related Equipment tab. You can also use an integration model based on the Relationships Equipment Licenses connector
- Update: In this tab or run the Link to a License wizard in Equipment forms or in License forms > Related Equipment tab. You can also use an integration model based on the Relationships Equipment Licenses connector.
Attributes
AttributeTab
List of attributes linked to the current object.
- Only attributes compatible with the model type can be associated.
- Update: Using an automatic discovery tool, e.g. processor, speed, memory, disk space. Can also be inherited from the model or by adding in this tab when specific conditions exist. Can also be updated via an integration model based on the Attributes (Equipment, Contracts, Licenses) connector.
Capacities
CapacityTab
List of capacities linked to the current object.
example Disk Space, Power
- Update: Inherited from the model or in this tab when specific conditions exist. Can also be updated via an integration model based on the Capacities (Equipment, Contracts, Licenses) connector.
- If one of the CI capacities exceeds the threshold, this will appear in the CMDB Graph (
).
To anticipate in how many months the maximum threshold will be reached for a given capacity, you can use the Capacity Simulation wizard accessible from the Impact Analysis wizard.
Inventory Data
InventoryDataTab
List of information on the current object detected by an automatic discovery tool.
Discussions
DiscussionTab
List of discussions associated with the current object.
- Users can access discussions based on their domain and the visibility of the discussion. Users must also belong to a group authorized to take part in discussions, i.e. in the Group form, the Discussion Enabled box must be selected.
- Enter the keywords you want in the Search field and press <Enter>.
*To cancel the search criteria and return to the complete list of discussions, provided you have the relevant rights, click within the box and then click
.
Attachments
AttachmentTab
List of documents associated with the current object.
- Update: In this tab - See the description
Related Contracts
CMDB_ContractTab
List of contracts associated with the current object.
- Update: In this tab, or run the Link to a Contract wizard, or in Contract forms. You can also use an integration model based on the Relationships Equipment Contracts connector
Service Levels
CMDB_ServiceLevelTab
List of service levels associated with the CI comprising all or some of the service level agreements between the IT Department and customers.
- Update: In Service Level forms in the Service Design menu > CI tab
Unavailability
List of unavailability periods for the current CI.
- These periods are taken into account when calculating the CI's unavailability time for the relevant SLA availability target. If unavailability is partial, it also takes into account the relevant ratios.
Continuity Plan
ContinuityPlanTab
List of continuity plans associated with the current object.
- Update: In this tab and also in Continuity Plan forms in the Service Design menu. You can also run the New Continuity Plan wizard
Incidents
IncidentTab
List of incidents associated with the current object.
- Update: In Incident forms
Service Requests
ServiceRequestTab
List of service requests linked to the current object.
- Update: In Service Request forms
Changes
ChangeRequestTab
List of change requests linked to the current object.
- Update: In Change Request forms
Problems
ProblemTab
List of problems associated with the current object.
- Update: In Problem forms
Known Errors
KnownErrorTab
List of known errors associated with the current object.
- Update: In Known Error forms
Actions
ActionTab
List of actions associated with the current object.
- Update: In Incident/Request forms when an action involving the current object is created
Events
EventTab
List of events associated with the current object.
- Update: Automatically when the Technical Support Agent receives an alert or in the New Event wizard.
History of Changes
HistoryOfChangeTab
List of all modifications made to the form.
- The fields taken into account are defined using rules in the history of changes.
- This is the AM_ASSET table.
Users
CMDB_UserTab
List of users associated with the CI.
- This information is used to alert users of the current CI in the event of an incident.
example Alert all users of the Expense account app that the app is unavailable due to a problem on the database server
- Update: In this tab or use an integration model based on the CMDB - CI, Employees connector
Roles
CMDB_RoleTab
List of CI roles authorized to intervene in the workflows of incidents or requests linked to the CI.
Release Projects
ReleaseProjectTab
List of release projects linked to the current object.
- Update: In this tab and also in Release Projects forms (All CI tab in the Service Transition menu)
Catalog
CMDB_CatalogTab
Related Projects
RelatedProjectTab
List of projects linked to the current object.
- Only project managers can associate a project with the current object. If this is not the case, no projects will appear in the list.
- Update: Use the Link Asset to Project wizard.
Blackout - All
List of all blackout periods defined for the current CI. This includes the Blackout - CIs and Blackout - Change Requests tabs.
Blackout - CIs
List of blackout periods defined for the current CI.
- Update: In this tab or run the New Blackout Period wizard.
Blackout - Change Requests
List of blackout periods defined for the current CI for change requests.
- Update: Run the New Blackout Period wizard in Change Request forms.
Amount Charged Back
AmountChargedBackTab
Details of the current object's charge back to the relevant cost centers. The amount charged back can be broken down by cost center calculated using their sharing value coefficient. See the examples
Procedures and Wizards
How to create a CI using an item of equipment
Step 1: Search for the item of equipment.
1. Select Asset & Configuration > Equipment > Inventory in the menu.
The equipment list will appear.
2. Select the item of equipment you want to manage in the CMDB.
Step 2: Create the CI.
1. Run the Manage in the CMDB wizard.
2. Specify the CI name and its status.
3. Click Finish.
The CI form will automatically appear.
Step 3: Define the relationship with the other CIs (impacting / impacted).
1. Select the Impacting CIs and Impacted CIs tabs.
2. Click New to add all the impacting / impacted CIs for the current CI.
- Relationship Type: This item of information does not affect operations in the CMDB.
- Tick the Blocking Component in case of Failure box if the relationship is blocking.
3. Click Finish.
Step 4 (optional): View the CMDB graph.
1. Click below the Name field.
The graph will appear. See the description.
2. Edit the layout of the graph you want.
3. Close the window to return to the CI form.
How to create an application CI or service CI
Step 1: Search for the item of equipment.
1. Select Asset & Configuration > Configuration Items (CIs) in the menu.
2. Click 
New in the top banner.
3. Select the associated model in the CI Catalog.
4. Specify the type of CI to create.
Application CI
- Tick the Integrated to the DML box.
- Click Finish.
- The form of the new CI will appear.
- The CI will automatically be created in the Definitive Media Library (DML) (Asset & Configuration > DML menu).
Service CI
- Tick the Is a Service box.
- Click Finish.
- The form of the new CI will appear.
- The CI will automatically be created in the Service Catalog (Service Design > Service Portfolio > Service Catalog menu).
Step 3: Define the relationship with the other CIs (impacting / impacted).
1. Select the Impacting CIs and Impacted CIs tabs.
2. Click New to add all the impacting / impacted CIs for the current CI.
- Relationship Type: This item of information does not affect operations in the CMDB.
- Tick the Blocking Component in case of Failure box if the relationship is blocking.
3. Click Finish.
Step 4 (optional): View the CMDB graph.
1. Click below the Name field.
The graph will appear. See the description.
2. Edit the layout of the graph you want.
3. Close the window to return to the CI form.
Wizards
Link Assets to Project
Archive CI
Collisions Detection
Unlock CI
Create Unavailability
Impact Analysis
End of Unavailability
Manage in the Service Catalog
Remove from CMDB
Notification for Information
New Continuity Plan
New Event
New Incident
New Change Request
New Service Request
New Blackout Period
Availability Simulation
CI Status:Update
Lock CI
Version: Update
Version: Prepare