App catalogue IT and operations

Change advisory board

Runs the weekly change advisory board on the live change calendar: every change with its risk, conflicts and affected services, and the decision written back to the change request.

HIERARCHY · CHANGE ADVISORY BOARDChange ownersL1: change ownerscreen · usersService ownersL1: service ownerscreen · usersChange advisory boardL1: board membersscreen · usersL2: CAB chairscreen · usersa person created at a level is assigned their parent-level and child-level users at the same timeTrigger and flow criteriaA normal change waiting for board approval whose planned start is within the next 14 days.
The hierarchy: functions, levels, and the criterion that starts the flow. Each level carries a screen and its people.
4 days
of configuration to a production-grade version
estimate
6
screens, desktop and mobile
catalogue
4
data handlers, read in place
catalogue
1
systems with a page for this app
catalogue
3
clocks with escalation
catalogue
What it does

Today, and with the app

Today the change manager exports the week's changes on Tuesday, pastes them into a deck, and the board spends the first 30 minutes finding out which changes touch the same servers. Decisions are typed into ServiceNow after the meeting, and the ones that were deferred are found again the next week.

The app picks up every normal change that waits for board approval and starts within the next 14 days, and shows it with its risk, its configuration items and the services those items support, the open incidents on the same items and every other change in the same window on a related item. The change owner completes the plan, test evidence and backout plan, the service owner assesses the impact on the service, and the board members review the conflicts and risk before the meeting, so the meeting itself deals with the 5 changes that need a discussion. The CAB chair records the decision and any new window in the app, and the decision, the schedule and the note are written to the change request in ServiceNow within seconds.

Who takes part

Collaborative app: levels first, then screens per level, then people, then the flow and trigger criteria

FunctionLevelDoes
Change ownersLevel 1: change ownercompletes the plan, test evidence and backout plan
Service ownersLevel 1: service ownerassesses the impact on the service and its users
Change advisory boardLevel 1: board membersreview risk and conflicts before the meeting and vote
Change advisory boardLevel 2: CAB chairdecides and records the outcome
Screens

6 screens, composed from the handlers

Every screen renders for desktop and mobile; portal screens are the same screens delivered to an outside login.

ScreenWhat is on it
S01 This week's changesgrid of changes by start, risk, service, owner and readiness; conflict and incident flags; open button
S02 Change detailplan, test evidence, backout plan, affected configuration items with relations, open incidents on them, other changes in the window; complete
S03 Impact assessmentservice owner view: services affected, users, business calendar, impact rating; confirm
S04 Board reviewchanges ready for the meeting with votes and comments; the 5 to discuss first; decision buttons: approve, approve with a new window, defer, reject; note
S05 Calendarchanges by day and service with conflicts highlighted; drag to a new window
S06 Change boardchanges approved, deferred and rejected per week; changes followed by an incident; readiness at meeting time
Data handlers

4 objects, read where they live

The first object is the main one; each system page shows the real table or resource behind every handler.

ObjectWhy the app reads itSee it on
Change requestthe change request, its type, risk, window and approvalServiceNow
Configuration itemthe configuration items the change touches and their relationsServiceNow
Incidentopen incidents on the same configuration itemsServiceNow
Employeechange owners, service owners and board membersServiceNow

Written back

ObjectWhat changes
Change requestboard decision written to the approval record; state set to scheduled, deferred or rejected; start and end updated when the board moves the window; note added
The flow

From the trigger to the last write

THE FLOW · CHANGE ADVISORY BOARD1Change picked uprisk, configuration items,related changes and openincidents attached;readiness checklist shownto the owner2Ready for reviewplan, test evidence andbackout plan complete;service owner's impactrating recorded by Monday12:003Pre-reviewedboard members vote andcomment by Tuesday 17:00;changes with a conflict ora dissent go to thediscussion list4DecidedCAB chair records thedecision at the Wednesdaymeeting; a new windowresolves the conflict onthe calendar5Written backdecision, state and windowwritten to the changerequest; owners notified
Each step and the criterion that moves it.

Start: A normal change waiting for board approval whose planned start is within the next 14 days.

# start criterion, in canonical fields; each system page shows it in that system's fields
{change.type} = 'normal' and {change.approval} = 'requested' and {change.start} <= today + 14

StepMoves when
Change picked uprisk, configuration items, related changes and open incidents attached; readiness checklist shown to the owner
Ready for reviewplan, test evidence and backout plan complete; service owner's impact rating recorded by Monday 12:00
Pre-reviewedboard members vote and comment by Tuesday 17:00; changes with a conflict or a dissent go to the discussion list
DecidedCAB chair records the decision at the Wednesday meeting; a new window resolves the conflict on the calendar
Written backdecision, state and window written to the change request; owners notified
Actions, clocks and measures

What the components do, what the clocks enforce, what the board shows

ComponentTrigger → action → outcome
grd_changeson load → read the changes in the window and their configuration items → mark the ones sharing an item or a service, count the open incidents
btn_mark_readyon click → check that plan, test evidence and backout plan are attached → move the change to review, notify the service owner
cal_windowon drag → check the new window against the business calendar and the other changes → store the new start and end, clear the conflict flag
btn_decideon click → update the approval record and the state in ServiceNow → store the sys_id, notify the change owner, refresh S01

Clocks

StepTime limit and escalation
ReadinessMonday 12:00 of the board week, then the change owner is reminded and the change is listed as at risk of deferral
Pre-reviewTuesday 17:00, then members who have yet to vote are reminded
Emergency change2 hours for the chair and 1 member to review it from the mobile screen

Measures

changes decided before the meetingchanges deferred for readinessconflicts resolved on the calendarchanges followed by an incident within 7 daysmeeting length
A day with the app

Illustrative

Names, places and figures are illustrative; the pattern is the catalogue's.

On Monday at 09:00 the app listed 47 changes for the week at a telecom operator in Manchester, flagged 4 that touched the same billing database within 6 hours of each other, and showed 2 open incidents on the storage array one of them used. By Tuesday evening 39 were pre-approved by the members' votes; the Wednesday meeting took 25 minutes and dealt with the 8 remaining, and the chair, Owen, moved 2 windows on the calendar and deferred 1 for a missing backout plan. Every decision was on the change request in ServiceNow before the members left the room.

illustrative scenario · Change advisory board
On your systems

One page per system

The objects with their real names, the criteria in that system's fields, the write interface and what to set up first.

Other systems connect through the same handlers; see how SmartApps connect.

Terms on this page

Normal changeA planned change that needs the board's approval; standard changes run by rule and emergency changes are reviewed within hours.
Configuration itemThe record in ServiceNow for a server, database or application, with its relations to other items and to services.
Backout planThe steps that return the service to its previous state when the change goes wrong.
Questions

How long does it take to have this running?

About 30 minutes to a first running screen on your live rows, and 4 working days to the production-grade version described here, most of it spent agreeing screens and criteria with the process owner.

Which system does it run on?

Any of ServiceNow, with the objects read in place; the pages above show the objects and the write path for each. Two systems at once is one handler per object per system.

Who takes part from outside the company?

Every role in this app is inside the company; an outside role can be added as a lane with a portal screen.

What does the audit record hold?

Every step, value, decision, notification and write-back acknowledgement of every instance, with the version of the app, append-only.

See this app on your data

Bring the process and the systems it touches. In the first session we register the data handlers, draw the levels or the lanes and run the first screen on your live rows.