Reference Data Class Viewer
This is a display of all the reference data in development. It is
organized by the OWL ontology namespace (i.e. URI/URN).
Each class is an OWL class displayed here as pseudo EXPRESS
classes for ease of readability.
The OASIS stage of each class is shown.
The classes are organized by the OWL ontology namespace
(i.e. URI/URN).
URN: urn:plcs:rdl:std
RDL File: committee-specification/plcs-arm-lf-express.rdf-xml.owl ()
Title:
Version: 1
Stage:
Description: This ontology is a subset of the PLCS ARM Long Form EXPRESS represented as OWL.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Activity is the identification of the occurrence of an action that has taken place, is taking place, or is expected to
take place in the future. The procedure executed during that Activity is identified with the Activity_method that is referred
to by the chosen_method attribute.
EXAMPLE: Change, distilling, design, a process to drill a hole, and a task such as training someone, are examples of activities.
NOTE: Status information identifying the level of completion of each activity may be provided within an instance of Activity_status.
NOTE: The items that are affected by an Activity, for example as input or output, may be identified within an instance of Applied_activity_assignment.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Activity_actual is a type of Activity. It is a record of the occurrence of an Activity. The Activity_actual is related
through an Activity_happening to the Activity for which it is an occurrence. The existence of an Activity_actual instance
means that the Activity_actual has started.
NOTE: A Calendar_date or Date_time should be assigned to the Activity_actual with the role "start date" to record when the
activity started.
NOTE: A Calendar_date or Date_time may be assigned to the activity with role "end date" to record when the activity finished.
In general, the absence of this assignment cannot be used to infer that the activity is continuing, only that the end of the
activity has not yet been recorded.
NOTE: A more detailed history of the progress of an activity may be recorded by applying states to the activity, but the meaning
of these states must be defined through local business rules.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Activity_happening is a type of Activity_relationship. It is a relationship between the definition of an activity ( Activity_happening.predicted )
and its actual occurrence ( Activity_happening.actual ).
NOTE: The ordinary value for Activity.name may be "actual", though this is redundant.
NOTE: Many Activity_actual s may be the actual for a single Activity.
EXAMPLE: a single defined activity is recorded historically by several sub-activities.
NOTE: A single Activity_actual may fulfil several activities.
EXAMPLE: a single servicing activity takes the opportunity to make additional checks and repairs.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Activity_method is a way to carry out an Activity.
NOTE: There may be more than one method for producing a required result
NOTE: This definition may be used to characterize a way to resolve a request for action. The concept of action request is
dealt with in module.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Activity_method_assignment is an association between an Activity_method and a Work_request. The relation_type attribute
characterizes the meaning of that association and the meaning of the Activity_method with respect to the Work_request.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Activity_method_realization is a further specification of how an activity method is to be performed with the Activity_method.
NOTE: More than one specification can be associated with the same Activity_method.
EXAMPLE: 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:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Activity_method_realization_relationship is a relationship between two Activity_method_realization entity instances.
NOTE: An Activity_method_realization_relationship may be used to specify sequencing and other constraints between different
realizations for the same Activity_method.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Activity_method_relationship is a relationship between two instances of Activity_method.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Activity_property is a property of an Activity or of an Activity_method.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Activity_property_representation is an association between an Activity_property and one of its representations.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Activity_relationship is a relationship between two instances of Activity.
EXAMPLE: The activity required to complete a work order, may be decomposed into a series of activities. Their corresponding
instances would be related using instances of the Activity_relationship entity.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Activity_status is the assignment of a status to an Activity.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Address is the information that locate persons or organizations. It provides location details for communication via postal
mail, telephone, facsimile, telex or electronic mail.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Address_assignment is the association of an Organization or a Person_in_organization with an Address.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Address_based_location_representation is a type of Location_representation specified by its postal identification.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Advisory_task_step is a type of Task_step. It conveys information.
NOTE: Some Task_method s may not require any action to be undertaken.
EXAMPLE: "Beware of hot exhausts", "do not use tool X this way" and similar messages.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Affected_items_assignment is an association of a Work_request with the product or activity data that are subjects of this Work_request.
EXAMPLE: In case a tire on a car is flat, a Work_request may be created and associated with the instances that represent the
tire that is flat, the car and the spare wheel.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Alias_identification is a type of Identification_assignment that provides an alias identifier to product or activity data.
NOTE: The alias identifier is conveyed within the identifier attribute inherited from Identification_assignment.
NOTE: Information about the organizational scope in which the alias applies may be provided by a specialization of Organization_or_person_in_organization_assignment.
NOTE: Alias identification only applies to concepts that possesses an attribute that conveys an identifier.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Alternate_part_relationship is a type of alternate_product_relationship where the alternate and base products are parts.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Amount_of_substance_unit is a type of Unit in which the number of elementary entities of a substance as compared to the
number of atoms in 0.012 kilograms of carbon-12 is expressed.
NOTE: This definition applies to the SI quantity 'mole'. When the mole is used, the elementary entities, whose quantity is
expressed, must be specified . They may be atoms, molecules, ions, electrons or other particles or specified groups of such
particles (see ISO 31-8).
NOTE: This unit corresponds to one of the seven fundamental quantities as specified in ISO 1000.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An And_state_cause_effect_definition is a type of State_cause_effect_definition. It relates one or more causing State_definition entities
and one effect State_definition. All the causing State_definition entities must exist prior to the single effect.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Applied_activity_assignment is an association of an Activity with product or activity data. It characterizes the role of
the concepts represented with these data with respect to the activity.
NOTE: This entity should not be used to represent the association of an activity with the organizations that are responsible
for its execution or its management. That kind of information can be represented with instances of Organization_or_person_in_organization_assignment.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Applied_activity_method_assignment is an association of an Activity_method with product or activity data.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Applied_independent_activity_property is a type of Activity_property that is an association of an Activity_property with
an Independent_property. It characterizes the fact that the Activity_property is the application of the Independent_property to
activity data.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Applied_independent_property is a type of Assigned_property that is associated with an Independent_property. It characterizes
the fact that the Applied_independent_property is the application of the Independent_property to product data.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Applied_independent_resource_property is a type of Resource_property that is associated to a Independent_property. It characterizes
the fact that the Resource_property is the application of the Independent_property to activity data.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Applied_information_usage_right is an application of a particular usage right to a set of items.
NOTE: 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:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Applied_state_assignment is a relationship that allows a subject to have State or to be in a State.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Applied_state_definition_assignment is a mechanism that enables an object to have or to be in a State_definition.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Approval is a formal confirmation of the quality of some activity or product data.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Approval_assignment is the assignment of an Approval to activity or product data.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Approval_relationship is a typed association between two instances of Approval.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Approval_status is a particular rank of approval.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Approving_person_organization is an association between an Approval and the organization or person and organization that
has granted this approval.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Assembly_component_relationship is a type of View_definition_usage. It identifies a possibly quantified usage of a product
version as a component of another product version. The relationship is established between two instances of Product_view_definition. The
inherited attribute View_definition_relationship.relating_view identifies the Product_view_definition of the assembly. The
inherited attribute View_definition_relationship.related_view identifies the Product_view_definition of the product version
that plays the role of component. The Assembly_component_relationship specifies that, in the Product_view_definition.initial_context of
the Product_view_definition that is referred to as View_definition_relationship.relating_view, it is considered that the product
version that is indirectly identified with the View_definition_relationship.related_view attribute, is a component of the
product version that is indirectly identified with the View_definition_relationship.relating_view attribute.
NOTE: In another context, the structure of the assembly may be described differently, adding, for example, an intermediate
level between the products.
NOTE: This entity data type may be used to establish assembly relationships during design or to represent the composition
of an assembly existing in the real world.
NOTE: An Assembly_component_relationship identifies an item in a parts list. Should the quantity be zero, the component would
still be listed in the parts list.
In case the component is a part, the following additional specifications apply:
* the quantity attribute shall either be not specified or shall characterize a number of occurrences of the component;
* if the quantity attribute specifies a number of occurrences, these occurrences shall be considered as a single group within
the assembly structure;
* if the quantity attribute is not specified, the relationship actually identifies a single occurrence of the component. In
case the component is a non-countable material, the following additional specifications apply:
* the quantity attribute shall either be not specified or shall characterize the amount of the material used as component;
* if the quantity attribute is not specified, the amount of material used as component shall be considered as unknown.
EXAMPLE: An assembly may require inclusion of ten grams of grease.
NOTE: This version of the Assembly structure module does not enable to represent the fact that the quantity of a fluid component
is, for example 'at most 10 grams' or 'between 5 or 20 grams'. However, some ISO 10303 application protocols, for example
ISO 10303-214, provide a representation for those requirements.
An Assembly_component_relationship shall be either a Next_assembly_usage, a or a Component_upper_level_identification.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Assembly_relationship_substitution is a relationship that indicates that an Assembly_component_relationship may be substituted
by another Assembly_component_relationship. Both assembly relationships shall refer to the same Product_view_definition of
the same assembly.
NOTE: Consequently, an Assembly_relationship_substitution actually specifies that the product version that plays the role
of component in the substitute_relationship may be replaced by the product version that plays the role of component in the base_relationship.
NOTE: 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.
NOTE: As instances of Assembly_component_relationship establish assembly relationships relevant in the definition contexts
of the assembly, the substitution only apply in these contexts.
An Assembly_relationship_substitution defines a one-way substitution: if A is specified as a substitute for B, B is not implied
to be a substitute for A.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Assigned_document_property is a type of Assigned_property that identifies a property assigned to a document definition
or to a file. When the Assigned_document_property is applied to a Digital_document_definition through the Assigned_property.described_element attribute,
the Assigned_document_property applies to all instances of Digital_file that are components of the Digital_document_definition. When
the Assigned_document_property is applied to a Physical_document_definition through the Assigned_property.described_element attribute,
the Assigned_document_property applies to all instances of Hardcopy that are components of the Physical_document_definition. When
the Assigned_document_property is applied to a File through the Assigned_property.described_element attribute, the Assigned_document_property applies
to the individual File.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Assigned_property is a property that is assigned to product data.
NOTE: The mapping provided for that entity and for its attribute described_element is incomplete. It needs to be completed
in any module that uses this module and extends the type property_assignment_select.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Attachment_slot is a type of Product that represents the position in which a part is or can be attached to a parent product.
EXAMPLE: 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:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Attachment_slot_as_planned is a type of Attachment_slot_version that identifies an individual that is the subject of a
plan to realize an Attachment_slot.
EXAMPLE: 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 Attachment_slot_as_planned entity data
type allow the company to associate individual engines with the aircraft at different times over the planned period.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Attachment_slot_as_realized is a type of Attachment_slot_version that identifies an individual that is a realized Attachment_slot.
EXAMPLE: 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:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Attachment_slot_definition is a type of Product_view_definition that identifies a view of an Attachment_slot.
EXAMPLE: 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:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Attachment_slot_design is a type of Attachment_slot_version that identifies the design version of an attachment slot.
EXAMPLE: WeMakeBigPlanes Limited creates design version 1.34 of the attachment slot for the starboard engine of an aircraft.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Attachment_slot_design_to_planned is a relationship between a design version of an Attachment_slot and a planned individual
that conforms to the design.
EXAMPLE: 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:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Attachment_slot_design_to_realized is a relationship between a design version of an Attachment_slot and a realized individual
that conforms to the design.
EXAMPLE: WeMakeBigPlanes Limited builds aircraft serial number 1234 with a starboard engine attachment slot that conforms
to design version 1.34.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Attachment_slot_on_product is a relationship between a product and an Attachment_slot that is a location on the product
at which to install removable parts.
EXAMPLE: An aircraft has a pylon mounting on a wing as a location at which to install various equipment. An instance of the Attachment_slot_on_product entity
data type identifies which attachment slot corresponds to the pylon.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Attachment_slot_planned_to_realized is a relationship between a realized individual of an Attachment_slot and a corresponding
planned individual.
EXAMPLE: WeMakeBigPlanes Limited builds aircraft serial number 2468 with a starboard engine attachment slot that was previously
planned.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Attachment_slot_version is a type of Product_version that identifies a version of Attachment_slot.
NOTE: This is a generic concept of version, in most situations it is possible and more specific to represent a version as Attachment_slot_design, Attachment_slot_as_planned or Attachment_slot_as_realized.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Attribute_translation_assignment is the assignment of a translation to a text attribute of an instance.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Axis_placement is a type of Detailed_geometric_model_element that defines a right-handed, 2D or 3D, coordinate system. If
the Axis_placement 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.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Breakdown is a type of Product that identifies a partitioning of a product into a set of related elements so as to form
explicit, parent-child views that comprise the product elements. The parent-child view is represented by Breakdown_element_usage objects
relating the elements in the breakdown that are represented by Breakdown_element objects. A Breakdown may be:
* a Functional_breakdown,
* a Hybrid_breakdown,
* a Physical_breakdown,
* a System_breakdown, or
* a Zone_breakdown.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Breakdown_context is a membership relationship between a Breakdown_element and a Breakdown of which the element is a member.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Breakdown_element is a type of Product that identifies the elements in one or more Breakdown objects.
NOTE: Breakdown_element is non-specific and allows for various types of product breakdown. The more specific breakdown elements
are Functional_element, Physical_element, System_element, and Zone_element.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Breakdown_element_definition is a type of Product_view_definition that identifies a view of a version ( Breakdown_element_version )
of a Breakdown_element.
NOTE: Breakdown_element_definition is non-specific and allows for various types of product breakdowns. The more specific breakdown
element definitions are Functional_element_definition, Physical_element_definition, System_element_definition and Zone_element_definition.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Breakdown_element_realization is a type of Product_definition_element_relationship that identifies a relationship between
a Breakdown_element_definition or a Breakdown_element_usage and an item that realizes that element definition or usage.
EXAMPLE: A pump realizes the 'provide fuel to engine' element in a functional breakdown for a ship.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Breakdown_element_usage is a type of View_definition_relationship that identifies a relationship between a parent and child Breakdown_element.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Breakdown_element_version is a type of Product_version that identifies a version of a Breakdown_element..
NOTE: Breakdown_element_version is non-specific and allows for various types of product breakdown. The more specific breakdown
elements are Functional_element_version, Physical_element_version, System_element_version and Zone_element_version.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Breakdown_of is a relationship between a Breakdown and a Product of which the breakdown is a view.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Breakdown_version is a type of Product_version that identifies a version of a Breakdown.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Calendar_date is a date that is defined as a day in a month of a year.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Cartesian_point is a type of Detailed_geometric_model_element that defines a point by a list of up to 3 cartesian coordinates.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Cartesian_transformation_2d is a type of Geometric_model. 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:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Cartesian_transformation_3d is a type of Detailed_geometric_model_element 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:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Certification is a certificate. It asserts satisfaction of particular quality criteria.
NOTE: Certification information can be attached to any aspect of product or activity data.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Certification_assignment is an association of a Certification with activity or product data.
EXAMPLE: 'certified supplier' is an example of certification that may be granted to an organization by its contractor.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Characterizable_object is an object that may be characterized with properties but that cannot be considered as a product
or an activity.
EXAMPLE: An orbit of a satellite is an example of Characterizable_object.
NOTE: A Characterizable_object may be used as an environmental condition under which the properties of a product are measured.
EXAMPLE: If a product has a set of properties that are measured within a particular atmosphere, the atmosphere may be described
with an instance of the entity data type Characterizable_object.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Class is a number of things considered together.
NOTE: In this part of ISO 10303, the term 'class' and 'set' are synonyms.
NOTE: A class can consist of all things with a particular set of properties. Hence information about the consequences of possessing
the set of properties can be assigned to the class. If a thing is classified as being a member of such a class, then a set
of properties possessed by the thing can be deduced.
NOTE: This entity may be instantiated as a compound instance involving another entity from ISO 10303.
Each Class is a Class_by_extension or a Class_by_intension
NOTE: The distinction between a Class_by_extension and a Class_by_intension can be imprecise. For example, the set of items
produced by a particular production run could be regarded as either. The entity type class is not specified as abstract, so
an application protocol or application module can decide to ignore the distinction.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Class_by_extension is a type of Class that is a set that is defined by means of a criterion that does not enumerate the
members.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Class_by_intension is a type of Class that is a set that is defined by enumerating the members.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Component_upper_level_identification is a type of Assembly_component_relationship. It identifies a component of an assembly
with respect to an upper level in the assembly structure.
NOTE: A Component_upper_level_identification does not add a component in an assembly, it provides a means to further characterize
a component with respect to an upper level assembly.
EXAMPLE: A Component_upper_level_identification may be used to assign a property to a component that applies in the context
of a particular upper level assembly.
The identified component is the version of product, indirectly referred to as the View_definition_relationship.related_view of
the sub_assembly_relationship. The upper level assembly is the version of product, indirectly referred to as the View_definition_relationship.relating_view of
the upper_assembly_relationship.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Composition_of_state is a type 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:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Composition_of_state_definition is a type of State_definition_relationship. It relates State_definition entities to one
another, when two or more State_definition entities act as parts to compose a whole State_definition, and furthermore, whole State_definition entities
can become parts of yet another whole State_definition.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Concurrent_elements is a type of Structured_task_element that comprises a set of actions to be performed during the time
required for the longest task. No specific order is required.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Condition is a definition of the precedent that must be fulfilled before a statement or relationship becomes valid.
NOTE: The condition is defined as a text based expression that is represented by the description attribute.
The parameters against which the condition is to be evaluated are identified by Condition_parameter. The target or consequence
of a condition is represented by Condition_assignment.
EXAMPLE: "If the engine has been running for 10000 hours then it requires a service" is an example of a conditional statement.
The conditional part of the statement is "If the engine has been running for 10000 hours" which is stored in definition attribute
on Condition. The parameter or subject of the condition is "the engine" which is represented by a Condition_parameter identifying
the Product_as_realized which represents the engine. The consequence of the condition is "then it requires a service". This
is represented by Condition_assignment identifying the task to perform the service, a Task_method.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Condition_assignment is a relationship that identifies the statement or relationship to which a Condition applies.
EXAMPLE: 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:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Condition_evaluation is a record of the evaluation of a Condition and the subsequent result.
EXAMPLE: 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 Condition_evaluation. 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:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Condition_evaluation_assignment is a relationship that identifies the statement or relationship to which the Condition_evaluation applies.
EXAMPLE: The Condition_evaluation (instance 87) is assigned to the activity of checking the oil level on car VIN 12345678.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Condition_evaluation_parameter is an identification of the product or activity data used in the evaluation of the Condition identified
by the Condition_evaluation.
EXAMPLE: The measured value of oil pressure from gauge 3 on car with VIN 12345678 (value = 1.9 bar).
NOTE: The product or activity data is defined in condition_evaluation_parameter_item. The contents of this select type are
defined in application modules that use this module.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Condition_parameter is a represention of the product or activity data that is used to specify a Condition.
EXAMPLE: Oil pressure on gauge 3.
NOTE: The product or activity data is defined in condition_parameter_item. The contents of this select type are defined in
application modules that use this module.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Condition_relationship is a relation between two conditions.
NOTE: The Condition_relationship normally represents a logical combination of conditions. The logical type is identified by
the classification of the Condition_relationship by a Classification_assignment.
EXAMPLE: "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:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Content_item is a reference to any item that can be referenced as part of the message content.
NOTE: As well as externally defined items such as drawings, photographs, and so on, a message can refer to any entity represented
in the schema it is used in, from products to property values, or actions to task steps. The mechanism used gives no interpretation
of how the Content_item.item_identifier is interpreted or how the data is accessed. For example, the identifier could be the
number of the entity in a file that conforms to ISO 10303-21. Interpretation of this entity and its attributes may be defined
through reference data.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Context_dependent_unit is a type of Unit that is not related to the system of units defined in this part of ISO 10303.
EXAMPLE: The number of parts in an assembly is a physical quantity that may be measured in a unit called 'parts'. Such a unit
cannot be related to an SI unit.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Contextual_item_shape is a type of Item_shape 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 View_definition_relationship.related_view of the View_definition_usage.
EXAMPLE: Flexible part may have several shapes, each associated with a particular occurrence of the part in assemblies.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Contract is a binding agreement.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Contract_assignment is an association of a Contract with activity or product data.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Conversion_based_unit is a type of Unit that that is based on another and related by a conversion factor.
NOTE: A Conversion_based_unit is often used to convert a unit in one system of units to a similar unit in another system.
EXAMPLE: An Imperial inch is 25.4 millimetres
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Date_or_date_time_assignment is an association of a Calendar_date or a Date_time with activity or product data.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Date_time is a time on a particular day.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Dated_effectivity is a type of Effectivity for which the domain of applicability is defined as an interval of time bounded
by dates or events. The interval may be open-ended.
EXAMPLE: Events may be used to bound a Dated_effectivity period, at planning phase.
Depending on whether the Dated_effectivity.end_bound attribute is specified, the actual domain of time defined by a Dated_effectivity is:
* either, the time interval between the start and end date or event;
* or, the open time interval that starts at the start date or event. If the Dated_effectivity.end_bound is an event that actually
identifies a point in time that comes before the Dated_effectivity.start_bound, then the actual domain of effectivity is empty.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Decision_point is a type of Structured_task_element. It requires a decision that determines which further Task_element is
to be followed.
NOTE: The condition on which the decision is based optionally allows a further Task_element to be invoked to provide the basis
for the decision.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Decreasing_resource_event is a type of Resource_event that decreases the balance of a managed resource.
EXAMPLE: Filling a requisition reduces an inventory.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Defined_state_relationship is a relationship that links a State_assertion to a State_assessment.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Derived_unit is a type of Unit that is defined by an expression of other units.
EXAMPLE: Newtons per square metre is a derived unit.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Descriptive_document_property is a type of String_representation_item that specifies a text based characteristics of a Document_definition or
of a File.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Detailed_geometric_model_element is a type of Representation_item. It identifies a geometric construct. Only non abstract
specializations of the Detailed_geometric_model_element entity data type can be instantiated.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Digital_document_definition is a type of Document_definition. It identifies a collection of files that are archived on an
optical computer disc, magnetic, electronic storage, or a combination thereof. A digital document definition may consist of
one or many component digital files.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Digital_file is a type of File. A Digital_file contains computer interpretable data and is stored on an electronic device.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Directed_activity is a type of Activity. It identifies an actvity that is governed by a Work_order.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Direction is a type of Detailed_geometric_model_element that defines a 2 or 3 dimensional vector.
NOTE: A Direction is not located in a geometric space but is used in the definition of geometric entities like Axis_placement.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Distribution_by_value is a type of Probability_distribution that explicitly lists pairs of random variable values and function
values.
NOTE: Distribution_by_value 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:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Document is a type of Product used to identify documentation data that is under configuration change management.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Document_assignment is a mechanism to associate a document with product data, where the assigned document provides information
about the data with which it is associated.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Document_definition is a type of Product_view_definition that is a Document_version in a particular format.
NOTE: A Document_version may have more than one representation.
EXAMPLE: A version of a logical document, which contains a shape model, may be represented in the native formats of different
CAD systems.
Each Document_definition is a Digital_document_definition or a Physical_document_definition.
NOTE: Aspects of the representation may not be known at the time the identification is established.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Document_definition_relationship is a relationship between two instances of Document_definition.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Document_location_identification is a type of External_source_identification that identifies the location of the components
of a Document_definition in an external storage system where they can be found.
EXAMPLE: An HTML file that includes a picture may be represented as a Document_definition made of two components:
* the HTML file;
* the binary file that contains the picture. If these files were located within the same directory or relatively to the same
directory, the External_source_identification.source_id attribute would convey the directory name.
EXAMPLE: Examples of External_source_identification.source_type are:
* 'URL' - for a web page;
* 'FTP' - for an FTP address;
* 'ISBN' - for physical documents.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Document_property_representation is a type of Representation that conveys the parameters of a particular aspect of an Assigned_document_property. Where
applicable, the following values shall be used for the inherited name attribute of the Document_property_representation :
* 'document content': a category of parameters that precise characteristics of the data contained in a document definition
or in a file;
* 'document creation': a category of parameters that detail the context of creation of a document definition or file;
* 'document format': a category of parameters that describe the format of a document definition or of a file;
* 'document size': a category of parameters that detail the size of a document definition or of a file. The following characteristics
may be items of a Document_property_representation with name 'document content':
* A Descriptive_document_property with name 'detail level' specifying the level of detail that is provided;
EXAMPLE: An example value for the 'detail level' property is 'rough 3d shape' - a 3D shape model without edge rounds and fillets.
* A Descriptive_document_property with name 'geometry type' specifying the kind or kinds of geometry that is contained;
EXAMPLE: examples of geometry type are: '3D wireframe model', '2D shape', 'surface model', 'closed volume', 'solid model',
'solid and surface model', '2D drawing'.
* A Descriptive_document_property with name 'real world scale' specifying a text representation of the scale used. The following
characteristics shall be an item of a Document_property_representation with name 'document creation':
* A Descriptive_document_property with name 'creating system' specifying the name of the computer application or the machine
that was used to generate the document definition or the file. The following characteristics may be items of a Document_property_representation with
name 'document creation':
* A Descriptive_document_property with name 'operating system' specifying the name of the operating system that was used;
* A Descriptive_document_property with name 'creating interface' specifying the name of the computer application used.
EXAMPLE: An example value for the 'creating interface' property is 'Postscript Printer Driver' indicating that a Postscript
Printer Driver was used to print a hardcopy.
The following characteristics may be items of a Document_property_representation with name 'document format':
* A Descriptive_document_property with name 'data format' specifying the name of the standard that defines the data structure
used. Where applicable the following values shall be used: 'DXF', 'IGES', 'ISO 10303-203', 'ISO 10303-214', 'TIFF CCITT GR4','VDAFS','VOXEL';
* A Descriptive_document_property with name 'character code' specifying the character code used. Where applicable the following
values shall be used: 'US ASCII 7bit', 'ISO 646', 'ISO 8859-1', 'EBCDIC', 'binary';
* A Descriptive_document_property with name 'size format standard' specifying the standard size used.
EXAMPLE: 'A0' and 'A4' are examples of standard sizes of paper sheets.
The following characteristics may be items of a Document_property_representation with name 'document size':
* A Numerical_document_property with name 'page count' specifying the number of pages in a Physical_document_definition or
a Hardcopy;
* A Numerical_document_property with name 'file size' specifying the size of a digital file or of a Digital_document_definition.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Document_version is a type of Product_version A Document_version identifies a particular version of a document.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Duration is a type of Value_with_unit that defines the magnitude of a time interval.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Effectivity is the identification of a domain of applicability.
NOTE: Instances of Effectivity may be applied to any kind of product or activity data, using the constructs defined in the Effectivity
application module.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Effectivity_assignment is the association of an Effectivity with product or activity data.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Effectivity_relationship is an association between two instances of Effectivity. The meaning of the relationship is represented
with the relation_type attribute.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Electric_current_unit is a type of Unit with which movement of electrically charged particles is expressed.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Element_constraint is a type of Task_element_relationship that signifies a constraint between Task_element s. The constraint
may only apply within the context of a Task_method or Task_element, specified as the context.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An End_task is a type of Task_element. It signifies a point at which to end the task.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Envelope is an historical record of the transmission of a Message. It 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:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Envelope_relationship is an association of one Envelope with another.
NOTE: The most obvious use of the association is to link an Envelope to its acknowledgements.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Event is the fact of the existence of a state at some point in time.
NOTE: The event may have occurred or may be not yet started.
NOTE: The point in time where an event will start or started, may not be known or specified.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Event_assignment is assignment of an Event to product or activity data.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Event_relationship is a relationship which exists between two Event s.
EXAMPLE: An instance of this entity data type with Event_relationship.relation_type 'sequence' may be used to specify that
an event shall end before another event starts.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Exit_loop is a type of Structured_task_element. It signifies a point at which to exit from a loop.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Experience_gained is a relationship between an Experience_instance and a person or organization.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Experience_instance is a particular eposide of contact with and/or observation of facts or events which contributes to
the accumulation of knowledge or skill.
EXAMPLE: Changing the exhaust system on a car.
EXAMPLE: 2 years work on same type of milling machine.
EXAMPLE: 100 flying hours in a Tornado jet.
EXAMPLE: 5 years as Workshop Manager.
The nature, duration and worth of the Experience_instance can be described using assigned properties or by referring to activities
or tasks.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Experience_type is a category or class of experience.
EXAMPLE: welding
EXAMPLE: mechanical design
EXAMPLE: flying
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An External_class is a type of Class that represents a reference to a class that is not included in the data exchange file
and is defined in an external class library.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An External_class_library is the identification of an external class library.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An External_geometric_model is a type of 3D Geometric_model whose content is provided in an external file. The set of items
of the External_geometric_model contains only one element that shall be an Axis_placement. This Axis_placement specifies the
reference location and orientation with respect to which placement of the External_geometric_model in other Geometric_model s
shall be defined.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An External_item_identification is a type of External_source_identification that provides the identifier of an item in the
context of an external source where it can be found.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An External_source_identification is the identification of the source where an item, or the components of an item, can be
found.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A File_location_identification is a type of External_item_identification that identifies the location of a File in an external
storage system where it can be found.
EXAMPLE: For a computer file identified by a filename and directory path, for example 'D:\project1\specification.txt', the External_item_identification.external_id attribute
represents the filename, 'specification.txt' and the External_source_identification.source_id attribute represents the path
name, 'D:\project1\'.
EXAMPLE: Examples of External_source_identification.source_type are:
* 'URL' - for a web page;
* 'FTP' - for an FTP address;
* 'ISBN' - for physical documents.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A File_relationship is a relationship between two instances of File.
EXAMPLE: A service manual may contain graphics for explanatory reasons. In this case, the File objects that contain the graphics
are referenced as related from the File object that contains the body of the service manual with Document_definition_relationship.relation_type 'reference'.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Functional_breakdown is a type of Breakdown that identifies a partitioning of a product into a set of related functional
elements so as to form explicit structural views that comprise the product elements. The composite - component view is represented
by Functional_element_usage instances relating the functional elements in the breakdown which are represented by Functional_element s.
EXAMPLE: A functional breakdown provides a decomposition of an aircraft in terms of high-level functional processes such as
flight, taxiing and at rest all the way down to low-level processes such as detect onboard fuel level, move tail rudder and
provide standard tow attachment point.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Functional_breakdown_context is a type of Breakdown_context that is an association of a Functional_element to a Functional_breakdown of
which the functional element is a member.
EXAMPLE: A function 'provide load lifting capability' is member of the functional breakdown of a helicopter.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Functional_breakdown_version is a type of Breakdown_version that identifies a version of a Functional_breakdown.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Functional_element is a type of Breakdown_element that identifies the elements in one or more Functional_breakdown objects.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Functional_element_definition is a type of Breakdown_element_definition that identifies a view of a version ( Functional_element_version )
of a Functional_element.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Functional_element_usage is a type of Breakdown_element_usage that is an association of a functional element to another
functional element that is a constituent. Functional_element.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Functional_element_version is a type of Breakdown_element_version that identifies a version of a Functional_element.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Geometric_coordinate_space is a type of Numerical_representation_context that defines a coordinate space where geometric
elements can be defined. It is either two-dimensional or three-dimensional. There shall be at least two units specified for
the Geometric_coordinate_space : one length unit and one plane angle unit. The length unit applies to each coordinate direction.
EXAMPLE: The length unit millimetre and the angle unit radian are examples of units that may assigned to a Geometric_coordinate_space.
NOTE: The origin for coordinate values is implicitly defined as being the cartesian point whose coordinates are all zero.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Geometric_model is a type of Representation dedicated to the description of geometric constructs. The Geometric_model is
founded in a Geometric_coordinate_space. The items of a Geometric_model are instances of Detailed_geometric_model_element.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Global_location_representation is a type of Location_representation specified using geographic means in the global system
and values, which could be physical or political geographic values.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Hardcopy is a type of File that represents a non-digital document.
EXAMPLE: An actual stack of paper consisting of one or more sheets, on which some product data is written, printed or plotted.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Hierarchical_interface_connection is a type of Interface_connection that provides an interconnection between components
at different levels in an assembly. Each connection point in the assembly is represented by a Interface_connector_occurrence.
EXAMPLE: 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 Interface_connector_occurrence and an instance of the Hierarchical_interface_connection entity data type identifies the
connection of the pins (the parts) to the plug (the assembly) in the assembly.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Hybrid_breakdown is a type of Breakdown that identifies a non-specific partitioning of a product into a set of related elements
so as to form explicit, parent-child views that comprise the elements. The parent-child view is represented by Hybrid_element_usage instances
relating the elements in the hybrid breakdown which are represented by types of Breakdown_element s.
EXAMPLE: A product breakdown in which a 'climate control' function has a decomposition that comprises a 'heating function'
and a 'cooling function' and in which the 'heating function' has a decomposition that comprises a 'heating element' and a
'heat distribution system' would be an example of a 'hybrid breakdown'.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Hybrid_breakdown_context is a type of Breakdown_context that is a relationship between a Breakdown_element and a Hybrid_breakdown of
which the hybrid element is a member.
EXAMPLE: A 'pipe element' might be a member of a 'heating function' breakdown in a hybrid decomposition.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Hybrid_breakdown_version is a type of Breakdown_version that identifies a version of a Hybrid_breakdown.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Hybrid_element_usage is a type of Breakdown_element_usage that identifies a relationship between a parent and child Breakdown_element where
the parent and child elements may be different subtypes of Breakdown_element.
EXAMPLE: In a hybrid breakdown, the 'fuel system' might include a 'tank element' and a 'fuel-injection element' as components.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Identification_assignment is the assignment of an identifier to product or activity data.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An In_zone is a relationship between a Zone_element and an item that exists within the zone.
EXAMPLE: A pump is in the starboard engine room of a ship.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Increasing_resource_event is a type of Resource_event that increases the balance of a managed resource.
EXAMPLE: Purchasing new stock increases an inventory.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Independent_property is a type of property.
NOTE: It is independent of its application to characterize a product or an activity.
EXAMPLE: The physical property kinematic viscosity, defined in ISO 31, is an example of Independent_property.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Independent_property_relationship is a relationship between two instances of Independent_property.
EXAMPLE: An Independent_property_relationship may be used to indicate that the values of a Independent_property can be derived
from the another Independent_property.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Independent_property_representation is the association of an Independent_property with a Representation.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Information_right is a definition what may or may not be done with an item of information in the sense of legal rights
and obligations.
EXAMPLE: Copyright is an Information_right.
EXAMPLE: 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:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Information_usage_right is an application an Information_right to a particular usage context.
NOTE: One view of the distinction between an Information_right and an Information_usage_right is that the Information_right represents
a standard clause in a contract, whereas an Information_usage_right represents the fact that the clause is used in a particular
contract.
NOTE: 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.
NOTE: The Approval of an Information_usage_right carries the meaning that the right is granted to all information items in
the relevant context, as opposed to the approval of an Applied_information_usage_right which is limited to particular items.
NOTE: Information_usage_right 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
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Information_usage_right_relationship is the relationship of one Information_usage_right to another.
EXAMPLE: Where one Information_usage_right supercedes another, then the original right is pointed to by the relating attribute,
its replacement by the related attribute, and the relation_type attribute takes the value "supercedes".
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Interface_connection is an interconnection between a connected pair of Interface_connector_occurrence s. Each Interface_connector_occurrence represents
the place where a product used in an assembly can interact with other products in the assembly.
EXAMPLE: 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 Interface_connector_occurrence and an instance of the Interface_connection entity data type identifies the connection
of the pins to the wires in the assembly.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Interface_connector is a type of Product that identifies a part of a product with which one or more other products or the
environment interacts.
NOTE: This is sometimes referred to as a "port".
EXAMPLE: A computer has a socket to which to connect a network cable. An instance of the Interface_connector 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:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Interface_connector_as_planned is a type of Interface_connector_version that identifies an individual that is the subject
of a plan to realize an Interface_connector.
EXAMPLE: 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:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Interface_connector_as_realized is a type of Interface_connector_version that identifies an individual that is a realized Interface_connector.
EXAMPLE: 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:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Interface_connector_definition is a type of Product_view_definition that identifies a view of an Interface_connector.
EXAMPLE: 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 Interface_connector_definition entity data type collects these data together.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Interface_connector_design is a type of Interface_connector_version that identifies a design version of an Interface_connector.
EXAMPLE: BuildAWidget Incorporated creates design version 2.10 for an electrical supply connector.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Interface_connector_design_to_planned is a relationship between a design version of an Interface_connector and a planned
individual that is to conform to the design.
EXAMPLE: BuildAWidget Incorporated plans production of pump serial number 30301 with an electrical supply connector that is
to conform to design version 2.10.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Interface_connector_design_to_realized is a relationship between a design version of an Interface_connector and a realized
individual that conforms to the design.
EXAMPLE: BuildAWidget Incorporated builds pump serial number 30301 with an electrical supply connector that conforms to design
version 2.11.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Interface_connector_occurrence is an occurrence of a Interface_connector_definition. The Interface_connector_occurrence represents
the place where a product used in an assembly can interact with other products in the assembly. The interaction is represented
by a Interface_connection.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Interface_connector_planned_to_realized is a relationship between a realized individual of an Interface_connector and a
corresponding planned individual.
EXAMPLE: BuildAWidget Incorporated builds pump serial number 30302 with an electrical supply connector that was previously
planned.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Interface_connector_version is a type of Product_version that identifies a version of an Interface_connector.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Interface_definition_connection is an interconnection between a connected pair of Interface_connector_definition s or, if
the point of interconnection is not specified, the interconnection between a pair of views ( Product_view_definition s) on
products
EXAMPLE: 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 Interface_definition_connection entity data type identifies
this fitting of the plug into the socket.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Interface_definition_for is a relationship between an Interface_specification and an item that conforms to the specification.
EXAMPLE: The infrared transmitter in a television remote control conforms to the specification that has the identifier 2345/XYZ/001.
An instance of the Interface_definition_for entity data type is necessary to identify this relationship.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Interface_specification is a type of Product that provides a definition of necessary attributes for one or more items that
participate in an interface.
EXAMPLE: BSI develops a standard for connecting domestic electrical equipment to the electricity supply.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Interface_specification_definition is a type of Product_view_definition that provides a view of an Interface_specification.
EXAMPLE: 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:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Interface_specification_version is a type of Product_version that identifies a version of an Interface_specification.
EXAMPLE: In 1999, BSI issues a new version of a standard for connecting domestic electrical equipment to the electricity supply.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Item_design_association is the association of a Product_configuration with a Product_view_definition or a Product_version.
It specifies the design that corresponds to the Product_configuration. If the design is a Product_view_definition, the Item_design_association represents
the statement that, in the considered definition context, the product version, that is, the Product_view_definition is a valid
way to implement the Product_configuration.
NOTE: This association might not be valid in all definition contexts of the product version.
If the design is a Product_version, the Item_design_association represents the statement that, in all definition contexts,
the Product_version is a valid way to implement the Product_configuration.
NOTE: The association might not be valid for other versions of the product.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Item_shape is the shape of shapeable_item.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Item_usage_effectivity is an effectivity domain that constrains the use of a product with or within another product, in
the context of a Product_configuration. The effectivity_domain attribute identifies a domain of effectivity. The item_usage_relationship attribute
identifies a relationship which characterizes the use of the product with or within another product.
EXAMPLE: This relationship may be an assembly-component relationship or a make-from relationship.
The resolved_configuration attribute identifies an association between a Product_configuration and a product that implements
it. This attribute establishes the context in which the item_usage_relationship is considered and constrained. When the effectivity
domain is a range of serial numbers, the serial numbers considered are those of the Product_configuration. When the effectivity
domain is defined using a production lot number, the production lot considered is one of the Product_configuration. When the
effectivity domain is an interval of time, the interval of time considered is related to the production of the Product_configuration.
NOTE: When no effectivity constraint is applied to a View_definition_usage, the validity or applicability status of this View_definition_usage is
unknown.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Justification is the identification and description of the reasons for something. Justification entities may be associated
with the data to which they apply.
EXAMPLE: 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:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Justification_assignment is the association between a Justification and the item for which the Justification is provided.
EXAMPLE: The item can be an activity or a product design.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Justification_relationship is an association between two Justification s.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Justification_support_assignment is the association between a Justification and the item providing evidential support for
the Justification.
EXAMPLE: The support item can be the results from an analysis, a report, or professional judgment.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Language is 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.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Language_indication is the identification of the Language in which a text attribute of one or more instances has been specified.
NOTE: The Language_indication entity data type identifies the primary language of a text attribute while the Attribute_translation_assignment entity
data type enables to convey the translations of that attribute in various languages.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Length_unit is a type of Unit in which distances are expressed.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Local_time is a point in time in a day, represented on a 24-hour clock by hour, minute and second. It is expressed in the
local time zone and the offset from the Coordinate Universal Time shall be specified.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Location is a place or position where an activity or event can occur or a product or resource can exist.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Location_assignment 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:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Location_relationship is a relationship between two locations.
EXAMPLE: Location B, which is in reference to location A or Location B (UK), which is a refinement of Location A (Europe).
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Location_representation is a means of representing a location.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Looping_element is a type of Task_element. It invokes a specified number of repetitions of a further Task_element.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Lot_effectivity is a type of Effectivity for which the domain of applicability is defined as a given batch of items.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Luminous_intensity_unit is a type of Unit in which the brightness of a body is expressed.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Make_from_relationship is a type of View_definition_usage established between two instances of Part_view_definition. 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.
NOTE: The related part version may identify a raw material or a semi-finished part.
NOTE: The characteization of the process of transformation from the related part version to the relating part version it out
of the scope of this application module.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Managed_resource is a representation of a resource that is provided with resource management capabilities. The role of a
managed resource is determined by classification.
EXAMPLE: A managed resource can be classified as "Stock line".
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Managed_resource_relationship is an association between two managed resources. The meaning of the relationship is determined
by classification.
EXAMPLE: A managed resource relationship can be classified as "Alternative" or "Prefered".
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Mapping_based_template_instance is a type of Detailed_geometric_model_element. It is the replication of a Geometric_model.
The replication transformation is defined by a Mapping_based_template_instance.source Axis_placement and a Mapping_based_template_instance.target that
may be an Axis_placement or a cartesian_transformation. In the first case, the transformation shall be computed as the isometric
transformation that maps:
* the Axis_placement.origin of the Mapping_based_template_instance.source onto the Axis_placement.origin of the Mapping_based_template_instance.target,
* the Axis_placement.x_axis of the Mapping_based_template_instance.source onto the Axis_placement.x_axis of the Mapping_based_template_instance.target,
* the Axis_placement.y_axis of the Mapping_based_template_instance.source onto the Axis_placement.y_axis of the Mapping_based_template_instance.target. In
the second case, the transformation shall be computed as the transformation that maps:
* the Axis_placement.origin of the Mapping_based_template_instance.source onto the translation point of the Mapping_based_template_instance.target,
* the Axis_placement.x_axis of the Mapping_based_template_instance.source onto the first element of the Mapping_based_template_instance.target of
the Axis_placement_mapping.target,
* the Axis_placement.y_axis of the Mapping_based_template_instance.source onto the second element of the Cartesian_transformation_2d.multiplication_matrix of
the Axis_placement_mapping.target,
* in case the transformation is a 3D transformation, the normalised vector product of the Axis_placement.x_axis and the Axis_placement.y_axis of
the Mapping_based_template_instance.source onto the third element of the Cartesian_transformation_2d.multiplication_matrix of
the Mapping_based_template_instance.target.
NOTE: In the case where the Geometric_coordinate_space of the replicated model is not the same as the Geometric_coordinate_space in
which the template_instance is founded, care shall be taken of any difference in the length units of both the instances of Geometric_coordinate_space,
as unit conversion may be required.
EXAMPLE: In a technical drawing of a mechanical part with several identical drilling holes, the hole geometry, is represented
by a circle named 'annotated drilling hole'. This representation of the hole is replicated several times at different locations
by corresponding template_instance objects.
NOTE: The mapping-table defines two interpretations for this ARM entity. The first one uses the MIM entity mapped_item which
uses the same principle to define the transformation as the Axis_placement_mapping and Axis_placement_transformation_mapping entities.
The second one uses the MIM entity representation_relationship_with_transformation. Although this latter entity is not semantically
equivalent to the ARM entity, the second interpretation is kept because of its use in some implementations.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Market is the identification of a marketing segment for products.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Mass_unit is a type of Unit with which mass is expressed.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Measure_item is a type of Representation_item that conveys the value of a quantity. Only specializations of this entity
can be instantiated.
CLASS
Measure_item;
SUBCLASS OF (
Representation_item
);
SUPERCLASS OF (
Value_with_tolerances,
Value_list,
Measure_item_with_precision,
Numerical_item_with_global_unit,
Value_set,
Value_range,
Value_range_with_global_unit,
Value_limit,
Value_limit_with_global_unit,
Numerical_item_with_unit,
);
END_CLASS;
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Measure_item_with_precision is a type of Measure_item that has a precision defined as the number of digits that are significant.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Message is a collection of information, brought together by an originator (the message definer) for some particular purpose,
generally the fulfillment of a process. A Message is an historical record, intended to be sent using an Envelope and in consequence,
is not versioned.
NOTE: 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:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Message_relationship is a link between two related messages. The meaning of the association depends on Message_relationship.role.
EXAMPLE: If Message.id =2 replaces Message.id =1, then Message_relationship.related points to Message.id =2 and Message_relationship.relating points
to Message.id =1 with Message_relationship.role ="replaces".
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Next_assembly_usage is a type of Assembly_component_relationship. It establishes a relationship between a component and
its immediate parent assembly in a product structure.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Numerical_document_property is a type of Numerical_item_with_unit that specifies a numerical characteristic of a Document_definition or
of a File.
EXAMPLE: The size of a digital file expressed in Megabytes is an example of Numerical_document_property.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Numerical_item_with_global_unit is a type of Measure_item where the value is expressed with respect to a unit provided as
a global information associated with the representation context.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Numerical_item_with_unit is a type of Measure_item that is also a Value_with_unit. The quantity value is therefore provided
with its own unit.
NOTE: A unit that is specified by Numerical_item_with_unit supersedes a unit associated with the Numerical_representation_context.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Numerical_representation_context is a type of Representation_context in which units and uncertainties may be defined. These
units and uncertainties apply to the instances of Representation_item that are used in that context.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Observation is an historical record of something that has occured during the life of a product or its support environment.
Its use is restricted to observations not directly represented in the data model, and should not be used where some other
reporting data structure is defined.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Observation_consequence is an association of an observation to the consequences that follow from it, where those consequences
are in the form of a Work_request.
NOTE: One of the uses of Observation_consequence is to close one of the feedback loops from the use of a product to requests
for its enhancements.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Observation_item is a reference to any item that an observation can be made about, or any item that can be used as part
of the observation.
NOTE: An observation can refer to any entity represented in the schema it is used in, from products to property values, or
actions to task steps. The mechanism used gives no interpretation of how the Observation_item.item_identifier is interpreted
or how the data is accessed. For example, the identifier could be the number of the entity in a file conforming to ISO-10303-21.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Observation_relationship is a 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 Observation_relationship against reference data.
EXAMPLE: The Observation of a persistant fault is composed of a series of Observation of occurances of the same fault. That
is, Observation_relationship.related points to the composite Observation, while Observation_relationship.relating points to
one actual Observation of the occurance. The Observation_relationship.role of the relationship is "observed instance", while
it is classified as "is composed of". In this example, the component Observation will apply to Product_as_realized and the
consequence will be to rectify the individual faults, while the composite Observation will apply to a Product_version and
the consequence will be a design change.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Or_state_cause_effect_definition is a type of State_cause_effect_definition. It relates one or more State_definition entities
that are causes to a State_definition that is the effect. At least one cause must exist prior to the effect.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Organization is an administrative structure in which persons are active.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Organization_based_location_representation is a type of Location_representation that specifies a location in the context
of an organization.
EXAMPLE: The location "Room 99" in "The Administration Building" of a particular university might be represented using one
instance of Organization_based_location_representation with two instances of Organizational_location_identification and one
instance of Organization.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Organization_or_person_in_organization_assignment is an association of an organization or a person in an organization with
activity or product data.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Organization_relationship is a relationship between two instances of Organization.
EXAMPLE: A team belongs to a department which itself belongs to a company. Such an organizational structure can be described
up using instances of Organization_relationship.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Organization_type is a recognized kind of Organization.
EXAMPLE: legal entity
EXAMPLE: change control board
EXAMPLE: sales organization
EXAMPLE: manufacturing organization
EXAMPLE: department
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Organizational_location_identification is location that is defined by an identification which is specific in an organization
context.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Parameterized_distribution is a type of Probability_distribution that is used to link a named probability distribution to
the parameters that define it.
NOTE: The Parameterized_distribution.parameterization_name of this entity is used to discriminate between alternative parameterizations
of the same distribution.
NOTE: To calculate a value using a Parameterized_distribution 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 Probability_derivation_parameter in the Probability module (see note 2).
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Part is a type of Product that collects the definitional information of the versions of either a part or of a non-countable
material.
NOTE: A Part does not represent an actual physical object that is or was existing in the real world.
NOTE: A complex instance of the Part entity and of the Document entity may be created in order to represent a document that
is a component of a manufactured product, for example a user manual of a car.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Part_version is a type of Product_version that identifies a version of a part. A Part_version serves as the collector of
the data characterizing a realizable object in various application contexts.
NOTE: A Part_version is expected to be functionally and physically interchangeable with the other versions of the same Part.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Part_view_definition is a type of Product_view_definition that defines a characterization view of a version of a Part.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Partial_document_assignment is a type of Document_assignment. A Partial_document_assignment identifies a specific portion
of the contents of a document. It assigns this portion to the product data for which it is relevant.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Person is an individual human being.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Person_in_organization is the identification of a Person and of his role in an Organization
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Person_or_organization_or_person_in_organization_in_position is a Person, Organization, or Person_in_organization that holds
a Position. A person may hold more than one position within an organization or organizations.
EXAMPLE: A person can hold two positions in an organization: Production Manager and Safety Officer.
A position in an organization can be held by more than one person or organization.
EXAMPLE: Two people can hold the same position in a job-share scheme.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Person_or_organization_or_person_in_organization_in_position_relationship is a relationship between one Organization, Person,
or Person_in_organization and another. Examples of the relationship are
EXAMPLE: successor
EXAMPLE: job-share
NOTE: The meaning of the relationship is determined by classification
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Physical_breakdown is a type of Breakdown that identifies a partitioning of a product into a set of related physical elements
so as to form explicit, parent-child views that comprise the product elements. The parent-child view is represented by Physical_element_usage instances
relating the physical elements in the breakdown which are represented by Physical_element s.
EXAMPLE: A physical breakdown might provide a decomposition of an automobile in terms such as body, roof, bonnet, bumpers
and this breakdown might be differerent from, and orthogonal to, a parts decomposition.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Physical_breakdown_context is a type of Breakdown_context that is a membership relationship between a Physical_element and
a Physical_breakdown of which the physical element is a member.
EXAMPLE: A wheel is a member of the physical breakdown of an automobile.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Physical_breakdown_version is a type of Breakdown_version that identifies a version of a Physical_breakdown.
EXAMPLE: An engineer modifies the current physical breakdown for an aircraft on the basis of a tail re-design.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Physical_document_definition is a type of Document_definition. A physical document definition may consist of one or many
component hardcopy files.
EXAMPLE: Paper plots of technical drawings, micro fiche, or paper documents such as calculations or test reports are examples
of Physical_document_definition.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Physical_element is a type of Breakdown_element that identifies the elements in one or more Physical_breakdown objects.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Physical_element_definition is a type of Breakdown_element_definition that identifies a view of a version ( Physical_element_version )
of a Physical_element.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Physical_element_usage is a type of Breakdown_element_usage that is a relationship between a parent and child Physical_element.
EXAMPLE: In a physical breakdown, the aircraft (parent) might include (as children) a fuselage, wings, tail and undercarriage.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Physical_element_version is a type of Breakdown_element_version that identifies a version of a Physical_element.
EXAMPLE: An engineer changes the details describing the undercarriage that is an element in a physical breakdown of an aircraft.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Plane_angle_unit is a type of Unit by which a angles in planes are expressed.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
CLASS
PLCS-ARM-LF-THING;
SUPERCLASS OF (
Project_assignment,
Approval_relationship,
Organization,
Requirement_source,
Representation,
Condition,
Message_relationship,
Interface_connector_design_to_realized,
Observation,
State_definition,
Information_usage_right,
Condition_evaluation_assignment,
Interface_connector_planned_to_realized,
Product_view_definition,
Applied_activity_assignment,
Approval_status,
Justification_support_assignment,
Position_type_assignment,
Information_usage_right_relationship,
Resource_property_representation,
Effectivity_relationship,
Observation_relationship,
Related_condition_parameter,
Product_planned_to_realized,
Unit,
Position_position_type_assignment,
Attribute_translation_assignment,
Product_design_to_individual,
Alternate_part_relationship,
Applied_state_definition_assignment,
Work_request_status,
Contract_assignment,
Product,
Effectivity,
Breakdown_context,
Effectivity_assignment,
Independent_property,
Location,
Defined_state_relationship,
Condition_relationship,
Location_representation,
Condition_parameter,
Activity_method_realization,
Activity_method,
Item_design_association,
Independent_property_relationship,
Representation_context,
Attachment_slot_design_to_planned,
Requirement_assignment,
Security_classification,
Interface_definition_for,
Activity_method_relationship,
Digital_file,
State_relationship,
Event_relationship,
Experience_gained,
Representation_relationship,
Required_resource_relationship,
Interface_connector_occurrence,
Work_output_assignment,
Work_output,
Type_of_person_assignment,
State_definition_relationship,
Activity_relationship,
Certification,
Task_element_state_relationship,
Approving_person_organization,
Position_assignment,
Product_group_membership,
Resource_item_assignment,
Envelope_relationship,
Item_usage_effectivity,
Local_time,
Contract,
Task_method_state_relationship,
Product_design_version_to_individual,
Required_resource_assignment,
Condition_evaluation,
Activity_method_realization_relationship,
Applied_state_assignment,
Selected_item_assignment,
Message,
Representation_item,
Position_relationship,
Content_item,
Project_relationship,
Product_concept,
Address_assignment,
Attachment_slot_planned_to_realized,
Resource_item_relationship,
State,
Breakdown_of,
Interface_connector_design_to_planned,
Location_relationship,
Activity_status,
Activity_property_representation,
Time_interval_relationship,
Affected_items_assignment,
Certification_assignment,
Task_objective,
Product_relationship,
Activity_property,
Project,
Value_with_unit,
Breakdown_element_realization,
Organization_relationship,
Type_of_person_definition_required_attributes_relationship,
Experience_instance,
Work_order,
Attachment_slot_on_product,
Interface_connection,
View_definition_relationship,
Date_or_date_time_assignment,
Person_or_organization_or_person_in_organization_in_position,
Calendar_date,
Type_of_person,
Location_assignment,
Product_group,
Resource_item,
Position,
Managed_resource,
Required_resource,
Managed_resource_relationship,
Applied_information_usage_right,
Qualification_assignment,
Type_of_person_definition,
Product_version_relationship,
Security_classification_assignment,
In_zone,
Language_indication,
Market,
Product_version,
Information_right,
Observation_consequence,
Regional_coordinate,
Resource_as_realized,
Position_group,
Date_time,
Work_request,
Approval_assignment,
Product_category,
Event_assignment,
Independent_property_representation,
Person_or_organization_or_person_in_organization_in_position_relationship,
Task_objective_state_relationship,
Language,
Property_representation,
Resource_as_realized_assignment,
Justification_relationship,
Assembly_relationship_substitution,
File_relationship,
Interface_definition_connection,
Justification_assignment,
Person,
Class,
State_assertion,
Qualification_type,
Product_group_relationship,
Approval,
View_definition_context,
Qualification_type_relationship,
Work_output_relationship,
Resource_property,
Resource_event_correspondence_relationship,
External_class_library,
Observation_item,
Experience_type,
External_source_identification,
Condition_assignment,
Document_assignment,
Attachment_slot_design_to_realized,
Item_shape,
Resource_event_relationship,
Identification_assignment,
Document_definition_relationship,
Hardcopy,
Justification,
Type_of_person_definition_relationship,
Event,
Organizational_location_identification,
Address,
Position_group_relationship,
Position_type,
Person_in_organization,
Position_group_assignment,
Envelope,
Characterizable_object,
State_role,
Organization_type,
Organization_or_person_in_organization_assignment,
Applied_activity_method_assignment,
Product_configuration,
Activity_method_assignment,
Assigned_property,
Condition_evaluation_parameter,
State_assessment,
Resource_as_realized_relationship,
Resource_event,
Activity,
);
END_CLASS;
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
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.
EXAMPLE: Company Director
EXAMPLE: Service Engineer
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Position_assignment is an association of a Position with activity or product data.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Position_group is a group for collecting people in their positions to cooperate in an assignment.
EXAMPLE: People representing utility companies who cooperate with each other to coordinate road works.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Position_group_assignment is an association of a Position_group with activity or product data.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Position_group_relationship is a relationship that specifies the participation of a position in a group.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Position_position_type_assignment is an assignment of Position_type to a Position. It allows many positions to be described
by many position types.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Position_relationship is a relationship between Position s. Examples of relationships between Position s are
EXAMPLE: Superior / Subordinate
EXAMPLE: Superceded by
NOTE: The meaning of the relationship is determined by classification.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Position_type is a recognized kind of position.
EXAMPLE: Chief Executive Officer
EXAMPLE: Manager
EXAMPLE: Service engineer
EXAMPLE: Programmer
EXAMPLE: Aircraft engineering technician propulsion
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Position_type_assignment is the association of a Position_type with activity or product data.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Probability is a type of Representation that is a probability value (see definition 3.5.1 above).
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Probability_by_name is a type 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.
EXAMPLE: 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:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Probability_derivation_parameter is a type of Numerical_item_with_global_unit that is used by a Probability_derived in a
particular role in order to calculate the particular probability.
EXAMPLE: 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"
NOTE: The role name is given by the 'name' attribute inherited from Representation_item, and the set of such names and their
interpretation is defined through reference data.
NOTE: The value attribute, which holds the parameter value, is inherited from the supertype.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Probability_derived is a type of Probability_numeric that associates a particular value of Probability_numeric with the
source from which the value derived together with any parameters used to get the particular value.
NOTE: Where the probability derived from a probability distribution, the parameters of Probability_derived are those needed
to get a single value from the distibution, and not those which characterise 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 Probability_derived will be the 'number of heads obtained'.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Probability_distribution is a type of Probability_generator that is a probability distribution.
NOTE: For a full understanding of probability distribution and the terms used, a textbook on probability theory should be
consulted.
NOTE: 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: The attributes 'name', 'id' and 'description' are inherited from the supertype 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 Probability_distribution.distribution_name attribute.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Probability_distribution_parameter is a type of Numerical_item_with_global_unit that is one of the set of values that characterises
a probability distribution.
EXAMPLE: The Normal (or Gaussian) distribution has, in the standard parameterisation, two parameters: the mean and the variance
NOTE: For many common distributions, the mean and the variance are sufficient to characterize a distribution, and the parameter
list may be empty.
NOTE: Probability_distribution_parameter inherits the 'name' attribute from its supertype, and this is used to identify the
name of the parameter within the particular parameterization. The value attribute is also inherited.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Probability_function_value is a type of Numerical_item_with_global_unit that is the value of the probability function at
the given random variable value.
NOTE: 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:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Probability_generator is a type of Representation. It is a source from the Probability_derived is derived. The Probability_derivation_parameter s
are applied to the Probability_generator to get the particular derived value.
NOTE: A Probability_generator will generally be either a Probability_distribution or a function of some statistics.
EXAMPLE: 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:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Probability_named_value is a type of Representation_item that is used to hold the name of the probability value.
NOTE: The value attribute is the description inherited from the supertype. In general, this value will be one of an enumeration
of possible values defined through reference data.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Probability_numeric is a type of Probability that is expressed as a numeric value between 0 and 1.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Probability_numeric_value is a type of Numerical_item_with_global_unit providing a numeric representation of a probability.
NOTE: The value attribute is inherited from the supertype.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Product is the identification of a product or of a type of product. It is a collector of data common to all revisions of
the Product.
NOTE: Products that this entity data type can represent, include:
* products existing in the real world;
* products that may come into existence as a consequence of some realization process. This includes parts and documents;
* products that are functions. In the interpreted models, these various meanings are represented within instances of the entity product_related_product_category,
with prescribed values of the category name. For example, the category name 'document' shall be used when characterizing the
fact that a product is actually a document.
EXAMPLE: The SS Titanic is a product that could be represented by the entity data type Product.
EXAMPLE: Lifeboat is a class of products that could be represented by the entity data type Product. Each lifeboat on the SS
Titanic is a member of this class.
NOTE: A product is identified by an organization or a person in an organization. The definition of the domain of uniqueness
and the mechanism for guaranteeing the uniqueness of product id are outside the scope of this application module.
NOTE: A product may have zero or more versions. A version of a product is represented with an instance of the entity Product_version or
of one of its specializations.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Product_as_individual is a type of Product that identifies an individual artefact that has been made or is planned to be
made. It is a collector of data common to all revisions of the Product_as_individual.
NOTE: Revisions ( Product_as_individual_version ) 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 subtype Product_as_planned is used to represent the
revision of an individual artefact that has yet to be made and the subtype Product_as_realized is used to represent the revision
of an individual artefact that has been made.
NOTE: Where physical products are being represented, the Product_as_individual represents the physical or planned physical
realization of a product.
NOTE: It is likely, but not essential, that the artefact, was or will be made from a product design. The product design will
be represented by a Product which will be related to the Product_as_individual by Product_design_to_individual.
NOTE: Many physical products may be produced from a given design. A single Product may lead to many Product_as_individual s.
EXAMPLE: The design of a personal computer is represented by a Product.
EXAMPLE: The personal computer with a serial number on a persons desk is represented by a Product_as_individual and an associated
revision represented by Product_as_realized.
EXAMPLE: The personal computer that has been ordered, allocated a serial number for manufacturing planning, but not yet manufactured,
is represented by a Product_as_individual and an associated revision represented by Product_as_planned.
EXAMPLE: 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 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 which is 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 which is related
back to the Product_as_individual.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Product_as_individual_effectivity is a type of Effectivity for which the domain of applicability is defined as a set of
instances of Product_as_individual.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Product_as_individual_version is a type of Product_version. It is a revision of a Product_as_individual and acts as a collector
of the definitions of this revision.
EXAMPLE: 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: 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 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:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Product_as_individual_view is a type of Product_view_definition that defines a characterization view of a version of a Product_as_individual.
NOTE: The Product_as_individual_view entity type 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 Product_as_individual_view for
the same Product_as_individual_version.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Product_as_planned is a type of Product_as_individual_version that identifies a revision of an individual artefact that
has yet to be made.
NOTE: It may be planned to make the artefact from of a version of a product design ( Product_version ). If this is the case,
then the relationship between the artefact ( Product_as_planned ) and the design ( Product_version ) is represented by Product_design_version_to_individual.
NOTE: If the planned artefact ( Product_as_planned ) is subsequently made into an actual artefact ( Product_as_realized )
then they are related by the Product_planned_to_realized relationship.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Product_as_realized is a type of Product_as_individual_version that identifies a revision of an individual artefact that
has been made. A product whose properties can only be known by observation or by derivation from observations.
NOTE: Where physical products are being represented, the Product_as_realized represents the physical product - something one
can touch.
NOTE: The artefact may have been made from a version of a product design ( Product_version ). If this is the case, then the
relationship between the artefact ( Product_as_realized ) and the design ( Product_version ) is represented by Product_design_version_to_individual.
NOTE: The artefact may have been planned and represented by Product_as_planned. In which case, the actual artefact ( Product_as_realized )
is related to the planned artefact ( Product_as_planned ) by the Product_planned_to_realized relationship.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Product_based_location_identification is a type of Location_representation that specifies a location in the context of a
product.
EXAMPLE: Seat number M in the Aircraft.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Product_category is a type of product that is defined for a purpose that is specific to a module or application protocol.
NOTE: For the purpose of a general classification of products, use entity Class and Classification_assignment, standardized
in ISO 10303-1070 and ISO 10303-1114.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Product_concept is the identification of a set of similar products that were, are or will be proposed to customers.
NOTE: The definition of product concepts is driven by market and customer requirements and forecasting. A Product_concept often
corresponds to the highest level item(s) manufactured by an organization for customers.
EXAMPLE: In an organization which manufactures cars and engines for cars, the car models will be represented by instances
of Product_concept.
NOTE: The entity data type Product_concept 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: A product concept may be characterized by a set of product features identified by the customers or derived from customers'
needs.
NOTE: Depending on the kind of industry and products, a product concept might be offered to the customers in one or many different
configurations.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Product_configuration is the identification of a Product_concept as a configuration.
NOTE: The entity Product_configuration corresponds to the concept of configuration item defined, in some configuration management
standards, as an item subject to configuration management.
EXAMPLE: A Product_configuration may represent a component of a contracted product, onto which severe safety rules apply and
for which configuration management is therefore rigorously applied.
NOTE: A Product_configuration may identify a variation of a Product_concept, an entire Product_concept, or some portion thereof.
NOTE: A Product_configuration can be established prior to the existence of a corresponding product.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Product_design_to_individual is a relationship between a product design, represented by Product, and the product that is
planned to be made or has been made from the design, represented by Product_as_individual.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Product_design_version_to_individual is a relationship between a version of a product design, represented by Product_version,
and the product that is planned to be made ( Product_as_planned ) or has been made ( Product_as_realized ) from the design.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Product_group is an identification of a set of Product_concept s, Product s, Product_group s, Product_version s or Product_as_individual s
that have been grouped together.
EXAMPLE: All the aircraft sold to BigPlanes airways.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Product_group_membership is an identification of an instance of an entity defined in the type product_select that belongs
to a Product_group.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Product_group_relationship is a relationship between two Product_group s. Classification_assignment is used to specify the
meaning or type of the relationship.
NOTE: A subset is a common type of relationship. It indicates that one Product_group is a subset of another.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Product_in_attachment_slot is a type of View_definition_usage that is a relationship between an Attachment_slot and a Product_view_definition of
a Product that is designed to be attached to the attachment slot.
EXAMPLE: 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:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Product_planned_to_realized is a relationship that establishes that a revision of a planned artefact represented by Product_as_planned has
been realized as a revision of an actual artefact Product_as_realized.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Product_relationship is an association between two Product s.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Product_version is a revision of a Product. It is a collector of the definitions of this revision of the Product.
NOTE: The set of all instances of Product_version of the same Product represents the history of the product.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Product_version_relationship is an association between two versions of Product.
NOTE: A relationship may exist between Product_version of different Product s or between different versions of the same Product.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Product_view_definition is a characterization of a Product_version, relevant in one or more application domains and for
one or more life cycle stages. A Product_view_definition is a collector of the properties that characterize the Product_version in
the initial_context and additional_contexts.
EXAMPLE: The design of the SS Titanic and the as-built description of the SS Titanic can be represented as two instances of Product_view_definition.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Project is an identified program of work.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Project_assignment is a mechanism to associate a Project with activity or product data.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Project_relationship is an association between two instances of Project with an identifiaction and a description of their
relationship.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Promissory_usage is a type of Assembly_component_relationship. 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 Next_assembly_usage.
NOTE: A Promissory_usage 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:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Property_representation is an association between an Assigned_property and one of its Representation s.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Property_value_representation is a type of Representation that represents one or more quantity values.
NOTE: The present version of this application module does not enable to represent whether the values have been imposed or
were derived or measured. It is expected that a future version will add this capability.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Qualification_assignment is the assignment of a qualification to a person or organization.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Qualification_type is the identification of a definitive recognition as a practitioner.
EXAMPLE: A driving licence.
EXAMPLE: A qualification for executing the Ground Running task for RB211 engines.
EXAMPLE: A Military rank such as Colonel, or Captain
EXAMPLE: Educational qualification such as GCSE, A level, Degree, Ordinary National Certificate, Higher National Certificate,
City and Guilds, or GNVQ.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Qualification_type_relationship is an association between two Qualification_type s.
EXAMPLE: Qualification X is a pre-requisite for qualification Y.
EXAMPLE: Qualification X is equivalent to qualification Y.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Qualified_property_value_representation is a type of Property_value_representation whose meaning or usage has been further
qualified.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Random_variable is a type of Numerical_item_with_global_unit that is the value of a random variable.
NOTE: The value attribute is inherited from the supertype.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Ratio_unit is a type of Unit that expresses the dimensionless ratio of two quantities of the same kind.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Regional_coordinate is a location that is specified relative to a Regional location system.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Regional_grid_location_representation is a type of Location_representation that specifies a reference grid system.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Related_condition_parameter is a relationship between a Condition_parameter and a Condition_evaluation_parameter. This relationship
is used to record the relationship between the parameters used to define a condition and the parameters used to evaluate it.
EXAMPLE: The value of oil pressure (1.9 bar) used in Condition_evaluation (instance 87) was a measured value of the parameter
used to define condition 29 (oil pressure on gauge 3).
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Relative_event is a type of Event the start of which will occur, respectively has occurred, with a time offset from the
start of another Event.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Repeat_count is a type of Looping_element. It invokes a specified number of repetitions of the Looping_element.repeated_element Task_element inherited
from the Looping_element supertype.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Repeat_until is a type of Looping_element. It invokes repetitions of a further Task_element 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:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Repeat_while is a type of Looping_element. It invokes repetitions of a further Task_element 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 Looping_element not
being executed at all.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Representation is a collection of one or more instances of Representation_item that are related in the specified Representation_context.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Representation_context is a context in which instances of Representation_item are related.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Representation_item is an element of representation. A Representation_item shall be in the set of items of one or more instances
of Representation or it shall belong to one or more instances of Representation, being referred to, directly of indirectly,
by items of these instances of Representation.
NOTE: this constraint is formally represented in the Express specification of the resource entity that corresponds to Representation_item in
the MIM schema.
Only specializations of Representation_item can be instantiated.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Representation_relationship is an association between two instances of Representation.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Required_resource is an identified need for resource. The role of a required resource is determined by classification.
EXAMPLE: "facility", "test equipment", "supervisor" are examples of classifications of a required resource.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Required_resource_assignment is an association of a resource requirement statement with one or more entities that requires
the resource.
EXAMPLE: task, task step, activity, activity method, organization are examples of entities to which the resource requirement
statement could be related.
The role of the assignment is determined by classification.
EXAMPLE: The assignment can be classified as "required by".
NOTE: An association between a required resource and actions that are needed prior to its usage.
EXAMPLE: 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.using
EXAMPLE: 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.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Required_resource_by_resource_item is a type of Required_resource that is a statement of a required resource that can be
identified within the application context.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Required_resource_by_specification is a type of Required_resource where a collection of characteristics determine whether
an item would be suitable to meet the requirement. More than one item can fulfill the requirement.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Required_resource_relationship is a relationship between two required resource statements. The meaning of the relationship
is determined by classification.
EXAMPLE: "alternative" and "realized by" are examples of required resource relationship.
EXAMPLE: A Required_resource_by_specification for a power supply can be realized by a Required_resource_by_resource_item with
part number "ABC-1234".
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Requirement is a type of Product that is used to uniquely identify a requirement.
NOTE: The term "requirement" is used here in the sense that term is used in systems engineering and similar industrial domains.
NOTE: There may be many versions of a requirement Requirement_version ). There may also be more than one domain-specific view
of a given Requirement_version (using the Requirement_view_definition entity). The requirement entity is simply a placeholder
for holding a unique requirement. Most associations and properties are defined at the Requirement_view_definition level -
that is in the context of a domain.
EXAMPLE: A requirement may be identified as "NOx emissions requirement", and uniquely identified as "Req2".
NOTE: Systems engineering tools and organizations may use differing identification mechanisms. Multiple identifiers may be
assigned to a requirement using the Alias_identification entity.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Requirement_assignment is used to relate a requirement (via the Requirement_view_definition entity) to data types representing
the items which are affected by the requirement.
EXAMPLE: 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:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Requirement_collection_relationship is a type of View_definition_relationship 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.
NOTE: The inherited " View_definition_relationship.relating_view " and " View_definition_relationship.related_view " attributes
have been renamed for purposes of clarity.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Requirement_source is a relationship between a requirement (via the Requirement_view_definition entity) and the data types
representing the source of the requirement
EXAMPLE: 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:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Requirement_version is a type of Product_version that identifies a particular version of a requirement.
NOTE: This entity is used to record different versions of a requirement. In this case, the word "version" implies "revision"
- that is a particular release of a requirement.
EXAMPLE: A given requirement might have versions 1.0, 1.1, 1.2 and 2.0.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Requirement_version_relationship is a type of Product_version_relationship that is used to relate a previous version (predecessor)
of a requirement to the version that replaces it (successor).
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Requirement_view_definition is a type of Product_view_definition that provides a view of a requirement version relevant
for one or more application domains. This view collects requirement data for specific engineering purposes.
EXAMPLE: An engineer may have responsibility for collecting all requirements associated with the cooling of an engine - covering
engine block, tubing, water pump, electric fan.
Some requirements in a Requirement_view_definition might impact on different disciplines. Multiple Requirement_view_definition objects
may be used to present different views of a given requirement for each discipline.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Resource_as_realized is a record of a resource that has been used or consumed.
EXAMPLE: A resource as realized can be classified as "Used" or "Consumed".
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Resource_as_realized_assignment is an association of a resource record statement with the entity that used or consumed the
resource. The role of the assignment is determined by classification.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Resource_as_realized_relationship is a relationship between the record of used or consumed resources and the corresponding
statement of Required_resource.
EXAMPLE: "Alternative" and "Corresponding" are examples of classifications of resource as realized relationship.
NOTE: A resource used or consumed can be recorded without having a corresponding resource requirement statement.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Resource_as_realized_resource_item is a type of Resource_as_realized that is a used or consumed resource.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Resource_event 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.
EXAMPLE: A resource event can be classified as "Planned" or "Actual".
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Resource_event_correspondence_relationship is an association of a resource event and a corresponding statement of Required_resource.
The meaning of the relationship is determined by classification.
NOTE: A resource event can be planned or recorded without having a corresponding resource requirement statement.
EXAMPLE: A resource event correspondence relationship can be classified as "Designated for".
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Resource_event_relationship is a specification of how an Resource_event may be associated with another Resource_event. The
meaning of the relationship is determined by classification.
EXAMPLE: A managed resource relationship can be classified as "realized by" or "replaces".
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Resource_group_relationship is a type of Resource_item_relationship that specifiies the means to associate two resource
items that are part of a resource group. The meaning of the entity is determined by classification.
EXAMPLE: The relationship between a tool set and a mallet could be classified as "Contains".
EXAMPLE: The relationship between a facility and compressed air could be classified as "Provides".
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Resource_item is an item that can occur in the role of a resource within the application context.
EXAMPLE: A Resource_item may be classified as "Facility", "Replaceble unit", or "Package".
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Resource_item_assignment is an association of a resource item with some product information. The role of the assignment
is determined by classification.
EXAMPLE: The assignment can be classified as "applicable to" or "acquired for".
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Resource_item_relationship is a specification of how a resource item may be associated with another resource item. The role
of the relationship is determined by classification.
EXAMPLE: The relationship between a product and a package can be classified as "Preferred".
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Resource_property is a property of a resource related object.
NOTE: The resource related object is specified in another module
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Resource_property_representation is an association between an Resource_property and one of its representations.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Scheme is a type of Activity_method. 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.
NOTE: A Scheme may be classified as a Plan or Schedule, and it may be further classified into specific types of Plans or Schedules.
EXAMPLE: Acquisition plan, Maintenance plan, Resource schedule are examples of schemes.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Scheme_entry is a type of Activity_method that provides the identification and description of a single entry in a specific Scheme.
NOTE: A Scheme_entry may be associated with time constraints.
NOTE: A Scheme_entry only exists within the scope of a specific Scheme.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Scheme_entry_assignment is a type of Applied_activity_method_assignment. It associates a Scheme_entry with one of more items.
NOTE: The Scheme_entry_assignment links the single items included in Plans and Schedules with their associated Scheme_entry.
These items may be actions, events, or tasks depending on the nature of the Plan or Schedule.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Scheme_entry_relationship is a type of Activity_method_relationship. It relates two Scheme_entry entities. An association
may exists between Scheme_entry entities that relate to different Scheme or between different Scheme_entry entity instances
for the same Scheme.
NOTE: The Scheme_entry_relationship provides the ability to relate entries included in Plans or Schedules in different ways.
By applying classifications on the Scheme_entry_relationship it can be used for different purposes.
EXAMPLE: Decomposition, Dependency, and sequencing are examples of kinds of relationships possible between schema entries.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Scheme_relationship is a type of Activity_method_relationship relating two Scheme s.
NOTE: The Scheme_relationship 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 Scheme_relationship it
can be used for different purposes.
EXAMPLE: Decomposition, based-on, alternative, version are kinds of relationships between Scheme s.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Scheme_subject_assignment is a type of Applied_activity_method_assignment. It associates a Scheme with a specific subject.
NOTE: The Scheme_subject_assignment links the Plans and Schedules with their associated subjects or targets. This may indicate
the intent of the scheme.
EXAMPLE: The maintenance plan for an individual vehicle, where the subject attribute points to an entity instance representing
the individual vehicle.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Scheme_version is a type of Activity_method. It enables version control of Scheme.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Scheme_version_assignment is a type of Applied_activity_method_assignment. It associates a Scheme with a information describing
the version.
NOTE: The role of the association may be defined through classification.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Scheme_version_relationship is a type of Activity_method_relationship relating two Scheme_version s.
NOTE: The meaning of the relationship may be defined through classification.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Security_classification is a level of confidentiality that can be applied to protect activity or product data against unauthorized
usage.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Security_classification_assignment is an association of a Security_classification with activity or product data.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Selected_item is a type of Class used to classify identified product or activity data as being significant for configuration
management purposes.
EXAMPLE: Time Change/Shelf Life Selected Item (TCSI/SLSI)is an example of a selected item - All items that must be replaced
at specific intervals or that have an elapsed time-related shelf life, are designated as TCSIs or SLSIs, as appropriate. These
items do not require the rigorous, up-front CM activity (for example FCA/PCA but rather, they concentrate on the post-delivery
CM aspects related to traceability in the field. This is commensurate with their emphasis on being changed/replaced at certain
times.
EXAMPLE: Maintenance Selected Item (MSI) is an example of a selected item - Certain items whose maintenance requirements dictate
a more detailed traceability than normal items, may be designated as MSIs. MSIs emphasize post-delivery traceability for maintenance
purposes.
EXAMPLE: Support Equipment Selected Item (SESI) is an example of a selected item - Certain support equipment items that require
some additional traceability, but do not require up-front CM activity are designated as SESIs. These items typically require
traceability by lot or batch, but not by individual item serial number.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Selected_item_assignment is the identification of the product or activity data referenced by Selected_item_assignment.item as
being a Selected_item.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Sequence_of_state is a type of State_relationship in which one set of State precedes another set of State.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Sequence_of_state_definition is a type of State_definition_relationship. It defines a sequence of two or more state definitions.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Sequencing_relationship is a type of Scheme_entry_relationship. It defines a specific type of sequencing and relative timing
for two Scheme_entry.
NOTE: Specific types of sequencing could include start-start, finish-start.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Serial_effectivity is a type of Effectivity for which the domain of applicability is defined as a possibly open-ended interval
of serial numbers.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Simultaneous_elements is a type of Concurrent_elements that represents two or more actions to be performed together.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Solid_angle_unit is a type of Unit that is solid angle.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A State is the mode of being in which something does or could exist or existed for a period of time.
NOTE: A state's existence can be just a state that an object is currently in, a predicted state that an object will eventually
be in, or an observed state that an object has been in.
NOTE: The period of existence may be an instant or longer.
EXAMPLE: Main Engine No. 1 is in "operation".
EXAMPLE: When Generator No. 2 surpasses 5,000 service hours, it will enter "maintenance" mode.
EXAMPLE: The portable computer's power supply was attached after it displayed a "low-battery" warning.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A State_assertion is used to assert that the subject State is in conformance with a particular State_definition.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A State_assessment is used to determine whether the subject State is comparable with a particular State_definition.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A State_cause_effect is a type 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:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A State_cause_effect_definition is a type of State_definition_relationship that is used to define a causal relationship between
two sets of State_definition entities. At least one State_definition acts as a cause and at least one State_definition acts
as a effect.
NOTE: Additional causal relationships between states can be expressed using the following subtypes: And_state_cause_effect_definition, Or_state_cause_effect_definition,
and Xor_state_cause_effect_definition.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A State_complement_definition is a type of State_definition_relationship. It is a relationship among three sets of State_definition entities.
It defines the complement of a set of State_definition entities relative to a set of State_definition entities that are the
universe.
NOTE: The semantics are the same as in elementary set theory.
NOTE: The relationship between a State_definition and its complement is symmetrical.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A State_definition is a mode of being. A State_definition defines the types of State that can exist. A State 's existence
can be assessed and asserted against State_definition from State.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A State_definition_relationship is an association between two or more instances of State_definition.
NOTE: Relationships between State_definition entities may be used to support fault diagnosis.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A State_observed is a type of State. It is an individual or realized State that is observed.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A State_predicted is a type of State It is a predicted actual State. Where a predicted state needs to be related to an observed
state, the State_predicted_to_observed entity shall be used.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A State_predicted_to_observed is a type of state relationship. It specifies the relationship between two individual states,
one of which is a State_predicted to a second state which is a State_observed.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A State_proper_subset_definition is a type of State_definition_relationship. It is a relationship between two sets of State_definition entities.
NOTE: The relationship between a state and its environment can be described as a State_proper_subset_definition. The identification
of an instrinsic state is the proper_subset. The identification of an extrinsic state is the proper_superset.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A State_relationship is a relationship between two or more State.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A State_role is a specification of the purpose of the association of the Applied_state_assignment with product or activity
data.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A State_subset_definition is a type of State_definition_relationship. It is a relationship between two sets of State_definition entities.
NOTE: The first set may be equal to the second set.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A State_symptom_definition is a type of State_definition_relationship. It relates two or more State_definition entities in
regards to symptom, where a symptom is something that indicates the existence of something else. At least one State_definition acts
as a symptom_cause and at least one State_definition acts as a symptom_effect.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A State_transition is a type 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:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A State_transition_definition is a type of State_definition_relationship. It relates two or more State_definition entities
before and after a transition in state, where at least one State_definition is a start_state and at least one State_definition is
an end_state.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A String_representation_item is a type of Representation_item that specifies a text.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Structured_task_element is a type of Task_element. It is made up of other Task_element s
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Supplied_part_relationship is a type of Product_version_relationship that relates two instances of Product_version that
represent the same object in different organizational contexts. One of the organizations is the supplier of the object to
the other organization. This entity is applicable for part versions and document versions.
NOTE: This entity enables to represent the fact that two organizations may use distinct identifiers to identify their Product s
and their versions.
NOTE: 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.
NOTE: The module provides a more general mechanism that can be used to track alias identifiers for any entity data type that
has a id attribute.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A System_breakdown is a type of Breakdown that identifies a partitioning of a system into a set of related elements so as
to form explicit, assembly - component views that comprise the system elements. The assembly-component view is represented
by System_element_usage instances relating the system elements in the breakdown which are represented by System_element s.
EXAMPLE: A system breakdown provides a decomposition of an aircraft in terms of high-level mechanisms 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:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A System_breakdown_context is a type of Breakdown_context that is a membership relationship between a System_element and a System_breakdown of
which the system element is a member.
EXAMPLE: A heating system is a member of the breakdown of a climate control system.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A System_breakdown_version is a type of Breakdown_version that identifies a version of a System_breakdown.
EXAMPLE: 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:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A System_element is a type of Breakdown_element that identifies the elements in one or more System_breakdown objects.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A System_element_definition is a type of Breakdown_element_definition that identifies a view of a version ( System_element_version )
of a System_element.
EXAMPLE: 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:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A System_element_usage is a type of Breakdown_element_usage that is a relationship between a System_element_definition and
another System_element_definition that is a constituent.
EXAMPLE: In a system breakdown, the fuel system might include a fuel storage system and a fuel injection system as components.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A System_element_version is a type of Breakdown_element_version that identifies a version of a System_element.
EXAMPLE: A sound engineer changes the details describing the public address system that is an element in a system breakdown
of an aircraft.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Task_element is a type of Activity_method. It is a representation of all or part of how to undertake a task.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Task_element_assignment is a type of Applied_activity_method_assignment. It is an association of a Task_element with product
or activity data.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Task_element_levels is a type of Task_element that provides two or more different descriptions in place of a single method.
The actual work will be the same whichever alternative Task_element is followed.
NOTE: This can be used to provide defferent levels of description of a task for people with varying levels of experience or
expertise.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Task_element_relationship is a type of Activity_method_relationship. It relates two instances of Task_element.
EXAMPLE: Can be used to capture a time dependency that cuts across the structure of the method.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Task_element_sequence is a type of Task_element that comprises a sequence of steps to be followed in a specified order.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Task_element_state_relationship is an type of Activity_method_relationship. It is an association between a State or a State_definition and
a Task_element. The meaning of the entity is determined by classification. Candidate meanings include:
* assumed starting state;
* required starting state.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Task_invocation is a type of Task_element. It is an instruction to perform another task.
EXAMPLE: A Task_element calls a pre-defined task to perform an instrument calibration.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Task_method is a type of Activity_method. It is a specification of work.
NOTE: The task method may be implemented using people, machines or a combination.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Task_method_assignment is a type of Applied_activity_method_assignment. It is an association of a Task_method with product
or activity data.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Task_method_relationship is a type of Activity_method_relationship. It relates two task methods.
NOTE: The nature of the relationship is determined from its classification.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Task_method_state_relationship is a relationship between a state and a Task_method.
NOTE: The meaning of the entity is determined by classification. Candidate meanings include:
* Assumed starting state;
* Required starting state.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Task_method_version is a type of Activity_method which allows the explicit reference to versions of a Task_method and to
track changes against a Task_method.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Task_method_version_assignment is a type of Applied_activity_method_assignment. It is an association of a Task_method_version with
product or activity data.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Task_method_version_relationship is a type of Activity_method_relationship. It relates two instances of Task_method_version.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Task_objective is a result or objective that is reached by undertaking a Task_method.
NOTE: More than one Task_method may be defined for a given objective, if there can be several ways to accomplish the objective.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Task_objective_state_relationship is a relationship between a state and a Task_objective.
NOTE: The meaning of the entity is determined by classification. Candidate meanings include:
* Intended finishing state;
* Alternative finishing state.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Task_step is a type of Task_element that is not further sub-divided.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Thermodynamic_temperature_unit is a type of Unit in which the degree of heat of a body is expressed.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Time_interval_effectivity is a type of Effectivity for which the domain of applicability is defined as a Time_interval.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Time_interval_relationship is the association of two instances of Time_interval. The meaning of this association is specified
in the Time_interval_relationship.relation_type attribute.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Time_unit is a type of Unit with which the duration of a period is expressed.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Tracing_relationship is a type of View_definition_relationship that shows tracing from ( Tracing_relationship.traces_from )
one requirement to another ( Tracing_relationship.traces_to ).
EXAMPLE: A requirement on the performance of a catalytic converter in a car may be traced from a more general emissions requirement.
A requirement may trace to many other requirements and vice versa - this is achieved by creating multiple instances of the
tracing relationship entity.
NOTE: The inherited " View_definition_relationship.relating_view " and " View_definition_relationship.related_view " attributes
have been renamed for purposes of clarity.
NOTE: 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.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Transformation_based_template_instance is a type of Detailed_geometric_model_element. It is the replication of a Geometric_model.
The replication transformation is defined by a cartesian_transformation.
NOTE: In the case where the Geometric_coordinate_space of the replicated model is not the same as the Geometric_coordinate_space in
which the template_instance is founded, care shall be taken of any difference in the length units of both the instances of Geometric_coordinate_space,
as unit conversion may be required.
NOTE: The mapping-table defines two interpretations for this ARM entity. The first one uses the MIM entity mapped_item which
uses the same principle to define the transformation as the Axis_placement_mapping and Axis_placement_transformation_mapping entities.
The second one uses the MIM entity representation_relationship_with_transformation. Although this latter entity is not semantically
equivalent to the ARM entity, the second interpretation is kept because of its use in some implementations.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Type_of_person is a type of person.
EXAMPLE: Class 3 welder
EXAMPLE: Truck driver
EXAMPLE: Electronics engineer
EXAMPLE: Mechanical technician
EXAMPLE: Helicopter pilot
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Type_of_person_assignment is the association of a Type_of_person in a role with an activity or product data.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Type_of_person_definition is the definition of a Type_of_person in terms of required properties or attributes.
EXAMPLE: 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:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Type_of_person_definition_relationship is a relationship between two definitions of a type of person ( Type_of_person_definition ).
EXAMPLE: "alternate" and "superceded by" are examples of Type_of_person_definition_relationship s.
NOTE: The meaning of the relationship is determined by classification.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Type_of_person_definition_required_attributes_relationship is a relationship between a Type_of_person_definition and the
attributes required to define that type of person.
EXAMPLE: 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:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Uncertainty_with_unit is a type of Value_with_unit that specifies the uncertainty that applies to a type of measure. An Uncertainty_with_unit applies
to each Representation_item that uses the type of measure specified in the Value_with_unit.value_component of the Uncertainty_with_unit.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Unit is a unit quantity.
CLASS
Unit;
SUBCLASS OF (
PLCS-ARM-LF-THING
);
SUPERCLASS OF (
Conversion_based_unit,
Context_dependent_unit,
Solid_angle_unit,
Amount_of_substance_unit,
Derived_unit,
Luminous_intensity_unit,
Time_unit,
Ratio_unit,
Plane_angle_unit,
Length_unit,
Electric_current_unit,
Thermodynamic_temperature_unit,
Mass_unit,
);
END_CLASS;
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Value_limit is a type of Measure_item that specifies a qualified numerical value representing either the lower limit or
the upper limit of a particular quantifiable characteristic.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Value_limit_with_global_unit is a type of Measure_item that specifies a qualified numerical value representing either the
lower limit or the upper limit of a particular quantifiable characteristic and for which the value unit is globally assigned.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Value_list is a type of Measure_item that is an ordered collection of Measure_item s.
EXAMPLE: A Measure_item may be composed of different values such as 'mass', 'speed', and 'age' which are all necessary in
a given context. The Value_list collects all of them in a given order, such that each is identifiable by its index in the
list.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Value_range is a type of Measure_item that is a pair of numbers representing the range in which the value shall lie.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Value_range_with_global_unit is a type of Measure_item that is a pair of numerical values representing the range in which
the value shall lie. The unit of measure is globally assigned.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Value_set is a type of Measure_item that is an unordered collection of Measure_item s.
EXAMPLE: A Measure_item may be composed of different values such as 'mass', 'speed', and 'age' which are all necessary in
a given context. The Value_set collects all of them in a given order, such that each is identifiable by its index in the list.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Value_with_tolerances is a type of Measure_item 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:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Value_with_unit is the specification of a physical quantity by its value and its unit.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A View_definition_context is the grouping of an application domain and a life cycle stage. It identifies a universe of discourse
suitable for the description of products.
NOTE: Requirements and vocabularies vary among the industrial activity fields. This entity intends to identify such a domain.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A View_definition_relationship is an association between two instances of Product_view_definition. This association represents
a relationship between the product versions, indirectly identified by the instances of Product_view_definition, relevant in
the definition contexts of the related instances of Product_view_definition.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A View_definition_usage is a type of View_definition_relationship that specifies a directed association between two instances
of Product_view_definition. This association represents a relationship stating that, in the definition contexts of the related
instances of Product_view_definition, it is considered that the related product is used in the context of the relating product.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Work_order is an authoritative instrument which provides directions to achieve the specified results. A Work_order is the
authorization for one or more Activity objects to be performed.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Work_output is a statement of output resulting from an activity or a task. The role of the work output is determined by
classification.
EXAMPLE: When applicable a work output may be classified as
* "Planned";
* "Actual";
* "By-product";
* "Waste product".
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Work_output_assignment 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. The role of the assignment is determined by classification.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Work_output_relationship is a relationship between two work output statements. The meaning of the relationship is determined
by classification.
EXAMPLE: A Work_output_relationship is classified as "realized by".
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Work_request is the solicitation for some work to be done.
NOTE: These requests may not be acted upon depending on the authorization granted to the request or its associated Work_order.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Work_request_status is an association of a status with a Work_request.
NOTE: A Work_request may have zero or more statuses, assigned at various dates by various organizations.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
An Xor_state_cause_effect_definition is a type of State_cause_effect_definition. It relates one of the single or many causing
state definition(s) and one effect State_definition, whereby any and only one of the causing state definitions exists prior
to the single effect to take place.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Zone_breakdown is a type of Breakdown that identifies a partitioning of a product into a set of related zonal elements so
as to form explicit, parent-child views that comprise the product elements. The parent-child view is represented by Zone_element_usage instances
relating the zonal elements in the breakdown which are represented by Zone_element s.
EXAMPLE: A zonal breakdown provides a means of identifying the 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:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Zone_breakdown_context is a type of Breakdown_context that is a membership relationship between a Zone_element and a Zone_breakdown of
which the zonal element is a member.
EXAMPLE: A 'fire-check zone' might be a member of the zonal breakdown of a building.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Zone_breakdown_version is a type of Breakdown_version that identifies a version of a Zone_breakdown.
EXAMPLE: An architect modifies the current fire-check zone breakdown for an building on the basis of reports from a buildings
inspector.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Zone_element is a type of Breakdown_element that identifies the elements in one or more Zone_breakdown objects.
EXAMPLE: 'Empennage', 'Right vertical stabilizer and rudder' and 'Lower rudder' are all elements in a zonal breakdown of an
aircraft.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Zone_element_definition is a type of Breakdown_element_definition that identifies a view of a version ( Zone_element_version )
of a Zone_element.
EXAMPLE: For an aircraft, an element 'Right vertical stabilizer tip' is in a zonal breakdown that an engineer uses for reliability-centred
maintenance analysis.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Zone_element_usage is a type of Breakdown_element_usage that is a relationship between a parent and child Zone_element.
EXAMPLE: In a zonal breakdown, the 'wing' (parent) might include (as children) an 'inner wing' and an 'outer wing'.
Source:ISO 10303-239 Creator:OASIS PLCS Technical Committee Reference Data Development Team
Definition:
A Zone_element_version is a type of Breakdown_element_version that identifies a version of a Zone_element.
EXAMPLE: 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.
RDL File: committee-specification/plcs-arm-lf-express-ap239-definitions.rdf-xml.owl ()
Title:
Version: 1
Stage:
Description:
This ontology provides the AP239 definitions of the PLCS ARM Long Form EXPRESS.
RDL File: committee-specification/plcs-dc-elements-1.1.rdf-xml.owl ()
Title:
Version:
Stage:
Description: Most elements of this ontology were taken from the Dublin Core and should
have a URI of http://purl.org/dc/elements/1.1/ however, as there is no
official Dublin Core OWL representation, PLCS has adopted this on in the
interim. Non-DC element names start as "OASIS_".
RDL File: committee-specification/plcs-dc-terms.rdf-xml.owl ()
Title:
Version:
Stage:
Description: All terms in this ontology were taken from
the Dublin Core and should have a URI of http://purl.org/dc/terms/
however, as there is no official Dublin Core OWL representation, PLCS has
adopted this on in the interim.
RDL File: committee-specification/plcs-std-rdl.rdf-xml.owl ()
Title:
Version: $Id: plcs-std-rdl.rdf-xml.owl,v 1.12 2010/09/09 11:01:18 annmeads Exp $1
Stage: CommitteeSpecificationCommitteeSpecification
Description:
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, Saab Aerotech
Last modified:2009-06-30
Definition:
description that describes how to gain access to the associated object.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, Saab Aerotech Created:2008-03-06
Last modified:2009-07-06
Definition:
breakdown element identification code that identifies an item that can be opened or removed in order to gain access to other
items in a Product.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, Saab Aerotech
Last modified:2009-06-30
Definition:
view definition usage that specifies that the relating item is dependent upon the related item to be removed or opened, in
order to gain access to relating item.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Brad Harris, Eurostep Limited Created:2007-07-09
Last modified:2007-07-09
Definition:
An acquisition_process is an Agreement_process that classifies the associated data as having been defined within the context
of the process that obtains a product or service in accordance with the acquirer's requirements.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2007-04-02
Last modified:2007-07-12
Definition:
An Activity_actual_duration is Activity_property representing the length of time an Activity took to complete. The time may
be measured in units such as Hours, Minutes, Seconds.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2007-04-02
Last modified:2007-07-12
Definition:
An Activity_elapsed_duration is an Activity_property representing the time taken so far on an Activity that has not yet completed.
The time may be measured in units such as Man hours or Hours,Minutes, Seconds.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2007-01-23
Last modified:2007-07-23
Definition:
An Activity_identification_code is an Identification_code that is used to identify an activity that is planned or has happened.
EXAMPLE: The identification of of a planned activity in a project plan or the identification of a maintenance activity that
happened last week.
CONSTRAINT: An Identification_assignment classified as an Activity_identification_code can only be
assigned to an Activity or Activity_actual or their subclasses.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited
Definition:
An Activity_input is an Applied_activity_assignment class whose members are inputs to an Activity.
CLASS
Activity_input;
SUBCLASS OF (
EXPRESS:Applied_activity_assignment,
);
END_CLASS;
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2005-01-12
Last modified:2007-07-23
Definition:
An Activity_method_identification_code is an Identification_code that identifies an Activity_method.
EXAMPLE: The identification of a description of how to perform a maintenance activity.
CONSTRAINT: An Identification_assignment classified as an Activity_method_identification_code can only be
assigned to an Activity_method or its subclasses.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited
Definition:
An Activity_output is an Applied_activity_assignment class whose members are outputs from an Activity.
CLASS
Activity_output;
SUBCLASS OF (
EXPRESS:Applied_activity_assignment,
);
END_CLASS;
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2007-04-02
Last modified:2007-07-12
Definition:
An Activity_percentage_complete is an Activity_property representing in percentage terms, how complete an activity is.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2007-04-02
Last modified:2007-07-12
Definition:
An Activity_planned_duration is Activity_property representing the planned or expected time that an Activity will take to
complete. The time may be measured in units such as Man hours or Hours,Minutes, Seconds.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2007-04-02
Last modified:2007-07-11
Definition:
An Actual_effectivity is an Effectivity_assignment that classifies the
assigned_effectivity as being an actual period of time during which the
associated items are, or were, effective.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2009-05-08
Definition:
activity actual that supported the operation of product or returned the product to an operational state.
CLASS
Actual_logistics_activity;
SUBCLASS OF (
EXPRESS:Activity_actual,
);
SUPERCLASS OF (
Actual_maintenance_activity,
Actual_transport_activity,
);
DISJOINT WITH (
Activity_actual,
Scheduled_task,
Planned_activity,
Fit_form_function_change,
Removal,
Actual_operational_activity,
Installation,
Lifing_extension,
Overhaul,
Directed_activity,
Controlled_exchange_activity,
Actual_maintenance_activity,
Actual_transport_activity,
);
END_CLASS;
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2007-04-02
Last modified:2009-05-08
Definition:
Actual logistics activity that has been performed on a product.
CLASS
Actual_maintenance_activity;
SUBCLASS OF (
Actual_logistics_activity
);
SUPERCLASS OF (
Fit_form_function_change,
Removal,
Installation,
Lifing_extension,
Overhaul,
Controlled_exchange_activity,
);
DISJOINT WITH (
Activity_actual,
Scheduled_task,
Planned_activity,
Fit_form_function_change,
Removal,
Actual_operational_activity,
Actual_logistics_activity,
Installation,
Lifing_extension,
Overhaul,
Directed_activity,
Controlled_exchange_activity,
Actual_transport_activity,
);
END_CLASS;
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2009-05-08
Definition:
activity actual that has been performed by a product during its intended use.
CLASS
Actual_operational_activity;
SUBCLASS OF (
EXPRESS:Activity_actual,
);
DISJOINT WITH (
Activity_actual,
Scheduled_task,
Planned_activity,
Fit_form_function_change,
Removal,
Actual_logistics_activity,
Installation,
Lifing_extension,
Overhaul,
Directed_activity,
Controlled_exchange_activity,
Actual_maintenance_activity,
Actual_transport_activity,
);
END_CLASS;
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2009-05-08
Definition:
actual logistics activity that moved a product from one location to another
CLASS
Actual_transport_activity;
SUBCLASS OF (
Actual_logistics_activity
);
DISJOINT WITH (
Activity_actual,
Scheduled_task,
Planned_activity,
Fit_form_function_change,
Removal,
Actual_operational_activity,
Actual_logistics_activity,
Installation,
Lifing_extension,
Overhaul,
Directed_activity,
Controlled_exchange_activity,
Actual_maintenance_activity,
);
END_CLASS;
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Tim Turner, LSC Group Created:2007-01-30
Last modified:2007-07-13
Definition:
An Address_based_location_identification_code is an Idenitification_code that identifies an Address_based_location_representation.
CONSTRAINT: An Identification_assignment classified as an Address_based_location_identification_code can only be assigned
to an Address_based_location_representation or its subclasses.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Tim Turner, LSC
Definition:
A Adjacent_location is a classification of a Location_relationship where the related_location is adjacent to the relating_location.
Each location shall unique in that they shall not provide different representations of the same location. There is no specification
on how close an Adjacent_location needs to be to the relating_location. However, sub-classes may provide narrower definitions
for other contexts.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, Saab Aerotech
Last modified:2009-06-30
Definition:
planned duration of activity that represents the planned or expected time it will take to complete an overall activity, including
the roll up of all the planned or expected durations for all its subactivities.
Note: The duration may be measured in units such as Hours, Minutes, Seconds.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, Saab Aerotech
Last modified:2009-06-30
Definition:
labour time planned that represents the planned or expected amount of work that will be consumed performing an overall activity,
including the roll up from all its subactivities.
Note: The duration may be measured in units such as Man_hours.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Trine Hansen, DNV Created:2004-11-24
Last modified:2007-07-10
Definition:
An Agreement_process is a Process_domain domain that classifies the associated data as having been defined within the context
of specifying the
requirements for the establishment of agreements with organizational entities external and internal to the organization.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Tim Turner, LSC
Definition:
An Alternative_location is a classification of a Location_relationship where the related_location is an alternative to the
relating_location. Each location shall unique in that they shall not provide different representations of the same location.
An alternative_location may provide similar facilities as the relating_location.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited
Definition:
AP239 message that contains ISO 10303-239 data conformant to ISO 10303-239 edition 1.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Tim Turner, LSC Group
Definition:
AP239 message that contains ISO 10303-239 data conformant to ISO 10303-239 edition 1, as modified on DEXLIB, recorded as
schema version 1.11
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Tim Turner, LSC Group
Definition:
AP239 message that contains ISO 10303-239 data conformant to ISO 10303-239 edition 1, as modified on DEXLIB, recorded as
schema version 1.11
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited
Definition:
AP239 message that contains ISO 10303-239 data conformant to ISO 10303-239 edition 1, technical corrigendum 1.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Tim Turner, LSC Group
Definition:
AP239 message that contains ISO 10303-239 data conformant to ISO 10303-239 edition 2.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited
Definition:
message that contains data of a given version of ISO 10303-239.
Note: Subclass names shall identify the version of ISO 10303-239 to which the data in the message conforms. This information
is used by translators to correctly decode a message..
Version:1 Stage:CommitteeSpecification Revision:0
Source:ISO/TS 10303-1019:2004 Product data representation and exchange: Application module: Product view definition Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2007-07-23
Last modified:2007-07-23
Definition:
An Application_domain is a View_definition_context that classifies the associated data as having been defined within the context
of that Application_domain .
NOTE - 'electrical design' and 'mechanical design' are not understood to mean the design life cycle -
within the application domain 'mechanical design', you may have concurrent 'manufacturing' and 'design'
life-cycle view definitions.
EXAMPLE: 'assembly study', 'digital mock-up', 'electrical design', 'mechanical design', 'preliminary design', 'process planning'
are examples of application domains.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PDM Schema usage guide Creator:Mike Ward, Eurostep Limited Created:2007-01-23
Last modified:2007-07-11
Definition:
approval_status that denotes official acceptance.
Version:1 Stage:CommitteeSpecification Revision:0
Source:UK MoD TES/ILS and Eng Pol under UK_Defence Development Programme Creator:Tim Turner Created:
Last modified:2007-07-23
Definition:
An Approved_item_name is a Resource_item_name that identifies a Resource_item with a name that has been (implicitly) approved
by a National Codification Bureau.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2007-04-02
Last modified:2007-07-11
Definition:
approval_status that denotes official acceptance with constraints or limitations on usage.
EXAMPLE: This could be used to assert that a part may used on an aircraft so long as the aircraft does not fly above 3000
metres.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Brad Harris, Eurostep Limited Created:2007-07-09
Last modified:2007-07-09
Definition:
An Architectural_design_process is a Technical_process that classifies the associated data as having been defined within the
context of synthesizing a solution that satisfies system requirements.
CLASS
Architectural_design_process;
SUBCLASS OF (
Technical_process
);
DISJOINT WITH (
Operation_process,
Implementation_process,
Validation_process,
Verification_process,
Maintenance_process,
Transition_process,
Stakeholder_requirements_definition_process,
Requirements_analysis_process,
Disposal_process,
Integration_process,
);
END_CLASS;
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS Creator:Leif Gyllstrom, Saab Aerotech Created:2007-05-23
Last modified:2009-07-06
Definition:
name by which a position in an assembly structure is known.
Example: Left front wheel.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Brad Harris, Eurostep Limited Created:2007-07-10
Last modified:2007-07-23
Definition:
An Asserter_of is an Organization_or_person_in_organization_assignment that
classifies the associated assigned_entity(organization_or_person_in_organization_select) as being
the asserter of the associated items.
EXAMPLE: This could be used to define the person who asserts that an item of equipment has a specific fault.
CLASS
Assertor_of;
SUBCLASS OF (
EXPRESS:Organization_or_person_in_organization_assignment,
);
DISJOINT WITH (
Contractor,
Security_classifier_of,
Creator_of,
Maintainer_of,
Contractee,
Operator_of,
Owner_of,
User_of,
Responsible_for,
Measurer_of,
Manufacturer_of,
Assessor_of,
Executor_of,
Sender_of,
Performer_of,
Designer_of,
Issuer_of,
Installed_in_position,
Observer_of,
Receiver_of,
Reporter_of,
);
END_CLASS;
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Brad Harris, Eurostep Limited Created:2007-07-10
Last modified:2007-07-23
Definition:
An Assessor_of is an Organization_or_person_in_organization_assignment
that classifies the associated
assigned_entity(organization_or_person_in_organization_select) as being
the assessor of the associated items.
EXAMPLE: This could be used to define the person who assesses that an item of equipment has a specific
fault.
CLASS
Assessor_of;
SUBCLASS OF (
EXPRESS:Organization_or_person_in_organization_assignment,
);
DISJOINT WITH (
Contractor,
Security_classifier_of,
Creator_of,
Maintainer_of,
Contractee,
Operator_of,
Owner_of,
User_of,
Responsible_for,
Measurer_of,
Manufacturer_of,
Executor_of,
Sender_of,
Performer_of,
Designer_of,
Assertor_of,
Issuer_of,
Installed_in_position,
Observer_of,
Receiver_of,
Reporter_of,
);
END_CLASS;
Version:1 Stage:CommitteeSpecification Revision:0
Source: Creator:Trine Hansen, DNV Created:
Last modified:2007-07-12
Definition:
An Assignment_type is the type of the assignment of an identifier by an Identficaton_assignment. This distinguishes the use
of a particular identifier in the context of alternative identifiers for the same item. For example, the preferred identifier
indicates that this identification is the preferred identification. Note - This is an abstract class, in other words, the
class should never be instantiated in an exchange file. Instead, sub classes will be instantiated.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2005-01-12
Last modified:2007-07-13
Definition:
An Attachment_slot_identification_code is an Identification_code that identifies
an Attachment_slot.
CONSTRAINT: An Identification_assignment classified as an Attachment_slot_identification_code can only
be assigned to an Attachment_slot or its sub classes.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, Saab Aerotech Created:2009-06-30
Definition:
class identification code that identifies a class that classifies a Breakdown element from specific application domain point
of view.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2007-01-23
Last modified:2007-07-23
Definition:
A Breakdown_element_identification_code is an Identification_code that identifies a breakdown_element.
EXAMPLE: An SNS_identification_code (Standard Numbering System)
that is used in AECMA 1000D as a method to describe the functional and/or physical breakdown of items of the material.
CONSTRAINT: An Identification_assignment classified as a Breakdown_element_identification_code can only
be assigned to a Breakdown_element or its sub classes.
Version:1 Stage:CommitteeSpecification Revision:0
Source:OASIS PLCS Creator:Per Myrseth, DNV Created:2005-10-25
Last modified:2007-07-18
Definition:
A Breakdown_element_name is a Name by which a Breakdown_element is known.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, Saab Aerotech
Definition:
breakdown element definition classification that organizes Breakdown elements in logical groups as required by a support concept
or support plan.
Version:1 Stage:CommitteeSpecification Revision:0
Source:OASIS PLCS Creator:Per Myrseth, DNV Created:2005-10-14
Last modified:2007-07-12
Definition:
A Breakdown_element_version_identifcation_code is a Version_identifcation_code that identifies a particular version of a Breakdown_element.
CONSTRAINT: An Identification_assignment classified as a Breakdown_element_version_identifcation_code can only be assigned
to a
Breakdown_element_version or its subclasses.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2005-01-12
Last modified:2007-07-13
Definition:
A Breakdown_identification_code is an Identification_code that identifies a breakdown of product, such as a physical or zonal
breakdown.
CONSTRAINT: An Identification_assignment classified as a Breakdown_identification_code can only be assigned to a Breakdown
or its sub classes.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited
Definition:
A Breakdown_name is a Name by which a Breakdown is known.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:David Price, Eurostep Limited Created:2007-05-11
Last modified:2007-07-12
Definition:
A Breakdown_version_identifcation_code is a Version_identifcation_code that identifies a particular version of a Breakdown_version.
CONSTRAINT: An Identification_assignment classified as a Breakdown_version_identifcation_code can only be assigned to a Breakdown_version
or its subclasses.
Version:1 Stage:CommitteeSpecification Revision:0
Source:http://www.dlis.dla.mil/cage_welcome.asp Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2004-03-02
Last modified:2007-07-13
Definition:
A CAGE_code is an Organization_identification_code.
A CAGE (Commercial & Government Entity) Code is a five (5) position code that identifies companies doing or wishing to do
business with the Federal Government. The codes are assigned by Defense Logistics Information Service (DLIS). The format of
the code is that the first and fifth position must be numeric. The second, third and fourth may be any mixture of alpha/numeric
excluding I and O. All positions are non-significant.
For details see: http://www.dlis.dla.mil/cage_welcome.asp
CONSTRAINT: An Identification_assignment classified as a CAGE_code can only be assigned to an Organization or its subclasses.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Per Myrseth, DNV
Last modified:2009-06-30
Definition:
property value representation that is the result of an estimation or stipulation of a value based on calculations
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2005-01-12
Last modified:2007-07-13
Definition:
A Certification_identification_code is an Identification_code that identifies a Certification.
CONSTRAINT: An Identification_assignment classified as a Certification_identification_code can only be assigned to a Certification
or its subclasses.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2009-05-06
Definition:
identification code that identifies a class where the identifier is a member of a set of predefined values according to some
encoding scheme.
Note:
The set of values are often referred to as a code list or value list.
Note:
The ISO 10303-239 Class entity being identified is being used for classification of any ISO 10303-239 entity. The class being
identiified is not a member of the referenced data library.
Version:1 Stage:CommitteeSpecification Revision:0
Source:UK MoD TES/ILS and Eng Pol under UK_Defence Development Programme Creator:Tim Turner Created:2007-07-23
Last modified:2007-07-23
Definition:
A Codification_stage is a Support_stage that classifies the associated data as having been defined within the context of
spare part codification.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, Saab Aerotech Created:2007-05-23
Last modified:2009-06-30
Definition:
computable condition that can evaluate the Condition_parameter(s) using a comparative relationship.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Sean Barker, BAE Systems Created:2007-05-23
Last modified:2009-06-30
Definition:
Condition that determines that its related Condition_parameter(s) can be evaluated against recorded data without recourse
to human intervention.
Version:1 Stage:CommitteeSpecification Revision:0
Source:ISO 15288 Creator:Trine Hansen, DNV Created:2004-11-23
Last modified:2007-07-23
Definition:
A Concept_stage is a Life_cycle_stage that classifies the associated data as having been defined within the context of assessing
new
business opportunities and developing preliminary system requirements and
a feasible design solution.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Tim Turner, LSC
Definition:
A Concession is a class of Approval whose members represent a concession. A concession is the approval to perform an activity
or use a product when there is some variance from the design. Note: a concession is typically limited to the delivery of a
product that has non-conforming characteristics within specified limits for an agreed time or quantity of product.
CLASS
Concession;
SUBCLASS OF (
EXPRESS:Approval_assignment,
);
END_CLASS;
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited
Definition:
A Concession_condition is a Condition that compares a life property to a value in order to provide limitations on the usage
of a product.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Tim Turner, LSC
Definition:
A Concession_justification is a class of Justification whose members represent a justification which is used to represent
the reason behind (for) a concession. A concession is the approval to perform an activity or use a product when there is some
variance from the design. A justification is the reason for a variance from the original intent.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Tim Turner, LSC Group Created:2007-02-26
Last modified:2007-07-12
Definition:
A Condition_type_code is a Condition that classifies Condition instances.
NOTE: It is expected that sub-classes of this class will define specific types of
Conditions which will allow the grouping of conforming
entries together
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2007-01-23
Last modified:2007-07-12
Definition:
A Configuration_change classifies a Directed_activity or a Work_order as being one that
results in a change to the configuration of the product design and actual product.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Brad Harris, Eurostep Limited Created:2007-07-09
Last modified:2007-07-09
Definition:
A Configuration_management_process is a Project_process that classifies the associated data as having been defined within
the context of
establishing and maintaining the integrity of all identified outputs of a
project or process and making them available to concerned parties.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2005-01-12
Last modified:2007-07-13
Definition:
A Contract_identification_code is an Identification_code that identifies a Contract.
CONSTRAINT: An Identification_assignment classified as a Contract_identification_code can only be assigned to a Contract or
its subclasses.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Brad Harris, Eurostep Limited Created:2007-07-10
Last modified:2007-07-23
Definition:
A Contractee is an Organization_or_person_in_organization_assignment that classifies the associated assigned_entity(organization_or_person_in_organization_select)
as being the contractee with respect to the associated items(contract).
NOTE: The assigned_entity(organization_or_person_in_organization_select) that is classified as the Contractee, awards a contract
to a contractor.
CLASS
Contractee;
SUBCLASS OF (
EXPRESS:Organization_or_person_in_organization_assignment,
);
DISJOINT WITH (
Contractor,
Security_classifier_of,
Creator_of,
Maintainer_of,
Operator_of,
Owner_of,
User_of,
Responsible_for,
Measurer_of,
Manufacturer_of,
Assessor_of,
Executor_of,
Sender_of,
Performer_of,
Designer_of,
Assertor_of,
Issuer_of,
Installed_in_position,
Observer_of,
Receiver_of,
Reporter_of,
);
END_CLASS;
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Brad Harris, Eurostep Limited Created:2007-07-10
Last modified:2007-07-23
Definition:
A Contractor is an Organization_or_person_in_organization_assignment that classifies the associated assigned_entity(organization_or_person_in_organization_select)
as being the contractor with respect to the associated items(contract).
NOTE: The assigned_entity(organization_or_person_in_organization_select) that is classified as the Contractor, is awarded
a contract by a contractee.
CLASS
Contractor;
SUBCLASS OF (
EXPRESS:Organization_or_person_in_organization_assignment,
);
DISJOINT WITH (
Security_classifier_of,
Creator_of,
Maintainer_of,
Contractee,
Operator_of,
Owner_of,
User_of,
Responsible_for,
Measurer_of,
Manufacturer_of,
Assessor_of,
Executor_of,
Sender_of,
Performer_of,
Designer_of,
Assertor_of,
Issuer_of,
Installed_in_position,
Observer_of,
Receiver_of,
Reporter_of,
);
END_CLASS;
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2007-04-02
Last modified:2007-07-12
Definition:
A Controlled_exchange classifies an Activity as being one that perform a
controlled exchange on a reportable item, ie the removal of a serviceable
reportable item from one item of equipment for installation on another.
CLASS
Controlled_exchange_activity;
SUBCLASS OF (
Actual_maintenance_activity
);
DISJOINT WITH (
Activity_actual,
Scheduled_task,
Planned_activity,
Fit_form_function_change,
Removal,
Actual_operational_activity,
Actual_logistics_activity,
Installation,
Lifing_extension,
Overhaul,
Directed_activity,
Actual_maintenance_activity,
Actual_transport_activity,
);
END_CLASS;
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, Saab Aerotech
Last modified:2009-06-30
Definition:
resource property that represents the amount of money that is needed in order to buy, do, or make it.
CLASS
Cost;
SUBCLASS OF (
EXPRESS:Resource_property,
);
SUPERCLASS OF (
Estimated_cost,
);
END_CLASS;
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Brad Harris, Eurostep Limited Created:2007-07-10
Last modified:2007-07-10
Definition:
A Creator_of is an Organization_or_person_in_organization_assignment that classifies the associated assigned_entity(organization_or_person_in_organization_select)
as being the creator of the associated items.
CLASS
Creator_of;
SUBCLASS OF (
EXPRESS:Organization_or_person_in_organization_assignment,
);
DISJOINT WITH (
Contractor,
Security_classifier_of,
Maintainer_of,
Contractee,
Operator_of,
Owner_of,
User_of,
Responsible_for,
Measurer_of,
Manufacturer_of,
Assessor_of,
Executor_of,
Sender_of,
Performer_of,
Designer_of,
Assertor_of,
Issuer_of,
Installed_in_position,
Observer_of,
Receiver_of,
Reporter_of,
);
END_CLASS;
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, Saab Aerotech
Last modified:2009-06-30
Definition:
condition parameter that defines that the Condition is to be evaluated against a defined customer.
Note: The condition parameter must be an instance of Organization.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2005-01-12
Last modified:2007-07-05
Definition:
date_or_date_time_assignment that identifies the date or date and time on which something actually happened to the associated
item.
CLASS
Date_actual;
SUBCLASS OF (
EXPRESS:Date_or_date_time_assignment,
);
SUPERCLASS OF (
Date_actual_start,
Date_actual_reported,
Date_actual_assessment,
Date_actual_creation,
Date_actual_observation,
Date_actual_end,
Date_actual_extraction,
Date_actual_release,
Date_actual_modified,
Date_message_data_frozen,
Date_message_sent,
Date_actual_assertion,
);
DISJOINT WITH (
Date_planned,
);
END_CLASS;
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:David Price, Eurostep Limited Created:2007-07-05
Last modified:2007-07-05
Definition:
A Date_actual_assertion is a Date_actual that classifies the associated
assigned_date as being that on which the associated items (e.g.
state_assertion) was asserted.
CLASS
Date_actual_assertion;
SUBCLASS OF (
Date_actual
);
DISJOINT WITH (
Date_actual_start,
Date_actual_reported,
Date_actual_assessment,
Date_actual_creation,
Date_actual_observation,
Date_actual_end,
Date_actual_extraction,
Date_actual_release,
Date_actual_modified,
Date_message_data_frozen,
Date_message_sent,
);
END_CLASS;
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:David Price, Eurostep Limited Created:2007-07-05
Last modified:2007-07-05
Definition:
A Date_actual_assessment is a Date_actual that classifies the associated
assigned_date as being that on which the associated
items(state_assessment) was assessed.
CLASS
Date_actual_assessment;
SUBCLASS OF (
Date_actual
);
DISJOINT WITH (
Date_actual_start,
Date_actual_reported,
Date_actual_creation,
Date_actual_observation,
Date_actual_end,
Date_actual_extraction,
Date_actual_release,
Date_actual_modified,
Date_message_data_frozen,
Date_message_sent,
Date_actual_assertion,
);
END_CLASS;
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2007-07-05
Last modified:2007-07-05
Definition:
A Date_actual_creation is a Date_actual that classifies the associated
assigned_date as being that on which the associated
items were created.
CLASS
Date_actual_creation;
SUBCLASS OF (
Date_actual
);
DISJOINT WITH (
Date_actual_start,
Date_actual_assessment,
Date_actual_observation,
Date_actual_end,
Date_actual_extraction,
Date_actual_release,
Date_actual_modified,
Date_message_data_frozen,
Date_message_sent,
Date_actual_assertion,
);
END_CLASS;
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2007-07-05
Last modified:2007-07-05
Definition:
A Date_actual_end is a Date_actual that classifies the associated
assigned_date as being that on which the associated
items ended.
CLASS
Date_actual_end;
SUBCLASS OF (
Date_actual
);
DISJOINT WITH (
Date_actual_start,
Date_actual_reported,
Date_actual_assessment,
Date_actual_creation,
Date_actual_observation,
Date_actual_extraction,
Date_actual_release,
Date_actual_modified,
Date_message_data_frozen,
Date_message_sent,
Date_actual_assertion,
);
END_CLASS;
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:David Price, Eurostep Limited Created:2007-07-05
Last modified:2007-07-05
Definition:
A Date_actual_extraction is a Date_actual that classifies the associated
assigned_date as being that on which the associated
items(message) was extracted from the sending system.
CLASS
Date_actual_extraction;
SUBCLASS OF (
Date_actual
);
DISJOINT WITH (
Date_actual_start,
Date_actual_reported,
Date_actual_assessment,
Date_actual_creation,
Date_actual_observation,
Date_actual_end,
Date_actual_release,
Date_actual_modified,
Date_message_data_frozen,
Date_message_sent,
Date_actual_assertion,
);
END_CLASS;
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:David Price, Eurostep Limited Created:000-00-00
Last modified:2007-07-06
Definition:
A Date_actual_modified is a Date_actual that assigns a date or date_time when something was actually modified.
CLASS
Date_actual_modified;
SUBCLASS OF (
Date_actual
);
DISJOINT WITH (
Date_actual_start,
Date_actual_reported,
Date_actual_assessment,
Date_actual_creation,
Date_actual_observation,
Date_actual_end,
Date_actual_extraction,
Date_actual_release,
Date_message_data_frozen,
Date_message_sent,
Date_actual_assertion,
);
END_CLASS;
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2007-07-05
Last modified:2007-07-05
Definition:
date_actual that identifies the date or date and time on which an observation was actually made on the associated item.
CLASS
Date_actual_observation;
SUBCLASS OF (
Date_actual
);
DISJOINT WITH (
Date_actual_start,
Date_actual_reported,
Date_actual_assessment,
Date_actual_creation,
Date_actual_end,
Date_actual_extraction,
Date_actual_release,
Date_actual_modified,
Date_message_data_frozen,
Date_message_sent,
Date_actual_assertion,
);
END_CLASS;
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2005-01-12
Last modified:2007-07-05
Definition:
A Date_actual_release is a Date_actual that classifies the associated
assigned_date as being that on which the associated items were released.
CLASS
Date_actual_release;
SUBCLASS OF (
Date_actual
);
SUPERCLASS OF (
Work_order_issue_date,
Work_request_issue_date,
);
DISJOINT WITH (
Date_actual_start,
Date_actual_reported,
Date_actual_assessment,
Date_actual_creation,
Date_actual_observation,
Date_actual_end,
Date_actual_extraction,
Date_actual_modified,
Date_message_data_frozen,
Date_message_sent,
Date_actual_assertion,
);
END_CLASS;
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2007-07-05
Last modified:2007-07-05
Definition:
A Date_actual_reported is a Date_actual that classifies the associated
assigned_date as being that on which the associated items were reported.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2007-07-05
Last modified:2007-07-05
Definition:
A Date_actual_start is a Date_actual that classifies the associated
assigned_date as being that on which the associated items started.
CLASS
Date_actual_start;
SUBCLASS OF (
Date_actual
);
DISJOINT WITH (
Date_actual_reported,
Date_actual_assessment,
Date_actual_creation,
Date_actual_observation,
Date_actual_end,
Date_actual_extraction,
Date_actual_release,
Date_actual_modified,
Date_message_data_frozen,
Date_message_sent,
Date_actual_assertion,
);
END_CLASS;
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Sean Barker, BAE SYSTEMS Created:2006-06-14
Last modified:2007-07-19
Definition:
A Date_message_data_frozen is a Date_actual that classifies the associated
assigned_date as being that on which the information content of the associated items(Content_item)
was frozen.
NOTE: This should not be used if the different elements of the content_item were collected at significantly different times.
CLASS
Date_message_data_frozen;
SUBCLASS OF (
Date_actual
);
DISJOINT WITH (
Date_actual_start,
Date_actual_reported,
Date_actual_assessment,
Date_actual_creation,
Date_actual_observation,
Date_actual_end,
Date_actual_extraction,
Date_actual_release,
Date_actual_modified,
Date_message_sent,
Date_actual_assertion,
);
END_CLASS;
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Brad Harris, Eurostep Limited Created:2007-07-19
Last modified:2007-07-19
Definition:
A Date_message_sent is a Date_actual that classifies the associated
assigned_date as being that on which the associated items(Message) was
sent.
CLASS
Date_message_sent;
SUBCLASS OF (
Date_actual
);
DISJOINT WITH (
Date_actual_start,
Date_actual_reported,
Date_actual_assessment,
Date_actual_creation,
Date_actual_observation,
Date_actual_end,
Date_actual_extraction,
Date_actual_release,
Date_actual_modified,
Date_message_data_frozen,
Date_actual_assertion,
);
END_CLASS;
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2005-01-12
Last modified:2007-07-05
Definition:
A Date_planned is a Date_or_date_time_assignment that classifies the
associated assigned_date as being that on which the associated items are
planned to occur - as opposed to when they were predicted to occur or when
they actually did occur.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2005-01-12
Last modified:2007-07-06
Definition:
A Date_planned_creation is a Date_planned that classifies the associated
assigned_date as being that on which the associated
items are planned to be created.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:David Price, Eurostep Limited Created:2007-07-05
Last modified:2007-07-05
Definition:
A Date_planned_end is a Date_planned that classifies the associated
assigned_date as being that on which the associated items are planned to
end.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2005-01-12
Last modified:2007-07-05
Definition:
A Date_planned_release is a Date_planned that classifies the associated
assigned_date as being that on which the associated items are planned to
be released.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2007-07-05
Last modified:2007-07-05
Definition:
A Date_planned_start is a Date_planned that classifies the associated
assigned_date as being that on which the associated items are planned to
start.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Brad Harris, Eurostep Limited Created:2007-07-09
Last modified:2007-07-09
Definition:
A Decision_making_process is a Project_process that classifies the associated data as having been defined within the context
of selecting the most beneficial course of project action where alternatives exist.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited
Definition:
A Deferred_activity is a State_of_activity that defines a deferred state
for an activity. The completion of the activity has been deferred to a
later date.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited
Definition:
A Deferred_life_condition is a Condition that compares a life property to a value in order to trigger a deferred activity.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited
Definition:
A Deferred_time_condition is a Condition that triggers a deferred activity at specified time.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited
Definition:
A Deferred_work_order is a State_of_work_order that defines a deferred state for a work order. The work order has been raised,
but its processing has been deferred to a later date.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited
Definition:
A Definition_assignment is a Document_assignment that assigns a document in the role of providing a definition. For example,
the documents defining the activities performed by a typical activity.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Trine Hansen, DNV Created:2004-11-24
Last modified:2007-07-12
Definition:
A Deprecated_identifier is an Assignment_type that has been deprecated.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited
Last modified:2009-06-30
Definition:
descriptor assignment that classifies the associated text as being a description.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, Saab Aerotech
Last modified:2009-06-30
Definition:
document assignment that assignes a descriptive text to something.
Note: This class is valid for PLCS ed 1. Its usage will replaced by an explicit Description_assignment class in PLCS ed 2.
Version:1 Stage:CommitteeSpecification Revision:0
Source:UK MoD JSC TLS Creator:Ann Meads Created:2010-03-16
Last modified:2010-03-16
Definition:
A Design is a Concept_stage that classifies the associated data as being Design.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Brad Harris, Eurostep Limited Created:2007-07-10
Last modified:2007-07-10
Definition:
A Designer_of is an Organization_or_person_in_organization_assignment
that classifies the associated
assigned_entity(organization_or_person_in_organization_select) as being
the designer of the associated items.
CLASS
Designer_of;
SUBCLASS OF (
EXPRESS:Organization_or_person_in_organization_assignment,
);
DISJOINT WITH (
Contractor,
Security_classifier_of,
Creator_of,
Maintainer_of,
Contractee,
Operator_of,
Owner_of,
User_of,
Responsible_for,
Measurer_of,
Manufacturer_of,
Assessor_of,
Executor_of,
Sender_of,
Performer_of,
Assertor_of,
Issuer_of,
Installed_in_position,
Observer_of,
Receiver_of,
Reporter_of,
);
END_CLASS;
Version:1 Stage:CommitteeSpecification Revision:0
Source:ISO 15288 Creator:Trine Hansen, DNV Created:2004-11-23
Last modified:2007-07-23
Definition:
A Development_stage is a Life_cycle_stage that classifies the associated data as having been defined within the context of
developing a
system-of-interest that can be produced, tested, evaluated, operated, supported and retired in response to acquirer requirements.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited
Definition:
message that contains ISO 10303-239 data conformant to a specified DEX.
Note: Subclass names shall identify the version of a DEX to which the data in the message conforms. This information is used
by translators to correctly decode a message.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited
Definition:
DEX message that identifies that the message contains ISO 10303-239 data conformant to the Aviation maintenance DEX version
1.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, Saab Aerotech
Definition:
DEX message that identifies that the message contains ISO 10303-239 data conformant to the Task set DEX version 1.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Trine Hansen, DNV Created:2004-11-24
Last modified:2007-07-06
Definition:
A Discipline_domain is an Application_domain that classifies the associated data as having been defined within the context
of that Discipline_domain.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Brad Harris, Eurostep Limited Created:2007-07-09
Last modified:2007-07-09
Definition:
A Disposal_process is a Technical_process that classifies the associated data as having been defined within the context of
ending the existence of a system entity.
CLASS
Disposal_process;
SUBCLASS OF (
Technical_process
);
DISJOINT WITH (
Operation_process,
Architectural_design_process,
Implementation_process,
Validation_process,
Verification_process,
Maintenance_process,
Transition_process,
Stakeholder_requirements_definition_process,
Requirements_analysis_process,
Integration_process,
);
END_CLASS;
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2005-01-12
Last modified:2007-07-13
Definition:
A Document_identification_code is an Identification_code that identifies a Document.
CONSTRAINT: An Identification_assignment classified as a Document_identification_code can only be assigned to a Document or
its subclasses where the document is not a descriptor or an information collection.
Version:1 Stage:CommitteeSpecification Revision:0
Source:UK MoD TES/ILS and Eng Pol under UK_Defence Development Programme Source:PLCS OASIS Creator:Leif Gyllstrom, Saab Aerotech Created:2005-12-15
Last modified:2009-07-06
Definition:
name by which a Document is known.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, Saab Aerotech
Last modified:2009-06-30
Definition:
document assignment that determines that the associated document is a source for reference.
Version:1 Stage:CommitteeSpecification Revision:0
Source: Creator: Created:
Last modified:2007-07-23
Definition:
A Document_version_identification_code is a Version_identification_code that identifies a particular version of a document.
CONSTRAINT: An Identification_assignment classified as a Document_version_identification_code can only be assigned to a Document_version
or its subclasses.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Source:http://www.dnb.com/us/duns_update/index.html Creator:Rob Bodington, Eurostep Limited Created:2004-03-02
Last modified:2007-07-13
Definition:
A DUNS_code is an Organization_identification_code.
A D-U-N-S Number is a nine-digit sequence allocated by DUNN and Bradstreet for identifying an organization.
For further details see: http://www.dnb.com/us/duns_update/index.html
CONSTRAINT: An Identification_assignment classified as a DUNS_code can only be assigned to an Organization or its subclasses.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, Saab Aerotech
Last modified:2009-06-30
Definition:
condition that defines the effectivity domain for an associated Effectivity.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, Saab Aerotech
Definition:
condition_assignment that assigns a domain of applicability to an instance of Effectivity, or subclass thereof.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2007-04-02
Last modified:2007-07-13
Definition:
An Effectivity_identification_code is an Identification_code that is used to identify a Effectivity.
CONSTRAINT: An Identification_assignment classified as a Effectivity_identification_code can only be
assigned to a Effectivity or it subclasses.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited
Definition:
An End_location is a Location_for_activity that is the relocation of a product at the start of the activity.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Brad Harris, Eurostep Limited Created:2007-07-09
Last modified:2007-07-09
Definition:
An Enterprise_environment_management_process is an Enterprise_process
that classifies the associated data as having been defined within the context of defining and maintaining the policies and
procedures needed for the organization's business with respect to the scope of the ISO 15288 International Standard.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Trine Hansen, DNV Created:2004-11-24
Last modified:2007-07-10
Definition:
An Enterprise_process is a Process_domain that classifies the associated data as having been defined within the context of
managing the
organization's capability to acquire and supply products or services
through the initiation, support and control of projects. It provides
resources and infrastructure necessary to support projects and ensure the
satisfaction of organizational objectives and established agreements.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, Saab Aerotech
Last modified:2009-06-30
Definition:
state definiton that represents a definition of typical external physical conditions, such as average temperature, visibility,
humidity etc.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, Saab Aerotech Created:2007-05-23
Last modified:2009-06-30
Definition:
comparative condition that specifies that a relationship is an equality relationship.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, Saab Aerotech
Last modified:2009-06-30
Definition:
cost that represents the first rough cost estimate for a resource, activity or product.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Per Myrseth, DNV
Last modified:2009-06-30
Definition:
property value representation that is the result of an approximate calculation of quantity or degree or worth
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, Saab Aerotech
Last modified:2009-06-30
Definition:
trigger that defines that something is initiated as a consequence of an observation, activity, event, or change of state.
Note: Events may relate to e.g. detection of a condition or failure, to a planned or actually performed activity, to a maintenance
opportunity, or to change of a role.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Brad Harris, Eurostep Limited Created:2007-07-10
Last modified:2007-07-10
Definition:
An Executor_of is an Organization_or_person_in_organization_assignment that is assigning a person or organization to an activity
in the role of a executor. It specifies that the person or organization is executing the action. The Organization_or_person_in_organization_assignment
is typically assigned to an activity.
CLASS
Executor_of;
SUBCLASS OF (
EXPRESS:Organization_or_person_in_organization_assignment,
);
DISJOINT WITH (
Contractor,
Security_classifier_of,
Creator_of,
Maintainer_of,
Contractee,
Operator_of,
Owner_of,
User_of,
Responsible_for,
Measurer_of,
Manufacturer_of,
Assessor_of,
Sender_of,
Performer_of,
Designer_of,
Assertor_of,
Issuer_of,
Installed_in_position,
Observer_of,
Receiver_of,
Reporter_of,
);
END_CLASS;
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited
Definition:
A Failure_mode is a State_of_physical_object defines a fault or failure state that a physical object can be in.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS Creator:Leif Gyllstrom, Saab Aerotech Created:2005-12-12
Last modified:2009-07-06
Definition:
state definition identification code that identifies a Failure_mode.
CONSTRAINT: An Identification_assignment classified as a Failure_mode_definition_identification_code can only be
assigned to a State_definition or its subclasses.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS Creator:Leif Gyllstrom, Saab Aerotech Created:2005-12-12
Last modified:2009-07-06
Definition:
name by which a defined Failure_mode is known.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2005-01-12
Last modified:2007-07-13
Definition:
A File_identification_code is an Idenitification_code that identifies a File.
CONSTRAINT: An Identification_assignment classified as a File_identification_code can only be assigned to a File or its subtypes.
Version:1 Stage:CommitteeSpecification Revision:0
Source:UK MoD TES/ILS and Eng Pol under UK_Defence Development Programme Creator:Tim Turner Created:2007-01-30
Last modified:2007-07-18
Definition:
A File_name is a Name by which a File is known.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2007-04-02
Last modified:2007-07-12
Definition:
A Fit_form_function_change classifies an Activity as being one that
changes the fit form and function of a part resulting in a change in part
number, serial number and NSN code
CLASS
Fit_form_function_change;
SUBCLASS OF (
Actual_maintenance_activity
);
DISJOINT WITH (
Activity_actual,
Scheduled_task,
Planned_activity,
Removal,
Actual_operational_activity,
Actual_logistics_activity,
Installation,
Lifing_extension,
Overhaul,
Directed_activity,
Controlled_exchange_activity,
Actual_maintenance_activity,
Actual_transport_activity,
);
END_CLASS;
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, Saab Aerotech
Definition:
required resource by resource item that is mandatory during task performance.
Version:1 Stage:CommitteeSpecification Revision:0
Source:OASIS PLCS Creator:Per Myrseth, DNV Created:2005-10-26
Last modified:2007-07-18
Definition:
A Functional_breakdown_element_name is a Breakdown_element_name by which a Functional_breakdown_element is known.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Tim Turner, LSC Group Created:
Last modified:2007-07-23
Definition:
A Geographic_location_identification_code is an Idenitification_code that identifies an Global_location_representation.
CONSTRAINT: An Identification_assignment classified as a Geographic_location_identification_code can only be assigned to a
Global_location_representation or its subclasses.
Version:1 Stage:CommitteeSpecification Revision:0
Source:OASIS PLCS Creator:Per Myrseth, DNV Created:2005-06-29
Last modified:2007-07-18
Definition:
A Hazard_material_user_group_name is a Name of the hazardous material user group
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Tim Turner, LSC
Definition:
A Hierarchical_relationship is a classification of a Location_relationship where the related_location represents the child
(dependant) location, and the relating_location represents the parent location. Each location shall unique in that they shall
not provide different representations of the same location. A Hierarchical_relationship may be specialised to provide a narrower
context and definition.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:
Last modified:2007-07-23
Definition:
An Identification_code is an Identifier_type where the associated identifier is structured according to a given convention,
and whose value is unique within a given context.
NOTE: Values can be singular, or they can be a concatenation of parts each with a meaning.
EXAMPLE: Tag number, serial number, package number and document number.
CLASS
Identification_code;
SUBCLASS OF (
Identifier_type
);
SUPERCLASS OF (
Zone_breakdown_identification_code,
Work_request_identification_code,
Work_order_identification_code,
Scheme_identification_code,
Message_identification_code,
Relationship_identification_code,
File_identification_code,
Interface_connection_identification_code,
Project_identification_code,
Qualification_type_identification_code,
Breakdown_element_identification_code,
Position_identification_code,
Activity_method_identification_code,
Part_identification_code,
Attachment_slot_identification_code,
Organization_type_identification_code,
Person_in_organization_identification_code,
Resource_event_identification_code,
Zone_element_identification_code,
Task_element_identification_code,
Class_identification_code,
Task_step_identification_code,
Market_identification_code,
Observation_identification_code,
Type_of_person_identification_code,
View_definition_relationship_identification_code,
Progression_identification_code,
Location_identification_code,
Product_concept_identification_code,
Product_configuration_identification_code,
State_identification_code,
Interface_connector_identification_code,
Document_identification_code,
Person_identification_code,
Contract_identification_code,
Activity_identification_code,
Breakdown_identification_code,
Resource_item_identification_code,
Information_right_identification_code,
Organization_identification_code,
State_definition_identification_code,
Certification_identification_code,
Interface_specification_identification_code,
Requirement_identification_code,
Product_group_identification_code,
Product_as_individual_identification_code,
Effectivity_identification_code,
);
END_CLASS;
Version:1 Stage:CommitteeSpecification Revision:0
Source:ISO 15926: Class - Identifier Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2004-03-02
Last modified:2007-07-13
Definition:
An Identifier_type classifies an Identification_assignment as being either a code or a name.
NOTE: Each subclass under the Identification_code and Name classes is based on an entity type in the ISO 10303-239 information
model.
These classes are place holders where business specific subclasses that add identifier, coding and naming conventions, can
be added.
One set of such business specific classes can be found under Organization_identification_code, where CAGE, DUNS and NCAGE
are defined as examples.
NOTE: This is an abstract class, in other words, the class should never be instantiated in an exchange file. Instead, subclasses
shall be instantiated.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Brad Harris, Eurostep Limited Created:2007-07-09
Last modified:2007-07-09
Definition:
An Implementation_process is a Technical_process that classifies the associated data as having been defined within the context
of producing a
specified system element.
CLASS
Implementation_process;
SUBCLASS OF (
Technical_process
);
DISJOINT WITH (
Operation_process,
Architectural_design_process,
Validation_process,
Verification_process,
Maintenance_process,
Transition_process,
Stakeholder_requirements_definition_process,
Requirements_analysis_process,
Disposal_process,
Integration_process,
);
END_CLASS;
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Tim Turner, LSC Group
Definition:
A Information_collection_assignment is a Document_assignment that assigns a document in the role of representing a collection
of information. For example, the document collecting a baseline.
Version:1 Stage:CommitteeSpecification Revision:0
Source: Creator: Created:
Last modified:2007-07-23
Definition:
An Information_collection_identification_code is an Identification_code that identifies a document which
groups a set of data elements together for a specific purpose at a given point in time.
EXAMPLE: The set of information that defines a Product Baseline.
CONSTRAINT: An Identification_assignment classified as an information_collection_identification_code can only be assigned
to a Document or its subclasses where the document is classified as being an Information_collection.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Tim Turner, LSC Group
Definition:
An Information_collection_member is a Information_collection_assignment that identifies the member(s) that constitute the
collection of information. For example, identifying the member(s) that represent a baseline task (or set of tasks) in an
information collection.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS Creator:Tim Turner, LSC Group Created:2010-01-26
Last modified:2010-01-26
Definition:
name by which an information collection is known.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Tim Turner, LSC Group
Definition:
An Information_collection_target is an Information_collection_assignment that assigns a document in the role of representing
a collection of information, to a target for which that information collection can be applied to. For example, assigning the
information collected about a baseline to an end item or product.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Brad Harris, Eurostep Limited Created:2007-07-09
Last modified:2007-07-09
Definition:
An Information_management_process is a Project_process that classifies the associated data as having been defined within the
context of providing relevant, timely, complete, valid and, if required, confidential
information to designated parties during and, as appropriate, after the
system life cycle.
Version:1 Stage:CommitteeSpecification Revision:0
Source: Creator: Created:
Last modified:2007-07-23
Definition:
An Information_right_identification_code is an Identification_code that is used to identify a Information_right.
CONSTRAINT: An Identification_assignment classified as a Information_right_identification_code can only be
assigned to a Information_right or it subclasses.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2007-04-02
Last modified:2007-07-12
Definition:
An Installation classifies an Activity as being one that installs a
reportable item in an item of equipment.
CLASS
Installation;
SUBCLASS OF (
Actual_maintenance_activity
);
DISJOINT WITH (
Activity_actual,
Scheduled_task,
Planned_activity,
Fit_form_function_change,
Removal,
Actual_operational_activity,
Actual_logistics_activity,
Lifing_extension,
Overhaul,
Directed_activity,
Controlled_exchange_activity,
Actual_maintenance_activity,
Actual_transport_activity,
);
END_CLASS;
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2007-04-02
Last modified:2007-07-12
Definition:
An Installation_effectivity is a dated effectivity representing the time when a part was fitted or installed in a position.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2007-11-20
Last modified:2007-11-20
Definition:
An Installed_in_position is a Breakdown_element_realization
that represents the fact that a part has been installed in a position.
CLASS
Installed_in_position;
SUBCLASS OF (
EXPRESS:Breakdown_element_realization,
);
DISJOINT WITH (
);
END_CLASS;
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Brad Harris, Eurostep Limited Created:2007-07-09
Last modified:2007-07-09
Definition:
An Integration_process is a Technical_process that classifies the associated data as having been defined within the context
of assembling a system that is consistent with the architectural design.
CLASS
Integration_process;
SUBCLASS OF (
Technical_process
);
DISJOINT WITH (
Operation_process,
Architectural_design_process,
Implementation_process,
Validation_process,
Verification_process,
Maintenance_process,
Transition_process,
Stakeholder_requirements_definition_process,
Requirements_analysis_process,
Disposal_process,
);
END_CLASS;
Version:1 Stage:CommitteeSpecification Revision:0
Source: Creator: Created:
Last modified:2007-07-23
Definition:
An Interface_connection_identification_code is an
Identification_code that is used to identify a Interface_connection.
CONSTRAINT: An Identification_assignment classified
as an Interface_connection_identification_code can only be
assigned to a Interface_connection or it subclasses.
Version:1 Stage:CommitteeSpecification Revision:0
Source: Creator: Created:
Last modified:2007-07-23
Definition:
An Interface_connector_identification_code is an
Identification_code that is used to identify a Interface_connector.
CONSTRAINT: An Identification_assignment classified
as an Interface_connector_identification_code can only be
assigned to a Interface_connector or it subclasses.
Version:1 Stage:CommitteeSpecification Revision:0
Source: Creator: Created:
Last modified:2007-07-23
Definition:
An Interface_specification_identification_code is an
Identification_code that is used to identify a Interface_specification.
CONSTRAINT: An Identification_assignment classified
as an Interface_specification_identification_code can only be
assigned to a Interface_specification or it subclasses.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Brad Harris, Eurostep Limited Created:2007-07-09
Last modified:2007-07-09
Definition:
An Investment_management_process is an Enterprise_process that classifies the associated data as having been defined within
the context of initiating and sustaining sufficient and suitable projects in order to meet the
objectives of the organization. This process commits the investment of
adequate organization funding and resources, and sanctions the authorities
needed to establish selected projects. It performs continued qualification
of projects to confirm they justify, or can be redirected to justify,
continued investment.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Brad Harris, Eurostep Limited Created:2007-07-10
Last modified:2007-07-10
Definition:
An Issuer_of is a type of person or organization which plays the role of issuing (originating) the item to which the person
or organization is assigned. The issuer may or may not also be the same as the owner of the item.
CLASS
Issuer_of;
SUBCLASS OF (
EXPRESS:Organization_or_person_in_organization_assignment,
);
DISJOINT WITH (
Contractor,
Security_classifier_of,
Creator_of,
Maintainer_of,
Contractee,
Operator_of,
Owner_of,
User_of,
Responsible_for,
Measurer_of,
Manufacturer_of,
Assessor_of,
Executor_of,
Sender_of,
Performer_of,
Designer_of,
Assertor_of,
Installed_in_position,
Observer_of,
Receiver_of,
Reporter_of,
);
END_CLASS;
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Tim Turner, LSC Group Created:2007-02-26
Last modified:2007-07-23
Definition:
A Justification_assignment_role is a Justification_assignment that classifies that the associated Justification is related
to the associated Item within the context
of a specific role.
NOTE: It is expected that sub-classes of this will define those specific roles.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Tim Turner, LSC
Definition:
A Justification_support_assignment_role specifies that the Justification being assigned to an item is done so in the context
of a specific role. It is expected that sub-classes of this will provide the context of the role.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2007-04-02
Last modified:2007-07-12
Definition:
A Labour_time_consumed is a Resource_property representing the number of man hours that have been consumed performing an activity.
The unit of the property is Man_hours.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited
Definition:
A Labour_time_planned is an Resource_property representing the number of man hours that have been planned for performing an
activity. The unit of the property is Man_hours.
Version:1 Stage:CommitteeSpecification Revision:0
Source:ISO/TS 10303-1019:2004 Product data representation and exchange: Application module: Product view definition Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2007-07-06
Last modified:2007-07-06
Definition:
A Life_cycle_stage is a View_definition_context that classifies the associated data as having been defined within the context
of that Life_cycle_stage.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2007-04-02
Last modified:2007-07-12
Definition:
A Lifing_extension classifies an Activity as being one that records the change of when a activity should be performed on a
product in focus.
CLASS
Lifing_extension;
SUBCLASS OF (
Actual_maintenance_activity
);
DISJOINT WITH (
Activity_actual,
Scheduled_task,
Planned_activity,
Fit_form_function_change,
Removal,
Actual_operational_activity,
Actual_logistics_activity,
Installation,
Overhaul,
Directed_activity,
Controlled_exchange_activity,
Actual_maintenance_activity,
Actual_transport_activity,
);
END_CLASS;
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Tim Turner, LSC Group Created:2007-02-26
Last modified:2007-07-23
Definition:
A Location_assignment_role is a Location_assignment that classifies that
the associated Location_for_assignment is related to the associated
Entity_for_location within the context of a specific role.
NOTE: It is expected that sub-classes of this will define those specific roles.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Tim Turner, LSC Group Created:2007-02-26
Last modified:2007-07-23
Definition:
A Location_for_activity is a Location_assignment_role that classifies that
the associated Location_for_assignment is related to the associated
Entity_for_location(Activity) within the context of a specific role.
NOTE: It is expected that sub-classes of this will define those specific roles.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2005-01-12
Last modified:2007-07-13
Definition:
A Location_identification_code is an Idenitification_code that identifies a Location.
CONSTRAINT: An Identification_assignment classified as a Location_identification_code can only be assigned to a Location or
its subclasses.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Tim Turner, LSC Group Created:2007-02-26
Last modified:2007-07-23
Definition:
A Location_relationship_role is a Location_relationship that classifies the role of the relationship between the relating
location and the related location.
NOTE: Each of the two locations that is referenced shall be unique in that they shall not provide different representations
of the same location.
NOTE: It is expected that sub-classes of this will define those specific roles.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, Saab Aerotech
Last modified:2009-06-30
Definition:
condition relationship that forms an expression which is either true or false.
Example: AND and OR
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Source:2009-06-12 Creator:Leif Gyllstrom, Saab Aerotech
Definition:
task method that supports the operation of product or returns the product to an operational state.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2005-01-12
Last modified:2007-07-16
Definition:
A Lot_identification_code is an Identification_code that identifies a lot / batch of individual parts.
CONSTRAINT: An Identification_assignment classified as a Lot_identification_code can only be assigned to a Product_group or
its subclasses..
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Brad Harris, Eurostep Limited Created:2007-07-10
Last modified:2007-07-23
Definition:
organization_or_person_in_organization_assignment that identifies the person or organization that maintains the associated
item.
EXAMPLE: This could be used to define the organization that maintains an item of equipment.
CLASS
Maintainer_of;
SUBCLASS OF (
EXPRESS:Organization_or_person_in_organization_assignment,
);
DISJOINT WITH (
Contractor,
Security_classifier_of,
Creator_of,
Contractee,
Operator_of,
Owner_of,
User_of,
Responsible_for,
Manufacturer_of,
Assessor_of,
Executor_of,
Sender_of,
Designer_of,
Assertor_of,
Issuer_of,
Observer_of,
Receiver_of,
);
END_CLASS;
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Brad Harris, Eurostep Limited Created:2007-07-09
Last modified:2007-07-09
Definition:
A Maintenance_process is a Technical_process that classifies the associated data as having been defined within the context
of sustaining the
capability of the system to provide a service.
CLASS
Maintenance_process;
SUBCLASS OF (
Technical_process
);
DISJOINT WITH (
Operation_process,
Architectural_design_process,
Implementation_process,
Validation_process,
Verification_process,
Transition_process,
Stakeholder_requirements_definition_process,
Requirements_analysis_process,
Disposal_process,
Integration_process,
);
END_CLASS;
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, Saab Aerotech Created:2009-06-12
Definition:
logistics task that defines how maintenance is to be performed on a product.
Version:1 Stage:CommitteeSpecification Revision:0
Source:OASIS PLCS Creator:Per Myrseth Created:2005-10-03
Last modified:2007-07-18
Definition:
Maintenance_task_name is a name for a maintenance task
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Trine Hansen, DNV Created:2004-11-24
Last modified:2007-07-12
Definition:
A Mandatory_identifier is an Assignment_type that is mandatory, ie it
must be preserved in any data exchange.
NOTE: The use of this classification is only relevant within the context of a given data
exchange agreement.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2007-04-02
Last modified:2007-07-23
Definition:
organization_or_person_in_organization_assignment that identifies the person or organization that made the associated item.
EXAMPLE: This could be used to define the organization that manufactured an item of equipment.
CLASS
Manufacturer_of;
SUBCLASS OF (
EXPRESS:Organization_or_person_in_organization_assignment,
);
DISJOINT WITH (
Contractor,
Security_classifier_of,
Creator_of,
Maintainer_of,
Contractee,
Operator_of,
Owner_of,
User_of,
Responsible_for,
Measurer_of,
Assessor_of,
Executor_of,
Sender_of,
Performer_of,
Designer_of,
Assertor_of,
Issuer_of,
Installed_in_position,
Observer_of,
Receiver_of,
Reporter_of,
);
END_CLASS;
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, Saab Aerotech
Last modified:2009-07-06
Definition:
idenitification code that identifies a Market.
CONSTRAINT: An Identification_assignment classified as a Market_identification_code can only be assigned to a Market.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, Saab Aerotech
Last modified:2009-07-06
Definition:
name by which a Market is known.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Mike Ward, Eurostep Limited Created:2007-01-23
Last modified:2007-07-19
Definition:
A Material_resource_item is a Resource_item that is classified as being a quantity of raw material, artefacts, tools, or equipment;
or a facility; or the use of raw materials, artefacts, tools, equipment, or facilities for a certain period of time or for
the carrying out of certain tasks in an application context.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Per Myrseth, DNV
Last modified:2009-06-30
Definition:
property value representation that in a unit of measure reflects a property of an object.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2007-11-20
Last modified:2007-11-20
Definition:
A Measurer_of is an Organization_or_person_in_organization_assignment
that classifies the associated
assigned_entity(organization_or_person_in_organization_select) as being
the person or organization that measured of the associated items. Normally a property.
EXAMPLE: This could be used to record the organization that measured a property on a product.
CLASS
Measurer_of;
SUBCLASS OF (
EXPRESS:Organization_or_person_in_organization_assignment,
);
DISJOINT WITH (
);
END_CLASS;
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2007-04-02
Last modified:2007-07-13
Definition:
An Message_identification_code is an
Identification_code that is used to identify a Message.
CONSTRAINT: An Identification_assignment classified
as a Message_identification_code can only be
assigned to a Message or its subclasses.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2004-03-02
Last modified:2007-07-23
Definition:
A Name is an Identifier_type where the associated identifier is not structured, and whose value cannot be assumed to be unique
in any context.
EXAMPLE: The name of a part or the name of a document.
CLASS
Name;
SUBCLASS OF (
Identifier_type
);
SUPERCLASS OF (
Hazard_material_user_group_name,
Breakdown_element_name,
State_definition_name,
Qualification_type_name,
Zone_breakdown_name,
Task_step_name,
Resource_item_name,
File_name,
Zone_element_name,
Product_group_name,
Document_name,
Market_name,
Organization_type_name,
Information_collection_name,
Task_method_name,
Work_request_name,
Assembly_component_name,
Type_of_person_name,
Product_concept_name,
Breakdown_name,
Organization_name,
Part_name,
Product_configuration_name,
Maintenance_task_name,
);
END_CLASS;
Version:1 Stage:CommitteeSpecification Revision:0
Source:http://www.ncb.mod.uk/ncage.htm Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2007-01-23
Last modified:2007-07-13
Definition:
A NCAGE_code is an Organization_identification_code.
Each manufacturer or supplier who provides equipment or spares to the MOD, together with other organisations who provide design
control drawings, standards or specifications, or a service to the MOD may be allocated a NATO Commercial And Government Entity
Code (NCAGE Code).
Each country in the NATO Codification System (NCS) allocates these unique 5 character codes to companies located in that country,
and within the UK they are allocated by the UK National Codification Bureau (NCB).
NCAGE codes allocated in the UK begin with U or K, suffixed by 3 alphanumeric and 1 numeric characters, whilst other nations
within the NCS have different formats, for example the USA has 3 alphanumeric characters prefixed and suffixed by a numeric
character.
NCAGE records are used to hold manufacturer/supplier details such as name, address, post code, telephone number, fax and
company e-mail address.
The NCAGE code is used along with the manufacturer/suppliers part number to form a reference which is held on the NATO Stock
Number (NSN) record.
This reference enables users of the NCS to determine who manufactures/supplies the Item of Supply.
For further details see: http://www.ncb.mod.uk/ncage.htm
CONSTRAINT: An Identification_assignment classified as an NCAGE_code can only be assigned to an Organization or its subclasses.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, Saab Aerotech
Last modified:2009-06-30
Definition:
probability numeric that is expressed as a numeric value between 0 and 1.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, Saab Aerotech
Last modified:2009-06-30
Definition:
computable condition that requires the condition parameter(s) to be false in order for the Condition to be true.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PDM Schema usage guide Creator:Mike Ward, Eurostep Limited Created:2007-01-23
Last modified:2007-07-11
Definition:
approval_status that denotes no official acceptance as yet.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited
Definition:
A NSN_code is a NATO_code that identifies the
items of supply.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2007-04-02
Last modified:2007-07-13
Definition:
An Observation_identification_code is an Identification_code that is used to identify an Observation.
CONSTRAINT: An Identification_assignment classified as a Observation_identification_code can only be
assigned to a Observation or its subclasses.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Brad Harris, Eurostep Limited Created:2007-07-10
Last modified:2007-07-23
Definition:
An Observer_of is an Organization_or_person_in_organization_assignment that classifies the associated assigned_entity(organization_or_person_in_organization_select)
as being the observer of the associated items.
EXAMPLE: This could be used to define the person who observed a fault on an item of equipment.
CLASS
Observer_of;
SUBCLASS OF (
EXPRESS:Organization_or_person_in_organization_assignment,
);
DISJOINT WITH (
Contractor,
Security_classifier_of,
Creator_of,
Maintainer_of,
Contractee,
Operator_of,
Owner_of,
User_of,
Responsible_for,
Measurer_of,
Manufacturer_of,
Assessor_of,
Executor_of,
Sender_of,
Performer_of,
Designer_of,
Assertor_of,
Issuer_of,
Installed_in_position,
Receiver_of,
Reporter_of,
);
END_CLASS;
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, Saab Aerotech Created:2009-06-30
Definition:
maintenance task that requires the task target item to be removed from the end item.
Note: Also see the class Task_product_on_off_classification_code.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, Saab Aerotech
Definition:
maintenance task that can be performed without removing the task target item from the end item.
Note: Also see the class Task_product_on_off_classification_code.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Brad Harris, Eurostep Limited Created:2007-07-09
Last modified:2007-07-09
Definition:
An Operation_process is a Technical_process that classifies the associated data as having been defined within the context
of using the system in order to deliver its services.
CLASS
Operation_process;
SUBCLASS OF (
Technical_process
);
DISJOINT WITH (
Architectural_design_process,
Implementation_process,
Validation_process,
Verification_process,
Maintenance_process,
Transition_process,
Stakeholder_requirements_definition_process,
Requirements_analysis_process,
Disposal_process,
Integration_process,
);
END_CLASS;
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, Saab Aerotech
Last modified:2009-06-30
Definition:
condition parameter that defines that the Condition is to be evaluated against a defined operational environment.
Note: The condition parameter must be an instance of State_definition classified as a subclass of Environment_typical.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, Saab Aerotech
Last modified:2009-06-30
Definition:
state of physical object that is characterized by the list of actions that can be performed by the product.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, Saab Aerotech
Last modified:2009-06-30
Definition:
condition parameter that defines that the Condition is to be evaluated against a defined operational state for the Product.
Note: The condition parameter must be an instance of State_definition classified as a subclass of Operational_state.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, Saab Aerotech Created:2009-06-12
Definition:
task method that is to be performed by a product during its intended use.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Brad Harris, Eurostep Limited Created:2007-07-10
Last modified:2007-07-23
Definition:
An Operator_of is an Organization_or_person_in_organization_assignment that classifies the associated assigned_entity(organization_or_person_in_organization_select)
as being the operator of the associated items.
EXAMPLE: This could be used to define the operator of an item of equipment.
CLASS
Operator_of;
SUBCLASS OF (
EXPRESS:Organization_or_person_in_organization_assignment,
);
DISJOINT WITH (
Contractor,
Security_classifier_of,
Creator_of,
Maintainer_of,
Contractee,
Owner_of,
User_of,
Responsible_for,
Measurer_of,
Manufacturer_of,
Assessor_of,
Executor_of,
Sender_of,
Performer_of,
Designer_of,
Assertor_of,
Issuer_of,
Installed_in_position,
Observer_of,
Receiver_of,
Reporter_of,
);
END_CLASS;
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS Creator:Leif Gyllstrom, Saab Aerotech Created:2007-03-23
Last modified:2009-07-06
Definition:
organization name that is an abbreviation of the name by which an Organization in known.
Example:: 'A' as an abbreviation of 'Army'.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Tim Turner, LSC Group Created:2007-01-30
Last modified:2007-07-13
Definition:
An Organization_based_location_identification_code is an Idenitification_code that identifies an Organizational_based_location_representation.
CONSTRAINT: An Identification_assignment classified as an Organization_based_location_identification_code can only be assigned
to an Organizational_based_location_representation or its subclasses.
Version:1 Stage:CommitteeSpecification Revision:0
Source:ISO 15926: Class - Organization code Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2004-03-02
Last modified:2007-07-13
Definition:
An Organization_identification_code is an identification_code that identifies an organization.
CONSTRAINT: An Identification_assignment classified as an Organization_identification_code can only be assigned to an Organization
or its subclasses.
Version:1 Stage:CommitteeSpecification Revision:0
Source:UK MoD TES/ILS and Eng Pol under UK_Defence Development Programme Creator:Tim Turner, LSC Group Created:2004-11-24
Last modified:2007-07-23
Definition:
An Organization_name is a Name by which an Organization is known.
EXAMPLE:: OntologiesRus Ltd
Version:1 Stage:CommitteeSpecification Revision:0
Source: Creator:Leif Gyllstrom, Saab Aerotech Created:2007-05-23
Last modified:2007-07-13
Definition:
iIdentification code that identifies an Organization_type.
CONSTRAINT: An Identification_assignment classified as an Organization_type_identification_code can only be
assigned to a Organization_type or its subclasses.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS Creator:Leif Gyllstrom, Saab Aerotech Created:2007-05-23
Last modified:2009-07-06
Definition:
name by which a type of Organization is known.
Example: Government organization, Supplier, First line maintenance.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Tim Turner, LSC Group Created:2007-01-30
Last modified:2007-07-13
Definition:
An Organizational_location_identification_code is an Idenitification_code that identifies an Organizational_location_identification.
CONSTRAINT: An Identification_assignment classified as an Organizational_location_identification_code can only be assigned
to an Organizational_location_identification or its subclasses.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2007-04-02
Last modified:2007-07-12
Definition:
An Overhaul classifies an Activity as being one that overhauls a
reportable item.
CLASS
Overhaul;
SUBCLASS OF (
Actual_maintenance_activity
);
DISJOINT WITH (
Activity_actual,
Scheduled_task,
Planned_activity,
Fit_form_function_change,
Removal,
Actual_operational_activity,
Actual_logistics_activity,
Installation,
Lifing_extension,
Directed_activity,
Controlled_exchange_activity,
Actual_maintenance_activity,
Actual_transport_activity,
);
END_CLASS;
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2007-01-23
Last modified:2007-07-23
Definition:
An Owner_of is an Organization_or_person_in_organization_assignment that classifies the associated assigned_entity(organization_or_person_in_organization_select)
as being the owner of the associated items.
EXAMPLE: This could be used to define the person who owns an item of equipment.
CLASS
Owner_of;
SUBCLASS OF (
EXPRESS:Organization_or_person_in_organization_assignment,
);
DISJOINT WITH (
Contractor,
Security_classifier_of,
Creator_of,
Maintainer_of,
Contractee,
Operator_of,
User_of,
Responsible_for,
Measurer_of,
Manufacturer_of,
Assessor_of,
Executor_of,
Sender_of,
Performer_of,
Designer_of,
Assertor_of,
Issuer_of,
Installed_in_position,
Observer_of,
Receiver_of,
Reporter_of,
);
END_CLASS;
Version:1 Stage:CommitteeSpecification Revision:0
Source:OASIS PLCS Creator:Per Myrseth, DNV Created:2005-10-18
Last modified:2007-07-18
Definition:
A Part_block_name is Name that is the the human readable identifier of a block
Version:1 Stage:CommitteeSpecification Revision:0
Source:OASIS PLCS Creator:Per Myrseth, DNV Created:2005-09-15
Last modified:2007-07-18
Definition:
A Part_category_name is a Product_group_name by which Part_category is known.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, Saab Aerotech Created:2009-06-12
Definition:
class identification code that identifies a class that defines a specialization of Part regardless of its version, application
domain or life cycle stage.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, Saab Aerotech Created:2009-06-30
Definition:
part view classification that classifies the part inherent property involving or exposing one to risk (as of loss or harm).
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2007-01-23
Last modified:2007-07-23
Definition:
A Part_identification_code is an Identification_code that identifies a type of part.
EXAMPLE: A part number.
CONSTRAINT: An Identification_assignment classified as a Part_identification_code can
only be assigned to a Part or its subclasses.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, Saab Aerotech
Definition:
part view classification that determines the maturity a part with respect to distribution, availability or support
Version:1 Stage:CommitteeSpecification Revision:0
Source:OASIS PLCS Creator:Per Myrseth, DNV Created:2005-10-18
Last modified:2007-07-18
Definition:
A Part_module_name is the human readable identifier of a module
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Trine Hansen, DNV Created:2004-11-24
Last modified:2007-07-18
Definition:
A Part_name is a Name by which a Part is known.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, Saab Aerotech
Definition:
part view classification that determines the ability of a damaged or failed part to be restored to acceptable operating condition.
Example: Discardable, Partial_repairable and Fully_repairable
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Tim Turner, LSC Group Limited Created:
Last modified:2007-07-23
Definition:
A Part_version_identifcation_code is a Version_identifcation_code that identifies a particular version of a part.
NOTE: A part design will be identified by its part number (a Part_identification_code) whereas a Part_version_identification_code
identifies the version of a part.
EXAMPLE: Rev A, Rev B.
CONSTRAINT: An Identification_assignment classified as a Part_version_identification_code can only be assigned to a Part_version
or its
subclasses.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, Saab Aerotech Created:2009-02-12
Definition:
class identification code that identifies a class that classifies a Part from specific application domain point of view.
Version:1 Stage:CommitteeSpecification Revision:0
Source:OASIS PLCS Creator:Per Myrseth, DNV Created:2005-10-25
Last modified:2007-07-18
Definition:
A Part_work_breakdown_element_name is the human readable identifier of a part work breakdown element
Version:1 Stage:CommitteeSpecification Revision:0
Source:OASIS PLCS Creator:Per Myrseth, DNV Created:2005-10-18
Last modified:2007-07-18
Definition:
A Part_zone_name is a name that is the human readable identifier of a zone.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, SAAB
Definition:
Assignment of defined portion of a Document to something in the role of being a source for reference.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, Saab Aerotech
Last modified:2009-06-30
Definition:
probability numeric that is expressed as a numeric value between 0 and 100.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2007-11-20
Last modified:2007-11-20
Definition:
A Performer_of is an Organization_or_person_in_organization_assignment
that classifies the associated
assigned_entity(organization_or_person_in_organization_select) as being
the performer of the associated items. Normally an activity.
EXAMPLE: This could be used to
record the organization that undertook some maintenance an item of equipment.
CLASS
Performer_of;
SUBCLASS OF (
EXPRESS:Organization_or_person_in_organization_assignment,
);
DISJOINT WITH (
);
END_CLASS;
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, Saab Aerotech
Last modified:2009-06-30
Definition:
condition parameter that defines that the Condition is to be evaluated against a defined performing Organization.
Note: The condition parameter must be an instance of Organization or Organization_type.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited
Last modified:2009-06-30
Definition:
independent property that defines the interval between activities.
Note: This may be defined as time interval or as number of events, such as number of landings.
CLASS
Periodicity;
SUBCLASS OF (
EXPRESS:Independent_property,
);
END_CLASS;
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2007-01-23
Last modified:2007-07-23
Definition:
A Person_identification_code is an Identification_code that is used to uniquely identify a person.
EXAMPLE: A persons social security number.
CONSTRAINT: An Identification_assignment classified as a Person_identification_code can only be assigned to Person or its
subclasses.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2007-01-23
Last modified:2007-07-23
Definition:
A Person_in_organization_identification_code is an
Identification_code used to identify a person in the context of
an organizations.
EXAMPLE: An employee code.
CONSTRAINT: An Identification_assignment classified as a Person_in_organization_identification_code can only be assigned to
Person_in_organization or its subclasses.
Version:1 Stage:CommitteeSpecification Revision:0
Source:OASIS PLCS Creator:Per Myrseth, DNV Created:2005-10-26
Last modified:2007-07-18
Definition:
A Physical_breakdown_element_name is a Breakdown_element_name by which a Physical_element in a breakdown is known.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited
Definition:
A Planned_activity is an activity that has not started and is planned to start sometime in the future.
CLASS
Planned_activity;
SUBCLASS OF (
EXPRESS:Activity,
);
DISJOINT WITH (
Activity_actual,
Scheduled_task,
Fit_form_function_change,
Removal,
Actual_operational_activity,
Actual_logistics_activity,
Installation,
Lifing_extension,
Overhaul,
Directed_activity,
Controlled_exchange_activity,
Actual_maintenance_activity,
Actual_transport_activity,
);
END_CLASS;
Version:1 Stage:CommitteeSpecification Revision:0
Source: Creator: Created:
Last modified:2007-07-23
Definition:
An Position_identification_code is an Identification_code that is used to identify a Position.
CONSTRAINT: An Identification_assignment classified as a Position_identification_code can only be
assigned to a Position or its subclasses.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, Saab Aerotech
Last modified:2009-06-30
Definition:
condition parameter that defines that the Condition is to be evaluated against a defined position within a Product.
Note: The condition parameter must be an instance of Breakdown_element_version.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, Saab Aerotech
Last modified:2009-06-30
Definition:
condition assignment that defines that the associated condition must happen or be done before the assigned thing can cease
or cease to exist.
CLASS
Post_condition;
SUBCLASS OF (
EXPRESS:Condition_assignment,
);
END_CLASS;
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, Saab Aerotech
Last modified:2009-06-30
Definition:
condition assignment that defines that the associated condition must happen or be done before the assigned thing can happen
or exist.
CLASS
Precondition;
SUBCLASS OF (
EXPRESS:Condition_assignment,
);
END_CLASS;
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Trine Hansen, DNV Created:2004-11-24
Last modified:2007-07-12
Definition:
A Preferred_identifier is an Assignment_type that is the preferred
identification to be used.
NOTE: This identification is intended to be globally unique.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Trine Hansen, DNV Created:2004-11-24
Last modified:2007-07-06
Definition:
A Process_domain is an Application_domain that classifies the associated
data as having been defined within the context of that Process_domain.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2005-01-12
Last modified:2007-07-16
Definition:
A Product_as_individual_identification_code is an Identification_code that is used to identify an actual part.
CONSTRAINT: An Identification_assignment classified as a Product_as_individual_identification_code can only be assigned to
Product_as_realized or a Product_as_planned or its subclasses.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Tim Turner, LSC Group Created:2006-06-14
Last modified:2007-07-13
Definition:
A Product_location_identification_code is an Idenitification_code that identifies an Product_based_location_representation.
CONSTRAINT: An Identification_assignment classified as a Product_location_identification_code can only be assigned to a Product_based_location_representation
or its subclasses.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2004-03-02
Last modified:2007-07-23
Definition:
A Product_concept_identification_code is a Identification_code used to identify a Product_concept,
that is a set of similar products that were, are or will be proposed to customers.
EXAMPLE: A VW Golf.
CONSTRAINT: An Identification_assignment classified as a Product_concept_identification_code can only be assigned to a
Product_concept or its subclasses.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS Creator:Leif Gyllstrom, Saab Aerotech Created:2006-01-04
Last modified:2009-07-06
Definition:
name by which a Product_concept is known.
Example: VW Golf.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, Saab Aerotech
Last modified:2009-06-30
Definition:
condition parameter that defines that the Condition is to be evaluated against a defined product.
Note: The condition parameter must be an instance of Part_version.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, Saab Aerotech
Last modified:2009-06-30
Definition:
condition parameter that defines that the Condition is to be evaluated against a defined product configuration.
Note: The condition parameter must be an instance of Product_configuration.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2007-01-23
Last modified:2007-07-23
Definition:
A Product_configuration_identification_code is an Identification_code that identifies a particular configuration of a product.
EXAMPLE: A VW Golf configured with drivers airbags and stereo.
CONSTRAINT: An Identification_assignment classified as a Product_configuration_identification_code can only be assigned to
a Product_configuration or its subclasses.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, Saab Aerotech
Last modified:2009-07-06
Definition:
name by which a Product_configuration is known.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2005-01-12
Last modified:2007-07-23
Definition:
A Product_group_identification_code is an Identification_code that identifies a group of products.
EXAMPLE: The identification of a batch or lot of parts according to a given identification system.
CONSTRAINT: An Identification_assignment classified as a Product_group_identification_code can only be assigned to a Product_group
or its subclasses..
Version:1 Stage:CommitteeSpecification Revision:0
Source:OASIS PLCS Creator:Per Myrseth, DNV Created:2005-10-12
Last modified:2007-07-18
Definition:
A Product_group_name is a Name by which a Product_group is known.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2007-01-23
Last modified:2007-07-20
Definition:
A Product_life_cycle_support is a Discipline_domain that classifies the associated data as having been defined within the
context of Product life cycle
support.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, Saab Aerotech
Last modified:2009-06-30
Definition:
condition parameter that defines that the Condition is to be evaluated against a defined Product modification.
Note: The condition parameter must be an instance of Work_request.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2007-01-23
Last modified:2007-07-20
Definition:
A Product_usage is an Applied_activity_assignment that classifies that the
associated item can or has performed the associated assigned_activity.
CONSTRAINT: An Applied_activity_assignment classified as a Product_usage can
only assign items that are either a Product_as_realized, a
Product_as_planned, a Part or their subtypes.
CLASS
Product_usage;
SUBCLASS OF (
EXPRESS:Applied_activity_assignment,
);
END_CLASS;
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, Saab Aerotech
Last modified:2009-06-30
Definition:
condition parameter that defines that the Condition is to be evaluated against a defined Product variant.
Note: The condition parameter must be an instance of Part_version.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, Saab Aerotech
Last modified:2009-06-30
Definition:
condition parameter that defines that the Condition is to be evaluated against a defined zone within a product.
Note: The condition parameter must be an instance of Zone_element_version.
Version:1 Stage:CommitteeSpecification Revision:0
Source:ISO 15288 Creator:Trine Hansen, DNV Created:2004-11-23
Last modified:2007-07-23
Definition:
A Production_stage is a Life_cycle_stage that classifies the associated data as having been defined within the context of
producing or
manufacturing the product, testing the product and producing related
supporting and enabling systems as needed.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2007-01-23
Last modified:2007-07-23
Definition:
A Progression_identifcation_code is an Identifier_type that is used to track the evolution or modification of something.
The code is normally
sequential and encoded according to some convention.
EXAMPLE: The version numbers of a part design or the revision numbers of software code.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Brad Harris, Eurostep Limited Created:2007-07-09
Last modified:2007-07-09
Definition:
A Project_assessment_process is a Project_process that classifies the associated data as having been defined within the context
of determining the status of the project.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Brad Harris, Eurostep Limited Created:2007-07-09
Last modified:2007-07-09
Definition:
A Project_control_process is a Project_process that classifies the associated data as having been defined within the context
of directing project
plan execution and ensuring that the project performs according to plans
and schedules, within projected budgets and it satisfies technical
objectives.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2004-01-14
Last modified:2007-07-23
Definition:
A Project_identification_code is an Identification_code that identifies a project.
EXAMPLE: The project code which is used to identify the project against which time is booked.
CONSTRAINT: An Identification_assignment classified as a Project_identification_code can only be assigned to a Project or
its subclasses.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Brad Harris, Eurostep Limited Created:2007-07-09
Last modified:2007-07-09
Definition:
A Project_planning_process is Project_process that that classifies the associated data as having been defined within the
context of producing and
communicating effective and workable project plans.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Trine Hansen, DNV Created:2004-11-24
Last modified:2007-07-10
Definition:
A Project_process is a Process_domain that classifies the associated data as having been defined within the context of establishing
and
evolving project plans, assessing actual achievement and progress against
the plans and controlling execution of the project through to fulfilment.
Individual project processes may be invoked at any time in the life cycle
and at any level in a hierarchy of projects, as required by project plans
or unforeseen events. A project process is applied with a level of rigour
and formality that depends on the risk and complexity of the project.
CLASS
Project_process;
SUBCLASS OF (
Process_domain
);
SUPERCLASS OF (
Risk_management_process,
Decision_making_process,
Project_assessment_process,
Configuration_management_process,
Project_control_process,
Information_management_process,
Project_planning_process,
);
DISJOINT WITH (
Agreement_process,
Technical_process,
Enterprise_process,
);
END_CLASS;
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2005-01-12
Last modified:2007-07-16
Definition:
A Qualification_type_identification_code is an Identification_code that identifies a Qualification.
CONSTRAINT: An Identification_assignment classified as a Qualification_type_identification_code can only be assigned to a
Qualification or its subclasses.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS Creator:Leif Gyllstrom, Saab Aerotech Created:2007-05-23
Last modified:2009-07-06
Definition:
name by which a type of Qualification is known.
Example: Ph.D.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Brad Harris, Eurostep Limited Created:2007-07-09
Last modified:2007-07-09
Definition:
A Quality_management_process is an Enterprise_process that classifies the associated data as having been defined within the
context of assuring that products, services and implementations of life cycle processes meet
enterprise quality goals and achieve customer satisfaction.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2007-04-02
Last modified:2007-07-12
Definition:
An Quantity is a property representing a quantity of something.
EXAMPLE: 10 bolts. 10 litres of oil
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Brad Harris, Eurostep Limited Created:2007-07-10
Last modified:2007-07-23
Definition:
A Receiver_of is an Organization_or_person_in_organization_assignment that
classifies the associated
assigned_entity(organization_or_person_in_organization_select) as being
the receiver of the associated items.
EXAMPLE: This could be used to define the person that has received a message.
CLASS
Receiver_of;
SUBCLASS OF (
EXPRESS:Organization_or_person_in_organization_assignment,
);
DISJOINT WITH (
Contractor,
Security_classifier_of,
Creator_of,
Maintainer_of,
Contractee,
Operator_of,
Owner_of,
User_of,
Responsible_for,
Measurer_of,
Manufacturer_of,
Assessor_of,
Executor_of,
Sender_of,
Performer_of,
Designer_of,
Assertor_of,
Issuer_of,
Installed_in_position,
Observer_of,
Reporter_of,
);
END_CLASS;
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Tim Turner, LSC Group Created:2007-01-30
Last modified:2007-07-13
Definition:
A Regional_grid_location_identification_code is an Idenitification_code that identifies an Regional_grid_location_representation.
CONSTRAINT: An Identification_assignment classified as a Regional_grid_location_identification_code can only be assigned to
a Regional_grid_location_representation or its subclasses.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Mike Ward, Eurostep Limited Created:2007-01-23
Last modified:2007-07-23
Definition:
approval_status that denotes a failure to gain approval.
NOTE: The equivalent term in the PDM Schema Usage Guide is disapproved.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited
Definition:
A Relationship_identification_code is an Identification_code that identifies a View_definition_relationship.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2007-04-02
Last modified:2007-07-12
Definition:
A Removal classifies an Activity as being one that removes a
reportable item in an item of equipment.
CLASS
Removal;
SUBCLASS OF (
Actual_maintenance_activity
);
DISJOINT WITH (
Activity_actual,
Scheduled_task,
Planned_activity,
Fit_form_function_change,
Actual_operational_activity,
Actual_logistics_activity,
Installation,
Lifing_extension,
Overhaul,
Directed_activity,
Controlled_exchange_activity,
Actual_maintenance_activity,
Actual_transport_activity,
);
END_CLASS;
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, Saab Aerotech
Last modified:2009-06-30
Definition:
description that describes how to remove the associated object from its end item.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, Saab Aerotech Created:2008-03-06
Last modified:2009-07-06
Definition:
task method identification code that identifies a method that can be used in order to remove an item from its end item.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2007-11-20
Last modified:2007-11-20
Definition:
A Reporter_of is an Organization_or_person_in_organization_assignment
that classifies the associated assigned_entity(organization_or_person_in_organization_select) as being
the reporter of the associated items. Normally an activity or a property
EXAMPLE: This could be used to record the organization that reported on some maintenance activity.
CLASS
Reporter_of;
SUBCLASS OF (
EXPRESS:Organization_or_person_in_organization_assignment,
);
DISJOINT WITH (
);
END_CLASS;
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, Saab Aerotech
Definition:
required resource relationship that determines that the relating required resource can be found and be used instead of the
other.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, Saab Aerotech
Definition:
required resource relationship that determines that the relating required resource can take the place or perform the function
of the other required resource.
Note: Not necessarily the other way around.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, Saab Aerotech
Definition:
required resource relationship that determines that the related required resource is replaced by the relating required resource.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2005-01-12
Last modified:2007-07-16
Definition:
A Requirement_identification_code is an Idenitification_code that identifies a Requirement.
CONSTRAINT: An Identification_assignment classified as a Requirement_identification_code can only be assigned to a Requirement
or its
subclasses.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Brad Harris, Eurostep Limited Created:2007-07-09
Last modified:2007-07-09
Definition:
A Requirements_analysis_process is a Technical_process that classifies the associated data as having been defined within the
context of transforming the stakeholder, requirement-driven view of desired services into a
technical view of a required product that could deliver those services.
CLASS
Requirements_analysis_process;
SUBCLASS OF (
Technical_process
);
DISJOINT WITH (
Operation_process,
Architectural_design_process,
Implementation_process,
Validation_process,
Verification_process,
Maintenance_process,
Transition_process,
Stakeholder_requirements_definition_process,
Disposal_process,
Integration_process,
);
END_CLASS;
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Mike Ward, Eurostep Limited Created:2007-01-23
Last modified:2007-07-20
Definition:
A Resource_as_realized_consumed_by is a Resource_as_realized_assignment that classifies that the associated item(activity)
consumes the associated assigned_resource.
CONSTRAINT: A Resource_as_realized_assignment classified as a Resource_as_realized_consumed_by can only be
assigned to an Activity_actual, Applied_activity_assignment, Event, Relative_event or their subclasses.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Mike Ward, Eurostep Limited Created:2007-01-23
Last modified:2007-07-20
Definition:
A Resource_as_realized_employed_by is a Resource_as_realized_assignment
that classifies that the associated item(activity) employs or uses the
associated assigned_resource without consuming it.
CONSTRAINT: A Resource_as_realized_assignment classified as a
Resource_as_realized_employed_by can only be assigned to an
Activity_actual, Applied_activity_assignment, Event, Relative_event or
their subclasses.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2005-01-12
Last modified:2007-07-23
Definition:
A Resource_event_identification_code is an Identification_code that identifies a Resource_event.
EXAMPLE: A transaction within a stock control system.
CONSTRAINT: An Identification_assignment classified as a Resource_event_identification_code can only be assigned to a Resource_event
or its subclasses.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2005-01-12
Last modified:2007-07-16
Definition:
A Resource_item_identification_code is an Idenitification_code that identifies a Resource_item.
CONSTRAINT: An Identification_assignment classified as a Resource_item_identification_code can only be
assigned to a Resource_item or its subclasses.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS Creator:Leif Gyllstrom, Saab Aerotech Created:2007-03-01
Last modified:2009-07-06
Definition:
name by which a Resource_item is known.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Brad Harris, Eurostep Limited Created:2007-07-09
Last modified:2007-07-09
Definition:
A Resource_management_process is an Enterprise_process that classifies the associated data as having been defined within the
context of providing resources to projects. This process provides resources, materials and
services to projects to support organization and project objectives
throughout the life cycle. This includes a supply of educated, skilled and
experienced personnel qualified to perform life cycle processes. This
process assures that there is effective co-ordination and sharing of
resources, information and technologies.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, SAAB
Last modified:2009-06-30
Definition:
resource property that represents the planned or expected time that a Resource will be fully or partially occupied by an activity.
Note: The time may be measured in units such as Hours, Minutes, Seconds.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Brad Harris, Eurostep Limited Created:2007-07-10
Last modified:2007-07-10
Definition:
Responsible_for is an Organization_or_person_in_organization_assignment that is assigning a person or organization to something
in the role of responsible for. It specifies that the person or organization is responsible for the information.
CLASS
Responsible_for;
SUBCLASS OF (
EXPRESS:Organization_or_person_in_organization_assignment,
);
DISJOINT WITH (
Contractor,
Security_classifier_of,
Creator_of,
Maintainer_of,
Contractee,
Operator_of,
Owner_of,
User_of,
Measurer_of,
Manufacturer_of,
Assessor_of,
Executor_of,
Sender_of,
Performer_of,
Designer_of,
Assertor_of,
Issuer_of,
Installed_in_position,
Observer_of,
Receiver_of,
Reporter_of,
);
END_CLASS;
Version:1 Stage:CommitteeSpecification Revision:0
Source:ISO 15288 Creator:Trine Hansen, DNV Created:2004-11-23
Last modified:2007-07-23
Definition:
A Retirement_stage is a Llife_cycle_stage that classifies the associated data as having been defined within the context of
providing for
the removal of a system-of-interest and related operational and support
services, and the operation and support the retirement system itself.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Brad Harris, Eurostep Limited Created:2007-07-09
Last modified:2007-07-09
Definition:
A Risk_management_process is a Project_process that classifies the associated data as having been defined within the context
of reducing the
effects of uncertain events that may result in changes to quality, cost,
schedule or technical characteristics.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2007-04-02
Last modified:2007-07-12
Definition:
A Scheduled_task classifies an Activity as being one that is a scheduled task on a reportable item.
CLASS
Scheduled_task;
SUBCLASS OF (
EXPRESS:Activity,
);
DISJOINT WITH (
Activity_actual,
Planned_activity,
Fit_form_function_change,
Removal,
Actual_operational_activity,
Actual_logistics_activity,
Installation,
Lifing_extension,
Overhaul,
Directed_activity,
Controlled_exchange_activity,
Actual_maintenance_activity,
Actual_transport_activity,
);
END_CLASS;
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, Saab Aerotech
Last modified:2009-06-30
Definition:
trigger that defines that something is initiated with a specified periodicity or interval.
Note: May be expressed in units of time or count (quantity of events).
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2005-01-12
Last modified:2007-07-16
Definition:
A Scheme_identification_code is an Idenitification_code that identifies a Scheme.
CONSTRAINT: An Identification_assignment classified as a Scheme_identification_code can only be
assigned to a Scheme or its subclasses.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS Oasis Creator:Tim Turner Created:2006-03-21
Last modified:2007-07-16
Definition:
A Scheme_version_history is a Scheme_version_identification_code that identifies a Scheme_version_relationship (that relates
two scheme_versions together).
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS Oasis Creator:Tim Turner Created:2006-03-21
Last modified:2007-07-16
Definition:
A Scheme_version_identification_code is a Version_identification_code that identifies a particular version of a scheme.
CONSTRAINT: An Identification_assignment classified as a Scheme_version_identification_code can only be assigned to a Scheme_version
or its subclasses.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Brad Harris, Eurostep Limited Created:2007-07-10
Last modified:2007-07-10
Definition:
A Security_classifier_of is an
Organization_or_person_in_organization_assignment that classifies the
associated assigned_entity(organization_or_person_in_organization_select)
as being that which assigned the associated
items(security_classification_assignment).
CLASS
Security_classifier_of;
SUBCLASS OF (
EXPRESS:Organization_or_person_in_organization_assignment,
);
DISJOINT WITH (
Contractor,
Creator_of,
Maintainer_of,
Contractee,
Operator_of,
Owner_of,
User_of,
Responsible_for,
Measurer_of,
Manufacturer_of,
Assessor_of,
Executor_of,
Sender_of,
Performer_of,
Designer_of,
Assertor_of,
Issuer_of,
Installed_in_position,
Observer_of,
Receiver_of,
Reporter_of,
);
END_CLASS;
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Brad Harris, Eurostep Limited Created:2007-07-10
Last modified:2007-07-23
Definition:
A Sender_of is an Organization_or_person_in_organization_assignment
that classifies the associated
assigned_entity(organization_or_person_in_organization_select) as being
the sender of the associated items.
EXAMPLE: This could be used to define the person that has sent a message.
CLASS
Sender_of;
SUBCLASS OF (
EXPRESS:Organization_or_person_in_organization_assignment,
);
DISJOINT WITH (
Contractor,
Security_classifier_of,
Creator_of,
Maintainer_of,
Contractee,
Operator_of,
Owner_of,
User_of,
Responsible_for,
Measurer_of,
Manufacturer_of,
Assessor_of,
Executor_of,
Performer_of,
Designer_of,
Assertor_of,
Issuer_of,
Installed_in_position,
Observer_of,
Receiver_of,
Reporter_of,
);
END_CLASS;
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, Saab Aerotech
Last modified:2009-06-30
Definition:
effectivity context that defines the Product context for which an associated Serial_effectivity is defined.
Version:1 Stage:CommitteeSpecification Revision:0
Source:ISO 15926: Class - Serial identification code Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2004-03-02
Last modified:2007-07-16
Definition:
A Serial_identification_code is a Product_as_individual_identification_code
that is used to identify an actual part.
NOTE: It is typically assigned by the manufacturing organization. The code could consist of characters only,
numbers only or a combination of characters and numbers (i.e. an alphanumeric code).
NOTE: Serial number is a Serial_identification_code.
CONSTRAINT: An Identification_assignment classified as a Serial_identification_code can only be assigned to a Product_as_individual
or its subclasses.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, Saab Aerotech
Last modified:2009-06-30
Definition:
task method that requires resources which needs to be highlighted from a planning/scheduling perspective.
Example: Special tools.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Brad Harris, Eurostep Limited Created:2007-07-09
Last modified:2007-07-09
Definition:
A Stakeholder_requirements_definition_process is a Technical_process that classifies the associated data as having been defined
within the context of defining the requirements for a system that can provide the services
needed by users and other stakeholders in a defined environment.
CLASS
Stakeholder_requirements_definition_process;
SUBCLASS OF (
Technical_process
);
DISJOINT WITH (
Operation_process,
Architectural_design_process,
Implementation_process,
Validation_process,
Verification_process,
Maintenance_process,
Transition_process,
Requirements_analysis_process,
Disposal_process,
Integration_process,
);
END_CLASS;
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited
Definition:
A Start_location is a Location_for_activity that is the relocation of a product at the start of the activity.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2005-01-12
Last modified:2007-07-16
Definition:
A State_definition_identification_code is an Idenitification_code that identifies a State_definition.
CONSTRAINT: An Identification_assignment classified as a State_definition_identification_code can only be
assigned to a State_definition or its subclasses.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS Creator:Leif Gyllstrom, Saab Aerotech Created:2005-12-12
Last modified:2009-07-06
Definition:
name by which a State is known.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2005-01-12
Last modified:2007-07-23
Definition:
A State_identification_code is an Identification_code that identifies a State.
EXAMPLE: The identification of a failure.
CONSTRAINT: An Identification_assignment classified as a State_identification_code can only be assigned to a State or its
subclasses.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited
Definition:
A State_of_activity is a State_definition that defines a state for an activity.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited
Definition:
state_defnition that defines the status of an approval.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited
Definition:
A State_of_contract is a State_definition that defines a state for a Contract.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited
Definition:
A State_of_physical_object is a State_definition that defines a state for a physical object such as Parts, Product_as_individual,
Physical_breakdown_element.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited
Definition:
A State_of_work order is a State_definition that defines a state for a work order.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited
Definition:
A State_of_work_request is a State_definition that defines a state for a work order.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, Saab Aerotech Created:2009-06-12
Definition:
resource item identification code that identifies an item of supply.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2007-04-02
Last modified:2007-07-20
Definition:
A Succession_relationship is a Representation_relationship that classifies that the two Representations being related by the
Representation_relationship are a sequence.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Brad Harris, Eurostep Limited Created:2007-07-09
Last modified:2007-07-09
Definition:
A Supply_process is an Agreement_process that classifies the associated
data as having been defined within the context of providing an acquirer
with a product or service that meets agreed requirements.
Version:1 Stage:CommitteeSpecification Revision:0
Source:ISO 15288 Creator:Trine Hansen, DNV Created:2004-11-23
Last modified:2007-07-23
Definition:
A Support_stage is a Life_cycle_stage that classifies the associated data as having been defined within the context of providing
logistics, maintenance, and support services that enable continued
system-of-interest operation and a sustainable service.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited
Definition:
A Symptom is an Observation that a product is exhibiting behaviour that indicates that there may be a fault with the product.
CLASS
Symptom;
SUBCLASS OF (
EXPRESS:Observation,
);
END_CLASS;
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Brad Harris, Eurostep Limited Created:2007-07-09
Last modified:2007-07-09
Definition:
A System_life_cycle_processes_management_process is an Enterprise_process that classifies the associated data as having been
defined within the context of assuring that effective system life cycle processes are
available for use by the organization.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, Saab Aerotech
Definition:
task method classification that organizes tasks according to the strategy and condition that triggers the performance of
the task.
Example: Corrective vs Preventive, Scheduled vs Unscheduled.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, Saab Aerotech
Last modified:2009-06-30
Definition:
task method classification that defines the relative importance of the task to the operation of the equipment (product in
focus).
Version:1 Stage:CommitteeSpecification Revision:0
Source: Creator: Created:
Last modified:2007-07-23
Definition:
A Task_element_identification_code is an Identification_code that is used to identify a Task_element.
CONSTRAINT: An Identification_assignment classified as a Task_element_identification_code can only be
assigned to a Task_element or it subclasses.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, Saab Aerotech Created:2006-09-30
Definition:
class identification code that identifies a class that is classifying a Task_method.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2005-01-12
Last modified:2007-07-23
Definition:
A Task_method_identification_code is an Activity_method_identification_code that identifies a Task_method.
EXAMPLE: The identification according to the AECMA S1000D task numbering procedures.
CONSTRAINT: An Identification_assignment classified as a Task_method_identification_code can only be assigned to a Task_method
or its subclasses.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS Creator:Leif Gyllstrom, Saab Aerotech Created:2007-05-23
Last modified:2009-07-06
Definition:
name by which a Task_method is known.
Example: Lights - manual test.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, SAAB Created:2009-06-12
Definition:
task method version assignment that asserts that the Task_method_version is valid and appropriate in the context of the referenced
entity instance.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, Saab Aerotech Created:2009-06-12
Definition:
task method classification that identifies the location where the Task_method is to be performed with respect to the end item.
Note: Also see the classes Off_product_task and On_product_task..
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, Saab Aerotech
Last modified:2009-07-06
Definition:
identification code that is used to identify a Task_step.
CONSTRAINT: An Identification_assignment classified as a Task_step_identification_code can only be assigned to a Task_step
or it subclasses.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, Saab Aerotech Created:2008-03-06
Last modified:2009-07-06
Definition:
name by which a Task_step is known.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Trine Hansen, DNV Created:2004-11-24
Last modified:2007-07-10
Definition:
A Technical_process is a Process_domain that classifies the associated data as having been defined within the context of defining
the
requirements for a system, transforming the requirements into an effective
product, permitting consistent reproduction of the product where necessary,
using the product to provide the required services, sustaining the provision
of those services and disposing of the product when it is retired from service.
CLASS
Technical_process;
SUBCLASS OF (
Process_domain
);
SUPERCLASS OF (
Operation_process,
Architectural_design_process,
Implementation_process,
Validation_process,
Verification_process,
Maintenance_process,
Transition_process,
Stakeholder_requirements_definition_process,
Requirements_analysis_process,
Disposal_process,
Integration_process,
);
DISJOINT WITH (
Agreement_process,
Project_process,
Enterprise_process,
);
END_CLASS;
Version:1 Stage:CommitteeSpecification Revision:0
Source:OASIS PLCS Creator:Per Myrseth, DNV Created:2005-06-28
Last modified:2007-07-18
Definition:
Test_equipment_name is a Product_group_name of interpretable text/ code that identifies the type of test equipment.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Brad Harris, Eurostep Limited Created:2007-07-09
Last modified:2007-07-09
Definition:
A Transition_process is a Technical_process that classifies the associated data as having been defined within the context
of establishing a
capability to provide services specified by stakeholder requirements in
the operational environment.
CLASS
Transition_process;
SUBCLASS OF (
Technical_process
);
DISJOINT WITH (
Operation_process,
Architectural_design_process,
Implementation_process,
Validation_process,
Verification_process,
Maintenance_process,
Stakeholder_requirements_definition_process,
Requirements_analysis_process,
Disposal_process,
Integration_process,
);
END_CLASS;
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, Saab Aerotech
Last modified:2009-06-30
Definition:
condition assignment that initiates something when the associated condition is fulfilled.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2007-01-23
Last modified:2007-07-23
Definition:
A Type_of_person_identification_code is an Identification_code that is used to identify a Type_of_person.
CONSTRAINT: An Identification_assignment classified as a Type_of_person_identification_code can only be
assigned to a Type_of_person or it subclasses.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS Creator:Leif Gyllstrom, Saab Aerotech Created:2007-05-23
Last modified:2009-07-06
Definition:
name by which a Type_of_person is known.
Example: Crane operator, Welder, Maintainer level 3.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2007-01-23
Last modified:2007-07-20
Definition:
A Typical_activity classifies an Activity_method as being one that something or someone may undertake.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2007-04-02
Last modified:2007-07-16
Definition:
product_as_individual_identification_code that provides a unique identification of an individual item according the US DOD
UID registry.
CONSTRAINT: An Identification_assignment classified as a UID can only be assigned to a Product_as_individual or its subclasses.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Brad Harris, Eurostep Limited Created:2007-07-10
Last modified:2007-07-10
Definition:
An User_of is an Organization_or_person_in_organization_assignment that is assigning a person or organization to something
in the role of user.
CLASS
User_of;
SUBCLASS OF (
EXPRESS:Organization_or_person_in_organization_assignment,
);
DISJOINT WITH (
Contractor,
Security_classifier_of,
Creator_of,
Maintainer_of,
Contractee,
Operator_of,
Owner_of,
Responsible_for,
Measurer_of,
Manufacturer_of,
Assessor_of,
Executor_of,
Sender_of,
Performer_of,
Designer_of,
Assertor_of,
Issuer_of,
Installed_in_position,
Observer_of,
Receiver_of,
Reporter_of,
);
END_CLASS;
Version:1 Stage:CommitteeSpecification Revision:0
Source:ISO 15288 Creator:Trine Hansen, DNV Created:2004-11-23
Last modified:2007-07-23
Definition:
A Utilization_stage is a Life_cycle_stage that classifies the associated data as having been defined within the context of
operation of the
product, delivering services within the intended environments and ensuring continued operational effectiveness.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Brad Harris, Eurostep Limited Created:2007-07-09
Last modified:2007-07-09
Definition:
A Validation_process is a Technical_process that classifies the associated data as having been defined within the context
of providing objective
evidence that the services provided by a system when in use comply with
stakeholder requirements.
CLASS
Validation_process;
SUBCLASS OF (
Technical_process
);
DISJOINT WITH (
Operation_process,
Architectural_design_process,
Implementation_process,
Verification_process,
Maintenance_process,
Transition_process,
Stakeholder_requirements_definition_process,
Requirements_analysis_process,
Disposal_process,
Integration_process,
);
END_CLASS;
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2007-01-23
Last modified:2007-07-23
Definition:
A Variant_identifcation_code is a Progression_identifcation_code that identifies a particular variant of a product.
NOTE: The variant is a derivation from a product.
EXAMPLE: A VW Golf GL, A VW Golf GTI.
CONSTRAINT: An Identification_assignment classified as a Variant_identification_code can only be assigned to a Task_method
or Activity_method.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Brad Harris, Eurostep Limited Created:2007-07-09
Last modified:2007-07-09
Definition:
A Verification_process is a Technical_process that classifies the associated data as having been defined within the context
of confirming that the
specified design requirements are fulfilled by the system.
CLASS
Verification_process;
SUBCLASS OF (
Technical_process
);
DISJOINT WITH (
Operation_process,
Architectural_design_process,
Implementation_process,
Validation_process,
Maintenance_process,
Transition_process,
Stakeholder_requirements_definition_process,
Requirements_analysis_process,
Disposal_process,
Integration_process,
);
END_CLASS;
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2007-01-23
Last modified:2007-07-23
Definition:
A Version_identifcation_code is a Progression_identifcation_code that identifies a particular version of an item in a series
of versions.
NOTE: The code is normally sequential.
CONSTRAINT: An Identification_assignment classified as a Version_identification_code can only be assigned to a Product_version
or its sub classes, Task_method_version, Scheme_version
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Mike Ward, Eurostep Limited Created:2006-12-07
Last modified:2007-07-16
Definition:
A View_definition_relationship_identification_code is an Identification_code that identifies a View_definition_relationship.
CONSTRAINT: An Identification_assignment classified as a View_definition_relationship_identification_code can only be assigned
to a View_definition_relationship or its subclasses.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PDM Schema usage guide Creator:Mike Ward, Eurostep Limited Created:2007-01-23
Last modified:2007-07-11
Definition:
approval_status that denotes that official acceptance is no longer being sought.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2007-04-02
Last modified:2007-07-23
Definition:
A Work_order_identification_code is an Identification_code that is used to identify a Work_order.
CONSTRAINT: An Identification_assignment classified as a Work_order_identification_code can only be
assigned to a Work_order or it subclasses.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited
Definition:
A Work order issue date is a type of Date_actual_release (a Date_or_date_time_assignment) that assigns a date or date_time
at which something a work order is actually released. For example, the date that a work order is released for bid.
Version:1 Stage:CommitteeSpecification Revision:0
Source: PLCS Oasis Creator:Tim Turner Created:2006-03-21
Last modified:2007-07-16
Definition:
A Work_order_state_identification_code is a State_identification_code that identifies the permissible types of state that
a work order can be in.
CONSTRAINT: An Identification_assignment classified as a Work_order_state_identification_code can only be assigned to a State
or its
subclasses.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS Oasis Creator:Tim Turner Created:2006-03-21
Last modified:2007-07-16
Definition:
A Work_package_version is a Scheme_version_identification_code that identifies a version of a Work_package.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS Oasis Creator:Tim Turner Created:2006-03-21
Last modified:2007-07-16
Definition:
A Work_package_version_history is a Scheme_version_history identifies a Scheme_version_relationship that relates two work
package
versions (classified scheme_versions) together.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited Created:2007-04-02
Last modified:2007-07-23
Definition:
A Work_request_identification_code is an Identification_code that is used to identify a Work_request.
CONSTRAINT: An Identification_assignment classified as a Work_request_identification_code can only be
assigned to a Work_request or it subclasses.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited
Definition:
A Work order issue date is a type of Date_actual_release (a Date_or_date_time_assignment) that assigns a date or date_time
at which something a work order is actually released. For example, the date that a work order is released for bid.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, Saab Aerotech Created:2008-03-06
Last modified:2009-07-06
Definition:
name by which a Work_request is known.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited
Definition:
A Work_request_purpose is a work_request that has been raised for a particular purpose. Note this class is "abstract". Only
subsets of it should be used.
Version:1 Stage:CommitteeSpecification Revision:0
Source:OASIS PLCS Creator:Per Myrseth, DNV Created:2005-10-26
Last modified:2007-07-18
Definition:
A Zone_breakdown_element_name is a Breakdown_element_name by which a Zone_element is known.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, Saab Aerotech
Last modified:2009-07-06
Definition:
iIdentification code that identifies a zonal breakdown of a product.
CONSTRAINT: An Identification_assignment classified as a Zone_breakdown_identification_code can only be assigned to a Zone_breakdown
or its sub classes.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, Saab Aerotech Created:2008-03-06
Last modified:2009-07-06
Definition:
name by which a Zone_breakdown is known.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, Saab Aerotech
Last modified:2009-07-06
Definition:
idenitification code that identifies a Zone_element.
CONSTRAINT: An Identification_assignment classified as a Zone_element_identification_code can only be assigned to a Zone_element,
or Class representing a zone code.
Version:1 Stage:CommitteeSpecification Revision:0
Source:PLCS OASIS Creator:Leif Gyllstrom, Saab Aerotech Created:2008-03-06
Last modified:2009-07-06
Definition:
name by which a Zone_element is known.