Help TOC > PLCS technical description > Business DEXs
Business DEXs Date: 2010/03/30 10:39:30
Revision: 1.29

This technical description provides an overview of how the same constructs used for generic DEXs may be used to further specialize PLCSProduct Life Cycle Support The project developing ISO 10303-239. The name of ISO 10303-239 (published by ISO in 2005). to operate within a more constrained Business ContextA "business context" is a context in which a specialized vocabulary is employed. This may be an individual organization, a larger business community, or a particular project (or initiative). A number of Business DEXs and Templates are identified within a given Business Context and each DEX is defined using the specialized vocabulary of its Business Context.. The context may be a project, an organization or enterprise. One or more Business DEXsA Business DEX is a DEX that has been defined outside the OASIS PLCS TC. It is, generally speaking, more business specific and may extend or specialize a PLCS DEX. A Business DEX is defined and managed within a specific Business Context. may be defined within such a context.

Note: In order to distinguish between the similar terms used for components developed by the OASIS PLCS TCThe technical committee within OASIS responsible for developing the PLCS DEXs http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=plcs. for submission as a standard and business specific components, the components may be prefixed "PLCS" or "Business" respectively. A DEX that is standardized by the OASIS PLCS TC is then referred to as a "PLCS DEX" rather than a "Business DEX".

The PLCS DEXs are defined using standard terminology and support activities defined in the ISO 10303-239ISO 10303-239 Industrial automation systems and integration — Product data representation and exchange Part 239: Application protocol: Product life cycle support, See: http://en.wikipedia.org/wiki/ISO_10303 and http://www.iso.org Activity ModelAn IDEF0 model that describes an application in terms of its processes and information flows.. Whilst this provides a definition of a data exchange that satisfies a particular business need, it may still be too generic for defining a contractual data exchange agreement. In particular:

The approach is, therefore, to define one or more Business DEXs within a specific Business Context.

The set of Business DEXs then provide a library of mappings to PLCS components that can be reused.

Business DEX

A Business DEX contains at least one Business Object, which is mapped to a Business TemplateA Business Template is a Template that represents a Business Object or part of a Business Object., which can make use of other Business Templates and PLCS Templates. The relationships between the various parts of a Business DEX and other DEXlibDEXlib is the XML environment created for the development of PLCS OASIS DEXs and components. It is also used for the development of Business DEXs and components. The ongoing work in the DEXlib development environment is published on a daily basis in HTML at http://www.plcs.org/plcs/dexlib/dex_index.htm. components are illustrated in Figure 1 and described below.



Figure 1 —  Constituents of a Business DEX and relation to OASIS PLCS constructs

Figure 1 —  Constituents of a Business DEX and relation to OASIS PLCS constructs

Definition: A Business DEX is a DEX that has been defined outside the OASIS PLCS TC. It is, generally speaking, more business specific and may extend or specialize a PLCS DEX. A Business DEX is defined and managed within a specific Business ContextA "business context" is a context in which a specialized vocabulary is employed. This may be an individual organization, a larger business community, or a particular project (or initiative). A number of Business DEXs and Templates are identified within a given Business Context and each DEX is defined using the specialized vocabulary of its Business Context..

Organizations that wish to exchange data must agree on both the technical aspects of the data exchange (what information and in what format) and the business processes that should be applied (when to exchange data, how to approve it, etc). A Business DEX is a full specification of the technical aspects of a data exchange, and fulfills the technical requirements of an exchange agreement.

A Business DEX might be created because its scope is not considered generic enough to apply across different businesses and therefore not meaningful to become a OASIS PLCS DEX, or because it was developed to only meet a specific business need. When it is made available for public scrutiny and feedback, Business DEXs may be found to be of interest in a broader context. This might lead to such DEXs being generalized and adopted by the OASIS PLCS TC. Developing and publishing a Business DEX can also be used as a first step to initiating a new PLCS DEX, if no suitable PLCS DEXs is available. The fact that the DEXlib development platform is available also for non OASIS PLCS DEXs, facilitates such transitions.

There are no explicit CapabilitiesA description of how EXPRESS entities are used to represent a given concept (a specific "functionality" or "capability"). It provides guidance and rules on what Entities should be used to represent a given concept, how the entities should be related, and what Reference Data should be used. As well as general guidance, a set of Templates are documented within a Capability to provide precise specifications of which Entities should be instantiated to represent identified concepts. for Business DEXs or direct relationships between the Capabilities and the Business Templates.

Business Objects

Definition: A Business Object is a description in business terms of a concept required for data exchange in a given business domain, coupled with a mapping to relevant PLCS entities. A Business Object is defined in the context of a Business DEX.

A Business Object describes a specific business requirement. It may be documented using EXPRESSThe STEP product data specification language. It consists of language elements that allow an unambiguous data definition and specification of constraints on the data defined. Defined in ISO 10303-11. See: http://en.wikipedia.org/wiki/ISO_10303-11, UML, or some other modelling paradigm. The component concepts of a Business Object are represented using the EXPRESS datatypes specified by one or more Business Templates that are equivalent to the Business Object.

Business Templates

Definition: A Business Template is a TemplateA Template is a precise specification of which entities (and attributes) in ISO 10303-239 PLCS should be instantiated, and which Reference Data should be used, to represent a concept providing documented functionality in a Capability. A Template defined and managed by the OASIS PLCS TC may be referred to as a "PLCS Template", as opposed to a "Business Template" that represents a Business ObjectA Business Object is a description in business terms of a concept required for data exchange in a given business domain, coupled with a mapping to relevant PLCS entities. A Business Object is defined in the context of a Business DEX. or part of a Business Object.

A Business Template is very similar to a PLCS Template, in that it defines PLCS entities and their relations, and uses PLCS Templates as needed to simplify this. The only difference is that a Business Template may use both PLCS Templates and Business Templates whereas a PLCS Template can only use other PLCS Templates.

Business Reference Data Library

Definition: A Business RDL is a Reference Data Library that specializes the OASIS RDL further in order to achieve semantic precision in a specific business context. A Business RDL is a Reference Data Library that specializes the OASIS RDLThe Reference Data Library standardized and managed by the OASIS PLCS TC (managed in DEXlib). Sometimes referred to as "OASIS PLCS RDL". further in order to achieve semantic precision in a specific Business ContextA "business context" is a context in which a specialized vocabulary is employed. This may be an individual organization, a larger business community, or a particular project (or initiative). A number of Business DEXs and Templates are identified within a given Business Context and each DEX is defined using the specialized vocabulary of its Business Context..

Each Business DEX must define a Business RDL with Reference Data ClassA Reference Data Class is Reference Data that represents a class. The class definition representing a Reference Data item (e.g. term, definition and rules), used to specialize entities of the information model, to make the use of them semantically more precise. It is sometimes called a "RDL class".es that fulfil the requirements of the Business Objects. Classes from OASIS RDL may, of course, be used unmodified, but it is unlikely that these classes will suffice for all purposes.

The DEXlib development environment has a specific section for Business DEXs. This is not part of the official OASIS PLCS standardization work, but is provided for the mutual benefit of projects and organizations working with ISO 10303-239 PLCS. It is used to publish work that has been developed in parallel to the OASIS PLCS TC work, and is typically either project specific (with a much more narrow context than PLCS), or work that is intended to become part of OASIS PLCS TC but is not yet not generalized enough.

Business Contexts

The business specific information in DEXlib is organized into "Business Contexts" - a context for the information. The Context may be a project, an organization, or an enterprise. One or more Business DEXs may be defined within the same Context.

Definition: A "business context" is a context in which a specialized vocabulary is employed. This may be an individual organization, a larger business community, or a particular project (or initiative). A number of Business DEXsA Business DEX is a DEX that has been defined outside the OASIS PLCS TC. It is, generally speaking, more business specific and may extend or specialize a PLCS DEX. A Business DEX is defined and managed within a specific Business Context. and TemplatesA Template is a precise specification of which entities (and attributes) in ISO 10303-239 PLCS should be instantiated, and which Reference Data should be used, to represent a concept providing documented functionality in a Capability. A Template defined and managed by the OASIS PLCS TC may be referred to as a "PLCS Template", as opposed to a "Business Template" are identified within a given Business Context and each DEX is defined using the specialized vocabulary of its Business Context.

Structure and contents of Business DEXs

Each Business DEX Contains: