Levels of service dictate when an asset should be deployed.
Tier 1 applications:
Phoenix
ESI
FinInfo
Integrations
Show integrations wit
...
Normal deployments will take place every Tuesday at 4:30 PM.
...
If production service is down, emergency deployment will take place ASAP to restore service.
...
Purpose
All deployments must be approved by the Change Advisory Board (CAB), which is composed of Technology Services managers and meets every Tuesday. Approved deployments will occur on the next Tuesday unless deemed an emergency, in which case they will be expedited. The CAB ensures that no overlapping initiatives are scheduled, and all deployments will be communicated to customers beforehand, with specific communication methods based on asset tiers. For instance, Tier 1 assets will be communicated through https://status.ssdmo.org/, while integrations will be communicated directly to the service owner.
Change Advisory Board (CAB) Deployment Approval Process
All deployments must be scheduled and approved through the Change Advisory Board (CAB).
The CAB consists of the managers of Technology Services.
The CAB meeting takes place every Tuesday.
Unless there is an emergency, all deployments that are approved will take place on a the next Tuesday, after the approval.
All deployments are scheduled through the CAB to ensure that no competing initiatives are scheduled at the same time.
All deployments will be communicated to the customer prior , to the delivery date.
...
All deployments will be communicated based on the tier of the asset.
Tier 1 assets will be communicated through https://status.ssdmo.org/
Integrations will be communicated to the service owner.
Note: if a production service is down, an emergency deployment will take place as soon as possible to restore service.