Production Countdown Sequence

Aras understands that the need for flexibility during development will interfere with the project’s chosen practices.

However, during the countdown sequence to production deployment, Aras requires a protocol to ensure a smooth transition and secure the necessary approvals.

Aras focuses on the following Branches:

• Development
• SIT
• UAT
• Staging
• Production

As part of the production deployment sequence, Aras mandates that the project team integrate their release candidate from the Development Branch into the “sit” Branch before deploying it in the SIT environment.

During deployment, the project team can deploy from any Work (Team) Repository Branch to the SIT environment to support ongoing testing.

During the countdown sequence, the change implementation policy requires the project team to deploy to the SIT environment only from the “sit” Branch. The practice of deploying to SIT only from the “sit” Branch during the countdown sequence helps ensure alignment. The customer is required to identify the Build for which they approve for System Qualification.

Aras mandates that the project team obtains a System Qualification Approval (SQA) from the client to conclude SIT testing. This approval signifies that the client is content with the entire solution. All necessary integrations, SSO connections, CAD, and Office connectors have been established as needed.

Note that the project team may have identified a release candidate, deployed it to SIT, collected feedback, and performed remediation to obtain SQA. Aras does not dictate the number of cycles; the customer just provides SQA before deployment to UAT.

Once the SQA is obtained, the project team immediately asks Aras to initiate the suitable Build deployment in the UAT environment. The project team should prepare and deploy to the UAT environment from the “uat” Branch. In collaboration with the client, the project team facilitates a system review by the end-users, leading towards the Function Qualification Approval (FQA). The client must provide FQA before Production Qualification Approval (PQA).

In projects involving data migration, the project team must secure Data Qualification Approval (DQA). To obtain DQA, the project team must request production environment provisioning and necessary endpoints to run the data import. Once the project team has imported the data, the team must ask the customer to review the data and approve data quality.

The project team must request the UAT, staging, and production environments with the customers’ approval. The staging environment is used for importing data from other systems and as pre-production to perform final testing to secure PQA.