1 / 8

CMS Migration to SiteManager

CMS Migration to SiteManager. Division of Construction Management. C onstruction M anagement S ystem. CMS was implemented in 1993 First large system that made use of PCs, client-server software, and local and wide area networks. CMS pushed ODOT into the age of information technology.  .

fadhila
Download Presentation

CMS Migration to SiteManager

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CMS Migration to SiteManager Division of Construction Management

  2. Construction Management System • CMS was implemented in 1993 • First large system that made use of PCs, client-server software, and local and wide area networks. • CMS pushed ODOT into the age of information technology.   2010 Conaway Conference

  3. Why Move to SiteManger? CMS SiteManager • High cost to maintain • CMS is a mainframe application and ODOT is moving in the direction of removing all applications from Supra 2X • Unable to make significant enhancements to the application • Slow speed • No archive capabilities. Every project imported into CMS since 1993 is still in CMS • Limited to no growth for the future • Same vendor developed CMS • Vendor maintenance releases and yearly upgrades • ODOT can submit and gets to vote on enhancements • SiteManager is part of the AASHTO product line which integrates with PES/LES, BAMS/DSS, Expedite, Estimator, SiteXchange • 21 other states use SiteManager - Large user support community • Growth for Future – off-line capabilities, standard electronic doc. templates, key-event e-mail distribution, file attachment, and an archive module 2010 Conaway Conference

  4. Old Vs New 2010 Conaway Conference

  5. Pilot • Implementation – March, 2010 • 24 identified multi-year projects • 7 districts • First projects to start work in March, 2010 • Begin user training in February, 2010 • No conversion projects until 2011 2010 Conaway Conference

  6. A Few Things to know • SiteManager projects will run in parallel with CMS until ODOT is confident SiteManager is working correctly. • SiteManager will run in a terminal services environment located at the SOCC instead of being installed locally on the PC’s. No more updates to download. • CMS Portal reports are being rewritten to reflect SiteManager terminology and pull project data. • A SiteManager GQL data model has been built. • Virtual Warehouse and WebCMS are being rewritten to pull SiteManager project data. 2010 Conaway Conference

  7. Terminology Changes • SiteManager Contract ID Vs CMS Project Number • Contract ID = MOT77246 (county/PID) • Project Number = 09-0103 • SiteManager Line Item Vs CMS Reference Number • Line Item = 0001 • Reference Number = 1 • SiteManager Alt. ID Vs CMS Project Number • Alt. ID = 09-0103 • Project Number = 09-0103 • SiteManager Project Number Vs CMS Part Code • Project Number = MOT77246-1/4 (Funding Identifier) • Part Code = 01 2010 Conaway Conference

  8. Challenges • CHANGE • Large project that involves many internal and external customers • CHANGE • Largest IT system implementation since the implementation of CMS • CHANGE • Training and Support • CHANGE • Marketing • CHANGE 2010 Conaway Conference

More Related