Change management
Changes with their governance gates, and whether the process was followed.
Change management
Record changes with the approval they needed, the back-out plan and the window they ran in. Governance rules decide what each change class requires, and change metrics show how much of the estate is changing outside the process.
Key capabilities
- Change classes with governance gates
- Approval, ownership and back-out plans
- Maintenance windows
- Attachments and evidence against each change
- Change metrics and reporting
Configuration management (CMDB)
A configuration-item register with a graph of how items relate. Import from CSV to get started, then keep the links that let a change request show its blast radius, so you answer "what else does this touch" before a change rather than after an incident.
Key capabilities
- Configuration items with attributes and relationships
- Configuration-item graph
- CSV import and bulk update
- Links to assets and changes
Proof point
A change linked to its configuration items shows its blast radius before it runs, so "what else does this touch" is answered before the change, not in the incident review.
Questions about this module
Do we need a change advisory board?
No. Frameworks require a documented process with approvals and records, not a committee. A reviewer other than the author, recorded in the tool, satisfies most requirements for engineering changes.
What counts as an emergency change?
A change deployed before the normal approval to restore service or fix a security issue. It must be reviewed and approved after the fact, and that review is the evidence.
Which tools does this pull from?
GitHub, GitLab, Jira, Linear, Asana and CI systems through the integrations page.