e-Manifest Tracking System Project

1
e-Manifest Tracking System Project
2
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

3
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

4
Michigan DEQ Hazardous Waste Manifest Processing
UnitApril, 2007
5
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

6
2. Project Overview (contd)

• Solution

7
3. Project Challenges

• Challenges/Risks
• Private industry interest and acceptance
• Compatibility with National electronic
  manifesting initiative
• Adoption by EPA Office of Solid Waste

8
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 (SMEs)
• Project Support
• Contractor

9
4. Project Team (contd)

• 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

10
4. Project Team (contd)

• Steering Committee Responsibilities
• Main agency project representative
• Approve project schedule
• Commit agency resources
• Authorize scope, resource and budget
  modifications
• Ensure senior management project commitment

11
4. Project Team (contd)

• 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

12
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

13
5. Project Tasks and Schedule (contd)

• Phase 1 Tasks
• Initiation and Project Management
• Business Process Analysis and Technology Research
• State Readiness Assessment
• Infrastructure Preparation to Support e-Manifest
  Data Flow

14
5. Project Tasks and Schedule (contd)

• 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

15
5. Project Tasks and Schedule (contd)

• 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

16
5. Project Tasks and Schedule (contd)

• Schedule

Task Start Date End Date
e-Manifest Tracking System Project Plan 1/24/2007 11/5/2008
Phase 1. Project Initiation, Business Process Analysis, Technology Research, Infrastructure Preparation 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
Phase 2. Design and Development of a Central e-Manifest Tracking System 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
Phase 3. State e-Manifest Data Flow Design and Development 11/9/2007 3/24/2008
Design State Specific e-Manifest Data Flows 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
Produce System Documentation 7/15/2008 7/28/2008
Phase 5. Post Implementation / Lessons Learned 7/29/2008 11/5/2008
Post Production Support 7/29/2008 10/29/2008
17
5. Project Tasks and Schedule (contd)

• Key areas of involvement

18
6. Project Controls

• Communication
• Project Web site
• Status reporting
• Meeting minutes
• Deliverables and documentation
• Acceptance Criteria
• Issue Management
• Risk Management

19
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

20
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

21
Contact

• Michael Beaulac
• State Assistant Administrator
• Executive Division
• 517-241-7808
• beaulacm_at_michigan.gov