Model:- psm_model

The PLCS Platform Specific Model is a model intended for implementation.

The model has been derived from the ISO 10303-239 AP239 edition 2 EXPRESS model. It is documented as an EXPRESS models and a corresponding SysML block definition model.

The SysML XMI and EXPRESS models are available for download.

The document describes the changes that have been made to AP239 ed2 schema in order to create the PLCS PSM schema.

The changes are grouped into the following sections:

  1. Classification efficiency
  2. ViewDefinitionContext
  3. Identification efficiency
  4. Description Attribute
  5. Attribute redundancy
  6. Role entity redundancy
  7. Composition
  8. Assignment / Relationship objects
  9. Event
  10. Properties
  11. Risk properties
  12. Units
  13. Message
  14. Shape
  15. Multiple inheritance
  16. single_property_is_definition
  17. single_property_is_definition

This section describes the changes that have been made in order to provide an efficient approach to classification.

  1. Add Classification;
  2. Remove the classification entities that should be in the reference data.

The following types have been added to the AP239 schema in order to create the PLCS PSM schema:

The following entities have been added to the AP239 schema in order to create the PLCS PSM schema:

The following entities, attributes types have been deleted from the AP239 schema in order to create the PLCS PSM schema:

Types

Entities

The following entities and types in the AP239 schema have been replaced in order to create the PLCS PSM schema:

The inheritance of the following entities from the AP239 schema has been modified in order to create the PLCS PSM schema:

The following select types in the AP239 schema have been replaced with abstract supertypes. The select becomes an abstract supertypes, and each entity that is a member of the select, is subtype.

This section describes the changes that have been made to ViewDefinitionContext.

The following entities have been added to the AP239 schema in order to create the PLCS PSM schema:

The following entities and types in the AP239 schema have been replaced in order to create the PLCS PSM schema:

This section describes the changes that have been made in order to provide an efficient approach to identification.

The following types have been added to the AP239 schema in order to create the PLCS PSM schema:

The following entities have been added to the AP239 schema in order to create the PLCS PSM schema:

The following entities, attributes types have been deleted from the AP239 schema in order to create the PLCS PSM schema:

Types

Entities

The following entities and types in the AP239 schema have been replaced in order to create the PLCS PSM schema:

The inheritance of the following entities from the AP239 schema has been modified in order to create the PLCS PSM schema:

The following select types in the AP239 schema have been replaced with abstract supertypes. The select becomes an abstract supertypes, and each entity that is a member of the select, is subtype.

This section describes the changes that have been made in order to improve how descriptions are assigned

The following entities have been added to the AP239 schema in order to create the PLCS PSM schema:

The following entities, attributes types have been deleted from the AP239 schema in order to create the PLCS PSM schema:

Types

Entities

The following select types in the AP239 schema have been replaced with abstract supertypes. The select becomes an abstract supertypes, and each entity that is a member of the select, is subtype.

This section describes which attributes have been identified as being redundant and therefore can be removed from the schema.

The following entities, attributes types have been deleted from the AP239 schema in order to create the PLCS PSM schema:

Attributes

The following attributes have been deleted from every entity.

The following entities and types in the AP239 schema have been replaced in order to create the PLCS PSM schema:

Remove entities that represent a role. The role should be represented by classification

The following entities, attributes types have been deleted from the AP239 schema in order to create the PLCS PSM schema:

Entities

The following entities and types in the AP239 schema have been replaced in order to create the PLCS PSM schema:

This section describes the changes that have been made in order to force use of composition rather than reference.

The following types have been added to the AP239 schema in order to create the PLCS PSM schema:

The following entities and types in the AP239 schema have been replaced in order to create the PLCS PSM schema:

This section describes the changes that have been made in order to make the assignment and relationship entities explicit

The following entities have been added to the AP239 schema in order to create the PLCS PSM schema:

The inheritance of the following entities from the AP239 schema has been modified in order to create the PLCS PSM schema:

According to AP239 the Event entity should not be used. This section describes the changes that have been made to remove Event.

The following entities, attributes types have been deleted from the AP239 schema in order to create the PLCS PSM schema:

Types

Entities

The following types in the AP239 schema have been replaced in order to create the PLCS PSM schema:

This section describes the changes that have been made in order to make the representation of properties more efficient.

The following entities have been added to the AP239 schema in order to create the PLCS PSM schema:

AP239 requires that properties assigned to activity, resources, documents and products are all treated differently. In the PSM, only one approach is required, hence a number of property entities are redundant.

The following entities, attributes types have been deleted from the AP239 schema in order to create the PLCS PSM schema:

Types

Entities

The inheritance of the following entities from the AP239 schema has been modified in order to create the PLCS PSM schema:

The following select types in the AP239 schema have been replaced with abstract supertypes. The select becomes an abstract supertypes, and each entity that is a member of the select, is subtype.

This section describes the changes that have been made in order to make the properties associated with Risk conform to the new property model.

The following entities have been added to the AP239 schema in order to create the PLCS PSM schema:

The following entities, attributes types have been deleted from the AP239 schema in order to create the PLCS PSM schema:

Entities

The following entities and types in the AP239 schema have been replaced in order to create the PLCS PSM schema:

This section describes the changes that have been made in order to make the representation of units efficient.

The following entities, attributes types have been deleted from the AP239 schema in order to create the PLCS PSM schema:

Entities

The following entities and types in the AP239 schema have been replaced in order to create the PLCS PSM schema:

This section describes the changes that have been made in order to make the representation of message efficient.

Every exchange that is performed according to a DEX should contain one ExchangeContextClassLibrary that defines the ontology that is to be used with the data. Each exchange is represented by a message. Therefore relate the message to the ExchangeContextClassLibrary

The following entities have been added to the AP239 schema in order to create the PLCS PSM schema:

The following entities, attributes types have been deleted from the AP239 schema in order to create the PLCS PSM schema:

Types

Entities

The following entities and types in the AP239 schema have been replaced in order to create the PLCS PSM schema:

The following select types in the AP239 schema have been replaced with abstract supertypes. The select becomes an abstract supertypes, and each entity that is a member of the select, is subtype.

remove the function

The following entities and types in the AP239 schema have been replaced in order to create the PLCS PSM schema:

In order to enable easy implementation of entities that have multiple inheritance, it is necessary to ensure that entities that have supertypes are only subtype of only one instantiable entity. All other inherited supertypes should be abstract. This requires that a number entities are made abstract or removed from the inheritance

The following entities, attributes types have been deleted from the AP239 schema in order to create the PLCS PSM schema:

Entities

The following entities and types in the AP239 schema have been replaced in order to create the PLCS PSM schema:

Modify Single_property_is_definition to work with new property model

The following entities and types in the AP239 schema have been replaced in order to create the PLCS PSM schema: