1

Architecting and Engineering the Naval Force: A Warfare Systems Perspective

18 June 2009

Architecting and Engineering the Naval Force: A Warfare Systems Perspective

18 June 2009

RDML (Sel) Jerry K. Burroughs

SPAWAR Chief Engineer

Distribution Statement D: Distribution authorized to Department of Defense (DOD) and U. S. DOD contractors only. Other requests must be referred to SPAWAR HQ PAO.

2

Connecting The ForceConnecting The Force

• Connecting the Force: Engineering Perspective:– Rigorous Up Front Systems Engineering– Common Standards– Systems Engineering Technical Reviews– Single Technical Authority for Networks– View the Network as a Warfare System

3

Common MOC ArchitectureCommon MOC Architecture

• Developed Engineering and Functional Baseline that Defines MOC/MDA Networks Design

• Conduct Analysis of Network Performance Attributes

• Developing Common MOC Architecture

4

Navy Data Centers Navy Data Centers

• Develop The Navy System and Technical Architecture for Data Centers IAW DECC Standards and NNE-2016

• Develop the Processes for Validating the Navy Enterprise Data Centers to Navy Standards

• Develop and Promulgate a Construct for a SYSCOM Operated, NWCF-Run, Data-Application Hosting Center

5

Platform Network Technical Authority Instruction

Platform Network Technical Authority Instruction

• Establish SPAWAR Network Technical Authority Through of Construct of Improved Requirements and Acquisition Governance in Conjunction with ASN(RDA) and OPNAV Efforts

• Clarify Interdependent Roles of Requirements, Design, Implementation, Certification, and Sustainment

6

Platform Networks Architecture Demonstration

Platform Networks Architecture Demonstration

• Developing Generic Platform Network Architecture Data Applicable to All Ship Classes

• Enterprise Information Environment (EIE) and other Applicable Standards

• Document Generic Platform Network Architecture

• Engineering Baseline• Functional Baseline• Performance Baseline

7

CANES/NGEN AlignmentCANES/NGEN Alignment

Today

IT 21

CANES

ONE-NET

NGEN

Mid Term

Phased Alignment As 2016 Architecture MaturesPhased Alignment As 2016 Architecture Matures

Common Contracting

Shared Specifications

Common Tech Solutions

Interop Issues

Limited Trust

Unique C&A

NMCI

Shared GAL

Common Firewall

Portal

Unique Testing

Shared C&A NNETarget

Architecture2016

SeamlessUser

Experience

Future

SPAWAR 5.0 & NETWARCOMdeveloping

8

SHADE-TSHADE-T

• C5F UON for Shared Awareness and Deconfliction (SHADE) to Support Multi-National Counter-Piracy Efforts

• SHADE-T is a Geospatial Information System (GIS) Based Web Application Hosted by Non Classified Enclave (NCE) Using Google Maps Technology – Provides CTF-151 and Non-Coalition Partners

a Limited UNCLAS COP

9

What is the Problem?Need for Improved Information Sharing

What is the Problem?Need for Improved Information Sharing

Operationally Derived Operationally Derived RequirementsRequirements

To Achieve

Operationally

Significant Results

Federal Inter- Agency

Federal Inter- Agency

State,Civil, Local

State,Civil, Local

Foreign Allies and Partners

Foreign Allies and Partners

Info sharing

Implement Implement Lessons Lessons LearnedLearned

DOJ / DHS Experience in Fed, State, Local, Tribal

Interoperability

DOJ / DHS Experience in Fed, State, Local, Tribal

Interoperability

DOD and IC Information Sharing

Initiatives

DOD and IC Information Sharing

Initiatives

Lessons Learned from Lessons Learned from Information Sharing Efforts Information Sharing Efforts

DOJ / DHS Experience in

Fed, State, Local, Tribal

Interoperability

DOJ / DHS Experience in

Fed, State, Local, Tribal

Interoperability

DOD and IC Information

Sharing Initiatives

DOD and IC Information

Sharing Initiatives

Info Sharing Lessons

Learned from Iraq and

Afghanistan

Info Sharing Lessons

Learned from Iraq and

Afghanistan

9/11

Hurricane Katrina

Hurricane Katrina

San Diego

Wildfires

Asian TsunamiAsian Tsunami

GWOT GWOTNGOs

and Industry

NGOs and Industry

10 10

What is the Universal Core (UCore)?What is the Universal Core (UCore)?

An information exchange specification and implementation

profile: – Vocabulary

• Of most commonly exchanged concepts: Who, What, When, Where

– XML representation of the concepts

– Security markings to permit controlled access, electronic tear lines

– Messaging framework to package and unpackage the content consistently

– Guidance for extension to permit tailoring to specific mission areas

UCore V2.0 Conceptual Data Model

Messaging Framework

MetadataMessage Framework

When What

Where

Who

11

Systems Engineering Technical Reviews

Systems Engineering Technical Reviews

NOTE: Gate Reviews are NOT SETR Events

Technical reviews occur as the system matures throughout the program life cycle

MaterialSolutionAnalysis

Material DevelopmentDecision

Technology Development

Engineering and Manufacturing Development

Production & Deployment

Operation & Support

A

ITR ASR SRR I SRR II IBRSFR PDR CDR TRR SVR/FCAPRR

OTRR PCA ISR

Systems Engineering Technical Review Timing

Milestones

Phases

Reviews

Pre-System Acquisition System Acquisition Sustainment

Integrated System

Design

System Capability & Manufacturing Process

Demonstration

B C

Technical Reviews

Program Reviews

Software Reviews

Technical Readiness Assessment

TRA TRAIRRSSR

1 2 3 4 5 6

PDR

Pass 1 Pass 2

Acquisition Gate Reviews

Preferred

System Concept

System Specification

or

Functional Baseline

Allocated Baseline

Initial Product Baseline

Final Product Baseline

Acquisition Reviews

ASR – Alternative Systems ReviewCDR – Critical Design ReviewFCA – Functional Configuration AuditIBR – Integrated Baseline ReviewIRR – Integration Readiness Review

ISR – In-Service ReviewITR – Initial Technical ReviewOTRR – Operational Test Readiness ReviewPCA – Physical Configuration AuditPDR – Preliminary Design Review

PRR – Production Readiness ReviewSFR – System Functional ReviewSRR – System Requirements ReviewSSR – Software Specification ReviewSVR – System Verification ReviewTRR – Test Readiness Review

12

SummarySummary

• Connecting the Force:– Rigorous Up Front Systems Engineering– Common Standards

• Single Technical Authority for Networks

• Viewing the Network as a Warfare System