DEF STAN 00-60 (PART 0)/4

ANNEX C

ANNEX C

DATA DICTIONARY AND RELATED TECHNICAL INFORMATION

C-1

DEF STAN 00-60 (PART 0)/4

ANNEX C

Collation Page

C-2

DEF STAN 00-60 (PART 0)/4

ANNEX C

CONTENTS

Refer to main contents list (pages 2 thru 6)

C-3

DEF STAN 00-60 (PART 0)/4

ANNEX C

Collation Page

C-4

DEF STAN 00-60 (PART 0)/4

ANNEX C

Introduction

C.0 Production of the UK MOD ILS DEF STAN 00-60 Data Dictionary and Related Technical Information

C.0.1 This Annex to DEF STAN 00-60 (Part 0) prescribes the Data Element Definitions (DED), data field lengths and formats for Logistic Support Analysis (LSA) Record (LSAR) data. It identifies the LSAR reports that may be generated from the LSAR data and identifies the LSAR relational Tables and automated data processing specifications for transmission and delivery of LSAR data.

C.0.2 This Annex comprises the full LSAR Relational Tables with keys shown, and eight appendices:

Appendix A comprises the LSAR Reports Summary. This Summary contains the descriptions of the LSAR Output Reports.

Appendix B comprises LSAR Reports/Relational Data Table Cross-Reference Matrix. This Matrix cross-refers the LSAR Relational Tables, in Table sequence order, with the LSAR Output Reports together with their constituent Data Element requirements.

Appendix C comprises example LSAR Output Report Illustrations.

Appendix D comprises the Index of Data Element Titles. This Index contains a list of all Data Elements, in numerical order, and their associated relational Table locations and codes.

Appendix E comprises the Alphabetical Listing of Data Element Codes. This contains a list of Data Element Codes and their associated Role Name Titles.

Appendix F comprises the Data Element Dictionary. This lists the Data Element Definitions in numerical order.

Appendix G comprises the Alphabetical Listing Of Data Element Titles. This lists the Data Element Titles with their associated Data Element Number.

Appendix H comprises Document References. This contains a list of Reference Documents contained within the Data Element Definitions.

C-5

DEF STAN 00-60 (PART 0)/4

ANNEX C

Collation page

C-6

DEF STAN 00-60 (PART 0)/4

ANNEX C

Logistic Support Analysis Record Relational Tables

C.1 Scope

This Annex establishes the Logistic Support Analysis (LSA) Record (LSAR) relational Table titles, data content and format to be produced by an LSAR relational Automated Data Processing (ADP) system. It defines all the relational Tables that comprise an LSAR database.

C.2 Concept

In a relational database system, information is organized in the form of Tables. Categories or columns of information are listed across the top of each Table. Individual sets of information are listed as rows. LSAR relational Tables are two-dimensional matrices of related data.

Tables are defined in terms of columns (or data element definitions (DED)) and rows (or multiple sets of the columnar data elements). Information in this format can be easily visualized and understood. Within each Table, certain data may be defined as foreign key, or key, eg, required to be present when a new row of data is established. These data keys comprise a unique set of identifiers for each row of information in the data Table. Relational Tables are structured according to the data associations which dictate the Table configuration. Although each relational Table is independent and equal, data integrity rules will dictate that a row of information be established in a Table from which foreign keys originate, prior to the establishment of the lower-tiered data Table. The interrelationships and data hierarchy between Tables are only established through common data element keys and data values. The Tables listed in this Annex comprise the total LSAR relational database.

C.3 Relational Data Tables Format

The relational Tables are shown in this Annex by functional areas in the following sequence:

C-7

DEF STAN 00-60 (PART 0)/4

ANNEX C

C.3.1 Functional LSAR Relational Table Listing and Table Relationships. Preceding the data Tables for each functional area are listings of the applicable data Tables and an illustration showing the data Table relationships. The listing contains each LSAR relational Table code and title.

These Table codes cannot be modified when establishing/creating a relational LSAR ADP System. This list of relational Tables comprises the LSAR database. Each figure depicts the Table title and code. Starting at the top of the figure, Table keys are migrated down to each successive level of related Tables shown through line relationships. Only additional keys are shown as you progress from top to bottom (eg, Figure 6, contains Table XB. This Table has data keys End Item Acronym Code (EIAC) (migrated from Table XA) and LSA Control Number (LCN), Alternate LCN Code (ALC), and LCN Type (listed beneath the line in the Table block)).

C.3.2 LSAR Relational Tables. The detailed portion of each functional area contains each LSAR Table, a brief description of the Table contents and business rules, and the format and content of the Table elements. Each Table contains a Table Code, Table Title, Table Description and columnar listing comprising:

(a)Data element code

(b)Data element title or role name

(c)Data element field format

(d)Data element number

(e)Key indicator

C.3.2.1 Format. The general format for the relational Tables is as follow:

C-8

DEF STAN 00-60 (PART 0)/4

ANNEX C

C.3.2.2 Definition of Terms

C.3.2.2.1 Table Code. The three-position code, left-justified, assigned to each Table in the relational LSAR used for locating and referencing the data elements to the appropriate relational LSAR Table in the DED cross-reference index.

C.3.2.2.2 Table Title. A descriptive phrase used to identify the relational Table. Sufficient adjectival modifiers are used with the phrase to ensure unique identification.

C.3.2.2.3 Table Description. A short statement outlining the contents and associated business rules of the data Table.

C.3.2.2.4 Data Element Code (CODE). A nine-position code, left-justified, used to identify the DED. Each DED Code is unique within the Table in which the DED is listed. The DED Code cannot be changed or modified when independently developing a relational LSAR ADP System. The last three positions of the code are the Table code. When a key migrates to a new Table, thus becoming a foreign key, it will retain the Table code where the key originated, unless the key is required to assume a ‘role name’ in the new Table. Origination of foreign keys which assume role names are defined in the business rules for the data Table.

C.3.2.2.5 Data Element Title. The noun phrase used to identify the data element. Sufficient modifiers are used with the noun name to ensure title uniqueness for specific data element definition.

C.3.2.2.6 Field Format. A 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. A specification of the character type, wherein:

(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

C-9

DEF STAN 00-60 (PART 0)/4

ANNEX C

justified (R); and, those which always occupy the entire field are fixed (F). A dash (-) is used if this 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 with a fixed decimal location. A dash (-) is used if this column is not applicable. ‘AS’ means ‘As Specified’ and the detailed instructions will indicate the location of decimal points.

(e)Formats. Field formats for extended narrative data fields are capable of accepting a maximum of 99,999, 65-character lines, of information by means of a text sequencing code.

C.3.2.2.7 DED Number. A sequentially assigned number to each data element in the dictionary for use in locating and referencing it throughout the dictionary and the relational data Tables.

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 INTERIM DEF STAN 00-60, start at number 601 (DED 601 was deleted in Issue 4 of this Standard); those introduced in subsequent issues of DEF STAN 00-60, 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.3.2.2.8 Key Data Element Code (KEY). An indicator that identifies key and mandatory data within a data Table. The indicators are ‘F’, foreign key, ‘K’, key, or ‘M’, mandatory, nonidentifying data element. Key data cannot have a null value (unless specified in the business rules) when attempting to establish a data row in a given data Table.

C.3.2.2.9 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.3.2.2.10 Data Migration. The term ‘migrates from’ signifies that the data is sourced from another Table location. The sourced data remains within its originating Table.

C.3.3 LSAR Data Table Exchange/Delivery. Depending upon contractual requirements, exchange/delivery of the LSAR data may take the form of full file replacement or ‘change only’ data (changes to the DEF STAN 00-60 data Tables since previous submittal of the LSAR data). Both capabilities are required of DEF STAN 00-60 LSAR systems.

To identify the Standard and Issue status of exchange/delivery LSAR data files, each transfer file shall include a 25 character Status Identifier (25 X F -) which consists of a 11 character (11 X F -) Standard identifier, followed by a three character (3 X F -) Standard issue identifier, an 8 character Date identifier (8 N F -; see DED 071) and a 3 character Data drop identifier (3 X F -) as follows: STANDARD|ISSUE|DATE|DROP (An example Status Identifier for LSAR data transfer files created to this issue of this Standard is: “DEFSTAN006000420000625001”).

C-10