Distribution Architecture Review Feedback to Distribution IS

1. Distribution Architecture ReviewFeedback to Distribution IS 3 November 2000

2. Meeting Objectives Give you a ‘tour’ of the Model as it exists today Raise your awareness of the Model structure, capabilities, and contents (e.g. the standards) Agree ownership, access & use Discuss the handover and implementation Capture priorities, issues, suggestions for improvement, & initiate action plan Agenda Introductions Progress to Date Background Model Standards Key issues raised Implementation Processes Architecture Benefits Next Steps Distribution Architecture Review

3. Distribution Architecture ReviewFeedback to Distribution IS Introductions

4. Distribution Architecture ReviewFeedback to Distribution IS Progress to date

5. Background to the Review • History • Programme of Work review (Mike C, Howard G) January 2000 • IS reorganisation(s) • Business reorganisation(s) • Objectives • Reduce cost of IT ownership • Define IS Standards and Processes for the new IS organisation • Collate inventory of current technology base • Highlight key architectural issues and areas for improvement • Highlight any gaps in the coverage of the IS ‘life-cycle’ (as per ITIL) • Additional objectives • Align IS with Distribution business strategy • Create an accessible repository for this information

6. Initial Scope Applications currently supported by Distribution IS Information collected Applications processes supported Technologies hardware software data management Data model and flows Sources Application Support inventory questionnaire Y2K inventory interviews anything else available! Tools CASEwise repository diagramming MS Office data collection and input reporting Output HTML CASEwise model MS-Office documents (standards) The Model

7. G G R G A A A G R A A A G Standards - Position Today Operating systems Databases Middleware Communication protocols Development tools Business reporting tools Security Archiving, backup & restore Disaster Recovery System management tools Hardware platforms Development & Test environments Documentation

8. Database Management Availability Mgmt Capacity Mgmt Backup ……... .DOC Hyperlinks To Help Navigation DBMS - Oracle .DOC link to document link to document link to document link to document link to document Archive, Backup & Recovery .DOC Standards - Linking To The Model

9. Database Management Availability Mgmt Capacity Mgmt Backup ……... link to document link to document .DOC Hyperlinks To Help Navigation DBMS - Oracle .DOC link to document link to document Archive, Backup & Recovery .DOC Standards - Linking To The Model

10. Distribution Architecture ReviewFeedback to Distribution IS Key Issues raised

11. Issues - Architecture Review • Information has in many cases been hard to obtain • seen as an “extra” job, on top of existing workload • been asked many times before • the information is hard to find • elapsed time has therefore been > anticipated • Much of the Architecture is “owned” by the Programme, which is under review • have therefore concentrated on the Current architecture, but this is only part of the picture • little point in developing some standards until critical Programme decisions are taken • lack of information on pre production environments, though these are already impacting current operations

12. Issues - Distribution IS • IS Operations • set up as a Business As Usual (Production Operations) function • having to support full ITIL lifecycle e.g.: a map is required of the various operational and testing environments that need to be supported, & how they will evolve over time • new areas being added (Pre-Production) • there is a significant workload related to changes • there are gaps in the service provided by ITSU. • Process • Operational processes are being created “ground up” in response to immediate requirements.

13. Issues - ‘Life Cycle’ Coverage • Imbalance between Process Support for Owners and Contributors Service Delivery Availability Capacity Cost Management Contingency Service Level Management Management Planning Management Service Support Help Desk Change Problem Configuration Software Control & Management Management Management Management Distribution

14. Issues - Architecture • Technical Architecture • The ‘to be’ picture is still some way off being decided • The Distribution 'Programme' is seen to be acting as the default Design Authority e.g.: project teams are taking MIMS and UDB related decisions that will have a major impact on future architectures, and how they are supported and operated. • Information Architecture • There are too many standalone databases • There is a need for an MI architecture (a standard tool alone does not solve this issue). • Application Architecture • There is duplicate (potential) functionality in the chosen solutions of the main programme projects =>potential for consolidation • The existing architecture has potential for consolidation of applications to fewer servers, beyond that currently planned. • Operational Architecture • There is a lack of coverage in key areas e.g. pre-production standards • There is process ‘overload’ on some of the functional areas

15. Issues - Model • Relationship with other current / planned initiatives • Business Process Modelling • Systems Integration • Ownership • Programme • Issues with current intention / message of Business and Information Architectures • Toolset • Architecture review CASEwise • Process Modelling MOOD • Considerations • costs • skills • match to requirements (for IS = fit with current model)

16. Service Delivery Service Delivery Availability Capacity Cost Management Contingency Service Level Availability Capacity Cost Management Contingency Service Level Management Management Planning Management Management Management Planning Management Service Support Service Support Help Desk Change Problem Configuration Software Control & Help Desk Change Problem Configuration Software Control & Management Management Management Management Management Management Management Management Distribution Distribution Issues - Technical Standards • Areas of Focus - and the Gaps

17. Distribution Architecture ReviewFeedback to Distribution IS Implementation

18. Implementation - Processes & Standards • Agree ownership of IS processes • Owners to then agree on use of model ProcessOwner Availability Management System Manager Capacity Management System Manager Cost Management Planning & Strategy Analyst Contingency Planning System Manager Service Level Management IS Operations Configuration Management System Manager Help Desk Management Help Desk Problem Management System Manager Change Management System Manager Software Control & Distribution System Manager • tie in with other work (BW etc) Service Delivery Service Support

19. Distribution IS Implementation - Architecture 1) Recommended Initial set up • minimum feasible configuration • keep it simple while issues are resolved • Architecture • Costs • Software • 1 x Enterprise edition client £ 5,000 • Hardware • Standard PC NIL • Total £5k

20. IS Planning & Strategy Implementation - Architecture 2) Possible Phase 2 • indicative Client Server configuration • bed in processes before “hard coding” business rules • Architecture • Costs • Software • Server Option, (Oracle) per Server £10,000 • 1 x Enterprise edition client £ 5,000 • 3 x Professional client £ 7,750 • Hardware • Oracle server £ 2,000 (free?!) • Total £20 - 22k IS Application IS Operations IS Technical Services Services Oracle

21. Metadata - processes - roles - groups IS Planning & Strategy Implementation - Architecture 3) Possible Phase 3 • integrate with Notes (or other tools) • develop workflow to actively drive IS processes • Architecture • Costs • Architecture (as before) £20-22k • Development estimated 3 weeks • 1 x Notes developer • 1 x IS model manager Workflow IS Application IS Operations IS Technical Services Services Oracle Notes server

22. Current State Future State • Architecture • Definition • Impact Analysis • Configuration • Management • Applications • Network • Operations • Security/Access • etc • Enabling new • Projects • Check-out/ Kick-start • Reuse • Project Deliverables • Check-in • Impact Analysis • Costs (IS) vs • Benefits (Process) • Reuse (design objects) • Reduced timescales • Facilitates standards • Consistency • Single source of data • Facilitates standards • Event • Management • Operational • Processes • Application Specific • Events • Tools / • Interfaces • CASE tools etc. • DBMSs Implementation - Benefits

23. Distribution Architecture ReviewFeedback to Distribution IS Next Steps

24. Model Scope Programme IS Next Steps - Model • Implement current deliverables • Review current content • Agree IS standards with stakeholders • Implement agreed content • Implement Phase 1 CASEwise architecture • Resolve tool issues • CASEwise, MOOD or both? • Develop and agree further Phase plans • Develop the model further • Further IS standards and processes • more ITIL coverage • Integration with Programme • “to be” definition • business ownership for architecture • full lifecycle processes and standards • roles and responsibilities

25. Next Steps - IS • IS tasks which could be tackled in the short term • Consolidation • systems software e.g. Operating Systems • hardware e.g. Servers • Business Continuity • process definition • conducting Business Impact Assessment • IT Disaster Recovery • Proposal to cover the range of problems from Incidents to full Disasters • ESM Tool Selection • Change Management • Co-ordination & streamlining • Proactive Problem Management and Root Cause Analysis • process definition • selection of tools • gather key problem related information • perform analysis

26. Next Steps - Programme • Getting visibility of the ‘to be’ direction • Information Architecture (MI / data warehouse) • Assistance is resolving the outstanding Systems Architecture decisions with major impact on IS e.g. application consolidation • Help in resolving (quickly) the questions on the Technical Architecture with major impact on IS e.g. Middleware

27. Thanks For Your Time !