Erweiterte Anpassung > Business Logic Customization > Data Exchange using Standards in Windchill > STEP Data Exchange using EXPRESS > PLCS Data Exchange
  
PLCS Data Exchange
PLCS Terminology
DEX / Data Exchange Specification
A Data Exchange Specification (DEX) is a subset of the ISO 10303-239 PLCS information model. A DEX is designed to support data exchange for specific activities, provide guidance and rules for how to use and combine the selected entities and external Reference Data in data exchanges. Each DEX includes a complete EXPRESS schema. This is a subset of the ISO 10303-239 schema with a derived XML Schema. Both can be used to define and validate a data exchange file. A DEX that is defined and managed by the OASIS PLCS TC is referred to as a "PLCS DEX", as opposed to a "Business DEX."
Reference Data
Reference Data is data that represents information about classes or individuals which are common to many users. Reference Data provides a tailorable structured vocabulary that extends the PLCS information model with business-specific semantics.
Capability
A Capability is a 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 are used to represent a given concept, how the entities are related, and what Reference Data are used, as well as general guidance. A set of Templates are documented within a Capability to provide precise specifications of which Entities are instantiated to represent identified concepts.
Template
A Template is a precise specification of which entities and attributes in the ISO 10303-239 PLCS are instantiated. It also specifies 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 is referred to as a "PLCS Template", as opposed to a "Business Template."
Templates describe and specify how common business concepts are represented using the PLCS information model. Templates have been defined at a fine grained level to encourage maximum reuse across different DEXs, hence ensuring consistent usage of the PLCS information model. For example, the Template representing_organization is used to represent an organization, and can be reused whenever this is required.