Best way to map specification characteristics from product/service order as an attribute in CI cmdb class

[VR17]

Best way to  map specification characteristics from product/service  order as an attribute  in CI  cmdb class .Looking for some best approach/documentation  to integrate Order management with CMDB

[Tom Schnarr]

There are a few hops to get from the product/service/resource (PSR) specification to the CI.

- each PSR specification is associated to a specification category.  Use the specification category to group similar specs - if they have a consistent fulfilment pattern - one spec maps to the sub-flows 

- each specification category then maps to a Model category.  Use theModel category to map the PSR to the ci class 

- for the specification category - you will then ensure your flow designer follows the pattern (use existing subflows for reference).  - in the task you can define additional characteristics to pass to the the relevant CI.

[SN Arch Guy]

Thanks Tom, but I am still unclear on several things relating to OMT, PSRs, and CSDM.

• So are you saying that there is no ServiceNow-provided mapping from PSR records to CMDB CI classes and records? That each customer must provide a flow to create the CIs that they want?
• In your example, you show a flow creating a Technical Service record. Would a flow need to be created or modified to create the actual cmdb_ci_firewall_device record? At what point in an order does / should this record get created, if at all?
• Referring to the PSR diagram in the docs, where would the cmdb_ci_firewall_device record belong? Is it a resource? Are there existing table relationships in ServiceNow that connect these things?
• If ServiceNow discovery is used, what would link the PSR tables to a CI that is found? The model category? But that assumes that the model category is filled out on the specification category?
• If viewing a CI record, is there a way to quickly get to the order, the resource, ... like via a related list?