UoN Enterprise Architecture 2006-11-01

8/11/2019 UoN Enterprise Architecture 2006-11-01

1/19


2/19

November 2006

Enterprise rchitecture Overview


3/19

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


4/19

November 2006 4

Where we have come from

Organisational change 2005 restructure

Legacy Technology unable to support the business goingforward

Little or No standards / methodology

No one overseeing the bigger picture across the organisation

Decentralised IT


5/19

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 andSDLC, 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


6/19

November 2006 6


2006 Program of Works50+ 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 Portfolios Program of Works


7/19

November 2006 7


Currently only used by ITCovers PoW and operations

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

AAG MembershipEnterprise Applications

Solutions Architect

Infrastructure

Security

Data Services

Client Services

Web Group

(Note: No Business Representation)

Bottom up approach to EA driven by IT


8/19

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 systemsold 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 EnterpriseArchitecture within IT

Seen as a hold up for existing processes / projects


9/19

November 2006 9

Our Enterprise Architecture Framework

InformationArchitecture

ApplicationArchitecture

BusinessArchitecture

Technology Architecture

Business Model

Business Direction

Stakeholders

Functions

Information

Data Model

Information Flows

Databases

Applications

Application Integration

Application Technology

Server Technology

Network / Communications

Platforms / Operating Systems

Database Systems

Security Technologies

etc.


10/19

November 2006 10

Architecture Development Process

C u

r r en

t M

o d el

T 1

T 2

T ar g e

t M

o d el

Appl ica t ionInformat ion

Technical

Bus ines s

Business StrategyIT Strategy

Policies

Enterprise Architecture Principles

Technology Standards and Guidelines

Business and IT Strategiesensure that architectures align

with business needs and priorities

Architecture layers providelinkage between business models

and technical architecture

Principles give high level directionto enable decision making

High-level context diagramspresent broader picture

Subject area models provide thelinkage between the global

context and projects

Detailed models describe thesubject matter at a project level

Standards and guidelines provide

specific direction on implementingarchitectures

Transition Plans provide theimplementation roadmap


11/19

November 2006 11

UoN Service Delivery Model / Value ChainGetNew Bus iness Developservices Getpaid

INVOICESTUDENTS

ATTRACTSTUDENTS

SCOPERESEARCHPROJECT

Student DESIGNPROGRAM

Deliverservices

TRANSFERLEARNING

ASSESSLEARNING

CONDUCT ANDPUBLISH

RESEARCHResearch

MARKETRESEARCHPROJECT

PROCESSFUNDING

ENROLSTUDENTS

PROCESSPAYMENT or

FUNDING VALIDATELEARNING

ADMITSTUDENTS

FINANCEMANAGEMENT

ACADEMICREGISTRAR

HRMANAGEMENT

CORPORATEINFORMATION

ITMANAGEMENT

LEGALCOUNSEL

FACILITIESMANAGEMENT S

u p p o r t s e r v

i c e s

GRADUATESTUDIES

INTERNATIONALRESEARCHSERVICES

MARKETING/PUBLIC

RELATIONS

Researchoutputs, papers

Degree

NUWAYSProject


12/19

November 2006 12

Student Service Delivery Model

(2) exams: includes all forms of evaluation (lab, tutorial, course work)(1) learning includes: courses, lab, tutorial, placements

GetNew Bus iness Developservices Getpaid

Deliverservices

ATTRACTSTUDENTS

DESIGNPROGRAM

TRANSFERLEARNING

ASSESSLEARNING

ENROLSTUDENTS

INVOICESTUDENTS

PROCESSPAYMENT or

FUNDING

Identify newprogram need

Evaluateprogram

(program review)

Providescholarships

Set up/verifyProgram

Set up/verifycourses

Set up/verifytimetable(lectures)

Set up/verifytimetable(tutorials)

Designexams (2)

Organiseexams

Conductexams

Markexams

Validate andpublish results

Designlearning (1)

Deliverlearning

Set up/verifycharges

Publish feecharges

Configure feesand rules(Nustar)

Run tuitioncalculation

process (Nustar)

Receivepayment

Applypayment against

student debt

VALIDATEDEGREE

Verify degreerequirements

met

Redesignprogram

Designprogram

Gradepublished

Degreeconferred

Learning (1) delivered

PaymentsreceivedBill sent

Program/courses /timetables

published

Program revised,new program

outlined

ADMITSTUDENTS

Set/verifyadmission rules

Applyadmission rules

Offer/No Offerproduced

Publishprogram/courses

Run billingprocess

Promoteuniversity

Provide programinformation

Understandtarget markets

Events hosted,materials

distributed

Makeoffer

Conductceremony

Organiselearning

Organiseceremony

Reconcile forcompliance


13/19

November 2006 13

Architecture Governance Model

IT Governance CommitteeSenior Executive level

IT Policy, Standards & Architecture Review

IT Management level

Subject matter expertsArchitectureAdvisory

Group

IT service

delivery teams

IT development

teams

Adhoc

working groups

Vendors and

consultants

Standards

PoliciesGuidelines

ExceptionsGranted

UoNEA

R e q u e s t

f o r

E x c e p

t i o n

P r o

j e c t

A r c

h i t e c t u r e

Updates

UpdatesUpdates

Business / Projects

A r c

h i t e c t u r e

A d v i c e

R e

j e c t e

d E x c e p

t i o n ,

R e c o m m e n

d a

t i o n

AAG


14/19

November 2006 14

Architecture Principles

InformationArchitecture

ApplicationArchitecture

BusinessArchitecture

Technology Architecture

Application Architecture PrinciplesCommon Use ApplicationsEase of UseRe-use Before BuyingBuy Before BuildingMinimise Package ModificationsComponent-based Architecture

Channel and Device IndependenceIntegration Services IndependenceInterfaces to External Environment Adopt Web-based Technologies

Information Architecture PrinciplesSingle Customer Identification

Consistent Definition of ProductsIdentification of Customer Contact Points

Data Accessible Across University of NewcastleTimely Information

Reuse Data

Use One Data MasterSingle Algorithm for Each Business Measure

Data SecurityCommon Vocabulary and Data Definitions

Centralised Analytical Data Repositories

Technology Architecture Principles

Technical Environment for the FutureUse Proven TechnologiesDisaster Recovery / Business ContinuityInteroperabilityControl Technical Diversity A Single Integrated WAN based on IP Protocol

Consistent Office EnvironmentEnsure Enterprise-Wide Integration of IT SecurityNon-RepudiationDeploy a Perimeter Layer Protecting InternalNetwork AccessSecurity Infrastructure to Support Distributed UsersUse Portals to Provide Security at a Higher Level


15/19

November 2006 15

Architecture Services for Projects

1. Preliminaryconsultation

BusinessCase

FunctionalSpecification

SolutionOptions

TechnicalDesign

Specification

BusinessRequirementsSpecification

Businessidea

Preliminary advicere: solution options &

architectural implications

EnterpriseArchitecture

Model

EnterpriseArchitecturePrinciples

3. Detailed architecturalanalysis

(environmental scanning;gap analysis;

assessment of options etc)

Technologytrends

ProjectCharter

Implementation ofnew/changed

architecture components(those not project specific)

E n

t e r p r i s e

A r c

h i t e c

t

S o

l u t i o n s

A r c

h i t e c

t

P r o

j e c

t M a n a g e m e n

t

Businesstrends andstrategies

Ongoing adviceto refine

project shape

2. Projectplanning

advice

Advice regardingimplementation

(eg cost/time) oftechnology solutions

New/changedarchitecturalcomponents

required due toexternal factors

Recommendedtechnology

solution

PTO

1.Discovery 2. Design

New/changedarchitecturalcomponents

required by project


16/19

November 2006 16

Architecture Services for Projects

5. Architecturalissues

management

EnterpriseArchitecture

Model

EnterpriseArchitecturePrinciples

E n

t e r p r i s e

A r c

h i t e c

t

S o

l u t i o n s

A r c

h i t e c

t

P r o

j e c

t M a n a g e m e n

t

Implementation ofnew/changedarchitecturecomponents

(project specific)

Resolution ofarchitectural

issues

Escalation ofarchitectural

issues

IssuesRegister

TechnicalDesign

Specification

4. Architecturalcompliance

review

Contd

Incorporatenew/changed elements

into the Enterprise Architecture Model

Go Live

2. Design contd 3. Deployment


17/19

November 2006 17

Technology Architecture Components


18/19

November 2006 18

Where to from Now?

Adoption of Use of Enterprise Architecture outside of IT

Establish an EA group with a business focus

Learn and improve

Work collaboratively

Continual Development of Enterprise Architecture withalignment to the strategic direction of UoN

Become proactive rather than reactive


19/19

November 2006 19

Thankyou

David Hall

Program Director Project Office

[email protected]

Stephen Bosworth

Enterprise Applications

[email protected]

Carey Steller

Solutions Architect

[email protected]
mailto:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]

UoN Enterprise Architecture 2006-11-01

Documents

Transcript of UoN Enterprise Architecture 2006-11-01