Хорошев / ИЛП_материал_маг_02.15 / DEF STAN 00-60 / Issue 4 / Part 0 - Appendix F to Annex C - Data element dictionary

DEF STAN 00-60 (PART 0)/4

APPENDIX F TO ANNEX C

Against the assembly variants and configurations (V/C) enter a single alpha code in the following specified positions, filling the remaining positions with significant blanks.

This indicates that UOCA can be applied for, up to a maximum of, 6 assembly V/Cs.

Identifies equipment variants and configurations (V/C) and provides the means of relating the applicability of breakdown parts to their respective equipments.

The Usable on Code Equipment will only be provided in the Initial Provisioning (IP) presentation of an equipment, it will not be given in an IP presentation of an aircraft or engine. The inclusion of more than eight equipment V/Cs in a single presentation is not considered practical. When these circumstances arise, they should be handled by splitting the equipment V/Cs appropriately to make additional IP presentations. The data element is not to be transmitted if there is only one build standard.

For applicable codes refer to AECMA 2000M (TEI UCE).

709 SUPPORT EQUIPMENT VALIDATION/COMPATIBILITY 1 A F - CHECK

A code that states whether, for a recommended task, a validation/ compatibility check has been carried out or is required for an item of Support Equipment.

Certain features of an equipment or armament store merit a particularly high standard of Quality Assurance because of their importance to safety and/or operation of the equipment, the armament store or the platform on which they are mounted.

The Vital Features Item Codes are as follows:

C/F-219

DEF STAN 00-60 (PART 0)/4

APPENDIX F TO ANNEX C

A code which identifies the bay or location where the support equipment is to be used. The work centre codes are provided by the Project.

Air Systems: Work centre codes are supplied by Support Equipment Scaling located at RAF Logistic Support Services 2 (LSS2/CSDE).

A code which identifies the breakdown sequence of assembly, below the SNS level, to which maintenance and descriptive information applies. Where used, it shall be allocated from 00 to 99 and subsequently A1 to A9, B1 to B9, etc. to Z9, excluding the letters ‘I’ and ‘O’. This is a constituent of the AECMA 1000D Data Module Code as detailed in Part 10 of this Standard..

MAINTENANCE PROCEDURE DISASSEMBLY CODE. A disassembly code associated with a maintenance procedure.

SUBTASK DISASSEMBLY CODE. A disassembly code associated with a subtask.

A code which represents the Material Item Category Code (MICC) and Standard Numbering System (SNS) required for electronic documentation. This comprises the following subfields:

NOTE:- Subfield (b) also equates to fields 1, 2, 3, 4, 5 and 6 of AECMA 2000M TEI CSN.

A code used to identify the type of information contained in a data module. This is a constituent of the AECMA 1000D Data Module Code. Refer to Part 10 of this DEF STAN for applicable codes.

C/F-220

DEF STAN 00-60 (PART 0)/4

APPENDIX F TO ANNEX C

MAINTENANCE PROCEDURE INFORMATION CODE. An information code associated with a maintenance procedure.

SUBTASK INFORMATION CODE. An information code associated with a subtask.

A code used to identify different data modules which are applicable to the same subject and type of data. This is a constituent of the AECMA 1000D Data Module Code. Refer to AECMA S1000D for guidance on application of codes.

MAINTENANCE PROCEDURE INFORMATION CODE VARIANT. An Information code variant associated with a maintenance procedure.

SUBTASK INFORMATION CODE VARIANT. An Information code variant associated with a subtask.

805 INITIAL PROVISIONING PROJECT NUMBER SUBJECT 19 X L - (AECMA 2000M TEI IPS)

Describes the subject of the IP Project Number (IPPN).

A code which identifies where the task/operation described in a data module will be performed. This is a constituent of the AECMA S1000D Data Module Code.

Refer to AECMA S1000D for guidance on application of these codes.

MAINTENANCE PROCEDURE ITEM LOCATION CODE. An Item Location Code associated with a maintenance procedure.

C/F-221

DEF STAN 00-60 (PART 0)/4

APPENDIX F TO ANNEX C

SUBTASK ITEM LOCATION CODE An Item Location Code associated with a subtask.

807 SOFTWARE DELIVERABLE SOURCE LINES OF CODE 8 N R - (DSLOC)

The number of lines of deliverable software source code.

SOFTWARE DELIVERABLE SOURCE LINES OF CODE (DSLOC) PREDICTED. The predicted number of lines of deliverable software source code.

SOFTWARE DELIVERABLE SOURCE LINES OF CODE (DSLOC) MEASURED. The measured number of lines of deliverable software source code.

A narrative indicating the usage of modern software engineering methods and techniques. Automated tools that implement the methods and techniques should be identified. Details of the implementation language should also be included.

810 SOFTWARE INTELLECTUAL PROPERTY RIGHTS (IPR) 25 X L - HOLDER

The name of the organization that owns the IPR.

A Narrative description identifying the interdependency between the software candidate under analysis and other software or hardware items.

A numeric field which defines the size of the executable program in Mbytes.

SOFTWARE PROGRAM SIZE PREDICTED. The predicted size of the executable program in Mbytes.

SOFTWARE PROGRAM SIZE MEASURED. The measured size of the executable program in Mbytes.

C/F-222

DEF STAN 00-60 (PART 0)/4

APPENDIX F TO ANNEX C

SOFTWARE SAFETY INTEGRITY LEVEL. The Software safety integrity level as determined by the completion of a hazard analysis iaw DEF STAN 00-56.

The size of computer memory required for the satisfactory operation of a software program.

The version number of the software item.

Procedural packaging specifications relate to existing Standard Family Specifications which define the packaging of either a range of similar assemblies or families of components which can be treated in the same manner for packaging purposes. For further information and applicable codes refer to DEF STAN 81-131.

Indicates the number of Units of Issue (DED 488) contained in a standard package. Enter the actual quantity. Where items are to be packaged separately, enter 1; where item is not subject to a Standard Package Quantity, enter 0. The SPQ shall be provided for all items which have a Reason For Selection (DED 668) other than 0.

C/F-223

DEF STAN 00-60 (PART 0)/4

APPENDIX F TO ANNEX C

A code identifying the specific ammunition container assembly by reference to the Master Register Index or the Drawing Number as defined in JSP 422 (or for Land Service Ammunition in the Catalogue of Ordnance Stores and Ammunition (COSA) T9).

An abbreviated description of the type and material of the ammunition container or unit load container (ULC) as defined in JSP 422, eg BW = Box Wood.

A unique narrative in abbreviated form which describes the item of ammunition as shown in the Catalogue No/ADAC Cross Reference List provided by Log IS Agency (LISA) 2B.

A UN certificate provided by the competent authority in the country of ammunition production. Without this certificate, dangerous goods including ammunition and explosives, as defined in UN Transport of Dangerous Goods (THE ORANGE BOOK), ST/SG/AC.10/1, cannot be moved across international borders.

Narrative information which denotes the possibility of damage to materiel during the performance of tasks/subtasks. This equates to AECMA 1000D CAUTION INFORMATION.

A code, allocated by the Project, which identifies non-textual information. This unique identifier facilitates configuration and hypertext linking within data modules, in accordance with AECMA 1000D. The code application, given below, forms part of the AECMA S1000D Illustration Control Number (ICN). For further details of the ICN see Part 10 of this Standard.

Data shall be allocated as follows:

Responsible Partner Company (RPC) - The CAGE 5 X F - Code (See DED 046) for the partner company

responsible for entering the Illustration into the Common Source DataBase (CSDB).

C/F-224

A number which identifies the required item (ie Support Equipment, consumable etc) for an entry within a data module. This unique identifier is required in accordance with AECMA 1000D.

Supplementary task/subtask-related narrative information, not covered in Warning Information (DED 828) or Caution Information (DED 823). This equates to AECMA 1000D NOTE INFORMATION.

C/F-225

DEF STAN 00-60 (PART 0)/4

APPENDIX F TO ANNEX C

827 MAXIMUM ALLOWABLE MAINTENANCE INTERVAL 6 N R - (MAMI)

The maximum allowable interval between maintenance actions, used with an associated Measurement Base (DED 238). This equates to AECMA 1000D THRESHOLD INTERVAL.

Narrative information which denotes possible hazards, which may cause loss of life, physical injury or ill health during the performance of tasks/subtasks. A warning shall satisfy the Health and Safety at Work etc Act 1974, as amended by the Consumer Protection Act 1987, The Control Of Substances Hazardous To Health (COSHH) Regulations and other legislation in force at time of contract award. This equates to AECMA 1000D WARNING INFORMATION.

A code used to uniquely identify a country/organisation. This equates to AECMA 2000M TEI USR, which should be referred to for appropriate codes.

A code used to uniquely identify a maintenance procedure.

REFERENCE MAINTENANCE PROCEDURE IDENTIFIER. A code that identifies referenced maintenance procedure information.

A four position code used to indicate the sequence of a procedural step for a task. Task Sequence Numbers shall begin with 0001 through 9999 and assigned to each sequential task required to perform a maintenance procedure.

A code to identify the category of a software item. Applicable codes are as follows:-

C/F-226

A code which identifies whether data contained in an AECMA 2000M IP message relates to a chapterised or a non-chapterised project. Applicable codes are as follows:

A six-position code identifying the users of the equipment/item under analysis. See DED 376 for applicable codes.

SE USING SERVICE DESIGNATOR CODE. A six-position code identifying users of the support equipment under analysis.

836 OPERATIONAL TEST PROGRAMME (OTP) LOCATION 1 A F -

A code to indicate whether an OTP resides in an item of test equipment or in the unit under test.

A justification of why, for the item under analysis, formal failure analysis, such as FMECA and RCM, is not documented in the LSAR. Justification may include, but not be limited to, the following:

Failure analysis documented outside the LSAR.

Simple item, only corrective maintenance required.

COTS/NDI items, no redesign or preventive maintenance; FMECA/RCM not required.

C/F-227