1. International Defence Enterprise Architecture Specification (IDEAS)
Meeting 03/07
Record of Decisions
10 Sep – 14 Sep 07
London, England

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

3. 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
Execute experiments and demonstrate at EA conference
Prepare for Exercise in FY09

4. 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 (export to RDF)
derive model from agreed operational constructs
provide complete semantics.
Participants will fully document all aspects of the model and methodology for the IDEAS capability.

5. Agenda Monday 10 Sep Tuesday 11 Sep 0930 Opening remarks – Welcome
1000 Group Discussion with Mr. George Wauer - OASD(NII)
Review of action items from the Apr 07 meeting; Detailed aims of this meeting
1100 Update on National EA Programs to include any DODAF,CADM, MODAF and M3 updates
Lunch
Coalition Battle Management Command and Control (CBMC2) – Joint Close Air Support (JCAS) Environment and Initial Roadmap project discussion
1400 Summary of Modelers meeting - Ian Bailey and all
1500 Break
1515 Review of progress on initial experiment model - Dave McDaniel and all
Review Status of IDEAS Model with a view to refine and complete – Chris Partridge and Ian Bailey
1645 Wrap up of days activities
1700 Adjourn
Tuesday 11 Sep
Welcome / Housekeeping / Recap of previous day / today’s aims
0945 IDEAS Modeling/Experiment Modeling
1030 Break
1045 IDEAS Modeling/Experiment Modeling
1200 Lunch
1300 IDEAS Modeling/Experiment Modeling
1515 IDEAS Modeling
1645 Wrap up of days activities

6. Agenda Wednesday 12 Sep Thursday 13 Sep 0930 Welcome and Housekeeping
Recap previous day/ aims for today
0945 IDEAS modeling
1030 Break
1045 IDEAS modeling
1200 Lunch
1300 Future roadmap dates
1330 IDEAS modeling / Management meeting (in Parallel)
1500 Break
1530 IDEAS modeling
1645 Wrap up of days activities
1700 Adjourn
Thursday 13 Sep
Recap previous day / aims for today
1300 Update on management meeting
1330 IDEAS modeling
1530 IDEAS modeling / Management meeting (in Parallel)

7. Agenda Friday 14 Sep 0930 Welcome and Housekeeping
Recap previous day / aims for today
0945 Finalize IDEAS modeling for this session
1030 Break
1045 Document current status and discuss future work
1200 Lunch
1300 Agree on actions and future schedule
1330 Close meeting

8. Reviewed Action Items from May 2007 Meeting
All to continue engagement with J6 staff and with G6/medical or Health Services staff to clarify the casualty management scenario requirements. CONTINUING ACTION
All to provide input to the OCD as soon as possible. CONTINUING ACTION
All to identify other documents that are needed (especially plain English explanations/guidelines to the IDEAS work) and circulate for agreement – volunteers to write the docs required – US (Francisco) will draft object definitions and UK (Chris) pattern use descriptions. CONTINUING ACTION
All management reps to write up an approx one page summary of the way ahead for IDEAS from their nation’s perspective (with any additional comments on issues, way ahead for the architecture frameworks etc) and circulate by early July to allow creation of a strategy paper before the September meeting. COMPLETED
All – volunteer required to ensure that the Casualty Management Scenario is written up as a plain English ‘story’ to assist with informing others of what we are addressing. CONTINUING ACTION
US to arrange an agenda slot in next years UD DoD EA conference for the IDEAS ‘launch’. DONE
UK to provide a copy of the letter sent to UPDM. DONE; WILL RESEND
UK will create a collaboration space for the IDEAS members on DONE
UK to tidy up the model to complete adjustments made at this meeting and circulate ASAP. DONE
UK to put links to national (and NATO) framework sites on the IDEAS website. DONE
UK to advise hotel and meeting arrangements for the September meeting. DONE
AUS to provide an updated version of the draft OCD to be put on the IDEAS website. DONE

9. Aims of meeting
To confirm and agree on the changes made to the model since the last meeting.
To confirm and agree on the changes made to the Experiment.
Identify and prioritize the remaining IDEAS development activities and issues.
Continue development of a simple demonstrator which can be run on a laptop and used to show results of this work to senior management.
Finalize the identification of the work required to allow the finalisation of a working model and simple demonstrator.
Agree the baseline for the scope of the casualty management scenario to be addressed, in the light of the data gathered by UK staff in the MEAO and model those aspects.
To continue definition of the exchange mechanism, using the M3 model, CADM, and the selected modeling tools.
Confirm schedule of activities to Apr 08 and beyond.

10. IDEAS Model Status at start of Sep 07 meeting
Foundation still well defined
Namespace pattern sufficiently well defined for current experimentation
Still need to finalise patterns for Agent overlap with Process, Information Element Export/Import, Event/Trigger, Duration, and Command Relationship.
Data for OCD 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.

11. National Updates (1) UK US MODAF 1.1 released
Metamodel aligned with UML 2.1
NATO adopted metamodel – some changes to support them.
J6 staff worked on modeling of casualty tracking and have completed a pilot
Establishing governance for MODAF and M3
Continued update of the M3 and development of MOD Ontology for further enhancement of the Model.
SOA related activities getting greater focus, including development of an EA/SOA/IDEAS demonstrator showing federation of SOAs, which was successfully demonstrated during the CIWID 2007.
Development of MODAF/EA Primer in conjunction with Swedish Armed Forces. US
CADM 1.5 and DODAF 1.5 release a package April 07
DODAF 2.0 input being sought now – expect about a year effort from here – IDEAS members invited to the workshops
Next DoD EA Conference is 14 Apr 08 in Orlando, FL
Plan to present IDEAS Model Demonstration at that time

12. National Updates (2) CA AUS SW
Stakeholder review of DNDAF V1.0 complete – Translating into French before official release
Internal team review of DADM v1.0 complete, will be released at the same time as DNDAF v1.0
A Network pilot project is set up with stakeholder to validate DNDAF and DADM. The stakeholder will select a small set of sub-views to develop based on stakeholder requirements. The timeframe to complete this pilot is four to six months.
A write up of the Canadian DND roadmap document was provided to Aus to update the OCD.
AUS
SOW about to be issued to contract staff review and update of DAF to take into account the current state of the other nations frameworks and to ensure convergence
Ongoing resourcing issues for Architecture support in general
Updating Policy, Doctrine and Governance which supports DAF
Utilizing stakeholder working group to accomplish
Working group will also provide input to DAF review and update
Training planning is ongoing to ensure that training stays aligned with DAF current version
Training demand continues to increase
Management requirement for ‘IDEAS Implementation Plan’
Interaction with other areas doing ontology/semantic interoperability based work (CSIRO, DSTO)
OCD requires update for demo and exercise SW
Still keen to be involved in IDEAS as interoperability is key
NAF V3 being presented this week in Brussels
New temp frame work/directions for EA in SWAF

13. MODAF Update
MODAF v1.1 and M3 v1.1 was released in Apr 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
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).

14. 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.

15. DNDAF Update
Stakeholder review complete and V1.0 will be formally released after French translation.
DNDAF will be used for a pilot project to validate its usage.
Have developed a quick reference guide, and will be released after French translation.

16. DODAF and CADM Update
DODAF 1.5 and CADM 1.5 was released as a package together
DODAF v2 will be a larger shift towards a net centric framework
DODAF v2 will support major DOD decision processes
JCIDS
PfM/CPM
System Engineering
PPBE
Operations Planning
Defense Acquisition System
DODAF V2 development workshops started
DODAF V2 due for release approximately Nov 08, with interim releases in between

17. Achievements this Meeting
OV-5 Activity Whole-Part
Design complete
Exchange experimentation:
OV-5 Operational Nodes Activity
Design completed
OV-5 Information Flow
Design completed other than cosmetic
Started OV-6c Event Trigger
Design sketched (duration and causality TBD)
Started OV-4 Command Relationship
Design sketched
Did IDEAS Project AV-1
Updated Experiment plan (GANNT chart)
Clear and confirmed agreement of the areas of the IDEAS work needing review/change/enhancement and of their priorities, to facilitate the definition of future work packages and deliverables.
Defined Process, Information Element and Agent patterns.
Development of test OV 5 and initial experimental data for the casualty management scenario.
Clarification and confirmation of the patterns documented last meeting, and in the intervening time.
Initial definition of XML requirements for the casualty management scenario.
Identification and development of necessary mappings to the foundation model based on analysis of OWL and best practice modeling techniques.
Information added to the OCD from Sweden (will require review before the next meeting).
Development of a draft experiment schedule for the OV5 exchange.
Modeling of objects required for the casualty management scenario (more refinement will be required).
Good progress on the IDEAS model development as a whole.
Better common understanding of the future development paths for the individual nation’s frameworks to ensure that structures converge to deliver greater interoperability.
Review of national frameworks directions for Interoperability.

18. WG Decisions
Identified and agree the set of issues/areas of the model needing further work.
Scope items:
Transaction
Process
Agents
Services
Information Element
Event/Trigger
Stimulus/Response
Message
Sequence
Need to consider deleting the power-type box from the model.
Need to consider modeling tuple-places in each diagram. However the models become overly complex. (Chris and Ian to address).
Event Trigger – Pathological case No info. (Agreed to include this case).
Canadian concept of many-to-many between Process and Function in OV-5a and b. Possible semantic difference between MoDAF and DNDAF.
How attributes / properties handled in the IDEAS ontology has been resolved.
Recognised that the agreement by NATO to use the IDEAS exchange mechanism means that the IDEAS core model will need to grow over time to support the increasing demands of the various allies.
Updated the target datasets:
OV-5 Activity Whole-Part
OV-5 Operational Nodes Activity
OV-5 Information Flow
OV-6c Event Trigger
OV-4 Command Relationship

19. Actions from WG Meeting
All to continue engagement with J6 staff and with G6/medical or Health Services staff to clarify the casualty management scenario requirements.
All to continue to provide input to the OCD and other needed documentation as soon as possible.
Circulate and review electronic copy of Joint Experimentation, Test and Evaluation, and Advanced Concept Technology Demonstration (JETA) Integration Into Joint Training Manual
All to identify other documents that are needed (especially plain English explanations/guidelines to the IDEAS work) and circulate for agreement – volunteers to write the docs required – US (Francisco) will draft object definitions and UK (Chris) pattern use descriptions.
All management reps to write up an approx one page summary of the way ahead for IDEAS from their nation’s perspective (with any additional comments on issues, way ahead for the architecture frameworks etc) and circulate by early July to allow creation of a strategy paper before the September meeting.
All – volunteer required to ensure that the Casualty Management Scenario is written up as a plain English ‘story’ to assist with informing others of what we are addressing.

20. Program of Work Schedule
28 January – 1 February 2008
Location: Stockholm, Sweden
Key objective: prepare for April demo
April 2008
Week after US DOD EA conf (14-18 April) in Orlando, FL
Key objective: demo
Future Efforts are based on funding provided by each national representative and as described in AV-1

21. Things to resolve
Funding for continued effort and deployment of capability as described in AV-1

22. 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”

23. 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
BORO Logo

24. International Defence Enterprise Architecture Specification (IDEAS)
10 Sep – 14 Sep 07
London, England