
In this glossary, you will find a set of terms we have defined and reused extensively in our white papers. We have tried to use as few terms as possible. When several terms relate to the same concept, we define only one term and add the others as synonyms.
Chain of Business Functions triggered by an independent Event delivering Process Value to a Client Process.
Example: “execute a Customer order”. The Independent Client Event is the Customer's request.
Example: “hire an employee”. The Independent Client Event is the Manager’s request.
End to End Processes are Operation Processes or Transformation Processes.
A Business Process is broken down into 2 parts:
· the End to End Process Invariants which define the Functions of the Business Process which are the same for all competitors.
· the Business Process Specificities which define what has been added by the Enterprise to customize the Business Process Invariants and gain a competitive advantage.
Business Actor who obtains Value from End to End Process.
For Primary Processes it is the Enterprise Customer.
For Resources Processes (such as human Resources, or Enterprise reporting), the Business Process Client is generally an Employee.
An Enterprise is an agent which creates "value" for a Customer. The value can be economic or not (for example, cultural value).
An Enterprise can be a Legal Entity, a part of a Legal Entity, a network of Legal Entities.
A Group of Companies may represent a real Economic Entity with a unique decision center, without being described as one big Legal Entity. The Group teams represent an Enterprise, and each Company represents an Enterprise.
An Enterprise is described according to a cube of 3 dimensions:
· Complexity: isolates Enterprise Real World from Enterprise Model.
· Agility: isolates Enterprise Operations from Enterprise Transformations.
· Synergy: isolates Specific Elements from Shared Resources and Reused Model.
Defines together
· How an Enterprise is Operated
· How an Enterprise is Transformed
The Enterprise Model Representation is described as a Cube:

An Entity is a set of real world objects which have same Attributes and same behavior (same Life cycle and same Functions).
An Entity can be a Business Entity or an Organization Entity.
Each Entity has its life cycle. Many life cycles are similar: we have formalized the most common life cycles in the Entity Patterns: Operation, Descriptor, Stock and Multi-Application Process.
Type which proposes a pre-defined list of values. These values are often expressed in business terms and not necessarily in technical terms.
Example: Type “Sex” = (male, female, unknown)
A Business Event triggers an End to End Process.
An Organization Event triggers an Organization Process.
Execution of a Solution Model for an Enterprise.
An Executed Solution includes not only the executed Actions but also its Resources: Organization Actors and Information. If these Resources are not private to the Executed Solution, but Shared with other Executed Solutions, they are part of “Shared Resources”.
Enlarges Enterprise Scope to partners, providers and Customers when they become Organization Actors.
Example: when an Enterprise sells its Products through distribution networks which belong to other Legal Entities, we must define Cross Processes and standardize Business Entity definitions and identifiers, which means that together they represent a global Enterprise, the Extended Enterprise
Most of the concepts developped on this website are further developped in our white papers. You can download any white paper freely. Please do not re-use without explicit permission.
Please contact us at contact@ceisar.org if you would like to know more about the CEISAR and our work. We welcome any feed-back and contribution to our research.
Click here to view a full list of our current publications and downloads.