Хорошев / ИЛП_материал_маг_02.15 / Спецификация AECMA Specification 2000M / MIL-STD-1388-2B

MIL-STD-1388-2B

APPENDIX A

APPENDIX A

LOGISTIC SUPPORT ANALYSIS RECORD RELATIONAL TABLES

10. SCOPE. This appendix establishes the Logistic Support Analysis (LSA) Record (LSAR) relational table titles and 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.

20. 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, e.g., 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 appendix comprise the total LSAR relational database.

30.RELATIONAL DATA TABLES FORMAT. The relational tables are shown in this

appendix by functional areas in the following sequence:

a.X, Cross functional requirement

b.A, Operations and maintenance requirement

c. B, Reliability, availability, and maintainability; failure modes, effects, and criticality analysis; and, maintainability analysis

d. C, Task inventory, task analysis, personnel and support requirements

e.E, Support equipment and training materiel requirements

f.U, Unit under test requirements and description

g.F, Facilities considerations

h.G, Personnel skill considerations

i.H, Packaging and provisioning requirement

j.J, Transportability engineering analysis

30.1Functional LSAR relational table listing and table relationships. Preceding the data tables for each functional area are a listing of the applicable data tables and an illustration showing the data table

-21-

MIL-STD-1388-2B

APPENDIX A

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

related tables shown through line relationships. Only additional keys are shown as you progress from top to bottom (e.g., figure 4, 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)).

30.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 the following entries:

a.Table code

b.Table title

c.Table description

d.Columnar listing of the table contents

(1)DED code

(2)Data element title or role name

(3)Data element field format

(4)DED number

(5)Key indicator

30.2.1Format. The general format for the relational tables is as follows:

30.2.2 Definition of Terms.

30.2.2.1Table 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.

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

30.2.2.3Table Description. A short statement outlining the contents and associated business rules of the data table.

-22-

MIL-STD-1388-2B

APPENDIX A

30.2.2.8 Key Data Element Code (KEY). An indicatqr 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.

30.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.

30.3 LSAR Data Table Exchange/Delivery. Depending upon contractual language, exchange/delivery of the LSAR data may take the form of full file replacement or “change only” data (changes to the MIL-STD-1388-2B data tables since the previous submittal of the LSAR data). Both capabilities are required of validated MIL-STD-1388-2B LSAR systems. Also, LSAR data tables shall be exchanged/delivered via variable length ASCII file formats. All data elements shall be positioned at their respective offsets in the table row field. The following paragraphs define the requirements to insure that automated LSAR systems will produce and load standard outputs not only for all MIL-STD-1388-2B data tables (full file replacement), but also standard outputs for “change only” data. Each type of transaction shall be identified by the use of an update code (UC); multiple transactions are possible for “change only” data delivery. The UC is not a data element within each relational table. Instead, the UC appends the appropriate table row(s) identifying the transactions which have occurred.

30.3.1 Full file replacement. When providing an initial LSAR file delivery or a full file replacement, a UC = * must be present for the appropriate row of Table XA. The file structure for full file replacement is as follows:

The UC (K) identifies the type of transaction as being full file replacement or initial delivery. The Table ID is XA in this case and the Table Row only needs the key data element (EIAC) input. Each element of the transaction shall be contiguous and without the vertical lines shown above.

30.3.2 Change only data delivery. “Change only” data delivery requires multiple types of change transactions. Each type of change transaction is listed below with its definition and appropriate UC.

a.Add Transaction - UC = A. The Add Transaction Code identifies that

the record to be loaded is a new record to be added to the respective table. The appearance of an add implies that the key data elements do not already exist in the table being accessed. However, those key data elements must already exist in the prerequisite tables. The add record shall contain the required key fields and shall invoke a full record insert to the specified table.

b. Delete Transaction - UC = D. The Delete Transaction Code identifies the transaction record as a delete of an existing record pertaining to the identified key data elements. If the table is prerequisite to another table and there is data in the other table matching on the identified keys, this

transaction shall not delete the data in the specified table. A global delete transaction (identified below) shall delete table records and associated

-24-

MIL-STD-1388-2B

Appendix A

40. CROSS FUNCTIONAL REQUIREMENT. The following “X” data tables have attributes which cross multiple functional areas or are used as a link to various functional data tables. Included under these tables are the functional and physical breakdown LCN, assignment and application of UOCS, technical manual numbers, and government provided level of repair analysis (LORA) modeling information. Figure 4 depicts the key relationships for these tables.

40.1 Table XA. End Item Acronym Code. This table contains the EIAC (EIACOBXA) used to define the LSAR system documented in the relational database. Also included in this table are LORA modeling parameters provided by the requiring authority. When the classical or modified classical LCN assignment is used (see Appendix C), then an entry is required in LCN structure (LCNSTRXA).

MIL-STD-1388-2B

APPENDIX A

40.2 Table XB, LSA Control Number Indentured Item. This table contains all LCNs and information about the indentured location of the LCN in the hardware/ functional configuration of the system/equipment. Table keys include: EIAC (EIACODXA); LCN (LSACONXB); ALC (ALTLCNXB); and, LCN Type (LCNTYPXB).

If LCN Structure from table XA (LCNSTRXA) is blank, LCN Indenture Code (LCNINDXB) is mandatory.

b. If LCN Structure is not blank, the LCN (LSACONXB) must match an indenture level length specified by the LCN Structure, or be a greater length than the total of all LCN Structure indenture levels, e.g., if the LCN Structure is “12233”, an LCN must be either 1, 3, 5, 8, 11, or greater than 11 positions. If the LCN is greater than 11 positions, the LCN Indenture Code

is an item capable of independent operation for its intended use, e.g. , rifle, radio receiver, or is a class or group of equipment that is managed and provisioned under a separate Provisioning Contract Control Number (PCCN). Table keys include: EIAC (EIACODXA); LCN (LSACONXB); ALC (ALTLCNXB); and, LCN Type (LCNTYPXB).

-28-

MIL-STD-1388-2B

APPENDIX A

a.The System/EI Identifier (SYSIDNXB) of “S” or “E” identifies LCNs as

representing System/EIs from table XB for entry into this table.

b. For identical PCCNs (PCCNUMXC), the UOCs (UOCSEIXC) must be different.

40.4 Table XD, System/End Item Serial Number. This table is only used when parts configuration control is managed by serial numbers (S/N) of a system/EI. It contains Serial Numbers applicable to a System/End Item, and if required, Serial Number UOC assignments, e.g., for model V10, identified in table XC, applicable serial numbers may be 110 through 118, 121 and 125-130, while for model V10A, also identified in table XC, the applicable serial numbers may be 119, 122-124, and 131-150. For these serial number(s) specific serial number UOCS may be assigned as follows:

a. S/N From (FRSNUMXD) must be less than or equal to S/N To (TOSNUMXD).

b. For the identical EIAC, LCN, ALC and LCN Type, S/N UOCs must be different.

MIL-STD-1388-2B

40.5 Table XE, LCN to Serial Number Usable On Code. This table contains LCN and system/EI S/N LCNs in order to determine the associated S/N and S/N UOCs for the LCN. Table keys include all columns.

a.Table keys LSACONXE, ALTLCNXE, and LCNTYPXE migrate from table XB.

b. Rows of information from this table with LCNTYPXE and LTYSEIXE of “P” must match entries in table HN, when this table is established.

40.6 Table XF. LCN to System/End Item Usable On Code. This table contains LCNs and System/EI LCNs in order to determine the associated UOC for the LCN. This table and table HO (for provisioning) are critical to qualify an LCN for report requests when a specific UOC is required for report selection. Table keys include all columns.

a.Table keys LSACONXF, ALTLCNXF, and LCNTYPXF originate in table XB.

b. Rows of information from this table with LCNTYPXF and LTYSEIXF of “P” must match entries in table HO, when this table is established.

40.7 Table XG, Functional/Physical LCN Mapping. This table contains a crosslisting of functional/physical LCNs. All data, except EIACODXA, originate in

-30-