Service operations

Register disruption, set impact and urgency, coordinate restoration, and confirm closure evidence.

Use a dedicated major incident, establish command, coordinate responders, and verify external updates.

Document a root-cause investigation, select the correct change path, and validate implementation.

Compare SLA and contract targets, verify time calculations, and trace missing commitments.

Use the incident lifecycle, including hold reasons, restoration evidence, and the five-business-day reopening window.

Choose the approval path, satisfy the schedule and implementation gates, and verify the post-implementation review.

Use the requested-items and approval tabs, then confirm what was actually delivered.

11 declared fields for Blackout period. Required fields include Blackout name, Starts, Ends, Scope.

11 declared fields for CAB meeting. Required fields include Meeting name, Board, Meeting date and time, Approval group.

19 declared fields for Standard change template. Required fields include Template name, Description, Implementation plan, Test plan.

19 declared fields for Service task. Required fields include Parent ticket, Parent module, Task type, Short description.

39 declared fields for Incident. Required fields include Short description, Description.

48 declared fields for Major incident. Required fields include Short description, Description, Impacted business service.

45 declared fields for Problem. Required fields include Short description, Description.

67 declared fields for Change. Required fields include Short description, Description, Change type, Planned start.

44 declared fields for Request. Required fields include Short description, Description.