Basic CMDB
Basic CMDB
Two object types. One hour. Your first working CMDB.
The Basic CMDB is the simplest schema in LaunchPad. Version 2.0 keeps just two object types of its own, Server and Application, and connects them to the people and places that matter through references to the Core schema. It is purpose-built for small IT teams who need to stop tracking infrastructure in spreadsheets and start tracking it properly, without spending weeks designing a schema first.
What you get
| Object Type | Purpose | Key Attributes |
|---|---|---|
| Server | Physical and virtual servers | Hostname, IP address, server type, operating system, environment, status, plus references to Person (Managed By) and Location (Located In) |
| Application | Software applications | Application name, version, environment, status, plus references to Person (Managed By) and Server (Runs On) |
2 object types · 3 reference types
The relationships answer the questions every IT team asks first: applications run on servers, servers sit in locations, and people manage both. Person and Location are not duplicated inside this schema; they are Core schema types that Basic CMDB references, so the same person record can manage a server here and own a contract in another schema.
The template also ships with a small set of sample servers and applications, so you can see working relationships before you add a single record of your own.
No Core schema yet? You still get the full model
Basic CMDB is often the very first thing a team installs, before Core or anything else. That is fine. At deploy time, LaunchPad asks you how to resolve each external reference (Person and Location), and you choose one of three modes:
| Mode | What happens | When to choose it |
|---|---|---|
| Link to Core | Managed By and Located In point at the Person and Location types in your installed Core schema | Recommended whenever Core is already deployed |
| Create here | LaunchPad creates Person and Location inside your Basic CMDB schema, using the bundled Core definition (one level, scalar attributes only) | First install with no Core present; you want real, linkable records from day one |
| Keep as text | Managed By and Located In become free-text attributes | You only want a name typed in a box, with no linked records |
A first-run user who picks Create here still ends up with a working model: Server and Application plus real Person and Location records they can link to, query, and report on. Nothing about the day-one experience requires Core to be installed first.
Pro tip: If you know you will grow into multiple schemas, deploy Core first and choose Link to Core. Shared people and locations from the start means no consolidation work later. If today is about getting a CMDB working before lunch, Create here is the right call.
When to use this schema
Choose the Basic CMDB if:
-
You have fewer than 100 servers and a small IT team.
-
You want a working CMDB before lunch, not a six-week design project.
-
Your immediate goal is simple asset tracking and ownership visibility.
-
You are new to Assets and want to learn the fundamentals with a manageable schema.
If you need more depth (databases, network devices, cloud infrastructure), look at the Standard CMDB instead. Not sure which schema fits? See Which Schema Should I Choose?
Schema at a glance
Server ────── (Managed By) ──▶ Person (Core)
Server ────── (Located In) ──▶ Location (Core)
Application ─ (Managed By) ──▶ Person (Core)
Application ─ (Runs On) ─────▶ Server
Two object types, three reference types (Managed By, Runs On, Located In). Deploy it in under an hour and start adding real data immediately.
Documentation
Quick Start Guide Step-by-step deployment guide. Takes you from zero to a working CMDB in under an hour, including the deploy-time reference choices, record creation order, and verification queries.
Governance playbook and forms specification for this schema are part of the LaunchPad Playbooks offering (coming soon).