JSF Digital Product Data - ndiastorage.blob.core ... · JSF Digital Product Data Jim Hollenbach,...

JSF Digital Product DataJSF Digital Product DataJim Hollenbach, Simulation Strategies, Inc.

JSF Modeling Information Sources Action Team25 June 2002

DISTRIBUTION STATEMENT A: Approved for Public Release; distribution is unlimitedRef: JSF02-0294, 7517

VISION

DISTRIBUTION STATEMENT A. Approved for public release; distribution is unlimited.

BE THE MODEL ACQUISITION PROGRAM FOR JOINTSERVICE AND INTERNATIONAL COOPERATION

DEVELOP AND PRODUCE AN AFFORDABLE NEXTGENERATION STRIKE FIGHTER WEAPON SYSTEM

AND SUSTAIN IT WORLDWIDE

3DISTRIBUTION STATEMENT A: Approved for Public Release; distribution is unlimited

LOCKHEED MARTINMULTI-SERVICE DESIGN

STOVL

CV CTOL

Lift Fan

Roll Nozzle

3-BearingSwivelDuct


SYSTEM DEVELOPMENT ANDDEMONSTRATION (SDD) SCHEDULE

SDD Start

Critical DesignReview

FY01 02 03 04 05 06 07 08 09 10 11 12CY01 02 03 04 05 06 07 08 09 10 11 12

PreliminaryDesignReview

Initial Operational Capability

STOVL CV

USMC USAF USN

UK

First FlightConventionalTake Off/Land

BLOCK 1• Basic warfighter capability• Flight qualified• Interdiction, limited air-to-air• JDAM/AIM-120

Block 1 Capability Development & Flight Test

Block 2 CapabilityDevelopment & Flight Test

BLOCK 2• Interdiction, limited air-to-air• Close air support &

destruction of enemy airdefenses

• Additional bombs qualified

Block 3 CapabilityDevelopment & Flight TestBLOCK 3

• Threshold compliant JSF w/ key weapons• All JSF missions• Additional missiles/bombs qualified

First Engine to Test

Low Rate Initial Production Start


GOVERNMENT & INDUSTRYPARTNERSHIP

• Lockheed Martin provides a Distributed Product Description (DPD)of the Joint Strike Fighter• Includes all authoritative information needed to represent the JSF’s

operational performance, logistical characteristics, and cost• Spans the engineering, engagement, mission, and campaign levels

• Government provides the simulation environment in which theDPD-based JSF will operate• Threat systems, friendly systems, logistics resources and infrastructure, Blue

& Red C4I, multi-spectral databases, terrain & atmosphere representations

Government and Industry willform a closer M&S partnership

than ever before!


Simulation Based Acquisition (SBA):

Shared Info is the Hub of IPPD

D R I V E R S

C o n c e p t

E x p l o r a t i o n &

Definition

Demonstrat ion /

Validation

E n g i n e e r i n g

M a n u f a c t u r i n g

& D e v e l o p m e n t

P r o d u c t i o n &

D e p l o y m e n t

Upgrade

and Replace

n t

P H A S E

1000

10010

MGMT

Jan Apr Jul Oct

OperationalConcept

Document

J O I N T S T R I K E

F I G H T E R

C4I Support Plan

Joint Strike Fighter

System ThreatAssessment

Report

Section 5 Packaging

Section 6Notes

Section 4 Performance

Verification

Section 3 Performance

Requirements

Section 1 Scope

Section 2 ApplicableDocuments

WING/TAILF I L L E T S

A I R F I E L DT A I L H O O K

A V I O N I C S

E N G I N E

LIFT/ FANE N G I N E

JORD JMS

Marines

Air Force

Navy

AUTONOMIC BATTLEFIELD

JSF PARADIGM

Logical

Logical

Logical

JSF DPD& other

shared info(e.g., threats)

Cost, Schedule &Program Mgmt

Mission Planning,Wargaming

T&E

Concept DevelopmentFunctional Design

Physical & Info System Design

Manufacturing

SystemRequirements

Models & Simulations

Logistics

Training

Distributed Networks

(JSF M&S Support Plan Fig. 5-3)


Components of theJSF M&S Toolset

Strike WarfareCollaborative Environment

(SWCE) Toolset

Engineering & ManufacturingCollaborative Environment

(EMCE) Toolset

(JSF M&S Support Plan Fig. 5-1)


Consistent, AuthoritativeInformation Sources Are Vital

• To ensure M&S-derived answers are correct– Establish validity by tracing analyses back to authoritative information

– Verify JSF meets requirements

– Reduce the confusion and bad analysis that arise if operating on wrongor logically inconsistent information

• To conserve resources, improve efficiency– Avoid having to repeatedly find, produce and/or translate the same

information

– Provide more timely analyses, resulting in shorter decision cycle timesand more efficient systems engineering

– Avoid the costs of correcting mistakes discovered late in program


JSF SBA Implementation Team

SBA Implementation Council

M&S User Action TeamFunctional needs

& processes

Analysis Training Test

M&S Tools Action TeamSoftware applications

Modeling InformationSources Action Team

Authoritative data

V&V

Actio

n Te

amQ

ualit

y co

ntro

l/risk

redu

ctio

nMission Systems

M&S working group

Associated work groups


Modeling Information Sources Action TeamPrimary Deliverables

• Electronic access to all information needed forrepresentations in SWCE and EMCE tools

• Accompanying glossaries and metadata toconvey information lineage and guide its use

• Training and technical support


Compile

Load

Paths to System Representations(refinement of JSF MSSP Figure 5-5)

Develop asoftware component

Develop a simulationapplication

Input data sets

Input data sets

Input data sets

Executableapplications

Model or simulationmodified to represent

a battlespace

Model or simulationdeveloped to represent

a system

Model or simulationinitialized to represent

a battlespace

(Fed

erat

e)ex

ecut

e(F

eder

ate)

exec

ute

(Fed

erat

e)ex

ecut

e

Load

Load

Compile

Data-driven system representation in another’s tool (e.g., Thunder, JIMM)

Software representation within another’s tool (e.g., ESAMS)

System representation as a dedicated application (e.g., JSF Virtual Simulator)

Info

rmat

ion

map

ping

, tra

nsla

tion,

pre

-pro

cess

ing

Authoritative infoin its original form

DIFs

Mostauthoritative

systeminformation

Information inapplication-specific

form


Information Types

• Parametric data

• Algorithms

• Software code

• Publications

• Subject Matter Expert knowledge

Initial focus has been on parametric dataInitial focus has been on parametric data


Data Characterization

• Regardless of its subject, data may be characterized by its:

– Trustworthiness: “authoritative” or “non-authoritative”

– Evidence in the real world: “empirical” or “derived”

– Context dependency: “context-independent” or “context-dependent”

– Granularity: “primitive” or “aggregated”

– Structure: “atomic” or “complex”

– Source (relative to the enterprise): “external” or “internal”

• Above characterizations are orthogonal

– A data element could be described by any combination


Simplistic View of Data Inputs

Engineering-levelM&S tools

Campaign-level

M&S tools

Mission-levelM&S tools

Engagement-levelM&S tools

Prim

itive

Aggre

gated

• JSF data sources

• Threat data sources

• Friendly data sources

• Natural environment data sources


A More Complete Picture

Engineering

Campaign

Mission

Engagement

Context-dependent data

Context-dependent data

Internally derived

Internally derived

Conte

xt-ind

epen

dent

data

Conte

xt-ind

epen

dent

data

Exter

nally

or in

terna

lly ge

nerat

ed

Exter

nally

or in

terna

lly ge

nerat

ed

Prim

itive

Aggre

gated

Normally some preprocessing(e.g., smoothing, adjustment) asdata is moved between tools


An Example Thread (simplified)

ENGINEERING

ENGAGEMENT

MISSION

CAMPAIGN

ACQUIRE

COVART

FASTGENFLIR 92

HITRAN

MODTRAN

RCHEM

SPIRITS

SHAZAM

ASM

DIADSBRAWLER

ESAMSMIL GOLD

RADGUNS MOSAIC

JSF Virtual Simulator

JIMM

GIANT EADSIM

LCOM

CFAM

THUNDER

AFMSS(CLOAR)

JSFPO-JSFPO-providedprovided

M&SM&S(SWCE)(SWCE)

LM-LM-providedprovided

M&SM&S(EMCE)(EMCE)

ACADCATIA RationalRose

NASTRANPGEN 4


Implications

• Much “authoritative data” will be internally generated– and hence most subject to outside skepticism

• LM and JSFPO must have a shared understanding ofthe analysis process and what organizations/tools willbe regarded as the authoritative source– requiring revisions to normal procedures


Information Flow (Logical Depiction)

MNSORD

C o n c e p t E x p l o r a t i o n &

D e f i n i t i o nD e m o n s t r a t i o n /

Validation

E n g i n e e r i n g M a n u f a c t u r i n g & D e v e l o p m e n t

P r o d u c t i o n & D e p l o y m e n tU p g r a d e a n d R e p l a c e

n t

P H A S E

100010010 MGMTJan Apr Jul Oct

Models & Simulations(authoring & analysis)

Modeling InformationSource Repository

(e.g., RAS)

Other militarysystems

(threat, friendly)

Naturalenvironment,infrastructure

Users

E-m

ail a

lerts

, dow

nloa

ds

Brow

sing

, dow

nloa

d re

ques

ts

via web(browsers,

e-mail, FTP) orother means

External (to JSF) Source Documents and Databases(from intel agencies, other program offices, NIMA, etc.)

Operationalcontext

(scenarios,doctrine, ROE,

etc.)

JSFInteractions(Pd, Pk,etc.)

Color key: JSFPO provided LM provided

DPDDPDASDBASDBMSEDBMSEDB

JSF Authoritative Modeling Information Database (JAMID)JSF Authoritative Modeling Information Database (JAMID)


Operational Context DB Scope(Enterprise-wide standards for analysis; in priority order)

• Scenarios– Road to war– Blue TPFD– Orders of battle (UOB, EOB, etc.)– Geographic area– Infrastructure targets, location

• Mission Groups• Missions• Vignettes (created by JSFPO)

• Use Cases (created by JSF IPTs)

– Initiating inputs, required actions, MOPs

• Natural environment conditions– Time of day, weather

• Concept of Operations (CONOPS)• Force doctrine• Tactics• Rules of engagement (ROE)• Firing doctrine• Infrastructure lay down (other than targets)

Not in Operational Context DB:– Study-specific archives

• Input data sets• Raw execution outputs• Discretionary analyst

decisions– e.g., Blue mission routes

– System C&P data• Context independent• Context dependent (e.g., Pk)

– Natural environment instancedata (MSEDB)

– Infrastructure C&P (MSEDB)

Othermilitary

systems(threat, friendly)

Operationalcontext

Natural / civil

environment

JSF

Interactions(Pd, Pk,etc.)

JAMID v N+1JAMID v N+1(developmental)(developmental)

Modeling Information Life Cycle

Othermilitary

systems(threat, friendly)

Operationalcontext

Naturalenvironment,infrastructure

JSF

Interactions(Pd, Pk,etc.)

JAM

ID R

epos

itory

(RAS

)

MNSORD

C o n c e p t E x p l o r a t i o n & D e f i n i t i o nD e m o n s t r a t i o n / Validation

E n g i n e e r i n g M a n u f a c t u r i n g & D e v e l o p m e n tP r o d u c t i o n & D e p l o y m e n tU p g r a d e a n d

R e p l a c en tP H A S E

100010010 MGMTJan Apr Jul Oct

Authoring tools(e.g., architecture, CAD)

Relevant information(data in tool-specific form)

Study-specificinput datasets

& software code

Analyst actionAnalyst action

Tran

slat

ion

serv

ices

(map

ping

, sem

antic

s/sy

ntax

)

JAMID Version NJAMID Version N(baseline)(baseline)

Raw M&S results

Smoothed / analyzed resultsDesignchangeMOMs

JSFJSFcontrolcontrolboardsboards

JSF changesholding tank Individual JSF

design changes

SSs s aa

Study-Study-specificspecificarchivesarchives

NIMA,DTRA,

NRO, etc.

ProgramOffices

IntelCenters

JSFPO,JFCOM,DoD, etc.

Threat C&PThreat C&Pinformationinformation

OperationalOperationalcontextcontext

informationinformation

NaturalNaturalenvironment &environment &infrastructureinfrastructure

C&P informationC&P information

Blue system C&PBlue system C&Pinformationinformation

Update cycle AUpdate cycle ATrigger: New JSF baselineTrigger: New JSF baseline

(batch update of JSF &(batch update of JSF &all other instance data)all other instance data)

JAMID InformationJAMID InformationModel changesModel changes

Structure & scopeStructure & scopeupdates due to tool changesupdates due to tool changes

Update Cycle BUpdate Cycle BTrigger: SWCE/EMCETrigger: SWCE/EMCE

change decisionschange decisions

MNSORD

C o n c e p t E x p l o r a t i o n & D e f i n i t i o n

D e m o n s t r a t i o n / Validation

E n g i n e e r i n g M a n u f a c t u r i n g & D e v e l o p m e n t

P r o d u c t i o n & D e p l o y m e n t

U p g r a d e a n d R e p l a c e

n t

P H A S E

100010010 MGMT

Jan Apr Jul Oct

Analysis tools(e.g., models, simulations)

DISTRIBUTION STATEMENT A: Approved forPublic Release; distribution is unlimited


Information Modeling Challenges


M&S Tool Data Engineering Process(DMSO’s Reverse Engineering for Data Integration and Sharing (REDIS) process, simplified)

Data InterchangeData InterchangeFormat specsFormat specs

Integrated DatabasesIntegrated Databases

Subject Area Information ModelSubject Area Information Model

Model 1Model 1InformationInformation

ModelModel


ModelModel


ModelModel


ModelModel

Model nModel nInformationInformation

ModelModel

Model 1Model 1data Filesdata Files



Model nModel nData FilesData Files


Reverse

Reverse

En

gin

eering

En

gin

eering

Integration/Synthesis

Fo

rward

Fo

rward

En

gin

eering

En

gin

eering

Data DictionaryData Dictionary

…

…


DPD Architecture Is Represented in UMLas a Collection of Layered Models

XML DIF

XML Schema

XML Schema

RDB Schema

Air System Capability Model for simulation input and

model derivation traceability

DatabaseServer

RAS Server

RASClient

Air SystemViews

Database programmingand connectors

Data formatting driven by XSLT rules

Air System Model(UML object model)

DPD Meta Model(UML Class model)

Graph Model(UML Class model)

Data Storage Model(UML Class model)

instance

encoding

encoding


JAMID Development Strategy

• Integrated development– Consistent information models for DPD, ASDB, etc.– Consistent user interface, procedures, training, etc.– Common distribution infrastructure (RAS, LM VPN)– Coordinated CM, update procedures, metadata, etc.

• Spiral development– A series of builds, prioritized per program needs

• Information to support an increasing number ofrepresentations, in increasing numbers of tools,interfaced to an increasing number of organizations

– Brawler datasets will be first cycle

• Various classification levels, as appropriate


Summary

• Breaking new ground to achieve major improvements

• Big change to how we do business

• Incremental delivery of capability, incremental changesfor users

• Requires careful planning and management

• The jury’s out on whether we’ll succeed- but we’re taking bets

DISTRIBUTION STATEMENT A: Approved for Public Release; distribution is unlimited

Back-Ups


MIS AT Members

• Action Team Leader: JSFPO MS&A military officer or government civilian[Maj Steve Bishop, USAF]

• JSFPO Team Technical Lead [Jim Hollenbach, Simulation Strategies]

• Lockheed Martin Team Technical Lead [Dr. Henson Graves, LM DPDArchitect]

• LM DPD/RAS Project Manager [Russ Campbell, LM]

• ASDB Project Manager [Steve Hix, Paradigm Technologies]

• JSF weapons information representative [Curtis Erickson, AAC/ENMI -Orion Technologies]

• Natural/civil environment representative [Floyd Adagio, Orion Networking]

• JSF Threat Working Group representative [Tim Armstrong, Veridian]

• Operational context representative [Roman Marzak, Veridian Engineering]

• DMSO representative [Roy Scrudder, ARL UT]

• Other representatives as approved by the SBA Implementation Council


Shared Responsibilities During SDD

The Government will: The SDD contractor shall:

Establish and maintain a Strike WarfareCollaborative Environment in which the DPD-basedJSF representations will operate, that spans thecollaboration focus areas of mission effectivenessanalysis, autonomic logistics analysis, engineeringand manufacturing analysis and cost analysis

Establish and manage an Engineering andManufacturing Collaborative Environment

Provide configuration-managed versions of a JSFSWCE Suite of Models and Simulations

Develop, populate, and manage the JSF DPD, which,as a minimum, shall provide, via a DIF, all the JSFinformation needed to represent the JSF in the SWCEand the EMCE SoM&S.

Develop, maintain, and manage the configuration ofa library of SWCE boxed sets. Develop translationsand Digital System Models (DSMs) not provided bythe WSC.

Develop the software that may be necessary toconvert DPD information into the form needed toinitialize or configure an individual model orsimulation for that portion of the SWCE SoM&S thatthe WSC uses. This shall include translations andJSF Digital System Models.

Provide an Authoritative Systems Database (ASDB)which is accessible through the JSF ResourceAccess System

Develop and maintain a web-based JSF ResourceAccess System

(JSF M&S Support Plan Table 1-1)


Dimensions ofInformation Coherency

Temporal coherence– The extent to which the data being used for different tools

and sites has the same time stamp

Organizational coherence– The extent to which all JSF Enterprise organizations are

using the same set of databases

Layer (tier, level, stratum) coherence– The extent to which all the information at a given level of

granularity (e.g., engagement level) is logically consistent

Granularity coherence– The extent to which the information at different levels of

abstraction is logically consistent

Hard

Hard

Very

Har

dVe

ry H

ard


Context Dependency

• “Context-independent” data– Entity attributes that remain stable regardless of its environment– Examples: structure, weight, radar signal, cost

• “Context-dependent” data– Conditional attributes (“it depends”)– Determined by:

• How the system is employed• The characteristics of its natural environment• Interactions with other systems

– Examples:• Speed, range, turn performance• Radar, IR and visual signatures• Engagement range, Ps, Pk, exchange ratio, targets killed


Compile

Load

Current JSF Definitions(initial attempt at DPD implementation)

Develop asoftware component

Develop a simulationapplication

Input data sets

Input data sets

Input data sets

Executableapplications

Model or simulationmodified to represent

a battlespace

Model or simulationdeveloped to represent

a system

Model or simulationinitialized to represent

a battlespace

(Fed

erat

e)ex

ecut

e(F

eder

ate)

exec

ute

(Fed

erat

e)ex

ecut

e

Load

Load

Compile

System rep data driven in another’s tool (e.g., Thunder, JIMM)

System rep coded in software in another’s tool (e.g., ESAMS)

System rep in own dedicated application (e.g., SAF, simulators)

Info

rmat

ion

map

ping

, tra

nsla

tion,

pre

-pro

cess

ing

Authoritative infoin its original form

DIFs

MostauthoritativeInformation

about asystem

Application-specificequivalents/abstractions

DSMDPD


Interactions with other Action Teams

• Identify representations of interest (User AT)

• Identify SWCE & EMCE tool information types (Tools AT)

• Identify authoritative sources for derived information (User AT)

• Define data quality documentation to support VV&A (V&V AT)

• Define metadata templates (User AT)

• Capture security, network and user interface needs (User AT)

• Plan JAMID/RAS user training and support (User AT)

• Establish user feedback for JAMID QA (User AT, V&V AT)

• Define threat data fill/update process (Threat Working Group)

Action Teams must work togetherAction Teams must work together

JSF Digital Product Data - ndiastorage.blob.core ... · JSF Digital Product Data Jim Hollenbach,...

Documents

Transcript of JSF Digital Product Data - ndiastorage.blob.core ... · JSF Digital Product Data Jim Hollenbach,...