Basic CMDB - quick start guide
Basic CMDB - quick start guide
You have been asked to set up "some kind of asset database" for the IT team. Maybe you are replacing a spreadsheet that got out of hand. Maybe someone mentioned ITIL in a meeting and now everyone wants a CMDB. Either way, you need something that works, and you need it before lunch.
The Basic CMDB gives you exactly three object types: Person, Server, and Application. No overengineering, no six-month design phase. Deploy it, add your first records, and you will have a working CMDB within an hour.
When to use this schema
The Basic CMDB is designed to get you started quickly with minimal complexity. Deploy it in these scenarios:
First CMDB: Your team has never used a CMDB and you need to demonstrate value before investing in a larger schema.
Small IT teams: You have fewer than 10 IT staff and fewer than 100 servers, and need simple visibility into who manages what.
Spreadsheet replacement: You currently track servers and applications in spreadsheets and need a structured, queryable alternative.
Pilot project: You want to evaluate Assets with real data before committing to a larger schema deployment.
Not quite right? If you need to track networks, databases, cloud resources, or software licences, start with the Standard CMDB. If you need shared organisational data (teams, departments, vendors) that other schemas will reference, use the Core Schema. If you have complex infrastructure with 100+ servers or multi-site operations, the Standard CMDB will save you from outgrowing this schema within weeks.
Schema overview
Why start basic
| Benefit | Description |
|---|---|
| Fast Implementation | Deploy in under an hour |
| Low Maintenance | Minimal ongoing data entry |
| Easy Adoption | Team learns quickly |
| Clear Value | Immediate visibility gains |
| Smooth Growth | Natural upgrade path |
Object type summary
| Object Type | Purpose | Record Count Target |
|---|---|---|
| Person | IT team members and stakeholders | 5-50 records |
| Server | Physical and virtual servers | 10-100 records |
| Application | Business applications | 5-50 records |
Relationship architecture
┌──────────────┐ ┌──────────────┐ ┌──────────────┐
│ Person │◄──────│ Server │◄──────│ Application │
│ (IT Team) │Managed │(Infra- │Runs On│ (Software) │
│ │ By │ structure) │ │ │
└──────────────┘ └──────────────┘ └──────────────┘
Screenshot coming soon
Key relationships:
Server → Person (Managed By): "Who manages this server?"
Application → Server (Runs On): "Where does this app run?"
Application → Person (Managed By): "Who manages this application?"
Documentation
This guide is split into three focused sections:
Object type reference: Full attribute tables, allowed values, naming conventions, and real-world examples for all three object types (Person, Server, Application).
Deployment guide: Step-by-step walkthrough from planning your data to verifying relationships, plus four common relationship patterns to follow.
Growing and maintaining your CMDB: When to upgrade to a larger schema, how your data migrates, troubleshooting tips, essential AQL queries, and weekly health checks.