Introduction
Enterprises around the globe, financial and non-financial, nowadays are required to leverage tools to have model governance or Ai governance, this has become specially meaningful with all the explosion of generative Ai and Ai in general. In order to meet this requirement ModelOp Center is providing the ability to create Application Forms, which are meant to allow customers to define individual customer perspectives, e.g: exact inputs that I need to collect from a governance perspective in a nice easy to use and wizard base-form.
Some of the key design principles are listed below:
Make it simple and easy for customers to use and govern their models with MOC; and get started incrementally.
Make it super simple for customers, to collect everything that the organization needs from the governance perspective, about all their use-cases.
Easy to use form-base approach for non-technical people to define Model governance forms.
Application Forms Overview
Application Forms have the 2 main components:
Application Form
Custom Form Fields ( General Custom Form Fields that can be shared among Application Forms).
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
andModel 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.
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