Service catalogue
Service catalogue
Ask three people in your organisation which IT services exist, who owns them, and what response times apply, and you will get three different answers. The Service Catalogue schema replaces that guesswork with a structured, browsable catalogue where every service has a named owner, a defined service level, and a documented way to request it.
Version 2.0 extends the Core Schema. People and teams are no longer duplicated inside the catalogue: service ownership points at Core's Person type and support responsibility points at Core's Team type, so the same person and team records serve every schema you deploy.
What you get
| Object Type | Purpose | Key Attributes |
|---|---|---|
| Service Category | Groupings that organise services for browsing | Category name, description, icon, display order, status |
| Service Level | SLA definitions with response and resolution targets | Level name, availability target, response time, resolution time, support hours |
| Business Service | Customer-facing services available to the organisation | Service name, category, service level, owner, support team, criticality, status |
| Service Offering | Specific offerings or request types within a service | Offering name, parent service, price, fulfilment time, approval required |
| Knowledge Article | Self-service documentation and guides | Title, URL, article type, service, last updated, views |
| Service Request Type | Types of requests that can be made for services | Request type name, parent service, expected SLA, approval required |
6 object types · 6 reference types · extends Core Schema
Together with Core's Person and Team, these model the full lifecycle of a service: what it is, who owns it, what level of support applies, how users request it, and where the documentation lives.
What comes from Core
Two roles that earlier versions modelled locally now live in the Core Schema:
| Role | Core object type | How the catalogue uses it |
|---|---|---|
| Service owner | Person | Business Service's required Owner attribute (Owned By reference) |
| Support team | Team | Business Service's Support Team attribute (Supported By reference) |
Core's Team type also carries the operational detail the catalogue used to hold itself: escalation path, on-call rotation, email, and Slack channel all live on the Team record.
When you deploy, LaunchPad asks how to resolve each external reference:
- Link to Core, which connects to your existing Core Schema (recommended when Core is installed)
- Create here, which builds the Person and Team types inside this schema from the bundled Core definition
- Keep as text, which keeps the attribute as free text with no object reference
Pro tip: Start with your five most-used services. Define those fully (business service, offering, level, owner, support team) before expanding to the rest. A small, complete catalogue is far more useful than a large, half-finished one.
When to use this schema
Deploy the Service Catalogue if:
-
You need to publish a structured catalogue of IT services for your organisation.
-
Service ownership is unclear and you want explicit accountability for each service.
-
You are connecting services and request types to SLAs and need those relationships modelled in Assets.
-
Your service desk team needs a single reference for what is supported and by whom.
This schema is designed to sit on top of the Core Schema, which supplies the shared people and team records. It also pairs well with SLA Management for enforcement and escalation. If your focus is infrastructure tracking rather than service delivery, look at the Standard CMDB instead.
Not sure which schema fits? See Which Schema Should I Choose?
Schema at a glance
Business Service ──(Categorized As)──▶ Service Category
Business Service ──(Governed By)────▶ Service Level
Business Service ──(Owned By)───────▶ Person (Core)
Business Service ──(Supported By)───▶ Team (Core)
Service Offering ─────(Part Of)─────▶ Business Service
Service Request Type ──(Part Of)────▶ Business Service
Service Request Type ──(Governed By)▶ Service Level
Knowledge Article ──(Documented In)─▶ Business Service
Six object types modelling the service delivery chain, with every relationship carrying its own reference type: Categorized As for category membership, Governed By for service level assignment, Part Of for the offering and request type hierarchy, Owned By and Supported By for the Core links, and Documented In for knowledge coverage.
Documentation
Quick Start Guide Step-by-step deployment guide covering service hierarchy, Core resolution, ownership assignment, and SLA linkage.
Governance playbook and forms specification for this schema are part of the LaunchPad Playbooks offering (coming soon).