Copyright © 2006 Raytheon Company. All rights reserved.
Reference Architecture And The JCIDS ProcessNetwork Centric Systems
Chuck [email protected]
31 October 2006
2Copyright © 2006 Raytheon Company. All rights reserved.
AgendaDoD TransformationWhat is a reference architecture?Why develop Reference ArchitecturesAcquisition processesPutting It All TogetherHow to Use a Reference Architecture in AcquisitionSummary
3Copyright © 2006 Raytheon Company. All rights reserved.
Acquisition Theology
Requirements Generation System
Integrated atDepartment
Systems
Requirements
Bottom Up, Often StovepipesArmy
NavyAir Force
MarinesCombat
CommandsServices Agencies
JCIDS
Joint Operational Concept
Integrated Architectures
Joint Capabilities
Top Down, Born Joint
Military Strategy Joint Vision
4Copyright © 2006 Raytheon Company. All rights reserved.
Requirements Based AcquisitionRequirements Service Not Joint Focused
Lacked Construct For Objective Analysis
Systems Not Necessarily Integrated
Program Duplication Across Services
Evolutionary Acquisition Not Institutionalized
Joint Warfighting Needs Not A Priority
Requirements Generation System
Integrated atDepartment
Systems
Requirements
Bottom Up, Often StovepipesArmy
NavyAir Force
MarinesCombat
CommandsServices Agencies
5Copyright © 2006 Raytheon Company. All rights reserved.
JCIDS Capability Based AcquisitionMethodology To Identify Capabilities Gaps
Mandate Broader Review Of Proposals
Engage The Acquisition Community Early
Define Non-materiel And Materiel Solutions
Prioritize Capability Gaps And Proposals
Coordination With Departments And Agencies
JCIDS
Joint Operational Concept
Integrated Architectures
Joint Capabilities
Top Down, Born Joint
Military Strategy Joint Vision
6Copyright © 2006 Raytheon Company. All rights reserved.
An architecture is “the structure of components, their relationships, and the principles and guidelines governing their design and evolution over time.”
- C4ISR Architecture Framework, Version 2.0,derived from IEEE
An “official” definition:
What is an Architecture?
7Copyright © 2006 Raytheon Company. All rights reserved.
What Is a Reference Architecture?A Reference Architecture (RA) Is the Normalized Architecture of Several End Systems That Share One or More Common Domains, Containing a Set of Architectural Best Practices for Use by Architecture Teams in Your Organization. RAs Provide an Advanced Point of Departure for Implementing Solutions So That Each Implementation Reduces:
Cost by Taking Advantage of Opportunities for Reuse of Services, Products, Data Definitions, Etc.
Schedule byStarting With a Common Set of Artifacts to Be Tailored for Implementation
Risk byProviding Consistent Decomposition and Design Patterns Utilizing Related Expertise and Reuse of Proven ArtifactsExploiting Lessons Learned
8Copyright © 2006 Raytheon Company. All rights reserved.
Global Information Grid
What Is a Reference Architecture?
ForceNet
C2 Constellation
LandWarNet
NASA's Deep Space
Network
ReferenceArchitecture
9Copyright © 2006 Raytheon Company. All rights reserved.
Why Reference Architectures?Reduces cost, schedule, and risk through an established set of core modules that may be tailored to meet Government’s mission needsDemonstrating current performance through proven and mature solutionsProvides a common set of demonstrated capabilities, industry is able to engage the customer intelligently and quickly provide a solution to customer needsPresent an approach that is communicated with a common language
10Copyright © 2006 Raytheon Company. All rights reserved.
Ada
pter
sA
pplic
atio
ns
C2
Rep
osito
ry
J2E
E
Inte
rope
rabi
lity
Net
ted
Sen
sors
Info
Sec
Infra
stru
ctur
e
Reference ArchitectureLibrary
No RA RA
How to Use a Reference Architecture
Infrastructure
Netted Sensors
Command & Control
Information Assurance
Applications
ENTERPRISE ARCHITECTURE
RAs reduce time to market by reducing cost, schedule, and risk
…
11Copyright © 2006 Raytheon Company. All rights reserved.
Acquisition ProcessesJoint Capabilities Integrated Development System (JCIDS)– Top-down process– Methodology to identify capabilities gaps– Mandate broader review of proposals– Engage the acquisition community early– Define non-materiel and materiel solutions – Prioritize capability gaps and proposals– Coordination with departments and agenciesJoint Rapid Acquisition Cell (JRAC)– Quickly address in order to prevent combat related loss of life and/or
mission failure– Based on unforeseen military requirements that must be resolved in days,
weeks or months– Provides policies and procedures for initiation, review, evaluation, approval
and follow-up of combatant commander urgent operational needs request
12Copyright © 2006 Raytheon Company. All rights reserved.
Functional Solution Analysis
DOTMLPF
Joint Capability Integrated Development System (JCIDS)
IntegratedArchitectures
Functional Area Analysis
JCD
FunctionalNeeds
Analysis
Ideas forMateriel
Approaches
Analysis ofMateriel
Approaches
DoD StrategicGuidance
Family of Joint Future ConceptsCONOPS
Joint Tasks
Using information from DoD Strategicand Vision documents, expected threats are used to create mission scenariosend-to-end
Considering infinite resources whatCapabilities would be required to accomplish the mission
Generate and Integrated Target Architecture Based on Mission Scenario
Assess current and programmed joint capabilities to accomplish the tasks
Generate an as-is architecture from available and planned capabilities.
Using the as-is architecture and the target architecture analyze the mission scenario when looking for discrepancies.
From analysis generate a prioritized list of capability gaps described in terms of• Functional Area
• Relevant range of operations• Timeframe under consideration
There will be a Functional Solution Analysis on each capability chosen from the JCD.
PostIndependent
Analysis
Approach NApproach 2
Approach 1Ideas forNon-MaterielApproaches
Analysis ofNon-Materiel Approaches
Question to be answeredCan the capability be accomplished with a non-material solution?
Question to be answered –Or will it require a material solution? Question to be answered –Or will it require a hybrid solution? The post independent analysis
chooses the best approach and the acquisition process begins
13Copyright © 2006 Raytheon Company. All rights reserved.
JCIDS Feeds the Acquisition Process
IntegratedArchitectures
Functional Area Analysis
JCD
FunctionalNeeds
Analysis
DoD StrategicGuidance
Family of Joint Future ConceptsCONOPS
Joint Tasks
CDD
CPD
ICD
DCR
Functional Solution Analysis
DOTMLPF
Ideas forMateriel
Approaches
Analysis ofMateriel
Approaches PostIndependent
Analysis
Approach NApproach 2
Approach 1Ideas forNon-MaterielApproaches
Analysis ofNon-Materiel Approaches
DOTMLPF
Ideas forMateriel
Approaches
Analysis ofMateriel
Approaches PostIndependent
Analysis
Approach NApproach 2
Approach 1Ideas forNon-MaterielApproaches
Analysis ofNon-Materiel Approaches
IntegratedArchitectures
14Copyright © 2006 Raytheon Company. All rights reserved.
JRAC PolicyRapidly validate a resource deployed and/or employed combatant commander’s Joint Urgent Operational Needs (JUON)
Quickly address Immediate Warfighter Need (IWN) in order to prevent combat related loss of life and /or mission failure
Considered as joint in nature and outside of the scope of existing DoD 5000 Series and services processes
Not intended to compete with any of the current service processes but rather to complement them
Not intended to replace any other Joint Staff process but potentially leverage these processes and focus them in support of combatant commander JUONs
Supports Current Force Acquisition
15Copyright © 2006 Raytheon Company. All rights reserved.
JRAC – Process Flow
OIF/OEF/GWOToriginates JUON
COCOM certifiesand prioritizes JUON
COCOM DECLINES JUON
Joint Staff validatesand recommends
JOINT STAFF DECLINES IWN
JRACdesignates as IWN
IWN solutionpresented to
leadership
COCOM/Servicesexecute solution
Feedback DIRECTION TOEXECUTE
JRAC TRACKS AND FACILITATESSOLUTION <120 DAYS
Provide the warfighter with the best in product through an integrated multi-vendor solution
16Copyright © 2006 Raytheon Company. All rights reserved.
Putting it all together
TailorReference
Architecture
GenerateSystem
Requirements
CreateSolution
17Copyright © 2006 Raytheon Company. All rights reserved.
Putting all together
Global Store
Build Rapid IntegratedSystem Model
DemonstrateModel toCustomer
Shop for Multi-Vendor
Solution
GovernmentContractors
CommercialVendors
18Copyright © 2006 Raytheon Company. All rights reserved.
How to Use a Reference Architecture in Acquisition
RA• BRM/TRM/DRM• Executable – M&S framework
Enterprise/System/Product
Models Customer Needs:• Strategy/CONOPS/
roadmaps• Capabilities• Specific programs/
resources
Investment Planning
Dialog
Mission Solutions• Customer dialog• Requirements refinement• Program shaping• Brand building
RAs Improve Customer Communication And Facilitate Strategic Planning
RaytheonValue Add
OperationalModel
Solution Model
Proposals/Program Plans
Quantified Metrics:• MOPs/MOEs• Alternatives/what-ifs
Dialog
REAP Process• Integrated methodology• Virtual/physical rapid prototyping
19Copyright © 2006 Raytheon Company. All rights reserved.
RAs Support Transformation
IntegratedArchitectures
Functional Area Analysis
JCD
FunctionalNeeds
Analysis
DoD StrategicGuidance
Family of Joint Future ConceptsCONOPS
Joint Tasks
CDD
CPD
ICD
DCR
Functional Solution Analysis
DOTMLPF
Ideas forMateriel
Approaches
Analysis ofMateriel
Approaches PostIndependent
Analysis
Approach NApproach 2
Approach 1Ideas forNon-MaterielApproaches
Analysis ofNon-Materiel Approaches
Functional Solution Analysis
DOTMLPF
Ideas forMateriel
Approaches
Analysis ofMateriel
Approaches PostIndependent
Analysis
Approach NApproach 2
Approach 1Ideas forNon-MaterielApproaches
Analysis ofNon-Materiel Approaches
IntegratedArchitectures
Where do reference architectures play?
20Copyright © 2006 Raytheon Company. All rights reserved.
RAs Support Current Force
Where do reference architectures play?Where do reference architectures play?
OIF/OEF/GWOToriginates JUON
COCOM certifiesand prioritizes JUON
COCOM DECLINES JUON
Joint Staff validatesand recommends
JOINT STAFF DECLINES IWN
JRACdesignates as IWN
IWN solutionpresented to
leadership
COCOM/Servicesexecute solution
Feedback DIRECTION TOEXECUTE
JRAC TRACKS AND FACILITATESSOLUTION <120 DAYS
21Copyright © 2006 Raytheon Company. All rights reserved.
SummaryRAs provide a consistent point of departure for implementing solutions so that each realization of the architecture:
Follows a consistent decomposition and design patternReduces cost by
Exploiting opportunities for reuse of services, products, data definitions, etc.
Reduces schedule byStarting with a core architecture to be tailored for implementation
Reduces risk byIncorporating required global capabilitiesProfits from lessons learned and related expertise
Industry’s investment in reference architectures provides reduced cost, risk, and schedule
Top Related