# CI Relationship Mapper (COBIT BAI10)

> Draft the CMDB data model: how Hardware links to Software and Business Process. Ensures impact analysis is accurate. Includes orphan CI detector.



Tags: COBIT, BAI10, CMDB, Configuration, Impact Analysis


## Example Prompts

- Draft the data model for how our hardware links to software and business process
- Scan our configuration narrative for orphaned CIs (no service or owner)
- Define CMDB logic so impact analysis for changes is accurate

URL: https://rakenne.app/skills/ci-relationship-mapper/index.md

Try this skill: https://rakenne.app/a/?skill=ci-relationship-mapper



## Overview

Draft the CMDB data model: how Hardware links to Software and Business Process. Ensures impact analysis is accurate. Includes orphan CI detector.

## Example Conversation

> **You:** We're documenting our CMDB logic — which servers host which apps and how they link to business services. Can you draft the relationship model and check for orphan CIs?

> **Agent:** I'll draft a configuration narrative with CI relationships (e.g. Server X hosts Application Y; Application Y supports Order Fulfilment), assign owners and link each CI to a service where applicable, then run `orphan_ci_detector`.

> **Agent:** Created `cmdb-logic-bai10.md`. Running `orphan_ci_detector`...

> **Agent:** **FAIL** — orphaned CIs: legacy-db-01, backup-server-02 (no link to service or owner in the doc). I've added owner and service links for both. Re-running...

> **Agent:** **PASS** — all CIs now have a link to a service or owner. Impact analysis can trace changes to the business.

## What the Tools Validate

**`orphan_ci_detector`** scans the configuration narrative or CMDB logic document (Markdown or text):

- **Detection:** Identifies CIs from phrasing such as "server X", "application Y", "configuration item: Z", "hardware/software: …".
- **Rule:** For each CI mentioned, the document must state a link to a service or an owner (e.g. "links to", "owned by", "supports service", "assigned to") within context (same section or nearby).
- **Output:** PASS if every detected CI has a service/owner link; FAIL with a list of orphaned CIs. Add owner or link to business service and re-run so impact analysis is accurate (BAI10).

## Output Excerpt

**CMDB logic (excerpt):**

```markdown
## CI relationships (BAI10)

| CI              | Type     | Owner    | Supports service      |
|-----------------|----------|----------|------------------------|
| app-server-01   | Hardware | Infra    | Order Management       |
| order-mgmt-app  | Software | Product  | Order Management       |
| legacy-db-01    | Database | DBA team | Order Management (legacy) |
```

**orphan_ci_detector report (excerpt):**

```
=== ORPHAN CI DETECTOR (BAI10) ===
Result: PASS

Document: cmdb-logic-bai10.md
CIs detected: 3. Orphaned (no link to service or owner): 0.
All CIs have a link to a service or owner.
No orphaned CIs.
```

## Getting Started

Add your asset/CI list and any existing relationship or service catalog notes to the project workspace, then activate the *CI Relationship Mapper (COBIT BAI10)* skill. The agent will draft the relationship model and run `orphan_ci_detector` until no orphans remain.


---

Back to [Skill Library](https://rakenne.app/skills/index.md)