《指挥控制本体国外英文教学课件PPT.ppt》由会员分享，可在线阅读，更多相关《指挥控制本体国外英文教学课件PPT.ppt（37页珍藏版）》请在三一办公上搜索。
1、1,Proposed Application of Ontology within the U.S.C2 Core Effort,Ms.Leslie Winters,USJFCOM J87Dr.Bill Mandrick,University of Buffalo*,*Supporting U.S.Army Center for Software Excellence and C2 Core Operational Content Working Group,2,Purpose,Describe U.S.efforts to apply ontology to the development
2、of the C2 Core*,*For XML-based data exchange internal to U.S.,3,Outline,C2 Core Overview C2 Core Semantics 9 Step Ontology Process C2 Domain Analysis C2 Core Ontology Conclusions Discussion,4,U.S.C2 Core Data Exchange Standard,5,C2 Core Concept,C2 Core standardizes the meaning and format of the most
3、 commonly exchanged C2 data:Understandable,Interoperable,The C2 Core will standardize a subset of the C2 data vocabulary and provide a uniform methodology for building understandable and interoperable XML-based messages.,6,C2 Core Components,IES=Information Exchange Specification;the prescribed XML
4、format for a C2 Core compliant message,IEP=Information Exchange Package;Actual XML message constructed according to IES,C2 CM and Vocabulary describe common C2 terms and their relationships.,C2 Specific Extensions to UCore are the reusable XML-based components of the C2 Core:the building blocks for
5、constructing C2 messages.,C2 Core messages are constructed from“reuseable components”using a common format and agreed upon meaning,7,C2 Core Development Approach,C2 Core Developed Collaboratively based on Existing Standards and IERs,8,C2 Core Architectural Framework,UCore-enabled systems can underst
6、and all UCore message content except the Structured Payloads C2 Core-enabled systems can also understand C2 Core based Structured Payload Additional Structured Payloads from C2 COIs and/or PORs can fill in remaining concepts,9,C2 Core,Building C2 Core(Ontology Perspective),9,Message,Guides,Details,B
7、ottom-Up,Data Exchange RequirementsMessaging Requirements,Use cases,msgs,artifacts from the field,Doctrinal Publications,Top-Down,RepresentConsensus:NamesStructureSemanticsRelationships,UCore Taxonomy/UCore-SL),C2 Core Ontology,produces,10,10,C2 Core,Using C2 Core(Ontology Perspective),11,C2 Core St
8、atus,Independent Assessment Team Report,Dec 2008DoD CIO Interim Guidance memo signed Mar 09Cross-C/S/A C2 Core Working groups underwayTools and Technical FrameworkOperational Content(to include C2 Domain Ontology)Verification,Validation,and Implementation“Testable Baseline”out 30 Jun 09;Approved by
9、C2 Portfolio Data and Services Steering Committee 30 Jul 09 Initial reusable components,processes,conformance rules,documentation C2 Core V0.5 MAR 10;Continual maturation via iterative approachVersion 1.0 4Q FY10(suitable for early adopters and piloting/test events)Version 2.0 4Q FY11(suitable for i
10、mplementation assuming successful testing),12,C2 Core Semantics,13,9 Step Ontology Process,Initial Domain Analysisa)Identify Domain Boundariesb)Identify Categories and Sub-Categoriesc)Eye towards instance(tactical)leveld)SME input2)Identify Doctrinal Sources 3)Extract high-frequency terminology and
11、definitions4)Develop Taxonomy and Relations5)Map to UCore 2.0 Taxonomy6)Extend to Instance Level Terminology(Vocabularies)7)Acquire SME Feedback8)Revise9)Field Ontology,Brief to here,14,C2 Domain Analysis,So,what is the C2 Domain?The C2 Domain consists of 6 components:Force Structure,Integration,Org
12、anizationSituational AwarenessPlanning and AnalysisDecision Making and DirectionOperational Functions and TasksMonitoring Progress(Assessing)C2 Core Ontology is based upon these elementsVocabulary derived from Joint Doctrine,15,Command,Control,COMMANDER,SUBORDINATE COMMANDER,SUBORDINATE COMMANDER,SU
13、BORDINATE COMMANDER,Source:USMC Doctrinal Publication 6,Force Structure and Integration,Operational Functions and Tasks,Situational Awareness,Planning and Analysis,Command Decision Making and Direction,C2 Domain Analysis,Monitoring and Assessing,16,C2 Domain Analysis,Extend UCore one level down into
14、 C2 CoreC2 EntitiesC2 EventsMid-Level(Utility)OntologyNo specialized termsOrganizes appropriate doctrinal terminology and semanticsIncorporates actual data requirementsIdentifies requirements through/for scenarios,messages,data exchanges,models,.Requires SME participation and consensus,Bottom Up,Top
15、 Down,17,Top-Down and Bottom-Up Define One Synchronous Model,OntologyDefines objects,events and relations as they are in the world rather than as they are described in the context of a particular messaging frameworkProvides a common source of semantics that enables consolidation of data from differe
16、nt domains/sourcesOptimized to enable aggregation of and inferencing on XML instancesData Exchange Components(reusable)Capture real data exchange requirementsConsensus-based representationsOptimized for composition of XML components into IESs,17,18,JP 5-0 Joint Operation PlanningJP 1-02 DoD Dictiona
17、ry of Military and Related TermsJP 3-13.1 Joint Doctrine for Command and ControlJP 3-0 Joint OperationsFM 3-0 OperationsMCDP Command and Control,C2 Core Ontology Doctrinal Sources,19,High-Frequency Terminology,Getting to the Low-Hanging FruitReliable Data SourcesGood C2 ModelsC2 ExperienceApply 10/9
18、0 ruleUse“Best Practices”SME Input,20,Taxonomy,Entity,Event,Role,Information Content Entity,Organization,Geographic Feature,Document,Planned Event,Humanitarian Assistance Event,Terrorist Event,Military Event,UCore Thing,C2 Core,Grid Location,Target,Joint Operation,Joint Operation Plan,Military Unit,
19、Campaign Plan Document,Engagement,Humanitarian Aid Operation,Battle,Campaign,Instance Level,Tactical Messages,IESs,IEPs,COI Vocabularies,21,The C2 Core Ontology,A Few Examples(Screenshots)From Protg,22,C2 Information Content Entities,Doctrinal Definition:A clear,concise statement of what the force m
20、ust do and the conditions the force must meet to succeed with respect to the enemy,terrain,and the desired end state(FM 3-0).,23,C2 Core Ontology Events,Doctrinal Definition:A C2 Process whereby Combatant Commanders and subordinate joint force commanders translate national or theater strategy into o
21、perational concepts through the development of an Operation Plan for a Campaign.(JP 1-02),Definitions based upon Joint Doctrine,24,Example,C2 Core OntologyDescribes the C2 Domain accurately With categories that extend from UCore 2.0And acts as a middle(semantic)layerEstablishes a systematic way of o
22、rganizing the terms,entities,and eventsUsing doctrinally sound terminology Some examples from JC3IEDM,25,Military Organizations,JC3IEDM Terms,UCore 2.0“Entities”,Bold Terms=C2 Core,26,Geographic Features,Area of InfluenceArea of InterestArea of OperationsArea of ResponsibilityPhase Line,UCore Defini
23、tion:Physical or cultural areas,regions or divisions that can be defined in terms of geographic coordinates.Derived from Geographic Names Information Service.USGS.Accessed 10 March 2009.JC3IEDM Terms,High-Level JC3IEDM Terms are included in C2 Core Ontology,27,Information Entities,JC3IEDM Terms,C2 C
24、ore Definition:An entity which consists of information and which inheres in some information bearing entity.,28,Plans,MIP Configuration Management PlanMIP Development Plan MIP Programme Management PlanOperations Plan Operations Order,C2 Core Definition:An information content entity that is a specifi
25、cation of events that are to occur in order to obtain some objective.,JC3IEDM Terms,C2 Core Ontology,29,Vehicles,JC3IEDM Terms,Some JC3IEDM terms map directly to UCore terms,30,Operations,Military Operations Other Than WarCivil/Military OperationsPeace Support OperationsReconnaissance Non-combatant
26、Evacuation Operations,JC3IEDM Terms,C2 Core Taxonomy“Events”,C2 Core Definition:The process of carrying on combat,including movement,supply,attack,defense,and maneuvers needed to gain the objectives of any battle or campaign.(JP 1-02),31,The Ontology,Features:Limited to 200+/-terms Commonly understo
27、od relationsis apart oftemporal part ofparticipates inetcResults in Triples Allows for Unique Identifiers to be assigned to each instanceResearch in Referent Tracking Systems(Warehousing and Inferencing),32,Conclusions,The C2 Core Ontology:Describes the C2 Domain accuratelyProvides a systematic proc
28、ess for organizing the terms,entities,and events for Command and ControlUses categories that extend from UCore 2.0Acts as a middle(semantic)layer connecting UCore 2.0 with C2 Core vocabularies,33,Discussion,34,Backups,35,DoD Net-Centric Data Strategy(2003)Ensure data are visible,accessible and usabl
29、e DoDD 8320.02(Dec 2004)DoD policy that Data is an essential enabler of network-centric warfare(NCW)and shall be made visible,accessible,and understandable DoD 8320.02-G(Apr 2006)Identify data assets to share;Making data accessible by commonly supported access methods,understandablereaching agreemen
30、t on the meanings CJCSI 8410.01(Mar 2007)Services shall implement net-centric data sharing,by establishing appropriate plans,programs,policies,processes,&procedures according to DoDD 8320.02.DoD C2 Strategic Plan(Dec 2008)Successful implementation of data&services strategies for C2 capabilities requ
31、ires identification of authoritative C2 data sources CJCSI 6212.01E(Dec 2008)to gain Interoperability&Supportability Certification,program data&services,must be“exposed”by making data elements&provided services visible,accessible,and understandable ASD(NII)/DoD CIO Memorandum(Mar 2009)Establishes an
32、 objective for the C2 CPM and DoD Components to identify data sharing requirementsDirects the development of a C2 Core DoD CIO Universal Core Memo(Jul 09)UCore,coupled with domain cores(e.g.C2 Core)has the potential to dramatically improve DoD internal and external information sharing”,Policy is Cle
33、ar Authoritative Data Exposure and Common Data Exchange Standards are Essential to Way Ahead,Guidance and Direction,36,Top-Down,Uses a mid-level or utility ontology.Details UCore for C2 domain.Organizes appropriate doctrinal terms and semantics.Helps identify potentially missing requirements.Helps i
34、nform data requirements analysis.Used as common framework to identify,name,and represent requirements as exchange components.Documents relationships and rules between objects.,36,37,37,Bottom-Up,Incorporates the actual data exchange requirements.Identifies requirements through/for scenarios,messages,data exchanges,models,.Consensus-based and NDR-conforming naming,structure,and semantics.Builds data representations that define the exchange of XML instances.Requires SME guidance and consensus.,
