Core schema
Core schema
Every LaunchPad schema needs to know about people, teams, vendors, and locations. The Core schema defines that master data once, so no other schema ever has to duplicate it.
This is the hub in LaunchPad's hub-and-spoke design. Deploy Core first, and every spoke schema you add afterwards (Standard CMDB, Cybersecurity, Vendor Management, and the rest) links its ownership and organisational references straight back to it. One source of truth, shared everywhere.
What you get
| Object Type | Purpose | Key Attributes |
|---|---|---|
| Person | Employees, contractors, and external contacts | Name, email, department, team, job title, manager |
| Team | Functional groups that own assets and receive tickets | Name, team lead, team type, escalation path |
| Department | Organisational structure units | Name, code, head, parent department, cost centre |
| Location | Physical places where people work and assets reside | Name, type, region, tier rating, capacity |
| Vendor | External organisations you purchase from or partner with | Name, type, relationship owner, risk level |
| Application | Software applications used by the organisation | Name, type, vendor, owners, criticality |
| Cost Center | Financial units for budget tracking and allocation | Name, code, owner, status |
| Business Service | Business-facing services delivered to internal or external customers | Name, service ID, criticality, owner, support team |
8 object types · 15 reference types
Together these eight types form your organisational directory: people belong to departments and teams, teams sit in departments, vendors provide applications, cost centres fund departments, and business services carry an owner and a support team. Business Service is new in v1.2, giving spoke schemas a shared service record to point at instead of inventing their own.
Pro tip: Core is designed as a foundation layer. You do not need to populate every object type on day one. Start with Person and Team, then add the rest as your CMDB matures.
When to use this schema
Deploy Core first if you intend to run two or more schemas side by side (for example, Standard CMDB alongside Vendor Management). At deploy time, the other schemas offer to link their people, team, vendor, and location references to your Core objects instead of duplicating organisational data.
If you only ever need a single schema, you can skip Core: each template can deploy standalone and create local copies of the types it needs. Core becomes valuable the moment you want one shared directory that multiple schemas point back to.
Not sure which path fits? See Which Schema Should I Choose?
Schema at a glance
Person ──(Member Of)──▶ Department / Team
Person ──(Works At)──▶ Location
Team ──(Part Of)──▶ Department
Department ──(Funded By)──▶ Cost Center
Vendor ──(Provides)──▶ Application
Application ──(Owned By)──▶ Person
Business Service ──(Supported By)──▶ Team
Eight object types, tightly connected. Spoke schemas reference Person, Team, Vendor, Location, and now Business Service rather than recreating them.
Documentation
Quick Start Guide Step-by-step deployment guide covering all eight object types, relationship configuration, and initial data population.
Governance playbook and forms specification for this schema are part of the LaunchPad Playbooks offering (coming soon).