Modelscape™ Governance™ is an interactive environment that comprises a regulatory-compliant governance solution for all models in a business area. Use Modelscape Governance if you develop, validate, review, test, deploy, monitor, and use models. Modelscape Governance brings together Modelscape models, model versions, and lifecycles. To customize the environment further for your needs, see Extensibility.
Use Modelscape Governance to perform these tasks:
Model metadata management for any programming language or spreadsheet
Metadata tracking for data you use in the model development process
Dependency analysis and tracking for models and data
Inspection, viewing, and analysis of model and data relationships
Viewing and reporting on the model state within the model lifecycle
Management of the model hierarchy and dependencies
You can also extend and customize Modelscape Governance to perform these tasks:
Score model risk and automate reporting.
Customize workflow and approval procedures.
Review, comment on, and approve models for state changes across the model lifecycle.
Generate reports and customized dashboards for model governance.
Integrate models with internal or vendor applications.
For more information about extending and customizing Modelscape Governance, see Extensibility.
Modelscape Governance Workflow
Working with Modelscape Models and Model Versions
Modelscape models are quantitative solutions that apply statistical, economic, or other techniques to given inputs to produce an output. You can use these outputs to guide pricing or other business decisions. Modelscape models must be backed by a Git™ repository and associated with a lifecycle.
Each Modelscape model has multiple model versions. Model versions are committed updates of a Modelscape model. For example, Probability of Default for Retail Credit in Europe is a Modelscape model, and its 2015 and 2020 versions are the model versions. While a Modelscape model corresponds to a Git repository, a model version refers to a Git commit.
Create Lifecycles Using Lifecycle Designer
Each Modelscape model must be associated with a lifecycle. A lifecycle represents the steps of a model version from drafting and proposal to retiring and decommissioning. At any time, each model version is in one specific state of the model lifecycle. This figure shows a simplified example lifecycle:
To create and edit lifecycles, use the Lifecycle Designer app.
Create Modelscape Models and Add Dependencies Between Modelscape Models
You can use the Inventory Browser app to create new models.
When you have more than one model, you can add dependencies between the models using the Dependency Editor in the Inventory Browser app.