SBA Yesterday & Today:

Current View of SBA inAdvanced Systems Engineering

andSystem-of-Systems

Environment

Dr. Judith Dahmann

• SBA concepts have been a topic of interest for several years– Where are we in implementing these concepts in today’s

systems acquisitions?

• Growing emphasis on Network Centric Warfare, CoalitionOperation and Systems of Systems– How do SBA concepts support tomorrow’s acquisition

environments?

“A concept which envisions greater and more integrated use of modeling and simulationin the acquisition process. DoDand industry would be enabled by robust, collaborative use ofsimulation technology that is integrated across acquisitionprograms and phases.”

November 1998

Simulation-Based Acquisition Defined

OriginsNeed for More Cost Effective Acquisition Process

• Declining defense budgets and changing force structure– Modernization/Transformation versus Recapitalization– 1995 Vice President’s National Performance Review (NPR) -- 25%

reduction in delivery time for new systems– Department of Defense (DoD) stretch of NPR goal to 50% reduction, plus

reduction in Total Ownership Costs

• Cost-performance consideration allow routine use of advancedIT, modeling and simulation tools– Defense Systems Affordability Council recognizes M&S potential

SBA BenefitsRisk Reduction

• Continuous evaluation of system development

• Rapid evaluation of concept design

• Reduce and delay need for physical prototype

• Facilitate continuous user participation indevelopment process

• Efficient development/evaluation ofmanufacturing plans

• Reuse of system software and hardware intraining simulators

M&S Use in the Army Acquisition Process, Dr Herbert K. Fallin, Jr; 1997

Original Goals

• Substantially reduce the time, resources and riskassociated with the entire acquisition process

• Increase the quality, military worth and supportability offielded systems, while reducing their total ownership coststhroughout the total life cycle

• Enable Integrated Product and Process Development (IPPD)across the entire acquisition life cycle.

1998 SBA Roadmap

• Joint SBA task force,including government andindustry, identified cultural,process, and technicalelements

• Identified actions needed toimplement new approach tosystems acquisitionefficiently, expeditiously, andnon-intrusively

Key Ideas

• Shared system or product description– a shared, definitive source of data describing the system which evolves as the system

matures and serves as a common reference for multiple disciplines through systemdevelopment life cycle

• Multiple concurrent views and assessments of the system– based on shared system descriptive data allowing for consideration of more options, and

their implications, at each stage of the development and acquisition process

• Early and continuous use of simulation– in lieu of hardware prototyping and live test; by representing as many aspects of a systems

in simulation for as long as possible, reducing costs of development

• Common tools– employed at different stages of the acquisition process and reuse of tools (including

simulations) which have been used by others, reducing cost and time and increasingcredibility since each user doesn't have to do all the tool development for themselves

Joint Strike Fighter

JSF Suite of Models and Simulations (SoM&S)

JSF Strike WarfareCollaborative Environment

(SWCE) Toolset

JSF Engineering & ManufacturingCollaborative Environment

(EMCE) Toolset

SWCE SoM&S EMCE SoM&S

JSF Distributed ProductDescription (DPD)

JSF Resource Access System (RAS)

Databases Databases

Authoritative SystemsData Base (ASDB)

Scenarios

MSDBMSDB

Scenarios

Geometric DataNon-geometric DataAnalysis ResultsBehavioral Data

Wargame models(e.g., MARS)

Other models

Hardware inthe loop

MARVEDS

Embedded SW

Engineeringanalysis models(e.g., ASAP, RTS)

Physical models & tests

DDXX

Aerial Common Sensor

Engineering Analysis/

ACS Virtual Prototype

Engineering Analysis/

ACS Virtual Prototype

Operational AnalysisSynthetic

Environment

Operational AnalysisSynthetic

Environment

Total Ownership Cost Model

Analysis

Total Ownership Cost Model

Analysis5/10/00 835GR.53.06

Operational Training

Synthetic Environment

Operational Training

Synthetic Environment

Spiral Development Loops

Army Future Combat System

Other Users (Army, Navy, Air Force, Joint, etc.)

Integrated Data Environment (Windchill™ based)

FCS Distributed Product Description (DPD)Shared Segment

FCS Army/Industry Resource Repository (FAIRR)

Scenario Databases

EnvironmentDatabases

Red System Data/Models

Blue System Data/Models

FCS PM Documents

Government LedFuture Combat Collaborative

Environment (FCCE)

FCS

M&

S U

pgra

des

FCS Advanced Collaborative EnvironmentLSI Led

Design/Engineering/Manufacturing Collaborative Environment (DEMCE)

FCS

M&

S U

pgra

des

Archived M&S

•Test, Evaluation, Analysis, Experimentation, Demonstration• Develop/refine/illuminate concepts, doctrine, TTP• View operational & force effectiveness parameters • Training

Management and Collaborative Tools

LSI Tools

Gov’t Tools

Gov’tPrivate

• Computer Aided Systems Engineering • Computer Aided Design• Computer Aided Manufacturing• Virtual System Assessment• Visualization• Design/Engineering Review

LSI Private

Gov’tPrivate

LSI Private

Interfaces

Technology Adoption Life Cycle

Innovators Early Adopters

EarlyMajority

LateMajority

Laggards

Where are we today?

Boeing 777?JSF?

SBA Roadmap?

…probably further to the left than we would like to think…..

DDXX?FCS?

NDIA SBA Conference May 2001 Findings

• Progress has be made• Programs/Services are creating the

systems engineering environments fortheir specific applications

• Industry investing for their owncompetitive advantage

• However….• Limited attention to system-wide issues• Ongoing developments will not ‘work

together’ across systems throughout thelifecycle to create the needed leverage

• Many needed components are availablefrom ongoing efforts, but these are notdesigned to be reused, there is duplication ofefforts and there are missing elements

‘System of Systems’ Pose New Challenges

• Systems of systems pose new challenges– For operations– …. and for development

• To address these challenges, common environments whichcan be used across systems are needed

• In each of the Services, and at the DOD level, new initiativesare being created to address the SOS development issues

• These new initiatives provide broader and more extensibleadvanced systems engineering environments to supportfuture system development

Air Force Joint Synthetic Battlespace

Today: Unable to Fully Understand

Operational Impacts in aHeavily VegetatedEnvironment

--Camouflage, Hyper-spectral,…

Future: Able to Understand

Operational Impacts in allEnvironments

Government Sites

Contractor Sites

ACQUISITIONS&T, R&D, T&E

JNTF(SWC)

IWC

SMC

OFFUTT AFB (RJ MT)

AFC2TIGFt Hood (CCTT)

TACCSFTACCSF

AFRL Mesa56 FW

RJ19 SOS

NCAOC

Bell

Today: Unable to Fully Understand

System of Systems andEnvironmental Impacts

Future: Simulations Readily Available

to Assess SystemComplexities

A Common ArchitectureThat:

-Represents the NaturalEnvironment Realistically

-Physics Based Sensor Models

-Allows Integration of LegacySimulations

Joint Synthetic BattlespaceWARFIGHTER

Requirements,

Training &

Rehearsal

Army Joint Virtual Battlespace

SMART(Simulation & Modeling for Acquisition,

Requirements and Training)……Tool To Support The Objective Force and

Future Combat System

JVB 04-19a

NTM

Global Hawk

JSTARS

Carrier

ACS

Comanche

M1A2

M577

Joint Environment

Army Environment

JointStrike

Fighter

Command andControl

FCS Network Centric

JVB Design Includes:• Joint Forces

• Legacy Forces

• Objective Force

• Future Combat Systems

- C3

- ISR

- Robots

- New Weapons

• Dynamic Weather

• Dynamic Terrain

• High Fidelity Terrain

• Certified Data

Navy Collaborative Engineering Environment

RequirementDocuments

RequirementAnalysis ToolMEMO

SRDMNSORD

DOORS

StructuredRequirements

FunctionAnalysis Tool

CORE

Function

ModelFuncti

onModel

FunctionInformation

FunctionBaselines

Interchange(Server)

ProjectRepository

SystemsSpec

PhysicalImplementation

Information

ResourceConstraint

InterchangeClient

ArchitectureRepresentation

RationalRoseDIAD

JMAAT

OperationalViewSystem

ViewTechnical

View

ArchitectureInformation

Experiment DataSystem Data

InterfaceData

LSSEAnalysis

COPATRABRCA

TRIMSM&S

COST MODELSHSI

CAD/CAM

Joint Distributed Engineering Plant

• JDEP will build interoperableforces by providing a tool for

• Developers to engineerinteroperability into theirsystems

• Testers to test and evaluateinteroperability among systems

• War fighters to assessoperational capabilities of forces

• Single Integrated Air Picture(SIAP) Systems Engineer

• Pilot development of systems ofsystems engineeringenvironment for the DOD

JDEPJDEP2002/32002/3

AWACS30/35 w/RSIP

Boeing Seattle

AEGISShips

B/L 5.3.7.2NSWC DD

ATRC/DOC

PATRIOTPDB 5

Huntsville

E-2 ESTELLE PAX River

TPS-59MCTSSA

ScenarioFederationManager

DataCollector/

Viewer

AWACS TPS-59Patriot E2 AEGIS

Interoperable Systems of Systems Require Interoperable Development Environments

Army JVB

Navy CEE

AF JSB SharedSystem of Systems

DevelopmentCapability

JDEP

As with interoperable war fighting capabilities, Service and Jointdevelopment capabilities must work together to create the needed

system of systems development and engineering environment

Coalition Partners

Challenges

• Challenges of advanced systems of systems engineeringenvironments parallel those of interoperable operational systems ofsystems

• Cooperation among Services and DOD communities to create needcomponents

• Need ways to continue to identify and address technical and policyareas– Key interfaces and common standards– Opportunities for shared developments– Building components for reuse and sharing– Routine application of shared engineering capabilities throughout the

system of systems life cycle

Future VisionFuture Vision

Simulation-supported system of system engineering environmentswill develop hand-in-hand with mission area capabilities

20032003TodayToday

Sys ASys A

Sys XSys X

Sys DSys D

Sys BSys B

Sys CSys C

Sys YSys Y

Joint StaffJoint StaffMission Areas (MA)Mission Areas (MA)

“To Be”“To Be”

- Precision Engagement- Deployment/Redeployment- Dominant Maneuver- Strategic Deterrence- Overseas Presence &

Force Projection- Special Operations- Joint C2- Focused Logistics- Information Superiority- Multinational Ops &

Interagency Coordination- Full Dimensional Protection

Mission FocusMission FocusSystem FocusSystem Focus

Sys ASys A

Sys XSys X

Sys DSys D

Sys BSys B

Sys CSys CSys YSys Y

Sys ASys ASys BSys BSys DSys D

JointJointC2C2 JointJoint

C2C2

System of System Engineering Environments

Summary

• Concepts of simulation support to acquisition and development arekey to advanced engineering environments

• Early emphasis on individual systems and improved efficiency

• Future direction toward enabling systems of systems development,test and war fighter assessment

• Interoperable systems of systems to support joint war fighting requiresshared system of system engineering environments