Nustar uon

November 2006

Enterprise Architecture Overview

November 2006 3

Our Areas of Interest

• Business – HE Functional Reference Models

• Platform Standards – Taxonomy

• Architecture Governance

• What other Universities are doing in this space

• Methods/Tools being used to achieve goals of EA

November 2006 4

Where we have come from

• Organisational change – 2005 restructure

• Legacy Technology unable to support the business going

forward

• Little or No standards / methodology

• No one overseeing the “bigger picture” across the organisation

• Decentralised IT

November 2006 5

Enterprise Architecture and UoN

• Very early stages

• Major business and systems change

▪ Organisation Restructure completed early 2006

▪ Centralised IT

▪ Program of Works (EPMO) within IT

▪ Formation of roles/groups (AAG, CAB, PoW, Change Office, IT Governance Committee)

• Introduction of Groups and Processes

▪ Start of ITIL implementation, Change Office (PMO), “formalised” Project Methodology and SDLC,

Architecture Governance, Standards

• Enterprise Architecture Consultant – “EA in a box”

▪ Light inventory across Business, Information, Applications, Technology

▪ Provided principals, some mapping between inventories, gap analysis

▪ Current Activities/Changes/Lack of Ownership made this difficult – “hitting a moving target”

▪ Tool - System Architect

November 2006 6

Enterprise Architecture and UoN

• 2006 Program of Works

▪ 50+ Projects with IT underpinning them

▪ Infrastructure (network, server consolidation, etc)

▪ Information Management (BI, ECMS)

▪ Business (HR, Finance, Research, Students, Facilities, etc)

▪ Teaching / Learning (Blackboard/LOMS, Academic Support)

▪ Operational (ID Mngt, Integration,adopt mainstream technology)

▪ Client Services (“17000” Centralised Service Desk, MOE, ITIL rollout)

▪ NUWays: Focussed on Business Process Improvement and EPMO

• Formed

▪ Change Office

▪ AAG – Architecture Advisory Group

▪ CAB – Change Advisory Board

▪ Project Portfolio’s – Program of Works

November 2006 7

Enterprise Architecture and UoN

• Currently only used by IT

▪ Covers PoW and operations

▪ Reaction to the amount of project work being undertaken, realisation for EA out of PoW

• AAG Membership

▪ Enterprise Applications

▪ Solutions Architect

▪ Infrastructure

▪ Security

▪ Data Services

▪ Client Services

▪ Web Group

▪ (Note: No Business Representation)

• Bottom up approach to EA – driven by IT

November 2006 8

Challenges Experienced

• Current IT Inventory = 100+ Main Applications

▪ ~65% in-house developed – mainly “gap fillers” around the enterprise applications

▪ Current upgrades will supersede some but still expected to be significant

▪ Mixed blend of technology:

➢ ERP, disparate systems

➢ old and new technology

➢ “islands of data” and “the spider web” of integration (point to point)

• Time / Resources / Size of Work for Enterprise Architecture

• Standards / Guidelines

• Expectations of Business and IT

• Implementation, Acceptance and Understanding of Enterprise

Architecture within IT

• Seen as a hold up for existing processes / projects

November 2006 9

Our Enterprise Architecture Framework

Information

Architecture