Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

This article describes how ModelOp Center’s MLC’s can be used to orchestrate and automate the annual review process.

Table of Contents

Overview

The ModelOp Life Cycle Manager (MLC Manager) orchestrates and automates the the various steps involved in conducting an annual review of a model for Model Risk and Governance processes.

Pre-Requisites

The following are the prerequisites for leveraging this Annual Review Process MLC:

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

  • Attachments must be enabled for the Jira project

  • Standard Risk Tests model must be present with a valid snapshot

  • Business model must be deployed in production

  • Business model must have appropriate assets with the BASELINE_DATA and COMPARATOR_DATA asset roles

Process Overview

The process is triggered for the annual review of a snapshot of a business model(s) when a business model is deployed to production and the expiration date of the snapshot is within the 30 days of the current date. The annual review MLC runs Standard Risk Tests on the snapshot and generates test results. These results are used to generate a model review document for validation by a model reviewer. When the document review is approved the MLC updates the snapshot’s custom metadata with the annual review date and time and the validator of the ticket. Finally, the MLC updates the expiration date of the snapshot.

  1. Scheduler - the process is triggered by a signal (com.modelop.mlc.definitions.Signals_deployable_model_annual_review) and retrieves a deployed model(s) in production.

  2. Model Initial Checkpoint - the process continues if the model’s snapshot is within the 30 days of expiration date and is not already validated or pending for validation.

  3. Run Standard Risk Tests - the process validates if the model assets with the BASELINE_DATA and COMPARATOR_DATA assets roles in preparation to run Standard Risk Tests on the model. If the assets are present in the model the MLC runs the Standard Risk Tests and creates a notification if any of the monitors in Standard Risk Tests fail to run. If the test job fails, a Jira ticket is created with the failed job error message. A test can be re-run if the Jira ticket is moved to Done.

  4. Approval Based on Test Results - A Jira ticket is created with document generated from the model test results for validation. If ticket is moved to Done the flow continues and adds the generated document to the model snapshot.

  5. Annual Validation - Jira ticket is created with the test result document for the senior analyst for the final sign-off.

  6. Update Snapshot Metadata- If ticket is moved to Done the snapshot's custom metadata is updated with the sign-off date and the validator's info. The snapshot's expiration date is also updated. If the ticket is moved to Rejected the custom metadata is updated with Annual Model Review: Rejected.

  7. Error handling -

    1. An error is logged if the flow is unable to read the model(s) in production

    2. An error notification is created for the following:
      i. Standard Risk Test snapshot is not found.
      ii. the first Jira ticket with document has been moved to Rejected.
      iii. any other exception occurs in the flow.

Related Articles

Next Article: Operationalizing Models: Overview >

  • No labels