Model automation
An example system can include: at least one processor; and non-transitory computer-readable storage storing instructions that, when executed by the at least one processor, cause the system to: generate a configuration manager programmed to configure a workstream including a plurality of models, wherein the workstream defines metadata associated with execution of each of the plurality of models; generate an execution manager programmed to execute each of the plurality of models in the workstream according to the metadata; and generate a results manager programmed to access results of the execution of the workstream.
1. A system, comprising:
at least one processor; and
non-transitory computer-readable storage storing instructions that, when executed by the at least one processor, cause the system to:
generate a configuration manager programmed to configure a workstream including a plurality of models, wherein the workstream defines metadata associated with execution of each of the plurality of models;
generate an execution manager programmed to execute each of the plurality of models in the workstream according to the metadata; and
generate a results manager programmed to access results of the execution of the workstream;
wherein the configuration manager is programmed to define a visual depiction of the workstream showing each of the plurality of models and model dependencies associated therewith; and
wherein the visual depiction includes a legend providing source information for the plurality of models depicted on the visual depiction.
2. The system of claim 1 , wherein the execution manager is further programmed to programmatically execute a model of the plurality of models in the workstream.
3. The system of claim 2 , wherein the model is a legacy model configured for manual execution.
4. The system of claim 2 , wherein the execution manager includes a plurality of model runner nodes, wherein each of the plurality of model runner nodes is programmed to execute a different type of the plurality of models.
5. The system of claim 1 , wherein the configuration manager defines an acyclic construction of the model dependencies.
6. The system of claim 1 , wherein the configuration manager is programmed to allow a first model to be added to the workstream and a second model to be removed from the workstream.
7. The system of claim 1 , wherein the configuration manager visually maps each upstream model and each downstream model for the plurality of models in the workstream.
8. The system of claim 1 , comprising further instructions that, when executed by the at least one processor, cause the system to define a versioning for the workstream.
9. The system of claim 8 , wherein the versioning includes:
a first versioning for the data and the metadata associated with the plurality of models in the workstream;
a second versioning for the workstream; and
a third versioning for each of the plurality of models in the workstream.
10. A computer implemented method, comprising:
generating a configuration manager programmed to configure a workstream including a plurality of models, wherein the workstream defines metadata associated with execution of each of the plurality of models;
generating an execution manager programmed to execute each of the plurality of models in the workstream according to the metadata; and
generating a results manager programmed to access results of the execution of the workstream;
wherein the configuration manager is programmed to define a visual depiction of the workstream showing each of the plurality of models and model dependencies associated therewith; and
wherein the visual depiction includes a legend providing source information for the plurality of models depicted on the visual depiction.
11. The method of claim 10 , wherein the execution manager is further programmed to programmatically execute a model of the plurality of models in the workstream.
12. The method of claim 11 , wherein the model is a legacy model configured for manual execution.
13. The method of claim 11 , wherein the execution manager includes a plurality of model runner nodes, wherein each of the plurality of model runner nodes is programmed to execute a different type of the plurality of models.
14. The method of claim 10 , wherein the configuration manager defines an acyclic construction of the model dependencies.
15. The method of claim 10 , wherein the configuration manager is programmed to allow a first model to be added to the workstream and a second model to be removed from the workstream.
16. The method of claim 10 , wherein the configuration manager visually maps each upstream model and each downstream model for the plurality of models in the workstream.
17. The method of claim 10 , further comprising defining a versioning for the workstream.
18. The method of claim 17 , wherein the versioning includes:
a first versioning for the data and the metadata associated with the plurality of models in the workstream;
a second versioning for the workstream; and
a third versioning for each of the plurality of models in the workstream.