Www.monash.edu. Enterprise Architecture in Higher Education, CSU Nathan Bailey, Enterprise Architect, Monash University ITS 1st November 2006 Top-down.

www.monash.edu

www.monash.edu

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’

www.monash.edu

3

Defining the outcome

• Why architecture?

www.monash.edu

4

The dode

www.monash.edu

5

Architecture

• reduce implementation and maintenance costs

• improve responsiveness and service• align university-wide activity (economies

of scale)• define growth paths (dept => fac => uni-

wide)

www.monash.edu

6

Is architecture about…

• the design activity (‘design’)• the implementation activity

(‘engineering’)• the maintenance activity (‘service

management’)• all + more?

www.monash.edu

7

Top-down

• Governance (Okay)• Strategic Planning (Good)• Capital Projects (Good-ish)• Procurement / acquisition (Good)• Changing 30 major and 300 minor

fiefdoms (Mmm…)• => Ensuring consistency

www.monash.edu

8

Bottom-up

• Source code control• Design and maintenance documents• Service management documents (ITIL)• => Improving reproducibility

www.monash.edu

9

In the middle

• Information management• Application portfolio

– Duplication of solutions (shared services)

– Technology and skills register

– “as is” => “to be” impact

www.monash.edu

10

Data

• RQF• LTPF• AUQA• => Increased focus

www.monash.edu

11

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?)

www.monash.edu

12

How are we doing?

www.monash.edu

13

Measuring maturity

• By CMMI• By artifacts (roadmaps,

blueprints, etc.)• By activity (eg. review +

sign offs, consults, sponsorships, proposals, etc.)

www.monash.edu

14

Still worry about

• Getting ITS to change (silos and control)• Identity management• Data governance

– Risks in compliance (records, IP management, etc.)

www.monash.edu

15

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

www.monash.edu

16

Preferred architecture…

www.monash.edu

17

Focus: Consolidation and reuse

www.monash.edu

18

Changing our modus operandi

•Commoditise everything•Create value in discrete business components (not bespoke silos)

www.monash.edu

19

Big picture

www.monash.edu

20

Big picture

www.monash.edu

21

Commoditise compute and storage (cf. ‘grid’)

www.monash.edu

22

Commoditise data models

www.monash.edu

23

Build discrete, reusable business components

www.monash.edu

24

Deploy in user-centred, audience targeted, homogeneous environment