Enterprise Architecture Overview
November 2006
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
3
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
4
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
5
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
6
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
7
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
8
Our Enterprise Architecture Framework
Business Model
• Business Direction
• Stakeholders
• Functions
• Information
Business
Architecture
• Data Model
• Information Flows
• Databases
• Applications
Information
Architecture
Application
Architecture
• Application Integration
• Application Technology
• Server Technology
• Network / Communications
• Platforms / Operating Systems
Technology Architecture
• Database Systems
• Security Technologies
• etc.
November 2006
9
Architecture Development Process
Business and IT Strategies
ensure that architectures align
with business needs and priorities
Business Strategy
IT Strategy
Policies
Principles give high level direction
to enable decision making
Enterprise Architecture Principles
Technical
Application
Information
Business
Architecture layers provide
linkage between business models
and technical architecture
Target Model
T2
T1
November 2006
Current Model
Transition Plans provide the
implementation “roadmap”
Technology Standards and Guidelines
High-level context diagrams
present broader picture
Subject area models provide the
linkage between the global
context and projects
Detailed models describe the
subject matter at a project level
Standards and guidelines provide
specific direction on implementing
10
architectures
UoN Service Delivery Model / Value Chain
Develop
services
Get
New Business
Get
paid
ATTRACT
STUDENTS
INVOICE
STUDENTS
Student
DESIGN
PROGRAM
ADMIT
STUDENTS
ENROL
STUDENTS
Support services
Research
SCOPE
RESEARCH
PROJECT
CORPORATE
INFORMATION
MARKETING/
PUBLIC
RELATIONS
FINANCE
MANAGEMENT
HR
MANAGEMENT
November 2006
MARKET
RESEARCH
PROJECT
RESEARCH
SERVICES
IT
MANAGEMENT
PROCESS
PAYMENT or
FUNDING
PROCESS
FUNDING
ACADEMIC
REGISTRAR
FACILITIES
MANAGEMENT
Deliver
services
NUWAYS
Project
TRANSFER
LEARNING
ASSESS
LEARNING
Degree
VALIDATE
LEARNING
CONDUCT AND
PUBLISH
RESEARCH
GRADUATE
STUDIES
Research
outputs, papers
INTERNATIONAL
LEGAL
COUNSEL
11
Student Service Delivery Model
Develop
services
DESIGN
PROGRAM
Identify new
program need
ATTRACT
STUDENTS
Promote
university
Evaluate
Provide program
program
information
(program review)
Deliver
services
ENROL
STUDENTS
INVOICE
STUDENTS
PROCESS
PAYMENT or
FUNDING
TRANSFER
LEARNING
ASSESS
LEARNING
VALIDATE
DEGREE
Set up/verify
Program
Set up/verify
charges
Receive
payment
Design
learning(1)
Design
exams (2)
Verify degree
requirements
met
Apply
admission rules
Set up/verify
courses
Publish fee
charges
Apply
payment against
student debt
Organise
learning
Organise
exams
Organise
ceremony
Make
offer
Publish
program/courses
Configure fees
and rules
(Nustar)
Deliver
learning
Conduct
exams
Conduct
ceremony
Set up/verify
timetable
(lectures)
Run tuition
calculation
process (Nustar)
Mark
exams
Set up/verify
timetable
(tutorials)
Run billing
process
Validate and
publish results
ADMIT
STUDENTS
Understand
Set/verify
target markets admission rules
Design
program
Redesign
program
Get
paid
Get
New Business
Provide
scholarships
Reconcile for
compliance
Program revised, Events hosted,
new program
materials
outlined
distributed
Offer/No Offer
produced
Program/courses
/timetables
published
Bill sent
November 2006
(1) learning includes: courses, lab, tutorial, placements
Payments
received
Learning(1)
delivered
Grade
published
Degree
conferred
12
(2) exams: includes all forms of evaluation (lab, tutorial, course work)
Architecture Governance Model
Senior Executive level
IT Governance Committee
IT Management level
IT Policy, Standards & Architecture Review
IT service
Subject matter experts
Architecture
Adhoc
Advisory
working groups
Standards
Policies
Guidelines
Updates
AAG
IT development
teams
Group
Rejected Exception,
Recommendation
Request for
Exception
Project
Architecture
Architecture Advice
Business / Projects
delivery teams
Vendors and
consultants
Updates
Exceptions
Granted
Updates
UoN
EA
November 2006
13
Architecture Principles
Information Architecture Principles
Application Architecture Principles
Single Customer Identification
Common Use Applications
Consistent Definition of ProductsBusiness Ease of Use
Identification of Customer Contact Points
ArchitectureRe-use Before Buying
Data Accessible Across University of Newcastle
Buy Before Building
Timely Information
Minimise Package Modifications
Reuse Data
Component-based Architecture
Use One Data Master
Channel and Device Independence
Single Algorithm for Each Business Measure
Integration Services Independence
Information
Application
Data Security
Interfaces
to External Environment
Architecture
Architecture
Common Vocabulary and Data Definitions
Adopt Web-based Technologies
Centralised Analytical Data Repositories
Technology Architecture Principles
Technical Environment for the Future
Consistent Office Environment
Technology Architecture
Use Proven Technologies
Ensure Enterprise-Wide Integration of IT Security
Disaster Recovery / Business Continuity
Non-Repudiation
Interoperability
Deploy a Perimeter Layer Protecting Internal
Control Technical Diversity
Network Access
A Single Integrated WAN based on IP Protocol
Security Infrastructure to Support Distributed Users
Use Portals to Provide Security at a Higher Level
November 2006
14
Project Management
Architecture
Services for Projects
1.Discovery
Business
idea
Business
Case
Enterprise Architect
Solutions Architect
Preliminary advice
re: solution options &
architectural implications
1. Preliminary
consultation
Project
Charter
Business
Requirements
Specification
Advice regarding
implementation
(eg cost/time) of
technology solutions
2. Project
planning
advice
2. Design
Functional
Specification
Ongoing advice
to refine
project shape
3. Detailed architectural
analysis
(environmental scanning;
gap analysis;
assessment of options etc)
Technology
trends
November 2006
New/changed
architectural
components
required due to
external factors
Enterprise
Architecture
Model
PTO
Recommended
technology
solution
Solution
Options
New/changed
architectural
components
required by project
Business
trends and
strategies
Technical
Design
Specification
Enterprise
Architecture
Principles
Implementation of
new/changed
architecture components
(those not project specific)
15
Architecture Services for Projects
Project Management
2. Design cont’d
Cont’d
3. Deployment
Technical
Design
Specification
Issues
Register
Go Live
Solutions Architect
Escalation of
architectural
issues
4. Architectural
compliance
review
Implementation of
new/changed
architecture
components
(project specific)
Resolution of
architectural
issues
5. Architectural
issues
management
Incorporate
new/changed elements
into the Enterprise
Architecture Model
Enterprise Architect
Enterprise
Architecture
Principles
Enterprise
Architecture
Model
November 2006
16
Technology Architecture Components
November 2006
17
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 with
alignment to the strategic direction of UoN
• Become proactive rather than reactive
November 2006
18
Thankyou
• David Hall
Program Director – Project Office
David.Hall@newcastle.edu.au
• Stephen Bosworth
Enterprise Applications
Stephen.Bosworth@newcastle.edu.au
•Carey Steller
Solutions Architect
Carey.Steller@newcastle.edu.au
November 2006
19