MFWCAA Conference MEC² Integration Project Transition to Economic Stability Division Transition Support Systems Division.

Slides:



Advertisements
Similar presentations
1 Unified Information Technology System Development – Project Overview Board of Early Education and Care February 10, 2009.
Advertisements

1. 2 August Recommendation 9.1 of the Strategic Information Technology Advisory Committee (SITAC) report initiated the effort to create an Administrative.
The Value of a Project Management Office Copyright: Kathy J. Lang, 2004.
ERP Applications Selection in a Changing Marketplace Evaluation of Software Providers for Midsize Institutions Bill Reed Director, Special Projects Northern.
System Development Life Cycle (SDLC)
© 2007 AT&T Knowledge Ventures. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Knowledge Ventures. Interactive Solutions & Design Group.
DC Access System (DCAS)
Getting a XBRL Project Up and Running. Mr John Morgan UBmatrix Australia th XBRL International Conference “Getting.
Rational Unified Process
READ THIS SLIDE CAREFULLY The intent of this presentation is to provide an “Executive Summary” of your project to Design Day attendees and judging panel.
Copyright © 2006 by The McGraw-Hill Companies, Inc. All rights reserved. McGraw-Hill Technology Education Copyright © 2006 by The McGraw-Hill Companies,
1 April 2010 TX SET Timeline Project Conceptualization 11 weeks Market Requirements 12 weeks ERCOT Requirements 12 weeks Conceptual Design 6 weeks Detail.
Pertemuan Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
Technology Use Plan Mary Anderson 7/29/08 EDTECH 571 click to go to each slide.
LBNL Budget System Proposal Finance Network October 14, 2004.
Putting the We in… We are Penn State! Copyright [Carol Findley, Lisa Dibert] [2003]. This work is the intellectual property of the authors. Permission.
Disabled Children and Adults Pathfinder Every Deaf Child Matters Conference 26 th June 2012.
National Finance Center’s 2008 Customer Forum EmpowHR 9.0 Billy Dantagnan Teracore.
Release & Deployment ITIL Version 3
Annual SERC Research Review - Student Presentation, October 5-6, Extending Model Based System Engineering to Utilize 3D Virtual Environments Peter.
Revenue Cycle Management Medical Technology Acquisition and Assessment Team Members: Joseph Dixon, Michael Morotti, Mari Pirie-St. Pierre, David Robbins.
SYSTEM ANALYSIS AND DESIGN
Summary of SCETC RFP for Enterprise Application Suite Presented By: Catrina Howatt Board Meeting: November 13, 2012.
Systems Analysis and Design: The Big Picture
May Agenda  PeopleSoft History at Emory  Program Governance  Why Upgrade Now?  Program Guiding Principles  High-Level Roadmap  What Does This.
Improper Authorizations for Payment October 21, 2008.
Chapter 2: Approaches to System Development
Copyright Course Technology 1999
IT Project Management Cheng Li, Ph.D. August 2003.
INFORMATION TECHNOLOGY FOR MINNESOTA GOVERNMENT MNsure IT 2015 Overview March 26, 2015.
Roles and Responsibilities
Software Engineering Chapter 15 Construction Leads to Initial Operational Capability Fall 2001.
Original VIP Intranet Template The original (state approved) template used a two-column layout and bright red/blue color combination The colors, while.
1 ISA&D7‏/8‏/ ISA&D7‏/8‏/2013 Systems Development Life Cycle Phases and Activities in the SDLC Variations of the SDLC models.
Chapter 14 Information System Development
Relationships July 9, Producers and Consumers SERI - Relationships Session 1.
Role-Based Guide to the RUP Architect. 2 Mission of an Architect A software architect leads and coordinates technical activities and artifacts throughout.
1 E-911 Services Board Meeting General Business Meeting September 8,
1 OSU-Okmulgee Assessment Plan 2003 Welcome to Phase I Training.
Object-oriented Analysis and Design Stages in a Software Project Requirements Writing Analysis Design Implementation System Integration and Testing Maintenance.
Project Life Cycles.
Module 2: Creating a Plan for Network Security. Overview Introduction to Security Policies Designing Security by Using a Framework Creating a Security.
U.S. Department of Agriculture eGovernment Program eGovernment Working Group Meeting February 11, 2004.
Information Systems Engineering. Lecture Outline Information Systems Architecture Information System Architecture components Information Engineering Phases.
Presentation to the Information Services Board March 6, 2008 Bill Kehoe, Chief Information Officer Bill Kehoe, Chief Information Officer.
Fifth Lecture Hour 9:30 – 10:20 am, September 9, 2001 Framework for a Software Management Process – Life Cycle Phases (Part II, Chapter 5 of Royce’ book)
ERP at The University of Nebraska: Defining Roles Don Mihulka, University of Nebraska Dave Reifschneider, Prescient Consulting Jim Buckler, Prescient Consulting.
Project Kick-off Meeting Presented By: > > > > Office of the Chief Information Officer.
Systems Analysis and Design in a Changing World, Fourth Edition
This material was developed by Oregon Health & Science University, funded by the Department of Health and Human Services, Office of the National Coordinator.
Systems Analysis & Design AUTHOR: PROFESSOR SUSAN FUSCHETTO 10/24/
RBS/RATEX Direction Update Larry G. Daniels, CSP, EVP/COO RATEX Business Solutions, Inc Hickory Road, Suite 10 Plymouth Meeting, PA (800)
Rational Unified Process (RUP)
IS2210: Systems Analysis and Systems Design and Change Twitter:
State of Georgia Release Management Training
University of Wyoming Financial Reporting Initiative Update April 2016.
ITIL® Service Asset & Configuration Management Foundations Service Transition Thatcher Deane 02/17/2010.
Canadian SNOMED CT Strategy October 2012 Draft. Content 1 Background Approach Current State Future State Considerations Action Plan.
TK2023 Object-Oriented Software Engineering
Roles and Responsibilities
Fundamentals of Information Systems, Sixth Edition
Systems Analysis and Design in a Changing World, 4th Edition
Project Charter General Information Project Title Date
Project Initiatives Identified by the CIA Project
Department of Licensing HP 3000 Replatforming Project Closeout Report
Presentation to Project Certification Committee, DoIT August 24, 2008
McGraw-Hill Technology Education
System Analysis and Design:
IT Next – Transformation Program
Presentation transcript:

MFWCAA Conference MEC² Integration Project Transition to Economic Stability Division Transition Support Systems Division

MEC² Integration Project A brief history What is the “MEC² Integration Project”? Where are we now?

A brief history CCAP was part of the Department of Children, Families and Learning when the current MEC² system was developed and implementation started When Governor Pawlenty took office, he renamed CFL as the Department of Education and CCAP (and MEC²) was moved to DHS CFL and DHS staff began working together on the current MEC² system in May 2003

A brief history As part of the move to DHS, management asked for an assessment of the MEC² system At this point in time, MEC² was partially rolled out to counties – 45% had or were near the end of transition MEC² Assessment was completed by Computer Aid, INC (CAI) –Assessment of: Project methods Application of tools Quality of work done

A brief history Recommendation of assessment was to move forward with MEC² - it also included a study of combining MEC² and MAXIS As with any new system, problems were identified with MEC² that needed to be fixed As staff investigated the problems, basic structural and functional issues were found that made maintenance and enhancements extremely difficult Management asked for an investigation of options for addressing these issues to stabilize the system and allow future enhancement

A brief history Three plans were created for addressing the structural and functional issues: –Stabilization Plan – prioritizing and fixing the various problems –Plan to create a new stand-alone system –Plan to create a new release of MEC², integrated with MAXIS After analysis of the three plans and the time required for completion of each, CFS Management approved the integrated option which was then submitted to DHS Executive Systems

A brief history What does “integrated” mean? –Child Care data is included in the MAXIS database –Shares the data in common with cash, FS and HC –Uses the MAXIS infrastructure for backend processing (such as the background processing for eligibility determination and batch processing like issuance) –Maintains a web-based graphical (point & click) front end – a different “window” or view into the data

A brief history Why recommend an integrated option? –Leverages the following items: MAXIS infrastructure for database normalization Batch processing Effective dating Interfaces and integration with SMI, PRISM, issuance and security

A brief history Why recommend an integrated option? (cont.) –Supports the CFS Futures Vision, the ITS Strategic Plan and Governor’s Drive to Excellence by reducing the number of system silos and creates the base for MAXIS modernization –Best option for meeting the aggressive timeline as experienced MAXIS staff can be added to work on back-end components.

A brief history DHS Executive Systems gave approval to proceed with an integrated option, provided counties approved of the option County feedback was very supportive of integrated MEC²-MAXIS option –Expressed their trust in systems developed by TES/TSS staff –Expressed confidence in the MAXIS system infrastructure –Raised concern that MEC² system continue to be supported at the current level during integrated system development phase DHS Executive Systems gave final approval to project on 1/20/05

What is the “MEC² Integration Project”? The goal of the MEC² Integration Project is to provide an accurate, stable Child Care Assistance Program (CCAP) system (Minnesota Electronic Child Care – MEC²), extendable to and integrated with the MAXIS infrastructure that is secure, easy to maintain, flexible and user friendly.

What is the “MEC² Integration Project”? We must implement the core system (including graphical user interface) and develop training by 7/1/06 Workers must not take a step backwards in terms of functionality with the implementation of the new release of MEC² Counties using CSIS for child care payments must be converted to the new release of MEC² no later than 12/31/06 Coordinate with the large number of changes affecting counties (HealthMatch, SSIS-Fiscal, SMI)

What is the “MEC² Integration Project”? The decisions we are making today for the child care solution need to keep in mind the strategic vision of modernizing MAXIS and bringing it to the same level of having a graphical user interface. time Strategic vision x x x MAXIS GUI Child Care System Where we are today

What is the “MEC² Integration Project”? At this time, the scope for the 7/1/06 release includes: –Graphical user interface (point & click) –Provider registration and maintenance –Client eligibility and co-payment determination –Service Authorizations –Billing –Payments (including issuance from the IOC, corrective payments and remittance advices with payments) –Re-determination processing –Client and provider notices and correspondence

What is the “MEC² Integration Project”? At this time, the scope for the 7/1/06 release includes: –Reports –Claim establishment and recovery processing –Provider withholding –Interfaces (Finance, Licensing, SMI, PRISM) –Case management tools Periodic processing Alerts Case notes Case transfer (within county & move to new county)

What is the “MEC² Integration Project”? At this time, the scope for the 7/1/06 release excludes: –Waiting list functionality –Budget Projection Tool –HealthMatch interface –WorkForce One interface –Maintenance of the existing MEC² system (this is part of another project)

Where are we now? Project Planning Team has developed the project charter and scope focus statements –Project charter is a high-level statement of what we intend to accomplish - was approved by the sponsors (Kate Wulf and Ann Sessoms) on 3/11/05 –Detailed scope focus statements were created to further define scope inclusions and exclusions – these statements were approved 5/2/05 – this is the maximum scope for the project at this point

Where are we now? Business analysis and design are in progress, focusing on the core building blocks of the system: –Case establishment & client data collection –Provider registration & maintenance –Eligibility & co-payment determination –Service Authorizations –Billing –Payments

Where are we now? Graphical presentation standards are being developed –Prototype was created to demonstrate the navigation and look & feel of the system – presented to the County Advisory Committee & MEC² User Group on 8/15/05 – positive feedback received –All panels created by the business analysts are undergoing the scrutiny of the GUI standards lead analyst to ensure consistency and usability

Where are we now? (cont.) Technical work is progressing on security, technical standards and issues related to the platform –Proof of Concept was completed using the components planned for the new release of the MEC² system – it was successfully deployed to our server at OET (formerly known as Intertech) Work is also progressing on the Java object modeling and Adabas file design – plan is to begin construction of the core building blocks the first of October

Where are we now? (cont.) As the core building blocks are established, the focus will shift for both technical and business groups to the next iteration of development, including, but not limited to notices, financial interfaces and reports, and claims processing. Details concerning the project schedule, timeline and roll-out schedule are being hammered out Implementation and conversion are planned to begin 7/1/06

Wrap Up Questions? Comments? Suggestions?