Presentation is loading. Please wait.

Presentation is loading. Please wait.

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

Similar presentations


Presentation on theme: "MDA Data Sharing COI Pilot Demonstration and Flag Review 17 October 2006."— Presentation transcript:

1

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

3 UNCLASSIFIED 2 Welcome Mr. Greg Spencer Executive Director, ONI

4 UNCLASSIFIED 3 MDA DS COI Executive Committee Co-Chair RDML Ronald Hewitt USCG CIO

5 UNCLASSIFIED 4 Environment Crises create unanticipated data needs… Look to recent events: –Katrina –Tsunami Relief –9/11 –USS Cole Current infrastructure is not responsive…

6 UNCLASSIFIED 5 Other Gov’t Organizations (OGA) DOD TSA ICE CBP Intel Community DHS Unanticipated Users Law Enforcement (LEA) Industry Non-Gov’t Agencies (NGA) NORAD NORTHCOM USCG …point-to-point data sharing… The Current Paradigm

7 UNCLASSIFIED 6 NSPD 41 / HSPD 13 National Strategy Maritime Security All Threats (Defense and Security) Global Maritime Intelligence Integration Maritime Operational Threat 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

8 UNCLASSIFIED 7 The MDA Challenge

9 UNCLASSIFIED 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 Understandable Data Sharing in a Net- Centric Department of Defense Visible Accessible Communities of Interest

10 UNCLASSIFIED 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) SOA NetCentricity InfoSharing CommunityOfInterest

11 UNCLASSIFIED 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

12 UNCLASSIFIED 11 MDA DS COI Steering Committee Co-Chair CAPT John Macaluso USCG R&D Program Manager

13 UNCLASSIFIED 12 MDA DS COI Governance

14 UNCLASSIFIED 13 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

15 UNCLASSIFIED 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 Stated in February 2006

16 UNCLASSIFIED 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 Stated in February 2006

17 UNCLASSIFIED 16 Trusted Interoperable Responsive Accessible Understandable Visible Is 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

18 UNCLASSIFIED 17 MDA DS COI Introduction Kickoff MDA COI Feb 06 WGs Stood up 4 Mar 06 Pilot Selected 31 Mar 06 Common Vocabulary Delivered 24 May 06 Pilot Demo Oct 06 1 st Anniversary 22 Feb 07 2 nd MDA Meeting 13 Jul 06 Pilot 3-way NCES “Discovery” Aug 06 Pilot 3-way NCES “Messaging” Sep 06 Pilot UDOP Selection Aug 06 Define Future Spirals Funding 5 Jul Oct OT&E

19 UNCLASSIFIED 18 MDA DS COI Data Management WG Co-Chair Mr. Mark Andress Senior Analyst, ONI-11

20 UNCLASSIFIED 19 Trusted Interoperable Responsive Accessible Understandable Visible Is 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

21 UNCLASSIFIED 20 So What? Community data models are the key enablers to information sharing and achieving a common understanding –Frees agencies from trying to achieve a unified model for collection, storage and characterization of their information within their own agency Community data models provide the framework for advanced fusion services –Pre and post fusion process enhancement Community security markings enable a trusted information sharing environment

22 UNCLASSIFIED 21 Vocabulary Based On… Needs of MDA DS COI stakeholders –And the existing schemas within the organizations of the stakeholders Initiatives interested in our activities International Maritime Organization (IMO) specification for Automatic Identification System (AIS) Objectives of the MDA DS COI pilot Future plans to accommodate data fusion and aggregation

23 UNCLASSIFIED 22 Develop UML Use-Case Auto Generate XSD - XML Vocabulary Handbook Vocabulary Development Process Determine Pilot Demonstration Class Relationship Diagram

24 UNCLASSIFIED 23 Vocabulary Design UML Use-Case

25 UNCLASSIFIED 24 MessageTemporal Object Conveyance Transponder Vessel AIS Transponder Time, Location, Vector, Heading, & Rate of Turn Collector AIS Specific Info Security Markings

26 UNCLASSIFIED 25 Vocabulary Design XML Schema Definition & XML Instances Heading is measured with respect to true north. Measured in degrees (0 <= heading < 360 )

27 UNCLASSIFIED 26 Vocabulary Design XML Schema Definition & XML Instances - T09:30:47.0Z T09:30:49.0Z - AMRS 54a T09:30:47.0Z https://www.notional-amrs.mil/MMSI/ Message Classification Markings Collector Conveyance Vessel Time, Location, Vector, Heading, & Rate of Turn Transponder AIS Transponder

28 UNCLASSIFIED 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

29 UNCLASSIFIED 28 Pilot Working Group Mr. John Shea Technical Director, PEO C4I – PMW 180

30 UNCLASSIFIED 29 Trusted Interoperable Responsive Accessible Understandable Visible Is 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

31 UNCLASSIFIED 30 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 Stated in February 2006

32 UNCLASSIFIED 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.

33 UNCLASSIFIED 32 MDA DS Pilot Implementation Plan 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.

34 UNCLASSIFIED 33 MDA DS Pilot Implementation Plan 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)

35 UNCLASSIFIED 34 MDA DS Pilot Implementation Plan 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 Visible Accessible Understandable DOD Directive Data Sharing in a Net-Centric Department of Defense

36 UNCLASSIFIED 35 High-Level Pilot Architecture COI MDA DS COI – Data Producers NAIS Aggregation NAIS AMRS ONI - AMRS Aggregation Navy Organic AIS Aggregation Infrastructure: NCES SOA Foundation DHS Consumers Data Sharing SOA Foundation HSIN Portal HSIN Identity Store (Portal Authentication) Defense Online Portal NCES Service Discovery NCES Security Service Navy Afloat Volpe DHS DOD DOD Consumers Content Discovery Volpe Aggregation NCES Federated Search and Messaging Services

37 UNCLASSIFIED 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 NMIC/ONI High-Level Pilot Architecture COI MDA DS COI – Data Producers NAIS Aggregation NAIS AMRS ONI - AMRS Aggregation Navy Organic AIS Aggregation Navy Afloat Volpe Aggregation

38 UNCLASSIFIED 37 USCG – Nationwide AIS –Coastal and river ways within CONUS, Alaska, Hawaii and Puerto Rico –Terrestrial receivers –Between antennas, at about sites reporting –~ 23.8 million “incoming” AIS messages reported per day –Aggregation USCG Operations System Center High-Level Pilot Architecture COI MDA DS COI – Data Producers NAIS Aggregation NAIS AMRS ONI - AMRS Aggregation Navy Organic AIS Aggregation Navy Afloat Volpe Aggregation

39 UNCLASSIFIED 38 Navy Organic AIS –Terrestrial NAVCENT –Shipboard: USS Reagan and USS Vela Gulf –~ 580,000 “incoming” AIS messages reported per day –Aggregation SPAWAR-SSC San Diego High-Level Pilot Architecture COI MDA DS COI – Data Producers NAIS Aggregation NAIS AMRS ONI - AMRS Aggregation Navy Organic AIS Aggregation Navy Afloat Volpe Aggregation

40 UNCLASSIFIED 39 DOT Volpe Center –Service contracts with various Customers, including NAVEUR/6 th Fleet and 2 nd Fleet –15 AIS Receiver Sites reporting –~ 432,000 “incoming” AIS messages reported per day –Aggregation Volpe (Cambridge, MA) High-Level Pilot Architecture COI MDA DS COI – Data Producers NAIS Aggregation NAIS AMRS ONI - AMRS Aggregation Navy Organic AIS Aggregation Navy Afloat Volpe Aggregation

41 UNCLASSIFIED 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 High-Level Pilot Architecture COI MDA DS COI – Data Producers NAIS Aggregation NAIS AMRS ONI - AMRS Aggregation Navy Organic AIS Aggregation Navy Afloat Volpe Aggregation

42 UNCLASSIFIED 41 MDA DS COI UDOP NCES Messaging Service FS Volpe USCG OSC ONI AMRS “Pilot” Channels A – NE USA B – SE USA C – MED West D – MED East E – West USA F – All G – AMRS MP FS MP FS MP FS MP Subscription Request Messages Received (in COI Vocab) Navy Organic A CDEFGB High-Level Pilot Architecture

43 UNCLASSIFIED 42 Demonstration

44 UNCLASSIFIED 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

45 UNCLASSIFIED 44 Switch To iMapData workstation

46 UNCLASSIFIED 45 Discovery Pilot Architecture FS COI Pilot – Notional Use Case # 1: DHS User Sequence Metadata Discovery - Federated Search (FS) MDA DS COI – Data Producers NAIS Contributors NAIS AMRS ONI - AMRS Contributors Infrastructure: NCES SOA Foundation DHS Consumers Data Sharing SOA Foundation HSIN Portal Fed Search WebPart HSIN Identity Store (Portal Authentication) Defense Online Portal NCES Service Discovery NCES Security Service 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 Fed Search Results Federated Search 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 Navy Afloat Volpe Aggregation Navy Organic AIS Aggregation Aggregated Search Results Returned in DDMS format Federated Search Aggregator

47 UNCLASSIFIED 46 AMRS High-Level Pilot Architecture COI Pilot – Notional Use Case # 2: Access Access of AIS Data, displayed in iMapDatga MDA DS COI Data Producers NAIS Aggregation ONI - AMRS Aggregation Infrastructure: Collaboration SOA Foundation HSIN Portal Pilot UDOP HSIN Identity Store (Portal Authentication) NCES Service Discovery NCES Security Service Content Delivery (AIS Data) NCES Messaging Service M DHS DOD NCES SOA Foundation DHS Consumers Interfaces: DOD Consumers Content Delivery Other UDOP MP Messaging Publisher MS Messaging Subscriber NAIS MP Navy Afloat Volpe MP AMRS 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 Navy Organic AIS Aggregation Volpe Aggregation iMapData UDOP Messaging Subscriber / Receiver iMapData Cache Translate COI Schema to iMapData schema Store Refresh Data from Cache

48 UNCLASSIFIED 47 High-Level Pilot Architecture 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 ONI - AMRS Aggregation Navy Organic AIS Aggregation Infrastructure: NCES SOA Foundation DHS Consumers Data Sharing SOA Foundation HSIN Portal HSIN Identity Store (Portal Authentication) Defense Online Portal NCES Service Discovery NCES Security Service Navy Afloat Volpe DHS DOD DOD Consumers Content Discovery DHS user logs into HSIN portal NCES SS authenticates HSIN portal & authorizes DHS user Volpe Aggregation

49 UNCLASSIFIED 48 Other Visualization Tools

50 UNCLASSIFIED 49 Trans View 32 (TV32) –Dave Phinney (Volpe Center) Google Earth –Jason DeShano (Pilot Technical Team - OSD/NII)

51 UNCLASSIFIED 50 Observations and Lessons Learned

52 UNCLASSIFIED 51 Observations and Lessons Learned 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

53 UNCLASSIFIED 52 Observations and Lessons Learned 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

54 UNCLASSIFIED 53 Observations and Lessons Learned Defining smaller increments with clear milestones is imperative –Days and weeks, not months and years –Identify high-value capabilities and show results early

55 UNCLASSIFIED 54 Observations and Lessons Learned 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

56 UNCLASSIFIED 55 Observations and Lessons Learned 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

57 UNCLASSIFIED 56 Observations and Lessons Learned 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

58 UNCLASSIFIED 57 Observations and Lessons Learned 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

59 UNCLASSIFIED 58 Observations and Lessons Learned Now is the time for Program of Records to start working their “NCES convergence” strategy –Start by making PoR data discoverable….

60 UNCLASSIFIED 59 Metrics

61 UNCLASSIFIED 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

62 UNCLASSIFIED 61 Federated Search Development Metrics

63 UNCLASSIFIED 62 Data Producer (Messaging) Development Metrics

64 UNCLASSIFIED 63 Data Consumer (UDOP) Development Metrics

65 UNCLASSIFIED 64 Acknowledgements

66 UNCLASSIFIED 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

67 UNCLASSIFIED 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

68 UNCLASSIFIED 67 Break Followed by a special presentation – “Navy C2 UNCLAS Possibilities”

69 UNCLASSIFIED 68 Navy C2 UNCLAS Possibilities Mr. Mike Spencer PEO C4I – PMW 150 Program Manager

70 UNCLASSIFIED 69 Agenda UNCLAS COP Discussion –Definition –Guidance Demonstration Beyond AIS Next Steps / Take Aways

71 UNCLASSIFIED 70 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”

72 UNCLASSIFIED 71 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

73 UNCLASSIFIED 72 OS Independent Track Plot TDA Weather TDA Overlay TDA Hardware Independent Solution Imagery TDA Mapping Chat/ Track Mgmt Weather What is C2 For UNCLAS COP Users?

74 UNCLASSIFIED 73 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

75 UNCLASSIFIED 74 Unclassified COP (UCOP) Demo & Possibilities leveraging MDA DS COI Pilot Architecture UCOP NCES Messaging Service Channel A Channel B Channel C Channel D Channel F Channel E Channel G AIS “Pilot” Channels A – NE USA B – SE USA C – MED West D – MED East E – West USA F – All G – AMRS Subscription Request Message (in COI Vocab) Received AIS Cameras Coastal 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)

76 UNCLASSIFIED 75 UNCLAS COP Demonstration Thin and Thick Client Demonstration –Access and Display AIS data via NORTHCOM MDA D/S COI Services

77 UNCLASSIFIED 76 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 ( nm) High Seas (200+ nm) Ports & WaterwaysCoastalEEZHigh Seas USN Primary Responsibility US Coast Guard Foreign Ports?

78 UNCLASSIFIED 77 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 UNCLAS User Foreign Embassies FUTURE Information Grid Sensor Grids C2 Execution Grids

79 UNCLASSIFIED 78 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”

80 UNCLASSIFIED 79 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

81 UNCLASSIFIED 80 Way Ahead – Discussions CAPT John Macaluso USCG R&D Program Manager

82 UNCLASSIFIED 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 Mitre, ONI) –Migrate from NCES SIL to DECC & harden capabilities –OT&E Phase (During CWID 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 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

83 UNCLASSIFIED 82 Closing Remarks RDML Ron Hewitt and Mr. Greg Spencer

84 UNCLASSIFIED 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

85 UNCLASSIFIED 84 Thank You...


Download ppt "MDA Data Sharing COI Pilot Demonstration and Flag Review 17 October 2006."

Similar presentations


Ads by Google