open source in mission critical operations -...

Open Source in Mission Critical Operations

Speakers: John Scott (Moderator)Director, Open Source Software & Open Integration, Mercury Federal Systems, Inc.

Rob WolborskyProgram Manager, Tactical Networks, US Navy Program Executive Office Command, Control, Communications, Computers and Intelligence

Paul D. SchoenDirector, Infrastructure SW Development Group & SOSCOE, The Boeing Company

Don BurkeIntellipedia Doyen, Office of the Chief Information Officer, Central Intelligence Agency

Martin StadtlerManager, Consulting Practice, Red Hat

Mission Critical Operations

Information Dominance Anytime, Anywhere…

PEOC4I.NAVY.MIL

Program Executive OfficeCommand, Control, Communications, Computers and Intelligence (PEO C4I)

Benefits of Open Source to the Tactical Domain

DISTRIBUTION STATEMENT D. Distribution authorized to the Department of Defense and U.S. DoD contractors only due to critical technology content November 2008. Other requests shall be referred to the PEO C4I and Space (Program Office PMW 160) or SPAWAR Office of Congressional and Public Affairs (SPAWAR 00P).

5 Nov 2009Robert Wolborsky

Program Manager (PMW 160)

UNCLASSIFIED//FOR OFFICIAL USE ONLY

Benefits of Open Source to the Tactical Domain

• The flexibility of using open source products products promotes interoperability between COI services

• More Open = More Flexibility = More Adoption

• More Adoption = More Invocation of multi- services

Ex. METOC data consumed by C2 services

• Ease in Reengineering• Reduces time of delivery of services to the

fleet

UNCLASSIFIED//FOR OFFICIAL USE ONLY

Benefits of Open Source to the Tactical Domain Cont’d

• Reduces our dependencies to any single entity

• Promotes the states of vendor agnostic

Ex: Ease of transitioning capabilities from Jboss to Sun application servers (vise versa)

• Increases the independence of Tactical programs in influencing the direction and modification of open source capabilities.

• Above all, It reduces IT burden and life cycle costs in procurement of these services!

UNCLASSIFIED//FOR OFFICIAL USE ONLY4

We get it.We also integrate it, install it and support it. For today and tomorrow.

111/19/2009 3:44:27 PM

Approved for Public Release, distribution is unlimited. PEO Integration Case 09-066. 2 November 2009Approved for Public Release, distribution is unlimited. PEO Integration Case 09-066. 2 November 2009

Open Source Software use in Mission/Safety Critical Systems

by System Of Systems Common Operating

Environment (SOSCOE)

Open Source Software use in Mission/Safety Critical Systems

by System Of Systems Common Operating

Environment (SOSCOE)

Paul Schoen, DirectorInfrastructure Software Development & SOSCOECombat Systems, NS&S, The Boeing Company

Paul Schoen, DirectorInfrastructure Software Development & SOSCOECombat Systems, NS&S, The Boeing Company

Approved for Public Release, distribution is unlimited. PEO Integration Case 09-066. 2 November 2009 2 of xx 11/19/2009 3:44:27 PM

SOSCOE Components and Tools promote Reuse

• SOSCOE Software Developer toolkit (SDK) includes – Runtime software

• Executable processes• Run time libraries

– Developer Tools• Code Generators• TDD Editor• Administrative tools

– Documentation• Programmer’s Reference Manual• Developer’s User Guide

– Installation and field upgrade tools– Configuration examples and files

Developer Tools

Deployed Executables

User Documentation

Use of a Single Toolkit significantly reduces maintenance costs,promotes reuse of applications and guarantees interoperable solutions


SOSCOE is a collection of product lines associated with scalable Editions

Multiple products and editions allow SOSCOE to meet performance, scalability, portability, composability, and interoperability requirements of platforms

Standard EditionReal Time Edition

Micro Edition

Tactical COE Foundation: Discovery and dissemination of services/data in a secure and trustable manner for the tactical environment

Interoperability: Extensible and secure interoperability of data and services with external systems to include current force, enterprise services (NCES), and JIMI

Systems Management: Uniform configuration and process management and customization for the tactical environment. Includes support for the maintenance of complex multi blade deployments, field update/versioning

Collaboration: Instant messaging, whiteboard, and email capabilities supporting tactical users including seamless collaboration to enterprise users

User Experience: Comprehensive source of user documentation, guidance, examples, and tutorials for solution developers and integrators

Information and Knowledge Services: Data management, mining, and search for the tactical environment including semantic interchange

Workflow Automation and Policy: Complete environment for automating and orchestrating operational task sequences for SOA-based applications

SOSCOE Product Line SOSCOE Deployments StandardEdition

Real-timeEdition

MicroEdition 1.8 2.0 2.5 3.0 3.5

Class I Unmanned Air Vehicles (UAV) Class IV Unmanned Air Vehicle (Fire Scout) Non Line of Sight – Launch System (NLOS-LS) Small Unmanned Ground Vehicle (SUGV) Multifunctional Utility Logistics Equipment Vehicle (MULE) Unattended Ground Sensors (UGS) Soldier Systems Command and Control Vehicle (C2V) Reconnaissance and Surveillance Vehicle (RSV) Infantry Combat Vehicle (ICV) Mounted Combat System (MCS) Non-Line-Of-Sight Cannon (NLOS-C) Non-Line-Of-Sight Mortar (NLOS-M) Medical and Evacuation Vehicle (MedEvac) Maintenance and Recovery Vehicle (MRV) Centralized Controller B-Kit Objective and Additional Systems

Armed Robotic Vehicle (ARV) Class II Unmanned Air Vehicles (UAV) Class III Unmanned Air Vehicles (UAV) Intelligent Munitions System (IMS)

SOSCOE Deployments StandardEdition

Real-timeEdition

MicroEdition 1.8 2.0 2.5 3.0 3.5



SOSCOE Deployments StandardEdition

Real-timeEdition

MicroEdition 1.8 2.0 2.5 3.0 3.5




Native OSNative OS

Software Make/Buy/Reuse Design Models

Reuse Model

API

Integration Code

Reuse Code

New Code Model

API

SOSCOEImplementation

Software

Buy Model

API

Integration Code

COTS/GOTS

SOSCOE ServicesSOSCOE Services SOSCOENative OS

By basing the SOSCOE APIs on standards (DISR, WSTAWG, OMG, etc.), the Battle Command Services are isolated from any

dependence on the computer HW, OS and COTS products. This will allow SOSCOE to upgrade/change implemented code over time

without changes required in the application services.


Today’s Unified Battle Command Challenge – Affordable Modernization

• Multiple tactical systems, all with unique and beneficial features in five major components for each system

– Wide range of hardware solutions– Operating systems (Windows, Linux, etc. and versions

therein)– Communications interfaces, processor allocation,

applications control, data management, and information assurance (middleware)

– Application Software– System user interfaces or I/O

• Cost savings are achieved through standardization today and evolution to common HW, OS, Middleware, SOA, and GUI

– Leveraging COTS and OSS increases saving in development and maintenance

Hardware & Devices

OperatingSystem

MiddlewareSoftware

Applications

User Interface

ComputerSystems


“TIERS” of Use of SOSCOE - An Investment Strategy in Reuse

Integration Goal Required SOSCOE Enabling UBC Capabilities

Supported / Req Transport

External Capabilities

Integrated into Battle Command

BC Infrastructure Components(TIN, Policy, …)

WMI Compliance

Integrated on Platform

COE Components

ICS OS CompliantHealth to PSMRSCo-exist with WMI

Integrated into Tactical NCIE

Tactical Service-based Components

Common Transient Data model TopicsNMS

>=JTRS SRW/WNW Waveforms

Integrated into Strategic NCIE

Strategic SOA Components

COI-coordinated web service interfaces

>= WIN-T/JNN Comms

GIG-BENCES Discovery

Legacy Interoperability

NONE SOSCOE Interop Legacy Waveforms(EPLRS, SINCGARS, …)

Native formatted message interface standards

Tier 0Interfacing

Tier 1Net-CentricExchange

Tier 2Platform Integration

Tier 3Int. BC

Net-CentricThreshold

There is no impact to the external system to interoperate with SOSCOE based system but communication is limited to existing message sets and NR KPP not satisfied

Provides complete and seamless interoperability between systems, allows for the complete leverage of Battle Command Applications at the component level.

External systems “adopt” enough SOSCOE services to discover, be discovered, and exchange Data in a trustable manner, BUT no ability to participate as a full member of the COI with respect to Application Services

External systems “port” their systems on top of SOSCOE but do not decompose the software into “TIN-ABLE Components”. External systems can exploit a SOSCOE based system but can not fully exploit external system beyond Data

External systems implemented using WEB Services (SOAP, WSDL, HTTP, etc) Interact with a SOSCOE based system via the “Edge Node”. Limited to high bandwidth connections and “subset” of data exposed


SOSCOE – Conclusion

• SOSCOE is a tailorable software toolkit to support legacy and SOA applications for the Tactical Domain

– Designed to exist in a Bandwidth and Computer constrained environment – Supports net centric tenets– Product Line approach allows for a Scale-able application and maintenance

• Provides critical Information Assurance • Reduces Enterprise life cycle costs

– High degree of use of Open Source Software and COTS• Enables a loosely coupled system with “Plug and Play” of new hardware and software applications

• Allows the user to establish an “Investment Strategy” for evolutionary and incremental change

The Army-Boeing partnership has made SOSCOE an integrating solution for the Tactical Domain

The IC’s Social Software Environment

For 11/5/2009 panel Don Burke, CIA 1

Don BurkeCIA/CIOFor GOSCON panel11/5/2009

Disclaimers and Context The views expressed are my own and not those of the US Federal Government

Links or discussions of specific products do not constitute endorsement


Intellipedia: Some Background Represents a suite of tools on three different networks

The servers and software are maintained and operated by the Office of the Director of National Intelligence

Users of the tools populate the information CIA has been a leading advocate and was the pilot customer for Intellipedia in 2005


A Suite of Open Source ToolsThat enable Andy McAfee’s “SLATES” MediaWiki – Intellipedia Gallery – Photo management KnowledgeTree ‐ A Web‐based Share drive Jabber – Chat WordPress ‐ Blogging StatusNet (formerly laconica) – Microblogging


ComparisonWikipedia Allows "anonymous" edits Encyclopedic Few contributors responsible for majority of edits

Neutral Point of View (NPOV)

Intellipedia Edits are attributable Not limited to being an encyclopedia

Many contributors from different agencies

Attributable Point of View


Lessons Learned Along the Way Start with small projects first Myth: It is all about youth/"net generation" Keep it Simple (wiki editing) Be Selfish Grassroots vs. Top‐Down The Power of One Maintain a “Sense of Play “


Our Core Principles and Results Work at Broadest Possible Audience Replace Existing Processes Work topically, Not Organizationally

Result: Thousands of small wins a day People connecting, sharing, and collaborating

See Prof. Wesch’s video: “The Machine is Us/Using Us.”


Questions?

Tell us what you think: Complete the survey

open source in mission critical operations -...

Documents