Definition:
An
Activity is the identification of the occurrence of an action that has taken place, is taking
place, or is expected to take place
in the
future.
The procedure executed during that
Activity is identified with the
Activity_method that is referred to by the
chosen_method attribute.
EXAMPLE
Change, distilling, design, a process to drill a hole, and a task such as training
someone, are examples
of activities.
NOTE 1
Status information identifying the level of completion
of each activity may be provided within an instance of
Activity_status.
NOTE 2
The items that are affected by an
Activity, for example as input or output, may be identified
within an instance of
Applied_activity_assignment.
Properties:
References:
the
Activity_method that specifies the approach selected to carry out the
Activity.
Values:
the identifier that distinguishes the Activity.
the words by which the Activity is known.
the text that provides further information about the Activity.
The value of the attribute need not be specified.
Definition:
An
Activity_actual is a type of
Activity.
It is a record of the occurrence of an
Activity. The
Activity_actual
is related through an
Activity_happening
to the
Activity for which it is an occurrence. The existence of an
Activity_actual
instance means that the
Activity_actual
has started.
NOTE 2
A
Calendar_date
or
Date_time
may be assigned to the activity with role "end date" to record when the activity finished.
In general, the absence of this
assignment cannot be used to infer that the activity is continuing, only that the
end of the activity has not yet been recorded.
NOTE 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.
Definition:
An
Activity_happening is a type of
Activity_relationship. It is a relationship between the definition of an activity (
predicted) and its actual occurrence (
actual).
NOTE 1
The ordinary value for
name may be "actual", though this is redundant.
EXAMPLE 1
a single defined activity is recorded historically by several sub-activities.
EXAMPLE 2
a single servicing activity takes the opportunity to make additional checks and repairs.
Properties:
References:
Definition:
An
Activity_method
is a way to carry out an
Activity.
NOTE 1
There may be more than one method for producing a required result
NOTE 2
This definition may be used to characterize a way to resolve a request for action.
The concept of action request is represented by
Work_request.
Properties:
Values:
the text that provides further information about the
Activity_method.
The value of this attribute need not be specified.
the text that describes the results of application of this method. The
value of this attribute need not be specified.
EXAMPLE
an
Activity_method
is a test that consists of several steps; each may have a positive or negative result.
the text that provides an informal description of the reason for the
Activity_method
.
Definition:
An
Activity_method_assignment is an association between an
Activity_method
and a
Work_request.
The
relation_type attribute characterizes the meaning of that association and the meaning of the
Activity_method
with respect to the
Work_request.
Properties:
References:
Values:
the text that identifies the nature of the relationship between the
Activity_method
and the
Work_request.
Where applicable, the following values shall be used:
-
'recommended method': the
Activity_method
is the recommended approach to accomplish the requested work;
-
'non recommended method': the
Activity_method
should not be used to accomplish the requested work.
Definition:
An
Activity_method_realization is a further specification of how an
activity method is to be performed with the
Activity_method.
NOTE 1
More than one specification can be associated with the same
Activity_method.
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:
References:
the item that realizes the
Activity_method.
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.
Values:
an identifier for the Activity_method_realization.
the word or group of words by which the realization is known.
the text that provides further information about the manner in which the
Activity_method
is realized by the item.
The value of this attribute need not be specified.
Definition:
An
Activity_method_realization_relationship
is a relationship between two
Activity_method_realization
entity instances.
NOTE
An
Activity_method_realization_relationship may be used to specify sequencing and other constraints
between different realizations for the same
Activity_method.
Properties:
References:
Values:
an identifier for the relationship.
the word or group of words by which the relationship is known.
the text that provides further information about the relationship.
The value of this attribute need not be specified.
Definition:
An
Activity_method_relationship is a relationship between two instances of
Activity_method.
Properties:
References:
the first instance of
Activity_method that is
part of the relationship.
NOTE 1
The relating_method usually identifies the
activity the definition of the related_method 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
Activity_method that is
part of the relationship.
NOTE 3
The
related_method usually identifies the
Activity_method,
which is based on the definition of the
relating_method.
Values:
the word or group of words by which the Activity_method_relationship is known.
the text that provides further information about the Activity_method_relationship.
The value of this attribute need not be specified.
Definition:
An
Activity_property is a property of an
Activity
or of an
Activity_method.
Properties:
References:
the object of which the Activity_property identifies a characteristic.
Values:
the words by which the Activity_property is known.
the text that provides further information about the Activity_property.
Definition:
An
Activity_property_representation is an association between an
Activity_property
and one of its representations.
Properties:
References:
Values:
the text that provides further information about the Activity_property_representation.
The value of this attribute need not be specified.
the string that specifies the meaning of the representation with
respect to the property.
EXAMPLE
'numerical representation' and 'text representation' are examples of role.
Definition:
An
Activity_relationship is a relationship between two instances of
Activity.
EXAMPLE
The activity required to complete a work order, may be decomposed into a series of
activities.
Their corresponding instances would be related using instances of the Activity_relationship entity.
Properties:
References:
the first of the instances of
Activity
that is part of the relationship.
NOTE 1
The relating_activity usually identifies the
activity the definition of the related_activity 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_activity usually identifies the
Activity,
which is based on the definition of the
relating_activity.
NOTE 4
The meaning of this attribute is defined by the name attribute.
Values:
the words by which the Activity_relationship is known.
the text that provides further information about the Activity_relationship.
The value of the attribute need not be specified.
Definition:
An
Activity_status is the assignment of a status to an
Activity
.
Properties:
References:
the
Activity
to which the
Activity_status applies.
Values:
the label that provides a user interpretable designation for the level of completion
of the
Activity.
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:
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.
Definition:
An
Address_assignment is the association of an
Organization
or a
Person_in_organization
with an
Address.
Properties:
References:
Values:
the string that specifies the type of the
Address.
The value of this attribute need not be specified.
EXAMPLE
'postal address' and 'visitor address' are examples of address types that may be
used to characterize addresses of an organization.
Definition:
An
Address_based_location_representation
is a type of
Location_representation specified by its postal identification.
Properties:
References:
the location where mail can be received.
Definition:
An Advisory_note is
the link between a task element with an advisory task step.
Properties:
References:
Definition:
An
Advisory_task_step is
a type of
Task_step. It conveys information.
NOTE
Some
Task_methods
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
Affected_items_assignment is an association of a
Work_request with
the product or activity data that are subjects of this
Work_request.
EXAMPLE
In case a tire on a car is flat, a
Work_request may be created and associated with the instances that represent the tire
that is flat, the car and the spare wheel.
Properties:
References:
the
Work_request for which a set of items is being identified.
Definition:
An
Alias_identification is a type of
Identification_assignment
that provides an alias identifier to product or activity data.
NOTE 3
Alias identification only applies to concepts that possesses an attribute that conveys
an identifier.
Properties:
References:
the inherited
items
attribute shall not contain any element that is not aliasable.
Definition:
An
Alternate_part_relationship is a type of
Alternate_product_relationship where the alternate and base products are parts.
Properties:
References:
the
Part that may replace in all its usages, the base part.
the
Part for which an alternate is specified.
Definition:
An
Alternate_product_relationship is an association between two instances of
Product.
It specifies that any version of the
alternate_product,
may be used in place of any version of the
base_product.
The relationship established by the Alternate_product_relationship 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
Alternate_product_relationship 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 Alternate_product_relationship for which the base_product is an assembly
involves that the entire product structure of the alternate_product may be used in place of the
base_product 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:
References:
the
Product
that may be used in place of the
base_product.
Values:
the words by which the Alternate_product_relationship is known.
The value of the attribute need not be specified.
the text that provides further information about the Alternate_product_relationship.
The value of the attribute need not be specified.
a text description that specifies the rationale and criteria used to assess the capability
of replacing the
base_product
by the
alternate_product.
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)
Alternate_product_relationship::allInstance()->isUnique(Sequence{alternate_product,
base_product})
All Supertype Blocks:
Unit
Definition:
An
Amount_of_substance_unit is a type of
Unit
in which the number of elementary entities of
a substance as compared to the number of atoms in 0.012 kilograms of carbon-12 is
expressed.
NOTE 1
This definition applies to the SI quantity 'mole'. When the mole is used, the elementary
entities, whose
quantity is expressed, must be specified . They may be atoms, molecules, ions, electrons
or other particles or
specified groups of such particles (see ISO 31-8).
NOTE 2
This unit corresponds to one of the seven fundamental quantities as specified in ISO
1000.
Definition:
An Analysis is a type 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.
Definition:
An Analysis_assignment is a relationship that relates a specific version of an analysis to the item being
analyzed.
Properties:
References:
the version of the analysis being related
the item being analyzed
Definition:
An
Analysis_design_version_relationship is a type of
Analysis_assignment
that is used when analysing a version of a product.
Properties:
References:
the product version that is the subject of the analysis.
Definition:
An Analysis_discipline_definition is a type of
Product_view_definition.
It is a definition or view of an
Analysis_version
taken from the perspective of the analysing organization. The
Analysis_discipline_definition
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.
Properties:
References:
Definition:
An
Analysis_model is a type of
Representation
used to support the description of analysis concepts.
Properties:
References:
Definition:
An
Analysis_representation_context is a type of
Representation_context
that defines the context for the
Representation_items used in an
Analysis_model.
Definition:
An Analysis_version is a type of
Product_version
that identifies a particular version of an analysis.
Properties:
References:
the Analysis_version identifies a version of.
Definition:
A
Analysis_version_relationship is a type of
Product_version_relationship that is used to assert an association between two versions of an analysis.
Properties:
References:
Definition:
A
Analysis_version_sequence is a type of
Analysis_version_relationship that is used to assert that the one analysis version (the successor) replaces another
(its predecessor).
Definition:
An
And_state_cause_effect_definition
is a type of
State_cause_effect_definition.
It relates one or more causing
State_definition entities
and one effect
State_definition. All the causing
State_definition entities must exist prior to
the single effect.
Definition:
An
Applied_activity_assignment is an association of an
Activity
with product or activity data. It characterizes the role of the concepts represented
with these data with respect to the
activity.
NOTE
This entity should not be used to represent the association of an activity with the
organizations that are responsible for
its execution or its management.
That kind of information can be represented with instances of
Organization_or_person_in_organization_assignment
.
Properties:
References:
the set of
activity_item
that are associated with the
assigned_activity.
Values:
the text that specifies the purpose of the association of the
Applied_activity_assignment with product or activity data.
Where applicable, the following values shall be used for role:
Definition:
An
Applied_activity_method_assignment is an association of an
Activity_method with product or activity data.
Properties:
References:
the
Activity_method that is to be associated with product or activity data.
Values:
the text that specifies the purpose of the association of the Applied_activity_method_assignment with product or activity data.
Definition:
An
Applied_independent_activity_property is a type of
Activity_property
that is an association of an
Activity_property
with an
Independent_property.
It characterizes the fact that the
Activity_property
is the application of the
Independent_property
to activity data.
Properties:
References:
Definition:
An
Applied_independent_property is a type of
Assigned_property
that is associated
with an
Independent_property.
It characterizes the fact that the
Applied_independent_property
is the application of the
Independent_property
to product data.
Properties:
References:
Definition:
An
Applied_independent_resource_property is a type of
Resource_property
that is associated to a
Independent_property
.
It characterizes the fact that the
Resource_property
is the application of the
Independent_property
to activity data.
Properties:
References:
Definition:
An
Applied_information_usage_right is an application of a particular usage right to a set of items.
NOTE
If an approval is applied to this entity, it carries the meaning that the particular
set of items is approved for
the given usage. This approval generally indicates that the approval is exceptional,
for example, where the information belongs
to another project, and that project agrees
to share some particular items of information. There is a further implication that
the set of entities should not be changed
once the approval is given.
Properties:
References:
the set of information usage right items to which the usage right applies.
the right which is applied to the items
Definition:
An
Applied_state_assignment 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.
the purpose of the association of the Applied_state_assignment
with product or activity data.
Definition:
An
Applied_state_definition_assignment is a mechanism that
enables an object to have or to be in a
State_definition.
Properties:
References:
the purpose of the association of the Applied_state_definition_assignment with product or activity data.
Definition:
An Approval is a formal confirmation of the quality of some activity
or product data.
Properties:
References:
the
Approval_status
that provides a user interpretable designation
of the level of approval.
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.
Values:
the text that completes the information provided within the status
attribute, specifying the reason or goal of the Approval.
EXAMPLE
'released for production' or 'preliminary design completed' are approval purposes.
Definition:
An
Approval_assignment is the assignment of an
Approval
to activity or product data.
Properties:
References:
the
Approval
that is assigned with activity or product data.
the activity or product data to which the
Approval
is assigned.
Values:
the text that precises the role of the
Approval
with respect to the items it is assigned to.
The value of this attribute need not be specified.
EXAMPLE
'legal requirement' is an example of role that may be used to represent the fact that
a particular approval addresses a legal
requirement for a product.
Definition:
An
Approval_relationship 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.
Values:
the text that specifies the meaning of the relationship.
Where applicable, the following values shall be used:
- 'decomposition': The Approval_relationship defines a relationship
where the related
Approval
is one of the components into which the relating
Approval
is broken down with no implication of 'sequence' or 'dependency';
- 'dependency': The Approval_relationship defines a relationship
where the issuing of the related
Approval is dependent on the issuing of the relating
Approval;
- 'precedence': the Approval_relationship defines a relationship where the related
Approval
has higher priority than the relating
Approval;
- 'sequence': The Approval_relationship defines a relationship where the relating
Approval
shall be completed before the related
Approval is given.
NOTE
The value 'dependency' does not imply the semantics of the
the values 'decomposition' or 'sequence'.
EXAMPLE 1
The
Approval of an assembly may be dependent on the
Approval of
all of the constituents of the assembly.
EXAMPLE 2
In parallel approval processes of two assemblies, assignment of an
Approval
on one of the assemblies may depend on an
Approval assigned to the second assembly.
the text that provides further information about the Approval_relationship.
The value of this attribute need not be specified.
Definition:
An Approval_status is a particular rank of approval.
Properties:
Values:
the text by which the Approval_status is designated.
EXAMPLE
'approved' and 'disapproved' are examples of Approval_status.
Definition:
An
Approving_person_organization is an association between an
Approval and the organization or person and organization that has granted this approval.
Properties:
References:
the point in time when the
Approval has been given. The value of this attribute need not be specified.
the
Approval that has been given by the considered person or the organization.
Values:
the text that specifies the role of the considered person or
organization with respect to the approval.
The value of this attribute need not be specified. By default, the
person or organization shall only be considered as an approver without any
specific role.
EXAMPLE
'quality insurance auditor', 'production cost examiner' are examples of values of
role of persons or organizations with respect
to approvals assigned to product data.
Definition:
An
Assembly_component_relationship is a type of
Product_occurrence_definition_relationship.
It identifies a possibly quantified usage of a product version as a component of
another product version.
The relationship is established between two
Product_view_definitions
The inherited attribute
relating_view
identifies the
Product_view_definition
of the assembly.
The inherited attribute
related_view
identifies the
Product_view_definition
of the product version that plays the role of component.
The Assembly_component_relationship specifies that, in the
initial_context
of the
Product_view_definition
that is referred to as
relating_view,
it is considered that the product version that is indirectly identified with the
related_view
attribute, is a component of the product version that is indirectly identified with
the
relating_view
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.
An Assembly_component_relationship is either a
Next_assembly_usage, a
Promissory_usage
or a
Component_upper_level_identification.
Properties:
References:
the
Value_with_unit that defines the amount of this usage of the component in the assembly. The value
of this attribute need not be specified.
Values:
the text 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.
Definition:
An
Assembly_relationship_substitution is a relationship that indicates that an
Assembly_component_relationship
may be substituted by another
Assembly_component_relationship.
Both assembly relationships shall refer to the same
Product_view_definition
of the same assembly.
NOTE 1
Consequently, an Assembly_relationship_substitution actually specifies that the product version
that plays the role of component in the substitute_relationship
may be replaced by the product version that plays the role of component in the base_relationship.
NOTE 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
Assembly_component_relationship
establish assembly relationships relevant in the definition contexts of the assembly,
the substitution only apply in these contexts.
An
Assembly_relationship_substitution defines a one-way substitution: if A is specified as a substitute for
B, B is not implied to be a substitute for A.
Properties:
References:
Values:
the words by which the Assembly_relationship_substitution is known.
The value of the attribute need not be specified.
the text that provides further information about the Assembly_relationship_substitution.
The value of the attribute need not be specified.
Constraints:
Constraint: UR1Specification: (OCL2.0)
Assembly_relationship_substitution::allInstance()->isUnique(Sequence{base_relationship,
substitute_relationship})
Definition:
An
Assigned_document_property is a type of
Assigned_property that identifies a property assigned to a document definition or to a file.
When the
Assigned_document_property is applied to a
Digital_document_definition
through the
described_element attribute, the
Assigned_document_property applies to all instances of
Digital_file
that are components of the
Digital_document_definition.
When the
Assigned_document_property is applied to a
Physical_document_definition
through the
described_element attribute, the
Assigned_document_property applies to all instances of
Hardcopy
that are components of the
Physical_document_definition.
When the
Assigned_document_property is applied to a
File
through the
described_element attribute, the
Assigned_document_property applies to the individual
File.
Properties:
References:
the element to which the property is assigned.
Definition:
An
Assigned_property is a property that is assigned to product data.
NOTE
The mapping provided for that entity and for its attribute
described_element is incomplete.
It needs to be completed in any module that uses this module and extends the type
property_assignment_select.
Properties:
References:
the element to which the property is assigned.
Values:
the text that provides further an identifier for the Assigned_property. The value of this attribute need not be specified.
the
words by which the Assigned_property is known.
the text that provides further information about the property. The value of this attribute
need not be specified.
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
Justification_assignment
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
Item_assumed
Properties:
Values:
the identifier for the Assumption.
the words by which the Assumption is known.
The value of this attribute need not be specified.
the text that provides further information about the Assumption.
The value of this attribute need not be specified.
Definition:
An Assumption_assignment 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 item providing the context for the assumption.
Values:
the text that provides further information about the Assumption_assignment.
The value of this attribute need not be specified.
the function performed by the assigned
Assumption.
Definition:
An
Assumption_relationship is an association between two
Assumptions.
Properties:
References:
one instance of
Assumption
that is part of the relationship.
the other instance of
Assumption
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.
Values:
the text that provides further information about the Assumption_relationship.
The value of this attribute need not be specified.
the meaning of the relationship.
Definition:
An
Attachment_slot is a type of
Product
that represents the position in which a part is or can be attached to a parent product.
EXAMPLE
A fast jet aircraft has two engines. These engines are removable and interchangeable
between individual aircraft. An attachment
slot represents each installation position for an engine so as to ensure that an accurate
record is maintained of which engines
fly in which pairing on which aircraft for how many hours.
Definition:
An
Attachment_slot_as_planned is a type of
Attachment_slot_version that identifies an individual that is the subject of a plan to realize an
Attachment_slot.
EXAMPLE
FlyFasterWithUs Group will buy an aircraft with serial number 1234 next
year. The company wishes to plan the schedule for removal of engines from
the aircraft for maintenance purposes. Instances of the Attachment_slot_as_planned
entity data type allow the company to associate individual engines with the
aircraft at different times over the planned period.
Definition:
An
Attachment_slot_as_realized is a type of
Attachment_slot_version that identifies an individual that is a realized
Attachment_slot.
EXAMPLE
FlyFasterWithUs Group operates an aircraft with serial number 1234 next year. The
company records which individual engines
power the aircraft at different times during the lifetime of the aircraft.
Definition:
An
Attachment_slot_definition is a type of
Product_view_definition that identifies a view of an
Attachment_slot.
EXAMPLE
An airworthiness authority requires an airline company to report which individual
engines power the aircraft at different
times during the lifetime of the aircraft.
Properties:
References:
Definition:
An
Attachment_slot_design is a type of
Attachment_slot_version that identifies the design version of an attachment slot.
EXAMPLE
WeMakeBigPlanes Limited creates design version 1.34 of the attachment slot for the
starboard engine of an aircraft.
Definition:
An
Attachment_slot_design_to_planned is a relationship between a design version of an
Attachment_slot and a planned individual that conforms to the design.
EXAMPLE
WeMakeBigPlanes Limited plans production of aircraft serial number 1234 with a starboard
engine attachment slot that is to
conform to design version 1.34.
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.
Values:
the identifier for the relationship between the design and the planned individual.
the words by which the relationship between the design and the planned individual
is known.
the text that provides further information about the relationship between
the design and the planned individual.
The value of this attribute need not be specified.
Definition:
An
Attachment_slot_design_to_realized
is a relationship between a design version of an
Attachment_slot and a realized individual that conforms to the design.
EXAMPLE
WeMakeBigPlanes Limited builds aircraft serial number 1234 with a starboard engine
attachment slot that conforms to design
version 1.34.
Properties:
References:
the version of the concept to which the realized individual conforms.
the individual that conforms to the design.
Values:
the identifier for the relationship between the design and the realized individual.
the words by which the relationship between the design and the realized individual
is known.
the text that provides further information about the relationship between
the design and the realized individual.
The value of this attribute need not be specified.
Definition:
An
Attachment_slot_on_product
is a relationship between a product and an
Attachment_slot that is a location on the product at which to install removable parts.
EXAMPLE
An aircraft has a pylon mounting on a wing as a location at which to install various
equipment. An instance of the Attachment_slot_on_product entity data type identifies which attachment slot corresponds to the pylon.
Properties:
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.
Values:
the identifier for the relationship between the attachment slot and the product.
the words by which the relationship between the attachment slot and the product is
known.
the text that provides further information about the relationship between
the attachment slot and the product.
The value of this attribute need not be specified.
Definition:
An
Attachment_slot_planned_to_realized
is a relationship between a realized individual of an
Attachment_slot and a corresponding planned individual.
EXAMPLE
WeMakeBigPlanes Limited builds aircraft serial number 2468 with a starboard engine
attachment slot that was previously planned.
Properties:
References:
the attachment slot that relates to the realized individual.
the individual that relates to the planned individual.
Values:
the identifier for the relationship between the planned individual and the realized
individual.
the words by which the relationship between the planned individual and the realized
individual is known.
the text that provides further information about the relationship between the
planned individual and the realized individual.
The value of this attribute need not be specified.
Definition:
An
Attachment_slot_version is a type of
Product_version that identifies a version of
Attachment_slot.
Properties:
References:
Definition:
An
Attribute_classification is an
assertion that an attribute on an instance of an EXPRESS entity is a
member of a
Class.
EXAMPLE
Three approval statuses for documents are agreed in a given business
process: 'approved', 'dis-approved' and 'in-work'.
Each of which will be represented by a
Class.
When assigning a status, 'approved' for example, to a given document,
the status will be represented by the attribute
status_name
defined on an instance of the entity,
Approval_status.
The value of this attribute will be identified by an instance of
Attribute_classification in which the
allowed_value
attribute is the
Class
'approved', the
attribute_name
attribute is
status_name
and the
classified_entity
attribute is instance of
Approval_status.
Properties:
References:
the
Class
that defines the value of the attribute identified by
attribute_name on the entity identified by the
classified_entity attribute.
an instance of one of the types of
classified_attribute_select.
The instance shall have an attribute or an inherited attribute with name
attribute_name.
Values:
the name of the EXPRESS attribute whose value is being assigned.
Definition:
An Attribute_translation_assignment is the assignment of a translation to a text attribute of an instance.
Properties:
References:
the instance for which a translation is specified for the considered_attribute in the indicated language.
the
Language in which the translation is provided.
Values:
the name of the attribute for which a translation is provided.
the text string that specifies the translation in an additional language.
Constraints:
Constraint: UR1Specification: (OCL2.0)
Attribute_translation_assignment::allInstance()->isUnique(Sequence{considered_instance,
considered_attribute, translation_language})
Definition:
An
Axis_placement is a type of
Detailed_geometric_model_element
that defines a right-handed, 2D or 3D, coordinate system.
If the Axis_placement belongs to a 3D geometric space, the third direction of the coordinate system is
defined
by the vector product of x-axis and y-axis.
An
Axis_placement may be an
Axis_placement_2d
or an
Axis_placement_3d.
Properties:
References:
the
Cartesian_point
that defines the position of the
Axis_placement in the geometric space.
the
Direction
that defines the first axis of the
Axis_placement.
the
Direction
that defines the second axis of the
Axis_placement.
Definition:
An
Axis_placement_2d is a type of
Axis_placement.
Definition:
An
Axis_placement_3d is a type of
Axis_placement.
Definition:
An
Axis_placement_mapping is a geometric transformation defined by a source
Axis_placement
and a target
Axis_placement
that results from the transformation of the source one.
Both instances of
Axis_placement
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
x_axis
of the source onto the
x_axis
of the target;
- the
y_axis
of the source onto the
y_axis
of the target.
NOTE
By construction, the determinant of the transformation matrix equals one.
Properties:
References:
the
Axis_placement
that plays the role of source in the transformation.
the
Axis_placement
that plays the role of target in the transformation.
Definition:
A
Breakdown
is a type of
Product
that identifies a partitioning of a product into a set of related elements so as
to form explicit, parent-child
views that comprise the product elements.
The parent-child view is represented by
Breakdown_element_usage
objects relating the elements in the breakdown that are represented by
Breakdown_element
objects.
Definition:
A
Breakdown_context
is a membership relationship between a
Breakdown_element
and a
Breakdown
of which the element is a member.
Properties:
References:
Values:
the identifier for the membership relationship between the breakdown
element and the breakdown.
the word or words by which the membership relationship between the breakdown element
and the breakdown is known.
the text that provides further information about the membership relationship
between the
Breakdown_element
and the
Breakdown.
The value of this attribute need not be specified.
Definition:
A
Breakdown_element
is a type of
Product
that identifies the elements in one or more
Breakdown
objects.
Definition:
A
Breakdown_element_definition
is a type of
Product_view_definition
that identifies a view of a version
(
Breakdown_element_version)
of a
Breakdown_element.
Properties:
References:
Definition:
A
Breakdown_element_realization
is a type of
Product_definition_element_relationship
that identifies a relationship between a
Breakdown_element_definition
or a
Breakdown_element_usage
and an item that realizes that element definition or usage.
EXAMPLE
A pump realizes the 'provide fuel to engine' element in a functional breakdown
for a ship.
Definition:
A
Breakdown_element_usage
is a type of
View_definition_relationship
that identifies a relationship between a parent and child
Breakdown_element.
Properties:
References:
the parent breakdown element of the relationship.
the child breakdown element of the relationship
Values:
the word or words by which the relationship between the parent and the child breakdown
elements is known.
Definition:
A
Breakdown_element_version
is a type of
Product_version
that identifies a version of a
Breakdown_element.
.
Properties:
References:
Definition:
A
Breakdown_of
is a relationship between a
Breakdown
and a
Product
of which the breakdown is a view.
Properties:
References:
the product of which the breakdown is a view.
Values:
the identifier for the relationship between the breakdown and the product.
the word or words by which the relationship between the breakdown and the product
is known.
the text that provides further information about the
relationship between the breakdown and the product.
The value of this attribute need not be specified.
Definition:
A
Breakdown_version
is a type of
Product_version
that identifies a version of a
Breakdown.
Properties:
References:
the
Breakdown_version shall only be a version of a
Breakdown.
the Breakdown_version shall be a breakdown of one and only one product.
Definition:
A Calendar_date is a date that is defined as a day in a month of a year.
Properties:
Values:
the year element of the Calendar_date.
the month element of the Calendar_date.
the day element of the Calendar_date.
Definition:
A
Cartesian_point is a type of
Detailed_geometric_model_element
that defines a point by a list of up to 3 cartesian coordinates.
Properties:
Values:
the list of up to 3 length measure values that define the cartesian coordinates of
the point.
Definition:
A
Cartesian_transformation_2d is a type of
Detailed_geometric_model_element.
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:
References:
the array of two instances of
Direction
that defines the multiplication matrix of the transformation.
the
Cartesian_point
that defines the position of the result of the application of the transformation
to the origin of the geometric space.
Definition:
A
Cartesian_transformation_3d is a type of
Detailed_geometric_model_element
that is a geometric transformation defined in a 3D geometric space by a 3*3 matrix
and a cartesian point.
Let be:
- M, the 3*3 multiplication matrix of the cartesian transformation;
- A, the point of the cartesian transformation;
- P, a point in the geometric space;
- Q, the result of the application of the transformation to P.
The coordinates of Q shall be obtained by the formula: Q = M*P + A
Properties:
References:
the array of three instances of
Direction
that defines the multiplication matrix of the transformation.
the
Cartesian_point
that defines the position of the result of the application of the transformation
to the origin of the geometric space.
Definition:
A
Causal_consequence is a type of
View_definition_relationship
that identifies secondary effects related to or resulting from a particular
Risk_consequence.
Properties:
References:
represents the more immediate consequence of the risk occuring
represents the aftereffect of the more immediate risk consequence.
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:
Values:
the words by which the
Certification is known.
EXAMPLE 1
'AP 214 certified' is an example of name that can be used to indicate a certification
of a STEP interface.
EXAMPLE 2
'ISO 9000' is an example of name that can be used to indicate that a product has been
developed following ISO 9000 directives.
the
text that provides further information about the
Certification
.
The value of the attribute need not be specified.
the text that identifies the type of the certification.
Definition:
A
Certification_assignment 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 activity or product data to which the
Certification
is assigned.
Values:
the text that specifies the purpose of the association of the
Certification
with respect to the product or activity data it is granted to.
EXAMPLE 2
'Software acceptance' is an example of role that can be used to track the fact that
an external product has been inspected
before having been made available in an organization.
Definition:
A
Chain_based_geometric_item_specific_usage is a type of
Geometric_item_specific_usage
that represents a chain of
Geometric_models
in a graph of
Geometric_models,
where the undirected links in the graph can be
Geometric_coordinate_spaces,
Geometric_model_relationships,
or
Geometric_placement_operations.
Properties:
References:
the list of items that relate nodes in the chain.
Definition:
A
Class is a number of things considered together.
NOTE 1
In this part of ISO 10303, the term 'class' and 'set' are
synonyms.
NOTE 2
A class can consist of all things with a particular set of
properties. Hence information about the consequences of
possessing the set of properties can be assigned to the class.
If a thing is classified as being a member of such a class,
then a set of properties possessed by the thing can be
deduced.
NOTE 3
This entity may be instantiated as a compound instance involving
another entity from ISO 10303.
Each
Class is a
Class_by_extension
or a
Class_by_intension
NOTE 4
The distinction between a
Class_by_extension
and a
Class_by_intension
can be imprecise. For example, the set of
items produced by a particular production run could be regarded
as either. The entity type class is not specified as abstract, so
an application protocol or application module can decide to
ignore the distinction.
Properties:
Values:
the identifier that distinguishes the Class.
the word or words by which the Class is known.
the text that provides further information about the Class.
The value of this attribute need not be specified.
All Supertype Blocks:
Class
Definition:
A
Class_by_extension is a type of
Class
that is a set that is defined by means of a
criterion that does not enumerate the members.
All Supertype Blocks:
Class
Definition:
A
Class_by_intension is a type of
Class
that is a set that is defined by enumerating the
members.
Definition:
A
Classification_assignment is the assignment of a
Class to product or activity data for their classification. That means that every member
of
items belongs to the
assigned_class.
Properties:
References:
the
Class that is considered in the assignment.
Values:
the meaning of the relationship between the assigned_class and the associated items.
The value of this attribute need not be specified.
NOTE
When there is a specific role, the assignment has extra information that can be useful
to differentiate this assignment from
others.When all the items are assigned to the same
Class in the same way there is no need to specify a role. Just when it is needed to distinguish
them, the role attribute is useful.
EXAMPLE 1
The role for 'electromagnetic compatibility' has the associated object that is a classification
that categorizes the classified
element in respect of its ability to comply with requirements concerning electromagnetic
interference.
EXAMPLE 2
The role for 'environmental conditions' has the associated object that is a classification
that categorizes the classified
element in respect of its ability to comply with environmental impact requirements.
Definition:
An
Collection is a type of
Product
that identifies a set of data.
Definition:
An
Collection_assignment is an association of an
Collection_view_definition
with the object to which the collection has relevance.
Properties:
References:
the object to which the collection has relevance.
Definition:
An
Collection_membership is an association of an
Collection_view_definition
with an object that represents a member of the collection.
Properties:
References:
an object that represents a member of the collection.
Definition:
An
Collection_relationship is a type of
Product_relationship
that represents an association between two
Collection objects.
Properties:
References:
Definition:
An
Collection_version is a type of
Product_version that represents a revision of an
Collection.
Properties:
References:
Definition:
An
Collection_version_relationship is a type of
Product_version_relationship
that represents an association between two
Collection_version objects.
Properties:
References:
the other instance of
Collection_version
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_version_sequence_relationship is a type of
Collection_version_relationship
that represents a sequential association between two
Collection_version objects.
Definition:
An
Collection_view_definition is a type of
Product_view_definition
that represents a characterization of an
Collection_version 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 Collection_view_definition.
Properties:
References:
Definition:
A
Complement is a relationship that is between
- set S1,
- set U, and
- set S2
that indicates set S
2 consists of all members of U that
are not members of S
1.
Properties:
References:
the
Class
that has
set_2 as its complement within universe.
the
Class
that has
set_1 as its complement within universe.
the
Class
that is the union of
set_1 and
set_2.
Values:
an identifier for the Complement relationship.
the word or sequence of words by which the Complement relationship is
referenced.
the text that provides further information about the Complement relationship.
Definition:
A
Component_upper_level_identification is a type of
Assembly_component_relationship.
It identifies a component of an assembly with respect to an upper level in the assembly
structure.
NOTE
A
Component_upper_level_identification
does not add a component in an assembly, it provides a means to further characterize
a component with respect to an upper
level assembly.
The identified component is the version of product, indirectly referred to as the
related_view
of the sub_assembly_relationship.
The upper level assembly is the version of product, indirectly referred to as the
relating_view
of the upper_assembly_relationship.
Properties:
References:
the
Next_assembly_usage
that identifies indirectly the component that is further characterized by the
Component_upper_level_identification.
Constraints:
Constraint: UR1Specification: (OCL2.0)
Component_upper_level_identification::allInstance()->isUnique(Sequence{upper_assembly_relationship,
sub_assembly_relationship})
Definition:
A
Composition_of_state is a type of state relationship and it relates the nature of states
in relation to one another, where two or more
State parts compose a whole
State; and furthermore,
whole states can become parts of yet another whole
State.
Definition:
A
Composition_of_state_definition is a type of
State_definition_relationship.
It relates
State_definition entities to one another,
when two or more
State_definition entities act as
parts to compose a whole
State_definition; and furthermore, whole
State_definition entities can become parts of yet another whole
State_definition.
Definition:
A
Concurrent_elements
is a type of
Structured_task_element
that comprises a set of actions to be performed during the time required for the longest
task. No specific order is required.
Properties:
References:
Definition:
A
Condition is a definition of the precedent that must be fulfilled
before a statement or relationship becomes valid.
NOTE
The condition is defined as a text based expression that is represented
by the description attribute.
The parameters against which the condition is to be evaluated are
identified by
Condition_parameter.
The target or consequence of a condition is represented by
Condition_assignment.
EXAMPLE
"If the engine has been running for 10000 hours then it requires a
service"
is an example of a conditional statement. The conditional
part of the statement is "If the engine has been running for 10000
hours" which is stored in definition attribute on Condition.
The parameter or subject of the condition is "the engine" which is
represented by a
Condition_parameter
identifying the
Product_as_realized
which represents the engine.
The consequence of the condition is "then it requires a service".
This is represented by
Condition_assignment
identifying the task to perform the service, a
Task_method.
Properties:
Values:
the words by which a Condition is known.
the text that provides further information about the Condition.
The value of the attribute need not be specified.
Definition:
A
Condition_assignment is a relationship that identifies the statement or relationship to
which a
Condition
applies.
EXAMPLE
Condition 29 applies to the relationship between a Saab 9.3 car and
the activity of checking the oil level on that make of car.
Properties:
References:
the product or activity data to which the
Condition
is being assigned.
Definition:
A
Condition_evaluation is a record of the evaluation of a
Condition and the
subsequent result.
EXAMPLE
A
Condition is
"If the measured value of oil pressure from gauge 3 on a car is less
than 2 bar then check the oil level"
When the condition is evaluated it is recorded by an instance of
Condition_evaluation.
The measured value of oil pressure from gauge 3 on car with VIN 12345678
is 1.9 bar. Therefore the result of the evaluated the condition
is true.
Properties:
Parts:
the indication whether the
Condition evaluates to True, False or Unknown.
References:
Values:
the words by which the Condition_evaluation is known.
the text that provides further information about the
Condition_evaluation.
The value of the attribute need not be specified.
Definition:
A
Condition_evaluation_assignment is a relationship that identifies the statement or
relationship to which the
Condition_evaluation
applies.
EXAMPLE
The
Condition_evaluation
(instance 87) is assigned to the activity of checking the
oil level on car VIN 12345678.
Properties:
References:
Definition:
A
Condition_evaluation_parameter is an identification of the product or
activity data used in the evaluation of the
Condition
identified by the
Condition_evaluation.
EXAMPLE
The measured value of oil pressure from gauge 3 on car with VIN
12345678 (value = 1.9 bar).
Properties:
References:
Values:
the words by which a Condition_evaluation_parameter is known.
the text that provides further information about the
Condition_evaluation_parameter.
The value of the attribute need not be specified.
Definition:
A
Condition_parameter is a represention of the product or
activity data that is used to specify a
Condition.
EXAMPLE
Oil pressure on gauge 3.
NOTE
The product or activity data is defined in
condition_parameter_item.
The contents of this select type are defined in application modules
that use this module.
Properties:
References:
the
Condition
for which the parameter is an input.
the product or activity data which acts as a parameter to the condition.
The value of this attribute need not be specified.
Values:
the words by which a Condition_parameter is known.
the text that provides further information about the Condition_parameter.
The value of the attribute need not be specified.
Definition:
A
Condition_relationship is a relation between two conditions.
NOTE
The
Condition_relationship normally represents a logical
combination of conditions. The logical type is identified by the
classification of the
Condition_relationship by a
Classification_assignment.
EXAMPLE
"If the engine has been running for 10000 hours AND the engine is
fitted with a clog-up-quick Oil filter then change the oil filter" is
an example of two conditions related by a logical AND.
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.
Values:
the words by which the Condition_relationship is known.
the text that provides further information about the Condition_relationship.
The value of the attribute need not be specified.
Definition:
A Conditional_effectivity is a type 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
Content_item is a reference to any item that can be referenced as part of the message content.
NOTE 1
As well as externally defined items such as drawings, photographs, and
so on, a message can refer to any entity represented in the schema it is
used in, from products to property values, or actions to task steps. The
mechanism used gives no interpretation of how the
item_identifier
is interpreted or how the data is
accessed. For example, the identifier could be the number of the
entity in a file that conforms to ISO 10303-21.
Interpretation of this entity and its attributes may be
defined through reference data.
Properties:
Values:
the mechanism to reference any entity or object in the message.
NOTE 2
The
item_identifier should provide a unique reference to the item referred to in the
Message.
the type of the item.
EXAMPLE 1
A
Product
in a file that conforms to ISO 10303-21 may be given the type
'ISO 10303-21 entity'.
The value of the
item_identifier
attribute would
then be the object identifier in the file.
EXAMPLE 2
A log file from built-in test equipment may be given the type
'equipment log file'.
the information required to access the data. This may include or imply a
description that associated entities are accessed as part of the
message.
The value of this attribute need not be specified.
All Supertype Blocks:
Unit
Definition:
A
Context_dependent_unit is a type of
Unit
that is not related to the system of units defined in this part of ISO 10303.
EXAMPLE
The number of parts in an assembly is a physical quantity that may be measured in
a unit called
'parts'. Such a unit cannot be related to an SI unit.
Definition:
A
Contextual_item_shape is a type of
Item_shape
that identifies the shape of a product version in the context of its use in another
product version.
The product version whose contextual shape is identified, is the product version associated
with the
related_view
of the
View_definition_usage.
EXAMPLE
Flexible part may have several shapes, each associated with a particular occurrence
of the part in assemblies.
Properties:
References:
Definition:
A
Contextual_shape_representation is a relationship that relates a
Contextual_item_shape
and a
Geometric_model_relationship.
Properties:
References:
Definition:
A Contract is a binding agreement.
Properties:
Values:
the identifier for the contract.
the text that provides information about the objectives of the contract.
the text that identifies the type of the contract.
Definition:
A
Contract_assignment 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 activity or product data to which the
Contract
is assigned.
Definition:
A
Contract_relationship is a relationship between two
Contract objects.
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.
All Supertype Blocks:
Unit
Definition:
A
Conversion_based_unit is a type of
Unit
that that is based on another and related by a conversion factor.
NOTE
A Conversion_based_unit is often used to convert a unit in one system of units to a similar unit in another
system.
EXAMPLE
An Imperial inch is 25.4 millimetres
Properties:
References:
Definition:
A
Date_or_date_time_assignment is an association of a
Calendar_date
or a
Date_time
with activity or product data.
Properties:
References:
Values:
the text that specifies the purpose of the association between the
Calendar_date
or
the
Date_time
with activity or product data.
Definition:
A Date_time is a time on a particular day.
Properties:
References:
the date element of the date time combination.
the time element of the date time combination.
Definition:
A
Dated_effectivity is a type of
Effectivity for which the domain of
applicability is defined as an interval of time bounded by dates or events.
The interval may be open-ended.
Depending on whether the
end_bound attribute is specified, the actual domain of time defined by a
Dated_effectivity is:
- either, the time interval between the start and end date or event;
- or, the open time interval that starts at the start date or event.
If the
end_bound is an event that actually identifies a point in time that comes before the
start_bound, 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 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
Decision_point is a type of
Structured_task_element.
It requires a decision that determines which further
Task_element is to be followed.
NOTE
The condition on which the decision is based optionally allows a further
Task_element
to be invoked to provide the basis for the decision.
Properties:
References:
the criterion to be tested in order to make a decision.
the
Task_element
to be performed if the test condition is satisfied.
The value of this attribute need not be specified.
the
Task_element
to be performed if the test condition is not satisfied.
The value of this attribute need not be specified.
the
Task_element
to be performed if the test condition can not be evaluated or returns unknown.
The value of this attribute need not be specified.
Definition:
A Decreasing_resource_event is a type of
Resource_event
that decreases the balance of a managed resource.
EXAMPLE
Filling a requisition reduces an inventory.
Definition:
A
Defined_state_relationship is a relationship that links a
State_assertion
to a
State_assessment.
Properties:
References:
Values:
the words by which the Defined_state_relationship is known.
the text that provides further information about the Defined_state_relationship. The value of this attribute need not be specified.
Definition:
A
Definitional_representation_relationship is a type of
Representation_relationship.
The representation indicated by
rep_1
is part of the definition indicated by
rep_2.
All Supertype Blocks:
Unit
Definition:
A
Derived_unit is a type of
Unit
that is defined by an expression of other units.
EXAMPLE
Newtons per square metre is a derived unit.
Properties:
References:
a set of units and their exponents whose product defines the
Derived_unit.
NOTE
Each element is one term in the Derived_unit.
Definition:
A
Derived_unit_element is the association of an exponent with a
Unit.
Properties:
References:
Values:
Definition:
A
Description_text 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:
Values:
the text that constitutes the description
Definition:
A Description_text_assignment is the assignment of a description to something.
Properties:
References:
the text that constitutes the description
the set of items being described
Definition:
A
Descriptive_document_property is a type of
String_representation_item that specifies a text based
characteristics of a
Document_definition
or of a
File.
Properties:
References:
Definition:
A
Detailed_geometric_model_element is a type of
Representation_item.
It identifies a geometric construct.
Only non abstract specializations of the Detailed_geometric_model_element entity data type can be instantiated.
A
Detailed_geometric_model_element is either a
Cartesian_point
or a
Direction
or an
Axis_placement
or a
Cartesian_transformation_2d
or a
Cartesian_transformation_3d
or a specialization defined elsewhere.
Definition:
A
Digital_document_definition
is a type of
Document_definition.
It identifies a collection of files that are archived on an optical computer disc,
magnetic, electronic storage, or a combination
thereof.
A digital document definition may consist of one or many component digital files.
Properties:
References:
the set of instances of
Digital_file that
provides the content of the digital document.
Definition:
A
Digital_file is a type of
File.
A
Digital_file contains computer interpretable data and is stored on an electronic device.
Definition:
A
Directed_activity is a type of
Activity. It identifies an actvity that is governed by a
Work_order.
Properties:
References:
the
Work_order that governs the
Directed_activity.
Definition:
A
Direction is a type of
Detailed_geometric_model_element
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
Axis_placement.
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 Distribution_by_value is a type of
Probability_distribution
that explicitly lists pairs of random variable values and function values.
NOTE 1
Distribution_by_value is used where there is no named distribution which can be used to identify the distribution,
for
example, when the distribution is derived from observation.
Properties:
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 occuring.
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).
Values:
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.
Definition:
A
Document is a type of
Product used to identify documentation data that is under
configuration change management.
Definition:
A Document_assignment is a mechanism to associate a document
with product data, where the assigned document provides information about
the data with which it is associated.
Properties:
References:
Values:
the text that provides the meaning of the
Document_assignment.
EXAMPLE
-
'additional information': The assigned document provides
information that is relevant for the associated object, but is not
a description of the associated object itself;
-
'behavior': The assigned document specifies information about the
behavior of the associated object;
-
'description': The assigned document provides textual information for the
associated object itself;
-
'informative': The assigned document may or may not be considered;
-
'mandatory': The associated object shall conform to the content of the
assigned document;
-
'mathematical description': The assigned document specifies the
associated object by providing the algorithmic specification of its
behavior.
Definition:
A Document_definition
is a type of
Product_view_definition that is a
Document_version 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
Document_definition
is a
Digital_document_definition
or a
Physical_document_definition.
NOTE 2
Aspects of the representation may not be known at the time the identification is established.
Properties:
References:
Definition:
A
Document_definition_relationship is a relationship between two instances of
Document_definition.
Properties:
References:
the other instance of
Document_definition that participates in the relationship.
If one element of the relationship is dependent upon the other, this attribute shall
be the dependent one.
Values:
the
relation_type
specifies the meaning of the relationship.
Where applicable the following values shall be used:
- 'addition': The application object specifies that the related document provides supplementary
or collateral information with
regard to the information provided by the relating document;
- 'copy': The application object defines a relationship where the related
Document_definition is a copy of the relating
Document_definition;
- 'decomposition': The application object defines a relationship where the related
Document_definition is one of potentially more sub documents of the relating
Document_definition;
EXAMPLE 1
The decomposition of a document into clauses is an example for the use of this value.
- 'derivation': The application object defines a relationship where the related
Document_definition is derived from the relating
Document_definition;
EXAMPLE 2
A raster image may be derived from a 3D CAD model.
EXAMPLE 3
A html version may be derived from a text document as an alternative.
- 'peer': The application object specifies that the related document provides required
information with regard to that provided
by the relating document. The peer document is essential for a complete understanding;
- 'reference': The application object defines a relationship where the related document
is referenced from the relating;
EXAMPLE 4
A hyperlink is an example for a 'reference'.
- 'sequence': The application object defines a logical sequence where the related
Document_definition comes after the relating
Document_definition;
EXAMPLE 5
A sequence of clauses.
- 'substitution': The application object defines a relationship where the related
Document_definition replaces the relating
Document_definition;
- 'translation': The
Document_definition_relationship specifies that the related document is generated through a translation process from
the relating document.
Definition:
A
Document_location_identification is a type of
External_source_identification that identifies the location of
the components of a
Document_definition in an external storage system where they can be found.
EXAMPLE 1
An HTML file that includes a picture may be represented as a
Document_definition made of two components:
- the HTML file;
- the binary file that contains the picture.
If these files were located within the same directory or relatively to the same directory,
the
source_id attribute would convey the directory name.
EXAMPLE 2
Examples of
source_type
are:
- 'URL' - for a web page;
- 'FTP' - for an FTP address;
- 'ISBN' - for physical documents.
Definition:
A
Document_property_representation is a type of
Representation that conveys the parameters of a particular aspect of an
Assigned_document_property.
Where applicable, the following values shall be used for the inherited name attribute
of the
Document_property_representation:
-
'document content': a category of parameters that precise characteristics of the data
contained in a document definition or
in a file;
-
'document creation': a category of parameters that detail the context of creation
of a document definition or file;
-
'document format': a category of parameters that describe the format of a document
definition or of a file;
-
'document size': a category of parameters that detail the size of a document definition
or of a file.
The following characteristics may be items of a
Document_property_representation with name 'document content':
-
A
Descriptive_document_property with name 'detail level' specifying the level of detail that is provided;
EXAMPLE 1
An example value for the 'detail level' property is 'rough 3d shape' - a 3D shape
model without edge rounds and fillets.
-
A
Descriptive_document_property with name 'geometry type' specifying the kind or kinds of geometry that is contained;
EXAMPLE 2
examples of geometry type are:
'3D wireframe model', '2D shape', 'surface model', 'closed volume', 'solid model',
'solid and surface model',
'2D drawing'.
-
A
Descriptive_document_property with name 'real world scale' specifying a text representation of the scale used.
The following characteristics shall be an item of a
Document_property_representation with name 'document creation':
-
A
Descriptive_document_property with name 'creating system' specifying the name of the computer application or the
machine that was used to generate the
document definition or the file.
The following characteristics may be items of a
Document_property_representation with name 'document creation':
The following characteristics may be items of a
Document_property_representation with name 'document format':
The following characteristics may be items of a
Document_property_representation with name 'document size':
Properties:
References:
Definition:
A
Document_version is a type of
Product_version
A
Document_version identifies a particular version of a document.
Properties:
References:
the
Document of which the instance of this entity type is a version.
Definition:
A
Duration is a type of
Value_with_unit
that defines the magnitude of a time interval.
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:
Values:
the text that provides further information about the
Effectivity.
The value of the attribute need not be specified.
Definition:
An
Effectivity_assignment is the association of an
Effectivity
with product or activity data.
Properties:
References:
the instance of the
Effectivity entity that is assigned.
Values:
the text that specifies the purpose of the association of the
Effectivity with
items.
For an
Effectivity that identifies a period of time, if applicable, the following values shall be used:
- 'actual': The
assigned_effectivity defines a period of time during which the associated items are or were effective;
- 'planned': The
assigned_effectivity defines a period of time during which the associated items are or were expected to
be effective;
- 'required': The
assigned_effectivity defines a period of time during which the associated items are or were required to
be effective.
Definition:
An
Effectivity_relationship is an association between two instances of
Effectivity.
The meaning of the relationship is represented with the
relation_type attribute.
Properties:
References:
Values:
the text that specifies the meaning of the relationship.
Where applicable, the following value shall be used:
- 'constraint': The domain of the related
Effectivity shall be included in the domain of the relating
Effectivity.
the text that provides further information about the relationship.
The value of the attribute need not be specified.
All Supertype Blocks:
Unit
Definition:
An
Electric_current_unit is a type of
Unit
with which movement of electrically charged particles is expressed.
Definition:
An
Element_constraint is a type of
Task_element_relationship
that signifies a constraint between
Task_elements. The constraint may only apply within the context of a
Task_method
or
Task_element, specified as the context.
Properties:
References:
the
Task_element 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 callibration.
Or a 30 minute wait is required between
stages of a method.
Definition:
An
End_task is a type of
Task_element.
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:
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.
Values:
an identifier for the Envelope.
NOTE 1
The id is unique and is used to identify which Envelope an
acknowledgement is referring to.
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 recepients' 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.
Definition:
An Envelope_relationship is an association of one
Envelope with another.
NOTE
The most obvious use of the association is to link an
Envelope to its acknowledgements.
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.
Values:
the role the relationship takes.
The value of this attribute need not be specified.
EXAMPLE
If Envelope with id = 123 gets is acknowledged by Envelope id = 246, then
Envelope_relationship.relating points to Envelope.id=123,
Envelope_relationship.related points to Envelope.id=246 and
Envelope_relationship.relation_type="acknowledges".
Definition:
A Environment_assignment 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
Environment_definition is a type 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.
Definition:
A
Environment_definition_version is a type of
Product_version
that identifies a particular version of an
Environment_definition.
Properties:
References:
Definition:
A Environment_definition_view is a type of
Product_view_definition
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
Environment_view_definition_relationship is a type of
View_definition_relationship
that represents an association between two
Environment_definition_view
objects.
Properties:
References:
Definition:
An
Event is the fact of the existence of a state at some point in time.
NOTE 1
The event may have occurred or may be not yet started.
NOTE 2
The point in time where an event will start or started, may not be known or specified.
Properties:
References:
the
Calendar_date or
Date_time when the event is or was planned to start.
The value of the attribute need not be specified.
Values:
the identifier that distinguishes the
Event.
the
words by which the event is known.
EXAMPLE
'Start of production' and 'break down of machine A' are examples of event names.
the
text that provides further information about the event.
The value of the attribute need not be specified.
Definition:
An
Event_assignment is assignment of an
Event
to product or activity data.
Properties:
References:
the
Event
to be assigned to product or activity data.
the product or activity data to which the Event is assigned.
Values:
the text that specifies the meaning of the event with respect to the
items.
EXAMPLE
'Deadline' is an example of role for an event assigned to activities
that are expected to be completed before this event.
Definition:
An
Event_relationship is a relationship which exists between two
Events.
EXAMPLE
An instance of this entity data type with
relation_type 'sequence' may be used to specify that an event shall end before another event starts.
Properties:
References:
one of the instances of
Event
that is a part of the relationship.
the other related instance of
Event is a part of the relationship. If one element of the relationship is dependent upon
the other, this attribute shall be the
dependent one.
Values:
the string that defines the kind of relationship that is specified.
Where applicable, the following values shall be used:
- 'actualization': The relationship specifies that the relating
Event identifies a predicted or planned event and the related
Event identifies the point in time when that event actually occurred.
This relationship is valid if the
actual_start_date attribute of the relating
Event is not specified and the
actual_start_date attribute of the related
Event is specified, or, if both these attributes are specified and equal;
- 'exclusiveness': The relationship specifies that the relating and the related
Event shall not have any overlap during their duration;
- 'sequence': The relationship specifies that the relating
Event shall be completed before the related
Event starts;
- 'simultaneity': The relationship specifies that that both the relating and related
Event are considered as occurring during the same time period or shall be performed together
in order to ensure consistency and
enhance efficiency.
NOTE
The criteria for 'simultaneity' and in particular the allowed delay between two events
declared simultaneous, are user-dependent.
the
text that provides further information about the Event_relationship.
The value of the attribute need not be specified.
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:
References:
identifies the validation or verification for which this evidence has been related.
the component data items used to support this evidence.
Definition:
An
Exit_loop is a type of
Structured_task_element.
It signifies a point at which to exit from a loop.
Definition:
An
Expanded_uncertainty is a type of
Standard_uncertainty
that specifies the factor of an uncertainty.
Properties:
Values:
the multiplier of the uncertainty of the value.
Definition:
An
Experience_gained is a relationship between an
Experience_instance and a person or organization.
Properties:
References:
Values:
the text that specifies the function performed by the
person or organization during the process of gaining the
Experience_instance.
The value of the attribute need not be specified.
EXAMPLE 1
inspector
EXAMPLE 2
manager
EXAMPLE 3
mechanic
Definition:
An
Experience_instance
is a particular eposide of contact with and/or observation of facts or events which
contributes to the accumulation of knowledge
or skill.
EXAMPLE 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
Experience_instance can be described using assigned properties or by referring to activities or tasks.
Properties:
References:
an experience instance contributes to the definition of the experience gained.
the
Activity or
Resource_as_realized
that provides the content of the
Experience_instance.
The value of the attribute need not be specified.
Values:
the text that provides further information about the experience instance.
The value of the attribute need not be specified.
Definition:
An
Experience_type is a
category or class of experience.
EXAMPLE 1
welding
EXAMPLE 2
mechanical design
EXAMPLE 3
flying
Properties:
References:
Values:
the word or words by which the Experience_type is known.
the text that provides further information about the Experience_type.
The value of the attribute need not be specified.
Definition:
An
Experience_type_relationship 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
External_analysis_model is a type of
Analysis_model
whose content is provided in an external file.
Properties:
References:
the
Digital_file
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
External_class is a type of
Class
that represents a reference to a class that is not included in the data
exchange file and is defined in an external class library.
Properties:
References:
the identification of the external class library that provides the definition
for the class.
Definition:
An
External_class_library is a type of
External_source.
An
External_class_library is the identification of an external class library.
Definition:
An
External_geometric_model is a type of 3D
Geometric_model
whose content is provided in an external file.
The set of items of the External_geometric_model contains only one element that shall be an
Axis_placement.
This
Axis_placement
specifies the reference location and orientation with respect to which placement of
the External_geometric_model in other
Geometric_models shall be defined.
Properties:
References:
the
Axis_placement
that defines the reference position or orientation of the
External_geometric_model.
NOTE
Most of times, the position is the origin point of the coordinate space and the orientation
matrix is the identity matrix.
the
Digital_file
that contains the external geometry information.
Definition:
An
External_item_identification is a type of
External_source_identification
that provides the identifier of an item in the context of an external source where
it can be found.
Properties:
Values:
the identifier of the external item, in its external context.
EXAMPLE 1
For a digital file, the file name of a file in the directory where it is located is
an example of external_id.
EXAMPLE 2
For a book, the external_id could be the ISBN number.
Definition:
An External_source is an identification of a source of
product data that is not the EXPRESS schema to which the exchange conforms.
NOTE
The product data may conform to some other part of this International Standard.
Properties:
Values:
the identification of the External_source.
the text that characterizes the External_source.
The value of this attribute need not be specified.
Definition:
An External_source_identification is the identification of the source where an item, or the components of an item,
can be found.
Properties:
References:
Values:
the text that identifies the context in which the
external_id
is specified.
EXAMPLE 1
For a digital file identified by a filename and directory path, the source_id is the directory path.
the text that identifies the identification scheme of the source_id.
EXAMPLE 2
In the case of files, examples of source_type are:
- 'URL' - for a web page;
- 'FTP' - for an FTP address;
- 'ISBN' - for physical documents.
the text that provides further information about the external identification. The
value of this attribute need not be specified.
Definition:
A
File is a file stored on a computer system or in
a stack of non-digital documents.
A
File is either a
Hardcopy
or a
Digital_file.
Properties:
Values:
the identifier for the File.
EXAMPLE
This attribute may be used to convey the identification of a digital file in the directory
where it is stored.
a string that provides a version identifier for the file. The value of this attribute
need not be specified.
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.
Definition:
A File_location_identification is a type of
External_item_identification
that identifies the location of
a
File
in an external storage system where it can be found.
EXAMPLE 1
For a computer file identified by a filename and directory path, for
example 'D:\project1\specification.txt', the
external_id
attribute represents the filename,
'specification.txt' and the
source_id
attribute represents the path
name, 'D:\project1\'.
EXAMPLE 2
Examples of
source_type
are:
- 'URL' - for a web page;
- 'FTP' - for an FTP address;
- 'ISBN' - for physical documents.
Definition:
A
File_relationship is a relationship between two instances of
File.
EXAMPLE 1
A service manual may contain graphics for explanatory reasons.
In this case, the File objects that contain the graphics are referenced as related
from the File object that contains the
body of the service manual with
relation_type '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.
Values:
the
relation_type
is the meaning of the relationship.
Where applicable the following values shall be used:
- 'addition': The application object specifies that the related document provides supplementary
or collateral information with
regard to the information provided by the relating document;
EXAMPLE 2
The recommended practices for this part of ISO 10303 may be an addition.
- 'copy': The application object defines a relationship where the related
File is a copy of the relating
File;
- 'decomposition': The application object defines a relationship where the related
File is one of potentially more sub documents of the relating
File;
EXAMPLE 3
The decomposition of a document into clauses or into several CAD models is an example
for 'decomposition'.
- 'derivation': The application object defines a relationship where the related
File is derived from the relating
File;
EXAMPLE 4
The derivation of a hypertext document from an text document is an example for 'derivation'.
- 'peer': The application object specifies that the related document provides required
information with regard to that provided
by the relating document. The peer document is essential for a complete understanding;
- 'reference': The application object defines a relationship where the related document
is referenced from the relating one;
EXAMPLE 5
The link in a hypertext document may be a reference.
- 'sequence': The application object defines a logical sequence where the related
File comes after the relating
File;
EXAMPLE 6
A sequence of clauses is an example for 'sequence'.
- 'substitution': The application object defines a relationship where the related
File replaces the relating
File;
- 'translation': The application object specifies that the related document is generated
through a translation process from
the relating document.
The values 'addition', 'decomposition', and 'peer' are used for the purpose of creating
logical structures of documents.
These values shall only be used for the
relation_type of
Document_definition, if the referenced
File objects do not participate in a
Document_definition.
In the latter case,
Document_definition_relationship shall be used instead.
the
text that provides further information about the
Document_definition. The value of this attribute need not be specified.
Definition:
A
Function_value_pair 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:
References:
the value of the probability function for the given random variable value.
the value of the random variable.
Definition:
A
Functional_breakdown is a type of
Breakdown
that identifies a partitioning of a product into a set of related functional
elements so as to form explicit structural views that comprise the
product elements.
The composite - component view is represented by
Functional_element_usage
instances relating the functional elements in the breakdown which are represented
by
Functional_elements.
EXAMPLE
A functional breakdown provides a decomposition of an aircraft in terms
of high-level functional processes such as flight, taxiing and at rest all
the way down to low-level processes such as detect onboard fuel level, move
tail rudder and provide standard tow attachment point.
Definition:
A
Functional_breakdown_context
is a type of
Breakdown_context
that is an association of a
Functional_element
to a
Functional_breakdown
of which the functional element is a member.
EXAMPLE
A function 'provide load lifting capability' is member of the functional breakdown
of a helicopter.
Properties:
References:
Definition:
A
Functional_breakdown_version
is a type of
Breakdown_version
that identifies a version of a
Functional_breakdown
.
Properties:
References:
Definition:
A
Functional_element
is a type of
Breakdown_element
that identifies the elements in one or more
Functional_breakdown
objects.
Definition:
A
Functional_element_definition
is a type of
Breakdown_element_definition
that identifies a view of a version (
Functional_element_version
) of a
Functional_element
.
Properties:
References:
Definition:
A
Functional_element_usage is a type of
Breakdown_element_usage
that is an association of a functional element to another functional element that
is a constituent.
Functional_element.
Properties:
References:
Definition:
A
Functional_element_version
is a type of
Breakdown_element_version
that identifies a version of a
Functional_element
.
Properties:
References:
Definition:
Definition:
Definition:
A
Geometric_coordinate_space is a type of
Numerical_representation_context
that defines a coordinate space where geometric elements can be defined. It is either
two-dimensional or three-dimensional.
There shall be at least two units specified for the Geometric_coordinate_space: one length unit and one plane angle unit.
The length unit applies to each coordinate direction.
EXAMPLE
The length unit millimetre and the angle unit radian are examples of units that
may assigned to a Geometric_coordinate_space.
NOTE
The origin for coordinate values is implicitly defined as being the cartesian point
whose coordinates are all zero.
Properties:
Values:
the dimensionality of the geometric space.
Definition:
A Geometric_item_specific_usage is an identification of a
Detailed_geometric_model_element
within a
Geometric_model
or an
External_geometric_model
as being the element that describes a
Shape_element
or
Shape_element_relationship
of an
Item_shape
that is described by the
Geometric_model
or an
External_geometric_model.
EXAMPLE
In an application protocol, an instance of
Geometric_model
describes the
Item_shape
of a product.
One element of the
Geometric_model
- a curve
- represents the boundary of a hole that is a
Shape_element
in the product.
This entity data type may be used to state that the curve describes the hole, in
the context of the entire
Geometric_model
describing the shape of the product.
Properties:
References:
Values:
specifies a STRING value.
specifies additional information about the Geometric_item_specific_usage.
The value of this attribute need not be specified.
Definition:
A
Geometric_model is a type of
Representation
dedicated to the description of geometric constructs.
The Geometric_model is founded in a
Geometric_coordinate_space.
The items of a Geometric_model are instances of
Detailed_geometric_model_element.
Properties:
References:
Values:
the text that specifies the version identifier of the Geometric_model. The value of this attribute need not be specified.
the
length_measure
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
Geometric_coordinate_space
of the Geometric_model.
The value of this attribute need not be specified.
Definition:
A
Geometric_model_relationship is a type of
Representation_relationship.
Properties:
References:
Definition:
A
Geometric_model_relationship_with_transformation is a type of
Geometric_model_relationship.
A
Geometric_model_relationship_with_transformation may be a
Geometric_relationship_with_placement_transformation
or a
Geometric_relationship_with_operator_transformation
Definition:
A
Geometric_operator_transformation is a type of
Geometric_placement_operation.
Properties:
References:
Definition:
A
Geometric_placement is a type of
Geometric_placement_operation.
Properties:
References:
Definition:
A
Geometric_placement_model is a type of
Geometric_model.
Properties:
References:
Definition:
A
Geometric_placement_operation is a type of
Detailed_geometric_model_element.
A
Geometric_placement_operation may be a
Geometric_placement
or a
Geometric_operator_transformation.
Properties:
References:
Definition:
A
Geometric_relationship_with_operator_transformation is a type of
Geometric_model_relationship_with_transformation.
Properties:
References:
the
cartesian_transformation
that identifies the transformation for the
Geometric_relationship_with_operator_transformation.
Definition:
A
Geometric_relationship_with_placement_transformation is a type of
Geometric_model_relationship_with_transformation.
Properties:
References:
the
Axis_placement_mapping
that identifies the transformation for the
Geometric_relationship_with_placement_transformation.
Definition:
A
Global_location_representation is a type of
Location_representation specified using geographic means in the global system and values, which could be
physical or political geographic values.
Properties:
References:
specifies the height above sea-level of the location (
Length_unit).
The value of the attribute need not be specified.
the angular distance of a place north or south of the equator (
Plane_angle_unit).
the angular distance of a place east or west of the Greenwich meridian (
Plane_angle_unit).
Values:
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 detailled within refinements.
The value of the attribute need not be specified.
Definition:
A
Hardcopy is a type of
File that represents a non-digital document.
EXAMPLE
An actual stack of paper
consisting of one or more sheets, on which some product data is written,
printed or plotted.
Definition:
A Hierarchical_interface_connection is a type of
Interface_connection
that provides an interconnection between components at different levels
in an assembly. Each connection point in the assembly is represented by a
Interface_connector_occurrence.
EXAMPLE
An appliance such as a television has a power lead and attached plug.
The plug and power lead could be represented as an assembly
of parts such as the plug pins and wires.
Each connection point of the pins and wires in the assembly is
represented by a
Interface_connector_occurrence
and an instance of the
Hierarchical_interface_connection entity data
type identifies the connection of the pins (the parts) to the plug (the
assembly) in the assembly.
Definition:
An Identification_assignment is the assignment of an identifier to product or activity data.
Properties:
References:
the data to which the identification is assigned.
Values:
the text that conveys the assigned identifier.
the text that specifies the purpose of the association of the identification
with respect to the product or activity data it is granted to.
EXAMPLE
The value "inventory" may be used to assigned an inventory number to a product in
a warehouse.
the text that provides further information about the identification. The value of
this attribute need not be specified.
Definition:
A
Identification_relationship is a relationship between a pair of
Identification_assignments.
NOTE
This relationship may be classified in other modules to provide more specific meanings.
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:
the other instance of
Identification_assignment
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
In_zone
is a relationship between a
Zone_element
and an item that exists within the zone.
EXAMPLE
A pump is in the starboard engine room of a ship.
Properties:
References:
the item that exists in the zone.
the region in which the item exists.
Values:
an identifier for the relationship between the zone and the item in the zone.
the words by which the In_zone is known.
the text that provides further information about the relationship
between the zone and the item in the zone.
The value of this attribute need not be specified.
Definition:
A Increasing_resource_event is a type of
Resource_event
that increases the balance of a managed resource.
EXAMPLE
Purchasing new stock increases an inventory.
Definition:
An
Independent_property is a type of property.
NOTE
It is independent of its application to characterize a product or an activity.
EXAMPLE 1
The physical property kinematic viscosity, defined in ISO 31, is an example of Independent_property.
Properties:
Values:
a string that specifies the identifier of the Independent_property.
a string that specifies the type of the Independent_property.
EXAMPLE 2
'kinematic viscosity' is an example of property_type.
the
text that provides further information about the Independent_property.
The value of this attribute need not be specified.
Definition:
An
Independent_property_relationship is a relationship
between two instances of
Independent_property.
Properties:
References:
the other of the instances of
Independent_property
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.
Values:
the meaning of the relationship.
Where applicable, the following values shall be used:
the text that provides further information about the Independent_property_relationship.
The value of this attribute need not be specified.
Definition:
An
Independent_property_representation is a type of
Property_definition_representation.
An
Independent_property_representation is the association of an
Independent_property
with a
Representation.
Properties:
References:
Definition:
An Information_right 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 Information_right.
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:
Values:
an identifier for the right.
NOTE
The identifier should be unique, however there is no meaningful way of specifying
the scope over which it
is unique.
the word or words by which the right is known.
the text that provides further information about what the right allows the user to
do, and what is not
permitted.
The value of this attribute need not be specified.
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
Information_usage_right is an application an
Information_right to a particular usage context.
NOTE 1
One view of the distinction between an
Information_right and an
Information_usage_right
is that the
Information_right represents a standard clause in a contract, whereas an
Information_usage_right
represents the fact that the clause is used in a particular contract.
NOTE 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
Information_usage_right carries the meaning that the right
is granted to all information items in the relevant context, as opposed to the approval
of an
Applied_information_usage_right
which is limited to particular items.
NOTE 4
Information_usage_right provides a mechanism for recording significant rights within
a product database. The legal significance of the presence or absence of a right is
outside the scope
of this part of ISO 10303
Properties:
References:
Values:
the identifier of the Information_usage_right.
the word or words by which the Information_usage_right is known.
the additional information to be recorded about the
Information_usage_right.
The value of this attribute need not be specified.
Definition:
An
Information_usage_right_relationship is the relationship of one
Information_usage_right to another.
EXAMPLE
Where one
Information_usage_right supercedes another, then the original right is pointed to by the
relating
attribute, its replacement by the
related attribute, and the
relation_type attribute takes the value "supercedes".
Properties:
References:
Values:
a role that defines the behaviour of the relationship.
Definition:
A Interface_connection is an interconnection between a connected
pair of
Interface_connector_occurrences.
Each
Interface_connector_occurrence
represents the place where a product used in an assembly can interact
with other products in the assembly.
EXAMPLE
An appliance such as a television has a power lead and attached plug.
The plug and power lead could be represented as an assembly
of parts such as the plug pins and wires.
Each connection point of the pins and wires in the assembly is
represented by a
Interface_connector_occurrence
and an instance of the
Interface_connection entity data
type identifies the connection of the pins to the wires in the assembly.
Properties:
References:
the other instance of the connected pair of
Interface_connector_occurrences.
If one element of the relationship is dependent upon the other, this attribute shall
be the dependent one.
Values:
the identifier for the Interface_connection.
the text that provides further information about the Interface_connection.
The value of this attribute need not be specified.
the type of the connection.
Definition:
An Interface_connector is a type of
Product
that identifies a part of a product with which one or more other products
or the environment interacts.
NOTE
This is sometimes referred to as a "port".
EXAMPLE
A computer has a socket to which to connect a network cable. An instance of the Interface_connector entity data type identifies the role of the socket in the interface and is the subject
of a specification that defines the
necessary geometrical and electrical attributes to ensure a functioning interface
between the computer and network hardware.
Definition:
An
Interface_connector_as_planned is a type of
Interface_connector_version that identifies an individual that is the subject of a plan to realize an
Interface_connector.
EXAMPLE
Company Acme Limited is planning to produce an aircraft with serial number 1234 next
month. This aircraft has connectors
on each engine for fuel pipes. The company wishes to plan when each connector will
be realized and then identify a date on
which an inspector can test all the realized connectors.
Definition:
An
Interface_connector_as_realized is a type of
Interface_connector_version that identifies an individual that is a realized
Interface_connector.
EXAMPLE
Company WeFlySafest Corporation owns and operates an aircraft with serial number 1234.
When landing at Heathrow airport,
the pilot reports a loss of fuel pressure on engine number 4 with serial number A9876
and recommends that an inspector tests
the realized connector on the engine.
Definition:
An
Interface_connector_definition is a type of
Product_view_definition that identifies a view of an
Interface_connector.
EXAMPLE
A reliability engineer assesses the likely failure modes of design version 3.8 for
the connector between a brake unit and
the hydraulic control system. The engineer generates a set of data that is a specific
view of the connector. An instance
of the Interface_connector_definition entity data type collects these data together.
Properties:
References:
the item for which the Interface_connector_definition provides an interface capability.
Definition:
An
Interface_connector_design is a type of
Interface_connector_version that identifies a design version of an
Interface_connector.
EXAMPLE
BuildAWidget Incorporated creates design version 2.10 for an electrical supply connector.
Definition:
An
Interface_connector_design_to_planned
is a relationship between a design version of an
Interface_connector and a planned individual that is to conform to the design.
EXAMPLE
BuildAWidget Incorporated plans production of pump serial number 30301 with an electrical
supply connector that is to conform
to design version 2.10.
Properties:
References:
the version to which the planned individual will conform.
the individual that is to conform to the design version.
Values:
an identifier for the relationship between the design and the planned individual.
the words by which the relationship between the design and the planned
individual is known.
the text that provides further information about the relationship between
the design and the planned individual.
The value of the attribute need not be specified.
Definition:
An
Interface_connector_design_to_realized
is a relationship between a design version of an
Interface_connector and a realized individual that conforms to the design.
EXAMPLE
BuildAWidget Incorporated builds pump serial number 30301 with an electrical supply
connector that conforms to design version
2.11.
Properties:
References:
the version to which the realized individual conforms.
the individual that conforms to the design.
Values:
an identifier for the relationship between the design and the realized individual.
the words by which the relationship between the design and the realized
individual is known.
the text that provides further information about the relationship between
the design and the realized individual.
The value of the attribute need not be specified.
Definition:
A
Interface_connector_occurrence is an occurrence of a
Interface_connector_definition.
The
Interface_connector_occurrence represents the place where a
product used in an assembly can interact with other products in the
assembly. The interaction is represented by a
Interface_connection.
Properties:
References:
the item for which the Interface_connector_occurrence provides an interface capability.
Values:
the identifier for the Interface_connector_occurrence.
the words by which the Interface_connector_occurrence is known.
the text that provides further information about the Interface_connector_occurrence.
The value of this attribute need not be specified.
Definition:
An
Interface_connector_planned_to_realized
is a relationship between a realized individual of an
Interface_connector and a corresponding planned individual.
EXAMPLE
BuildAWidget Incorporated builds pump serial number 30302 with an electrical supply
connector that was previously planned.
Properties:
References:
the individual that relates to the realized individual.
the individual that relates to the planned individual.
Values:
an identifier for the relationship between the planned individual and the realized
individual.
the words by which the relationship between the planned individual and the
realized individual is known.
the text that provides further information about the relationship between the planned
individual
and the realized individual.
The value of the attribute need not be specified.
Definition:
An
Interface_connector_version is a type of
Product_version that identifies a version of an
Interface_connector.
Properties:
References:
Definition:
A
Interface_definition_connection is an interconnection between a connected
pair of
Interface_connector_definitions
or, if the point of interconnection is not specified, the interconnection
between a pair of views (
Product_view_definitions) on products
EXAMPLE
A socket in the wall provides access to the domestic electricity supply.
An appliance such as a television has a power lead and plug that fits into
the socket. An instance of the Interface_definition_connection entity data
type identifies this fitting of the plug into the socket.
Properties:
References:
Values:
the identifier for the Interface_definition_connection.
the text that provides further information about the Interface_definition_connection.
The value of this attribute need not be specified.
the type of the connection.
Definition:
An
Interface_definition_for is a relationship between an
Interface_specification and an item that conforms to the specification.
EXAMPLE
The infrared transmitter in a television remote control conforms to the specification
that has the identifier 2345/XYZ/001.
An instance of the Interface_definition_for entity data type is necessary to identify this relationship.
Properties:
References:
the specification that defines necessary attributes for the item that participates
in the interface.
the item that conforms to the interface specification.
Values:
an identifier for the relationship between the specification and the conforming item.
the words by which the relationship between the specification and the
conforming item is known.
the text that provides further information about the relationship between
the specification and the conforming item.
The value of the attribute need not be specified.
Definition:
An
Interface_specification is a type of
Product that provides a definition of necessary attributes for one or more items that participate
in an interface.
EXAMPLE
BSI develops a standard for connecting domestic electrical equipment to the electricity
supply.
Definition:
An
Interface_specification_definition is a type of
Product_view_definition that provides a view of an
Interface_specification.
EXAMPLE
When developing a BSI standard for connecting domestic electrical equipment to the
electricity supply, collected comments
from experts form a new view on a version of the standard.
Properties:
References:
Definition:
An
Interface_specification_version is a type of
Product_version that identifies a version of an
Interface_specification.
EXAMPLE
In 1999, BSI issues a new version of a standard for connecting domestic electrical
equipment to the electricity supply.
Properties:
References:
Definition:
An
Intersection is a relationship that is between:
- set R;
- and set of sets {Si},
that indicates set R consists of each thing that is a member of
each set within {Si}.
Properties:
References:
the set of sets that have the resultant as their intersection.
the set that consists of each thing that is a member of each set
within operand.
Values:
an identifier for the Intersection relationship.
the word or sequence of words by which the Intersection relationship
is referenced.
the text that provides further information about the Intersection relationship.
The value of the attribute need not be specified.
Definition:
An Item_assumed 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
Resource_item_assignment,
the location by a
Location,
and the existence of the facility at the location, by a
Location_assignment
assigning a location to the resource.
Properties:
References:
the item that is assumed to be true.
Definition:
An
Item_design_association is the association of a
Product_configuration with a
Product_view_definition or a
Product_version.
It specifies the
design that corresponds to the
Product_configuration.
If the design is a
Product_view_definition, the Item_design_association represents the statement that, in the considered definition context, the product
version, that is, the
Product_view_definition is a valid way to implement the
Product_configuration.
NOTE 1
This association might not be valid in all definition contexts of the product version.
If the design is a
Product_version, the Item_design_association represents the statement that, in all definition contexts, the
Product_version is a valid way to implement the
Product_configuration.
NOTE 2
The association might not be valid for other versions of the product.
Properties:
References:
Constraints:
Constraint: UR1Specification: (OCL2.0)
Item_design_association::allInstance()->isUnique(Sequence{configuration, design})
Definition:
An
Item_shape is the shape of a
shapeable_item.
Properties:
References:
specifies the role of the
shapeable_item
whose shape is the
Item_shape.
Values:
specifies the text that provides an identifier for the Item_shape. The value of this attribute need not be specified.
specifies the text that provides further information about the Item_shape. The value of this attribute need not be specified.
Definition:
An
Item_usage_effectivity is an effectivity domain that constrains the use of a product with or within another
product, in the context of a
Product_configuration.
The effectivity_domain attribute identifies a domain of effectivity.
The item_usage_relationship attribute identifies a relationship which characterizes the use of the product with
or within another product.
EXAMPLE
This relationship may be an assembly-component relationship or a make-from relationship.
The
resolved_configuration attribute identifies an association between a
Product_configuration and a product that implements it.
This attribute establishes the context in which the
item_usage_relationship is considered and constrained.
When the effectivity domain is a range of serial numbers, the serial numbers considered
are those of the
Product_configuration.
When the effectivity domain is defined using a production lot number, the production
lot considered is one of the
Product_configuration.
When the effectivity domain is an interval of time, the interval of time considered
is related to the production of the
Product_configuration.
Properties:
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:
Values:
the identifier for the Justification.
the word or group of words by which the Justification is referred.
The value of the attribute need not be specified.
the text that provides further information about the Justification.
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
Justification_assignment is the association between a
Justification
and the item for
which the
Justification
is provided.
EXAMPLE
The item can be an activity or a product design.
Properties:
References:
Values:
the text that provides further information about the Justification_assignment.
The value of the attribute need not be specified.
Definition:
A
Justification_relationship is an association between two
Justifications.
Properties:
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.
Values:
the word or group of words by which the Justification_relationship is referred.
the text that provides further information about the Justification_relationship.
The value of the attribute need not be specified.
Definition:
A
Justification_support_assignment is the association between a
Justification
and
the item providing evidential support for the
Justification
.
EXAMPLE
The support item can be the results from an analysis, a report, or
professional judgment.
Properties:
References:
Values:
the text that provides further information about the
Justification_support_assignment.
The value of the attribute need not be specified.
the function performed by the assigned support item.
Definition:
A Language is the identification of a language by its code as defined in ISO 639-2 and possibly
its country code as specified in ISO
3166-1.
Properties:
Values:
the string that specifies the identifier of the Language in the
Alpha-3 bibliographic code of ISO 639-2.
EXAMPLE 1
'eng' for English, 'fre' for French, 'rus' for Russian, or 'ger' for German are examples
of language_code.
the string that specifies the identifier of the country according to the alpha-2 code
of ISO 3166-1.
The value of this attribute need not be specified.
EXAMPLE 2
'GB' for the United Kingdom or 'US' for the United States of America are examples
of country_code.
Constraints:
Constraint: UR1Specification: (OCL2.0)
Language::allInstance()->isUnique(language_code)
Definition:
A
Language_indication is the identification of the
Language in which a text attribute of one or more instances has been specified.
NOTE
The
Language_indication entity data type identifies the primary language of a text attribute while the
Attribute_translation_assignment entity data type enables to
convey the translations of that attribute in various languages.
Properties:
References:
the instance for which the
Language of the
considered_attribute has been identified.
the
Language used to write the text attribute of the
considered_instance.
Values:
the name of the attribute the
Language of which has been identified.
All Supertype Blocks:
Unit
Definition:
A
Length_unit is a type of
Unit
in which distances are expressed.
Definition:
A Local_time is a point in time in a day, represented on a 24-hour clock
by hour, minute and second. It is expressed in the local time zone and the offset
from the Coordinate Universal Time shall be specified.
Properties:
References:
the offset applied from the Coordinated Universal Time.
The following formulas apply for the determination of the local time:
Values:
the number of hours.
the number of minutes. The value of this attribute need not be specified.
the number of seconds. The value of this attribute need not be specified.
Definition:
A Location is a place or position where an activity or event can occur or a product or resource
can exist.
Properties:
References:
specifies zero or more means of representing a location.
Values:
the word or group of words by which the location is known.
the text that provides further information about the location.
The value of the attribute need not be specified.
Definition:
A Location_assignment is a relationship between a product, event, or
person and a location. There may be distinct assignment for each
qualification. for example planned, scheduled or actual. Each assignment
may have a start and end date or time. A location may have multiple
assignments.
Properties:
References:
the item that is assigned to the specified location.
EXAMPLE 2
a product, person, product group,
event, or activity may have a location.
the location that is the subject of this assignment
Values:
the text that provides further information about the location assignment.
The value of the attribute need not be specified.
the possible functions of location assignments in
particular contexts.
The value of the attribute need not be specified.
EXAMPLE 1
Examples of roles of a location assignment are
- operating;
- storage;
- maintenance; and
- engineering.
Definition:
A
Location_relationship is a relationship between two locations.
EXAMPLE
Location B, which is in reference to location A or Location B (UK), which is a refinement
of Location A (Europe).
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.
Values:
the word or group of words by which the location relationship is known.
the text that provides further information about the location relationship.
The value of the attribute need not be specified.
Definition:
A Location_representation is a means of representing a location.
Definition:
A
Looping_element is a type of
Task_element.
It invokes a specified number of repetitions of a further
Task_element.
Properties:
References:
Definition:
A
Lot_effectivity is a type of
Effectivity for which the domain
of applicability is defined as a given batch of items.
Properties:
References:
the size of the batch of items.
Values:
the identification of the batch of items.
All Supertype Blocks:
Unit
Definition:
A
Luminous_intensity_unit is a type of
Unit
in which the brightness of a body is expressed.
Definition:
A
Make_from_relationship is a type of
View_definition_usage established between two instances of
Part_view_definition.
It specifies that, in the context of the definition of the relating part version,
the relating part version is considered
as resulting from the manufacturing transformation
of the related part version.
NOTE 1
The related part version may identify a raw material or a semi-finished part.
NOTE 2
The characteization of the process of transformation from the related part version
to the relating part version it out of
the scope of this application module.
Properties:
References:
the instance of
Part_view_definition that specifies a definition of the part version that results from the manufacturing
transformation.
the instance of
Part_view_definition that specifies a definition of the part version that is the input of the manufacturing
transformation.
the
Value_with_unit 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.
Values:
an integer that ranks the preference for use of the related part version among all
instances of
Make_from_relationship
that have the same value for the inherited
relating_view
attribute. This value is an integer that only has meaning when comparing it with corresponding
values for
Make_from_relationship sharing the same
relating_view. It is a relative ranking value,
not an absolute ranking. A lower value indicates a higher preference for the
related_view, and
a higher value indicates a lower preference. The value of this attribute need not
be specified.
Definition:
A Managed_resource is a representation of a resource that is provided with resource management capabilities.
The role
of a managed resource is determined by classification.
EXAMPLE
A managed resource can be classified as "Stock line".
Properties:
References:
the measure of the amount of the resource that is avaialable at a given
location.
The value of this attribute need not be specified.
Values:
the words by which the managed resource is known.
the text that provides further information about the managed resource. The value
of this attribute need not be specified.
Definition:
A Managed_resource_by_reference is a type of
Managed_resource
that is described in terms of an identifiable item (not referenced as a realization
of a
Resource_item)
which is provided with resource management capabilities.
Properties:
References:
a reference to an item that is provided with resource management capabilities.
Definition:
A Managed_resource_by_resource_item is a type of
Managed_resource
that is described in terms of an identifiable resource (within the application context)
which is provided with resource
management capabilities.
Properties:
References:
a reference to an identifiable
Resource_item (within the application context) that (when realized) will satisfy that requirement.
Definition:
A Managed_resource_relationship is an association between two managed resources. The meaning of the relationship
is determined by classification.
EXAMPLE
A managed resource relationship can be classified as "Alternative" or "Prefered".
Properties:
References:
the other instance of
Managed_resource
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.
Values:
the words by which the managed resource relationship is known.
the text that provides further information about the managed resource relationship.
The value of the attribute need not be
specified.
Definition:
A Market is the identification of a marketing segment for products.
Properties:
Values:
the words by which the market is known.
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.
All Supertype Blocks:
Unit
Definition:
A
Mass_unit is a type of
Unit
with which mass is expressed.
Definition:
A
Measure_item is a type of
Representation_item
that conveys the value of a quantity. Only specializations of this entity can be instantiated.
Definition:
A
Measure_item_with_precision is a type of
Measure_item that has a precision defined as the number of digits that are significant.
Properties:
Values:
the number of digits that are significant.
Definition:
A Measure_qualification 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:
References:
Values:
the words by which the Measure_qualification is known.
the text that provides further information about the Measure_qualification.
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:
References:
the actual contents of the Message or a reference to the contents.
the identification of who
(
Organization
or
Person_in_organization)
or what defined the message, that is, identified its purpose and contents.
The value of this attribute need not be specified.
Values:
the identifier of the message.
NOTE 2
The identifier should be unique.
the general purpose of the message, allowing it to be differentiated
from other types of message, and so be handled appropriately. The contents
of this entity are defined through reference data.
NOTE 3
The following gives an example of reference data for
message_type:
- field input - used to identify data acquired directly from the environment, for example,
on a maintenance engineer's palm
top;
- synchronization - used to indicate that the attached data has been changed in the
originator's data base, and should be used
to update the recipients database;
- action required - used to prompt the recipient to respond to the contents of the reports;
- urgent action required - as above, but with a high priority.
the text that specifies the purpose of the message.
The value of this attribute need not be specified.
NOTE 4
Using an analogy of e-mail, purpose is equivalent of the text of the message.
Definition:
A
Message_relationship is a link between two related messages. The meaning of the association depends on
Message_relationship.role.
EXAMPLE
If
id=2 replaces
id=1, then
Message_relationship.related points to
id=2 and
Message_relationship.relating points to
id=1 with
Message_relationship.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.
Values:
the role of the message association.
Definition:
A Name_assignment is an identification of a name used to designate
product data.
Properties:
References:
the things to which the name is assigned.
Values:
the word or words by which the product data is known.
the text that describes the purpose of the association of the
Name_assignment with product data.
Definition:
A
Next_assembly_usage is a type of
Assembly_component_relationship.
It establishes a relationship between a component and its immediate parent assembly
in a product structure.
Definition:
A
Numerical_document_property is a type of
Numerical_item_with_unit that specifies a numerical characteristic of a
Document_definition
or of a
File.
Properties:
References:
Definition:
A
Numerical_item_with_global_unit is a type of
Measure_item
where the value is expressed with respect to a unit provided as a global information
associated with the representation context.
Properties:
References:
the value of the quantity. The type of this value shall be consistent
with exactly one of the units globally assigned within the
Numerical_representation_context.
Definition:
A
Numerical_item_with_unit is a type of
Measure_item
that is also a
Value_with_unit.
The quantity value is therefore provided with its own unit.
Definition:
A
Numerical_representation_context is a type of
Representation_context
in which units and uncertainties may be defined.
These units and uncertainties apply to the instances of
Representation_item
that are used in that context.
Properties:
References:
the set of
Unit
that apply for attribute values of instances of
Representation_item
used in that context. The value of this attribute need not be specified.
NOTE
The
units
of
Numerical_representation_context is only intended to provide a default unit. Its use is not intended to prevent
representation items being specified with the same or different units to the context.
the uncertainty measures that apply on attribute values of instances of
Representation_item
used in that context. The value of this attribute need not be specified.
Definition:
An Observation is an historical record of something that has occured during the life of a product
or its support environment.
Its use is restricted to observations not directly represented in the data model,
and should not be used where some other
reporting data structure is defined.
Properties:
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
Product_as_realized.
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
Activity_actual
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
Activity_actual is the maintenance activity itself.
EXAMPLE 4
Aircraft health monitoring data is collected during a flight. The flight profile may
be recorded using the
Activity_actual.
NOTE 3
Some business rules may require that an observation is always made against an
Activity_actual, while others may not require that the activity be recorded.
Values:
an identifier for the Observation.
NOTE 1
The identifier should be unique over the set of virtual, extended and real enterprises
that may exchange observations. The
scope is defined by business rules outside the scope of this standard.
the word or group of words by which the Observation is known.
the text that provides further information about the Observation.
Definition:
An Observation_assignment 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.
Values:
the text that describes the purpose that
Observation_assignment plays in the link between the
Observation and any item that an observation can be made about, or any item that can be used
as part of the observation. .
Definition:
An Observation_consequence is an association of an
observation to the consequences that follow from it, where those
consequences
are in the form of a
Work_request.
NOTE 1
One of the uses of Observation_consequence is to close one of the feedback loops from the use of a product to requests for its
enhancements.
Properties:
References:
Values:
the identifier of the Observation_consequence.
the word or group of words by which the Observation_consequence is known.
the text that describes the purpose that
Observation_consequence plays in the link between the
Observation and the
Work_request it
raises.
NOTE 2
The roles played by Observation_consequence are defined though business rules, and may be identified through reference data.
Definition:
An Observation_relationship is a relationship between two
observations. The nature of this relationship is identified
by the role. Where there is a structural relationship between
Observation,
the semantics of the structure are identified by the classification of
the Observation_relationship against reference data.
EXAMPLE
The
Observation of a persistant fault is composed of a series of
Observation of occurances of the same fault. That is,
Observation_relationship.related points to the composite
Observation, while
Observation_relationship.relating points to one actual
Observation of the occurance. The
Observation_relationship.role of the relationship is "observed instance", while it is classified as "is composed
of".
In this example, the component
Observation will apply to
Product_as_realized and the consequence will be to rectify the individual faults,
while the composite
Observation will apply to a
Product_version and the consequence will be a design change.
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.
Values:
the text that specifies the purpose of the relationship.
Definition:
An
Observed_environment is a type of
Product
that represents a record of observations about the environment in which a
product is or has been operating.
Definition:
An Observed_environment_assignment 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
Observed_environment_to_definition is a relationship between a record of a set of observations about an
environment, represented by an
Observed_environment,
and a typical environment, represented by an
Environment_definition.
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
Observed_environment_to_definition_version is a relationship between a version
of the record of a set of observations about an
environment, represented by an
Observed_environment_version,
and a version of the typical environment, represented by
Environment_definition_version.
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
Observed_environment_to_definition_view is a relationship between a view
of the record of a set of observations about an
environment, represented by an
Observed_environment_view,
and a view of the typical environment, represented by
Environment_definition_view.
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
Observed_environment_version is a type of
Product_version
that identifies a particular version of an
Observed_environment.
Properties:
References:
Definition:
An
Observed_environment_view is a type of
Product_view_definition
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
Observed_environment_view_definition_relationship is a type of
View_definition_relationship
that represents an association between two
Observed_environment_view
objects.
Properties:
References:
Definition:
An
Or_state_cause_effect_definition is a type of
State_cause_effect_definition. It relates
one or more
State_definition entities that are causes to a
State_definition that is the effect.
At least one cause must exist prior to the effect.
Definition:
An Organization is an administrative structure in which persons are active.
Properties:
Values:
the
identifier that distinguishes the Organization. The value of this attribute need not be specified.
the words by which the Organization is known.
Definition:
An
Organization_based_location_representation is a type of
Location_representation that specifies a location in the context of an organization.
EXAMPLE
The location "Room 99" in "The Administration Building" of a particular university
might be represented using one instance
of
Organization_based_location_representation with two instances of
Organizational_location_identification and one instance of
Organization.
Properties:
References:
the organization in which the location identifier is meaningful.
Definition:
An Organization_or_person_in_organization_assignment is an
association of an organization or a person in an organization with activity or product
data.
Properties:
References:
the organization or person in organization that is to be associated with the activity
or product data.
the activity or product data to which the organization or person in an organization
is assigned.
Values:
the text that specifies the purpose of the association of an organization or a person
in an organization
with activity or product data.
Definition:
An
Organization_organization_type_relationship
is a relationship between an
Organization
organization and an
Organization_type.
Properties:
References:
Definition:
An
Organization_relationship is a relationship between two instances of
Organization.
EXAMPLE
A team belongs to a department which itself belongs to a company. Such an organizational
structure can be described up using
instances of Organization_relationship.
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.
Values:
the string that specifies the meaning of the relationship.
Where applicable the following values shall be used:
-
'hierarchy': The related Organization is a sub organization of the relating
Organization;
-
'legal succession': The related
Organization
is the legal successor of the relating
Organization;
-
'reorganization': The related
Organization
is the successor of the relating
Organization
due to an organizational transfer of responsibility.
the text that provides further information about the Organization_relationship.
The value of this attribute need not be specified.
Definition:
An
Organization_type 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:
Values:
the words by which the Organization_type is known.
the text that provides further information about the Organization_type.
The value of the attribute need not be specified.
Definition:
An Organizational_location_identification
is location that is defined by an identification which is specific in an organization
context.
Properties:
Values:
the text that characterizes the identification location.
EXAMPLE
compartment or building.
the value of organization based location identification.
Definition:
A Parameterized_distribution is a type of
Probability_distribution that is used to link a named probability distribution to the parameters that define
it.
NOTE 1
The
parameterization_name of this entity is used to discriminate between alternative parameterizations of the
same distribution.
NOTE 2
To calculate a value using a
Parameterized_distribution it is necessary to know the general distribution function, the value
of the distribution function parameters, and the specific random variable value for
which the probability evaluation is required.
The Probability Distribution module does not define the formula for the distribution
function, and it is assumed that this
is defined externally, either through reference
information or via a "formula" module. This entity provides the distribution function
parameters. The value of the random
variable for which the probability
is calculated is provided by the
Probability_derivation_parameter in the Probability module (see note 2).
Properties:
References:
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.
Values:
the name of the parameterization, distinguishing it from other parameterizations.
Definition:
A Part is a type of
Product
that collects the definitional information of the versions of either a
part or of a non-countable material.
NOTE 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.
Definition:
A
Part_version is a type of
Product_version
that identifies a version of a part. A
Part_version serves as the collector
of the data characterizing a realizable object in various application contexts.
NOTE
A
Part_version is expected to be functionally and physically interchangeable with the other versions
of the same
Part.
Properties:
References:
the
Part
of which the
Part_version specifies a version.
Definition:
A
Part_view_definition is a type of
Product_view_definition
that defines a characterization view of a version of a
Part.
Properties:
References:
the
Part_version
of which the
Part_view_definition defines a view.
Definition:
A
Partial_document_assignment is a type of
Document_assignment.
A
Partial_document_assignment identifies a specific portion of the
contents of a document. It assigns this portion to the product data for which it
is relevant.
Properties:
Values:
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:
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 prefix_titles.
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 suffix_titles.
Definition:
A
Person_in_organization is the identification of a
Person
and of his role in an
Organization
Properties:
References:
Values:
Definition:
A
Person_or_organization_or_person_in_organization_in_position
is a
Person,
Organization, or
Person_in_organization
that holds a
Position.
A person may hold more than one position within an organization or organizations.
EXAMPLE 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:
References:
Values:
Definition:
A
Person_or_organization_or_person_in_organization_in_position_relationship
is a relationship between one
Organization,
Person, or
Person_in_organization
and another.
Examples of the relationship are
EXAMPLE 1
successor
EXAMPLE 2
job-share
NOTE
The meaning of the relationship is determined by classification
Properties:
References:
the
other instance of
Organization,
Person, or
Person_in_organization
that participates in the relationship.
If one element of the relationship is dependent upon the other, this attribute shall
be the dependent one.
Values:
the words by which the relationship is known.
the text that provides further information about the relationship.
The value of the attribute need not be specified.
Definition:
A
Physical_breakdown is a type of
Breakdown
that identifies a partitioning of a product into a set of related physical
elements so as to form explicit, parent-child views that comprise the
product elements.
The parent-child view is represented by
Physical_element_usage
instances relating the physical elements in the breakdown which are represented
by
Physical_elements.
EXAMPLE
A physical breakdown might provide a decomposition of an
automobile in terms such as body, roof, bonnet, bumpers and this breakdown
might be differerent from, and orthogonal to, a parts decomposition.
Definition:
A
Physical_breakdown_context
is a type of
Breakdown_context
that is a membership relationship between a
Physical_element
and a
Physical_breakdown
of which the physical element is a member.
EXAMPLE
A wheel is a member of the physical breakdown of an automobile.
Properties:
References:
Definition:
A
Physical_breakdown_version
is a type of
Breakdown_version
that identifies a version of a
Physical_breakdown
.
EXAMPLE
An engineer modifies the current physical breakdown for an aircraft on the basis
of a tail re-design.
Properties:
References:
Definition:
A
Physical_document_definition is a type of
Document_definition.
A physical document definition may consist of one or many component hardcopy files.
EXAMPLE
Paper plots of technical drawings, micro fiche, or paper documents such as calculations
or test reports are examples of
Physical_document_definition.
Properties:
References:
the set of instances of
Hardcopy that form the physical document.
Definition:
A
Physical_element
is a type of
Breakdown_element
that identifies the elements in one or more
Physical_breakdown
objects.
Definition:
A
Physical_element_definition
is a type of
Breakdown_element_definition
that identifies a view of a version
(
Physical_element_version)
of a
Physical_element.
Properties:
References:
Definition:
A
Physical_element_usage
is a type of
Breakdown_element_usage
that is a relationship between a parent and child
Physical_element.
EXAMPLE
In a physical breakdown, the aircraft (parent) might include (as children) a fuselage,
wings, tail and undercarriage.
Properties:
References:
Definition:
A
Physical_element_version
is a type of
Breakdown_element_version
that identifies a version of a
Physical_element
.
EXAMPLE
An engineer changes the details describing the undercarriage that is an element
in a physical breakdown of an aircraft.
Properties:
References:
All Supertype Blocks:
Unit
Definition:
A
Plane_angle_unit is a type of
Unit
by which a angles in planes are expressed.
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:
References:
the
Address
of the position.
The value of the attribute need not be specified.
the position that is used by the organization.
Values:
the words by which the Position is known.
the text that provides further information about the Position.
The value of the attribute need not be specified.
Definition:
A
Position_assignment is an association of a
Position
with activity or product data.
Properties:
References:
the activity or product data to which the
Position
is assigned
the
Position
that is to be associated with the activity or product data.
the text that describes the purpose of which the
Position is operating with respect to the activity or product data
Definition:
A
Position_group is a group for collecting people in their positions to cooperate in an assignment.
EXAMPLE
People representing utility companies who cooperate with each other to coordinate
road works.
Properties:
Values:
the words by which the position group is known.
the text that provides further information about the Position_group.
The value of the attribute need not be specified.
Definition:
A
Position_group_assignment is an association of a
Position_group
with activity or product data.
Properties:
References:
the
Position_group
that is to be associated with the activity or product data.
the text that describes the purpose of which the
Position_group
is operating with respect to the activity or product data
Definition:
A Position_group_relationship 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
Position_group_role
is the role of a
Position_group
in an organization.
Properties:
Values:
the words by which the role is known.
the text that provides further information about the role.
The value of the attribute need not be specified.
Definition:
A
Position_position_type_assignment is an assignment of
Position_type
to a
Position.
It allows many positions to be described by many position types.
Properties:
References:
Definition:
A
Position_relationship is a relationship between
Positions.
Examples of relationships between
Positions
are
EXAMPLE 1
Superior / Subordinate
EXAMPLE 2
Superceded by
NOTE
The meaning of the relationship is determined by classification.
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.
Values:
the words by which the relationship is known.
the text that provides further information about the relationship.
The value of the attribute need not be specified.
Definition:
A
Position_role
is a role performed by the
Position.
Properties:
Values:
the words by which the role is known.
the text that provides further information about the role.
The value of the attribute need not be specified.
Definition:
A
Position_type 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:
References:
the
Type_of_person that serves as a defining example for the
Position_type.
Values:
the words by which the Position_type is known.
the text that provides further information about the
Position_type.
The value of the attribute need not be specified.
Definition:
A
Position_type_assignment is the association of a
Position_type
with activity or product data.
Properties:
References:
the activity or product data to which the
Position_type
is assigned.
the
Position_type
that is to be associated with the activity or product data.
the text that describes the purpose of which the type of position is operating with
respect to the activity or product
data
Definition:
A
Position_type_role is a role performed by the type of
Position.
Properties:
Values:
the words by which the role is known.
the text that provides further information about the role.
The value of the attribute need not be specified.
Definition:
A
Power_set is a relationship that is between:
and that indicates S
* is the set of all subsets of S.
Properties:
References:
the set that is the union of the derived.
the set of all subsets of the base.
Values:
an identifier for the Power_set relationship.
the word or sequence of words by which the Power_set relationship
is referenced.
the text that provides further information about the Power_set relationship.
The value of the attribute need not be specified.
Definition:
A
Pre_defined_type_qualifier is a type of
Type_qualifier
whose
name
has predefined value as specified in constant
pre_defined_type_qualifiers:
- '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.
Definition:
A Precision_qualifier is a specification of the number of significant digits in the representation of a
value.
Precision_qualifier shall be interpreted in accordance with Precision_qualifier 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:
Values:
specifies the number of significant digits of the value.
Definition:
A
Probability is a type of
Representation
that is a probability value (see definition 3.5.1 above).
Definition:
A Probability_by_name is a type of
Probability
whose value belongs to a one of a set of named classes,
rather than by assigning a specific numerical value, which may not be
available.
EXAMPLE
A safety assessment methodology classes the probability an accident as "very unlikely",
"unlikely", "significantly likely"
and
"almost certain". Any process that has a "very likely" or "almost certain" chance
of causing serious injury is shut down.
Properties:
References:
Definition:
A Probability_derivation_parameter is a type of
Numerical_item_with_global_unit
that is used by a
Probability_derived
in a particular role in order to calculate the particular probability.
EXAMPLE
In a coin tossing trial, the probability calculated is that of getting more than
6 heads
in ten tosses. The parameter with the role "minimum number of heads" will have the
value "6"
NOTE 1
The role name is given by the 'name' attribute
inherited from
Representation_item,
and the set of such names and their interpretation is defined through reference data.
NOTE 2
The value attribute, which holds the parameter value, is inherited from the supertype.
Definition:
A
Probability_derived is a type of
Probability_numeric
that associates a particular value of
Probability_numeric
with the source from which the value derived together with any parameters used to
get the particular value.
NOTE 1
Where the probability derived from a probability
distribution, the parameters of Probability_derived are those needed to get a single value from
the distibution, and not those which characterise the distribution. For example, in
the case of coin tossing,
the distribution is a Binomial distribution, with parameters of 'probability for a
single toss', and
'number of tosses', whereas the parameter for the Probability_derived will be the 'number of heads
obtained'.
Properties:
References:
the source from which the value derives.
NOTE 2
The possibile sources for values include a probability distribution, a statistic
or a reference document.
Definition:
A Probability_distribution is a type of
Probability_generator 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.
This module provides the description of the distribution of a particular experiment,
say, 10 tosses of a particular coin.
The actual probability of an outcome, say 6 heads in 10 tosses, is recorded using
the probability module.
NOTE 3
The attributes 'name', 'id' and 'description' are inherited from the supertype
Representation. The name provides a cue to the particular source of the distribution, such as "A
fair coin tossed 10 times",
rather than the type of distribution (in this case Binomial) which is given by the
Probability_distribution.distribution_name attribute.
Properties:
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 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.
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 Probability_distribution_parameter is a type of
Numerical_item_with_global_unit
that is one of the set of values that characterises a probability
distribution.
EXAMPLE
The Normal (or Gaussian) distribution has, in the standard parameterisation, two
parameters: the mean and the variance
NOTE 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
Probability_distribution_parameter inherits the
'name' attribute from its supertype, and this is used to identify the name
of the parameter within the particular parameterization. The value
attribute is also inherited.
Definition:
A Probability_function_value is a type of
Numerical_item_with_global_unit that is the value of the probability function at the given random variable value.
NOTE
The value is an inherited attribute. It is not in general a probability value. In
some functions for continuous distributions,
the probability that the random variable lies between two values is the integral of
the function of that range.
Definition:
A Probability_generator is a type of
Representation.
It is a source from the
Probability_derived
is derived. The
Probability_derivation_parameters
are applied to the Probability_generator 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 Probability_named_value is a type of
Representation_item
that is used to hold the name of the probability value.
NOTE
The value attribute is the description inherited from the supertype. In general, this
value will be one of an enumeration
of possible values defined through reference data.
Definition:
A
Probability_numeric is a type of
Probability
that is expressed as a numeric value between 0 and 1.
Properties:
References:
Definition:
A Probability_numeric_value is a type of
Numerical_item_with_global_unit
providing a numeric representation of a probability.
NOTE
The value attribute is inherited from the supertype.
Definition:
A
Probability_representation is a type of
Activity_property_representation
that associates the
Risk_event_probability property with its representation.
Properties:
References:
the attribute hold the probable event that can occur.
the attribute hold the representation of the probability of the event to occur.
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. The definition
of the domain of uniqueness and
the mechanism for guaranteeing the uniqueness of product id are outside the scope
of this application module.
NOTE 3
A product may have zero or more versions.
A version of a product is represented with an instance of the entity
Product_version or of one of its specializations.
Properties:
Values:
the
identifier that distinguishes the product.
NOTE 4
A particular codification for the values of this attribute may be specified in the
EXPRESS schemas that use or specialize
this entity, or in an agreement of common understanding between the partners sharing
this information.
EXAMPLE 3
Part numbers, stock item numbers, and serial numbers are examples of product identifiers.
the words by which the product is known. The value of this attribute need not be
specified.
the text that provides further information about the Product. The value of this attribute need not be specified.
Definition:
A Product_as_individual is a type of
Product
that identifies an individual artefact that has been made
or is planned to be made. It is a collector of data common to all
revisions of the Product_as_individual.
NOTE 2
Where physical products are being represented, the
Product_as_individual
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
Product_as_individual
and an associated revision represented by
Product_as_planned.
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.
Definition:
A
Product_as_individual_effectivity
is a type of
Effectivity
for which the domain of applicability is defined as a set of instances of
Product_as_individual.
Properties:
References:
Definition:
A Product_as_individual_version is a type of
Product_version.
It is a revision of a
Product_as_individual
and acts as a collector of the definitions of this revision.
EXAMPLE 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:
References:
Definition:
A Product_as_individual_view is a type of
Product_view_definition
that defines a characterization view of a version of a
Product_as_individual.
Properties:
References:
Definition:
A
Product_as_planned is a type of
Product_as_individual_version
that identifies a revision of an individual artefact that has yet to be made.
Definition:
A
Product_as_realized is a type of
Product_as_individual_version
that identifies a revision of an individual artefact that has been made.
A product whose properties can only be known by observation
or by derivation from observations.
NOTE 1
Where physical products are being represented, the
Product_as_realized
represents the physical product - something one can touch.
Definition:
A
Product_based_location_identification
is a type of
Location_representation that specifies a location in the context of a product.
EXAMPLE 1
Seat number M in the Aircraft.
Properties:
References:
the product that provides the context for the location specification.
Values:
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."
Definition:
A
Product_concept 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
Product_concept 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
Product_concept.
NOTE 2
The entity data type
Product_concept enables to represent customer-oriented identification of products that are to be
delivered to customers,
while the entity data type Product enables to identify and to track the history of
items that are designed and manufactured,
as a tangible solution, or component of the solution, for a product concept.
NOTE 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:
References:
Values:
the
identifier for the
Product_concept.
EXAMPLE 2
The id may be a sales model number.
the
text that provides further information about the
Product_concept.
The value of the attribute need not be specified.
Constraints:
Constraint: UR1Specification: (OCL2.0)
Product_concept::allInstance()->isUnique(id)
Definition:
A
Product_configuration is the identification of a
Product_concept as a configuration.
NOTE 1
The entity
Product_configuration corresponds to the concept of configuration item defined, in some configuration management
standards, as an item subject
to configuration management.
EXAMPLE
A
Product_configuration may represent a component of a contracted product, onto which severe safety rules
apply and for which configuration management
is therefore rigorously applied.
Properties:
References:
the
Product_concept that defines the context in which the configuration item has been defined.
the set of instances of the entity data type
Item_design_association
that identify products which provide a solution for the configuration item.
In this version of the application module, the cardinality of the set shall be not
higher than one.
Values:
the identification of the identifier that distinguishes the configuration item.
the words by which the configuration item is known.
the
text that provides further information about the Product_configuration. The value of the attribute need not be specified.
Definition:
A
Product_configuration_hierarchical_relationship is a type of
Product_configuration_relationship
that is used to represent a hierarchical relationship between a parent
Product_configuration
and a child
Product_configuration.
Definition:
A
Product_configuration_relationship is a relationship between a pair of
Product_configurations.
Properties:
References:
the other instance of
Product_configuration
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
Product_configuration_revision_sequence is a type of
Product_configuration_relationship
that is used to relate a previous version (predecessor) of a
Product_configuration
to the version that replaces it (successor).
Definition:
Properties:
References:
Values:
the identifier for the relationship between the breakdown item and the product item.
the word or words by which the relationship between the breakdown item and the product
item is known.
the text that provides further information about the
relationship between the breakdown item and the product item.
The value of this attribute need not be specified.
Definition:
A
Product_design_to_individual
is a relationship between a product design, represented by
Product,
and the product that is planned to be made
or has been made from the design, represented by
Product_as_individual.
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
Product_design_version_to_individual is a
relationship between a version of a product design, represented by
Product_version
or
Product_configuration,
and the product that is planned to be made (
Product_as_planned)
or has been made (
Product_as_realized)
from the design.
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
Product_design_view_to_individual
is a relationship between a product design, represented by
Product_view_definition.
or
Product_configuration,
and a view of the product that is planned to be made or has been made
(
Product_as_individual_view)
from the design.
Properties:
References:
Definition:
A
Product_group is an identification of a set of
Product_concepts,
Products,
Product_groups,
Product_versions or
Product_as_individuals
that have been grouped together.
EXAMPLE
All the aircraft sold to BigPlanes airways.
Properties:
Values:
the identifier that distinguishes the product group.
the text that provides further information about the characteristics which defines
this group.
The value of this attribute need not be specified.
the text that provides further information about the objectives of this
product group.
EXAMPLE 1
All individual products which are subject of a planned maintenance.
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
Product_group_membership is an identification of an instance of an entity defined in
the type
product_select
that belongs to a
Product_group.
Properties:
References:
Definition:
A
Product_group_relationship is a relationship between two
Product_groups.
Classification_assignment
is used to specify the meaning or type of the relationship.
NOTE
A subset is a common type of relationship. It indicates that one
Product_group
is a subset of another.
Properties:
References:
one of the instances of
Product_group that is a part of the relationship.
the other instance of
Product_group that is part of the relationship. If one element of the relationship is dependent
upon the other, this attribute shall be
the dependent one.
Values:
the text that provides further information about the Product_group_relationship.
The value of this attribute need not be specified.
the possible functions of a Product_group_relationship in particular contexts. The value of the attribute need not be specified.
Definition:
A
Product_in_attachment_slot is a type of
View_definition_usage
that
is a relationship between an
Attachment_slot
and a
Product_view_definition
of a
Product
that is designed to be attached to the attachment slot.
EXAMPLE
A long-range fuel tank is designed to be attached to an aircraft in an
attachment slot that corresponds to a pylon mounting on a wing.
Properties:
References:
Values:
the words by which the relationship between the attachment slot and the product is
known.
Definition:
A
Product_occurrence_definition_relationship is an occurrence relationship between two instances of
Product_view_definition.
Properties:
References:
the other instance of
Product_view_definition
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
Product_planned_to_realized
is a relationship that establishes that a revision of a planned artefact represented
by
Product_as_planned
has been realized as a revision of an actual artefact
Product_as_realized.
Properties:
References:
Definition:
A
Product_relationship is an association between two
Products.
Properties:
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.
Values:
the text that specifies the nature of the relationship between the instances of
Product
.
the text that provides further information about the
Product_relationship.
The value of this attribute need not be specified.
Definition:
A
Product_version is a revision of a
Product.
It is a collector of the definitions of this revision of the
Product.
NOTE
The set of all instances of
Product_version of the same
Product
represents the history of the product.
Properties:
References:
the
Product, the
Product_version identifies a version of.
Values:
the
identifier for the Product_version.
the text that provides further information about the Product_version.
The value of this attribute need not be specified.
Definition:
A
Product_version_relationship is an association between two versions of
Product.
Properties:
References:
the other instance of
Product_version
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.
Values:
Definition:
A
Product_view_definition is a characterization of a
Product_version,
relevant in one or more application domains and for one or more life cycle stages.
A Product_view_definition is a collector of the properties that characterize the
Product_version
in the initial_context and additional_contexts.
EXAMPLE 1
The design of the SS Titanic and the as-built description of the SS Titanic can
be represented as
two instances of Product_view_definition.
Properties:
References:
the
View_definition_context
in which the
defined_version
has been primarily characterized by the
Product_view_definition .
the
Product_version
of which the
Product_view_definition provides a characterization.
Values:
the identifier that distinguishes the Product_view_definition.
NOTE
The value of this attribute may be an empty string.
the words by which the Product_view_definition is known. The value of
this attribute need not be specified.
the text that provides further information about the Product_view_definition.
The value of this attribute need not be specified.
NOTE 2
This attribute may be used to precise the kind of definition.
EXAMPLE 2
In case the Product_view_definition characterizes a mating, this attribute may identify the kind of mating.
'clipping', 'welding' are examples of additional_characterization for a mating definition.
Definition:
A Project is an identified program of work.
Properties:
References:
the set of instances of
Organization
that specify the organizations that are responsible for the project.
Values:
the words by which the
Project is known.
the text that provides further information about the
Project. The value of this attribute need not be specified.
Definition:
A
Project_assignment is a mechanism to associate a
Project
with activity or product data.
Properties:
References:
the set of instances of entity types listed in
project_item, that are
associated with the
Project.
There shall exist at least one entity type listed in
project_item
for the
Project_assignment.
Values:
the text that specifies the meaning of the
Project with respect to the product or activity it is associated with.
When identifying the activities included in the work program of the project, the value
'work program' shall be assigned to
the role attribute.
Definition:
A
Project_relationship is an association between two instances of
Project with an identifiaction 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.
Values:
the text that specifies the meaning of the relationship.
Where applicable the following values shall be used:
- 'decomposition': The application object defines a relationship where
the related project is a component of the relating project;
- 'dependency': The completion of the related project depends upon the completion of
the relating project;
- 'sequence': The application object defines a relationship where
the relating project shall be completed before the related project starts;
- 'succession': The related project is the successor of the relating project.
the text that provides further information about the relationship.
The value of this attribute need not be specified.
Definition:
A
Promissory_usage
is a type of
Assembly_component_relationship.
It establishes a relationship between an assembly and a component, regardless of the
number of intermediate levels between
them, which may be established with instances of
Next_assembly_usage.
NOTE
A
Promissory_usage
may be used when the product structure is not completely defined, to capture the intent
that the constituent will
be used in that assembly.
Definition:
A
Proper_subset is a relationship that is between:
that indicates:
- each member of set A is also a member of set B; and
- set A does not equal set B.
Properties:
References:
the
Class
that contains only members of superset.
the
Class
that contains all members of subset.
Values:
an identifier for the Proper_subset relationship.
the word or sequence of words by which the Proper_subset
relationship is referenced.
the text that provides further information about the Proper_subset relationship.
The value of the attribute need not be specified.
Definition:
A
Property_definition_representation is an association between an
represented_definition
and one of its
Representations.
Properties:
References:
Values:
the text that provides further information about the Property_definition_representation. The value of this attribute need not be specified.
the string that specifies the role of the representation with respect to the property.
The value of this attribute need not
be specified.
EXAMPLE
'detailed representation', 'simplified representation' are examples of role.
Definition:
A
Property_representation is a type of
Property_definition_representation.
A
Property_representation is an association between an
Assigned_property
and one of its
Representations.
Properties:
References:
Definition:
A
Property_value_representation is a type of
Representation
that represents one or more quantity values.
NOTE
The present version of this application module does not enable to represent whether
the values have been imposed or were derived
or measured.
It is expected that a future version will add this capability.
Properties:
References:
Definition:
A Qualification_assignment 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 orgainization.
the person, organization or person in organization who has the qualification.
Definition:
A
Qualification_type 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:
Values:
the words by which the Qualification_type is known.
the text that provides further information about the Qualification_type.
The value of this attribute need not be specified.
Definition:
A
Qualification_type_relationship is an association between two
Qualification_types.
EXAMPLE 1
Qualification X is a pre-requisite for qualification Y.
EXAMPLE 2
Qualification X is equivalent to qualification Y.
Properties:
References:
the other instance
Qualification_types participating in the relationship.
If one element of the relationship is dependent
upon the other, this attribute shall be the dependent one.
Values:
the words by which the Qualification_type_relationship is known.
the text that provides further information about the Qualification_type_relationship
The value of this attribute need not be specified.
Definition:
A
Qualified_numerical_item_with_unit is a type of
Numerical_item_with_unit
and a type of
Qualified_representation_item
that specifies the type and uncertainty of a datum.
The uncertainty may be specified as precision, qualitative uncertainty, or expanded
uncertainty.
The uncertainty is defined in clause 2 of "The Guide to the Expression of Uncertainty
in Measurement".
Definition:
A
Qualified_representation_item is a type of
Representation_item
for which qualifiers are defined to describe its reliability and/or uncertainty.
Properties:
References:
specifies a role of the
value_qualifier
for the
Qualified_representation_item.
There shall exist one or more
value_qualifier
for the
Qualified_representation_item.
Definition:
A
Qualitative_uncertainty is a type of
Uncertainty_qualifier.
The uncertainty is defined in clause 2 of "The Guide to the Expression of Uncertainty
in Measurement".
Properties:
Values:
specifies a STRING for the Qualitative_uncertainty.
Definition:
A Random_variable is a type of
Numerical_item_with_global_unit
that is the value of a random variable.
NOTE
The value attribute is inherited from the supertype.
All Supertype Blocks:
Unit
Definition:
A
Ratio_unit is a type of
Unit
that expresses the dimensionless ratio of two quantities of the same kind.
Definition:
A Referenced_content_item is a means of linking to the actual content of a message.
Properties:
References:
the link to the actual contents of the
Message.
Definition:
A Regional_coordinate is a location that is specified relative to a Regional location system.
Properties:
References:
Values:
the word or group of words by which the grid system is known.
Definition:
A
Regional_grid_location_representation is a type of
Location_representation that specifies a reference grid system.
Properties:
Values:
the word or group of words by which the grid system is known.
the text that provides further information about the regional grid location representation.
The value of the attribute need not be specified.
Definition:
A
Related_condition_parameter is a relationship between a
Condition_parameter
and a
Condition_evaluation_parameter.
This relationship is used to record the relationship between the
parameters used to define a condition and the parameters used to evaluate
it.
EXAMPLE
The value of oil pressure (1.9 bar) used in
Condition_evaluation (instance 87) was
a measured value of the parameter used to define condition 29 (oil pressure
on gauge 3).
Properties:
References:
Values:
the words by which the Related_condition_parameter is known.
the text that provides further information about the
Related_condition_parameter.
The value of the attribute need not be specified.
Definition:
A
Related_consequence is a type of
View_definition_relationship
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.
All Supertype Blocks:
Event
Definition:
A
Relative_event is a type of
Event the start of which will occur, respectively has occurred, with a time offset from
the start of another
Event.
Properties:
References:
the
Event with respect which the relative event is based on.
the difference in time between the start of both events. A negative offset specifies
that the
Relative_event occurs before the
base_event.
Definition:
A
Repeat_count is a type of
Looping_element. It invokes a specified number of repetitions of the
repeated_element
Task_element
inherited from the
Looping_element supertype.
Properties:
Values:
the number of times the
repeated_element
is to be executed.
NOTE
If the
Repeat_count entity is combined with the other subtypes of
Looping_element, this becomes the maximum number of repetitions.
Definition:
A
Repeat_until is a type of
Looping_element.
It invokes repetitions of a further
Task_element
and is repeated until the specified condition is satisfied. The element being repeated
shall be executed at least once
and the condition tested after the first execution.
Properties:
References:
the criterion to be tested in order to determine that the looping method shall be
exited.
Definition:
A
Repeat_while is a type of
Looping_element.
It invokes repetitions of a further
Task_element
and is repeated while the specified condition is satisfied. The test condition shall
be evaluated prior to invoking the
method and may result in the
Looping_element
not being executed at all.
Properties:
References:
the criterion to be tested in order to determine that the
Looping_element
shall be continued.
Definition:
A
Representation is a collection of one or more instances of
Representation_item
that are related in the specified
Representation_context.
Properties:
References:
the Representation_context that specifies the context of the Representation.
Values:
the identifier for the Representation. The value of this attribute need not be specified.
the words by which the Representation is known.
EXAMPLE
The name of a Representation may be the name of a CAD model.
the text that provides further information about the Representation.
The value of this attribute need not be specified.
Definition:
A
Representation_context is a context in which instances of
Representation_item
are related.
Properties:
References:
Values:
the identifier for the Representation_context.
the text that describes the type of the context.
EXAMPLE 1
'numeric values' is an example of kind of Representation_context.
EXAMPLE 2
'2D space' or '3D space' are examples of kind which can be used for geometric representation
contexts.
Definition:
A
Representation_item is an element of representation.
A Representation_item shall be in the set of items of one or more instances of
Representation
or it shall belong to one or more instances of
Representation,
being referred to, directly of indirectly, by items of these instances of
Representation.
NOTE
this constraint is formally represented in the Express specification of the resource
entity that corresponds to Representation_item
in the MIM schema.
Only specializations of
Representation_item can be instantiated.
Properties:
Values:
the words by which the Representation_item is known.
EXAMPLE
The name of a geometric Representation_item may be its element tag in the originating CAD system.
Definition:
A
Representation_proxy_item is a type of
Representation_item that allows other constructs in the modules to act as representation items.
Properties:
References:
Definition:
A
Representation_relationship is an association between two instances of
Representation.
Properties:
References:
one of the instances of
Representation
that is a part of the relationship.
the other instance of
Representation
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.
Values:
the string that specifies the type of the relationship.
Where applicable, the following values shall be used:
the text that provides further information about the relationship.
Definition:
A Required_resource 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:
References:
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.
Values:
the words by which the required resource is known.
the text that provides further information about the required resource. The value
of this attribute need not be specified.
Definition:
A
Required_resource_assignment 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.using
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
Required_resource_by_reference is a type of
Required_resource
that is described in terms of an identifiable item (not referenced as a realization
of a
Resource_item) which will satisfy the requirement.
Properties:
References:
a reference to an item that satifies a resource requirement.
Definition:
A
Required_resource_by_requirement is a type of
Required_resource
that is described in terms of a specification of a type of item which will satisfy
the requirement.
Definition:
A
Required_resource_by_resource_item is a type of
Required_resource
that is described in terms of an identifiable resource (within the application context)
which will satisfy the requirement.
Properties:
References:
a reference to an identifiable
Resource_item (within the application context) that will satisfy that requirement.
EXAMPLE
Tool kit, facility, and product category are examples of resource items.
Definition:
A
Required_resource_relationship 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:
References:
the other instance of
Required_resource
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.
Values:
the words by which the relationship is known.
the text that provides further information about the relationship. The value of this
attribute need not be specified.
Definition:
A Required_resource_requirement is an association of a required resource with one or
more requirement version entities that fulfil the resource requirement.
Properties:
References:
Definition:
A
Requirement is a type 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
Alias_identification entity.
Definition:
A
Requirement_assignment is used to relate a requirement (via the
Requirement_view_definition entity) to data types representing the items
which are affected by the requirement.
EXAMPLE
A requirement "the vehicle shall have a maximum power output of at least 150BHP" could
be assigned to the data types
which are used to represent the vehicle's engine.
Properties:
References:
the item which has the requirement assigned to it.
Values:
an identifier that distinguishes the Requirement_assignment.
the text that provides further information about the Requirement_assignment.
The value of this attribute need not be specified.
Definition:
A
Requirement_collection_relationship
is a type of
View_definition_relationship
that is used to relate a parent (collection) requirement to its member requirements.
This provides a method for collecting
together a
set of requirements and treating them as a single requirement, whilst still being
able to refer to individual requirements.
Definition:
A
Requirement_satisfied_by is a relationship between an item (specified in
requirement_satisfaction_item) 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:
References:
the item that satisfies the requirement.
the requirement that is satisfied.
the
Requirement_assignment that is satisfied by the
Requirement_satisfied_by.
The value of this attribute need not be specified.
Values:
the identifier that distinguishes theRequirement_satisfied_by.
the text that provides further information about the
Requirement_satisfied_by.
The value of this attribute need not be specified.
Definition:
A
Requirement_source is a relationship between a requirement (via the
Requirement_view_definition entity) and the data types representing the source of the requirement
EXAMPLE
The source of the requirement "the vehicle shall have a maximum power output of at
least 150BHP" could be a document representing
the findings of a
market survey of sports car buyers.
Properties:
References:
the item which is the source of the requirement.
the requirement which is to be related to its source.
Values:
the identifier that distinguishes theRequirement_source.
the text that provides further information about the
Requirement_source.
The value of this attribute need not be specified.
Definition:
A
Requirement_version is a type of
Product_version
that identifies a particular version of a requirement.
NOTE
This entity is used to record different versions of a requirement. In
this case, the word "version" implies "revision"
- that is a particular release of a requirement.
EXAMPLE
A given requirement might have versions 1.0, 1.1, 1.2 and 2.0.
Properties:
References:
the
Requirement
for which the
Requirement_version identifies a version.
Definition:
A
Requirement_version_relationship is a type of
Product_version_relationship
that is used to relate a previous version (predecessor) of a requirement to the
version that replaces it (successor).
Properties:
References:
Definition:
A
Requirement_view_definition is a type of
Product_view_definition
that provides a view of a requirement version relevant for one or more application
domains. This view collects requirement data for specific engineering purposes.
EXAMPLE
An engineer may have responsibility for collecting all requirements associated
with the cooling
of an engine - covering engine block, tubing, water pump, electric fan.
Some requirements in a
Requirement_view_definition might impact on different disciplines.
Multiple
Requirement_view_definition objects may be used to present different views
of a given requirement for each discipline.
Properties:
References:
Definition:
A
Requirement_view_definition_relationship is a type of
View_definition_relationship.
A
Requirement_view_definition_relationship is the association between one
Requirement_view_definition and another.
Properties:
References:
Definition:
A
Resource_as_realized is a record of a resource that has been used or consumed.
EXAMPLE
A resource as realized can be classified as "Used" or "Consumed".
Properties:
References:
the amount of the Resource_as_realized 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.
Values:
the words by which Resource_as_realized is known.
the text that provides further information about the Resource_as_realized. The value of this attribute need not be specified.
Definition:
A Resource_as_realized_assignment is an association of a resource record statement with the
entity that used or consumed the resource.
The role of the assignment is determined by classification.
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 Resource_as_realized_by_reference is a type of
Resource_as_realized
that is described in terms of an identifiable item (not referenced as a realization
of a
Resource_item)
which is provided with resource management capabilities.
Properties:
References:
a reference to an item that is provided with resource management capabilities.
Definition:
A Resource_as_realized_by_resource_item is a type of
Resource_as_realized
that is described in terms of an identifiable resource (within the application context)
which is provided with resource
management capabilities.
Properties:
References:
a reference to an identifiable
Resource_item (within the application context) that realizes the resource.
EXAMPLE
person, tool kit, and facility are examples of items that may be a resource for some
activity or task.
Definition:
A Resource_as_realized_relationship is a relationship between
the record of used or consumed resources and the corresponding statement of
Required_resource.
EXAMPLE
"Alternative" and "Corresponding" are examples of classifications of resource as
realized relationship.
NOTE
A resource used or consumed can be recorded without having a corresponding resource
requirement statement.
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.
Values:
the words by which the Resource_as_realized_relationship is known.
the text that provides further information about the Resource_as_realized_relationship. The value of this attribute need not be specified.
Definition:
A
Resource_event is an event or action that affects the balance or availability of a managed resource.
The role of a resource event is determined
by classification.
EXAMPLE
A resource event can be classified as "Planned" or "Actual".
Properties:
References:
the measure of the amount of resource affected by the change.
The value of this attribute need not be specified.
the managed resource that is affected by the resource event.
Values:
the words by which the resource event is known.
the text that provides further information about the resource event. The value of
the attribute need not be specified.
Definition:
A
Resource_event_correspondence_relationship is an association of a resource event and a corresponding statement of
Required_resource. The meaning of the relationship is determined by classification.
NOTE
A resource event can be planned or recorded without having a corresponding resource
requirement statement.
EXAMPLE
A resource event correspondence relationship can be classified as "Designated for".
Properties:
References:
Values:
the words by which the Resource_event_correspondence_relationship is known.
the text that provides further information about the relationship. The value of this
attribute need not be specified.
Definition:
A
Resource_event_relationship is a specification of how an
Resource_event
may be associated with another
Resource_event. The meaning of the relationship is determined by classification.
EXAMPLE
A managed resource relationship can be classified as "realized by" or "replaces".
Properties:
References:
one of the instances of
Resource_event
that is a part of the relationship.
the other instance of
Resource_event
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.
Values:
the words by which the relationship is known.
the text that provides further information about the managed resource relationship.
The value of the attribute need not be
specified.
Definition:
A
Resource_group_relationship is a type of
Resource_item_relationship
that specifiies the means to associate two resource items that are part of a resource
group. The meaning of
the entity is determined by classification.
EXAMPLE 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:
References:
the measure of the amount of related
Resource_item. The value of the attribute need not be specified.
Definition:
A
Resource_item is an item that can occur in the role of a resource within the application context.
EXAMPLE
A Resource_item may be classified as "Facility", "Replaceble unit", or "Package".
Properties:
Values:
the words by which the Resource_item is known.
the text that provides further information about the Resource_item. The value of the attribute need not be specified.
Definition:
A Resource_item_assignment is an association of a resource
item with some product information. The role of the assignment is
determined by classification.
EXAMPLE
The assignment can be classified as "applicable to" or "acquired for".
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 Resource_item_realization 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:
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 Resource_item_relationship is a specification of how a resource item may be associated with another resource
item. The role of the relationship is
determined by classification.
EXAMPLE
The relationship between a product and a package can be classified as "Preferred".
Properties:
References:
one of the instances of
Resource_item
that is a part of the relationship.
the other instance of
Resource_item
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.
Values:
the word or words by which the Resource_item_relationship is known.
the text that provides further information about the resource item relationship. The
value of the attribute need not be specified.
Definition:
A
Resource_property is a property of a resource related object.
NOTE
The resource related object is specified in another module
Properties:
References:
the object of which the Resource_property identifies a characteristic.
Values:
the words by which the Resource_property is known.
the text that provides further information about the Resource_property.
Definition:
A
Resource_property_representation is an association between an
Resource_property
and one of its representations.
Properties:
References:
Values:
the text that provides further information about the Resource_property_representation.
The value of this attribute need not be specified.
the text that specifies the meaning of the representation with respect
to the property.
EXAMPLE
'numerical representation' and 'text representation' are examples of role.
Definition:
A
Risk is a type 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 occurance
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.
Definition:
A
Risk_attitude is a type of
Property_representation
and a factor that helps weigh the criticality of the
Risk_level.
NOTE
A negative number for the criticality factor means risk attractive and gives a concave
function if increasing,
a convex if decreasing. For a risk averse utility function the criticality factor
should be positive if the function is increasing, negative if decreasing utility.
The converse applies for risk attractive utility functions.
Properties:
References:
Definition:
A
Risk_consequence is a type of
Product_view_definition 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.
Properties:
References:
the version of the risk this is a consequence of.
Definition:
A
Risk_event is a type of
Applied_activity_method_assignment
that is the unwanted (or wanted) event.
Properties:
References:
a set of items that contains the various perceptions of the risk that this event will
trigger.
Definition:
An
Risk_event_probability is a type of
Activity_property
that describes the probability of the activity method identified as the risk event
occurring.
Properties:
References:
the activity method that the probability is assigned to.
Definition:
A
Risk_impact_assignment is an assignment between a
Risk_consequence
and a set of items that might be impacted by the risk.
Properties:
References:
assignement to the consequence
the items impacted by this consequence
Definition:
A
Risk_level is a type of
Assigned_property
that defines an identifiable goal or objective for the
Risk_perception.
Properties:
References:
Definition:
A
Risk_perception is a type of
Product_view_definition
and that defines values or concerns with which a stakeholder views a particular
Risk.
The context in which a
Risk_perception is made is represented by
Risk_perception_context.
NOTE 1
There is only one probability for each perceived risk. The probability for
something to happen does not vary depending on the consequences.
NOTE 2
Risk_perception depends on the stakeholder's expressed needs, issues, and knowledge.
NOTE 3
Risk_perception can differ from objective data.
NOTE 4
Risk_perception 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:
References:
the version of the risk this is a perception of.
Definition:
A
Risk_perception_context is a type of
View_definition_context
defining the context for describing the perception of the risk.
Definition:
A
Risk_perception_relationship is a type of
View_definition_relationship
and defines an association between two instances of
Risk_perception.
Properties:
References:
the first of the instances of
Risk_perception that is a part of the relationship.
the second of the instances of
Risk_perception that forms the relationship.
Definition:
A Risk_perception_source_assignment is an assignment of the set of items that are the source to the risk
Properties:
References:
the source to be assigned to
the items assigned to the risk perception.
Definition:
A
Risk_relationship is a type of
Product_relationship
and an association between two instances of
Risk.
Properties:
References:
Definition:
A
Risk_version is a type of
Product_version
Properties:
References:
Definition:
A Same_as_external_item is a statement that one or more data instances are the same as an item external to
the dataset.
NOTE
This capability is similar in nature to the
SameAs built-in property in
the
World Wide Web Consortium Web Ontology Language, available from their Web site.
SameAs indicates that two individuals or classes have the same 'identity'.
Properties:
References:
the source, external to the dataset, where the external item is defined or accessible.
the items in the dataset that are the same as the external item.
Values:
the identifier of the external item.
the description of the Same_as_external_item.
the role of the Same_as_external_item.
Definition:
A
Same_membership is a relationship that is between
that indicates the sets have the same members, that is they are
equal.
Properties:
References:
the class that contains the same members as set_2.
the class that contains the same members as set_1.
Values:
an identifier for the Same_membership relationship.
the word or sequence of words by which the Same_membership
relationship is referenced.
the text that provides further information about the Same_membership relationship.
The value of the attribute need not be specified.
Definition:
A
Scheme is a type of
Activity_method.
It provides the identification and description of an intended course of action to
accomplish an objective.
A
Scheme enables the ordering of entries.
Dates and times may be specified for entries and time intervals between entries.
NOTE
A Scheme may be classified as a Plan or Schedule, and it may be further classified
into specific types of Plans or Schedules.
EXAMPLE
Acquisition plan, Maintenance plan, Resource schedule are examples of schemes.
Definition:
A
Scheme_entry is a type of
Activity_method
that provides the identification and description of a single entry in a specific
Scheme.
NOTE 1
A Scheme_entry may be associated with time constraints.
NOTE 2
A
Scheme_entry only exists within the scope of a specific
Scheme.
Properties:
References:
the
Scheme into which the
Scheme_entry is included.
Definition:
A
Scheme_entry_assignment is a type of
Applied_activity_method_assignment.
It associates a
Scheme_entry
with one of more items.
NOTE
The
Scheme_entry_assignment links the single items included in Plans and Schedules with their associated
Scheme_entry.
These items may be actions, events, or tasks depending on the nature of the Plan
or Schedule.
Properties:
References:
Definition:
A
Scheme_entry_relationship is a type of
Activity_method_relationship.
It relates two
Scheme_entry entities.
An association may exists between
Scheme_entry
entities that relate to different
Scheme
or between different
Scheme_entry
entity instances for the same
Scheme.
NOTE
The Scheme_entry_relationship provides the ability to relate entries included in Plans or Schedules in different
ways. By applying classifications on the
Scheme_entry_relationship it can be used for different purposes.
EXAMPLE
Decomposition, Dependency, and sequencing are examples of kinds of relationships possible
between schema entries.
Properties:
References:
Definition:
A
Scheme_relationship is a type of
Activity_method_relationship
relating two
Schemes.
NOTE
The
Scheme_relationship
provides the ability to relate Plans or Schedules represented by the
Scheme
entity in different ways. If classifications are available to the schema using this
on, by applying classifications on the
Scheme_relationship it can be used for different purposes.
EXAMPLE
Decomposition, based-on, alternative, version are kinds of relationships between
Schemes.
Properties:
References:
Definition:
A
Scheme_subject_assignment is a type of
Applied_activity_method_assignment.
It associates a
Scheme
with a specific subject.
NOTE
The Scheme_subject_assignment links the Plans and Schedules with their associated subjects or targets.
This may indicate the intent of the scheme.
EXAMPLE
The maintenance plan for an individual vehicle,
where the subject attribute points to an entity instance
representing the individual vehicle.
Properties:
References:
the set of items to which a
Scheme is associated.
Definition:
A
Scheme_version is a type of
Activity_method. It enables version control of
Scheme.
Properties:
References:
the
Scheme that the entry is related to.
Definition:
A
Scheme_version_assignment is a type of
Applied_activity_method_assignment.
It associates a
Scheme
with a information describing the version.
NOTE
The role of the association may be defined through classification.
Properties:
References:
Definition:
A
Scheme_version_relationship is a type of
Activity_method_relationship
relating two
Scheme_versions.
NOTE
The meaning of the relationship may be defined through classification.
Properties:
References:
Definition:
A Security_classification is a level of confidentiality that can be applied to protect activity or product
data against unauthorized usage.
Properties:
Values:
the text that specifies the required degree of security.
the text that provides further information about the
Security_classification
.
The value of this attribute need not be specified.
Definition:
A
Security_classification_assignment is an association of a
Security_classification
with activity or product data.
Properties:
References:
Definition:
A
Selected_item is a type of
Class
used to classify identified product or activity data as being
significant for configuration management purposes.
EXAMPLE 1
Time Change/Shelf Life Selected Item (TCSI/SLSI)is an example of a selected item
- All items that
must be replaced at specific intervals or that have an elapsed time-related
shelf life, are designated as TCSIs or SLSIs, as appropriate. These items
do not require the rigorous, up-front CM activity (for example FCA/PCA but
rather, they concentrate on the post-delivery CM aspects related to
traceability in the field. This is commensurate with their emphasis on
being changed/replaced at certain times.
EXAMPLE 2
Maintenance Selected Item (MSI) is an example of a selected item - Certain items whose
maintenance
requirements dictate a more detailed traceability than normal items, may be
designated as MSIs. MSIs emphasize post-delivery traceability for
maintenance purposes.
EXAMPLE 3
Support Equipment Selected Item (SESI) is an example of a selected item - Certain
support equipment
items that require some additional traceability, but do not require
up-front CM activity are designated as SESIs. These items typically require
traceability by lot or batch, but not by individual item serial number.
Definition:
A
Selected_item_assignment
is the identification of the product or activity data referenced by
item
as being a
Selected_item.
Properties:
References:
the class of
Selected_item
to which the product or activity data referenced by
item
belongs.
the product or activity data that is being designated as a
Selected_item.
the context in which the product or activity data is being identified as
being a
Selected_item.
EXAMPLE
The engine is a identified as a selected item on the car.
Definition:
A
Sequence_of_state is a type of
State_relationship in which one set of
State precedes another set of
State.
Definition:
A
Sequence_of_state_definition is a type of
State_definition_relationship.
It defines a sequence of two or more state definitions.
Definition:
A Sequencing_relationship is a type of
Scheme_entry_relationship.
It defines a specific type of sequencing and relative timing for two
Scheme_entry.
NOTE 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
relating_entry
and the
related_entry.
The value of this attribute need not be specified.
NOTE 2
For a positive
time_lag, the
relating_entry
is the later entry in time.
Values:
the type of sequencing between the relating scheme entry and
related_entry
related scheme entry.
EXAMPLE
finish to start, start to start, finish to finish, start to finish.
Definition:
A
Serial_effectivity is a type of
Effectivity for which the domain
of applicability is defined as a possibly open-ended interval of serial numbers.
Properties:
Values:
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:
A
Shape_dependent_property_representation is the representation of a characteristic derived from or imposed to an
Item_shape
or a
Shape_element.
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 Shape_dependent_property_representation is independent of the representations of the shape.
NOTE 2
The present version of this application module does not enable to represent whether
the characteristics has been imposed or
was derived.
It is expected that a future version will add this capability.
Properties:
References:
the
Representation
that contains the items that express the characteristic.
NOTE
Depending on the
characteristic_type, the
described_element may need to be a
Geometric_model.
Values:
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 described_element, evaluated or required independently of any representation of the described_element;
- 'centroid': the characteristic is the centre of mass of a body as
evaluated from a geometric representation of the described_element;
- 'moment of inertia': the characteristic is the 3*3 matrix of inertia of the described_element;
- 'surface area': the characteristic is the extent of the surface of the described_element;
- 'volume': the characteristic is the volume of the described_element.
the text that provides further information about the Shape_dependent_property_representation. The value of this attribute need not be specified.
Definition:
A Shape_description_association is an association of a geometric representation with a shape characteristic.
Properties:
References:
Values:
the string that specifies the role of the representation with respect to
the property. The value of this attribute need not be specified.
EXAMPLE
'simplified representation', 'idealized representation' are examples of role.
the text that provides further information about the Shape_description_association. The value of this attribute need not be specified.
Definition:
A
Shape_element is a portion of a shape.
EXAMPLE
The threaded portion of the shape of a bolt may be represented as a Shape_element, so that other properties, such as surface finish, may be associated with it.
Properties:
References:
the
Item_shape that the
Shape_element is a part of.
Values:
the identifier that distiguishes the Shape_element. The value of this attribute need not be specified.
the name of the Shape_element. The value of this attribute need not be specified.
the text that provides further information about the Shape_element. The value of this attribute need not be specified.
Definition:
A
Shape_element_relationship is a relationship between two instances of
Shape_element.
Properties:
References:
one of the instances of
Shape_element that takes part in the relationship.
.
the other instance of
Shape_element that takes part in the relationship.
Values:
the string that specifies the type of the relationship. The value of this attribute
need not be specified.
the text that provides further information about the Shape_element_relationship. The value of this attribute need not be specified.
Definition:
A
Shape_placement_association is a type of
Shape_description_association.
Properties:
References:
Definition:
A
Simultaneous_elements is a type of
Concurrent_elements
that represents two or more actions to be performed together.
Definition:
A
Single_property_is_definition is a type of
Assigned_property
that identifies this property as being the
Product_view_definition
itself.
Any other property that is associated with the
Product_view_definition
is assumed to be a non-defining property, such as an annotation etc.
This allows direct represent the definition by assigning representations to this
property.
EXAMPLE
A single property is definition attached to a Requirement view definition would allow
us to provide multiple
representations of the same requirement view definition, such as the string representation
"weight must be 4Kg" and
a numeric representation "4Kg" specified as a value with units. Without this capability
we would only be
able to identify a text property representing the string and a weight property identifying
value with unit.
EXAMPLE
A single property is definition attached to an analysis view definition would allow
us to provide a representation
of that analysis view definition without having specific structures defined for all
possible analysis techniques
(a task much too large for STEP). For example a collection of scheme entry relationships
representing the
critical path of a critical path analysis for a scheme.
NOTE - This depends on the representation proxy item capability also defined in this
module.
Properties:
References:
Constraints:
Constraint: UR1Specification: (OCL2.0)
Single_property_is_definition::allInstance()->isUnique(described_element)
All Supertype Blocks:
Unit
Definition:
A
Solid_angle_unit is a type of
Unit
that is solid angle.
Definition:
A
Standard_uncertainty is a type of
Uncertainty_qualifier.
A
Standard_uncertainty may be an
Expanded_uncertainty.
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
Start_task is a type of
Task_element.
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.
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 object is currently in, a predicted
state that an object will
eventually be in, or an observed state that an object has been in.
NOTE 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:
Values:
the words by which the State is known.
the text that provides further information about the State.
The value of the attribute need not be specified.
Definition:
A
State_assertion is used to assert that the subject
State is in conformance with a particular
State_definition.
Properties:
References:
the subject
State being asserted.
Values:
the words by which the State_assertion is known.
the text that provides further information about the
State_assertion.
The value of the attribute need not be specified.
Definition:
A
State_assessment is used to determine whether the subject
State is comparable with a particular
State_definition.
Properties:
References:
Values:
the words by which the State_assessment is known.
the text that provides further information about the
State_assessment.
The value of the attribute need not be specified.
Definition:
A State_cause_effect is a type of state relationship and it relates two or more states as
one state causing particular resulting effect state(s). In turn, an effect state
can
become a new causing state yielding in yet more effect states.
Definition:
A
State_cause_effect_definition
is a type of
State_definition_relationship
that is used to define a causal relationship between two sets of
State_definition entities.
At least one
State_definition acts as a
cause
and at least one
State_definition acts as a
effect.
Definition:
A
State_complement_definition is a type of
State_definition_relationship.
It is a relationship among three sets of
State_definition entities.
It defines the complement of a set of
State_definition entities
relative to a set of
State_definition entities that are the universe.
NOTE 1
The semantics are the same as in elementary set theory.
NOTE 2
The relationship between a
State_definition and its complement is symmetrical.
Properties:
References:
the complement of set_1 within universe.
Definition:
A State_definition is a mode of being. In formal systems, a State_definition is the definition
of a situation during which some (usually implicit) invariant condition holds.
Properties:
Values:
the words by which the State_definition is known.
the text that provides further information about the State_definition. The value of this attribute need not be specified.
Definition:
A
State_definition_relationship is an association between two or more instances of
State_definition.
NOTE
Relationships between
State_definition entities may be used to support fault diagnosis.
Properties:
References:
the other of the instances of
State_definition
that is a part of the relationship.
Values:
the words by which the State_definition_relationship is known.
the text that provides further information about the State_definition_relationship. The value of this attribute need not be specified.
Definition:
A
State_definition_role is the purpose of the association of the
Applied_state_definition_assignment
with product or activity data.
Properties:
Values:
the words by which the State_definition_role is known.
the text that provides further information about the State_definition_role. The value of this attribute need not be specified.
All Supertype Blocks:
State
Definition:
A
State_observed is a type of
State.
It is an individual or realized
State that is observed.
All Supertype Blocks:
State
Definition:
A
State_predicted is a type of
State
It is a predicted actual
State. Where a predicted state needs to be related to an observed state,
the
State_predicted_to_observed entity
shall be used.
Definition:
A
State_predicted_to_observed is a type of state relationship. It specifies the relationship between two
individual states, one of which is a
State_predicted to a second state which is a
State_observed.
Properties:
References:
Definition:
A
State_proper_subset_definition is a type of
State_definition_relationship.
It is a relationship between two sets of
State_definition entities.
NOTE
The relationship between a state and its environment can be described as a State_proper_subset_definition. The identification of
an instrinsic state is the proper_subset. The identification of an extrinsic state is the proper_superset.
Definition:
A
State_relationship is a relationship between two or more
State.
Properties:
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.
Values:
the words by which the State_relationship is known.
the text that provides further information about the State_relationship.
The value of this attribute need not be specified.
Definition:
A
State_role is a specification of the purpose of the association of the
Applied_state_assignment with product or activity data.
Properties:
Values:
the words by which the State_role is known.
the text that provides further information about the State_role.
The value of the attribute need not be specified.
Definition:
A
State_subset_definition is a type of
State_definition_relationship.
It is a relationship between two sets of
State_definition entities.
NOTE
The first set may be equal to the second set.
Definition:
A
State_symptom_definition is a type of
State_definition_relationship.
It relates two or more
State_definition entities
in regards to symptom, where a symptom is something that indicates the existence of
something else.
At least one
State_definition acts as a
symptom_cause
and at least one
State_definition acts as a
symptom_effect.
Definition:
A
State_transition is a type of state relationship and it relates two or more states before and
after a transition in
State, where at least one
State is a start state and at least one
State
is an end state.
Definition:
A
State_transition_definition is a type of
State_definition_relationship.
It relates two or more
State_definition entities before and after
a transition in state, where at least one
State_definition is
a
start_state and at least one
State_definition is an
end_state.
Definition:
A
String_representation_item is a type of
Representation_item
that specifies a text.
Properties:
Values:
the string that is the element of representation.
Definition:
A
Structured_task_element is a type of
Task_element. It is made up of other
Task_elements
Definition:
A
Subset is a relationship that is between:
that indicates:
Properties:
References:
the class that contains only members of superset.
the class that contains all members of subset.
Values:
an identifier for the Subset relationship.
the word or sequence of words by which the Subset relationship is
referenced.
the text that provides further information about the Subset relationship.
The value of the attribute need not be specified.
Definition:
A
Supplied_part_relationship is a type of
Product_version_relationship
that relates two instances of
Product_version
that represent the same object in different organizational contexts.
One of the organizations is the supplier of the object to the other organization.
This entity is applicable for part versions and document versions.
NOTE 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 type of
Product
used to identify a conceptual solution to a collection of reqirements.
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 discernable by reproducable measurement
of its characteristics, and has a defined
boundary (statically and dynamically) with respect to the universe".
Definition:
A
System_breakdown is a type of
Breakdown
that identifies a partitioning of a system into a set of related
elements so as to form explicit, assembly - component views that comprise the
system elements.
The assembly-component view is represented by
System_element_usage
instances relating the system elements in the breakdown which are represented
by
System_elements.
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.
Definition:
A
System_breakdown_context is a type of
Breakdown_context
that is a membership relationship between a
System_element
and a
System_breakdown of which the system element is a member.
EXAMPLE
A heating system is a member of the breakdown of a climate control system.
Properties:
References:
Definition:
A
System_breakdown_version
is a type of
Breakdown_version
that identifies a version of a
System_breakdown
.
EXAMPLE
A logistics engineer modifies the current systems breakdown for an aircraft and
associated support equipment on the basis
of results from a
level of repair analysis.
Properties:
References:
Definition:
A
System_element
is a type of
Breakdown_element
that identifies the elements in one or more
System_breakdown
objects.
Definition:
A
System_element_definition
is a type of
Breakdown_element_definition
that identifies a view of a version
(
System_element_version)
of a
System_element.
EXAMPLE
The collision avoidance system element of a system breakdown is subject to a level
of repair analysis to support implementation
of optimized maintenance for an aircraft.
Properties:
References:
the
System_element_definition shall only be a view of a
System_element.
Definition:
A
System_element_usage
is a type of
Breakdown_element_usage
that is a relationship between a
System_element_definition
and another
System_element_definition
that is a constituent.
EXAMPLE
In a system breakdown, the fuel system might include a fuel storage system and
a fuel injection system as components.
Properties:
References:
Definition:
A
System_element_version
is a type of
Breakdown_element_version
that identifies a version of a
System_element
.
EXAMPLE
A sound engineer changes the details describing the public address system that
is an element in a system breakdown of an
aircraft.
Properties:
References:
the
System_element_version shall only be a version of a
System_element
.
Definition:
A
System_version is a type of
Product_version
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:
References:
Definition:
A
System_version_relationship is a type of
Product_version_relationship
used to relate versions of a system.
Properties:
References:
Definition:
A
System_version_sequence is a type of
System_version_relationship
used to relate a previous version of a system to the version that replaces it.
Definition:
A
System_view_definition is a type of
Product_view_definition
that provides a view of a system version relevant for one or more application domains.
Properties:
References:
Definition:
A
Task_element is a type of
Activity_method.
It is a representation of all or part of how to undertake a task.
Definition:
A
Task_element_assignment is a type of
Applied_activity_method_assignment.
It is an association of a
Task_element with product or activity data.
Properties:
References:
Definition:
A
Task_element_levels is a type of
Task_element
that provides two or more different descriptions in place of a single method. The
actual work will be the same whichever
alternative
Task_element
is followed.
NOTE
This can be used to provide defferent levels of description of a task for people with
varying levels of experience or expertise.
Properties:
References:
the
Task_elements describing two or more ways in which the same work may be undertaken.
Definition:
A
Task_element_relationship is a type of
Activity_method_relationship.
It relates two instances of
Task_element.
EXAMPLE
Can be used to capture a time dependency that cuts across the structure of the method.
Properties:
References:
one instance of
Task_element
that is a part of the relationship.
the other instance of
Task_element
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
Task_element_sequence is a type of
Task_element
that comprises a sequence of steps to be followed in a specified order.
Properties:
References:
the
Task_elements
to be followed in the order specified in the list.
Definition:
A
Task_element_state_relationship is an type of
Activity_method_relationship.
It is an association between a
State
or a
State_definition
and a
Task_element. The meaning of the entity is determined by classification. Candidate meanings include:
- assumed starting state;
- required starting state.
Properties:
References:
Definition:
A
Task_invocation is a type of
Task_element.
It is an instruction to perform another task.
EXAMPLE
A
Task_element
calls a pre-defined task to perform an instrument calibration.
Properties:
References:
Definition:
A
Task_method is a type of
Activity_method.
It is a specification of work.
NOTE
The task method may be implemented using people, machines or a combination.
Properties:
References:
the intended result or results of the task.
Definition:
A
Task_method_assignment is a type of
Applied_activity_method_assignment.
It is an association of a
Task_method with product or activity data.
Properties:
References:
the set of things that are associated to the
Task_method.
Definition:
A
Task_method_relationship is a type of
Activity_method_relationship. It relates two task methods.
NOTE
The nature of the relationship is determined from its classification.
Properties:
References:
one of the instances of
Task_method that is a part of the relationship.
the other instance of
Task_method 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 Task_method_state_relationship is a relationship between a state
and a
Task_method.
NOTE
The meaning of the entity is determined by classification. Candidate
meanings include:
- Assumed starting state;
- Required starting state.
Properties:
References:
the mode of being that is related.
Definition:
A
Task_method_version is a type of
Activity_method which allows the explicit reference to versions of a
Task_methodand to track changes against a
Task_method.
Properties:
References:
the way in which the task is to be carried out.
The value of this attribute need not be specified.
Definition:
A
Task_method_version_assignment is a type of
Applied_activity_method_assignment. It is an association of a
Task_method_version with product or activity data.
Properties:
References:
Definition:
A
Task_method_version_relationship is a type of
Activity_method_relationship. It relates two instances of
Task_method_version.
Properties:
References:
Definition:
A
Task_objective is a result or objective that is reached by undertaking a
Task_method.
NOTE
More than one
Task_method may be defined for a given objective, if there can be several ways to accomplish
the objective.
Properties:
Values:
the word or group of words by which the Task_objective is known.
the text that provides further information about the Task_objective.
Definition:
A
Task_objective_state_relationship
is a relationship between a state and a
Task_objective.
NOTE
The meaning of the entity is determined by classification. Candidate
meanings include:
- Intended finishing state;
- Alternative finishing state.
Properties:
References:
the mode of being that is related.
Definition:
A
Task_step is a type of
Task_element
that is not further sub-divided.
Properties:
Values:
All Supertype Blocks:
Unit
Definition:
A
Thermodynamic_temperature_unit is a type of
Unit
in which the degree of heat of a body is expressed.
Definition:
A Time_interval is the identification of an intervening time.
Properties:
Values:
the
text that provides further information about the
Time_interval.
The value of this attribute need not be specified.
Definition:
A
Time_interval_assignment is an association of a
Time_interval
with product data.
Properties:
References:
the instance of the
Time_interval entity data type that is associated with product data.
Definition:
A
Time_interval_effectivity is a type of
Effectivity for which the domain
of applicability is defined as a
Time_interval.
Properties:
References:
Definition:
A
Time_interval_relationship is the association of two instances of
Time_interval.
The meaning of this association is specified in the
relation_type attribute.
Properties:
References:
the first instance of
Time_interval that is part of the relationship.
the other instance of
Time_interval. If one element of the relationship
is dependent upon the other, this attribute shall be the dependent one.
Values:
the text that identifies the meaning of the relationship.
Definition:
A
Time_interval_role is a role for an
Time_interval_assignment and a description of that role.
Properties:
Values:
Definition:
A
Time_interval_with_bounds is a type of
Time_interval.
A
Time_interval_with_bounds is bounded either on one side or both sides.
If neither secondary_bound nor
Duration are specified,
the time interval begins at the point in time identified by primary_bound and
has no specified end point.
Properties:
References:
the bound of the Time_interval_with_bounds from which the length of the time interval is measured.
The value of this attribute need not be specified.
the other bound of the Time_interval_with_bounds.
The value of this attribute need not be specified.
the
Duration that specifies
the length of the time interval from the primary bound.
If positive, the Time_interval_with_bounds defines a lower bounded time interval, else an upper bounded
time interval.
The value of this attribute need not be specified.
Definition:
A Time_offset is an oriented offset from Coordinated Universal Time.
Properties:
Parts:
the direction of the offset.
Values:
the number of hours by which a time is offset from Coordinated Universal Time.
the
number of minutes by which a time is offset from Coordinated Universal Time.
The value of this attribute need not be specified.
All Supertype Blocks:
Unit
Definition:
A
Time_unit is a type of
Unit
with which the duration of a period is expressed.
Definition:
A
Tracing_relationship
is a type of
View_definition_relationship
that shows tracing from
(
traces_from)
one requirement to another
(
traces_to).
EXAMPLE
A requirement on the performance of a catalytic converter in a car may be traced from
a more general emissions requirement.
A requirement may trace to many other requirements and vice versa - this is achieved
by creating multiple instances of
the tracing
relationship entity.
NOTE 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
Type_of_person 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:
References:
the same Type_of_person can be described by many different
definitions.
EXAMPLE
has a degree or has 3 years experience
Values:
the words by which the Type_of_person is known.
the text that provides further information about the Type_of_person.
The value of this attribute need not be specified.
Definition:
A
Type_of_person_assignment is the association of a
Type_of_person
in a role with an activity or product data.
Properties:
References:
Values:
Definition:
A
Type_of_person_definition is the definition of a
Type_of_person
in terms of required properties or attributes.
EXAMPLE
A junior mechanical design engineer could be specified to be either someone who has
- 3 years experience of working in a mechanical design department, or
- a degree in mechanical engineering.
Properties:
Values:
the words by which the Type_of_person_definition is known.
the text that provides further information about the Type_of_person_definition.
The value of this attribute need not be specified.
Definition:
A
Type_of_person_definition_relationship is a relationship
between two definitions of a
type of person (
Type_of_person_definition).
EXAMPLE
"alternate" and "superceded by" are examples of Type_of_person_definition_relationships.
NOTE
The meaning of the relationship is determined by classification.
Properties:
References:
the other instance of
Type_of_person_definition
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.
Values:
the words by which the Type_of_person_definition_relationship is known.
the text that provides further information about
Type_of_person_definition_relationship.
The value of this attribute need not be specified.
Definition:
A
Type_of_person_definition_required_attributes_relationship is a relationship between a
Type_of_person_definition
and the attributes required to define that type of person.
EXAMPLE
The type of person "van driver" is required to possess the qualification named "commercial
driving license" or the experience
level "3 years of driving more than 10,000 miles per year".
Properties:
References:
the required attributes of a person.
EXAMPLE 1
Must have a degree
EXAMPLE 2
Must have 10 years experience
Definition:
A
Type_qualifier is the specification of the type of a datum.
A
Type_qualifier is a
Pre_defined_type_qualifier
or a specialization defined in another application module.
Properties:
Values:
the words by which the Type_qualifier is known.
Definition:
An
Uncertainty_qualifier is a supertype of a
Standard_uncertainty
or a
Qualitative_uncertainty.
The uncertainty is defined in clause 2 of "The Guide to the Expression of Uncertainty
in Measurement".
Properties:
Values:
specifies the STRING that serves to identify the Uncertainty_qualifier.
the text that provides further information about the Uncertainty_qualifier.
Definition:
An
Uncertainty_with_unit is a type of
Value_with_unit
that specifies the uncertainty that
applies to a type of measure. An
Uncertainty_with_unit applies to each
Representation_item
that uses the type of measure specified in the
value_component
of the
Uncertainty_with_unit.
Properties:
Values:
the words by which the Uncertainty_with_unit is known.
the
text that provides further information about the Uncertainty_with_unit. The value of this attribute need not be specified.
Definition:
A
Union is a relationship that is between:
- set R;
- and set of sets {Si},
that indicates set R consists of each thing that is a member of any
set within {S
i}.
Properties:
References:
the set of sets that have the resultant as their union.
the set that consists of each thing that is a member of any set
within operand.
Values:
an identifier for the Union relationship.
the word or sequence of words by which the Union relationship is
referenced.
the text that provides further information about the Union relationship.
The value of the attribute need not be specified.
Definition:
A Unit is a unit quantity.
Properties:
Parts:
the boolean value that indicates whether the Unit is one of the units defined in the SI system.
Values:
the words by which the Unit is known.
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
validated_by.
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:
References:
identifies the item which is been validated by this entity.
the collection of evidence used in this validation.
Definition:
A Value_function is a numerically defined function that describes the distribution function.
Properties:
References:
a single random variable/function value point on the function.
Definition:
A
Value_limit is a type of
Numerical_item_with_unit
and a type of
Qualified_representation_item
that specifies a qualified numerical value representing either the lower
limit or the upper limit of a particular quantifiable characteristic.
Properties:
References:
Definition:
A
Value_list is a type of
Measure_item
that is an ordered collection of
Measure_items.
EXAMPLE
A
Measure_item
may be composed of different values such as 'mass', 'speed', and 'age'
which are all necessary in a given context. The
Value_list
collects all of them in a given order, such that each is identifiable
by its index in the list.
Properties:
References:
the values.
Definition:
A
Value_range is a type of
Measure_item that is a pair of numbers representing the range in which the value shall lie.
Properties:
References:
the
lower limit.
the upper limit.
Definition:
A
Value_range_with_global_unit is a type of
Measure_item that is a pair of numerical values representing the range in which the value shall
lie. The unit of measure is globally
assigned.
Properties:
References:
the lower limit.
the upper limit.
Definition:
A
Value_set is a type of
Measure_item
that is an unordered collection of
Measure_items.
EXAMPLE
A
Measure_item
may be composed of different values such as 'mass', 'speed', and 'age'
which are all necessary in a given context. The
Value_set
collects all of them in a given order, such that each is identifiable
by its index in the list.
Properties:
References:
the values.
Definition:
A
Value_with_tolerances is a type of
Measure_item that specifies a range of values by specifying a single nominal value and two tolerances
that are offsets from the single
value. The range is defined to be the closed interval [item value + lower limit, item
value + upper limit].
Properties:
References:
specifies
the single value that is the base value for specifying the range.
Values:
the lower limit of the range.
the upper limit of the rhange.
Definition:
A Value_with_unit is the specification of a physical quantity by its value and its unit.
Properties:
References:
the
Unit
with which the physical quantity is expressed.
the value of the quantity.
Definition:
A
Verification is an objective assertion of a claim that requirement is satisfied by a particular
item represented in a
Requirement_satisfied_by has been verified. The evidence used in this verification is identified by the inverse
attribute
verified_by.
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:
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
Verification_relationship is an association between two verifications.
NOTE
This relationship may be classified in other modules to provide more specific meanings.
Properties:
References:
the first verification in this relationship.
the other verification in this relationship.
Definition:
A
View_definition_context is the grouping of an application domain and a life cycle stage.
It identifies a universe of discourse suitable for the description of products.
NOTE
Requirements and vocabularies vary among the industrial activity fields. This entity
intends to identify such a domain.
Properties:
Values:
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 application_domain is an empty string, the View_definition_context 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 life_cycle_stage is an empty string, the View_definition_context shall be considered as not specific of any life cycle stage.
the text that provides further information about the View_definition_context.
The value of this attribute need not be specified.
Definition:
A
View_definition_relationship is an association between two instances of
Product_view_definition.
This association represents a relationship between the product versions, indirectly
identified by the instances of
Product_view_definition, relevant in the definition contexts of the
related instances of
Product_view_definition.
Properties:
References:
the other instance of
Product_view_definition
that is part of the relationship.
If one element of the relationship is dependent upon the other, this attribute shall
be the
dependent one.
Values:
the identifier for the View_definition_relationship.
The value of this attribute need not be specified.
the meaning of the relationship.
The value of this attribute need not be specified.
In particular, this attribute is not required in subtypes of this entity.
the text that provides further information about the View_definition_relationship.
The value of this attribute need not be specified.
Definition:
A
View_definition_usage is a type of
View_definition_relationship
that specifies a directed
association between two instances of
Product_view_definition.
This association represents a relationship stating that, in the definition contexts
of the related
instances of
Product_view_definition, it is considered that the related product is used in the context of the relating
product.
Definition:
A Work_order is an authoritative instrument which provides directions to achieve
the specified results.
A Work_order is the authorization for one or more
Activity objects to be performed.
Properties:
References:
the set of zero, one or more instances of
Work_request that
defines the expected results.
Values:
the words by which the Work_order is known.
the text that provides further information about the Work_order.
The value of this attribute need not be specified.
Definition:
A
Work_output is a statement of output resulting from an activity or a task.
The role of the work output is determined by classification.
EXAMPLE 1
When applicable a work output may be classified as
- "Planned";
- "Actual";
- "By-product";
- "Waste product".
Properties:
References:
the amount of output resulting from the associated activity or task.
The value of this attribute need not be specified.
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.
Values:
the words by which the Work_output is known.
the text that provides further information about the Work_output.
The value of this attribute need not be specified.
Definition:
A Work_output_assignment is an association of a work output statement with the
source that produces or delivers the output. The work output can be planned as well
as actual.
The role of the assignment is determined by classification.
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
Work_output_relationship is a relationship between two work output statements. The meaning of the relationship
is determined by classification.
EXAMPLE
A Work_output_relationship is classified as "realized
by"
.
Properties:
References:
one of the instances of
Work_output that is a part of the relationship.
the other instance of
Work_output 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.
Values:
the words by which the Work_output_relationship is known.
the text that provides further information about the Work_output_relationship.
The value of this attribute need not be specified.
Definition:
A
Work_request is the solicitation for some work to be done.
NOTE
These requests may not be acted upon depending
on the authorization granted to the request or its associated
Work_order.
Properties:
Values:
the identification that distinguishes the Work_request.
the
text that provides further information about the Work_request.
The value of this attribute need not be specified.
EXAMPLE
This attribute may contain a description of the issue that was the origin of the request.
the
text that describes the reason for the activity request.
EXAMPLE
'technical improvement',
'government regulation', 'durability improvement', 'tool improvement', 'production
relief', 'production
requirement', 'quality improvement', 'security reason', 'standardization', 'cost reduction',
'customer rejection' in case
the request results from a rejection by a customer,
'change of standard', 'production alignment', and 'procurement alignment' are examples
of purpose.
Definition:
A
Work_request_status is an association of a status with
a
Work_request.
NOTE
A
Work_request may have zero or more statuses, assigned at various dates by various organizations.
Properties:
References:
Values:
the text that provides a user interpretable designation for the level of completion
of the study and resolution of the work request.
EXAMPLE
'drafted', 'issued', 'deferred', 'in-hand', 'completed', 'cancelled', 'rejected' are
examples of request status.
Definition:
An
Xor_state_cause_effect_definition is a type of
State_cause_effect_definition.
It relates one of the single or many causing state definition(s) and one effect
State_definition,
whereby any and only one of the causing state definitions exists prior to the single
effect to take place.
Definition:
A
Zone_breakdown is a type of
Breakdown
that identifies a partitioning of a product into a set of related zonal
elements so as to form explicit, parent-child views that comprise the
product elements.
The parent-child view is represented by
Zone_element_usage
instances relating the zonal elements in the breakdown which are represented
by
Zone_elements.
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'.
Definition:
A
Zone_breakdown_context is a type of
Breakdown_context
that is a membership relationship between a
Zone_element
and a
Zone_breakdown
of which the zonal element is a member.
EXAMPLE
A 'fire-check zone' might be a member of the zonal breakdown of a building.
Properties:
References:
Definition:
A
Zone_breakdown_version
is a type of
Breakdown_version
that identifies a version of a
Zone_breakdown
.
EXAMPLE
An architect modifies the current fire-check zone breakdown for an building on
the basis of reports from a
buildings inspector.
Properties:
References:
the
Zone_breakdown_version shall only be a version of a
Zone_breakdown
.
Definition:
A
Zone_element
is a type of
Breakdown_element
that identifies the elements in one or more
Zone_breakdown
objects.
EXAMPLE
'Empennage', 'Right vertical stabilizer and rudder' and 'Lower rudder' are all
elements in a zonal breakdown
of an aircraft.
Definition:
A
Zone_element_definition
is a type of
Breakdown_element_definition
that identifies a view of a version
(
Zone_element_version)
of a
Zone_element.
EXAMPLE
For an aircraft, an element 'Right vertical stabilizer tip' is in a zonal breakdown
that an engineer uses for
reliability-centred maintenance analysis.
Properties:
References:
the
Zone_element_definition shall only be a view of a
Zone_element.
Definition:
A
Zone_element_usage
is a type of
Breakdown_element_usage
that is a relationship between a parent and child
Zone_element.
EXAMPLE
In a zonal breakdown, the 'wing' (parent) might include (as children) an 'inner wing'
and an 'outer wing'.
Properties:
References:
Definition:
A
Zone_element_version
is a type of
Breakdown_element_version
that identifies a version of a
Zone_element.
EXAMPLE
An engineer defines an inspection task on a breakdown element 'Upper rudder' that
is part of a zonal breakdown
of an aircraft. The engineer identifies the corresponding view of the breakdown
element.
Properties:
References:
the
Zone_element_version shall only be a version of a
Zone_element
.
Definition:
The
measure_value type is an extensible list of alternate data types that allows
for the designation of the data types
any_number_value,
any_string_value,
length_measure and
plane_angle_measure.