Skip to end of banner
Go to start of banner

Deployment regulations

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

  • Levels of service dictate when an asset should be deployed.

  • Tier 1 applications:

    • Phoenix

    • ESI

    • FinInfo

  • Integrations

    • Show integrations wit

  • 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 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.

  • Normal deployments will take place every Tuesday.

To ensure a structured deployment process, the levels of services determine deployment timing. Normal deployments are scheduled for every Tuesday at 4:30 PM. In case of a production service outage, emergency deployments are promptly executed to restore service. All deployments require CAB scheduling, with meetings held every Tuesday at 2:00 PM. Approved deployments are then scheduled for a subsequent Tuesday to prevent conflicting initiatives. This process guarantees coordinated and efficient deployment activities.

  • No labels