1. International Defence Enterprise Architecture Specification (IDEAS)
Meeting 04/2006
Record of Decisions
23 to 27 October 2006
Washington, DC, USA

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 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)
Co-exists as part of each nations architecture repository solution
Develop the repository data exchange mechanism

4. Agenda
Monday 23
Welcome
Review of action items from the June meeting
Update on management meeting
Aims of this meeting
National Updates
Break
Framework Updates NAF, MODAF, AUSDAF, DNDAF
Lunch
IDEAS model progress review and refresher on BORO methodology
Tuesday 24
DODAF and CADM update
IDEAS WG meeting
Dinner Cruise on the Potomac
Wednesday 25
IDEAS WG meeting
Thursday 26
Friday 27
Finalise modeling and definition work for this meeting
Lunch
Document current status and discuss future work
Agree actions and future schedule
Close meeting

5. Review of Action Items from June 2006 meeting
UK MOD will develop and propose the top level ontological model to be used as the 80% solution based upon the results of this meeting and the 0.3 IDEAS model – good progress has been made but was delayed by funding issues.
Using the approved methodology, clean up 0.3 version of the IDEAS model – some progress
National representatives will identify and provide additional operational scenarios for further model development – little progress
Validate proposed IDEAS meeting schedule – generally agreed, but changes to Canada representation may change locations

6. Aims of meeting
To agree on the required final content for the top level ontology
To complete the definition of the top level ontology
To review the Communications scenario work in the context of the ontology and amend as necessary
To identify specific tasks required to allow the functioning of the demo at CWID 07
To begin work on the Logistics scenario
To identify any other scenarios suitable for addressing in the near future

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

8. National Updates (1) UK US
Funding and activity moratorium caused a delay – it has recently been lifted for EA after a months delay
MODAF and metamodel review going well with good input
Defining future program of work for MODAF and metamodel at present (changes to OV2 and SV1 and SV6 likely plus services views)
Changes will go into NAF as well as MODAF
UK is adopting an ontological approach to all EA work
Looking at a federated repository
Developing an EA/SOA/IDEAS demonstrator (to be used at CWID 07) US
Not a lot of progress with J6 yet
Progress on CADM 1.04 and DODAF briefed.

9. National Updates (2) CA AUS SW
Little progress with J6 due to staff changes
C2 projects showing strong interest – want EA guidance
Aiming to use this strong interest to improve senior management support
DNDAF and model guidance to be published soon
AUS
Meetings with J6 – pace of operations is limiting the available time for them to meet and be involved
Repository development continuing (Rochade, fed by System Architect) review of approach in progress
Mapping SA metamodel and Rochade model for CADM to support XML data exchange between them
Training course development continues SW
Organisational reviews – new chain of command for the architecture work - good support still
Have used the EA work in a number of activities with good response from Generals

10. NATO Update
Draft TORs exist for NATO Architecture Board exist but no final decision has yet been made to form this or where it might sit in the structure. (AMB TOR.doc, AMG TOR.doc)
NC3 Board has asked all Nations if they can provide something to fast track NNEC – Sweden will possibly work with UK on demonstrator and use that

11. NAF Update
NAF v3 revision – 7 nations, NC3A and Info sec community – 13 meetings, 5 workshops so far – all suffering from resource constraints
Ontology workshop 6-8 Feb 07
Syndicate meetings
27-28 Feb 07
26-27 April 07
31 May-1 June 07
Uses AV, OV, SV, TV, capability view, services view and program view
Final expected Q2 07 (at draft .9 now)
Has 7 chapters and 3 annexes
Presentation provided by Frits Broekema ( NAF update IDEAS.ppt)
Metamodel is currently based on MODAF M3 v1 and has not yet had all NATO extensions added
MODAF and NAF Metamodels are converging
Development plan for NATO metamodel – see MM Development Roadmap v1.0.ppt

12. MODAF Update Proposals with MODAF Technical Committee
Changes to OV2 to allow for future architectures which are a combination of ‘to be’ and of existing systems which must be retained
Changes to SV1 – make it more of a solutions view – can show people and covers DOTMLPF better
Maybe hybrid SV4/OV5 to cover system human connections
All based on user requests

13. AUSDAF Update
User feedback from training courses being assessed – courses being updated and needs for change in the framework being captured
Has a placeholder for data Views but they are not implemented
Intent to start a user community forum including industry partners
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 very early stages
Pretty much identical to DODAF except for System view (has SV10a, b and c)
Use CV like AUS does rather than AV
Has info view, strategic view and security view that DODAF doesn’t
Looking at OV7 and SV11 linked by IV
Current first priority is to choose and acquire EA tools
Looking to get users to validate the framework and model
Planning to develop training courses – reusing some of the AUS developed course material
Starting to look at possible ‘human view’
Intranet portal in development

15. DODAF Update Direction to make DODAF ‘more Net Centric’
As part of the ‘computing infrastructure strategy’
Presentation by Brian Wilczynski (DOD-EA-CONFERENCE_BREAKOUT-SESSION-FULL-BRIEF-Wednesday.ppt)
DARS, Guidance, Update of product descriptions etc, documentation update, federated architectures, more SOA relevant capability
Net Centric concepts defined and DODAF 1.5 revised to support them
V2 planned for Q1 2008
1.5 is transitional, v2 will be a shift towards a net centric framework
Vol 1 – guidelines and definitions, Vol 2 product descriptions, Vol 3 architecture data management
DODAF Working group – anyone commercial or otherwise is welcome even if they are not currently working on a DoD project
All 3 Vols at 1.5 out in draft in mid Jan 07. Vol 2 draft provided now (DODAF1 5_Volume II_DRAFT_13SEP2006_FINAL2.pdf)
Upgrading guidance doco to improve answering ‘how do I do that’ questions

16. CADM Update CADM 1.04 coming (1.03 is current)
Presentation from Francisco Loaiza (CADM 104 Overview for IDEAS.ppt)
1.02 to 1.03 improved the consistency of naming of physical specs
1.04 takes 1.03 and addresses complexity issues
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.04
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 and adds metamodeling and Business rules to guide use
UML version complete in Sparx EA, plus XMI file
Erwin version complete
Main report and business Rule document drafts complete
Applicability of this approach will be assessed as this is adopted and the path for future versions determined from that

17. Tasks needed to allow the CWID demo to operate
Limited dictionary of synonyms and homonyms
Definition of a small number of scenarios which are commonly understood by all nations easily
the initial scenario used as a focus for the work is “Country A needs to carry out an action in a coalition AO. Country A does not have resources on the ground to deliver the action. Country A sends a request to Countries B and C asking what they have that can meet the spec needed – this request is an architectural definition of the need, delivered in IDEAS format (converted from their own format). Countries Band C pick it up in IDEAS format, push it into their own format, make the assessment of what they can supply, push the response back into IDEAS format. Country A collects the response in IDEAS format, pushes it back into its own format and assesses the best fit for the need.”
Make scenarios clearly show that the IDEAS format provides a method of describing data which can then be transferred to and understood by any allied nation. It does not make decisions or define actions – it is a data transfer descriptive interchange format and mechanisms for supporting interoperability between different formats.
Define the core ontological patterns needed for the demonstrator
Define the architectural data elements needed to be transferred

18. Achievements this Meeting
Modeling the patterns for Standards and Agreement and System
Modeling of the links which bridge System and technical Views
Discussion and basic agreement that Interoperability can be defined by a profile of Standards and represented using the standards pattern
Defining the ontological patterns required to support the data exchange for the planned CWID demonstration
Identification of a common need to have a mechanism to deliver data exchanged in the IDEAS format into each national architecture repository system
Review of national and NATO frameworks directions for Interoperability

19. WG Decisions
To limit the initial top level ontology to the foundation elements agreed at meeting 02 of 2005 (Myrtle Beach) (IDEAS Classes.xls)
To progress the scenario work with the intent of having scenarios useable for the demo at CWID 07
To further extend/populate the top level ontology only where the scenario work clearly identifies a need to do so

20. Actions from WG 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.
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)
UK to continue to tidy up the model from this weeks meeting and circulate as V 0.4

21. Management Meeting 20 October 2006 - Williamsburg VA
It was agreed that
An OCD for the IDEAS work, and other ‘project management’ style documentation for the program of work, should be produced. AUS agreed to develop some draft documents for circulation before the next meeting
A template for an MOU should be developed, for use when any other country wishes to join the IDEAS effort as observer, noting that full observer or participant status will only be available where a nation can bring real value to the work and is willing to actively commit resource effort.
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
Where a nation identifies an existing international project which may be able to use the IDEAS work, the contact lists will be shared to allow nations to co-ordinate effort better internally
The demonstrator that UK are building for CWID07 (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 invitation from the AUS Ops Planning staff to be involved in the planning process for Op Talisman Sabre 07 be accepted
Mailing lists will be developed – core participants as a separate list from ‘other interested parties’
Future meetings will 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 Washington, and the future program of work were confirmed.
The future schedule of meetings to be confirmed next week when Canada member is available

22. Program of Work Schedule
March
Canberra, Australia
April30 to May
Ottawa, Canada (To be confirmed)
Meeting will occur following the US DoD Enterprise Architecture Conference (San Diego, April 07)
Aug/Sept 2007
Location TBD – UK or Europe

23. Things to resolve Equivalence/alias
Ian’s concerns with fusion approach to end to end agreement