OWL Definition:
An Activity is a
action or a set of actions that consume time and resources and whose performance is necessary to achieve, or
contribute to, the realization of one or more outcomes.
The procedure executed during an Activity is identified by the ActivityMethod that
is referred to by the chosenMethod attribute.
EXAMPLE 1:
Changing the design of a bicycle
EXAMPLE 2:
Designing a bicycle
EXAMPLE 3:
Training someone to ride a bicycle
NOTE 1:
The action or set of actions is something that has taken place, is taking place, or
is expected to take place in the future.
NOTE 2:
The procedure executed during an
Activity is identified by the
ActivityMethod that
is referred to by the
chosenMethod attribute.
NOTE 3:
Status information identifying the level of completion of each activity may be
provided within an instance of
StateObserved.
NOTE 4:
The items that are affected by an
Activity, for example as input or output,
may be identified within an instance
of
ActivityAssignment.
Sources:
ISO 10303-239ed2 transformed to AP239AP233 PSMISO/IEC 15288:2003, "Systems and software engineering - System life cycle processes"
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 an Activity is identified by the ActivityMethod that
is referred to by the chosenMethod attribute.
EXAMPLE
Change, distilling, design, a process to drill a hole, and a task such as training
someone, are examples of activities.
NOTE 1
Status information identifying the level of completion of each activity may be provided
within an instance of
StateObserved.
NOTE 2
The items that are affected by an
Activity, for example as input or output, may be identified within an instance
of
ActivityAssignment.
Properties:
Parts:
a set of text based descriptions of the Activity.
A reference to a class held externally to the exchange file that classifies this
Activity. This
Activity is a member of the referenced class.
References:
OWL Definition:
An ActivityActual is a
activity that has started but not necessarily finished.
It is a record of the occurrence of an Activity.
The ActivityActual is related
through an ActivityHappening to the Activity
of which it is an occurrence. The existence of an ActivityActual instance means that the ActivityActual has commenced.
EXAMPLE 1:
The replacement of the tyres of my bicycle, frame number ZH002342, on October 25,
2011.
NOTE 3:
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.
Sources:
ISO 10303-239ed2 transformed to AP239AP233 PSM
Definition:
An ActivityActual is a specialization of Activity.
It is a record of the occurrence of an Activity. The ActivityActual is related
through an ActivityHappening to the Activity
of which it is an occurrence. The existence of an ActivityActual instance means that the ActivityActual has commenced.
NOTE 2
A date and 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 3
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.
OWL Definition:
An ActivityAssignment is a
assignment of an activity to something.
NOTE 2:
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
OrganizationOrPersonInOrganizationAssignment.
Sources:
ISO 10303-239ed2 transformed to AP239AP233 PSM
Definition:
An ActivityAssignment
is a specialization of an AssignmentObject
that represents the assignment of
Activity instances to instances
that are specializations of ActivityAssignmentSelect.
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
OrganizationOrPersonInOrganizationAssignment
Properties:
References:
Definition:
An ActivityHappening is a specialization of ActivityRelationship.
It is a relationship between the definition of an activity (Predicted) and its actual occurrence (Actual).
EXAMPLE 1
A single defined check (e.g. an oil-check) is actually performed on many occasions
or vehicles.
EXAMPLE 2
A single actual servicing activity includes several checks and repairs (e.g. an oil-check
and a
tyre-replacement).
Properties:
References:
OWL Definition:
An ActivityMethod is a
specific way to carry out an activity.
EXAMPLE 1:
instructions for changing a tyre.
NOTE 1:
A method typically follows a defined and regular plan.
NOTE 2:
There may be more than one method for producing a required result.
NOTE 3:
The method may be used to characterize a way to resolve a request for action.
The concept of action request is
represented by
WorkRequest.
Sources:
ISO 10303-239ed2 transformed to AP239AP233 PSM
Definition:
An
ActivityMethod 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
represented by
WorkRequest.
Properties:
Parts:
a reference to a class held externally to the exchange file that classifies this ActivityMethod. This
ActivityMethod is a member of the referenced class.
the text that describes the results of application of this method.
Definition:
An
ActivityMethodAssignment is an association of an
ActivityMethod with product or activity data.
Properties:
References:
the
ActivityMethod that is to be associated with product or
activity data.
the set of activity or product data to which the
ActivityMethod is assigned.
Definition:
An ActivityMethodRealization is a specialization of an
AssociationObject.
It is a further specification of how an activity method
is to be performed with the
ActivityMethod.
NOTE 1
More than one specification can be associated with the
same
ActivityMethod.
EXAMPLE 1
For a given planned activity there may be a task specification, a statement of how
task performance is to be logged
and a schedule that all apply.
Properties:
Parts:
References:
the item that realizes the ActivityMethod.
EXAMPLE 2
A plan, schedule, or task description may realize the activity method.
NOTE 2
More than one such item can be associated with the activity.
Definition:
An ActivityMethodRealizationRelationship is a specialization of an
RelationshipObject that is a relationship between
two instances of ActivityMethodRealization.
NOTE
An
ActivityMethodRealizationRelationship may be used to specify
sequencing and other constraints between different realizations for the same
ActivityMethod.
Properties:
Parts:
References:
Definition:
An ActivityMethodRelationship is a specialization of an RelationshipObject that is a relationship
between two instances of ActivityMethod.
Properties:
Parts:
References:
the first instance of ActivityMethod that is part of the relationship.
NOTE 1
The relating usually identifies the activity the definition of the relatedMethod is based on, for
example, derived from or dependent on.
NOTE 2
The meaning of this attribute is defined by the name attribute.
the other instance of ActivityMethod that is part of the relationship.
NOTE 3
The
related usually identifies the
ActivityMethod, which is
based on the definition of the
relatingMethod.
Definition:
An ActivityRelationship is a specialization of an RelationshipObject that 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
ActivityRelationship entity.
Properties:
Parts:
References:
the first of the instances of Activity that is part of the relationship.
NOTE 1
The relating usually identifies the activity the definition of the relatedActivity is based on, for
example, derived from or dependent on.
NOTE 2
The meaning of this attribute is defined by the name attribute.
the second instance of Activity that is part of the relationship.
NOTE 3
The
related usually identifies the
Activity, which is based on
the definition of the
relatingActivity.
NOTE 4
The meaning of this attribute is defined by the name attribute.
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.
Properties:
Parts:
a reference to a class held externally to the exchange file that classifies this Address. This
Address is a member of the referenced class.
Values:
the words by which the Address is known. It specifies the name of the location identified by the address. The value
of
this attribute need not be specified.
EXAMPLE
"White House", "Buckingham Palace", and "North Pole" are examples of address name.
the number of a location on a street. The value of this attribute need not be specified.
the name of a street. The value of this attribute need not be specified.
the number of a postal box. The value of this attribute need not be specified.
the name of a town. The value of this attribute need not be specified.
the name of a region. The value of this attribute need not be specified.
the code that is used by the country's postal service. The value of this attribute
need not be specified.
the name of a country. The value of this attribute need not be specified.
an organization-defined address for internal mail delivery. The value of this attribute
need not be specified.
the number to which facsimiles may be sent. The value of this attribute need not
be specified.
the number at which telephone calls may be received. The value of this attribute
need not be specified.
the electronic address to which electronic mail may be sent. The value of this attribute
need not be specified.
the number where telex messages may be received. The value of this attribute need
not be specified.
the text that specifies the Uniform Resource Locator associated with the address.
The value of this attribute
need not be specified.
OWL Definition:
An AddressAssignment is a
assignment of an address to something.
Sources:
ISO 10303-239ed2 transformed to AP239AP233 PSM
Definition:
An AddressAssignment
is a specialization of an AssignmentObject
that represents the association of an Organization or a PersonInOrganization with an Address.
Properties:
References:
the set of activity or product data to which the
Address is
assigned.
Definition:
An
AddressBasedLocationRepresentation is a specialization of
LocationRepresentation specified by its postal identification.
Properties:
References:
the location where mail can be received.
Definition:
An AdvisoryNote is the link between a task element with an advisory task step.
Properties:
Parts:
References:
Definition:
An
AdvisoryTaskStep is a type of
TaskStep. It conveys information.
NOTE
Some
TaskMethods may not require any action to be undertaken.
EXAMPLE
"Beware of hot exhausts", "do not use tool X this way" and similar messages.
Definition:
An
AlternatePartRelationship is a specialization of
AlternateProductRelationship where the alternate and base products are parts.
Properties:
References:
the
Part for which an alternate is specified.
the
Part that may replace in all its usages, the base part.
Definition:
An
AlternateProductRelationship is an association between two instances of
Product. It specifies that any version of the
AlternateProduct, may be used in place of any version of the
baseProduct.
The relationship established by the
AlternateProductRelationship is not symmetric: if B is an alternate product for A, A is not implied to be an alternate
product for B.
NOTE 1
If a product is an alternate for another product, it is understood that there is
no interest to keep track of which
product, the base or any alternates specified, is used as a particular instance of
the base product within a product structure.
NOTE 2
An organization may track design changes for a base part, and establish effectivity
conditions for the use of that base
part in various assemblies to be manufactured. The use of an alternate product implies
that an organization does not specify any
particular version of the alternate product nor establish effectivities relating to
it.
NOTE 3
An
AlternateProductRelationship may relate products of any kind, provided both related instances of
Product identify products of the same kind, for example part-part or document-document.
NOTE 4
An AlternateProductRelationship for which the baseProduct is an assembly involves that the entire product
structure of the alternateProduct may be used in place of the baseProduct and its product structure.
EXAMPLE
Two bolts of the same size are products. One bolt has a square head and the other
has a hexagonal head. The two bolts are
considered equivalent with respect to form, fit, and function: they both have sufficiently
close physical shape, they take up the same
space when used, and they both serve to fasten two things together. Thus, one of these
two bolts could be considered to be an alternate
part for the other bolt.
Properties:
Parts:
a text description that specifies the rationale and criteria used to assess the capability
of replacing the BaseProduct by the AlternateProduct.
EXAMPLE
The concept of alternate products usually refers to form, fit, function, and quality.
Additional properties such as
performance, noise, endurance, or reliability may also be considered as a prerequisite
for the replacement.
Constraints:
Constraint: UR1Specification: (OCL2.0)
AlternateProductRelationship::allInstances()->isUnique(Sequence{relating, related})
Definition:
An Analysis is a specialization of Product. It is produced via a reproducible
process.
NOTE
Analysis is the process of studying or examining something in an organized way to
learn more about it, or a particular study or
examination of something. The full range of the analysis process includes mathematical,
physical testing, cognitive, chemical, etc.
Properties:
Parts:
the versions of the Analysis.
Definition:
An
AnalysisAssignment is a specialization of a
AssignmentObject
that relates a specific version of an analysis to the item being analyzed.
Properties:
References:
the set of activity or product data to which the
AnalysisVersion is
assigned.
Definition:
An AnalysisDisciplineDefinition is a specialization of ProductViewDefinition. It is a definition or
view of an AnalysisVersion taken from
the perspective of the analysing organization. The AnalysisDisciplineDefinition is controlled by the analysing
organization. The entity may be used to capture the definition of a particular
version of an analysis at any intermediate stage of its development where the
definition is not formally released by an organization at the analysis version level.
It may be used to capture the various stages in the definition cycle of a product.
If the analysis is explicitly represented by a model then the model is referenced
from
AnalysisDisciplineDefinition.definitionalRepresentations.
Properties:
References:
the
AnalysisVersion of which the
AnalysisDisciplineDefinition provides a characterization.
Definition:
An AnalysisModel is used to support
the description of analysis concepts.
Properties:
References:
The data that makes up the analysis model.
Definition:
An AnalysisModelObject represents the results of an analysis.
Properties:
Parts:
a reference to a class held externally to the exchange file
that classifies this AnalysisModelObject. This AnalysisModelObject is a member of the
referenced class.
References:
Definition:
An
AnalysisRepresentationContext
defines the context for the items (
AnalysisModelItemsSelect) used
in an
AnalysisModel.
Properties:
Parts:
a set of text based descriptions of the AnalysisRepresentationContext.
a reference to a class held externally to the exchange file
that classifies this Product This Product is a member of the
referenced class.
Definition:
An AnalysisVersion is a specialization of ProductVersion that identifies a
particular version of an analysis.
Properties:
Parts:
References:
the
Analysis that the
AnalysisVersion is a version of.
Definition:
A
AnalysisVersionRelationship is a specialization of
ProductVersionRelationship that is used to assert an association between two versions of an analysis.
Properties:
References:
Definition:
A
AnalysisVersionSequence is a specialization of
AnalysisVersionRelationship that is used to assert that the one analysis version (the successor) replaces another
(its
predecessor).
Definition:
An
AndStateCauseEffectDefinition is a specialization of
StateCauseEffectDefinition. It relates one or more causing
StateDefinition
entities and one effect
StateDefinition. All the causing
StateDefinition entities must exist prior to the single effect.
OWL Definition:
An ApplicationDomain is a
application or discipline.
EXAMPLE 1:
Product support
EXAMPLE 2:
Digital mock-up
EXAMPLE 3:
Preliminary design
EXAMPLE 4:
Electrical design
NOTE 2:
The context is typically an application, process or discipline.
Sources:
ISO 10303-239ed2 transformed to AP239AP233 PSM
Definition:
An ApplicationDomain defines the scope of applicability for a ViewDefinitionContext
Each ApplicationDomain optionally references a data item in either a ExternalOwlObject or a ExternalItem that may indicate what the domain is.
Properties:
References:
a reference to an
ExternalOwlClass or an
ExternalItem held externally to the exchange file that provides the
definition of the
ApplicationDomain.
Constraints:
Constraint: UR1Specification: (OCL2.0)
ApplicationDomain::allInstances()->isUnique(definition)
OWL Definition:
An Approval is a
formal record of the fact that the item to which the approval is assigned fulfills agreed criteria.
EXAMPLE 1:
A formal record that a type of maintenance procedure "XYZ" has been authorized.
Sources:
ISO 10303-239ed2 transformed to AP239AP233 PSM
Definition:
An Approval is a formal confirmation of the quality of some activity or product data.
Properties:
Parts:
a set of text based descriptions of the
Approval.
a reference to a class held externally to the exchange file that classifies this Approval This
Approval is a member of the referenced class.
Values:
the point in time when the Approval is or was supposed to be performed.
The value of this attribute need not be specified.
the point in time when the Approval actually became valid.
The value of this attribute need not be specified.
Definition:
An
ApprovalAssignment is the assignment of an
Approval to activity or
product data.
Properties:
References:
the
Approval that is assigned with activity or product data.
the set of activity or product data to which the
Approval is
assigned.
Definition:
An
ApprovalRelationship is a typed association between two instances of
Approval.
Properties:
References:
one of the instances of
Approval that is a part of the
relationship.
the other instance of
Approval that is a part of the relationship.
If one element of the relationship is dependent of the other, this attribute shall
be the dependent one.
Definition:
An
ApprovingPersonOrganization is an association between an
Approval
and the organization or person and organization that has granted this approval.
Properties:
Parts:
a reference to a class held externally to the exchange file that classifies this
ApprovingPersonOrganization This ApprovingPersonOrganization is a member of the referenced
class.
References:
the
Approval that has been given by the considered person or the organization.
Values:
the point in time when the
Approval has been given. The value of this attribute need not be specified.
Definition:
An
AssemblyRelationshipSubstitution is a relationship that indicates that an
AssemblyViewRelationship may be substituted by another
AssemblyViewRelationship.
Both assembly relationships shall refer to the same ProductViewDefinition of the same assembly.
NOTE 1
Consequently, an AssemblyRelationshipSubstitution actually specifies that the product version that plays the role
of component in the substituteRelationship may be replaced by the product version that plays the role of component in the
baseRelationship.
NOTE 2
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 3
As instances of
AssemblyViewRelationship establish assembly
relationships relevant in the definition contexts of the assembly, the substitution
only apply in these contexts.
An
AssemblyRelationshipSubstitution defines a one-way substitution: if A is specified as a substitute for B, B is not
implied to be
a substitute for A.
Properties:
References:
Constraints:
Constraint: UR1Specification: (OCL2.0)
AssemblyRelationshipSubstitution::allInstances()->isUnique(Sequence{baseRelationship,
substituteRelationship})
Definition:
An
AssemblyViewRelationship is a specialization of
ViewDefinitionRelationship. It identifies a possibly quantified usage of a product version as a component of
another product version.
The relationship is established between two ProductViewDefinitions
The inherited attribute relating
identifies the ProductViewDefinition of the assembly.
The inherited attribute related
identifies the ProductViewDefinition of the product version that plays the role of
component.
The AssemblyViewRelationship specifies that, in the InitialContext of the ProductViewDefinition that is referred to as
relating, it is considered that
the product version that is indirectly identified with the related attribute, is a component of the product version that is
indirectly identified with the relating attribute.
NOTE 1
In another context, the structure of the assembly may be described differently, adding,
for example, an intermediate
level between the products.
NOTE 2
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.
Properties:
Parts:
the
Identifier that identifies this usage of the component in the assembly in a diagram, list, chart,
or on a physical
piece of equipment. The value of this attribute need not be specified.
the
ValueWithUnit that defines the amount of this usage of the
component in the assembly. The value of this attribute need not be specified.
OWL Definition:
An AssignmentObject is a
allocation of an object to a target object.
EXAMPLE 1:
Assignment of a start date to the target object - a project.
NOTE 1:
The object being allocated is normally, but not always, of a different type to the
target of the allocation.
NOTE 2:
An assignment implies a direction from an object to a target object.
Sources:
ISO 10303-239ed2 transformed to AP239AP233 PSM
Definition:
An AssignmentObject defines the allocation of one datatype to another.
Only non-abstract specializations of the AssignmentObject datatype can be instantiated.
Properties:
Parts:
a reference to a class held externally to the exchange file that classifies this AssignmentObject This
AssignmentObject is a member of the referenced class.
Definition:
An AssignmentObjectRelationship is an association between two AssignmentObjects.
NOTE
An AssignmentObjectRelationship can be used to represent a historical sequence of assignments.
Properties:
References:
the second instance of AssignmentObject that is a part of the relationship.
NOTE
If one
AssignmentObject in the
relationship is dependent upon the other, this attribute shall be the dependent
one.
OWL Definition:
An AssociationObject is a
link between two objects.
EXAMPLE 1:
In zone is an association between a zone and something in the zone
NOTE 1:
An association implies no directionality or precedence between the objects
NOTE 2:
The objects being associated are normally, but not always, of different types or subtypes.
Sources:
ISO 10303-239ed2 transformed to AP239AP233 PSM
Definition:
An AssociationObject is an abstract generalization of instances that represent an
association between two sets of product or activity data.
Properties:
Parts:
A set of text based descriptions of the object.
a reference to a class held externally to the exchange file that classifies this AssociationObject. This
AssociationObject is a member of the referenced class.
Definition:
An Assumption is the identification of something assumed to be true without proof.
The reason or justification for an assumption being made shall be represented by
a JustificationAssignment being assigned to the Assumption.
EXAMPLE
An activity is planned based on the assumption that the resource required to perform
the activity is available at a location.
The item that is assumed shall be related to the Assumption by an ItemAssumed
Properties:
Parts:
a set of text based descriptions of the
Assumption.
a reference to a class held externally to the exchange file that classifies this Assumption This
Assumption is a member of the referenced class.
Definition:
An AssumptionAssignment is an association between an Assumption and the context in
which the assumption is made.
EXAMPLE
The following set of assumptions are relevant to the project.
Properties:
References:
the
Assumption that is assigned to activity or product data.
the set of activity or product data to which the
Assumption is
assigned.
Definition:
An
AssumptionRelationship is an association between two
Assumptions.
Properties:
Parts:
References:
Definition:
An
AttachmentSlot is a specialization 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.
Properties:
Parts:
the versions of the AttachmentSlot.
Definition:
An
AttachmentSlotAsPlanned is a specialization of
AttachmentSlotVersion that identifies an individual that is the subject of a plan to realize an
AttachmentSlot.
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 AttachmentSlotAsPlanned entity data type allow
the company to associate individual engines with the aircraft at different times over
the planned period.
Definition:
An
AttachmentSlotAsRealized is a specialization of
AttachmentSlotVersion that identifies an individual that is a realized
AttachmentSlot.
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.
Definition:
An
AttachmentSlotDefinition is a specialization of
ProductViewDefinition that identifies a view of an
AttachmentSlot.
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.
Properties:
References:
Definition:
An
AttachmentSlotDesign is a specialization of
AttachmentSlotVersion
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.
Definition:
An
AttachmentSlotDesignToPlanned is a relationship between a design version of an
AttachmentSlot 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.
Properties:
References:
the version of the attachment slot concept to which the planned individual will conform.
the attachment slot that is to conform to the design version.
Definition:
An
AttachmentSlotDesignToRealized is a relationship between a design version of an
AttachmentSlot 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.
Properties:
References:
the version of the concept to which the realized individual conforms.
the individual that conforms to the design.
Definition:
An
AttachmentSlotOnProduct is a relationship between a product and an
AttachmentSlot 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 AttachmentSlotOnProduct entity data
type identifies which attachment slot corresponds to the pylon.
Properties:
Parts:
a reference to a class held externally to the exchange file that classifies this AttachmentSlotOnProduct
This AttachmentSlotOnProduct is a member of the referenced class.
References:
the thing that associates the attachment slot location at which to attach parts to
the product view definition.
a location on a product at which to attach parts via an aperture.
Definition:
An
AttachmentSlotPlannedToRealized is a relationship between a realized individual of an
AttachmentSlot and a corresponding planned individual.
EXAMPLE
WeMakeBigPlanes Limited builds
aircraft serial number 2468 with a starboard engine attachment slot that was previously
planned.
Properties:
References:
the attachment slot that relates to the realized individual.
the individual that relates to the planned individual.
Definition:
An
AttachmentSlotVersion is a specialization of
ProductVersion that
identifies a version of
AttachmentSlot.
Properties:
Parts:
References:
Definition:
An
AxisPlacement is a specialization of
DetailedGeometricModelElement
that defines a right-handed, 2D or 3D, coordinate system.
If the AxisPlacement belongs to a 3D geometric space, the third
direction of the coordinate system is defined by the vector product of x-axis and
y-axis.
An
AxisPlacement may be an
AxisPlacement2d or an
AxisPlacement3d.
Properties:
Parts:
the
CartesianPoint that defines the position of the
AxisPlacement in the geometric space.
the
Direction that defines the first axis of the
AxisPlacement.
the
Direction that defines the second axis of the
AxisPlacement.
Definition:
An
AxisPlacement2d is a specialization of
AxisPlacement.
Definition:
An
AxisPlacement3d is a specialization of
AxisPlacement.
Definition:
An
AxisPlacementMapping is a geometric transformation defined by a source
AxisPlacement and a target
AxisPlacement that results from the transformation of
the source one.
Both instances of AxisPlacement shall have the same dimensionality.
The transformation shall be computed as the isometric transformation that maps:
- the origin of the source onto the origin of the target;
- the XAxis of the source onto the XAxis of the target;
- the YAxis of the source onto the YAxis of the target.
NOTE
By construction, the determinant of the transformation matrix equals one.
Properties:
Parts:
the
AxisPlacement that plays the role of source in the
transformation.
the
AxisPlacement that plays the role of target in the
transformation.
OWL Definition:
A Breakdown is a
set of breakdown elements chosen in order to partition a product in a desired way, together with the hierarchical relationships between these breakdown elements.
The hierarchical relationships, a parent-child view, is represented by
BreakdownElementUsage
instances relating the elements in the breakdown that are represented by
BreakdownElement instances.
Sources:
ISO 10303-239ed2 transformed to AP239AP233 PSM
Definition:
A
Breakdown is a specialization 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 BreakdownElementUsage instances relating the
elements in the breakdown that are represented by BreakdownElement instances.
Properties:
Parts:
the versions of the Breakdown.
Definition:
A
BreakdownContext is a membership relationship between a
BreakdownElement and a
Breakdown of which the element is a member.
Properties:
Parts:
a reference to a class held externally to the exchange file that classifies this BreakdownContext This
BreakdownContext is a member of the referenced class.
References:
Constraints:
Constraint: ur1Specification: (OCL2.0)
BreakdownContext::allInstances()->isUnique(Sequence{breakdown, breakdownElement})
OWL Definition:
A BreakdownElement is a
partition representing a physical, functional, system, or zonal aspect of a product.
NOTE 1:
Breakdown elements are physical, functional, system, or zonal partitions of a
breakdown.
NOTE 2:
A
breakdown element is non-specific and allows for various types of
breakdown.
Sources:
ISO 10303-239ed2 transformed to AP239AP233 PSM
Definition:
A BreakdownElement is a specialization of Product that identifies the elements in
one or more Breakdown instances.
Properties:
Parts:
the versions of the BreakdownElement.
Definition:
A BreakdownElementDefinition is a specialization of ProductViewDefinition that
identifies a view of a version ( BreakdownElementVersion) of a BreakdownElement.
Properties:
References:
Definition:
A
BreakdownElementRealization is a specialization of
ProductDefinitionElementRelationship that identifies a relationship between a
BreakdownElementDefinition or a
BreakdownElementUsage 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.
Properties:
Parts:
Definition:
A
BreakdownElementUsage is a specialization of
ViewDefinitionRelationship that identifies a relationship between a parent and child
BreakdownElement.
Properties:
References:
OWL Definition:
A BreakdownElementVersion is a
version of a breakdown element.
NOTE 1:
Breakdown element version is non-specific and allows for various types of product breakdown.
Sources:
ISO 10303-239ed2 transformed to AP239AP233 PSM
Definition:
A BreakdownElementVersion is a specialization of ProductVersion that identifies a
version of a BreakdownElement.
Properties:
Parts:
References:
Definition:
A
BreakdownOf is a relationship between a
Breakdown and a
Product of which the breakdown is a view.
Properties:
Parts:
a reference to a class held externally to the exchange file that classifies this BreakdownOf This
BreakdownOf is a member of the referenced class.
References:
OWL Definition:
A BreakdownVersion is a
version of a breakdown.
Sources:
ISO 10303-239ed2 transformed to AP239AP233 PSM
Definition:
A
BreakdownVersion is a specialization of
ProductVersion that
identifies a version of a
Breakdown
Properties:
Parts:
the Breakdown_version shall be a breakdown of one and only one product.
References:
the
Breakdown that the
BreakdownVersion is a version of.
Definition:
A
CartesianPoint is a specialization of
DetailedGeometricModelElement
that defines a point by a list of up to 3 cartesian coordinates.
Properties:
Values:
the list of up to 3 length measure values that define the cartesian coordinates of
the point.
Definition:
A
CartesianTransformation2d is a specialization of
DetailedGeometricModelElement. It is defined in a 2D geometric space by a 2*2 matrix and a cartesian point.
Let be:
- M, the 2*2 multiplication matrix of the cartesian transformation;
- A, the point of the cartesian transformation;
- P, a point in the geometric space;
- Q, the result of the application of the transformation to P.
The coordinates of Q shall be obtained by the formula: Q = M*P + A
Properties:
Parts:
the array of two instances of
Direction that defines the
multiplication matrix of the transformation.
the
CartesianPoint that defines the position of the result of the
application of the transformation to the origin of the geometric space.
Definition:
A
CartesianTransformation3d is a specialization of
DetailedGeometricModelElement that is a geometric transformation defined in a 3D geometric space by a 3*3 matrix
and a
cartesian point.
Let be:
- M, the 3*3 multiplication matrix of the cartesian transformation;
- A, the point of the cartesian transformation;
- P, a point in the geometric space;
- Q, the result of the application of the transformation to P.
The coordinates of Q shall be obtained by the formula: Q = M*P + A
Properties:
Parts:
the array of three instances of
Direction that defines the
multiplication matrix of the transformation.
the
CartesianPoint that defines the position of the result of the
application of the transformation to the origin of the geometric space.
Definition:
A
CausalConsequence is a specialization of
ViewDefinitionRelationship
that identifies secondary effects related to or resulting from a particular
RiskConsequence.
Properties:
References:
the second instance of CausalConsequence that is a part of the relationship.
NOTE
If one
CausalConsequence in the relationship is dependent upon the other, this
attribute shall be the dependent one.
OWL Definition:
A Certification is a
record created as a result of a successful certification providing proof of complying to or passing certain criteria.
NOTE 1:
The certificate can be attached to any aspect of product or activity data.
NOTE 2:
The certificate should record who provided the certification and when.
Sources:
ISO 10303-239ed2 transformed to AP239AP233 PSM
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.
Properties:
Parts:
a reference to a class held externally to the exchange file that classifies this Certification This
Certification is a member of the referenced class.
Definition:
A
CertificationAssignment is an association of a
Certification with
activity or product data.
EXAMPLE 1
'certified supplier' is an example of certification that may be granted to an organization
by its contractor.
Properties:
References:
the set of activity or product data to which the
Certification is
assigned.
Definition:
A
ChainBasedGeometricItemSpecificUsage is a specialization of
GeometricItemSpecificUsage that represents a chain of
GeometricModels in a graph
of
GeometricModels, where the undirected links in the graph can be
GeometricCoordinateSpaces,
GeometricModelRelationships,
or
GeometricPlacementOperations.
Properties:
References:
the list of items that relate nodes in the chain.
Definition:
A Classification is a relationship to the class that a subject is a member of.
NOTE
The subject is represented by a Block that has a "classifiedAs" as a property of type
Classification.
Properties:
References:
the class that the subject is a member of.
Definition:
A ClassificationRelationship is a specialization of an RelationshipObject that is a relationship between
two instances of Classification.
Properties:
References:
one of the instances of
Classification that is a part of the
relationship.
the other instance of
Classification that is part of the
relationship. If one element of the relationship is dependent upon the other, this
attribute shall be the dependent one.
Definition:
An
Collection is a specialization of
Product that identifies a set of
data.
Properties:
Parts:
the versions of the Collection.
Definition:
An
CollectionAssignment is an association of an
CollectionViewDefinition with the instance to which the collection has relevance.
Properties:
References:
Definition:
An
CollectionMembership is an association of an
CollectionViewDefinition with an instance that represents a member of the collection.
Properties:
References:
an instance that represents a member of the collection.
Definition:
An
CollectionRelationship is a specialization of
ProductRelationship
that represents an association between two
Collection instances.
Properties:
References:
Definition:
An
CollectionVersion is a specialization of
ProductVersion that
represents a revision of an
Collection.
Properties:
Parts:
References:
the
Collection that the
CollectionVersion is a version of.
Definition:
An
CollectionVersionRelationship is a specialization of
ProductVersionRelationship that represents an association between two
CollectionVersion instances.
Properties:
References:
the other instance of
CollectionVersion that is part of the
relationship. If one element of the relationship is dependent upon the other, this
attribute shall be the dependent one.
Definition:
An
CollectionVersionSequenceRelationship is a specialization of
CollectionVersionRelationship that represents a sequential association between two
CollectionVersion instances.
Definition:
An
CollectionViewDefinition is a specialization of
ProductViewDefinition that represents a characterization of an
CollectionVersion relevant in one or more
application domains and for one or more life cycle stages.
EXAMPLE
A set of data relevant to the design of the SS Titanic and a set of
data relevant to the as-built description of the SS Titanic might be represented as
two instances of CollectionViewDefinition.
Properties:
References:
the
CollectionVersion of which the
CollectionViewDefinition provides a characterization.
Definition:
A
ComponentUpperLevelIdentification is a specialization of
AssemblyViewRelationship. It identifies a component of an assembly with respect to an upper level in the assembly
structure.
NOTE
A
ComponentUpperLevelIdentification does not add a component in an
assembly, it provides a means to further characterize a component with respect to
an upper level assembly.
The identified component is the version of product, indirectly referred to as the
related of the subAssemblyRelationship.
The upper level assembly is the version of product, indirectly referred to as the
relating of the upperAssemblyRelationship.
Properties:
References:
the
AssemblyViewRelationship that identifies indirectly the
upper level assembly in the context of which the component is identified.
the
NextAssemblyViewUsage that identifies indirectly the component that
is further characterized by the
ComponentUpperLevelIdentification.
Constraints:
Constraint: UR1Specification: (OCL2.0)
ComponentUpperLevelIdentification::allInstances()->isUnique(Sequence{upperAssemblyRelationship,
subAssemblyRelationship})
Definition:
A
CompositionOfState is a specialization of state relationship and it relates the nature of states in
relation to
one another, where two or more
State parts compose a whole
State; and furthermore, whole states can become parts of yet another whole
State.
Definition:
A
CompositionOfStateDefinition is a specialization of
StateDefinitionRelationship. It relates
StateDefinition entities to one another,
when two or more
StateDefinition entities act as parts to compose a whole
StateDefinition; and furthermore, whole
StateDefinition
entities can become parts of yet another whole
StateDefinition.
Definition:
A
ConcurrentElements is a specialization of
StructuredTaskElement that
comprises a set of actions to be performed during the time required for the longest
task. No specific order is required.
Properties:
Parts:
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 ConditionParameter.
The target or consequence of a condition is represented by ConditionAssignment.
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
ConditionParameter identifying the
ProductAsRealized which represents the
engine. The consequence of the condition is "then it requires a service". This is
represented by
ConditionAssignment identifying the task to perform the service, a
TaskMethod.
Properties:
Parts:
a set of text based descriptions of the
Condition.
a reference to a class held externally to the exchange file that classifies this Condition This
Condition is a member of the referenced class.
the
ConditionParameters that represent the parameters against which the condition is to
be evaluated.
Definition:
A
ConditionAssignment 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.
Properties:
References:
the set of activity or product data to which the
Condition is
assigned.
Definition:
A
ConditionEvaluation 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
ConditionEvaluation. The measured value of oil pressure from gauge 3 on car with VIN
12345678 is 1.9 bar. Therefore the result of the evaluated the condition is true.
Properties:
Parts:
a reference to a class held externally to the exchange file that classifies this ConditionEvaluation This
ConditionEvaluation is a member of the referenced class.
the indication whether the
Condition evaluates to True, False or Unknown.
References:
Definition:
A
ConditionEvaluationAssignment is a relationship that identifies the statement or relationship to which the
ConditionEvaluation applies.
EXAMPLE
The
ConditionEvaluation (instance 87) is assigned to the activity of checking the oil level on car VIN 12345678.
Properties:
References:
Definition:
A
ConditionEvaluationParameter is an identification of the product or activity data used in the evaluation of the
Condition identified by the
ConditionEvaluation.
EXAMPLE
The measured value of oil pressure from gauge 3 on car with VIN 12345678 (value =
1.9 bar).
Properties:
Parts:
a reference to a class held externally to the exchange file that classifies this
ConditionEvaluationParameter This ConditionEvaluationParameter is a member of the referenced
class.
a reference to a class held externally to the exchange file that classifies this ConditionParameter This
ConditionParameter is a member of the referenced class.
References:
Definition:
A
ConditionParameter is a representation of the product or activity data that is used to specify a
Condition.
EXAMPLE
Oil pressure on gauge 3.
Properties:
Parts:
a reference to a class held externally to the exchange file
that classifies this ConditionParameter This ConditionParameter is a member of the
referenced class.
References:
the product or activity data which acts as a parameter to the condition. The value
of this attribute need not be
specified.
the
Condition for which the parameter is an input.
Definition:
A ConditionRelationship is a relation between two conditions.
Properties:
References:
one of the instances of
Condition that is a part of the
relationship.
the other instance of
Condition that is part of the relationship.
If one element of the relationship is dependent upon the other, this attribute shall
be the dependent one.
Definition:
A ConditionalEffectivity is a specialization of Effectivity for which the domain
of applicability is defined by an explicit condition.
Properties:
References:
the
Condition that defines the domain of applicability.
Definition:
A ContextualItemShape is a specialization of ItemShape that identifies
the shape of a product version in the context of its use in another product version.
The product version whose contextual shape is
identified, is the product version associated with the related of the ViewDefinitionUsage.
EXAMPLE
Flexible part may have several shapes, each associated with a particular occurrence
of the part in assemblies.
Properties:
References:
the
ProductViewDefinition
that identifies the definition of the product version whose shape is considered.
Definition:
A
ContextualShapeRepresentation is a relationship that relates a
ContextualItemShape and a
GeometricModelRelationship.
Properties:
References:
Definition:
A Contract is a binding agreement.
Properties:
Parts:
a set of text based descriptions of the
Contract.
a reference to a class held externally to the exchange file that classifies this Contract This
Contract is a member of the referenced class.
Definition:
A
ContractAssignment is an association of a
Contract with activity or
product data.
Properties:
References:
the
Contract that is to be associated with activity or product
data.
the set of activity or product data to which the
Contract is
assigned.
Definition:
A
ContractRelationship is a relationship between two
Contract
instances.
Properties:
References:
an instance of
Contract that is a part of the relationship.
the other instance of
Contract that is a part of the relationship.
If one
Contract in the relationship is dependent upon the other, this attribute shall
be the dependent one.
Definition:
A DateTimeAssignment
is a specialization of an AssignmentObject
that represents the assignment of a date and time,
DateTimeString with activity or product data.
Properties:
Parts:
a reference to a class held externally to the exchange file that classifies this DateTimeAssignment This
DateTimeAssignment is a member of the referenced class.
References:
the set of activity or product data to which the date and time is
assigned.
Values:
the date and time that is assigned to activity or product data.
Definition:
ADateTimeStringProxy is an abstract generalization of instances that represents a date time string
NOTE
Only non-abstract specializations of the DateTimeStringProxy can be instantiated.
Properties:
Values:
value [1] : DateTimeString
the date time string.
Definition:
A
DatedEffectivity is a specialization 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
DatedEffectivity period, at planning phase.
Depending on
which of the
startBound and
endBound attributes are specified, the actual domain
of time defined by a
DatedEffectivity is:
- the time interval between the start and end date or event;
- the open time interval that starts at the start date or event;
- the open time interval that ends at the end date or event (i.e. the start is unknown).
If the
EndBound is an event that actually identifies a
point in time that comes before the
StartBound, then the actual
domain of effectivity is empty.
Properties:
References:
the date or event that defines the lower bound of the interval of applicability.
The value of the attribute need
not be specified. If the value for this attribute is not specified, the interval of
applicability has no lower limit.
the date or event that defines the upper bound of the interval of applicability.
The value of the attribute need
not be specified. If the value for this attribute is not specified, the interval of
applicability has no upper limit.
Definition:
A
DecisionPoint is a type of
StructuredTaskElement. It requires a
decision that determines which further
TaskElement is to be followed.
NOTE
The condition on
which the decision is based optionally allows a further
TaskElement to be invoked to
provide the basis for the decision.
Properties:
Parts:
the
TaskElement to be performed if the test condition is satisfied.
The value of this attribute need not be specified.
the
TaskElement to be performed if the test condition is not
satisfied. The value of this attribute need not be specified.
the
TaskElement to be performed if the test condition can not be
evaluated or returns unknown. The value of this attribute need not be specified.
References:
the criterion to be tested in order to make a decision.
Definition:
A DecreasingResourceEvent is a specialization of ResourceEvent that decreases the
balance of a managed resource.
EXAMPLE
Filling a requisition reduces an inventory.
Definition:
A
DefinedStateRelationship is a relationship that links a
StateAssertion to a
StateAssessment.
Properties:
Parts:
References:
Definition:
A Descriptor is a set of words that describe something.
EXAMPLE
The same thing may have multiple descriptions associated with it.
Relating both a short description and a long description to an operational activity
or an organization,
as required by the US DoD Architecture Framework, are examples of multiple descriptions
applied to the same item.
Properties:
Parts:
the
LocalizedString representing providing the textual content of
the description.
a reference to a class held externally to the exchange file that classifies this Description This
Description is a member of the referenced class.
References:
the context in which the
Descriptor has been made.
Definition:
A
DescriptorRelationship is a relationship between a pair of
Descriptors
Properties:
References:
one of the instances of
Descriptor that is a part of the relationship.
the other instance of
Descriptor that is part of the relationship.
If one element of the relationship is dependent upon the other, this attribute shall
be the dependent one.
Definition:
A
DetailedGeometricModelElement
identifies a geometric construct.
Only non abstract specializations of the
DetailedGeometricModelElement entity data type can be instantiated.
Properties:
Parts:
a reference to a class held externally to the exchange file that classifies this
DetailedGeometricModelElement This DetailedGeometricModelElement is a member of the referenced
class.
Definition:
A
DigitalDocumentDefinition is a specialization of
DocumentDefinition.
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.
Properties:
References:
the set of instances of
DigitalFile that provides the content of
the digital document.
All Supertype Blocks:
File Definition:
A
DigitalFile is a specialization of
File. A
DigitalFile
contains computer interpretable data and is stored on an electronic device.
Definition:
A
DirectedActivity is a specialization of
Activity. It identifies an
activity that is governed by a
WorkOrder.
Properties:
References:
the
WorkOrder that governs the
DirectedActivity.
Definition:
A
Direction is a specialization of
DetailedGeometricModelElement that
defines a 2 or 3 dimensional vector.
NOTE 1
A
Direction is not located in a geometric space but is used in the
definition of geometric entities like
AxisPlacement.
Properties:
Values:
the list of 2 or 3 length measure values that define the direction ratios of the Direction.
NOTE 2
The coordinates of a Direction may not be normalised and the actual magnitudes of the components have no
effect upon the direction being defined; only the ratios x:y:z or x:y are significant.
Definition:
A DistributionByValue is a specialization of ProbabilityDistribution that
explicitly lists pairs of random variable values and function values.
NOTE 1
DistributionByValue is used where there is no named distribution which can be used to identify the distribution,
for example,
when the distribution is derived from observation.
Properties:
Parts:
the type of function which the (random variable, function value) pair list represents.
NOTE 3
Probabilities may be described by a number of different types of functions, such as
the cumulative distribution
function, the probability density function for continuous distributions or the probability
generation function for discrete
distributions. Each function is identified through reference-data.
References:
a list of pairs consisting of a random variable value and the corresponding function
value. This represents a numerical
approximation to a probability distribution.
NOTE 2
the value of random variable increases strictly monotonically along the list.
EXAMPLE 1
The distribution is the probability generating function for an unfair dice ((1,0.1),
(2,0.166),...,(6,0.23)).
Here each pair represents the value on the face and the probability of it occurring.
The probability of rolling a 1 or a 2 is
therefore (0.1 + 0.166).
EXAMPLE 2
The distribution is a cumulative distribution function for the measured length of
a component ((2.1, 0.0),
(2.2, 0.1), (2.3, 0.6), (2.4, 1.0)) Here each pair represents a length and the probability
that the component exceeds that
length. The probability that the component is between 2.2m and 2.3m long is therefore
0.5 (0.6 - 0.1).
Definition:
A
Document is a specialization of
Product used to identify
documentation data that is under configuration change management.
Properties:
Parts:
the versions of the Document>.
Definition:
A DocumentAssignment is a mechanism to associate a document with product data, where the assigned document
provides
information about the data with which it is associated.
Properties:
References:
the set of activity or product data to which the
Document is
assigned.
Definition:
A DocumentDefinition is a specialization of ProductViewDefinition that is a
DocumentVersion in a particular format.
EXAMPLE
A version of a logical document, which contains a shape model, may be represented
in the native formats of different CAD
systems.
Each DocumentDefinition is a DigitalDocumentDefinition or a PhysicalDocumentDefinition.
NOTE 2
Aspects of the representation may not be known at the time the identification is established.
Properties:
References:
the
DocumentVersion of which the
DocumentDefinition provides a characterization.
Definition:
A
DocumentDefinitionRelationship is a relationship between two instances of
DocumentDefinition.
Properties:
Parts:
References:
the other instance of
DocumentDefinition that participates in the
relationship. If one element of the relationship is dependent upon the other, this
attribute shall be the dependent one.
Definition:
A
DocumentVersion is a specialization of
ProductVersion A
DocumentVersion identifies a particular version of a document.
Properties:
Parts:
References:
the
Document that the
DocumentVersion is a version of.
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.
Properties:
Parts:
a reference to a class held externally to the exchange file that classifies this Effectivity This
Effectivity is a member of the referenced class.
Definition:
An
EffectivityAssignment is the association of an
Effectivity with
product or activity data.
Properties:
References:
the instance of the
Effectivity entity that is assigned.
Definition:
An
EffectivityRelationship is an association between two instances of
Effectivity. The meaning of the relationship is represented with the
relationType attribute.
Properties:
References:
Definition:
An
ElementConstraint is a specialization of
TaskElementRelationship
that signifies a constraint between
TaskElements. The constraint may only apply within the
context of a
TaskMethod or
TaskElement,
specified as the context.
Properties:
References:
the TaskElement within which the constraint applies. The value of this attribute
need not be specified.
EXAMPLE
Within a specific method, use of test equipment must be preceded by calibration. Or
a 30 minute wait is required between
stages of a method.
Definition:
An
EndTask is a type of
TaskElement. It signifies a point at which to
end the task.
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.
Properties:
Parts:
a reference to a class held externally to the exchange file that classifies this Envelope This
Envelope is a member of the referenced class.
the request for and acknowledgement of receipt of the Envelope. The value of this attribute need not be specified.
On transmission of a Message this attribute shall take one of the values ""
(blank), "ask message arrival" or "ask message read". A blank value expects no reply.
A value of "ask message arrival" asks if
the Message arrived at the recipients' mailbox, and requires the reply
Envelope to have values "acknowledge arrival" if the Message arrives at
the destination, or "delivery failure" if failure of the delivery is detected.
NOTE 2
Envelope is used to provide an audit trail. There is no assumption that the transmission system
has any knowledge of
Envelope or its usage. However, if it reports some failure, this can then be recorded in the
way described.
A value of "ask message read" asks if the recipient has actually opened the Message
to read it, and expects the reply "acknowledge read" on success, or "contents corrupt"
if it is not possible to for it to be
read.
NOTE 3
For any single
Envelope, there should be an acknowledgement per recipient. The acknowledgement will not
contain a
Message.
References:
the
Message that the
Envelope is wrapping. A
Message should be present unless the
Envelope is being used to carry an acknowledgement.
The value of this attribute need not be specified.
Definition:
An EnvelopeRelationship is an association of one Envelope with another.
NOTE
The most obvious use of the association is to link an
Envelope to its
acknowledgements.
Properties:
References:
one of the instances of
Envelope participating in the relationship
the other instance of the
Envelope participating in the
relationship. If one
Envelope participating in the relationship is dependent upon the
other, this attribute shall be the dependent one.
Definition:
A EnvironmentAssignment is an assignment of a product to the environment in which it operates or is supported.
Properties:
References:
the product that is or planned to be operating in the environment.
Definition:
An
EnvironmentDefinition is a specialization of
Product that is used
to identify the definition of typical environment in which a product is to be, has
been or is planned to be deployed in, operated in, or
supported in.
Properties:
Parts:
the versions of the EnvironmentDefinition.
Definition:
A
EnvironmentDefinitionVersion is a specialization of
ProductVersion
that identifies a particular version of an
EnvironmentDefinition.
Properties:
Parts:
References:
Definition:
A EnvironmentDefinitionView is a specialization of ProductViewDefinition that
provides a view of a version of an environment definition relevant for one or more
application domains. This view collects the
characteristics that define an environment.
NOTE
The characteristics include the resources available, the locations in which the product
is to operate as well as climatic
conditions such temperature ranges.
Properties:
References:
Definition:
A
EnvironmentViewDefinitionRelationship is a specialization of
ViewDefinitionRelationship that represents an association between two
EnvironmentDefinitionView instances.
Properties:
References:
Definition:
An Evidence is a collector of items used together to provide a single piece of evidence within
a validation or
verification. For example a document and its approval by a customer may be used together
to provide evidence of customer acceptance.
Properties:
Parts:
a set of text based descriptions of the
Evidence.
a reference to a class held externally to the exchange file that classifies this Evidence This
Evidence is a member of the referenced class.
References:
identifies the validation or verification for which this evidence has been related.
the component data items used to support this evidence.
Definition:
A ExchangeContextClassLibrary is a representation of a universal resource identifier for the OWL reference-data
library that
provides the context for an exchange of data.
NOTE
Each data exchange takes place in the context of a single OWL class library that references
any other OWL libraries that are
required.
Properties:
Values:
the URI by which the ExchangeContextClassLibrary is referenced and identified.
Constraints:
Constraint: UR1Specification: (OCL2.0)
ExchangeContextClassLibrary::allInstances()->isUnique(libraryId)
Definition:
An
ExitLoop is a type of
StructuredTaskElement. It signifies a point
at which to exit from a loop.
Definition:
An
ExpandedUncertainty is a specialization of
StandardUncertainty that
specifies the factor of an uncertainty.
Properties:
Values:
the multiplier of the uncertainty of the value.
Definition:
An
ExperienceGained is a relationship between an
ExperienceInstance and
a person or organization.
Properties:
Parts:
a reference to a class held externally to the exchange file that classifies this ExperienceGained This
ExperienceGained is a member of the referenced class.
References:
Definition:
An
ExperienceInstance is a particular episode of contact with and/or observation of facts or events which
contributes to the accumulation of knowledge or skill.
EXAMPLE 1
Changing the exhaust system on a car.
EXAMPLE 2
2 years work on same type of milling machine.
EXAMPLE 3
100 flying hours in a Tornado jet.
EXAMPLE 4
5 years as Workshop Manager.
The nature, duration and worth of the
ExperienceInstance can be
described using assigned properties or by referring to activities or tasks.
Properties:
Parts:
a reference to a class held externally to the exchange file that classifies this ExperienceInstance This
ExperienceInstance is a member of the referenced class.
References:
an experience instance contributes to the definition of the experience gained.
the
Activity or
ResourceAsRealized that provides the content of the
ExperienceInstance. The value of the attribute need not be
specified.
Definition:
An
ExperienceType is a category or class of experience.
EXAMPLE 1
welding
EXAMPLE 2
mechanical design
EXAMPLE 3
flying
Properties:
Parts:
References:
Definition:
An
ExperienceTypeRelationship is used to relate a compound experience to its component experiences.
EXAMPLE
Ten
years programming experience made up of five years C++ programming experience and
five years Java programming experience.
Properties:
References:
Definition:
An
ExternalAnalysisModel is a specialization of
AnalysisModel whose
content is provided in an external file.
Properties:
References:
the DigitalFile that contains the analysis representation.
EXAMPLE
The external file may be an analysis representation defined using AP209 in Physical
File Format, or a tool specific format.
Definition:
An ExternalClass defines a relationship between a datatype and an non-OWL reference-data class of
which instances of the datatype are members.
Properties:
Parts:
the identification of the ExternalClass.
References:
the document that provides the definition for the ExternalClass.
Constraints:
Constraint: ur1Specification: (OCL2.0)
ExternalClass::allInstances()->isUnique(Sequence{id, source})
Definition:
An
ExternalGeometricModel is a specialization of 3D
GeometricModel
whose content is provided in an external file.
The set of items of the ExternalGeometricModel contains only one element that
shall be an AxisPlacement. This AxisPlacement
specifies the reference location and orientation with respect to which placement of
the ExternalGeometricModel in other
GeometricModels shall be defined.
Properties:
Parts:
the AxisPlacement that defines the reference position or orientation of the
ExternalGeometricModel.
NOTE
Most of times, the position is the origin point of the coordinate space and the orientation
matrix is the identity matrix.
References:
the
DigitalFile that contains the external geometry information.
Definition:
An ExternalItem is the representation of a reference to an object or item
that is external to the data exchange file.
EXAMPLE
The location of a digital file in a file system.
EXAMPLE
A section in a document.
EXAMPLE
A definition.
Properties:
Parts:
the identification of the ExternalItem.
References:
the document within which the ExternalItem is defined.
Constraints:
Constraint: ur1Specification: (OCL2.0)
ExternalItem::allInstances()->isUnique(Sequence{id, source})
Definition:
An ExternalOwlClass defines a relationship between a datatype and an
OWL reference-data class of which instances of the datatype are members.
The OWL class is defined and managed in an ontology external to the data exchange
file.
Properties:
References:
Values:
the Uniform Resource Identifier (normally an http:// URL) that specifies the OWL
reference-data class of which
referenced instances are members.
Constraints:
Constraint: ur1Specification: (OCL2.0)
ExternalOwlClass::allInstances()->isUnique(class)
Definition:
An ExternalOwlObject states that a block instance is the same as an OWL reference-data item.
NOTE
This capability is similar in nature to the
ProxyObject built-in property in the
World Wide Web Consortium Web Ontology Language
, available from their Web site.
ProxyObject indicates that two individuals or classes have the same 'identity'.
Properties:
Values:
the Uniform Resource Identifier (normally an http:// URL) that provides the identification
and location of the
OWL file and the relevant reference-data item within it.
Constraints:
Constraint: ur1Specification: (OCL2.0)
ExternalOwlObject::allInstances()->isUnique(individual)
OWL Definition:
An ExternalPropertyDefinition is a
identification of the definition of a property.
EXAMPLE 1:
The property definition Colour is a definition of red, green and blue values.
NOTE 1:
A property may reflect physics or arbitrary user defined measurements
NOTE 2:
An ExternalPropertyDefinition is a reference to a property definition
that is defined externally to the exchange file.
Sources:
ISO 10303-239ed2 transformed to AP239AP233 PSM
Definition:
An ExternalPropertyDefinition is a reference to a property definition
that is defined externally to the exchange file.
A Property definition is the definition of a particular quality or feature of a product
or activity data.
A Property definition may reflect physics or arbitrary user defined measurements.
EXAMPLE
Colour is a property of product and is defined by a red, green and blue values.
Properties:
Parts:
a reference to a class held externally to the exchange file that classifies this
ExternalPropertyDefinition. This ExternalPropertyDefinition is a member of the referenced
class.
a reference to an
ExternalOwlClass or an
ExternalItem held externally to the exchange file for which the
ExternalPropertyDefinition is a proxy.
References:
a reference to an
ExternalOwlClass or an
ExternalItem held externally to the exchange file that provides the definition of
the
ExternalPropertyDefinition.
the set of units that are allowed to be used when specifying a value for the property.
Constraints:
Constraint: UR1Specification: (OCL2.0)
ExternalPropertyDefinition::allInstances()->isUnique(definition)
Definition:
An ExternalTypeQualifier is a reference to the specification of the type of
a datum that is defined externally to the exchange file.
Properties:
Parts:
OWL Definition:
An ExternalUnit is a
measurable quantity, dimension, or magnitude adopted as a basis or standard of measurement
for other quantities of the same kind and in terms of which their magnitude is calculated
or expressed.
EXAMPLE 1:
Ohm is the unit of electrical resistance
NOTE 1:
An ExternalUnit is a reference to a unit
that is defined externally to the exchange file.
Sources:
Oxford English Dictionary
Definition:
An ExternalUnit is a unit quantity.
Properties:
Parts:
a reference to a class held externally to the exchange file that classifies this ExternalUnit This
ExternalUnit is a member of the referenced class.
References:
a reference to an
ExternalOwlClass or an
ExternalItem held externally to the exchange file that provides the
definition of the
ExternalUnit.
Constraints:
Constraint: UR1Specification: (OCL2.0)
ExternalUnit::allInstances()->isUnique(definition)
Definition:
A File is a file stored on a computer system or in a stack of non-digital documents.
Properties:
Parts:
a set of version identifiers for the File.
a string that provides information about the kind of data stored in the file. The
value of this attribute need not be specified.
Where applicable, the following values shall be used:
- 'geometry': The file contains a shape model;
- 'NC data': The file contains numerical control data;
- 'FE data': The file contains finite element data;
- 'sample data': The file represents measured data;
- 'process plan': The document file represents process planning data;
- 'check plan': The document file represents quality control planning data;
- 'drawing': The document file represents a technical drawing.
a reference to a class held externally to the exchange file that classifies this File This File is
a member of the referenced class.
a set of text based descriptions of the
File.
References:
the identification of the File in a an external file management system.
Definition:
A
FileRelationship is a relationship between two instances of
File.
EXAMPLE 1
A service manual may contain graphics for explanatory reasons. In this case, the
File instances that contain the
graphics are referenced as related from the File instance that contains the body of
the service manual with
RelationType 'reference'.
Properties:
References:
one instance of
Filethat participates in the relationship.
the other instance of
File that participates in the relationship.
If one element of the relationship is dependent upon the other, this attribute shall
be the dependent one.
Definition:
A
FunctionValuePair is a single random variable/value pair, thus defining a single point on the distribution
curve
of a numerically defined distribution.
EXAMPLE
The distribution function for the tossing of two coins uses the number of heads as
the
random variable and the probability as value of the function, and has the form of
a list of three pairs ((0, 0.25), (1, 0.5), (2,
0.25)) - 0, 1 and 2 being the random variable values, 0.25, 0.5 and 0.25 being the
probability values.
Properties:
Parts:
the value of the probability function for the given random variable value.
the value of the random variable.
OWL Definition:
A FunctionalBreakdown is a
breakdown comprising functional elements.
The composite - component view is represented by FunctionalElementUsage
instances relating the functional elements in the breakdown which are represented
by FunctionalElements.
EXAMPLE 1:
A functional breakdown provides a decomposition of an aircraft in terms of high-level processes such as
"flight" and "taxiing" all the way down to low-level functions such as "detect onboard
fuel level", "move tail rudder", and "provide standard tow attachment point".
NOTE 1:
The
functional breakdown is a partitioning of a product into a set of related
functional elements so as to form explicit, parent-child views.
Sources:
ISO 10303-239ed2 transformed to AP239AP233 PSM
Definition:
A
FunctionalBreakdown is a specialization 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 FunctionalElementUsage
instances relating the functional elements in the breakdown which are represented
by FunctionalElements.
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 on-board
fuel level, move tail rudder and provide standard
tow attachment point.
Properties:
Parts:
the versions of the FunctionalBreakdown.
Definition:
A
FunctionalBreakdownContext is a specialization of
BreakdownContext
that is an association of a
FunctionalElement to a
FunctionalBreakdown of which the functional element is a member.
EXAMPLE
A function 'provide load lifting capability' is
member of the functional breakdown of a helicopter.
Properties:
References:
Definition:
A
FunctionalBreakdownVersion is a specialization of
BreakdownVersion
that identifies a version of a
FunctionalBreakdown
Properties:
References:
Definition:
A
FunctionalElement is a specialization of
BreakdownElement that
identifies the elements in one or more
FunctionalBreakdown instances.
Properties:
Parts:
the versions of the FunctionalElement.
Definition:
A
FunctionalElementDefinition is a specialization of
BreakdownElementDefinition that identifies a view of a version (
FunctionalElementVersion ) of a
FunctionalElement
Properties:
References:
Definition:
A
FunctionalElementUsage is a specialization of
BreakdownElementUsage
that is an association of a functional element to another functional element that
is a constituent.
FunctionalElement.
Properties:
References:
the second instance of FunctionalElement that is a part of the relationship.
NOTE
If one
FunctionalElement in the relationship is dependent upon the other, this
attribute shall be the dependent one.
Definition:
A
FunctionalElementVersion is a specialization of
BreakdownElementVersion that identifies a version of a
FunctionalElement
Properties:
Parts:
References:
Definition:
A
GeometricCompositionWithOperatorTransformation is a specialization of
GeometricRelationshipWithOperatorTransformation.
Definition:
A
GeometricCompositionWithPlacementTransformation is a specialization of
GeometricRelationshipWithPlacementTransformation.
Definition:
A
GeometricCoordinateSpace is a type of
ChainedGeometricModelLinkSelect 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 GeometricCoordinateSpace: 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
GeometricCoordinateSpace.
NOTE
The origin for coordinate values is implicitly defined as being the cartesian point
whose coordinates are all zero.
Properties:
Parts:
the uncertainty measures that apply.
References:
the set of ExternalUnit.
NOTE
The units is only intended to provide a default unit. Its use is not intended to prevent
GeometricCoordinateSpace being
specified with the same or different units to the context.
Values:
the dimensionality of the geometric space.
Definition:
A GeometricItemSpecificUsage is an identification of a DetailedGeometricModelElement within a GeometricModel or an ExternalGeometricModel as being the element that describes a ShapeElement or
ShapeElementRelationship of an ItemShape
that is described by the GeometricModel or an ExternalGeometricModel.
EXAMPLE
In an application protocol, an instance of
GeometricModel describes the
ItemShape of a product. One element of the
GeometricModel - a curve - represents the boundary of a hole that is a
ShapeElement in the product. This entity data type may be used to state that the curve describes
the hole, in the context
of the entire
GeometricModel describing the shape of the product.
Properties:
Parts:
References:
Definition:
A GeometricModel is a model comprising geometric constructs.
The GeometricModel is founded in a GeometricCoordinateSpace.
The items of a GeometricModel are instances of DetailedGeometricModelElement.
Properties:
Parts:
a set of version identifiers for the GeometricModel.
Values:
the LengthMeasure that specifies the radius of a sphere that encloses all elements
of the geometric model. The centre of the sphere is located at the origin of the GeometricCoordinateSpace of the GeometricModel.
The value of this attribute need not be specified.
Definition:
A
GeometricModelRelationship is a type of
ChainedGeometricModelLinkSelect.
Properties:
References:
one of the instances of GeometricModel
that is a part of the relationship.
the other instance of GeometricModel
that is a part of the relationship. If one element of the relationship is the dependent
upon the other,
this attribute shall be the dependent one.
Definition:
A
GeometricModelRelationshipWithTransformation is a specialization of
GeometricModelRelationship. A
GeometricModelRelationshipWithTransformation may be a
GeometricRelationshipWithPlacementTransformation or a
GeometricRelationshipWithOperatorTransformation
Definition:
A
GeometricOperatorTransformation is a specialization of
GeometricPlacementOperation.
Properties:
References:
Definition:
A
GeometricPlacement is a specialization of
GeometricPlacementOperation.
Properties:
Parts:
Definition:
A
GeometricPlacementModel is a specialization of
GeometricModel.
Properties:
Parts:
Definition:
A
GeometricPlacementOperation is a specialization of
DetailedGeometricModelElement. A
GeometricPlacementOperation may be a
GeometricPlacement or a
GeometricOperatorTransformation.
Properties:
Parts:
References:
Definition:
A
GeometricRelationshipWithOperatorTransformation is a specialization of
GeometricModelRelationshipWithTransformation.
Properties:
References:
Definition:
A
GeometricRelationshipWithPlacementTransformation is a specialization of
GeometricModelRelationshipWithTransformation.
Properties:
References:
the
AxisPlacementMapping that identifies the transformation for the
GeometricRelationshipWithPlacementTransformation.
Definition:
A
GlobalLocationRepresentation is a type of
LocationRepresentation
specified using geographic means in the global system and values, which could be physical
or political geographic values.
Properties:
Parts:
specifies the height above sea-level of the location. The value of the attribute
need not be specified.
specifies the geographical, physical or political region of the indicated location,
such as Europe, North
America, Berlin or Indian Ocean. The precise location can be further detailed within
refinements. The value of the attribute need
not be specified.
the angular distance of a place north or south of the equator.
the angular distance of a place east or west of the Greenwich meridian.
All Supertype Blocks:
File Definition:
A
Hardcopy is a specialization 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.
Definition:
A HierarchicalInterfaceConnection is a specialization of InterfaceConnection that
provides an interconnection between components at different levels in an assembly.
Each connection point in the assembly is represented
by a InterfaceConnectorOccurrence.
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
InterfaceConnectorOccurrence and an instance of the
HierarchicalInterfaceConnection entity data type identifies the connection of the pins (the parts) to the plug (the
assembly)
in the assembly.
Definition:
An Identifier provides the identifying name or code for the activity or product data.
Properties:
Parts:
a reference to a class held externally to the exchange file that classifies this Identifier This
Identifier is a member of the referenced class.
References:
the context within which the Identifier has been cerated and is unique.
Values:
the alphanumeric string that represents an identifying name or code.
Constraints:
Constraint: UR1Specification: (OCL2.0)
Identifier::allInstances()->isUnique(Sequence{idString, role, identificationContext})
Definition:
A IdentifierRelationship is a relationship between a pair of Identifiers.
EXAMPLE
ISO is an acronym for "International Standard Organization". When ISO and "International
Standard Organization" are used as
identifiers for the ISO organization, they may be related to indicate that ISO is
the acronym for "International Standard
Organization".
Properties:
References:
one of the instances of
Identifier that is a part of the
relationship.
the other instance of
Identifier that is part of the
relationship. If one element of the relationship is dependent upon the other, this
attribute shall be the dependent one.
Definition:
An
InZone is a relationship between a
ZoneElement and an item that
exists within the zone.
EXAMPLE
A pump is in the starboard engine room of a ship.
Properties:
References:
the item that exists in the zone.
the region in which the item exists.
Definition:
A IncreasingResourceEvent is a type of ResourceEvent that increases the balance of
a managed resource.
EXAMPLE
Purchasing new stock increases an inventory.
Definition:
An InformationRight is a definition of what may or may not be done with information in the sense of legal
rights and
obligations.
EXAMPLE 1
Copyright is an InformationRight.
EXAMPLE 2
For the purposes of developing a new system, details of government furnished equipment
may be made available to a
particular project team. The team may copy and use the information internally, but
may not pass it on, either to a third part, or to
another team, and must destroy the information at the end of the contract.
Properties:
Parts:
a reference to a class held externally to the exchange file that classifies this InformationRight This
InformationRight is a member of the referenced class.
the text that describes any conditions and limitations that apply to the exercise
of the right. The value of this attribute need
not be specified.
EXAMPLE 3
The description of the right states that copying is permitted within the project team only, whereas
the
restriction notes the additional constraint that the information must be destroyed at the end
of the project.
Definition:
An
InformationUsageRight is an application an
InformationRight to a
particular usage context.
NOTE 1
One view of the distinction between an
InformationRight and an
InformationUsageRight is that the
InformationRight represents a standard clause in a contract, whereas an
InformationUsageRight represents the fact
that the clause is used in a particular contract.
NOTE 2
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 3
The
Approval of an
InformationUsageRight carries the meaning that the
right is granted to all information items in the relevant context, as opposed to the
approval of an
InformationUsageRightAssignment which is limited to particular items.
NOTE 4
InformationUsageRight provides a mechanism for recording significant rights within a product database.
The legal significance
of the presence or absence of a right is outside the scope of this part of ISO 10303
Properties:
Parts:
a reference to a class held externally to the exchange file that classifies this InformationUsageRight
This InformationUsageRight is a member of the referenced class.
the additional information to be recorded about the InformationUsageRight. The value of this attribute
need not be specified.
References:
Definition:
An
InformationUsageRightAssignment 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.
Properties:
References:
Definition:
An
InformationUsageRightRelationship is the relationship of one
InformationUsageRight to another.
EXAMPLE
Where one
InformationUsageRight
supercedes another, then the original right is pointed to by the
relating attribute, its replacement by the
related
attribute, and the
relationType attribute takes the value "supercedes".
Properties:
References:
the other instance of
InformationUsageRight that is a part of the
relationship. If one
InformationUsageRight participating in the relationship is
dependent upon the other, this attribute shall be the dependent one.
Definition:
A InterfaceConnection is an interconnection between a connected pair of InterfaceConnectorOccurrences. Each InterfaceConnectorOccurrence represents
the place where a product used in an assembly can interact with other products in
the assembly.
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
InterfaceConnectorOccurrence and an instance of the
InterfaceConnection entity
data type identifies the connection of the pins to the wires in the assembly.
Properties:
Parts:
a reference to a class held externally to the exchange file that classifies this InterfaceConnection This
InterfaceConnection is a member of the referenced class.
References:
the other instance of the connected pair of
InterfaceConnectorOccurrences. If one element of the relationship is dependent upon the other, this attribute
shall be
the dependent one.
Definition:
An InterfaceConnector is a specialization of Product that identifies a part of a
product with which one or more other products or the environment interacts.
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 InterfaceConnector entity data type
identifies the role of the socket in the interface and is the subject of a specification
that defines the necessary geometrical and
electrical attributes to ensure a functioning interface between the computer and network
hardware.
Properties:
Parts:
the versions of the InterfaceConnector.
Definition:
An
InterfaceConnectorAsPlanned is a specialization of
InterfaceConnectorVersion that identifies an individual that is the subject of a plan to realize an
InterfaceConnector.
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.
Definition:
An
InterfaceConnectorAsRealized is a specialization of
InterfaceConnectorVersion that identifies an individual that is a realized
InterfaceConnector.
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.
Definition:
An
InterfaceConnectorDefinition is a specialization of
ProductViewDefinition that identifies a view of an
InterfaceConnectorVersion.
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
InterfaceConnectorDefinition entity data type collects these data together.
Properties:
References:
the item for which the InterfaceConnectorDefinition provides an interface capability.
Definition:
An
InterfaceConnectorDesign is a specialization of
InterfaceConnectorVersion that identifies a design version of an
InterfaceConnector.
EXAMPLE
BuildAWidget Incorporated creates design version 2.10 for an electrical supply connector.
Definition:
An
InterfaceConnectorDesignToPlanned is a relationship between a design version of an
InterfaceConnector 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.
Properties:
References:
the version to which the planned individual will conform.
the individual that is to conform to the design version.
Definition:
An
InterfaceConnectorDesignToRealized is a relationship between a design version of an
InterfaceConnector 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.
Properties:
References:
the version to which the realized individual conforms.
the individual that conforms to the design.
Definition:
A
InterfaceConnectorOccurrence is an occurrence of a
InterfaceConnectorDefinition. The
InterfaceConnectorOccurrence represents the place where a product used in an
assembly can interact with other products in the assembly. The interaction is represented
by a
InterfaceConnection.
Properties:
Parts:
a reference to a class held externally to the exchange file that classifies this
InterfaceConnectorOccurrence This InterfaceConnectorOccurrence is a member of the referenced
class.
References:
the item for which the InterfaceConnectorOccurrence provides an interface capability.
Definition:
An
InterfaceConnectorPlannedToRealized is a relationship between a realized individual of an
InterfaceConnector and a corresponding planned individual.
EXAMPLE
BuildAWidget Incorporated builds
pump serial number 30302 with an electrical supply connector that was previously planned.
Properties:
References:
the individual that relates to the realized individual.
the individual that relates to the planned individual.
Definition:
An
InterfaceConnectorVersion is a specialization of
ProductVersion
that identifies a version of an
InterfaceConnector.
Properties:
Parts:
References:
Definition:
A
InterfaceDefinitionConnection is an interconnection between a connected pair of
InterfaceConnectorDefinitions or, if the point of interconnection is not specified, the
interconnection between a pair of views (
ProductViewDefinitions) on products
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 InterfaceDefinitionConnection entity data type identifies this fitting of the plug into
the socket.
Properties:
Parts:
a reference to a class held externally to the exchange file that classifies this
InterfaceDefinitionConnection This InterfaceDefinitionConnection is a member of the referenced
class.
References:
Definition:
An
InterfaceDefinitionFor is a relationship between an
InterfaceSpecification 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 InterfaceDefinitionFor
entity data type is necessary to identify this relationship.
Properties:
References:
the specification that defines necessary attributes for the item that participates
in the interface.
the item that conforms to the interface specification.
Definition:
An
InterfaceSpecification is a specialization 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.
Properties:
Parts:
the versions of the InterfaceSpecification.
Definition:
An
InterfaceSpecificationDefinition is a specialization of
ProductViewDefinition that provides a view of an
InterfaceSpecification.
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.
Properties:
References:
Definition:
An
InterfaceSpecificationVersion is a specialization of
ProductVersion
that identifies a version of an
InterfaceSpecification.
EXAMPLE
In 1999, BSI issues a new
version of a standard for connecting domestic electrical equipment to the electricity
supply.
Properties:
Parts:
References:
Definition:
An ItemAssumed is an association between an Assumption and the item that is being
assumed.
EXAMPLE
A facility is assumed to exist at a given location.
The facility shall be represented by a ResourceItemAssignment, the location by a
Location, and the existence of the facility at the location, by a LocationAssignment assigning a location to the resource.
Properties:
Parts:
a reference to a class held externally to the exchange file that classifies this ItemAssumed This
ItemAssumed is a member of the referenced class.
References:
the item that is assumed to be true.
Definition:
An
ItemDesignAssociation is the association of a
ProductConfiguration
with a
ProductViewDefinition or a
ProductVersion. It specifies the
design that corresponds to the
ProductConfiguration.
If the
design is a ProductViewDefinition, the ItemDesignAssociation represents the
statement that, in the considered definition context, the product version, that is,
the ProductViewDefinition is a valid way to implement the ProductConfiguration.
NOTE 1
This association might not be valid in all definition contexts of the product version.
If the design is a ProductVersion, the ItemDesignAssociation represents the
statement that, in all definition contexts, the ProductVersion is a valid way to implement
the ProductConfiguration.
NOTE 2
The association might not be valid for other versions of the product.
Properties:
References:
Constraints:
Constraint: UR1Specification: (OCL2.0)
ItemDesignAssociation::allInstances()->isUnique(Sequence{configuration, design})
Definition:
AnItemShape is a specialization of an ItemShapeObject
that represents the shape of a ShapeableItemSelect.
Properties:
References:
Definition:
AnItemShapeObject is an abstract generalization of instances that represents
the shape of a ShapeableItemSelect.
NOTE
Only non-abstract specializations of the ItemShapeObject can be instantiated.
Properties:
Parts:
a set of text based descriptions of the
ItemShape.
a reference to a class held externally to the exchange file that classifies this ItemShape This
ItemShape is a member of the referenced class.
Definition:
An
ItemUsageEffectivity is an effectivity domain that constrains the use of a product with or within another
product, in the context of a
ProductConfiguration.
The effectivityDomain attribute
identifies a domain of effectivity.
The itemUsageRelationship attribute identifies a relationship which characterizes the use of the product with
or within another
product.
EXAMPLE
This relationship may be an assembly-component relationship or a make-from relationship.
The
resolvedConfiguration attribute identifies an association between a
ProductConfiguration and a product that implements it. This attribute establishes the context in which
the
itemUsageRelationship is considered and constrained.
When the effectivity domain is a range of serial numbers, the serial
numbers considered are those of the ProductConfiguration.
When the effectivity domain is defined using a production lot number, the production
lot considered is one of the ProductConfiguration.
When the effectivity domain is an interval of time, the interval of time considered
is related to the production of the ProductConfiguration.
Properties:
Parts:
a reference to a class held externally to the exchange file that classifies this ItemUsageEffectivity This
ItemUsageEffectivity is a member of the referenced class.
References:
the
Effectivity that defines the domain of effectivity.
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.
Properties:
Parts:
a reference to a class held externally to the exchange file that classifies this Justification This
Justification is a member of the referenced class.
the text that provides information about the nature of the context in which the Justification applies.
The value of the attribute need not be specified.
Definition:
A
JustificationAssignment 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.
Properties:
References:
the set of activity or product data to which the
Justification is
assigned.
Definition:
A
JustificationRelationship is an association between two
Justifications.
Properties:
Parts:
References:
the other instance of
Justification that is part of the
relationship. If one element of the relationship is dependent upon the other then
this attribute shall be the dependent one.
Definition:
A
JustificationSupportAssignment 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.
Properties:
References:
OWL Definition:
A LifeCycleStage is a
period in a lifecycle.
EXAMPLE 1:
The design phase.
EXAMPLE 2:
The manufacturing phase.
EXAMPLE 3:
The support phase.
NOTE 1:
The combination of an
application domain and a
life-cycle stage defines a view of a product.
Sources:
ISO 10303-239ed2 transformed to AP239AP233 PSM
Definition:
A LifeCycleStage represents a point, period, or
step in a lifecycle. It is referenced by ViewDefinitionContext.
Properties:
References:
a reference to an
ExternalOwlClass or an
ExternalItem held externally to the exchange file that provides the
definition of the
LifeCycleStage.
Constraints:
Constraint: UR1Specification: (OCL2.0)
LifeCycleStage::allInstances()->isUnique(definition)
Definition:
A LocalizedString is a text based string. The language in which
the string is expressed is optionally identified.
Properties:
References:
the language in which the text is expressed.
Values:
the set of characters of which the string is comprised.
Definition:
A Location is a place or position where an activity or event can occur or a product or resource
can exist.
Properties:
Parts:
a set of text based descriptions of the
Location.
a reference to a class held externally to the exchange file that classifies this Location This
Location is a member of the referenced class.
References:
specifies zero or more means of representing a location.
Definition:
A LocationAssignment is a relationship between a product, event, or person and a location. There may be
distinct
assignment for each qualification. for example planned, scheduled or actual. Each
assignment may have a start and end date or time. A
location may have multiple assignments.
Properties:
References:
the
Location that is assigned to activity or product data.
the set of activity or product data to which the
Location is
assigned.
Definition:
A
LocationRelationship 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).
Properties:
References:
one instance of
Location that is a part of the relationship.
the other instance of
Location that is a part of the relationship.
If one element of the relationship is dependent upon the other then this attribute
shall be the dependent one.
Definition:
A LocationRepresentation is a means of representing a location.
Properties:
Parts:
a reference to a class held externally to the exchange file that classifies this LocationRepresentation
This LocationRepresentation is a member of the referenced class.
Definition:
A
LoopingElement is a specialization of
TaskElement. It invokes a
specified number of repetitions of a further
TaskElement.
Properties:
Parts:
Definition:
A
LotEffectivity is a specialization of
Effectivity for which the
domain of applicability is defined as a given batch of items.
Properties:
Parts:
the identification of the batch of items.
the size of the batch of items.
Definition:
A
MakeFromRelationship is a specialization of
ViewDefinitionUsage
established between two instances of
PartViewDefinition. It specifies that, in the context of
the definition of the relating part version, the relating part version is considered
as resulting from the manufacturing transformation of
the related part version.
NOTE 1
The related part version may identify a raw material or a semi-finished part.
Properties:
Parts:
the
ValueWithUnit that specifies the amount of the related part
version that is used to produce the relating part version. The value of this attribute
need not be specified. The quantity is
specified when the related part version is a countable material. If the value is absent
, it shall be considered that one occurrence
of the related part version is used to produce the relating part version.
References:
the instance of
PartViewDefinition that specifies a definition of
the part version that results from the manufacturing transformation.
the instance of
PartViewDefinition that specifies a definition of
the part version that is the input of the manufacturing transformation.
Values:
an integer that ranks the preference for use of the related part version among all
instances of
MakeFromRelationship that have the same value for the inherited
RelatingView attribute. This value is an integer that only has
meaning when comparing it with corresponding values for
MakeFromRelationship sharing
the same
RelatingView. It is a relative ranking value,
not an absolute ranking. A lower value indicates a higher preference for the
RelatedView, and a higher value indicates a lower preference. The value of this
attribute need not be specified.
Definition:
A ManagedResource is a representation of a resource that is provided with
resource management capabilities. The role of a managed resource is determined by
classification.
EXAMPLE
A managed resource can be classified as "Stock line".
Properties:
Parts:
a reference to a class held externally to the exchange file that classifies this ManagedResource This
ManagedResource is a member of the referenced class.
the measure of the amount of the resource that is available at a given location.
The value of this attribute
need not be specified.
References:
a reference to an identifiable ResourceItem (within the application context) that (when realized)
will satisfy that requirement.
Definition:
A ManagedResourceRelationship 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 "Preferred".
Properties:
References:
the other instance of
ManagedResource that is a part of the
relationship. If one element of the relationship is dependent upon the other, this
attribute shall be the dependent one.
Definition:
A Market is the identification of a marketing segment for products.
Properties:
Parts:
a set of text based descriptions of the
Market.
a reference to a class held externally to the exchange file that classifies this Market This Market
is a member of the referenced class.
the text that identifies a marketing category of products.
EXAMPLE
'Luxury automobiles', 'laptop personal computers', and 'budget personal stereos' are
examples of market segment types.
The value of this attribute need not be specified.
Definition:
A MeasureQualification is a means to provide information about measurements in which there is an associated
uncertainty. The uncertainty may be specified as precision, qualitative uncertainty,
or expanded uncertainty, and the type of the related
datum shall be included. The uncertainty is defined in clause 2 of "The Guide to the
Expression of Uncertainty in Measurement".
Properties:
Parts:
a reference to a class held externally to the exchange file that classifies this MeasureQualification This
MeasureQualification is a member of the referenced class.
References:
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 1
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.
Properties:
Parts:
a set of text based descriptions of the
Message.
a reference to a class held externally to the exchange file that classifies this Message This
Message is a member of the referenced class.
References:
the actual contents of the Message or a reference to the contents.
the identification of who (
Organization or
PersonInOrganization) or what defined the message, that is, identified its purpose and
contents. The value of this attribute need not be specified.
the ExchangeContextClassLibrary that identifies the OWL class library used in the
exchange. This OWL class library may reference any other OWL libraries that are required.
Definition:
A
MessageRelationship is a link between two related messages. The meaning of the association depends on
MessageRelationship.role.
EXAMPLE
If
Id=2 replaces
Id=1, then
MessageRelationship.related points to
Id=2 and
MessageRelationship.relating points to
Id=1 with
MessageRelationship.role="replaces".
Properties:
References:
one of the instances of
Message participating in the relationship.
the other instance of
Message participating in the relationship. If
one
Message participating in the relationship is dependent upon the other, this
attribute shall be the dependent one.
Definition:
A
NextAssemblyViewUsage is a specialization of
AssemblyViewRelationship. It establishes a relationship between a component and its immediate parent assembly
in a product structure.
Definition:
A
NumericalContext is a context in which
a
NumericalValue is recorded.
The context may represent the organization, technique or system used to establish
the
NumericalValue.
Properties:
Parts:
a reference to a class held externally to the exchange file that classifies this NumericalContext. This
NumericalContext is a member of the referenced class.
a set of text based descriptions of the NumericalContext.
Values:
the accuracy to which the
NumericalValues
in this context are measured.
specifies the minimum number of decimal digits that
ValueWithUnits
in this
NumericalContext are measured.
If present, the numerical measure or range may be specified using more digits than
the significant digits but shall not be specified using less digits.
The value of this attribute need not be specified.
Definition:
A
NumericalValue is a specialization of
a
ValueWithUnit
representing a quantity expressed with a numerical value and a unit.
Properties:
References:
the context in which the NumericalValue is recorded.
Values:
the quantity of the NumericalValue.
Definition:
An Observation is an historical record of something that has occurred 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.
Properties:
Parts:
a reference to a class held externally to the exchange file that classifies this Observation This
Observation is a member of the referenced class.
References:
the context in which the observation is made.
EXAMPLE 2
A problem is found during a maintenance operation. The set of contexts can include
the equipment being
maintained, the end product the equipment is fitted to, the activity being undertaken,
the manual that describes the activity and
the resources being used.
the person or equipment that did the observing. By default this is a piece of physical
equipment, represented by ProductAsRealized.
NOTE 2
One use of
Observation is to provide a link between health monitoring equipment and the file it produces
(recorded as a
Document).
the ActivityActual that was being performed when the observation was made. The
value of this attribute need not be specified.
EXAMPLE 3
An unexpected problem may be found during a maintenance activity, in which case the
ActivityActual is the maintenance activity itself.
EXAMPLE 4
Aircraft health monitoring data is collected during a flight. The flight profile may
be recorded using the
ActivityActual.
NOTE 3
Some business rules may require that an observation is always made against an
ActivityActual, while others may not require that the activity be recorded.
Definition:
An ObservationAssignment is an association of an Observation with any item that an
observation can be made about, or any item that can be used as part of the observation.
Properties:
References:
the Observation that applies to or is relevant to the assigned item.
any item that an observation can be made about, or any item that can be used as part
of the observation.
Definition:
An ObservationConsequence is an association of an observation to the consequences that follow from it, where
those consequences
are in the form of a WorkRequest.
NOTE 1
One of the uses of ObservationConsequence is to close one of the feedback loops from the use of a product to
requests for its enhancements.
Properties:
Parts:
References:
Definition:
An ObservationRelationship 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 ObservationRelationship against reference-data.
EXAMPLE
The
Observation of a persistent fault is composed of a series of
Observation of occurrences of the same fault. That is,
ObservationRelationship.related
points to the composite
Observation, while
ObservationRelationship.relating points
to one actual
Observation of the occurrence. The
ObservationRelationship.role of
the relationship is "observed instance", while it is classified as "is composed of".
In this example, the component
Observation will apply to
ProductAsRealized and the
consequence will be to rectify the individual faults, while the composite
Observation will
apply to a
ProductVersion and the consequence will be a design change.
Properties:
References:
one instance of
Observation that is a part of the relationship.
the other instance of
Observation that is a part of the
relationship. If one element of the relationship is dependent upon the other then
this attribute shall be the dependent one.
Definition:
An
ObservedEnvironment is a specialization of
Product that represents
a record of observations about the environment in which a product is or has been operating.
Properties:
Parts:
the versions of the ObservedEnvironment.
Definition:
An ObservedEnvironmentAssignment is an assignment of a product to the environment in which is or has operated.
Properties:
References:
the product that is or was operating in the environment.
Definition:
An
ObservedEnvironmentToDefinition is a relationship between a record of a set of observations about an
environment, represented by an
ObservedEnvironment, and a typical environment, represented by
an
EnvironmentDefinition. The typical environment is the expected environment about which
observations have been made.
Properties:
References:
the typical environment about which the recorded observations have been made.
the record of observations about an environment.
Definition:
An
ObservedEnvironmentToDefinitionVersion is a relationship between a version of the record of a set of
observations about an environment, represented by an
ObservedEnvironmentVersion, and a
version of the typical environment, represented by
EnvironmentDefinitionVersion. The typical
environment is the expected environment about which observations have been made.
Properties:
References:
the version of the typical environment about which the recorded observations have
been made.
the version of the record of observations about an environment.
Definition:
An
ObservedEnvironmentToDefinitionView is a relationship between a view of the record of a set of observations
about an environment, represented by an
ObservedEnvironmentView, and a view of the typical
environment, represented by
EnvironmentDefinitionView. The typical environment is the
expected environment about which observations have been made.
Properties:
References:
the view of the typical environment about which the recorded observations have been
made.
the view of the record of observations about an environment.
Definition:
An
ObservedEnvironmentVersion is a specialization of
ProductVersion
that identifies a particular version of an
ObservedEnvironment.
Properties:
Parts:
References:
Definition:
An
ObservedEnvironmentView is a specialization of
ProductViewDefinition that provides a view of a version of an observed environment relevant for one or
more application domains. This view collects the
characteristics of the observations on the environment.
Properties:
References:
Definition:
An
ObservedEnvironmentViewDefinitionRelationship is a specialization of
ViewDefinitionRelationship that represents an association between two
ObservedEnvironmentView instances.
Properties:
References:
Definition:
An
OrStateCauseEffectDefinition is a specialization of
StateCauseEffectDefinition. It relates one or more
StateDefinition entities that
are causes to a
StateDefinition that is the effect. At least one cause must exist prior to
the effect.
Definition:
An Organization is an administrative structure in which persons are active.
Properties:
Parts:
a reference to a class held externally to the exchange file that classifies this Organization This
Organization is a member of the referenced class.
Definition:
An
OrganizationBasedLocationRepresentation is a specialization of
LocationRepresentation 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
OrganizationBasedLocationRepresentation with two instances of
OrganizationalLocationIdentification and one instance of
Organization.
Properties:
References:
the organization in which the location identifier is meaningful.
Definition:
An OrganizationOrPersonInOrganizationAssignment is an association of an organization or a person in an organization
with activity or product data.
Properties:
References:
the organization or person in organization that is to be associated with the activity
or product data.
Definition:
An
OrganizationOrganizationTypeRelationship is a relationship between an
Organization organization and an
OrganizationType.
Properties:
References:
Definition:
An
OrganizationRelationship 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 OrganizationRelationship.
Properties:
References:
one of the instances of
Organization that is a part of the
relationship.
the other instance of
Organization that is part of the
relationship. If one element of the relationship is dependent upon the other, this
attribute shall be the dependent one.
Definition:
An
OrganizationType is a recognized kind of
Organization.
EXAMPLE 1
legal entity
EXAMPLE 2
change control board
EXAMPLE 3
sales organization
EXAMPLE 4
manufacturing organization
EXAMPLE 5
department
Properties:
Parts:
Definition:
An OrganizationalLocationIdentification is location that is defined by an identification which is specific in an
organization context.
Properties:
Parts:
a reference to a class held externally to the exchange file that classifies this
OrganizationalLocationIdentification This OrganizationalLocationIdentification is a member of the referenced
class.
Values:
the text that characterizes the identification location.
EXAMPLE
compartment or building.
the value of organization based location identification.
Definition:
A ParameterizedDistribution is a specialization of ProbabilityDistribution that is
used to link a named probability distribution to the parameters that define it.
NOTE 1
The
ParameterizationName of this
entity is used to discriminate between alternative parameterizations of the same distribution.
NOTE 2
To calculate a value using a
ParameterizedDistribution it is necessary to know the general distribution function,
the value of the distribution function parameters, and the specific random variable
value for which the probability evaluation is
required. The Probability Distribution module does not define the formula for the
distribution function, and it is assumed that this is
defined externally, either through reference information or via a "formula" module.
This entity provides the distribution function
parameters. The value of the random variable for which the probability is calculated
is provided by the
ProbabilityDerivationParameter.
Properties:
Parts:
the list of parameters used in the parameterization.
NOTE 3
In many distributions there is a trivial relationship between the mean and variance
for the distribution. In such
a case it is not necessary to list the parameters.
the name of the parameterization, distinguishing it from other parameterizations.
Definition:
A Part is a specialization of Product that collects the definitional information
of the versions of either a part or of a non-countable material.
NOTE 1
A Part does not represent an actual physical object that is or was existing in the real
world.
NOTE 2
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.
Properties:
Parts:
the versions of the Part.
OWL Definition:
A PartVersion is a
version of a part specification.
NOTE 1:
A
part specification version typically specifies a part that is functionally and physically interchangeable with
the other versions of the same
part specification.
Sources:
ISO 10303-239ed2 transformed to AP239AP233 PSM
Definition:
A
PartVersion is a specialization of
ProductVersion that identifies a
version of a part. A
PartVersion serves as the collector of the data characterizing a realizable object in various
application
contexts.
NOTE
A
PartVersion is expected to be functionally and physically interchangeable with the other versions
of the same
Part.
Properties:
Parts:
References:
the
Part that
the
PartVersion is a version of.
Definition:
A
PartViewDefinition is a specialization of
ProductViewDefinition that
defines a characterization view of a version of a
Part.
Properties:
References:
the
PartVersion of which the
PartViewDefinition
provides a characterization.
Definition:
A
PartialDocumentAssignment is a specialization of
DocumentAssignment.
A
PartialDocumentAssignment identifies a specific portion of the contents of a document. It assigns this portion
to the product
data for which it is relevant.
Properties:
Parts:
the word or group of the words that convey the subject or sub contents of the Document.
Definition:
A Person is an individual human being.
Properties:
Parts:
a set of text based descriptions of the
Person.
a reference to a class held externally to the exchange file
that classifies this Person This Person is a member of the
referenced class.
Values:
the Person's name.
the first element of the Person's list of forenames. The value of this attribute need not be specified.
the Person's other forenames. The value of this attribute need not be specified.
the text that specifies the Person's social or professional standing and appear before his or her names. The value of
this
attribute need not be specified.
EXAMPLE 1
"Mr.", "Ms", "Dr." and combinations are examples of prefixTitles.
the text that specifies the Person's social or professional standing and appear after his or her names. The value of
this
attribute need not be specified.
EXAMPLE 2
"Ph.D." and "Esquire" are examples of suffixTitles.
Definition:
A
PersonInOrganization is the identification of a
Person and of his
role in an
Organization
Properties:
Parts:
a reference to a class held externally to the exchange file
that classifies this PersonInOrganization. This
PersonInOrganization is a member of the referenced
class.
References:
Definition:
A
PersonOrOrganizationOrPersonInOrganizationInPosition is a
Person,
Organization, or
PersonInOrganization that
holds a
Position. A person may hold more than one position within an organization or
organizations.
EXAMPLE 1
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 2
Two people can hold the same
position in a job-share scheme.
Properties:
Parts:
a reference to a class held externally to the exchange file
that classifies this PersonOrOrganizationOrPersonInOrganizationInPosition
This PersonOrOrganizationOrPersonInOrganizationInPosition is a member of
the referenced class.
References:
Definition:
A PersonOrOrganizationOrPersonInOrganizationInPositionRelationship is a specialization of an
RelationshipObject that is a relationship between one Organization, Person, or PersonInOrganization and another.
Examples of the relationship are:
EXAMPLE 1
successor
EXAMPLE 2
job-share
Properties:
Parts:
References:
the other instance of
Organization,
Person, or
PersonInOrganization that participates
in the relationship. If one element of the relationship is dependent upon the other,
this attribute shall be the dependent one.
OWL Definition:
A PhysicalBreakdown is a
breakdown comprising physical elements.
The parent-child view is represented by PhysicalElementUsage instances relating
the physical elements in the breakdown which are represented by PhysicalElements.
EXAMPLE 1:
A physical breakdown of a motor car into body, roof, bonnet, bumpers etc.
NOTE 1:
The physical breakdown is a partitioning of a product into a set of related physical partitions so as to
form explicit, parent-child views.
Sources:
ISO 10303-239ed2 transformed to AP239AP233 PSM
Definition:
A
PhysicalBreakdown is a specialization 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 PhysicalElementUsage instances relating
the physical elements in the breakdown which are represented by PhysicalElements.
EXAMPLE
A physical breakdown might provide a decomposition of an automobile in terms such
as body, roof, bonnet, bumpers and this
breakdown might be different from, and orthogonal to, a parts decomposition.
Properties:
Parts:
the versions of the PhysicalBreakdown.
Definition:
A
PhysicalBreakdownContext is a specialization of
BreakdownContext
that is a membership relationship between a
PhysicalElement and a
PhysicalBreakdown of which the physical element is a member.
EXAMPLE
A wheel is a member of the
physical breakdown of an automobile.
Properties:
References:
Definition:
A
PhysicalBreakdownVersion is a specialization of
BreakdownVersion
that identifies a version of a
PhysicalBreakdown
EXAMPLE
An engineer modifies the current
physical breakdown for an aircraft on the basis of a tail re-design.
Properties:
References:
Definition:
A
PhysicalDocumentDefinition is a specialization of
DocumentDefinition. 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
PhysicalDocumentDefinition.
Properties:
References:
the set of instances of
Hardcopy that form the physical document.
OWL Definition:
A PhysicalElement is a
breakdown element that represents something physical.
EXAMPLE 1:
Body, roof, bonnet, bumpers etc. are examples of
physical elements of the
physical breakdown of an motor car.
Sources:
ISO 10303-239ed2 transformed to AP239AP233 PSM
Definition:
A
PhysicalElement is a specialization of
BreakdownElement that
identifies the elements in one or more
PhysicalBreakdown instances.
Properties:
Parts:
the versions of the PhysicalElement.
Definition:
A
PhysicalElementDefinition is a specialization of
BreakdownElementDefinition that identifies a view of a version (
PhysicalElementVersion) of a
PhysicalElement.
Properties:
References:
Definition:
A
PhysicalElementUsage is a specialization of
BreakdownElementUsage
that is a relationship between a parent and child
PhysicalElement.
EXAMPLE
In a physical
breakdown, the aircraft (parent) might include (as children) a fuselage, wings, tail
and undercarriage.
Properties:
References:
the second instance of PhysicalElement that is a part of the relationship.
NOTE
If one
PhysicalElement
in the relationship is dependent upon the other, this attribute shall be the
dependent one.
Definition:
A
PhysicalElementVersion is a specialization of
BreakdownElementVersion that identifies a version of a
PhysicalElement
EXAMPLE
An engineer changes the details
describing the undercarriage that is an element in a physical breakdown of an aircraft.
Properties:
Parts:
References:
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 1
Company Director
EXAMPLE 2
Service Engineer
Properties:
Parts:
a set of text based descriptions of the
Position.
a reference to a class held externally to the exchange file
that classifies this Position This Position is a member of the
referenced class.
References:
the
Address of the position. The value of the attribute need not be
specified.
the position that is used by the organization.
Definition:
A
PositionAssignment is an association of a
Position with activity or
product data.
Properties:
References:
the
Position
that is assigned to activity or product data.
the set of activity or product data to which the
Position is assigned.
Definition:
A
PositionGroup 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.
Properties:
Parts:
a reference to a class held externally to the exchange file
that classifies this PositionGroup This PositionGroup is a member
of the referenced class.
Definition:
A
PositionGroupAssignment is an association of a
PositionGroup with
activity or product data.
Properties:
References:
the set of activity or product data to which the
PositionGroup is assigned.
Definition:
A PositionGroupRelationship is a relationship that specifies the participation of a position in a group.
Properties:
References:
the collection of jobs or functions performed by people.
the job or function that belongs to the group.
Definition:
A
PositionPositionTypeAssignment is an assignment of
PositionType to a
Position. It allows many positions to be described by many position types.
Properties:
References:
Definition:
A PositionRelationship is a specialization of an RelationshipObject that is a relationship between
two instances of Position.
Examples
of relationships between Positions are:
EXAMPLE 1
Superior / Subordinate
EXAMPLE 2
Superceded by
Properties:
References:
one instance of
Position that participates in the relationship.
the other instance of
Position that participates in the
relationship. If one element of the relationship is dependent upon the other, this
attribute shall be the dependent one.
Definition:
A
PositionType is a recognized kind of position.
EXAMPLE 1
Chief Executive Officer
EXAMPLE 2
Manager
EXAMPLE 3
Service engineer
EXAMPLE 4
Programmer
EXAMPLE 5
Aircraft engineering technician propulsion
Properties:
Parts:
References:
the
TypeOfPerson that serves as a defining example for the
PositionType.
Definition:
A
PositionTypeAssignment is the association of a
PositionType with
activity or product data.
Properties:
References:
the
PositionType
that is assigned to activity or product data.
the set of activity or product data to which the
PositionType is assigned.
Definition:
A
PreDefinedTypeQualifier is a type of
TypeQualifierSelect
whose
name has predefined values:
- 'minimum': the value is a minimum value;
- 'maximum': the value is a maximum value;
- 'nominal': the value is a nominal value;
- 'specified': the value has been specified;
- 'typical': the value is typical;
- 'calculated': the value has been calculated;
- 'designed': the value represents a value intended by the design;
- 'estimated': the value has been estimated;
- 'measured': the value has been measured;
- 'required': the value represents a requirement;
- 'set point': the value is used as an initialization value;
- 'basic': the value is a basic value;
- 'lower deviation': the value is maximum deviation in the negative direction from the
nominal or basic value;
- 'upper deviation': the value is maximum deviation in the positive direction from the
nominal or basic value.
Properties:
Values:
the words by which the PreDefinedTypeQualifier is known.
Definition:
A PrecisionQualifier is a specification of the number of significant digits in the representation of a
value.
PrecisionQualifier shall be interpreted in accordance with PrecisionQualifier in part 45 of this standard.
NOTE
The precision is defined in clause 2 of "The Guide to the Expression of Uncertainty
in Measurement".
Properties:
Parts:
Values:
specifies the number of significant digits of the value.
Definition:
A
Probability is a specialization of
PropertyValue that is a
probability value (see definition 3.5.1 above).
Definition:
A ProbabilityByName is a specialization of Probability whose value belongs to a
one of a set of named classes, rather than by assigning a specific numerical value,
which may not be available.
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.
Properties:
References:
the named probability value
Definition:
A ProbabilityDerivationParameter is a specialization of NumericalValue that is used by a ProbabilityDerived 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 1
The value attribute, which holds the parameter value, is inherited from the parent
generalization.
Definition:
A
ProbabilityDerived is a specialization of
ProbabilityNumeric that
associates a particular value of
ProbabilityNumeric with the source from which the value
derived together with any parameters used to get the particular value.
NOTE 1
Where the probability derived from a probability
distribution, the parameters of ProbabilityDerived are those needed to get a single value from the distribution, and not those
which 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 ProbabilityDerived will be
the 'number of heads obtained'.
Properties:
Parts:
the source from which the value derives.
NOTE 2
The possible sources for values include a probability distribution, a statistic or
a reference document.
Definition:
A ProbabilityDistribution is a specialization of ProbabilityGenerator that is a
probability distribution.
NOTE 1
For a full understanding of probability distribution and the terms used, a textbook
on probability theory should be
consulted.
NOTE 2
This entity describes a particular probability distribution, rather than the general
type of distribution. For example,
in coin tossing experiment, the number of heads that may occur is given by a binomial
distribution - that is, a type of distribution,
and outside the scope of this module.
Properties:
Parts:
the text that distinguishes whether the domain of the probability distribution is
discrete or continuous.
EXAMPLE 1
The measurement of a person's height is a continuous distribution, since it can take
any value between 0 and
3m.
EXAMPLE 2
Coin tossing gives rise to a discrete distribution, since the number of heads cannot
be a fraction.
Values:
the name of the type of distribution. The value of the attribute need not be specified.
NOTE 4
The name is taken from reference-data, which is based on the standard mathematical
names for distributions, such
as "Binomial", "Normal", "Gaussian". Empirically derived distributions will not normally
be named.
the expectation E(x), which is the "summation" of x.p(x) over all x, where x is the
random variable, and p(x) is
the probability of its occurrence. The term "summation" covers both literal summation
in the case of a discrete distribution, and
integration for a continuous distribution.
the real number indicating the square of the standard deviation of the probability
distribution.
Definition:
A ProbabilityDistributionParameter is a specialization of NumericalValue 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 1
For many common distributions, the mean and the variance are sufficient to characterize
a distribution, and the parameter
list may be empty.
NOTE 2
ProbabilityDistributionParameter inherits the 'name' attribute from its parent generalization, and this is used to
identify
the name of the parameter within the particular parameterization. The value attribute
is also inherited.
Definition:
A ProbabilityFunctionValue is a specialization of NumericalValue 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.
Definition:
A ProbabilityGenerator is a specialization of PropertyValue. It is a source from
the ProbabilityDerived is derived. The ProbabilityDerivationParameters are applied to the ProbabilityGenerator to get the particular derived value.
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"
Definition:
A ProbabilityNamedValue is used to hold the name of the probability value.
NOTE
The value attribute is the description inherited from the parent generalization. In
general, this value will be one of an
enumeration of possible values defined through reference-data.
Properties:
Parts:
a text based descriptions of the
Product.
a reference to a class held externally to the exchange file
that classifies this ProbabilityNamedValue This
ProbabilityNamedValue is a member of the referenced
class.
the name of the probability value.
Definition:
A
ProbabilityNumeric is a specialization of
Probability that is
expressed as a numeric value between 0 and 1.
Properties:
Parts:
the value of the probability
Definition:
A ProbabilityNumericValue is a specialization of NumericalValue
providing a numeric representation of a probability.
NOTE
The value attribute is inherited from the parent generalization.
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 1
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.
EXAMPLE 1
The SS Titanic is a product that could be represented by the entity data type Product.
EXAMPLE 2
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 2
A product is identified by an organization or a person in an organization.
NOTE 3
A product may have zero or more versions. A version of a product is represented with
an instance of the entity
ProductVersion or of one of its specializations.
Properties:
Parts:
a set of text based descriptions of the
Product.
a reference to a class held externally to the exchange file
that classifies this Product This Product is a member of the
referenced class.
the versions of the Product.
Definition:
A ProductAsIndividual is a specialization 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
ProductAsIndividual.
NOTE 2
Where physical products are being represented, the
ProductAsIndividual
represents the physical or planned physical realization of a product.
EXAMPLE 1
The design of a personal computer is represented by a Product.
EXAMPLE 3
The personal computer that has been ordered, allocated a serial number for manufacturing
planning, but not yet manufactured, is
represented by a ProductAsIndividual and an associated revision represented by
ProductAsPlanned.
EXAMPLE 4
HMS Daring is the first of a new class of ships known as Type 45 Destroyers. It is
due to enter service in two years time.
- The Type 45 ship design that applies to HMS Daring is represented by a Product;
- The ship HMS Daring is represented by a ProductAsIndividual. This identifies the
planned ship, and when built, the actual ship;
- The planned revision of the future ship HMS Daring is represented by a ProductAsPlanned which is related back to the ProductAsIndividual;
- When built, the first revision the actual ship, HMS Daring will be represented by
a ProductAsRealized which is related back to the ProductAsIndividual.
Properties:
Parts:
the versions of the ProductAsIndividual.
Definition:
A
ProductAsIndividualEffectivity is a specialization of
Effectivity
for which the domain of applicability is defined as a set of instances of
ProductAsIndividual.
Properties:
References:
Definition:
A ProductAsIndividualVersion is a specialization of ProductVersion. It is a
revision of a ProductAsIndividual and acts as a collector of the definitions of this
revision.
EXAMPLE 2
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.
Properties:
Parts:
References:
Definition:
A ProductAsIndividualView is a specialization of ProductViewDefinition that
defines a characterization view of a version of a ProductAsIndividual.
Properties:
References:
Definition:
A
ProductAsPlanned is a specialization of
ProductAsIndividualVersion
that identifies a revision of an individual artefact that has yet to be made.
Definition:
A
ProductAsRealized is a specialization of
ProductAsIndividualVersion
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 1
Where physical products are being represented, the
ProductAsRealized represents the physical product - something one can touch.
Definition:
A
ProductBasedLocationIdentification is a specialization of
LocationRepresentation that specifies a location in the context of a product.
EXAMPLE 1
Seat number M in the
Aircraft.
Properties:
Parts:
the letters, numbers, or text, or combinations of letters, numbers, and text, that
identify a location in the context of a
product.
NOTE
Such identification can be expressed in functional or physical terms.
EXAMPLE 2
"1B" - where this is a seat number in an aircraft.
the text by which a location in the context of a product is known. The value of this
attribute need not be specified.
EXAMPLE 3
"The co-pilot's seat."
References:
the product that provides the context for the location specification.
Definition:
A
ProductConcept is the identification of a set of similar products that were, are or will be proposed
to
customers.
NOTE 1
The definition of product concepts is driven by market and customer requirements and
forecasting. A
ProductConcept often corresponds to the highest level item(s) manufactured by an organization for
customers.
EXAMPLE 1
In an organization which manufactures cars and engines for cars, the car models will
be represented by instances of
ProductConcept.
NOTE 2
The entity data type
ProductConcept enables to represent customer-oriented
identification of products that are to be delivered to customers, while the entity
data type Product enables to identify and to track
the history of items that are designed and manufactured, as a tangible solution, or
component of the solution, for a product concept.
NOTE 3
A product concept may be characterized by a set of product features identified by
the customers or derived from
customers' needs.
NOTE 4
Depending on the kind of industry and products, a product concept might be offered
to the customers in one or many
different configurations.
Properties:
Parts:
a reference to a class held externally to the exchange file
that classifies this ProductConcept This ProductConcept is a
member of the referenced class.
References:
the Market for which the ProductConcept is intended. The value of the attribute need not be specified.
Definition:
A
ProductConfiguration is the identification of a
ProductConcept as a
configuration.
NOTE 1
The entity
ProductConfiguration corresponds to the concept
of configuration item defined, in some configuration management standards, as an item
subject to configuration management.
EXAMPLE
A
ProductConfiguration may represent a component of a contracted product, onto
which severe safety rules apply and for which configuration management is therefore
rigorously applied.
Properties:
Parts:
a reference to a class held externally to the exchange file
that classifies this ProductConfiguration This
ProductConfiguration is a member of the referenced
class.
References:
the
ProductConcept that defines the context in which the
configuration item has been defined.
the set of instances of the entity data type
ItemDesignAssociation that identify
products which provide a solution for the configuration item.
Definition:
A
ProductConfigurationHierarchicalRelationship is a specialization of
ProductConfigurationRelationship that is used to represent a hierarchical relationship between a parent
ProductConfiguration and a child
ProductConfiguration.
Definition:
A
ProductConfigurationRelationship is a relationship between a pair of
ProductConfigurations.
Properties:
References:
the other instance of
ProductConfiguration that is a part of the
relationship. If one element of the relationship is dependent upon the other, this
attribute shall be the dependent one.
Definition:
A
ProductConfigurationRevisionSequence is a specialization of
ProductConfigurationRelationship that is used to relate a previous version (predecessor) of a
ProductConfiguration to the version that replaces it (successor).
Definition:
Properties:
References:
Definition:
A
ProductDesignToIndividual 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
ProductAsIndividual.
Properties:
References:
the design of the product that is being made.
the product that has been or is planned to be made from this design.
Definition:
A
ProductDesignVersionToIndividual is a relationship between a version of a product design, represented by
ProductVersion or
ProductConfiguration, and
the product that is planned to be made (
ProductAsPlanned) or has been made (
ProductAsRealized) from the design.
Properties:
References:
the version of the product design that is being made.
the product that has been or is planned to be made from this version of the design.
Definition:
A
ProductDesignViewToIndividual is a relationship between a product design, represented by
ProductViewDefinition. or
ProductConfiguration, and a
view of the product that is planned to be made or has been made (
ProductAsIndividualView)
from the design.
Properties:
References:
Definition:
A
ProductGroup is an identification of a set of
ProductConcepts,
Products,
ProductGroups,
ProductVersions or
ProductAsIndividuals that have been
grouped together.
EXAMPLE
All the aircraft sold to BigPlanes airways.
Properties:
Parts:
a reference to a class held externally to the exchange file
that classifies this ProductGroup This ProductGroup is a member of
the referenced class.
the characteristics that are common to all members of this group. The value of this
attribute need not be
specified.
the context in which the product group has meaning. The value of this attribute need
not be specified.
EXAMPLE 2
The project or equipment end item to which the group belongs.
Definition:
A
ProductGroupMembership is an identification of an instance of an entity defined in the type
ProductGroupMembershipSelect that belongs to a
ProductGroup.
Properties:
Parts:
References:
Definition:
A
ProductGroupRelationship is a relationship between two
ProductGroups.
ExternalOwlClass is used to specify the meaning or type of the relationship.
NOTE
A
subset is a common type of relationship. It indicates that one
ProductGroup is a subset of
another.
Properties:
Parts:
References:
one of the instances of
ProductGroup that is a part of the
relationship.
the other instance of
ProductGroup that is part of the
relationship. If one element of the relationship is dependent upon the other, this
attribute shall be the dependent one.
Definition:
A
ProductInAttachmentSlot is a specialization of
ViewDefinitionUsage
that is a relationship between an
AttachmentSlot and a
ProductViewDefinition of a
Product that is designed to be attached to the
attachment slot.
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.
Properties:
References:
Definition:
A
ProductPlannedToRealized is a relationship that establishes that a revision of a planned artefact represented
by
ProductAsPlanned has been realized as a revision of an actual artefact
ProductAsRealized.
Properties:
References:
Definition:
A
ProductRelationship is an association between two
Products.
Properties:
Parts:
References:
one of the instances of
Product that is a part of the relationship.
the other instance of
Product that is a part of the relationship.
If one element of the relationship is dependent on the other, this attribute shall
be the dependent one.
Definition:
A
ProductVersion 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
ProductVersion of the same
Product represents the history of the product.
Properties:
Parts:
a reference to a class held externally to the exchange file
that classifies this ProductVersion This ProductVersion is a
member of the referenced class.
References:
the
Product, the
ProductVersion identifies a version of.
Definition:
A
ProductVersionRelationship is an association between two versions of
Product.
Properties:
References:
the first instance of
ProductVersion that is a part of the
relationship.
the other instance of
ProductVersion that is a part of the
relationship. If one element of the relationship is dependent up on the other, this
attribute shall be the dependent one.
OWL Definition:
A ProductViewDefinition is a
collector of information for a product version relevant from the perspective of a particular point of view defined by an application domain and a life-cycle phase.
EXAMPLE 1:
The electrical
product view and mechanical
product view provide the electrical and mechanical aspects of a
product specification.
Sources:
ISO 10303-239ed2 transformed to AP239AP233 PSM
Definition:
A
ProductViewDefinition is a characterization of a
ProductVersion,
relevant in one or more application domains and for one or more life cycle stages.
A ProductViewDefinition is a collector of
the properties that characterize the ProductVersion in the initialContext and
additionalContexts.
EXAMPLE 1
The design of the SS Titanic and the as-built description of the SS Titanic can be
represented as two instances of
ProductViewDefinition.
Properties:
Parts:
a set of text based descriptions of the ProductViewDefinition.
a reference to a class held externally to the exchange file
that classifies this ProductViewDefinition This
ProductViewDefinition is a member of the referenced
class.
References:
the initial
ViewDefinitionContext in which the
definedVersion
has been characterized by the
ProductViewDefinition.
the
ProductVersion of which the
ProductViewDefinition
provides a characterization.
Constraints:
Constraint: ur1Specification: (OCL2.0)
ProductViewDefinition::allInstances()->isUnique(Sequence{viewDefinitionOf, initialContext})
Definition:
A Project is an identified program of work.
Properties:
Parts:
a set of text based descriptions of the
Project.
a reference to a class held externally to the exchange file
that classifies this Project This Project is a member of the
referenced class.
References:
the set of instances of
Organization that specify the organizations
that are responsible for the project.
the date and time or the
Activity when execution of the
Project is expected to start. The value of this attribute need not be specified.
the date and time or the
Activity when the
Project is or was expected to be finished. The value of this attribute need not be specified.
Values:
the date and time when the
Project was actually started. The value of this
attribute need not be specified.
the date and time when the
Project was actually finished. The value of this
attribute need not be specified.
Definition:
A
ProjectAssignment is a mechanism to associate a
Project with
activity or product data.
Properties:
References:
Definition:
A
ProjectRelationship is an association between two instances of
Project with an identification and a description of their relationship.
Properties:
References:
one instance of
Project that is a part of the relationship.
the other instance of
Project that is a part of the relationship.
If one element of the relationship is dependent upon the other, this attribute shall
be the dependent one.
Definition:
A
PromissoryAssemblyViewUsage is a specialization of
AssemblyViewRelationship. It establishes a relationship between an assembly and a component, regardless of
the number of intermediate levels between them, which
may be established with instances of
NextAssemblyViewUsage.
NOTE
A
PromissoryAssemblyViewUsage may be used when the product structure is not completely defined, to capture the
intent that the constituent will be used in that assembly.
Definition:
A PropertyDefinitionAssignment is a specialization of an AssignmentObject that represents the assignment
of a ExternalPropertyDefinition to product or activity data.
Properties:
References:
the set of units that are allowed to be used when specifying a value for the property.
Constraints:
Constraint: UR1Specification: (OCL2.0)
PropertyDefinitionAssignment::allInstances()->isUnique(Sequence{assignedTo, assignedPropertyDefinition})
Definition:
To be defined
Properties:
References:
To be defined
To be defined
Definition:
A PropertyValue acts as a proxy for a notional property value which may have several representations.
NOTE
The actual magnitude and descriptions of a PropertyValue (e.g. 1 kilogramme or 2.2 pounds) are only provided as part of one
or more representations of a PropertyValue. The PropertyValue itself cannot have a magnitude, or even a name, that is
independent of the type of representation chosen for the value in question.
Properties:
Parts:
a reference to a class held externally to the exchange file
that classifies this PropertyValue This
PropertyValue is a member of the referenced
class.
the
MeasureQualification that is that provides information about the
uncertainty associated with the measured
PropertyValue.
References:
Definition:
A PropertyValueAssignment assigns a PropertyValue (or collection of equivalent PropertyValues) to activity or product data.
Properties:
Parts:
the
PropertyValue, or collection of equivalent PropertyValues, assigned to activity or product data.
NOTE
This allows multiple representations of the same conceptual property value to be assigned,
each property value should have the same property definition.
EXAMPLE
A collection of mass properties such as "1Kg" and "2.2lb" could be assigned representing
the same conceptual mass in different units.
References:
the set of activity or product data to which the
PropertyValue is assigned.
OWL Definition:
A PropertyValueRelationship is a
relationship between two property values.
EXAMPLE 1:
An association between a value for a length
property expressed in metres and an equivalent value for the same
property expressed in yards.
EXAMPLE 2:
10 metres is equivalent to 10.936133 yards
Sources:
ISO 10303-239ed2 transformed to AP239AP233 PSM
Definition:
A PropertyValueRelationship is a specialization of RelationshipObject.
It represents an association between two PropertyValues.
Properties:
References:
Definition:
A Proxy is a relationship between a subject and something for which the subject is a proxy.
Properties:
References:
the reference to the proxy
Definition:
A ProxyRelationship is a relationship between a pair of Proxys.
NOTE
This relationship may be classified to provide more specific meanings.
Properties:
References:
one of the instances of
Proxy that is a part of the
relationship.
the other instance of
Proxy that is part of the
relationship. If one element of the relationship is dependent upon the other, this
attribute shall be the dependent one.
Definition:
A QualificationAssignment is the assignment of a qualification to a person or organization.
Properties:
References:
the type of qualification that has been gained by the person or organization.
the person, organization or person in organization who has the qualification.
Definition:
A
QualificationType is the identification of a definitive recognition as a practitioner.
EXAMPLE 1
A
driving licence.
EXAMPLE 2
A qualification for executing the Ground Running task for RB211 engines.
EXAMPLE 3
A Military rank such as Colonel, or Captain
EXAMPLE 4
Educational qualification such as GCSE, A level, Degree, Ordinary National Certificate,
Higher National Certificate,
City and Guilds, or GNVQ.
Properties:
Parts:
Definition:
A
QualificationTypeRelationship is an association between two
QualificationTypes.
EXAMPLE 1
Qualification X is a prerequisite for qualification Y.
EXAMPLE 2
Qualification X is equivalent to qualification Y.
Properties:
References:
the other instance
QualificationTypes participating in the
relationship. If one element of the relationship is dependent upon the other, this
attribute shall be the dependent one.
Definition:
A
QualitativeUncertainty is a specialization of
UncertaintyQualifier.
The uncertainty is defined in clause 2 of "The Guide to the Expression of Uncertainty
in Measurement".
Properties:
Parts:
specifies a STRING for the QualitativeUncertainty.
Definition:
A RandomVariable is a specialization of NumericalValue that is the
value of a random variable.
NOTE
The value attribute is inherited from the parent generalization.
Definition:
A RegionalCoordinate is a location that is specified relative to a Regional location system.
Properties:
Parts:
a reference to a class held externally to the exchange file
that classifies this RegionalCoordinate This RegionalCoordinate is
a member of the referenced class.
the value and unit for the coordinate within the regional location system used.
References:
Definition:
A
RegionalGridLocationRepresentation is a specialization of
LocationRepresentation that specifies a reference grid system.
Definition:
A
RelatedConditionParameter is a relationship between a
ConditionParameter and a
ConditionEvaluationParameter.
This relationship is
used to record the relationship between the parameters used to define a condition
and the parameters used to evaluate it.
EXAMPLE
The value of oil pressure (1.9 bar) used in
ConditionEvaluation (instance 87) was a
measured value of the parameter used to define condition 29 (oil pressure on gauge
3).
Properties:
Parts:
a reference to a class held externally to the exchange file
that classifies this RelatedConditionParameter This
RelatedConditionParameter is a member of the referenced
class.
References:
Definition:
A
RelatedConsequence is a specialization of
ViewDefinitionRelationship
describing the expected consequences of a specific perception of a risk.
Properties:
References:
represents the expected consequences if the risk occurs
represents the perception of the risk that can lead to the specified consequences.
OWL Definition:
A RelationshipObject is a
dependency between two objects.
NOTE 1:
The objects being related are normally, but not always, of the same type or subtype.
Definition:
A RelationshipObject represents a dependency between sets of product or activity data.
Properties:
Parts:
a reference to a class held externally to the exchange file
that classifies this RelationshipObject This RelationshipObject is
a member of the referenced class.
Definition:
A
RepeatCount is a type of
LoopingElement. It invokes a specified
number of repetitions of the
RepeatedElement
TaskElement inherited from the
LoopingElement
parent generalization.
Properties:
Values:
the number of times the RepeatedElement is to be
executed.
NOTE
If the
RepeatCount entity is combined with the other subtypes of
LoopingElement, this becomes the maximum number of repetitions.
Definition:
A
RepeatUntil is a type of
LoopingElement. It invokes repetitions of a
further
TaskElement and is repeated until the specified condition is satisfied. The element
being repeated shall be executed at least once and the condition tested after the
first execution.
Properties:
References:
the criterion to be tested in order to determine that the looping method shall be
exited.
Definition:
A
RepeatWhile is a type of
LoopingElement. It invokes repetitions of a
further
TaskElement and is repeated while the specified condition is satisfied. The test
condition shall be evaluated prior to invoking the method and may result in the
LoopingElement not being executed at all.
Properties:
References:
the criterion to be tested in order to determine that the
LoopingElement shall be continued.
Definition:
A RequiredResource is an identified need for resource. The role of a required
resource is determined by classification.
EXAMPLE 1
"facility", "test equipment", "supervisor" are examples of
classifications of a required resource.
Properties:
Parts:
a reference to a class held externally to the exchange file
that classifies this RequiredResource This RequiredResource is a
member of the referenced class.
the required quantity of the required resource. The value of this attribute
need not be specified.
EXAMPLE 2
Quantity can be specified using amount or duration.
References:
a reference to an identifiable item (within the application context) that will satisfy
that requirement for a resource.
EXAMPLE
Tool kit, facility, and product category are examples of resource items.
Definition:
A
RequiredResourceAssignment is an association of a resource requirement statement with one or more entities that
requires the resource.
EXAMPLE 1
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 2
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 3
A resource required by the activity "12" needs to be calibrated prior to usage. The
calibration activity "21" is
associated with the same required resource
EXAMPLE 4
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.
Properties:
References:
the required resource that is to be associated with the requiring entity.
the entity to which the required resource statement is assigned.
Definition:
A
RequiredResourceRelationship is a relationship between two required resource statements. The meaning of the
relationship is determined by classification.
EXAMPLE 1
"alternative" and "realized by" are examples of required resource
relationship.
Properties:
Parts:
References:
the other instance of
RequiredResource that is a part of the
relationship. If one element of the relationship is dependent upon the other, this
attribute shall be the dependent one.
Definition:
A
Requirement is a specialization of
Product that is used to uniquely
identify a requirement.
NOTE 1
The term "requirement" is used here in the sense that term is used in systems engineering
and
similar industrial domains.
EXAMPLE
A requirement may be identified as "NOx emissions requirement", and uniquely identified
as "Req2".
NOTE 3
Systems engineering tools and organizations may use differing identification mechanisms.
Multiple identifiers may be
assigned to a requirement using the
Identifier entity.
Properties:
Parts:
the versions of the Requirement.
Definition:
A
RequirementAssignment is used to relate a requirement (via the
RequirementViewDefinition 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.
Properties:
References:
the item which has the requirement assigned to it.
Definition:
A RequirementCollectionRelationship is a specialization of ViewDefinitionRelationship that is used to relate a parent (collection) requirement to its member requirements.
This
provides a method for collecting together a set of requirements and treating them
as a single requirement, whilst still being able to
refer to individual requirements.
Definition:
A
RequirementSatisfiedBy is a relationship between an item (specified in
RequirementAssignmentSelect) and a requirement, asserting that the item satisfies the identified requirement.
EXAMPLE
A
data type used to represent a vehicle's engine with a power output of 160BHP could
be asserted to satisfy a requirement "the vehicle
shall have a maximum power output of at least 150BHP".
Properties:
Parts:
a reference to a class held externally to the exchange file
that classifies this RequirementSatisfiedBy. This RequirementSatisfiedBy is a member of the
referenced class.
References:
the item that satisfies the requirement.
the requirement that is satisfied.
the
RequirementAssignment that is satisfied by the
RequirementSatisfiedBy. The value of this attribute need not be specified.
Definition:
A
RequirementSource is a relationship between a requirement (via the
RequirementViewDefinition 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.
Properties:
Parts:
a reference to a class held externally to the exchange file
that classifies this RequirementSource This RequirementSource is a
member of the referenced class.
References:
the item which is the source of the requirement.
the requirement which is to be related to its source.
Definition:
A
RequirementVersion is a specialization of
ProductVersion 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.
Properties:
Parts:
References:
the
Requirement
that the
RequirementVersion is a version of.
Definition:
A
RequirementVersionRelationship is a specialization of
ProductVersionRelationship that is used to relate a previous version (predecessor) of a requirement to the version
that
replaces it (successor).
Properties:
Parts:
References:
Definition:
A RequirementViewDefinition is a specialization of ProductViewDefinition 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 1
An engineer may have responsibility for collecting all requirements associated with
the cooling
of an engine - covering engine block, tubing, water pump, electric fan.
Some requirements in a
RequirementViewDefinition might impact on different disciplines. Multiple RequirementViewDefinition instances may be used
to present different views of a given requirement for each discipline.
The definition of the requirement is represented by a set of definitional properties
referenced from
RequirementViewDefinition.definitionalRepresentations. If more than one definitional property is provided
each property shall be equivalent.
Any other property that
is associated with the RequirementViewDefinition
is assumed to be a non-defining property, such
as an annotation etc.
EXAMPLE 2
The requirement that the weight should be less than 4 Kgs can be represented by
by a string representation "weight must be 4Kg" and a numeric representation "4Kg"
specified as a
value with units.
NOTE
The definition attribute of each of the definitionalRepresentations shall refer to
a definition for RequirementDefinition.
EXAMPLE 3
The definition attribute of the definitionalRepresentations could refer to an
ExternalPropertyDefinition
that uses an
ExternalOwlObject with individual set to
"http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/contexts/OASIS/refdata/plcs-rdl#Requirement_definition".
Properties:
Parts:
the properties that define the requirement
References:
the
RequirementVersion of which the
RequirementViewDefinition provides a characterization.
Definition:
A
RequirementViewDefinitionRelationship is a specialization of
ViewDefinitionRelationship. A
RequirementViewDefinitionRelationship is the association between one
RequirementViewDefinition and another.
Properties:
References:
Definition:
A
ResourceAsRealized is a record of a resource that has been used or consumed.
EXAMPLE
A resource as realized can
be classified as "Used" or "Consumed".
Properties:
Parts:
a reference to a class held externally to the exchange file
that classifies this ResourceAsRealized This ResourceAsRealized is
a member of the referenced class.
the amount of the ResourceAsRealized that has been used or consumed. The value of this attribute need not be specified.
EXAMPLE
The quantity can be recorded as amount or duration.
References:
a reference to an item that is provided with resource management capabilities.
Definition:
A ResourceAsRealizedAssignment 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.
Properties:
References:
the resource record that is to be associated with one or more activities or tasks
that used or consumed the
resource.
the entity that used or consumed the resource.
Definition:
A ResourceAsRealizedRelationship is a relationship between the record of used or consumed resources and the corresponding
statement of RequiredResource.
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.
Properties:
References:
the other instance of that is a part of the relationship. If one element of the relationship
is dependent upon
the other, this attribute shall be the dependent one.
Definition:
A ResourceEvent is an abstract generalization of instances that represents an event or action that
affects the balance or availability of a managed resource.
NOTE
Only non-abstract specializations of the ResourceEvent can be instantiated.
A ResourceEvent is The role of a
resource event is determined by which is defined by the
classifiedAs property.
EXAMPLE
A resource event can be classified as "Planned" or "Actual".
Properties:
Parts:
a reference to a class held externally to the exchange file
that classifies this ResourceEvent This ResourceEvent is a member
of the referenced class.
the measure of the amount of resource affected by the change. The value of this attribute
need not be specified.
References:
the managed resource that is affected by the resource event.
Definition:
A
ResourceEventCorrespondenceRelationship is an association of a resource event and a corresponding statement of
RequiredResource. 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".
Properties:
References:
the instance of
ResourceEvent that is a part of the relationship.
Definition:
A
ResourceEventRelationship is a specification of how an
ResourceEvent
may be associated with another
ResourceEvent. The meaning of the relationship is determined
by classification.
EXAMPLE
A managed resource relationship can be classified as "realized by" or "replaces".
Properties:
References:
one of the instances of
ResourceEvent that is a part of the
relationship.
the other instance of
ResourceEvent that is a part of the
relationship. If one element of the relationship is dependent upon the other then
this attribute shall be the dependent one.
Definition:
A
ResourceGroupRelationship is a specialization of
ResourceItemRelationship that specifies the means to associate two resource items that are part of a resource
group. The
meaning of the entity is determined by classification.
EXAMPLE 1
The relationship between a tool set and a mallet could be
classified as "Contains".
EXAMPLE 2
The relationship between a facility and compressed air could be classified as "Provides".
Properties:
Parts:
the measure of the amount of related
ResourceItem. The value of the
attribute need not be specified.
Definition:
A
ResourceItem is an item that can occur in the role of a resource within the application context.
EXAMPLE
A
ResourceItem may be classified as "Facility", "Replaceable unit", or "Package".
Properties:
Parts:
a reference to a class held externally to the exchange file
that classifies this ResourceItem This ResourceItem is a member of
the referenced class.
Definition:
A ResourceItemAssignment 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".
Properties:
References:
the resource item that is to be associated with an item.
the resource assignment item to which the resource item is assigned.
Definition:
A ResourceItemRealization is a specification of how a resource item may be associated with an item that serves
as the resource.
EXAMPLE
A product may serve as a resource.
Properties:
Parts:
References:
the item that is to be associated with the resource that it serves as.
the resource that is to be associated with an item that serves as that resource.
Definition:
A ResourceItemRelationship 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".
Properties:
Parts:
References:
one of the instances of
ResourceItem that is a part of the
relationship.
the other instance of
ResourceItem that is a part of the
relationship. If one element of the relationship is dependent upon the other, this
attribute shall be the dependent one.
Definition:
A
Risk is a specialization of Product that is the potential for realization of unwanted
negative consequences of an
event.
NOTE 1
ISO GUIDE 73 defines "risk" as the combination of the probability of an event and
its consequence. In some
situations, risk is a deviation from the expected.
NOTE 2
A risk can also have a possible positive outcome. In such cases it is often referred
to as an opportunity or reward.
NOTE 3
ISO/IEC Guide 51:1999 defines risk as the combination of the probability of occurrence
of harm and the severity of that
harm.
NOTE 4
In the safety field, risk management is focused on prevention and mitigation of harm.
ISO/IEC Guide 51:1999 should be
used for safety aspects.
EXAMPLE 1
'Line shutdown' is an example of
Risk in the context of a manufacturing
system's reliability.
EXAMPLE 2
'Transportation jam-up', 'customer anger', 'collateral damage', and 'greater susceptibility
to interruption of supply
during crises' are all examples of
Risk.
EXAMPLE 3
'Privacy' and 'security' are examples of
Risk for the telecommunications
industry.
EXAMPLE 4
'Fly-by-wire', the form-fit-function replacement of mechanical devices with a combination
of electrical, hydraulic,
and pneumatic units.
EXAMPLE 5
Timing such as 'premature rejection' and 'premature commitment' are other examples
of
Risk.
Properties:
Parts:
the versions of the Risk.
Definition:
A
RiskConsequence is a specialization of
RiskViewDefinition and
specifies the outcome of an event.
NOTE 1
There may be one or more consequences of an event.
NOTE 2
Consequences can range from positive to negative. However, consequences are always
negative for safety aspects.
NOTE 3
Consequences can be expressed qualitatively or quantitatively.
Definition:
A RiskEvent
is a specialization of an AssignmentObject
that represents the unwanted (or wanted) event resulting in the RiskPerception.
The probability of the event occurring is represented by a set of probabilities referenced
from
RiskEvent.probabilityRepresentations. If more than one probability is provided
each probability shall be equivalent.
NOTE
The definition attribute of the probabilityRepresentations shall refer to a definition
for perceivedProbability.
EXAMPLE
The definition attribute of the probabilityRepresentations could refer to an
ExternalPropertyDefinition
that uses an
ExternalOwlObject with individual set to
"http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/contexts/OASIS/refdata/plcs-rdl#Perceived_Probability".
Properties:
Parts:
the probability representations of the risk event occurring.
References:
a set of items that contains the various perceptions of the risk that this event will
trigger.
Definition:
A RiskImpactAssignment is a specialization of AssignmentObject and a type of
PropertyAssignmentSelect.
It assigns a RiskConsequence to a set of items that might be impacted by the risk.
Properties:
References:
Definition:
A RiskPerception is a specialization of RiskViewDefinition that defines values
or concerns (a risk level) with which a stakeholder views a particular Risk.
The risk level is represented by a set of property values referenced from
RiskPerception.riskLevelRepresentations. If more than one property value is provided
each property value shall be equivalent.
EXAMPLE 1
One riskLevelRepresentation could be 4 (from a maximum of 5) and a second could be
"high".
NOTE 1
The definition attribute of each of the riskLevelRepresentations shall refer to a
definition for RiskLevel.
EXAMPLE 2
The definition attribute of the riskLevelRepresentations could refer to an
ExternalPropertyDefinition
that uses an
ExternalOwlObject with individual set to
"http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/contexts/OASIS/refdata/plcs-rdl#Risk_Level".
NOTE 2
RiskPerception depends on the stake holder's expressed needs, issues, and knowledge.
NOTE 3
RiskPerception can differ from objective data.
NOTE 4
RiskPerception may be used qualitatively or quantitatively to form a risk matrix.
NOTE 5
Risk will be perceived differently in different contexts, such as in the context of human
safety, mission success, project time schedule, performance or economy.
Properties:
Parts:
optionally defines a collection of representations for an identifiable goal or objective
for the
RiskPerception.
Definition:
A
RiskPerceptionRelationship defines an association between two instances of
RiskPerception.
Properties:
References:
Definition:
A RiskPerceptionSourceAssignment is a specialization of AssignmentObject.
It assigns a RiskPerception to a set of one or many items that are the source for the
RiskPerception.
Properties:
References:
the
RiskPerception that is assigned to the set of one or many items
that are its source.
Definition:
A RiskRelationship is a specialization of ProductRelationship.
It is an association between two an association between two instances of Risk.
Properties:
References:
the first instance of
Risk that is a part of the
relationship.
the second instance of Risk that is a part of the relationship.
NOTE
If one
Risk in
the relationship is dependent upon the other, this attribute shall be the
dependent one.
Definition:
A RiskVersion is a specialization of ProductVersion.
It defines a form of a risk that differ in certain respects from an earlier form
of that risk or from other forms of that risk.
NOTE 1
Use of
RiskVersion allows several
RiskPerception instances to be
assigned to a specific
Risk.
Properties:
Parts:
References:
the
Risk that
the
RiskVersion is a version of.
Definition:
ARiskViewDefinition is a specialization of a ProductViewDefinition and is an abstract generalization of instances that represents …
NOTE
Only non-abstract specializations of the RiskViewDefinition can be instantiated.
Properties:
References:
the
RiskVersion of which the
RiskViewDefinition provides a characterization.
Definition:
A
Scheme is a specialization of
ActivityMethod. It provides the
identification and description of an intended course of action to accomplish an objective.
A
Scheme enables the ordering of
entries. Dates and times may be specified for entries and time intervals between entries.
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.
Properties:
Parts:
the versions of the Scheme
Definition:
A
SchemeEntry is a specialization of
ActivityMethod that provides the
identification and description of a single entry in a specific
Scheme.
NOTE 1
A
SchemeEntry may be associated with time constraints.
NOTE 2
A
SchemeEntry only exists within the scope of a specific
Scheme.
Properties:
References:
Definition:
A SchemeEntryAssignment
is a specialization of an AssignmentObject
that represents the assignment of
SchemeEntry instances to instances
that are specializations of SchemeEntryAssignmentSelect.
NOTE
The
SchemeEntryAssignment links the single items included in Plans and Schedules with their associated
SchemeEntry. These items may be actions, events, or tasks depending on the nature of the Plan
or
Schedule.
Properties:
References:
the
SchemeEntry that is assigned to activity or product data.
the set of items which are associated with a
SchemeEntry.
Definition:
A
SchemeEntryRelationship is a specialization of
ActivityMethodRelationship. It relates two
SchemeEntry entities. An association
may exists between
SchemeEntry entities that relate to different
Scheme or between different
SchemeEntry entity instances
for the same
Scheme.
NOTE
The SchemeEntryRelationship provides the ability to relate
entries included in Plans or Schedules in different ways. By applying classifications
on the SchemeEntryRelationship it can be
used for different purposes.
EXAMPLE
Decomposition, Dependency, and sequencing are examples of kinds of relationships possible
between schema entries.
Properties:
References:
the first instance of
SchemeEntry that is a part of the
relationship.
the second instance of SchemeEntry that is a part of the
relationship.
NOTE
If one
SchemeEntry in the relationship is dependent upon the other, this attribute shall be
the dependent one.
Definition:
A SchemeRelationship is a specialization of ActivityMethodRelationship
relating two Schemes.
NOTE
The
SchemeRelationship provides the ability to relate
Plans or Schedules represented by the
Scheme entity in different ways. If classifications
are available to the schema using this on, by applying classifications on the
SchemeRelationship it can be used for different
purposes.
EXAMPLE
Decomposition, based-on, alternative, version are kinds of relationships between
Schemes.
Properties:
References:
the first instance of
Scheme that is a part of the
relationship.
the second instance of Scheme that is a part of the relationship.
NOTE
If one
Scheme in
the relationship is dependent upon the other, this attribute shall be the
dependent one.
Definition:
A SchemeSubjectAssignment
is a specialization of an AssignmentObject
that represents the assignment of
Scheme with a specific subject.
NOTE
The SchemeSubjectAssignment 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.
Properties:
References:
the
Scheme that is assigned to a specific subject.
the set of items to which a
Scheme is associated.
Definition:
A
SchemeVersion is a specialization of
ActivityMethod. It enables
version control of
Scheme.
Properties:
Parts:
References:
the
Scheme that the
SchemeVersion is a version of.
Definition:
A SchemeVersionAssignment
is a specialization of an AssignmentObject
that represents the assignment of a
SchemeVersion instances to instances
that are specializations of SchemeVersionAssignmentSelect.
Properties:
References:
Definition:
A SchemeVersionRelationship is a specialization of ActivityMethodRelationship relating two SchemeVersions.
Properties:
References:
Definition:
A SecurityClassification is a level of confidentiality that can be applied to protect activity or product
data
against unauthorized usage.
Properties:
Parts:
References:
a reference to an
ExternalOwlClass or an
ExternalItem held externally to the exchange file that provides the definition of
the
SecurityClassification.
Definition:
A
SecurityClassificationAssignment is an association of a
SecurityClassification with activity or product data.
Properties:
References:
Definition:
A
SelectedItemAssignment is the identification of the product or activity data referenced by
Item as being a member of
a class identified by
ClassSelect.
Properties:
Parts:
the class to which the product or activity data
referenced by
Item belongs.
References:
the product or activity data that is being designated as a
ClassSelect.
the context in which the product or activity data is being identified as being a
ClassSelect.
EXAMPLE
The engine is a identified as a selected item on the car.
Definition:
A
SequenceOfState is a specialization of
StateRelationship in which
one set of
State precedes another set of
State.
Definition:
A
SequenceOfStateDefinition is a specialization of
StateDefinitionRelationship. It defines a sequence of two or more state definitions.
Definition:
A SequencingRelationship is a specialization of SchemeEntryRelationship. It
defines a specific type of sequencing and relative timing for two SchemeEntry.
NOTE 1
Specific types of sequencing could include start-start, finish-start.
Properties:
References:
the amount of time, either positive or negative, before the sequencing applies between
the RelatingEntry and the RelatedEntry. The value of this attribute need not be specified.
NOTE 2
For a positive
timeLag, the
RelatingEntry is the later entry in time.
Definition:
A
SerialEffectivity is a specialization of
Effectivity for which the
domain of applicability is defined as a possibly open-ended interval of serial numbers.
Properties:
Parts:
the first valid serial number.
the last valid serial number. The value of the attribute need not be specified. If
the value for this attribute
is not specified, the interval of applicability has no upper bound.
Definition:
ASetMembership is a relationship that is between a set and a thing that indicates the thing is a
member of the set.
NOTE
the term 'class' and 'set' are synonyms.
Properties:
References:
the member of the set
the set that has the thing as a member
Definition:
A
ShapeDependentPropertyRepresentation is the representation of a characteristic derived from or imposed to an
ItemShape or a
ShapeElement.
EXAMPLE 1
The centre of mass is an example of shape dependent property, of a shape, that can
be represented by a cartesian point.
EXAMPLE 2
The area and the volumes are examples of characteristic that can be represented by
a measure value with unit.
NOTE 1
A ShapeDependentPropertyRepresentation is independent of the representations of the shape.
Properties:
Parts:
the string that specifies the type of the characteristic that is represented.
Where applicable, the following values shall be used:
- 'centre of mass': the characteristic is the centre of the mass of the describedElement, evaluated or required
independently of any representation of the describedElement;
- 'centroid': the characteristic is the centre of mass of a body as evaluated from a
geometric representation of the
describedElement;
- 'moment of inertia': the characteristic is the 3*3 matrix of inertia of the describedElement;
- 'surface area': the characteristic is the extent of the surface of the describedElement;
- 'volume': the characteristic is the volume of the describedElement.
the PropertyValue that contains the items that express the characteristic.
NOTE
Depending on the
characteristicType, the
describedElement may need to be a
GeometricModel.
References:
Definition:
A ShapeDescriptionAssociation is an association of a geometric representation with a shape characteristic.
Properties:
Parts:
References:
Definition:
A
ShapeElement is a portion of a shape.
EXAMPLE
The threaded portion of the shape of a bolt may be represented as
a ShapeElement, so that other properties, such as surface finish, may be associated with it.
Properties:
Parts:
the name of the ShapeElement. The value of this attribute need not be specified.
References:
the
ItemShape that the
ShapeElement is a part of.
Definition:
A
ShapeElementRelationship is a relationship between two instances of
ShapeElement.
Properties:
Parts:
References:
one of the instances of
ShapeElement that takes part in the
relationship.
the other instance of
ShapeElement that takes part in the
relationship.
Definition:
A
ShapePlacementAssociation is a specialization of
ShapeDescriptionAssociation.
Properties:
References:
Definition:
A
SimultaneousElements is a specialization of
ConcurrentElements that
represents two or more actions to be performed together.
Definition:
A
StandardUncertainty is a specialization of
UncertaintyQualifier. A
StandardUncertainty may be an
ExpandedUncertainty. The uncertainty is defined in
clause 2 of "The Guide to the Expression of Uncertainty in Measurement".
Properties:
Values:
specifies a REAL value of the uncertainty.
Definition:
A
StartTask is a type of
TaskElement. It signifies the start point of
the task.
NOTE
Not all formal task description require start and end elements, their inclusion is
in a sequence is optional.
OWL Definition:
A State is a
mode of being in which something does, could, or did exist for a period of time.
EXAMPLE 1:
Main Engine No. 1 is in the state "operation".
EXAMPLE 2:
The portable computer's power supply was attached after it displayed a warning of
a "low-battery" state.
EXAMPLE 3:
When Generator No. 2 exceeds 5,000 service hours, it will enter "maintenance" state.
NOTE 1:
The period of existence may be an instant or longer.
Sources:
ISO 10303-239ed2 transformed to AP239AP233 PSM
Definition:
A
State is the mode of being in which something does or could exist or existed for a period
of time.
NOTE 1
A state's existence can be just a state that an instance is currently in, a predicted
state that an instance will eventually
be in, or an observed state that an instance has been in.
NOTE 2
The period of existence may be an instant or longer.
EXAMPLE 1
Main Engine No. 1 is in "operation".
EXAMPLE 2
When Generator No. 2 surpasses 5,000 service hours, it will enter "maintenance" mode.
EXAMPLE 3
The portable computer's power supply was attached after it displayed a "low-battery"
warning.
Properties:
Parts:
a set of text based descriptions of the
State.
a reference to a class held externally to the exchange file
that classifies this State This State is a member of the
referenced class.
OWL Definition:
A StateAssertion is a
statement confirmed by evidence such as a measurement assertion that a state is in conformance with a particular state definition.
Sources:
ISO 10303-239ed2 transformed to AP239AP233 PSM
Definition:
A
StateAssertion is used to assert that the subject
State is in
conformance with a particular
StateDefinition.
Properties:
Parts:
a reference to a class held externally to the exchange file
that classifies this StateAssertion This StateAssertion is a
member of the referenced class.
References:
the subject
State being asserted.
OWL Definition:
A StateAssessment is a
subjective statement without supporting evidence that a state is in conformance comparable with a particular state definition.
NOTE 1:
A state assessment is made without objective evidence, e.g. a measurement.
Sources:
ISO 10303-239ed2 transformed to AP239AP233 PSM
Definition:
A
StateAssessment is used to determine whether the subject
State is
comparable with a particular
StateDefinition.
Properties:
Parts:
a reference to a class held externally to the exchange file
that classifies this StateAssessment This StateAssessment is a
member of the referenced class.
References:
Definition:
An
StateAssignment is a relationship that allows a subject to have
State or to be in a
State.
Properties:
References:
a
State the subject has or is in.
the subject which has or is in a
State.
Definition:
A StateCauseEffect is a specialization of state relationship and it relates two or more states as one
state causing
particular resulting effect state(s). In turn, an effect state can become a new causing
state yielding in yet more effect states.
Definition:
A
StateCauseEffectDefinition is a specialization of
StateDefinitionRelationship that is used to define a causal relationship between two sets of
StateDefinition entities. At least one
StateDefinition
acts as a
cause and at least one
StateDefinition acts as a
effect.
Definition:
A
StateComplementDefinition is a specialization of
StateDefinitionRelationship. It is a relationship among three sets of
StateDefinition entities. It defines the complement of a set of
StateDefinition
entities relative to a set of
StateDefinition entities that are the universe.
NOTE 1
The semantics are the same as in elementary set theory.
NOTE 2
The relationship between a
StateDefinition and its complement is
symmetrical.
Properties:
References:
the complement of set1 within universe.
OWL Definition:
A StateDefinition is a
definition of a possible or typical state.
EXAMPLE 1:
The definition of the
state, ”flying” is that the aircraft is off the ground.
Sources:
ISO 10303-239ed2 transformed to AP239AP233 PSM
Definition:
A StateDefinition is a mode of being. In formal systems, a StateDefinition is the definition of a situation
during which some (usually implicit) invariant condition holds.
Properties:
Parts:
a reference to a class held externally to the exchange file
that classifies this StateDefinition This StateDefinition is a
member of the referenced class.
References:
a reference to an
ExternalOwlClass or an
ExternalItem held externally to the exchange file that provides the
definition of the
StateDefinition.
Constraints:
Constraint: UR1Specification: (OCL2.0)
StateDefinition::allInstances()->isUnique(definition)
Definition:
An
StateDefinitionAssignment is a mechanism that enables an instance to have or to be in a
StateDefinition.
Properties:
References:
the instance whose
StateDefinition is given by the
describedStateDefinition.
Definition:
A
StateDefinitionRelationship is an association between two or more instances of
StateDefinition.
NOTE
Relationships between
StateDefinition entities may be
used to support fault diagnosis.
Properties:
Parts:
References:
one of the instances of
StateDefinition that is a part of the
relationship.
the other of the instances of
StateDefinition that is a part of the
relationship.
All Supertype Blocks:
State OWL Definition:
A StateObserved is a
state that something has been observed to be in.
Sources:
ISO 10303-239ed2 transformed to AP239AP233 PSM
Definition:
A
StateObserved is a specialization of
State. It is an individual or
realized
State that is observed.
All Supertype Blocks:
State OWL Definition:
A StatePredicted is a
state that something has been predicted to be in.
Sources:
ISO 10303-239ed2 transformed to AP239AP233 PSM
Definition:
A
StatePredicted is a specialization of
State It is a predicted actual
State. Where a predicted state needs to be related to an observed state, the
StatePredictedToObserved entity shall be used.
Definition:
A
StatePredictedToObserved is a specialization of state relationship. It specifies the relationship between
two
individual states, one of which is a
StatePredicted to a second state which is a
StateObserved.
Properties:
References:
Definition:
A
StateProperSubsetDefinition is a specialization of
StateDefinitionRelationship. It is a relationship between two sets of
StateDefinition entities.
NOTE
The relationship between a state and its environment can be described as a
StateProperSubsetDefinition. The identification of an intrinsic state is the properSubset. The identification of an
extrinsic state is the properSuperset.
Definition:
A
StateRelationship is a relationship between two or more
State.
Properties:
Parts:
References:
one of the set of instances of
State that is a part of the
relationship.
the other of the set of instances of
State that is a part of the
relationship.
Definition:
A
StateSubsetDefinition is a specialization of
StateDefinitionRelationship. It is a relationship between two sets of
StateDefinition entities.
NOTE
The first set may be equal to the second set.
Definition:
A
StateSymptomDefinition is a specialization of
StateDefinitionRelationship. It relates two or more
StateDefinition entities in
regards to symptom, where a symptom is something that indicates the existence of something
else. At least one
StateDefinition acts as a
symptomCause and at least one
StateDefinition acts as a
symptomEffect.
Definition:
A
StateTransition is a specialization of state relationship and it relates two or more states before
and after a
transition in
State, where at least one
State is
a start state and at least one
State is an end state.
Definition:
A
StateTransitionDefinition is a specialization of
StateDefinitionRelationship. It relates two or more
StateDefinition entities
before and after a transition in state, where at least one
StateDefinition is a
startState and at least one
StateDefinition is an
endState.
Definition:
A
StringValue is a specialization of
PropertyValue
that represents a sequence of one or more alphanumeric characters.
Properties:
Parts:
specifies the string represented by the StringValue.
Definition:
A
StructuredTaskElement is a type of
TaskElement. It is made up of
other
TaskElements
Definition:
ASubsetMember is a relationship that is between:
that indicates:
- each member of set A is also a member of set B.
NOTE
Set A may be equal to set B.
Properties:
References:
the set that contains all members of subset.
the set that contains only members of superset.
Definition:
A
SuppliedPartRelationship is a specialization of
ProductVersionRelationship that relates two instances of
ProductVersion that
represent the same instance in different organizational contexts.
One of the organizations is the supplier of the instance to the other
organization.
This entity is applicable for part versions and document versions.
NOTE 1
This entity enables to represent the fact that two organizations may use distinct
identifiers to identify their
Product and their versions.
NOTE 2
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.
Definition:
A
System is a specialization of
Product used to identify a conceptual
solution to a collection of requirements.
NOTE 1
The concept system is any thing - matter, energy, organisation or information
or a combination of these - for which reproducible measurements exist. The concept
system excludes any asserted thing based on personal
experience for which no reproducible measurements exist.
NOTE 2
SEDRES Definition: "An assembly of interacting, active components or elements forming
a whole".
NOTE 3
Another definition would be "That which is discernible by reproducible measurement
of its characteristics, and has a
defined boundary (statically and dynamically) with respect to the universe".
Properties:
Parts:
the versions of the System.
OWL Definition:
A SystemBreakdown is a
breakdown comprising system elements.
The parent-child view is represented by SystemElementUsage instances
relating the system elements in the breakdown which are represented by SystemElements.
EXAMPLE 1:
A
system breakdown provides a decomposition of an aircraft in terms of high-level
Systems such as "fuel system" or "flight control system" - which might, in the second example,
further decompose into low-level systems such as "autopilot system" and "instrument
landing system".
NOTE 1:
The
system breakdown is a partitioning of a
product into a set of related
system elements so as to form explicit, parent-child views.
Sources:
ISO 10303-239ed2 transformed to AP239AP233 PSM
Definition:
A
SystemBreakdown is a specialization 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 SystemElementUsage instances
relating the system elements in the breakdown which are represented by SystemElements.
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.
Properties:
Parts:
the versions of the SystemBreakdown.
Definition:
A
SystemBreakdownContext is a specialization of
BreakdownContext that
is a membership relationship between a
SystemElement and a
SystemBreakdown of which the system element is a member.
EXAMPLE
A heating system is a member of the breakdown of a climate
control system.
Properties:
References:
Definition:
A SystemBreakdownVersion is a specialization of BreakdownVersion that
identifies a version of a SystemBreakdown
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.
Properties:
References:
OWL Definition:
A SystemElement is a
breakdown element that represents a System.
Sources:
ISO 10303-239ed2 transformed to AP239AP233 PSM
Definition:
A
SystemElement is a specialization of
BreakdownElement that
identifies the elements in one or more
SystemBreakdown instances.
Properties:
Parts:
the versions of the SystemElement.
Definition:
A
SystemElementDefinition is a specialization of
BreakdownElementDefinition that identifies a view of a version (
SystemElementVersion) of a
SystemElement.
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.
Properties:
References:
Definition:
A
SystemElementUsage is a specialization of
BreakdownElementUsage that
is a relationship between a
SystemElementDefinition and another
SystemElementDefinition 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.
Properties:
References:
Definition:
A
SystemElementVersion is a specialization of
BreakdownElementVersion
that identifies a version of a
SystemElement
EXAMPLE
A sound engineer changes the details
describing the public address system that is an element in a system breakdown of an
aircraft.
Properties:
Parts:
References:
Definition:
A
SystemVersion is a specialization of
ProductVersion that represents
a particular version of a system.
NOTE
In this case, this means "revision". So for a given system (e.g. a fuel injection
system) we may
have several versions of the system design (e.g. v1, v1.1 etc.)
Properties:
Parts:
References:
the
System that
the
SystemVersion is a version of.
Definition:
A
SystemVersionRelationship is a specialization of
ProductVersionRelationship used to relate versions of a system.
Properties:
References:
the first instance of
SystemVersion that is a part of the
relationship.
the second instance of SystemVersion that is a part of the
relationship.
NOTE
If one
SystemVersion in the relationship is dependent
upon the other, this attribute shall be the dependent one.
Definition:
A
SystemVersionSequence is a specialization of
SystemVersionRelationship used to relate a previous version of a system to the version that replaces it.
Definition:
A
SystemViewDefinition is a specialization of
ProductViewDefinition
that provides a view of a system version relevant for one or more application domains.
Properties:
References:
the
SystemVersion of which the
SystemViewDefinition provides a characterization.
Definition:
A
TaskElement is a specialization of
ActivityMethod. It is a
representation of all or part of how to undertake a task.
Definition:
A TaskElementAssignment
is a specialization of an AssignmentObject
that represents the assignment of
TaskElement instances to instances
that are specializations of TaskAssignmentSelect.
Properties:
References:
Definition:
A
TaskElementLevels is a type of
TaskElement that provides two or more
different descriptions in place of a single method. The actual work will be the same
whichever alternative
TaskElement is followed.
NOTE
This can be used to provide different levels of description of a task
for people with varying levels of experience or expertise.
Properties:
Parts:
the
TaskElements describing two or more ways in which the same work
may be undertaken.
Definition:
A
TaskElementRelationship is a specialization of
ActivityMethodRelationship. It relates two instances of
TaskElement.
EXAMPLE
Can be used to capture a time dependency that cuts across the structure of the method.
Properties:
References:
one instance of
TaskElement that is a part of the relationship.
the other instance of
TaskElement that is a part of the
relationship. If one element of the relationship is dependent upon the other, this
attribute shall be the dependent one.
Definition:
A
TaskElementSequence is a specialization of
TaskElement that
comprises a sequence of steps to be followed in a specified order.
Properties:
Parts:
the
TaskElements to be followed in the order specified in the list.
Definition:
A
TaskElementStateRelationship is an type of
ActivityMethodRelationship. It is an association between a
State or a
StateDefinition and a
TaskElement. The meaning of the entity is determined by
classification. Candidate meanings include:
- assumed starting state;
- required starting state.
Properties:
Parts:
References:
Definition:
A
TaskInvocation is a type of
TaskElement. It is an instruction to
perform another task.
EXAMPLE
A
TaskElement calls a predefined task to perform an
instrument calibration.
Properties:
References:
Definition:
A
TaskMethod is a specialization of
ActivityMethod. It is a
specification of work.
NOTE
The task method may be implemented using people, machines or a combination.
Properties:
Parts:
the versions of the TaskMethod.
References:
the intended result or results of the task.
Definition:
A TaskMethodAssignment
is a specialization of an AssignmentObject
that represents the assignment of
TaskMethod instances to instances
that are specializations of TaskAssignmentSelect.
Properties:
References:
the set of things that are associated to the
TaskMethod.
Definition:
A TaskMethodRelationship is a specialization of ActivityMethodRelationship. It relates two task methods.
Properties:
References:
one of the instances of
TaskMethod that is a part of the
relationship.
the other instance of
TaskMethod that is a part of the
relationship. If one element of the relationship is dependent upon the other, this
attribute shall be the dependent one.
Definition:
A TaskMethodStateRelationship is a relationship between a state and a TaskMethod.
NOTE
The meaning of the entity is determined by classification. Candidate meanings include:
- Assumed starting state;
- Required starting state.
Properties:
Parts:
References:
the mode of being that is related.
Definition:
A
TaskMethodVersion is a specialization of
ActivityMethod which allows
the explicit reference to versions of a
TaskMethodand to track changes against a
TaskMethod.
Properties:
Parts:
the way in which the task is to be carried out. The value of this attribute need
not be specified.
References:
Definition:
A TaskMethodVersionAssignment
is a specialization of an AssignmentObject
that represents the assignment of
TaskMethodVersion instances to instances
that are specializations of TaskAssignmentSelect.
Properties:
References:
Definition:
A
TaskMethodVersionRelationship is a specialization of
ActivityMethodRelationship. It relates two instances of
TaskMethodVersion.
Properties:
References:
Definition:
A
TaskObjective is a result or objective that is reached by undertaking a
TaskMethod.
NOTE
More than one
TaskMethod may be defined for a given objective,
if there can be several ways to accomplish the objective.
Properties:
Parts:
a reference to a class held externally to the exchange file
that classifies this TaskObjective This TaskObjective is a member
of the referenced class.
Definition:
A
TaskObjectiveStateRelationship is a relationship between a state and a
TaskObjective.
NOTE
The meaning of the entity is determined by classification. Candidate meanings include:
- Intended finishing state;
- Alternative finishing state.
Properties:
Parts:
References:
the mode of being that is related.
Definition:
A
TaskStep is a specialization of
TaskElement that is not further
sub-divided.
Properties:
Parts:
the text describing what is to be done to accomplish the TaskStep
Definition:
A TimeInterval is the identification of an intervening time.
Properties:
Parts:
Definition:
A
TimeIntervalAssignment is an association of a
TimeInterval with
product data.
Properties:
References:
the instance of the
TimeInterval entity data type that is
associated with product data.
Definition:
A
TimeIntervalEffectivity is a specialization of
Effectivity for which
the domain of applicability is defined as a
TimeInterval.
Properties:
References:
Definition:
A
TimeIntervalRelationship is the association of two instances of
TimeInterval. The meaning of this association is specified in the
RelationType attribute.
Properties:
References:
the first instance of
TimeInterval that is part of the
relationship.
the other instance of
TimeInterval. If one element of the
relationship is dependent upon the other, this attribute shall be the dependent one.
Definition:
A TimeIntervalWithBounds is a specialization of TimeInterval. A
TimeIntervalWithBounds is bounded either on one side or both sides.
If neither secondaryBound nor NumericalValue by the durationFromPrimaryBound
are specified, the time interval begins at the point in time identified by
primaryBound and has no specified end point.
Properties:
Parts:
the duration that specifies the length of the time interval from the primary bound.
If positive, the TimeIntervalWithBounds defines a lower bounded time interval,
else an upper bounded time interval.
The value of this attribute need not be specified.
References:
the bound of the TimeIntervalWithBounds
from which the length of the time interval is measured. The value
of this attribute need not be specified.
the other bound of the TimeIntervalWithBounds. The
value of this attribute need not be specified.
Definition:
A TracingRelationship is a specialization of ViewDefinitionRelationship that shows
tracing from ( TracesFrom) one requirement to another (
TracesTo).
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 2
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.
Definition:
A
TypeOfPerson is a type of person.
EXAMPLE 1
Class 3 welder
EXAMPLE 2
Truck driver
EXAMPLE 3
Electronics engineer
EXAMPLE 4
Mechanical technician
EXAMPLE 5
Helicopter pilot
Properties:
Parts:
References:
the same TypeOfPerson can be described by many different definitions.
EXAMPLE
has a degree or has 3 years experience
Definition:
A
TypeOfPersonAssignment is the association of a
TypeOfPerson in a
role with an activity or product data.
Properties:
References:
Definition:
A
TypeOfPersonDefinition is the definition of a
TypeOfPerson 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.
Properties:
Parts:
a reference to a class held externally to the exchange file
that classifies this TypeOfPersonDefinition This
TypeOfPersonDefinition is a member of the referenced
class.
Definition:
A TypeOfPersonDefinitionRelationship is a relationship between two definitions of a type of person (TypeOfPersonDefinition).
A TypeOfPersonDefinitionRelationship is a specialization of a
RelationshipObject that is a relationship between
two instances of a type of person
(TypeOfPersonDefinition).
EXAMPLE
"alternate" and "superceded by" are examples of
TypeOfPersonDefinitionRelationships.
Properties:
References:
the other instance of
TypeOfPersonDefinition that is a part of the
relationship. If one element of the relationship is dependent upon the other, this
attribute shall be the dependent one.
Definition:
A
TypeOfPersonDefinitionRequiredAttributesRelationship is a relationship between a
TypeOfPersonDefinition 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".
Properties:
References:
the required attributes of a person.
EXAMPLE 1
Must have a degree
EXAMPLE 2
Must have 10 years experience
Definition:
An
UncertaintyQualifier is a generalization of a
StandardUncertainty
or a
QualitativeUncertainty. The uncertainty is defined in clause 2 of "The Guide to the
Expression of Uncertainty in Measurement".
Properties:
Parts:
specifies the STRING that serves to identify the UncertaintyQualifier.
Definition:
A
Validation is a subjective assertion that an item is "fit for purpose". Evidence used in this
validation is
identified by the inverse attribute
validatedBy. Validation is commonly understood to mean "Have we built the right system?".
Validation is concerned with ensuring that the system will meet the customer’s objectives
and expectations. Validation usually includes
testing under normal usage conditions.
NOTE
An item may pass validation even though some requirements fail verification.
NOTE
It is assumed that meta data supporting the validation will be applied using assignment
entities, such as identification assignment,
person and organization assignment etc..
EXAMPLE
Every flight of every Space Shuttle has been a "Validation" flight to test the new
design under actual conditions. No two
shuttles have flown in the same configuration and many systems cannot be validated
except under actual conditions.
Properties:
Parts:
a set of text based descriptions of the
Validation.
a reference to a class held externally to the exchange file
that classifies this Validation This Validation is a member of the
referenced class.
References:
identifies the item which is been validated by this entity.
the collection of evidence used in this validation.
Definition:
A ValueFunction is a numerically defined function that describes the distribution function.
Properties:
References:
a single random variable/function value point on the function.
Definition:
A
ValueLimit is a specialization of
NumericalValue that
specifies a qualified numerical value representing either the lower limit or the upper
limit of a particular quantifiable characteristic.
Properties:
References:
There shall exist exactly one
PreDefinedTypeQualifier for the
ValueLimit. It shall be classified as 'minimum' or 'maximum'.
Definition:
A
ValueList is a specialization of
PropertyValue that is an ordered
collection of
PropertyValues.
EXAMPLE
A
PropertyValue may be composed of different values such as 'mass', 'speed', and 'age' which are
all necessary in a given
context. The
ValueList collects all of them in a given order, such that each is
identifiable by its index in the list.
Properties:
Parts:
the values.
Definition:
A
ValueRange is a specialization of
ValueWithUnit that is a pair of
numbers representing the range in which the value shall lie.
Properties:
Values:
the lower limit.
the upper limit.
Definition:
A
ValueSet is a specialization of
PropertyValue that is an unordered
collection of
PropertyValues.
EXAMPLE
A
PropertyValue may be composed of different values such as 'mass', 'speed', and 'age' which are
all necessary in a given
context. The
ValueSet collects all of them in a given order, such that each is
identifiable by its index in the list.
Properties:
Parts:
the values.
Definition:
A
ValueWithTolerances is a specialization of
ValueWithUnit 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].
Properties:
Values:
specifies the single value that is the base value for specifying the range.
the lower limit of the range.
the upper limit of the range.
OWL Definition:
A ValueWithUnit is a
property value specified as a value and unit.
Sources:
ISO 10303-239ed2 transformed to AP239AP233 PSM
Definition:
A ValueWithUnit is a specialization of a PropertyValue and is an abstract
generalization of instances that represents the specification of a physical quantity
by its value and its unit.
NOTE
Only non-abstract specializations of the ValueWithUnit can be
instantiated.
Properties:
References:
the
ExternalUnit with which the physical quantity is expressed.
Values:
specifies the number of decimal digits that are relevant for the ValueWithUnit.
If present, the numerical measure or range may be specified using more digits than
the significant digits
but shall not be specified using less digits.
The value of this attribute need not be specified.
Definition:
A
Verification is an objective assertion of a claim that requirement is satisfied by a particular
item represented
in a
RequirementSatisfiedBy has been verified. The evidence used in this verification is
identified by the inverse attribute
verifiedBy. Verification is commonly understood to mean "Have we built the system right?".
Verification ensures that the specified requirements have been met. Verification uses
the methods of Test, Analysis, Inspection,
Demonstration, Similarity.
NOTE
Just because an item is verified does not ensure that it meets all stakeholder needs
or expectations,
many of these are never specified are of an un-testable nature e.g. "the car should
look sporty".
NOTE
It is assumed that meta data supporting the verification will be applied using assignment
entities, such as identification
assignment, person and organization assignment etc..
EXAMPLE
A data type used to represent a vehicle's engine with a power output of 160BHP could
be asserted to satisfy a requirement "the
vehicle shall have a maximum power output of at least 150BHP". This assertion may
be verified by analysis results on simulations of the
engine. In this case the analysis results would be identified in the items collection
of an evidence instance, possibly including the
approval of the analysis. The evidence instance would identify that it is used to
support the required verification.
Properties:
Parts:
a reference to a class held externally to the exchange file
that classifies this Verification This Verification is a member of
the referenced class.
References:
the claimed requirement satisfaction by a particular item which is been verified
by this entity.
the collection of evidence used in this verification.
Definition:
A VerificationRelationship is an association between two verifications.
Properties:
References:
the first verification in this relationship.
the other verification in this relationship.
Definition:
An ViewDefinitionContext 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.
Properties:
Parts:
a set of text based descriptions of the ViewDefinitionContext.
References:
the text that identifies the application context that bounds the universe of discourse.
EXAMPLE 1
'assembly study', 'digital mock-up', 'electrical design', 'mechanical design', 'preliminary
design', 'process
planning' are examples of application domains
If applicationDomain is an empty string, the ViewDefinitionContext shall be considered as not specific of any
application domain.
the text that identifies a stage in the life cycle of a product.
EXAMPLE 2
'design phase', 'production', 'recycling phase' are examples of life cycle stages.
If lifeCycleStage is an empty string, the ViewDefinitionContext shall be considered as not specific of any life
cycle stage.
Constraints:
Constraint: UR1Specification: (OCL2.0)
ViewDefinitionContext::allInstances()->isUnique(Sequence{applicationDomain, lifeCycleStage})
Definition:
A
ViewDefinitionRelationship is an association between two instances of
ProductViewDefinition.
This association represents a relationship between the product versions, indirectly
identified by
the instances of ProductViewDefinition, relevant in the definition contexts of the related
instances of ProductViewDefinition.
Properties:
Parts:
References:
the other instance of
ProductViewDefinition that is part of the
relationship. If one element of the relationship is dependent upon the other, this
attribute shall be the dependent one.
Definition:
A
ViewDefinitionUsage is a specialization of
ViewDefinitionRelationship that specifies a directed association between two instances of
ProductViewDefinition.
This association represents a relationship stating that, in the definition contexts
of the related instances of ProductViewDefinition, it is considered that the related product is used in the context of the
relating product.
Definition:
A WorkOrder is an authoritative instrument which provides directions to achieve the specified
results.
A WorkOrder is the authorization for one or more Activity instances to be
performed.
Properties:
Parts:
a set of text based descriptions of the
WorkOrder.
a reference to a class held externally to the exchange file
that classifies this WorkOrder This WorkOrder is a member of the
referenced class.
References:
the set of zero, one or more instances of
WorkRequest that defines
the expected results.
Definition:
An
WorkOrderAssignment is an association of a
WorkOrder with the
product or activity data that are subjects of this
WorkOrder.
EXAMPLE
In case a tyre on a
car is flat, a
WorkOrder may be created and associated with the instances that represent
the tyre that is flat, the car and the spare wheel.
Properties:
References:
the
WorkOrder for which a set of items is being identified.
the set of things that are affected by the
WorkOrder.
Definition:
A
WorkOutput is a statement of output resulting from an activity or a task. The role of the work
output is
determined by classification.
EXAMPLE 1
When applicable a work output may be classified as
- "Planned";
- "Actual";
- "By-product";
- "Waste product".
Properties:
Parts:
a set of text based descriptions of the
WorkOutput.
a reference to a class held externally to the exchange file
that classifies this WorkOutput This WorkOutput is a member of the
referenced class.
the amount of output resulting from the associated activity or task. The value of
this attribute need not be
specified.
References:
a reference to a detailed representation of the item that is defined as the work
output. It can refer to an actual as well as to
a type of item. The value of this attribute need not be specified.
EXAMPLE 2
A work output can be a product or a certificate.
Definition:
A WorkOutputAssignment is an association of a work output statement with the source that produces or delivers
the
output. The work output can be planned as well as actual. The role of the assignment
is determined by classification.
Properties:
References:
the work output that is to be associated with one or more activities or tasks that
produce or deliver the
output.
the source that produces or delivers the work output.
Definition:
A
WorkOutputRelationship is a relationship between two work output statements. The meaning of the relationship
is
determined by classification.
EXAMPLE
A WorkOutputRelationship is classified as "realized by"
.
Properties:
References:
one of the instances of
WorkOutput that is a part of the
relationship.
the other instance of
WorkOutput that is a part of the
relationship. If one element of the relationship is dependent upon the other, this
attribute shall be the dependent one.
Definition:
A
WorkRequest 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
WorkOrder.
Properties:
Parts:
a reference to a class held externally to the exchange file
that classifies this WorkRequest This WorkRequest is a member of
the referenced class.
Definition:
An
WorkRequestAssignment is an association of a
WorkRequest with the
product or activity data that are subjects of this
WorkRequest.
EXAMPLE
In case a tyre on a
car is flat, a
WorkRequest may be created and associated with the instances that represent
the tyre that is flat, the car and the spare wheel.
Properties:
References:
the
WorkRequest for which a set of items is being identified.
the set of things that are affected by the
WorkRequest.
Definition:
AWorkRequestRelationship is a specialization of an RelationshipObject that is a relationship between
two instances of WorkRequest.
Properties:
References:
the first of the instances of WorkRequest that is part of the relationship.
the second instance of WorkRequest that is part of the relationship
.
NOTE
NOTE
If one
WorkRequest in the relationship is dependent upon the other, this
attribute shall be the dependent one.
Definition:
An
XorStateCauseEffectDefinition is a specialization of
StateCauseEffectDefinition. It relates one of the single or many causing state definition(s) and one effect
StateDefinition, whereby any and only one of the causing state definitions exists prior to the single
effect to take place.
OWL Definition:
A ZoneBreakdown is a
breakdown comprising zone elements.
The parent-child view is represented by ZoneElementUsage instances relating the zonal elements in the breakdown
which are represented by ZoneElements.
EXAMPLE 1:
A zonal breakdown provides a decomposition of an aircraft in terms of spaces or high-level conceptual
parts such as 'wing' - which might further decompose into lower-level zones such as
'inner-wing', and 'outer wing'.
NOTE 1:
The
zonal breakdown is a partitioning of a product into a set of related
zone elements so as to form explicit, parent-child views.
Sources:
ISO 10303-239ed2 transformed to AP239AP233 PSM
Definition:
A
ZoneBreakdown is a specialization 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 ZoneElementUsage instances relating the
zonal elements in the breakdown which are represented by ZoneElements.
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'.
Properties:
Parts:
the versions of the ZoneBreakdown.
Definition:
A
ZoneBreakdownContext is a specialization of
BreakdownContext that is
a membership relationship between a
ZoneElement and a
ZoneBreakdown of which the zonal element is a member.
EXAMPLE
A 'fire-check zone' might be a member of the zonal breakdown
of a building.
Properties:
References:
Definition:
A
ZoneBreakdownVersion is a specialization of
BreakdownVersion that
identifies a version of a
ZoneBreakdown
EXAMPLE
An architect modifies the current
fire-check zone breakdown for an building on the basis of reports from a buildings
inspector.
Properties:
References:
OWL Definition:
A ZoneElement is a
breakdown element that represents a 3 dimensional space.
EXAMPLE 1:
'Empennage', 'Right vertical stabilizer and rudder' and 'Lower rudder' are all elements
in a zonal breakdown of an aircraft.
Sources:
ISO 10303-239ed2 transformed to AP239AP233 PSM
Definition:
A
ZoneElement is a specialization of
BreakdownElement that identifies
the elements in one or more
ZoneBreakdown instances.
EXAMPLE
'Empennage', 'Right vertical
stabilizer and rudder' and 'Lower rudder' are all elements in a zonal breakdown of
an aircraft.
Properties:
Parts:
the versions of the ZoneElement.
Definition:
A
ZoneElementDefinition is a specialization of
BreakdownElementDefinition that identifies a view of a version (
ZoneElementVersion) of a
ZoneElement.
EXAMPLE
For an aircraft, an element
'Right vertical stabilizer tip' is in a zonal breakdown that an engineer uses for
reliability-centred maintenance analysis.
Properties:
References:
Definition:
A
ZoneElementUsage is a specialization of
BreakdownElementUsage that
is a relationship between a parent and child
ZoneElement.
EXAMPLE
In a zonal breakdown, the
'wing' (parent) might include (as children) an 'inner wing' and an 'outer wing'.
Properties:
References:
the first instance of
ZoneElement that is a part of the
relationship.
the second instance of ZoneElement that is a part of the relationship.
NOTE
If one
ZoneElement in
the relationship is dependent upon the other, this attribute shall be the
dependent one.
Definition:
A
ZoneElementVersion is a specialization of
BreakdownElementVersion
that identifies a version of a
ZoneElement.
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.
Properties:
Parts:
References:
the
ZoneElement that the
ZoneElementVersion is a version of.
Definition:
An
ActivityAssignmentSelect is an abstract generalization of instances to which instances of
Activity and
WorkOrder can be assigned by the
ActivityAssignment.assignedTo and
WorkOrderAssignment.assignedTo attributes respectively.
Definition:
An ActivityMethodRealizationSelect is an abstract generalization of instances.
Definition:
An
AnalysisAssignmentSelect is an abstract generalization of instances to which instances of
AnalysisAssignmentSelect can be assigned by the
AnalysisAssignment.assignedTo attribute.
Definition:
An AnalysisModelItemsSelect is an abstract generalization of instances.
Definition:
An
ActivityMethodAssignmentSelect is an abstract generalization of instances to which instances of
ActivityMethodAssignmentSelect can be assigned by the
ActivityMethodAssignment.assignedTo attribute.
Definition:
An
ApprovalAssignmentSelect is an abstract generalization of instances to which instances of
ApprovalAssignmentSelect can be assigned by the
ApprovalAssignment.assignedTo attribute.
Definition:
An AssignedDocumentSelect is an abstract generalization of instances.
Definition:
An AssumedItemSelect is an abstract generalization of instances.
Definition:
An
AssumptionAssignmentSelect is an abstract generalization of instances to which instances of
AssumptionAssignmentSelect can be assigned by the
AssumptionAssignment.assignedTo attribute.
Definition:
A BreakdownOfSelect is an abstract generalization of instances.
Definition:
A BreakdownSelect is an abstract generalization of instances.
Definition:
A CartesianTransformationSelect is an abstract generalization of instances.
Definition:
A
CertificationAssignmentSelect is an abstract generalization of instances to which instances of
CertificationAssignmentSelect can be assigned by the
CertificationAssignment.assignedTo attribute.
Definition:
A ChainedGeometricModelLinkSelect is an abstract generalization of instances.
Definition:
A ClassSelect is an abstract generalization of instances.
Definition:
A
CollectionAssignmentSelect is an abstract generalization of instances to which instances of
CollectionAssignmentSelect can be assigned by the
CollectionAssignment.assignedTo attribute.
Definition:
A CollectionMemberSelect is an abstract generalization of instances.
Definition:
A
ConditionEvaluationAssignmentSelect is an abstract generalization of instances to which instances of
ConditionEvaluationAssignmentSelect can be assigned by the
ConditionEvaluationAssignment.assignedTo attribute.
Definition:
A ConditionEvaluationParameterSelect is an abstract generalization of instances that represents
parameters used by a ConditionEvaluation.
NOTE
Only non-abstract specializations of the ConditionEvaluationParameterSelect can be instantiated.
Definition:
A
ConditionAssignmentSelect is an abstract generalization of instances to which instances of
ConditionAssignmentSelect can be assigned by the
ConditionAssignment.assignedTo attribute.
Definition:
A ConditionParameterSelect is an abstract generalization of instances that
represents parameters used by a Condition.
NOTE
Only non-abstract specializations of the ConditionParameterSelect can be instantiated.
Definition:
A ConnectionSelect is an abstract generalization of instances.
Definition:
A ConnectorOnSelect is an abstract generalization of instances.
Definition:
A ConstraintContextSelect is an abstract generalization of instances.
Definition:
A
ContractAssignmentSelect is an abstract generalization of instances to which instances of
ContractAssignmentSelect can be assigned by the
ContractAssignment.assignedTo attribute.
Definition:
A
DateTimeAssignmentSelect is an abstract generalization of instances to which instances of
DateTimeAssignmentSelect can be assigned by the
DateTimeAssignment.assignedTo attribute.
Definition:
A DateOrEventSelect is an abstract generalization of instances that represents
a date or event.
NOTE
Only non-abstract specializations of the DateOrEventSelect can be instantiated.
Definition:
A DefinedActivitiesSelect is an abstract generalization of instances.
Definition:
A DefinedAttributesSelect is an abstract generalization of instances.
Definition:
A DefinedMethodsSelect is an abstract generalization of instances.
Definition:
A
DocumentAssignmentSelect is an abstract generalization of instances to which instances of
DocumentAssignmentSelect can be assigned by the
DocumentAssignment.assignedTo attribute.
Definition:
An
EffectivityAssignmentSelect is an abstract generalization of instances to which instances of
EffectivityAssignmentSelect can be assigned by the
EffectivityAssignment.assignedTo attribute.
Definition:
An
EnvironmentAssignmentSelect is an abstract generalization of instances to which instances of
EnvironmentAssignmentSelect can be assigned by the
EnvironmentAssignment.assignedTo attribute.
Definition:
An EvidenceSelect is an abstract generalization of instances.
Definition:
An EvidenceSupportSelect is an abstract generalization of instances.
Definition:
An ExternalSourceSelect is an abstract generalization of instances.
Definition:
A GeometricItemSpecificUsageSelect is an abstract generalization of instances.
Definition:
An IdentificationContextSelect is an abstract generalization of instances.
Definition:
An
InformationUsageRightAssignmentSelect is an abstract generalization of instances to which instances of
InformationUsageRightAssignmentSelect can be assigned by the
InformationUsageRightAssignment.assignedTo attribute.
Definition:
An InterfaceDefinitionForSelect is an abstract generalization of instances.
Definition:
An InZoneSelect is an abstract generalization of instances.
Definition:
An ItemUsageRelationshipSelect is an abstract generalization of instances.
Definition:
A
JustificationAssignmentSelect is an abstract generalization of instances to which instances of
JustificationAssignmentSelect can be assigned by the
JustificationAssignment.assignedTo attribute.
Definition:
A
JustificationSupportAssignmentSelect is an abstract generalization of instances to which instances of
JustificationSupportAssignmentSelect can be assigned by the
JustificationSupportAssignment.assignedSupportItem attribute.
Definition:
A
LocationAssignmentSelect is an abstract generalization of instances to which instances of
LocationAssignmentSelect can be assigned by the
LocationAssignment.assignedTo attribute.
Definition:
A MessageContentSelect is an abstract generalization of instances.
Definition:
A MessageDefinerSelect is an abstract generalization of instances.
Definition:
A MethodOrMethodVersionSelect is an abstract generalization of instances.
Definition:
An ObservationConsequenceSelect is an abstract generalization of instances.
Definition:
An
ObservationAssignmentSelect is an abstract generalization of instances to which instances of
ObservationAssignmentSelect can be assigned by the
ObservationAssignment.assignedTo attribute.
Definition:
An ObservedContextSelect is an abstract generalization of instances.
Definition:
An
ObservedEnvironmentAssignmentSelect is an abstract generalization of instances to which instances of
ObservedEnvironmentAssignmentSelect can be assigned by the
ObservedEnvironmentAssignment.assignedTo attribute.
Definition:
An
OrganizationOrPersonInOrganizationAssignmentSelect is an abstract generalization of instances to which instances of
OrganizationOrPersonInOrganizationAssignmentSelect can be assigned by the
OrganizationOrPersonInOrganizationAssignment.assignedTo attribute.
Definition:
An OrganizationOrPersonInOrganizationSelect is an abstract generalization of instances.
Definition:
A PersonOrOrganizationOrPersonInOrganizationSelect is an abstract generalization of instances.
Definition:
A PositionContextSelect is an abstract generalization of instances.
Definition:
A
PositionGroupAssignmentSelect is an abstract generalization of instances to which instances of
PositionGroupAssignmentSelect can be assigned by the
PositionGroupAssignment.assignedTo attribute.
Definition:
A
PositionAssignmentSelect is an abstract generalization of instances to which instances of
PositionAssignmentSelect can be assigned by the
PositionAssignment.assignedTo attribute.
Definition:
A PositionPersonOrOrganizationOrPersonInOrganizationSelect is an abstract generalization of instances.
Definition:
A
PositionTypeAssignmentSelect is an abstract generalization of instances to which instances of
PositionTypeAssignmentSelect can be assigned by the
PositionTypeAssignment.assignedTo attribute.
Definition:
A ProductBasedLocationRepresentationSelect is an abstract generalization of instances.
Definition:
A ProductDesignViewOrConfigurationSelect is an abstract generalization of instances.
Definition:
A ProductSelect is an abstract generalization of instances.
Definition:
A ProductGroupMembershipSelect is an abstract generalization of instances.
Definition:
A ProductVersionOrConfigurationSelect is an abstract generalization of instances.
Definition:
A
ProjectAssignmentSelect is an abstract generalization of instances to which instances of
ProjectAssignmentSelect can be assigned by the
ProjectAssignment.assignedTo attribute.
Definition:
A
PropertyAssignmentSelect is an abstract generalization of instances to which instances of
ExternalPropertyDefinition and
PropertyValue can be assigned by the
PropertyDefinitionAssignment.assignedTo and
PropertyValueAssignment.assignedTo attributes respectively.
Definition:
A ProxyItemSelect is an abstract generalization of instances.
Definition:
A
QualificationAssignmentSelect is an abstract generalization of instances to which instances of
QualificationAssignmentSelect can be assigned by the
QualificationAssignment.assignedTo attribute.
Definition:
A
RequiredResourceAssignmentSelect is an abstract generalization of instances to which instances of
RequiredResourceAssignmentSelect can be assigned by the
RequiredResourceAssignment.assignedTo attribute.
Definition:
A
RequirementAssignmentSelect is an abstract generalization of instances to which instances of
RequirementAssignmentSelect can be assigned by the
RequirementAssignment.assignedTo and
RequirementSatisfiedBy.satisfiedBy attribute.
Definition:
A RequirementSourceSelect is an abstract generalization of instances.
Definition:
A
ResourceAsRealizedAssignmentSelect is an abstract generalization of instances to which instances of
ResourceAsRealizedAssignmentSelect can be assigned by the
ResourceAsRealizedAssignment.assignedTo attribute.
Definition:
A ResourceAsRealizedRelationshipSelect is an abstract generalization of instances.
Definition:
A
ResourceItemAssignmentSelect is an abstract generalization of instances to which instances of
ResourceItemAssignmentSelect can be assigned by the
ResourceItemAssignment.assignedTo attribute.
Definition:
A ResourceItemSelect is an abstract generalization of instances.
Definition:
A ResourceRealizationSelect is an abstract generalization of instances.
Definition:
A
RiskImpactAssignmentSelect is an abstract generalization of instances to which instances of
RiskImpactAssignmentSelect can be assigned by the
RiskImpactAssignment.assignedTo attribute.
Definition:
A
RiskPerceptionSourceAssignmentSelect is an abstract generalization of instances to which instances of
RiskPerceptionSourceAssignmentSelect can be assigned by the
RiskPerceptionSourceAssignment.assignedTo attribute.
Definition:
A
SchemeEntryAssignmentSelect is an abstract generalization of instances to which instances of
SchemeEntryAssignmentSelect can be assigned by the
SchemeEntryAssignment.assignedTo attribute.
Definition:
A
SchemeSubjectAssignmentSelect is an abstract generalization of instances to which instances of
SchemeSubjectAssignmentSelect can be assigned by the
SchemeSubjectAssignment.assignedTo attribute.
Definition:
A
SchemeVersionAssignmentSelect is an abstract generalization of instances to which instances of
SchemeVersionAssignmentSelect can be assigned by the
SchemeVersionAssignment.assignedTo attribute.
Definition:
A
SecurityClassificationAssignmentSelect is an abstract generalization of instances to which instances of
SecurityClassificationAssignmentSelect can be assigned by the
SecurityClassificationAssignment.assignedTo attribute.
Definition:
A SelectedItemContextSelect is an abstract generalization of instances.
Definition:
A
SelectedItemAssignmentSelect is an abstract generalization of instances to which instances of
SelectedItemAssignmentSelect can be assigned by the
SelectedItemAssignment.assignedTo attribute.
Definition:
A ShapeableItemSelect is an abstract generalization of instances.
Definition:
A ShapeDependentSelect is an abstract generalization of instances.
Definition:
A ShapeSelect is an abstract generalization of instances.
Definition:
A
StateAssignmentSelect is an abstract generalization of instances to which instances of
StateAssignmentSelect can be assigned by the
StateAssignment.assignedTo attribute.
Definition:
A
StateDefinitionAssignmentSelect is an abstract generalization of instances to which instances of
StateDefinitionAssignmentSelect can be assigned by the
StateDefinitionAssignment.assignedTo attribute.
Definition:
A StateOrStateDefinitionSelect is an abstract generalization of instances.
Definition:
A
TaskAssignmentSelect is an abstract generalization of instances to which instances of
TaskElement,
TaskMethod and
TaskMethodVersion can be assigned by the
TaskElementAssignment.assignedTo,
TaskMethodAssignment.assignedTo and
TaskMethodVersionAssignment.assignedTo attributes respectively.
Definition:
A
TimeIntervalAssignmentSelect is an abstract generalization of instances to which instances of
TimeIntervalAssignmentSelect can be assigned by the
TimeIntervalAssignment.assignedTo attribute.
Definition:
A
TypeOfPersonAssignmentSelect is an abstract generalization of instances to which instances of
TypeOfPersonAssignmentSelect can be assigned by the
TypeOfPersonAssignment.assignedTo attribute.
Definition:
A TypeQualifierSelect is an abstract generalization of instances.
Definition:
A ValidationSelect is an abstract generalization of instances.
Definition:
A ValueQualifierSelect is an abstract generalization of instances.
Definition:
A VersionOrDefinitionSelect is an abstract generalization of instances.
Definition:
A
WorkOutputAssignmentSelect is an abstract generalization of instances to which instances of
WorkOutputAssignmentSelect can be assigned by the
WorkOutputAssignment.assignedTo attribute.
Definition:
A WorkOutputSelect is an abstract generalization of instances.
Definition:
A
WorkRequestAssignmentSelect is an abstract generalization of instances to which instances of
WorkRequestAssignmentSelect can be assigned by the
WorkRequestAssignment.assignedTo attribute.