LJMU Enterprise Architecture Pilot

(LEAP)

Summary (1)

The LJMU Enterprise Architecture Pilot (LEAP) will build on existing work in Information Systems Architecture, Governance and technical web services development to pilot The Open Group Architecture Framework (TOGAF) approach to establishment of a full Enterprise Architecture model

Summary (2) LEAP will also incorporate work carried out by

the LJMU Process Framework project, which has developed an overall process management model for the University within the context of our strategic commitment to the EFQM Excellence Model, and has produced detailed process maps of many areas of the business with more recently a particular emphasis on student administration. Phase 1 of the pilot will concentrate on developing the architecture model for the Student Recruitment, Development and Support core process identified within the LJMU Process Framework.

Draft Work Plan (1) LJMU Enterprise Architecture Project: Initial Schedule of Deliverables/Milestones

2008 2009Deliverable Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar

Develop project plan

Project plan delivered Definition of Phase 1 EA ScopeDevelopment of Phase 1 EAReview of Phase 1 EAImplementation Planning Phase 1 EAImplementation Phase 1 EADefinition of Phase 2 EA ScopeDevelopment of Phase 2 EAFirst project reportSecond project report Third project reportDevelop final report/case studyFinal report delivered

Draft Work Plan (2)WORKPACKAGES Month 1 2 3 4 5 6 7 8 9 10 11 12 1: Project management X X X X X X X X X X X X 2 Direct TOGAF activity X X X X 3 Governance X X X X 4 Business architecture X X X X X 5 IS Architecture X X X X X X 6 Technology

Architecture X X X

7 Dissemination X X X X X X X X X X X X 8 Tool evaluation X X X 9 Quality Assurance X X X X X X X X X X X X 10. Exit/sustainability X X

Motivation - LJMU• Already identified EA work as essential to

contextualise other activity eg ISA, Student Administration Review, technical service developments

• Architecture = key responsibility in new Governance structure

• Major investment with Oracle predicated on Fusion implementation, requiring SOA approach

• Opportunity to engage with other practitioners/the Open Group to advance learning & expertise

Motivation: LJMU (SMG slide)

• Opportunity to:– define our IT architecture, linking process,

data, applications and infrastructure = in essence, defining what services we require now/in future, and which systems deliver/will deliver these services

– be flexible and future-proofed– standardise data and processes– benefit from work being carried out

elsewhere in the community

Key IT Governance Decisions

IT Principles DecisionsHigh-level statements about how IT is used in the business

IT ArchitectureDecisions

Organising logic for data,applications, and infrastruc-ture captured in a set ofpolicies, relationships, andtechnical choices to achievedesired business and technical standardisationand integration

IT InfrastructureDecisions

Centrally co-ordinated, sharedIT services that provide thefoundation for the enterprise’sIT capability.

Business Applications Needs

Specifying the business needfor purchasing or internallydeveloped IT applications.

IT Investment andPrioritisation decisions

Decisions about how muchand where to invest in IT,including project approvalsand justification techniques.

(Weill and Ross, 2004, IT Governance, HBSP)

LJMU Governance Model

Information Management

Steering GroupBusiness Membership

Development Programme

Business Membership

IT Steering Group

Business Membership

ArchitecturePrinciples

InfrastructureBusiness Applications Needs

ITMembership

Investment & prioritisation

Methodologies: MSP ITIL

MonitoringComplianceReview

Motivation: Wider Community

• Contribute to the development of EA models for the sector

• Promote the importance of effective Governance structures for EA/SOA implementation

• Contribute models at various levels to the e-Framework

• Support the development of shared service approaches

What does success look like…

for LJMU• Senior Management engaged with

EA/SOA approach• Understanding/model of how things fit

together in student administration area• Commitment to continuing

development• Practical implementation of services

linked to business objectives• Enhanced ability to deliver EA/SOA

approach

What does success look like…

for Programme• Enhanced understanding of importance

of EA/SOA approaches across the sector

• Validation (or otherwise!) of TOGAF approach

• Contribution to e-Framework• Learning from early adopters as basis

for future work

Overlaps & synergies

• Differences/similarities in Governance structures

• Combining top-down/bottom-up approaches ref KEAP

• Impact/significance of supplier engagement eg LJMU/Oracle; Cardiff/IBM

• Value of pilot in supporting institutional strategic objectives, key to all projects

Issues & Questions

• Not a lot of time• Risk of retrofitting TOGAF• Meeting project objectives as opposed

to JISC requirements (not same thing)• Would like some early advice on tool

selection (if necessary – currently using Visio)