A05 1240BE23Q0059_PWS_80242023.pdf

US Department of Agriculture (USDA)

U.S. Forest Service

2023 Forest Service Pavement Management

Performance Work Statement

Solicitation: 1240BE23Q0059

Contract: TBD

Contents Project Title General Information

1.0 Background and Purpose

2.0 Definitions

3.0 Performance Tasks and Performance Standards

4.0 Deliverable / Schedule

5.0 Government Furnished

6.0 Travel- Not Used

7.0 Contractor’s Key Personnel

8.0 Security Requirements -Not Used

9.0 Data Rights

10.0 Section 508 - Electronic and Information Technology Standards –Not Used

11.0 Performance Requirement Summary

ATTACHMENTS

TABLE 1. Data Dictionary Paved_Roads_Lines/Polygons, Parking Lots with Road Centerline TABLE 2. Forest Service data to PAVER Fields TABLE 3. Paved_Parking Adjacent to Road Centerline, Multi-part Polygons, and Boat Ramps Example 1 Road to Parking Lot, road is <0.10 mi long Example 2 Road to Parking Lot, road is >0.10 mi long Example 3. Parking Where Road Continues Through Example 4. Parking Areas, Multi-part Polygons at Recreation Sites Example 5. Boat Ramp Example Additional PAVER and Field Data Collection Direction

Project Title 2023 U.S. Forest Service Pavement Management

General Information

1.0 Background and Purpose

The US Forest Service has a requirement for inventorying and reporting current surface condition of roads, parking areas, and boat ramps. This contract is for the inventory and condition assessment of paved assets on multiple Forests.

The work items within this contact include creating or editing an existing PAVER and GIS database to reflect the inventory of paved roads, parking lots with roads, adjacent paved parking, and boat ramp features using aerial imagery and field observations. Field verify the surface type, lengths, widths, and GIS created polygons. Make edits to PAVER and GIS as necessary after field observations.

This Contract includes a list of roads that have adjacent parking and boat ramps that are to be condition surveyed. Field collect pavement distresses per ASTM D6433. The intent is to provide a functional pavement management database using PAVER software with an accurate inventory of road section lengths, parking, boat ramps, report network surface condition, and to provide recommendations for maintenance or reconstruction options. Maintenance and rehabilitation recommendation reports will also be used to understand budget needs and prioritization of work.

The pavement distress data collection is to be accomplished using manual method or semi-automated methods with manual distress data interpretation. The intent is to collect all of the ASTM distresses within the sample areas. The samples are to represent the full width of road. The contractor is required to perform enabling tasks including a proof-of-concept review for manual field or semi-automated data collection, business practices and protocols for data collection, and approved work schedule.

Performance tasks are specified at PWS Section 3.

1.1 Project Location.

Predominately in Forest Service Regions 5 & 6 California, Oregon, Arizona, Kentucky, Tennessee, North Carolina, Wisconsin, Pennsylvania See PWS paragraph 3.

Forest Service WO Engineering 324 24th Street Ogden, UT 84401 Todd Touchard, (385) 358-2473, todd.touchard@usda.gov

1.2 Period of Performance.

25 September 2023 to 30 December 2024

1.3 Contractor Work Plan, Schedule, Forest Communication, and Project Segmentation. The

Contractor shall develop and maintain an overall work plan that includes the field work schedule, communication plan, and safety plan with performance milestones to ensure services are performed in accordance with this PWS. The plan shall also include any planned sub-contracting.

The work will be conducted on multiple Forests and States. Contractor shall attend virtual meeting(s) with the Forests to describe data collection process, present proposed schedule, discuss road access, road conditions, safety, contact lists, contact phone numbers, and potential impacts to public. The schedule and field work will be impacted by gate closure dates, snow pack levels, wildfires, construction activities, etc.

During field work, the Contractor will need to regularly communicate with Forest Staff on progress, changes to schedule, etc. A contact list of Forest Service staff will be provided. For planned roads that can not be surveyed, the survey work will either be re-scheduled or other roads substituted.

The contractor shall analyze the existing PAVER databases, GIS shapefiles, paved roads inventory and create workable schedules and delivery products that will be used to defined project segmentation or milestones. The project segmentation will be used to define partial and final payments events for task items. Project segmentation shall define the work and deliverables associated with tasks for invoicing. The work plan, schedule, and project segmentation shall be submitted to the COR within thirty (30) days from the date of award for comments and acceptance.

Deliverable 01

1.4 Quality Assurance: The Contractor shall comply with the quality assurance program as defined in the Quality Assurance Surveillance Plan (QASP). It defines how the performance standards will be applied, the frequency of surveillance, and the minimum Acceptable Quality Level(s) (AQL).

Government surveillance of Contractor performance is not limited to the Performance Objectives as outlined in this PWS. The Government reserves the right to conduct compliance surveillance of any contractual requirement of this acquisition.

1.5 Quality Control Plan. The Contractor shall develop and maintain a QCP to ensure services are performed in accordance with this PWS. The QCP document or plan must be forwarded to and accepted by the COR. The Contractor shall develop and implement procedures to identify, prevent, and ensure non-recurrence of deficiencies. The Contractor’s QCP is the means by which the Contractor ensures that work complies with the requirements of the contract. The QCP shall be delivered to the CO within thirty (30) days from the date of award. After acceptance of the QCP the Contractor shall receive the Contracting Officer’s acceptance in writing of any proposed change to the QCP. Deliverable 02

1.6 Contracting Officer’s Representative (COR): A COR may be assigned to this contract to monitor all technical aspects and assist in contract administration. The COR may be authorized to perform the following functions: ensure that the Contractor performs the technical requirements of the contract; perform inspections necessary in connection with contract performance; maintain written and oral communication with the Contractor concerning technical aspects of the contract;

issue written interpretations of technical requirements (without increasing or decreasing contract scope), including Government drawings, designs, and specifications; monitor Contractor's performance and notify both the CO and Contractor of deficiencies; and provide site entry of Contractor personnel. The COR is not authorized to change any of the terms and conditions of the contract.

1.7 Accidents: Report any accident within 24 hours from occurrence to the COR. Deliverable 03

2.0 Definitions

AASHTO R56- Standard Practice for Certification of Inertial Profiling Systems. This practice describes a certification procedure for test equipment used to measure a longitudinal surface elevation profile of highways based on an inertial reference system that is mounted on a host vehicle

AASHTO R57- Standard Practice for Certification of Inertial Profiling Systems. This practice describes the procedure for operating and verifying the calibration of an inertial profiling system. This practice is meant to be performed as a quality control/quality assurance (QC/QA) test for use with the appropriate smoothness specification for paving operations and for network-level data collection.

AASHTO R 85-18- Standard Specifications and Standard Practices. Quantifying Cracks in Asphalt Pavement Surfaces from Collected Pavement Images Utilizing Automated Methods

AASHTO R 86-18- Standard Specifications and Standard Practices. Collecting Images of Pavement Surfaces for Distress Detection

AASHTO M 328- Standard Specification for Inertial Profiler. The objective of this specification is to define the required attributes of an inertial profiler, which, when combined with an operator, becomes a complete inertial profiling system (IPS). The system may be used to measure a longitudinal pavement profile for construction quality control and acceptance or for network data collection.

Adjacent Parking- Parking that along or at end of a road. The beginning or edge of parking is within 500ft of road. Parking lot may or may not have an access road or entrance driveway.

ASTM D 6433-20- Standard Practice for Roads and Parking Lots Pavement Condition Index Surveys

ASTM E950- Standard test method for measuring the longitudinal profile of traveled surfaces with an accelerometer established inertial profiling reference.

ALQ, Acceptable Quality Level- The allowable leeway or variance from a standard before the

Government will reject the specific service. An AQL does not say that the Contractor may knowingly offer defective service. It implies that the Government recognizes that defective performance sometimes happens unintentionally. As long as the percent of defective performance does not exceed the AQL, the service will not be rejected by the Government. The Contractor, however, must re-perform the defective service when possible.

IRI- International Roughness Index

FHWA- Federal Highway Administration

Life-Cycle Sustainment Plan (LCSP) Outline provides a framework to think systematically and critically through the set of planning factors that must be integrated and communicated across the enterprise to achieve required sustainment outcomes.

PAVER 7- The Pavement Maintenance Management System software. Uses inspection data and a pavement condition index (PCITM) rating from zero (failed) to 100 (excellent) for consistently describing a pavement's condition and for predicting its M&R needs many years into the future.

Performance Requirements Summary (PRS). Identifies the key performance indicators of the contract that will be evaluated by the Government to ensure the Contractor meets standards.

PCI, Pavement Condition Index- Rating from 0 to 100 of the severity and extent of distresses observed on a pavement surface. Examples of typical pavement surface distresses are spalling, rutting, scaling, and cracking.

Quality Assurance Surveillance Plan (QASP). An organized written document used for quality assurance surveillance. The document contains specific methods to perform surveillance of the Contractor for each item of the Performance Requirements Summary.

Semi-Automated Condition Survey- Determining the ASTM distress severity and/or quantity using a combination of computer aided software and collection with manual observations.

3.0 Performance Tasks and Performance Standards

3.1 PAVER and Graphic Information System (GIS) Overlay Work, Inventory, and Field Observation Edits. Task includes using aerial maps to create GIS polygons and lines to represent the paved assets.

GIS work shall be submitted 30 days for review before doing field data condition collection activities.

Existing PAVER databases likely will not have all the adjacent parking lots, road/parking lots, adjacent parking areas, and paved boat ramps that are required to be inventoried and condition surveyed.

Either create a new GIS/PAVER database and move prior road inspection data, or edit the existing GIS/PAVER as needed to meet current attached schema and include missing features. A list of the existing database are shown below.

3.1.1 Existing GIS and PAVER database data.

Forest Existing

PAVER

Database

Existing GIS Polygon Work

ELDORADO NATIONAL FOREST - CA Yes Limited STANISLAUS NATIONAL FOREST - CA Yes No OCHOCO NATIONAL FOREST– OR Yes No SIUSLAW NATIONAL FOREST – OR Yes No UMPQUA NATIONAL FOREST – OR Yes No WILLAMETTE NATIONAL FOREST – OR Yes No DANIEL BOONE NATIONAL FOREST – KY No No CHEROKEE NATIONAL FOREST – TN No No LAND BETWEEN THE LAKES – KY Yes No NATIONAL FORESTS IN NORTH CAROLINA – NC No No CHEQUAMEGON-NICOLET NATIONAL FOREST - WI Yes Limited

When creating a new PAVER database, the Contractor shall edit provided road centerlines to create a GIS polygon layer representing the paved roads. Draw polygons to represent adjacent features including paved boat ramps, parking lots, and other paved parking areas (see GIS Deliverables Table below).

The road list may include mis-identified roads as paved but are gravel, and the length of the paved road may not be correct. Use available aerial images to identify and edit road polygons and features (parking and boat ramps) before doing field work. The GIS schema requirements for the attribute table, road sectioning, parking lots, parking areas, and boat ramps, etc are attached. An example geodatabase is also attached.

During field work, create sketches and notes to correctly inventory assets and update GIS layers as necessary. The updated shapefiles will be used to update or create the PAVER database for final delivery. Provide a report per Forest with major errors found such as surface type as gravel not paved include error description and screen shot or pictures as needed. The GIS deliverables are shown in Table below.

3.1.2 GIS Deliverables.

Item No.

Deliverable Objective Due

1 Per Forest Geodatabase with the following feature classes:

1. Centerline

2. Road Paved Areas Polygons

3. Other Paved features Polygons

Centerline: Final product of the realigned road centerlines with all required attributes and metadata updated.

30 days after USFS staff confirm completion of review phase

2 Road Paved Areas Polygon Feature Class: Roads, Parking (parking lots that have an existing Forest Service provided centerline).

Final product of buffered road polygons by road segment to approximate width of road. All required attributes will be filled in and metadata updated.

30 days after USFS staff confirm completion of review phase

3 All other paved features Polygon Feature Class: Parking Lots, Parking Areas, Boat Ramps that are features near or adjacent to a road.

Final product of paved parking areas and boat ramps associated with the roads. These polygons will be clipped to the road layer with no slivers or gaps between aligning segments. All required attributes will be filled in and metadata updated.

30 days after USFS staff confirm completion of review phase

Standard:

• The realignment of linear road features to match aerial photography within the project area.

Displacement of linear features shall not exceed 10 feet of centerline of road.

• Polygons of parking lots and boat ramps shall have a GIS area within 90% of true surface area.

• Payment for this task may be billed once completed and approved. The final GIS work after field observation shall be invoiced in the task shown in Section 3.5.

• The location of the roads, road list, existing GIS line work that will be edited, is provided as a KMZ, Excel spreadsheet, and shape files.

Acceptable Quality Level: 98%

3.2 Proof-of-Concept Review. Government and Contractor shall agree upon a set of roads and features for proof-of-concept review. This on-site technical field evaluation shall include at least 10 miles of various pavement condition, uses, and surface types that are anticipated to be encountered. Examples of pavement use types include roads, parking lots, campground parking areas, and boat ramps. Surface types and surface seals include: AC, AAC, ST, PCC, chip seal, slurry seal, and fog seals. Demonstrate paved data collection methods, methods for Maintenance and Rehabilitation (M&R) recommendations, sampling, video collection, pictures, GIS/inventory verification, and safety procedures.

The data collection vehicle/equipment being proposed by the contractor for performing the work for this contract shall provide equal or better performance than the collection vehicle used for the on-site evaluation tests. The technical field evaluation will evaluate the contractor’s ability to perform the work described in Section 3.4. and shall be completed prior to initiating the field tasks described in paragraph 3.4.

Key personnel that will be doing the field collection shall attend the field work.

Sampling and data collection for proof of concept will require data collection in all lanes on the roads selected by the contractor. This task requires close coordination between the Contractor and the COR and approvals before beginning field data collection work.

Standard:

• Manual and/or Automated Methods of distress collection per appropriate standards.

• Process data and provide PCI ratings for government review based on ASTM D 6433-20.

• Provide a file compatible with PAVER 7 and in a format accepted by the COR within 30 days of data initially collected.

• Provide unpaved data in a format accepted by the COR within 30 days of data initially collected.

• Provide manual field check data for Quality Control.

• Allow 15 days for government review of data and obtain approval from CO before proceeding with data collection after proof-of-concept review.

3.3 Business Practice Protocols for Data Collection and Management. Develop and submit for approval Business Practice Protocols that meet industry standard requirements for completing Quality Control for the collection of data and include associated Protocols for data management of collected data points including the following. If doing automated surveys, at a minimum, the Contractor is to do a manual survey per road or per 10-miles of long roads.

• The distresses can be collected by automated means if it can be demonstrated to correctly report the condition category and PCI

• Field Data Collection Procedures for paved and unpaved roads.

• Quality Control Plan

• Collection of images for distress detection shall be in accordance with AASHTO R 86-18.

• Quantifying crack from collected images shall be in accordance with AASHTO R 85-18.

• Determine IRI of paved roads in accordance with AASHTO M 328 and ASTM E950 and certified according to AASHTO R56.

• Calibrate equipment according to AASHTO R57.

3.4 Paved Road Condition Survey, Field Surface Type and Inventory Verification. The intent is to obtain pavement distress data useful for reporting condition of paved assets, which will also be used for the planning of network wide maintenance and rehabilitation projects. The provided centerline mileage does not represent actual driven miles of the paved road or parking and should be understood to represent the Forest Service paved road route, parking, and adjacent paved features to be surveyed.

Task includes condition assessment of roads with associated parking lots, parking areas, and boat ramps. Surface condition assessments are to be done in accordance with ASTM Standard D 6433-20. Additional field work includes identifying fill failures in travel ways and record as additional samples. Collection of distresses can be done using manual or approved automated means with vehicles or devices that meet AASHTO and industry standards of quality assurance protocols.

In general, a minimum of 5 samples are to be done per mile of road. For pavements that have less than 45 PCI, the samples may be reduced to 3 samples per mile. When conducting manual or automated surveys, the samples may be reduced to as low as 1 sample per branch when less than 25 PCI or for safety, as approved by the COR.

Parking lots survey samples are generally done at a representative area within each lot.

Sampling can be reduced to represent multiple parking lots that have similar distresses. If one inspection represents multiple parking lots, copy the inspection to each section. Parking lot sample locations are to be described in the inspection comment field. For parking areas (multiple parking spots along the same Branch ID) within recreation areas find sample areas that are also representative.

Collect video along the length of roadway with sufficient resolution to record defects. Multiple pictures of the roadway maybe substituted for video in an acceptable format by COR. High quality pictures are to be taken of each sample and associated surveyed features. The contractor is to name, organize, submit pictures and video as accepted in format by COR.

Provide a standalone data viewing software and/or online/website for video/data display to interpret results.

The contractor shall field verify and correct PAVER data. See attached for additional data collection direction. Typical corrections include paved road length, road width, significant condition changes in road condition, unseen parking lots, boat ramps, and current surface type such as Asphalt (AC) & thickness, AC Overlays (AAC), Bituminous Surface Treatment (ST), Portland Cement Concrete (PCC), chip seals, surface seals, etc. This task requires field personnel that have experience and knowledge of identifying pavement and surface seal types and will be updated in PAVER Work History with work date of 01/01/1901 for surface seals, overlays, etc.

• Road, Parking, and Boat Ramp distresses identified and measured per ASTM 6433-20

• Data is uploaded via most current version of PAVER 7.

• Identify road surface type (AC, AAC, ST, PCC), surface seals (chip seal, slurry seal, fog seal, etc), and thicknesses.

3.5 PAVER Database Deliverable, Maintenance and Rehabilitation Report, Updated GIS Files.

Submit a draft PAVER database per Forest with updated shapefiles and include the previous inspections from existing PAVER database shown Table 3.1.1 in Section 3.1 into the correct Sections. Submit final database no later than 15 days after Forest Service review and comments.

An all-inclusive draft data collection and M&R report will be delivered to the Forest Service within 60 days of the completion of field data collection. Submit final report no later than 15 days after Forest Service review and comments. Report to include the minimum following items:

a) Executive Project Summary

b) Maintenance and Rehabilitation Plan (M&R) per Forest.

c) Budget scenarios per Forest: determine budget requirements for target 70 PCI, budget to maintain current PCI, and eliminate backlog scenario. All scenarios are 10-year.

d) Spreadsheet showing condition of each road and feature. The format includes Network

Name, Network ID, Branch Name, Branch ID, Route_CN, Section ID, Street Type, From, To, Inspection Date, PCI, and condition category.

• PAVER 7.1.1

Acceptable Quality Level: 95%

4.0 Deliverable / Schedule

DELIVERABLE REFERENCE FREQUENCY SUBMIT TO

01 – Contractor Work Plan In accordance with PWS paragraph 1.3

Within thirty (30) calendar days after contract award.

To the Contracting Officer via the Contracting Officers’ Representative (COR)

02 - Quality Control Plan

(QCP)

In accordance with PWS paragraph 1.5

Within thirty (30) calendar days after contract award.

To the Contracting Officer via the Contracting Officers’ Representative (COR)

03 – Reporting Accidents In accordance with PWS paragraph 1.7

Report any accident within 24 hours from occurrence.

To the Contracting Officer’s Representative (COR) and/or Contracting Officer.

04– Key Personnel In accordance with PWS paragraph 7.0

Within thirty (30) calendar days after contract award.

To the Contracting Officer via the Contracting Officers’ Representative (COR)

5.0 Government Furnished

The following are Government furnished items:

1) Excel spreadsheet of roads to be surveyed

2) KMZ file, Google Earth file showing location of roads

3) ArcGIS shape files of roads

6.0 Travel- Not Used

7.0 Contractor’s Key Personnel

7.1 The following positions are considered key personnel and shall be readily accessible to the COR during working hours:

Project Manager. Names key personnel and contact information shall be provided to the COR 10 calendar days of award. (Deliverable 04)

7.2 Contractor personnel qualifications. Within the last 3 years, experience and knowledge in Pavement Management Systems.

2 years experience as project manager on pavement management projects covering multiple states.

Signed resumes shall be submitted to the COR within 10 calendar days of award. (Deliverable 04)

8.0 Security Requirements -Not Used

9.0 Data Rights

All data collected and provided is the property of the USDA, U.S. Forest Service.

10.0 Section 508 - Electronic and Information Technology Standards –Not Used

11.0 Performance Requirement Summary

Required Services

(PWS Task)

Performance Standard

Acceptable Quality

Level (AQL)

Method of Surveillance

Graphic Information System Overlay Work and Field Verification. IAW Para 3.1

The realignment of linear road features to match aerial photography within the project area.

Displacement of linear features shall not exceed 10 feet.

Road surface shall be categorized by type

98% Initial Acceptance -100% Inspection

Proof of Concept Review. IAW PWS Para 3.2

• Process data and provide PCI ratings for government review based on ASTM D 6433-20.

• Provide a file compatible with PAVER 7 and in a format approved by the COR within 30 days of data initially collected.

• Provide manual field check data for Quality Control.

98% -Initial Acceptance -100% Inspection

Business Practice Protocols for Data Collection and Management. IAW PWS Para 3.3

•The distresses can be collected by manual or semi-automated means according to protocol set by AASHTO and Industry Standards •Field Data Collection Procedures •Quality Control Plan •Collection of images for distress detection shall be in accordance with

AASHTO R 86-18.

•Quantifying crack from collected images shall be in accordance with AASHTO R 85- 18.

•Calibrate equipment according to

AASHTO R57.

98% -Initial Acceptance, -Periodic inspections, -Random observations

Paved Road Condition Survey, PWS Paragraph 3.4

•Distress identified and graded.

•Data is uploaded via PAVER 7.

•Surface type identified.

•Paved surface inventory, length, width, surface seal

98% -Periodic inspections, -Random observations -Delivery

Maintenance and Rehabilitation Recommendation

-Executive Project Summary -List and Description of Route Sections 95%

-Initial Acceptance -100% Inspection -Delivery

IAW PWS Para 3.3 Report. IAW PWS Para 3.5

-M&R Recommendations based on field observation, notes, the PCI values, and/or distress types of each project -Data is uploaded into PAVER 7.

-PAVER 7 used to create budget scenarios

ATTACHMENTS

TABLE 1. Data Dictionary Paved_Roads_Lines/Polygons, Parking Lots with Road Centerline

Field Name Field Type Description/Domain NET_ID Text 10 Forest number provided in Road Core data as the Security ID, example

0101, 0304, 0419, etc.

NET_NAME

Text 25

You will be provided a spreadsheet of that provides Forest Name and corresponding Security_ID (Road Core data). So, 0306 would be entered as “GILA NATIONAL FOREST”.

RTE_CN Text 25 Provided field of the route CN number for each line segment.

PFSR_CLASS Text 25 Provided field contains the PFSR Status. Options are blank, FLTP NETWORK, FLTP

NETWORK – SUBSET.

BR_ID

Branch ID field. Use the provided road ID, which is the road number. For unknown roads that are required to be drawn, USFS will provide temporary ID naming such as CIB-01 for the first unknown road on the Cibola NF.

BR_NAME

Branch Name, i.e., road name if one is available. Not all road routes will have names so this field may be blank. For non-inventoried roads, use newly generated BR_ID as Name. Provided by USFS.

BR_USE Text 25 Branch Use. Populated with “ROADWAY” or “PARKING” BR_COMM Text 25 Branch comments, if any, for example to communicate info for field verification or need for the Forest Service to correct data errors.

SEC_ID

Text 10

Section ID. Sections are a contiguous pavement area having uniform construction, maintenance, usage history and condition. A section should have the same traffic volume and load intensity. If the surface type changes, then break the line. If not provided, populate a number for each road section in the format of 10, 20, 30. Break roads into 1- mile sections, except for the last section. The last section will be the remainder length of the road; it should not be a short section under 0.5 mile, or longer than 1.5 miles.

SEC_FROM

Road beginning of section milepost. For example, if SEC_ID is 10 then SEC_FROM = 0.0, If SEC_ID is 20 then SEC_FROM = 1.0, etc. If a roadway is an extension, the milepost would not start at 0 it would begin with the previous road milepost number (Beginning Mile Post (BMP) provided in Road Core data). To be reported with (3) significant figures.

SEC_TO

Road end of section milepost. The last section will be the ending miles of the line segment is the provided Ending Mile Post (EMP) of the road, not the calculated length of the GIS line of field measured length. This value is taken directly from the existing INFRA dataset (significant figures not changed). If a new intermediate section is created then the To is the mile post (0.001) where next Section begins. To be reported with (3) significant figures.

SEC_SURFAC

Paved area material. Use provided Surface_Type, observed surface in aerials, or provided current surface types. Populate with “AC”, “ST”, “PCC”.

AC=Asphalt or Paved, ST= Bituminous Surface Treatment, or PCC=Portland Cement Concrete.

SEC_RANK

Section road ranking. Use the Functional Categories to populate this Field with “A”, “C”, or “L”. Arterial, Local, Collector, If blank populate with L.

SEC_CONSTR Text 10 Date (if known) of road segment construction. This will be provided by USFS and, if not known, a default date of 1/1/1900 will be used.

Field Name Field Type Description/Domain (Table 1 Continued)

SEC_LENGTH

Double

For road lines use the calculated length of each road segment to the nearest whole foot (ft). For road polygons, use the same number calculated for the road line segment. If the road polygon is a parking lot, SEC_LENGTH is the square root of the calculated total area. To be reported with (1) significant figures.

SEC_WIDTH

For road line features use 17.9 for a single lane road or 23.9 for a double lane road. For road polygons, use the same number calculated for the road line segment. If the road polygon is a parking lot, SEC_WIDTH is the square root of the calculated total area. To be reported with (1) significant figures.

OPER_MAINT

Use provided OPER_MAINT_LEVEL, Operational Maintenance Level, of the segment and converted to abbreviations: OPML-1, OPML-2, OPML- 3, OPML- 4, OPML-5. If not provided or blank be designated as “NA”.

Values will need transform, i.e. “2 - HIGH CLEARANCE” becomes “OPML-2”, etc.

STREET_TYPE

Street type. Will be “ROADWAY” for all road sections, if the road centerline includes parking, those sections will be labeled as

“PRKNG_LOT”.

LANES_PAVE Text 10 Number of road LANES provided and convert to single digit number such as “1”, “2”, etc.

AREA_SQFT

DOUBLE

For Paved_Road_Polygons: Right click field name and use Calculate Geometry to derive area values in square feet. To be reported with (0) significant figures.

TABLE 2. Forest Service data to PAVER Fields

PAVER

INFRA FIELD

FS Road Core Data

GIS TABLE

HEADING

COMMENTS

N E

T W

O

R K

ID SECURITY_I NET_ID SECURITY ID

NAME

NET_NAME

FOREST NAME

B R

A N

C

H ID ID BR_ID ROAD ID

NAME NAME BR_NAME ROAD NAME

USE - BR_USE ROADWAY

COMMENTS - BR_COMMENT ROAD COMMENTS

RTE_CN RTE_CN RTE_CN

S E

C T

I O N

ID

ROAD: 010, 020, 030...

PARKING LOT w/ road centerline: 10, 20, 30 PARKING w/ road center-line: PL-01, PL-02…

Parking Area: PA-01, Boat Ramp: BR-

FROM

BMP (FIRST

SECTION)

TO

EMP (LAST SECTION)

SEC_TO

SURFACE SURFACE_TY SEC_SURFACE AC, ST, OR PCC

RANK FUNCTIONAL_CLASS SEC_RANK A, C, or L

CONSTRUCTION

DATE

- SEC_CONSTR MM/DD/YYYY (IF UNKNOWN 01/01/1900)

LENGTH (FT) - SEC_LENGTH ROAD: LENGTH OF SECTION IN FEET

PARKING: 𝐴𝐴𝐴𝐴𝐴𝐴𝐴𝐴𝐴𝐴𝐴𝐴 or calculated

WIDTH (FT) - SEC_WIDTH ROAD: WIDTH OF ROAD IN FEET

PARKING: 𝐴𝐴𝐴𝐴𝐴𝐴𝐴𝐴𝐴𝐴𝐴𝐴 or calculated

TRUE AREA (SQFT) - - DO NOT MASS POPULATE

SLAB LENGTH (FT) - SLAB_LENG LENGTH OF PCC SLAB

SLAB WIDTH (FT) - SLAB_WIDTH WIDTH OF PCC SLAB

TOTAL SLABS - NO_SLABS TOTAL NUMBER OF SLABS

STREET TYPE

STREET_TYP

ROADWAY, PRKNG_LOT, PRKING_AREA, BOAT

RAMP, HELIPAD, AIRFIELD

LANES LANES LANES_PAVE 1 OR 2

GRADE - - Not Used

COMMENTS - BR_COMM COMMENTS

CATEGORY OPER_MAINT_LEVEL OPER_MAINT OPML-1, OPML-2, OPML-3, OPML-4, OPML-5

(NA if blank)

TABLE 3. Paved_Parking Adjacent to Road Centerline, Multi-part Polygons, and Boat Ramps

Field Name Field Type Description/Domain

NET_ID Text 10 Network ID, use data from adjacent road.

NET_NAME Text 25 Network Name, use data from adjacent road.

RTE_CN Text 25 Route Control Number, use data from adjacent road.

PFSR_CLASS Text 25 Primary Forest Service Road Classification, use data from adjacent road.

BR_ID Text 25 Branch ID field, use data from adjacent road. If a feature is not associated with a FS road, use local road information.

BR_NAME Text 25 Branch Name, use data from adjacent road. If a feature is not associated with a FS road, use local road information.

BR_USE Text 10 Branch Use, use data from adjacent road. If a feature is not associated with a road, Use “PRKNG_LOT”.

BR_COMM Text 25 Branch comments, if there are any.

Section ID. To be generated by contractor. This field will vary by associated road but will follow the following examples. Additional information on parking lots is attached.

PARKING LOTS

PL-01, PL-02, PL-03…

PARKING AREAS (in rec Sites for multipart polygons, copy BMP/EMP from road) PA-01

BOAT RAMP

BR-01, BR-02, BR-03…

Number designations will be based on the entire road length. For example, if a road has two separate parking lots adjacent to it at mile post 0.5 and 5.2, the first will have a SEC_ID of PL- 01 and the second will have a SEC_ID of PL-02. For parking lots that mirror each other across a road segment, create a multi-part polygon and use PL (because it is not a small or individual parking area).

Beginning milepost of feature. These are features along the road, determine the BMP to the nearest 0.001 mile post. If a multi-part polygon then measure distance from beginning of adjacent road to first feature. To be reported with (3) significant figures. If STREET_TYPE = PRKNG_AREA then take from ROAD_CORE BMP

SEC_TO Text 10 End milepost of feature, not required. Leave blank or if available report with (3) significant figures. If STREET_TYPE = PRKNG_AREA then take from

ROAD_CORE EMP

Type

Description/Domain (TABLE 3 Continued)

PRKNG_NAME

Parking Lot Name: This will be a provided name or could be edited to visitor center parking, trailhead name, etc, or left blank. The provided name will come from the Road Parking Feature Database, otherwise enter in “NA”. If the parking lot is not adjacent to a road (i.e. trailhead, or is along non-USFS road) use the Rec Sites Database to find the name.

PRKNG_LOC

Location of parking along road, direction is based on ascending mile posts or stationing, use RIGHT, LEFT, BOTH, populate when drawing, otherwise leave blank. If a parking lot is not associated with a FS Road, for example, alongside a state road, provide the Lat/Long of Parking Lot, (6) significant figures.

PRKNG_STND Text 25 Number of Standard Parking Spaces, if none provided leave blank.

Adopted from NO_PKG_SPACES attribute of the Road Parking Feature Database where available.

PRKNG_ACC Text 25 Number of Accessible Parking Spaces, if none provided leave blank.

Adopted from ACCESIBLE_PKG_INC attribute of the Road Parking Feature Database where available.

PRKNG_RV Text 25 Number of Bus, Trailer, or RV Parking Spaces, if none provided leave blank.

FEATURE_CN

Feature unique Control Number, use supplied geodatabase/excel sheet to match, if none provided leave blank. Adopted from FLMA_ASSET_IDENT attribute of the Road Parking Feature Database where available.

FEATURE_ID Text 25 BR_ID followed by BMP, include a dash, example “B702-0.043”. Scenarios where RTE_CN is NULL, the FEATURE_ID value looks like: “NA-0.043”

SEC_SURFAC

Typically the same as the adjacent road, can be different if provided or observed in aerials. Populate with “AC”, “ST”, “PCC”. AC=Asphalt or Paved, ST= Bituminous Surface Treatment, or PCC=Portland Cement Concrete.

SEC_RANK Text 25 Section ranking. Use the same ranking as adjacent road.

SEC_CONSTR Text 10 Date (if known) of road feature construction. This will be provided by USFS and, if not known, a default date of 1/1/1900 will be used.

SEC_LENGTH

For all parking areas use the square root of the calculated total area to determine SEC_LENGTH. For multipart polygons, use the square root of total area in feet (1 decimal significant figures) for all parts combined.

For boat ramps, measure the length, extend 3 times the length (unless water is low and the entire length is visible) into the water and estimate in feet to the nearest whole even number. Capture only the white area and do not include the shoulder. To be reported with (1) significant figures, unless BOAT_RAMP which has (0) significant figures.

Type

Description/Domain (TABLE 3 Continued)

SEC_WIDTH

For all parking areas use the square root of the calculated total area to determine SEC_WIDTH. For multipart polygons, use the square root of total area in feet (1 decimal significant figures) for all parts combined.

For boat ramps, measure the width and estimate in feet to the nearest whole EVEN number. For Boat Ramps, capture only the white area and do not include the shoulder. To be reported with (1) significant figures, unless BOAT_RAMP which has (0) significant figures.

OPER_MAINT Text 10 Operational Maintenance Level, use data from adjacent road. OPML-1, OPML-2, OPML-3, OPML-4, OPML-5. If there is no adjacent FS road or value then enter “NA”.

STREET_TYPE

Street type. Will vary by type of feature. Domain: PRKNG_LOT, BOAT RAMP, PRKNG_AREA, or AIRFIELD. Parking Areas are associated with recreation sites and are grouped as multipart polygons.

LANES_PAVE

Number of lanes. For parking lots, this will be blank, for boat ramp this is the number of lanes of ramp. Only for “STREET_TYPE = BOAT RAMP '' manually measure the length/width of the boat ramp to the nearest whole foot. 18ft wide or less = 1 lane.

WATER_NAME Text 25 Water Name, may use dam, reservoir, lake or river name. Use ONLY for boat ramps.

SLAB_LENGT Double Slab Length. This field will only be filled out for polygons with a SEC_SURFAC of PCC. For such polygon features the value will be 10. For all other features this field will be left blank.

SLAB_WIDTH Double Slab Length. This field will only be filled out for polygons with a SEC_SURFAC of PCC. For such polygon features the value will be 10. For all other features this field will be left blank.

AREA_SQFT Double For Paved_Road_Polygons: Right click field name and use Calculate Geometry to derive area values in square feet. To be reported with (0) significant figures.

Example 1 Road to Parking Lot, road is <0.10 mi long.

Lot Type 1a. Road & Parking, short access road(s) <0.10 mi into parking lot or may not have any entrance road with an existing Forest Service road centerline. Typical configurations:

Lot Type 1b. Parking lot, short access road(s) <0.10 mi into parking lot or may not have any entrance road without an existing Forest Service road centerline. Typical configurations:

Feature Class: Other_Paved_Areas

Actions:

● Lot Type 1a. If parking lot has an existing centerline, leave it, do not redraw it.

○ This is inventoried as a road and parking lot. The centerline road data in the parking lot provides the Branch ID and Branch Name, and is recorded as Section 10.

○ Fields to populate from road centerline data in parking lot: Route CN, Branch ID, BMP is “FROM”, EMP is “TO”.

○ GIS map service for National Forest System roads showing centerlines can be found at

USDA Forest Service FSGeodata Clearinghouse - Download National Datasets.

○ If there is an existing inventoried parking lot for this site, populate Feature_CN that from the provided existing Forest Service features.

● Lot Type 1b. If parking lot has NO existing centerline, do not draw a new one.

○ This is a parking lot feature of the adjacent road. This is a Parking Lot Section of an adjacent Road (Branch). The Section ID will be PL-01.

○ Use Road data from adjacent Forest Service road such as Route CN, Branch ID, Branch Name, “FROM” is the milepost where the parking lot begins and measured along the adjacent road, “TO” is left blank.

○ Create a Feature_ID

○ If there is an existing inventoried parking lot for this site, populate Feature_CN that from the provided existing Forest Service features.

https://data.fs.usda.gov/geodata/edw/datasets.php

● Do not draw in parking lots that are widened areas for turning.

GIS Special Notes

● Create a single Other_Paved_Areas polygon that covers both the entrance road and parking area, and there are no section breaks between the polygons.

Example 2 Road to Parking Lot, road is >0.10 mi long.

Feature Class: Paved_Road_Lines

Action:

● If there is not an existing road line, draw a new one

○ Branch ID would be Forest 3 letters than sequential number. For Example CIB-01 for the first new road line on the Cibola National Forest. Branch Name is CIB-01

● Sectioning, Street Type

○ Create a new road segment for the entrance road where SEC_ID = 10 and STREET_TYPE = ROADWAY; add this to the Paved_Road_Lines feature class

○ Section ID, use Sectioning rules, for first mile of road to parking lot use

10. The parking lot would be the last Section ID number.

○ Street Type for Road is is Roadway, for Parking its PRKING_LOT

● Create a polygon for the entrance road that is the approximate width of the road. SEC_ID = 10 and STREET_TYPE = ROADWAY.

● A separate Paved_Road_Polygon will be created for the parking lot area, example is a SEC_ID =

20, if the entrance road is 2.0 miles, the parking lot would be SEC_ID=30, etc.

● If there is an existing inventoried parking lot for this site, populate Feature_CN that from the provided existing Forest Service features

● In the example, the “FROM” mile post of Section 20 is where section break occurs, the “TO” would be from the centerline data and shown as the EMP of the road.

Example 3. Parking Where Road Continues Through

The scenario of when to use a multi-part polygon for a parking lot split by a road. Parking lots can be a mirror or offset.

Example 4. Parking Areas, Multi-part Polygons at Recreation Sites.

Where PRKNG_AREAS are built as multi-part polygons as opposed to represented as individual parking spots such as spurs (single, doubles), pull-throughs, etc.

Scenario:

• A campground or recreation area has many small parking areas that area paved .

Action:

● Create a multipart polygon (single feature) for all of the parking spaces along same road (Branch

ID)

● STREET_TYPE = PRKNG_AREA

● SEC_FROM = BMP from adjacent ROAD_CORE segment (centerline data)

● SEC_TO = EMP from adjacent ROAD_CORE segment (centerline data)

Example 5. Boat Ramp Example

● SECTION ID = BR-01

● STREET_TYPE = BOAT RAMP

Additional PAVER and Field Data Collection Direction This additional direction is provided to make sure that during field work, these fields get verified and edited.

Road PAVER Fields The following standard PAVER fields are to be verified during the condition survey and edit as necessary:

- SAMPLE ID- is the mile post location of beginning of sample to nearest 0.001

- LENGTH– verify or record the true length in feet of the road section

- WIDTH - verify or record the average width of the section

- AREA – verify True Area calc is correct, average width x length

- SEC_FROM SEC_TO – In general, this should not be edited in the field, unless new Sections are being created.

- WORK HISTORY- Record the surface type, asphalt thickness, and surface seals

- STREET TYPE: ROADWAY

- SECTION COMMENT- Record the recommend M&R in the Section 10 (first section) comment field for each Branch

Parking Lot GIS, PAVER, & Field Data Collection Direction Conduct manual surveys of parking lots at field determined representative sample locations. Take picture of survey location and collect the GPS location.

PARKING LOT PAVER FIELDS

The following standard PAVER fields are to be verified during the condition survey and edit as necessary:

- SEC_ID = Section ID: 10, 20, 30 (parking with centerlines) or PL-01, PL-02 or PA-01, BR-01, etc

- SEC_FROM SEC_TO = For Parking Lots that have no road centerline, the From is the mile post

(nearest 0.001) where the parking lot begins along the road, the To is optional. For Parking Areas along roads you should not have to edit, From and To are Beginning Mile Post (BMP) and Ending Mile Post (EMP) taken from the centerline road data.

- SEC_SURFACE = Surface Type: AC, ST, or PCC

- SEC_LENGTH SEC_WIDTH = Section Length, Width: Width and Length in feet, for irregular shapes & islands use square root for length and width that will provide correct area of the polygon. For multipart polygons within recreation sites with parking areas including spurs, pull throughs, restroom parking, etc the total area is used and length and width is populated using square root function.

- AREA – verify True Area calc appears correct

- STREET TYPE: PRKING_LOT

- INSPECTION COMMENT FIELD: Record size and describe location of sample in parking lot

PAKRING LOT USER DEFINED FOREST SERVICE PAVER FIELDS

For parking lots along FLTP Subset roads:

- PRK_NAME = Parking Lot Name: This will be a provided name or could be edited to visitor center parking, trailhead name, etc, or left blank.

- PRK_LOC = Location: create list in PAVER for Right, Left, or Both

- Number of Parking Spaces:

o PRKNG_STND = Standard:

o PRKNG_ACC = Accessible:

o PRKNG_RV = Bus/RV/Trailer:

PARKING AREA FOREST SERVICE PAVER FIELDS

For parking lots in recreation area, parking lots that are apart of multipart polygons:

o PARKING_RV = For multipart polygons in campgrounds (spurs, pull throughs, restroom parking, etc) for example, this would be populated with the count number of parking areas o STREET_TYPE = PRKNG_AREA

BOAT RAMPS

Below are unique additional fields and direction for boat ramps. Only inventory and rate PCC boat ramps, including precast PCC.

- Section ID= BR-01, BR-02, etc

- SEC_SURFACE= PCC

- LANES= make sure to edit number of lanes of the Boat Ramp, assume 10ft per lane

- WATER_NAME= may use dam or reservoir name

- Rank= L

- STREET_TYPE= Boat Ramp

- SEC_LENGTH SEC_WIDTH = Section Length, Width: estimate width and length to whole number

- SECTION COMMENT= record if PCC precast, any special maintenance issues (slab voids, missing rip rap, etc)