Скачать презентацию International Defense Enterprise Architecture Specification IDEAS Meeting 02 08 Скачать презентацию International Defense Enterprise Architecture Specification IDEAS Meeting 02 08

3dfc65bc834078d621c9b08619650ed2.ppt

  • Количество слайдов: 38

International Defense Enterprise Architecture Specification (IDEAS) Meeting 02/08 Agenda and Record of Decisions London, International Defense Enterprise Architecture Specification (IDEAS) Meeting 02/08 Agenda and Record of Decisions London, UK 15 Sep– 19 Sep 08

Working Group Participation • Member Nations: • • • Australia Canada United Kingdom United Working Group Participation • Member Nations: • • • Australia Canada United Kingdom United States Sweden • Observer Organizations: • NATO • Object Management Group (by MOD Rep) 2

Agenda Monday 15 Sep -- All 0900 Welcome - Opening remarks All-Hands Meeting: National Agenda Monday 15 Sep -- All 0900 Welcome - Opening remarks All-Hands Meeting: National updates Managers Bi-Weekly Status and Progress Dave Action Items from Apr 08 including Deferred Status and Progress Dave Maturity Assessment Rework Status and Progress Doug Model Changes Status and Progress Change Log Ian and Doug 1200 Lunch 1330 Do. DAF Meta Model Dave M 3 Ian UPDM DMM Ian COMPLETE IDEAS - MODAF SUBJECT AREA MAPPING Doug and Ian If not completed, map IDEAS Subject Areas to M 3. COMPLETE IDEAS - DODAF 2. 0 SUBJECT AREA MAPPING Doug and Dave Complete review of Subject Area mapping. Look at DM 2, compare, assess, against IDEAS model. Doug Review of updates with view towards meeting BORO standards Chris 1645 Wrap up of days activities and Adjourn. At times Management will meet separate from Modelers. 3

Meeting Outline • • • Objectives Proposed Activities Roadmap Status Review of Accomplishments 4 Meeting Outline • • • Objectives Proposed Activities Roadmap Status Review of Accomplishments 4

Draft Agenda Modelers: Tue 16 Sep – Fri 19 Sep (Subject to Change) Tuesday Draft Agenda Modelers: Tue 16 Sep – Fri 19 Sep (Subject to Change) Tuesday 0900 AM Services Frameworks, Examples, etc. Measure and Capability analysis Tuesday 1300 PM + Wednesday 0800 AM Services Modeling in IDEAS Welcome and Housekeeping and recap previous day / aims for today Look at Open Group Services Ontology, NATO Services taxonomy, OASIS, W 3 C, etc. Review Housekeeping and recap previous day / aims for today Need to cover business services, e. g. , search and rescue, restaurant, How does Transformation relate to Capability? Net-Centricity is important in U. S. Transformation. Wednesday 1300 PM RDF Mappings Thursday 0900 AM Measures Housekeeping and recap previous day / aims for today Issue of dispositions. Continue work on Measures at the Type level. Maybe another example that's an organizational measure (e. g. , cost or personnel skill level). Friday 0900 AM Capability Housekeeping and recap previous day / aims for today Particularly Capability taxonomy -- how differ from Process taxonomy, Effects, Actors? Reference NAF CV-1. Friday 1130 AM Wrap up of activities and Adjourn 5

Agenda MANAGEMENT: Tuesday 16 Sep – Friday 19 Sep 1. Topic Description Rationale Experimentation Agenda MANAGEMENT: Tuesday 16 Sep – Friday 19 Sep 1. Topic Description Rationale Experimentation What is the intended scope of the Experiment planned for May 2009? Experimentation definition required to support preparatory planning and related work plan definition. Maybe look into CWID. Look into open source, e. g. , Eclipse 2. Topic Description Rationale IDEAS Working Plan Update 3. Topic Description Status of Exchange Mechanisms MODX, UPDM XMI, DM 2 PES, IDEAS RDFS, NATO AEDM, NATO Meta Model 1. Comparison of exchange models 2. Way forward for cooperation Rationale 4. Topic Description Rationale Release into public domain for early adoption 6

Major Objectives Per TOR • Deliver a specification for the exchange of architectural documentation 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. 7

Proposed Activities • Chart the path to complete the development of the IDEAS Model. Proposed Activities • Chart the path to complete the development of the IDEAS Model. • Nations propose to accelerate the completion of version 1. 0 of the IDEAS model. • 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 8

 • Maturity Matrix Sample • Shows handful started in telecoms • Update the • Maturity Matrix Sample • Shows handful started in telecoms • Update the Action Items and the Maturity Model from the September 2008 Modeling meeting. (Doug) 9

Current Master Schedule This Master Schedule is subject to change, once the new work Current Master Schedule This Master Schedule is subject to change, once the new work plan has been agreed and funded. The UK will draft a proposed new timeline for competition and distribute it to members for approval. 10

IDEAS Model Status at end of Sept 08 Meeting • • • Foundation still IDEAS Model Status at end of Sept 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. Identified a number of implementation issues e. g. RDF/XSD. Capability model started and is about 75% complete. Measures / Performance Criteria started. Work on Services model will start once the definition of Services has been finalised by the Nations. 11

IDEAS Model Status at end of Sept 08 Meeting (Cont. ) • OV-5 Activity IDEAS Model Status at end of Sept 08 Meeting (Cont. ) • OV-5 Activity Whole-Part • Design complete • Exchange experimentation: • OV-5 Operational Nodes Activity • Design completed • Exchange experimentation: • Started OV-4 Command Relationship • Design sketched • Issues highlighted relating to Roles / Persontype / skills, which will need addressing. • OV-5 Information Flow • Design completed other than cosmetic • Started OV-6 c Event Trigger • Design sketched (duration and causality TBD) • Completed IDEAS Project AV-1 • Experiment plan (GANNT chart) needs to be updated with the new information, once that has been agreed. • Started SV-1 • Started stv-2 12

Aims of Meeting • To confirm and agree on the changes made to the 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 schedule of activities beyond Sept 08. 13

MODAF Update • MODAF v 1. 2 and M 3 v 1. 2 was MODAF Update • MODAF v 1. 2 and M 3 v 1. 2 was released in May 08 with web based documentation. • Has incorporated a lot of the NATO requirements – SOA Views added, and SOA elements integrated into existing views • New version is available on www. modaf. org. uk. • Cleaned up resources model in SVs – more in line with IDEAS and allows for better re-use 14

AUSDAF Update • Senior Officer Appointments and Changes within CIOG • ICT Strategy Development AUSDAF Update • Senior Officer Appointments and Changes within CIOG • ICT Strategy Development – supporting new Defence White Paper • AUSDAF Review continues: Phase 2: Req’s Development (BA 2015+) • Demonstrating AUSDARS Capability to Defence Executive • DAF, BPM and SA Training Delivery contracts being renewed 15

AUSDAF Update (Cont. ) • DAS continues to coordinate the DIE architecture assessment program. AUSDAF Update (Cont. ) • DAS continues to coordinate the DIE architecture assessment program. • DAS interacts with other areas involved with semantic interoperability (NICTA). 16

DNDAF Update • CA • DNDAF/DADM V 1. 5 were completed and released in DNDAF Update • CA • DNDAF/DADM V 1. 5 were completed and released in April 08. • Development of DNDAF Documents are on going • 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 is close to complete 17

DNDAF Update (Cont. ) • Working on two pilot projects BICES (Battlefield Information Collection DNDAF Update (Cont. ) • Working on two pilot projects BICES (Battlefield Information Collection & Exploitation System) & MUSIC (Multi-User Sensor Integration within Common Environment) to validate DNDAF & DADM. • Providing training and education on DNDAF monthly. • Interfacing DNDAF/DADM using System Architect. • DND/CF Corporate EA Tools license RFP issued to industry. • Development DNDAF/DADM V 2. 0, to include Business, Capability views and SOA concept are ongoing. • Reference model being defined for Operational Activities, Services, Application, and System Functions. 18

DODAF Update • Do. DAF 2. 0 being developed in four “spirals” to be DODAF Update • Do. DAF 2. 0 being developed in four “spirals” to be completed by Nov 08 • Analysis of requirements to support Do. D’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 Do. DAF 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 19

Uses IDEAS Foundation and Common Patterns 20 Uses IDEAS Foundation and Common Patterns 20

Do. DAF 2. 0 Meta Model (Version 0. 1) Overview 21 Do. DAF 2. 0 Meta Model (Version 0. 1) Overview 21

Sweden Update • The decision to use MODAF was signed by the Sw. AF Sweden Update • The decision to use MODAF was signed by the Sw. AF Joint Chief Information Officer (CIO), Rear Admiral (L. H. ) Thomas Engevall, on 15 May 2008. • Subsequently, both the Commander Armed Forces Headquarters/chief of staff Swedish Armed Forces, Lieutenant General Sverker Göransson, and the Director General of Defence Materiel Administration (FMV), Gunnar Holmgren, have committed their organisations to the changeover to model-based capability development using MODAF. • The pilot projects will be European Union Battle Group 2011 and the Swedish Defence Information Infrastructure. • Government decision on mandate for the Sw. AF to accept the invitation to become a full member of IDEAS was made 2008 -09 -11. The Sw. AF Joint CIO started the internal process to get the mandate to sign the TOR on behalf of the Sw. AF. 22

Sweden Update (Cont. ) Pilots FM LS / NII BG 11 2008 H MÅL Sweden Update (Cont. ) Pilots FM LS / NII BG 11 2008 H MÅL (Legacy) Sw. AF AF H MÅL NY (33%) Sw. AF AF 2009 2010 ”Sw. AF AF” Pilot Project Report Sw. AF AF 2011 2012 2013

Sweden Update (Cont. ) Some expected outcomes and benefits by transferring to model based Sweden Update (Cont. ) Some expected outcomes and benefits by transferring to model based capability development: • Possibilities for interoperability - a common framework facilitates cost effective information management and mutual understanding nationally and internationally. • Increased Traceability - could be achieve by connection the enterprise to a whole providing overview on how systems and sub-systems could interact with each other. • Governance – of whole or parts of systems can be simplified if responsibilities are made clear and if important parameters are identified. • Cost control - can be strengthened if the enterprise is structured and arranged so that possible economical advantages are identified. • Effectiveness - increases: • If influence by changes are immediately identified. • By the re-use and multi-use of Architecture data. • By common training and common usage of architecture as a tool.

Management Meeting Actions • Testing and Experimentation : TBD. At this time in the Management Meeting Actions • Testing and Experimentation : TBD. At this time in the development of IDEAS, the Exercise task is beyond the current capabilities of the Group and it should be deleted as a Group requirement and left to member nations to implement as they see fit or a broader group should be found to take responsibility for Exercise • Timing and Location of Accelerated Development : TBD. The UK will propose a schedule that will allow for completion of the model by Apr 09. • Core Modelers – Develop Final Product • All Modelers - Review of Final Product • All Models - Meeting to Finalize Product (if necessary) • Post IDEAS Working Group Objectives and Organization: TBD. After the Architecture Exchange Specification is finalized the members will consider transforming the Working Group into an Defence Enterprise Architecture Forum to continue to facilitate the exchange of architecture information among the member nations. • Future meetings : TBD. The next management meeting will be scheduled before the Jun 09 Enterprise Architecture Conference. 25

The Modellers Activities Monday • 0900 – 1400: Management Briefs • 1400 – on: The Modellers Activities Monday • 0900 – 1400: Management Briefs • 1400 – on: Capabilities and Measures and Effects or Dispositions and Manifestations Capability = ability to do something you want Effects Capabilities Manifestation of Outcomes Disposition (allowable state changes and causalities) Testimony

The Modellers Activities - Tuesday AM: Capabilities and Measures Examples • Making tea: • The Modellers Activities - Tuesday AM: Capabilities and Measures Examples • Making tea: • Outcome/Effect: Steve enjoying nice cup of tea • Task/Activity/Process: making tea • Resource: tea making thing (e. g. , kettle, teapot, cup, magic tea making device) • Measures: if kettle, 100 C; on outcome, Steve’s assessment of good tea Capabilities Disposition (possible future states or effects) Effects Manifestation of Outcomes Testimony

The Modellers Activities - Tuesday AM: Capabilities and Measures Examples Capability: Maritime Domain Awareness The Modellers Activities - Tuesday AM: Capabilities and Measures Examples Capability: Maritime Domain Awareness includes: 1. the ability [of the US Govt] to have awareness of maritime objects with 90% probability of detection under conditions of sea state < 6 2. the ability [same] to detect “threat” with 99% probability and 0. 001% of false alarm 3. Etc. … so as to have the effect that probability of attack on homeland ports is less than. 001% over 10 years. C 1. 2. 1. 3 Sea State Roughness of seas caused by wind or disturbances. DESCRIPTORS: Calm to slight (Beaufort Force < 5, Sea State 3 or less, seas 4 ft or less) Moderate (Beaufort Force 5, Sea State 4, seas 4 -8 ft) Rough (Beaufort Force 6 -7, Sea State 5 -6, seas 8 -16 ft) Very rough (Beaufort Force 8 -9, Sea State 6, seas 17 -20) High (Beaufort Force 10, Sea State 7, seas 20 -30 ft) Extremely rough (Beaufort Force above 10, Sea State above 7, seas above 30 ft) Capabilities Disposition (possible future states or effects) Effects Manifestation of Outcomes Testimony

The Modellers Activities - Tuesday AM: Capabilities and Measures Examples Force Application The ability The Modellers Activities - Tuesday AM: Capabilities and Measures Examples Force Application The ability to integrate the use of maneuver and engagement in all environments to create the effects necessary to achieve mission objectives. Engagement – The ability to use kinetic and non-kinetic means in all environments to generate the desired lethal and/or nonlethal effects from all domains and the information environment. Kinetic Means – The ability to create effects that rely on explosives or physical momentum (i. e. , of, relating to, or produced by motion). Non-Kinetic Means – The ability to create effects that do not rely on explosives or physical momentum. (e. g. , directed energy, computer viruses/hacking, chemical, and biological). Conduct Attack on Operational Targets Using Nonlethal Means To engage operational targets with nonlethal joint and multinational means designed to degrade, impair, disrupt, or delay the performance of enemy operational forces, tasks, and facilities. The means include the use of psychological operations, special operations forces, electronic attack, and other IO capabilities.

The Modellers Activities - Tuesday AM: Capabilities and Measures Examples The Modellers Activities - Tuesday AM: Capabilities and Measures Examples

The Modellers Activities - Tuesday more: Capabilities and Measures Examples • Also airman search The Modellers Activities - Tuesday more: Capabilities and Measures Examples • Also airman search and rescue • Strategic Mobility • Playing Shostakovich #5

Wednesday: Resource Model aligned across nations Wednesday: Resource Model aligned across nations

The Modellers Activities - Wednesday: Resource Model aligned across nations • Resources include: • The Modellers Activities - Wednesday: Resource Model aligned across nations • Resources include: • DLODs (GBR) • DOTMLPF (USA); SWE and NATO add an “I” for Infrastructure / Interoperability) • PRICIE (CAN) • FIC (AUS) • Cross-reference might be interesting

The Modellers Activities - Thursday: • Definitions scheme presented and US definition file provided The Modellers Activities - Thursday: • Definitions scheme presented and US definition file provided (new AI for Doug to take and apply) • “R” hell – Roles, Responsibilities, Requirements • On Roles, UK & CA use (CA -- along with Skills); US uses Person. Types & Skills instead • Non-name mapping – need to scope (new AI) • Issue on Roles vs Person. Types and Skills (new AI) • JPJ Colonial/Royal Navy and Led Zepplin example • Singleton type (a set with one member) issue (new AI) • Mixed place tuple. Type • Æ, {Æ}, {{Æ}}, {{{Æ}}}, {{{{Æ}}}}, … • RDF/XSD implementation (new AI)

The Modellers Activities - Friday: Counterpart discussion – will just be for examples (tutuorial The Modellers Activities - Friday: Counterpart discussion – will just be for examples (tutuorial material).

The Modellers Activities - Friday: Disposition – Manifestation • Draft of Capability model (new The Modellers Activities - Friday: Disposition – Manifestation • Draft of Capability model (new AI for all to review) • Tie in to Measures, Conditions, Rules, . . . and other parts of Do. DAF Capability after Dave cleans up DM 2 associations (new AI)

The Modellers Activities - Friday: • Action Item review and update: • Did huge The Modellers Activities - Friday: • Action Item review and update: • Did huge chunks of SV 1 • Did most of Capability (3/4 s) • Started measure / performance criteria – need to finish • Did OV 4 s (Role AI) • Did not investigate Service in details. • Agreed draft algorithm for definition.

Miscellaneous • US recorded 7 new DM 2 action items to take back home Miscellaneous • US recorded 7 new DM 2 action items to take back home