Service model reference
Service model reference
A note on spelling. This documentation is written in British English, but the LaunchPad templates deploy into Jira Assets using the object type and field names exactly as the product ships them, and some of those use American spelling: for example Service Catalog, Cost Center, Color Code, Fulfillment Time, and the License fields. When you search Assets or write AQL, match the name as it appears in your instance (for example Service Catalog, not "Service Catalogue").
Each LaunchPad template comes with three documentation pages covering different aspects of day-to-day use.
The Quick Start Guide covers the template's purpose, its object types and attributes, deployment steps, and practical examples for getting data in quickly. Start here when deploying a new service model.
The Governance Playbook covers ownership responsibilities, data quality rules, review schedules, and lifecycle management. Read this once the service model is live and you need to keep it healthy.
The Forms Specification defines the recommended Jira Service Management portal forms for each object type in the service model. Use this when setting up request forms so that users can create and update records through a standardised interface.
How the catalogue fits together
The thirteen service models form a hub and spokes rather than a flat list. Core Schema is the hub: it holds the master data (people, teams, vendors, cost centres, business services) that every other domain refers to. The domain models are spokes that extend Core, and when you deploy one, each reference back to the hub is resolved in one of three modes: link to the existing Core object type, create the type locally, or keep the value as plain text. See Hub-and-spoke architecture for the model and The three reference modes for the deploy-time decision.
The five categories below group the service models by the job they do. They are organisational labels only and carry no price meaning: LaunchPad pricing is per object across the whole product, whatever category a model sits in. See Pricing.
Foundation
The hub plus the models most environments stand up first. Core Schema is the foundation in the strict sense: the master-data hub every other model builds on. Standard CMDB and Workforce Management sit in this category because each can act as a foundation when deployed standalone with people created locally via Create here, though the recommended foundation remains Core.
| Service model | Key | Object types | Version |
|---|---|---|---|
| Basic CMDB | BCMDB | 2 | v2.0 |
| Core Schema | CORE | 8 | v1.2 |
| Standard CMDB | SCMDB | 8 | v3.0 |
| Workforce Management | WFM | 9 | v3.2 |
Operational
Day-to-day service delivery: the catalogue you publish, the priorities you assign, and the service levels you commit to.
| Service model | Key | Object types | Version |
|---|---|---|---|
| Service Catalogue | SCAT | 6 | v2.0 |
| Priority Matrix | PRIO | 4 | |
| SLA Management | SLA | 3 | v1.1 |
Specialised
Deep coverage of a single technical domain, built as spokes on the Core hub.
| Service model | Key | Object types | Version |
|---|---|---|---|
| Cloud-Native Infrastructure | CLOUD | 10 | v1.1 |
| Cybersecurity | CSEC | 5 | v1.1 |
| Software Asset Management | SAM | 8 | v2.0 |
Enterprise
Large-estate models for organisations with many domains and many suppliers.
| Service model | Key | Object types | Version |
|---|---|---|---|
| Enterprise IT CMDB | ENTIT | 20 | v2.0 |
| Vendor Management | VEND | 11 | v2.0 |
Governance
Keeping the documentation and lifecycle of your service models under control.
| Service model | Key | Object types | Version |
|---|---|---|---|
| Documentation Management | DOCM | 7 | v1.2 |
Select any service model above to see its overview, then follow the links to the Quick Start Guide, Governance Playbook, and Forms Specification.