Business As Usual Process Flow in Operations Manager and CDH

From PegaWiki
This is the approved revision of this page, as well as being the most recent.
Jump to navigation Jump to search

Business As Usual Process Flow in Operations Manager and CDH

Description End-to-end process flow for Business As Usual using Operations Manager and Customer Decision Hub
Version as of 8.5
Application Pega Customer Decision Hub
Capability/Industry Area Change and Revision Management



Introduction[edit]

Pega 1:1 Operations Manager is a new module of Pega Customer Decision Hub™, as of Pega Platform version 8.4. You can use Pega 1:1 Operations Manager in conjunction with Revision Management to push business-as-usual changes into production. In Pega 1:1 Operations Manager, users can create and deploy new actions to production, as well as request updates to existing actions.

The overall process is defined in Pega 1:1 Operations Manager as a set of stages, as shown in the image below:

Business As Usual stages in Pega 1:1 Operations Manager

This article describes the end-to-end process that users will follow in Pega 1:1 Operations Manager and Pega Customer Decision Hub, from capturing the initial request to deploying and completing a set of changes (a revision).

Use case example[edit]

Various business stakeholders in U-Bank have new actions that they would like to deliver to their customers via Pega Customer Decision Hub. Those requests will be captured in business terms, planned, built, tested and then deployed as part of a collection of change requests, known as a revision.

Before you begin[edit]

It is assumed that you have a high level understanding of Pega 1:1 Operations Manager. If that is not the case, the most recent Academy mission Business Agility in 1:1 Customer Engagement is a good place to start.

It is also recommended that you review the following documents, either before or after reading this article:

Overview of the content creation process using Pega 1:1 Operations Manager[edit]

To deliver Business As Usual (BAU) changes to actions and treatments, various users will carry out tasks in Pega Customer Decision Hub and Pega 1:1 Operations Manager. Each task will be carried out in the Business Operations Environment, working in a specific area inside of those portals. The diagram below illustrates the overall process flow with the different portals, tools and roles that will carry out each task:

Overall BAU process

The process has been broken down into 4 key parts:

Portal: Where in Pega Platform this work will be carried out

Tool: Where in the portal the work will be carried out

Role: Who will carry out the work (See Reference Organizational Architecture for more details on roles and responsibilities).

Step: The task(s) that will be carried out

Step by step details of the content creation process using Pega 1:1 Operations Manager[edit]

1. Capture request[edit]

The NBA Analyst or Business User captures the initial request or idea in the context of a next best action.

Capture the request

2. Plan request[edit]

The team lead reviews the request and assigns it a rank to support planning the sprint.

Plan the request

3. Build or update action[edit]

The NBA Specialist extends the initial request to build out the required artefacts.

Building or updating the action

4. Test action[edit]

The NBA Specialist switches from Pega 1:1 Operations Manager to Pega Customer Decision Hub.

Test the action - entering the test stage in Pega 1:1 Operations Manager

The NBA Specialist carries out a persona test to test and validate the engagement policy created for that action.

Test the action - persona test in Pega Customer Decision Hub

The NBA Specialist carries out a group level audience simulation to evaluate that action compared to its peers.

Test the action - audience simulation in Pega Customer Decision Hub

5. Submit change[edit]

The NBA Specialist submits the completed change for review.

Submit the change

The above process will be repeated until all changes in the sprint are completed. When this set of changes are ready to be tested and then promoted to production, the following steps will be followed:

6. Complete change[edit]

The Team Lead will review the details of this change and either approve or return the change.

Submit the change

7. Simulate revision[edit]

The Team Lead will prepare this change, along with all other changes in the revision, ready for final testing.

Simulate the revision

8 Test revision I[edit]

The NBA Designer will carry out an All Group Level audience simulation to review the impact of all the changes in this revision.

Test The Revision With Simulation

9. Test revision II[edit]

The NBA Designer will run a distribution report to review the impact of all the changes in this revision.

Test the revision with distribution

10. Performance check revision[edit]

The Team Lead will performance test the revision prior to deployment.

Performance test the revision

11. Deploy revision[edit]

The Team Lead will deploy the revision, which will start the Deployment Manager automated processes.

Deploy the revision

12. Complete revision[edit]

The Team Lead will mark the revision as complete after Deployment Manager confirms the processes have completed.

Complete the revision

Summary[edit]

This is the overall process used to create actions and treatments by using Pega 1:1 Operations Manager and Pega Customer Decision Hub as part of a standard Business As Usual process.