Ref data:- http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm
Ontology
Status: created
Version: v1.0
Revision : $Revision: 1.41 $
File: plcs-psm-en.owl
Description:
This ontology provides English language descriptions for the OWL classes derived from the PLCS model.
Change history:
Last editor: $Author: philsp $
Last edit date: $Date: 2013-08-23 19:38:45 $
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#Activity    [Status: passed_review]
Class label: activity
Class specification
Definition:
action or a set of actions that consume time and resources and whose performance is necessary to achieve, or contribute to, the realization of one or more outcomes
Notes:
NOTE 1:  The action or set of actions is something that has taken place, is taking place, or is expected to take place in the future.
Examples:
EXAMPLE 1:  Changing the design of a bicycle
EXAMPLE 2:  Designing a bicycle
EXAMPLE 3:  Training someone to ride a bicycle
Sources:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
  2. ISO/IEC 15288:2003, "Systems and software engineering - System life cycle processes"
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ActivityActual    [Status: passed_review]
Class label: actual activity
Description:
activity that has started but not necessarily finished
Examples:
EXAMPLE 1:  The replacement of the tyres of my bicycle, frame number ZH002342, on October 25, 2011.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ActivityAssignment    [Status: passed_review]
Class label: activity assignment
Description:
assignment of an activity to something
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ActivityHappening    [Status: ready_for_review]
Class label: activity happening
Description:
activity relationship between an activity and an activity happening
Notes:
NOTE 1:  A single activity may realize several activity happenings.
NOTE 2:  A single activity happening may be realizations of several activities
Examples:
EXAMPLE 1:  A single actual servicing activity includes several checks and repairs (e.g. an oil-check and a tyre-replacement).
EXAMPLE 2:  A single defined check (e.g. an oil-check) is actually performed on many occasions or vehicles.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ActivityMethod    [Status: passed_review]
Class label: method
Class specification
Definition:
specific way to carry out an activity
Notes:
NOTE 1:  A method typically follows a defined and regular plan.
NOTE 2:  There may be more than one method for producing a required result.
Examples:
EXAMPLE 1:  instructions for changing a tyre.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ActivityMethodAssignment    [Status: passed_review]
Class label: method assignment
Description:
assignment of a method to something
Examples:
EXAMPLE 1:  Instructions on how to change a tyre assigned to the part "Tyre".
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ActivityMethodRealization    [Status: ready_for_review]
Class label: activity method realization
Description:
association of an method with a scheme or task that puts it inot practice
Notes:
NOTE 1:  More than one specification can be associated with the same ActivityMethod.
Examples:
EXAMPLE 1:  For a given planned activity there may be a task specification, a statement of how task performance is to be logged and a schedule that all apply.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ActivityMethodRealizationRelationship    [Status: ready_for_review]
Class label: activity method realization relationship
Description:
relationship between two activity method realizations
Notes:
NOTE 1:  An activity method realization relationship may be used to specify sequencing and other constraints between different realizations for the same method.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ActivityMethodRelationship    [Status: ready_for_review]
Class label: activity method relationship
Description:
relationship between two methods
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ActivityRelationship    [Status: ready_for_review]
Class label: activity relationship
Description:
relationship between two activities
Examples:
EXAMPLE 1:  The activity required to complete a work order, may be decomposed into many sub-activities. These can be related using activity relationships.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#Address    [Status: ready_for_review]
Class label: address
Description:
information that locates persons or organizations
Notes:
NOTE 1:  An address provides location details for communication via postal mail, telephone, facsimile, telex or electronic mail.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#AddressAssignment    [Status: passed_review]
Class label: address assignment
Description:
assignment of an address to something
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#AddressBasedLocationRepresentation    [Status: created]
Class label: Address based location representation
Description:
An AddressBasedLocationRepresentation is a specialization of LocationRepresentation specified by its postal identification
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#AdvisoryNote    [Status: ready_for_review]
Class label: advisory note
Description:
link between a task element and an advisory task step
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#AdvisoryTaskStep    [Status: created]
Class label: advisory task step
Description:
An AdvisoryTaskStep is a type of TaskStep. It conveys information
Notes:
NOTE 1:  Some TaskMethods may not require any action to be undertaken.
Examples:
EXAMPLE 1:  "Beware of hot exhausts", "do not use tool X this way" and similar messages.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#AlternatePartRelationship    [Status: created]
Class label: Alternate part relationship
Description:
An AlternatePartRelationship is a specialization of AlternateProductRelationship where the alternate and base products are parts
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#AlternateProductRelationship    [Status: created]
Class label: Alternate product relationship
Description:
An AlternateProductRelationship is an association between two instances of Product. It specifies that any version of the AlternateProductRelationship, may be used in place of any version of the baseProduct. The relationship established by the AlternateProductRelationship is not symmetric: if B is an alternate product for A, A is not implied to be an alternate product for B
Notes:
NOTE 1:  An AlternateProductRelationship for which the baseProduct is an assembly involves that the entire product structure of the alternateProduct may be used in place of the baseProduct and its product structure.
NOTE 2:  An AlternateProductRelationship may relate products of any kind, provided both related instances of Product identify products of the same kind, for example part-part or document-document.
NOTE 3:  An organization may track design changes for a base part, and establish effectivity conditions for the use of that base part in various assemblies to be manufactured. The use of an alternate product implies that an organization does not specify any particular version of the alternate product nor establish effectivities relating to it.
NOTE 4:  If a product is an alternate for another product, it is understood that there is no interest to keep track of which product, the base or any alternates specified, is used as a particular instance of the base product within a product structure.
Examples:
EXAMPLE 1:  Two bolts of the same size are products. One bolt has a square head and the other has a hexagonal head. The two bolts are considered equivalent with respect to form, fit, and function: they both have sufficiently close physical shape, they take up the same space when used, and they both serve to fasten two things together. Thus, one of these two bolts could be considered to be an alternate part for the other bolt.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#Analysis    [Status: created]
Class label: analysis
Description:
An Analysis is a specialization of Product. It is produced via a reproducible process
Notes:
NOTE 1:  Analysis is the process of studying or examining something in an organized way to learn more about it, or a particular study or examination of something. The full range of the analysis process includes mathematical, physical testing, cognitive, chemical, etc.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#AnalysisAssignment    [Status: ready_for_review]
Class label: analysis assignment
Description:
assignment of an analysis to something
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#AnalysisDisciplineDefinition    [Status: created]
Class label: Analysis discipline definition
Description:
An AnalysisDisciplineDefinition is a specialization of ProductViewDefinition. It is a definition or view of an AnalysisVersion taken from the perspective of the analysing organization. The AnalysisDisciplineDefinition is controlled by the analysing organization. The entity may be used to capture the definition of a particular version of an analysis at any intermediate stage of its development where the definition is not formally released by an organization at the analysis version level. It may be used to capture the various stages in the definition cycle of a product
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#AnalysisModel    [Status: ready_for_review]
Class label: internal analysis model
Description:
analysis model that supports the description of analysis concepts
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#AnalysisModelObject    [Status: ready_for_review]
Class label: analysis model
Description:
representation of the results of an analysis
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#AnalysisRepresentationContext    [Status: created]
Class label: Analysis representation context
Description:
An AnalysisRepresentationContext defines the context for the items (AnalysisModelItemsSelect) used in an AnalysisModel
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#AnalysisVersion    [Status: created]
Class label: Analysis version
Description:
An AnalysisVersion is a specialization of ProductVersion that identifies a particular version of an analysis
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#AnalysisVersionRelationship    [Status: created]
Class label: Analysis version relationship
Description:
A AnalysisVersionRelationship is a specialization of ProductVersionRelationship that is used to assert an association between two versions of an analysis
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#AnalysisVersionSequence    [Status: created]
Class label: Analysis version sequence
Description:
A AnalysisVersionSequence is a specialization of AnalysisVersionRelationship that is used to assert that the one analysis version (the successor) replaces another (its predecessor)
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#AndStateCauseEffectDefinition    [Status: created]
Class label: And state cause effect definition
Description:
An AndStateCauseEffectDefinition is a specialization of StateCauseEffectDefinition. It relates one or more causing StateDefinition entities and one effect StateDefinition. All the causing StateDefinition entities must exist prior to the single effect
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ApplicationDomain    [Status: passed_review]
Class label: application domain
Description:
application or discipline
Notes:
NOTE 1:  The combination of an application domain and a life-cycle phase defines a view of a product.
NOTE 2:  The context is typically an application, process or discipline.
Examples:
EXAMPLE 1:  Product support
EXAMPLE 2:  Digital mock-up
EXAMPLE 3:  Preliminary design
EXAMPLE 4:  Electrical design
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#Approval    [Status: passed_review]
Class label: approval
Class specification
Definition:
formal record of the fact that the item to which the approval is assigned fulfills agreed criteria
Examples:
EXAMPLE 1:  A formal record that a type of maintenance procedure "XYZ" has been authorized.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ApprovalAssignment    [Status: ready_for_review]
Class label: approval assignment
Description:
assignment of an approval to something
Examples:
EXAMPLE 1:  The assignment of the formal record of authorization to maintenance procedure "XYZ".
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ApprovalRelationship    [Status: created]
Class label: Approval relationship
Description:
relationship between two instances of Approval
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ApprovingPersonOrganization    [Status: created]
Class label: Approving person organization
Description:
An ApprovingPersonOrganization is an association between an Approval and the organization or person and organization that has granted this approval
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#AssemblyRelationshipSubstitution    [Status: created]
Class label: Assembly relationship substitution
Description:
relationship that indicates that an AssemblyViewRelationship may be substituted by another AssemblyViewRelationship. Both assembly relationships shall refer to the same ProductViewDefinition of the same assembly. An AssemblyRelationshipSubstitution defines a one-way substitution: if A is specified as a substitute for B, B is not implied to be a substitute for A
Notes:
NOTE 1:  As instances of AssemblyViewRelationship establish assembly relationships relevant in the definition contexts of the assembly, the substitution only apply in these contexts.
NOTE 2:  Consequently, an AssemblyRelationshipSubstitution actually specifies that the product version that plays the role of component in the substituteRelationship may be replaced by the product version that plays the role of component in the baseRelationship.
NOTE 3:  The instance of the substitute constituent does not require the same spatial relationship or the same quantity. A substitute constituent does not require equivalent form, fit, and function of the constituent for which it is a substitute.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#AssemblyViewRelationship    [Status: ready_for_review]
Class label: assembly component relationship
Description:
view definition relationship between two product views
Notes:
NOTE 1:  An assembly component relationship identifies a (possibly quantified) use of a product view as a component of another product view
NOTE 2:  In different contexts, the structure of an assembly may be described differently. One assembly description may, for example, may define an intermediate level between two product versions that is absent from another assembly description.
NOTE 3:  An assembly component relationship may be used to establish assembly relationships during design or to represent the composition of an assembly existing in the real world.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#AssignmentObject    [Status: passed_review]
Class label: assignment
Description:
allocation of an object to a target object
Notes:
NOTE 1:  The object being allocated is normally, but not always, of a different type to the target of the allocation.
NOTE 2:  An assignment implies a direction from an object to a target object.
Examples:
EXAMPLE 1:  Assignment of a start date to the target object - a project.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#AssignmentObjectRelationship    [Status: ready_for_review]
Class label: assignment object relationship
Description:
relationship between two assignments
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#AssociationObject    [Status: passed_review]
Class label: association
Description:
link between two objects
Notes:
NOTE 1:  An association implies no directionality or precedence between the objects
NOTE 2:  The objects being associated are normally, but not always, of different types or subtypes.
Examples:
EXAMPLE 1:  In zone is an association between a zone and something in the zone
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#Assumption    [Status: created]
Class label: Assumption
Description:
An Assumption is the identification of something assumed to be true without proof. The reason or justification for an assumption being made shall be represented by a JustificationAssignment being assigned to the Assumption. The item that is assumed shall be related to the Assumption by an ItemAssumed
Examples:
EXAMPLE 1:  An activity is planned based on the assumption that the resource required to perform the activity is available at a location.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#AssumptionAssignment    [Status: ready_for_review]
Class label: assumption assignment
Description:
assignment of an Assumption to something
Examples:
EXAMPLE 1:  The following set of assumptions are relevant to the project.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#AssumptionRelationship    [Status: created]
Class label: Assumption relationship
Description:
relationship between two Assumptions
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#AttachmentSlot    [Status: passed_review]
Class label: attachment slot
Description:
place on a product nominated for the attachment of part specifications
Notes:
NOTE 1:  nominated position (or place) on a product where a part specification is attached or can be attached
Examples:
EXAMPLE 1:  A fast jet aircraft has two engines. These engines are removable and interchangeable between individual aircraft. An attachment slot represents each installation position for an engine so as to ensure that an accurate record is maintained of which engines fly in which pairing on which aircraft for how many hours.
Source:
  1. ISO 10303-239:2012 Product life cycle support
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#AttachmentSlotAsPlanned    [Status: created]
Class label: Attachment slot as planned
Description:
An AttachmentSlotAsPlanned is a specialization of AttachmentSlotVersion that identifies an individual that is the subject of a plan to realize an AttachmentSlot
Examples:
EXAMPLE 1:  FlyFasterWithUs Group will buy an aircraft with serial number 1234 next year. The company wishes to plan the schedule for removal of engines from the aircraft for maintenance purposes. Instances of the AttachmentSlotAsPlanned entity data type allow the company to associate individual engines with the aircraft at different times over the planned period.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#AttachmentSlotAsRealized    [Status: created]
Class label: Attachment slot as realized
Description:
An AttachmentSlotAsRealized is a specialization of AttachmentSlotVersion that identifies an individual that is a realized AttachmentSlot
Examples:
EXAMPLE 1:  FlyFasterWithUs Group operates an aircraft with serial number 1234 next year. The company records which individual engines power the aircraft at different times during the lifetime of the aircraft.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#AttachmentSlotDefinition    [Status: created]
Class label: Attachment slot definition
Description:
An AttachmentSlotDefinition is a specialization of ProductViewDefinition that identifies a view of an AttachmentSlot
Examples:
EXAMPLE 1:  An airworthiness authority requires an airline company to report which individual engines power the aircraft at different times during the lifetime of the aircraft.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#AttachmentSlotDesign    [Status: created]
Class label: Attachment slot design
Description:
An AttachmentSlotDesign is a specialization of AttachmentSlotVersion that identifies the design version of an attachment slot
Examples:
EXAMPLE 1:  WeMakeBigPlanes Limited creates design version 1.34 of the attachment slot for the starboard engine of an aircraft.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#AttachmentSlotDesignToPlanned    [Status: created]
Class label: Attachment slot design to planned
Description:
An AttachmentSlotDesignToPlanned is a relationship between a design version of an AttachmentSlot and a planned individual that conforms to the design
Examples:
EXAMPLE 1:  WeMakeBigPlanes Limited plans production of aircraft serial number 1234 with a starboard engine attachment slot that is to conform to design version 1.34.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#AttachmentSlotDesignToRealized    [Status: created]
Class label: Attachment slot design to realized
Description:
An AttachmentSlotDesignToRealized is a relationship between a design version of an AttachmentSlot and a realized individual that conforms to the design
Examples:
EXAMPLE 1:  WeMakeBigPlanes Limited builds aircraft serial number 1234 with a starboard engine attachment slot that conforms to design version 1.34.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#AttachmentSlotOnProduct    [Status: created]
Class label: Attachment slot on product
Description:
An AttachmentSlotOnProduct is a relationship between a product and an AttachmentSlot that is a location on the product at which to install removable parts
Examples:
EXAMPLE 1:  An aircraft has a pylon mounting on a wing as a location at which to install various equipment. An instance of the AttachmentSlotOnProduct entity data type identifies which attachment slot corresponds to the pylon.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#AttachmentSlotPlannedToRealized    [Status: created]
Class label: Attachment slot planned to realized
Description:
An AttachmentSlotPlannedToRealized is a relationship between a realized individual of an AttachmentSlot and a corresponding planned individual
Examples:
EXAMPLE 1:  WeMakeBigPlanes Limited builds aircraft serial number 2468 with a starboard engine attachment slot that was previously planned.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#AttachmentSlotVersion    [Status: created]
Class label: Attachment slot version
Description:
An AttachmentSlotVersion is a specialization of ProductVersion that identifies a version of AttachmentSlot
Notes:
NOTE 1:  This is a generic concept of version, in most situations it is possible and more specific to represent a version as AttachmentSlotDesign, AttachmentSlotAsPlanned or AttachmentSlotAsRealized.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#AxisPlacement    [Status: created]
Class label: Axis placement
Description:
An AxisPlacement is a specialization of DetailedGeometricModelElement that defines a right-handed, 2D or 3D, coordinate system. If the AxisPlacement belongs to a 3D geometric space, the third direction of the coordinate system is defined by the vector product of x-axis and y-axis. An AxisPlacement may be an AxisPlacement2d or an AxisPlacement3d
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#AxisPlacement2d    [Status: created]
Class label: Axis placement2d
Description:
An AxisPlacement2d is a specialization of AxisPlacement
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#AxisPlacement3d    [Status: created]
Class label: Axis placement3d
Description:
An AxisPlacement3d is a specialization of AxisPlacement
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#Breakdown    [Status: passed_review]
Class label: breakdown
Description:
set of breakdown elements chosen in order to partition a product in a desired way, together with the hierarchical relationships between these breakdown elements
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#BreakdownContext    [Status: ready_for_review]
Class label: breakdown context
Description:
link between a breakdown and a constituent breakdown element
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#BreakdownElement    [Status: passed_review]
Class label: breakdown element
Description:
partition representing a physical, functional, system, or zonal aspect of a product
Notes:
NOTE 1:  Breakdown elements are physical, functional, system, or zonal partitions of a breakdown.
NOTE 2:  A breakdown element is non-specific and allows for various types of breakdown.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#BreakdownElementDefinition    [Status: ready_for_review]
Class label: breakdown element definition
Description:
product view of a breakdown element version
Notes:
NOTE 1:  Breakdown element definition is non-specific and allows for various types of breakdown. The more specific breakdown element definitions are functional element definition, physical element definition, System element definition, and Zone element definition.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#BreakdownElementRealization    [Status: ready_for_review]
Class label: breakdown element realization
Description:
product definition element relationship between a breakdown element definition or a breakdown element usage and an item that realizes that element definition or usage
Examples:
EXAMPLE 1:  A pump realizes the 'provide fuel to engine' element in a functional breakdown for a ship.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#BreakdownElementUsage    [Status: ready_for_review]
Class label: breakdown element usage
Description:
view definition relationshipbetween a two breakdown elements
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#BreakdownElementVersion    [Status: passed_review]
Class label: breakdown element version
Class specification
Definition:
version of a breakdown element
Notes:
NOTE 1:  Breakdown element version is non-specific and allows for various types of product breakdown.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#BreakdownOf    [Status: ready_for_review]
Class label: breakdown of
Description:
link between a breakdown and a product which it provides a view of
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#BreakdownVersion    [Status: passed_review]
Class label: breakdown version
Class specification
Definition:
version of a breakdown
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#CartesianPoint    [Status: created]
Class label: Cartesian point
Description:
A CartesianPoint is a specialization of DetailedGeometricModelElement that defines a point by a list of up to 3 cartesian coordinates
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#CartesianTransformation2d    [Status: created]
Class label: Cartesian transformation2d
Description:
A CartesianTransformation2d is a specialization of DetailedGeometricModelElement. It is defined in a 2D geometric space by a 2*2 matrix and a cartesian point. Let be: M, the 2*2 multiplication matrix of the cartesian transformation; A, the point of the cartesian transformation; P, a point in the geometric space; Q, the result of the application of the transformation to P. The coordinates of Q shall be obtained by the formula: Q = M*P + A
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#CartesianTransformation3d    [Status: created]
Class label: Cartesian transformation3d
Description:
A CartesianTransformation3d is a specialization of DetailedGeometricModelElement that is a geometric transformation defined in a 3D geometric space by a 3*3 matrix and a cartesian point. Let be: M, the 3*3 multiplication matrix of the cartesian transformation; A, the point of the cartesian transformation; P, a point in the geometric space; Q, the result of the application of the transformation to P. The coordinates of Q shall be obtained by the formula: Q = M*P + A
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#CausalConsequence    [Status: created]
Class label: Causal consequence
Description:
A CausalConsequence is a specialization of ViewDefinitionRelationship that identifies secondary effects related to or resulting from a particular RiskConsequence
Notes:
NOTE 1:  A CausalConsequence is considered as an aftereffect of an immediate CausalConsequence.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#Certification    [Status: ready_for_review]
Class label: certificate
Class specification
Definition:
record created as a result of a successful certification providing proof of complying to or passing certain criteria
Notes:
NOTE 1:  The certificate can be attached to any aspect of product or activity data.
NOTE 2:  The certificate should record who provided the certification and when.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#CertificationAssignment    [Status: ready_for_review]
Class label: certification assignment
Description:
assignment of a certificate to something
Examples:
EXAMPLE 1:  'certified supplier' is an example of certification that may be granted to an organization by its contractor.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ClassificationRelationship    [Status: created]
Class label: Classification relationship
Description:
relationship between two instances of Classification
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#Collection    [Status: ready_for_review]
Class label: collection
Description:
product that specifies a set of data
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#CollectionAssignment    [Status: ready_for_review]
Class label: collection assignment
Description:
assignment of a collection view definition to something
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#CollectionMembership    [Status: ready_for_review]
Class label: collection membership
Description:
associationof a collection view definition with a member of the collection
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#CollectionRelationship    [Status: created]
Class label: Collection relationship
Description:
An CollectionRelationship is a specialization of ProductRelationship that represents an association between two Collection instances
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#CollectionVersion    [Status: ready_for_review]
Class label: collection version
Description:
version of a collection
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#CollectionVersionRelationship    [Status: created]
Class label: Collection version relationship
Description:
An CollectionVersionRelationship is a specialization of ProductVersionRelationship that represents an association between two CollectionVersion instances
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#CollectionVersionSequenceRelationship    [Status: created]
Class label: Collection version sequence relationship
Description:
An CollectionVersionSequenceRelationship is a specialization of CollectionVersionRelationship that represents a sequential association between two CollectionVersion instances
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#CollectionViewDefinition    [Status: ready_for_review]
Class label: collection view definition
Description:
product view of a collection version
Examples:
EXAMPLE 1:  A set of data relevant to the design of the SS Titanic and a set of data relevant to the as-built description of the SS Titanic might be represented as two instances of collection view definition.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ComponentUpperLevelIdentification    [Status: created]
Class label: Component upper level identification
Description:
A ComponentUpperLevelIdentification is a specialization of AssemblyViewRelationship. It identifies a component of an assembly with respect to an upper level in the assembly structure. The identified component is the version of product, indirectly referred to as the ProductOccurrenceDefinitionRelationship of the subAssemblyRelationship. The upper level assembly is the version of product, indirectly referred to as the ProductOccurrenceDefinitionRelationship of the upperAssemblyRelationship
Notes:
NOTE 1:  A ComponentUpperLevelIdentification does not add a component in an assembly, it provides a means to further characterize a component with respect to an upper level assembly.
Examples:
EXAMPLE 1:  A ComponentUpperLevelIdentification may be used to assign a property to a component that applies in the context of a particular upper level assembly.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#CompositionOfState    [Status: created]
Class label: Composition of state
Description:
A CompositionOfState is a specialization of state relationship and it relates the nature of states in relation to one another, where two or more State parts compose a whole State; and furthermore, whole states can become parts of yet another whole State
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#CompositionOfStateDefinition    [Status: created]
Class label: Composition of state definition
Description:
A CompositionOfStateDefinition is a specialization of StateDefinitionRelationship. It relates StateDefinition entities to one another, when two or more StateDefinition entities act as parts to compose a whole StateDefinition; and furthermore, whole StateDefinition entities can become parts of yet another whole StateDefinition
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ConcurrentElements    [Status: created]
Class label: Concurrent elements
Description:
A ConcurrentElements is a specialization of StructuredTaskElement that comprises a set of actions to be performed during the time required for the longest task. No specific order is required
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#Condition    [Status: ready_for_review]
Class label: condition
Class specification
Definition:
state of affairs that must be exist before a statement or relationship becomes valid
Notes:
NOTE 1:  The condition is a text based expression.
Examples:
EXAMPLE 1:  "If the engine has been running for 10000 hours then it requires a service"
Sources:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
  2. OED
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ConditionalEffectivity    [Status: created]
Class label: Conditional effectivity
Description:
A ConditionalEffectivity is a specialization of Effectivity for which the domain of applicability is defined by an explicit condition
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ConditionAssignment    [Status: ready_for_review]
Class label: condition assignment
Description:
assignment of a condition to something
Examples:
EXAMPLE 1:  Condition 29 applies to the relationship between a Saab 9.3 car and the activity of checking the oil level on that make of car.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ConditionEvaluation    [Status: created]
Class label: Condition evaluation
Description:
A ConditionEvaluation is a record of the evaluation of a Condition and the subsequent result
Examples:
EXAMPLE 1:  A Condition is "If the measured value of oil pressure from gauge 3 on a car is less than 2 bar then check the oil level" When the condition is evaluated it is recorded by an instance of ConditionEvaluation. The measured value of oil pressure from gauge 3 on car with VIN 12345678 is 1.9 bar. Therefore the result of the evaluated the condition is true.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ConditionEvaluationAssignment    [Status: ready_for_review]
Class label: condition evaluation assignment
Description:
assignment of a Condition evaluation to something
Examples:
EXAMPLE 1:  The ConditionEvaluation (instance 87) is assigned to the activity of checking the oil level on car VIN 12345678.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ConditionEvaluationParameter    [Status: created]
Class label: Condition evaluation parameter
Description:
A ConditionEvaluationParameter is an identification of the product or activity data used in the evaluation of the Condition identified by the ConditionEvaluation
Notes:
NOTE 1:  The product or activity data is defined in . The contents of this select type are defined in application modules that use this module.
Examples:
EXAMPLE 1:  The measured value of oil pressure from gauge 3 on car with VIN 12345678 (value = 1.9 bar).
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ConditionParameter    [Status: ready_for_review]
Class label: condition parameter
Description:
link between conditionand the product or activity data that specifies it
Examples:
EXAMPLE 1:  Oil pressure on gauge 3.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ConditionRelationship    [Status: ready_for_review]
Class label: condition relationship
Description:
relationship between two conditions
Examples:
EXAMPLE 1:  "If the engine has been running for 10000 hours AND the engine is fitted with a clog-up-quick Oil filter then change the oil filter" is an example of two conditions related by a logical AND.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ContextualItemShape    [Status: created]
Class label: Contextual item shape
Description:
A ContextualItemShape is a specialization of ItemShape that identifies the shape of a product version in the context of its use in another product version. The product version whose contextual shape is identified, is the product version associated with the ViewDefinitionRelationship of the ViewDefinitionUsage
Examples:
EXAMPLE 1:  Flexible part may have several shapes, each associated with a particular occurrence of the part in assemblies.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#Contract    [Status: ready_for_review]
Class label: contract
Description:
written or spoken agreement intended to be enforceable by law
Sources:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
  2. OED
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ContractAssignment    [Status: ready_for_review]
Class label: contract assignment
Description:
assignment of a contract to something
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ContractRelationship    [Status: created]
Class label: Contract relationship
Description:
relationship between two Contract instances
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#DatedEffectivity    [Status: ready_for_review]
Class label: dated effectivity
Description:
effectivity for which the domain of applicability is defined as an interval of time bounded by dates or events
Notes:
NOTE 1:  The interval may be open-ended.
Examples:
EXAMPLE 1:  Events may be used to bound a DatedEffectivity period, at planning phase.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#DateTimeAssignment    [Status: passed_review]
Class label: date time assignment
Description:
assignment of a date and time to something
Examples:
EXAMPLE 1:  A statement that an activity has started on a given date.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#DecisionPoint    [Status: created]
Class label: Decision point
Description:
A DecisionPoint is a type of StructuredTaskElement. It requires a decision that determines which further TaskElement is to be followed
Notes:
NOTE 1:  The condition on which the decision is based optionally allows a further TaskElement to be invoked to provide the basis for the decision.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#DecreasingResourceEvent    [Status: created]
Class label: Decreasing resource event
Description:
A DecreasingResourceEvent is a specialization of ResourceEvent that decreases the balance of a managed resource
Examples:
EXAMPLE 1:  Filling a requisition reduces an inventory.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#DefinedStateRelationship    [Status: created]
Class label: Defined state relationship
Description:
relationship that links a StateAssertion to a StateAssessment
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#Descriptor    [Status: ready_for_review]
Class label: descriptor
Class specification
Definition:
an element or term that serves to describe, identify, or index something.
Sources:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
  2. OED
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#DescriptorRelationship    [Status: created]
Class label: descriptor relationship
Description:
relationship between two descriptors
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#DetailedGeometricModelElement    [Status: created]
Class label: Detailed geometric model element
Description:
A DetailedGeometricModelElement is a specialization of RepresentationItem. It identifies a geometric construct. Only non abstract specializations of the DetailedGeometricModelElement entity data type can be instantiated
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#DigitalDocumentDefinition    [Status: ready_for_review]
Class label: digital document definition
Description:
document definition of a collection of files that are archived on optical, magnetic, or electronic media, or a combination thereof
Notes:
NOTE 1:  A digital document definition may consist of one or many component digital files.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#DigitalFile    [Status: ready_for_review]
Class label: digital file
Description:
file that contains computer interpretable data and is stored on an electronic device or on optical, magnetic, or electronic media, or a combination thereof
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#DirectedActivity    [Status: passed_review]
Class label: directed activity
Description:
activity that is governed by a work order
Notes:
NOTE 1:  A directed activity is an activity planned to be undertaken in the future.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#Direction    [Status: created]
Class label: Direction
Description:
A Direction is a specialization of DetailedGeometricModelElement that defines a 2 or 3 dimensional vector
Notes:
NOTE 1:  A Direction is not located in a geometric space but is used in the definition of geometric entities like AxisPlacement.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#DistributionByValue    [Status: created]
Class label: Distribution by value
Description:
A DistributionByValue is a specialization of ProbabilityDistribution that explicitly lists pairs of random variable values and function values
Notes:
NOTE 1:  DistributionByValue is used where there is no named distribution which can be used to identify the distribution, for example, when the distribution is derived from observation.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#Document    [Status: ready_for_review]
Class label: document
Description:
product used to specify data that is under configuration change management
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#DocumentAssignment    [Status: ready_for_review]
Class label: document assignment
Description:
assignment of a document to something
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#DocumentDefinition    [Status: ready_for_review]
Class label: document definition
Description:
product view of a document version in a particular format
Notes:
NOTE 1:  Each document definition is a digital document definition or a physical document definition.
NOTE 2:  A DocumentVersion may have more than one representation.
NOTE 3:  Aspects of the representation may not be known at the time the identification is established.
Examples:
EXAMPLE 1:  A version of a logical document, which contains a shape model, may be represented in the native formats of different CAD systems.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#DocumentDefinitionRelationship    [Status: created]
Class label: document definition relationship
Description:
relationship between two instances of DocumentDefinition
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#DocumentVersion    [Status: ready_for_review]
Class label: document version
Description:
version of a document
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#Effectivity    [Status: ready_for_review]
Class label: effectivity
Description:
specification of a domain of applicability
Notes:
NOTE 1:  Instances of effectivity may be applied to any kind of product or product data.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#EffectivityAssignment    [Status: ready_for_review]
Class label: effectivity assignment
Description:
assignment of an effectivity to something
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#EffectivityRelationship    [Status: created]
Class label: Effectivity relationship
Description:
relationship between two instances of Effectivity. The meaning of the relationship is represented with the relationType attribute
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ElementConstraint    [Status: created]
Class label: Element constraint
Description:
An ElementConstraint is a specialization of TaskElementRelationship that signifies a constraint between TaskElements. The constraint may only apply within the context of a TaskMethod or TaskElement, specified as the context
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#EndTask    [Status: created]
Class label: End task
Description:
An EndTask is a type of TaskElement. It signifies a point at which to end the task
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#Envelope    [Status: ready_for_review]
Class label: envelope
Description:
historical record of the transmission of a message
Notes:
NOTE 1:  Envelope is used to record the audit data for sending and acknowledging a message. Because it is an historical record, each envelope is only used once and so is not versioned.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#EnvelopeRelationship    [Status: created]
Class label: Envelope relationship
Description:
relationship between two envelopes
Notes:
NOTE 1:  The most obvious use of the association is to link an Envelope to its acknowledgements.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#EnvironmentAssignment    [Status: ready_for_review]
Class label: environment assignment
Description:
assignment of an Environment definition view to something
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#EnvironmentDefinition    [Status: created]
Class label: Environment definition
Description:
An EnvironmentDefinition is a specialization of Product that is used to identify the definition of typical environment in which a product is to be, has been or is planned to be deployed in, operated in, or supported in
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#EnvironmentDefinitionVersion    [Status: created]
Class label: Environment definition version
Description:
A EnvironmentDefinitionVersion is a specialization of ProductVersion that identifies a particular version of an EnvironmentDefinition
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#EnvironmentDefinitionView    [Status: created]
Class label: Environment definition view
Description:
A EnvironmentDefinitionView is a specialization of ProductViewDefinition that provides a view of a version of an environment definition relevant for one or more application domains. This view collects the characteristics that define an environment
Notes:
NOTE 1:  The characteristics include the resources available, the locations in which the product is to operate as well as climatic conditions such temperature ranges.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#EnvironmentViewDefinitionRelationship    [Status: created]
Class label: Environment view definition relationship
Description:
A EnvironmentViewDefinitionRelationship is a specialization of ViewDefinitionRelationship that represents an association between two EnvironmentDefinitionView instances
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#Evidence    [Status: ready_for_review]
Class label: evidence
Description:
collection of items used together to provide a single piece of evidence within a Validation or ]verification http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#Verification]
Examples:
EXAMPLE 1:  For example a document and its approval by a customer may be used together to provide evidence of customer acceptance
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ExitLoop    [Status: created]
Class label: Exit loop
Description:
An ExitLoop is a type of StructuredTaskElement. It signifies a point at which to exit from a loop
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ExpandedUncertainty    [Status: created]
Class label: Expanded uncertainty
Description:
An ExpandedUncertainty is a specialization of StandardUncertainty that specifies the factor of an uncertainty
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ExperienceGained    [Status: created]
Class label: Experience gained
Description:
An ExperienceGained is a relationship between an ExperienceInstance and a person or organization
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ExperienceInstance    [Status: created]
Class label: Experience instance
Description:
An ExperienceInstance is a particular episode of contact with and/or observation of facts or events which contributes to the accumulation of knowledge or skill. The nature, duration and worth of the ExperienceInstance can be described using assigned properties or by referring to activities or tasks
Examples:
EXAMPLE 1:  100 flying hours in a Tornado jet.
EXAMPLE 2:  2 years work on same type of milling machine.
EXAMPLE 3:  5 years as Workshop Manager.
EXAMPLE 4:  Changing the exhaust system on a car.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ExperienceType    [Status: ready_for_review]
Class label: experience type
Description:
category of experience
Examples:
EXAMPLE 1:  flying
EXAMPLE 2:  mechanical design
EXAMPLE 3:  welding
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ExperienceTypeRelationship    [Status: created]
Class label: Experience type relationship
Description:
relationship used to relate a compound experience to its component experiences
Examples:
EXAMPLE 1:  Ten years programming experience made up of five years C++ programming experience and five years Java programming experience.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ExternalAnalysisModel    [Status: ready_for_review]
Class label: external analysis model
Description:
analysis model whose content is provided in an external file
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ExternalPropertyDefinition    [Status: passed_review]
Class label: property
Description:
identification of the definition of a property
Notes:
NOTE 1:  A property may reflect physics or arbitrary user defined measurements
Examples:
EXAMPLE 1:  The property definition Colour is a definition of red, green and blue values.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ExternalTypeQualifier    [Status: ready_for_review]
Class label: external type qualifier
Description:
reference to the specification of the type of datum that is defined externally to an exchange file
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ExternalUnit    [Status: passed_review]
Class label: unit
Class specification
Definition:
measurable quantity, dimension, or magnitude adopted as a basis or standard of measurement for other quantities of the same kind and in terms of which their magnitude is calculated or expressed
Examples:
EXAMPLE 1:  Ohm is the unit of electrical resistance
Source:
  1. Oxford English Dictionary
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#File    [Status: ready_for_review]
Class label: file
Class specification
Definition:
a collection of data or programs stored under a single identifying name using digital or other media
Sources:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
  2. OED
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#FileRelationship    [Status: created]
Class label: File relationship
Description:
relationship between two instances of File
Examples:
EXAMPLE 1:  A service manual may contain graphics for explanatory reasons. In this case, the File instances that contain the graphics are referenced as related from the File instance that contains the body of the service manual with DocumentDefinitionRelationship 'reference'.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#FunctionalBreakdown    [Status: passed_review]
Class label: functional breakdown
Description:
breakdown comprising functional elements
Notes:
NOTE 1:  The functional breakdown is a partitioning of a product into a set of related functional elements so as to form explicit, parent-child views.
Examples:
EXAMPLE 1:  A functional breakdown provides a decomposition of an aircraft in terms of high-level processes such as "flight" and "taxiing" all the way down to low-level functions such as "detect onboard fuel level", "move tail rudder", and "provide standard tow attachment point".
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#FunctionalBreakdownContext    [Status: ready_for_review]
Class label: functional breakdown context
Description:
breakdown context that links a functional element to a functional breakdown of which includes the functional element as a member
Examples:
EXAMPLE 1:  A function 'provide load lifting capability' is a member of the functional breakdown of a helicopter.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#FunctionalBreakdownVersion    [Status: ready_for_review]
Class label: functional breakdown version
Description:
version of a functional breakdown
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#FunctionalElement    [Status: passed_review]
Class label: functional element
Description:
breakdown element that represents a function
Notes:
NOTE 1:  Functional elements are partitions of a functional breakdown
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#FunctionalElementDefinition    [Status: ready_for_review]
Class label: functional element definition
Description:
breakdown element definition of a functional element version
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#FunctionalElementUsage    [Status: ready_for_review]
Class label: functional element usage
Description:
breakdown element usage that links a functional element to a constituent functional element
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#FunctionalElementVersion    [Status: ready_for_review]
Class label: functional element version
Description:
version of a functional element
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#GeometricOperatorTransformation    [Status: created]
Class label: Geometric operator transformation
Description:
A GeometricOperatorTransformation is a specialization of GeometricPlacementOperation
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#GeometricPlacement    [Status: created]
Class label: Geometric placement
Description:
A GeometricPlacement is a specialization of GeometricPlacementOperation
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#GeometricPlacementOperation    [Status: created]
Class label: Geometric placement operation
Description:
A GeometricPlacementOperation is a specialization of DetailedGeometricModelElement. A GeometricPlacementOperation may be a GeometricPlacement or a GeometricOperatorTransformation
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#GlobalLocationRepresentation    [Status: created]
Class label: Global location representation
Description:
A GlobalLocationRepresentation is a type of LocationRepresentation specified using geographic means in the global system and values, which could be physical or political geographic values
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#Hardcopy    [Status: ready_for_review]
Class label: hardcopy
Class specification
Definition:
file that is stored on non-digital media
Examples:
EXAMPLE 1:  An actual stack of paper consisting of one or more sheets, on which some product data is written, printed or plotted.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#HierarchicalInterfaceConnection    [Status: created]
Class label: Hierarchical interface connection
Description:
A HierarchicalInterfaceConnection is a specialization of InterfaceConnection that provides an interconnection between components at different levels in an assembly. Each connection point in the assembly is represented by a InterfaceConnectorOccurrence
Examples:
EXAMPLE 1:  An appliance such as a television has a power lead and attached plug. The plug and power lead could be represented as an assembly of parts such as the plug pins and wires. Each connection point of the pins and wires in the assembly is represented by a InterfaceConnectorOccurrence and an instance of the HierarchicalInterfaceConnection entity data type identifies the connection of the pins (the parts) to the plug (the assembly) in the assembly.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#Identifier    [Status: ready_for_review]
Class label: identifier
Class specification
Definition:
name or code that is used to label something and to refer to that thing
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#IdentifierRelationship    [Status: created]
Class label: identifier relationship
Description:
relationship between a pair of Identifications
Notes:
NOTE 1:  This relationship may be classified in other modules to provide more specific meanings.
Examples:
EXAMPLE 1:  ISO is an acronym for "International Standard Organization". When ISO and "International Standard Organization" are used as identifiers for the ISO organization, they may be related to indicate that ISO is the acronym for "International Standard Organization".
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#IncreasingResourceEvent    [Status: created]
Class label: Increasing resource event
Description:
A IncreasingResourceEvent is a type of ResourceEvent that increases the balance of a managed resource
Examples:
EXAMPLE 1:  Purchasing new stock increases an inventory.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#InformationRight    [Status: created]
Class label: Information right
Description:
An InformationRight is a definition of what may or may not be done with information in the sense of legal rights and obligations
Notes:
NOTE 1:  This a general purpose definition of a right that may be applied to many things. The usage of the InformationRight is represented by InformationUsageRight. The application of that right to information is represented by InformationUsageRightAssignment.
Examples:
EXAMPLE 1:  Copyright is an InformationRight.
EXAMPLE 2:  For the purposes of developing a new system, details of government furnished equipment may be made available to a particular project team. The team may copy and use the information internally, but may not pass it on, either to a third part, or to another team, and must destroy the information at the end of the contract.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#InformationUsageRight    [Status: created]
Class label: Information usage right
Description:
An InformationUsageRight is an application an InformationRight to a particular usage context
Notes:
NOTE 1:  InformationUsageRight provides a mechanism for recording significant rights within a product database. The legal significance of the presence or absence of a right is outside the scope of this part of ISO 10303
NOTE 2:  One view of the distinction between an InformationRight and an InformationUsageRight is that the InformationRight represents a standard clause in a contract, whereas an InformationUsageRight represents the fact that the clause is used in a particular contract.
NOTE 3:  The Approval of an InformationUsageRight carries the meaning that the right is granted to all information items in the relevant context, as opposed to the approval of an InformationUsageRightAssignment which is limited to particular items.
NOTE 4:  The context for the usage can be defined through the contract which defines the right, the organization that grants the right, the person or organization which is granted the right, and any dates such as the starting or ending dates for the right. The meaning of each association is identified through the roles of the assignments, and these are defined through reference-data.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#InformationUsageRightAssignment    [Status: ready_for_review]
Class label: information usage right assignment
Description:
assignment of an Information usage right to something
Notes:
NOTE 1:  If an approval is applied to this entity, it carries the meaning that the particular set of items is approved for the given usage. This approval generally indicates that the approval is exceptional, for example, where the information belongs to another project, and that project agrees to share some particular items of information. There is a further implication that the set of entities should not be changed once the approval is given.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#InformationUsageRightRelationship    [Status: created]
Class label: Information usage right relationship
Description:
relationship of one InformationUsageRight to another
Examples:
EXAMPLE 1:  Where one InformationUsageRight supercedes another, then the original right is pointed to by the relating attribute, its replacement by the related attribute, and the relationType attribute takes the value "supercedes".
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#InterfaceConnection    [Status: created]
Class label: Interface connection
Description:
A InterfaceConnection is an interconnection between a connected pair of InterfaceConnectorOccurrences. Each InterfaceConnectorOccurrence represents the place where a product used in an assembly can interact with other products in the assembly
Examples:
EXAMPLE 1:  An appliance such as a television has a power lead and attached plug. The plug and power lead could be represented as an assembly of parts such as the plug pins and wires. Each connection point of the pins and wires in the assembly is represented by a InterfaceConnectorOccurrence and an instance of the InterfaceConnection entity data type identifies the connection of the pins to the wires in the assembly.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#InterfaceConnector    [Status: created]
Class label: Interface connector
Description:
An InterfaceConnector is a specialization of Product that identifies a part of a product with which one or more other products or the environment interacts
Notes:
NOTE 1:  This is sometimes referred to as a "port".
Examples:
EXAMPLE 1:  A computer has a socket to which to connect a network cable. An instance of the InterfaceConnector entity data type identifies the role of the socket in the interface and is the subject of a specification that defines the necessary geometrical and electrical attributes to ensure a functioning interface between the computer and network hardware.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#InterfaceConnectorAsPlanned    [Status: created]
Class label: Interface connector as planned
Description:
An InterfaceConnectorAsPlanned is a specialization of InterfaceConnectorVersion that identifies an individual that is the subject of a plan to realize an InterfaceConnector
Examples:
EXAMPLE 1:  Company Acme Limited is planning to produce an aircraft with serial number 1234 next month. This aircraft has connectors on each engine for fuel pipes. The company wishes to plan when each connector will be realized and then identify a date on which an inspector can test all the realized connectors.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#InterfaceConnectorAsRealized    [Status: created]
Class label: Interface connector as realized
Description:
An InterfaceConnectorAsRealized is a specialization of InterfaceConnectorVersion that identifies an individual that is a realized InterfaceConnector
Examples:
EXAMPLE 1:  Company WeFlySafest Corporation owns and operates an aircraft with serial number 1234. When landing at Heathrow airport, the pilot reports a loss of fuel pressure on engine number 4 with serial number A9876 and recommends that an inspector tests the realized connector on the engine.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#InterfaceConnectorDefinition    [Status: created]
Class label: Interface connector definition
Description:
An InterfaceConnectorDefinition is a specialization of ProductViewDefinition that identifies a view of an InterfaceConnector
Examples:
EXAMPLE 1:  A reliability engineer assesses the likely failure modes of design version 3.8 for the connector between a brake unit and the hydraulic control system. The engineer generates a set of data that is a specific view of the connector. An instance of the InterfaceConnectorDefinition entity data type collects these data together.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#InterfaceConnectorDesign    [Status: created]
Class label: Interface connector design
Description:
An InterfaceConnectorDesign is a specialization of InterfaceConnectorVersion that identifies a design version of an InterfaceConnector
Examples:
EXAMPLE 1:  BuildAWidget Incorporated creates design version 2.10 for an electrical supply connector.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#InterfaceConnectorDesignToPlanned    [Status: created]
Class label: Interface connector design to planned
Description:
An InterfaceConnectorDesignToPlanned is a relationship between a design version of an InterfaceConnector and a planned individual that is to conform to the design
Examples:
EXAMPLE 1:  BuildAWidget Incorporated plans production of pump serial number 30301 with an electrical supply connector that is to conform to design version 2.10.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#InterfaceConnectorDesignToRealized    [Status: created]
Class label: Interface connector design to realized
Description:
An InterfaceConnectorDesignToRealized is a relationship between a design version of an InterfaceConnector and a realized individual that conforms to the design
Examples:
EXAMPLE 1:  BuildAWidget Incorporated builds pump serial number 30301 with an electrical supply connector that conforms to design version 2.11.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#InterfaceConnectorOccurrence    [Status: created]
Class label: Interface connector occurrence
Description:
A InterfaceConnectorOccurrence is an occurrence of a InterfaceConnectorDefinition. The InterfaceConnectorOccurrence represents the place where a product used in an assembly can interact with other products in the assembly. The interaction is represented by a InterfaceConnection
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#InterfaceConnectorPlannedToRealized    [Status: created]
Class label: Interface connector planned to realized
Description:
An InterfaceConnectorPlannedToRealized is a relationship between a realized individual of an InterfaceConnector and a corresponding planned individual
Examples:
EXAMPLE 1:  BuildAWidget Incorporated builds pump serial number 30302 with an electrical supply connector that was previously planned.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#InterfaceConnectorVersion    [Status: created]
Class label: Interface connector version
Description:
An InterfaceConnectorVersion is a specialization of ProductVersion that identifies a version of an InterfaceConnector
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#InterfaceDefinitionConnection    [Status: created]
Class label: Interface definition connection
Description:
A InterfaceDefinitionConnection is an interconnection between a connected pair of InterfaceConnectorDefinitions or, if the point of interconnection is not specified, the interconnection between a pair of views ( ProductViewDefinitions) on products
Examples:
EXAMPLE 1:  A socket in the wall provides access to the domestic electricity supply. An appliance such as a television has a power lead and plug that fits into the socket. An instance of the InterfaceDefinitionConnection entity data type identifies this fitting of the plug into the socket.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#InterfaceDefinitionFor    [Status: created]
Class label: Interface definition for
Description:
An InterfaceDefinitionFor is a relationship between an InterfaceSpecification and an item that conforms to the specification
Examples:
EXAMPLE 1:  The infrared transmitter in a television remote control conforms to the specification that has the identifier 2345/XYZ/001. An instance of the InterfaceDefinitionFor entity data type is necessary to identify this relationship.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#InterfaceSpecification    [Status: created]
Class label: Interface specification
Description:
An InterfaceSpecification is a specialization of Product that provides a definition of necessary attributes for one or more items that participate in an interface
Examples:
EXAMPLE 1:  BSI develops a standard for connecting domestic electrical equipment to the electricity supply.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#InterfaceSpecificationDefinition    [Status: created]
Class label: Interface specification definition
Description:
An InterfaceSpecificationDefinition is a specialization of ProductViewDefinition that provides a view of an InterfaceSpecification
Examples:
EXAMPLE 1:  When developing a BSI standard for connecting domestic electrical equipment to the electricity supply, collected comments from experts form a new view on a version of the standard.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#InterfaceSpecificationVersion    [Status: created]
Class label: Interface specification version
Description:
An InterfaceSpecificationVersion is a specialization of ProductVersion that identifies a version of an InterfaceSpecification
Examples:
EXAMPLE 1:  In 1999, BSI issues a new version of a standard for connecting domestic electrical equipment to the electricity supply.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#InZone    [Status: created]
Class label: In zone
Description:
An InZone is a relationship between a ZoneElement and an item that exists within the zone
Examples:
EXAMPLE 1:  A pump is in the starboard engine room of a ship.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ItemAssumed    [Status: created]
Class label: Item assumed
Description:
An ItemAssumed is an association between an Assumption and the item that is being assumed
Examples:
EXAMPLE 1:  A facility is assumed to exist at a given location. The facility shall be represented by a ResourceItemAssignment, the location by a Location, and the existence of the facility at the location, by a LocationAssignment assigning a location to the resource.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ItemDesignAssociation    [Status: created]
Class label: Item design association
Description:
An ItemDesignAssociation is the association of a ProductConfiguration with a ProductViewDefinition or a ProductVersion. It specifies the design that corresponds to the ProductConfiguration. If the design is a ProductViewDefinition, the ItemDesignAssociation represents the statement that, in the considered definition context, the product version, that is, the ProductViewDefinition is a valid way to implement the ProductConfiguration. If the design is a ProductVersion, the ItemDesignAssociation represents the statement that, in all definition contexts, the ProductVersion is a valid way to implement the ProductConfiguration
Notes:
NOTE 1:  The association might not be valid for other versions of the product.
NOTE 2:  This association might not be valid in all definition contexts of the product version.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ItemShape    [Status: created]
Class label: Item shape
Description:
An ItemShape is the shape of a
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ItemShapeObject    [Status: created]
Class label: Item shape object
Description:
AnItemShapeObject is an abstract generalization of instances that represents the shape of a ShapeableItemSelect
Notes:
NOTE 1:  Only non-abstract specializations of the ItemShapeObject can be instantiated.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ItemUsageEffectivity    [Status: created]
Class label: Item usage effectivity
Description:
An ItemUsageEffectivity is an effectivity domain that constrains the use of a product with or within another product, in the context of a ProductConfiguration. The effectivityDomain attribute identifies a domain of effectivity. The itemUsageRelationship attribute identifies a relationship which characterizes the use of the product with or within another product. The resolvedConfiguration attribute identifies an association between a ProductConfiguration and a product that implements it. This attribute establishes the context in which the itemUsageRelationship is considered and constrained. When the effectivity domain is a range of serial numbers, the serial numbers considered are those of the ProductConfiguration. When the effectivity domain is defined using a production lot number, the production lot considered is one of the ProductConfiguration. When the effectivity domain is an interval of time, the interval of time considered is related to the production of the ProductConfiguration
Notes:
NOTE 1:  When no effectivity constraint is applied to a ViewDefinitionUsage, the validity or applicability status of this ViewDefinitionUsage is unknown.
Examples:
EXAMPLE 1:  This relationship may be an assembly-component relationship or a make-from relationship.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#Justification    [Status: ready_for_review]
Class label: justification
Description:
the identification and description of the reasons for something
Examples:
EXAMPLE 1:  A justification may be provided for a product design. Similarly, a justification may be provided for why an activity is needed or was undertaken.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#JustificationAssignment    [Status: ready_for_review]
Class label: justification assignment
Description:
assignment of a justification to something
Examples:
EXAMPLE 1:  The item can be an activity or a product design.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#JustificationRelationship    [Status: created]
Class label: Justification relationship
Description:
relationship between two Justifications
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#JustificationSupportAssignment    [Status: ready_for_review]
Class label: justification support assignment
Description:
assignment of something to a justification
Examples:
EXAMPLE 1:  The support item can be the results from an analysis, a report, or professional judgment.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#Language    [Status: passed_review]
Class label: language
Description:
a language in which human readable text is written
Notes:
NOTE 1:  The identification of a language by its code as defined in ISO 639-2 and possibly its country code as specified in ISO 3166-1. The language is used in an exchange as defined using BCP47.
Examples:
EXAMPLE 1:  en.
EXAMPLE 2:  en-gb.
EXAMPLE 3:  sv.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#LifeCycleStage    [Status: passed_review]
Class label: life-cycle phase
Description:
period in a lifecycle
Notes:
NOTE 1:  The combination of an application domain and a life-cycle stage defines a view of a product.
Examples:
EXAMPLE 1:  The design phase.
EXAMPLE 2:  The manufacturing phase.
EXAMPLE 3:  The support phase.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#Location    [Status: ready_for_review]
Class label: location
Description:
place or position where an activity or event can occur or something can exist
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#LocationAssignment    [Status: ready_for_review]
Class label: location assignment
Description:
assignment of a location to something
Notes:
NOTE 1:  A LocationAssignment is a relationship between a product, event, or person and a location. There may be distinct assignment for each qualification. for example planned, scheduled or actual. Each assignment may have a start and end date or time. A location may have multiple assignments
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#LocationRelationship    [Status: ready_for_review]
Class label: location relationship
Description:
relationship between two locations
Examples:
EXAMPLE 1:  Location B, which is in reference to location A or Location B (UK), which is a refinement of Location A (Europe).
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#LocationRepresentation    [Status: created]
Class label: Location representation
Description:
A LocationRepresentation is a means of representing a location
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#LoopingElement    [Status: created]
Class label: Looping element
Description:
A LoopingElement is a specialization of TaskElement. It invokes a specified number of repetitions of a further TaskElement
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#LotEffectivity    [Status: ready_for_review]
Class label: lot effectivity
Description:
effectivity for which the domain of applicability is defined as a given batch of items
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#MakeFromRelationship    [Status: created]
Class label: Make from relationship
Description:
A MakeFromRelationship is a specialization of ViewDefinitionUsage established between two instances of PartViewDefinition. It specifies that, in the context of the definition of the relating part version, the relating part version is considered as resulting from the manufacturing transformation of the related part version
Notes:
NOTE 1:  The characterization of the process of transformation from the related part version to the relating part version it out of the scope of this application module.
NOTE 2:  The related part version may identify a raw material or a semi-finished part.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ManagedResource    [Status: created]
Class label: Managed resource
Description:
A ManagedResource is a representation of a resource that is provided with resource management capabilities. The role of a managed resource is determined by classification
Examples:
EXAMPLE 1:  A managed resource can be classified as "Stock line".
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ManagedResourceRelationship    [Status: created]
Class label: Managed resource relationship
Description:
relationship between two managed resources. The meaning of the relationship is determined by classification
Examples:
EXAMPLE 1:  A managed resource relationship can be classified as "Alternative" or "Preferred".
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#Market    [Status: created]
Class label: Market
Description:
A Market is the identification of a marketing segment for products
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#MeasureQualification    [Status: created]
Class label: Measure qualification
Description:
A MeasureQualification is a means to provide information about measurements in which there is an associated uncertainty. The uncertainty may be specified as precision, qualitative uncertainty, or expanded uncertainty, and the type of the related datum shall be included. The uncertainty is defined in clause 2 of "The Guide to the Expression of Uncertainty in Measurement"
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#Message    [Status: ready_for_review]
Class label: message
Description:
collection of information, brought together by an originator (the message definer) for some particular purpose, generally the fulfillment of a process
Notes:
NOTE 1:  A message is an historical record, intended to be sent using an envelope and in consequence, is not versioned.
NOTE 2:  The same message can be sent several times using different envelope. Once it has been sent once, it cannot be further changed. However it should not remain unsent, since that is to confuse its functions and therefore its meaning with other entities such as one of the types of document.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#MessageRelationship    [Status: created]
Class label: Message relationship
Description:
relationship between two related messages. The meaning of the association depends on MessageRelationship.role
Examples:
EXAMPLE 1:  If Message=2 replaces Message=1, then MessageRelationship.related points to Message=2 and MessageRelationship.relating points to Message=1 with MessageRelationship.role="replaces".
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#NextAssemblyViewUsage    [Status: ready_for_review]
Class label: next assembly usage
Description:
assembly component relationship between two product views where one is the parent assembly and the other is a component of that assembly
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#NumericalContext    [Status: ready_for_review]
Class label: numerical context
Description:
circumstances in which a numerical value is recorded and in which that numerical value can be fully understood
Notes:
NOTE 1:  A numerical context may represent the organization, technique, or system which creates the numerical value.
Sources:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
  2. OED
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#NumericalValue    [Status: passed_review]
Class label: numerical value
Description:
value with unit where the value part is expressed numerically
Examples:
EXAMPLE 1:  10 kilogram
Source:
  1. ISO 10303-239:2012 Product life cycle support
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#Observation    [Status: ready_for_review]
Class label: observation
Description:
historical record of something that has occurred during the life of a product or its support environment
Notes:
NOTE 1:  The use of observation is restricted to observations not directly represented in the data model, and it should not be used where some other reporting data structure is defined.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ObservationAssignment    [Status: ready_for_review]
Class label: observation assignment
Description:
assignment of an observation to something
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ObservationConsequence    [Status: created]
Class label: Observation consequence
Description:
An ObservationConsequence is an association of an observation to the consequences that follow from it, where those consequences are in the form of a WorkRequest
Notes:
NOTE 1:  One of the uses of ObservationConsequence is to close one of the feedback loops from the use of a product to requests for its enhancements.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ObservationRelationship    [Status: created]
Class label: Observation relationship
Description:
relationship between two observations. The nature of this relationship is identified by the role. Where there is a structural relationship between Observation, the semantics of the structure are identified by the classification of the ObservationRelationship against reference-data
Examples:
EXAMPLE 1:  The Observation of a persistent fault is composed of a series of Observation of occurrences of the same fault. That is, ObservationRelationship.related points to the composite Observation, while ObservationRelationship.relating points to one actual Observation of the occurrence. The ObservationRelationship.role of the relationship is "observed instance", while it is classified as "is composed of". In this example, the component Observation will apply to ProductAsRealized and the consequence will be to rectify the individual faults, while the composite Observation will apply to a ProductVersion and the consequence will be a design change.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ObservedEnvironment    [Status: created]
Class label: Observed environment
Description:
An ObservedEnvironment is a specialization of Product that represents a record of observations about the environment in which a product is or has been operating
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ObservedEnvironmentAssignment    [Status: ready_for_review]
Class label: observed environment assignment
Description:
assignment of an Observed environment view to something
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ObservedEnvironmentToDefinition    [Status: created]
Class label: Observed environment to definition
Description:
An ObservedEnvironmentToDefinition is a relationship between a record of a set of observations about an environment, represented by an ObservedEnvironment, and a typical environment, represented by an EnvironmentDefinition. The typical environment is the expected environment about which observations have been made
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ObservedEnvironmentToDefinitionVersion    [Status: created]
Class label: Observed environment to definition version
Description:
An ObservedEnvironmentToDefinitionVersion is a relationship between a version of the record of a set of observations about an environment, represented by an ObservedEnvironmentVersion, and a version of the typical environment, represented by EnvironmentDefinitionVersion. The typical environment is the expected environment about which observations have been made
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ObservedEnvironmentToDefinitionView    [Status: created]
Class label: Observed environment to definition view
Description:
An ObservedEnvironmentToDefinitionView is a relationship between a view of the record of a set of observations about an environment, represented by an ObservedEnvironmentView, and a view of the typical environment, represented by EnvironmentDefinitionView. The typical environment is the expected environment about which observations have been made
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ObservedEnvironmentVersion    [Status: created]
Class label: Observed environment version
Description:
An ObservedEnvironmentVersion is a specialization of ProductVersion that identifies a particular version of an ObservedEnvironment
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ObservedEnvironmentView    [Status: created]
Class label: Observed environment view
Description:
An ObservedEnvironmentView is a specialization of ProductViewDefinition that provides a view of a version of an observed environment relevant for one or more application domains. This view collects the characteristics of the observations on the environment
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ObservedEnvironmentViewDefinitionRelationship    [Status: created]
Class label: Observed environment view definition relationship
Description:
An ObservedEnvironmentViewDefinitionRelationship is a specialization of ViewDefinitionRelationship that represents an association between two ObservedEnvironmentView instances
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#Organization    [Status: ready_for_review]
Class label: organization
Class specification
Definition:
structured body of persons with a particular purpose
Sources:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
  2. OED
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#OrganizationalLocationIdentification    [Status: created]
Class label: Organizational location identification
Description:
An OrganizationalLocationIdentification is location that is defined by an identification which is specific in an organization context
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#OrganizationBasedLocationRepresentation    [Status: created]
Class label: Organization based location representation
Description:
An OrganizationBasedLocationRepresentation is a specialization of LocationRepresentation that specifies a location in the context of an organization
Examples:
EXAMPLE 1:  The location "Room 99" in "The Administration Building" of a particular university might be represented using one instance of OrganizationBasedLocationRepresentation with two instances of OrganizationalLocationIdentification and one instance of Organization.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#OrganizationOrganizationTypeRelationship    [Status: created]
Class label: Organization organization type relationship
Description:
relationship between an Organization organization and an OrganizationType
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#OrganizationOrPersonInOrganizationAssignment    [Status: ready_for_review]
Class label: organization or person in organization assignment
Description:
assignment of an organization or a person in organization to something
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#OrganizationRelationship    [Status: created]
Class label: Organization relationship
Description:
relationship between two instances of Organization
Examples:
EXAMPLE 1:  A team belongs to a department which itself belongs to a company. Such an organizational structure can be described up using instances of OrganizationRelationship.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#OrganizationType    [Status: created]
Class label: Organization type
Description:
An OrganizationType is a recognized kind of Organization
Examples:
EXAMPLE 1:  change control board
EXAMPLE 2:  department
EXAMPLE 3:  legal entity
EXAMPLE 4:  manufacturing organization
EXAMPLE 5:  sales organization
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#OrStateCauseEffectDefinition    [Status: created]
Class label: Or state cause effect definition
Description:
An OrStateCauseEffectDefinition is a specialization of StateCauseEffectDefinition. It relates one or more StateDefinition entities that are causes to a StateDefinition that is the effect. At least one cause must exist prior to the effect
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ParameterizedDistribution    [Status: created]
Class label: Parameterized distribution
Description:
A ParameterizedDistribution is a specialization of ProbabilityDistribution that is used to link a named probability distribution to the parameters that define it
Notes:
NOTE 1:  The ParameterizedDistribution of this entity is used to discriminate between alternative parameterizations of the same distribution.
NOTE 2:  To calculate a value using a ParameterizedDistribution it is necessary to know the general distribution function, the value of the distribution function parameters, and the specific random variable value for which the probability evaluation is required. The Probability Distribution module does not define the formula for the distribution function, and it is assumed that this is defined externally, either through reference information or via a "formula" module. This entity provides the distribution function parameters. The value of the random variable for which the probability is calculated is provided by the ProbabilityDerivationParameter in the Probability module (see note 2).
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#Part    [Status: passed_review]
Class label: part specification
Class alternative label: part specification
Description:
specification for either a physical product or for a non-countable material
Notes:
NOTE 1:  A part specification may specify a single piece part, an assembly of arbitrary complexity, a raw material, or a tool.
NOTE 2:  A part specification may have zero or more versions.
NOTE 3:  A part specification is collector of definitional information of all versions of a physical product.
NOTE 4:  A part specification is not an actual physical object that is or was existing in the real world.
NOTE 5:  A part specification defines the fit, form, or function of a planned or actual physical object or data set.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#PartialDocumentAssignment    [Status: ready_for_review]
Class label: partial document assignment
Description:
document assignment that identifies a specific portion of the contents of a document and assigns that portion to something
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#PartVersion    [Status: passed_review]
Class label: part specification version
Description:
version of a part specification
Notes:
NOTE 1:  A part specification version typically specifies a part that is functionally and physically interchangeable with the other versions of the same part specification.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#PartViewDefinition    [Status: ready_for_review]
Class label: part view definition
Description:
product view of a part specification version
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#Person    [Status: ready_for_review]
Class label: person
Class specification
Definition:
individual human being
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#PersonInOrganization    [Status: ready_for_review]
Class label: person in organization
Description:
role of person in an organization
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#PersonOrOrganizationOrPersonInOrganizationInPosition    [Status: created]
Class label: Person or organization or person in organization in position
Description:
A PersonOrOrganizationOrPersonInOrganizationInPosition is a Person, Organization, or PersonInOrganization that holds a Position. A person may hold more than one position within an organization or organizations. A position in an organization can be held by more than one person or organization
Examples:
EXAMPLE 1:  A person can hold two positions in an organization: Production Manager and Safety Officer.
EXAMPLE 2:  Two people can hold the same position in a job-share scheme.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#PersonOrOrganizationOrPersonInOrganizationInPositionRelationship    [Status: created]
Class label: Person or organization or person in organization in position relationship
Description:
relationship between one Organization, Person, or PersonInOrganization and another. Examples of the relationship are
Notes:
NOTE 1:  The meaning of the relationship is determined by classification
Examples:
EXAMPLE 1:  job-share
EXAMPLE 2:  successor
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#PhysicalBreakdown    [Status: passed_review]
Class label: physical breakdown
Description:
breakdown comprising physical elements
Notes:
NOTE 1:  The physical breakdown is a partitioning of a product into a set of related physical partitions so as to form explicit, parent-child views.
Examples:
EXAMPLE 1:  A physical breakdown of a motor car into body, roof, bonnet, bumpers etc.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#PhysicalBreakdownContext    [Status: ready_for_review]
Class label: Physical breakdown context
Description:
breakdown context that links a physical element and a physical breakdown of which it is a member
Examples:
EXAMPLE 1:  A wheel is a member of the physical breakdown of an automobile.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#PhysicalBreakdownVersion    [Status: ready_for_review]
Class label: physical breakdown version
Description:
version of a physical breakdown
Examples:
EXAMPLE 1:  An engineer modifies the current physical breakdown for an aircraft on the basis of a tail re-design.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#PhysicalDocumentDefinition    [Status: ready_for_review]
Class label: physical document definition
Description:
document definition of a hardcopy document
Notes:
NOTE 1:  A physical document definition may consist of one or many component hardcopy files.
Examples:
EXAMPLE 1:  Paper plots of technical drawings, micro fiche, or paper documents such as calculations or test reports are examples of physical document definitions.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#PhysicalElement    [Status: passed_review]
Class label: physical element
Description:
breakdown element that represents something physical
Notes:
NOTE 1:  Physical elements are partitions of a physical breakdown
Examples:
EXAMPLE 1:  Body, roof, bonnet, bumpers etc. are examples of physical elements of the physical breakdown of an motor car.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#PhysicalElementDefinition    [Status: ready_for_review]
Class label: physical element definition
Description:
breakdown element definition of a Physical element version
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#PhysicalElementUsage    [Status: ready_for_review]
Class label: physical element usage
Description:
breakdown element usage that links two physical elements
Examples:
EXAMPLE 1:  In a physical breakdown, the aircraft (parent) might include (as children) a fuselage, wings, tail and undercarriage.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#PhysicalElementVersion    [Status: created]
Class label: Physical element version
Description:
A PhysicalElementVersion is a specialization of BreakdownElementVersion that identifies a version of a PhysicalElement
Examples:
EXAMPLE 1:  An engineer changes the details describing the undercarriage that is an element in a physical breakdown of an aircraft.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#PlcsThing    [Status: ready_for_review]
Class label: plcs thing
Description:
uppermost class in the hierarchy of PLCS classes
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#Position    [Status: created]
Class label: Position
Description:
A Position is a function or job performed by a person. It defines responsibilities and activities. A position that is not fulfilled by a person is a vacancy
Examples:
EXAMPLE 1:  Company Director
EXAMPLE 2:  Service Engineer
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#PositionAssignment    [Status: ready_for_review]
Class label: Position assignment
Description:
assignment of a Position to something
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#PositionGroup    [Status: created]
Class label: Position group
Description:
A PositionGroup is a group for collecting people in their positions to cooperate in an assignment
Examples:
EXAMPLE 1:  People representing utility companies who cooperate with each other to coordinate road works.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#PositionGroupAssignment    [Status: ready_for_review]
Class label: position group assignment
Description:
assignment of a Position group to something
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#PositionGroupRelationship    [Status: created]
Class label: Position group relationship
Description:
relationship that specifies the participation of a position in a group
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#PositionPositionTypeAssignment    [Status: ready_for_review]
Class label: position position type assignment
Description:
assignment of a Position type to a Position
Notes:
NOTE 1:  It allows many Positions to be described by many Position types.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#PositionRelationship    [Status: created]
Class label: Position relationship
Description:
relationship between Positions. Examples of relationships between Positions are
Notes:
NOTE 1:  The meaning of the relationship is determined by classification.
Examples:
EXAMPLE 1:  Superceded by
EXAMPLE 2:  Superior / Subordinate
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#PositionType    [Status: created]
Class label: Position type
Description:
A PositionType is a recognized kind of position
Examples:
EXAMPLE 1:  Programmer
EXAMPLE 2:  Aircraft engineering technician propulsion
EXAMPLE 3:  Chief Executive Officer
EXAMPLE 4:  Manager
EXAMPLE 5:  Service engineer
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#PositionTypeAssignment    [Status: ready_for_review]
Class label: Position type assignment
Description:
assignment of a Position type to something
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#PrecisionQualifier    [Status: created]
Class label: Precision qualifier
Description:
A PrecisionQualifier is a specification of the number of significant digits in the representation of a value. PrecisionQualifier shall be interpreted in accordance with PrecisionQualifier in part 45 of this standard
Notes:
NOTE 1:  The precision is defined in clause 2 of "The Guide to the Expression of Uncertainty in Measurement".
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#Probability    [Status: ready_for_review]
Class label: probability
Description:
property value that that represents the likelihood of something
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ProbabilityByName    [Status: created]
Class label: Probability by name
Description:
A ProbabilityByName is a specialization of Probability whose value belongs to a one of a set of named classes, rather than by assigning a specific numerical value, which may not be available
Examples:
EXAMPLE 1:  A safety assessment methodology classes the probability an accident as "very unlikely", "unlikely", "significantly likely" and "almost certain". Any process that has a "very likely" or "almost certain" chance of causing serious injury is shut down.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ProbabilityDerivationParameter    [Status: created]
Class label: Probability derivation parameter
Description:
A ProbabilityDerivationParameter is a specialization of NumericalItemWithGlobalUnit that is used by a ProbabilityDerived in a particular role in order to calculate the particular probability
Notes:
NOTE 1:  The role name is given by the 'name' attribute inherited from RepresentationItem, and the set of such names and their interpretation is defined through reference-data.
NOTE 2:  The value attribute, which holds the parameter value, is inherited from the parent generalization.
Examples:
EXAMPLE 1:  In a coin tossing trial, the probability calculated is that of getting more than 6 heads in ten tosses. The parameter with the role "minimum number of heads" will have the value "6"
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ProbabilityDerived    [Status: created]
Class label: Probability derived
Description:
A ProbabilityDerived is a specialization of ProbabilityNumeric that associates a particular value of ProbabilityNumeric with the source from which the value derived together with any parameters used to get the particular value
Notes:
NOTE 1:  Where the probability derived from a probability distribution, the parameters of ProbabilityDerived are those needed to get a single value from the distribution, and not those which characterize the distribution. For example, in the case of coin tossing, the distribution is a Binomial distribution, with parameters of 'probability for a single toss', and 'number of tosses', whereas the parameter for the ProbabilityDerived will be the 'number of heads obtained'.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ProbabilityDistribution    [Status: created]
Class label: Probability distribution
Description:
A ProbabilityDistribution is a specialization of ProbabilityGenerator that is a probability distribution
Notes:
NOTE 1:  For a full understanding of probability distribution and the terms used, a textbook on probability theory should be consulted.
NOTE 2:  This entity describes a particular probability distribution, rather than the general type of distribution. For example, in coin tossing experiment, the number of heads that may occur is given by a binomial distribution - that is, a type of distribution, and outside the scope of this module. This module provides the description of the distribution of a particular experiment, say, 10 tosses of a particular coin. The actual probability of an outcome, say 6 heads in 10 tosses, is recorded using the probability module.
NOTE 3:  The attributes 'name', 'id' and 'description' are inherited from the parent generalization. Representation. The name provides a cue to the particular source of the distribution, such as "A fair coin tossed 10 times", rather than the type of distribution (in this case Binomial) which is given by the ProbabilityDistribution.distributionName attribute.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ProbabilityDistributionParameter    [Status: created]
Class label: Probability distribution parameter
Description:
A ProbabilityDistributionParameter is a specialization of NumericalItemWithGlobalUnit that is one of the set of values that characterizes a probability distribution
Notes:
NOTE 1:  For many common distributions, the mean and the variance are sufficient to characterize a distribution, and the parameter list may be empty.
NOTE 2:  ProbabilityDistributionParameter inherits the 'name' attribute from its parent generalization, and this is used to identify the name of the parameter within the particular parameterization. The value attribute is also inherited.
Examples:
EXAMPLE 1:  The Normal (or Gaussian) distribution has, in the standard parameterization, two parameters: the mean and the variance
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ProbabilityFunctionValue    [Status: created]
Class label: Probability function value
Description:
A ProbabilityFunctionValue is a specialization of NumericalItemWithGlobalUnit that is the value of the probability function at the given random variable value
Notes:
NOTE 1:  The value is an inherited attribute. It is not in general a probability value. In some functions for continuous distributions, the probability that the random variable lies between two values is the integral of the function of that range.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ProbabilityGenerator    [Status: created]
Class label: Probability generator
Description:
A ProbabilityGenerator is a specialization of Representation. It is a source from the ProbabilityDerived is derived. The ProbabilityDerivationParameters are applied to the ProbabilityGenerator to get the particular derived value
Notes:
NOTE 1:  A ProbabilityGenerator will generally be either a ProbabilityDistribution or a function of some statistics.
Examples:
EXAMPLE 1:  A probability of "0.67" is derived from a Normal (or Gaussian) distribution using the parameter "plus or minus '1.0' standard deviations from the mean"
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ProbabilityNamedValue    [Status: created]
Class label: Probability named value
Description:
A ProbabilityNamedValue is a specialization of RepresentationItem that is used to hold the name of the probability value
Notes:
NOTE 1:  The value attribute is the description inherited from the parent generalization. In general, this value will be one of an enumeration of possible values defined through reference-data.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ProbabilityNumeric    [Status: ready_for_review]
Class label: numerical probability
Description:
probability that is expressed as a numerical value
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ProbabilityNumericValue    [Status: created]
Class label: Probability numeric value
Description:
A ProbabilityNumericValue is a specialization of NumericalItemWithGlobalUnit providing a numeric representation of a probability
Notes:
NOTE 1:  The value attribute is inherited from the parent generalization.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#Product    [Status: passed_review]
Class label: product
Class specification
Definition:
something tangible or intangible that is a result of a deliberate process
Notes:
NOTE 1:  A product can be a physical object as well as the specification for producing such a physical object.
NOTE 2:  Products are typically given identifiers and tracked.
Examples:
EXAMPLE 1:  The SS Titanic.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ProductAsIndividual    [Status: ready_for_review]
Class label: product as individual
Description:
product that specifies an individual artefact that has been made or is planned to be made
Notes:
NOTE 1:  It is likely, but not essential, that the artefact, was or will be made from a product design which will be related to the product as individual by [product design to individual http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ProductDesignToIndividual.
NOTE 2:  Many physical products may be produced from a given design. A single product may lead to many products as individual.
NOTE 3:  products as individual versions of product as individual are used to represent whether an individual artefact has yet to be made or has been made. The product as individual version specialization Product as planned is used to represent the revision of an individual artefact that has yet to be made and the specialization product as realized is used to represent the revision of an individual artefact that has been made.
NOTE 4:  Where physical products are being represented, the product as individual represents the physical or planned physical realization of a product.
Examples:
EXAMPLE 1:  The design of a personal computer is represented by a Product.
EXAMPLE 2:  The personal computer that has been ordered, allocated a serial number for manufacturing planning, but not yet manufactured, is represented by a ProductAsIndividual and an associated revision represented by ProductAsPlanned.
EXAMPLE 3:  The personal computer with a serial number on a persons desk is represented by a ProductAsIndividual and an associated revision represented by ProductAsRealized.
EXAMPLE 4:  HMS Daring is the first of a new class of ships known as Type 45 Destroyers. It is due to enter service in two years time. The Type 45 ship design that applies to HMS Daring is represented by a Product; The ship HMS Daring is represented by a ProductAsIndividual. This identifies the planned ship, and when built, the actual ship; The planned revision of the future ship HMS Daring is represented by a ProductAsPlanned which is related back to the ProductAsIndividual; When built, the first revision the actual ship, HMS Daring will be represented by a ProductAsRealized which is related back to the ProductAsIndividual.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ProductAsIndividualEffectivity    [Status: ready_for_review]
Class label: product as individual effectivity
Description:
effectivity for which the domain of applicability is defined as a set of instances of products as individuals
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ProductAsIndividualVersion    [Status: ready_for_review]
Class label: product as individual version
Description:
version of a product as individual
Examples:
EXAMPLE 1:  The car on my drive is represented by a product as individual. The current configuration status of the car can be represented by a product as realized related to the product as individual. If a safety modification is made to the car resulting in a new configuration status of the car, then this may be represented by a new product as realized.
EXAMPLE 2:  The HMS Daring is the first of a new class of ships known as Type 45 Destroyers and is due to be built in two years' time. The version of the generic Type 45 ship design that applies to HMS Daring is represented by a product version; The ship HMS Daring is represented by a product as individual. This identifies the planned ship, and when built, the actual ship; The planned revision of the future ship HMS Daring is represented by a Product as planned related back to the product as individual; When built, the first revision the actual ship, HMS Daring will be represented by a product as realized related back to the product as individual.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ProductAsIndividualView    [Status: ready_for_review]
Class label: product as individual view
Description:
product view of a product as individual
Notes:
NOTE 1:  The product as individual view supports the representation of different views of a product as individual for different purposes. Multiple views of the same product as individual are represented by different instances of ProductAsIndividualView for the same product as individual version
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ProductAsPlanned    [Status: created]
Class label: Product as planned
Description:
A ProductAsPlanned is a specialization of ProductAsIndividualVersion that identifies a revision of an individual artefact that has yet to be made
Notes:
NOTE 1:  If the planned artefact ( ProductAsPlanned) is subsequently made into an actual artefact ( ProductAsRealized) then they are related by the ProductPlannedToRealized relationship.
NOTE 2:  It may be planned to make the artefact from of a version of a product design ( ProductVersion). If this is the case, then the relationship between the artefact ( ProductAsPlanned) and the design ( ProductVersion) is represented by ProductDesignVersionToIndividual.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ProductAsRealized    [Status: ready_for_review]
Class label: product as realized
Description:
version of a product as individual that has been made
Notes:
NOTE 1:  A product as realized's properties can only be known by observation or by derivation from observations.
NOTE 2:  The artefact may have been made from a version of a product (ie a product version). If this is the case, then the relationship between the product as realized and the (product version http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ProductVersion] is represented by product design version to individual.
NOTE 3:  The artefact may have been planned and represented by Product as planned. In which case, the actual product as realized is related to the Product as planned by the Product planned to realized association.
NOTE 4:  Where physical products are being represented, the product as realized represents the physical product - something that can be touched.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ProductBasedLocationIdentification    [Status: created]
Class label: Product based location identification
Description:
A ProductBasedLocationIdentification is a specialization of LocationRepresentation that specifies a location in the context of a product
Examples:
EXAMPLE 1:  Seat number M in the Aircraft.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ProductConcept    [Status: created]
Class label: Product concept
Description:
A ProductConcept is the identification of a set of similar products that were, are or will be proposed to customers
Notes:
NOTE 1:  A product concept may be characterized by a set of product features identified by the customers or derived from customers' needs.
NOTE 2:  The entity data type ProductConcept enables to represent customer-oriented identification of products that are to be delivered to customers, while the entity data type Product enables to identify and to track the history of items that are designed and manufactured, as a tangible solution, or component of the solution, for a product concept.
NOTE 3:  Depending on the kind of industry and products, a product concept might be offered to the customers in one or many different configurations.
NOTE 4:  The definition of product concepts is driven by market and customer requirements and forecasting. A ProductConcept often corresponds to the highest level item(s) manufactured by an organization for customers.
Examples:
EXAMPLE 1:  In an organization which manufactures cars and engines for cars, the car models will be represented by instances of ProductConcept.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ProductConfiguration    [Status: created]
Class label: Product configuration
Description:
A ProductConfiguration is the identification of a ProductConcept as a configuration
Notes:
NOTE 1:  A ProductConfiguration may identify a variation of a ProductConcept, an entire ProductConcept, or some portion thereof.
NOTE 2:  A ProductConfiguration can be established prior to the existence of a corresponding product.
NOTE 3:  The entity ProductConfiguration corresponds to the concept of configuration item defined, in some configuration management standards, as an item subject to configuration management.
Examples:
EXAMPLE 1:  A ProductConfiguration may represent a component of a contracted product, onto which severe safety rules apply and for which configuration management is therefore rigorously applied.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ProductConfigurationHierarchicalRelationship    [Status: created]
Class label: Product configuration hierarchical relationship
Description:
A ProductConfigurationHierarchicalRelationship is a specialization of ProductConfigurationRelationship that is used to represent a hierarchical relationship between a parent ProductConfiguration and a child ProductConfiguration
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ProductConfigurationRelationship    [Status: created]
Class label: Product configuration relationship
Description:
relationship between a pair of ProductConfigurations
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ProductConfigurationRevisionSequence    [Status: created]
Class label: Product configuration revision sequence
Description:
A ProductConfigurationRevisionSequence is a specialization of ProductConfigurationRelationship that is used to relate a previous version (predecessor) of a ProductConfiguration to the version that replaces it (successor)
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ProductDefinitionElementRelationship    [Status: ready_for_review]
Class label: product definition element relationship
Description:
relationship between a breakdown element usage or a breakdown element definition and a view definition usage or a resource item or a product view or a Product group or an Interface connector occurrence or an assembly component relationship
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ProductDesignToIndividual    [Status: ready_for_review]
Class label: product design to individual
Description:
association between a product and a product as individual
Notes:
NOTE 1:  A product design to individual associates a product design, represented by product, with a product that is planned to be made or has been made from the design, represented by product as individual.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ProductDesignVersionToIndividual    [Status: ready_for_review]
Class label: product design version to individual
Description:
association between a product version or Product configuration and a Product as planned or product as realized
Notes:
NOTE 1:  A product design version to individual associates a version of a product design, represented by product version or Product configuration, and the product that is planned to be made (Product as planned) or has been made (product as realized) from the design.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ProductDesignViewToIndividual    [Status: created]
Class label: Product design view to individual
Description:
A ProductDesignViewToIndividual is a relationship between a product design, represented by ProductViewDefinition. or ProductConfiguration, and a view of the product that is planned to be made or has been made ( ProductAsIndividualView) from the design
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ProductGroup    [Status: created]
Class label: Product group
Description:
A ProductGroup is an identification of a set of ProductConcepts, Products, ProductGroups, ProductVersions or ProductAsIndividuals that have been grouped together
Examples:
EXAMPLE 1:  All the aircraft sold to BigPlanes airways.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ProductGroupMembership    [Status: created]
Class label: Product group membership
Description:
A ProductGroupMembership is an identification of an instance of an entity defined in the type that belongs to a ProductGroup
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ProductGroupRelationship    [Status: created]
Class label: Product group relationship
Description:
relationship between two ProductGroups. is used to specify the meaning or type of the relationship
Notes:
NOTE 1:  A subset is a common type of relationship. It indicates that one ProductGroup is a subset of another.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ProductInAttachmentSlot    [Status: created]
Class label: Product in attachment slot
Description:
A ProductInAttachmentSlot is a specialization of ViewDefinitionUsage that is a relationship between an AttachmentSlot and a ProductViewDefinition of a Product that is designed to be attached to the attachment slot
Examples:
EXAMPLE 1:  A long-range fuel tank is designed to be attached to an aircraft in an attachment slot that corresponds to a pylon mounting on a wing.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ProductPlannedToRealized    [Status: created]
Class label: Product planned to realized
Description:
A ProductPlannedToRealized is a relationship that establishes that a revision of a planned artefact represented by ProductAsPlanned has been realized as a revision of an actual artefact ProductAsRealized
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ProductRelationship    [Status: created]
Class label: Product relationship
Description:
relationship between two Products
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ProductVersion    [Status: passed_review]
Class label: product version
Class specification
Definition:
version of a product
Notes:
NOTE 1:  The set of all instances of product version of the same product represents the history of the product.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ProductVersionRelationship    [Status: created]
Class label: Product version relationship
Description:
relationship between two versions of Product
Notes:
NOTE 1:  A relationship may exist between ProductVersion of different Product or between different versions of the same Product.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ProductViewDefinition    [Status: passed_review]
Class label: product view
Description:
collector of information for a product version relevant from the perspective of a particular point of view defined by an application domain and a life-cycle phase
Examples:
EXAMPLE 1:  The electrical product view and mechanical product view provide the electrical and mechanical aspects of a product specification.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#Project    [Status: created]
Class label: project
Description:
identified program of work
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ProjectAssignment    [Status: ready_for_review]
Class label: Project assignment
Description:
assignment of a project to something
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ProjectRelationship    [Status: created]
Class label: Project relationship
Description:
relationship between two instances of Project with an identification and a description of their relationship
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#PromissoryAssemblyViewUsage    [Status: created]
Class label: Promissory usage
Description:
A PromissoryUsage is a specialization of AssemblyViewRelationship. It establishes a relationship between an assembly and a component, regardless of the number of intermediate levels between them, which may be established with instances of NextAssemblyUsage
Notes:
NOTE 1:  A PromissoryUsage may be used when the product structure is not completely defined, to capture the intent that the constituent will be used in that assembly.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#PropertyDefinitionAssignment    [Status: ready_for_review]
Class label: property definition assignment
Description:
assignment of a property to something
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#PropertyDefinitionRelationship    [Status: created]
Class label: property definition relationship
Description:
relationship between two properties
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#PropertyValue    [Status: passed_review]
Class label: property value
Description:
quantification or qualification of a property
Examples:
EXAMPLE 1:  A length property quantified as "10 metres".
Source:
  1. ISO 10303-239:2012 Product life cycle support
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#PropertyValueAssignment    [Status: passed_review]
Class label: property value assignment
Description:
assignment of a property value to something
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#PropertyValueRelationship    [Status: passed_review]
Class label: property value relationship
Description:
relationship between two property values
Examples:
EXAMPLE 1:  An association between a value for a length property expressed in metres and an equivalent value for the same property expressed in yards.
EXAMPLE 2:  10 metres is equivalent to 10.936133 yards
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ProxyRelationship    [Status: created]
Class label: Proxy relationship
Description:
relationship between a pair of Proxies
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#QualificationAssignment    [Status: ready_for_review]
Class label: qualification assignment
Description:
assignment of a qualification type to something
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#QualificationType    [Status: ready_for_review]
Class label: qualification type
Description:
category of qualification
Examples:
EXAMPLE 1:  A Military rank such as Colonel, or Captain
EXAMPLE 2:  A driving licence.
EXAMPLE 3:  A qualification for executing the Ground Running task for RB211 engines.
EXAMPLE 4:  Educational qualification such as GCSE, A level, Degree, Ordinary National Certificate, Higher National Certificate, City and Guilds, or GNVQ.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#QualificationTypeRelationship    [Status: created]
Class label: Qualification type relationship
Description:
relationship between two QualificationTypes
Examples:
EXAMPLE 1:  Qualification X is a prerequisite for qualification Y.
EXAMPLE 2:  Qualification X is equivalent to qualification Y.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#QualitativeUncertainty    [Status: created]
Class label: Qualitative uncertainty
Description:
A QualitativeUncertainty is a specialization of UncertaintyQualifier. The uncertainty is defined in clause 2 of "The Guide to the Expression of Uncertainty in Measurement"
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#RandomVariable    [Status: created]
Class label: Random variable
Description:
A RandomVariable is a specialization of NumericalItemWithGlobalUnit that is the value of a random variable
Notes:
NOTE 1:  The value attribute is inherited from the parent generalization.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#RegionalCoordinate    [Status: created]
Class label: Regional coordinate
Description:
A RegionalCoordinate is a location that is specified relative to a Regional location system
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#RegionalGridLocationRepresentation    [Status: created]
Class label: Regional grid location representation
Description:
A RegionalGridLocationRepresentation is a specialization of LocationRepresentation that specifies a reference grid system
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#RelatedConditionParameter    [Status: created]
Class label: Related condition parameter
Description:
A RelatedConditionParameter is a relationship between a ConditionParameter and a ConditionEvaluationParameter. This relationship is used to record the relationship between the parameters used to define a condition and the parameters used to evaluate it
Examples:
EXAMPLE 1:  The value of oil pressure (1.9 bar) used in ConditionEvaluation (instance 87) was a measured value of the parameter used to define condition 29 (oil pressure on gauge 3).
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#RelatedConsequence    [Status: created]
Class label: Related consequence
Description:
A RelatedConsequence is a specialization of ViewDefinitionRelationship describing the expected consequences of a specific perception of a risk
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#RelationshipObject    [Status: passed_review]
Class label: relationship
Description:
dependency between two objects
Notes:
NOTE 1:  The objects being related are normally, but not always, of the same type or subtype.
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#RepeatCount    [Status: created]
Class label: Repeat count
Description:
A RepeatCount is a type of LoopingElement. It invokes a specified number of repetitions of the LoopingElement TaskElement inherited from the LoopingElement parent generalization
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#RepeatUntil    [Status: created]
Class label: Repeat until
Description:
A RepeatUntil is a type of LoopingElement. It invokes repetitions of a further TaskElement and is repeated until the specified condition is satisfied. The element being repeated shall be executed at least once and the condition tested after the first execution
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#RepeatWhile    [Status: created]
Class label: Repeat while
Description:
A RepeatWhile is a type of LoopingElement. It invokes repetitions of a further TaskElement and is repeated while the specified condition is satisfied. The test condition shall be evaluated prior to invoking the method and may result in the LoopingElement not being executed at all
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#RequiredResource    [Status: ready_for_review]
Class label: required resource
Description:
an identified need for a resource
Examples:
EXAMPLE 1:  required resource by resource item and fixed required resource are examples of required resources
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#RequiredResourceAssignment    [Status: ready_for_review]
Class label: required resource assignment
Description:
assignment of a required resource to something
Notes:
NOTE 1:  An association between a required resource and actions that are needed prior to its usage.
Examples:
EXAMPLE 1:  A resource required by the activity "12" needs to be calibrated prior to usage. The calibration activity "21" is associated with the same required resource.
EXAMPLE 2:  A resource required by the task "123" needs to be disposed after its usage. This disposal task "456" is associated with the same required resource.
EXAMPLE 3:  The assignment can be classified as "required by".
EXAMPLE 4:  task, task step, activity, activity method, organization are examples of entities to which the resource requirement statement could be related.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#RequiredResourceByResourceItem    [Status: ready_for_review]
Class label: required resource by resource item
Description:
required resource that is satisfied by a resource item
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#RequiredResourceRelationship    [Status: ready_for_review]
Class label: required resource relationship
Description:
relationship between two required resources
Examples:
EXAMPLE 1:  required resource alternative relationship and required resource supersede relationship are examples of required resource relationships.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#RequiredResourceRequirement    [Status: created]
Class label: Required resource requirement
Description:
A RequiredResourceRequirement is an association of a required resource with one or more requirement version entities that fulfil the resource requirement
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#Requirement    [Status: ready_for_review]
Class label: requirement
Description:
product that specifies a requirement
Notes:
NOTE 1:  Systems engineering tools and organizations may use differing identification mechanisms. Multiple identifiers may be assigned to a requirement using identifier.
NOTE 2:  The term requirement is used here in the sense that term is used in systems engineering and similar industrial domains.
NOTE 3:  There may be many versions of a requirement (requirement versions). There may also be more than one domain-specific view of a given requirement version (using requirement view definition). The requirement entity is simply a placeholder for holding a unique requirement. Most associations and properties are defined at the RequirementViewDefinition level - that is in the context of a domain.
Examples:
EXAMPLE 1:  A requirement may be identified as "NOx emissions requirement", and uniquely identified as "Req2".
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#RequirementAssignment    [Status: ready_for_review]
Class label: requirement assignment
Description:
assignment of a (requirement view http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#RequirementViewDefinition] to something
Examples:
EXAMPLE 1:  A requirement "the vehicle shall have a maximum power output of at least 150BHP" could be assigned to the data types which are used to represent the vehicle's engine.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#RequirementCollectionRelationship    [Status: created]
Class label: Requirement collection relationship
Description:
A RequirementCollectionRelationship is a specialization of ViewDefinitionRelationship that is used to relate a parent (collection) requirement to its member requirements. This provides a method for collecting together a set of requirements and treating them as a single requirement, whilst still being able to refer to individual requirements
Notes:
NOTE 1:  The inherited " ViewDefinitionRelationship" and " ViewDefinitionRelationship" attributes have been renamed for purposes of clarity.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#RequirementSatisfiedBy    [Status: created]
Class label: requirement satisfied by
Description:
A RequirementSatisfiedBy is a relationship between an item and a requirement, asserting that the item satisfies the identified requirement
Examples:
EXAMPLE 1:  A data type used to represent a vehicle's engine with a power output of 160BHP could be asserted to satisfy a requirement "the vehicle shall have a maximum power output of at least 150BHP".
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#RequirementSource    [Status: created]
Class label: Requirement source
Description:
A RequirementSource is a relationship between a requirement (via the RequirementViewDefinition entity) and the data types representing the source of the requirement
Examples:
EXAMPLE 1:  The source of the requirement "the vehicle shall have a maximum power output of at least 150BHP" could be a document representing the findings of a market survey of sports car buyers.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#RequirementVersion    [Status: ready_for_review]
Class label: requirement version
Description:
product version of a requirement
Notes:
NOTE 1:  In this case, the word "version" implies "revision" - that is a particular release of a requirement.
Examples:
EXAMPLE 1:  A particular requirement might have versions 1.0, 1.1, 1.2, and 2.0.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#RequirementVersionRelationship    [Status: created]
Class label: Requirement version relationship
Description:
A RequirementVersionRelationship is a specialization of ProductVersionRelationship that is used to relate a previous version (predecessor) of a requirement to the version that replaces it (successor)
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#RequirementViewDefinition    [Status: ready_for_review]
Class label: requirement view definition
Description:
product view of a requirement version
Notes:
NOTE 1:  A requirement view definition collects requirement data for specific engineering purposes. Some requirements in a requirement view definition might impact on different disciplines. Multiple requirement view definitions may present different views of a given requirement for each discipline.
Examples:
EXAMPLE 1:  An engineer may have responsibility for collecting all requirements associated with the cooling of an engine - covering engine block, tubing, water pump, electric fan.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#RequirementViewDefinitionRelationship    [Status: created]
Class label: Requirement view definition relationship
Description:
A RequirementViewDefinitionRelationship is a specialization of ViewDefinitionRelationship. A RequirementViewDefinitionRelationship is the association between one RequirementViewDefinition and another
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ResourceAsRealized    [Status: ready_for_review]
Class label: resource as realized
Description:
record of a resource that has been used or consumed
Notes:
NOTE 1:  A resource as realized may be "used" or "consumed".
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ResourceAsRealizedAssignment    [Status: ready_for_review]
Class label: resource as realized assignment
Description:
assignment of a resource as realized to something
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ResourceAsRealizedRelationship    [Status: created]
Class label: Resource as realized relationship
Description:
relationship between the record of used or consumed resources and the corresponding statement of RequiredResource
Notes:
NOTE 1:  A resource used or consumed can be recorded without having a corresponding resource requirement statement.
Examples:
EXAMPLE 1:  "Alternative" and "Corresponding" are examples of classifications of resource as realized relationship.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ResourceEvent    [Status: created]
Class label: Resource event
Description:
A ResourceEvent is an event or action that affects the balance or availability of a managed resource. The role of a resource event is determined by classification
Examples:
EXAMPLE 1:  A resource event can be classified as "Planned" or "Actual".
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ResourceEventCorrespondenceRelationship    [Status: created]
Class label: Resource event correspondence relationship
Description:
relationship between a resource event and a corresponding statement of RequiredResource. The meaning of the relationship is determined by classification
Notes:
NOTE 1:  A resource event can be planned or recorded without having a corresponding resource requirement statement.
Examples:
EXAMPLE 1:  A resource event correspondence relationship can be classified as "Designated for".
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ResourceEventRelationship    [Status: created]
Class label: Resource event relationship
Description:
relationship between two Resource events
Examples:
EXAMPLE 1:  A managed resource relationship can be classified as "realized by" or "replaces".
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ResourceGroupRelationship    [Status: created]
Class label: Resource group relationship
Description:
A ResourceGroupRelationship is a specialization of ResourceItemRelationship that specifies the means to associate two resource items that are part of a resource group. The meaning of the entity is determined by classification
Examples:
EXAMPLE 1:  The relationship between a facility and compressed air could be classified as "Provides".
EXAMPLE 2:  The relationship between a tool set and a mallet could be classified as "Contains".
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ResourceItem    [Status: ready_for_review]
Class label: resource item
Description:
stock or supply of materials, assets, or labour
Examples:
EXAMPLE 1:  A resource item may be classified as "Facility", "Replaceable unit", or "Package".
Sources:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
  2. OED
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ResourceItemAssignment    [Status: ready_for_review]
Class label: Resource item assignment
Description:
assignment of a resource item to something
Examples:
EXAMPLE 1:  The assignment can be classified as "applicable to" or "acquired for".
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ResourceItemRealization    [Status: ready_for_review]
Class label: resource item realization
Description:
specification of how a resource item may be associated with an item that serves as the resource
Examples:
EXAMPLE 1:  A product may serve as a resource.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ResourceItemRelationship    [Status: ready_for_review]
Class label: resource item relationship
Description:
relationship between two resource items
Notes:
NOTE 1:  A resource item relationship specifies of how a resource item may be associated with another resource item.
NOTE 2:  The role of the resource item relationship is indicated by classification.
Examples:
EXAMPLE 1:  The resource item relationship between an artefact and its packaging might be classified as "Preferred".
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#Risk    [Status: created]
Class label: Risk
Description:
A Risk is a specialization of Product that is the potential for realization of unwanted negative consequences of an event
Notes:
NOTE 1:  A risk can also have a possible positive outcome. In such cases it is often referred to as an opportunity or reward.
NOTE 2:  ISO GUIDE 73 defines "risk" as the combination of the probability of an event and its consequence. In some situations, risk is a deviation from the expected.
NOTE 3:  ISO/IEC Guide 51:1999 defines risk as the combination of the probability of occurrence of harm and the severity of that harm.
NOTE 4:  In the safety field, risk management is focused on prevention and mitigation of harm. ISO/IEC Guide 51:1999 should be used for safety aspects.
Examples:
EXAMPLE 1:  'Fly-by-wire', the form-fit-function replacement of mechanical devices with a combination of electrical, hydraulic, and pneumatic units.
EXAMPLE 2:  'Privacy' and 'security' are examples of Risk for the telecommunications industry.
EXAMPLE 3:  'Line shutdown' is an example of Risk in the context of a manufacturing system's reliability.
EXAMPLE 4:  'Transportation jam-up', 'customer anger', 'collateral damage', and 'greater susceptibility to interruption of supply during crises' are all examples of Risk.
EXAMPLE 5:  Timing such as 'premature rejection' and 'premature commitment' are other examples of Risk.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#RiskConsequence    [Status: created]
Class label: Risk consequence
Description:
A RiskConsequence is a specialization of ProductViewDefinition and specifies the outcome of an event
Notes:
NOTE 1:  Consequences can be expressed qualitatively or quantitatively.
NOTE 2:  Consequences can range from positive to negative. However, consequences are always negative for safety aspects.
NOTE 3:  There may be one or more consequences of an event.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#RiskEvent    [Status: ready_for_review]
Class label: risk event
Description:
assignment of an method to a Risk perception
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#RiskImpactAssignment    [Status: ready_for_review]
Class label: risk impact assignment
Description:
assignment of a Risk consequence to something
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#RiskPerception    [Status: created]
Class label: Risk perception
Description:
A RiskPerception is a specialization of ProductViewDefinition that defines values or concerns with which a stakeholder views a particular Risk. The context in which a RiskPerception occurs is represented by RiskPerceptionContext
Notes:
NOTE 1:  Risk will be perceived differently in different contexts, such as in the context of human safety, mission success, project time schedule, performance or economy.
NOTE 2:  RiskPerception can differ from objective data.
NOTE 3:  RiskPerception depends on the stakeholder's expressed needs, issues, and knowledge.
NOTE 4:  RiskPerception may be used qualitatively or quantitatively to form a risk matrix.
NOTE 5:  There is only one probability for each perceived risk. The probability for something to happen does not vary depending on the consequences.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#RiskPerceptionContext    [Status: created]
Class label: RiskPerceptionContext
Description:
defines the context for the perception of the risk.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#RiskPerceptionRelationship    [Status: created]
Class label: Risk perception relationship
Description:
A RiskPerceptionRelationship is a specialization of ViewDefinitionRelationship that defines an association between two instances of RiskPerception
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#RiskPerceptionSourceAssignment    [Status: ready_for_review]
Class label: risk perception source assignment
Description:
assignment of a Risk perception to something
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#RiskRelationship    [Status: created]
Class label: Risk relationship
Description:
A RiskRelationship is a specialization of ProductRelationship. It is an association between two an association between two instances of Risk
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#RiskVersion    [Status: created]
Class label: Risk version
Description:
A RiskVersion is a specialization of ProductVersion. It defines a form of a risk that differ in certain respects from an earlier form of that risk or from other forms of that risk
Notes:
NOTE 1:  Use of RiskVersion allows several RiskPerception instances to be assigned to a specific Risk.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#RiskViewDefinition    [Status: created]
Class label: Risk view definition
Description:
A RiskViewDefinition is a specialization of a ProductViewDefinition  and is an abstract generalization of instances that represents …
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#Scheme    [Status: created]
Class label: Scheme
Description:
A Scheme is a specialization of ActivityMethod. It provides the identification and description of an intended course of action to accomplish an objective. A Scheme enables the ordering of entries. Dates and times may be specified for entries and time intervals between entries
Notes:
NOTE 1:  A Scheme may be classified as a Plan or Schedule, and it may be further classified into specific types of Plans or Schedules.
Examples:
EXAMPLE 1:  Acquisition plan, Maintenance plan, Resource schedule are examples of schemes.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#SchemeEntry    [Status: created]
Class label: Scheme entry
Description:
A SchemeEntry is a specialization of ActivityMethod that provides the identification and description of a single entry in a specific Scheme
Notes:
NOTE 1:  A SchemeEntry only exists within the scope of a specific Scheme.
NOTE 2:  A SchemeEntry may be associated with time constraints.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#SchemeEntryAssignment    [Status: ready_for_review]
Class label: scheme entry assignment
Description:
assignment of a Scheme entry to something
Notes:
NOTE 1:  The SchemeEntryAssignment links the single items included in Plans and Schedules with their associated SchemeEntry. These items may be actions, events, or tasks depending on the nature of the Plan or Schedule.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#SchemeEntryRelationship    [Status: created]
Class label: Scheme entry relationship
Description:
A SchemeEntryRelationship is a specialization of ActivityMethodRelationship. It relates two SchemeEntry entities. An association may exists between SchemeEntry entities that relate to different Scheme or between different SchemeEntry entity instances for the same Scheme
Notes:
NOTE 1:  The SchemeEntryRelationship provides the ability to relate entries included in Plans or Schedules in different ways. By applying classifications on the SchemeEntryRelationship it can be used for different purposes.
Examples:
EXAMPLE 1:  Decomposition, Dependency, and sequencing are examples of kinds of relationships possible between schema entries.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#SchemeRelationship    [Status: created]
Class label: Scheme relationship
Description:
A SchemeRelationship is a specialization of ActivityMethodRelationship relating two Schemes
Notes:
NOTE 1:  The SchemeRelationship provides the ability to relate Plans or Schedules represented by the Scheme entity in different ways. If classifications are available to the schema using this on, by applying classifications on the SchemeRelationship it can be used for different purposes.
Examples:
EXAMPLE 1:  Decomposition, based-on, alternative, version are kinds of relationships between Schemes.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#SchemeSubjectAssignment    [Status: ready_for_review]
Class label: scheme subject assignment
Description:
assignment of a Scheme to something
Notes:
NOTE 1:  The SchemeSubjectAssignment links the Plans and Schedules with their associated subjects or targets. This may indicate the intent of the scheme.
Examples:
EXAMPLE 1:  The maintenance plan for an individual vehicle, where the subject attribute points to an entity instance representing the individual vehicle.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#SchemeVersion    [Status: created]
Class label: Scheme version
Description:
A SchemeVersion is a specialization of ActivityMethod. It enables version control of Scheme
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#SchemeVersionAssignment    [Status: ready_for_review]
Class label: scheme version assignment
Description:
assignment of a Scheme version to something
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#SchemeVersionRelationship    [Status: created]
Class label: Scheme version relationship
Description:
A SchemeVersionRelationship is a specialization of ActivityMethodRelationship relating two SchemeVersions
Notes:
NOTE 1:  The meaning of the relationship may be defined through classification.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#SecurityClassification    [Status: ready_for_review]
Class label: security classification
Description:
level of confidentiality that can be applied to protect something against unauthorized usage
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#SecurityClassificationAssignment    [Status: ready_for_review]
Class label: security classification assignment
Description:
assignment of a security classification to something
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#SelectedItemAssignment    [Status: ready_for_review]
Class label: selected item assignment
Description:
assignment of a classification to something
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#SequenceOfState    [Status: created]
Class label: Sequence of state
Description:
A SequenceOfState is a specialization of StateRelationship in which one set of State precedes another set of State
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#SequenceOfStateDefinition    [Status: created]
Class label: Sequence of state definition
Description:
A SequenceOfStateDefinition is a specialization of StateDefinitionRelationship. It defines a sequence of two or more state definitions
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#SequencingRelationship    [Status: created]
Class label: Sequencing relationship
Description:
A SequencingRelationship is a specialization of SchemeEntryRelationship. It defines a specific type of sequencing and relative timing for two SchemeEntry
Notes:
NOTE 1:  Specific types of sequencing could include start-start, finish-start.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#SerialEffectivity    [Status: ready_for_review]
Class label: serial effectivity
Description:
effectivity for which the domain of applicability is defined as a possibly open-ended interval of serial numbers
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ShapeElementRelationship    [Status: created]
Class label: Shape element relationship
Description:
relationship between two instances of ShapeElement
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#SimultaneousElements    [Status: created]
Class label: Simultaneous elements
Description:
A SimultaneousElements is a specialization of ConcurrentElements that represents two or more actions to be performed together
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#StandardUncertainty    [Status: created]
Class label: Standard uncertainty
Description:
A StandardUncertainty is a specialization of UncertaintyQualifier. A StandardUncertainty may be an ExpandedUncertainty. The uncertainty is defined in clause 2 of "The Guide to the Expression of Uncertainty in Measurement"
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#StartTask    [Status: created]
Class label: Start task
Description:
A StartTask is a type of TaskElement. It signifies the start point of the task
Notes:
NOTE 1:  Not all formal task description require start and end elements, their inclusion is in a sequence is optional.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#State    [Status: passed_review]
Class label: state
Class specification
Definition:
mode of being in which something does, could, or did exist for a period of time
Notes:
NOTE 1:  The period of existence may be an instant or longer.
Examples:
EXAMPLE 1:  Main Engine No. 1 is in the state "operation".
EXAMPLE 2:  The portable computer's power supply was attached after it displayed a warning of a "low-battery" state.
EXAMPLE 3:  When Generator No. 2 exceeds 5,000 service hours, it will enter "maintenance" state.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#StateAssertion    [Status: passed_review]
Class label: state assertion
Description:
statement confirmed by evidence such as a measurement assertion that a state is in conformance with a particular state definition
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#StateAssessment    [Status: passed_review]
Class label: state assessment
Description:
subjective statement without supporting evidence that a state is in conformance comparable with a particular state definition
Notes:
NOTE 1:  A state assessment is made without objective evidence, e.g. a measurement.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#StateAssignment    [Status: ready_for_review]
Class label: state assignment
Description:
assignment of a state to something
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#StateCauseEffect    [Status: created]
Class label: State cause effect
Description:
A StateCauseEffect is a specialization of state relationship and it relates two or more states as one state causing particular resulting effect state(s). In turn, an effect state can become a new causing state yielding in yet more effect states
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#StateCauseEffectDefinition    [Status: created]
Class label: State cause effect definition
Description:
A StateCauseEffectDefinition is a specialization of StateDefinitionRelationship that is used to define a causal relationship between two sets of StateDefinition entities. At least one StateDefinition acts as a cause and at least one StateDefinition acts as a effect
Notes:
NOTE 1:  Additional causal relationships between states can be expressed using the following subtypes: AndStateCauseEffectDefinition, OrStateCauseEffectDefinition, and XorStateCauseEffectDefinition.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#StateComplementDefinition    [Status: created]
Class label: State complement definition
Description:
A StateComplementDefinition is a specialization of StateDefinitionRelationship. It is a relationship among three sets of StateDefinition entities. It defines the complement of a set of StateDefinition entities relative to a set of StateDefinition entities that are the universe
Notes:
NOTE 1:  The relationship between a StateDefinition and its complement is symmetrical.
NOTE 2:  The semantics are the same as in elementary set theory.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#StateDefinition    [Status: passed_review]
Class label: state definition
Description:
definition of a possible or typical state
Examples:
EXAMPLE 1:  The definition of the state, ”flying” is that the aircraft is off the ground.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#StateDefinitionAssignment    [Status: ready_for_review]
Class label: State definition assignment
Description:
assignment of a state definition to something
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#StateDefinitionRelationship    [Status: created]
Class label: State definition relationship
Description:
relationship between two or more instances of StateDefinition
Notes:
NOTE 1:  Relationships between StateDefinition entities may be used to support fault diagnosis.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#StateObserved    [Status: passed_review]
Class label: observed state
Description:
state that something has been observed to be in
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#StatePredicted    [Status: passed_review]
Class label: predicted state
Description:
state that something has been predicted to be in
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#StatePredictedToObserved    [Status: created]
Class label: State predicted to observed
Description:
A StatePredictedToObserved is a specialization of state relationship. It specifies the relationship between two individual states, one of which is a StatePredicted to a second state which is a StateObserved
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#StateProperSubsetDefinition    [Status: created]
Class label: State proper subset definition
Description:
A StateProperSubsetDefinition is a specialization of StateDefinitionRelationship. It is a relationship between two sets of StateDefinition entities
Notes:
NOTE 1:  The relationship between a state and its environment can be described as a StateProperSubsetDefinition. The identification of an intrinsic state is the properSubset. The identification of an extrinsic state is the properSuperset.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#StateRelationship    [Status: created]
Class label: State relationship
Description:
relationship between two or more State
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#StateSubsetDefinition    [Status: created]
Class label: State subset definition
Description:
A StateSubsetDefinition is a specialization of StateDefinitionRelationship. It is a relationship between two sets of StateDefinition entities
Notes:
NOTE 1:  The first set may be equal to the second set.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#StateSymptomDefinition    [Status: created]
Class label: State symptom definition
Description:
A StateSymptomDefinition is a specialization of StateDefinitionRelationship. It relates two or more StateDefinition entities in regards to symptom, where a symptom is something that indicates the existence of something else. At least one StateDefinition acts as a symptomCause and at least one StateDefinition acts as a symptomEffect
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#StateTransition    [Status: created]
Class label: State transition
Description:
A StateTransition is a specialization of state relationship and it relates two or more states before and after a transition in State, where at least one State is a start state and at least one State is an end state
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#StateTransitionDefinition    [Status: created]
Class label: State transition definition
Description:
A StateTransitionDefinition is a specialization of StateDefinitionRelationship. It relates two or more StateDefinition entities before and after a transition in state, where at least one StateDefinition is a startState and at least one StateDefinition is an endState
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#StringValue    [Status: passed_review]
Class label: string value
Description:
property value expressed as a sequence of one or more alphanumeric characters
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#StructuredTaskElement    [Status: created]
Class label: Structured task element
Description:
A StructuredTaskElement is a type of TaskElement. It is made up of other TaskElements
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#SuppliedPartRelationship    [Status: created]
Class label: Supplied part relationship
Description:
A SuppliedPartRelationship is a specialization of ProductVersionRelationship that relates two instances of ProductVersion that represent the same instance in different organizational contexts. One of the organizations is the supplier of the instance to the other organization. This entity is applicable for part versions and document versions
Notes:
NOTE 1:  The module provides a more general mechanism that can be used to track alias identifiers for any entity data type that has an id attribute.
NOTE 2:  This entity enables to represent the fact that two organizations may use distinct identifiers to identify their Product and their versions.
NOTE 3:  This mechanism can only be used in an information system or in exchange files where the content of the id attribute of instances of Product is not constrained by a particular identification scheme.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#System    [Status: created]
Class label: System
Description:
A System is a specialization of Product used to identify a conceptual solution to a collection of requirements
Notes:
NOTE 1:  Another definition would be "That which is discernible by reproducible measurement of its characteristics, and has a defined boundary (statically and dynamically) with respect to the universe".
NOTE 2:  SEDRES Definition: "An assembly of interacting, active components or elements forming a whole".
NOTE 3:  The concept system is any thing - matter, energy, organization or information or a combination of these - for which reproducible measurements exist. The concept system excludes any asserted thing based on personal experience for which no reproducible measurements exist.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#SystemBreakdown    [Status: passed_review]
Class label: system breakdown
Description:
breakdown comprising system elements
Notes:
NOTE 1:  The system breakdown is a partitioning of a product into a set of related system elements so as to form explicit, parent-child views.
Examples:
EXAMPLE 1:  A system breakdown provides a decomposition of an aircraft in terms of high-level Systems such as "fuel system" or "flight control system" - which might, in the second example, further decompose into low-level systems such as "autopilot system" and "instrument landing system".
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#SystemBreakdownContext    [Status: created]
Class label: System breakdown context
Description:
A SystemBreakdownContext is a specialization of BreakdownContext that is a membership relationship between a SystemElement and a SystemBreakdown of which the system element is a member
Examples:
EXAMPLE 1:  A heating system is a member of the breakdown of a climate control system.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#SystemBreakdownVersion    [Status: created]
Class label: System breakdown version
Description:
A SystemBreakdownVersion is a specialization of BreakdownVersion that identifies a version of a SystemBreakdown
Examples:
EXAMPLE 1:  A logistics engineer modifies the current systems breakdown for an aircraft and associated support equipment on the basis of results from a level of repair analysis.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#SystemElement    [Status: passed_review]
Class label: system element
Description:
breakdown element that represents a System
Notes:
NOTE 1:  System elements are partitions of a system breakdown.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#SystemElementDefinition    [Status: created]
Class label: System element definition
Description:
A SystemElementDefinition is a specialization of BreakdownElementDefinition that identifies a view of a version ( SystemElementVersion) of a SystemElement
Examples:
EXAMPLE 1:  The collision avoidance system element of a system breakdown is subject to a level of repair analysis to support implementation of optimized maintenance for an aircraft.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#SystemElementUsage    [Status: created]
Class label: System element usage
Description:
A SystemElementUsage is a specialization of BreakdownElementUsage that is a relationship between a SystemElementDefinition and another SystemElementDefinition that is a constituent
Examples:
EXAMPLE 1:  In a system breakdown, the fuel system might include a fuel storage system and a fuel injection system as components.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#SystemElementVersion    [Status: created]
Class label: System element version
Description:
A SystemElementVersion is a specialization of BreakdownElementVersion that identifies a version of a SystemElement
Examples:
EXAMPLE 1:  A sound engineer changes the details describing the public address system that is an element in a system breakdown of an aircraft.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#SystemVersion    [Status: created]
Class label: System version
Description:
A SystemVersion is a specialization of ProductVersion that represents a particular version of a system
Notes:
NOTE 1:  In this case, this means "revision". So for a given system (e.g. a fuel injection system) we may have several versions of the system design (e.g. v1, v1.1 etc.)
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#SystemVersionRelationship    [Status: created]
Class label: System version relationship
Description:
A SystemVersionRelationship is a specialization of ProductVersionRelationship used to relate versions of a system
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#SystemVersionSequence    [Status: created]
Class label: System version sequence
Description:
A SystemVersionSequence is a specialization of SystemVersionRelationship used to relate a previous version of a system to the version that replaces it
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#SystemViewDefinition    [Status: created]
Class label: System view definition
Description:
A SystemViewDefinition is a specialization of ProductViewDefinition that provides a view of a system version relevant for one or more application domains
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#TaskElement    [Status: ready_for_review]
Class label: task element
Description:
method that represents the undertaking of a task
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#TaskElementAssignment    [Status: created]
Class label: task element assignment
Description:
assignment of a task element to something
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#TaskElementLevels    [Status: created]
Class label: Task element levels
Description:
A TaskElementLevels is a type of TaskElement that provides two or more different descriptions in place of a single method. The actual work will be the same whichever alternative TaskElement is followed
Notes:
NOTE 1:  This can be used to provide different levels of description of a task for people with varying levels of experience or expertise.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#TaskElementRelationship    [Status: created]
Class label: Task element relationship
Description:
A TaskElementRelationship is a specialization of ActivityMethodRelationship. It relates two instances of TaskElement
Examples:
EXAMPLE 1:  Can be used to capture a time dependency that cuts across the structure of the method.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#TaskElementSequence    [Status: created]
Class label: Task element sequence
Description:
A TaskElementSequence is a specialization of TaskElement that comprises a sequence of steps to be followed in a specified order
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#TaskElementStateRelationship    [Status: created]
Class label: Task element state relationship
Description:
relationship between a State or a StateDefinition and a TaskElement. The meaning of the entity is determined by classification. Candidate meanings include: assumed starting state; required starting state
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#TaskInvocation    [Status: ready_for_review]
Class label: task invocation
Description:
task element that constitutes an instruction to perform another task method
Examples:
EXAMPLE 1:  The specification of a predefined task method for performing an instrument calibration.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#TaskMethod    [Status: ready_for_review]
Class label: task method
Description:
method that relates an activity to a Task objective
Notes:
NOTE 1:  The task method may be implemented using people, machines or a combination.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#TaskMethodAssignment    [Status: ready_for_review]
Class label: task method assignment
Description:
assignment of a task method to something
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#TaskMethodRelationship    [Status: created]
Class label: Task method relationship
Description:
A TaskMethodRelationship is a specialization of ActivityMethodRelationship. It relates two task methods
Notes:
NOTE 1:  The nature of the relationship is determined from its classification.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#TaskMethodStateRelationship    [Status: created]
Class label: Task method state relationship
Description:
relationship between a state and a TaskMethod
Notes:
NOTE 1:  The meaning of the entity is determined by classification. Candidate meanings include: Assumed starting state; Required starting state.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#TaskMethodVersion    [Status: ready_for_review]
Class label: task method version
Description:
version of a task method version
Notes:
NOTE 1:  This allows for the explicit reference to versions of a task method and for the tracking of changes to a task method.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#TaskMethodVersionAssignment    [Status: ready_for_review]
Class label: task method version assignment
Description:
assignment of a task method version to something
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#TaskMethodVersionRelationship    [Status: created]
Class label: Task method version relationship
Description:
A TaskMethodVersionRelationship is a specialization of ActivityMethodRelationship. It relates two instances of TaskMethodVersion
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#TaskObjective    [Status: created]
Class label: Task objective
Description:
A TaskObjective is a result or objective that is reached by undertaking a TaskMethod
Notes:
NOTE 1:  More than one TaskMethod may be defined for a given objective, if there can be several ways to accomplish the objective.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#TaskObjectiveStateRelationship    [Status: created]
Class label: Task objective state relationship
Description:
relationship between a state and a TaskObjective
Notes:
NOTE 1:  The meaning of the entity is determined by classification. Candidate meanings include: Intended finishing state; Alternative finishing state.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#TaskStep    [Status: created]
Class label: Task step
Description:
A TaskStep is a specialization of TaskElement that is not further sub-divided
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#TimeInterval    [Status: created]
Class label: Time interval
Description:
A TimeInterval is the identification of an intervening time
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#TimeIntervalAssignment    [Status: ready_for_review]
Class label: time interval assignment
Description:
assignment of a Time interval to something
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#TimeIntervalEffectivity    [Status: ready_for_review]
Class label: time interval effectivity
Description:
effectivity for which the domain of applicability is defined as a Time interval
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#TimeIntervalRelationship    [Status: created]
Class label: Time interval relationship
Description:
relationship between two instances of TimeInterval. The meaning of this association is specified in the TimeIntervalRelationship attribute
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#TimeIntervalWithBounds    [Status: created]
Class label: Time interval with bounds
Description:
A TimeIntervalWithBounds is a specialization of TimeInterval. A TimeIntervalWithBounds is bounded either on one side or both sides. If neither secondaryBound nor Duration are specified, the time interval begins at the point in time identified by primaryBound and has no specified end point
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#TracingRelationship    [Status: created]
Class label: Tracing relationship
Description:
A TracingRelationship is a specialization of ViewDefinitionRelationship that shows tracing from ( TracingRelationship) one requirement to another ( TracingRelationship). A requirement may trace to many other requirements and vice versa - this is achieved by creating multiple instances of the tracing relationship entity
Notes:
NOTE 1:  Properties may be attached to tracing relationships. This is intended to deal with "user defined" attributes which are common on tracing relationships in requirements tools.
NOTE 2:  The inherited " ViewDefinitionRelationship" and " ViewDefinitionRelationship" attributes have been renamed for purposes of clarity.
Examples:
EXAMPLE 1:  A requirement on the performance of a catalytic converter in a car may be traced from a more general emissions requirement.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#TypeOfPerson    [Status: ready_for_review]
Class label: Type of person
Description:
category of person
Examples:
EXAMPLE 1:  Class 3 welder
EXAMPLE 2:  Electronics engineer
EXAMPLE 3:  Helicopter pilot
EXAMPLE 4:  Mechanical technician
EXAMPLE 5:  Truck driver
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#TypeOfPersonAssignment    [Status: ready_for_review]
Class label: type of person assignment
Description:
assignment of a Type of person to something
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#TypeOfPersonDefinition    [Status: created]
Class label: Type of person definition
Description:
A TypeOfPersonDefinition is the definition of a TypeOfPerson in terms of required properties or attributes
Examples:
EXAMPLE 1:  A junior mechanical design engineer could be specified to be either someone who has 3 years experience of working in a mechanical design department, or a degree in mechanical engineering.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#TypeOfPersonDefinitionRelationship    [Status: created]
Class label: Type of person definition relationship
Description:
relationship between two definitions of a type of person ( TypeOfPersonDefinition)
Notes:
NOTE 1:  The meaning of the relationship is determined by classification.
Examples:
EXAMPLE 1:  "alternate" and "superceded by" are examples of TypeOfPersonDefinitionRelationships.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#TypeOfPersonDefinitionRequiredAttributesRelationship    [Status: created]
Class label: Type of person definition required attributes relationship
Description:
relationship between a TypeOfPersonDefinition and the attributes required to define that type of person
Examples:
EXAMPLE 1:  The type of person "van driver" is required to possess the qualification named "commercial driving license" or the experience level "3 years of driving more than 10,000 miles per year".
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#UncertaintyQualifier    [Status: created]
Class label: Uncertainty qualifier
Description:
An UncertaintyQualifier is a generalization of a StandardUncertainty or a QualitativeUncertainty. The uncertainty is defined in clause 2 of "The Guide to the Expression of Uncertainty in Measurement"
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#Validation    [Status: created]
Class label: Validation
Description:
A Validation is a subjective assertion that an item is "fit for purpose". Evidence used in this validation is identified by the inverse attribute validatedBy. Validation is commonly understood to mean "Have we built the right system?". Validation is concerned with ensuring that the system will meet the customer’s objectives and expectations. Validation usually includes testing under normal usage conditions
Notes:
NOTE 1:  It is assumed that meta data supporting the validation will be applied using assignment entities, such as identification assignment, person and organization assignment etc..
NOTE 2:  An item may pass validation even though some requirements fail verification.
Examples:
EXAMPLE 1:  Every flight of every Space Shuttle has been a "Validation" flight to test the new design under actual conditions. No two shuttles have flown in the same configuration and many systems cannot be validated except under actual conditions.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ValueLimit    [Status: created]
Class label: Value limit
Description:
A ValueLimit is a specialization of NumericalItemWithUnit that specifies a qualified numerical value representing either the lower limit or the upper limit of a particular quantifiable characteristic
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ValueList    [Status: created]
Class label: Value list
Description:
A ValueList is a specialization of MeasureItem that is an ordered collection of MeasureItems
Examples:
EXAMPLE 1:  A MeasureItem may be composed of different values such as 'mass', 'speed', and 'age' which are all necessary in a given context. The ValueList collects all of them in a given order, such that each is identifiable by its index in the list.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ValueRange    [Status: created]
Class label: Value range
Description:
A ValueRange is a specialization of MeasureItem that is a pair of numbers representing the range in which the value shall lie
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ValueSet    [Status: created]
Class label: Value set
Description:
A ValueSet is a specialization of MeasureItem that is an unordered collection of MeasureItems
Examples:
EXAMPLE 1:  A MeasureItem may be composed of different values such as 'mass', 'speed', and 'age' which are all necessary in a given context. The ValueSet collects all of them in a given order, such that each is identifiable by its index in the list.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ValueWithTolerances    [Status: created]
Class label: Value with tolerances
Description:
A ValueWithTolerances is a specialization of MeasureItem that specifies a range of values by specifying a single nominal value and two tolerances that are offsets from the single value. The range is defined to be the closed interval [item value + lower limit, item value + upper limit]
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ValueWithUnit    [Status: passed_review]
Class label: value with unit
Description:
property value specified as a value and unit
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#Verification    [Status: created]
Class label: Verification
Description:
A Verification is an objective assertion of a claim that requirement is satisfied by a particular item represented in a RequirementSatisfiedBy has been verified. The evidence used in this verification is identified by the inverse attribute verifiedBy. Verification is commonly understood to mean "Have we built the system right?". Verification ensures that the specified requirements have been met. Verification uses the methods of Test, Analysis, Inspection, Demonstration, Similarity
Notes:
NOTE 1:  It is assumed that meta data supporting the verification will be applied using assignment entities, such as identification assignment, person and organization assignment etc..
NOTE 2:  Just because an item is verified does not ensure that it meets all stakeholder needs or expectations, many of these are never specified are of an untestable nature e.g. "the car should look sporty".
Examples:
EXAMPLE 1:  A data type used to represent a vehicle's engine with a power output of 160BHP could be asserted to satisfy a requirement "the vehicle shall have a maximum power output of at least 150BHP". This assertion may be verified by analysis results on simulations of the engine. In this case the analysis results would be identified in the items collection of an evidence instance, possibly including the approval of the analysis. The evidence instance would identify that it is used to support the required verification.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#VerificationRelationship    [Status: created]
Class label: Verification relationship
Description:
relationship between two verifications
Notes:
NOTE 1:  This relationship may be classified in other modules to provide more specific meanings.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ViewDefinitionRelationship    [Status: ready_for_review]
Class label: view definition relationship
Description:
relationship between two product views
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ViewDefinitionUsage    [Status: ready_for_review]
Class label: view definition usage
Description:
view definition relationship between two product views
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#WorkOrder    [Status: ready_for_review]
Class label: work order
Description:
authoritative instrument which provides directions to achieve the specified results
Notes:
NOTE 1:  A work order is an authorization for one or more activity instances to be performed.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#WorkOutput    [Status: created]
Class label: Work output
Description:
A WorkOutput is a statement of output resulting from an activity or a task. The role of the work output is determined by classification
Examples:
EXAMPLE 1:  When applicable a work output may be classified as "Planned"; "Actual"; "By-product"; "Waste product".
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#WorkOutputAssignment    [Status: ready_for_review]
Class label: work output assignment
Description:
assignment of a Work output to something
Notes:
NOTE 1:  A WorkOutputAssignment is an association of a work output statement with the source that produces or delivers the output. The work output can be planned as well as actual.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#WorkOutputRelationship    [Status: created]
Class label: Work output relationship
Description:
relationship between two work output statements. The meaning of the relationship is determined by classification.
Examples:
EXAMPLE 1:  A WorkOutputRelationship is classified as "realized by"
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#WorkRequest    [Status: ready_for_review]
Class label: work request
Description:
solicitation for some work to be done
Notes:
NOTE 1:  Work requests may or may not be acted upon depending on the authorization granted to the work request or its associated work order.
NOTE 2:  These requests may not be acted upon depending on the authorization granted to the request or its associated WorkOrder.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#WorkRequestAssignment    [Status: ready_for_review]
Class label: work request assignment
Description:
assignment of a work request to something
Examples:
EXAMPLE 1:  In case a tyre on a car is flat, a WorkRequest may be created and associated with the instances that represent the tyre that is flat, the car and the spare wheel.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#WorkRequestMethodAssignment    [Status: passed_review]
Class label: method assigned to work request
Description:
assignment of a method to a work request
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#WorkRequestRelationship    [Status: created]
Class label: Work request relationship
Description:
relationship between two instances of WorkRequest
Notes:
NOTE 1:  The meaning of the relationship is determined by classification which is identified by the RelationshipObject property. The possible classifications are subclasses of .
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#XorStateCauseEffectDefinition    [Status: created]
Class label: Xor state cause effect definition
Description:
An XorStateCauseEffectDefinition is a specialization of StateCauseEffectDefinition. It relates one of the single or many causing state definition(s) and one effect StateDefinition, whereby any and only one of the causing state definitions exists prior to the single effect to take place
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ZoneBreakdown    [Status: passed_review]
Class label: zonal breakdown
Description:
breakdown comprising zone elements
Notes:
NOTE 1:  The zonal breakdown is a partitioning of a product into a set of related zone elements so as to form explicit, parent-child views.
Examples:
EXAMPLE 1:  A zonal breakdown provides a decomposition of an aircraft in terms of spaces or high-level conceptual parts such as 'wing' - which might further decompose into lower-level zones such as 'inner-wing', and 'outer wing'.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ZoneBreakdownContext    [Status: created]
Class label: Zone breakdown context
Description:
A ZoneBreakdownContext is a specialization of BreakdownContext that is a membership relationship between a ZoneElement and a ZoneBreakdown of which the zonal element is a member
Examples:
EXAMPLE 1:  A 'fire-check zone' might be a member of the zonal breakdown of a building.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ZoneBreakdownVersion    [Status: ready_for_review]
Class label: zone breakdown version
Description:
zone breakdown version that identifies a version of a zonal breakdown
Examples:
EXAMPLE 1:  An architect modifies the current fire-check zone breakdown for an building on the basis of reports from a buildings inspector.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ZoneElement    [Status: passed_review]
Class label: zone element
Description:
breakdown element that represents a 3 dimensional space
Notes:
NOTE 1:  Zone elements are partitions of a zonal breakdown
Examples:
EXAMPLE 1:  'Empennage', 'Right vertical stabilizer and rudder' and 'Lower rudder' are all elements in a zonal breakdown of an aircraft.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ZoneElementDefinition    [Status: created]
Class label: Zone element definition
Description:
A ZoneElementDefinition is a specialization of BreakdownElementDefinition that identifies a view of a version ( ZoneElementVersion) of a ZoneElement
Examples:
EXAMPLE 1:  For an aircraft, an element 'Right vertical stabilizer tip' is in a zonal breakdown that an engineer uses for reliability-centred maintenance analysis.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ZoneElementUsage    [Status: created]
Class label: Zone element usage
Description:
A ZoneElementUsage is a specialization of BreakdownElementUsage that is a relationship between a parent and child ZoneElement
Examples:
EXAMPLE 1:  In a zonal breakdown, the 'wing' (parent) might include (as children) an 'inner wing' and an 'outer wing'.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Class URI:   http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#ZoneElementVersion    [Status: created]
Class label: Zone element version
Description:
A ZoneElementVersion is a specialization of BreakdownElementVersion that identifies a version of a ZoneElement
Examples:
EXAMPLE 1:  An engineer defines an inspection task on a breakdown element 'Upper rudder' that is part of a zonal breakdown of an aircraft. The engineer identifies the corresponding view of the breakdown element.
Source:
  1. ISO 10303-239ed2 transformed to AP239AP233 PSM
Issue reporting