1. Name of entity 1

2. The Singapore Ministry of Defences Corporate IT (CIT) Approach to Enterprise Architecture Lim Han Chiew Programme Manager, DSTA Masterplanning and Systems Architecting

3. Name of entity 3 Disclaimer Views expressed in this presentation are solely that of the speaker's and shared in the spirit of knowledge exchange They do NOT necessarily represent MINDEF's views

4. Name of entity 4 Presentation Agenda Motivation for Enterprise Architecture The MINDEF Enterprise Architecture Framework MINDEFs Business Transformation Approach Leveraging on Model-Driven Architecture Technology Challenges, Lessons Learnt and Benefits MINDEF – Ministry of Defence, Singapore

5. Name of entity 5 Brief Overview of the Singapore Ministry of Defence (MINDEF) MINDEFs Mission To enhance Singapores peace and security, and should deterrence and diplomacy fail, to secure a swift and decisive victory over the aggressor Conscript Armed Forces –2-year National Service for all males at age 18 –350,000 Active, NS and Regulars –Reserve Service Annual duty of up to 40 days till age 40-45

6. Name of entity 6 MINDEF & SAF Mission Areas Cross-Mission Area Forum Governance via SAF Forums Governance via MINDEF CIO Forum Operational Mission Area (OMA) (Command & Control Domain) Corporate Business Mission Area (CBMA) (CIT Domain) Defence Information Infrastructure Mission Area (DIIMA) (IT Infra, KM, etc.) SAF - Singapore Armed Forces

7. Name of entity 7 Motivation for Enterprise Approach - The Enterprise System (ES) for Logistics Towards Effective Integration of Business, Processes & Information across MINDEF and the SAF. A cost-effective common business ecosystem that works coherently and can adapt to changes quickly as a whole. Joint Logistics MIS

8. Name of entity 8 Enterprise Process Harmonisation & Standardisation

9. Name of entity 9 MINDEF Success Story in EA - ES Achieved a high degree of standardisation of processes > 90% common across all three Services and Joint Units –Streamlined operations and saved > $80m in IT capital costs –Created a strong Corporate/Tri-Service data environment –Enhanced process integration & information interoperability Achieved significant gains in combat effectiveness and operational efficiency through the adoption of commercial best business practices and common, integrated, end-to-end business processes Provided the starting point for developing a shared information environment across MINDEF/SAF Similar approach to be taken for other Enterprise-wide projects eg. e-HR

10. Name of entity 10 MINDEF CIT EA Journey Laying the EA Foundation Driving Business Transformation Building Up Architecting Capability Towards Enterprise Integration FY2006FY2008FY2007FY2009-10 iMBT Common Modelling Language EA Reference Models EA Repository & Tools CARAT (EA Framework) CARAT - ACtionable ARchitecture FrAmework for MINDEF CIT

11. Name of entity 11 Learning from the Building Industry Vision The Building & Construction industry has effectively bridged the gap between business requirements and implementation through very mature and concise engineering practices

12. Name of entity 12 Business-IT Alignment Gap Business Architect's Views System Engineer's Views Vision ?

13. Name of entity 13 Transform the Business First Business Architect's Views System Engineer's Views Vision Transform and Improve the Business Processes first before IT Investments

14. Name of entity 14 EA Driver - Business Transformation Map Common Architecture Language OV-0 OV-5 OV-6 SVs

15. Name of entity 15 Common Architecture Modelling Language - Minimal Set Business Architect's Views System Engineer's Views Vision OV-0 OV-1 OV-5 OV-2 OV-3 OV-6 OV-7 SV-1 SV-2 SV-4 SV-6 OV-4 SV-11 TV-1 OV-0: Defence Business Map OV-1: Concept of Operations OV-2: Ops Node Connectivity OV-3: Info Exchange Reqts Matrix Info Exchange Structure OV-4: Organisation Structure Chart OV-5: Ops Activity Model OV-6: Ops Activity Sequence & Timing OV-7: Logical Data Model SV-1: Systems Interface SV-2: Systems Communications SV-4: Systems Function SV-6: Systems Data Exchange SV-11: Physical Schema TV-1: Technical Standards Profile Recommended Views Core Views

16. Name of entity 16 Business-IT Alignment OV-0 Defence Business Map OV-5 (What) Operational Activity Model OV-6 (How) Operational Activity Sequence & Timing Descriptions Technical Model Implementation Tier Business Reference Model

17. Name of entity 17 AVATAR (EA Repository) Common EA Repository

18. Name of entity 18 EA Directive - Effective 1 Apr 08 Policy for Development and Management of CIT EA * States the role of Business Owners in the overall CIT EA planning and development * States the role and delivery of Ops Manager and Project Management Team in project development * Specifies the list of architecture models to be delivered * States the Governance and Compliance Requirements

19. Name of entity 19 Architecture Views Submission Requirements

20. Name of entity 20 The Integrated Methodology for Business Transformation (iMBT) Stakeholders Tools & Template Process

21. Name of entity 21 IT Governance Structure Defence Business Map

22. Name of entity 22 OV-0 Defence Business Map Single High Level View of MINDEFs Line of Business (LOB) for Investment Prioritisation and Identification of Opportunities for Cross-LOB Collaboration Line of Business Functions / Capabilities

23. Name of entity 23 OV-5 Activity Models OV-0 OV-5 OV-6 2nd-level OV-5 OV-5 Activity Node Tree 1st-level OV-5 OV-0 Business Value Chain showing the inter-dependencies among business functions and the stakeholders involved IDEF0 Notation

24. Name of entity 24 OV-6 Activity Sequence & Timing Descriptions OV-0 OV-5 OV-6 OV-5 EPC Notation OV-6 Detailed business processes showing how business operations are to be conducted

25. Name of entity 25 MINDEFs Business Transformation Governance Structure

26. Name of entity 26 The Integrated Methodology for Business Transformation (iMBT)

27. Name of entity 27 Business Transformation Projects in 2008

28. Name of entity 28 Value Proposition: Reuse Logistics & Finance Business Processes Building & Infra Business Processes Medical Business Processes 30 Scenarios reused out of 35 Scenarios 18 Scenarios reused; 5 to be enhanced 114 Scenarios AVATAR

29. Name of entity 29 Moving Forward - Executable Architecture Business - IT Alignment AVATAR

30. Name of entity 30 Model-Driven Architecture - From AVATAR to ORACLE

31. Name of entity 31 Model-Driven Architecture for CIT Environment

32. Challenges in the EA Journey Establishing and institutionalising a new architecture language has helped but buy-in is difficult to sustain –Frequent changes in leaderships and operation managers –Value of EA models to the business and technical people is not always apparent –Ownership and update of the EA models remain a problem –EA tool limitations and integration gaps impede acceptance –New business analysis competency needed EA Tools are important but they also present problems due to their limitations

33. Name of entity 33 Lessons Learned in the EA Journey Governance –There is a risk of over-governance with too many forums –Submission of the EA views and the governance process need to be closely integrated with the system development process Architecture Modelling –The choice of the model notation is important. Some are more difficult to visualise and comprehend –Setting up a central modelling facility was a good way to bring the EA models together but the effort is seen as separate from the system development process

34. Name of entity 34 Benefits of the EA Efforts Despite the challenges, the following benefits were achieved: –The formal top-level management structure has ensured that there is executive support –The lower level governance structure put in place was able to facilitate the needed business-IT alignment –Achieved reuse of business processes resulting in cost savings –The common architecture language has helped to facilitate understanding across all stakeholders

35. Name of entity 35 Way Ahead Focusing on Enterprise Integration –Develop the Enterprise Data Reference Model –Develop the Service Reference Model –Develop the Performance Reference Model Strengthening the current EA Foundation –Improved Governance and Compliance Realising the Model-Driven Architecture approach in system developments

37. Name of entity 37 iMBT Phase 1

38. Name of entity 38 iMBT Phase 2

39. Name of entity 39 iMBT Phase 3

40. Name of entity 40 New Competencies and Roles OV-6