Subscription Management

The workflow covers the cases for creating a new subscription for the following request types:

1. BL Application Development:

This process covers steps for creating a new subscription for BL application development requirements.

• In this case, an empty Azure Subscription is created and a BL member is assigned ownership of the subscription. The BL member owner is responsible for managing and maintaining the Azure subscription.

2. ABB Ability™ Platform:

This process covers steps for creating a new subscription for ABB Ability™ Platform deployment requests in case there is no existing subscription that can be reused.

• In this case, an empty Azure Subscription is created and the operations team is assigned ownership of the subscription. The operations team is completely responsible for managing and maintaining the Azure subscription.

NOTE

Access to this subscription is not provided to outside of the operations team. For verifying the cost of the deployed platform instance, "Billing Reader" rights will be assigned to the BL representative of the deployments.

BL Application Development Workflow

1. Approved iProcess Ticket Assigned to Operations Engineer

For any new subscription creation, an approved ticket is required and is assigned to an operations engineer.

• The workflow for requesting a new Azure Subscription can be found here.

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. Fill Checklist

The operations engineer creates a new copy of the checklist and fills out the applicable entries before creating the subscription.

• The checklist for creating a new Azure Subscription can be found here.

3. Create a VSTS Task

The operations engineer creates a VSTS task for creating a new subscription and adds the updated checklist from step 2 (above).

4. Create Subscription

The operations engineer creates the Azure Subscription following the accepted naming convention.

The naming convention for Azure Subscriptions is as follows:

<BUNAME>-<ProjectName(short)>-<Type>

ProjectName:Shortened 5-6 chars [Optional]

Type: Dev/Tst/Prd/Stg

Ex. - RMDR-WWO-Dev, RMDR-Dev

5. Add BL Member as Owner per Request

The operations engineer assigns the owner access to the BL Member, as mentioned in the ticket.

6. Update Subscription Details in Invoicing and Ops Portal

The operations engineer updates the subscription details in the invoicing tool and Ops SharePoint Portal.

Steps to Update in the Invoicing Tool

• Log in to the invoicing tool.
• Select the appropriate Division, BL.
• Select the Subscription tab and from the populated list, select the new subscription.

Steps to Update in the Ops SharePoint Portal

• Launch the SharePoint Portal.

• Click on the Edit option and select the last row of the list. Update the following entries:

  • Account Name: name of the BL account in which the subscription is created

  • Subscription Name: name of the subscription

  • Region:

    • For China: CN

    • For EU, North America: EU/NA

  • Division: applicable division

  • BL: applicable BL

  • Source of Request: iProcess, ServiceNow

  • Source ID: ID of the iProcess, ServiceNow

  • Contact: two BL contact email IDs

7. Update Checklist

The operations engineer updates the relevant checklist entries post, creating a subscription.

8. Update VSTS Task

The operations engineer updates the VSTS task and verifies the updated checklist entries are available as an attachment.

9. Assign VSTS Task to an Operations Team Member for Review

The operations engineer assigns the VSTS task for peer review to one of the operations team members.

10. Verify Each Checklist Entry

The assigned operations team member verifies all the checklist entries.

11. All Details are Correct

• NO Update the VSTS task with comments and actions.

  • If the operations team member finds any missing information, the VSTS task is assigned back to the operations engineer with comments in the VSTS task.

  • Perform necessary actions: The operations engineer updates the entries following comments, then updates the checklist and reassigns it to the operations team for peer review [steps 7 to 9].

• YES Update VSTS task with approval comments.

  • If the operations team member finds all the inputs to be correct and verifies all the fields, he/she updates the VSTS task with comments and assigns it back to the operations engineer.

12. Close the VSTS Task

The operations engineer closes the VSTS task.

13. Close iProcess Subscription Request Ticket

The operations engineer closes the iProcess Subscription Request Ticket, updating the subscription details.

• Auto-Notification mail sent: After the operations engineer closes the iProcess ticket, an auto-notification email is sent to the BL about the ticket closure.

14. Send Email to BL Subscription Owner with Naming Convention Document

The operations engineer sends the naming convention document and subscription details via email to the BL owner of the subscription.

15. End

End of the process for creating a new Azure subscription for BL.

Ability Platform Workflow

1. Approved iProcess Ticket Assigned to the Operations Engineer

The operations engineer receives the ticket.

• The workflow for requesting new Platform requests can be found here.

2. New Subscription Required

The operations engineer determines whether there is an existing subscription.

• NO The operations engineer continues with the platform deployment process.

• YES The operations engineer follows the procedure to create new subscriptions for ABB Ability™ deployment.

3. Create a New Copy of Checklist and Update with the Details

The checklist can be found here.

4. Create a VSTS Task

The operations engineer creates a VSTS task for creating a new subscription and adds the updated checklist from step 3 (above).

5. Create Subscription

The operations engineer creates an Azure Subscription following the accepted naming convention.

The naming convention for new subscriptions for platform deployment is as follows:

ABB-Ability-Platform-<BUNAME><ProjectName(short)>-<Type>

ProjectName:Shortened 5-6 chars [Optional]

Type: Dev/Tst/Prd/Stg

Ex. - ABB-Ability-Platform-RMRO-Dev

6. Add Operations Team as Owner per Request

The operations engineer assigns the owner access to the operations team Group ID.

7. Update Subscription Details in Invoicing Tool and DevOps SharePoint Portal

The operations engineer updates the subscription details in the Invoicing Tool and Ops SharePoint Portal.

Steps to Update in Invoicing Tool

• Log in to the invoicing tool.

• Select the appropriate Division, BL.

• Select the Subscription tab and from the list populated, select the new subscription.

Steps to Update in Ops SharePoint Portal

• Launch the SharePoint Portal.

• Click the Edit option and select the last row from the list. Update the following entries:

  • Account Name: name of the BL Account in which the subscription is created.

  • Subscription Name: name of the subscription

  • Region:

    • For China: CN

    • For EU, North America: EU/NA

  • Division: applicable division

  • BL: applicable BL

  • Source of Request: iProcess, ServiceNow

  • Source ID: ID of the iProcess, ServiceNow

  • Contact: two BL contact email IDs

8. Update Checklist with Details after Creating Subscription

The operations engineer updates the relevant checklist entries after creating the subscription.

9. Update VSTS Task

The operations engineer updates the VSTS task and verifies the updated checklist entries are available as an attachment.

10. Assign VSTS Task to Operations Team Member for Review

The operations engineer assigns the VSTS task for peer review to one of the operations team members.

11. Verify Each Checklist Entry

The assigned operations team member verifies all the checklist entries.

12. All Details Are Correct

• NO Update VSTS task with comments and actions.

  • If the operations team member finds any missing information, he assigns the VSTS back to the operations engineer with comments in the VSTS task.

  • Perform necessary actions: The operations engineer updates the entries following comments, then updates the checklist and reassigns it to the operations team for peer review [steps 7 to 9].

• YES Update VSTS task with approval comments.

  • If the operations team member finds all the inputs to be correct and verifies all the fields, he/she updates the VSTS task with comments and assigns it back to the operations engineer.

13. Close VSTS Task

The operations engineer closes the VSTS task.

14. Continue with the Deployment Process

The operations engineer continues with the ABB Ability™ Platform deployment process.

14. End

This concludes the process for creating a new Azure subscription for ABB Ability™ Platform deployment.

BL Application Development Workflow Diagram

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

Ability Platform Workflow Diagram