1 / 33

Maritime Domain Awareness -- The Coast Guard C4ISR Challenges CAPT James Cash, USCG Chief, Office o

2. . . Standup GMSAAug 2007. Address Policy Issues that impact Information Sharing Increase Maritime Information Sharing: - Stakeholder Board; MDA Enterprise Architecture Hub - Info Sharing Hubs (Cargo, People, Vessels, Infrastructure) - Create collaborative global, maritime,

kieu
Download Presentation

Maritime Domain Awareness -- The Coast Guard C4ISR Challenges CAPT James Cash, USCG Chief, Office o

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


    1. 1 GOOD AFTERNOON, ADMIRALS, I’M SUSAN HENRY, ADMIRAL NIMMICH’S SENIOR MARITIME DOMAIN AWARENESS ARCHITECT. THIS IS MY OUT-BRIEF ON THE WORK OUR COLLECTIVE MATRIX TEAM HAS COMPLETED FOR YOU IN THE PAST SIX MONTHS OF THE C2 CONVERGENCE INITIATIVE. YOU SHOULD HAVE THESE SAME SLIDES IN YOUR FOLDERS. I WILL JUST GO OVER A FEW OF THEM, TO ALLOW TIME FOR QUESTIONS AND DISCUSSION. GOOD AFTERNOON, ADMIRALS, I’M SUSAN HENRY, ADMIRAL NIMMICH’S SENIOR MARITIME DOMAIN AWARENESS ARCHITECT. THIS IS MY OUT-BRIEF ON THE WORK OUR COLLECTIVE MATRIX TEAM HAS COMPLETED FOR YOU IN THE PAST SIX MONTHS OF THE C2 CONVERGENCE INITIATIVE. YOU SHOULD HAVE THESE SAME SLIDES IN YOUR FOLDERS. I WILL JUST GO OVER A FEW OF THEM, TO ALLOW TIME FOR QUESTIONS AND DISCUSSION.

    2. 2 The signing of NSPD-41/HSPD-13 & the National Strategy for Maritime Security was a seminal event. We are a maritime nation yet we never had a National Strategy for Maritime Security until 2005! The Strategy is an impressive achievement in that it recognizes the full range of 21st Century threats & challenges that the maritime domain presents to the security of the U.S & our friends & allies. As a post 9/11 strategy document, terrorism & the proliferation of WMD rise to the top as the highest priorities, but it recognizes transnational crime writ large, the facilitation of commerce & the protection of the living & non-living resources that our economies depend. The National Strategy has 8 supporting plans, intended to be implemented as a integrated set to breath life into the Strategy. I am responsible for implementing the GMII Plan; Admiral Metcalf is responsible for implementing the MDA CONOPS – a derivative of the MDA Plan. The GMII Plan & the MDA Plan/MDA CONOPS are intended to complement one another. Taken together as a matched set, they work to implement the National Strategy by (1) facilitating commerce & (2) denying the maritime domain to bad actors & their illicit cargoes, & (3) how? - by making the maritime domain more transparent. More specifically, the intent of the GMII Plan is put better information in the hands of analysts so they can better inform decision makers – be they policy makers, military commanders, law enforcement officers, diplomats, etc. - so they can make better informed, more timely decisions to deter, prevent or respond to threats to the U.S. & our friends & allies. [I may move this to my talking points for Slide 4; need to think some more about the flow.] Lee – The National Strategy for Maritime Security directs that steps be taken to enhance what might be referred to as the FOUR PILLARS: Certainly Maritime Security, but also Maritime Safety, Maritime Environmental Protection and Maritime Commerce: Security, Safety, Environment and Commerce. Our goal is to address National Policy, and to some extent Processes, which I will elaborate further in a minute, that are barriers for the sharing of information that will enhance all four of these Pillars. It is in our areas of emphasis across these four Pillars that we start to draw some of the distinctions, or differing areas of focus, between our two organizations. Next Slide. The signing of NSPD-41/HSPD-13 & the National Strategy for Maritime Security was a seminal event. We are a maritime nation yet we never had a National Strategy for Maritime Security until 2005! The Strategy is an impressive achievement in that it recognizes the full range of 21st Century threats & challenges that the maritime domain presents to the security of the U.S & our friends & allies. As a post 9/11 strategy document, terrorism & the proliferation of WMD rise to the top as the highest priorities, but it recognizes transnational crime writ large, the facilitation of commerce & the protection of the living & non-living resources that our economies depend. The National Strategy has 8 supporting plans, intended to be implemented as a integrated set to breath life into the Strategy. I am responsible for implementing the GMII Plan; Admiral Metcalf is responsible for implementing the MDA CONOPS – a derivative of the MDA Plan. The GMII Plan & the MDA Plan/MDA CONOPS are intended to complement one another. Taken together as a matched set, they work to implement the National Strategy by (1) facilitating commerce & (2) denying the maritime domain to bad actors & their illicit cargoes, & (3) how? - by making the maritime domain more transparent. More specifically, the intent of the GMII Plan is put better information in the hands of analysts so they can better inform decision makers – be they policy makers, military commanders, law enforcement officers, diplomats, etc. - so they can make better informed, more timely decisions to deter, prevent or respond to threats to the U.S. & our friends & allies. [I may move this to my talking points for Slide 4; need to think some more about the flow.] Lee – The National Strategy for Maritime Security directs that steps be taken to enhance what might be referred to as the FOUR PILLARS: Certainly Maritime Security, but also Maritime Safety, Maritime Environmental Protection and Maritime Commerce: Security, Safety, Environment and Commerce. Our goal is to address National Policy, and to some extent Processes, which I will elaborate further in a minute, that are barriers for the sharing of information that will enhance all four of these Pillars. It is in our areas of emphasis across these four Pillars that we start to draw some of the distinctions, or differing areas of focus, between our two organizations. Next Slide.

    3. 3 Federal MDA Context Collaborate with other department Executive Agents for interaction with MDA Stakeholders Board SECNAV is DoD Executive Agent CG happy to assist TRANSCOM Collaborate with other department Executive Agents for interaction with MDA Stakeholders Board SECNAV is DoD Executive Agent CG happy to assist TRANSCOM

    4. 4

    5. 5 CG C4ISR Challenges See, Understand and Share Information with all port partners to provide consistent Maritime Security Nationwide. Deploy Sensors Leverage Intel Community Capability Fuse Data MDA “Information Hubs” a Model for Information Sharing in a Net Centric Environment

    6. 6 Complex MDA Security Challenge

    7. 7

    8. 8 LRIT Concept Used with permission of Inmarsat This is the LRIT concept. Originally, LRIT was based solely on Inmarsat-C GMDSS sending automated reports to a central LRIT Data Management Centre. It is not quite that way anymore, but conceptually, LRIT still is ships reporting through mandated equipment to the LRIT system for access by contracting governments. This is the LRIT concept. Originally, LRIT was based solely on Inmarsat-C GMDSS sending automated reports to a central LRIT Data Management Centre. It is not quite that way anymore, but conceptually, LRIT still is ships reporting through mandated equipment to the LRIT system for access by contracting governments.

    9. 9 LRIT Coverage Flag States - All flag ships worldwide. Port States - All ships indicating an intention to enter a port facility, at a distance or time set by the Port State, but not in internal waters of another contracting government. Coastal States - All ships, regardless of flag, within a distance of 1000 nautical miles of the coast, but not in internal waters of another contracting government, nor in the territorial sea of the contracting government whose flag the ship is entitled to fly. Here are the limits of what you are entitled to as a contracting government. As a Flag, you can track your ships anywhere. As a port state, once a ship has indicated its intention to enter your port, you can gain access (but not in the internal waters of another contracting government.) Finally, as a coastal state, you have access to LRIT information up to 1000 nm off your coast – yes, that means ships on innocent passage or on the high seas - but not in the internal waters of another, and not in the territorial sea of the flag state.Here are the limits of what you are entitled to as a contracting government. As a Flag, you can track your ships anywhere. As a port state, once a ship has indicated its intention to enter your port, you can gain access (but not in the internal waters of another contracting government.) Finally, as a coastal state, you have access to LRIT information up to 1000 nm off your coast – yes, that means ships on innocent passage or on the high seas - but not in the internal waters of another, and not in the territorial sea of the flag state.

    10. 10

    11. 11 I-1 expands the current limited capability to other critical ports that have very little to no MDA capability. This leaves these ports very vulnerable and without the basic vessel tracking and identification capability. I-1 will facility CG asset tracking as CG vessels are out-fitted with AIS capabilities. I-1 will pass the CG asset’s position reports to the CG COP for display. This will include the encrypted messaging. I-1 will look to re-use ALL Govt infrastructure to include R-21 sites where available.I-1 expands the current limited capability to other critical ports that have very little to no MDA capability. This leaves these ports very vulnerable and without the basic vessel tracking and identification capability. I-1 will facility CG asset tracking as CG vessels are out-fitted with AIS capabilities. I-1 will pass the CG asset’s position reports to the CG COP for display. This will include the encrypted messaging. I-1 will look to re-use ALL Govt infrastructure to include R-21 sites where available.

    12. 12

    13. 13

    14. 14

    15. 15 AIS from Space 6 AIS-enabled satellites launched 6/08 1 CG Concept Demo satellite 5 “quick launch” ORBCOMM birds 1 “quick launch” ground spare ORBCOMM made business decision to develop & implement AIS capability on additional comm’l satellites “Next Generation” ORBCOMM satellites AIS capability included in requirements Up to 25 AIS enabled satellites expected by end of 2011 NAIS Procuring Data as a Service, not satellites.

    16. 16

    17. 17 Briefing length = Welcome questions throughout I’m the Sponsor Rep CDR Ken Marien is the Project Mgr Briefing length = Welcome questions throughout I’m the Sponsor Rep CDR Ken Marien is the Project Mgr

    18. WatchKeeper Installations Here is the five year deployment schedule…note that we estimate, based on the visualization tools pilot, it will take 18 months to develop, deploy and customize the application. Based on the current CIP we will start 6-8 SCCs per year.Here is the five year deployment schedule…note that we estimate, based on the visualization tools pilot, it will take 18 months to develop, deploy and customize the application. Based on the current CIP we will start 6-8 SCCs per year.

    19. 19 MNS as originally drafted, and only recently revalidated, showed SCCs lack: Situational awareness – basically the eyes & ears on the water … of vessels, activities, events IT Systems to link information. We don’t have an information shortage MISLE, AIS, SANS, etc… all pumping out valuable info We don’t have the solution to pull all the info together such that watch standers can turn this information into action. Facilities to coordinate joint ops planning, mission coordination w/ port partnersMNS as originally drafted, and only recently revalidated, showed SCCs lack: Situational awareness – basically the eyes & ears on the water … of vessels, activities, events IT Systems to link information. We don’t have an information shortage MISLE, AIS, SANS, etc… all pumping out valuable info We don’t have the solution to pull all the info together such that watch standers can turn this information into action. Facilities to coordinate joint ops planning, mission coordination w/ port partners

    20. 20 This IOC / C21 Project gets us that new capability – in 3 parts Information Management Tools – called WatchKeeper Push & Pull Info w/ port partners Better understand anything/everything happening in operating environ Business rules for anomoly detection So when that contact passes that “do not cross” line in the water – the watch is immediately notified Facility upgrades & expansions For port partner watch standers Surge Operations Daily Operations coordination Sensor Network – cameras & radars (both ours & port partner owned) To monitor ops thruout Response to query about Safe Port Act Mandates: IOC Characteristics: Composition and operational characteristics of existing Command Centers: Miami, HR, Charleston, SD & virtual OpCen in new York Fit the needs of individual port areas Provide for participation by CBP, ICE, TSA, DOJ, DOD, fed, state & local agencies, AMSCs Support AMSPs, intel activities, ifro sharing, vessel tracking, FMSC Security Incidents Cmd Post This IOC / C21 Project gets us that new capability – in 3 parts Information Management Tools – called WatchKeeper Push & Pull Info w/ port partners Better understand anything/everything happening in operating environ Business rules for anomoly detection So when that contact passes that “do not cross” line in the water – the watch is immediately notified Facility upgrades & expansions For port partner watch standers Surge Operations Daily Operations coordination Sensor Network – cameras & radars (both ours & port partner owned) To monitor ops thruout Response to query about Safe Port Act Mandates: IOC Characteristics: Composition and operational characteristics of existing Command Centers: Miami, HR, Charleston, SD & virtual OpCen in new York Fit the needs of individual port areas Provide for participation by CBP, ICE, TSA, DOJ, DOD, fed, state & local agencies, AMSCs Support AMSPs, intel activities, ifro sharing, vessel tracking, FMSC Security Incidents Cmd Post

    21. 21

    22. 22 This IOC / C21 Project gets us that new capability – in 3 parts Information Management Tools – called WatchKeeper Push & Pull Info w/ port partners Better understand anything/everything happening in operating environ Business rules for anomoly detection So when that contact passes that “do not cross” line in the water – the watch is immediately notified Facility upgrades & expansions For port partner watch standers Surge Operations Daily Operations coordination Sensor Network – cameras & radars (both ours & port partner owned) To monitor ops thruout Response to query about Safe Port Act Mandates: IOC Characteristics: Composition and operational characteristics of existing Command Centers: Miami, HR, Charleston, SD & virtual OpCen in new York Fit the needs of individual port areas Provide for participation by CBP, ICE, TSA, DOJ, DOD, fed, state & local agencies, AMSCs Support AMSPs, intel activities, ifro sharing, vessel tracking, FMSC Security Incidents Cmd Post This IOC / C21 Project gets us that new capability – in 3 parts Information Management Tools – called WatchKeeper Push & Pull Info w/ port partners Better understand anything/everything happening in operating environ Business rules for anomoly detection So when that contact passes that “do not cross” line in the water – the watch is immediately notified Facility upgrades & expansions For port partner watch standers Surge Operations Daily Operations coordination Sensor Network – cameras & radars (both ours & port partner owned) To monitor ops thruout Response to query about Safe Port Act Mandates: IOC Characteristics: Composition and operational characteristics of existing Command Centers: Miami, HR, Charleston, SD & virtual OpCen in new York Fit the needs of individual port areas Provide for participation by CBP, ICE, TSA, DOJ, DOD, fed, state & local agencies, AMSCs Support AMSPs, intel activities, ifro sharing, vessel tracking, FMSC Security Incidents Cmd Post

    23. 23

    24. 24 CONVERGENCE TASKS (G-CCS Memo) 1. Draft Flag digest, provide status briefing to G-CCS on Flag Memo on C2 & COP Systems Convergence. Who: CG-7M + CG-6 When: Jan 2. Develop enterprise work plan, roles and teams with CG-6d and core staff. Who: CG-7M + CG-6 When: Jan – after Dec CG-6 reorg off-site (2 months’ delayed from original plan) 3. Develop Convergence plan, architectural goals and approach. Who: CG-6d, CG-7M2, G-OCC staff and stakeholders When: Jan (2 months’ delayed from original plan) 4. Review available Federal COP and related MDA C4ISR requirements & architecture products, and provide relevant GFI to Acquisitions via Sponsors. Who: CG-7M lead review; C2 Convergence Team + support contractors When: Jan (not yet begun; will have to do it fast) Develop Draft SOO, attach supporting reference documents and deliver to Acquisitions. Who: C2 Convergence Team (including G-A & G-D) + support contractors When: Feb (NAIS), Mar (Deepwater & C2010) 6. Develop Convergence plan for C2 systems, draft COMDTINST. Who: C2 Convergence Team with G-A & G-D + support contractors When: Jun 06 (informal concurrence), Aug 06 (Concurrent Clearance). CONVERGENCE TASKS (G-CCS Memo) 1. Draft Flag digest, provide status briefing to G-CCS on Flag Memo on C2 & COP Systems Convergence. Who: CG-7M + CG-6 When: Jan 2. Develop enterprise work plan, roles and teams with CG-6d and core staff. Who: CG-7M + CG-6 When: Jan – after Dec CG-6 reorg off-site (2 months’ delayed from original plan) 3. Develop Convergence plan, architectural goals and approach. Who: CG-6d, CG-7M2, G-OCC staff and stakeholders When: Jan (2 months’ delayed from original plan) 4. Review available Federal COP and related MDA C4ISR requirements & architecture products, and provide relevant GFI to Acquisitions via Sponsors. Who: CG-7M lead review; C2 Convergence Team + support contractors When: Jan (not yet begun; will have to do it fast) Develop Draft SOO, attach supporting reference documents and deliver to Acquisitions. Who: C2 Convergence Team (including G-A & G-D) + support contractors When: Feb (NAIS), Mar (Deepwater & C2010) 6. Develop Convergence plan for C2 systems, draft COMDTINST. Who: C2 Convergence Team with G-A & G-D + support contractors When: Jun 06 (informal concurrence), Aug 06 (Concurrent Clearance).

    25. 25 MDA Governance Coordinate with Air and Land Executive Agents for MDA DOD Coast Guard DOT Northcom – “Executive Agent for “ADA” CBP – “Executive Agent” “LDA” “Civil ADA”

    26. 26 MDA Governance Coordinate with Air and Land Air: National Capital Region Enhanced Regional Situational Awareness Land: SBINET Maritime: DOD – MDA Spiral 1, Non Class Enclave DHS - CG – IOC/C21 Watchkeeper, CG Homeport’s Alert and Warning System. DOT - Marview CBP – SBINET–Northern Border

    27. 27 CG C4ISR Challenges See, Understand and Share Information with all port partners to provide consistent Maritime Security Nationwide. Deploy Sensors Leverage Intel Community Capability Fuse Data MDA “Information Hubs” a Model for Information Sharing in a Net Centric Environment

    28. 28 Federal MDA Governance ..

    29. 29 CONVERGENCE TASKS (G-CCS Memo) 1. Draft Flag digest, provide status briefing to G-CCS on Flag Memo on C2 & COP Systems Convergence. Who: CG-7M + CG-6 When: Jan 2. Develop enterprise work plan, roles and teams with CG-6d and core staff. Who: CG-7M + CG-6 When: Jan – after Dec CG-6 reorg off-site (2 months’ delayed from original plan) 3. Develop Convergence plan, architectural goals and approach. Who: CG-6d, CG-7M2, G-OCC staff and stakeholders When: Jan (2 months’ delayed from original plan) 4. Review available Federal COP and related MDA C4ISR requirements & architecture products, and provide relevant GFI to Acquisitions via Sponsors. Who: CG-7M lead review; C2 Convergence Team + support contractors When: Jan (not yet begun; will have to do it fast) Develop Draft SOO, attach supporting reference documents and deliver to Acquisitions. Who: C2 Convergence Team (including G-A & G-D) + support contractors When: Feb (NAIS), Mar (Deepwater & C2010) 6. Develop Convergence plan for C2 systems, draft COMDTINST. Who: C2 Convergence Team with G-A & G-D + support contractors When: Jun 06 (informal concurrence), Aug 06 (Concurrent Clearance). CONVERGENCE TASKS (G-CCS Memo) 1. Draft Flag digest, provide status briefing to G-CCS on Flag Memo on C2 & COP Systems Convergence. Who: CG-7M + CG-6 When: Jan 2. Develop enterprise work plan, roles and teams with CG-6d and core staff. Who: CG-7M + CG-6 When: Jan – after Dec CG-6 reorg off-site (2 months’ delayed from original plan) 3. Develop Convergence plan, architectural goals and approach. Who: CG-6d, CG-7M2, G-OCC staff and stakeholders When: Jan (2 months’ delayed from original plan) 4. Review available Federal COP and related MDA C4ISR requirements & architecture products, and provide relevant GFI to Acquisitions via Sponsors. Who: CG-7M lead review; C2 Convergence Team + support contractors When: Jan (not yet begun; will have to do it fast) Develop Draft SOO, attach supporting reference documents and deliver to Acquisitions. Who: C2 Convergence Team (including G-A & G-D) + support contractors When: Feb (NAIS), Mar (Deepwater & C2010) 6. Develop Convergence plan for C2 systems, draft COMDTINST. Who: C2 Convergence Team with G-A & G-D + support contractors When: Jun 06 (informal concurrence), Aug 06 (Concurrent Clearance).

    30. 30 Federal MDA Executive Agents -- DoD, DHS & DOT Coordinate & integrate federal policies, plans,& programs associated with MDA related activities: Ensure effective interagency MDA planning & execution Identify MDA requirements & necessary resources Act as principle Dept reps at interagency MDA policy forums Assess & evaluate federal MDA performance & report results Establish & maintain MDA EA business records In coordination with other MDA EAs, recommend perspective Directors of GMSA & GMAII when necessary Liaise with other federal MDA EAs

    31. 31

    32. 32

    33. 33

More Related