130 likes | 298 Views
Enterprise Architecture in Defence. Katie de Bourcier Director Information Exploitation 24 th Feb 2009. A non-technical perspective on EA. It’s about Understanding the business Sharing that understanding Seeing how we can do our business better It helps in making decisions about
E N D
Enterprise Architecture in Defence Katie de Bourcier Director Information Exploitation 24th Feb 2009
A non-technical perspective on EA • It’s about • Understanding the business • Sharing that understanding • Seeing how we can do our business better • It helps in making decisions about • Structures • Processes • Human factors • Information solutions • Or any other aspect of the organisation or activity • It’s a means to an end – does it pass the “so what” test?
Defence – the Challenge • Changing nature of the threat – international terrorism – demands a joined-up response across: • The three Services and the MOD Civil Service • Government • Allies and coalition partners • Continuing pressure to improve departmental efficiency and focus resources on the front line • Drive to increase departmental effectiveness • Capability Review in 2007, re-review currently underway • Internal transformation programmes
Information is the Key • Effective management, assurance and exploitation of information recognised as fundamental to achieving Defence objectives • Integrating sensors, decision-makers, and weapons in the battlespace • Increasing interoperability nationally and internationally • Optimizing the use of resources in a robust operational support structure • Improving information-sharing and decision-making in the non-operational environment • Ensuring effective performance measurement and a clear audit trail for decisions and actions • A new Government Knowledge and Information Management strategy – “Information Matters” – launched November 2008
Enterprise Architecture in Defence • EA in Defence has been developing since 2004 – • Prompted by the Network Enabled Capability Programme • Original focus on equipment acquisition and support domain, with a strong systems engineering focus • MODAF developed as the MOD’s architecture framework • Recognition that this was not full use of the potential of enterprise architecture to put technical solutions in the context of business objectives, strategy and process • Set up programme to promote wider exploitation of EA – pilot projects carried out to test the concept • Now seen as key part of future role of the MOD CIO
Casualty Information Management - Background • Pilot project to evaluate EA to address real issue of managing information about operational casualties from the battlefield back to NHS hospitals in the UK • Complex: • Global • Multinational • Multiple agencies • Multiple stakeholder perspectives (eg clinical, personnel management)
The Approach • Strategic goals and approved doctrine used to model the “As should be” architecture • Observation in the field used to derive the “As is” process • Analysis used to develop a proposed architecture for improved casualty information management • Proposals validated with medical and other stakeholders
HQ ISAF RC (SOUTH) KANDAHAR UK COMMAND HQS FORWARD OPERATING BASES ISAF RC(South) J3/J4 Med Ops HQ Kandahar Battle Group HQ Permanent Joint HQ MOD Centre / DCMC Patrol Commander Combat Medical Team UK MEDICAL AND WELFARE ORGANISATIONS Welfare Co-ord NSCCC Innsworth ROLE 2 FACILITY – CAMP BASTION Combined Military / NHS Hospitals (UK) Medical Emergency Response Team Role 2 Field Hospital National HQ RC(South) HQ Kandahar STRATEGIC AIR MDU Selly Oak AeroMed Evacuation Medical Care Rehabilitation Headley Court Casualty Tracking Pilot Study
Outcomes from the Pilot • Replacement field hospital system developed and rolled out quickly (47 days) – continuity from outgoing system • Required architectures (business process and technical solution) must be developed in a coherent manner • People are critical to the process - wall to wall IT is not always the best solution: • Post-it notes on a white board visually more effective than laptops • Satellite phones made medical evacuation tasking more effective - allows in-flight reprioritisation
MODAF • Developed by the MOD from US DoDAF - extended and modified to support EA approach to planning and change management in MOD. • Provided the template against which NATO Architecture Framework version 3.0 has been developed. • Now used by a wide range of government and industry organisations . . .
Who Uses MODAF ? UK Ministry of Defence & its suppliers Thales, BAE Systems, Lockheed Martin, Serco, Boeing, General Dynamics, etc. etc. Intelligence Services GCHQ and others National Air Traffic Control (NATS) Swedish Armed Forces Critical National Infrastructure UK e-borders project Adapted by NATO to become NAF Rev 3 MODAF has since moved on with the release of v1.2 V1.2 uses the same SOA meta-model elements as NAF