IT Master Calendar Implementation Requests Criteria

IT Master Calendar Implementation Requests Criteria

Document number: 99003

The Master Calendar is a planning tool used by Project Managers and Requesters (for non-project activities) to identify appropriate and inappropriate windows for activities. The Master Calendar helps identify, in advance, target dates of activities impacting the production environment, allowing time to negotiate with the business or the PM/Requester. This tool is intended to avoid conflicts between planned changes so any change that has an application impact should be submitted to the calendar, even if it does not involve downtime.

The Implementation Request should be submitted as early in the process as practicable. This is a planning and coordination tool so the request should be made based on the target date even if there is a possibility that the date will change in the future. Providing a view of planned activities allows better coordination and reduces the risks of unexpected complications.

The following activities require an Implementation Request in the IT Master Calendar:

Project-related activities; more specifically projected Go-Live dates. This includes any activities with an application impact regardless of whether downtime is required.
Planned non-project activities which involve application and/or end-user downtime.
Planned activities that have an affect on workflow or business processes of one or more of the main pillars (Customer, Employee, Infrastructure, or Supplier) during a defined blackout period.

For more information on using the IT Master Calendar, see Eureka! document 99004 — IT Master Calendar Views. For more information on how to submit a request, see Eureka! document 99005—IT Impementation Requests Submission.