eManifest Tracking System Project Overview 1 Introduction Problem
e-Manifest Tracking System Project
Overview 1. Introduction – Problem Statement 2. Project Overview 3. Project Challenges 4. Project Team 5. Project Tasks and Schedule 6. Project Controls 7. Current Status
Introduction – Problem Statement ® Problem Example: Michigan receives ~40, 000 paper manifests/mo - 2, 800/day ® Each manifest reviewed by State to verify: ® the waste shipment amounts, and ® that shipments have been delivered to treatment, storage, and disposal (TSD) facilities in a timely manner ® Once paper manifests are received, some states transfer them to electronic formats - scanning, microfilm, and/or manual data entry ® Manual validation & processing requires full-time resources ® leads to data quality problems, and ® timing issues related to regulatory response time
Michigan DEQ Hazardous Waste Manifest Processing Unit April, 2007
2. Project Overview Goals: ® Pilot an electronic manifest process using the Exchange Network as the enabler ® Eliminate current paper based processing burden, including manual validation by state regulators ® Drastically improve intra-state and inter-state cradle to grave tracking of hazardous waste by providing rapid access to data consumers
2. Project Overview (cont’d) Solution:
3. Project Challenges/Risks: ® Private industry interest and acceptance ® Compatibility with National electronic manifesting initiative ® “Adoption” by EPA Office of Solid Waste
4. Project Team Roles: ® Team Members – EPA, Massachusetts, New Jersey, Minnesota and Michigan, Windsor Solutions ® Project Management ® Michael Beaulac, MDEQ ® Mark Breithart, MDIT ® Jason Bunker, Windsor Solutions ® Steering Committee ® Subject Matter Experts (SME’s) ® Project Support ® Contractor
4. Project Team (cont’d) Project Manager Responsibilities: ® Chair project team ® Resource coordination ® Facilitate issue resolution ® Monitor project status ® Ensure project objectives & requirements are met ® Deliverable acceptance and sign-off
4. Project Team (cont’d) Steering Committee Responsibilities: ® Main agency project representative ® Approve project schedule ® Commit agency resources ® Authorize scope, resource and budget modifications ® Ensure senior management project commitment
4. Project Team (cont’d) SME Responsibilities: ® Provide vision for business and application designs ® Participate in requirements gathering and design sessions ® Review and comment on delivered documentation ® Participate in testing phases of prototype solution Subject matter experts identified
5. Project Tasks and Schedule Major Phases: ® Phase 1: Project Initiation, Business Process Analysis, Technology Research, Infrastructure Preparation ® Phase 2: Design and Development of a Central e. Manifest Tracking System ® Phase 3: State e-Manifest Data Flow Design and Development ® Phase 4: State e-Manifest Data Flow Installation ® Phase 5: Post Implementation/Lessons Learned
5. Project Tasks and Schedule (cont’d) Phase 1 Tasks: ® Initiation and Project Management ® Business Process Analysis and Technology Research ® State Readiness Assessment ® Infrastructure Preparation to Support e-Manifest Data Flow
5. Project Tasks and Schedule (cont’d) Phase 2 Tasks: ® Development of a Central e-Manifest Schema for Data Exchange ® Central Manifest Tracking System Design and Development ® Agreement for, and Acquisition of Mobile Devices
5. Project Tasks and Schedule (cont’d) Phase 3 Tasks: ® State-Specific Data Flow System Design Documents ® State-Specific Data Flow Development Phase 4 Tasks: ® Configure test and production environments ® Migration and Data Flow Installation ® Conduct e-Manifest & Tracking System User Training Phase 5 Tasks: ® Post Production Support
5. Project Tasks and Schedule (cont’d) Schedule: Task Start Date e-Manifest Tracking System Project Plan End Date 1/24/2007 11/5/2008 1/24/2007 4/16/2007 Project Initiation and Project Management 1/24/2007 3/9/2007 Business Process Analysis and Technology Research 2/13/2007 4/16/2007 State Readiness Assessment 3/12/2007 4/11/2007 Infrastructure Preparation to support e-Manifest data flow 3/12/2007 4/13/2007 4/17/2007 11/8/2007 Develop Central e-Manifest Schema 4/17/2007 10/16/2007 Design and Develop CMTS 4/17/2007 11/8/2007 Develop Mobile CMTS 6/22/2007 11/6/2007 11/9/2007 3/24/2008 Develop State Specific e-Manifest Data Flows 12/20/2007 3/4/2008 Phase 4. State e-Manifest Data Flow Installation 3/25/2008 7/28/2008 Configure Test and Production Environments 3/25/2008 6/5/2008 Migration and Data Flow Installation / Implementation 6/6/2008 7/14/2008 Conduct e-Manifest & Tracking System User Training 6/6/2008 7/21/2008 7/15/2008 7/28/2008 7/29/2008 11/5/2008 7/29/2008 10/29/2008 Phase 1. Project Initiation, Business Process Analysis, Technology Research, Infrastructure Preparation Phase 2. Design and Development of a Central e-Manifest Tracking System Phase 3. State e-Manifest Data Flow Design and Development Design State Specific e-Manifest Data Flows Produce System Documentation Phase 5. Post Implementation / Lessons Learned Post Production Support
5. Project Tasks and Schedule (cont’d) Key areas of involvement:
6. Project Controls ® Communication ® ® ® Project Web site Status reporting Meeting minutes Deliverables and documentation Acceptance Criteria Issue Management ® Risk Management ®
7. Current Status To Date: ® Developed detailed Project Plan ® Project Web Site: ® http: //www. windsorsolutions. biz/emanifest ® http: //emanifest. windsorsolutions. biz ® Implemented project management protocols
7. Current Status To Date: ® Business Process Analysis & Technology Research ® Coordinated and scheduled initial state requirements gathering workshops ® Worked with industry lobby (Environmental Technology Council) and EPA to acquire industry representatives
Contact Michael Beaulac State Assistant Administrator Executive Division 517 -241 -7808 beaulacm@michigan. gov
- Slides: 21