State of Indiana Business One Stop (BOS) Program Roadmap Updated June 6, 2013 RFI ATTACHMENT D.

Slides:



Advertisements
Similar presentations
1. 2 August Recommendation 9.1 of the Strategic Information Technology Advisory Committee (SITAC) report initiated the effort to create an Administrative.
Advertisements

Program Management Office (PMO) Design
First create and sign up for a blue host account Through the help of Blue Host create a WordPress website for the business After you created WordPress.
Roadmap for Sourcing Decision Review Board (DRB)
Course: e-Governance Project Lifecycle Day 1
Global Business Blueprint Summary Presenters: Laurie Dempsey, CBP Lois McCluskey, eCP January 28, 2004.
<<replace with Customer Logo>>
Self-Service Business Intelligence for the Product Management Department (Concurrency Corporation)
Delivery Business Solutions April 29, Nashville PMI Symposium April 29, 2013 Stephanie Dedmon, PMP Director, Business Solutions Delivery Department.
Decision Making Tools for Strategic Planning 2014 Nonprofit Capacity Conference Margo Bailey, PhD April 21, 2014 Clarify your strategic plan hierarchy.
ECM RFP 101 Presented by: Carol Mitchell C.M. Mitchell Consulting.
ClosingExecuting/ Controlling ControllingPlanningInitiatingOpportunityAssessment Client AcceptancePlanning ApprovalInitiating ApprovalOpportunity Assessment.
Validata Release Coordinator Accelerated application delivery through automated end-to-end release management.
Financial Systems Needs Assessment Project Update Monthly Research Administrators Meeting March 11, 2010.
Dr. Julian Lo Consulting Director ITIL v3 Expert
Panorama Consulting Group LLC ERP Assessment, Selection, and Planning SAMPLE APPROACH.
Program Management Overview (An Introduction)
IT Strategic Planning Project – Hamilton Campus FY2005.
Managing the Information Technology Resource Jerry N. Luftman
Ashoka Indonesia Implementation Kick-off August 2014
1 Purchasing and Procurement Processes Module Four Revision Date: 2/06/2015.
Effort in hours Duration Over Weeks Or Months Inception Launch Web Lifecycle Methodology Maintenance Phases Copyright Wonderlane Studios.
IS&T Project Management: How to Engage the Customer September 27, 2005.
Enterprise Architecture
Web Development Process Description
Project Management Process Overview
Agenda Teams Responsibilities Timeline Homework and next steps.
New Business Architecture
Campaign Readiness Project Overview Enabling a structured, scalable approach to customer-centric campaigns.
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
State of Maine NASACT Presentation “Using the Business Case to Guide a Transformation Procurement” 1 Using the Business Case to Guide a Transformation.
What is Oracle Hyperion Planning  Centralized, web- based Budgeting and Planning application  Combines Operational and Financial measures to improve.
GBA IT Project Management Final Project - Establishment of a Project Management Management Office 10 July, 2003.
Workshop on Programming in support of Anti-Corruption Agencies Bratislava, 30 June - 1 July 2009 A methodology for capacity assessment of AC agencies:
CSI - Introduction General Understanding. What is ITSM and what is its Value? ITSM is a set of specialized organizational capabilities for providing value.
Copyright © 2004 by The Web Services Interoperability Organization (WS-I). All Rights Reserved 1 Interoperability: Ensuring the Success of Web Services.
Service Transition & Planning Service Validation & Testing
Certification and Accreditation CS Phase-1: Definition Atif Sultanuddin Raja Chawat Raja Chawat.
University of Wisconsin System HRS Project Update to ITC November 19, 2010.
Implementation Overview SHRP 2 Oversight Committee June 18, 2012.
U.S. Department of Agriculture eGovernment Program Design Approach for usda.gov April 2003.
Project Life Cycle.
Microsoft Office Project 2003: Selling EPM in your Organization Matt Wilson Business Solutions Specialist LMR Solutions.
The Development of BPR Pertemuan 6 Matakuliah: M0734-Business Process Reenginering Tahun: 2010.
Project Kick-off Meeting Presented By: > > > > Office of the Chief Information Officer.
Federal Geographic Data Committee, Coordination Group Meeting Washington, DC 7 June 2005 Study Results Geospatial Interoperability Standards: A Return-on-Investment.
U.S. Department of Agriculture eGovernment Program January 9, 2002 eGovernment Working Group Chris Niedermayer, USDA eGovernment Executive Barbara LaCour.
Business Analysis. Business Analysis Concepts Enterprise Analysis ► Identify business opportunities ► Understand the business strategy ► Identify Business.
TDRp Implementation Challenges David Vance, Executive Director Peggy Parskey, Assistant Director October 23, 2014.
Overview of RUP Lunch and Learn. Overview of RUP © 2008 Cardinal Solutions Group 2 Welcome  Introductions  What is your experience with RUP  What is.
Information Technology Services Strategic Directions Approach and Proposal “Charting Our Course”
U.S. Department of Agriculture eGovernment Program eDeployment Kickoff August 26, 2003.
State of Georgia Release Management Training
Friday Institute Leadership Team Glenn Kleiman, Executive Director Jeni Corn, Director of Evaluation Programs Phil Emer, Director of Technology Planning.
Replacing Your LMS: Why, When, What & How? When considering the viability of your LMS, it’s critical to deeply consider your organization and its needs.
1 SCR756 – Enhancements to the MarkeTrak application –Fondly called - MarkeTrak Phase 3 –ERCOT CEO determined that SCR756 is not necessary prior to the.
Project Life Presented by Chuck Ray, PMP ITS Project Manager.
University of Wyoming Financial Reporting Initiative Update April 2016.
Planning Engagement Kickoff
SAM Baseline Review Engagement
Sample Fit-Gap Kick-off
Update from the Faster Payments Task Force
Project Management Lifecycle Phases
Hyper-V Cloud Proof of Concept Kickoff Meeting <Customer Name>
Description of Revision
The Open Group Architecture Framework (TOGAF)
Project Ideation Agile Down-to-Earth © 2016.
Agenda Purpose for Project Goals & Objectives Project Process & Status Common Themes Outcomes & Deliverables Next steps.
{Project Name} Organizational Chart, Roles and Responsibilities
Presentation transcript:

State of Indiana Business One Stop (BOS) Program Roadmap Updated June 6, 2013 RFI ATTACHMENT D

Program Roadmap Overview and Objectives The BOS Program Roadmap is the recommended sequence for activities related to confirming scope and opportunity, selecting a solution partner, and deploying BOS capabilities based on priority and feasibility considerations. Objectives To document a strategy and plan for the sequencing of program activities and State of Indiana resource commitment To provide a tool for use in setting organizational expectations, planning communications to external groups, and communicating approximate project timelines To provide a means to anticipate project risks and dependencies

Program Key Success Factors The factors below have been identified through agency and benchmarking input as being critical to the success of the BOS program, and are factors in the Roadmap design. Focus on the Business Point of View: Spend time obtaining user input, and prioritize efforts and scope to provide a faster, better, and easier experience relative to addressing State requirements. Addressing Agency improvements should be considered within context of this first goal. Create a long term plan, with short term value delivery: Deliver value as quickly as possible by addressing improvements with a combination of largest impact and least effort. Cross Agency Participation and Collaboration: Facilitate collaboration and compromise to promote the greater good of addressing business user needs along with a more integrated system. Include Legal Review and Legislation: to address barriers relative to statutes Include Information Technology: the complexity of technical integration and data management should not be underestimated Clear Ownership and Governance: As databases and systems become connected, governance structure and a clear understanding of master data should be established to mitigate risks related to unintended impacts of changes. Willingness to Change Existing Processes: The potential for improvement is driven by the amount of change that can be made to existing processes. Agency stakeholders should be challenged to think about alternatives to current processes.

Roadmap for Overall Program To be updated following vendor input and RFP Complete 3-4 Months 2-4 Months 9-15 Months Ongoing 1: Program Charter and Roadmap 2: RFI and Requirements Gathering 3: RFP Development, Vendor Evaluation, & Selections 4: Solution Development & Initial Implementation 5: Operationalize and Expand Implementation Objectives Review available alternatives and obtain requirements for RFP and detailed scoping Identify solution partner and develop detailed budget Implement infrastructure & initial scope solution Set up operational structure and manage solution changes Key Tasks Facilitate Vendor Education Sessions Develop RFI Analyze Vendor Responses Conduct Functional and Technical Requirements Gathering Workshops Prioritize requirements and opportunities Develop RFP Distribute RFP Manage and Evaluate Responses Facilitate Vendor Demonstrations Select Vendor Finalize Contract Develop Budget & TCO Initiate Project Team Confirm Solution Roadmap Detailed Design (Technical and Functional) Acquire Components and Resources Implement Technology Configure System Integrate System Test System Implement System Support production environment Monitor and Report on Value Realization Increase Adoption Identify and prioritize improvements to BOS and related processes Implement new functionality Key Outputs Updated Charter RFI Vendor Evaluations and RFP Distribution List Functional & Technical Requirements RFP Vendor Selection Contract Budget and TCO Model Funding Model and Approval Detailed BOS Design Implementation Plan Solution Development Solution Implementation Operational Readiness Plan and Model Support Production System Value Realization – increased adoption and improved service model System enabled process improvements

Phase 2 – RFI and Requirements Gathering Step Activities Key Deliverables or Outputs 1. Facilitate Vendor Education Sessions Identify vendors Develop objectives and agenda Send Charter and Background Data Facilitate education sessions Document and share outputs Meeting agendas Meetings Meeting outputs for RFI and Requirements 2. Develop RFI Confirm RFI objectives and goals Identify and Contact vendors Draft RFI and review with Stakeholders Distribute RFI and Manage Responses RFI Goals Checkpoint RFI for Vendors RFI Responses 3. Analyze Vendor Responses Document responses and Summary Analysis Review Responses with Vendors (Q&A) Complete Analysis and Prioritize Vendors RFI Response Analysis Vendor Evaluation Input for Scope, Requirements and RFP 4. Develop and Prioritize Requirements Confirm scope, format, input data, and participants (with logistics) Identify and document functional and technical requirements Review and prioritize requirements and opportunities Refined Solution Scope Prioritized Technical Requirements Prioritized Functional Requirements Opportunity Analysis Input for RFP Key Success Factors: Keep vendor education sessions focused on State of Indiana needs and environment Leverage output from education and RFI to drive requirements gathering Involve Agency Legal departments in review of requirements relating to statutes Get input from the Business point of view in requirements and prioritization Identify opportunities for improvement during requirements (challenge the current state)

Phase 3 – RFP Development, Vendor Evaluation, & Selections Step Activities Key Deliverables or Outputs 1. Develop and Distribute RFP Confirm Timeline and General Requirements Consolidate Requirements and Data Build Framework for Cost Model Confirm evaluation criteria Distribute RFP to Vendors RFP Requirements Cost Framework Evaluation Criteria Final RFP 2. Manage and Evaluate Responses Respond to Vendor Questions Review and analyze responses Obtain input from stakeholders Conduct reference calls Confirm short-list of vendors Vendor Question Responses RFP Response Analysis and Scoring Vendor Short List 3. Facilitate Vendor Demonstrations Communicate and Coordinate Logistics Build Demonstration Agenda and Scripts Build Evaluation and Scoring Model Conduct Vendor Demonstrations Evaluate and Select Vendors Demo Agenda and Scripts Demo Evaluation and Vendor Scoring Model Vendor Demonstrations Vendor Selection 4. Finalize Contracts Contact Selected Vendor Obtain and Review Contract(s) Evaluate and Negotiate Proposed Contracts Finalize Contracts (pending budget approval) Draft Contract Final Contract 5. Update Budget and TCO Model Build Program Budget Model based upon RFP Responses and Vendor Contracts Build Total Cost of Ownership Model for input into budgeting processes Confirm Funding and Ownership Model Program Budget Total Cost of Ownership Approval for Funding and Funding Model Key Success Factors: Understand and confirm up- front how the vendor will be evaluated Structure components of the RFP to obtain comparable responses in key areas such as ability to meet requirements and costs Allow for flexibility in project approach Structure demonstrations to allow for comparability Allow for adequate Agency and Stakeholder participation in vendor demonstrations

Phase 3 – RFP Development, Vendor Evaluation, & Selections Solution Key Success Factors The factors below have been identified as being critical to the success of the BOS solution based upon benchmarking and agency input. These will continue to be evaluated and potentially adjusted through RFI and RFP input. Holistic View – Provides comprehensive portal to address all interactions with the State of Indiana, more integrated over time Usability – Solution must be easy for online users to understand and navigate Personalized – Ability to tailor content, workflow and security based on user’s role Security – User, role, and data security and auditability Flexibility – Ability to add new processes, transactions, and forms to the user interface Scalability – Solution must be able to handle increased users and performance demands over time Integration – Ability to share and leverage validated data across systems Lower Operational Cost – One shared platform that reduces overhead related to redundant user facing systems

Phase 4 – Solution Development and Initial Implementation To be updated following vendor input and RFP Step Activities Key Deliverables or Outputs 1. Confirm Solution Roadmap and Implementation Program Governance Build Solution Roadmap to confirm sequencing of functionality delivery Confirm project roles Identify timeline and commitments Kickoff Project BOS Solution Roadmap Project Team and Resources Implementation Plan Project Kickoff 2. Completed Detailed Design Confirm high level design of solution Conduct workshops to document needs for business rules, integration, reporting, workflow, etc.. Confirm technology scope Document changes required to support solution (organizational, process, etc…) Acquire components Detailed BOS Design Component acquisition Change Plan Quality Plan 3. Build, Configure, and Test Solution Implement acquired technology Build solution components Configure solution components Transform and cleanse existing data Build test plans Conduct testing Address issues and bugs Acquired technology components Configured Solution Test Plans and Results (System, Security, Performance, User Acceptance, Network) 4. Implement Solution Build implementation cut over plan Deliver Communications (i.e. Marketing, web, internal, etc..) End User and Administrator Training Finalize Operational Readiness Plan Training Plan Communications Solution Implementation Operational Readiness Plan Key Success Factors: Focus on meeting and testing against business user expectations Ability to leverage as much existing data as possible to ease transition for existing business users Focus on operational readiness and support capability Collaboration for design, configuration, and testing Change Management and Training to address new internal processes and user expectations Project Management to address stakeholder needs and manage a broad team

Phase 5 – Operationalize and Expand Implementation As the initial BOS solution is implemented, the State of Indiana will need to have in place a structure to support BOS alongside the program team, who will focus on future phase implementation components. Ongoing Program Implementation: Each phase of implementation will have is own set of detailed design and implementation activities, focused on new functional and technical scope to be confirmed during Phase 4. Operational Support and Management Provide operational support for BOS system(s) and processes (i.e. call center) Monitor and report on value realization Measure and increase adoption amongst business community and users Measure process efficiencies in terms of speed , costs, and support required Ongoing improvement for BOS and related processes Survey user base and agencies for improvement opportunities and prioritization Implement new releases (along with or including new processes or integrations)