"A framework [for enterprise modeling] is a skeletal structure that provides a context and a set of rules for the use of systems and modeling concepts for enterprise modeling. The resulting models need to describe the elements which are present in real systems, such as: material, energy, resource, information flows, and organizational phenomena. The models also have to accommodate the requirements of the users of these models, whose purposes vary over time according to their responsibilities, objectives, and the processes being considered."Although the above definition is given in the context of computer-integrated manufacturing and focuses more on properties of models than on the process of modeling, the definition includes four main concerns that Tema must discuss and incorporate:
Notice the resemblance between the above listed requirements to what constitutes a framework and the OPPO framework discussed in section 5.2.4: Context roughly corresponds to organization, set of rules refers to process, model concepts belong to the product aspect, and user requirements to models are clearly objectives.
The reason for including the criterion is obvious: Throughout the research project, considerable effort has been spent on studying enterprise modeling practice. The principles in chapter 7 represent the essence of these studies – the lessons learned. Not taking these into account when designing Tema would not make sense.
Tema is based on studies of practical modeling, and applicability
according to this practice is hence the ideal. In situations where observed
practice failed, Tema proposes and argues for solutions that are
perceived to meet the requirements with low demands on resources.
|Communication-intensive activities can be envisioned supported in many ways by computers in networks. Powerful real-time communication facilities with dedicated equipment, tailored software and virtually unlimited communication bandwidth might be a dream of some actors. Requiring this kind of technology to support Tema would violate the design principle of practical applicability. Tema proposes off-the-shelf solutions whenever possible.|
The main reason for including practical applicability as a design criterion in addition to the "fit with principles" criterion is to deal with the situations where observed practice did not work well (e.g., definition of terminology in TEK-S). In these situations, an assessment of perceived applicability of the proposed means must be made based on personal experience, others' documented experiences, literature studies or other arguments.
At one extreme, there is the stance that one should have no presumptions at all. All languages and methods must be invented as a part of the modeling effort. Every new problem requires a unique and tailored solution. This leads to a high degree of flexibility, but may be inefficient and miss the benefits of learning from other practitioners and theorists. Incapability of action may also be a consequence.
At the other extreme, there is the stance that all language concepts
and methodical steps can be decided and fixed in advance. This might be
highly efficient, but not necessarily effective (as lack
of flexibility may prevent the modelers from solving the problem at all,
or requires bending the approach to such a degree that the solution is
useless). A detailed method can only produce one kind of artifact. The
less flexible a method is, the more identical will the products be.
|Presumptionism manifests itself in many ways. To offer an ontology of the Universe of Production is a presumption as it restricts which elements can be represented in an enterprise model. Likewise, developing an ontology of the Universe of Modeling restricts the way enterprise modeling is performed (but not necessarily what can be represented).|
Tema is designed to be flexible at the expense of possible efficiency. The main reason is the kind of modeling that is sought supported: Enterprise modeling that dominantly involves sense-making and not mere representation.
The reason for including presumptionism as a design criterion is the perceived lack of both support and flexibility in current frameworks for enterprise modeling. Seeing enterprise modeling as essentially an act of sense-making instead of an act of representation implies a need for a shift in modelers' attention.
Elements of the framework are then presented and discussed according to the two main phases of enterprise modeling: The development phase (section 8.3) and the dissemination phase (section 8.4). Each phase is first presented in terms of an illustration followed by objectives, process, artifacts, modeling organization, forums and media.
The chapter is closed by an outline of a few possible technological solutions for supporting Tema, followed by concluding remarks.