LOG 211 Supportability Analysis

Student Guide

Log 211 Supportability Analysis

Student Guide

Logistics Product Data/SAE GEIA-STD-0007 Database

Content

SAE GEIA-STD-0007

Slide 41. Lesson 4: Logistics Product Data/SAE GEIA-STD-0007 Database

Welcome to Lesson 4 on the Logistics Product Data/SAE GEIA-STD-0007 Database.

Disclaimer: The supportability analysis tools identified in the LOG 211 course are provided solely to assist defense acquisition workforce professionals to identify best value product support solutions which optimize system readiness and life cycle cost. Neither the Department of Defense or the Defense Acquisition University provide any warranty of these tools whatsoever, whether express, implied, or statutory, including, but not limited to, any warranty of merchantability or fitness for a particular purpose or any warranty that the contents of the item will be error-free. The analytical tools cited in this LOG 211 course should under no circumstances be considered as being all-encompassing, and their use in this training course in no-wise meant to endorse the capabilities or products of any particular individual, company, or organization.

Introduction

Content

Slide 42. Topic 1: Introduction

Content

Technology Maturation & Risk Reduction

Technology Maturation & Risk Reduction

Slide 43. Life Cycle Management Framework –

Where Are You? What Influence Do You Have?

This lesson introduces students to Logistics Product Data (LPD) and the SAE GEIA-STD-0007 compliant database within which that data resides, called the Logistics Product Database. In addition, this lesson explores both the Original Equipment Manufacturer (OEM) and Life Cycle Logistician (LCL) roles in the design, development, validation, and management of LPD and its database.

Where Are You?

Initialization of the Logistics Product Database typically occurs in the Materiel Solution Analysis (MSA) phase of the Life Cycle Management Framework. Initialization includes updating incomplete or missing data in a predefined SAE GEIA-STD-0007 database structure consistent with system and support requirements (i.e., system product structure and operations and maintenance (O&M) requirements).

In the Engineering & Manufacturing Development (EMD) phase, the data matures as Supportability analyses are conducted and their results populated in the Logistics Product Database.

What Influence Do You Have?

Supportability Analysis depends on the accuracy of the product structure and data. The OEM design, develops, and populates the Logistics Product Database. The LCL proofs the OEM’s work, assuring the integrity of the information that will be used in subsequent Supportability analyses and its usefulness to both logisticians and design engineers.

MSA Phase: Through early involvement, the LCL exercises the greatest influence over the correct and complete Logistics Product Database specification, design, construction, and initial population. This occurs through the identification and incorporation of accurate design and Operations and Maintenance (O&M) requirements into the database.

EMD Phase: As data matures, the LCL runs reports and validates analysis results in the database. At this stage, the LCL primarily influences the support and supports the design.

Content

Slide 44. LPD Lesson Approach

The Set Up, Analyze, and Report Findings approach, as shown on this slide, will frame the discussion on LPD creation and maintenance. This lesson will go into detailed discussions of each of these three process steps.

Key questions in this lesson are:

What is Logistics Product Data (LPD)?

Where do I store the LPD?

Where do I access the data to perform Supportability analyses?

What updates to the LPD result from these analyses?

Where do I update the LPD with the results?

Whom should I inform of analysis results and any identified issues?

What documents are refined and when?

Content

Slide 45. Topics and Objectives

Overview of Logistics Product Data and Logistics Product Database

Content

Slide 46. Topic 2: Overview of Logistics Product Data and Logistics Product Database

Technology Maturation & Risk Reduction

Slide 47. What Is Logistics Product Data?

Logistics Product Data are like the words (data elements) used in the language of support requirements. The SAE GEIA-STD-0007 (grammatical rules) specifies how these words form meaningful sentences (support requirements). The 12 Integrated Product Support (IPS) Elements (chapters) organize the Supportability plot (objectives) to achieve Affordable System Operational Effectiveness (ASOE), to include:

Product Support Management*

Design Interface*

Sustaining Engineering*

Supply Support

Maintenance Planning & Management

Packaging Handling Storage & Transportation (PHS&T)

Technical Data*

Support Equipment

Training and Training Support

Manpower and Personnel

Facilities & Infrastructure

Computer Resources

Content

Slide 48. Where Is the LPD Located?

The LPD is located in a highly structured, relational database comprised of 108 tables of information. The Logistics Product Database serves as the single repository for all Supportability Analysis related Logistics Product Data throughout the system life cycle.

The Supportability Analysis tool allows LCLs to import and export data, run standard reports, and run detailed customized queries that cross-connect many tables together.

Database structure

Depth of data reflects the complexity of the system being developed.

Structure reflects system hierarchy.

As data mature, the program's Logistics Product Database is the structure for the common language necessary to refine data as further Supportability analyses are conducted.

Data format and attributes

Each piece of data (data element) in the database structure is assigned certain attributes/values in accordance with the SAE GEIA-STD-0007 standard established by the former Government Electronics and Information Technology Association (currently known as “TechAmerica”.

Database Tables

Tables align with certain Supportability analyses (e.g., Table B provides data from R&M/FMECA/RCM Analysis and Table C, O&M Tasks, provides data from the Maintenance Task Analysis).

Important: A mature database also assists in preparation of complex data deliverables (e.g., the program Technical Manual)

The data tables are relational (i.e., interconnected/linked); therefore, it is imperative that data be entered into the correct locations and in the correct format; an incorrect entry impacts many different areas.

Several applicable and SAE GEIA-STD-0007-compliant Supportability Analysis tools exist, including:

powerLOG-J (Note: This tool is used in LOG 211 Supportability Analysis)

Freeware for Government and industry

Available from US Army Logistics Support Activity (LOGSA) website

Contains many templates for reports, called Logistics Support Analysis Record (LSAR) Reports (e.g., LSAR-036, LSAR-080)

SLICwave

Commercial Software; not freeware

Contains preset tools to assist with creating and maintaining Logistics Product Data necessary for Supportability Analysis

Compliant with S1000D Data Module Technical Publishing

Omega

Commercial Software; not freeware

Enhanced Automated Graphical Logistics Environment (EAGLE)

Commercial Software; not freeware

Proprietary technical publishing module available using a default Data Type Definition (DTD) schema

Others

See the LOG 211 Supportability Analysis Capstone Notebook for a summary of other commonly used analysis tools.

Content

SAE GEIA-STD-0007

Slide 49. SAE GEIA-STD-0007

The SAE GEIA-STD-0007, Logistics Product Data, and its accompanying Handbook, SAE GEIA-HB-0007, detail the database table relationships, data elements, and progression of data refinement through each life cycle phase.

SAE GEIA-STD-0007 provides an industry standard for acquisition and exchange of LPD, providing:

Universally accepted Data Item Description (DID) DI-ALSS-81529 to contract for the Logistics Product Database citing SAE GEIA-STD-0007, SAE GEIA-HB-0007, and standards-based attribute collection sheet

Universally accepted standard reports along IPS Element functional areas

Data requirements

Data element attributes – Distinct or unique bits of information that provide IPS Element information for components and parts

Specific data format – Enables error free data transfer and interpretation among diverse teams having different product support roles

Data Tables – Collection areas or ‘buckets’ for like data; represented in specific tables in the database

Exchange protocols for data communication

Controls data transfer between organizations, preserving both data integrity and relationships

Promotes tool independence: Structure of Logistics Product Database enables standards-based import and export of data through a built-in tool, enabling the OEM to share data among its partners as well as the Government in any available standard compliant tool

Data transfer is accomplished through the use of Data Exchange Standards (DEX) that enable international compliance with world-wide supporting organizations

Logistics Product Database is built for maximum data reuse—“build once, use many times”

Maintenance Task Tables are directly reused in the system’s Technical Manuals via standard data module import/export strategy (S1000DTM)

S1000DTM is the International Specification for Technical Publications using a Common Source Database

S1000DTM is maintained by AeroSpace and Defense Industries Association of Europe (ASD), United States Aerospace Industries Association (AIA), and the Air Transport Association (ATA))

A common standard with common terminology bridges potential language gaps between engineering and logistics functional activities and data exchange

SAE GEIA-STD-0007 replaces the cancelled MIL-STD-1388-2B, Logistics Support Analysis Record (LSAR); it re-establishes the Industry/DoD exchange of Logistics Product Data in a common XML-based format

Output from the Logistics Product Database, because it is compliant with SAE GEIA-STD-0007, can interface with other tools compliant with international standards; (e.g., S1000D enables reuse of LPD maintenance task data for Technical Manual publishing)

Content

Slide 410. Initial and Mature Database – Inputs and Outputs

This diagram provides a high-level view of the inputs, process, and outputs of Logistics Product Data/Database creation and maintenance.

The database is generated by iterative updates and serves as both an input and output environment that enables all Supportability analyses.

Initially, there is not a lot of data. The database is populated with O&M requirements (e.g., Materiel Availability) and product structure (i.e., system hierarchy), representing the backbone of the Logistics Product Database. All further updates build upon this structure.

As Supportability analyses are completed, they become inputs into the database, enabling other more refined analyses.

Slide 411. ASOE Model

Logistics Product Data and its database contribute to all parts of the Affordable System Operational Effectiveness (ASOE) model by:

Providing the single repository of data throughout the system life cycle (all resource requirements for logistics elements)

Facilitating an interoperable approach to managing product and technical data

Providing data required to perform analyses that create, assess, and improve product support strategies

Having a SAE GEIA-STD-0007 database brings with it better fidelity in Supportability Analysis, a more supportable design, and, most importantly, a way for the LCL to track the quality and completeness of the data and reports -- this adds value and saves program cost.

Set Up – Database Initialization and Data Exchange

Content

Slide 412. Topic 3: Set Up – Database Initialization and Data Exchange

Slide 413. Set Up

Both the OEM and the LCL play important roles during the initialization of the Logistics Product Data within the program’s standards-based database.

The OEM builds, populates, and updates the Logistics Product Database.

The LCL ensures the data is available, accurate and complete for:

Engineering and logistics requirements

Supportability analyses and

Product support strategy formation

Role of the Integrated Product Team (IPT)

During the initial Set Up of the LPD, the IPT:

Identifies roles: Who is doing what?

Defines and enforces logistics product data quality assurance goals and expeditious data issue resolution path

Defines schedule/timeline for running standardized reports error free

Establishes Working-level Integrated Product Team (WIPT) expectations, roles and objectives for LPD initialization and update process

Content

Slide 414. Database Initialization – Populate System Requirements

Populate System Requirements – The A Table, Operations and Maintenance Requirement

Logistics Product Data is populated from:

Initial Data: System-Level/Mission Profile requirements, such as Materiel Availability, Operational Availability, Materiel Reliability, Mean Down Time specified in the ICD, CDD, and other documents.

Mature Data: Results from Supportability analyses and other program activities, which initially populate and continuously refine the Logistics Product Database.

Content

Slide 415. Database Initialization – Build Product Structure

Defining Product Structure—The X Table, Indenture

The OEM uses Technical Data—such as Computer Aided Design (CAD) models, 2D drawings, and hierarchy diagrams—to define the product structure and build the database to reflect appropriate and consistent levels of indenture. The system’s technical data matures as the system design is defined, tested and refined. Levels of indenture specify system components and establish the product structure—how the system, sub-systems, and components interrelate—down to the lowest appropriate level for maintenance concept compliance; (e.g., determine if lowest indenture is a Shop Replaceable Unit (SRU) or the SRUs piece parts).

The OEM typically 1) defines the indenture in a simple spreadsheet as a preliminary step in constructing the database structure. Additionally, the product structure (indenture) can be exported from Computer Aided Design (CAD) Tools. The OEM then 2) creates the structure using standardized processes in a SAE GEIA-STD-0007-compliant database tool, such as powerLOG-J. The tools map key (X Table) fields, such as Logistics Control Number (LCN) discussed on the next slide, across multiple tables so that the Maintenance (C tables) and Provisioning (H Tables) are always aligned with the product structure.

Content

Slide 416. Table XB in the LSAR Tool – powerLOG-J

IPS Element supportability attributes are linked dynamically to the product structure through the SAE GEIA-STD-0007 data tables by unique keys (or identifiers), such as a Logistics Control Number (LCN). The LCN is a unique identifier (ID) of that item and its position in the hierarchy. The LCN enables the return of all relevant information unique to that LCN in the database. The LCL may then export that data into a report for further manipulation and analysis, however required. Information accessed by LCNs includes:

Relationship of child to parent

Manufacturer

Part number and name

Number of items per that assembly

Provisioned item associations (answers whether the item is needed as a repair part for provisioning)

How to maintain the item

Whether to repair or throw away (Source, Maintenance, and Recoverability (SM&R) code)

What failure modes are associated as local or system effects

Mean Time between Failure (MTBF) value

Associated static part data (e.g., unit cost)

Associated dynamic parts application data (e.g., where is the same part applied throughout the system)

Content

SAE GEIA-STD-0007

Slide 417. Why LCLs Need to Know How SAE GEIA-STD-0007 Works

The parent-child relationship (who belongs to whom) established by the indenture level plays a role in everything, and LCNs are an example of this.

Logistics Product Data are organized by LCNs that incorporate Level of Indenture and link Maintenance Significant Items to their attributes, maintenance tasks, equipment, and resources.

If an error is found and the indenture changed, the associated data and its analysis inputs/outputs could also be in error. In other words, upon finding an error, all data associated with that error must be reviewed for accuracy and updated if necessary. Recognizing and correcting errors in LCN early has a big pay-off by reducing extensive rework potential.

Note: As part of the standards-based application, LCNs are populated by standard processes and database rules, as defined by SAE GEIA-STD-0007.

Content

Slide 418. Parts Application

Another example of the impact of correct indenture levels is Parts Application. All Integrated Product Support (IPS) Element data is associated to the product structure by indenture to form parts applications. In other words, the same part can be located in several different assemblies and different applications or functional roles. The result: A single part number may be assigned several: Source, Maintenance, and Recoverability (SM&R) codes with unique maintenance tasks, depending on where it is located.

These relationships are captured in the Parts Application (HG) table.

Content

SAE GEIA-STD-0007

Slide 419. Data Exchange – Validating Standards-based LPD

During Set Up, the Government requests and imports the LPD in the form of an export document from the OEM into its Supportability Analysis tool. When importing data into the Supportability Analysis tool, the LCL validates that the data is in the correct SAE GEIA-STD-0007 xml standard format, which conforms to the requirements outlined in the contract.

Should an error occur while importing, the LCL should note the type of error but not attempt to fix it. The LCL is not personally responsible for database errors; however, as part of the IPT, the LCL coordinates with their team member responsible for managing the SAE GEIA-STD-0007 database.

Establishing Contract Requirements

Contract Statements of Work (SOW) or Performance Work Statements (PWS) provide for the identification of the LPD and the database as a specified deliverable from the OEM. The IPT should investigate the each acquisition phase contract for the following:

Does the contract specify the Logistics Product Data and the Logistics Product Database as deliverable items and specify the means of delivery to the Government?

Is it in the contract requirements that the OEM deliver the data to the Government? Is the frequency of delivery specified?

Does the contract specify that the contractor must comply with SAE GEIA-STD-0007? See DI-ALSS-81529 and Contract Data Requirements Lists (CDRLs) related to this Data Item Definition in the contract.

It is a best practice to establish a business rule for including contractual requirements for the delivery of specific data and maturing that data through Supportability Analysis inputs. The delivery requirement should be scheduled as an iterative deliverable so the Government has a continuing oversight role in its quality assurance.

Analysis – Validate the LPD and Product Structure

Content

Slide 420. Topic 4: Analysis – Validate LPD and Product Structure

Content

Slide 421. Analysis

Given the importance of the LPD to conduct effective Supportability Analysis, LCL/IPT fundamental roles are LPD:

Quality assurance

Conformance with contractual requirements

This lesson topic details the steps the LCL takes in this data management role.

Logistics Product Data Quality control is an iterative and continuous process, repeated alongside Supportability Analysis progression.

Content

Slide 422. Validate the LPD – Table A – O&M Requirements

The OEM, or others authorized by the program’s Configuration Management Plan, will continually enter data in the Logistics Product Database as Supportability analyses generate outputs. The LCL must validate that data, both before and after each analysis.

Content

Slide 423. Validate Product Structure – Identifying Indenture Levels

The database structure must support the system requirements specified in the Capability Development Document (CDD), design criteria, system hierarchy, and other program documents. The LCL’s role is to compare the indenture levels established in the database against these documents to validate that requirements have been met.

Remember the importance of this step. The indentured product structure becomes the primary key for all Supportability Analysis data.

Content

Slide 424. Validate Product Structure – Checking the XB Table

Line Replaceable Units – Shop Replaceable Units

Note how the hierarchy for the Identification Friend or Foe (IFF) sub-system assigns individual components with LRU and SRU designations:

Strike Talon IFF System Product Structure Spreadsheet

LCN

Hierarchy

Item Name

QTY

Indenture A

Indenture B

Indenture C

Indenture D

Indenture E

A

End Item

STRIKE-TALON

1

x

 

 

 

 

ACA

SubSystem

COM/NAV SYSTEM

1

 

x

 

 

 

ACAG

Assembly

IFF SYSTEM AN/SPG-4

1

 

 

x

 

 

ACAGAA

LRU

CONTROLLER PWR/DISC

1

 

 

 

x

 

ACAGAAA

SRU

ANTENNA DRIVE ELCT

2

 

 

 

 

x

ACAGAG

LRU

TRANSPONDER UAV

1

 

 

 

x

 

ACAGAGA

SRU

ANTENNA RADALT

2

 

 

 

 

x

ACAGAGG

SRU

RADALT

1

 

 

 

 

x

If a component is reparable, it is designated as an LRU or SRU, and maintenance tasks are associated with the items’ failure modes.

Note: In this course, the terms “LRU” and “SRU” are used; some component agencies use the terms Weapon Replaceable Assembly (WRA) and Shop Replaceable Assembly (SRA), respectively.

Line Replaceable Unit (LRU)

Assembly level, with additional items inside (Shop Replaceable Units)

Items you can work on at the field level (forward handled)

Shop Replaceable Unit (SRU)

Items inside the LRU (assembly)

Items not forward handled

Selected Component Parts

Piece parts below SRU

Proprietary software; components easily bent or broken; lab environment required; components impacted by dust, sea air, mud, or corrosion; high level of skill required; diagnostics equipment

Comprehensive policies and strategies are associated with LRUs and SRUs and are defined in the CDD’s Maintenance Concept. The SAE GEIA-STD-0007 standard dictates the database fields labeled LRU/SRU.

Content

Slide 425. Run/Validate Standard Reports

The LCLs may read and QA the database straight from reports generated by the Supportability Analysis tool. These reports include error codes and a legend from which LCLs may diagnose mistakes. Errors in reports are useful indicators of problems with the data or database.

Content

Slide 426. Run/Validate Standard Reports – LSAR 080 Bill of Materials

As Supportability Analysis matures with time, the information contained in the LCL’s reports also matures. For example, if one of the Supportability analyses is not mature enough for associated data to be loaded, the relevant reports may not run, run with error or with headers and no information. LCL can run reports as a reliable indicator of data completeness.

Use the error code legend below to diagnose errors in the Strike Talon Bill of Materials (BOM) Report.

Part 2 – Error Listing

Report Findings – Report and Resolve Issues and Update Database

Content

Slide 427. Topic 5: Report Findings – Report and Resolve Issues and Update Database

Content

Slide 428. Report Findings

In the Report Findings step, the LCL reports any initial issues (e.g., incorrect product structure or system requirements data) with the Logistics Product Database to the appropriate IPTs for resolution. When the data matures and significant updates occur, the LCL uses program IPTs as the appropriate forum to introduce potential impacts to requirements, design or support strategy. By keeping the IPTs continuously informed, the LCL is more likely to gain concurrence and approval for recommended courses of action.

Content

Slide 429 Report Coordination – IPT Communication Paths

The LCL shares standard reports, errors and data integrity issues with Supportability Analysis leads through applicable IPTs; (i.e., IPT that the particular report is best aligned). Examples of IPTs involved in LPD initialization include:

Technical Data IPS Element- Product Support Management IPT

Initializes database by importing product structure and validating technical data.

The LCL notifies the IPT of Technical data conflicts between data sources such as 2D drawings and CAD models.

Product Support Management IPS Element – Requirements Management IPT

If data are loaded incorrectly into the database, findings are reported and resolution is handled through this communication chain.

If LCL finds errors, they resolve early so subsequent Supportability analyses are correct and potential rework is minimal.

Recall the impact of incorrect data. The OEM must accurately trace requirements from the CDD and input them into the database tables; (e.g., A and XB Tables). These O&M fields, such as number of systems fielded, must be correct in order for all downstream analyses/calculated variables to be correct. An error here is therefore compounded everywhere else and corrupts functional area report results that rely upon calculated fields such as Maintenance and Provisioning Reports.

Exercise and Simulation

Content

Slide 430. Topic 6: Exercise and Simulation

Content

Slide 431. Exercise and Simulation Overview

Resource: Strike Talon Hierarchy Acronym List

Strike Talon Acronym

Term

Com/Nav

Communications/Navigation

IFF

Identification, Friend or Foe

Aux

Auxiliary

UHF

Ultra-High Frequency

R/T

Receiver/Transmitter

SATCOM

Satellite Communications

Pwr

Power (like in power switch)

RADALT

Radar altimeter

IMMC

Integrated Mission Management Computer

MFAS

Mid-Frequency Active Sonar

Content

Slide 432. Exercise

Content

Slide 433. Simulation

Summary

Content

Slide 434. Topic 7: Summary

Content

Slide 435. Takeaways

Content

Slide 436. Summary

Congratulations! You have completed Lesson 4: Logistics Product Database/SAE GEIA-STD-0007 Database.

The SAE GEIA-STD-0007 is the foundation that the Logistics Product Data and Supportability Analysis are built. Normally, a course on the topic is about a week long, with another week for an introduction on how to implement the database using a specific tool. If you are to be designated the LCL and Logistics Product Database expert, it is recommended that you consider becoming immersed via formal training and having your organization purchase the STD and Handbook. These courses will demystify the area and give you solid footing from which to grow your skills.

4-42 of 42

January 2013

Final v1.3

January 2013

Final v1.3

4-41 of 42