Service Management

Changes governed, not just tracked.

Change calendar with freeze windows, a Change Advisory Board with enforced segregation of duties, risk-based approval workflows, and full traceability from request through implementation to review.

Request a demo

What you can do

Capabilities

Change calendar and freeze windows

Visual calendar showing all scheduled changes. Freeze windows block non-emergency changes during critical periods (month-end close, release weekends).

CAB with segregation of duties

CAB membership and approval chains enforce SoD: developer ≠ approver ≠ basis admin. Constraints are configurable and audited.

Risk-based approval workflows

Standard, normal, and emergency change types with risk scoring. Higher risk triggers additional approval steps automatically.

Transport-as-Change (SAP)

SAP transports map to change records with STMS bidirectional sync, object-level collision detection, and landscape mapping.

Test evidence and rollback

Change records carry test evidence, rollback plans, and implementation notes — linked to affected CIs for full traceability.

Post-implementation review

Automated PIR prompts after change window closes. Success/failure metrics feed back into risk scoring.

Compliance relevance

How this connects to regulation

BAIT

BAIT 5 — Segregation of duties enforced in CAB approval chains.

MaRisk

AT 7.2 — Change governance with approval chains and test evidence.

DORA

Art. 8 — Change testing evidence and traceability.

Related features

Incident & Problem CMDB SAP SolMan Replacement

Common questions

FAQ

Standard (pre-approved), normal (CAB review), and emergency (expedited with post-approval). Each has configurable approval workflows.

SAP transports are represented as change records with bidirectional STMS sync. Collision detection flags conflicting objects before promotion.

See ITSMx against your own compliance checklist.

30 minutes. We’ll map it to your DORA / NIS-2 / BAIT obligations.

Request a demo Talk to us