PLCS Statement of Technical Requirements. Technical Requirements Product Life Cycle Support. Configuration Management, страница 26

88.  an implementation_directive may address one or many approved requests;

89.  an implementation_directive is prepared by an organization at a certain point in time;

90.  the combination of the implementation_directive identifier and the organization identifier of the organization assigning the implementation_directive identifier will uniquely define the implementation_directive;

91.  an implementation_directive may impact different configuration baseline items from those identified in the request[38] (see point 6 above);

92.  implementation_directive(s) may be classified, decomposed and aggregated;

93.  an implementation_directive may be referenced by zero, one or many approvals[39]. The approval related information are those listed at point 11 above;

94.  an approved implementation_directive may be referenced by zero, one or many actual_resolution;

95.  an actual_resolution may address one approved implementation directive;

96.  from the information management perspective, an actual_resolution results in the creation of new data instances (e.g. new design version, new product_instance structure, new relationships between product views, etc );

97.  an actual_resolution is applied by a responsible organization;

98.  an actual_resolution is finalized at a certain point in time;

99. 

an actual_resolution may be referenced by zero or one approval[40]. The approval related information are those listed at point 11 above;

Most of the above requirements[41] are addressed in the high level model in figure 13

Figure 13 – High level diagram for Change Control

5.8  Other Issues to Consider

5.8.1  Supportability Characteristics

·  Required

·  Actual

·  Predicted (by whom)

·  Calculated (by whom)

5.8.2  Spare Analysis

Spare related information includes:

·  Items of supply (a class product_physical_design instances);

·  Initial procurement or Spare Specification, e.g. how many and where(a sub-set of items of supply with quantity and level of allocation)

·  Alternative identification (product_physical_design altenatives);

·  Production lead time (product_physical_design property);

·  Supplier information (product_physical_design property);

·  Unit of measure (product_physical_design property);

·  Price (product_physical_design property);

·  Pipe-line time (product_physical_design property);

·  Shelf life (product_physical_design property).

·  Kits/Groups

·  Supply quantities

5.8.3  Packaging

·  Package (a class of product_physical_design instance);

·  Package physical characteristics (product_physical_design property):

-  Size;

-  Weight;

-  Geometry/dimensions;

-  Stacking requirements;

-  Protection;

-  Marking;

-  Safety/hazard;

·  Package Identifier and Label(product_physical_design identification);

·  Package Content (product_physical_design collection);

5.8.4  Handling

·  Handling equipment (a class of  product_physical_design instance);

·  Handling instructions (task description);

·  Safety and security during handling(task advisory_stage description).

·  Emergency actions.

5.8.5  Storage

·  Type of storage

·  Permissible Storage condition (temperature, humidity)

·  Storage methods (stacking and distances);

·  In-storage maintenance;

·  Safety and security during storage;

·  Emergency actions.

5.8.6  Transport

·  Type of carrier and carrier characteristics;

·  Transportation methods per carrier;

·  Safety/Hazard during transport;

·  Tie down procedure (task description);