Aligning Enterprise Architecture and ERP presented by Ben Berry, ODOT Chief Information Officer ben.

1
Aligning Enterprise Architecture and ERP
presented by Ben Berry, ODOT Chief Information
Officerben.berry_at_odot.state.or.us
Joint DAS/ODOT Meeting on Enterprise Integrated
Systems Program

• August 25, 2008

2
Current State of Enterprise Programs

• Oregon Enterprise Architecture (EA)
• 09-11 DAS POP requests creation of EA
  Standards Program.
• Agency Directors in 2004 and 2006 documented need
  for effective, enterprise-level planning and
  IT-alignment.
• 2007-11 EIRMS endorsed by CIOC and Admin Business
  Directors calls for Enterprise business,
  technical architecture standards.
• If approved by Legislature, EA and Standards
  Program would begin July 2009.

• DAS ODOT agree to Enterprise Resource Planning
  (ERP)
• DAS/ODOT create ERP Interagency Agreement.
• 09-11 Program Option Package (POP) created.
• Selected pre-implementation vendor to the
  Integrated System ERP.
• Joint DAS/ODOT Steering Committee and Charter
  established.
• Joint Steering Committee direction to have Single
  Software for State.

3
Enterprise Architecture and ERP Alignment is
Elusive

• Define AS-IS COULD-BE
• functions for
• - Human Resources
• - Finance
• - Procurement

• Sustainable Business Architecture for Decisions
• Alignment of EA to business needs.
• A Repeatable EA framework
• Architecture is visible across state agencies

4
Enterprise Architecture should Inform ERP
5
Developing the Right Perspective is Critical!

• Targeted Interest
• Informed by EA
• Rich Reqts.
• Stake Holders
• Implement Bulletproof

• Shared Interest
• Enterprise perspective
• Migration path to move toward target
  architectures
• Consistent EA methodology statewide

• Opportunities and Stewardship for
• Improved performance
• Introduction of new capabilities
• Expanded responsibilities
• Reduced costs
• Leverage new technology

6
DAS ODOTIntegrated System ERP Program
Integrated System
Core ERP
Finance
HRIS
Enterprise Application Interfaces
Procurement
Authoritative Data Source
7
ERP Proposed Scope and Release Strategyas of
August 2008
8
Definition Enterprise Architecture

• The process of translating business vision and
  strategy into effective enterprise change by
  creating, communicating and improving key
  requirements, principles and models that describe
  the enterprises future state and enable its
  evolution. (Gartner)
• The practice of documenting the elements of
  business strategy, business case, business model
  and supporting technologies, policies and
  infrastructures that make up an enterprise.
  (Wikipedia)

9
EA Supports Agency Requirements Gathering
Integrated Data and Information from As-Is
through To Be State
Others
Forestry
DCBS
DAS
DHS
ODOT
10
What is the compelling business need for
Enterprise Architecture?

• Business Value to the Business
• Facilitates business transformation throughout
  the enterprise.
• Formalizes and captures knowledge about the
  business that helps identify new opportunities
  and clarify existing gaps.
• Provides a set of guidelines, standards, and
  blueprints that can be used to acquire, build and
  deploy business solutions.

• Technology Value to the IT Organization
• Makes new initiatives easier to manage because
  they are designed and implemented according to
  architecture guidelines.
• Delivers a more manageable, agile IT environment.
• Aligns IT initiatives to business imperatives so
  that business benefits justify the costs.
• Allows IT to stay ahead of the curve with respect
  to the underlying technologies and infrastructure
  to support business applications.

11
EA can Expose Core Business Functions
Agency Business Services
Statewide Enterprise Services
12
Enterprise Architecture can inform ERP
Procurement
Financials
Target Business Architecture
ODOT
DAS
Human Res
Business
Enterprise Information Architecture
Information (Data)
Enterprise Application Architecture
Application
Enterprise Technology Architecture
EA
Technology
Infrastructure
ERP
13
For example Incorporate Forestry Department EA
into Statewide EA/ERP
Forestry Business Improvement Initiative
14
So, what might an Action Path look like for
aligning EA/ERP?
Contractor Support
Finance Team
HRIS Team
EA Team
Governing Body
Activities
Activities
Contractor
Financial
HRIS
EA
1. Complete SOW and RFP to acquire contractor to
1. Complete SOW and RFP to acquire contractor to
I
AC
AC
R
AC
AC
R
develop

As
-
Is

EA for administrative functions
develop

As
-
Is

EA for administrative functions
and segment architectures for HR and Finance.
and segment architectures for HR and Finance.
2. Identify enterprise mission, vision,
principles and
2. Identify enterprise mission, vision,
principles and
R
C
C
AC/
environmental trends for enterprise
administrative
R
C
C
AC/
environmental trends for enterprise
administrative
systems.
Systems (Finance, HR and Procurement).
R
C
AC/
C
3. Create HR segment architecture for the
enterprise.
R
C
AC/
C
3. Create HR segment architecture for the
enterprise.
4. Develop a migration plan to move towards the

To
-
4. Develop a migration plan to move towards the

To
-
C
RA
C
C
RA
C
Be

target HR architecture.
Be

target HR architecture.
5. Create Financial segment architecture for the
5. Create Financial segment architecture for the
R
AC/
C
C
R
AC/
C
C
enterprise.
enterprise.
6. Develop a migration plan to move towards the
6. Develop a migration plan to move towards the
C
RA
C
C
RA
C
target Financial architecture.
target Financial architecture.
7. Develop a target architecture that reflects
the
7. Develop a target architecture that reflects
the
RA
C
C
enterprise

s need to evolve its information
RA
C
C
enterprise

s need to evolve its information
resources.
resources.
8. Refine an architecture development methodology
8. Refine an architecture development methodology
C
C
R
C
C
R
for continued ongoing use.
for continued ongoing use.
9. Establish governance structure to promote and
9. Establish governance structure to promote and
C
C
R
C
C
R
I
manage architecture as an ongoing process.
manage architecture as an ongoing process.
15
Enterprise Architecture Consulting Project
Approach and Milestones
Status and
Architecture
Architecture
Architecture
Planning
Management
Requirements
Principles
Modeling
Management
Action Plan
Wk 1-3
Wk 2-12
Wk 3-5
Wk 9-12
Gather and
Develop
Develop
Develop
Wk 1
Summarize
Conceptual
Evaluation
Transition
Wk 2-12
Inputs
Model
Criteria
Plan
Principles
Planning
Definition
Wk 6-9
Sessions
Workshops
Define
Document
Gap
Final
Architecture
Key
Analysis

• Set expectations
• Review contract
• Identify ARB members
• Identify key stakeholders
• Schedule interviews
• Schedule Workshops
• Team orientation
• Other logistics
• locations
• space
• communications
• Intranet Access

• Architecture Review Board
• Kickoff (half day)
• EA Principles
• ---------------
• EA Visioning
• EA Roles/Responsibilities
• EA Metrics
• ---------------
• EA Processes
• EA Tools
• ---------------
• EA Transition Plan
• ---------------

Presentation
Management
Requirements
Workshops

Processes

• Conceptual Model
• Access, Security
• Applications
• Data
• Common Services
• Application Development,
• Cross-Function Applications
• Systems Mgt
• Network, Platforms,
• Peripherals
• Autonomic/Grid/UMI

• Strategic documents
• Business models
• User groups
• Pilots
• Sourcing position
• Baseline assessment

• EA Processes
• Evaluation Criteria
• Arch Review Board
• Technical Steering Committee
• EA in a Box

• Complete Documentation
• Initiatives
• BP

16
Enterprise Architecture Consulting Estimated
Timeline for a 12-week engagement. A simple
project duration typically runs up to 16 weeks
and can be requested for any duration and volume
of content is estimated separately.

• lt An interim report will provide early feedback
  on the team's findings and recommendations.
• lt The final report will be presented at the end
  of the engagement.

17
How EA/ERP creates value for the enterprise

• Agency Directors
• ABSD
• CIOs

• ERP Stakeholders
• Segment Owners
• Business Mgrs

18
Remember, the 09-11 DAS POP already defines the
work of the EA Core Team

• Enterprise
• Build architecture models for core statewide
  functions, e.g. HR, finance, procurement.
• Prepare for dedicated EA resources in 2009-11.
• Promote EA concepts for and report to business
  community.
• Establish a infrastructure for collaboration and
  sharing information across agency boundaries.
• ERP Segment Architecture
• Inform ERP program.
• Support the ERP effort by creating reusable EA
  methods, templates, tools, etc.
• Use segment architecture effort to jump-start
  cross-agency business understanding.
• Agency Support
• Inform and promote Enterprise Architecture and
  ERP architecture to agencies.
• Develop methods, tools, and assistance for agency
  or segment architecture work.
• Work to ensure that agency needs are recognized
  in both models.
• Work with agencies to influence projects that
  contribute to enterprise architecture.
• Assist agencies to promote project concepts.
• Architect Community
• Build architects community to share experiences,
  build skills, and reuse products.
• Continue to build EA infrastructure, web
  accessible repository and support.

19
Expected Outcomes Top Down, Across and Bottom
Up
Enterprise Vision

• Build target architecture models for core
  statewide functions, e.g. HR, finance, and
  procurement.
• Promote EA concepts for business community.
• Establish a infrastructure for collaboration and
  sharing information across agency boundaries.
• Prepare for dedicated EA resources in 2009-11.

• Reuse agencys EA to ensure that their needs are
  recognized in a target statewide enterprise
  architecture model for core statewide functions.
• Work with agencies to influence projects that
  contribute to enterprise architecture.
• Assist agencies in promoting EA concepts.

Agency Architectures
Architects

• Establish a community of architects to share
  experiences, build skills, and reuse
  architectural products.

20
Contributors to this presentation

• CIO Management Council
• Ron Winterrowd
• ERP Program Manager (ODOT)
• Steve Schafer
• HRIS Project Manager (DAS HR)
• Tim Avilla
• IS Process Improvement (ODOT)
• Ed Arabas
• EISPD Administrative Services
• Scott Riordan
• EISPD Administrative Services

21
CIO Council
Aligning Enterprise Architecture and ERP