International Defence Enterprise Architecture Specification (IDEAS) June 2007 Michael L. Wayson DoD CIO (Architecture & Interoperability)

IDEAS Working Group Objectives To develop a planning capability to support the nations involved in coalition operations The objective is to automate the exchange and generation of planning information from participating national military architecture repository systems

Coalition Australia, Canada, UK, and USA have a history of military coalition Each nation is pursuing its own version of net-centric warfare Need for some degree of international net-centricity Shared situational picture Collaborative Engagement Capability etc. Each nation is developing its own architectural framework Requirement to share architectural information between nations to enable interoperability at the operational and system levels

Governance Structure IDEAS consists of Active nations (Voting) Observer Organizations (Non-voting) IDEAS organization structure: An Executive body that serves as a high level steering group that define program objective and resourcing A Working Group that undertakes the technical activities

Working Group Participation Active Nations: Australia Canada United Kingdom United States Observer Organizations: NATO Object Management Group (by UK MOD Rep) Swedish Armed Forces/FMV Architecture Team

Continuing Program of Activities Develop the IDEAS Model To specify the minimum set of data elements, attributes and relationships needed to support coalition force planning and other coalition operational activities Develop the models for sample planning/coalition activities scenarios Develop the Data exchange specification Specifies the interchange standard for participating IDEAS members and forms the main body of documentation used for configuration management of the data exchange mechanism Develop the Data exchange mechanism Specifies the data exchange format for IDEAS (based on XML technologies (using RDF/RDFS at present)) Co-exists as part of each nations architecture repository solution Develop the repository data exchange mechanism

IDEAS Core Model Concept Exchanges are via a commonly-agreed IDEAS Core Model, not translations from point-to-point

Methodology and Approach Participants continued the use of Business Objects Reference Ontology (BORO) methodology to clarify concepts Participants continued to: use UML as modeling language, profiled to IDEAS derive model from agreed operational constructs provide complete semantics Participants will fully document all aspects of the model and methodology for the IDEAS capability Participants will experiment with data exchange as they progress – test a little, design some more – so we don’t end up with an unimplementable model Eventually, participate in an exercise

high-level patterns (upper ontology) common objects (agreed taxonomy) Structure Layered approach Starting from first principles to ensure common understanding at the most fundamental level Reaching down to country-specific definitions whose meaning may need to be understood by other nations fundamental concepts: classes, instances, properties foundation high-level patterns (upper ontology) commonly used relationships: whole-part, sequence, etc. common objects (agreed taxonomy) internationally accepted terms: person, organization, materiel, etc. national extension national extension national extension national extension terminology specific to nations that which may be useful to other nations - e.g. Bowman, Bradley FV, etc.

IDEAS Model Status Foundation well defined Namespace pattern at initial definition Still need to finalise patterns for Overlap/Event, Time and Tuple Type Data being defined/incorporated/clarified Common Objects well defined Mapping of national terms to IDEAS terms has progressed facilitated by the namespace pattern Need to define who owns the namespace for each organisation/nation Top level IDEAS context diagram created and described Identified that a common upper level taxonomy will need to be defined for a number of areas of operational data likely to be exchanged via the IDEAS model

Program of Work Schedule 10 to 14 September 2007 London, UK February 2008 Location TBD (US or Sweden) April 2008 (Finalize Model) Before US DoD Enterprise Architecture Summit (14-18 April 2008) Between formal meetings – bi-weekly telecons, blogs/wiki, share site, and as-needed emails and phone calls to arrange and conduct experiments Brief Final IDEAS Model at DoD EA Summit

National Updates UK US MODAF 1.1 released at beginning April More capability oriented Metamodel aligned with UML 2.1 NATO adopting metamodel – some changes to support them J6 staff working on modeling of casualty tracking and have a pilot in mind – more detail once officially released Info management people (ICAD) have an ontology pilot using the IDEAS model also work in the logistics area using ontology to align taxonomies Establishing governance for MODAF and M3 SOA related activities getting greater focus, including developing an EA/SOA/IDEAS demonstrator. Looking at a logical open SOA services construct US CADM v1.5 and DODAF v1.5 released in April DODAF v2.0 input being sought now – expect about a year effort from here – IDEAS members invited to the workshops US DoD EA Conference was held in April– briefings on the web at KzoWebcasting.com/DoDEA

National Updates (Cont.) CA Stakeholder review of DNDAF v1.0 complete DNDAF official v1.0 to pilot due to happen in next few months. RFP out for EA toolset, expected to have evaluation finished very soon AUS Meetings with J6 – pace of operations, and TS07 planning, is limiting the available time for them to meet and be involved Repository development continuing (Rochade, fed by System Architect) test environment now in place – review about to happen of approach to repository development Mapping SA metamodel and Rochade model for CADM to support XML data exchange between them – ongoing work DSMS upgrade project just starting – v1.5 due out late this year Training course revisions complete, new materials and enhanced facilitator guides now in use. Pilot of Diploma course about to occur DAF review planned for Q3/4 07 SW Still keen to be involved in IDEAS as interoperability is key NAF V3 seems to be on schedule New temp frame work/directions for EA in SWAF

MODAF Update MODAF v1.1 and M3 v1.1 was released in April 07 with web based documentation. Has incorporated a lot of the NATO requirements – NAF v3 due in December will be an updated version of M3 with SOA related changes. New version is available on www.modaf.org.uk Version 2 is due for development and release by mid 2008 Recent work showing human functions in SVs Have a draft Spectrum Management View (for NATO purposes)

AUSDAF Update Intent to start a user community forum including industry partners – still planned, little progress due to resource issues With DODAF/MODAF/NAF updates mostly released now planning is in process for a full review and update starting Q3 07 for intended new release in Q1 08 Review will include changes to documentation structure to better align with DODAF/MODAF/NAF chapter structure

DNDAF Update Stakeholder review complete and v1.0 formally released. RFP to choose and acquire EA tools at evaluation stage with result expected by end May 07 Have developed an online tutorial and quick reference guide – about to be published Planning to develop training courses – reusing some of the AUS developed course material

DODAF and CADM Update DODAF v1.5 is released DODAF v2 will be a larger shift towards a net centric framework DODAF v2 development workshops starting soon and will continue over the next 6 months DODAF v2 due for release approximately March/April 2008 All volumes available on https:\\dars1.army.mil CADM v1.5 is released

Model Experimentation First experiment, exchange architecture data regarding the processes, agents, information flows, and sequences of activities involved in Battlefield Human Casualty Management. Using Canadian document as “test data”

Exchange Across Coalition Tools and Frameworks SA XML Import (Update logic) EE XML Export (ALL) Telelogic System Architect® SQL Query RDFS Database IDEAS Data Exchange Format (RDFS) IDEAS RDFS Generate Parse

Exercise Concept Identify a scenario where exchange of architecture planning data across the Coalition aids: Planning for interoperability, e.g., processes, organizations, and/or systems Identification of interoperability issues before they happen in a real operation Better synchronization of forces in real operations

www.ideasgroup.org