1 / 24

Enterprise Architecture in Higher Education, CSU Nathan Bailey, Enterprise Architect, Monash University ITS 1st November

Enterprise Architecture in Higher Education, CSU Nathan Bailey, Enterprise Architect, Monash University ITS 1st November 2006. Top-down and bottom-up -- our story Monash IT Architecture Identifying and adopting ‘reusable best practice’. Defining the outcome. Why architecture?. The dode.

willa
Download Presentation

Enterprise Architecture in Higher Education, CSU Nathan Bailey, Enterprise Architect, Monash University ITS 1st November

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 Higher Education, CSUNathan Bailey, Enterprise Architect, Monash University ITS1st November 2006 Top-down and bottom-up -- our story Monash IT Architecture Identifying and adopting ‘reusable best practice’

  2. Defining the outcome • Why architecture?

  3. The dode

  4. Architecture • reduce implementation and maintenance costs • improve responsiveness and service • align university-wide activity (economies of scale) • define growth paths (dept => fac => uni-wide)

  5. Is architecture about… • the design activity (‘design’) • the implementation activity (‘engineering’) • the maintenance activity (‘service management’) • all + more?

  6. Top-down • Governance (Okay) • Strategic Planning (Good) • Capital Projects (Good-ish) • Procurement / acquisition (Good) • Changing 30 major and 300 minor fiefdoms (Mmm…) • => Ensuring consistency

  7. Bottom-up • Source code control • Design and maintenance documents • Service management documents (ITIL) • => Improving reproducibility

  8. In the middle • Information management • Application portfolio • Duplication of solutions (shared services) • Technology and skills register • “as is” => “to be” impact

  9. Data • RQF • LTPF • AUQA • => Increased focus

  10. Data • Unified and cleansed • Building data-mart approach (client facing) • Building BPEL/SOA approach (back end) • Still need data model, data dictionary, data business owners and rules, etc. (eg. who owns ID numbers and how can they be used?)

  11. How are we doing?

  12. Measuring maturity • By CMMI • By artifacts (roadmaps, blueprints, etc.) • By activity (eg. review + sign offs, consults, sponsorships, proposals, etc.)

  13. Still worry about • Getting ITS to change (silos and control) • Identity management • Data governance • Risks in compliance (records, IP management, etc.)

  14. We have thousands (tens of thousands?) of these bespoke solutions… • A dozen or more groups managing networks • Dozens of storage management solutions • Over 100 groups managing servers • Hundreds of separate data models stored in hundreds of separate databases • Hundreds of application servers running hundreds of separate application frameworks • Thousands of separate applications written in a dozen or more separate languages • Dozens of different ways of identifying, analysing, designing, building, implementing and maintaining solutions to business problems

  15. Preferred architecture…

  16. Focus: Consolidation and reuse

  17. Changing our modus operandi • Commoditise everything • Create value in discrete business components(not bespoke silos)

  18. Big picture

  19. Big picture

  20. Commoditise compute and storage (cf. ‘grid’)

  21. Commoditise data models

  22. Build discrete, reusable business components

  23. Deploy in user-centred, audience targeted, homogeneous environment

More Related