|
|
Application module:
Effectivity |
ISO/TS 10303-1057:2014-02(E)
© ISO
|
This clause specifies the information requirements for the
Effectivity
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
Effectivity_arm
schema and identifies the necessary external references.
EXPRESS specification:
*)
SCHEMA Effectivity_arm;
(*
The following EXPRESS interface statements specify the elements
imported from the ARMs of other application modules.
EXPRESS specification:
*)
USE FROM
Time_interval_arm;
--
ISO/TS 10303-1065
USE FROM
Value_with_unit_arm;
--
ISO/TS 10303-1054
(*
NOTE 1
The schemas referenced above are specified in the following
part of ISO 10303:
| Time_interval_arm |
ISO/TS 10303-1065 |
| Value_with_unit_arm |
ISO/TS 10303-1054 |
NOTE 2
See Annex C,
Figures
C.1and C.2
for a graphical representation of this schema.
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.
A Dated_effectivity is a type of Effectivity for which the domain of
applicability is defined as an interval of time bounded by dates or events.
The interval may be open-ended.
EXAMPLE
Events may be used to bound a Dated_effectivity period, at planning phase.
Depending on whether the 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.
EXPRESS specification:
*)
ENTITY Dated_effectivity
SUBTYPE OF (Effectivity);
start_bound :
OPTIONAL
date_or_event;
end_bound :
OPTIONAL
date_or_event;
WHERE
WR1: EXISTS(start_bound) OR EXISTS(end_bound);
END_ENTITY;
(*
Attribute definitions:
start_bound:
the date or event that defines the lower bound of the interval of applicability.
end_bound:
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.
Formal propositions:
WR1:
At least either the start_bound or the end_bound shall be specified.
An Effectivity is the identification of a domain of applicability.
NOTE
Instances of Effectivity may be applied to any kind of product or activity data, using the constructs defined in the
Effectivity application module.
EXPRESS specification:
*)
ENTITY Effectivity
SUPERTYPE OF (ONEOF (Serial_effectivity,
Dated_effectivity,
Lot_effectivity,
Time_interval_effectivity));
id : STRING;
name : STRING;
description :
OPTIONAL
STRING;
END_ENTITY;
(*
Attribute definitions:
id:
the identifier that distinguishes the Effectivity.
name:
the
words by which the Effectivity is known.
description:
the text that provides further information about the Effectivity.
The value of the attribute need not be specified.
An Effectivity_relationship is an association between two instances of Effectivity.
The meaning of the relationship is represented with the relation_type attribute.
EXPRESS specification:
*)
ENTITY Effectivity_relationship;
relation_type : STRING;
description :
OPTIONAL
STRING;
relating_effectivity : Effectivity;
related_effectivity : Effectivity;
END_ENTITY;
(*
Attribute definitions:
relation_type:
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.
description:
the text that provides further information about the relationship.
The value of the attribute need not be specified.
relating_effectivity:
the first of the related instances of Effectivity.
related_effectivity:
the second of the related instances of Effectivity.
A Lot_effectivity is a type of Effectivity for which the domain
of applicability is defined as a given batch of items.
EXPRESS specification:
*)
ENTITY Lot_effectivity
SUBTYPE OF (Effectivity);
lot_id : STRING;
lot_size : Value_with_unit;
END_ENTITY;
(*
Attribute definitions:
lot_id:
the identification of the batch of items.
lot_size:
the size of the batch of items.
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.
EXPRESS specification:
*)
ENTITY Serial_effectivity
SUBTYPE OF (Effectivity);
start_id : STRING;
end_id :
OPTIONAL
STRING;
END_ENTITY;
(*
Attribute definitions:
start_id:
the first valid serial number.
end_id:
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.
A Time_interval_effectivity is a type of Effectivity for which the domain
of applicability is defined as a Time_interval.
EXPRESS specification:
*)
ENTITY Time_interval_effectivity
SUBTYPE OF (Effectivity);
effectivity_period : Time_interval;
END_ENTITY;
(*
Attribute definitions:
effectivity_period:
the Time_interval that defines the domain of validity.
*)
END_SCHEMA; -- Effectivity_arm
(*
© ISO 2014 — All rights reserved
