International Defence Enterprise Architecture Specification (IDEAS)

1. International Defence Enterprise Architecture Specification (IDEAS) Meeting 01/2007 Record of Decisions 5 to 9 March 2007 Canberra, Australia

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 • Develop the models for sample planning 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 (probably based on XML technologies (using OWL at present)) • Co-exists as part of each nations architecture repository solution • Develop the repository data exchange mechanism

4. Agenda • Monday 5 • 0830 Setup and housekeeping • 0845 Welcome – John Sheridan ASIAM • 0900 Update on National EA Programs • 1000 Break • 1030 Review of action items from the October meeting • 1100 Ontology Workshop – UK Ian Bailey • 1200 Lunch • 1300 J6 requirements and Scenario – UK Sqn Ldr Steve Bradbury • 1500 Break • 1530 Aims of this meeting • 1545 Review Status of IDEAS model – Ian Bailey • 1600 – 1700 IDEAS modeling • Tuesday 6 • 0830 Welcome/Housekeeping • 0845 recap of previous day/ today’s aims • 0900 IDEAS modeling • 1000 Break • 1030 Update on management meetin • 1045 IDEAS modeling • 1200 Lunch • 1300 IDEAS modeling • 1500 Break • 1530 DODAF and CADM update • 1630 meet AUS Defence community • 1730-1830 Meet and greet function

5. Agenda Wednesday 7 • 0845 Welcome and Housekeeping • 0845 Recap previous day/ aims for today • 0900 IDEAS modeling • 1000 Break • 1030 IDEAS modeling • 1200 Lunch presentation – Thales – ‘Industry perspective on issues working with Defence EA Frameworks’ • 1300 IDEAS modeling • 1500 Break • 1530 Daily wrap up • 1600 Social Event – tour to Tidbinbilla Deep Space Communications Centre Thursday 8 • 0845 Welcome and Housekeeping • 0845 Recap previous day/ aims for today • 0900 IDEAS modeling • 1000 Break • 1030 IDEAS modeling • 1200 Lunch presentation – Sparx Systems Enterprise Architect software • 1300 IDEAS modeling • 1500 Break • 1530 IDEAS modeling • 1630- 1645 Daily wrap up • 1830- 2200 Social Event – Dinner Cruise on Lake Burley Griffin Friday 9 • 0845 Welcome and Housekeeping • 0845 Recap previous day/ aims for today • 0900 Finalise IDEAS modeling • 1000 Break • 1030 Document current status and discuss future work • 1200 Lunch • 1300 Agree actions and future schedule • 1400-1430 Close meeting

6. Review of Action Items from October 2006 meeting • Each IDEAS management rep to liaise with J6 in their nation re actual comms /data transfer needs for real world situations – identify a scenario which means something to them so that we can show IDEAS affect on that. – Good progress – UK J6 representative at March IDEAS meeting, CA have J6 Liaison allocated, AUS J6 engagement continues. • CA to advise asap if they can host the meeting the week following the US DOD EA conference next year (conf week of 23 to 27 April 07, IDEAS week of 30 April to 4 May 07) – Canada have confirmed hosting the meeting in Ottawa. • UK to continue to tidy up the model from this weeks meeting and circulate as V 0.4 – A number of ‘tidy up sessions’ have occurred and a revised version has been circulated. The name pattern has been completed and needs review. UK have done some work on OWL (Ontology Web Language) translation.

7. Aims of meeting • To confirm the agreed definition of the top level ontology • To identify scenarios, based on J6 input, for ongoing IDEAS modeling • To identify any changes/additions needed to the model based on J6 requirements. • To review previously addressed scenarios with J6 input and amend as necessary • To model, to initial level, at least one J6 identified scenario • To identify specific tasks remaining to allow the functioning of the demo at CWID 07 • To identify any other scenarios suitable for addressing in the near future

8. 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 • derive model from agreed operational constructs • provide complete semantics

9. National Updates (1) • UK • EA work is accelerating almost exponentially • Establishing governance for MODAF and M3 • Have good 3 and 4 star buy in for use of EA in support of addressing coalition in theatre issues • Information Assurance activity using the SABSA methodology • Defining roles and responsibilities for MOD EA delivery • Use of Sharepoint with Webparts for Strategic Knowledge Information Portal (SKIP) (20061030 - SKIP N JC2sp - U (2).ppt) • SOA related activities getting greater focus, including developing an EA/SOA/IDEAS demonstrator (to be used at CWID 07). Looking at a logical open SOA services construct. • MOD Transformation activity using EA to work through the transformation, leading to more work with the business areas on business architectures • US • Not a lot of progress with J6 yet • Progress on CADM 1.5 and DODAF 1.5 to be briefed separately • DODAF 1.5 at full release end March 07 • Registry development ongoing

10. National Updates (2) • CA • Good progress with J6 – a J6 liaison to EA/IDEAS has been allocated • C2 projects showing strong interest – want EA guidance – now involved in using DNDAF for a number of projects as a pilot • Senior management support is improving • DNDAF official V1.0 to be released approx April – now in stakeholder review. • Model guidance, in the form of a tutorial quick reference guide, to be in next few months and made web available • RFT out for EA toolset, expected to have evaluation finished by April 07 • Looking at repository once toolset is chosen • Organising an internal, plus an industry involved , DNDAF working/user group • Considering having an annual Defence Nationale EA conference similar to the US DoD one • 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 • Mapping SA metamodel and Rochade model for CADM to support XML data exchange between them – ongoing work • Training course revisions complete, new materials and enhanced facilitator guides now in use • DAF review planned for Q3/4 07 • SW • EA work being moved to come under Supreme HQ management – better support. • Considering using MODAF rather than NAF v3 • New activity to develop a description of SWAF as a whole (effectively business architecture) • Still keen to be involved in IDEAS as interoperability is key

11. IDEAS Model Status at start of March 07 meeting • Foundation well defined • Namespace pattern at initial definition • Still need to do patterns for Event, Time and Tuple Type • 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 • Intentional construction pattern clarified • Document pattern clarified • 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

12. MODAF Update • MODAF next release will be end March 07 with web based documentation and a new version of the meta model to support that. • Pre release version is available on www.modaf.org.uk for IDEAS group review only – please do not post any comments.

13. AUSDAF Update • User feedback from training courses being assessed – needs for change in the framework being captured • Intent to start a user community forum including industry partners – still planned, little progress due to resource issues • Will wait for DODAF/MODAF/NAF updates before finalising any significant change • Intent to review for major change Q3 07 • Review will include changes to documentation structure to better align with DODAF/MODAF/NAF chapter structure

14. DNDAF Update • At stakeholder review before formal release of V1.0 • RFP to choose and acquire EA tools at evaluation stage with result expected by April/May • 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

15. DODAF Update • Net Centric concepts defined and DODAF 1.5 revised to support them and to support SOA • 1.5 is released, but is transitional, v2 will be a larger shift towards a net centric framework • New sub views added to support net-centricity • Improvement in consistency of volume presentation and alignment of the details in them with other strategic documents • Presentation by Francisco Loaiza (DoDAF_progress_report_06MAR07.ppt) • V2 still potentially planned for 2008 • Vol 1 – guidelines and definitions, Vol 2 product descriptions, Vol 3 architecture data management • Vol 3 draft provided now (DAF1 5_Volume III_FINAL DRAFT v1.0 - 01-17-2007.pdf) • All volumes available on https:\\dars1.army.mil

16. CADM Update • CADM 1.5 to be released with DODAF 1.5 (1.03 is current) • Presentation from Francisco Loaiza(CADM_progress_report_06MAR07.ppt) • 1.5 takes 1.03 and addresses complexity issues and aligns with DODAF 1.5 better • Supports repository • Reduced number of entities and relations • Increased number of business rules • Has explicit versioning • Streamlines specifications • Is backwards compatible – 1.02/1.03 data sets can be represented in 1.5 • Methodology changes • New supertypes • Entities part of taxonomies • Only essential 1.02/1.03 modeled explicitly • Intent to align with DODAF evolution to ensure that data layer is consistent and accessible in representing concepts • Reduces number of entities relationships and attributes to about 20% of 1.03 (down to 135 entities), and adds metamodeling and Business rules to guide use • Incorporates Net-Centric requirements and remains backwards compatible for mapping business rules and processes • Review workshops completed in Feb 07, Model IDEF 1x and UML drafts ready

17. Update on Tasks needed to allow the CWID demo to operate • Definition of a small number of scenarios which are commonly understood by all nations easily • The current scenarios planned by UK for use will all have some use of, or basis in, IDEAS developed functionality • The casualty management scenario, which has been worked on this meeting, will also likely be used • UK will provide a ‘marketing document’ which describes the CWID 07 demonstrator and the use of IDEAS within it.

18. Achievements this Meeting • Adoption and initial scoping of the casualty management scenario based on UK J6 input. • Clarification of patterns documented last meeting, and in the intervening time • Modeling of objects required for the casualty management scenario (more refinement will be required). This scenario has been identified as requiring a wider scope of modeling than previous scenarios reviewed. Good progress has been made in this area • 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

19. WG Decisions • Adopted the casualty management scenario as a vehicle to further test and demonstrate the IDEAS model • Selected a target set of views for the initial testing of data exchange (testing to be done by UK) (OV2, OV3, OV5, OV6c, OV7, SV1, SV4, SV6) • Progress the scenario work with the intent of having scenarios useable for the demonstrator capability at CWID and similar.

20. Actions from WG Meeting • Each IDEAS management rep to continue to liaise with J6 in their nation re actual comms /data transfer needs for real world situations – each to identify a scenario which means something to them so that we can show the IDEAS affect on that. • UK (Ian) to investigate the possible use of a UML profile for IDEAS to enable auto generation of OWL from EA files. • Each nation to discuss the casualty management scenario with their relevant staff to better understand the issues involved • AUS to reword the OCD draft to include the scenario work and reissue for comment before next meeting. • All to contribute to the OCD content before next meeting. • UK to continue to tidy up the model, incorporating all of the refinements, additions and changes from this week’s meeting and circulate as V 0.4 • UK to provide ontological review of the changes developed during this meeting

21. Management Meeting • It was agreed that • The OCD for the IDEAS work, and other ‘project management’ style documentation for the program of work, should be continued based on the AUS developed draft OCD, with all to add to the documents before the next meeting • That phases to this work be clearly identified to allow planning of deliverables. Agreement on first set of deliverables to be reached at next meeting. • The casualty management scenario provided by UK J6 staff should be pursued as an example which is valid for all nations and crosses coalition boundaries in the field • As each nation reviews or creates policy for architecture, content should be circulated between IDEAS members (where classification allows) to ensure that our approaches can be made to converge wherever possible to ensure improved future interoperability • As agreed last meeting, the demonstrator that UK are building for CWID (for EA and SOA) will use the IDEAS work as a basis and that the IDEAS group will work to facilitate the success of that demonstrator. This will have a coalition ops planning emphasis and will be aimed at producing material which can be used in a future ‘practical EA use in Planning’ tutorial. The work this meeting will enhance the scenarios to be used. • Future meetings will continue to be timed, where possible, in close proximity to other activities of interest (eg US DoD EA Conferences) to minimise travel costs for all. • The aims of the meeting in Canberra, and the future program of work were confirmed.

22. Program of Work Schedule • April 30 to May 4 2007 • Ottawa, Canada • Meeting will occur following the US DoD Enterprise Architecture Conference (San Diego, 24-26 April 07) • 10 to 14 September 2007 • London • February/March 2008 • Location TBD (possibly US)

23. Things to resolve • Equivalence/alias (needs Chris’ input) • Ian’s concerns with fusion approach to end to end agreement (needs Chris’ input) • Mailing lists will be developed – core participants as a separate list from ‘other interested parties’