Single model for enterprise system management
Thus product model is tradutionally used to manage product lifecycle:
a hierarchy of product requirements, a list of component parts and a list of product documentation. But this doesn't include works performed to develop the documents and produce the product.
At the same time the project management model pays a lot of attention to reflecting work and resources but the model of the product, for which the project is carried out, is represented in a very simplified way.
We can name a lot of example models used for automation of various activities. However all these models have a common important feature: all of them were initially created for describing one particular activity and the objects involved in it.
As we can see from the history of automated operations management system development, extending the boundaries of existing systems and their models to encompass other activities leads, as a rule, to creation of new models weakly interacting with the existing models.
Our approach to modeling Creating our operations management system we aimed at creating a model that is able to describe an activity and the objects involved in it with such detail that allows efficient management of any activity.
The results we've got show that we managed to implement our plans:
Documents about ASys model
It is impossible to manage an enterprise efficiently without a single model
A new approach to multiagent enterprise system management automation on the basis of a single model
News about ASys model
The Model on BPM 2012
ASys model was introduced at BPM 2012 Conference