Model:- psm_model
PLCS Platform Specific 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.

Changes made to AP239e2 in PLCS PSM

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
Classification efficiency

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.
Additions

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:

Deletions

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

Types

Entities

Replacements

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

Inheritance

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

Select conversion

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.

ViewDefinitionContext

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

Additions

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

Replacements

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

Identification efficiency

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

Additions

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:

Deletions

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

Types

Entities

Replacements

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

Inheritance

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

Select conversion

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.

Description Attribute

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

Additions

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

Deletions

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

Types

Entities

Select conversion

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.

Attribute redundancy

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

Deletions

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.

Replacements

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

Role entity redundancy

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

Deletions

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

Entities

Replacements

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

Composition

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

Additions

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

Replacements

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

Assignment / Relationship objects

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

Additions

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

Inheritance

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

Event

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

Deletions

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

Types

Entities

Replacements

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

Properties

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

Additions

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

Deletions

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

Inheritance

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

Select conversion

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.

Risk properties

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

Additions

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

Deletions

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

Entities

Replacements

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

Units

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

Deletions

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

Entities

Replacements

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

Message

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

Additions

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

Deletions

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

Types

Entities

Replacements

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

Select conversion

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.

Shape

remove the function

Replacements

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

Multiple inheritance

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

Deletions

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

Entities

Replacements

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

single_property_is_definition

Modify Single_property_is_definition to work with new property model

Replacements

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