MDA Data Sharing COI Pilot Demonstration and Flag Review 17 October 2006

MDA Data Sharing COI PilotDemonstration and Flag Review

17 October 2006

2

UNCLASSIFIEDUNCLASSIFIED

Welcome

Mr. Greg SpencerExecutive Director, ONI

3


MDA DS COI Executive Committee

Co-Chair

RDML Ronald HewittUSCG CIO

4


Environment

• Crises create unanticipated data needs…

• Look to recent events:– Katrina– Tsunami Relief – 9/11– USS Cole

• Current infrastructure is not responsive…

5


Other Gov’tOrganizations

(OGA)

DOD

TSA

ICE

CBP

IntelCommunity

DHS

UnanticipatedUsers

LawEnforcement

(LEA)

Industry

Non-Gov’tAgencies

(NGA)

NORADNORTHCOM

USCG…point-to-point data sharing…

The Current Paradigm

6


NSPD 41 / HSPD 13

National StrategyMaritime Security

All Threats(Defense and Security)

Global Maritime Intelligence Integration

Maritime OperationalThreat Response

Maritime Infrastructure Recovery

Maritime Commerce Security

Maritime Transportation System

Security

Maritime Domain Awareness

Policy Action

Working Groups

Policy Action

Working Groups

Maritime Security Policy and MDA

“Requires Unity of Effort”

Domestic Outreach

International Outreach and Coordination

7


The MDA Challenge

8


• A collaborative group of people that must exchange information in pursuit of its shared goals, interests, missions, or business processes and therefore must have a shared vocabulary for the information it exchanges … DOD Directive 8320.2

Understandable

Data Sharing in a Net-Centric

Department of Defense

Vis

ible

Accessible

Communities of Interest

9


Methodology

• Establish an MDA information-sharing capability, employing net-centric applications and services, among the cadre of MDA stakeholders

• Focus on creating a data standard supporting the net-centric information sharing across the full spectrum of MDA stakeholders culminating in the visibility, accessibility, and understanding of data on a User Defined Operational Picture (UDOP)

SOASOA

NetNetCentricityCentricity InfoInfo

SharingSharing

CommunityCommunityOfOf

InterestInterest

10


Benefits :

• Scalable and adaptable to the community

• Flexible and agile decision-making and execution

• Efficient in cost, schedule, and performance

• Improves community partnerships

Today – The first step toward net-centric data sharing for the MDA community

Today’s Demonstration

11


MDA DS COI Steering Committee Co-Chair

CAPT John MacalusoUSCG R&D Program Manager

12


MDA DS COI Governance

MDA DS COISteering Committee

Joint Implementationand Services

Data Management

Pilot Demonstration

MDAImplementation Team

Req & CapesWorking Group

Battle SpaceAwareness

(Analysis & Fusion)Net-Centric


(ISR, Collection)

Maritime SecurityPolicy Coordinating

Committee

CONOPSWorking Group

NSC = HDHSC = JS/J5

DHS = USCGDOD = JS/J5

DHS = USCG DOD = NORTHCOM/J5 DOD = NORTHCOM/J6DHS = USCGDOD = Joint Staff/J5

DHS = USCG

DHS = TBD DOD = OPNAV N2

DHS = TBDDOD = ONI

DHS = TBDDOD = N71

DHS = USCG Lead PEO C4I Lead OPNAV N3/N5 Lead

• Develop Shared Vocabulary

• Develop Metadata

• Develop repeatable process/capabilityto demo COI products- Leverage NCES

Services- Execute as Risk

Reduction

• Facilitate Serviceimplementation

• Negotiate & ManageSLAs

• Maintain COI ServiceProduction Plan

• Define/implement COICapability Roadmap

• Synchronize COI Products

MDA DS COIExecutive

DOD = NORTHCOM/J6DHS = USCG

MDA DS COISteering Committee



Data Management

Data Management

Pilot Demonstration

Pilot Demonstration

MDAImplementation Team

Req & CapesWorking Group


(Analysis & Fusion)Net-Centric


(ISR, Collection)

Maritime SecurityPolicy Coordinating

Committee

CONOPSWorking Group

•

•

•

-Services

-

•

•

•

•

•

MDA DS COIExecutive

13


Data Management WG Charter

• Data Management WG Charter– To develop a repeatable process for developing and

registering a common vocabulary supporting the MDA DS COI, beginning with the schematic representation of Automatic Identification System (AIS) data as it pertains to the MDA Pilot objectives.

Stated in February 2006

14


Pilot WG Charter

• Pilot Charter– Develop a repeatable process/capability to demonstrate

MDA COI Services and products (using AIS data), by leveraging Net-Centric Enterprise Services (NCES) within a risk reduction pilot scheduled for Oct 2006.


15


Joint Implementation & Services Charter

• MDA DS COI Joint Implementation and Services Charter– Synchronize COI products with acquisition processes and

facilitate implementation across COI spirals: To develop a Services Roadmap, tied to requirements and

capabilities. Define scope (boundary) to Pilot and future Spirals Negotiate data exposure, Service Level Agreements and

incentives. Develop metrics Evaluate budget opportunities Research existing capabilities, services and programs Research restrictions


16


TrustedTrusted

InteroperableInteroperable

ResponsiveResponsive

AccessibleAccessible

UnderstandableUnderstandable

VisibleVisibleIs an information resource discoverable by most users?

Is it connected to the network(s), and are tools readily available to use it?

Can it be intelligibly used? Are the semantics well documented?

Can it be easily combined or compared with other information or mediated?

Is the source, accuracy and currency of the resource available to users?

Is the resource answering user needs? Are robust, direct user feedback mechanisms in place to guide development?

Net Centric Data Strategy Goals

17


MDA DS COI Introduction

KickoffMDA COI

21-22 Feb 06

WGsStood up4 Mar 06

Pilot Selected31 Mar 06

CommonVocabularyDelivered24 May 06

PilotDemoOct 06

1st Anniversary22 Feb 07

2nd MDAMeeting13 Jul 06

Pilot3-way NCES“Discovery”

Aug 06

Pilot3-way NCES“Messaging”

Sep 06

Pilot UDOPSelection

Aug 06

Define Future Spirals

Funding5 Jul 06

17 Oct

OT&E

18


MDA DS COIData Management WG

Co-Chair

Mr. Mark AndressSenior Analyst, ONI-11

19


TrustedTrusted












22


Develop UML Use-CaseAuto Generate XSD - XML

Vocabulary Handbook

Vocabulary Development Process

Determine Pilot Demonstration

Class Relationship Diagram

23


Vocabulary DesignUML Use-Case

24

UNCLASSIFIEDUNCLASSIFIEDMessage

Temporal Object

Conveyance

Transponder

Vessel

AIS Transponder

Time, Location,Vector, Heading,& Rate of Turn

Collector

AIS Specific Info

Security Markings

25


Vocabulary DesignXML Schema Definition & XML Instances

<xsd:element name="heading"> <xsd:annotation> <xsd:documentation>Heading is measured with

respect to true north. Measured in degrees (0 <= heading < 360 )

</xsd:documentation> </xsd:annotation> <xsd:simpleType> <xsd:restriction base="xsd:decimal"> <xsd:fractionDigits value="1"/> <xsd:maxExclusive value="360"/> <xsd:minInclusive value="0"/> </xsd:restriction> </xsd:simpleType></xsd:element>

26


Vocabulary DesignXML Schema Definition & XML Instances

<?xml version="1.0" encoding="UTF-8" ?>  -<dmwg:Message xmlns:dmwg="http://some-dod-dhs-namespace.mil/" xmlns:ism="urn:us:gov:ic:ism:v2" ism:releasableTo="USA" ism:classification="U" ism:ownerProducer="GBR" ism:disseminationControls="FOUO" releasableToDepartment="DHS"> <version>0.1</version> <timeOrigin>2001-12-17T09:30:47.0Z</timeOrigin> <timeReceipt>2001-12-17T09:30:49.0Z</timeReceipt> - <collector>

<DataSource>AMRS</DataSource> <reportStationID>54a2</reportStationID>

</collector>- <conveyance xsi:type="dmwg:Vessel">

- <time> <startTime>2001-12-17T09:30:47.0Z</startTime> <endTime>2001-12-17T09:30:47.0Z</endTime>

</time>- <location locationAttribute="isAtLocation">

<latitude>26.158</latitude> <longitude>80.1835</longitude> <s-minor>10</s-minor> <s-major>10</s-major> <orientation>0</orientation> <hae>3.1</hae> <haeRange>3.1</haeRange>

</location>- <vector>

<courseOverGround>270</courseOverGround> <speedOverGround>4.0</speedOverGround>

</vector>- <trueHeading>

<heading>182</heading> </trueHeading>- <rateOfTurn>

<rate>0.0</rate> </rateOfTurn> <UID>https://www.notional-amrs.mil/MMSI/304244000</UID> <mmsi>304244000</mmsi> - <transponder xsi:type="dmwg:AIS_Transponder">

- <signal> <SignalStrength>3</SignalStrength>

</signal> <navigationalStatus>0</navigationalStatus>

</transponder> </conveyance> </dmwg:Message>

Message

Classification MarkingsCollector

Conveyance

Vessel

Time, Location,Vector, Heading,& Rate of Turn

Transponder

AIS Transponder

27


Challenges/Lesson Learned

• Real projects/requirements need to drive schema development

• Requests for acceleration of the MDA schema in support of current requirements are coming in– RMAC JCTD– CMA/MASTER JCTDs– Other agency information gathering efforts

• Need to reconcile the work being done at DOJ’s NIEM model and ODNI’s office with the work being done within our COI

• COI’s schemas should remain focused on the COI subject and relate to the other COIs as needed (JTM example)

• Security is still not comprehensive enough

28


Pilot Working Group

Mr. John SheaTechnical Director, PEO C4I – PMW 180

29


TrustedTrusted












30


MDA DS COI Pilot Charter

• MDA DS COI Pilot Charter– Develop a repeatable process/capability to demonstrate

MDA COI Services and products (using AIS data), by leveraging Net-Centric Enterprise Services (NCES) within a risk reduction pilot scheduled for Oct 2006.


31


MDA DS Pilot Implementation Plan

• MDA DS COI Pilot Implementation Plan– Demonstrate a global UNCLAS MDA Data Sharing

net-centric capability based initially on multiple Automatic Identification System (AIS) data producers adopting a common (MDA Community) vocabulary and schema.

– Utilize the DHS Homeland Security Information Network (HSIN) and DOD Net-Centric Enterprise Services (NCES) Early Capability Baseline (ECB) to offer Data Producers and Consumers a single/common seamless methodology for exposing, discovering, publishing and subscribing to UNCLAS MDA data.

32



• MDA DS COI Pilot Implementation Plan– Initially identified three AIS Data Producers – now four:

Navy Shipboard Organic Coast Guard Operations System Center (R&D Center

Experimental Network – will become NAIS) NMIC/ONI – Automatic Maritime Reporting System (AMRS) DOT / Volpe Center – NAVEUR AIS data

– Business Proposition: Make your data discoverable, understandable and accessible by implementing the MDA Data Sharing Community Vocabulary, NCES Federated Search and Messaging Services, according to the current NCES Early Capabilities Baseline (ECB) standards.

33



• MDA DS COI Pilot Implementation Plan– Select a 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 on HSIN or NIPRnet TV32 on Shipboard ISNS GeoViz and WebCOP as an example of UNCLAS C2 COP

– Represented by the four workstations in front of you

– Implementation methods are reusable / sharable (located on the HSIN MDA Portal)

34



• The Pilot Implementation plan was expressed in two Demonstration Use Cases.

• The ability to:– Discover: Data made visible and understandable on the

GIG by AIS data producers

– Access: Data made accessible on the GIG by AIS data producers

Vis

ible

Accessible

Understandable

DOD Directive 8320.2Data

Sharing in a Net-Centric Department of Defense

35


High-Level Pilot Architecture

COIMDA DS COI – Data Producers

NAIS Aggregation

NAIS

AMRS

ONI - AMRS Aggregation

Navy Organic AIS

AggregationInfrastructure:

NCES SOA Foundation

DHS Consumers

Data SharingSOA Foundation

HSIN PortalHSIN

Identity Store(Portal Authentication)

Defense Online Portal

NCES Service Discovery

NCES Security Service

Navy Afloat

Volpe

DHS DOD

DOD Consumers

Content Discovery

VolpeAggregation

NCES Federated Search and Messaging Services

36


• ONI – Automatic Maritime Reporting System– Bilateral agreements to share AIS data

– Data is restricted due to the nature of the agreements

– ~ 25 sites reporting

– ~ 100,000 “incoming” AIS messages reported per day

– Aggregation site @ NMIC/ONI



NAIS Aggregation

NAIS

AMRS


Navy Organic AIS

Aggregation

Navy Afloat

Volpe

VolpeAggregation

37


• USCG – Nationwide AIS– Coastal and river ways within CONUS, Alaska, Hawaii and

Puerto Rico

– Terrestrial receivers

– Between 60-100 antennas, at about 45-50 sites reporting

– ~ 23.8 million “incoming” AIS messages reported per day

– Aggregation site @ USCG Operations System Center



NAIS Aggregation

NAIS

AMRS


Navy Organic AIS

Aggregation

Navy Afloat

Volpe

VolpeAggregation

38


• Navy Organic AIS– Terrestrial receiver @ NAVCENT

– Shipboard: USS Reagan and USS Vela Gulf


– Aggregation site @ SPAWAR-SSC San Diego



NAIS Aggregation

NAIS

AMRS


Navy Organic AIS

Aggregation

Navy Afloat

Volpe

VolpeAggregation

39


• DOT Volpe Center– Service contracts with various Customers, including

NAVEUR/6th Fleet and 2nd Fleet

– 15 AIS Receiver Sites reporting


– Aggregation site @ Volpe (Cambridge, MA)



NAIS Aggregation

NAIS

AMRS


Navy Organic AIS

Aggregation

Navy Afloat

Volpe

VolpeAggregation

40


• Global UNCLAS AIS Reporting Summary:~ 95 AIS Receiver Sites reporting

~ 25 million “incoming” AIS messages reported per day

• Number of AIS Messages being “published” through NCES Messages Services is unknown– Metrics will be developed within the next 30-days



NAIS Aggregation

NAIS

AMRS


Navy Organic AIS

Aggregation

Navy Afloat

Volpe

VolpeAggregation

41


MDA DS COI

UDOP

NCES Messaging Service

FSVolpe

USCG OSC

ONI AMRS

“Pilot” Channels

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

MP

FS

MP

FS

MP

FS

MP

Subscription Request Messages Received (in COI Vocab)

Navy Organic

A C D E F GB


42


Demonstration

43


Use Case Scenario

1. We are a HLS Consumer

2. We will log-on to HSIN

3. Access the HSIN MDA Portal

4. Perform a (NCES) Federated Search to “discover” AIS Providers

5. “Access” discovered AIS sources and view the data using our HSIN Enterprise viewer - iMapData

44


Switch To iMapData workstation

45


Discovery Pilot Architecture

FS

FSFS

FS

FS

COI

Pilot – Notional Use Case # 1: DHS User SequenceMetadata Discovery - Federated Search (FS)

MDA DS COI – Data Producers

NAIS Contributors

NAIS

AMRS

ONI - AMRS Contributors

Infrastructure:

NCES SOA Foundation

DHS Consumers


HSIN Portal

Fed Search WebPart

HSIN Identity Store

(Portal Authentication)




FS

Interfaces:

FS Federated Search Web Service

DHS DOD

Fed Search WebPart

DOD Consumers

Content Discovery

DHS user logs into HSIN portal

User initiates Fed Search query

NCES SS authenticates HSIN portal & authorizes DHS user

Federated Search Requests

1

2

3

4

5

Fed SearchResults

FederatedSearch

RESULTS

Federated Search Aggregator

Query FSA and Display Results (one of the metadata attributes in each AIS provider result contains the Messaging channels to which that provider is publishing)

FS

FS

Navy Afloat

Volpe

VolpeAggregation

Navy Organic AIS

Aggregation

Aggregated Search Results Returned in DDMS format

Federated Search Aggregator

46


AMRS


COI

Pilot – Notional Use Case # 2: AccessAccess of AIS Data, displayed in iMapDatga

MDA DS COI Data Producers

NAIS Aggregation


Infrastructure:

CollaborationSOA Foundation

HSIN Portal

Pilot UDOP

HSIN Identity Store

(Portal Authentication)NCES Service

Discovery


Content Delivery(AIS Data)

NCES Messaging ServiceM

DHS DOD

NCES SOA Foundation

DHS Consumers

Interfaces:

DOD Consumers

Content Delivery

Other UDOP

MP Messaging Publisher

MSMessaging Subscriber

NAIS MP

MP

Navy Afloat

VolpeMP

MP

AMRS

MS MS

M Messaging Service

NCES SS authenticates & authorizes MDA COI roles (MDARestrictedAccess,MDAFullAccess) of data providers and UDOPs

One or more UDOP(s) is initialized and subscribes to receive AIS data

When a data producer receives data externally, it is published to the Messaging service asynchronously

The data is delivered to subscribing UDOP(s) with access to data from that data producer

Users login to UDOP to view AIS vessel information

1

2 3

4

5

Navy Organic AIS

Aggregation

VolpeAggregation

iMapData UDOP

Messaging Subscriber / Receiver

iMapDataCache

iMapDataCache

Translate COI Schema toiMapData schema

Store

Refresh Data from Cache

47



COI

HSIN maintains their own Identity Store – acting as an Enterprise COI without any reference to DOD / NCES

MDA DS COI – Data Producers

NAIS Aggregation

NAIS

AMRS


Navy Organic AIS

AggregationInfrastructure:

NCES SOA Foundation

DHS Consumers


HSIN PortalHSIN

Identity Store(Portal Authentication)




Navy Afloat

Volpe

DHS DOD

DOD Consumers

Content Discovery

DHS user logs into HSIN portal

NCES SS authenticates HSIN portal & authorizes DHS user

VolpeAggregation

48


Other Visualization Tools

49


• Trans View 32 (TV32)– Dave Phinney (Volpe Center)

• Google Earth– Jason DeShano (Pilot Technical Team -

OSD/NII)

50


Observations and Lessons Learned

51



• Firewalls are uniquely restricted within many organizations– Custom rule sets exist across the enterprise – no

clear, single policy– Access is often blocked to standard web interfaces

(HTTP)– “Special requests” and processes are needed to

implement

52



• Developers can implement net-centric capabilities rapidly– Net-Centricity is not difficult and existing

resources have the right capabilities– Net-Centricity is an extension of existing system

development

53



• Defining smaller increments with clear milestones is imperative– Days and weeks, not months and years– Identify high-value capabilities and show results

early

54



• Key enabler is “full-service facilitation” – Education ~50%– Technical ~30%– Program Management ~20%

• Subject Matter Experts (SMEs) are key to jump-start an effort like this– Operator

Understanding of workflows and data

– NCES Customer Liaison Office

55



• Leverage Reuse (knowledge and work products)– NCES– Interface software– Work plans (project plans – implementation tasks)– Stagger development – as one team nears

completion, start another team

• Leverage lessons learned

• Pilot’s are agile endeavors – “be flexible”, but tightly focused on your objectives

56



• NCES is “pre-Milestone B”– We are early adopters, as defined in the NCES

Early Capability Baseline (ECB) program– NCES needs to grow and to be scaleable to

support the various DOD Enterprises– COI Pilots are key in helping NCES mature

57



• Pilot costs:– NORTHCOM $300k– DOD CIO $100k - $100k contract

2 x SMEs– PMW 180 $75K– USCG funded their costs– ONI funded their costs

$475K cash

$1.3m total

58



• Now is the time for Program of Records to start working their “NCES convergence” strategy– Start by making PoR data discoverable….

59


Metrics

60


Software Re-Use During the Pilot

• NCES Content Discovery and Messaging SDK• Federated Search Implementation, Messaging

Publishing Implementation, and Messaging Subscription and Receiving Implementation WSDL template

• Common Aggregation server and software for SPAWAR SSC and Volpe– XCOP Server (engine)

• Federated Search WebPart

As one provider finished coding, the next provider could reuse part or all of the code

61


Federated Search Development Metrics

62


Data Producer (Messaging) Development Metrics

63


Data Consumer (UDOP) Development Metrics

64


Acknowledgements

65


MDA DS COI Pilot Team

• USCG RDC & OSC– Jay Spalding, Steve Munson, Kathy Shea, Stan Kim, Bob DeYoung

• USN, PMW180 and SPAWAR-SSC San Diego– Bob Poor, Jeff Thomas, LT Dan Wang, Steve Shell, Chris Acantilado

• NMIC/ONI– Steve Milwicz, Terrell Singleton, CAPT Darren Sawyer

• DOT Volpe Center– Kam Chin, David Phinney, Brian Long, Henry Wychorski

• HLS/HSIN– Jim Meck, Mike Fischbein, Ed Frankenberg, Navid Keshavarz-Nia, Joel

Thomas, Mark Townsend

• Data Management WG– Mark Andress, CDR Matt Zamary, Brian Freeman, Eric Tollefson, Dave

Reading

66


MDA DS COI Pilot Team

• DISA – NCES– CDR Rex Cobb

• DOD CIO Contract Support– Jason DeShano, BAH (Technical Lead)– Adam White, Solers– Trey Rhiddlehoover, Solers– Mark Margolis (Solers, former member)– Mark Miller (BAH, former member)

• DOD CIO’s office– Michael Todd

67


BreakFollowed by a special

presentation – “Navy C2 UNCLAS Possibilities”

68

UNCLASSIFIED

Navy C2 UNCLAS Possibilities

Mr. Mike SpencerPEO C4I – PMW 150 Program Manager

69

UNCLASSIFIED

Agenda

• UNCLAS COP Discussion– Definition

– Guidance

• Demonstration• Beyond AIS• Next Steps / Take Aways

70

UNCLASSIFIED

• To provide a visualization of managed, unclassified, releasable information in support of operations in a Maritime environment.

• Need to validate/verify that what warfighters “really want” :

– Shared situational awareness across the lowest common denominator– Classification Level: Sensitive But UNCLAS (SBU)

– Easy to add/access new data sources

Unclassified COP “Requirement Statement”

71

UNCLASSIFIED

UNCLAS COP Guidance

• Spiral development approach– Initial Spiral 0 (deliver 30 NOV)

OPNAV N6F guidance provided June 2006 PEO C4I UNCLAS COP White Paper (June 2006) Develop Pilot and Demo to OPNAV, providing a vision

of the “Art of the Possible” Parallel Effort to seek Warfighter Requirements

– Who is Designated N3 Warfighter as UNCLAS COP Stakeholder

• PEO-C4I UNCLAS COP IPT Established– Comprised of PMW 150/180/160/05/SSC(242) – Meets weekly, Thurs 3pm PDT – PEO C4I UNCLAS COP Collaborative website for meeting

notes/briefs/data sharing HTTPS://ucop.spawar.navy.mil

72

UNCLASSIFIED

OS Independent

Tra

ck P

lot

TD

A

Wea

ther

TD

A

Ove

rlay

TD

A

Hardware Independent Solution

Imag

ery

TD

A

Mapping Chat/Email

Track Mgmt Weather

What is C2 For UNCLAS COP Users?

73

UNCLASSIFIED

UCOP Spiral 0 Definition

• “Pure” internet-based unclassified “COP”

• No “FOUO” NIPRNET-based “COP”

• No “Releasable” CENTRIXS-like “COP”

• Spiral 0 to determine the Art of the Possible– Will be used to support requirements definition

refinement

• Both a Thin Client and Thick Client Deliverable

74

UNCLASSIFIED

Unclassified COP (UCOP) Demo & Possibilities leveraging MDA DS COI Pilot Architecture

UCOP

NCES Messaging Service

ChannelA

ChannelB

ChannelC

ChannelD

ChannelF

ChannelE

ChannelG

AIS “Pilot” ChannelsA – NE USAB – SE USAC – MED WestD – MED EastE – West USAF – AllG – AMRS

Subscription Request

Message (in COI Vocab) Received

AIS

CamerasCoastal Radars

Patrol Boats

Airborne Radar

OTH Radars

Airborne Visual

Lloyds London registry, Lloyds Ship

service, World registry service, Janes

Weather, CNN news, IONIC (civil points of

interest)

75

UNCLASSIFIED

UNCLAS COP Demonstration

• Thin and Thick Client Demonstration– Access and Display AIS data via

NORTHCOM MDA D/S COI Services

76

UNCLASSIFIED

Beyond AIS- Allow non-AIS Track Injects from UNCLAS Users

0 nm 12 nm 24 nm 200 nm 2000 nm

Internal Waters Territorial Seas(0-12 nm)

Contiguous Zone(12-24 nm)

EEZ(12-200 nm)

High Seas(200+ nm)

Ports & Waterways Coastal EEZ High Seas

USN Primary Responsibility

US Coast Guard

Foreign Ports?

77

UNCLASSIFIED

Requirements for UNCLAS COP- More than AIS?

Significant challenges for data sharing:

• Fusion ashore

• C2 Collaboration CONOPS

• Retasking authority

• Critical to Avoid UNCLAS stove piped Feeds /Collaboration

• Lack of access leads to duplication

• Delays in dissemination limit engagement of time critical targets/Response

FAA Feeds

Space Sensors

Land C2

UAVs

Logistics Centers

Navy C2

Intelligence Centers

Other data (Overlays / PIM Tracks)

Coalition Centers

UNCLASUser

Foreign Embassies

FUTUREFUTURE

Information Grid

Sensor Grids

C2 Execution Grids

78

UNCLASSIFIED

Next Steps

• Validate C2 Requirements for UNCLAS COP – Once approved, a more detailed POA&M will be provided

along with Architecture– Are USN UNCLAS COP requirements different from

Coalition Partner UNCLAS COP MHQ/MOC drives requirements that are joint and COCOM specific

(e.g. will USN actively use/manage UCOP?) How will UNCLAS data feed into Classified C2 system(s) Coalition Users need to “Authenticate” to Security Services

– Managed by MHQ/MOC or Coalition Countries?

• Socialize the MDA DS COI Pilot process and architecture– How can other data types/sources be incorporated

“exposed/used”

79

UNCLASSIFIED

AIS / MDA / UNCLAS COP Take Aways

• Very quick convergence of MDA – AIS …– Center of Gravity shifting to Fleet Command Centers

– Implications for UNCLAS Data Sharing and C2 are still evolving

• MDA DS COI Pilot was the Initial Showcase …– First step in achieving MDA net-centric transformation.

– Other Communities of Interests are being formed that will leverage lessons learned: Strike COI, SIGINT COI (formally ISR)

• UNCLAS COP can leverage AIS and MDA efforts– Requirements (for Spirals) need to be defined

– Policy issues need to be addressed and resolved

80


Way Ahead– Discussions

CAPT John MacalusoUSCG R&D Program Manager

81


MDA DS COI Future

• Spiral 1 (Limited, UNCLAS AIS on NCES)– Pilot Phase: Publish 4 Sources of AIS (DoD, DHS, DOT)

Output: Tech Demonstration (12,17 Oct 2006 @ Mitre, ONI)– Migrate from NCES SIL to DECC & harden capabilities– OT&E Phase (During CWID 2007 @ NAVEUR, SeaHawk)

Output: CWID JITC Assessment (DoD), R&D Center Assessment (DHS)

• Spiral 2 (Worldwide, UNCLAS AIS on NCES)– Pilot Phase

Output: Tech Demonstration (COCOMs TBD)– OT&E Phase (During CWID 2008 @ DHS/COCOMs TBD)

Output: CWID JITC Assessment (DoD), R&D Center Assessment (DHS)

• Spiral 3 (Limited, Classified AIS on NCES)– Pilot and OT&E Details TBD

• Spiral 4 (Worldwide Classified AIS on NCES)– Pilot and OT&E Details TBD

82


Closing Remarks

RDML Ron Hewitt and

Mr. Greg Spencer

83


The Way Ahead

• Inter-Departmental Collaboration Using COI Model– Need a structure to support policy/process change

– Move from ad-hoc to formal organization to manage future MDA DS COI efforts

– Need new funding paradigm for a shared resource

– Need new transition mechanism PORs/POMs are neither scalable, adaptable, flexible, nor agile

– Net-Centric Data Model Need new C&A process Need new enterprise rules for data access and security

– Address governmental & coalition need to share

84


Thank You . . .

Documents

MDA Data Sharing COI Pilot Demonstration and Flag Review 17 October 2006