Forward Schedule of Change

: Originally from UCM Central
: [This template was based on the IEEE template IEEE 828.1:1990]

Change scheduling is a sub-procedure done as part of Change Management and typically done as part of your initial approval/acceptance procedure. The schedule is typically defined through the formal Change Control/Advisory Board meetings and discussion with relevant parties (IT & Business).

To ensure future planned changes are communicated in advance, it is necessary that all appropriate Changes be scheduled in a central database. The information should be updated as new changes are approved, or when changes are closed.

Below UCMcentral provide a template Forward Schedule of Change (FSC). Ideally this information will be held within the Configuration Management Database and distributed via Intranet mechanisms (Web and Email).

Forward Schedule of Change
Change Request ID	CR0000	CR0001	CR0002	…
Change Headline	Summary	Summary	Summary	…
Target Start Date/Time	DDMMYY/HHMM	DDMMYY/HHMM	DDMMYY/HHMM	…
Effort (Man Hours)	0	0	0	…
Scheduled Outage	0	0	0	…
Target End Date/Time	DDMMYY/HHMM	DDMMYY/HHMM	DDMMYY/HHMM	…
Known Outages	TBI	TBI	TBI	…
Contact List	TBI	TBI	TBI	…
Systems Affected	TBI	TBI	TBI	…
Comments	N/A	N/A	N/A	…
Project Management Plan	Reference	Reference	Reference	…
Status	OPEN	OPEN	OPEN	…

Note: The Data provided in the FSC will typically come directly from the Change Management systems. Concise project timeline and resource details will be provided through a referenced Project Management

-- PatrickEgan? - 16 Dec 2002

Edit • Attach • Print version • History: r2 < r1 • Backlinks • Raw View • Raw edit • More topic actions