business models for interoperability

Your systems. Working as one. Your systems. Working as one.

Business Models for Interoperability

Practical efficiency for large system software development

Who Cares About OA?

© 2012 RTI 2

Everyone here!

Why Interoperable Open Architecture?


RTI Experience: Real-‐Time Infrastructure


RTI Background

Market Leader Over 70% DDS mw market share1 Largest embedded middleware vendor2

Standards Leader Active in 15 standards efforts OMG Board of Directors DDS authors

Real-‐Time Pedigree Founded by Stanford researchers High-‐performance control, tools history

Maturity Leader 500+ designs 350,000+ licensed copies TRL 9

© 2012 Real-‐Time Innovations, Inc.

1Embedded Market Forecasters 2VDC Analyst Report

6

2008

Global Support and Distribution


RTI Connext

RTI DataBus

Connext Micro

Pub/Sub API (DDS subset)

Small Device Apps

Connext DDS

Pub/Sub API (Full DDS)

DDS Apps

Connext Messaging

Messaging API (DDS++ & JMS)

General-‐Purpose Real-‐Time Apps

Connext Integrator

Adapters

Diverse Apps/Systems

Administration

Monitoring

Recording

Replay

Persistence

Logging

Visualization

Common Tools and Infrastructure Services


Interoperability Challenge

© 2012 Real-‐Time Innovations, Inc. 9 9

GVA DEF STAN 23-‐09

Interoperability


Interoperability

Busin

ess M

odels

Data Centric Approach

Data-‐centric middleware maintains state Infrastructure manages the content Developers write applications that read and update a virtual global data space


Persistence Service

Recording Service

Source (Key) Power Phase

WPT1 37.4 122.0 -12.20

WPT2 10.7 74.0 -12.23

WPTN 50.2 150.07 -11.98

Popular standards: DDS API, wire spec 13

Controlled State

Data centric Single source of truth Known structure Clear rules for access, changes, updates

Technologies Database Data-‐centric middleware

11/8/2012 14

DDS: the Data Bus Standard

Data Distribution Service from OMG

standards org 470+ members UML, DDS, SysML, MoDAF, DoDAF, more

DDS: open & cross-‐vendor Standard API enables choice of middleware Standard wire spec enables subsystem physical interoperability ~10 competitive implementations (!)


Cross-‐vendor source portability

Cross-‐vendor interoperability

DDS-‐RTPS Protocol Real-‐Time Publish-‐Subscribe

Distribution Fabric

DDS API

15

Government Adopts DDS

Dominant in military DISA: DISR mandated Navy: Open Architecture, FORCEnet Air Force, Navy and DISA: NESI Army, OSD: UCS NATO, UK MOD, South Korea, many more

Many other applications Air traffic control, industrial automation, transportation, medical

Hundreds of active programs Multiple interoperable implementations


17

Interoperability between the applications demonstrated by six different vendors in 2012

OCI ETRI PrismTech IBM RTI TwinOaks


Is This Interoperability?


Semantic

Syntactic

Technical

Technical Communications (how to share data) Syntactic Interfaces (what data to share) Semantic data dictionary (what data means)

What are we Trying to Achieve?

© 2012 RTI 19

Open Architecture Requires Interoperability at a Higher Level Than Key Interfaces.

Interchangeability

Integrateability

Extensibility

Interoperability: all of the above without rewriting everything

Interoperability


Interoperability

Busin

ess M

odels

Architecture Efforts


AF Avionics

Navy CCRL

Army COE

OSD UCS

GVA DEF STAN 23-‐09

Interoperability


Interoperability

Busin

ess M

odels

Open Business Models for Infrastructure Vendors

Enabling the basis for interoperability


The Great OSS Biz Model Quest

Pay only for support & services A poor biz model

Worked for Linux Community development challenge

Hidden adoption expense

Freemium (Dual licensing)


What Do Users W

No license cost Can modify and distribute modifications Community development Community forum Use for any application Access (right) to source code Freely downloadable


Highly Distributed Real-‐Time Systems

Many applications, processors 100+ processors in a car 1,000+ processors on a ship 100k+ processors in an industrial system 40M+ lines of code

Many people & teams Crosses divisions, companies, orgs Includes end users, suppliers, subs 50+ s/w suppliers for a modern naval ship


What Is an Infrastructure Community?

Any community sharing software Seeking a common or interoperable software infrastructure Across projects, divisions, companies, programs

Examples Software supply chains Enterprises or corporate divisions Government or industry standards communities (FACE, UCS, COE, ICE) Large projects


Infrastructure Communities


IC: JHU APL

Paid commercial license

Scope: Project

Free Project

Free Project

Free Project Paid commercial

license Scope: Project


Scope: Project

IC: UCS


Scope: Project

Free Project

Free Project




Scope: Project

IC: Audi


Scope: Project

Free Project

Free Project




Scope: Project

29

OCS Model Summary

Free, full source & binary DDS for IC No cost, no hassle, no strings Latest version Share source & binaries Professional T&M support

Low-‐cost commercial product for projects Tools, advanced functionality, warranty, platforms Simple, open, per-‐developer pricing Starts at £800/developer No royalties or deployment fees


I Open Source!

restricted to an IC

Within your IC: very open Outside your IC: why do you care?

It maps well to the enduring infrastructure problem


Many Biz Model Needs

Professional resources Support all versions (free, paid) Offer professional guidance, services

No legal strings Offer warranty and indemnification Control provenance No copyleft; keep your IP

Drive quality & usability Enforce quality control Push usability, docs, examples

Ensure vendor partnership Proactively develop to match needs Encourage latest technology, no branches Motivate features, usability, quality, accessibility Ensure vendor profitability

Open, fair pricing Offer usable free product Predictably & reasonably price advanced product Bound support costs Eliminate runtimes


Let you adopt without friction Support healthy vendor with known cost Encourage speculative vendor investment Retain your IP control Drive efficiency and low cost


Open Community Source Balance

Open Community Source Free, viral adoption

Support available

Low friction upgrade Advanced functionality, tools, platforms, warranty Clear, reasonable fees without surprise


IC model benefits Provides you freedom Encourages vendor investment Lowers overall cost

Open Community Source Model

Addresses real needs of customers Free, current, supported base product Powerful, low-‐friction upgrade Clean, open licensing Clean, open pricing

Addresses real needs of vendor Encourages investment in product Supports strong relationship


Business Models for Government Acquisition

Achieving the promise of interoperability


The sole imperative to control software cost is to establish a stable team working on a single code base

-‐-‐ Stan Schneider


Implications (!)

Stable teams imply continuous investment

Code repositories are expensive branches Even more expensive to revive

The IP without the team is inefficient

At least for emerging products, there is no stable external team

The best structure for large projects is team/code pairs Modularize by reducing team/code size => define interfaces and architecture


Repository Competition Process

Competition divorces team from code -‐learn, re-‐design, re-‐ -‐code

Result is very expensive!


Creation

Team Code Base

Team Team Team

Code Base

Competition

Team

Code Base

Code-‐Team Competition Process


Code Base

Team

Create and Maintain Multiple Code-‐Team Pairs

for Each Module

Code Base

Team

Code Base

Team Compete these Pairs for Each Module of Each Project

Code Base

Team

Build Project from Modules

Team Code Base

Code Base

Team

Team

Code Base


How? Interoperability.

41

How Does Interoperability Cut Cost?

Interoperability changes the nature of competition Modules are less expensive than code repositories

rewards excellence


Achieving Cost Control


Address interoperability levels with architecture Communications (how to share data) Interfaces (what data to share) Semantic data dictionary (what data means)

Reward module competition with acquisition policy

Look for opportunities to compete modules Encourage buy v build Reduce module granularity over time

The Required Technology is Maturing


RTI Databus Peer-‐to-‐peer for performance

System-‐of-‐systems routing RTI Databus

R

RTI Databus

R

R R

R R

R R

Hierarchical topology: Peer-‐to-‐peer within a system Automatically route data up/down the hierarchy

st Enduring organizations to evolve it Structures across programs to leverage it Open acquisition model to encourage it

Specify or own the right things Open semantic data model Open standard interfaces Code repositories only when forced


Why Invest in Interoperability?


Your systems. Working as one. Your systems. Working as one.

business models for interoperability

Documents

realtime innovations

realtime infrastructure

dds dds

dds api dds

ddsrtps protocol realtime

distributed realtime

interoperability challenge

crossvendor interoperability