1. Maritime Domain Awareness Data Sharing Community Of Interest (MDA DS COI) Spiral 3
Chris Raney
MDA DS COI Pilot Co-Lead
(619)

2. History of the MDA DS COI
DoD EA for MDA Designated
Aug 07
DHS EA for MDA Designated
Apr 08
MDA NORTHCOM
Feb 06
Spiral 1 Demo
Oct 06
Spiral 2 Kick Off
Apr 07
Spiral 3 Kick Off
Jan 08
Spiral 3 Demo
Mar 09
Advancing Net-Centric Information Sharing of MDA Data
Transition to National MDA Architecture Management Hub
Spiral 1 Kick Off
Mar 06
Spiral 1 Demo to CNO N6
Dec 06
National CONOPS for
MDA
Aug 07
Spiral 2 Demo
Apr 08
Navy MDA
Office
Established
Dec 08
Agile Interagency Team – Short Timelines – Delivering Capabilities

3. Considered an exemplar by DoD CIO
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. Uses DISA provided NCES Messaging Service NCES Messaging Service
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)
Data Producers
Navy AIS PoR
USCG OSC
MSSIS - Volpe (DOT)
ONI AMRS
MDA DS COI Channels:
A – NE USA
B – SE USA
C – MED West
D – MED East
E – West USA
F – Other AOI
G – AMRS A B C D E F G
Uses DISA provided NCES Messaging Service
Spiral 1 Pilot demonstrated in October brought together data producers and consumers:
Spiral 1 AIS Data Producers:
USCG - NAIS
Navy AIS PoR
MSSIS
AMRS
Spiral 1 AIS Data Consumers: Selected representative cross section of User Defined Operation Picture (UDOP) - visualization tools to view AIS Pilot data
iMapData Viewer on HSIN (pre-selected by HSIN), Google Earth, TV32, GeoViz and WebCOP (examples of UNCLAS C2 COP)
Developed Google Maps Mediation Service to support unanticipated user
NCES Messaging Service
iMapData
TV-32
WebCOP
GeoViz
GMMS
DHS User
DOT User
Navy User
Navy User
Unanticipated User
Data Consumers
Demonstrated in CWID 07

5. Demonstrated in Trident Warrior 08
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.
Talking Pt #1: Develop, expand, and enhance MDA data schemas
-- Incorporate UCORE, converge with Maritime Information Exchange Model (MIEM)
Talking Pt #2: Initiate Transition of Services to the Defense Enterprise Computing Center (DECC)
-- Provides unanticipated user with 24/7 operational capability
Demonstrated in Trident Warrior 08

6. 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.
The Maritime Information Exchange Model (MIEM) is transitioning to become a domain of the NIEM
Provides constructs for representing vessels, cargo, facilities, and people
Business Case for Transition:
Existing governance
Existing configuration management
Existing tool support
Existing help desk support
Existing training support
Fosters alignment with DHS and DoJ
Grant-money tied to NIEM-adoption
USCG and CBP are major MDA players in DHS

8. MIEM, NIEM, UCore Gather Form UCore MDA DS COI DMWG CMA MIEM High
AIS XML Formats
WHO, WHAT,
WHEN, WHERE
Gather Form
UCore
MDA DS COI
DMWG
CMA
MIEM
Spiral 1
High
Level Compatibility
Converge
Spiral 2
The Maritime Information Exchange Model (MIEM) is transitioning to become a domain of the NIEM
NIEM – UCore –
Small number of important, universally understandable concepts across a broad stakeholder base ().
MIEM – NIEM –
Fosters alignment with DOD, DHS and DoJ
Extensive governance support.
Provides constructs for representing vessels, cargo, facilities, and people
Business Case for Transition:
Existing governance
Existing configuration management
Existing tool support
Existing help desk support
Existing training support
Fosters alignment with DHS and DoJ
Grant-money tied to NIEM-adoption
USCG and CBP are major MDA players in DHS
MIEM 0.9
MIEM 1.0
NIEM-
Maritime
NIEM
Add
ANOA SILO
Spiral 3
Improve
Transition
Domain of 8

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.
The Coast Guard National Vessel Movement Center collects notices of arrival from vessels and publishes the data via the Ship Arrival Notification System (SANS).
Title 33 of the Code of Federal Regulations (CFR) establishes that all U.S. and foreign vessels 300 Gross Tons or more must file a NOA when bound for or departing U.S. ports or places; the 24 hour notification requirement change to 96 hours after 9/11
The greater notification time give analysts more time to evaluate threat potential
The data required in a NOA contains valuable information about a vessel, its cargo and its crew
Consumers such as port facilities, operations centers and intelligence organizations use the data to improve situational awareness
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

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.
Today
Single User
Manual
Resource 1
Add EACH
User
to List
Access List
Request Access
Administrator
Administrator
Resource 1 Owner
Administrator
Request
Access
Resource 2
Manual
Add EACH
User
Account
Domain
Resource 2 Owner
Administrator
Future
Users gain access seamlessly- no pre-registration, no delay …
Attribute Based Access Control enables:
Dynamic service and data discovery* and access
Unanticipated (but authorized) access to critical information
Resource owners can provide services and data to larger community
Dynamic, agile security posture (policy) change to meet mission tempo
For MDA:
How do you share the information that can be freely shared?
How do you restrict access to the parts of the information that have information sharing restrictions?
Millions of Users …
Policy
Resource 1
Policy
Resource 2
… while the services and data remain secure & protected!
Attributes

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
ANOA
without PII
ANOA
with PII
No ANOA
US-MDA User
US-MDA- Law Enforcement User
Foreign-MDA User

15. MDA DS COI Information Architecture
CMA
MASTER
GMMS
ISPAN
OGC Viz
SILO ONI
NCES Messaging Service
GCCS-M
GCCS-M
GCCS-M
GCCS-M
GCCS-M
SIPR RM RM RM RM RM
CDWSG
NIPR
FLT
AIS
Data
AIS
RCVR
AIS Junction
Box
ECDIS-N
SADI
ISNS
MASS C5F
MASS C2F
MASS C3F
MASS CPF
MASS SD
MDA PA
NAVAIR
Via RNOCs
DAS
ADS
AMN
SeaHawk
MIDAS
Neptune
NORTHCOM
AMRS
ONI
Afloat AIS
Volpe
NCES Messaging Service
MSSIS
NAIS
USCG
SCC-J
SMS
NWDC
IRRIS @
TRANSCOM
DRDC
Valcartier
MASTER
PANDA
JUMPS
On 218 Ships
MSSIS
Partner
Countries
ADS
USCG
OSC
DRDC
Atlantic
OLC2/TW
GMMS
TENCAP
RAGE
DSTL
Operational
GMMS
C4I
Suite
AIS
Radar
Imagery
ANOA
SILO
MSC
Anomalies
In Progress
Spiral 3 producers & consumers

16. What Have We Learned? Technical: Governance:
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.

17. What Have We Learned? Cultural: Implementation
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.
A core team is required to broker technical, governance, and cultural, and implementation issues.

18. Harvard Business Study
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 Education
John F. Kennedy School of Government, Harvard University
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.
MDA DS COI and its lessons learned will help shape the next generation of military and civilian leaders.

19. Impacting DoD Strategies and Policies
JROC : MDA DS COI used as an example on how to expose data and services to accelerate delivery of net-centric capabilities.
CJCSI E: MDA DS COI used as an example on how to expose data and services as part of Net-Ready Key Performance Parameter (KPP).
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.
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.
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.
DoD IM&IT Strategic Plan ( ): MDA DS COI is highlighted as a net-centric information sharing success story.

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.
Spiral 1: $.6M (Navy: $300K, USCG: $300K)
Spiral 2: $2.85M (Navy: $2M, USCG: $850K)
Spiral 3: $2.53M (Navy: 2M, USCG: $530K)
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.

21. Transition Status Transition Intent:
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
Data Mgmt WG
Pilot Tech WG
Policy 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.
A Recognized Net-Centric Success

24. Questions? Spiral 3 Demonstration: https://mda.spawar.navy.mil
Operational GMMS:
SILO Aggregator: