Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

2005 02 14 C2 I S R C O I Brief A K Maitra


Published on

  • Be the first to comment

  • Be the first to like this

2005 02 14 C2 I S R C O I Brief A K Maitra

  1. 1. Transforming the Way the AF Manages Data Net Centric Data Strategy using Communities of Interest Amit K. Maitra 540-270-5694 SAF/XCXA February 14, 200
  2. 2. <ul><li>The Air Force Strategy </li></ul><ul><li>To move from privately owned and stored data in disparate networks and within legacy systems/applications to an enterprise information environment where authorized known and authorized unanticipated users can access any information and can post their contributions for enterprise-wide access. </li></ul>Enabling Net-Centricity  Data Strategy <ul><li>To Consumer-centric: </li></ul><ul><li>Data is visible, accessible and understandable </li></ul><ul><li>Shared data – supports planned and unplanned consumers </li></ul><ul><li>Shared meaning of the data enables understanding </li></ul>Ubiquitous Global Network Metadata Catalogs Enterprise & Community Services Application Services (e.g., Web) Shared Data Space Metadata Registries Security Services (e.g., PKI, SAML) Producer Developer <ul><li>From Producer-centric: </li></ul><ul><li>Multiple calls to find data </li></ul><ul><li>Private data – only supports planned consumers </li></ul><ul><li>Data translation needed for understanding when pulled from multiple sources </li></ul>Consumer Producer and Developer System 1 Data System 2 Data System N Data Consumer . . .
  3. 3. Barriers to Identifying, Accessing and Understanding Data Defining The Data Problem B A R R I E R B A R R I E R B A R R I E R B A R R I E R “ What data exists?“ “ How do I access the data?” “ How do I know this data is what I need?” “ How can I tell someone what data I need?” “ How do I share my data with others?” “ How do I describe my data so others can understand it?” Organization “A” Organization “B” Organization “C” User is unaware this data exists User knows this data exists but cannot access it because of organizational and/or technical barriers ? User knows data exists and can access it but may not know how to make use of it due to lack of under- standing of what data represents Data Strategy Approach: Discovery Metadata Data Strategy Approach: Web Enabling, Web-service Enabling Data Strategy Approach: Communities of Interest, Metadata Registry End-User Consumer End-User Producer
  4. 4. Publishing and Subscribing of Data & Services Supporting Both Known and Unanticipated Authorized Users DoD Discovery Catalogs DoD Metadata Registry DoD Service Registry “ Shared Space” Unanticipated Authorized User of System A Data Query Catalogs and Registry System X “ Pull” Structural and Semantic Metadata “ Pull” Data Publish Structural and Semantic Metadata Publish Data and Services Publish Discovery Metadata System B Data exchanged across engineered, well-defined interfaces Known User of System A Data System A All Data Assets are Tagged with DoD Discovery Metadata Specification (DDMS) Metadata Leverages Service Oriented Architecture Data Producer Data Consumer
  5. 5. Data Sharing Responsibilities Air Force sees this as an AF transformational priority ! Air Force Information & Data management Strategy Policy, May 2004 DoD 8320.2 Directive, Data Sharing in a Net Centric Department of Defense DoD 8320.2 Directive codifies DoD Net-Centric Data Strategy (DoD CIO) Data Strategy Implementation Guide is under development (DoD CIO) <ul><li>Develop vocabularies, taxonomies for data exchange </li></ul><ul><li>Register these agreements in federated DoD metadata Registry </li></ul><ul><li>Direct development of federated metadata registry for semantic and structural metadata </li></ul>Make data understandable Structural & Semantic Data Descriptions <ul><li>Implement access services </li></ul><ul><li>Register access services in federated service registry </li></ul><ul><li>Maintain repository of acceptable commercial standards for web-based services </li></ul><ul><li>Direct development of federated service registry for web-services </li></ul>Make data accessible Sharing Data <ul><li>Tag data holdings with DDMS </li></ul><ul><li>Extend for COI specific search criteria </li></ul><ul><li>Develop, maintain DoD Discovery Metadata Specification (DDMS) to facilitate DoD-wide search </li></ul><ul><li>Direct development of Enterprise search capability </li></ul>Make data visible Contextual Data Scope of COI Role Scope of Enterprise Role Key Goal of DoD Directive 8320.2
  6. 6. Community of Interest (COI) Approach <ul><li>Define data sharing shortfall as a problem statement </li></ul><ul><li>Define COI-specific vocabularies and taxonomies </li></ul><ul><ul><li>Vocabularies to improve data exchange within COI and among COIs </li></ul></ul><ul><ul><li>Taxonomies to improve precision discovery </li></ul></ul><ul><li>Make their data assets visible and accessible </li></ul><ul><ul><li>Visible via service registry (WSDL), metadata registry (XSD), and data catalogs (DDMS) </li></ul></ul><ul><ul><li>Accessible via web services and common mime types </li></ul></ul><ul><li>Register semantic and structural metadata to the DoD Metadata Registry ( ) </li></ul><ul><ul><li>XML Gallery for XML schemas, stylesheets, domain sets, samples </li></ul></ul><ul><ul><li>Taxonomy Gallery for discovery taxonomies (OWL syntax) </li></ul></ul><ul><li>Pilots, Exercises, Integration with Programs of Record </li></ul><ul><ul><li>Data asset discovery and understanding </li></ul></ul><ul><ul><li>Data asset posting to shared spaces </li></ul></ul>
  7. 7. Activities for COIs to Implement <ul><li>Key Activities </li></ul><ul><li>Identify/establish COI </li></ul><ul><li>Identify membership and governance (e.g. Mission Areas, Domains) and key stakeholders (e.g. Programs, Operators) </li></ul><ul><li>Identify/prioritize/select key COI capabilities and data assets to expose to Enterprise </li></ul><ul><li>Register into DoD COI Directory ( ) </li></ul><ul><li>Define and register COI structural metadata (e.g. taxonomy, vocabulary, data models, schema) </li></ul><ul><li>Define discovery metadata and process (extend the DDMS) </li></ul><ul><li>Tag data assets and post to searchable catalogs (e.g. Domain metadata catalog and service registry) </li></ul><ul><li>Register COI services (supports separation of data from applications) </li></ul><ul><li>Operate and sustain COI services (e.g. web services) for selected COI capabilities (leverage NCES CES) </li></ul>COI Overview
  8. 8. Sample COI Organization Chart Steering Committee Forum (FO) (Chair or Co-Chair) Data Management Working Group (Military Service Co-Lead) WGs FOR DISCUSSION PURPOSES ONLY Additional Groups as needed Infrastructure Working Group (Military Service Co-Lead Executive Board (FO/GO) Chair or Co-Chair Pilot Demonstration Working Group (Military Service Co-Lead) <ul><li>Task: write web service to pub/sub the data </li></ul><ul><ul><li>Web Services </li></ul></ul><ul><ul><li>Leverage Net Centric Enterprise Service (NCES) services (discovery, security) </li></ul></ul><ul><li>Task: Develop common data vocabulary for a given report </li></ul><ul><ul><li>Bottoms up data user defined </li></ul></ul><ul><ul><li>Supports top down governance </li></ul></ul><ul><li>Task: Develop a repeatable process to demonstrate pub/sub web service </li></ul><ul><ul><li>Risk reduction for inclusion by Programs of Record </li></ul></ul>2 or 3 star level 1 star level with 0-6/GS-15 membership
  9. 10. Way Ahead <ul><li>ISR COI </li></ul><ul><ul><li>Purpose and Scope </li></ul></ul><ul><ul><li>Goals </li></ul></ul><ul><li>ISR COI Charter </li></ul><ul><li>Domain Name </li></ul><ul><li>Common Core Taxonomies </li></ul><ul><ul><li>Feature Level Metadata </li></ul></ul><ul><ul><li>Quality </li></ul></ul><ul><ul><li>Levels of Metadata </li></ul></ul><ul><ul><li>Symbology Metadata </li></ul></ul><ul><li>Producers / Contributors </li></ul><ul><ul><li>DoD MWG </li></ul></ul><ul><ul><li>Fed Geospatial MWG </li></ul></ul><ul><li>Helpful Resource : </li></ul><ul><li>Norman C. Andersen </li></ul><ul><li>Metadata Standards Officer, NCGIS </li></ul><ul><li>National Geospatial-Intelligence Agency </li></ul><ul><li>Mail Stop P-106 </li></ul><ul><li>12310 Sunrise Valley Drive </li></ul><ul><li>Reston, VA 20191 </li></ul><ul><li>Phone: 703-814-4565 </li></ul><ul><li>Fax: 703-961-0403 </li></ul><ul><li> </li></ul>
  10. 11. References to DoD COI Forum <ul><ul><ul><li>----- Original Message ----- </li></ul></ul></ul><ul><li>From: Bryan J. Aucoin </li></ul><ul><li>To: Brand Niemann ; [ drm -team] </li></ul><ul><li>Cc: Marianne Floyd-Y- ; Stephen Selwyn </li></ul><ul><li>Sent: Wednesday, January 18, 2006 6:18 PM </li></ul><ul><li>Subject: Re: [drm-team] TIME SENSITIVE: DoD COI Forum, Thursday, January 19th, at MITRE (also remote access) Just an FYI, Brand. The IC EA CoP is not an intended as open forum.  Many of our presenters brief with the implicit understanding that the documents will not be released outside of the Community without prior permission.  Most agencies within the Community have policy around this sort of &quot;unofficial release&quot;.  Please coordinate these request through Marianne. Brand Niemann wrote: See  for presentation files and see Reminder below. BrandP.S. I am still working on getting the files for the January 12th IC EA CoP Meeting.  REMINDER:  The next COI Forum is:   Date :       January 19, 2006, Time :       08:00 Registration, Duration : 08:30 - 12:30 Forum Location : MITRE 1                      Auditorium             7525 Colshire Drive             McLean, VA  22102-7508 NOTE, THIS IS A CHANGE:   Please park in either the West Parking or East Parking lot, as indicated on the map, and enter through the Conference Center entrance, also indicated on the map. Directions:   Dial in capability:  The local Virginia number is 703-983-1550. A toll free number is 866-648-7367. For any participants calling in from Bedford, MA, the local number is 781-271-6338. The caller will be asked for a meeting ID number, which is &quot;2665&quot;. There will be several other prompts that should be self-explanatory to get connected. Please initiate your call at 0810, to ensure that the phone conference is set and solid before the session begins at 0830.   If you require assistance, please contact Harry Wickes at 703-983-2665 (office), 202-352-7101 (mobile) or E-mail [email_address] Agenda8 Registration 8:30 Opening & Introductions 8:40 C2 Space Situation Awareness (SSA) COI 9:25 Role of Net-Centricity in Space C2 Weapon System 10:10 Network Break 10:40 Where is Your Welcome Sign 11:10 COI Lessons Learned 11:40 COI Gallery & DoD Metadata registry 12:25 Announcements 12:30 Closing/Remarks _________________________________________________________________ </li></ul><ul><li>Message Archives: </li></ul><ul><li> </li></ul><ul><li>Shared Files: </li></ul><ul><li>Community Portal: </li></ul><ul><li>To Post: </li></ul><ul><li>Community Wiki: </li></ul>
  11. 12. Reference Links <ul><li>The DoD Net-Centric Data Strategy </li></ul><ul><ul><li> </li></ul></ul><ul><li>Data Sharing in a Net-Centric DoD, DODD 8320.2 </li></ul><ul><li> </li></ul><ul><li>DoD Discovery Metadata Specification (DDMS) </li></ul><ul><ul><li> </li></ul></ul><ul><li>DDMS Schema information </li></ul><ul><ul><li> </li></ul></ul><ul><li>COI Directory </li></ul><ul><ul><li> </li></ul></ul>
  12. 13. Template for the ISR COI Charter <ul><li>Charter for the Intelligence, Surveillance, and Reconnaissance (ISR) </li></ul><ul><li>Under the </li></ul><ul><li>……… </li></ul><ul><li>1. PURPOSE </li></ul><ul><li>1.1 Charter. The purpose of this charter is to establish the Intelligence, Surveillance, and Reconnaissance (ISR) as a community of interest under the …... </li></ul><ul><li>1.2 ISR COI . </li></ul><ul><li>2. SCOPE </li></ul><ul><li>3. MISSION </li></ul><ul><li>4. REFERENCES </li></ul><ul><li>5. ORGANIZATION </li></ul><ul><li>7. PROCEDURES </li></ul><ul><li>Approval Authority: </li></ul><ul><li>Signature </li></ul><ul><li>…… </li></ul>
  13. 14. References to Upcoming Taxonomy Training <ul><li>From:Talcott Marilyn Civ SAF/XCXPJSent:Mon 2/13/2006 1:39 PMT </li></ul><ul><li>Our next Taxonomy Training Session will be held on 1 and 2 March at the Sumaria facility in O'Fallon Illinois (1728 Corporate Crossing, Suite # 1).  Cost for the training session will be $420.00.  This is a slight increase from the previous session due to the change in location.  If you or your designed reps are interested in attending this class please provide the following info: </li></ul><ul><ul><li>Name: </li></ul></ul><ul><ul><li>Organization: </li></ul></ul><ul><ul><li>Phone Number: </li></ul></ul><ul><ul><li>Email Address: </li></ul></ul><ul><li>Purpose for Attending:  (short explanation of why you desire to attend and/or require this training) Please email your info to Mr Matt Brady at:   by COB 21 February.  The class is limited to 16 attendees--we will notify selected attendees by COB 22 February. </li></ul><ul><li>For your planning purposes--We intend to offer a Taxonomy Training Session At Wright Patterson AFB on 14 and 15 March. </li></ul><ul><li>Thanks </li></ul><ul><li>Marilyn A. Talcott, GS-14, DAF </li></ul><ul><li>Federal Govt & DoD Liaison Officer </li></ul><ul><li>SAF/XCXPJ </li></ul><ul><li>(703) 696-6278 </li></ul>
  14. 15. Vocabulary Style Guide - Resources <ul><li>The C2 SSA COI Steering Committee Chair (Gen Shackelford) approved/signed the first installement of the C2 SSA Vocabulary.  The signed memo and vocabulary products can be found via this URL: </li></ul><ul><li> </li></ul><ul><li>or manually </li></ul><ul><li>/Data Management Working Group/C2 SSA Vocabulary   (This path contains the C2 SSA Vocabulary Guide and the C2 SSA COI Memo) </li></ul><ul><li>/Data Management Working Group/C2 SSA Vocabulary/C2 SSA Model   (This path contains the XML schemas and sample XML instance documents) </li></ul><ul><li>If you encounter problems finding the vocabulary products please don't hesitate to call and I will help you. </li></ul><ul><li>Thank You </li></ul><ul><li>Mark Pleimann (719) 572-8244 </li></ul><ul><li>Click the following URL to reply to the message/view previous messages: https:// =OO-OT-SP-03&MsgIndex=4694 </li></ul><ul><li>or via the AF Portal: https:// =OO-OT-SP-03&MsgIndex=4694 </li></ul>
  15. 16. Vocabulary Style Guide – Current Work Underway <ul><li>Ladies and Gentlemen, </li></ul><ul><li>HQ AFSPC/A5 respectfully requests your coordination on the Vocabulary Guide and Data Schema Extensions for the Command and Control (C2) Space Situation Awareness (SSA) Community Of Interest (COI). </li></ul><ul><li>1.      PURPOSE:  To conduct a review and coordinate the C2 SSA COI Vocabulary Guide and Data Schema Extensions prior to COI Chair approval, and registration into the DoD Metadata Registry for general use by authorized DoD system owners and users. </li></ul><ul><li>2.      BACKGROUND:  OSD/NII has sponsored the creation of this COI, chaired by AFSPC/CV, as a venue for programs of record to vet their net-centric requirements, and facilitate the discoverability, availability, and accessibility of C2 SSA data and information. </li></ul><ul><li>3.      DISCUSSION:  This Vocabulary Guide at Tab 2 and data schema extensions at Tabs 3-6 signifies the first step at standardizing Defense Satellite Communications System (DSCS) link availability data, and Global Positioning System (GPS) Navigational Accuracy Alert Services required to monitor, assess, plan, and execute the operational and tactical commander's intent in a net-centric environment.  Several eXtensible Markup Language (XML) samples are attached at Tabs 7-9, demonstrating how the data schema extensions can be used.  </li></ul><ul><li>Our goal is to have coordination due by 17 Feb 06, and schedule a subsequent comments resolution meeting during the week of 20 Feb 06 to address any concerns or critical comments.  We intend to have AFSPC/CV sign the advocacy letter at Tab 1, formalizing the approval of the Vocabulary Guide and data schema extensions prior to registration into the DoD Metadata Registry. </li></ul><ul><li>4.      VIEWS OF OTHERS:  None. </li></ul><ul><li>5.      RECOMMENDATION:  Request coordination and response NLT 17 Feb 06. </li></ul><ul><li>// Major Foster, A5 Executive Officer </li></ul><ul><li>   On behalf of // </li></ul><ul><li>MARK D. SHACKELFORD                             9 Tabs: </li></ul><ul><li>Maj Gen, USAF                                           1) C2SSA  Process Memo </li></ul><ul><li>Director of Plans & Requirements                        2) C2 SSA Vocabulary Guide 1-17-06 </li></ul><ul><li>                                                        3) C2ssa_schema </li></ul><ul><li>                                                        4) C2ssa_utilities </li></ul><ul><li>                                                        5) C2ssa_dscs_extension </li></ul><ul><li>                                                        6) C2ssa_gps_extension </li></ul><ul><li>                                                        7) sample_c2ssa_dscs_big_report </li></ul><ul><li>                                                        8) sample_c2ssa_gps </li></ul><ul><li>                                                        9) sample_c2ssa_sat_status </li></ul><ul><li><<Tab 1 - C2SSA process memo.doc>> <<Tab 6 - C2ssa_gps_extension.xsd>> <<Tab 7 - sample_c2ssa_dscs_big_report.xml>> <<Tab 8 - sample_c2ssa_gps.xml>> <<Tab 9 - sample_c2ssa_sat_status.xml>> <<Tab 3 - C2ssa_schema.xsd>> <<Tab 4 - C2ssa_utilities.xsd>> <<Tab 2 - C2 SSA Vocabulary Guide 1-17-06.doc>> <<Tab 5 - C2ssa_dscs_extension.xsd>> <<SSS - C2 SSA COI Vocab & Schema Coord.xfdl>> </li></ul>
  16. 17. Thank You