nasa/esa pde 05 20 apr 05 multiview: common data schema for complex systems

U.S. U.S. ArmyArmy

MaterielMaterielCommaComma

ndnd

Mr. Jim ColsonMr. Jim ColsonMr. Jim ColsonMr. Jim ColsonNASA/ESA PDE 0520 Apr 05

MultiView: Common Data Schema for Complex

Systems

NASA/ESA PDE 0520 Apr 05

MultiView: Common Data Schema for Complex

Systems

NEED TO BE FASTER, MORE AGILE, LESS BUREAUCRATIC - NEED TO FIGHT THIS EVERYDAYNEED TO BE FASTER, MORE AGILE, LESS BUREAUCRATIC - NEED TO FIGHT THIS EVERYDAYNEED TO BE FASTER, MORE AGILE, LESS BUREAUCRATIC - NEED TO FIGHT THIS EVERYDAYNEED TO BE FASTER, MORE AGILE, LESS BUREAUCRATIC - NEED TO FIGHT THIS EVERYDAY

2A012605LOGSA Brief at Mid Atlantic Log. Mar 2005

USAMC LOGSA--Supporting Warfighters Globally

Outline

LOGSA and the GEIA-927 MultiView

Standard

MultiView Project Overview

Current Status and Future Plans for

MultiView Project



Key Players

Transfer of Function:

DA Mandated. AMC Tasked LOGSA Dec 2004

GEIA-927 (MultiView) Standard Supported by:



GEIA-927 (MultiView) Project Overview

Top Level ReqIS Logical IS Implementation Environment

Structural / HMEConceptual

Control

DataData

Logical Info Processing EnvironmentTop Level Req Structural / HMEConceptual

REQ

SPEC

Syn Env

Logical Implementation Structural / HMECONCEPTUAL

Support Sys & Dev Eng Env

1000

100

10

Jan Apr Jul Oct

MANUFACTURING

Manufacturing

Environment Management

Develop Common Data Schema

• Leverage Existing and Emerging Data Standards

• Accommodate Tools in Use by Candidate Pilots

• Work in the Gaps Where Required

Validate in Distributed COTS Testbed

1

2

3

4

Conduct DoD Pilots

• Data Interoperability • Consistency Management• Interaction with Legacy Tools• Integration of Legacy/Emerging

Data Sources

Manage Transition

• Implement Testbed Capabilities• Demonstrate Utility (Collect Metrics)

• Evolve Industry Consortium• Focus on DoD Program Mgr Needs

T e s t b e d S e r v e r

I n t e r f a c e s t o L e g a c y D a t a b a s e s

J D B C F u t u r eX M L

C u s t o mO D B C

T e s t b e d M a p p e r

A b r a m sC l i e n t

Ab

rams D

ata

N

avig

atio

n

Ab

rams D

ata

A

na

lysis

Ab

rams D

ata

N

avig

atio

n

Ab

rams D

ata

A

na

lysis

SP

AR

PF

SAE

xcel …

Da

ta

Qu

ery

Q u e r yA n a l y z e r

C O T S - b a s e d c o m m u n i c a t i o n s

Q u e r yT r a n s l a t o r

R e s u l t s A g g r e g a t o r

R e s u l t sT r a n s l a t o r

M u l t i V i e w S c h e m aM V _ E l e m e n t

A c t o r

E v e n t

P e r s o n O r g a n i z a t i o n

F a c i l i t y E n v i r o n m e n t F l o w

F u n c t i o nP r o c e s sT o o l

S y s t e mM a t e r i a l _

o r _ c o m p o n e n t

D e s i g n

D o c u m e n t

P l a n O b j e c t i v e

R e q u i r e m e n t C o n s t r a i n t

M u l t i V i e w S c h e m aM V _ E l e m e n t

A c t o r

E v e n t

P e r s o n O r g a n i z a t i o n

F a c i l i t y E n v i r o n m e n t F l o w

F u n c t i o nP r o c e s sT o o l

S y s t e mM a t e r i a l _

o r _ c o m p o n e n t

D e s i g n

D o c u m e n t

P l a n O b j e c t i v e

R e q u i r e m e n t C o n s t r a i n t

M o d e l2 0 4

O D B C

O r a c l e J a s m i n e S y b a s e F u t u r e

C O T SC O T SM o d i f i e d

C O T SM o d i f i e d



C O T SM u l t i V i e w -

s p e c i f i cM u l t i V i e w -



s p e c i f i cK e y

Imp

ort

Imp

ort

N a t i v eO r a c l e



Data Source Confusion

Today: Suboptimal, Reactive Program Management EnvironmentFuture: Proactive Management Enabled by Integrated Information

Today: Suboptimal, Reactive Program Management EnvironmentFuture: Proactive Management Enabled by Integrated Information

DemonstrationValidation

EngineeringDevelopment

Ops &Support

ConceptExploration

System Data Today

Data Shortfalls, Management Challenges– Stovepiped Tools & Data Stores With

Limited Scope and Scalability – Limited Interoperability Among Tools &

Data Stores– Error-Prone Traceability & Consistency

Optimized Management Environment– Enables Collaborative, Concurrent Effort

Across Distributed Sites– Timely Snapshots of Program Status

Across Multiple Information Domains– Complete, Integrated Picture of the

Program

System Data in the Future IDE

Top-Level Requirements

FunctionalDesign

HW/SWDevelopment

HW/SWDesign

Budget, Schedule,

Risk

Logistics &Support

OperationalNeed

EnvironmentRepresentations



• Formal Structure for Representing Spectrum of System Data

• Dynamic Schema Provides Means for Accommodating Emerging Data Representation Needs

Top Level Req IS Logical EnvironmentConceptual

Control

DataData

Logical Info Processing EnvironmentTop Level Req Structural / HMEConceptual

REQSPEC

Syn Env

Logical Implementation Structural / HMECONCEPTUAL

Support Sys & Dev Eng Env

CapabilitiesPerformanceDependabilityMaintainabilityConstraints

PlatformsSensorsWeaponsCommunicationTactics

HardwareSoftwareOperatorsDocumentation

HullMechanicalElectricalHydraulicPneumatic

Atmospheric

TerrestrialThreatAllied

ScheduleCostRiskStaffingProgrammatics

1000

100

10

Jan Apr Jul Oct

MANUFACTURING

Manufacturing

Material AcqFabricationAssemblyInteg / TestHandling / DelivFactory FloorRobots / Mach

FunctionData FlowControl FlowEnergy FlowMaterial Flow

Environment Management

Sys Eng Meth & ToolsHW/SW/HF Eng M&THME/Hyd/Pneum M&TPower/Propulsion M&T

Logistics / SupplyOperationsTrainingMaintenanceRepair

Oceanographic

Common Systems Information Schema Concept

A Broad, Extensible Representation Approach is KeyA Broad, Extensible Representation Approach is Key



Data InteroperabilityReuse & Management

Within a Domain, between Tools

GEIA-927 SchemaMV_Element

Actor

Event

Person Organization

Facility Environment Flow

FunctionProcessTool

SystemMaterial_

or_component

Design

Document

Plan Objective

Requirement Constraint

SystemRequirements Structural

System Design

System HW, SW Design

SystemsEngineering



Data InteroperabilityReuse & ManagementWithin a Program, Across Domains


Actor

Event

Person Organization


FunctionProcessTool

SystemMaterial_

or_component

Design

Document

Plan Objective


Logistics SupportSystems Engineering

SystemRequirements

StructuralSystem Design


Training

Repair

Supply

DD(X)Program



Data InteroperabilityReuse & ManagementWithin a Service, Across Programs


Actor

Event

Person Organization


FunctionProcessTool

SystemMaterial_

or_component

Design

Document

Plan Objective


USAF

SystemsEngineering

ConceptDevelopment

LogisticsSupport

SystemsEngineering

LogisticsSupport

ConceptDevelopment

JSFV-22



Data InteroperabilityReuse & Management

Within DoD, Across ServicesGEIA-927 Schema

MV_Element

Actor

Event

Person Organization


FunctionProcessTool

SystemMaterial_

or_component

Design

Document

Plan Objective


DoD

V-22

Joint StrikeFighterSpace

BasedRadar

DD(X)

F/A-18E/F

Virginia ClassSubmarine



COTSServer

Agents

AdministrationQueries

Schema Editing

Manufacturing

StructuralSystem Design

ConceptDevelopment


ProgramMgmt.

Operations, Logistics& Training

SystemRequirements

Test & Eval

Viewer


Actor

Event

Person Organization


FunctionProcessTool

SystemMaterial_

or_component

Design

Document

Plan Objective


Life Cycle System Management

Establish Traceability – Determine impact of changes across

domains– Perform complex analysis on integrated

information

Configuration Manage Data– Baseline across all information domains– Manage multiple options & tradeoffs– Be alerted when data of interest changes

or schedule periodic analysis of data

Graphically View or Edit Any Information

– Common interface to all information– Aids verifying data completeness



What Has Been Done?

Standards Based– ISO 18876 (IIDEAS) Basis for Data Modeling Methodology

– ISO 15926-2 (EPISTLE Core Model(ECM)) Initial Integration Current State of Data Schema

– Detailed Integration Procedure Defined– Standards Integrated (ongoing)

• ISO 10303 STEP (Standard for the Exchange of Product Model Data)• PAS 20542 – Systems Engineering• DoD Corporate Logistics Data Model• AP212 – Electrotechnical Design and Installation• AP239 – Requirements, Effectivity, Documentation, Class, State,

Activity (Systems Engineering)

– Data Concepts Mapped to Model

– Usage and Tailoring Guides Developed

Common Data Schema Development



Implementation Initiatives

• Initial Schema Implementation on Abrams

• Schema Training and some Utilization on Navy DD(X) Program.

•Interest From V-22 and Other Programs.

•LOGSA Acquisition Logistics Tools Schema Implementation.

Excel

Concept Exploration &

Definition

Demonstration / Validation

Engineering Manufacturing & Development

Production & Deployment

Upgrade and Replace

nt

PHASE

1000100

10

MGMT

Jan Apr Jul Oct

SPAR(Simulation)

Post-Fielding Support Analysis

JDBC FutureXML

Data Comms

GEIA 927 SchemaMV_Element

Actor

Event

Person Organization


FunctionProcessTool

SystemMaterial_

or_component

Design

Document

Plan Objective


ODBC

Future

NativeOracle

Database Interface Mechanisms

Data Mapping &Translation

CDDBLIFCMIS

FEDLOG

IETM

SBSX

ATAV

FVPDS

WOLFOSMISWLMP

LIDB

CCSS

AMDF

CBS XPFSA

RIDB

SB700-20FVPDS

SDS AMCOS

JEDMICS

ReqVal

PADDS

MEARS

WebCATS

ATIRS

COTSLegacyModified COTS

MultiView-specific

Key

Controller



ILS Planning/Analyzing

Alternatives

LogisticsSystem

Development

EvaluatePost Production

Support

Metrics Tracking –Recap

6710

6710

6710

Integrated Logistics Support (ILS) And Supportability Planning Documents Generation

Rule Based Expert System

Current Policy Compliant

Web Based

System Development & Demonstration

Operations & Support

Technology Development

Production & Deployment

B C

EnsureSupportability

Considerations

Concept Refinement

A

Provides Weapon System View

Supports Fleet Management

Metric Tracking

Weapon system Assessment

Performance Data

Standard Logistics Formats

Interface with LMP

Satisfies LSAR And LMI Requirements

Assists In TechnicalManual Development

Level Of Repair Analysis

Force Structure Evaluation

Sparing/Stockage Optimization

Repair Versus Discard

Life Cycle Cost Model

Trade Off/Comparative Analyses

Warranty Analysis

Reliability Growth Analysis

Risk Analysis

LOGSA Acquisition Logistics Tools



What is Next ?

Next Integration Steps– Further Integration of AP233 (Systems Engineering)– Further Integration of AP239 (Product Life Cycle Support)– Evaluate EIA-836 (CM) for Integration

Future Plans– Identify Industry “Voids” in Data Interchange Standards such as

LMI/LSA Data.

– Integration of Acquisition Logistics Data Elements

– Simplify Schema (Remove Little Used Areas to Reduce Complexity)

– Development of Domain-Specific Views• Facilitate Standard Review by Industry Experts

– Incorporate Comments & Revisions• Restructure Standard to Accommodate Views

– Send for Ballot in Late 2005

Common Data Schema Development



Moving Forward

Upcoming Meetings/Workshops– GEIA G33 (SE) & G47 (CDM) 2005 Quarterly Meetings:

• April 12-14 Phoenix, AZ

• June 20-23 Baltimore, MD

• Sept 19-23 Atlanta, GA (Annual Conference)

– LOGSA/SOLE/ASAALT Hosted ILS Conference and Workshops • May 3-5 Huntsville, AL (Enabling Life Cycle Logistics)

Government & Industry Working Group– Cross Service Representation (Army, Navy, AF, DLA)– Multiple Industry Representatives – Promotion of Standard at All Levels of Government & Industry.