SCOPE OF WORK FOR RCI/SLD DATA COLLECTION

Transcription

1 SCOPE OF WORK FOR RCI/SLD DATA COLLECTION 1. General Description 1.1 Purpose This scope of work describes the requirements for collecting, processing, and reporting general descriptive data for a series of Department databases and computer systems, including but not limited to: on-system and off-system roadways for the Roadway Characteristics Inventory (RCI), and the Highway Performance Monitoring System (HPMS). Traditional RCI inventory is the primary means of data collection for this contract. 1.2 Objective Provide high quality, verifiable roadway characteristics information using state-of-the-art technology meeting established data quality and timeliness standards. 2. Responsibilities 2.1 District Manage the consultant s collection, entry, production, quality, and reporting of general interest roadway data and HPMS data. Provide maps, worksheets, forms, passwords, server clearance, etc., applicable to the work to be performed by the consultant. Procedures, manuals, and handbooks can be obtained by the consultant from the FDOT Tallahassee Maps and Publications Office ( ). Designate a Project Manager who shall be the Department s representative to the consultant. Monitor data quality to assure compliance with adopted procedures, manuals, handbooks, standards, and the scope of work. Obtain Information Resource Request(s) (IRR s) for task work orders involving information technology resources as defined by the Department. Specifically, no task work orders shall be issued for this contract for information technology resources without a prior approved IRR. A-1

2 2.2 Consultant Maintain a project office which shall manage the technical activities and resources of the contract. Appoint a dedicated project manager to direct and manage the contract. Support District staff in implementing the District RCI Quality Assurance/Quality Control (QA/QC) Program. Furnish all equipment necessary to perform the data collection, database entry, and production, including labor, transportation, accommodations, postage, paper, microcomputer(s), and software. Record and report all data collected or verified on the forms and/or documents approved by the Department. Furnish and maintain a Global Positioning System (GPS) which uses latitude and longitude based location methods compatible with approved Department mapping software to collect, verify, map, and integrate roadway data with existing Department databases and software. Provide remote sensing support as necessary. Provide 3D/4D visualization support as necessary. Provide Geographic Information Systems (GIS) support as necessary. Update SLD(s) using the Department s automated SLD production method or a method prescribed by the Department. 3. Reviews and Meetings 3.1 Monthly Project Status Meetings and Reports The consultant shall communicate the status of the technical effort, program schedule, and financial condition to the Department on regularly scheduled basis. The monthly project status meetings and reports shall be conducted face-to-face unless otherwise agreed on advance. 3.2 Technical Meetings The consultant shall conduct informal technical meetings with the Department on technical issues arising during the contract to include performance or reliability issues. Either the consultant or the Department may request technical meetings. The consultant A-2

3 shall track action items arising from the technical meetings for resolution/response and report the status at the monthly project status meetings. 4. Data Collection 4.1 Type of Data Descriptive roadway data of general interest includes that needed to produce legislatively mandated reports and to maintain the computer RCI database. General interest roadway data collected on state roads and local roads and data required for HPMS sample sections of state and local roads are listed in the GIRD procedure and accompanying handbooks. 4.2 Equipment The consultant shall provide an operable distance measuring instrument in each data collection vehicle. The consultant will also be responsible for maintaining computer workstations with applicable FDOT approved software including, but not limited to: VPN access, Arcview GIS, internet connection, and a Straight Line Diagram producing program. 4.3 Accuracy All RCI general descriptive data shall conform to the applicable data accuracy standards listed in the GIRD procedure ( ). The consultant is responsible for the accuracy of collected data. The Department shall review, and may spot check in the field and/or in the database(s), data reported by the consultant. Any roadway may be required to be reinventoried or completely redone at the expense of the consultant, if the data reported by the consultant fails to meet accuracy standards, is inconsistent with spot check conducted by the department or designated QC Consultant, is incomplete, or is not timely as specified by task work order and/or Department standard (e.g., procedure, handbook, manual, etc.). 5. Reporting Record the inventory data (actual or coded) collected for each roadway section in one or more of the forms, worksheets, and/or documents listed below. The locations of roadway features are measured and recorded in increments of a thousandth (0.001) of a mile for conventional inventory. The Department reserves the right to change the reporting requirements for any or all data items in this contract based upon changes in Department policy or standards 5.1 Roadway Characteristics Inventory data Refer to the Department s procedures and handbooks for descriptions of roadway features and feature coding information. Use Conventional Inventory method described below to record roadway feature data. Conventional Inventory: Record missing or new roadway features, verify the accuracy of existing roadway features, and measure/report data quality. Enter the roadway feature data into the database(s), update the SLD(s), run edits, and submit SLD hard copies as required to the Department by the task work order due date. A-3

4 The RCI Office and Field Handbook can be obtained at: Highway Performance Monitoring System data Record roadway feature data on HPMS sample report forms or as directed by the Department. Characteristics that are required to be inventoried vary by the type of roadway (e.g., rural/urban, functional classification, and on/off the State Highway System). Record the appropriate value or code observed or measured in the field in the blank space immediately to the right of the existing inventory value for each characteristic. Enter the roadway feature data into the HPMS database by the task work order due date, run edits, and provide field records to the Department. The HPMS Computer Based Training can be obtained at: 6. District RCI Quality Assurance and Quality Control (QA/QC) Program Consultant will provide services to support implementation of the District RCI QA/QC Program to ensure that all items submitted by District RCI Consultants for review and approval, or presented to the District for submittal to the Central Office, have been checked for accuracy and consistency among the RCI Basemap, Straight Line Diagram and RCI database, and that any quality assurance comments have been addressed. 6.1 RCI QA/QC Program Support Services The consultant will support district staff in implementing the QA/QC program through monitoring, assessing, and facilitating the accuracy of updates to RCI and HPMS data. Performing quality control reviews and quality assurance checks of all deliverables provided to the District includes the following activities: Conducting field verification of inventory updates to all On-System sections and HPMS samples and conducting random field verification of inventory updates to Off-System sections performed by District RCI Consultants and submitted to the District for review and approval. Reviewing each updated Straight Line Diagram and associated RCI data for the roadway section to assure the SLD representation of RCI data is consistent with the data in the RCI database and that the SLD is correctly formatted. Checking all Basemap Correction Packages for accuracy and consistency with FDOT naming standards in the RCI handbook and to ensure that all supporting material is included in the submittal. A-4

5 Checking all HPMS sample updates for accuracy as well as completeness, to ensure all required characteristics are collected and entered in the RCI database correctly. 6.2 Consultant will serve as extension of district staff for the following tasks: Work with District staff to coordinate Functional Classification changes with the District Functional Classification Administrator and the FDOT Central Office. Monitor and ensure all RCI, HPMS, and Traffic edits are clean and consistent with each other. Monitor timeliness of both RCI and HPMS data. Be responsible for updating and submitting all Key Sheet and HPMS map changes and monitor the timeliness of those changes. Monitor and change traffic section flow break locations as needed based on yearly review of traffic and growth patterns and ensure they are consistent with data in the RCI system. Ensure that inconsistencies between the basemap and RCI are eliminated and that all necessary changes to the basemap are coordinated with the CO. Monitor all Construction Acceptance notifications and conduct the roadway inventory, data entry, and SLD production within specified timeframes. Assist in coordinating with CO regarding all additions and deletions to the State Highway System (SHS) to include mapping and creation of all necessary supporting materials for the Basemap Correction Package required for addition or deletion to the RCI system. 7. Design Traffic Reports The consultant shall submit Design Traffic Reports for roadway segments and/or intersections to the Department on an as-needed basis in a format acceptable to the Department. A draft report shall be presented to the Department no later than four weeks from the task work order date to proceed unless specified otherwise. The draft report s traffic data and input assumptions will be reviewed and accepted (with proposed changes and modifications) by the Department prior to submittal of the final report. The consultant shall submit the final Design Traffic Report no later than two weeks from the Department s acceptance of the draft report unless specified otherwise. The Design Traffic Report format shall include the following: Cover sheet, certification sheet, project location map, technical summary sheet (with input assumptions and conclusions), present and future traffic data in schematic format, 18-kip equivalent single axle loadings, and calculation sheet (i.e., lane factors, growth factor, A-5

6 equivalency factor, etc.). Classification count(s), turning movement (with calculations to convert eight hour to twenty-four hour counts) and approach volume counts, Department history counts, model traffic data, etc., will be submitted separately with the final Design Traffic Report. The consultant shall submit four hard copies of the Design Traffic Report to the Department for final acceptance unless specified otherwise. 8. Speed and Vehicle Occupancy Studies The consultant shall submit speed and vehicle occupancy studies for roadway segments to the Department on an as-needed basis in a format acceptable to the Department. The consultant shall create and provide a tracking chart of speed and vehicle occupancy studies for each task work order. Prior to creation of the tracking chart, the consultant shall contact the Department for guidance. In addition, the consultant shall provide one hard copy of the disk directory with each submittal. The consultant shall physically count the number of passengers in each vehicle in each lane at indicated locations and times unless specified otherwise. The average number of passengers per vehicle per specified time per lane shall be calculated and reported. The consultant shall be paid per lane and per hour (i.e., a four lane site studied for four hours would be invoiced as sixteen hours) for each location studied and accepted by the Department. The consultant shall conduct speed studies at specified locations and times. Speed studies are defined as combined speed, gap, and/or classification studies. The consultant shall be paid for each count location (i.e., speed, gap, and/or classification study) obtained in the field and accepted by the Department. Speed and vehicle occupancy studies (including any necessary resets) shall be submitted to the Department according to the dates specified in the task work orders. Speed and vehicle occupancy studies submitted after the task work order deadlines shall not be accepted. 9. 3D/4D Visualization Support Services 9.1 Project Area Defined The visualization consultant shall develop an accurate 3D/4D visual representation of the study area as defined by the Department. 9.2 For Use in Design and Public Review The visual representation shall be suitable for supporting both the in-house development and evaluation of preliminary alternative designs as well as for use in the public involvement portions of the PD&E process, and other applications, as applicable. Suitability shall be the judgment of the Department with input from the PD&E, Design, and/or visualization consultant. A-6

7 9.3 Modeling to be Linked Directly to CAD where possible To the extent possible, the definition of roadway alignment and cross section characteristics shall be derived directly from Department computer aided design (CAD) files augmented by survey data where necessary. 9.4 Visualization of Both Before and After Conditions It shall be possible to use the computer generated visual representation to view the existing conditions as well as the proposed design alternatives under both day and nighttime conditions. Development of the before version of the project shall begin at the outset of the contract effort. Development to show design alternatives shall proceed in parallel with the actual design process so as to determine the value added of visualization for those actually involved in the development of preliminary design alternatives. 9.5 Level of Detail Distinct locations within the overall project may be identified by the Department for special emphasis. These locations shall be modeled at the highest level of detail supported by the system hardware and software. Requirements for animation may be limited to these higher detail sections. 9.6 Shall Support Effective Comparisons of Alternative Development and application methods shall utilized that will permit project design personnel and other viewers (e.g., the public) to make effective comparisons of alternative designs, as well as effective comparisons of existing and proposed alternatives. 9.7 Maximum Use of Photo Texture and Texture Mapping Photo texture and texture mapping (from 35mm still and digital photography, and/or digitized video) shall be used where possible to minimize additional 3d modeling requirements and to provide realistic views of natural and manmade features located to either side of the roadway. An effort shall be made to limit the development of wire frame models to only those structures or approximations of structures necessary for the application of photo texture and texture maps and the development of adequate visual fidelity (realism). 9.8 Use of Video The use of video shall be restricted to those instances mutually decided upon by the Department, the PD&E and/or Design consultant, and the visualization consultant where it is felt to be highly desirable to insert (blend) some static aspect of the proposed design with a dynamic view of the actual background scene. 9.9 Essential Manmade Elements Manmade features shall include the sidewalk environment, landscaping, and other feature that may be a part of the sidewalk environment, as well as major traffic control devices A-7

8 (including those for the control of pedestrian behavior), and other features at the Department s option Generic Representation of Vehicles and Pedestrians It shall be possible to represent parked (stationary) vehicles and, to the extent supported by the hardware and software used in the project, the presence of motor vehicle traffic. It shall be acceptable to use generic vehicles with low to moderate fidelity. It shall also be possible (within recognized hardware/software constraints) to model the presence of correctly scaled (but again highly generic) pedestrians. There shall be no requirement to model the actual movement of individual pedestrians or groups of pedestrians, although it shall be desirable to model pedestrians in representative locations and densities Selectable Eye Points for Viewing The viewer eye point shall be selectable so as to provide views from either a driver s perspective, the perspective of a pedestrian, that of a bicyclist or God s eye view. Under none of these viewing conditions shall the viewer (whether driver, pedestrian, or cyclist) actually control the path of travel shall be determined on a prior basis by the developer in conjunction with the Department Level of Desired Viewer Interaction It is intended that the representation be viewed on a large screen TV monitor. There are no requirements for the image generation system to support a real time, interactive view such as that associated with the use of a VR-type helmet display system. A pseudo-interactive (animated) capability shall be developed at selected points in the representation or along selected paths (splines) to simulate movement through the representation from a particular eye point. At a finite number of locations, it shall be possible to rotate the viewer s eye pint 360 degrees in azimuth and for the viewer to stop/freeze the animation at any time during the process Effects of Illumination It shall be possible, in addition to the representation of time of day, to model sun angle and shadows. It shall also be possible to represent the effects of manmade lighting (street fixtures, etc.) so as to provide the designer and public viewer of the designs and ability to estimate the effectiveness of project lighting (e.g., as it might affect the ability to detect pedestrians and bicyclists in the roadway or in crosswalk areas) Definitions Computer-Generated Model/Image An accurate 3D computer model or image of a defined area, containing the three dimensional characteristics of all the objects/features found in the area including those affecting appearance (i.e., surface texture, color, etc.). From the model, all possible observer viewpoints can be generated. With the help of the computer, it is possible to simulate flying, driving, or in a representation of real time (an animation). A-8

9 Photo-Composite (or Photo-Simulation) An image formed by overlaying a properly oriented computer generated image onto a photograph of the environment in which the proposed object is to exist. The background can either be stationary (as in an ordinary still photograph) or dynamic (as in a videotape). The object inserted into the photograph or video can itself be stationary (as in the case of a proposed structure like a building or a bridge) or displayed in motion (as in a display of a proposed train). In either case, the observer is limited to the particular viewpoint that has been pre-selected. Animation Sequences The illusion of motion produced by rapidly presenting individual scenes of different points along a predefined path. Thirty (30) images per second is generally the minimum requirement for the perception of smooth and realistic movement. This is the same method used to make animated motion pictures. Virtual Walk-Thru or Drive-Thru Motion through a 3D computer generated environment that is under the control of the viewer (pedestrian, driver, etc.) in real time (that is, the observer is controlling the path as he or she moves as opposed to the path being predefined. It is similar to a virtual reality video game Urban Simulation At the Department s option, the consultant shall use visual simulation technology to build virtual urban areas (e.g., Pensacola, Fort Walton Beach, Tallahassee, Panama City urban areas) in order to visualize and evaluate proposed changes and new developments in the urban environment. This urban simulation will allow the walking, driving, or flying safely anywhere while experiencing the environment as it currently exists, as it existed ten years ago, or as it might look in the future after physical changes are made. A-9