AIAA Presentation

1

Simulation Based Acquisition -- Key Concepts
-- Simulation Interoperability Workshop S99
Robin Frost Office of the Under Secretary of
Defense (Acquisition and Technology) DTSEE/SE (703
) 695-2300 frostrl_at_acq.osd.mil
2
THE GOALS

• Vice Presidents National Performance Review -
• Cut delivery time for new systems by 25
• Department of Defense -
• Stretched goal to 50 reduction of cycle time
• Set goal to reduce Total Ownership Cost
• Defense Systems Affordability Council -
• Recognized potential of MS
• Set SBA as one of the top initiatives to realize
  the stretch goal

3
WHERE IS COST DETERMINED?
100

90 of Total Cost Set Before Production
85 by End of System Definition
Decision Affecting Cost
70 by End of Concept Studies
50
0
3
6
15
1
35 years
System Life Cycle
Logistic Support Analysis Handbook, J. Jones
Life Cycle Costs Are Locked in During the Up
Front Design and Development Process
4
DRIVERS OF LIFE CYCLE COST
Logistics Support Costs (60)
Operations Costs (12)
Acquisition Costs (28)
Recurring Spt (92)
70 10 20
67 32 1
Personnel
Maint Labor
72 2 12 14
POL
Fabrication
Repair Materiel
Misc
Documentation
Replen Spares
Investment (8)
Design
Installation
Checkout
7 68 25
Initial Training
Initial Spares
Other
5
SIMULATION BASED ACQUISITION (SBA)
Vision
to have an Acquisition Process in which DoD and
Industry are enabled by robust, collaborative use
of simulation technology that is integrated
across acquisition phases and programs.
Goals
Substantially reduce the time, resources and risk
associated with the entire acquisition
process Increase the quality, military worth and
supportability of fielded systems, while reducing
their operating and sustaining costs throughout
the total life cycle Enable Integrated Product
and Process Development (IPPD) across the entire
acquisition life cycle.
6
SBA -- A WORK IN PROGRESS
Acquisition Tomorrow
Acquisition Today
SBA Roadmap
MS
SBA
1999
20??
DoD MS Community
The team making it happen...
DoD Operational Tester
DoD Acq Community
Industry
7
SBA OPERATIONS CONCEPT
Conceptual Development
Other System
CG47
CG47
DDG51
DDG51
DD963
DD963
PLAT
SIG/
KINE
SENS 4
2
SENS 3
C
Functional Design
SENS 2
SENS 1
COMMS
DATA
FUSION
Top Level System Requirements
Distributed Sim Framework
MNS
SYSTEM
CONCEPTS
Distributed Information Repository
ORD
Physical Info System (HW/SW) Design
System Info Repository
System Info Repository
REQ SPEC
Logical
Structural / HME
CONCEPTUAL
REQ SPEC
Logical
Structural / HME
CONCEPTUAL
System Info Repository
Cost, Schedule Program Management
REQ SPEC
Logical
Structural / HME
CONCEPTUAL
Concept
Engineering
Demonstration /
Production
Upgrade
PHASE
Exploration
Manufacturing
DRIVERS
Definition
Validation
Development
Deployment
and
Replace
Other System
nt
MGMT

1000

Operations, Logistics Training
100

Engineering Development Manufacturing
10
Jan Apr Jul Oct
TE

Extensive Re-use Within Phases and Across
Acquisition Programs
8
SPECTRUM OF TOOLS PARTNERSHIP
Virtual Prototypes
Synthetic Environments
System Info Repository
REQ SPEC
Logical
CONCEPTUAL
Industry Government
9
SBA - NOT JUST TECHNOLOGY
Environment
Tactical
Decision
Operational
System
Req Elicitation
Need
Integration
Support
Training and
and Analysis
Ops Support
and Test
Integrated Advanced Engineering and Management
Enterprise
Functional
Design
and Analysis
HME / HW / SW
Implementation
and Analysis
Modification
and Upgrade
HME / HW / SW
Development
Maintenance
and
Logistics

• Collaborative
• Distributed Engineering

- Seamless Integration of Engineering
Disciplines
Common Project Data Repository

Integrated Product Process Model
Format

• Info Repository

• Integrated Design Data Schema

- User Transparent Web Style Access
Together, these will facilitate --
An unprecedented quality of enterprise-wide,
collaborative decision making across the
acquisition life-cycle...
10
ENVIRONMENT
Gateway to Distributed DoD/Industry Resource
Repository
Collaborative Environment
PM Requirements
Resources
Acquisition Support Tools
Document Archives
Distributed Product Descriptions

• Both the DIRR and DPDs
• are interconnected using web technology
• have a configuration control process
• use encrypters/firewalls for access control

11
PROCESS
TRADITIONAL 1 ITERATION
OPERATE SUSTAIN
TRAIN
TEST
BUILD
DESIGN
SET REQMTS
OPERATE SUSTAIN
CONOPS DEVELOPMENT
MAINTAIN
LOGISTICS SIMULATIONS
TRAIN
TRAINING SIMULATIONS
TEST
VIRTUAL TESTING
IPT
BUILD
VIRTUAL BUILD
DESIGN
SYNTHESIZE DESIGN
REFINE REQUIREMENTS
INITIAL NEEDS ASSMT.
MULTIPLE ITERATIONS (MULTIPLE DESIGN LEARNING
CYCLES)
12
CULTURE
Evolved Acquisition Culture

• 5000 Policy
• Enabled Integrated Process Teams
• Sharing MS in Source Selection
• A Key Element of Acquisition Strategy
• Education
• Development of a Comprehensive Core Body of
  Knowledge

Culture
Evolved Acquisition Culture

• Enabled Integrated
• Process Teams

• Changing Roles
• and Responsibilities

13
TOP FOUR SBA ACTIONS TO IMPLEMENT -- THE VOICE
OF THE CUSTOMER --

• Implement appropriate collaborative environments
• Establish a concept of operations for use of
  Distributed Product Descriptions (DPDs)
  throughout the acquisition life cycle
• Establish and resource a process for populating
  and managing an online DoD/Industry repository
• Define, adopt, and develop relevant standard data
  interchange formats (DIFs) for the SBA
  architecture

THE CUSTOMER Services, Industry, Agencies
14
THE THREE ARCHITECTURE VIEWS
Organizations Activities Functions Processes
Information Flows
Operational Architecture
Systems Architecture
Platforms/Components Data Flows/Paths Interfaces
/Networks
Technical Architecture
Standards Rules Conventions
(Source C4ISR Architecture Framework Document,
Dec. 1997)
15
TOP-LEVEL VIEW OF SBA SYSTEMS ARCHITECTURE
Gateway to Distributed DoD/Industry Resource
Repository
Collaborative Environment
PM Requirements
Resources
Acquisition Support Tools
Document Archives
Distributed Product Descriptions

• Both the DIRR and DPDs
• are interconnected using web technology
• have a configuration control process
• use encrypters/firewalls for access control

16
KEY CONCEPTCollaborative Environments (CE)

• An enduring collection of resources, people,
  processes, and tools assembled to attack a given
  problem

17
Possible Focuses

• Can be organized by mission area, product area,
  susbsystem, etc
• focused on a critical mission area (will cross
  programs)
• Strike Warfare
• Land Warfare
• focused on product orientation (will cross
  programs)
• Tanks
• Ships
• subsystem (may or may not cross programs)
• Radar
• Etc

18
Results of Collaborative Environments

• Collaborative Environments will reach into the
  DoD/Industry Resource Repository and grab
  Distributed Product Descriptions
• Collaborative Environments will reuse and share
  models/sims/data across the Collaborative
  Environments
• Bottom line a way of organizing MS teams to
  foster reuse and interoperability

19
KEY CONCEPTDistributed Product Description (DPD)

• In its simplest form, a 3-dimensional
  representation of a system, along with associated
  process data
• Functional information (what does this thing do?)
• Requirements information (why do we need this?)
• Manufacturing information (what special tooling
  do we need to produce it?)
• Cost information (how much does it cost?)
• Has other features like user selectable views
• Anticipate need templates

20
VIRTUAL PROTOTYPES THROUGHOUT THE SYSTEM LIFE
CYCLE
Relational Design and Product Prototype
Enterprise Prototype
Support Prototype
Fabrication Prototype
Factory Prototype
Assembly Prototype
Commitment to Virtual Prototypes Is Key To
Realizing Significant Cycle Time and Cost
Reductions
B2854006
21
KEY CONCEPTDoD/Industry Resource Repository
(DIRR)

• A collection of pointers constituting a web
  technology-based distributed repository of tools,
  information resources, and generic infrastructure
  components for use within and reuse across
  acquisition programs
• The union of capabilities provided by all
  Collaborative Environments.

22
DIRR
23
BUILDS UPON THE MSRR

• Extension to MSRR in that it brings in Industry
• example purple JSF DPD
• Virtual repository/Card catalog of all existing
  repositories
• Since it incrementally builds off of the MSRR, it
  uses web-technology search engines
• Because it brings in industry, it brings up
  issues of proprietary data rights/access controls

24
KEY CONCEPTSDigital Interchange Format (DIF)

• Will be an extension to existing DIFs where they
  currently exist, such as SEDRIS
• MSDB pilot idea to extend SEDRIS to account for
  EO/IR/Visual
• Will be the go between for DPDs and the outside
  world (DIRR, etc)
• Will propose DIFs to DMSO Common Technical
  Framework/data std portion and the Joint
  Technical Architecture
• The essence of our SBA technical architecture

25
SBA-LIKE PROGRAM ACTIVITIES

• Joint Strike Fighter - Integrated across
  acquisition phases
• reuse across Services
• Virtual Strike Warfare Environment Leave-behind
  reusable technology for AOAs, TE, warfighters,
  training - developers, maintainers, virtual
  prototypes and HWIL
• Core suite (engineering - campaign-level MS)
  across Services reviewed quarterly
• Single common database for Logistics Modeling
  Environment RMS, cost, manpower, training
• Joint Interim Mission Model (Requirements,
  CONOPS, system of system trades) available to
  other programs via DMSOs MS Resource Repository
  
• Joint Common Cost Model developed with industry

26
SBA-LIKE PROGRAM ACTIVITIES (CONT)

• NSSN - Electronic Collaborative Environment
• Computer Aided Three Dimensional Interactive
  Application (CATIA) single common database for
  design, engineering, manufacturing, electronic
  mockups
• Navy reviews and approves design online,
  reduces physical mockups.
• Collaborative design integration (prime,
  suppliers, program office) for real-time design
  trades, analyses and changes
• Kinematic animations for more realistic design
  verification and validation
• Typical sailor for human factors design trades,
  verification and maintenance procedures.

27
SBA-LIKE PROGRAM ACTIVITIES (CONT)

• Grizzly - MS Effort Structured to Control Cost
  Mitigate Risk
• Integrated Systems Model End-to-End Digital
  Simulation integrating all MS actual control
  algorithms.
• Reduced redesign time for commanders control
  station optimized vehicle layout reduced
  physical prototyping virtual tested in different
  terrain.

28
THE CHALLENGES

• Many issues associated with how to construct CEs.
  They include
• defining relationships between components
• establishing the individual CEs operational,
  system and technical architecture
• The Joint SBA Task Force has proposed that an SBA
  reference system architecture for all CEs be
  developed
• The intent is to highlight the required
  piece-parts and opportunities for interface
  standards associated with a CE.

29
CAN WE LEARN FROM OTHERS

• The MS community may not have to wait for the
  results of studies and experiments
• It may be possible to leverage the work and
  experience of the software community over the
  past decade
• Computed aided software engineering (CASE) tools
  experience
• advances in computer technology, the increase
  size and complexity of software products resulted
  in a large and diverse collection of CASE tools
• To support the complete software development
  life-cycle, CASE tool environments were developed
• They learned that there was a difference between
  an environment and amalgamation

30
SBA SPECIAL INTEREST AREA
http//www.msosa.dmso.mil/sba/
31
BACK-UPS
32
OUSD(AT) GUIDANCE

• Memorandum on MS from Dr. Gansler (March 16,
  1998)
• Encourages the use of MS in Acquisition
• Emphasizes the need for planning for the use of
  MS
• Endorses SBA initiative
• Charge to SBA Workshop (Nov 3, 1998) must
  fully integrate MS

33
TO-BE COLLABORATIVE ENVIRONMENT
Operational Architecture
Senior Decision-Making Guidance
Acquire Assets
Provide Capabilities
Establish Direction
Employ Forces
Government/Industry/Academia Inter-function IPTs
Resource Allocation
Strategic Planning
Operations
Traditional Acquisition
Science Technology
Research Development
Requirements Generation
Non-Traditional Acquisition
Logistics Maintenance
Interoperable Tools
Interoperable Databases