This article describes how ModelOp Center’s MLC’s can be used to orchestrate and automate the Governance Vendor Implementation process.

Table of Contents

Overview

The ModelOp Life Cycle Manager (MLC Manager) orchestrates and automates the the various steps involved in registering Vendor Implementation of a model.

Pre-Requisites

The following are the prerequisites for leveraging this Governance Vendor Implementation MLC:

• The Jira project must be configured with Done and Rejected statuses in the workflow

• Attachments must be enabled for the Jira project.

• Deployment stage : Engine environment name must be "prod" + model tag (if any).

Process Overview

This is a full Vendor implementation of a model lifecycle. It begins with the gathering of the use case, and review of its risk to the business. It then creates a PIA Approval Ticket and proceeds if ticket is moved to Done State. It validates that the model has a documentation asset available and proceeds to create a Independent Risk Review ticket. After the model has assigned the risk the mlc creates a production approval ticket and after that ticket is marked Done it deploys the model in production.

Open

1. Scheduler - the process is triggered by adding a Vendor model implementation to a use case.

2. PIA Approval - the process creates a Jira ticket for PIA approval and continues after the ticket is moved to appropriate exit status.

3. Model Completeness Check - the process validates if the model assets with the MODEL_DOCUMENTATION.

4. Initial Risk Review - A Jira ticket is created to assign model risk.

5. Approval for deployment - Jira ticket is created to proceed with the model deployment.

6. Deploy to Production- f ticket is moved to Done the snapshot is deployed to production environment stage runtime.

7. Error handling - A notification with appropriate error message is created if any step fails in the mlc.

Next Article: Example Workflows - Basic Deployment >