Overview Tab

• “Snapshots” (aka Versions) section: Lists all snapshots of the model, their current deployment status and associated stage (environment), last modification date, and created date. Click on a given snapshot to see the snapshot details.

Open

• Associated Use Cases: Lists the Use Cases against which the Model Implementation is associated (i.e. which Use Cases use this model implementation)

Open

• Notifications section: Lists all the notifications related to this particular model. If a ticket (e.g. Jira or ServiceNOW) is associated with the model, a link to that ticket will be displayed. Click on the icon to view more details about the notification.

• Production Status: If the model is currently deployed in production, the business value and status “heatmap” will be displayed as well:

See the “Model Governance: Model Versioning” page for more details on model snapshots (versions).

Details tab

Provides detailed information, metadata, and entry points for a model:

• The Details section contains information and metadata about the Model Implementation. There are three sections:

  1. Basic Information: this includes the standard ModelOp fields about a Model Implementation, such as: Name of the Use Case, Description, Owning Group, Risk Tier, Organization, etc.

  2. Additional Information: this section contains the Customer-specific information that the Company has determined should be collected for a given Model Implementation. The specific fields can be configured in the ModelOp Custom Form Administration . These custom forms are configured by an Administrator and automatically are applied to a Model Implementation based on the Type + Methodology. Note that this section contains a variety of different field types: text input, drop-downs, radio buttons, etc. All of these are configurable by an Administrator.

  3. Detailed Metadata: this advanced section contains any technical or other metadata, typically Customer-specific metadata beyond what is in the Additional Information custom forms.

   

• Functions (Optional: When using a ModelOp Runtime or a Custom Monitor, the Functions define the entry points into the model for initialization, training, metrics testing, and scoring. For example, the Init Function is invoked upon deployment of a model and the Score Function is invoked when scoring. Click the “Edit” button to modify. Note that ModelOp will attempt to provide a drop-down of available functions from the main source code that has been possible.

Compliance tab

Allows users to generate a detailed Audit report. To run a report:

• Select the specific Snapshot of interest and select “Run Report”

• The detailed report will be displayed which includes all of the model details, tickets of high severity, test / monitor results, documentation, assets, deployments, and related MLC instances for the given snapshot.

Click the “Download” button to create a PDF version of the report:

Assets

Lists all of the specific assets associated with the model, which can be source code, trained model artifacts, model configuration files, associated data (training, test, etc.), documents, decision tables, etc.

Repository

Provides more information about the backing repository for the assets. Typically this is a git repository (e.g. Github, Bitbucket, etc.), but models can also be stored in other repositories such as Artifactory, SageMaker, or DataIku repositories.

For git-based repositories, there is more information about the last sync that occurred with the backing git repository

Schemas

Lists the schemas associated with the model. Note that there is only one input and one output schema supported.

For more information on creating input and output schemas, see the Model Schemas page.