Attachment_13_-_Cataloging_Schema_for_Logistics_and_Technical_Data.docx

Cataloging Schema for Logistics and Technical Data

Attachment 13

Document Identification Number AAA-INS-01002 15 Sep 2014

Program Manager

- Advanced Amphibious Assault

Work Instruction

AAA-INS-01002

v.1.1

Date Approved:

PM AAA:

Purpose:

The purpose of this Work Instruction is to provide standardized schema to catalog logistics and engineering technical data and data products in data bases and document libraries to provide for ready retrieval, use and re-use within and across PM AAA platform programs.

Overview:

A Master Cataloging Index (MCI) has been developed, using MIL-STD-881C as a starting point that provides the top four levels of a numerically based cataloging schema. This does not replace the Program Work Breakdown Structure (WBS) for overall program management of the project. This Instruction will be invoked by the Contract Statement of Work for use by Prime Contractors, and provided as an attachment to the contract. This Master Cataloging Index is to be used as a key field when setting up database or paper-based systems to store and manage logistics and engineering data and documents. It models a public library’s Dewey Decimal system. This master index will also be used as the first portion of Logistics Support Analysis (LSA) control numbers and Configuration Status Accounting (CSA) control numbers, as described below. This MCI is applicable and will be used across all amphibious platforms managed by PM AAA, and by all organizations, both government and prime contractors, associated with PM AAA platforms. For the legacy AAV platform, this MCI will be applied during development of future upgrades and design changes on a go-forward basis.

Roles and Responsibilities:

Instruction Document Owner: Although the Logistics Director is listed as the owner of this Instruction, in reality it is co-owned by both the Logistics and Systems Engineering Directors. Any proposed changes to this Instruction or attached MCI will be approved by them. Changes can be in the form of a revision to this Instruction, or via change notices if speed is required. The directors will also review the MCI annually to determine if any areas need to be added or the ‘Includes’ and ‘Excludes’ sections need clarification or incorporation of change notices.

Instruction Document Users: Users will implement this MCI when establishing data or document repositories that host logistics or engineering data or documents associated with PM AAA platforms. For electronic data systems, the MCI numbers will be used as a searchable and filterable key field. The MCI titles will also be used in conjunction with the numbers to provide clarity of what the number represents. The Program Office and Prime Contractors will also use this MCI when setting up databases to host logistics and engineering data and documents. By storing data to a common schema, bits and groupings of data can be shared or readily compared across projects. And the government users of the data in the logistics and engineering functional areas will be more readily able to search and consistently find data regardless of which project they are currently working.

Instructions:

1. When setting up electronic or paper-based data repositories to host logistics and engineering data, the MCI through level four will be used to catalog and index that data. For Logistics Support Analysis (LSA) and Configuration Status Accounting (CSA) databases, Control Numbers (CN) will be assigned down to the individual supply configuration worthy item level using the MCI numbers as the beginning of the control numbers (LCNs or CSA CN’s). Each application of the same part number, if they are supply configuration worthy, will have unique LCNs assigned, see example below. To aid in cataloging and assigning LCNs and CSA CNs, the MCI contains two columns: an ‘Includes’ column and an ‘Excludes’ column. These columns provide descriptive information to help the indexer determine which MCI number best applies for cataloging data or documents pertaining to a particular item on the vehicle platform. Below level four of the MCI, the owner of the data repository can breakout and assign LCNs based on their best judgment. Breakout is usually done only to the supply configuration worthy item level (e.g., a hydraulic actuator but not its piece parts; however, some ‘piece parts’, especially structurally related such as armor panels, would also get unique LCNs or CSA CNs assigned. However, this Instruction does not preclude the owner of a data repository from going below that level.

It is recommended that such break-downs be based on a hierarchy of the vehicles’ functional capabilities. For example, under System Survivability, Seats and Seating, the actual seats may be functionally grouped as follows: Crew Seats, Embarked Marine Seats and within the first grouping: Driver Seat, Troop Commander Seat, Vehicle Commander Seat, and Gunner’s Seat. Each Seat may be further broken down to its supply configuration worthy items: its foundation and attaching hardware; the actual seat; its safety harness (assuming the safety harness is procured separately and not inherently part of the seat assembly procured from the same vendor); and any other separately procured attachments.

The MCI is structured into two main groupings: items those are found on vehicles, and associated items that are found off vehicles but used to manufacture, test or support the vehicles. These two groups form the second level of the MCI. Levels three and four of the MCI only loosely follow Mil-STD 881C, Appendix G, for Ground Combat Vehicles. Rather than have separate and largely redundant sub-groupings by vehicle variants (e.g., Primary = Personnel , Secondary = Communications and Tertiary = Recovery) we have combined the unique aspects of C and R vehicles with the P variant items and integrated them as level three or four items.

2. Once the MCI is base lined, only additions will be permitted to MCI numbers and titles. Changes to the ‘Includes’ and ‘Excludes’ columns will be made as users seek clarification as to which MCI category any particular data set or document belongs to. Requested changes to the MCI should be submitted to either PM AAA Logistics or SE Director.

3. The PM AAA LSA Manager will develop an MCI Change Notice and staff the requested change through the Logistics and Engineering Directors for their approval. Once approved, the MCI change notices will be provided to all users.

Master Cataloging Index (MCI)

All On-Vehicle Items

1.1.1

Hull/Frame/Body/Cab

1.1.1.1

1.1.1.2

1.1.1.3

1.1.1.4

1.1.2

System Survivability

1.1.2.1

1.1.2.2

1.1.2.3

1.1.2.4

1.1.2.5

1.1.2.6

1.1.2.7

1.1.2.8

1.1.3

Turret/Copula Assembly

1.1.3.1

1.1.3.2

1.1.3.3

1.1.3.4

1.1.3.5

1.1.3.6

1.1.3.7

1.1.4

Suspension/Steering

1.1.4.1

1.1.4.2

1.1.4.3

1.1.4.4

1.1.4.5

1.1.5

Vehicle Electrical/Electronics

1.1.5.1

1.1.5.2

1.1.5.3

1.1.5.4

1.1.6

Power Package/Drive Train

1.1.6.1

1.1.6.2

1.1.6.3

1.1.6.4

1.1.6.5

1.1.6.6

1.1.6.7

1.1.6.8

1.1.6.9

1.1.7

Auxiliary Automotive

1.1.7.1

1.1.7.2

1.1.7.3

1.1.7.4

1.1.7.5

1.1.7.6

1.1.7.7

1.1.8

Fire Control System

1.1.8.1

1.1.8.2

1.1.8.3

1.1.9

Armament

1.1.9.1

1.1.9.2

1.1.10

Automatic/Manual Ammunition Handling

1.1.10.1

1.1.10.2

1.1.10.3

1.1.10.4

1.1.11

Navigation/Remote Piloting

1.1.11.1

1.1.11.2

1.1.12

Special Equipment

1.1.12.1

All items required to convert basic vehicle configurations to special-purpose configurations

1.1.12.2

Blades, booms, winches, robotic arms or manipulators, etc., to equip wreckers, recovery vehicles, supply vehicles and other field work units

1.1.12.3

Furnishings and equipment for command, shop, medical and other special-purpose vehicles

1.1.12.4

Specialized sensors not included elsewhere

1.1.12.5

Mine detection, neutralization and marking equipment

1.1.13

Communications

1.1.13.1

1.1.13.2

1.1.13.3

1.1.13.4

1.1.13.5

1.1.14

Primary Vehicle Application Software

1.1.14.1

1.1.14.2

Software Loader Verifier (SLV)

1.1.15

Other Vehicle Subsystems

1.1.15.1

1.1.15.2

1.1.15.3

Off Vehicle Items

1.2.1

Logistics Management

1.2.1.1

1.2.1.2

1.2.1.3

1.2.1.4

1.2.1.5

1.2.1.6

1.2.1.7

1.2.2

Facilities

1.2.2.1

1.2.2.2

1.2.2.3

1.2.2.4

1.2.2.5

1.2.2.6

1.2.3

Training Products

1.2.3.1

Training for DT/OT Events

Facilities

Training areas

Ranges

Curricula/courseware

1.2.3.2

New Equipment Team Training

Facilities

Training areas

Ranges

Curricula/courseware

1.2.3.3

Sustainment Training

Schoolhouse Curricula/courseware

1.2.3.4

1.2.4

Tech Pubs/Data

1.2.4.1

Fielded Level (O&I) Tech Pubs and Data

1.2.4.2

Secondary Reparables Overhaul Standards

1.2.5

Support & Test Equipment

1.2.5.1

Peculiar Support Equipment

S&TE Unique to vehicle platform used primarily by Intermediate Level maintainers

S&TE Unique to vehicle platform used only by depot level maintainers

1.2.5.2

Common Support Equipment

S&TE common with other vehicle platforms, used primarily by Intermediate Level maintainers

S&TE common with other vehicle platforms, used only by depot level maintainers

1.2.6

Packaging, Handling, Storage and Transportation (PHS&T

1.2.6.1

1.2.6.2

1.2.7

Primary Vehicle Integration, Assembly, Test and Checkout

1.2.7.1

Manufacturing Assembly Data and Instructions

1.2.7.2

Manufacturing Test Plans, Quality Checks and Reports

1.2.7.3

Manufacturing Jigs, Fixtures and Tooling

AAA-INS-01002 v1.0 image1.jpeg image2.jpeg