ГОСТ Р 55346—2012
(* The child specifies the component Physical element in the Physical_reference_relationship. *)
child: physical_instance_reference;
(* The mirror_of specifies the Physical_composition_relationship (or which the Physical_reference_relationship provides
the unambiguous reference. *)
mirror_of: physical_composition_relationship;
(* The parent specifies the decomposed Physical_instance_reference in the Physical_reference_relationship. *)
parent: physical_instance_reference;
(* The valid_configuration specifies the Physical_reference_configuration for which the parent and child PhysicalJn-
stance_reference are valid. *)
vaiid_configuration: physical_re(erence_configuration;
END_ENTITY;
(*A Pkis_minus_bounds is the specification of the allowable deviation from a numerical value applied to a Nominal_vaI-
ue. *)
ENTITY plus_minus_bounds;
(* The distribution_function specifies a mathematical function describing the projected distribution of measurement
values.’)
distributionJunction : OPTIONAL textual_specifrcation;
(* The limited_value specifies the Nominal_value further defined by the Plus_minus_bound. ")
limited_value: nominal_value:
(* The lowerbound specifies the value of the tolerance that shall be subtracted from the exact value to establish the
minimum allowed value. *)
lowerbound : NUMBER;
(* The significant_digits specifies the number of decimal digits indicating the accuracy of the lower bound and upper
bound values. *)
significant_digits ; OPTIONAL INTEGER;
(* The upper_bound specifies the value of the tolerance that shall be added to the exact value to establish the maxi
mum allowed vaiue. *)
upper_bound ; NUMBER;
END_ENTITY;
(’ A Project is an identified programme of work. <note>A Project may be further characterized by planned or actual dates,
allowed budget, or resources.</r»ote> <example number="21’>For the development of a new system, a project is set up
that is responsible for the development decisions as well as for the accounting of the costs.<texamp!e> *)
ENTITY project;
(* The actual_end_date specifies the date when the Project was actually finished. *)
actual_end_date; OPTIONAL datejime:
(* The actual_start_date specifies the date when the Project was actually started. *)
actual_start_date ; OPTIONAL datejime;
(* The description specifies additional information about the Project. ’)
description ; OPTIONAL text_select:
(* The id specifies the identifier of the Project. ’)
id ; elementjdentifier.
(* The name specifies the word, or group of words, that is used to refer to the Project. *)
name : label;
(* The planned_end_date specifies either the date when the Project is or was supposed to be finished or the duration of
the Project. *)
ptanned_end_date; OPTIONAL period_or_date_select;
(* The p)anned_start_date specifies the date when the Project is or was supposed to be started. *)
ptanned_start_date; OPTIONAL event_or_date_select;
(* The work_program specifies the Engineering j)rocess_activity objects that are carried out within the Project. *)
work_program : SET [0 : ?j OF engineering process activity:
END_ENTITY;
{’ A Project_event_reference is the definition of a point in time established relative to an event. *)
ENTITY project_event_reference:
(* The description specifies additional information about the Project_eventjeference. *)
description; OPTIONAL text_select:
(* The event type specifies the kind of event that serves as reference. <example number=’22">The two events ‘start of
system analysis* and “end of detailed design’ are examples of an event_type.</example> *)
eventjype ; label;
370