1. International Defense Enterprise Architecture Specification (IDEAS)
Meeting 01/08
Agenda and Record of Decisions
21 Apr – 25 Apr 08

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

3. Agenda Monday 21 Apr Tuesday 22 Apr 0800 Welcome - Opening remarks
All-Hands Management Meeting: Where we are now and where do we want to be? – The PLAN to complete the Model
Summary of Modelers Bi-Weekly meetings: Progress to date – All
Break
Update on National EA Programs to include any DODAF, CADM, MODAF and M3 updates.
Review of action items from the Sep 07 meeting.
Lunch
Principals Management Meeting to discuss resources, level of effort, future meetings, best way to move forward
1300 IDEAS Modeling/Experiment Modeling Start
1500 Break
1515 IDEAS Modeling/Experiment Modeling
1645 Wrap up of days activities
1700 Adjourn
Tuesday 22 Apr
Welcome / Housekeeping / Recap of previous day / today’s aims
0815 IDEAS Modeling/Experiment Modeling
0930 Break
0945 IDEAS Modeling/Experiment Modeling
1200 Lunch
1300 IDEAS Modeling/Experiment Modeling
1515 IDEAS Modeling
1645 Wrap up of days activities

4. Agenda Wednesday 23 Apr Thursday 24 Apr 0800 Welcome and Housekeeping
Recap previous day/ aims for today
0815 IDEAS modeling
0930 Break
0945 IDEAS modeling
1200 Lunch
1300 Management meeting / Future roadmap dates
1400 IDEAS modeling
1500 Break
1530 IDEAS modeling
1645 Wrap up of days activities
1700 Adjourn
Thursday 24 Apr
Recap previous day / aims for today
0945 Break
1000 IDEAS modeling
1300 IDEAS modeling
1515 IDEAS modeling

5. Agenda Friday 25 Apr 0800 Welcome and Housekeeping
Recap previous day / aims for today
0815 Finalize IDEAS modeling for this session
0915 Break
0930 Finalize IDEAS modeling for this session
1130 Agree on actions and future schedule
1200 Close meeting

6. Meeting Outline Objectives Proposed Activities Status Aims
Review of Accomplishments

7. Major objectives Per TOR
Deliver a specification for the exchange of architectural documentation and artifacts between coalition partners for the purpose of Coalition Military Operations.
To establish an oversight mechanism to perform configuration control activities.
To identify and approve all key activities and milestones required for the accomplishment of the Working Group’s goals.
Define, agree, and implement a technical approach for IDEAS testing.
Evolve the high level classes with all attributes and relationships that ensure a cohesive exchange infrastructure to meet the major goals and objectives.

8. Proposed Activities
Chart the path to complete the development of the IDEAS Model.
UK and US will take the lead for the development. The Working Group can monitor and review via the Web Site and by updates and can participate in the scheduled telephone conferences.
US and UK have resources available now to accomplish the work. Future resources are not guaranteed so the time to quickly move forward is now.
Propose the Working Group discuss and act to invite Sweden to formally join the Group as a full member.
Look for broader group for Exercise, e.g.,
Operational experts
Current systems experts
Exercise experience
i.e., more than just an data model activity

9. Daily CONOPS
The goal is to work towards the completion of the Model according to the Master Schedule – this is not a tutorial or review session!
Completion requires:
Baseline Current Model
Need full pass on Maturity Matrix – 400 items to review and judge – need to do ~ 100 items per day
Good forum for those coming up to speed on model or wanting a full view
Small group work on known incompletion issues -- pick ~4 daily topics for the week, e.g.,
Capability
Measures
Location
Training / Skill / Education
Object Exchange / Flow
Record “rabbit holes” in Action Item Excel list, assign someone(s) for further off-line investigation and report-out at telecon or next meeting, and move on
Bring each daily topic and baseline list to close at end of each day and debrief at end of day

10. Maturity Matrix Sample
Shows handful started in telecons

11. Current Master Schedule

12. IDEAS Model Status at start of Apr 08 Meeting
Foundation still well defined
Namespace pattern sufficiently well defined for current testing
Still need to finalize 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 organization/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.

13. IDEAS Model Status at start of Apr 08 Meeting
OV-5 Activity Whole-Part
Design complete
Exchange experimentation:
OV-5 Operational Nodes Activity
Design completed
Started OV-4 Command Relationship
Design sketched
OV-5 Information Flow
Design completed other than cosmetic
Started OV-6c Event Trigger
Design sketched (duration and causality TBD)
Completed IDEAS Project AV-1
Updated Experiment plan (GANNT chart)

14. Aims of Meeting
To confirm and agree on the changes made to the Model since the last meeting as a result of the work in the bi-weekly telephone sessions.
Identify and prioritize the remaining IDEAS development activities and issues with the goal of completing work on the model.
Confirm 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.
Confirm schedule of activities beyond Apr 08.

15. DoDAF 2.0 Meta Model (Version 0.1) Overview

16. Uses IDEAS Foundation and Common Patterns

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

18. AUSDAF Update
Director Architecture Support, Kim Lambert, has left Defence – DAS ‘Under New Management’
AUSDAF Review has commenced with a comparative review of allied architecture frameworks
1st Stage involves highlighting the need/generating support/to conduct a full AUSDAF review
AUSDAF Review development strategy / program governance structure/funding stream/WIP
NCWPO funds DARS development program
Defence cutbacks are causing resource issues for Architecture support in general.
Training review to be coordinated with AUSDAF Review.
Training demand continues to increase.
DAS continues to coordinate the DIE architecture assessment program
DAS interacts with other areas involved with semantic interoperability (CSIRO, DSTO)
DAS joins the Network Centric Operations Industry Consortium (NCOIC)
DAS initiates collaboration activity with US Turnkey Program

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

20. DODAF Update
DoDAF 2.0 being developed in four “spirals” to be completed by Nov 08
Analysis of requirements to support DoD’s core processes: budgeting, acquisition, capabilities development and integration, systems engineering, portfolio management, and operations planning
Spiral II release in Mar 08 included first version of DoDAF 2.0 Conceptual Data Model
Used IDEAS Foundation
Domain derived from many sources
Working on refinement and logical model attributes
Coordinating with OMG UPDM FTF

21. Sweden Update
Decision on using MODAF in the Swedish Armed Forces (SwAF) will be signed by SwAF Joint CIO on April 25.
New assignments to FMV in place. Due to Swedish Procurement Laws contracting consultants is expected to take a few months further.
Expected governmental positive decision on participation in IDEAS gives SwAF a mandate to extend our level of contribution in IDEAS in the future.
Piloting the use of MODAF/M3 in capability development for EU BG 2011 (see next slide).
Decision on Sweden taking a leading role for EU NEC Feasibility Study (see coming slide).

22. Swedish Armed Forces Headquarters from 1 April 2007
Supreme Commander / Director General
Chief of Staff Armed Forces
Internal Audit
Safety Inspectorate .
Dept. CO HQ
Develop-
ment.
Manage-ment
staff
Inter-
national
Plans &
policy
Business-
Develop.
CIO HQ
Surgeon General *
Dept.
Military
Intelligence
& Security
Directorate
Operations
Directorate
Training &
Procurement
Directorate
Director
Personnel
Director
Budget & Finance
Director Legal Affairs
Director
Public Relations
Strategic Operations
Staff
Operations
Tactical
Component
Commands
Army, Navy, Air Force
Inspectors
Personnel
Staff
Budget &
Finance
Staff
Legal
Affairs
Staff
Information
Staff
Plans
Training
Procurement
Army, Navy, Air Force
Command & Plans
Logistics
National Home Guard
Voluntary Forces
International training & testing
Public/Private Coord.
Command & Plans
Intelligence
Security
Development
Administration
Overall responsibility for SwAF EA – Mrs. Mia Arblom
Overall responsibility for SwAF EA AF + International co-operation – LtCol Mikael Hagenbo ( *)
Governmental
superintendence
Deployed
units
Units, schools, centres
and operational units
Overall responsibility for implementing SwAF EA from a capability perspective – LtCol Thomas Niclason

23. Coming work: Force and capability development within EU
EU NEC Feasibility Study
EUMC
EUMS
EDA
Force Development: The core process of developing forces for the future and providing the organisational units within the process of realising the future. This also includes contingency planning and development of doctrine and can be considered in the same context as capability planning.
Force Planning: The process of determining the availability of national forces and capabilities for the full range of EU missions.
Capability Development: The process by which capability planning is translated into new or enhanced capabilities to carry out required tasks.
Capability Planning: This method involves a functional analysis of operational requirements to meet concurrency assumptions for operations. Capabilities are identified based on the tasks required. Capability planning also identifies related progress objectives in this domain.
Framework of choice: MODAF ?

24. Program of Work Schedule
April 2008
Week after US DOD EA conf (14-18 April) in Orlando, FL.
Future Efforts are TBD

25. BACK UP MATERIAL

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

27. IDEAS Model Status at start of Apr 08 Meeting
Identified and agree the set of issues/areas of the model needing further work.
That the IDEAS data exchange will use the XML Syntax (most likely RDF). Use common leverage to get more vendors to be aware/helpful and compliant with Defense organizations requirements.
Recognized that the agreement by NATO and others 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 set of views for the initial testing of data exchange (testing to be done by UK/US) (OV2, OV3, OV5, OV6c, OV7, SV1, SV4, SV6) and agreed to start on OV5.

28. Experiment ’08 GANNT

29. Revisit Objectives Existing: New:
To deliver a specification for the exchange of architectural documentation and artifacts between coalition partners for the purpose of Coalition Military Operations:
Establish an oversight mechanism to perform configuration control activities.
Identify and approve all key activities and milestones required for the accomplishment of the Working Group’s goals.
Define, agree, and implement a technical approach for IDEAS testing.
Evolve the high level classes with all attributes and relationships that ensure a cohesive exchange infrastructure to meet the major goals and objectives.
New:
xxxAF support
UPDM
NAF
National ontology initiatives, e.g., US UCORE

30. Use Case Design: Initial Idea – Compare Doctrines
Went down this path for a while but then,…
Looking at recent CM “lessons learned” led us a different way, e.g.,
Scud missile attack on US barracks near end of Desert Storm

31. Better Use Case Design
EA Datasets
Lessons Learned

32. Some Possible Courses of Action
Mission Complete – Dis-establish Group
Energize Model Development
How?
Prepare for Handoff to ???

33. Continuing Program of Activities
Complete the development 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
Prepare for Exercise in FY09