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

« Previous Version 3 Next »

This article describes how ModelOp Center enables model interpretability/explainability monitoring.

Table of Contents

Introduction

Enterprises worldwide, both financial and non-financial, are increasingly required to implement model governance or AI governance frameworks. This need has become particularly pressing with the rapid advancements and widespread adoption of generative AI and AI technologies in general. To address this requirement, ModelOp Center offers the capability to create Application Forms. These forms enable customers to define specific perspectives and gather the exact inputs necessary for governance in an intuitive, wizard-based format.

Key design principles include:

  1. Simplicity and Ease of Use: Ensuring that customers can effortlessly manage and govern their models with ModelOp Center, allowing them to start incrementally.

  2. Comprehensive Data Collection: Making it exceptionally easy for customers to gather all required information from a governance perspective for all their use cases.

  3. User-Friendly Form-Based Approach: Providing a straightforward, form-based method for non-technical users to define model governance forms.

Application Forms Overview

Application Forms have the 2 main components:

  1. Application Form

  2. Custom Form Fields ( General Custom Form Fields that can be shared among Application Forms).

Screenshot 2024-07-12 at 1.00.59 PM.png

Application Forms:

  • Forms can only be managed by ADMINS.

  • An application form can be associated to:

    • Use-cases

    • Implementations:

      • Ensemble

      • Git Model

      • AWS Sagemaker

      • Generic Mode

  • An Application Form data (answers) will be stored at the StoredModel.modelMetadata.custom field

  • Only one Application Form can exist for a given combination of Model methodology and Model Type, as the goal is to drive consistency across the enterprise.

  • Once an application form has been used, it can only get new fields , existing fields can’t be modified or removed.

Screenshot 2024-07-12 at 1.01.29 PM.png

Custom Application Form Fields:

  • Custom fields are form independent fields that can be defined once and reused a cross multiple forms

  • Custom fields added into forms wont be kept in sync; if the custom field changes, the update wont be replicated to other forms including that custom field.

  • One, many or none custom fields can be associated to a given form

  • No labels