IT Architecture at Birmingham - PowerPoint PPT Presentation

it architecture at birmingham n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
IT Architecture at Birmingham PowerPoint Presentation
Download Presentation
IT Architecture at Birmingham

play fullscreen
1 / 20
IT Architecture at Birmingham
337 Views
Download Presentation
xiang
Download Presentation

IT Architecture at Birmingham

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. IT Architecture at Birmingham RUGIT March 2012

  2. Agenda • Architecture at Birmingham • Architecture at Imperial • Anti-Architecture at Warwick • Group discussion IT Architecture

  3. Agenda • Why Architecture? • What is Architecture? • Enterprise Architecture Framework • Principles • Process • Governance • Funnel • Questions IT Architecture

  4. Why Architecture? • Enterprise Architecture – a holistic approach to IT • Principles to drive realisation of IT Strategy • Rational approach to prioritising technology investment • Seeks benefits across the University as a whole • Simplify – reduce complexity (and associated costs) • Standardise – define and comply with standards, achieve economies of scale • Rationalise – eliminate duplication, maximise reuse • Architecture Governance • ITIL compatible – dovetails into existing IT Governance • Validates compliance so that benefits are actually achieved IT Architecture

  5. What is Architecture? • Policies • Security – IAM, encryption • Green IT – carbon counting, efficient use of resources • Services – loosely coupled components that implement services • Standards • SIB – a published Standards Information Base • Procedures • Architecture Process – covers entire system life cycle, includes: • Architecture Governance – extension of IT governance • Guidelines • Principles – based on IT Strategy + industry best practice • Patterns – reusable designs (benefit from experience) • TAM – Target Architecture Model (what we are aiming for) IT Architecture

  6. Birmingham Enterprise Architecture Framework IT Architecture

  7. Architecture Framework IT Architecture

  8. Application Architecture IT Architecture

  9. Data Architecture • Data Architecture Principles • subset of EA principles • Enterprise Information Model • based on semantic model • business entities • Logical Data Models • hierarchy of models • includes COTS • use data dictionary • Physical Data Models • tables, rows, columns, keys • Data Management Policy • information life cycle • data quality – active management IT Architecture

  10. Birmingham Enterprise Architecture Framework IT Architecture

  11. Architecture Principles IT Architecture

  12. Focus on System Life Cycle • System Life Cycle Process extends over entire life cycle of a system • Architecture Process supports entire system life cycle • Support model • Retirement (or Exit if system is externally managed service) IT Architecture

  13. Process Architecture Board Work-off list Solution Architecture • Solution Architecture • summarise architecture decisions and known facts • high-level business, application, data and technology description • produced by architects + project team • defines what will be delivered - changes subject to change control • delivered with PID, or shortly thereafter • Architecture Board • held before go-live (more if necessary) • assures solution is fit for purpose and Solution Architecture has been delivered • may result in work-off list, or delay go-live IT Architecture

  14. Solution Architecture Description • A short document that summarises the proposed solution • Not a design document (does not cross boundary between architecture and design) • Delivered with, or shortly after, PID • Contents: • Background + high-level architecture overview • Architecture Principles – how the solution will address them • Assumptions – major assumptions only • Decisions – technology choices etc. • Technology Stack – hardware, software, versions • Protocol Stack – which protocols used and where • Environments – (e.g. Development, Test, Production) with 1st cut sizing • Key Non-functional Requirements – how they will be met • Data – use/creation of enterprise data IT Architecture

  15. Non-Functional Requirements IT Architecture

  16. Architecture Board • Technical meeting chaired by IT Architect • Reviews solution architecture for: • Overall fitness for purpose • Adherence to Architecture Principles, Standards • Security – conformity with security policy, addresses specific risks • Information – access to / impact on the university’s enterprise data • Architecture Concerns – technical risks, issues etc. • Approves solution • May request / impose remedial action as necessary • Delay project close-down if outstanding major issues • Delay go-live if major risks to the university IT Architecture

  17. Changes • Architecture Compliance Form • Summary of system architecture • Check list – Principles, Requirements, Standards, Technology, Environments • Operational Testing – new focus • To show compliance with non-functional requirements • Architecture Compliance Review • Held before go-live • Based on Compliance Form • Architecture Authority process • Oversees architecture governance IT Architecture

  18. SPRC Strategic Planning and Resources Committee UEB University Executive Board ICG Infrastructure Coordination Group MIRG (IT) Major Investments Review Group BSSG Business Systems Strategy Group ITIG IT Infrastructure Group IMSG Information Management Steering Group BIRMS Banner Information Reporting & Mgmt System ISSG Information Security Steering Group RCMG Research Computing Management Group 6 monthly status review University capital planning IT Strategic Planning Group business case scrutiny holistic IT strategy & overview planning investment proposals aligning innovation with strategy IT Innovation Panel ISSG Information Security BSSG Applications ITIG Infrastructure architecture for each of BSSG / ITIG: strategic direction and tactics, and service management Reporting BIRMS RCMG UoB Student

  19. SUPPORT SYSTEMS CORE SYSTEMS IDEA IDEA Project Mgt software £?? from ?? Not started Student Hub software £?? from ?? Not started iVLE 2.0 Visioning (planned live 2013) HR workflow £?? from Incent. & Penalt.? Not started Research Assets re-use & booking £?? from ?? FEASIBILITY FEASIBILITY Student Accommodation £k from HAS Planned live Q2 2012 CAL Workload Allocation Model £? DRES £k (2yrs) Planned live Q1 2012 DEVELOPMENT DEVELOPMENT Module Evaluation £k Planned live Q3 2012 RMS/REF £? July 2012; rollout dates t.b.c. ITSMP £ Live in phases 2012 -2014 LMS (Library) £ Live in phases 2012 -2013 Single Source Curric £k JISC funding Live ?? BIRMS – Phase 2 £ Completed July 2012 Alta HR - my.teams Fully live Q4 2012; partial release April 2012 REAMS £ Live April 2012 Output metadata £ Planned live Q4 2011 e-Ticketing £ from HAS Planned live June 2012 Alta HR - Real Time Initiative £ Live April 2012 Research Grant System £ Development complete July 2012. Enterprise Search £ Phase 1 Live Q1 2012 EPOS £ from HAS Live summer 2012 E- Marketplace £ Live rollout starts Q4 2011 Asset Mgt - (Planon) £ Live Oct/Nov 2011 Alta HR Self service £ Off-campus access t.b.c. PG Admissions £ LiveNov 11 BAU BAU CampusM Talis AltaHR Proactis Occam BOXI Tokopen Raisers Edge SSM CODA Contensis Hobsons Tableau Planon WCN WebCT Luminis Research Accounting BAU REVIEW BAU REVIEW BOXI renewal (Q4 2012) £ Initial discussion Staff e-recruitment replacement? £?? Not started Oracle renewal (Q2 2014) £ Not started Banner renewal (2014) £ Initial discussions HR Systems Review £ Not started

  20. How we got started • Engaged experienced contractor • Established approach, framework, principles, process • Switched to permanent ‘Chief IT Architect’ • JD also includes: IT Security Officer and IT Innovation • Switched to new processes for all IT projects • Additional resources • Information Architect • Data Architect IT Architecture