FDOT District 4 Safety Program FM# 424855-3-32 Districtwide Traffic Operations Safety Studies Scope of Services I. GENERAL REQUIREMENTS This exhibit forms an integral part of the agreement between the State of Florida Department of Transportation (hereinafter referred to as the department) and the Consultant relative to the development of traffic safety studies and other safety related tasks to be performed by the consultant as directed by the Department. The general purpose of this contract is to provide the District Traffic Operations Engineer (DTOE), or its designee (hereinafter referred to as the department project manager), with professional services for conducting needed safety studies. The analysis and conceptual recommendations produced by the Consultant will provide valuable input into the development of safety projects targeting the emphasis areas of the Florida Strategic Highway Safety Plan (FSHSP). For the most part, these projects are implemented through the Department s work program. Other tasks assigned to the Consultant may include: Help resolve complaints or requests received from concerned citizens Review permits for special events from a safety/traffic operations perspective Conduct public hearings for access management changes related to safety projects Analyze traffic signal structures (i.e., mast arms or strain poles) in order to determine if they can accommodate the signal heads necessary to change the current phase Review fatal crashes Monitor safety in specific work-zones Update and maintain the Department s Skid Hazard Reporting System Develop and utilize GIS based tools to identify locations with targeted crash patterns II. PERSONNEL The Consultant s work shall be performed and/or directed by the key personnel identified in the technical/fee proposal presentations made by the Consultant. Any changes in the indicated personnel of the Consultant s office in charge of the work as identified in the Consultant s proposal shall be subject to review and approval by the Department. At a minimum, the Consultant s local team shall be made up of: Position 1. Consultant project manager Minimum Area(s) of expertise (for the team making up each category) traffic engineering, safety engineering, signal retiming, QA/QC, scheduling, presentation and communication skills 1
2. Senior engineer Signal retiming, traffic engineering, safety engineering, cost estimation, minor design, structural analysis 3. Engineer Signal retiming, traffic engineering, safety engineering, conceptual design, roadway lighting, cost estimation, minor design, structural analysis 4. Engineer in training Signal retiming, traffic engineering, safety engineering, roadway design, structural analysis 5. Office technician Microstation, MS-Office 6. Data collection Data collection equipment use and maintenance technician 7. GIS programmer GIS, MS-Access, Other databases 8. Administrative Assistant MS-Office A. Consultant Project Manager The project manager shall be a registered Professional Engineer (PE) in the State of Florida. The Consultant project manager shall have no less than 7 years of traffic and safety engineering experience. The Consultant project manager shall have a demonstrated ability to perform Quality Control / Quality Assurance checks on a variety of traffic safety studies/reports and technical memorandums. The Consultant project manager shall be knowledgeable of project scheduling techniques, and shall have a working knowledge of Microsoft Project, or a compatible project management/scheduling software. B. Senior Engineer Each senior engineer shall be licensed as a Professional Engineer (PE) in the State of Florida. The group of local senior engineers shall, at a minimum, have expertise in the following areas: 1. At least one senior engineer shall have 10+ years of traffic engineering experience 2. At least one senior engineer shall have 10+ years of safety engineering experience 3. At least one senior engineer shall have 7+ years of experience in the development of minor design plans 4. At least one senior engineer shall have 7+ years of experience in cost-estimation and benefit calculation C. Engineer Each engineer shall be registered as a Professional Engineer (PE) in the State of Florida. The group of local engineers in the Consultant s team shall, at a minimum, have the following areas of expertise: 1. At least one engineer shall have at least 6 years of traffic engineering and safety engineering experience. Typical assignments in safety/traffic engineering include: 2
a. Identifying potential study locations consistent with the Florida Strategic Highway Safety Plan b. Retrieving project information and construction history of potential study locations utilizing FDOT resources c. Retrieving and analyzing traffic and crash data (from the Department s CAR system and hard copy crash reports) d. Conducting field reviews to assess safety and operational conditions e. Performing complex safety and operational analyses of intersections and arterials for existing and proposed conditions f. Developing signing and pavement marking plans g. Conducting traffic signal warrant analyses h. Conducting left-turn phase warrant studies i. Conducting pedestrian safety studies j. Conducting safety reviews for 3R projects k. Developing engineering countermeasures that are viable for implementation l. Preparing construction cost estimates m. Calculating the Benefit to Cost ratio of a proposed safety project n. Calculating the Net Present Value of a proposed safety project o. Preparing technical memorandums summarizing findings and recommendations p. Reviewing work performed by CAD and field technicians 2. At least one engineer shall have 5 years of experience in roadway lighting. Typical assignments in roadway lighting include: a. Measuring existing levels of illumination b. Assessing if existing illumination meets the Department s minimum requirements for that road s classification c. Making lighting level recommendations to address safety concerns 3. At least one engineer shall have 5 years of experience in minor design. Typical assignments in minor design include: a. Developing complete and error free roadway plans suitable for bidding (ex., median opening modification, intersection expansion, etc) b. Developing design plans for minor structures (ex., mast arm signal, overhead cantilever sign, etc) c. Developing design plans for lighting systems D. Engineer in Training The group of local engineers in training in the Consultant s team shall, at a minimum, have the following areas of expertise: 1. At least one engineer shall have 2 years of traffic engineering experience, and 2 years of safety engineering experience. Typical assignment in safety/traffic engineering include: a. Identifying potential study locations consistent with the FL-SHSP b. Retrieving project information and construction history of potential study locations utilizing FDOT resources 3
c. Retrieving and analyzing traffic and crash data (from the Department s CAR system and hard copy forms) d. Conducting field reviews to assess safety and operational conditions e. Performing safety and operational analyses of intersections of existing and proposed conditions f. Conducting safety reviews for 3R projects g. Preparing construction cost estimates h. Calculating the Benefit to Cost ratio of a proposed safety project i. Calculating the Net Present Value of a proposed safety project j. Reviewing work performed by CAD and field technicians E. Office Technician The group of local office technicians in the Consultant s team shall, at a minimum, have the following areas of expertise: 1. At least one technician shall have 2 years of Microstation experience. Typical assignments include: a. Drawing collision diagrams b. Drawing condition diagrams representing existing conditions c. Drawing conceptual improvement diagrams representing proposed conditions d. Developing maintenance task work orders as directed by the Department project manager 2. The same technician shall have at least 3 years of Microsoft-Office experience 3. The same technician shall be able to learn and become proficient in the use of: a. FDOT s section number, node list, and mile point systems. b. FDOT s CARS database F. Data Collection Technician The group of local data collection technicians in the Consultant s team shall have at least 1 year of experience in data collection. The Consultant must ensure that the Data collection technicians are knowledgeable in the use, maintenance and calibration of the equipment they use. G. GIS Programmer The group of local GIS programmers in the Consultant s team shall be proficient in the use of ArcGIS and have at least 4 years of experience in the development of GIS based applications. H. Administrative Assistant The group of local secretaries in the Consultant s team shall have at least 3 years of experience in the use of MS-Office (MS-Word, Excel, and PowerPoint). III. SUBCONTRACTING Should the Consultant require the services of a specialist, the Consultant is authorized to subcontract these services under the provisions of paragraph 7.00 of the standard Consultant 4
agreement. Firms selected for subcontracts must be approved in writing and qualified by the Department prior to the Consultant authorizing any such work. The Consultant shall be fully responsible for the satisfactory performance of all subcontracted work. IV. BEGINNING AND LENGTH OF SERVICES Services to be provided by the Consultant under this agreement will be initiated and completed as directed by the department project manager on each task work order assigned under this agreement. Individual assignments will be issued to the Consultant during the twenty four (24) month period this agreement is in effect or as otherwise extended. The duration of services may be extended by a Time Extension Amendment if mutually agreed to in writing by the Department and the Consultant. V. ISSUANCE OF TASK WORK ORDERS The department s project manager shall issue a written work order authorizing the Consultant to perform one or more assignments. The Consultant shall not begin any work prior to receiving a signed task work order document. Such a task work order shall serve as a Notice to Proceed effective on the date specified in the task work order form. The work order issued by the department s project manager shall, at a minimum, specify: the type of work to be conducted the location and project limits (if applicable) the date on which the final deliverable is due the total price to be paid to the Consultant Due to the nature of the work to be assigned to under this contract, Consultant staff may be required to work at the FDOT Traffic Operations office. Such a requirement will be specified in the task work order. VI. BASIS OF PAYMENT Each study shall be priced individually and paid for as such. When more than one assignment is issued simultaneously, regardless of whether it is issued through one or multiple task work orders, payment shall be negotiated based on the expected reduction in the staff-hour effort caused by economies of scale. Assignments that require significant additional effort than the average negotiated task shall be submitted with staff-hour estimates for each task. Whenever deemed necessary by the Department, the total payment for an assignment shall be negotiated between the Department and the Consultant. 5
VII. SEALING OF FINAL DOCUMENTS All final study reports and memorandums submitted to the department project manager, unless otherwise notified in writing by the department project manager, shall be signed, sealed and dated by a Professional Engineer licensed in the State of Florida. VIII. EXPECTED ASSIGNMENTS The following list includes various Traffic Operations / Safety studies that the Department anticipates to assign to the Consultant. However, since the work to be assigned to the Consultant depends on the safety issues that are identified throughout the District, the Department does not guarantee that the Consultant will be assigned a minimum number or type of studies. The type of studies includes: A. Safety studies B. Permits review for special events C. Signal Retiming for Safety D. Structural analysis of traffic structures E. Road Safety Audits F. Safety reviews G. In-house support services H. Fatal crash review I. Skid Hazard Reporting System update J. 5% list analysis K. Geographic Information Systems (GIS) application development L. Net Present Value driven studies M. Data collection a. Automatic data recorder (ADR) counts summarized by i. 24-hour (1-day) traffic count (15 minute intervals) ii. 48-hour (2-day) traffic counts (15 minute intervals) iii. 168-hour (7-day) traffic counts (15 minute intervals) iv. 336-hour (14-day) traffic counts (15 minute intervals) b. Turning movement counts (TMCs) i. 4 hour turning movement and/or pedestrian counts ii. 6 hour turning movement and/or pedestrian counts iii. 8 hour turning movement and/or pedestrian counts c. Pedestrian volume counts d. Vehicle classification surveys i. 24 hour vehicle classification counts (15 minute intervals) ii. 48 hour vehicle classification counts (15 minute intervals) N. Other services a. Public hearings b. Traffic citation retrieval c. Field reviews d. Crash analysis e. No-passing zone study 6
f. Lighting i. Highway lighting justification ii. Iluminance measurement g. Spot speed study h. Safe curve speed study i. Conflict analysis j. Pedestrian safety study k. Fixed object inventory l. Railroad crossing preemption study m. Sight distance study n. Signal warrant analysis o. Parking study p. Operational analysis for intersections q. Operational analysis for arterials and networks r. Design of minor projects s. Miscellaneous services IX. TASK DESCRIPTION The following pages provide a brief description of what is entailed in each task A. Safety Study The Traffic Operations office is responsible for reducing crashes through the implementation of engineering countermeasures. Therefore, the study s goal is to develop traffic operational strategies to enhance safety, while minimizing impact, if any, on traffic flow. As part of this assignment, the Consultant shall complete the following tasks consistent with the procedures and guidelines outlined in the FDOT MUTS Manual, MUTCD, HSIP and AASHTO: 1. Collect data relevant to the study location, example: a. Crash data b. Hard copies of police reports c. High crash listing d. Aerial photographs e. Field inventory f. Lighting levels (if night time crashes are the object of the study) g. Other relevant data 2. Summarize the latest 3-year crash data by preparing crash summary tables 3. Review hard copies and: a. Prepare collision diagrams b. Ensure that there are no discrepancies between the police reports, the crash data, and the summary tables 4. Identify significant crash patterns 7
5. Conduct AM and/or PM peak hour field reviews to assess the existing safety and operational conditions 6. Develop engineering countermeasures to reduce number of crashes and/or the severity of the crash patterns identified while attempting to minimize any negative impact on operations. 7. Present findings at pre-safety Review Committee meeting (pre-src) 8. Revise recommendations, if necessary, based on the input from the pre-src meeting and conduct a more detailed safety analysis based on the findings from steps 4 and 6. The findings from step 4 and 6 should not limit the reach of this detailed safety analysis. 9. Assess the constructability of the proposed improvements 10. Prepare an existing condition sketch based on the MUTS Manual 11. When impacts on operations are unavoidable, conduct an operational analysis of the existing and proposed conditions. The operational analysis shall be made using the most recent version of a traffic analysis software package approved by the project manager. The Consultant shall choose the software package based on the software s ability to analyze the situation under consideration. The following software packages are considered as approved for general analysis: a. Signal 2000: Approved for analysis of single/isolated intersections b. SYNCHRO: Approved for analysis of non-isolated signals, or a network of signals. While SYNCHRO is also acceptable for analyses of single/isolated intersections, Signal 2000 is preferred 12. Prepare a conceptual improvement drawing depicting proposed improvements 13. Coordinate with other sections of the department and other public agencies (ex., counties, municipalities, etc) regarding the proposed improvements 14. Prepare a preliminary estimate of construction costs 15. Calculate the benefit to cost ratio of the proposed improvements 16. Prepare a technical memorandum to document the findings and recommendations of the study 17. Present revised findings and recommendations to the Safety Review Committee meeting (SRC) 18. Revise recommendations, if necessary, based on input from SRC meeting 19. Present for the second time the revised recommendations to the SRC, if needed 1. Safety Study Development Process The Department may develop Safety Studies by either: 1. Assigning all tasks (i.e., tasks 1-19) to the Consultant as a home-office task, or 2. Performing tasks 1-7 in house, and assign tasks 8-19 as a home-office task The following flowchart provides a high-level overview of the process that the Department currently follows to develop safety studies. Please note that not all tasks are represented, and that the process may be further streamlined and optimized at any time. 8
Safety Study Process Overview 9
2. Task product Regardless of the development process selected, the Consultant shall submit to the Department a report that includes the following items: 1. Crash analysis a. Collision diagrams b. Crash summary sheets 2. Findings of crash analysis and field review a. Crash patterns to address b. Other safety concerns not supported by available crash data 3. Recommendations a. Recommendations to address crash patterns b. Crash reduction sheet 4. Operational analyses a. Existing conditions b. Proposed conditions 5. Conceptual drawings a. Existing conditions b. Proposed conditions 6. Construction cost estimate 7. Benefit cost calculation 8. Net Present Value calculation B. Permits Review for Special Events The Traffic Operations office is responsible for reviewing and approving permits for special events. This review is comprehensive and looks at each permit application from multiple perspectives. At a minimum, the Consultant shall determine the adequacy of the permit s traffic control/traffic management plan and analyze the safety/operational impact that rerouted traffic will have on other roads. The consultant shall be responsible for assessing which perspectives of analysis are needed for each permit application, conducting the analyses, and making a recommendation to approve or reject the permit application. When the consultant makes a recommendation to approve the permit application, the consultant shall also include recommendations, if available, to minimize the event s negative impact in safety and/or mobility Examples of special events that require a permit include: A. Air & Sea Shows B. Renaissance Festivals C. Marathons 10
C. Signal Retiming for Safety The Traffic Operations office is responsible for the implementation of the FL-SHSP. The district believes that signal retiming process, due to its potential for enhancing traffic safety and improving traffic flow, is instrumental in addressing the emphasis areas of the FL-SHSP, specifically intersection crashes. The primary objective of signal retiming is to improve the safety and mobility of the street system by processing traffic through intersections safely and efficiently. A traffic signal that is properly designed and timed can be expected to reduce the frequency and severity of certain crash types. As part of this assignment, the consultant shall complete the following five steps consistent with the procedures and guidelines outlined in the FDOT Traffic Engineering Manual, MUTCD, FHWA Traffic Signal Timing Manual, and ITE Traffic Signal Timing Manual. Although these steps indicate the typical signal timing process, the consultant shall develop signal timing plans that are consistent with the policies, procedures and preferences of the respective signal maintaining agencies. The five distinct steps that define the signal timing development process are: 1 Project Scoping The project scoping is a key component of signal timing development. During this step, the consultant team shall establish the following items: a. Objectives Common objectives based on signal timing policies include reducing the number and severity of congestion related crashes, reducing stops, delay, and travel time for a corridor. During the project scoping period, the consultant shall also identify any known traffic related issues. The identification of these issues may be the result of public comments, staff observations, or known discrepancies with established policies. Once these issues, if any, are identified, the consultant shall develop objectives for the specific signal retiming project. Reducing the number and severity of congestion related crashes shall be the primary objective of all projects developed through this contract. b. Standards and Procedures The consultant shall adhere to the applicable procedures and standards contained in the current edition of MUTCD as well as FDOT standards and those followed by the signal maintaining agency with jurisdiction over the project location. The procedures and standards shall be confirmed as part of the scoping process. The standards identify parameters used for the timing of change and clearance intervals, actuated timing settings, pedestrian timing, signal operation plans and phasing changes (such as protected+permissive to protected+only left turn phase, right turn overlap phase etc). c. Control Sections The consultant shall identify logical groups (control sections) of signals to be included in the timing process. The concept of sections is an important one. Typically, every intersection in a section changes to a new timing plan at the same time of day. Each 11
intersection in a section likely operates in the same control mode manual, time of day, or traffic responsive. The control section boundaries are selected in a manner that will minimize the need for interaction with the signals in adjacent sections. Changes to control sections, if any, shall be, limited to those that can be implemented with the equipment already in the field. d. Performance Measures As the project scope is defined, performance measures must be selected to evaluate the success of the retiming effort. The consultant shall include expected crash/injury severity reduction, travel time, stops, delays, queue lengths, numbers of cycle failures, average speeds and the percent time that intersections are congested as the performance measures. e. Number of Timing Plans The consultant shall at a minimum develop five distinct signal timing plans (i.e., for the AM peak, mid-day peak, PM peak, day time off peak patterns and nighttime) for typical weekdays, unless otherwise directed by the signal maintaining agency. In addition to time-of-day plans, separate plans for weekdays, weekends or even specific days (such as Friday in a high weekend travel area) may be warranted based on variation in travel patterns and volumes. The consultant shall also determine the hours in which each timing plan is to be operated. 2 Data Collection The data typically can be categorized as: traffic characteristics, traffic control devices, intersection geometry, and crash history. The consultant is expected to collect the following data as part of this step: a. Crash Data The consultant shall analyze the crash data for the latest three-years available to identify discernible crash patterns. The consultant shall also develop collision diagrams intersection/ corridor using any automated crash mapping tool. Such automated tool shall be presented to the FDOT project manager for approval prior to utilizing it for any project. The consultant shall also develop and implement a QA/QC process for automated collision diagrams. At a minimum the consultant shall create the following histograms and tables as part of the crash analysis: Histograms Crashes by type Crashes by contributing cause Crashes by time of day Crashes by lighting condition Crashes by surface condition Crashes by weather condition Crashes by day of the week Crashes by month of the year Crashes by age group at fault Crashes by alcohol/drug involvement 12
Tables High crash spots High crash segments Crash summary by type Crash summary by contributing cause Crash summary by location b. 24-Hour Weekly Volume Profiles The weekly traffic volume profiles are an important element in the data collection effort and should be collected at critical locations along the corridor. Critical locations are those that govern the traffic characteristics of the corridor. c. Turning Movement Counts Intersection turning movement counts shall be collected for representative traffic periods. The traffic counts shall include a count of all vehicular traffic at the intersection, as categorized by intersection approach (i.e., northbound, southbound, etc.) and movement (i.e., left-turn, u-turns, through, or right-turn movement), pedestrians, and vehicle type (including transit). If heavy vehicles are significant (i.e. more than 2%), the vehicular count should be further categorized by vehicle classification. The presence of special users at the intersection (e.g., elderly pedestrians, school children, bicyclists, emergency responders, etc.) should also be documented. d. Vehicular Speed Data on vehicular traffic speed should be gathered, as needed, to identify the approach speeds to the intersection. This is especially important in determining the signal phasing. Traffic speeds are especially important when considering controller parameters influenced by detectors (for example, extension of green, time before reduction etc). e. Travel Time Runs The consultant shall conduct travel time runs to record delay, stop, and running time data. Such data can be used to calibrate the base analysis model and to compare the corridor operations before and after the new timings are implemented. f. Condition Diagram The consultant shall develop a scaled condition diagram to depict relevant geometric and traffic control data (such as number of lanes, lane width, lane assignment, turn bays, pedestrian crosswalks, vehicular and pedestrian signal heads, speed limit signs, phase sequence, use of overlaps, and signal timing settings etc.). g. Field Review Typically, the consultant shall conduct field reviews during AM peak, PM peak, off-peak periods on a typical weekday and weekend at the signalized intersections and of the subject corridor. The key elements to consider are location and operation of signal equipment, intersection geometry, signal phasing, intersection operations, vehicle queuing, adjacent traffic generators, preemption requirements (for trains, draw bridges and emergency vehicles), posted speed and/or free flow speed. 13
h. Existing Signal Timing The consultant shall obtain the existing signal timing sheets from the local maintaining agency to in order to develop a base analysis model. Key information from the existing signal timing includes phase sequence, yellow and all-red intervals, pedestrian walk and flashing don t walk intervals, minimum green, and detector settings. Additionally, if the intersection is operating in coordination, then the cycle length, splits and/or force-offs, offsets, and reference phases should be obtained from the existing signal timing. i. Intersection Analysis The consultant shall conduct an analysis to determine a reasonable signal phasing for the prevailing conditions, evaluate the need for coordination, identify traffic signal control mode of operation, verify detection design and to evaluate basic signal timing parameters to determine the settings that will operate as a part of the timing plan. 3 Model Development The consultant shall utilize the FDOT approved computer-based tools are to calculate and evaluate signal timing. Since many of these tools assume the presence of under-saturated conditions, it is important to recognize their capabilities and limitations. The requirements for developing timings for saturated and under-saturated conditions should be considered as the model is developed. The consultant should consider the following elements: Establish a standards and conventions document (i.e., file naming, map settings, base data parameters, analysis settings) that provides the user with consistency through the retiming process; Review the plan development in levels or stages to ensure efficiency; Coordinate with the respective signal maintaining agencies; and Include quality assurance and quality control measures. a. Data Input The consultant shall establish a base network utilizing computer models such as Synchro, PASSER, TRANSYT-7F, TEAPAC etc. for the study time periods (i.e., morning, midday, p.m., etc.). The typical data used in the model include lane geometry, link speeds and distances, phase numbering, left- and right-turn phasing, existing signal timing (i.e., yellow and all-red intervals, pedestrian walk and flashing don t walk intervals, minimum green, and detector settings), controller type, and coordinated reference phases. Field observations should be compared with the traffic operation results for each time period in the model. A review of the calibrated model shall be performed prior to moving forward with the timing plan development analysis. b. Analysis The consultant should utilize the following steps, which are typically used on the base network for each time period to select a cycle length, evaluate intersection and system operations, and identify the best plan based on the objectives of the study: 14
Cycle Length Selection Cycle length selection should reflect local policies and users of the system. The cycle length for the subject time period is determined based on the performance measures that have been identified for the system. Cycle Length Refinement Intersection Analysis Once a cycle length is selected, the volume-to-capacity ratios, movement splits, minimum splits, and vehicle queues should be evaluated at each of the subject intersections for the two to four cycle lengths identified for further refinement. This analysis allows the consultant to assess if the cycle length will meet specific objectives of the study. Corridor Refinement - System Analysis After the analysis is complete, a system analysis of the subject corridor or network should be completed to provide an analysis of: o Vehicle progression along the corridor o Intersection-to-intersection interaction o Left-turn operations Simulation The consultant shall use the simulation program to compare the selected performance measures resulting from the new timing with the measures produced by the existing timing or other cycle lengths. In this way, the potential effectiveness of the new timing can be evaluated. 4- Draft Timing Plans After the cycle lengths are evaluated, the intersections and system analyzed, and the timing plans compared, a preferred timing plan should be selected. The consultant shall submit the draft timing plans for review to the Department and the local signal maintaining agency. 5- Final Timing Plans Once the Department and local signal maintaining agency have completed their review and the comments have been incorporated into the draft timing plans, the timing plans are ready to be deemed final. Task products A signal retiming plan will be deemed completed after a safety report, signed and sealed by a professional engineer registered in the State of Florida, has been submitted and approved by the department. The safety report at a minimum shall include: Methodology, findings and recommendations Input and output data files of the computer model Hard copies of Signal phasing and timing plans 15
Copies of the correspondence with the local signal maintaining agency, meeting minutes etc. Benefit-Cost Analysis: Three types of B/C analysis shall be performed (*) Net Present Value (NPV) Analysis: Three types of NPV analysis shall be performed (**) Expected Crash Reduction Table based on the latest 3-year crash data The consultant shall submit four hard copies and two CD-ROMs (or DVDs) with PDF of the report and the files used to develop report in their native format (for example Synchro files, word documents, excel tables, jpeg files etc). (*): Benefit Cost Type 1: Type 2: Type 3: (**): Net Present Value Type 1: Type 2: Type 3: NPV based on crash reduction benefit NPV based on operational benefit NPV based on combination of crash reduction and operational benefit The consultant shall utilize a service life of three years for the purpose of benefit/cost and NPV analysis. D. Structural Analysis Typically, as part of retiming process, revisions to signal phasing may result in modifications to signal head configuration, thereby increasing the load due to additional signal heads. In such cases, the department may assign this task to the consultant to verify the structural integrity of the signal poles due to the additional loads. The consultant shall utilize FDOT approved analysis software packages (such as Atlas for strain poles and Mast Arm Program for mast arm supports) for conducting the structural analysis. If available, the department will provide access to as-built plans and/or survey files to the consultant. If such information is not available or if the study location is on a local roadway, the consultant shall be responsible for collecting pertinent data necessary to perform the structural analysis. 1. Task products A structural analysis task will be deemed completed after a technical report, signed and sealed by a professional engineer registered in the State of Florida, has been submitted and approved by the department. The technical report at a minimum shall include: findings and recommendations calculations Input and output data files of the computer model Hard copies of structural analysis worksheets 16
The consultant shall submit four hard copies and two CD-ROMs (or DVDs) with PDF of the report and the files used to develop report in their native format (for example computer model files, word documents etc). E. Road Safety Audits The Traffic Operations office is responsible for the implementation of the FL-SHSP. The district believes that RSAs, because of their proactive nature and the low-cost/high value nature of their recommendations, are instrumental in addressing the emphasis areas of the FL-SHSP. In general, RSAs aim to answer the following two questions: 1. What elements of the road may present a safety concern: to what extent, to which road users, and under what circumstances? 2. What opportunities exist to eliminate or mitigate identified safety concerns? The goal of an RSA is to develop recommendations that enhance safety, while minimizing impact, if any, on traffic flow. As part of this assignment, the Consultant shall complete the following steps consistent with the procedures and guidelines outlined in the FDOT MUTS Manual, MUTCD, HSIP, AASHTO, and FHWA RSA guidelines: 1. Identify project or existing road to be audited. 2. Select RSA team. The consultant team must provide a qualified and multidisciplinary team of experts suitable for the specific RSA to be conducted each RSA will likely require the participation of different areas of expertise. While in the ideal RSA some of the expertise is provided by the local agency and/or the Department, there may be occasions in which these agencies are unable to provide the necessary expertise. For these cases, the consultant team shall have access to experts within the necessary fields of expertise. Typical fields of expertise necessary to conduct an RSA are: a. Road safety specialist. The road safe specialist shall act as the leader of all RSAs. As the RSA team leader, the road safety specialist shall sign and seal the final RSA document the road safety specialist shall be a licensed engineer in the State of Florida b. Traffic operations engineer c. Road design engineer d. Local contact person e. Other areas of expertise. Some of the areas of expertise that may be required in some RSAs may include (this is not intended to be a comprehensive list): i. Human factors ii. Maintenance iii. Enforcement iv. First response v. Pedestrian & bicycle treatment vi. Transit operations vii. ITS 17
3. Conduct a pre-audit meeting to review project information. This meeting shall bring together the project owner, the design team (if any) and the audit team to discuss the context and scope of the RSA and to review all project information available. 4. Office review of crash data and other available information. This step aims to help identify areas of safety concerns. The RSA team should restrict its comments to those issues having a bearing on the safety of road users. Comments may be either specific to a particular location or broad-based. Issues related to aesthetics, amenities, or congestion should also be commented upon if they lead to less-safe conditions 5. Perform field reviews under various conditions. For typical RSAs, at least 3 field reviews ought to be performed: one during night time, one during the daytime peak period, and one during day-time off-peak period. The number/time of field reviews may be modified if the RSA study location justifies it. The objectives of the field reviews are: a. Gain insight into the project or existing road b. Verify/identify areas of safety concerns 6. Conduct audit analysis and prepare report findings. As a result, the safety issues are identified and prioritized and suggestions are made for reducing the degree of safety risk. Suggestions to enhance safety are to be prioritized using a Cartesian plane where the X axis represents feasibility, and the Y axis represents value. RSA suggestions should be appropriate to the state in the RSA and the elements being examined (ex., the suggestions of a construction phase RSA would be different than those made in a preliminary design RSA). The RSA results are then succinctly summarized in the formal RSA report. 7. Present audit findings to project owner, design team, RSA steering committee, or Safety Review Committee. The audit team will orally report the key RSA findings to the project owner, design team, RSA steering committee, or Safety Review Committee in order to facilitate the understanding of the RSA. 8. Record/Prepare Formal Response. The consultant team will summarize the feedback provided by the project owner, design team, RSA steering committee, or the Safety Review Committee to each safety issue/recommendation listed in the RSA report. The Consultant team shall also be prepared to conduct RSAs of any of the following types: 1. Pre-construction road safety audits a. Preliminary design road safety audits b. Detailed design road safety audits 2. Construction Road Safety Audits a. Pre-opening road safety audits 3. Post-Construction Road Safety audits a. RSAs of existing roads The members of the RSA team shall have demonstrated excellent command of the MUTCD and familiarity with the Department s Local Agency Participation (LAP) program. It is expected that many of the recommendations made on post-construction RSAs would involve pavement marking & signing enhancements. The consultant team shall have a 18
demonstrated ability and experience interpreting the MUTCD and creating pavement marking & signing plans. It is also expected that, occasionally, RSAs may recommend relatively high-cost safety enhancements (ex., installing a new signal, installing/upgrading lighting, etc). Should an RSA take place on a non-state Road, it is also possible that the local agency having jurisdiction over the road may not have available the funds necessary to implement the recommendation. In these cases, the consultant will be required to explain to the local agency the Department s LAP program. 1. Task products An RSA will be deemed completed after the following submittals are received and approved by the Department: 1. RSA report. In general, the RSA report shall follow the following sample outline: a. Introduction i. Scope and purpose of the RSA ii. Identification of project stage or existing road and items reviewed and not reviewed iii. Project limits b. Background i. Audit team, affiliation and qualifications of team members ii. Commentary on data received from project owner and design team iii. General observations regarding site visit c. Findings and suggestions i. List of safety issues 1. Safety issue 1 description of issue, evaluation of safety risk, suggestions 2. Safety issue 2 etc. ii. Prioritization of safety issues based on value and feasibility using Cartesian plane d. Formal statement. This is a concluding statement signed by the RSA team members indicating that they have participated in the RSA and agreed or reached consensus on its findings. The RSA team leader the Road Safety Specialist who is required to be a licensed engineer in the State of Florida, shall sign and seal the final report. 2. Crash summary tables. Each submission of the draft and the final technical memorandum shall be submitted with the supporting crash summary tables. The crash summary tables shall be developed using a spreadsheet compatible with MS-Office Excel 2007 and submitted to the Department in an electronic format. 2. Performance time When a single Road Safety Audit is issued in a task work order, the Consultant shall be provided 15 calendar days to conduct the RSA, submit a first draft to the Department, and make the 19
presentation of findings. The calendar days begin counting on the day the task work order is issued. The Department will prioritize the RSAs whenever multiple ones are issued in the same task work order. The consultant, however, shall have enough qualified staff to simultaneously conduct up to two RSAs 3. Format of Submittals All submittals, drafts and final document, shall be submitted to the Department in the following manner, unless directed otherwise by the Department s project manager: 1. Three (3) Hard copies (i.e., print), and 2. Electronic formats, which are: a. pdf, and b. the documents native format (ex., MS-Word, MS-Excel, etc). F. Safety Review The Traffic Operations office is responsible for supporting the Department s resurfacing, reconstruction and rehabilitation (3R) program by developing a Safety Review for each project. The purpose of this study task is to identify significant crash patterns and recommend actions aimed at enhancing safety on locations that are programmed for 3R projects. Under this task, the Consultant shall be responsible for: 1. Obtaining and analyzing all data necessary for the performance of the Safety Review. The data shall include, but is not limited to: a. The scope of the 3R project, if available b. The department high crash lists spot and segment c. Crash data for the most recent 3 years available, from the following sources: i. Department s crash database ii. Databases maintained by other agencies (ex., cities, counties, law enforcement agencies, etc) 2. Meeting with local government representatives/officials and groups of concerned citizens, if any, and document any safety concerns they may have 3. Analyzing crash data and identifying discernible crash patterns. At a minimum the Consultant shall create the following graphs and tables for analysis: a. Graphs: i. Crashes per study year ii. Crashes by type iii. Crashes by contributing cause iv. Distribution of crashes by locations of interest (ex., signalized, nonsignalized intersections, median openings, ramp, etc) b. Tables i. High crash spots ii. High crash segments iii. Collision summary by type 20
iv. Collision summary by contributing cause v. Crash summary by location assigning the rows to the locations of interest, and the columns to the crash types, and highlighting crash patterns that need further study 4. Conducting a field review during a peak hour (to be determined by the Consultant based on the period where most crashes occur) and identify probable causes for the crash patterns identified 5. Preparing a technical memorandum containing the findings of the crash data review, interviews with local officials, and the probable causes for the crash patterns identified 6. Recommending, for each crash pattern identified, if an additional study needs to be conducted. 1. Task products: This task will be deemed completed after the following submittals are received and approved by the Department: Final Technical memorandum. Prior to submitting the final technical memorandum, the Consultant shall submit the document as a draft. If changes need to be made, the Department will request a modified draft. The final technical memorandum shall be submitted only after an acceptable draft, which generates no comments from the Department is submitted. It is expected that the number of drafts submitted to the Department will vary based on the quality of the submittal. The final technical memorandum shall contain the name and contact information of the Consultant s engineer who managed the task. Crash summary tables. Each submission of the draft and the final technical memorandum shall be submitted with the supporting crash summary tables. The crash summary tables shall be developed using a spreadsheet compatible with MS-Office Excel 2007 and submitted to the Department in an electronic format. 2. Performance time When a single safety review is issued in a task work order, the Consultant shall be provided 15 working days to conduct a Safety Review and submit a first draft to the Department. The calendar days begin counting on the day the task work order is issued. The Department will prioritize the Safety Reviews whenever multiple Safety Reviews are issued in the same task work order. When this occurs, the Consultant shall submit the first draft of the highest priority Safety Review within the first 15 working days while the first draft for the second Safety Review, in terms of priority, shall be provided seven working days later that is, within the first 22 working days. This same seven working day increment shall be applied for each additional Safety Review assigned. Should the Department provide the Consultant comments on a Safety Review s first draft, the Consultant will be provided five (5) additional working days to submit a second draft. 21
Should the Department have comments on the second draft, or in any other subsequent draft, the Consultant will be given three (3) extra working days to implement the comments and submit a revised draft. 3. Format of submittals All submittals, drafts and final document, shall be submitted to the Department in the following manner, unless directed otherwise by the Department s project manager: 3. Three (3) Hard copies (i.e., print), and 4. Electronic formats, which are: a. pdf, and b. the documents native format (ex., MS-Word, MS-Excel, etc). G. In-house support services At the Department s request, the Consultant shall make available the services of any of the positions identified in the personnel section of the scope of services. When in-house support services are required, the Consultant will be compensated for hours on-the-job. 1. Potential in-house tasks The following table lists some of the tasks that may be assigned to the Consultant as in-house support services. The table also indicates the type of position that would be expected to perform this task: In-house task Fatal crash reviews Draw collision diagrams Retrieve crash data Draw existing condition diagram Draw proposed condition diagram Develop maintenance task work orders Crash analysis Operational analysis Field reviews and field measurements Others as needed Position Engineer in training Technician Technician Technician Technician Technician / engineer in training Engineer Engineer Technician / engineer in training / engineer Depending on the task assigned 2. Use of field overhead Whenever the Department requests the services of a single position on a full time basis (40 hours per week) for any period longer than 21 working days (typically equivalent to one calendar month), the fee shall be calculated using the Consultant s field overhead. 3. Related in-house support costs The Department expects that the employee provided by the Consultant for in-house support services will need the continued support from the home-office. For instance, the Consultant s home office is expected to make periodical reviews of the employee s performance and job satisfaction, provide training opportunities, and assist him/her with other administrative tasks (ex., preparation of timesheet, expense reimbursement documents, etc). 22
Thus, the Department will allow the Consultant to bill 3 project manager hours and 3 clerical hours for every 21 work days labored by each employee providing in-house support services. Whenever in-house support services are provided for a period briefer than 21 days, project management and clerical hours shall be prorated to the nearest half hour. 4. Work load limits for in-house support employees Whenever an employee is assigned to provide full time (i.e., 40 hours per week) in-house support services for the Department, the Consultant Project Manager shall limit the employee s work load to the 40 hours he/she is working for the Department, unless approved in writing by the Department s project manager. Such a limitation in the work load of employees providing in-house support services will help ensure that: employee burnout is avoided employee operates at peak performance employee s attention is focused entirely on the Department s work FDOT receives high quality services 5. Billing for in-house support services The Consultant shall invoice the Department on a monthly basis for in-house support services, unless otherwise approved by the Department s project manager. The invoice must be preceded by a progress report which shall, at a minimum, identify the hours labored by the employee on a daily basis. The Department s project manager will compare the days labored in the progress report with the task tracking sheet that in-house support employees will be asked to submit on a daily basis (the task tracking sheet identifies the tasks in which the employee worked during the day, and the time spent on each task). This task tracking sheet is to be submitted to the Department project manager via e-mail. The Department recommends that the employee also send a copy of such e-mail to his/her Consultant project manager. Should there be a discrepancy between the task tracking sheets and the progress report, the Department s project manager will reject the progress report and request that it be revised and resubmitted so that it is in full agreement with the task tracking sheets. 6. Evaluation of in-house support employees Employees providing in-house support services for periods longer than 21 working days will be evaluated on a monthly basis by the Department s project manager. The basis for evaluation will be determined for each employee based on the nature of the task(s) assigned. A copy of the evaluation will be provided to the employee and to the Consultant Project Manager. 23