1 / 30

Enterprise Architecture in the Ministry of Defence

Enterprise Architecture in the Ministry of Defence. Colonel Luigi Gregori Deputy Head Enterprise Architecture . Agenda. Strategic Context Where We Are What We Are Doing What We Are Planning To Do A Few Words on MODAF Some Parting Thoughts. Strategic Context.

magda
Télécharger la présentation

Enterprise Architecture in the Ministry of Defence

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Enterprise Architecture in the Ministry of Defence Colonel Luigi Gregori Deputy Head Enterprise Architecture

  2. Agenda Strategic Context Where We Are What We Are Doing What We Are Planning To Do A Few Words on MODAF Some Parting Thoughts

  3. Strategic Context

  4. Ministry of Defence Information Strategy (MODIS) 2009 • Defence Information Vision “Agile exploitation of our information capabilities to improve effectiveness and efficiency on operations and in support areas through access to, and sharing of, timely, accurate and trusted information.” • Delivery of Defence Information Vision is articulated in terms of four effects: Strategic Alignment Information Exploitation Accessibility and Trust Value For Money

  5. MODIS Strategic Alignment Effect – Enterprise Architecture Element “Establish and Evolve a Coherent Defence Enterprise Architecture” CIO Priorities: Act as the EA champion within Defence Develop MODAF and associated policy Support Process Owners with the development of EA to support their business processes Process Owner and TLB responsibilities: Develop EA for their functional scope . . . achieve coherence with overall Defence EA MODIS roadmap has end 2011 as the target for “develop EA”

  6. Enterprise Architecture (Sub) Strategy • Vision “A coherent federated Defence Enterprise Architecture to deliver effectiveness through understanding.” • Delivering the Vision • Policy – what CIO needs to mandate • Process and Framework – what needs to be provided to enable a federated enterprise architecture to emerge and to promote interoperability • People – what skills are needed and how they can be provided • Communications – getting the right message to the right people

  7. Enterprise Architecture Strategy- Process and Framework • Ministry of Defence Architecture Framework (MODAF). • Mandated in MODIS • Coherence with other frameworks to support information sharing • Manage the development of the framework to meet the business and user requirements. • Tools • MODAF compliant • Information sharing between architectures modelled in different tools

  8. Enterprise Architecture Strategy- Process and Framework (continued) • Architecture Patterns • Index of architecture artefacts to enable sharing and reuse of Patterns • Process • Plain English description of how to undertake Enterprise Architecture using MODAF

  9. Where We Are

  10. Use of EA continues to grow within MOD and over the past year we have been seeing its use in two buckets:

  11. Systems Engineering • Bucket 1 – Systems Engineering • Requirements management • Integration activities • Systems of Systems, support for TLCM Programmes (and Projects) • Provisioning operational capability • A more successful bucket!

  12. Supporting Business Transformation • Bucket 2 – Supporting Business Transformation • Clarify and communicating the strategic intent • Business Analysis • Process Improvement – strong drive for efficiency and savings • Supporting delivery of transformation in business and IS • A more difficult bucket……

  13. What We Are Doing

  14. Systems Engineering Bucket 1 Improvement Activities System of SystemsApproach led by SEIG and KSA, supported by CIO EA ways of working, governance, tools, policies, skills etc. Providing focused support in areas of key interest – e.g. ISTAR Domain Architecture Developing MODAF which provides a robust framework for Systems Engineering purposes

  15. Supporting Business Transformation (1) • Bucket 2 Improvement Activities • Finding that MODAF and Enterprise Architecture language is too ‘Geeky’ for the business audience, awkward to use and not intuitive… • Financial pressures mean the Business must improve, must do more for less. EA can help by providing clarity so we must promote EA for the Business better. • Process Owners – responsible for laying down the E2E process for their function.

  16. Supporting Business Transformation (2) • Two key enablers: • Developing a High Level Process for architectural support to business change • Working to upskill architects in MOD – identifying competences and conducting a TNA • Zachman EA Frameworks • Providing focused support in areas of key interest

  17. What We Are Planning To Do

  18. Implementing the EA Strategy and leveraging off current activities to ensure: Business Relevance Usability MODAF stability through regulation of updates

  19. Business Relevance • Demonstration of the benefits of the Enterprise Architecture by addressing areas of core concern to the MOD

  20. Usability • Providing an EA Framework (i.e. MODAF plus process plus guidance, etc) that is understood and can be used by all business areas of the MOD. Development of: • Generic process; • Rule book and Style Guide (with SEIG SOSA); • Plain English communications pieces; • A competence framework and training needs analysis for EA in MOD; • Shared access and reuse of existing architecture work

  21. MODAF Stability • MODAF version 1.2 unchanged since April 2008 to provide users (and tool vendors) with a stable environment to develop against. • However, recognise the need to balance stability with requests for change, particularly to support: • Emerging user requirements • Coherence with other frameworks • Coherence of MODAF implementation in tools • MODAF changes therefore need to be addressed in a controlled manner, and on a routine basis (e.g. annual updates) so stakeholders know when to expect change.

  22. MODAF Changes - 1 • MODAF version 1.2 stabilised since April 2010. • A number of minor changes are now being implemented to address changes requested by: • Users – business requirement. • Tool Vendors. • NATO Architecture Framework (NAF) Management Syndicate – to support alignment. • Principle remains to keep changes to a minimum to keep MODAF stable.

  23. MODAF Changes - 2 • Ports on SV-1 • Numerous minor fixes to examples • Minor fixes and additions to M3 (mostly descriptions and errors) • Numerous clarifications and fixes to documentation • Add new view for service composition • Add security aspects to MODAF • Add materiel and people flows to OV-3, SV-1, OV-5, SV-4, SV-6, OV-6c, SV-10c

  24. MODAF Coherence • Coherence with other Frameworks: • NAF Chapter 5 (NAF Meta Model) aligned with MODAF Meta Model in 2009. • International Defence Enterprise Architecture Specification (IDEAS) • Aus, Can, Swe, UK and US – NATO as observers • High-level model for Aus DAF, DNDAF, MODAF, DODAF and perhaps NAF • Tools: • Unified Profile for DoDAF and MODAF (UPDM) 2

  25. Some Parting Thoughts Business relevance Usability Modellers and Architects

  26. Top Down Architecture Development in support of Investment Managers, Scrutinisers, Strategic Decision Makers, Process Owners Operations/Business Information FEDERATION System Information Business Enterprise Architecture Technical Information Bottom Up Architecture Development in support of System Implementers, System Integrators, Software Developers

  27. Questions?

  28. Contacts: www.mod.uk/modaf Assistant Head Architecture Framework: Patrick.Gorman429@mod.uk

More Related