- Behavioural Rule
- Building Block component which describes the desired action(s) to be taken in the flow of control of a Domain Process or a Business Process.
set of Behavioural Rules defines the flow of control of Domain Process or Business Process by definition of selection criteria for executing a cluster of Business Processes and/or Enterprise Activities.
- Business Process (BP)
- describes pieces of enterprise behaviour at all levels of decomposition of the functional decomposition except the top and bottom levels. It may have a functional part defined, and must have a behaviour part and a structural part. It is employed by one or more Domain Processes and/or Business Processes and it employs one or more Business Processes and/or Enterprise Activities. It is triggered by a parent structure (Domain Process or Business Process).
- Capability
- element of the construct Capability Set used to characterise what a Resource can do (Such as to mill, to drill etc.) which is defined by its name and value or a set of enumerated values or a range of values. Capabilities are used to describe: Function related Capabilities, Object related Capabilities, Performance related Capabilities, Operation related Capabilities
- Capability Set
- defined as a collection of Capability Elements or Capabilities. It describes the set of Capabilities required by an Enterprise Activity or provided by a Resource.
- Domain
- represents a subset of the enterprise (i.e. the universe of discourse) to be analysed and for which a CIMOSA compliant Particular Model will be created (i.e. instantiated); used to break down system complexity.
a construct used to establish the content and the boundary of the part of the enterprise, which is subject to analysis based on a given set of business objectives and constraints. It is made of a set of interacting Domain Processes, Events and Object Views (information objects and physical objects including resources).
- CIMOSA Models
- used to describe the different phases of the enterprise life cycle (Requirement Definition, Design Specification and Implementation Description).
are subject to an enterprise engineering process (model development process) which is concerned with both model creation and model maintenance (model update and modification).
contain sets of instances of constructs structured to present solutions to problem areas in manufacturing enterprises in a process oriented language.
may represent partial (partially instantiated) or particular (fully instantiated) solutions.
- CIMOSA Modelling Framework
- provides a common structure for semantic unification within enterprise in the form of:
the CIMOSA Reference Architecture, which provides building blocks/constructs for enterprise modelling
the CIMOSA Particular Architecture, created for the particular enterprise using the reference Architecture.
represented by a three-dimensional structure whose orthogonal axes define the CIMOSA Model Creation Processes: Stepwise Instantiation, Stepwise Derivation and Stepwise Generation
applied and maintained through the definition and use of CIMOSA Environments: Enterprise Engineering Environment and Enterprise Operation Environment.
- CIMOSA Modelling Levels
- define three Modelling Levels: Requirements Definition, Design Specification and Implementation Description;
associated with each Modelling Levels there exist: a defined set of Generic Building Blocks (i.e. generic constructs) and Building Block Types (i.e. specific construct types), Partial Models and a Particular Model
- CIMOSA Particular Architecture
- defines the architectural solution for a specific manufacturing enterprise in a form derived directly from the CIMOSA Reference Architecture, conditioned by the needs and the requirements of that specific enterprise.
- CIMOSA Reference Architecture
- definite base from which CIMOSA Particular Architectures may be created. It consists of defined extendible sets of: Generic Building Blocks and Building Block Types defined as object classes, Partial Models and relationships, rules and constraints governing the application of the modelling constructs and Partial Models for specific use.
- CIMOSA View
- defines along its Stepwise Generation Axis four views (Function, Information, Resource, Organisation) which allow to focus on specific aspects of integrated enterprise models discarding others.
- Domain Process (DP)
- triggered by means of at least one Event and nothing else than Events and producing a defined end result (Function Output). It encapsulates a well defined set of enterprise functionalities and behaviour (i.e. Enterprise Activities and Business Process) to realise clearly defined objectives (Domain Objectives) under given constraints (Domain Constraints).
receives input from and/or provides output to other Domain Processes. It is only used by one Domain, i.e. it is not used either by any other Domain or a Business Process, and therefore is at the top of a functional decomposition hierarchy.
- Enterprise Activity (EA)
- describes a piece of functionality in the Function View of a particular enterprise at the Requirements Definition Modelling Level, i.e. "one of the things to be done".
a construct which has a functional part and a structure part defined, but not a behaviour part. It is employed by one or more Domain Processes and/or Business Processes, but does not employ any Business Process or Enterprise Activities. It is characterised by the definition of its inputs and outputs.
Enterprise Activities of a particular enterprise define elementary tasks to be performed in the enterprise which consume inputs to produce outputs and need allocation of time and resources for the full duration of their execution.
- Enterprise Object
- describes generalised, real or abstract, uniquely identified, entity of the enterprise's Information System (i.e. things which can be conceptualised or thought about as being a whole), and characterised by a unique identity, name and descriptive properties;
made of a set of Properties (or attributes) and possibly other constituent Enterprise Objects They can inherit properties from more generic Enterprise Objects.
- Enterprise Integration
- The process that combines separate entities (processes, products, activities) into what seems to be a synergetic whole. In the main realm of enterprise integration this means the "combination" of several different machines, computer programs and human resources grouping together to common goals. Enterprise Integration is a strategy rather than a technology.
- Enterprise Engineering
- The techniques to plan and operate the day to day business of an enterprise using engineering disciplines and methods. Enterprise Engineering makes use of business processes that can be composed to models of the enterprise or parts of it.
- Event
- (solicited and unsolicited) real-world happening, timer or request to do something in the enterprise or its environment. It can carry information(defined as Object View). It is used to trigger the execution of one or more Domain Processes (and hence indirectly activates an employed Business Process/Enterprise Activity) by initiating the processing of their associated set of Behavioural Rules. It may also be used to condition the flow of control of a Business Process within a Domain Process.
- Functional Entity
- active Resource able to perform, completely on its own, a (class of) Functional Operation(s). A Resource which is classified as a Functional Entity must be able to communicate with the IIS and to process the relevant external protocol (Human Dialogue Service, Machine Dialogue Service, Application Dialogue Service) of its Presentation Services.
- Functional Operation
- basic unit of work at the lowest level of granularity in the Function View. At run-time it is fully executed or not at all. It consists of a name, a reference to a Functional Entity and a list of arguments including a status code.
- Information Element (or attribute)
- used to represent any item of information which, for the purposes they are being used, are indivisible i.e. atomic in an Enterprise Object or one of its Object Views. Each Information Element is defined on a given data type.
- Object View
- description of one aspect of one or more Enterprise Objects. It therefore describes a subset of properties owned by one or more Enterprise Objects from a given standpoint. It is made of Information Elements and/or Object Views.
- Organisational Cell
- description of an organisational area.
describe generalised, real or abstract, uniquely identified, entities of the enterprise formal organisational structure, and are characterised by their unique identity, their name and descriptive properties. Each Organisational Cell contains at least one relationship to an Organisation Unit.
- Organisational Element
- represents an area of responsibility as well as an area of authority of apart of a job description which represents the atomic level of the Organisation View. The construct offers the possibility to specify different degrees of responsibility and authority for the different Specified Organisation Elements.
- Resource
- an enterprise mean required to execute Enterprise Activities
has a Capability Set characterising the functional, object related, performance and operational attributes of the Resource and provides a set of Functional Operations