| Name | Parent | Child | Description |
| Author of | Author of the selected CI | Selected CI is written by this CI | The attribute pertains to the authorship of a selected CI |
| Backed up by | Back up of the selected CI | Is backed up by the Selected CI | This feature refers to the backup status of a chosen CI |
| Cluster of | Belongs to the cluster of the selected CI | Belongs to the cluster of the selected CI | This signifies the membership of a chosen CI within a specific cluster. |
| Connected by | Selected CI is connected by this CI | Connected by the selected user | Indication that the chosen CI is connected by another CI or user, highlighting a relationship where the selected CI is linked or associated with the connecting CI or user. Example: Internet Connection, a smartphone is connected by a cellular network, providing access to the internet. |
| Connected to | Selected CI is connected to this CI | Connected to the selected CI | Showcases a connection or relationship between the two components. For example: IoT, the connected to field for the bulb would display the hub’s name. |
| Consists of | Selected CI consists of this CI | Consists of selected CI | This indicates that the chosen Configuration Item is composed of or includes another CI as its component or part, highlighting a relationship where the selected CI is made up of the specified component CI. Example: Data model, a database schema consists of tables, relationships, and attributes that define the data structure. |
| Consumed by | Selected CI is consumed by this CI | Consumed by the selected CI | This attribute indicates that the chosen Configuration Item is consumed or utilized by another CI or process, highlighting a relationship where the selected CI is a resource, input, or service used by the consuming CI. Example: Service Dependency, a micro service is consumed by another micro service in a micro services architecture. |
| Attached by | Selected CI contains this CI | Is attached by the selected CI | This attribute indicates that the chosen Configuration Items attached, linked, or associated with another CI, highlighting a relationship where the selected CI is connected or added as a component or part to the attaching CI.Collaborative Document contains an attached comment thread for discussions. |
| Contains | Selected CI contains this CI | Contains the selected CI | Indication that the chosen Configuration Item includes, encompasses, or holds another CI as a part, component, or element, highlighting a relationship where the selected CI acts as a container for the contained CI. Example: Database Table contains multiple tables that store structured data. |
| Cools | Selected CI cools this CI | Cools the selected CI | The attribute indicates that the chosen Configuration Item functions to cool, dissipate heat, or regulate temperature for another CI, highlighting a relationship where the selected CI plays a role in maintaining the temperature of the cooled CI. |
| Defines Resources for | Selected CI defines resources for this CI | Define Resources for the selected CI | The chosen Configuration Item establishes, specifies, or sets resources, capabilities, or allocations for another CI, highlighting a relationship where the selected CI provides resource definitions or guidelines to the CI it defines resources for. Example: Cloud Resource Configuration defines resources like virtual machines and storage for a cloud deployment. |
| Depends on | Selected CI depends on this CI | Depends the selected user | This attribute indicates that the chosen Configuration Item relies on or has a dependency on another CI or user, highlighting a relationship where the selected CI requires the support, functionality, or input of the depending CI or user to operate effectively. Example: Network Connectivity, a printer depends on network connectivity to receive print jobs from users. |
| Distributed by | Selected CI is distributed | Is distributed by the selected CI | The chosen Configuration Item is distributed or made available to others by another CI, entity, or user, highlighting a relationship where the distributing CI facilitates the dissemination or availability of the selected CI. Example: Newsletter Dissemination. An email newsletter is distributed by a company to its subscribers. |
| DR provided by | Selected CI's DR (Disaster Recovery) is provided by this CI | DR provided by the selected CI | The chosen Configuration Item serves as the source or provider of Disaster Recovery capabilities for another CI, highlighting a relationship where the providing CI ensures the availability of recovery mechanisms in the event of a disaster affecting the selected CI. Example: Data archival system ensures disaster recovery by storing historical data for compliance and recovery purposes. |
| Editor | Editor of the selected CI | Edited by the selected user | Indication that the chosen Configuration Item is associated with an entity or user who is responsible for making edits, modifications, or updates to the content, settings, or configuration of the selected CI. This relationship highlights the role of the editor in managing changes to the selected CI. Document Editor: An editor is responsible for editing and revising a document (selected CI) to improve its content. |
| Enables | Enables the selected CI | Is enabled by the selected CI | This attribute indicates that the chosen Configuration Item empowers or allows the functionality, operation, or capabilities of another selected CI. This relationship highlights the role of the enabling CI in providing necessary support or resources for the enabled CI. Example: An API enables developers to interact with software components programmatically. |
| Exchanges | Selected CI exchanges information with the selected CI | Exchanges information with the selected CI | Indication that the chosen Configuration Item is involved in a two-way exchange of information, data, or communication with another selected CI. This relationship highlights the active communication and interaction between the two CIs. Data Synchronization: Two databases exchange data updates to ensure consistency between them. |
| Exchanges data with | Selected CI exchanges data with this CI | Exchanges data with the selected CI | The attribute indicates that the chosen CI shares or transfers data with another CI, highlighting a relationship where both Cis interact to exchange specific data or information. Example: API Communication A web application can exchange data with a third-party API to retrieve external information or perform specific actions. |
| Feeds | Selected CI feeds this CI | Is fed by the selected CI | The chosen Configuration Item provides data, information, resources, or inputs to another CI, highlighting a relationship where the selected CI serves as a source or supplier of essential elements to the fed CI. Example: Sensor Data in a smart home feed data on temperature, humidity, and occupancy to a central control system. |
| From template | Selected CI has this CI | From template for selected CI | The indicates that the chosen Configuration Item is derived, created, or instantiated from a specific template CI, highlighting a relationship where the selected CI is based on or follows the structure, configuration, or guidelines provided by the template CI. Example: Software codebase is developed following a coding template for coding standards and best practices. |
| Has Registered | Selected CI has been registered to this CI | Has registered on the selected user | The chosen Configuration Item has been registered or recorded on another CI, highlighting a relationship where the selected CI is associated with or documented on the registering CI. Example: Software License has been registered with a licensing server, enabling the authorized use of the software. |
| Hosted on | Selected CI has been hosted on to this CI | Hosted on the selected CI | This attribute indicates that the chosen Configuration Item is hosted, deployed, or run on another CI, typically a server or computing environment. This relationship highlights that the selected CI relies on the hosting CI for execution and resources. Example: Cloud Service Hosting is hosted on a cloud provider’s infrastructure for scalability and availability. |
| Impacted By | Selected CI is impacted by this CI | Impacted by the selected CI | The chosen Configuration Item is affected, influenced, or impacted by another CI, event, or factor, highlighting a relationship where the selected CI's functioning, state, or performance is influenced by the impacting CI or event. Example: Network Outage, a server is impacted by a network outage causing loss of connectivity. |
| Implement End Point To | Selected CI is implemented the endpoint from this CI | Implement the endpoint from the selected CI | Indication that the chosen Configuration Item has implemented an endpoint from another CI, implying that the selected CI has established a connection, interface, or access point to the endpoint CI. Example: IoT Device Interaction, a smart home controller implements endpoints from various IoT devices to control and monitor them. |
| In Rack | Selected CI has been in rack to this CI | In Rack contains the selected CI | The chosen Configuration Item is physically located within or housed in a specific rack or rack unit. This relationship highlights the physical placement of the selected CI within the specified rack. Example: Storage system are installed in storage racks for data storage and retrieval. |
| Includes | Selected CI has been included on to this CI | Includes the selected CI | The chosen Configuration Item encompasses or contains another CI as a component, feature, or part, highlighting a relationship where the including CI has the selected CI as an integral element. Example: Software Module, an application suite includes individual software modules that provide specific functionalities. |
| Instantiates | Selected CI has been instantiated on this CI | Instantiates the selected CI | This attribute indicates that the chosen Configuration Item has been created, initialized, or instantiated on another CI, typically a computing environment or platform. This relationship highlights the process of setting up and initiating the selected CI within the context of the instantiating CI. Example: Software execution, an application is instantiated on a user's device or computer to run and perform tasks. |
| IP Connection | Selected CI has IP Connection to this CI | IP connection of the selected CI | This attribute indicates that the chosen Configuration Item is linked or connected to another CI through an Internet Protocol connection, facilitating data transmission and communication between the two CIs. Example: Remote Access, a remote desktop application, uses IP connections to allow remote access to a host computer. |
| Located In | Selected CI located in this CI | Located In for the selected CI | The chosen Configuration Item is physically situated within or positioned inside another CI, typically a larger or encompassing physical entity. This relationship highlights the spatial location of the selected CI. Example: Storage room, files are located in a storage room for safekeeping. |
| Located in Zone | Selected CI located in zone to this CI | Located In zone for the selected CI | This attribute indicates that the chosen Configuration Item is positioned within a specific zone or area, usually with defined boundaries or characteristics. This relationship highlights the spatial location of the selected CI within the context of the zone CI. Example: Medical zone, the Medical devices are located in a medical zone within a hospital.
|
| Manages | Selected CI has been managed on to this CI | Manages the selected CI | The chosen Configuration Item is under the management, control, or supervision of another CI or entity. This relationship highlights the overseeing and administrative role of the managing CI over the selected CI. Example: Asset Management, an IT asset management system manages computers and devices by tracking their usage and status. |
| Master of | Selected CI has master of the selected CI | Master of the selected CI | This attribute indicates that the chosen Configuration Item serves as a master or primary entity in relation to another CI. This relationship highlights that the selected CI is governed, controlled, or derived from the master CI. Example: Master Configuration, a master configuration file, defines standard settings for software applications. |
| Owns | Selected CI has been owned on to this CI | Owns the selected CI | The chosen Configuration Item is owned, possessed, or controlled by another CI or entity. This relationship highlights the ownership and responsibility that the owning CI has over the selected CI. Example: Resource Ownership, a team owns a shared server and manages its access and usage. |
| Powers | Selected CI has been Powered on to this CI | Powers the selected CI | Indication that the chosen Configuration Item is a source of power that enables the operation or functionality of another CI. This relationship highlights the role of the powering CI in supplying the necessary energy for the selected CI. Example: Power adapter, powers a printer by converting electrical current. |
| Provided By | Selected CI depends on this CI | Provides by the selected user | This Configuration Item relies on or is supported by another CI or entity for specific resources, services, or functionalities. This relationship highlights the provider's role in offering what the dependent CI needs. Example: Network connection, an application depends on a network router to establish internet connectivity. |
| Provides storage for | Selected CI's storage is provided by this CI | Provides storage for the selected CI | This attribute serves as a source or provider of storage resources for another CI. This relationship highlights the role of the providing CI in supplying the storage capacity required by the dependent CI. Example: Storage Array provides high-performance storage for databases in an enterprise environment. |
| Provisioned From | Selected CI depends on this CI | Provisioned from the selected CI | The chosen Configuration Item is provisioned, set up, or derived from another CI or entity. This relationship highlights the source from which the selected CI is created or obtained. Example: Server blueprint, a physical server is provisioned from a server blueprint that defines hardware and software settings. |
| Receives data from | Selected CI depends in this CI | Receives data from the selected CI | This attribute indicates that the chosen Configuration Item receives data, information, or communication from another source or CI, highlighting a relationship where the selected CI depends on the specified CI to provide data or input. Example: IoT Data exchange is a central data hub receives data from multiple IoT devices for storage and analysis. |
| Registered on | Selected CI has been registered on this CI | Registered on the selected CI | Indicates that the chosen CI is registered or associated with a specific user, highlighting a relationship where the selected CI is linked to the specified user for identification or ownership purposes. Example: Software Licenses is registered on user’s account, indicating that the user has ownership rights to use the software. |
| Routes Traffic | Selected routes traffic depends on this CI | Routes Traffic for the selected CI | This attribute plays a role in directing or routing network traffic for another CI. This relationship highlights the routing capabilities of the routing CI and its influence on the path of traffic for the selected CI. Example: Router, routes network traffic between subnets and directs data packets for servers. |
| Runs | Initiated running for selected CI | Runs the selected CI | Configuration Item initiates or is responsible for the execution and operation of another CI. This relationship highlights the role of the running CI in starting and managing the functionality of the selected CI. Example: Web Server, a web server runs websites and serves web content to users. |
| Sends Data To | Selected CI sends data to selected CI | Sends data to selected CI | The attribute indicates that the chosen Configuration Item is capable of transmitting or forwarding data to another selected CI. This relationship highlights the ability of the sending CI to deliver information or data to the receiving CI. Example: Network device, a computer sends data to a printer for printing. |
| Submits | Selected CI has been submitted to this CI | Submits the Selected CI | This attribute indicates that the chosen Configuration Item is presented or provided to another CI or entity for a specific purpose, often involving approval, review, or processing. This relationship highlights the action of submitting the selected CI to the receiving CI. Example: Document Submission, an employee submits an expense report to the finance department for reimbursement. |
| Subscribes to | Selected CI depends on this CI | Subscribes to by selected user | The attribute indicates that the chosen Configuration Item is linked to or relies on another CI or entity for receiving updates, notifications, or information. This relationship highlights the act of subscribing to the source CI for relevant updates. Example: Software Updates, a system administrator subscribes to software updates for security patches. |
| Supports | Selected CI has been supporting to this CI | Supports the selected CI | The chosen Configuration Item provides assistance, help, or resources to another CI or entity. This relationship highlights the role of the supporting CI in aiding and assisting the supported CI. Example: Technical Support, a help desk provides technical support to resolve issues with software applications. |
| Use End Point To | Selected CI uses end point to this CI | Use End Point to the selected CI | The chosen Configuration Item leverages or interacts with another CI or entity as an endpoint to achieve a specific purpose. This relationship highlights the utilization of the endpoint CI to fulfill a particular function for the using CI. Example: Messaging Platform, a chatbot uses a messaging platform's endpoint to interact with users. |
| Used by | Selected CI is used by the this CI | Used by the selected user | This attribute indicates that the chosen Configuration Item is actively utilized, operated, or relied upon by another CI or entity. This relationship highlights the role of the using CI in utilizing the functionalities or resources of the selected CI. Example: Application Usage, a software application is used by end-users to perform tasks. |
| Virtualized by | Selected CI is virtualized by this CI | Virtualized by the selected CI | The chosen Configuration Item has been transformed into a virtualized instance by another CI or entity. This relationship highlights the role of the virtualizing CI in creating and managing virtual instances of the selected CI. Example: Desktop virtualization, virtualizes desktop environments for remote access. |