The Modernization of the Aegis Fleet with Open Architecture

Andrew Winkler

Sept 28, 2011 Copyright © 2011 by Lockheed Martin Corporation

Distribution Statement A: Approved for Public Release. Distribution is unlimited

Topics Things to talk about… • Background – Aegis Overview – Capability Upgrade Evolution – Modernization Concept/Approach

• Aegis Open Architecture – Evolution to COTS Technologies and Products – Incremental/Spiral Development Approach

• Aegis Modernization – Overall Scope/Impact – Product Line Architecture – Integration of Common STM / TS Components

• Summary Copyright © 2011 by Lockheed Martin Corporation

Aegis – The Shield of the Fleet Design Cornerstones • Continuous Availability • Surveillance Coverage • Reaction Time • Firepower • Environmental Resistance

ASCM High Diver BMD

Shoot the Archer

CVN ASCM Sea Skim and Pop-up

Land Launch ASCM

DDG

Self Defense Copyright © 2011 by Lockheed Martin Corporation

Area Air Defense

Long Range Air Defense And BMD

Aegis Combat Systems Architecture

Radar System AN/SPY-1

Command and Decision System

Aegis Display System Vertical Launching System Mark 41

Fire Control System Mark 99 Standard Missile-2 SM-3 VLA TLAM ESSM Weapon Control System

Copyright © 2011 by Lockheed Martin Corporation

Aegis Combat Training System Mark 50

Operational Readiness Test System

Aegis Capability Overview CG / DDG AMOD DDG 113 CG 52 CGMOD NEW

Capability

DDG 103 DDG 91 DDG 85 NEW DDG 79 DDG 67 DDG 59 CG 59 DDG 51

NEW

NEW

Consoles

NEW Combat DF

CG 52 CG 47 NEW SPY-1A

NEW

NEW

ESSM

NEW

NEW

ACB08

NEW ACB12 + Fact of Life

DDG 116 + NEW ACB 14/16/ 18

Open C2

COTS SPY-1D (V)

CEC Helo Hangar 5”62 Gun

SPY-1B SPY-1D

VLS

1983

BMD 1991

BMD

Integrated Improved

BMD 1999

2004

2008

12 Generations and Over 27 Years of Proven Success Copyright © 2011 by Lockheed Martin Corporation

BMD

BMD

2012

2014-16

Aegis Modernization Concept I.

Decouple Hardware and Software Upgrades Using COTS – –

II. III. IV.

Software Upgrades Every Two Years Hardware Refresh Every Four Years

Build on Fielded Baselines Integrate Navy Enterprise HW and SW Solutions Transition Aegis to Navy Objective Architecture

Benefits of Aegis Modernization Concept – – – – –

More Capability to the Fleet Sooner Foster Collaboration and Competition Cost Savings from Commonality & Reuse Minimal Lifetime Spares Upgrades Backward Compatible

COTS & Open Architecture While Maintaining Engineering Discipline Copyright © 2011 by Lockheed Martin Corporation

Aegis Open Architecture

Copyright © 2011 by Lockheed Martin Corporation

AWS Computer Architecture Evolution B/L 1/2/3 Fielding

B/L 4/5

CG 47-64

DDG 51-78 CG 65-73

1983

1990

B/L 6 Ph I/III DDG 79-90 CG 66 & 69

COTS Selection

1998 1994

ACB08/TI08

ACB12/TI12

DDG 91-112

CG 52-58

CG 59+ DDG 51+

2005 1999

2009 2006

2012 2009

All COTS computers (MCE)

MIL Spec Design

MIL Spec Design

Processors

UYK-7 UYK-20

UYK-43 UYK-44

UYK-43/44+ Adjunct COTS

COTS

Mainstream COTS

Mainstream COTS

Software

CMS-2

CMS-2

CMS-2 C++, Ada

C++, Ada

Message-passing, Component-based C++, Java, Ada

Message-passing, Component-based C++, Java, Ada

Interfaces NTDS Parallel

NTDS Parallel NTDS Serial

NTDS Parallel NTDS Serial FDDI / Ethernet

NTDS Parallel NTDS Serial FDDI**/ Ethernet

NTDS Parallel NTDS Serial Ethernet

NTDS Parallel NTDS Serial Ethernet

Displays

UYH-4 UYQ-21 (TGC*)

UYQ-21/UYQ-70

UYQ-70

UYQ-70 ORTS Thin Clients

CDS

UYK-43s B5PIII TGC

SMP’s ALIS Network

All COTS SMP’s Fast Ethernet

Open Architecture Mainstream COTS Gig-Ethernet

Open Architecture COTS MMSP Product-Line

System Complexities

UYH-4

Mixed COTS and MIL Spec Design

B/L 7 Phase I

* Applicable to Baseline 5 Phase III Only ** Eliminated in Baseline 7 Phase IR Copyright © 2011 by Lockheed Martin Corporation

All COTS computers (MCE)

All COTS computers (MCE, CPS)

COTS Technology and Products Tech Insertion 00

2000

Tech Insertion 04

B7PhI

2004

B7PhIR DDG 91-102

Tech Insertion 08 ACB 08

DDG 103-112 LCS / NCS - Derivative

Non-LM Hardware • Computing Platform

Non-LM Software • Real Time Operating System

• VME Single Board Computer

• Pub-Sub Communications

• Network Switching

• High Availability Middleware

• SAN Storage • Network File System • Thin Client LCD Display • Analog Hardware/Devices

• Enterprise System Management • Human-Systems Software • Network Management Tools

Smaller Footprint and Reduced Processor Costs Copyright © 2011 by Lockheed Martin Corporation

2008

CG 52-59

Incremental Development “Build a little ... test a lot”

OA Radar

 Spiral-1

At-Sea Demo DDG 96



DDG 103-112 OA Display

Spiral-2 WSMR

OA Weapons

• Focused on Radar, Weapons • Model-Centric Development (UML) • Modern Languages (C/C++, Java) • Non-Proprietary Interfaces

 Spiral-3

ACB 08 CG 52-59

2007 Completed Modular Designs

Tech Insertion 08

2008-2011 Fielding Modular Design foundation

Open Architecture Foundation for Baseline 9 Developments Copyright © 2011 by Lockheed Martin Corporation

Where We are Today

Aegis Combat System

Aegis LAN Interconnect System Common Network (ALIS III) SPY SPQ -9B

SQQ -89

C&D

Harpoon WPNS DSPL CEC

TTWCS

ASW

SPY

Strike

Surface

NAV

EW

Open C2

Signal Processing

Radar Control

DDG-91 2004

Hardware

Custom

SMP

Software

Closed

Closed

CG-52 2008

Hardware

Custom

Software

Closed

CG-62/ DDG-51 2012

Hardware Software

SLQ -32

Nav Gun

Lamps

AWS

Technical Assessment

SPS -67

UFCS

VLS

EW IFF

Display

C&D

Mainstream Mainstream Open

Open

Weapons/ Fire Control

VLS

SMP

Mainstream

Closed

Closed

Mainstream Mainstream Mainstream Mainstream Mainstream Open

Open

Open

Open

Closed

Mainstream Mainstream Mainstream Mainstream Mainstream Mainstream Open

Open

Open

Open

Open

Open

Continuously Advancing the Aegis Combat System Forward Copyright © 2011 by Lockheed Martin Corporation

Today’s Aegis Combat System Surface Warfighting Electronics Architecture Detect/Control/Engage View

System/Subsystem View Aegis LAN Interconnect System Common Network (ALIS III) SPY C&D

SPQ -9B

SQQ -89

EW

Harpoon WPNS

SPS -67

UFCS

DSPL CEC

TTWCS

SPY-1 Radar

ASW

Sig Pro

SLQ -32

Nav Gun

Lamps

VLS

AWS

Federated, Tiered Architecture

IFF

Strike

C&D

Surface

Display

EW

NAV

Weapons

VLS

Aegis Weapon System

Efficient ACS Capability changes Well-Define Components and API’s

Track Management Senor Management

Doctrine Identification

Air Control Links

Command & Control

Supports Operational and Navy Business Model Objectives Copyright © 2011 by Lockheed Martin Corporation

Weapons Display

Aegis Modernization

Copyright © 2011 by Lockheed Martin Corporation

Roadmap to Aegis Modernization (AMOD) AMOD Advanced Capability Build 12 (DDG configuration)

NIFC-CA

Tech Insertion (TI) 12 ACS Element Upgrades JTM Alignment SM-6

Increased Battlespace and Multi-Mission Interoperability

Aegis BSP

Aegis BMD 5.0 NIFC-CA MMSP

AMOD Advanced Capability Build 12 (CG configuration) TI12 ACS Element Upgrades JTM Alignment SM-6

NIFC-CA

AMOD ACB12 (TI12)

MMSP COTS Based Infrastructure

Aegis BMD 4.0.1 Improved Discrimination Improved Track Handover Enhanced LoT Integrated IR/RF KA SM-3 Blk IA and IB

ACB08 OA Spiral 3 ACS Element Upgrades TI 08

CG MOD ACB08 (TI08)

Aegis BMD Block 06/08

Aegis BMD 3.6



Aegis BMD 3.6 LRS&T, Engagement and LoT Multi-Mission Integrated Mission Planning SM-3 Blk I and IA

Aegis BMD Block 04 Copyright © 2011 by Lockheed Martin Corporation



B/L 7 Phase IR OA Display Improvements CIWS Block 1B Fratricide Avoidance CEC 2.1 (Mode 5) COTS Refresh 1

B/L 7 Phase I COTS architecture

CR0 / CR1

AMOD Technical Scope HM&E Upgrades

Sea-Based Ballistic Missile Defense

BMD 4.0.1 Functionality and SM-3

Midcourse Defends Wide Regions

Terminal

Defends Localized Areas and Critical Assets

Boost Destroys Missile Regardless of Aim Point

Impact

Launch

Aegis Weapon System COTS Refresh 3

NIFC-CA and SM-6

Aegis Combat System Upgrades Operational Joint Track Manager (JTM)

SIGINT GMTI Imagery Acoustic

Sense Engage

DCGS (ISR Picture)

C2 Host Services

External Comms

Network Centric Enterprise Services (NCES)

UHF SATCOM

Tactical Joint Track Manager (JTM)

Track Mgmt

EO/IR

Sensor Adaptation

ES

Sensor Adaptation

SIGINT

Sensor Adaptation

Sensor Sensor Server Adaptation

Multi-Source Integration

Combat ID Classification Combat ID Identity

Info Exchange Managers Track Server Global Track Data Dissem Mgr

Geodetic Registration Composite Tracking

External Comms Adaptation

Global Track Level Global Track Management

EHF SATCOM JTRS MIDS/ JTIDS VRC-99 EPLRS

Composite Comm Svr Track Data Dissem Mgr

Composite Tracking (Sensor n) (Sensor NetNet 1-n)

Tactical Data Link Manager

Comms

Radar/ Radar/ IFF IFF

GCCS/JC2 (Common Operational Picture)

SHF SATCOM DDS

Open Network Interface / Real-Time Infrastructure Sensor types are for example, not an exhaustive list

Host Services Adaptation

Host C2 Adaptation

Host Weapons Adaptation

Host Nav/Time/DX

Host C2

Host Weapons

Communications devices shown are examples, not an exhaustive list

JTM Alignment Copyright © 2011 by Lockheed Martin Corporation

Way Ahead … Baseline 9

 Spiral-1

 Spiral-2

Focus: SPY, Weapons, and Display



Steering and Priming The SBIR Process

Technology Collaboration Center

Track Mgmt Display

Command & Control

Sensor Mgmt

Weapon Mgmt

Vehicle Control

Infrastructure Services

Middleware

Integrate 3rd Party

Operating System Hardware

Spiral-3

“ACB 08”

USS Bunker Hill CG-52

Applying S&T Investments Capability Based Plan – Baseline 9 Aligned

ACB 8.1

• Fielding Modular Software

Baseline 9 A/C

Baseline 9 B/D/E..

MM Signal Processor

• Open Standards • Collaborative Peer Review Environment

• Capability Improvements

• Full Government Purpose Data Rights

• BMD Merger • NIFC-CA • JTM / ATAC

• SBT • NIFC-CA Update

2012

2014-2016

• Leveraging small business innovation • Established Two Technology Centers 2010

Modular Design Foundation

Field Capability Through Modernization

Balancing Capabilities with Complex Combat System Integration Foundation Established for Transition to Objective Architecture Copyright © 2011 by Lockheed Martin Corporation

Implementing Open Architecture Layered Architecture Foundation

Infrastructure: • Common Services and APIs • Flexibility to Support Forward-Fit and Back-Fit

Track Mgmt Display

Command & Control

Componentized Objective Architecture: Sensor Mgmt

Weapon Mgmt

Infrastructure Services

Middleware

Common Computing Environment: • Standards-based Interfaces to network • Commercial Mainstream Products and Technologies

Vehicle Control

• Common Reusable Components • Platform Specific Components • Data Model • Extensible to the Future

Decouple Hardware (H/W) from Software (S/W)

Operating System Hardware

Upgrading Hardware and Software Independently Copyright © 2011 by Lockheed Martin Corporation

Top Level Objective Architecture “Component View…”

Track Server System Track Manager

Copyright © 2011 by Lockheed Martin Corporation

Joint Track Management Alignment Overview • Align AMOD and SSDS Track Management to a Common Architecture – Provide Consistent Functional Allocation, Data Representation and Attributes – Incorporate Reusable System Track Manager and Track Server Components

• Provides Hierarchical Track File (System Level – Source Level) • Provides Standard Interfaces – Track Server Standard Access Interface for Client Applications – Track Manager Integrates Track Data Sources via Common Interface; Extensible for New Track Data Sources

• Provides Two Complete Versions of Live Training Tracks: – Allows Training Override of Multiple Attributes – Training Tracks Can be Physically Relocated From Live Location

• Provides Dual Ownship – Tactical and Training: – Allows Training View to be Repositioned with No Impact to Tactical View Aligning the Architecture for Future: Common Components Across Ship Classes Copyright © 2011 by Lockheed Martin Corporation

JTM Alignment Integration of Common STM and TS Components… SI/DA Scope • Implement Common Track Server

External Communication Domain SATCOM

•Replace Existing PDM Component •Implement configurable track server – support multiple track sources •Standardize services and APIs •Integrate PDM, DDG-1000 and SSDS track server design concepts •Ensure resulting component will work for both AMOD and SSDS

Display Domain

• Consolidate System Track Manager

ADS ADS ADS GUIs GUIs GUIs

Data/status display

•Implement JTM hierarchical design approach •Consolidate STM and MNF •Improve track file and data xfer (e.g., capacity, types, attributes, …)

Display MGR DIF

Link Management

C2P/ CDLMS

L4A L11 L16

Track Management Domain Registration/gridlock

Track Distribution

Process Data Mgr

DDS

DDS

C2 Domain

SGS/AC

ID Assign

Radar

Multi-source Integration

Composite Tracking

SPY Mgr

SGS/AC

ICF

PDM

Sensor Management Domain SPY OA

ID Doctrine Mgr

Identification

Doctrine Mgr

IDA

System Track

DMF/ DCF

GCCS-M

SPF SPQ-9B

HSR Mgr

SPS-67

SSR Mgr

QBF

System Track Manager

Link Mgr LIF

RCF

CIWS

CEP

CEC Mgr CEF

UPX-29

STM

Id

IFF Mgr

Manual/ Track Maint.

Weapons Management Domain

MNF/ MTF

IAF EMF

Acoustic Sonar

LAMPS Mgr

Helo ES SLQ-32

Acoustic Mgr

EW Mgr

BMD Tracker

ASF

BMF

GTF

Engage Mgr

Gun Track Mgr

WCS OA

GWS

LEF

EWF

Aegis LAN Interconnect HIF

Copyright © 2011 by Lockheed Martin Corporation

Harpoon Interface Mgr

HWS

Availability Management Subcomponent Management

TS

Future Common TS Components

C o m m o n A P I

TS

Navigation

System Management (OASM)

GA SelfReliant

Operational Modes Data Recording

DXR

Hardware

STM

C2 Libraries

Component Framework Services

Operating System

Logging P/S Messaging

RTI DDS

Time

Time

Key

Component Framework Services Copyright © 2011 by Lockheed Martin Corporation

Common Components Component Framework Services Aegis C2/System Services

COTS

Common STM and TS Components Task Allocation… AMOD System

LM Tasks: - Update AMOD System Specs (A-level, B1, B5) - Provide Legacy Aegis Requirements (e.g., STM, PDM, MNF) to SI/DA - Validate Aegis Requirements Covered by Enterprise SRS’s - Remove STM/TS Functionality from Existing Components - Modify C&D Sensor Managers IAW Functional Allocation (Design, Code, and Test) - Modify Aegis Track Server Clients (Design, Code and Test) - Design, Code and Test AegisSpecific Component Framework - Integrate STM/TS into AMOD - Provide TOR/CPCRs - Verify System Performance Legend New/Modified AWS New Common -

AWS Track Clients

SI/DA Tasks:

C&D Sensor Mgrs

Common STM/TS

Common API

Aegis-Specific Component Framework

API

AMOD Infrastructure Services TI12 Middleware / OS / Hardware

LM and Third party Joint Tasks:

- Develop Enterprise SRSs for STM and TS from Aegis and SSDS - Develop UML Models - Auto-generate IDD and Interface Code from UML Models - Design, Code and Test STM and TS Components - Provide Interim and Final STM/TS Components to LM - Implement CM and Change Control of STM/TS - Implement CPCR Fixes to STM/TS Components - Support Integration of STM/TS into AMOD - Support SQT of STM and TS

Establish linked classified development environment Establish and Track Progress and Dependencies via Joint IMS Participate in Navy-led Data Model and Component Framework Working Groups Support Functional Allocation Support Definition of Data Model, TS APIs, and Common Service APIs Support Definition of Enterprise-level Processes and Artifacts Support Enterprise ETRs and Enterprise SSR Support Enterprise CCB and Prioritization/Adjudication of TORs/CPCRs

Allocation and Governance Was Essential Copyright © 2011 by Lockheed Martin Corporation

Objective Architecture Objective

Roles and Responsibilities… ADD

Architecture Precepts / Patterns Component Responsibilities / Interfaces Functional Allocation System Use Cases / Threads Common Data Groups

Product Line Development

ETR

Prescriptive

• • • • •

CM

Govern

Templates

• Peer Review • Comment Adjudications • Cross-Program Change Control • Cross-Program Review Boards • Decisions • Style and Format

Track Data Model

Message Definitions

Component Component SRS SRS

Develop Components Infra SVCs APIs

Analyze/Define System • Perform System Modeling • Allocate Requirements and Performance Budgets • Develop System Specs • Flow down Reqmts to Software Components

• Support Developer Peer Reviews • Integrate into System Configuration

Verify System

Sensor Mgmt DM

Copyright © 2011 by Lockheed Martin Corporation

Aegis

Integrate Components

TS APIs

Vehicle Control DM

GovernmentControlled

SSDS

• Support T&E through Sell-off

Component Developer

CSEA

AMOD C&D Component Architecture Message Processing… Source/Comms Management

ADS

System Track Management

Display Management

Engagement Management TS

DIF

HIF

IOP

TS

MTF

HWS

TS

DIP

TS

EMF

JTF

JTT

GWS

EFF

TS

SPY

BMF TS

SPF

ASW

Planning

TS

GWS

GTF

LAMPS (WCS)

LEF

WCS

C2 Services

Each node TS

TS

TS

TS

STM

DMF DDF

TS

SPQ-9B

TS

ICF

QBF

(CG Only)

CLM

TS

DXR

TS

DCF

RCF

SPS-67 (DDG Only)

TS

CEP IOP

C2P SGS/AC

IPC

CEF

MSF

TS

LIF

CSM

Identification

TS

IFF

TS

NVF

IAF

IDA ATAC

TS

EWF

EWS TS

ASW

ASF

Common Messages Across Ship Classes ERO/

ERS ERM One IWS Track Data Model: ~130 Messages ERG/ERA NAVSSI Copyright © 2011 by Lockheed Martin Corporation

Resource Management

MP (DDG Only)

What We Learned Process

• Documentation • Design/Integration Tools • Software Development • Test Environment

People • Skills / Expertise • Organization

Technical

Programmatic

• Architecture • Functional • Performance

• Dependencies • Risks • Earned Value

Lessons Learned Address Multiple Perspectives Copyright © 2011 by Lockheed Martin Corporation

Aegis Open Architecture Summary 1994

2000

2006

2012-2016

B7PhI

COTS Infrastructure DDG-91+

• Separation of Application/ Infrastructure • Commercial Standards • Commodity Products

CGM

Component-Based Software CG-52+

• Component-Based Designs • Layered Architecture • Configurable Test Environments

AMOD

Open Business/ Common Components

DDG-51+ / DDG 113

• Objective Architecture

CG-62-73

• Open Business Practices • Open Disclosure / Gov’t Purpose Data Rights • Increase Number of Players/ Opportunities

Copyright © 2011 by Lockheed Martin Corporation

Increased Capabilities • • • • •

AAW/BMD JTM SM-6 NIFC-CA SBT

Glossary Acronym ACB08 ACB12 ACS ADD Aegis ALIS AMOD API ASCM ASROC BL BMD C2 CCB CEC CG CIWS CM COTS CPCR CR CSEA CVN DDG DDS DM DOORS ESSM ETR GCC GFE HM&E HW IAW IDD IDS IMS IPO IR JTM KA

Description Advanced Capability Baseline 2008 Advanced Capability Baseline 2012 Aegis Combat System Architecture Definition Document (not an acronym) Greek Shield of Zeus Aegis LAN Interconnect System Aegis MODernization Application Programming Interface Anti-Ship Cruise Missile Anti-Submarine ROCket Baseline Ballistic Missile Defense Command and Control Configuration Control Board Cooperative Engagement Capability Guided Missile Cruisers Close In Weapon System Configuration Management Commercial Off-the-Shelf Computer Program Change Request COTS Refresh Combat System Engineering Agent Carrier Vessel Nuclear Guided Missile Destroyer Data Distribution Service Data Model Dynamic Object-Oriented Requirements System Evolved Sea Sparrow Missile Engineering Technical Review GNU Compiler Government Furnished Equipment Hull, Mechanical and Electrical Hardware In Accordance With Interface Definition Document Interface Design Specification Integrated Master Schedule Input/Output/Process Infrared Joint Track Management Kill Assessment

Copyright © 2011 by Lockheed Martin Corporation

Acronym LAN LM LOT MMSP MS NIFC-CA OA OAET OASM P/S PIDS PIM PSEA PSM Pub/Sub RF SAD SAN SBT SI/DA SM SMP SQT SRS SSDD SSDS SSR STM SVC SW SysML T&E TADIL TI TLAM TOR TS UML VLA VLS XML

Description Local Area Network Lockheed Martin Launch on TADIL Multi-Mission Signal Processor MicroSoft Naval Integrated Fire Control - Counter Air Open Architecture Open Architecture Enterprise Team Open Architecture System Management Publish/Subscribe Prime Item Development Specification Platform Independent Model Platform System Engineering Agent Platform Specific Model Publish/Subscribe Radio Frequency System Architecture Document Storage Area Network Sea-Based Terminal System Integrator / Design Agent Standard Missile Symmetric MultiProcessor System Qualification Test System Requirements Specification System/Segment Design Document Ship Self Defense System Software Specification Review System Track Manager Service Software Systems Modeling Language Test and Evaluation TActical Digital Information Link Technology Insertion Tomahawk Land-Attack Missile Test Observation Report Track Server Unified Modeling Language Vertical Launch ASROC Vertical Launch System eXtensible Markup Language

Application of Java In AEGIS Weapons Control

Andrew Winkler Sept 28, 2011 Copyright © 2011 by Lockheed Martin Corporation

Distribution Statement A: Approved for Public Release. Distribution is unlimited

Purpose  Overview of the use of Java in Aegis Weapons Control Open Architecture (WCOA) − Language Selection − Early Analysis  Java Virtual Machine assessment − Overview − Latest Performance Results

Copyright © 2011 by Lockheed Martin Corporation

Why Java?  Faced with a language selection in 2004 − Development team not trained in C++ or Java − Very aggressive schedule  Completely re-architect complex ~200 KSLOC shared memory based weapon control program from the top down  Complete AAW capability in 36 months.  Perceived benefits based on initial language assessment (2004) − Increased productivity − Language features − Reduced defects − Tools − Libraries  But would Java support performance requirements? − Initial Assessment performed in 2004

Copyright © 2011 by Lockheed Martin Corporation

Early Results (2004)  VM Run at RT Priority  Periodic offset by ~10ms − Default Sun timer resolution is 10ms − Can be set to hi-res – but not used for this measurement  The one outlier (~7ms) is the first 1st measurement − timer resolution? Sun 8 250ms 80%CPU Load 80 70 60

Count

50

Max (ms): 260.214 Min (ms): 253.306 Avg (ms): 259.7804 Std Dev (ms): 0.326611 Count 10000

40 30 20 10 0 252

254

256

258 Time (ms)

Copyright © 2011 by Lockheed Martin Corporation

260

262

Comparison to C++

Charts on same 2ms scale

Sun 8 250ms 80%CPU Load

70 60 50 Count

Behavior Consistent With Previous C/C++ Based Measurements for Sun

80

40 30 20 10 0 259000

259500

260000 Time (us)

Copyright © 2011 by Lockheed Martin Corporation

260500

261000

Initial Assessment  Results indicated JVM performance was generally coupled with underlying OS − Mainstream JVM on RTOS could exhibit some real time behavior − Still issues and watch items  Garbage Collection  JVM Control (other JVM threads)  Threading (priority inheritance)  Decision was made to proceed with Java − Early Data analysis indicated no major obstacles − The state of the market  Interest among mainstream vendors (BEA, Sun, IBM) for higher performance/deterministic JVMs  RT Java support from small vendors (Aicas, Aonix)  The emergence of RTSJ

Copyright © 2011 by Lockheed Martin Corporation

WCOA JVM Technical Requirements  Required − Ability to map Java thread priorities to underlying OS priorities − Ability to set Real-time scheduling policy (SCHED_FIFO, SCHED_RR) − Control over VM threads (e.g. priority, enable/disable)  Garbage collection, optimization − Deterministic behavior  Priority inheritance for synchronization  Deterministic GC  Low Jitter − Different Compilation options/control  Ahead-of-Time compilation  Just-in-Time compilation

 Desirable − Support for Real-Time Specification For Java (RTSJ) Copyright © 2011 by Lockheed Martin Corporation

Performance Data  Collected data for several JVMs  Examined Behavior of GC − 50ms periodic thread under load (~50%) − CPU load produced by creation and collection of objects − Examined instances where periodic ran long  Overruns typically caused by GC or another JVM thread such as optimization thread

 Jitter − Examine the deterministic behavior of an application over a long period of time (100,000+ data points) − Ran 20ms periodic thread under load (~50%) − CPU load produced by creation and collection of objects  Tactical Testing − Examined critical timelines running WCOA tactical code

Copyright © 2011 by Lockheed Martin Corporation

Non-Deterministic Garbage Collection

50ms Periodic Trace Events from Periodic thread

Kernel Trace

Copyright © 2011 by Lockheed Martin Corporation

Periodic Runs Long

Non-Deterministic Garbage Collection (Continued)

Periodic Runs Long

Periodic Should Have Run Here

GC Thread

Periodic thread runs after GC

Copyright © 2011 by Lockheed Martin Corporation

Deterministic Garbage Collection

No Overrun Periodics 50ms Periodic

GC Thread

Copyright © 2011 by Lockheed Martin Corporation

Deterministic Garbage Collection (Continued)

Signal to Wake Periodic Thread

GC Thread

Copyright © 2011 by Lockheed Martin Corporation

Periodic thread preempts GC and runs on time

Product ‘A’ JVM Jitter Data Product A Jitter (20ms 50%CPU) 0.18 0.16 0.14

Time (s)

0.12 0.1 0.08 0.06 0.04 0.02 0 0

5000

10000

15000

20000

25000

30000

Average (ms)

Stdev (ms)

Max (ms)

Min (ms)

28.446

18.150

169.189

20.142

Copyright © 2011 by Lockheed Martin Corporation

35000

Product ‘B’ JVM Jitter Data Product B Jitter (20ms Periodic 55%CPU) 0.021

0.0208

Time (s)

0.0206

0.0204

0.0202

0.02

0.0198

0.0196 0

5000

10000

15000

20000

25000

30000

Average (ms)

Stdev (ms)

Max (ms)

Min (ms)

19.997

0.056

20.935

19.775

Max Deviation < 1ms: Supports WCOA Requirements Copyright © 2011 by Lockheed Martin Corporation

Testing in Tactical Environment  Performed significant testing using three JVMs using WCOA tactical programs − Allowed study of different JVM features in a realistic environment  Analyzed Impact of JVM threads/features to critical timelines  JIT adversely impacted certain critical timelines running under two of the JVMs (one RT and one non-RT)  AOT or JIT at initialization solved problem for the RT JVM  JIT at init slows application initialization significantly  One JVM’s Optimization thread interfered with application health-checking – causing application to be terminated  Disabling optimization resolved problem  GC tuning essential even for Deterministic GC.  Poorly tuned RT JVM runs as poorly as NRT counterparts  Prevent out of memory conditions paramount

Java Performance Verified In Tactical Testing Copyright © 2011 by Lockheed Martin Corporation

What about benefits of using Java?  Did we get the benefits we were hoping for? − Ada programmers adapted quickly to Java  Tools like Eclipse helped transition − Developed ~150 KSLOCs in 18 months  Portability of Java allowed desktop testing & verification on Windows Platform  Verified 3500 Requirements in 5 months  89% 1st time pass rate  Java Performance − Java can support soft real-time, mission critical applications − Meets WCOA Performance Requirements  Looking forward − Keeping an eye on safety critical Java work and it’s implications for a mission critical profile  Development must keep in mind value proposition for users

Team Realizing Huge Benefits by Switching to Java Copyright © 2011 by Lockheed Martin Corporation