TOAMS Data Collection Tool For Traffic Asset Data


TOAMS Data Collection Tool For Traffic Asset Data000417b6df56f4ae5bbf-f6bd2cfeac0f4625637eac684e9e6a05.r25.cf1.rackcdn.com/...

0 downloads 336 Views 40KB Size

TOAMS Data Collection Tool For Traffic Asset Data Project Title Vendor

TOAMS Data Collection Tool – Development and Deployment Atkins Global (formerly PBS&J) (tentative)

Sponsor / Champion

William Johnson DTD IMB GIS Section Manager GPVII

Project Manager

Mark Harrington DTD IMB GIS Specialist GP III

Duration

Four months from Notice to Proceed (tentative)

SOW Date

06/14/2013

BACKGROUND In 2006, Region 3 Traffic contracted for and deployed SAMS, the Sign Asset Management System. Seeing its success, Region 1 expanded this system, contracting for two versions of TOAMS, the Traffic Operations Asset Management System. Region 1 has also been successful in using this system for sign inventory and management. The current version of TOAMS meets the following business needs. 1. Enables CDOT to collect and validate sign asset data, including GIS referencing data for map overlays. 2. Enables users to quickly and easily locate assets in order to assess needed repairs or replacement. 3. Allows users to generate and track work orders, ensuring all assets are kept up-to-date. 4. The reporting module of TOAMS allows the generation of reports for all levels of the organization, from field inspectors to top management. PROJECT PROPOSAL The TOAMS Data Collection Tool needs to provide the ability to collect traffic asset data on the road, where these assets are actually located. Whereas earlier and current versions of TOAMS include support for work order management, this tool focuses on field data collection. Other components of TOAMS provide work orders and reports, and these functions must remain as they are, and fully available to current and future TOAMS users.

Page 1

6/17/2013

TOAMS Data Collection Tool For Traffic Asset Data CURRENT SYSTEM NEEDS TOAMS currently has some deficiencies that prevent it from being effectively adopted by every traffic section. Developing version 3 intends to overcome these deficiencies. 1. Current TOAMS runs only on ArcGIS 9.x. This version is not supported by DTD. 2. Separate TOAMS versions (mostly the database) need to be built for each separate traffic section. 3. TOAMS can only be administered by the traffic section that uses it. 4. TOAMS administrators cannot modify tables to keep up with changes to devices, hardware, and MUTCD. 5. Condition data collection is not contained in TOAMS. 6. TOAMS users need more extensive QC while collecting traffic data. 7. TOAMS field collection software runs only on laptops. This proposal expects that Atkins Global will be the sole-source contractor. DATA COLLECTION TOOL REQUIREMENTS This section lists the functional and system requirements for the upgrade of TOAMS Data Collection Tool. 1. Upgrade TOAMS Data Collection Tool (both the field data collector and check-in / checkout manager) to run on ArcGIS 10.1. 2. Revise software architecture so that TOAMS be centrally managed. Includes converting database from personal SQL Server to a single enterprise SQL server that contains the entire TOAMS database. Continue to use check-in and check-out to manage change and quality control, enabling multiple simultaneous disconnected data collection users. Secure network connection to CDOT’s network is only required during data check-out and check-in. 3. Enable TOAMS administrator(s) to easily modify reference tables to keep up with changes to specifications relating to devices, hardware, and MUTCD. 4. Traffic asset types included in this proposal are limited to sign locations, sign poles, sign panels, connection hardware, hardware attached to poles, stencils, luminaires. The user interface will be arranged so that collecting data about different assets will be easy to learn and use. This may mean arranging asset type collection interfaces into separate tabs. 5. Export data into Excel spreadsheets. 6. Build out TOAMS ArcGIS MXDs for each CODT Region / Traffic Section. 7. Provide selected additional data QC on collected traffic data. Implement within the field data collector. Traffic management needs to specify these additional needs in detail. 8. Components of the TOAMS data collection tool are designed to be readily upgraded as hardware, software, and system software evolve. Component interfaces are well designed and specified.

Page 2

6/17/2013

TOAMS Data Collection Tool For Traffic Asset Data PROJECT DELIVERABLES This section lists the deliverable components of this project. These items are delivered from the contractor to CDOT by the end of the project. 1. Complete working software containing the TOAMS Data Collection Tool and the TOAMS administrator tool, plus all other components of TOAMS that were revised in order function with the newest versions of the TOAMS Data Collection Tool and the TOAMS administrator tool. 2. Training material for users of the TOAMS Data Collection Tool. 3. Training material for TOAMS administrators. 4. TOAMS system administration guide. 5. TOAMS system architecture description. 6. TOAMS source code for all components. DATA COLLECTION BUSINESS PROCESSES This section lists business process requirements. The upgrade to the TOAMS Data Collection Tool depends on understanding these requirements. 1. DTD’s GIS Section supports TOAMS software, hardware, network connections, and databases for the CDOT enterprise. DTD’s GIS Section will work with traffic sections to train traffic data collection staff to use this software. 2. Enable CDOT staff, temporary employees, and contractors to use the field data collector software and hardware, as needed by traffic sections. 3. Develop a training plan for state wide deployment. 4. Create written training and reference manuals for regional TOAMS administrators and data collectors. 5. For this proposal, the data collection software is built to run on laptop computers with a Windows operating system only. 6. Traffic sections expect to use the TOAMS field data collection tool to collect initial traffic asset data and to update existing traffic asset data

Page 3

6/17/2013

TOAMS Data Collection Tool For Traffic Asset Data STAKEHOLDERS Louis Henefeld Data Applications Unit Manager – Division of Transportation Development – CDOT Terri Lance Traffic Operations Specialist – Region 3 – CDOT Paul Scherner Traffic Operations Specialist – Region 1 – CDOT Alazar Tesfaye Professional Engineer II – Region 6 – CDOT Alisa Babler Professional Engineer II – Head Quarters –CDOT Daniel Thomas Professional Engineer I – Region 3 – CDOT Eric Lundberg Professional Engineer I – Region 2 – CDOT John Vetterling Auditor IV – Head Quarters – CDOT Matthew Jagow Professional Engineer I – Region 1 -CDOT Rick Routh – CDOT Professional Engineer I – Region 5- CDOT Shane Chevalier - CDOT Professional Engineer I – Head Quarters –CDOT Mark Harrington GP III Project Manager - Head Quarters –CDOT David Sprague Senior Project Manager, Traffic Engineering - Atkins William Johnson GISDM Section Manager – Division of Transportation Development – CDOT

Page 4

6/17/2013