Implementing SiteManager in a non-P/L/C State Dawn E. Scheel, P.E. TxDOT

Project Goals Successful Implementation of SiteManager Successful integration with TxDOT legacy systems Acceptance of SiteManager software amongst user community

Issues as a Non P/L/C Need to develop interfaces to existing TxDOT legacy systems including contract load utility Need to set up and load Code Table data which would have come from P/L/C Change Management Issue of using a joint development product instead of in house system

Implementation Stages Stage I - Project Initiation  Stage II - Implementation Requirements  Stage III - Design & Iteration Planning Stage IV - Development & Integration Stage V - Deployment

Stage I - Project Initiation Beta Test State for AASHTO Initial Planning and Budgeting –LBMS Project Engineer Methodology –Detailed Project Plan - MS Project –Preliminary Budget & Cost/Benefit Organized Project Team –Structure –Resources Obtained Administrative Approval

Stage II - Implementation Requirements Documented Current Business Practices Identified and Resolved Business Issues Identified and Resolved Gaps Established Security Groups & Code Tables Developed TxDOT Training Plan and Materials Designed Materials Sampling & Testing Approach Mapped data to and from existing legacy systems

Stage III - Design & Iteration Technical Issues –Test Strategy & Plan –Technical Architecture Testing & Design –Interface Design –Custom Report Development Business Issues –Sampling and Testing Set-Up –Training Material Preparation –Revise Policies & Procedures

Stage IV - Development & Integration Stage IV - Development & Integration Test Scripts Interface Development & Testing Pilot & Fine Tune Training Materials/Presentations

Stage V - Deployment Technical & Support Infrastructure set up Waco live late July month assessment period San Antonio live October month assessment period Remaining districts starting December 2000 Rate of one district per month All districts live by October 2002

Implementation Approach Initial Implementation Visit to each District Readiness Checklist Visit 2 months prior to Implementation Initially only new contracts. Goal of one contract per area office with initial training

Training and Support Training in the Districts One week of on-site support following training 3 Tiered Help Desk Support CST Support Team (4+4) On-line Help

Recommendations for Success Keep the end user needs first. Make sure you are improving their work and not making more work Have visible and active support from the top Line up technical support from the start Have dedicated project team

QUESTIONS?