Standard Model Definition
ModelOp Center provides the most robust and extensible definition of a model to allow for consistent deployment, monitoring, and governance of all models across the enterprise.
Elements of the Standard Model Definition
The ModelOp Standard Model Definition includes all of the metadata, technical model details, version information, MLC’s, and test results related to a given model. This information is listed in the Model Details page within ModelOp Center:
Model Info |
 Custom Metadata: Note that Custom Metadata can be added to a given model. Any metadata that adheres to valid JSON can be added/updated throughout the lifecycle of the model. The Custom Metadata will be displayed in the Model Details page.
 |
Model Source | Provides details of all the source code assets, typically stored in a remote git repository. The “Source” tab provides a view into the actual source code asset:  The “Metadata” tab lists all of the details of the source code management capability that is backing the source code assets, including remote repository URL / branch, last commit ID, and the repository type:  |
Schemas | Defines the input and output schemas to which the input data and output scores must adhere as part of model scoring. The schemas use the well-adopted Avro standard to enable a contract between the data ingress / egress and the model code.  For more information on creating input and output schemas, see the Schema Management page. |
Versions | Detailed list of all versions of the model, their last modification date, current deployment status, related tests, and a URL to view the Version details |
Model Platform | Lists the dependencies used by the model, both system and framework-specific libraries/frameworks. |
Attachments | Attachments are other model artifacts used during the life cycle of a model, including items such as training model coefficients/binaries, documents, decision tables, test data references, or other items. |
Model Metadata: textual overview and usage information about a model including: Name, Description & Usage, Tags.
Model Source Code: all of the source code assets associated with a model, including the main entry points for initializing a model, training, scoring, and validating/testing a model.
Model Attachments: trained artifacts and other files that are required to leverage the model.
Model Platform: all of the libraries, packages, and other dependencies required to execute the model.
Input & Output Schemas: as noted on the ModelOp Center Terminology page, one of ModelOp Center’s core abstractions is the separation of the model code (the “math”) from the data ingress and egress. The schemas leverage the type-agnostic specification to define the contract between the data pipelines and model code.
Model Functions: defines the entry points into the model source code such that ModelOp Center knows which functions to call to execute certain steps in the model’s life cycle (e.g. model training, model scoring, model validation/metrics, etc.)
Model Tests: all of the manual and automatically executed tests persist with the specific version of the model. To view the model tests, click Models > Model Tests:
Versioning
All of the elements of the standard model definition are versioned using our Model Manager micro service, and are backed by your preferred enterprise-standard versioning tooling. For example:
Model Source Code → backed by Git (all versions: Github, Bitbucket, Gitlab, etc.)
Model Attachments → backed by standard artifact repositories (such as S3, Artifactory, etc.)
All Other Elements → backed and versioned by ModelOp Center’s Model Manager
Supported Languages & Frameworks
While ModelOp Center supports almost any model language, framework, and overall model factory, below is a sampling of some of the more common ones that are supported in ModelOp Center. Each of these are encoded in ModelOp Center’s standard model definition
