1 / 49

C2 Core Tutorial

C2 Core Tutorial. Mr. Frank W. Klucznik Data and Services Division United States Joint Forces Command. Content. C2 Core’s Objective Historical Context C2 Core Overview C2 Core Developer Support Network (C2CDSN) Overview. Staff / Watch Officers. Staff / Watch Officers. Net-Centric

gauri
Download Presentation

C2 Core Tutorial

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. C2 Core Tutorial Mr. Frank W. Klucznik Data and Services Division United States Joint Forces Command

  2. Content • C2 Core’s Objective • Historical Context • C2 Core Overview • C2 Core Developer Support Network (C2CDSN) Overview

  3. Staff/ Watch Officers Staff/ Watch Officers Net-Centric Information Sharing Community Capability Community Capability Common Semantics Common Semantics Collaboration & Coordination Shared Understanding Objective - Shard Understanding Shared Operational Picture Shared Tactical Picture Commander Commander Community Information Sharing

  4. Historical Context Message Format / Information Exchange Specification / Document Schema IES defines System System IEP Message / Info Exchange Package / Document Data Source Data Consumer

  5. If these aren’t compatible This won’t work Process Producer Vocabulary Consumer Vocabulary System System XML (probably) Data Source Message / Info Exchange Package / Document Data Consumer

  6. Shared knowledge is embedded in translation software… very hard to get the knowledge back out for software maintenance, or for connecting with other partners TRANS TRANS Pairwise Solution Community of Two negotiate negotiate Vocabulary application application IEP Data Source Message / Info Exchange Package / Document Data Consumer

  7. 1 2 15 3 14 13 4 5 12 11 6 10 7 8 9 Pairwise Solution Does not scale in a large enterprise The N2 problem 15 applications 210 negotiations Total level of effort is O(n2)

  8. Community of Everyone 1 2 15 3 14 13 4 Vocabulary for Everything 5 12 11 6 10 7 8 9

  9. Community of Everyone Too much knowledge must be learned by too many people A top-down approach ignores knowledge people already have 1 2 15 3 14 13 4 Vocabulary for Everything 5 12 11 6 The mission of everyone changes much faster than the vocabulary can change 10 7 This learning is expensive, and takes a long time 8 9

  10. Communities of Interest COI Y COI Z COI X Vocabulary Y Vocabulary Z Vocabulary X If you can’t have one universal vocabulary understood by everyone, then you must have several vocabularies, each understood by some group

  11. Communities of Interest COI X COI Y COI Z X&Y Y&Z Vocabulary X Vocabulary Y Vocabulary Z translate translate When COIs must exchange data, we must translate between vocabularies (This by itself is an improvement: N2 is not so bad when N is small)

  12. # people in community Optimizing COI Vocabularies • Analysis indicates the best possible arrangement of COIs and vocabularies: • A small number of broad, shallow vocabularies:few definitions, understood by many people • A larger number of narrow, deep vocabularies:many definitions, understood by few people • Arranged in a rough hierarchy; deep vocabularies adopt and extend the shallow broad and shallow vocabulary narrow and deep vocabulary narrow and deep vocabulary # definitions in vocabulary specialized, extended vocabularies

  13. Optimizing COI Vocabularies • Partitioning knowledge between communities: • Achieve some of the most valuable interoperability • While retaining agility / flexibility in face of changing needs • Reducing cost and time to implement • Universal and common core vocabularies improve interoperability while retaining agility and local autonomy Universal Core C2 Core Common Core #1 Common Core #2 C2 COI #1 C2 COI #2

  14. Resulting Data Architecture Universal Core C2 Core Common Core Common Core COI COI COI COI COI COI COI COI COI COI

  15. What is C2 Core? • Open (XML based) Data Exchange Standard • First major implementation of UCore v2.0 • Composition • Vocabulary and data model • Architectural Framework • Reusable XML Components An evolving open standard built by the C2 Community for the C2 Community

  16. Relationship to Others • UCore v2.0 • ULEX Message Framework • 4Ws (who, what, when, where) • 5 methods of extension • C2 Core • C2 Vocabulary • Specs for Payload Extension • XML Naming & Design Rules • Info Exchange Specification • COI / POR Relationship analogous to Federal – State – City regulatory governance construct

  17. C2 Core Architecture IES C2 – Command and Control COI – Communities of Interest POR – Programs of Record IES – Information Exchange Specification IEP – Information Exchange Package

  18. Technical Architecture Maturation 2008 2010 2009 ULEX/UCore Implementation Options ULEX/UCore/C2 Core Payload Focused Approach Support broad range of exchange environments Digest Focused Approach

  19. C2 Core Today • Guidance and Misc Documentation • Implementation Guidance • Value Proposition • IES Development Guide • C2 Core Version Architecture • Governance • C2 CPM DSSC • Configuration Control Board & Charter • C2 Core Work Group • Technical Evaluation Teams • Community Outreach & Training • C2 Core Training & Familiarization • New content development (e.g. GFMDI, ASW COI, et al) • Conferences (e.g. DON IT, DoD Enterprise Architecture, et al) • Technical Exchange (e.g. UCore) • Experimental Products • C2 Core-UCore Binding Specification • C2 Core Genericode Specification • V1.0 Content (ready for piloting) • Semantic Overlaps Across C2 • Conceptual Data Model • V1.0 Technical Specifications • Development Concept & FAQ • Naming and Design Rules • Conformance Specification • IES Specification • Technical Analysis • XML Compression Analysis • Implementation Patterns Analysis • C2 Core Usage Patterns • Developer Tools & Support • C2 Core Developer Support Network • Schema Subset Generation Tool • Conformance Tool • Training (Levels I, II, III, IV) • Plans & Processes • Configuration Management Plan • Change Request Process

  20. Key Training Components • 48 Lessons covering 270+ topics • C2 Core Level I, II, III Material • IES Development Guide • Data Modelers Guide • C2 Core NDR Guide • Schema Writers Guide • XML Tutorial • Tool User Guides • Designed to support roles of: • Manager • Data Architect • Developer Lessons Topics

  21. Training Sample

  22. IES Package Content Subset c2core 1.0 - c2core.xsd appinfo - appinfo.xsd structures - structures.xsd external - ic-ism-v2.1.xsd proxy - xsd-proxy.xsd adapters - tspi-adapter.xsd ucore • - ucore.owl • ucore.xsd • et al ucore schema - coi-extension.xsd NOTE: Black generated by SSGT Green added manually Red added manually - ies-extension.xsd - exchange.xsd - wantlist.xml

  23. END

More Related