Managing model releases can be a challenging and time-consuming task for data science teams. However, by implementing a model catalog with release checklists, organizations can streamline their release process and ensure that their models are released to production quickly, safely and with little stress. In this post, we’ll review how ML teams and their partners can use customized release checklists integrated in Verta’s Model Catalog to simplify and streamline the model release and update process.
A model catalog is a centralized repository for storing and managing ML models. It provides a platform for data scientists to share their work and enables other members of the team to discover, reproduce and build on top of existing models. Model catalogs can also help an organization to maintain version control, track model performance over time, and improve collaboration between team members.
When it comes to releasing new models into production, data science teams can realize several key benefits by using a well-organized and easily accessible model catalog:
A release checklist is a set of guidelines and best practices that Data Science teams follow when releasing new models into production. The checklist helps to ensure that all necessary steps are taken to prepare the model for release and minimize the risk of errors or bugs. With Verta, you can customize one or more release checklists and set controls on who can complete them and what actions can be taken with model versions with incomplete checklists.
For example, a model release readiness checklist could include the following groups of steps:
Model Handoff Requirements might include discrete steps such as:
Responsible AI could be further broken down into steps such as:
And so on for the other steps in the release process.
By breaking down the complex process of releasing a new model into production into discrete steps arranged into logical workflows, a release checklist helps ensure that all the stakeholders in the release process follow these steps consistently across different models and projects - and that no steps get missed in the process.
The result is consistency of process, which helps avoid errors or bugs that can arise from missed steps or incomplete preparation. The release checklist-based process ensures that Data Science thoroughly tests and validates a model before release, improving the quality of the model.
A release checklist also helps to promote transparency and accountability within the organization. By documenting each step of the release process, data science teams can ensure that their work is easily auditable and that they are accountable for the models they release into production. (Model catalog also facilitate audits by providing a repository for all the documentation and artifacts related to a model, supporting Responsible AI.)
When used together, model catalogs and release checklists help data science teams manage their model releases more efficiently and effectively. When a data scientist is preparing to release a new model into production, they can use their model catalog to search for existing models that may be suitable for their project, saving them valuable time and effort, since they may not need to start from scratch. This kind of reuse of existing assets increases the value of an organization’s overall investment in Data Science and ML.
Once a model has been built and trained, the data scientist can use the release checklist to ensure that all necessary steps are taken to prepare the model for release, including testing the model, validating the results, and ensuring that it is properly documented. Then, as noted above, a robust model catalog will containerize the model to prepare it for production.
Once the container is ready to go, the model can be released into production. At this point, the data scientist can use the model catalog to track the performance of the model over time and make any necessary updates or revisions. New versions of the model will go through the same checklist process, ensuring - again consistency and quality across the lifecycle of the model.
Learn more about Verta's Model Catalog here.