|
|
Application module:
Observation |
ISO/TS 10303-1258:2011-10(E)
© ISO
|
This clause specifies the information requirements for the
Observation
application module. The information requirements are specified as the
Application Reference Model (ARM) of this application module.
NOTE 1 A graphical representation of the information
requirements is given in
Annex C.
NOTE 2 The mapping specification is specified in
5.1. It shows how
the information requirements are met by using common resources and
constructs defined or imported in the MIM schema of this application
module.
This clause defines the information requirements to which implementations shall
conform using the EXPRESS language as defined in ISO 10303-11.
The following begins the
Observation_arm
schema and identifies the necessary external references.
EXPRESS specification:
*)
SCHEMA Observation_arm;
(*
The following EXPRESS interface statements specify the elements
imported from the ARMs of other application modules.
EXPRESS specification:
*)
USE FROM
Activity_arm;
--
ISO/TS 10303-1047
USE FROM
Activity_as_realized_arm;
--
ISO/TS 10303-1259
USE FROM
Classification_assignment_arm;
--
ISO/TS 10303-1114
USE FROM
Management_resource_information_arm;
--
ISO/TS 10303-1288
USE FROM
Product_as_individual_arm;
--
ISO/TS 10303-1164
USE FROM
Work_order_arm;
--
ISO/TS 10303-1043
USE FROM
Work_request_arm;
--
ISO/TS 10303-1042
(*
NOTE 1
The schemas referenced above are specified in the following
part of ISO 10303:
| Activity_arm |
ISO/TS 10303-1047 |
| Activity_as_realized_arm |
ISO/TS 10303-1259 |
| Classification_assignment_arm |
ISO/TS 10303-1114 |
| Management_resource_information_arm |
ISO/TS 10303-1288 |
| Product_as_individual_arm |
ISO/TS 10303-1164 |
| Work_order_arm |
ISO/TS 10303-1043 |
| Work_request_arm |
ISO/TS 10303-1042 |
NOTE 2
See Annex C,
Figures
C.1and C.2
for a graphical representation of this schema.
This subclause specifies the ARM types
for this application module. The ARM types and
definitions are specified below.
The observation_approval type is an extension
of the
mri_approval_item type.
It adds the data
type
Observation
to the list of alternate data types.
It allows one or more approvals to be applied to an Observation.
EXPRESS specification:
*)
TYPE
observation_approval =
SELECT
BASED_ON
mri_approval_item
WITH
(Observation);
END_TYPE;
(*
The observation_classification_item type is an extension
of the
classification_item type.
It adds the data
types
Observation
and
Observation_relationship
to the list of alternate data types.
NOTE
The classification of Observation_relationship can be used to identify structures of Observations, through the use of the
classification "is composed of". Such classifications are defined through reference data.
EXPRESS specification:
*)
TYPE
observation_classification_item =
SELECT
BASED_ON
classification_item
WITH
(Observation,
Observation_relationship);
END_TYPE;
(*
The observation_consequence_item type is an
extensible list of alternate data types
that allows for the designation of the data
types
Activity, Work_order
and
Work_request.
NOTE
The list of entity data types may be
extended in application modules that use the constructs of
this module.
EXPRESS specification:
*)
TYPE
observation_consequence_item =
EXTENSIBLE
GENERIC_ENTITY
SELECT
(Activity,
Work_order,
Work_request);
END_TYPE;
(*
The observation_date_time type is an extension
of the
mri_date_or_date_time_item type.
It adds the data
type
Observation
to the list of alternate data types.
EXPRESS specification:
*)
TYPE
observation_date_time =
SELECT
BASED_ON
mri_date_or_date_time_item
WITH
(Observation);
END_TYPE;
(*
The observation_item type is an
extensible list of alternate data types.
Additional alternate data types are specified in select data
types that extend the
observation_item type.
NOTE
This empty extensible select requires
extension in a further module to ensure that entities that refer to it have
at least one valid instantiation.
EXPRESS specification:
*)
TYPE
observation_item =
EXTENSIBLE
GENERIC_ENTITY
SELECT;
END_TYPE;
(*
The observation_recorder type is an
extensible list of alternate data types
that allows for the designation of the data
type
Product_as_realized.
NOTE
The list of entity data types may be
extended in application modules that use the constructs of
this module.
observation_recorder points to the entity instances that can be identified as recording observational information.
By default, this is an identifiable piece of equipment, represented through a
Product_as_realized.
The list of entities may be extended through a higher level module.
EXPRESS specification:
*)
TYPE
observation_recorder =
EXTENSIBLE
SELECT
(Product_as_realized);
END_TYPE;
(*
The observed_context type is an
extensible list of alternate data types.
Additional alternate data types are specified in select data
types that extend the
observed_context type.
NOTE
This empty extensible select requires
extension in a further module to ensure that entities that refer to it have
at least one valid instantiation.
The observed_context links to entity instances that define the context in which the observation is made.
The entity data types that may be used to define the context are defined in a higher level module that uses this one.
EXPRESS specification:
*)
TYPE
observed_context =
EXTENSIBLE
SELECT;
END_TYPE;
(*
The observing_person type is an extension
of the
mri_organization_or_person_in_organization_item type.
It adds the data
type
Observation
to the list of alternate data types.
observing_person allows a person or person in organization to be associated to the Observation.
NOTE
The role of the person is noted in the role.
The usual role will be that of "observer".
EXPRESS specification:
*)
TYPE
observing_person =
SELECT
BASED_ON
mri_organization_or_person_in_organization_item
WITH
(Observation);
END_TYPE;
(*
This subclause specifies the ARM entities for this
module. Each ARM application entity is an atomic element that
embodies a unique application concept and contains attributes
specifying the data elements of the entity. The ARM
entities and definitions are specified below.
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.
EXPRESS specification:
*)
ENTITY Observation;
id : STRING;
name : STRING;
description : STRING;
in_context : SET[0:?] OF observed_context;
observed_by : SET[0:?] OF observation_recorder;
observed_during :
OPTIONAL
Activity_actual;
END_ENTITY;
(*
Attribute definitions:
id:
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.
name:
the word or group of words by which the Observation is known.
description:
the text that provides further information about the Observation.
in_context:
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.
observed_by:
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).
observed_during:
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.
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.
EXPRESS specification:
*)
ENTITY Observation_assignment;
assigned_observation : Observation;
item : observation_item;
role : STRING;
END_ENTITY;
(*
Attribute definitions:
assigned_observation:
the Observation that applies to or is relevant to the assigned item.
item:
any item that an observation can be made about, or any item that can be used as part of the observation.
role:
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. .
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.
EXPRESS specification:
*)
ENTITY Observation_consequence;
id : STRING;
name : STRING;
inferred_from : Observation;
requests : observation_consequence_item;
role : STRING;
END_ENTITY;
(*
Attribute definitions:
id:
the identifier of the Observation_consequence.
name:
the word or group of words by which the Observation_consequence is known.
inferred_from:
the Observation that leads to the consequence.
requests:
the Work_request that the consequence entails.
role:
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.
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
Observations,
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 Observations 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.
EXPRESS specification:
*)
ENTITY Observation_relationship;
relating : Observation;
related : Observation;
role : STRING;
END_ENTITY;
(*
Attribute definitions:
relating:
one instance of Observation that is a part of the relationship.
related:
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.
role:
the text that specifies the purpose of the relationship.
*)
END_SCHEMA; -- Observation_arm
(*
© ISO 2011 — All rights reserved
