# Blueprint Catalog exports — v0.2.0

Content CC BY 4.0 © Mike Reams (https://catalog.mikereams.com). All files are UTF-8 CSV, one row per capability unless noted, ordered
parents first (L1, then L2, then L3), so a single-file import never meets a child before its parent. Cells that start
with = + - @ are prefixed with ' to keep spreadsheets from running them.

| File | For |
|---|---|
| capabilities.csv | Any tool: id, parent_id, level, name, description, aliases, scope, domain, industry, url |
| servicenow-business-capabilities.csv | ServiceNow import set → Business Capability (cmdb_ci_business_capability) |
| leanix-business-capabilities.csv | LeanIX Excel/CSV import of Business Capability fact sheets |
| ardoq-capabilities.csv | Ardoq Excel/CSV import with a component path |
| product-capability-map.csv | Product capability → business capability edges (one row per edge) |

## ServiceNow

1. Create a data source from servicenow-business-capabilities.csv and load it into an import set table.
2. Transform map to Business Capability (cmdb_ci_business_capability): name → Name, short_description → Description,
   coalesce on a field that holds u_external_id (add a string field if your instance has none).
3. Resolve the parent in the transform (an onAfter script that looks up the record whose external id equals
   u_parent_external_id and sets the Parent shown on the Business capability form). Because rows are parents first, every
   parent already exists when its children load.
4. Test on a sub-production instance first; capability levels are recalculated by the platform's capability-level job.

## LeanIX

The file follows LeanIX's import rules: id, type and name columns present (id left empty so new fact sheets are
created), parents before children. Parents are referenced by display name; 36 names occur more than once in
the catalog, and only those carry their catalog id in brackets so every reference is unique. Export a template from your
own workspace first and rename the parent column to the header your workspace uses for the Business Capability
hierarchy. Run the import in test mode before writing.

## Ardoq

Map Path as a Component path (separator ::) with "create new component" enabled; Ardoq creates the parent–child
hierarchy from the path. Map Custom ID to the component's custom id so later imports update instead of duplicating.

These files describe how the catalog is shaped for each tool; field names in your tenant may differ. Not affiliated with
ServiceNow, LeanIX or Ardoq.