ITSMJune 27, 2026
Change and Release Management
Change and Release Management governs how work reaches your live environment. Every change is proposed, assessed for risk, approved by the right authority, and scheduled so it lands without colliding with other work or breaking dependent services. Approval gates, submission controls, and a full change history give you the assurance to move fast without inviting the next outage. The payoff is a higher rate of successful changes and far fewer self-inflicted incidents.
Use the Change and Release Management semantic blueprint
/semantius-admin use the architect, analyst and modeler skills to update the semantius platform with the model specified in https://www.semantius.com/blueprints/itsm-change-mgmt-semantic-blueprint.mdEntity summary
| Name | data_object | Description |
|---|---|---|
| CAB Meetings | cab_meetings |
Change Advisory Board meeting records covering agenda, attendees, changes reviewed, decisions, and minutes. |
| Change Collisions | change_collisions |
Detected conflicts between overlapping changes or a change scheduled in a blackout window, recording the colliding changes and the resolution. |
| Changes | service_changes |
Planned modifications to a service or configuration item, with change type, risk score, approval state, schedule, and back-out plan. |
| Service Releases | service_releases |
Release records that bundle one or more changes into a single shippable unit, with the release window, status, and rollback plan. |
| Configuration Items | configuration_items |
Canonical records of IT things under management: servers, containers, applications, services, network devices, databases, and cloud resources. |
| Locations | locations |
Physical or organizational locations referenced across the system, used to place and group other records. |
| Org Units | org_units |
Nodes in the organizational hierarchy such as divisions, departments, and teams, with manager, cost center alignment, geographic scope, and parent-child links. |
flowchart TD classDef master fill:#d4f4dd,stroke:#27ae60,color:#0b3d20; classDef embedded_master fill:#fff4cc,stroke:#c79100,color:#5b4500; classDef platform_builtin fill:#e0e0e0,stroke:#424242,color:#1a1a1a; locations["Locations"] service_changes["Changes"] configuration_items["Configuration Items"] org_units["Org Units"] service_releases["Service Releases"] cab_meetings["CAB Meetings"] change_collisions["Change Collisions"] users["Users"] service_changes -->|"updates"| configuration_items configuration_items -->|"changed_by"| service_changes service_changes -->|"impacts"| configuration_items org_units -->|"rolls_up_to"| org_units locations -->|"rolls_up_to"| locations users -->|"owned CIs"| configuration_items users -->|"leads"| org_units users -->|"owned changes"| service_changes service_changes -->|"is_approved_by"| users org_units -->|"has members"| users locations -->|"houses"| users class locations embedded_master; class service_changes master; class configuration_items embedded_master; class org_units embedded_master; class service_releases master; class cab_meetings master; class change_collisions master; class users platform_builtin; style locations stroke-dasharray:5 5; style org_units stroke-dasharray:5 5;