
Хорошев / ИЛП_материал_маг_02.15 / DEF STAN 00-60 / Issue 4 / Part 0 - Appendix F to Annex C - Data element dictionary
.pdfDEF STAN 00-60 (PART 0)/4
APPENDIX F TO ANNEX C
APPENDIX F TO ANNEX C
DATA ELEMENT DICTIONARY
DEF STAN 00-60 (PART 0)/4
APPENDIX F TO ANNEX C
Collation Page
DEF STAN 00-60 (PART 0)/4
APPENDIX F TO ANNEX C
C/F.0 Data Element Dictionary
This Appendix contains definitions for all data elements that appear in the LSAR relational data tables. The data element definition (DED) contains some or all of the following entries. When a standard data element acronym applies, this is also listed in this Appendix.
(a)DED number
(b)Data element title with acronym
(c)Field format
(d)DED
(e)Data item(s)
(f)Data code(s)
(g)Role name(s)
C/F.0.1 Format
The general format for the DED is as follows:
DED # |
DATA ELEMENT TITLE |
FIELD FORMAT |
|
|
(ACRONYM) |
|
|
|
DATA ELEMENT DEFINITION |
|
|
|
DATA ITEM(S) |
DATA CODE(S) |
|
|
ROLE NAME(S) |
|
|
Example of actual DED entry: |
|
|
|
643 |
ILLUSTRATION AFFECTED INDICATOR |
1 A F - |
|
|
(AECMA 2000M TEI IAI) |
|
|
Indicates whether a change to provisioning data affects the related illustration.
Illustration affected |
Y |
Illustration not affected |
N |
C/F-1
DEF STAN 00-60 (PART 0)/4
APPENDIX F TO ANNEX C
C/F.0.2 Definition of terms
C/F.0.2.1 DED number
A sequentially assigned number to each data element in the dictionary for use in locating and referencing it throughout the dictionary and data entry instructions (Annex C).
NOTE: Data elements which originated in the former MIL-STD-1388-2B Notice 1 are numbered from 001 to 518. Data elements which were introduced in INT DEF STAN 00-60, start at number 601 (DED 601 was deleted in Issue 4 of this Standard); those introduced in DEF STAN 00-60 Issue 1 and subsequent issues, start from number 801. A number of data elements have been removed where not required in UK usage, thus leaving gaps in the sequential numbering.
C/F.0.2.2 Data element title
The name used to identify the data element. Sufficient adjectival modifiers are used to ensure title uniqueness.
C/F.0.2.3 Field format
The specification for the length, type, positional justification, and decimal placement of a data element field, or subfield thereof, as described below:
(a)Length.
The number of character positions in the data element. In the event the length is variable, the maximum length is specified.
(b)Type.
The specification of the character type, wherein:
‘A’ specifies that all characters for the data entry are upper case alphabetical.
‘N’ specifies that all characters of the data entry are numerical.
‘X’ specifies that characters of the data field are upper case alphabetical (except narrative fields), numerical, special, or any combination thereof.
‘D’ specifies that characters of the data entry are numerical with floating decimal. Decimals may be entered as required or exponentially, eg, ‘0.0000325’ or ‘3.25E-5’.
C/F-2
DEF STAN 00-60 (PART 0)/4
APPENDIX F TO ANNEX C
(c)Justification.
Specifies from which side of the field the characters of the data element are entered. Those starting at the left are left justified (L), those starting at the right are right justified (R), those which always occupy the entire field are fixed (F). A dash (-) is used if the column is not applicable.
(d)Decimal Placement.
Specifies the number of character positions to the right of the assumed decimal point when the data element is numeric in all character positions. A dash (-) is used if this column is not applicable. ‘AS’ means ‘As Specified’ and the detailed instruction will indicate the location of decimal points.
C/F.0.2.4 DED
A narrative definition of the data element in sufficient detail to present a clear and complete understanding of the precise data or element of information that the data element represents.
C/F.0.2.5 Data item
One of a set of descriptive items of information or values that apply to a data element. For example, the data element ‘Skill Level Code’ contains the data items ‘Basic’, ‘Intermediate’, and ‘Advanced’.
NOTE: The term ‘Data Item’ used here should not be confused with the data item included in the term ‘Data Item Description’ which refers to contractual deliverables.
C/F.0.2.6 Data code
One or more alphabetical, numerical, special characters, or any combination thereof, that represent a data item to be entered in a field in the LSAR. A code is used instead of the data item itself, in order to conserve space in the data records and to facilitate machine processing eg the data element ‘Security Clearance’, and the Data Items ‘Top Secret’, ‘Secret’, ‘Confidential’ and ‘Unclassified’, are represented by the data codes ‘1’, ‘2’, ‘3’, and ‘4’, respectively.
NOTE 1: In some cases, a position left blank counts as a data code signifying some particular data item value as specified in the dictionary. For example for the data element, ‘Maximum Allowable Operating Time’, the third position of the four-position code designates the appropriate multiplier code. The codes are ‘ ’ (blank), X, C, or M, with a ‘ ’ (blank) designating a multiplier of one (1), ‘X’ a multiplier of ten (10), ‘C’ a multiplier of one hundred (100), and ‘M’ a multiplier of one thousand (1000).
C/F-3
DEF STAN 00-60 (PART 0)/4
APPENDIX F TO ANNEX C
NOTE 2: When DEDs, data items and data codes are too long to be included in this document, reference is made to definitions, items and codes in another document. For example, see ‘Procurement Code’, DED 666.
C/F.0.2.7 Role name
A unique modifier of a data element title which describes the use/application of the data element within a specific relational data table location.
C/F-4
DEF STAN 00-60 (PART 0)/4
APPENDIX F TO ANNEX C
001 ACHIEVED AVAILABILITY (Aa) |
8 N R 6 |
The probability that, when used under stated conditions in an ideal support environment, a system will operate satisfactorily at any time. This differs from Inherent Availability only in its inclusion of consideration for preventive action. Aa excludes supply downtime and administrative downtime. The measurement bases for MTBM and M shall be consistent when calculating Aa.
Aa may be expressed by the following formula:
Aa = |
MTBM |
|
|
|
|
|
|
|
|
|
|
MTBM + M |
|
|
|
|
|
|
|
|
|||
|
|
|
|
|
|
|
|
|
|||
|
æ 1 |
|
1 |
|
1 |
ö −1 |
|||||
|
where MTBM = ç |
|
+ |
|
|
|
+ |
|
|
÷ |
|
|
|
|
MTBM - NF |
|
|
||||||
|
|
è MTBF |
|
|
|
MTBPM ø |
|||||
|
|
|
|
|
|
|
N |
|
|
|
|
|
|
|
|
|
|
|
å(ETi )(TFi ) |
|
|||
|
|
|
|
|
M = |
i =1 |
|
|
|
|
|
|
|
|
|
|
N |
|
|
|
|
||
|
|
|
|
|
|
|
åTFi |
|
|
|
|
|
|
|
|
|
|
|
i =1 |
|
|
|
|
M |
= Mean active maintenance downtime (where corrective and |
||||||||||
|
preventive actions are considered) |
|
|
|
|
||||||
ETi |
= Elapsed time for task i |
|
|
|
|
|
|
|
|
||
TFi |
= Task frequency for task i |
|
|
|
|
|
|
|
|
||
N |
= Total number of tasks performed |
|
|
|
|
NOTE: The measurement bases for MTBF, MTBM-NF, and MTBPM shall be consistent when calculating the MTBM parameter.
REQUIRED ACHIEVED AVAILABILITY. An Aa representing the requirement/specification Aa.
002 ACQUISITION DECISION OFFICE |
15 X L - |
A code which identifies the Project Management Agency responsible for technical and acquisition management decisions.
003 ACQUISITION METHOD CODE (AMC) |
1 N F - |
A code assigned to describe the results of screening reviews of parts, defining either a single source or competitive procurement strategy for the item. Codes are as follows:
Not established |
0 |
C/F-5
DEF STAN 00-60 (PART 0)/4
APPENDIX F TO ANNEX C
Suitable for competitive acquisition |
1 |
(See notes 1 & 2) |
|
Suitable for competitive acquisition |
2 |
for the first time (See notes 1 & 2) |
|
Acquired directly from the actual |
3 |
manufacturer, whether or not the prime |
|
contractor is the actual manufacturer |
|
Acquire, for the first time, directly from |
4 |
the actual manufacturer rather than the prime |
|
contractor who is not the actual manufacturer |
|
Acquire only from the prime contractor |
5 |
although the engineering data identifies the |
|
Commercial And Government Entity (CAGE) code |
|
and Part Number of a source other than the |
|
prime contractor (See note 3) |
|
NOTE 1: Potential sources shall include dealers/distributors.
NOTE 2: If sources are limited to the prime contractor and a sub-contractor, a competitive code shall not be assigned unless both sources are expected to compete independently for contracts for the part.
NOTE 3: The MOD agency assigning this code shall provide the name and CAGE of the prime contractor to the agency responsible for acquiring the part.
005 ADAPTOR/INTERCONNECTION DEVICE REQUIRED |
1 A F - |
A single position code indicating whether an adaptor/interconnection device is required to provide mechanical and electrical connection between the Automatic Test Equipment (ATE)/Test, Measurement, and Diagnostic Equipment and a unit under test.
Required |
Y |
Not Required |
N |
006 ADDITIONAL REFERENCE NUMBER |
32 X L - |
A drawing or interchangeable reference number related to the reference number of the item under analysis. Only those ARNs that are known and available as a result of the contractor's design and production experience should be provided. This requirement is not intended to burden the contractor with the additional work load of searching for ARNs. When more than one manufacturer's reference number identifies a single design item, the additional reference number(s) which have been validated by the contractor as
C/F-6
DEF STAN 00-60 (PART 0)/4
APPENDIX F TO ANNEX C
completely interchangeable for the specific application and whose use will not invalidate the end item warranty shall be furnished.
007 ADDITIONAL SKILL REQUIREMENT: SKILL |
65 X - - |
REQUIRING A NEW OR REVISED SKILL CODE |
|
A narrative description identifying the new skills that are required in order to operate/maintain the equipment.
008 ADDITIONAL SKILLS AND SPECIAL TRAINING |
65 X - |
- |
REQUIREMENTS |
|
|
A narrative description identifying the new skills required to operate/maintain the equipment, and the additional training required for operator, maintenance, and instructor personnel. Includes the estimated lengths of courses, recommended site, justification for training, and prerequisite requirements for students.
009 ADDITIONAL SPECIFICATIONS/REQUIREMENTS |
65 X - |
- |
A narrative description of any specifications or requirements (related to the anticipated operation of the system, or the environment in which the system will be operated and maintained) that cannot be documented under the detailed specification/ requirements data.
010 ADDITIONAL SUPPORTABILITY CONSIDERATIONS |
65 X - |
- |
A narrative description of LSA modelling considerations which cannot be documented in the discrete supportability data elements. It may include such information as acceptable models, programme or model specific information, etc.
011 ADDITIONAL SUPPORTABILITY PARAMETERS |
65 X - |
- |
A narrative including a listing and description of specific data elements for which discrete fields are not provided. The documentation should also include the data element title, associated value to be recorded, associated units, and a description as necessary to define the scope and purpose of the data element and its use.
012 ADDITIONAL TRAINING REQUIREMENTS |
65 X - |
- |
A narrative description identifying the additional training required for operator, maintenance, and instructor personnel. Includes the estimated length of courses, recommended site, justification for training and prerequisite requirements for students.
C/F-7
DEF STAN 00-60 (PART 0)/4
APPENDIX F TO ANNEX C
013 ADMINISTRATIVE AND LOGISTIC DELAY TIME (ALDT) 3 N R -
The total time in days the system/equipment is inoperable due to delays in maintenance that are attributable to administration and logistics. ALDTs between UK MOD units and depots are available in JSP 336.
REQUIRED ALDT. An ALDT representing the requirement/ specification ALDT.
014 ADMINISTRATIVE LEAD TIME |
2 N R - |
The administrative time (in months) required to prepare, advertise and award a contract for wholesale supply re-order actions.
015 SUPPORT EQUIPMENT ALLOCATION DATA |
60 X - - |
The support equipment allocation information consisting of seven sub-fields:
a. |
Allowance (DED 016) |
10 |
X |
L |
- |
b. |
Allowance Range |
30 |
N |
AS |
- |
A 10 block spread format (Allowance Range 1-10 used to record the allowance for the end item, ATE item, or depot overhaul requirements). The Allowance Code (DED 016) will distinguish whether the allowance ranges are for end items, ATE items, or depot overhaul requirements. These 10 blocks may be labelled 1-4 through 251-450 to describe the number of end articles to be supported by the quantity of support equipment end items entered in the three (3) position sub-field. Block headings are: 1-4, 5-8, 9-12, 13-16, 17-24, 25-32, 33-64, 65-125, 126-250 and 251-450, respectively. For example: For SE end items, the quantity of end items required to support a range of 5 to 8 end articles is identified in the block labelled 5-8.
(1)For ATE items, the 10 blocks are associated with 1, 2, 3...10 to describe the number of ATE items to be supported by the quantity of support equipment items entered in the three position sub-field.
(2)For depot overhaul requirements/entries, associate the first three blocks with workload rates of 20, 50, 100 end articles per month to be supported by the quantity of support equipment items entered in the three-position sub-field.
c. |
Designation Description |
9 |
X |
F |
- |
A nine-position code that identifies the method of allowancing items. The codes include the following:
Inventory Record |
INVRECORD |
C/F-8