An Arbitrary Connector is a link between the two Concept Roles, represented in the form of a stroke.

A concept is a statement expressing the essential nature of a being, an object, a word through its essential properties and characteristics or its specific qualities.

A concept domain is a sub-set of elements of a subject area that reduces the scope of a fields.

A concept property is a category of linguistic unit used to represent properties of a concept: name, description, etc.s.

A Concept Role part of a High Level Operational Concept represented as a shape.

A concept type enables classification of concepts. Relationships between concept types are represented by concept type components.

A concept view enables representation of the semantic scope covered by a business object. A concept view is based on the selection of several concepts specific to the view.

A High Level Operational Concept is a rough draft of a model; unformal representation.

An Interface is a template of a contract between entities (organizational, IT …). The contract is described by available operations which can be triggered trough messages exchanged by roles (vendor, buyer..).

An Interface use is associated to an interface. It enables representation of complex exchanges.

An Operational Activity is an end-to-end collection of Activity Actions that creates an outcome for a customer, who may be the ultimate customer or an internal end-user of the Operational Activity.

An Operational Activity Action is a distinct, identifiable phase or step within an Operational Activity that has a unique entrance criteria, exit criteria, and identifiable participating Operational Performer or Operational Domain.

A Operational Activity Fulfillment follows the Class of Building Block Realization pattern and materializes the fulfillment of a Operational Activity by a BPMN Personnel Function, for instance.

A Operational Architecture represents the relationships of a Operational Domain with its partners.

An Operational Constraint is a rule that is under business jurisdiction.

A Operational Domain is a grouping of Operational Performer​s and their associated Operational Activities on the conjunction of two main criteria. 1. Their need in accomplishing one or more Capabilities. 2. The common skills and functionalities required to accomplish these Capabilities.

An Operational Domain Operational Activity Performance is the relationship between a Operational Domain and a Operational Activity that it performs.

An Operational Domain Role is the usage of an Operational Domain which is internal to the considered environment.

An Operational Partner is a conceptual stakeholder type that interacts with the enterprise in the context of the enterprise Operational Architecture. Examples : 'Private Sector Customer', 'Regulation Authority', 'Supplier'.

An Operational Performer​ is a skill or grouping of skills of interest for the enterprise.

An Operational Role represents the configuration of a Operational Performer within another one.

A Partner Operational Domain Role is the usage of a Operational Domain which is external to the considered environment.

A request point is a point by which an agent requests a service from potential suppliers.

A role is a participant in an interaction service, workflow or Personnel Function. It can be the initiator, that is the requester of a service, or it can represent a sub-contractor carrying out processing outside the service. A role is an integral part of the object that it describes, and is not reusable. It can subsequently be assigned to an org-unit internal or external to the organization or to an IT component. Examples: client, traveler.

A Service Interaction represents an interaction for service purpose between entities in a specific context inside or outside a company. These entities can be enterprise org-units, applications, activities or Personnel Functions, as well as external org-units. The content of this interaction is described in an Interface.

A service operation specifies exchanges between participants.

A service operation use represents the usage of a service operation in an service interface.

A service point is a point from which a system receives a request from another system and provides the requested service.

A Signal designates the content of a message or a message flow, independently of its structure. Signals may be used by several messages or message flows, since it is not associated with an sender and a destination.

A term is a word or group of words that is used for a specific meaning in a specific context.