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

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

3. Working Group Attendees
Frits Broekema
Fariba Hozhabrafkan
Mikael Hagenbo
Lars-Olof Kihlström
Olaf Kruidhof
Bill Tracey
Michael Wayson
Chris Partridge
Ian Bailey
Doug Wilson
Dennis Healy
Michael Wong
Stephen McCarthy
Dave McDaniel
Francisco Loaiza-Lemos
Gaetan Tremblay

4. 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
1830 Dinner

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

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

7. Meeting Outline Objectives Proposed Activities The Plan - Daily CONOPS
Master Schedule
Status
Aims
Review of Accomplishments

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

9. Proposed Activities
Chart the path to complete the development of the IDEAS Model.
UK and US can 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 Member Nations discuss and act to invite Sweden to formally join the Group as a full member.
Look for broader group to take responsibility for Exercise
Operational experts
Current systems experts
Exercise experience
i.e., much more than just a data model activity

10. The Plan-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 telecom 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.

11. Maturity Matrix Sample
Shows handful started in telecoms

12. Current Master Schedule

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

14. IDEAS Model Status at start of Apr 08 Meeting (Cont.)
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)

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

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

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

18. AUSDAF Update (Cont.)
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 CA DNDAF/DADM V1.0 were completed and released in Sep 07.
DNDAF/DADM V1.5 (small enhancement) will be released in April 08.
Development of DNDAF Documents
DNDAF Vol 1: Overview and Definitions
DNDAF Vol 2: DND/CF Views and Sub-views
DNDAF Vol 3: DADM
DNDAF Vol 4: Users Guide
DNDAF Vol 5: EA Management and Services
Development of EA Programme Governance Structure
Providing EA support/guidance to projects

20. DNDAF Update (Cont.)
Working on a pilot project BICES (Battlefield Information Collection & Exploitation System) to validate DNDAF & DADM.
Providing training and education on DNDAF.
Implementation of DNDAF/DADM into System Architect was completed.
CANFORGEN (Canadian Forces Generate) Order issues use of DNDAF and DADM for all new DND/CF Projects.
DND/CF Corporate EA Tools license RFP issued to industry.
Planning development of DND/CF EA Reference Models.
Development DNDAF/DADM V2.0, expect about a year effort, include Business, Capability views and SOA concept.

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

22. Uses IDEAS Foundation and Common Patterns

23. DoDAF 2.0 Meta Model (Version 0.1) Overview

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

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

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

27. Program of Work Schedule
April 2008
Orlando, FL.
Future Meetings: Sep 08, London, UK

28. Management Meeting Actions
The Group made the decision to invite Sweden to join the IDEAS Group as a full member. Mr. Wayson will send the invitation to Sweden.
The group undertook and accomplished the updating of the Terms of Reference and the Concept of Operations during the sessions.. The new updates are under review by the management group.
All agreed they needed to better understand where we are in the process and where we are going and how we are going to get there. All need to show their management how the IDEAS work has bearing and influence on individual National work. This is important if IDEAS is to continue to receive support and funding.
All stressed the importance that the individual national views were incorporated in the IDEAS development.
All agreed we needed to better define: where IDEAS is going, where we are, how are we going to measure progress, and how we are going to complete the model.

29. Working Group Daily Activities
IDEAS Meeting Activity Flow
 Day 1
 1. Interesting Points from last week’s DoD EA Conference:
Korea Institute for Defense Analyses KIDA ) shows interest in joining the IDEAS WG. The request is under review by the Chair.
Germans shows interest about the IDEAS work, and they will contact Mike upon this matter.
 2. Sweden to be invited to become a full member of the IDEAS WG.
 3. Experimental Exercise perspectives:
CBMJ6
CWID
Looking for a broader group to take responsibility
IDEAS sole responsibility is to do modeling
IDEAS model will be validated by operators for integrity and usages
 4. IDEAS activities:
Small group (Ian, Dave, Steve & Chris) will focus on IDEA modeling and share the work with nations was discussed.
Funding:
UK has to reuse the things developed in the IDEAS for MODAF
US will reuse the things out of IDEAS to support DoDAF
Nations will require more funding to support the IDEAS activities
BORO methodology is used to define a unify understanding for nation’s framework
UK:
Replace M3 with some of IDEAS foundation
Use M3 exchange in UPDM
MODAF v1.2 is released
US:
DoDAF v2.0 moves to UML, easier to describe concepts
US uses federated repository
DARS is only a registry

30. Working Group Daily Activities
Sweden:
Officially adopted MoDAF/M3
Lead on EU NEC feasibility study
Buy in model driven capability approach
EU NEC is responsible by EDA (Europe Defence Agency)
EDA framework of choice may be MoDAF, being under review
NATO:
Working on NATO repository, preparing a pilot using UML (Sparkx)
Tool vendor exhibits will take place in May
Working on OA (Over Arching Architecture) v3.0
Metadata model management will be leaded by UK
IDEAS model:
Foundation is completed, documentation is not completed ?
Common Pattern completed:
Before after
Overlap
International object
time
Common Pattern under discussion:
Measure
Object exchange
representation
5. Management’s focus for this week:
Need to show Senior management the deliverables, (i.e. ,COP, models)
Need know where we stand in details (work plan, what is needed)

31. Working Group Daily Activities
Develop a work plan
Maximize nation’s activities
Formulated ROD for funding
Need modeler input in order to help defining the scope of COP
6. The major focus of the Domain Package/Subject Area:
Location (CA, UK, US AU)
Measure (UK, US)
Capability (CA, US, UK)
Day 2
7. UK MOD Ontology Demo (by Ian):
Using IDEAS pattern to demonstrate location over Google Map. MOD customized the application to make it work (Ian said 10 days). The application can support more than one location. Postal code can be used as input as well .
8. The modeling team started to work on these subject areas:
 Location;
RealPropertyStructure
GeoPoliticalArea
Measure

32. Working Group Daily Activities
9. New objects included into the IDEAS model “Foundation”: disjoint, intersects (Set Theory).
Quality Assurance method was developed to validate the 400 objects in the IDEAS model as reported by US.
Doug (AUS) volunteered to work on this action item.
 Day 3
10. Reviewed the subject areas to determine their completeness:
 number
Signed off
Need QA
numerals
measure
Working in progress
Capability
Started to build
Location
12. GeoSpacetial point concept was discussed in details between US and UK. Intentional construction and Non-intentional construction, Lat., Long.

33. Working Group Daily Activities
Day 4
Continued to reviewing the subject areas :
Capability
Decision to define specific capability models to satisfy each nation’s requirements (US, CA, UK, AUS)
These models were considered completed based on nations consensus. Further development can be carried out internally by each nation to meet it’s need.
AUS will review UK, US, and CA models before building it’s own
A general Capability model was also developed for the Enterprise Architecture perspective.
Speed and Velocity
Partially built
Chris required more time to develop the detail pattern
Dave drafted the following models;
JSEAD Individual
JSEAD Type
Duration

34. Capability Development Roadmap
Activities for 2008 and 2009          
Update of the TOR
Operational Concept Document Development
Approach Development
Scenario Development
Method Selection
-Foundation
-Common object pattern development
-Domain / Subject Area
First data exchange experimentation
Second data exchange experimentation
Application of the pattern to the scenario
Second scenario development
Application of the patterns to the second scenario
Finalization of the patterns
Documentation of the models and patterns
Prove of Concept / Operational Exercise
End of Development Phase

35. Management Group Wrap-Up
Fariba Hozhabrafkan, representing the UK, was select as the next Chairperson of the IDEAS Group.
The next IDEAS meeting is scheduled for Sep in London, UK
The Group stressed the importance of the Bi-Weekly telephone/WEB meetings to ensure continue progress on the model.