ORCHESTLY TUTORIALS

Step 3: Publish Blueprint

Once the stages and transitions are configured, the blueprint is ready to publish.

Step 4: Execute blueprint

Once the blueprint is configured and published, we can execute it by creating a new job.

• Navigate to Jobs.
• Click Add Job.
• Select the layout used in Step 1.
• Fill the form and click Save.

This blueprint follows two different flows for emergency and non-emergency changes. Let's take a look at both of these flows.

Case 1: Change Type = Emergency

Initially, the job will land in the first stage of the blueprint and the transition will be displayed as a blue button. Here, the job starts in the Change request submitted stage and the first transition is Pickup for review.

The Assignee of the job can perform the first transition by clicking the Pickup for review button. The assignee will be prompted to attach the Change report. Once the report is filed, the assignee transfers the job to the Senior Management Team for evaluation by clicking Send for risk assessment.

Any user from the Senior Management Team can take over the job. They can either Approve or Reject the change. They will need to add a comment explaining their choice when they perform either action.

If the change is approved, an email about the change will be sent to all the employees in the organization.

If a change is rejected, the Assignee can appeal this by clicking Appeal Change. The user will be prompted to upload the Updated crisis change document.

If the change is approved, the Start emergency implementation transition will take place automatically and the job will progress to the next stage.

Once emergency implementation starts, the Emergency Committee takes charge. The job is currently in the Emergency implementation underway stage.

SLA:

A job can only stay in this stage for 3 days.

• On the 1st day, an early reminder email is sent to the Emergency Committee.

• On the 3rd day, a reminder is sent to the Emergency Committee and Senior Management Team.

• On the 4th day, an escalation email is sent to the Senior Management Team and CEO.

SLA

Here, any user from the Emergency Committee can perform the transition Plan and implement. When a user performs this transition, they will be prompted to fill out a multilevel checklist.

Once the change is implemented, it must be evaluated. This transition is automated by time with a wait period of one day. After one day, the transition takes place automatically and the job moves to the next stage.

Post-implementation review is crucial for emergency changes as it helps teams evaluate the effectiveness of the change. The Quality Analysis Team can click the Start incident tracking button to address individual incidents. Once the incident has been studied, a report can be attached by clicking the File report button.

Finally, once the emergency change is implemented in the organization, the Assignee can close the request by clicking Close request and uploading the Post change analysis report. One day after the job is completed, the change management report will be emailed to the senior management team.

Case 2: Change Type = Non-emergency

The job starts in the Change request submitted stage. The assignee of the job can review the change by clicking the Pickup for review button. The assignee will be prompted to attach the Change report.

Once the report is filed, the Assignee transfers the job to the Senior Management Team for evaluation by clicking Send for risk assessment.

Any user from the Senior Management Team can take over the job by performing the Approve change or Reject change transition. They will need to add a comment in the Comments field when they perform either action.

If the change is approved, an email about the change will be sent to all the employees of the organization.

If a change is rejected, the Assignee can appeal this by clicking Appeal Change. The user will be prompted to upload a file in the Updated crisis change document field.

If the change is approved, the Start step-by-step implementation transition will take place automatically the job will move to the next stage.

This stage contains 3 parallel transitions: Change planning, Change assessment, and Change forecasting, which the assignee can perform. Only after all of these transitions are completed, can the job move to the next stage.

The Assessment report, Planning report, and Forecasting report must to be submitted respectively for these three transitions.

Once all the parallel transitions are complete, the job moves to the Senior Management Team, who can approve the submitted reports. When a member of the team clicks Approve, a checklist pop-up appears.

Once the plan is approved, the Assignee can start implementing the change by clicking Begin implementation.

Once the change is implemented, the Evaluate change post implementation transition takes place automatically after a wait period of three days.

Finally, once the emergency change is implemented in the organization, the Assignee can close the request by clicking Close request and uploading the Post change analysis report. One day after the job is completed, the change management report will be emailed to the Senior Management team.