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 • Applications
• Information Flows • Application Integration
Information Application
• Databases Architecture Architecture
• 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
Business Strategy Principles give high level direction
IT Strategy to enable decision making
with business needs and priorities
Policies
Enterprise Architecture Principles
Architecture layers provide
Technical
Application High-level context diagrams
linkage between business models
present broader picture
and technical architecture Information
Business
Subject area models provide the
linkage between the global
Current Model
Target Model
context and projects
T1
T2
Detailed models describe the
Transition Plans provide the
subject matter at a project level
implementation “roadmap”
Standards and guidelines provide
specific direction on implementing
November 2006 Technology Standards and Guidelines architectures 10
UoN Service Delivery Model / Value Chain
Develop Get Get Deliver NUWAYS
services New Business paid services Project
ATTRACT TRANSFER
STUDENTS LEARNING
INVOICE
STUDENTS
DESIGN ADMIT ASSESS
Student STUDENTS PROCESS LEARNING Degree
PROGRAM
PAYMENT or
FUNDING
ENROL VALIDATE
STUDENTS LEARNING
SCOPE MARKET CONDUCT AND
PROCESS
Research RESEARCH RESEARCH PUBLISH Research
FUNDING
PROJECT PROJECT RESEARCH outputs, papers
Support services
CORPORATE MARKETING/ ACADEMIC
RESEARCH GRADUATE INTERNATIONAL
INFORMATION PUBLIC REGISTRAR
SERVICES STUDIES
RELATIONS
FINANCE HR IT FACILITIES LEGAL
MANAGEMENT MANAGEMENT MANAGEMENT MANAGEMENT COUNSEL
November 2006 11
Student Service Delivery Model
Develop Get Get Deliver
services New Business paid services
PROCESS
DESIGN ATTRACT ADMIT ENROL INVOICE PAYMENT or TRANSFER ASSESS VALIDATE
PROGRAM STUDENTS STUDENTS STUDENTS STUDENTS FUNDING LEARNING LEARNING DEGREE
Verify degree
Identify new Understand Set/verify Set up/verify Set up/verify Receive Design Design
requirements
program need target markets admission rules Program charges payment learning(1) exams (2)
met
Apply
Design Promote Apply Set up/verify Publish fee Organise Organise Organise
payment against
program university admission rules courses charges learning exams ceremony
student debt
Evaluate Configure fees
Provide program Make Publish Deliver Conduct Conduct
program and rules
information offer program/courses learning exams ceremony
(program review) (Nustar)
Set up/verify Run tuition
Redesign Provide Mark
timetable calculation
program scholarships exams
(lectures) process (Nustar)
Set up/verify
Run billing Validate and
timetable
process publish results
(tutorials)
Reconcile for
compliance
Program revised, Events hosted, Program/courses
Offer/No Offer Payments Learning(1) Grade Degree
new program materials /timetables Bill sent
produced received delivered published conferred
outlined distributed published
November 2006 12
(1) learning includes: courses, lab, tutorial, placements (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
delivery teams
Subject matter experts
Architecture Adhoc IT development
Business / Projects
Advisory working groups teams
Group
Rejected Exception,
Architecture Advice
Recommendation
Architecture
Request for
Exception
Project
Vendors and
consultants
Updates Updates
Standards AAG Exceptions
Policies
Granted
Guidelines
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
Data Security Application
Interfaces to External Environment
Architecture
Common Vocabulary and Data Definitions Architecture
Adopt Web-based Technologies
Centralised Analytical Data Repositories
Technology Architecture Principles
Technical Environment for the Future Consistent Office Environment
Use Proven Technologies Technology Architecture Enterprise-Wide Integration of IT Security
Ensure
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
Architecture Services for Projects
1.Discovery 2. Design
Business Project
Project Management
idea Business Charter Business
Case
Requirements
Functional
Specification Technical
Specification
Design
Specification
PTO
Advice regarding Ongoing advice
Preliminary advice
implementation to refine Recommended
re: solution options &
(eg cost/time) of project shape technology
architectural implications
technology solutions solution
Solutions Architect
3. Detailed architectural
analysis Solution
2. Project
1. Preliminary (environmental scanning; Options
planning
consultation gap analysis;
advice
assessment of options etc)
New/changed
architectural
components Enterprise
required by project
Enterprise Architect
Architecture
Principles
Business
trends and New/changed
strategies architectural Implementation of
components Enterprise new/changed
Technology
required due to Architecture architecture components
trends
external factors Model (those not project specific)
November 2006 15
Architecture Services for Projects
2. Design cont’d 3. Deployment
Cont’d Technical
Project Management
Issues
Design
Register
Specification
Implementation of
Go Live new/changed
architecture
components
(project specific)
Escalation of
architectural
issues Resolution of
architectural
Solutions Architect
issues
Incorporate
4. Architectural new/changed elements
compliance 5. Architectural into the Enterprise
review issues Architecture Model
management
Enterprise
Enterprise Architect
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