Atch_4_PWS_TO_3_27_Mar_18_(SAMPLE_ONLY).pdf

HTC711-18-R-D007

Attachment 4

Performance Work Statement Sample Task Order 3

Traffic Engineering and Safety Study 27 March 2018

1. OBJECTIVE

This Performance Work Statement (PWS) defines the specific tasks to be performed under the Traffic Engineering and Safety Study task order under the Surface Deployment and Distribution Command’s Transportation Engineering Agency (SDDCTEA) Traffic Engineering Services Indefinite Delivery, Indefinite Quantity (IDIQ) contract.

2. SCOPE OF WORK

The Contractor shall provide Traffic Engineering Services to SDDCTEA supporting Traffic Engineering Branch requirements in accordance with the details and specifications outlined herein.

3. TASK 1 - TRAFFIC ENGINEERING and SAFETY STUDY

The Contractor shall provide Traffic Engineering Services to SDDCTEA supporting Traffic Engineering Branch requirements in accordance with the details and specifications outlined herein. The Contractor shall provide all personnel, management, supervision, equipment, tools, supplies, materials, transportation, and any other items and services to inspect and evaluate the task to include: existing Entry Control Facilities (ECFs), Intersections, roadways, pedestrian safety, Traffic Safety Assessments (TSA), sign management study and other traffic engineering matters. Criteria shall be based on current SDDCTEA policies and practices, DOD, American Association of State Highway and Transportation Organizations (AASHTO), Institute of Transportation Engineers (ITE), and Federal Highway Administration (FHWA) policies and practices and specific Air Force, Army, Marines and Navy Branch policies and practices.

This task requires a high level of coordination with various installation stakeholders. The objectives of this task shall be completed as per the Delivery Table and developed as described in the following objectives:

3.1. Coordinate meetings and site visits with installation points-of-contacts to include approval of equipment placement and general operational parameters. Specifically, schedule and conduct an on-site in-brief with installation stakeholders to review the scope of work, discuss data collection activities and outcomes, and collect infrastructure information concerning future projects. Schedule and conduct an on-site out-brief with installation stakeholders to occur following SDDCTEA’s review and concurrence with the contents of the Draft Report. The out-brief presentation shall report major deficiencies and preliminary results, while also addressing potential improvements and recommendations. The out-brief shall also serve the purpose of soliciting comments from the installation to incorporate into the Draft-Final version of the Report.

• Installation Point of Contact:

o Name: CPT John Sample o Position: Base Commander o Department: Department of Logistics o Installation: Fort Army Base o Phone #: 555-867-5309 o E-mail: john.d.sample.mil@mail.mil

3.1.1. Project Schedule: Contractor shall provide to the COR and the assigned TEA

Traffic Engineer a draft Project Schedule within 10 days of notification of award of task order. Contractor shall provide a final Project Schedule within 5 days after receipt of comments on the draft. Contractor shall provide assigned Traffic Engineer with a monthly (date by agreement) update of the schedule.

3.1.2. In-brief: Contractor, in conjunction with Installation POC, shall schedule a face-to-face In-Brief Presentation/Meeting. Typically, this shall be conducted at the start of field collection of data. Contractor shall provide an electronic version of the Briefing to the COR and the assigned Traffic Engineer 10 days prior to the meeting for the draft presentation and 5 days prior to the meeting for the final presentation.

The Contractor shall provide to the COR and assigned Traffic Engineer meeting minutes of the In-Brief no later than 5 days after the In-Brief.

3.1.3. Draft Report: Contractor shall provide a Draft Report to the COR and assigned

Traffic Engineer no later than 90 days after completion of the site visit. The DrafT Report shall include adequate text, illustrations, and data to thoroughly document existing conditions & deficiencies; as well as to support the recommended improvements. Recommendations for all necessary improvements shall be described in text and illustrated. SDDCTEA shall have 15 days to review the Draft Report and provide comments. Draft report does not need to contain an executive summary.

3.1.4. Out-brief: Upon concurrence by the assigned Traffic Engineer that all comments on the Draft Report have been addressed, the Contractor shall coordinate with the Installation POC to schedule an Out-Brief at the soonest possible time available.

The Contractor shall provide a Draft copy of the Out-Brief presentation to the COR and assigned Traffic Engineer 10 days prior to the Out-Brief and 5 days prior to the meeting for the Final Out-Brief Presentation. The Contractor shall provide Out- Brief meeting minutes within 5 days of the Out-Brief. The Contractor will provide the Installation POC, cc’ing the COR and assigned Traffic Engineer, with a Draft Report (with SDDCTEA comments addressed) either before or at the Out-Brief.

The Installation POC shall have 15 days to review the Draft Report.

mailto:john.d.sample.mil@mail.mil

3.1.5. Trip Reports: Contractor shall provide trip reports for In-Brief, Site Visits, and Out-Brief no later than 10 days following trip for draft and five days after comments for final. Trip report will include activities undertaken; personnel traveling from Contractor; personnel met with from Installation; summary of justification for travel costs or ODC; and any follow-up actions necessary.

3.1.6. Draft-Final Report: Contractor shall provide a Draft-Final Report no later than 30 days after the Out-Brief. Draft-Final will contain an executive summary that summarized findings, recommendations and estimates. Draft-Final will be provided to COR, assigned Traffic Engineer, and Installation POC for concurrent review of no more than 15 days.

3.1.7. Final Report: Final report shall be submitted to the assigned Traffic Engineer and

Installation POC 30 days after end of Draft-Final comment period. Electronic copies will be sent to the assigned Traffic Engineer and the Installation POC. Two hard copies of the Final Report shall be transmitted to the Installation POC. Hard copies shall be 8.5 inch by 11 inch bound booklets with 11 inch by 17 inch pull out fold outs when necessary.

3.2. Conduct traffic Data Collection activities, including automatic traffic counts and required manual intersection counts. Counts shall be in accordance with the Institute of Transportation Engineers (ITE) recommended practices. Automatic traffic counts shall provide at least one 24-hour (15 minute interval) count. Traffic counts shall not be conducted on Monday’s or Friday’s, during inclement weather, or weeks with adjacent holidays unless approved by the installation POC and SDDCTEA.

Additionally, substantially remove all roadway tapes and/or other adhesive products necessary to achieve performance objectives listed herein, unless otherwise instructed by the installation POC. At a minimum, traffic data collection shall include:

• Collection of traffic data for four (4) ECFs shall include automatic traffic counts (24-hour), as well as documentation of the 15-minute incremental traffic queue during the AM, Mid-day, and PM peak-hours, and required manual intersection counts for two (2) adjacent roadway intersections (one on base and one off base for each ECF) during the AM, Mid-day, and PM peak-hours.

• Collection of existing Average Daily Traffic (ADT) volumes for ten (10) additional locations. This is intended to be a 2-way ADT at each location and will be used to determine base traffic patterns.

o A speed summary and inclusion into the report will also be required for each of these locations.

• Collection of existing Peak-Hour Turning Movement Counts (AM, Mid-day, and PM) for seven (7) additional intersections.

• Development a preliminary plan of count locations for presentation and discussion at the project in-brief meeting. The final locations may be determined in coordination with the installation stakeholders during the meeting.

3.3. Interview the post force protection and ID check personnel to query additional information concerning the current operation of the ECF(s).

3.4. Conduct an Origin-Destination (OD) Survey

3.5. Perform a compliance assessment of the existing ECF(s) based on the UFC 4-022-01;

4-022-02; SDDCTEA Pamphlet 55-15; the Manual on Uniform Traffic Control Devices (MUTCD); and the DoD Supplement to the MUTCD. This assessment shall analyze the adequacy of existing facilities to meet the future demand needs; including visitor center, truck inspection access, force protection and proper placement of Active Vehicle Barriers (threat calculations), roadway and ID check area lighting, roadway clear zone, striping, signing, and pedestrians.

3.6. Provide a comprehensive installation wide review of studied ECFs for proper future location, size, total number of lanes, and other related information. Calculate the ECF lane and manpower requirements based on SDDCTEA Pamphlet 55-15, UFC 4-022- 01, and the SMART Decision Evaluator software v.2.

3.7. Conduct a Traffic Safety Assessment (TSA) and provide remedial recommendations for the entry control facilities and studied intersections. Adequate detail should be provided to explain the deficiency. Recommendations shall provide specific improvements or fixes for the deficiencies noted; generalized statements will not be accepted. The TSA shall inventory deficiencies and, at a minimum, address:

• Traffic control

• Lane configuration

• Signing

• Striping

• Design vehicle accommodation/geometric adequacy

• Operational concerns

• Intersection Sight Distance

• Roadside hazards

• Improper traffic control devices

• Bicycle and pedestrian access

• Analysis of the most recent five years of crash data, and shall include remediation recommendations.

Provide a TSA for six (6) additional locations (other than studied intersections and ECFs). The installation has specific sites/locations where there has been pedestrian and bike conflicts with vehicles and other areas of concern.

3.8. Calculate the future traffic demand for ECFs, intersections, and roadways utilizing ITE trip generation analysis. Distribute and assign the traffic to the affected study intersections and roadway locations. Independent forecasting for the future traffic to be based on known building construction and/or relocation, Master Plan, BRAC, Grow the Army, and/or other known re-stationing. All information shall be obtained through interview with the installation POC and through independent research. The traffic forecast design year shall be full build out year of all known improvements and shall be based on the recommended 30th Highest Volume (Design Hourly Volume, DHV).

3.9. Utilize SMART Decision Evaluator software (available upon request from the COR) to assist in identifying the existing and future impacts of security, manpower, automation, and traffic on the ECF operations. ECFs shall be designed to a level of service “D”, or an acceptable length of traffic queue, for the fully compliant design year evaluation.

3.10. For all intersections and roadways counted, provide existing and future capacity and flow analysis utilizing HCS or SYNCHRO, traffic capacity software. Where complicated roundabout analysis is required, SIDRA Intersection software is preferred.

Provide a summary of results and recommendations based on Level of Service (LOS), with consideration of traffic flow and safety. Intersection summary shall include discussion of lane group LOS as well as intersection LOS. Analysis shall include queuing analysis for all intersection lane groups to identify congestion and a cursory check of signal warrants for all studied intersections. Recommendations shall be provided for the operational needs of the existing intersections, including intersection control type, pedestrian accommodations, and geometric improvements. Roundabouts shall be evaluated for all locations. Document the LOS for intersections for existing conditions, future with no improvements, and future with improvements.

3.11. Provide conceptual scaled drawings of recommendations for ECFs, intersections, and/or roadways that are included as part of this study (sight distance triangle requirements, geometric adjustments, striping adjustments, design vehicle accommodations, sidewalks, bicycle accommodation, etc.). This shall include all geometric data used in the roadway alignment, recommended lane configuration, active & passive vehicle barrier placement, striping, signing, environmental constraints, and a statement of feasibility of design. Additionally, label all facilities shown on ECF concepts. (This is intended to be 11” x 17” foldouts graphically identifying all recommendations - prepared in color to scale with MicroStation CADD software, and overlaid onto an aerial photograph).

3.12. Develop recommendations which shall address fully compliant facility; immediate health or safety issues; existing traffic issues; and any recommendations shall maximize use of existing facility with minimal construction/reconstruction.

Recommendations short of full compliance should focus on low costs (possibly non-permanent) solutions that meet capacity needs and provides adequate threat containment. Example recommendations may be, relocating AVB (s), adding chicanes, changing the safety scheme from signs and signals to stop control, adding an inspection area, utilizing outbound lanes in the morning for processing, etc.

3.13. Provide estimate of cost for all engineering recommendations with sufficient details such that the installation can use the figure for preparation of a DD-1391.

3.14. Provide a photographic record of all deficiencies where applicable.

3.15. The Contractor shall conduct an inspection and inventory of all regulatory, warning, and guide signs located on the installation. The number of signs that will not exceed five hundred (500) signs.

3.15.1.1. The Contractor shall verify/capture the following attributes:

• Sign Identification Number (i.e. a unique number identifying the sign panel), developed in coordination with the installation POC

• Sign Location (annotated in report

• GPS coordinates (i.e. GPS latitude and longitude) o The service provider shall survey the sign position using resource grade equipment and the survey shall match the projection system of the File Geo-database. All new sign locations shall be surveyed on the North side of the sign post and maintain +/-4” horizontal accuracy. The Contractor shall provide the “job” file from the GPS unit for all surveys.

• Street/Roadway Name (i.e. route name on which the sign is located)

• Installation Date (i.e. date when sign installed)

• Sign photo

• Sign code (i.e. the MUTCD designation)

• Sign message (if unique)

• Direction of travel (i.e. northbound, southbound, eastbound, westbound)

• Sign Position (i.e. Location of sign relative to road – left, right, overhead)

• Lateral offset (i.e. distance from the edge of the traveled way to the near edge of sign panel)

• Sign dimensions (i.e. width and height of sign panel)

• Mounting Height (i.e. height measured vertically from the bottom of the sign to the top of the curb, or in the absence of curb, to the elevation of the near edge of the traveled way)

• Location of sign panels on assembly with other sign panels (For example -label top sign as 1 and lower panels as 2, 3, etc.)

• Sign Substrate (i.e. the sign backing material; such as aluminum, plywood, fiberglass-reinforced plastic)

• ASTM D4956 “Type” and manufacturer of sheeting material (i.e. grade of retroreflective material)

• Sign retroreflectivity (Sign retroreflectivity shall be measured using one of the approved MUTCD methods with the chosen method identified within the PWS.) Retroreflectivity readings are not required for street name signs.

• Number of sign supports

• Type of sign support (i.e. wood post, U-channel steel post, square or round tube steel post, I-beam steel post, etc.)

• Physical condition of sign face (Comment on condition [e.g. cracking, delamination, etc.], fading or discoloration, contrast, retroreflectivity, and damage due to vandalization)

• Rating of the physical condition of sign face (e.g. good, marginal, poor)

• Rating of the physical condition of mounting (e.g. good, marginal, poor)

• Inspection/maintenance date (i.e. date when sign was last inspected and/or maintained)

• Inspection comments (i.e. supplementary notes about the sign)

• Name of Inspector (i.e. person who inspected and/or maintained the sign)

• Maintenance history (i.e. type of maintenance last performed)

• Additional field and desktop observations to be considered:

o Is the sign the correct one in accordance with the 2009 Edition of the MUTCD? (i.e. proper application) o Is the sign the correct size?

o Is the sign needed per the 2009 version of the MUTCD? (Provide only the required signage, eliminating redundant and unnecessary signs.)

o Is the sign correctly positioned with respect to lateral clearance?

o Is the sign correctly positioned with respect to height above ground?

o Is the sign correctly positioned with respect to longitudinal placement along road?

o Is the sign visible, both day and night, at the required distance? If not, indicate cause of problem (e.g. blocked by vegetation, other signs, etc.)

o Is sign support crashworthy (e.g. breakaway, yielding, or shielded with a longitudinal barrier)? If not, are sign supports located outside the clear zone?

3.15.1.2. The Contractor shall recommend additional signing, in accordance with the MUTCD, make installation recommendations in the report using the MUTCD sign codes, and provide GPS coordinates for all new locations and/or recommendations.

3.15.1.3. The Contractor shall develop a proposed baseline replacement schedule, in coordination with the installation POC. This replacement schedule shall be based on the findings of the initial inventory, with all signs identified for replacement, to be replaced in accordance with the MUTCD. The Roadway

Sign Management System shall include all signs inventoried and the Contractor’s estimate of remaining sign life.

The replacement schedule shall also consider installation’s budget and recommendations. The replacement schedule, which is built upon the initial sign inventory and inspection, shall become the Roadway Sign Management System. The System shall be designed for use as a management method to maintain traffic sign retroreflectivity at or above the established minimum levels, with the future users being the installation personnel.

3.15.1.4. The Contractor shall provide recommendations on sheeting types based on local environmental conditions, cost, and expected life.

3.15.1.5. The Contractor shall develop cost estimates based on the identified replacement schedule and recommended sheeting type. Include a separate cost for upgrading to breakaway sign posts, if required. Provide cost estimates in future dollars based on the anticipated year of replacement.

3.15.1.6. The Contractor shall develop a complete inventory database in ESRI GIS format and also include data results in Microsoft Excel format.

4. DELIVERABLES

4.1. All products, studies and analysis that are developed or provided under this PWS are the sole property of the Government. The Contractor shall not use, disclose, transfer, convert, or otherwise appropriate any technical data, processes, studies, or engineering analysis developed during performance of this PWS, unless written permission from the Contracting Officer is obtained. IAW DFARS 252.227-7013 and DFARS 252.227- 7014, the Government obtains under this contract "unlimited rights" to all non-commercial computer software, software source code, computer software documentation, enhancements, technical data, and similar non-commercial data developed exclusively at Government expense and delivered to the Government under this contract. "Unlimited rights" means rights to use, modify, reproduce, release, perform, display or disclose in whole or in part, in any manner and for any purpose whatsoever, and to have the ability to authorize others to do so. If any technical data or computer software applicable herein is changed (e.g. updated software, maintenance patches, version changes, new releases, substitutions) incident to this contract or in the exercise of any option associated with this contract, the Contractor shall deliver them with “unlimited rights” and those rights shall be at no cost to the Government.

4.2. All deliverables shall be made electronically via email to the Contracting Officer Representative (COR). If a delivery is submitted via email and the size or the firewall prevents its delivery, the Contractor shall provide a Secure File Transfer Protocol site that allows the Government to download the deliverable. If a site is not available or not feasible, the Government will make one available to the Contractor. In case no sites are available, the Contractor shall deliver via compact disk / digital videodisk (CD/DVD).

The CD/DVD must be properly labeled to identify the content to include classification, version number, and date.

4.3. Inspection and Acceptance. A deliverable is a specific measureable, tangible, and verifiable activity, outcome, result, item, or product that the Contractor shall provide and that will require formal Government acceptance and approval. The Government will review, assess, and provide comment, as required.

Final inspection and acceptance of all work performed, reports, or other deliverables shall be performed at the place of delivery. The COR will notify the Contractor of deliverable acceptance or provide comments in writing.

Deliverables Table Asserted Rights

Deliverable Delivery Schedule (days are calendar unless otherwise specified) Medium/Format PWS Paragraph

Project Progress Schedule Draft - 15 days after call order award.

Final – 5 days after receipt of draft comments;

Monthly Update- by agreement.

Microsoft Product (email soft copy)

3.1.1 Unlimited

Installation In-brief Presentation

Draft - 10 days prior to meeting

Final – 5 days prior to meeting

MS Power Point / Contractor Format using SDDCTEA template (email soft copy)

3.1.2 Unlimited

Installation In/Out-brief Meeting Minutes (including action items & responses)

5 days after meeting. MS Word / Contractor Format (email soft copy)

3.1.2 & 3.1.4 Unlimited

Draft Report -To SDDCTEA 90 days after completion of site visit.

-To installation after addressing SDDCTEA comments but NLT Out- Brief

Electronic.pdf / Contractor Format (email soft copy)

3.1.3 & 3.1.4 Unlimited

Installation Out-brief Presentation

Draft Slides - 10 days prior to meeting Final Slides – 5 days after receipt of draft comments.

MS Power Point / Contractor Format using SDDCTEA template (email soft copy)

3.1.4

Unlimited

Draft-Final Report 30 days after the Out-brief Meeting

Electronic.pdf / Contractor Format (email soft copy)

3.1.5 Unlimited

Final Report

30 days after review period

Electronic.pdf / Contractor Format (email soft copy)

Electronic (CD) (one per hard copy for Install. and one for TEA)

2 Hard Copies (8½” x 11” booklet w/11” x 17” fold outs when applicable)

3.1.6

Trip Report Draft - NLT 10 days following trip completion

Final - 5 days after receipt of draft comments.

MS Word / Contractor Format (email soft copy) 3.1.7

5. SERVICE DELIVERY SUMMARY

The Service Delivery Summary (SDS) represents the most important contract objectives that, when met, will ensure contract performance is satisfactory. Although not all PWS requirements are listed in the SDS, the Contractor is fully expected to comply with all requirements in the PWS.

Contract Deliverables PWS Paragraph Performance Threshold Draft, Draft-Final and Final Reports completed in an accurate and timely manner

3.1 through 3.15.1.6

No more than one late delivery and no more than five days late. No more than two sets of corrections/edits with all corrections accomplished within five days of notice.

6. GENERAL INFORMATION (SAMPLE TASK ORDER)

6.1. Place of Performance. The primary place of performance of field activities will be the subject installation as identified in the individual task order. All other work not requiring field data collection may occur at the primary place of business of the Service Provider, or sub-contracted entities (For Sample Purposes Only).

6.2. Period of Performance. The period of performance for this contract is 01 October

2018 through 30 September 2019 (For Sample Purposes Only).