Download presentation
Presentation is loading. Please wait.
Published byGodfrey Gilbert Modified over 9 years ago
1
1 Department of Defense Stability Operations Community of Interest for: Unclassified Information Sharing in Stability Operations, Humanitarian Assistance and Disaster Relief Operations Office of the Assistant Secretary of Defense for Networks and Information Integration OASD(NII) and the DoD Chief Information Officer Mr Bill Barlow Deputy Director, Integrated Information Communications Technologies (ICT) Support (IIS) Directorate March 2009 UNCLASSIFIED
2
Schedule Introductions Introduction to the Department of Defense Chief Information Officer’s Stability Operations Community of Interest –Purpose –Organizational composition –Stability Operations COI Pilot Test –How you can help Working Group Wrap up / Closing Remarks 2
3
UNCLASSIFIED Purpose of the COI 3 Community of Interest: A collaborative group of users that must exchange information in pursuit of its shared goals, interests, missions, or business processes and therefore must have shared vocabulary for the information it exchanges. - DoD Directive 8320.02 Establish common understanding of data elements and make them discoverable and accessible across multiple domains, agencies and applications Enable members of the community to perform their respective missions more efficiently through the sharing of unclassified information amongst those in the community.
4
UNCLASSIFIED 4
5
Integrated ICT Support (IIS) Directorate Mission " The Integrated Information and Communication Technology (ICT) Support (IIS)Directorate provides policy, oversight and guidance for ICT elements for stability operations, humanitarian assistance and disaster relief efforts (HADR), building partnership capacity (BPC), and contingency operations with particular emphasis on unclassified information sharing as a key enabler for these missions. The IIS Directorate assists in identifying technologies that enable information exchange and communications support for rapid demonstration, experimentation, and fielding. IIS leads the ASD/NII and DoD CIO outreach for Stability operations." 5
6
UNCLASSIFIED The Problem Set 6
7
UNCLASSIFIED The Problem Set: Lessons learned and relearned Regarding support for May 2006 Indonesia Earthquake: “JFCOM will do whatever it takes to support current operations in this area. In the mid term, we need to figure out how to disseminate unclassified data with the same priority we do classified data - perhaps more given the complexity of the long war and our need to communicate with non-traditional actors. It is key to how we interact with other nations, OGAs, IOs, and NGOs at all levels of conflict. Let’s work together to fix this shortfall with policy, technology, and processes that support rather than present obstacles. “ General Lance Smith Commander, U.S. Joint Forces Command, 29 May 2006 Regarding 2004 Indian Ocean Earthquake and Tsunami lessons learned : Effective coordination, partnership and stewardship are necessary to reach all children affected by an emergency. UNICEF Humanitarian Action Report, 2008 Regarding the 2008 Georgian Crisis: Department of State and USAID identified info sharing improvement recommendations to Department of Defense: –Need easier access to Civ-Mil Coordination Doctrine, reference documents, and Guidelines –Use of common terminology, standards (data, humanitarian i.e. Sphere) and interoperable software –Synchronize inter-agency training and education in civil-military coordination, information/ knowledge management, and cross-cultural understanding –Knowledge map and humanitarian “social network” analysis to identify existing sources of information, and key USG, UN, NGO, donor and host government actors and their contact info Dept. of State Humanitarian Information Unit, August 2008 DoD Geographic combatant commands identify unclassified info sharing with coalition, interagency, international and non-governmental organizations as part of “top ten” priorities. FY2010-2015 Integrated Priority Listings 7
8
UNCLASSIFIED The Problem Set: Complex dynamics of interagency operations 8 IO IGO NGO UN Academia DoD CC/S/A SJFHQ/JTF USAID DCHA OFDA (AT, DART, RMT) OTI Region Bureaus DoS PRM S/CRS (HSRT and ACT) HIU Multi- National Military Multinational Interagency Host Nation Internet Information Sharing Environments
9
UNCLASSIFIED Sri Lanka 2004 Over 270 Groups active in Tsunami relief activities. 9
10
UNCLASSIFIED Stab Ops Unclassified Information Sharing Framework 10 STABILITY OPERATIONS Phase 0 (Shape) Phase 2 (Seize Initiative) Phase 5 (Enable Civil Authority) Phase 1 (Deter) “The ability to conduct seamless knowledge sharing among DoD elements, USG agencies, and multinational partners prior to, during, and after the completion of SSTR ops” is a critical capability of the Military Support to SSTR Ops Joint Operating Concept MIL SPT TO SSTR OPS Phase 3 (Dominate) Phase 4 (Stabilize) Secr Asst Prgm Mgmt (DSAMS, DSCA 1000,, DISAM) FMS (SCIP) IMET (DISAM, ISAN) SECURITY COOPERATION EDUCATION Jt/Svc Mil Ed & Trng Links to IMET Current Doctrine & Opnl Application INFORMATION SHARING SERVICES IO/NGO/PO Partner Capability BPC/Reconstruction (“Development Gateway”) Opnl Spt/Sit Awareness (iMMAP) STRATEGIC OPERATIONAL TACTICAL Unclas Info Sharing OPERATIONAL SUPPORT JFCOM (HarmonieWeb) PC (APAN, SharePoint, WebEOC, UCOP, Info Rsc Ctr) SC (WebEOC, intellink) N-NC (DSE, Chat, COP, Portal) CC (HarmonieWeb) EC (HarmonieWeb, NCE) Civil-Military & Academia Rgnl Intl Outreach (RIO) Rgnl ctrs w/ NPS and NDU Center for Complex Opns BPC & Development Outside of STAB OPS
11
UNCLASSIFIED Direction from the DoD CIO Form the COI Working Group Focus on Humanitarian assistance and disaster response –US Government Interagency willingness to support these events Develop a pilot to foster the information sharing Build on that success to include additional agencies and additional missions 11
12
UNCLASSIFIED COI Membership Not limited to but should include: International Organizations (IO): UNOCHA, WFP, UNDP NGOs Coalition/Multinational: NATO, ISAF, OIF Coalition, OEF Coalition US Government Interagency: USAID, DoS, DoD –DoS: S/CRS, HIU –USAID: OFDA –DoD: USD(P), Joint Staff, Services, OASD(NII), National Defense University, Civil Affairs, Geographic COCOMs Industry 12 Desired membership: All producers and consumers of information relative to this COI are welcome and encouraged to participate.
13
UNCLASSIFIED Strive to Establish a Common Understanding Obtain a common understanding of the problems Familiarity with the COI framework Harmonized view on way ahead across the community regarding: –Agreement on the beginning of a data model thru a vocabulary –Concepts for Web Services –Governance- structure fleshed out –Pilot program –Overall timeline 13
14
UNCLASSIFIED Framework DoD Directive 8320.02 – accessible, visible, understandable, trusted –Tag data and expose- move away from silos and bad data mining capabilities –Web enabled sources- move away from off-line applications; decouple data from applications –Shared vocabularies- move away from mediation techniques to enhance inherent interoperability Services: video, chat, email, wiki, blog, secure transactions, encryption, Real Simple Syndication, publish and subscribe Software: goal is to wind up with open source, open standard products that can be made universally available Pilot Program 14
15
UNCLASSIFIED 15 Pilot Program Limited Scope to prove concepts USAID Field Operations Guide outlines ten assessment types- the COI agreed to use 3 (to limit the scope and prove the concepts) –Food –Fuel –Water
16
UNCLASSIFIED COI Pilot POA&M 16 High-level Graphic with dependencies, decision points, and final demonstrated illustrated. Kickoff COI 1 OCT 08 Stand up WGs 3 DEC 08 Select Pilot Capabilities Plan Vocab Defined Interim Pilot Capability 1 st COI Anniversary Services Inventory 2d COI Steering Committee Meeting 3rd SC Meeting 4th SC Meeting O&M Plan Integrate Pilot into Ops Potential Agency Budget Inputs
17
UNCLASSIFIED COI Feedback 1.Imagery + Assessment Report most useful - Geospatially coordinated information is most desirable 2.Assessment reports based upon an agreed vocabulary 3.Common data model for the Community is a must 4.Information sharing capabilities must cross from 3G cell phones to PC and MAC computers 5.Goal is to make the information sharing process compliant with DoDD 8320.02: accessible, visible, discoverable, understandable, trusted by any COI member. Operations shall not be hampered or obstructed for want of information if it is available. 6.Logistics needs assessment should be the focus of the pilot program (Reduce scope to Food, Fuel, Water for purposes of the demonstration) 7.NGO involvement is problematic in the COI as there is no compelling reason for participation. 17
18
Division of Labor Governance (Proposed) WGs Additional Working Groups as needed Executive Board (FO/GO) Chair or Co-Chair 2 or 3 star level 1 star level Chair with 0-6/GS-15 membership Develop repeatable process to demonstrate COI products (e.g, COI vocabulary) Leverage core enterprise services Execute as risk reduction for next Pgm of Record (PoR) spiral Steering Committee Forum (Chair or Co-Chair) Joint Implementation Working Group (Appropriate Lead/Co-Lead) Define & implement high level COI capability roadmap and schedule milestones Stand up Pilot WG as needed Synchronize COI products with existing processes (e.g., JCIDS, Acquisition, PPBE) Mission Area & Domain Portfolio Managers Data Management Working Group (Appropriate Lead/Co-Lead) Develop shared vocabulary for a given problem area in accordance with the DoD Net- Centric Data Strategy Promote & review COI activities Resolve cross-COI discrepancies Ensure appropriate participation Act as primary COI POC Track milestones & success criteria Pilot Demonstration Working Group (Appropriate Lead/Co-Lead) May be collapsed
19
UNCLASSIFIED Next COI working group is 1 April 2009 Contacts: –Mr William (Bill) Barlow, Tel: +1(703) 601-2437; email: William.barlow@osd.mil William.barlow@osd.mil –Mr. Paul Chlebo, Tel: +1(703) 601-0564; email: paul.chlebo.ctr@osd.mil paul.chlebo.ctr@osd.mil –(Primary) Mr. Gerry Christman, Tel: +1(703) 697-8195; email: Gerard.christman.ctr@osd.mil Gerard.christman.ctr@osd.mil –(Alternate) Mr. Sean McCarthy, Tel: +1(703) 601-2438; email; sean.mccarthy.ctr@osd.mil sean.mccarthy.ctr@osd.mil 19 Next Steps
20
UNCLASSIFIED Back Up Slides 20
21
UNCLASSIFIED Strategic Policy DoD Directive 8320.02 Data Sharing in a Net-Centric Department of Defense; Certified Current as of April 23, 2007 4.1 Data is an essential enabler of network-centric warfare (NCW) and shall be made visible, accessible, and understandable to any potential user 4.2 Data assets shall be made visible by creating and associating metadata (“tagging”). All metadata shall be discoverable, searchable, and retrievable using DoD-wide capabilities. DoD Information Sharing Strategy, May 4, 2007 –Provide a common vision to synchronize information sharing initiatives and investments throughout the Department. DoD Information Sharing Implementation Plan, Focus Area 6; July 22, 2008 –The lack of a federated SSTR architecture hinders combatant commands and mission partners in efficiently and effectively sharing information in civil support and SSTR operations. 21
22
UNCLASSIFIED Strategic Policy DoD Directive 3000.05, Military Support for Stability, Security, Transition, and Reconstruction (SSTR) Operations (November 28 th, 2005) (under revision as a DoD Instruction 2009) 4.1: Stability Operations are a core U.S. military mission that the Department of Defense shall be prepared to conduct and support. They shall be given priority comparable to combat operations….. 4.3: Many stability operations tasks are best performed by indigenous, foreign, or U.S. civilian professionals. Nonetheless, U.S. military forces shall be prepared to perform all tasks necessary to establish or maintain order when civilians cannot do so. 4.12: Information shall be shared with U.S. Departments and Agencies, foreign governments and forces, International Organizations, NGOs, and members of the Private Sector supporting stability operations, consistent with legal requirements. DoD Directive 3000.07, Irregular Warfare (December 1 st, 2008) 4.a. Recognize that IW is as strategically important as traditional warfare. 4.b. Improve DoD proficiency for IW, which also enhances its conduct of stability operations. Stability operations are a core U.S. military mission that the Department of Defense shall be prepared to conduct …in accordance with DoD Directive 3000.05. 4.h. Synchronize appropriate DoD IW-related activities with the efforts of other U.S. Government agencies, foreign security partners, and selected international organizations by supporting: 4.h(2) Integrated civilian-military teams for steady-state and surge activities,….. 4.h (5) Efforts to enhance information sharing, as appropriate, to increase situational awareness of irregular challenges. 22
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.