IT Master Calendar Implementation Requests Submission

IT Master Calendar Implementation Requests Submission

Document number: 99005

To make an Implementation Request to the IT Master Calendar submit the appropriate form. The link submitting an "Implementation Request" is on the right side of the Application Support Operations website (http://aso.peoplesoft.com).

For more information on the submission criteria, see Eureka! document 99003— IT Master Calendar Implementation Requests Criteria For more information on using the IT Master Calendar, see Eureka! document 99004 — IT Master Calendar Views

The form for submitting the request is relatively simple. There are a few things of particular note you should remember before starting.

The "day" starts at 12:01 AM as the default. So, for example, if you intend to indicate two full days (48 hours) remember to change the time to 11:59 PM. If you fail to do that you will end up scheduling only 24 hours and one minute.
"Downtime" includes all changes in which a user will be unable to access any portion of an application or will experience significantly impaired services.
An asterisk * indicates a required field.

Form fields and tips

Entry Type

Change
Downtime
Blackout
Specify your own value:

Most submissions should be Change, Downtime or Blackout. The last field is supplied for flexibility but should not be used if any of the three supplied fields apply. If you select "Change" that means there is no downtime required. If downtime is required as part of a change then the correct selection is "Downtime."

Title

Please enter a brief meaningful description of the request. eg: BLACKOUT-PSynergy-Month End, DOWNTIME-Maintenance-Network, PROJECT-CRM-upgrade

Use the pattern provided in the example as your guide for creating a description title. The purpose is to make it easy to find in a list. Keep it short, but descriptive.

Recurrence

None
Daily
Weekly
Monthly
Yearly

When you select a radio button you will be presented with the appropriate calendaring format "Pattern" for scheduling. The default is "None"

"Daily" can mean every day, but it is also the correct selection for any pattern more often than once a week. For example, if you were submitting a maintenance request that was to run every other day you would select "Daily" for "Recurrence", then enter "2" under "Recur every __ day(s)." Click the icon for a screen shot.

"Weekly" can mean every week, but it is also the correct selection for any pattern more often than once a month. For example, if you were submitting a maintenance request that was to run every other week you would select "Weekly" for "Recurrence", then enter "2" under "Recur every __ week(s)." Click the icon for a screen shot.

"Monthly" can mean every month, but it is also the correct selection for any pattern more often than once a year. For example, if you were submitting a maintenance request that was to run every 6 months you would select "Monthly" for "Recurrence", then enter "6" under "Recur every __ months(s)." Click the icon for a screen shot.

Begin

Enter date in MM/DD/YYYY format.

The appearance of this field will change depending upon what you have selected for "recurrence."

End

The appearance of this field will change depending upon what you have selected for "recurrence."

Description

Describe why the request is required

What is the change intended to accomplish?

Location

Enter a general physical location, e.g. Pleasanton Data Center.

IT Project ID

Please enter the project ID. If this not a project related entry please input "NON-PROJECT" or "BLACKOUT" as is relevant

This field will help sort and filter proposals for quick focus and identification. If there is no project ID then the appropriate entry is either "NON-PROJECT" or "BLACKOUT." Although this is a free form field please avoid getting creative.

Impact to application?

Please uncheck box if there is not an impact to user applications. For "Blackout" this must remain checked.

Situations in which the box would be unchecked are rare. If you think unchecking the box is appropriate please double check before doing so.

Applications Impacted

None
Customer Systems
Employee Systems
Supplier Systems
App. Infrastructure
Please select all applications that will be impacted by this downtime. "App. Infrastructure" must remain checked

This application doesn't provide an easy means to prevent unchecking "App. Infrastructure." Ensure this remains checked.

Request By

This value defaults automatically. Do not change

This is the name of the person making the entry. It is based on Active Directory. Do not change this value..

Assigned to

Customer Systems manager
Employee Systems manager
Supplier Systems manager
App. Infrastructure manager
Specify your own value:

Please select all managers whose areas are affected so that they may review this request. App. Infrastructure manager should always be selected.

If a change, downtime or blackout request will affect an area then the select that manager to review it. Ensure App. Infrastructure remains checked.

Status

Requested
In process
Approved
Cancelled
Denied
Managers to set status when working with or on completion of action. Defaults to "Requested"

Do not change the value in this field. for App Support Manager use only.

Workspace

Use a Meeting Workspace to organize attendees, agendas, documents, minutes, and other details for this event.

Not required

Please don't use the "Workspace" area. This is for for App Support Manager use only.

Approver's comments

ASO MANAGERS USE ONLY. This is used by the ASO managers to update approval comments

This field is only for Applications Support Managers.