1 / 25

My Two Cats Are a Community of Interest

Explore the history, current status, and future plans of Communities of Interest (COIs) in data sharing within the defense community. Learn about the evolution of COIs, their three main meanings, and the roles of cooperators in solving data-sharing problems. Understand the proposed definition of a COI, its functions, and how COIs operate through cooperation and collaboration. Discover the key elements, common functions, and stakeholders involved in COIs. This comprehensive outline provides insights into the importance of collaboration in improving net-centric data sharing.

coombs
Download Presentation

My Two Cats Are a Community of Interest

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. My Two Cats Are aCommunity of Interest Dr. Scott Rennersar@mitre.org

  2. Outline • History • Current situation • Proposed direction

  3. History of COIs • DoD Data Admin program, 1991-2000 • Data Interoperability Rapid Improvement Team, 2000 • AF SAB “Database Migration” study, 2001 • DoD Data “Broad Area Review”, 2002 • Net-Centric Data Strategy, 2003 • AF Information and Data Management Strategy, 2004 • IT Portfolio Management, 2004 • OSD(NII) COI Pilots, 2005 • C2 Space Situational Awareness • Blue Force Tracking • Maritime Domain Awareness

  4. Three “Correct” Meanings of “COI” • Vocabulary COI • People who have a common vocabulary for their domain • Deliberate vocabulary creation/teaching effort • Data standards consortia • Sharing COI • People who are actually sharing data with each other • Real producers, real consumers • Proponent COI • People who want a new/improved sharing capability • Not the people who develop or know the vocabulary • Not the people who actually produce or consume data • People with authority and money

  5. Useful Common Elements • COIs solve a data-sharing problem • COIs per se don’t do anything; their members do

  6. Proposed Definition • Within the context of the NCDS, a “community of interest” is defined as a group of people who cooperate to solve a problem in net-centric data sharing • To solve their problem, the members may • Form and promulgate a common vocabulary • For discovery metadata • For machine-to-machine data exchange • For architecture descriptions • Actually exchange information with each other • Develop new capabilities for new/improved info sharing • COIs do not overtly control resources or direct activitiesThey act entirely through the cooperation of their members and their respective organizations

  7. Who Cooperates? • If COIs act through the cooperation of their members…then who does the cooperating?

  8. Roles of the Cooperators • Information owners • Shared information space controllers • Semantic communities

  9. AF Information & Data Mgt. Strategy:The “Triangle Foundation” Shared Information Spaces Implementation and Infrastructure Community Vocabularies Information Owners / Data Producers

  10. Shared Information Spaces Shared Information Space Consumers and the information they need Validated info needs, driven by CONOPS and TTPDesignated authoritative sources meeting requirements Access control (users, roles, permissions)Priority and Quality of Service Controlling authority

  11. Information Owners Shared Information Space Consumers and the info they need • Information Owners / • Data Producers • Organizations with authority and responsibility for producing information • Identify subordinate owners, ensure they: • Supply discovery metadata • Establish, effect data access plan • Satisfy records mgt requirements, etc.

  12. UK US Australia Justice EPA DoD State Treasury Army Air Force Navy The Enterprise: Subordinates and Partners You can’t just say “all information is owned by the enterprise” AETC AMC ACC AFMC AFSOC

  13. Data Service Agreements Are Required Shared Information Space Consumers and the info they need Information Owners / Data Producers Organizations with authority and responsibility for producing information Agreements between producers and infospace controllers: Availability Access control

  14. Community Vocabularies Shared Information Space Consumers and the info they need Community Vocabularies Hierarchy of subject-area vocabularies Community understanding of data models for runtime data exchange, architectures, discovery metadata, information owner descriptions Information Owners / Data Producers Organizations with authority and responsibility for producing information

  15. Implementation Infrastructure Shared Information Space Consumers and the info they need Information Owners / Data Producers Organizations with authority and responsibility for producing information Community Vocabularies Subject-area vocabularies Data models for data exchange, architectures, discovery metadata Implementation and Infrastructure Data access implementation (warehouse, pub/sub, web service, portal, etc.) Physically located at producers, consumers, or someplace in between. Core services for identity, authentication, etc.

  16. COIs Operate at the Intersection Infospace COI Vocabulary Producers

  17. Video Store Infospace Employees, Customers, etc. CommonVocabulary Store #1Data Producer Store #2Data Producer Movies, Customers,Fines One enterprise, effective central control A Simple Enterprise When effective centralized, top-down control is feasible, no need to separate producer, infospace, vocabulary concerns

  18. COI PersonnelDataProducer PersonnelDataProducer PersonnelDataProducer PersonnelDataProducer Air Force Army Navy USMC Flight OperationsVocabulary Including roles and training requirements A More Complex Enterprise Flight Planner infospace Consumers and theinformation they need

  19. Consumers and theinformation they need PersonnelDataProducer PersonnelDataProducer Flight OperationsVocabulary PersonnelDataProducer Including roles and training requirements PersonnelDataProducer Still More Complex PACOMFlight Planner infospace several infospheres

  20. Expanding To The Enterprise The infospace will include information from other producers, following other vocabularies Infospace Your COI Producers will post to other infospaces, using other community vocabularies Other producers and other infospaces will use the community vocabulary Vocabulary Producers

  21. US Force Planning infospace Internal Revenue Service infospace PACOM Flight Planner infospace Flight Operations vocabulary US Tax Code vocabulary Global Force Management vocabulary PersonnelDataProducer Even More Complex: Producer View post data to multiple infospheres post data in multiple vocabularies

  22. AUS Force Planning infospace PACOM Flight Planner infospace Australian Taxation Office infospace PersonnelDataProducer Flight Operations vocabulary Australian Tax vocabulary AUS Force Management vocabulary Even More Complex: Producer View

  23. Consumers and theinformation they need Weather data producers Flight Operations vocabulary Weather vocabulary ISR data producers Imagery vocabulary Personnel data producers Even More Complex: Infospace View PACOM infospace consume data from multiple producers consume data following multiple vocabularies

  24. Other Government infospaces Commercial infospaces PACOM Flight Planner infospace Commercial Imagery data producers Imagery Vocabulary Other National Imagery data producers Pictures, their sources, representation, quality, etc. US Imagery data producers Even More Complex: Vocabulary View vocabulary used in multiple infospheres vocabulary used by multiple producers

  25. Summary • Too many meanings of “COI” • Common elements in the useful definitions • Solve a net-centric data sharing problem • Work through cooperation of COI members • Elements of an information management architecture • Information owners • Infospace controllers • Semantic communities • Future direction: governance and managementof those three elements

More Related