1

1

Maritime Domain Awareness Data Sharing

Community Of Interest(MDA DS COI)

Spiral 3

Chris RaneyMDA DS COI Pilot Co-Lead

raneyc@spawar.navy.mil(619) 553-5282

22

History of the MDA DS COI

MDA Conference @ NORTHCOM

Feb 06

Spiral 2 DemoApr 08

Spiral 1 Kick Off Mar 06 Spiral 1 Demo

to CNO N6Dec 06

Spiral 1 DemoOct 06

Spiral 2 Kick Off Apr 07

National CONOPS for

MDAAug 07

DHS EA for MDA Designated

Apr 08Spiral 3 Kick Off Jan 08

Spiral 3 DemoMar 09

Advancing Net-Centric Information Sharing of MDA Data

Transition to National MDA Architecture

Management Hub

Navy MDAOffice

EstablishedDec 08

Agile Interagency Team – Short Timelines – Delivering Capabilities

DoD EA for MDA

DesignatedAug 07

33

MDA DS COI Strategy

• Use a common vocabulary and NCES to make data visible, accessible, and understandable.

• Facilitate a net-centric information sharing process.• Leverage existing systems, don’t build new ones. • Enhance existing tools by providing valuable additional

data for the operator/analyst.• Create the rich information environment called out in the

National CONOPS for MDA.• Harness the power of the “coalition of the willing.”

Considered an exemplar by DoD CIO

4

MDA DS COI Spiral 1

• Spiral 1 demonstrated in October 2006 was first instance of cross federal net-centric information sharing:

– Data Producers: Navy AIS PoR, NAIS, AMRS, MSSIS– Data Consumers: iMapData Viewer, Google Earth, TV32, GeoViz,

WebCOP, and Google Maps Mediation Service (to support unanticipated user)

4

Data Producers

NCES Messaging Service

MSSIS - Volpe (DOT)

USCG OSC

ONI AMRSNavy AIS PoR

C D E FB GA

GMMSGeoVizWebCOPTV-32iMapData

Unanticipated User

Navy User

Navy User

DOT User

DHS User

Data Consumers

MDA DS COI Channels:

A – NE USAB – SE USAC – MED WestD – MED EastE – West USAF – Other AOIG – AMRS

Uses DISA provided NCES

Messaging Service

Demonstrated in CWID 07

55

MDA DS COI Spiral 2

• Increase number of MDA data producers and consumers• Develop Value Added Services.• Develop, expand, and enhance MDA data schemas. • Initiate transition of services to operational capabilities.

Demonstrated in Trident Warrior 08

66

MDA DS COI Spiral 3

• Exposing new data sources to the Enterprise on multiple security levels:– USCG Advanced Notice of Arrival (ANOA) data (NIPR).– ONI Single Integrated Look Out (SILO) data (SIPR).

• Pilot an Attribute Based Access Control (ABAC) framework to allow authorized sharing of this restricted data (e.g., Personally Identifiable Information (PII)).

• Support MDA related exercises to increase awareness of net-centric information sharing at the operational & tactical levels.

• Support information sharing with interagency and international partners:– DoD, DHS, DOT, DOJ– Canada, UK, France, NATO, etc.

7

Data Management Working Group

• Completed schema convergence with Maritime Information Exchange Model (MIEM) – SILO and ANOA Schemas (using v0.9).– Identified implementation challenges with MIEM.

• Supported MIEM 1.0 development – Provides constructs for representing vessels, cargo, facilities,

and people.

• Laid groundwork for MIEM transition to a domain under the National Information Exchange Model (NIEM).

• Aligning with Universal Core (WHO, WHAT, WHEN, WHERE)

– MDA DS COI influential in development of Universal Core (UCore) since 2007.

7

8

8

MIEM, NIEM, UCore

UCore

NIEMNIEM-

Maritime

Domain of

High Level Compatibility

MDA DS COIDMWG

CMAMIEM

MIEM 1.0MIEM 0.9

AIS XML Formats

TransitionImprove

Converge

GatherForm

Add ANOASILO

WHO, WHAT, WHEN, WHERE

Spiral 1

Spiral 2

Spiral 3

9

Notice of Arrival (NOA)

• Statutory 96 hour notification requirement for all vessels bound for or departing from U.S. ports or places.

• Vessel, cargo, and crew data (including PII).

• Increases situational awareness.

• Allows predictive analysis.

• Enhances threat evaluation.

Sensitive PII Must Be Protected

10

ANOA Data Services

• USCG NOA Publishing to NCES Messaging Service (ECB) – Publish modified NOAs in 1 hr intervals.– Publish to the Geographic Channels based on Arrival Port.– Format is SANS Schema (No PII).– Role based access control managed by MDA DS COI Pilot Technical

Team, USCG Approval.

• Federated Search (SANS schema)– Leverage experience with Historical Archive Service.– Query types:

• By NOA ID.• By date interval for COTP.• By date interval for Vessel (IMO, Vessel Name, Callsign).

11

Single Integrated Look Out (SILO)

• Called out in the Global Maritime Intelligence Integration (GMII) Plan– Increases situational awareness.– Fosters collaboration between intel analysts,

operators, and the community. • ONI consolidates various Vessel of Interest (VOI) lists

from across DoD and DHS.• VOI data is sent from the intel/ops centers to the SILO

Aggregator via Atom feeds. • SILO Aggregator publishes the VOI data in the MIEM-

based SILO schema to NCES Messaging Services on SIPRNET using web services.

12

SILO Data Services

• ONI SILO Publishing to NCES Messaging Service (SIPR) – Publish vessels of interest data every 4 hours. – Publishing data to the SILO channel.– Format is based on MIEM v0.9 – Role Based Access Control (RBAC) will be managed by MDA

DS COI Pilot Technical Team with ONI Approval.

• SILO Federated Search – Query types:

• By Vessel Name• By IMO• By MMSI

12

13

13

Attribute Based Access Control (ABAC)

Information is virtually ‘trapped’ within systems that require account creation, or addition to a list. Manual process to add EACH user to EACH resource.

Resource 1

Resource 2

Millions of Users

Today

Future

Attributes

… Policy

Policy

Domain

Access ListAdd EACH

User to List

Administrator

Resource 1

Resource 1 Owner

Manual

RequestAccess

Request Access

Add EACH User

Account

Resource 2 Manual

Single User

Users gain access seamlessly- no pre-registration, no delay …

… while the services and data remain secure & protected!

Resource 2 Owner Administrator

AdministratorAdministrator

14

Attribute Based Access Control for MDA

• Enables automated enforcement of information sharing policies in a net-centric environment.

• Leverages enterprise identity management services.

• Includes a local attribute store to support those users and/or attributes that are not in the enterprise attribute store.– Non-CAC users.– Attributes such as nationality or

role (law enforcement).

ANOA

ABAC

ANOAwithout

PII

ANOAwith PII

No ANOA

US-MDA User

US-MDA- Law Enforcement

User

Foreign-MDA User

1515

MDA DS COI Information Architecture

MASS SD

MASS @ Volpe NCES Messaging Service

MSSIS

MSSIS Partner

Countries

NAISUSCG

SCC-JSMS

DRDCAtlantic

NWDC

FLTAISData

MASS C5F MASS C2F MASS C3F MASS CPF

RM

GCCS-M

RM

GCCS-M

RM

GCCS-M

RM

GCCS-M

MDA PA

CDWSG

NCES Messaging Service

CMA MASTER GMMS

SAGE @NORTHCOMMIDASSeaHawk

Via RNOCs

NAVAIR

Neptune

SIPR

NIPR

PANDA

C4I Suite

AISRCVR

AIS JunctionBox

ECDIS-N SADI ISNS

RM

GCCS-M

ISPAN

Afloat AIS

AIS

ANOA

Radar

SILO

Anomalies In Progress

Imagery

OperationalGMMS

MSC

ADS

DRDCValcartier

USCG OSC

Telesto @DSTL

AMN

SILO ONI

OLC2/TWGMMS

OGC Viz

IRRIS @TRANSCOM

TENCAPRAGE

JUMPSMASTER

Spiral 3 producers & consumers

ADS

DASAMRSONI

On 218 Ships

16

What Have We Learned?• Technical:

– NCES and other SOA infrastructures (Consolidated Afloat Networks and Enterprise Services (CANES), etc) are still evolving.

• Strong partnership with NCES was basis of MDA DS COI’s success.

– Tiered security model is required to support non-classified data as well as maritime military information.

– Enterprise wide identity management infrastructure is vital to dynamic information sharing policies.

• Governance:– Most government net-centric information sharing is done only

when driven by senior leadership.– Effective governance is crucial to promoting common services

and schemas across the enterprise.– High level support can be leveraged to break down policy

barriers.16

17

What Have We Learned?• Cultural:

– DoD policy mandates net-centric information sharing, but provides no enforcement mechanism.

– Net-centricity involves much MORE than posting information to a portal or providing portal access.

– PoRs are systems oriented and not resourced to support information sharing.

– MDA involves more than just Navy + Coast Guard.

• Implementation– Organizations need support to shift to the net-centric information

sharing paradigm. – Coordination and collaboration is required between data

producers, consumers, and core enterprise services providers.

17A core team is required to broker technical, governance, and cultural, and implementation issues.

18

Harvard Business Study

• Describes how the MDA DS COI overcame organizational, governance, political, technical and cultural challenges to sharing information across federal agencies and demonstrated net-centric information sharing.

• “When you’re trying to transform a department, it’s not worth pushing people. They have to want it.” – Mr. Mike Krieger (then DOD CIO/IP&I)

– Coalition of the willing transforming MDA information sharing.

• “It’s what I have been trying to get to. This can give me a netted Navy.” – VADM Edwards (then CNO N6)

– Net-centric information sharing is critical to achieving maritime domain awareness.

18

Maritime Domain Awareness: A Case Study in Cross-Boundary Information Sharing Among the United States Navy, Coast Guard, and Department of Transportation

Leadership for a Networked World Program/Executive EducationJohn F. Kennedy School of Government, Harvard University

MDA DS COI and its lessons learned will help shape the next generation of military and civilian leaders.

19

Impacting DoD Strategies and Policies

19

JROC 010-08: MDA DS COI used as an example on how to expose data

and services to accelerate delivery of

net-centric capabilities.

CJCSI 6212.01E: MDA DS COI used as an example on

how to expose data and services as part of Net-Ready Key Performance Parameter

(KPP).

DoD Congressional Report: MDA DS COI is

a use case for how COI’s can help the DoD’s net-centric transformation and share information

across the federal government.

DoD IM&IT Strategic Plan (2008-2009): MDA DS COI is highlighted as a net-centric information sharing success

story.

MDA Architecture Management Hub Plan: MDA DS COI’s

ground breaking approach and strategy will be used as a foundation for the National

MDA Architecture Management Hub efforts.

DoD Information Enterprise Transition Plan: MDA DS COI is an example of how the DoD needs to transform its stove-

piped approach to achieve the DoD’s net-centric information

sharing vision.

Maritime Security Partnerships: The Naval Studies Board from the

National Research Council includes the MDA DS COI

as a key enabler of information sharing to support the National Strategy for Maritime

Security.

20

Return On Investment

• Total Navy & USCG Investment to Date: $5.98M.• Over the past three years, the MDA DS COI has:

– First persistent net-centric information sharing capability across the federal government and coalition partners.

– Influenced major net-centric/SOA-related acquisition programs such as NCES, CANES, NAIS, IOC/C21, etc.

– Supported major Navy exercises to expose the warfighter to net-centric operations in a SOA environment.

– First to demonstrate cross domain net-centric information sharing using DISA’s CDWSG.

– Empowering a coalition of the willing who are embracing net-centric technologies to share MDA data.

20

The MDA DS COI has been an outstanding net-centric pathfinder for DoD & DHS and has been an effective risk reduction for emerging

net-centric programs and initiatives.

2121

Transition Status• In April 2008, RADM Deutsch and Glenn stated that the MDA DS COI

needs to be elevated and sustained at the national level. • On 3 June 2008, the MDA DS COI ESC requested formal transition to

the National MDA Architecture Management Hub via the MDA Stakeholder Board.

• DON CIO designated the lead for the National MDA Architecture Management Hub.

• DoD CIO and DON CIO are working together to transition the MDA DS COI into the National MDA Architecture Management Hub.

– Transition timeframe: April 09.

• Transition Intent:– Expand the success of the MDA DS COI to implement net-centric data.

sharing and services to support the Global Maritime COI.– Document lessons learned for broad application.– Utilize the MDA DS COI processes for iterative development.

22

Proposed Transition of MDA DS COI

MDA DS COIData Mgmt WG Policy WGPilot Tech WG

23

Successfully Transformed Data Sharing

• Successfully made data visible, accessible, and understandable using Net-Centric Enterprise Services.– Exemplar for the Net-Centric Data Strategy.

• Transformed how MDA data is shared across the federal government.– First instance of net-centric sharing across multiple federal agencies.– Awarded 2007 Federal CIO Leadership Award.

• Catalyst for changing information sharing culture.• Operationalized net-centric information sharing.

– Publishing over 750,000 positions per day to NCES.– Supporting operational users and consumers.

23

A Recognized Net-Centric Success

2424

Questions?

Spiral 3 Demonstration: https://mda.spawar.navy.milOperational GMMS: https://mda.csd.disa.mil

SILO Aggregator: http://mio.nmic.smil.mil/SiloWeb2/