State of Washington Roadmap for Financial and Administrative Policies, Processes and Systems IPMA Forum 2005 Roadmap Program - PowerPoint PPT Presentation

1 / 33
About This Presentation
Title:

State of Washington Roadmap for Financial and Administrative Policies, Processes and Systems IPMA Forum 2005 Roadmap Program

Description:

State of Washington Roadmap for Financial and Administrative Policies, Processes and Systems IPMA Forum 2005 Roadmap Program May 24th, 2005 What is Enterprise ... – PowerPoint PPT presentation

Number of Views:221
Avg rating:3.0/5.0
Slides: 34
Provided by: brste
Category:

less

Transcript and Presenter's Notes

Title: State of Washington Roadmap for Financial and Administrative Policies, Processes and Systems IPMA Forum 2005 Roadmap Program


1
State of Washington Roadmap for Financial and
AdministrativePolicies, Processes and
SystemsIPMA Forum 2005Roadmap Program
  • May 24th, 2005

2
Agenda
Enterprise Architecture 15 min
Roadmap background 15 min
Applying EA to the Roadmap 25 min
Roadmap next steps 15 min
Q A 15 min
3
What is Enterprise Architecture?
  • Analogous to Building Architecture
  • Ensures the building matches the needs of the
    occupants - One size doesnt fit all
  • Provides multiple interrelated views to maintain
    context - e.g. plumbing, electrical, structural
  • Uses engineering principles to improve the
    likelihood of successful completion

4
ISB Enterprise Architecture Committee
Dennis Jones, OFM (co-chair)
Thomas Bynum, ESD
Sue Fleener, WSP
Cathy Munson, LSC
Christy Ridout, DSHS (co-chair)
Julian Soh, DOR
Tom Miller, DOP
Laura Parma DIS
Greg Brant, DIS (non-voting)
5
State of Washington Commonality Tiers
6
WA Tier One Enterprise Architecture Framework
Environmental Trends Business Drivers
Information (Data) Business
Technology
Inf. Subject Areas
Business Domains
Technology Domains
Information Vision Strategies
Business Vision Strategies
Technology Vision Strategies
Information Policies Standards
Maps and Linkages
Maps and Linkages
Business Policies Standards
Technology Directions
Information Models
Technology Policies Standards
Business Process Models
Common Datasets
Solution Architecture Services, Patterns,
Applications
7
The States Enterprise Architecture (EA) Program
  • A framework for decision-making
  • Principles driven
  • Focused at Tier One
  • Roadmap identified as EA early adopter

8
  • Roadmap Background

9
Current factors influencing Washington State
government
  • Significant budget shortfall
  • Priorities of Government
  • Personnel System Reform Act of 2002
  • Collective bargaining
  • Civil service reform
  • Competitive contracting
  • Government Management, Accountability and
    Performance

10
The time is right
11
About the Roadmap
  • The Roadmap project draws together agencies and
    central service providers to create a
    comprehensive plan for the transformation of
    Washington State financial and administrative
    policies, processes and information systems to
    solve todays common business problems with
    enterprise tools and best practices.

12
Roadmap Business Goals
  • Better information for better results
  • Improved management systems
  • Streamlined business processes

13
Scope
Risk Management
Projects Management
Decision Support
14
Roadmap challenge Fragmented governance
responsibility
15
Roadmap challengeInefficient business processes
2004 Financial Baseline Assessment
  • Typical financial benchmarks measure payments per
    A/P staffer
  • Data from 10 state agencies suggest that
    productivity lags benchmarks
  • Core payables processing was found to be the most
    labor intensive activity

16
Common business problems opportunities
17
Agency Prioritization Survey ResultsForced
ranking - All agencies
18
Agency Prioritization survey results
  • Over 50 central systems
  • 220 known agency shadow systems
  • Nearly 20,000 known desktop tools (spreadsheets,
    databases, etc.)

19
Business Case Value Themes
  • Better information, better results
  • More economical government
  • Better customer and business relationships
  • Optimized return on investment

20
  • Applying
  • Enterprise Architecture
  • to the Roadmap

21
Enterprise Architecture Approach
  • A framework for decision making using
  • Principles
  • Models
  • Policies
  • Standards

22
Architecture Principles
  • Applied ISB adopted architecture principles
  • Commonality - Should be common where there is a
    clear business case once designated as common,
    justification is required to deviate
  • Business alignment - Should align projects and
    investments based on Priorities of Government
    (POG)
  • Natural boundaries - Should be designed around
    natural boundaries
  • Other important principles
  • Do no harm to HRMS

23
Models - Functional Decomposition
24
Lessons Learned
  • Additional principles are derived from lessons
  • learned in other states and HRMS
  • Ensure strong sponsorship and governance
  • Focus on business outcomes not systems
  • Agree on common policies, processes, and data
    before picking system solutions
  • Transform incrementally
  • Agree on strategy for integrating new systems
    into the existing environment

25
Developed the Roadmap
  • Defined initial Roadmap business initiatives,
    projects and timeline based on

26
(No Transcript)
27
  • Roadmap Next Steps

28
Next Steps
  • Confirm executive sponsorship
  • Establish Roadmap governance
  • Begin the Foundation Initiatives
  • Business modeling
  • Integration architecture model
  • Enterprise service delivery model
  • Feasibility study
  • Acquisition
  • Budget request / decision package

29
Next Steps Business Process Modeling
  • ISB Enterprise Architecture Committees
    principles
  • Key Decisions
  • Designate Roadmap Business Processes as Tier One
    Common Statewide?
  • How do we align our business processes?
  • What best business practices do we want to adopt?

Commonality Business Ownership
Natural boundaries Business Continuity
30
Next StepsBusiness Process Modeling
  • Identify enterprise data standards
  • Key Decision
  • How do we maintain agency flexibility while
    leveraging statewide data to improve operations?
  • Evaluate functionality of solution alternatives
    against core business processes using models
  • Key Decision
  • What software products best implement our desired
    best practices?

31
Next StepsIntegration Strategy
  • Defining an Integration Architecture
  • Connect the legacy systems to the new environment
    as we transition
  • Assist agencies to connect their core system with
    new systems
  • Data standards, exchange formats, services and
    components, multiple models
  • Key Decisions
  • What are the critical success factors in creating
    a durable enterprise wide integration
    architecture?
  • How do we insulate systems from changes in
    interface requirements as we transition?

32
  • Q A

33
Roadmap contacts
  • Sadie Rodriguez-Hawkins, 360-664-7650,
    Sadie.Hawkins_at_ofm.wa.gov
  • Dennis Jones, 360-664-7695, Dennis.Jones_at_ofm.wa.go
    v
  • Kathy Rosmond, 360-664-7771, Kathy.Rosmond_at_ofm.wa.
    gov
  • Allen Schmidt, 360-664-7732, Allen.Schmidt_at_ofm.wa.
    gov
  • Visit the Roadmap website at
  • http//www.ofm.wa.gov/roadmap/default.htm
Write a Comment
User Comments (0)
About PowerShow.com