AP scope | AP module | AP contents | AP index | |
Application module: Scheme | ISO/TS 10303-1260:2004(E) © ISO |
This clause specifies the information requirements for the Scheme 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.
The following EXPRESS specification begins the Scheme_arm schema and identifies the necessary external references.
EXPRESS specification:
*)
SCHEMA Scheme_arm;
(*
The following EXPRESS interface statements specify the elements imported from the ARMs of other application modules.
EXPRESS specification:
*)
USE FROM
Activity_method_arm;
--
ISO/TS 10303-1049
USE FROM
Activity_method_assignment_arm;
--
ISO/TS 10303-1249
USE FROM
Date_time_assignment_arm;
--
ISO/TS 10303-1014
USE FROM
Person_organization_assignment_arm;
--
ISO/TS 10303-1013
USE FROM
Time_interval_arm;
--
ISO/TS 10303-1065
(*
NOTE 1 The schemas referenced above are specified in the following part of ISO 10303:
Activity_method_arm ISO/TS 10303-1049 Activity_method_assignment_arm ISO/TS 10303-1249 Date_time_assignment_arm ISO/TS 10303-1014 Person_organization_assignment_arm ISO/TS 10303-1013 Time_interval_arm ISO/TS 10303-1065
NOTE 2 See Annex C, Figures C.1, C.2and C.3 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 scheme_date_or_date_time_item type is an extension of the date_or_date_time_item type. It adds the data type Scheme_entry to the list of alternate data types.
EXPRESS specification:
*)
TYPE
scheme_date_or_date_time_item =
SELECT
BASED_ON
date_or_date_time_item
WITH
(Scheme_entry);
END_TYPE;
(*
The scheme_entry_item_select type is an extension of the activity_method_item type.
NOTE The list of entity data types may be extended in application modules that use the constructs of this module.
EXPRESS specification:
*)
TYPE
scheme_entry_item_select =
EXTENSIBLE
GENERIC_ENTITY
SELECT
BASED_ON
activity_method_item;
END_TYPE;
(*
The scheme_person_organization_select type is an extension of the organization_or_person_in_organization_item type. It adds the data types Scheme and Scheme_entry to the list of alternate data types.
EXPRESS specification:
*)
TYPE
scheme_person_organization_select =
SELECT
BASED_ON
organization_or_person_in_organization_item
WITH
(Scheme,
Scheme_entry);
END_TYPE;
(*
The scheme_subject_select type is an extension of the activity_method_item type.
NOTE The list of entity data types may be extended in application modules that use the constructs of this module.
EXPRESS specification:
*)
TYPE
scheme_subject_select =
EXTENSIBLE
GENERIC_ENTITY
SELECT
BASED_ON
activity_method_item;
END_TYPE;
(*
The scheme_version_select type is an extension of the activity_method_item type.
NOTE The list of entity data types may be extended in application modules that use the constructs of this module.
EXPRESS specification:
*)
TYPE
scheme_version_select =
EXTENSIBLE
GENERIC_ENTITY
SELECT
BASED_ON
activity_method_item;
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.
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.
EXPRESS specification:
*)
ENTITY Scheme
SUBTYPE OF (Activity_method);
END_ENTITY;
(*
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.
EXPRESS specification:
*)
ENTITY Scheme_entry
SUBTYPE OF (Activity_method);
scheme : Scheme_version;
END_ENTITY;
(*
Attribute definitions:
scheme: the Scheme into which the Scheme_entry is included.
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.
EXPRESS specification:
*)
ENTITY Scheme_entry_assignment
SUBTYPE OF (Applied_activity_method_assignment);
SELF\Applied_activity_method_assignment.assigned_activity_method RENAMED assigned_entry : Scheme_entry;
SELF\Applied_activity_method_assignment.items : SET[1:?] OF scheme_entry_item_select;
END_ENTITY;
(*
Attribute definitions:
assigned_entry: the Scheme_entry being assigned.
items: the set of items which are associated with a Scheme_entry.
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.
EXPRESS specification:
*)
ENTITY Scheme_entry_relationship
SUBTYPE OF (Activity_method_relationship);
SELF\Activity_method_relationship.relating_method RENAMED relating_entry : Scheme_entry;
SELF\Activity_method_relationship.related_method RENAMED related_entry : Scheme_entry;
END_ENTITY;
(*
Attribute definitions:
relating_entry: one of the instances of Scheme_entry that is a part of the relationship.
related_entry: the other instance of Scheme_entry 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.
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.
EXPRESS specification:
*)
ENTITY Scheme_relationship
SUBTYPE OF (Activity_method_relationship);
SELF\Activity_method_relationship.relating_method RENAMED relating_scheme : Scheme;
SELF\Activity_method_relationship.related_method RENAMED related_scheme : Scheme;
END_ENTITY;
(*
Attribute definitions:
relating_scheme: one of the instances of Scheme that is a part of the relationship.
related_scheme: the other instance of Scheme 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.
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.
EXPRESS specification:
*)
ENTITY Scheme_subject_assignment
SUBTYPE OF (Applied_activity_method_assignment);
SELF\Applied_activity_method_assignment.assigned_activity_method RENAMED assigned_scheme : Scheme;
SELF\Applied_activity_method_assignment.items : SET[1:?] OF scheme_subject_select;
END_ENTITY;
(*
Attribute definitions:
assigned_scheme: the Scheme which is being associated to a subject.
items: the set of items to which a Scheme is associated.
EXPRESS specification:
*)
ENTITY Scheme_version
SUBTYPE OF (Activity_method);
of_scheme : Scheme;
END_ENTITY;
(*
Attribute definitions:
of_scheme: the Scheme that the entry is related to.
NOTE The role of the association may be defined through classification.
EXPRESS specification:
*)
ENTITY Scheme_version_assignment
SUBTYPE OF (Applied_activity_method_assignment);
SELF\Applied_activity_method_assignment.assigned_activity_method RENAMED assigned_scheme_version : Scheme_version;
SELF\Applied_activity_method_assignment.items : SET[1:?] OF scheme_version_select;
END_ENTITY;
(*
Attribute definitions:
assigned_scheme_version: the Scheme_version which is being associated to the items.
items: the set of items to which a Scheme_version is associated.
NOTE The meaning of the relationship may be defined through classification.
EXPRESS specification:
*)
ENTITY Scheme_version_relationship
SUBTYPE OF (Activity_method_relationship);
SELF\Activity_method_relationship.relating_method RENAMED relating_scheme_version : Scheme_version;
SELF\Activity_method_relationship.related_method RENAMED related_scheme_version : Scheme_version;
END_ENTITY;
(*
Attribute definitions:
relating_scheme_version: one of the instances of Scheme_version that is a part of the relationship.
related_scheme_version: the other instance of Scheme_version 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.
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.
EXPRESS specification:
*)
ENTITY Sequencing_relationship
SUBTYPE OF (Scheme_entry_relationship);
sequencing_type : STRING;
time_lag :
OPTIONAL
Time_interval;
END_ENTITY;
(*
Attribute definitions:
sequencing_type: 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.
time_lag: 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.
*)
END_SCHEMA; -- Scheme_arm
(*
© ISO 2004 — All rights reserved