Decommission a Resource

This workflow explains the process for requesting the decommissioning of an existing deployment of the ABB Ability™ Platform or Azure Subscription.

Decommission Workflow

1. Create ServiceNow Ticket

To initiate any decommissioning, first create a ServiceNow ticket with the following details:

Decommission Request Inputs for ABB Ability™ Platform:

• Reason for decommissioning

• Platform subscription name

• Platform resource group name

• ARS Portal link

• API Endpoints: DA, IM, TD

• IoT Hub endpoints

Decommission Request Inputs for Azure Subscription:

• Reason for decommissioning

• Azure Subscription name

• Azure Subscription ID

INTERNAL PROCESS

All steps listed below this break are internal steps taken by the ABB Ability™ Platform Operations Team. These are listed for transparency purposes.

2. Receive Ticket

The operations engineer self-assigns the ticket or assigns the ticket to another Operations Team member.

3. Verify Details

The operations engineer verifies the details of the ticket.

4. All Required Inputs Available

• NO - The operations engineer identifies missing information in the ticket.

  • Requests for Input The operations engineer requests the missing information from the submitter of the ticket via ticket comments.

• YES - The operations engineer validates that all of the required inputs are available.

  • Confirm with CST The operations engineer adds comments to the ticket and asks for confirmation from the CST Team.

5. CST Provides Confirmation

• NO - CST Team does not confirm the decommissioning request.

  • Follow up with CST confirmation The operations engineer follows up with the CST Team on confirmation for decommissioning.

• YES - The CST Team confirms the decommissioning request.

6. Update Checklist

The operations engineer updates the decommissioning checklist with pre-decommissioning entries.

• Locate checklist here.

7. Create a VSTS Task

The operations engineer creates a VSTS task for decommissioning and attaches the decommissioning checklist to the task.

8. Start Decommissioning

The operations engineer starts the requested decommissioning.

9. Decommissioning Completed

• NO - There were issues during the decommissioning.

  • Create VSTS Bug The operations engineer creates a VSTS bug and starts working towards resolution of the identified issue.

• Yes - There were no issues during the decommissioning.

  • Update Checklist post-decommissioning The operations engineer updates the checklist with the post-decommissioning entries.

10. Send for Review

Assign the VSTS task and send for a review from one of the Operations team members.

11. All Required Inputs Available

• NO - There is missing information in the checklist.

  • Update comments in the VSTS task and assign back The Operations team member updates the VSTS task and assigns the task back to an operations engineer.

  • Operations engineer updates required details The operations engineer updates the missing details as per comments from review and assigns the task back to an Operations team member for re-review.

• YES - All the information is found to be correct.

  • Update comments in the VSTS task and assign back The Operations team member updates the checklist and assigns it back to an operations engineer.

12. Update ServiceNow Ticket to "Resolved" State

The operations engineer updates the ticket with comments and changes the status to a "Resolved" state.

13. Auto-Notification Email Received by the BL

An automatic notification email is received by the BL as a confirmation of the decommissioning.

Decommission Workflow Diagram

Note: For a full-size image, right click and select "Open image in new tab".