AG-3604-S-12-0039 Solicitation Package.pdf

SOL. NO: AG-3604-S-12-0039

PROJECT: Airborne LiDAR/WASP Prescribed Fire Infrared Mapping

TABLE OF CONTENTS

PAGES

SECTION DESCRIPTION

PART I - THE SCHEDULE

A SF-33, Solicitation, Offer and Award/Table of Contents 1-2

B Schedule of Items 3-4

C Description/Specifications/SOW 5-18

D Packaging and Marking 19

E Inspection and Acceptance 20-21

F Deliveries or Performance 22-23

G Contract Administration Data 24-25

H Special Contract Requirements 26-29

PART II - CONTRACT CLAUSES

I Contract Clauses 30-43

PART III - LIST OF DOCUMENTS, EXHIBITS, & OTHER ATTACHMENTS

J List of Drawings and Attachments 44

Attachment A, SAM & Banking Information 74 Attachment B, Experience Questionnaire 75-76

Attachment C, SCA Wage Determination No. 95-0222 77-79 Attachment D, Sample Proper Invoice 80-81

PART IV - REPRESENTATIONS AND INSTRUCTIONS

K Representations, Certifications, and Other 45-68 Statement of Offerors L Instructions, Conditions, & Notices to Offerors 69-71 M Basis for Award 72-74

PART I—THE SCHEDULE

SECTION B--SUPPLIES OR SERVICES AND PRICES/COSTS

SCHEDULE OF ITEMS

B.1 DESCRIPTION OF REQUIREMENT

The contractor shall provide all necessary equipment, labor, materials, and supervision necessary to conduct airborne Light Detection and Ranging (LiDAR) and WASP infrared mapping on Eglin Air Force Base (AFB) in Florida per the terms and specifications described in Section C – Description of Work.

The term of this contract will be approximately an eleven (11) month base period, with one (1) one year (12 month) option period, if exercised. The base period of this contract shall commence in approximately November 2012.

B.2 SCHEDULE OF ITEMS

BASE PERIOD (Approximately November 2012 to September 2013)

ITEM DESCRIPTION QUANTITY UNIT PRICE

1001 LiDAR & WASP Mapping 1 Job $____________

OPTION PERIOD 1 (Approximately October 2013 to September 2014)

ITEM DESCRIPTION QUANTITY UNIT PRICE

2001 LiDAR & WASP Mapping 1 Job $_____________

TOTAL = ______________

B.3 OFFERORS PLEASE NOTE:

A. Before preparing your offer, carefully review Sections K, L, and M. All questions must be e-mailed to the Contracting Officer, Maria Evans, at mtevans@fs.fed.us

B. One contract will be awarded in accordance with the evaluation factors in Sections L and M.

C. All prospective offerors are encouraged to inspect the site prior to submitting an offer to assess the condition of the site and the scope of work proposed. Failure to do so does not relieve the offeror from accurately determining the scope of work required. Please contact Matthew Dickinson by telephone at 740-368-0096 or by e-mail at mbdickinson@fs.fed.us mailto:mtevans@fs.fed.us mailto:mbdickinson@fs.fed.us

D. A post award pre-work meeting will be scheduled with the successful offeror/contractor.

This meeting must take place within ten (10) days of contract award.

E. This requirement is a total small business set aside. The NAICS Code for this acquisition is 541360, with a small business size standard of $14.0 Million.

F. Contractors are required to be registered in the System For Award Management (SAM)

[previously Central Contractor Registration (CCR)] per FAR 52.204-7, Central Contractor Registration – See Attachment A.

B.4 PERIOD OF THE CONTRACT

This contract is for approximately an eleven (11) month base period, with one (1) one year (12 month) option period, if exercised. This is a unilateral right of the Government to extend. Each time an option to extend is exercised; it will be for a period of one additional period. Contractor will be notified in accordance with appropriate clause contained in Section I.

B.5 TYPE OF CONTRACT

The Government contemplates award of a Firm-Fixed Price, multiple year contract resulting from this solicitation.

SECTION C - DESCRIPTION/SPECIFICATION/WORK STATEMENT

AIRBORNE LIDAR AND WASP PRESCRIBED FIRE INFRARED MAPPING

PROJECT – EGLIN AIR FORCE BASE, FLORIDA

The Contractor shall provide equipment, labor, and materials necessary to accomplish the following tasks on Eglin Air Force Base (EAFB) in west Florida:

1. Collect high density airborne Light Detection and Ranging (LiDAR) data pre- and post-fire over a collection of units scheduled for burning in November 2012.

2. Collect high density LiDAR on unit 307B adjacent to the burn units (pre- OR post-fire).

3. Map active-fire infrared heat release on all but one of the units in #1 using the WASP instrument

(Wildfire Airborne Sensing Platform) maintained and operated by Rochester Institute of Technology.

4. Collect high density LiDAR of 25 small, non-contiguous experimental plots in longleaf pine savanna located on the western side of EAFB.

Tasks 1-3 are intended to support research activities associated with the Prescribed Fire Combustion Atmospheric Dynamics Research Experiments project (Rx-CADRE). Task 3 is a unit burned during the 2008 Rx-CADRE field campaign and will not be burned in 2012. Task 4 is intended to support the Biodiversity Project (Patterns and Processes: Monitoring and Understanding Plant Diversity in Frequently Burned Longleaf Pine Landscapes).

The primary objectives of the RX-CADRE project are to characterize fire dynamics at burn unit scales (~1 to 1000 ha) and link those fire dynamics with fuels, first-order fire effects, and smoke transport. To date, the 2008 and 2011 field campaign successfully deployed a variety of monitoring methods on five prescribed fires in longleaf pine savanna systems at EAFB and the Jones Ecological Research Center (in southwest Georgia). Monitoring included aerial infrared mapping, aerial LiDAR, ground-based fire behavior monitoring, fire effects monitoring, and atmospheric and plume dynamics.

The Biodiversity Project seeks to test theoretical models of how groundcover plant diversity is maintained in fire-dependent longleaf pine savannas. LiDAR-based characterization of fuels and canopy will be used as part of a larger effort to test those models.

This timing of this work is late October and early November 2012 as dictated by the needs of the Rx- CADRE project. The Rx-CADRE 2012 burn sites are on Range B70 (Figure 1) and include a large area with no trees and fuels dominated by grass and scattered shrub-sized trees and a smaller area that is forested. The Rx-CADRE 2008 unit (307B) is forested. The Biodiversity Project plots (4 ha each with buffer) are scattered across the western side of EAFB (Figure 2).

Data usage for this contract will be broad. For LiDAR, the use will range from the generation of digital elevation models to the mapping of surface vegetation profiles. For the active-fire mapping, the WASP system built, maintained, and operated by the Rochester Institute of Technology (RIT) will be used to generate mosaics of instantaneous and integrated heat release. A WASP camera operator will be provided by RIT for this work and must be in the aircraft during flight operations. The WASP mapping involves close coordination with fire operations and sequential passes and image capture over the fire for up to four hours during burning operations.

In providing bids for this contract, the Contractor shall provide enough information on equipment, materials, and technical specifications (esp. Data Acquisition, Completeness, and Accuracy, see below) so that the bids can be adequately assessed and compared. For Tasks 1, 2, and 4 (LiDAR), the primary deliverable for this contract is the LiDAR all-return point cloud. The contractor must provide their own LiDAR instrument. For infrared mapping, the primary deliverable will be raw WASP data from multiple passes over three actively-burning prescribed fires. Use of the WASP system will require coordination with RIT.

Once bids have been evaluated, it may be necessary to reduce the scope of the work and/or separate the LiDAR and the WASP work through negotiation with potential vendors. Preferred would be a contract that performs both LiDAR and WASP measurements.

The window for Rx-CADRE burns is Friday, 2 November, through Monday, 19 November. Pre-fire LiDAR measurements can be made before the window (but no earlier than mid-October). Based on past successes for Rx-CADRE 2008 and 2011, a likely scenario is burning units B70EL2G, B70EL2F, and B70CL1G on two consecutive weekends (these are the units where WASP data are required), with the small burns planned for unit B70ES being conducted in the intervening week (no WASP required for these small units). Ideally, the first burns would occur on the first weekend of the Rx-CADRE window.

Burn days, however, are largely dependent on weather. Severe fire weather (e.g., drought) and a hurricane impacting EAFB in the weeks leading up to Rx-CADRE would result in re-scheduling of, at least, Tasks 1 & 3, probably to spring 2013. In other words, the Rx-CADRE leads must take unforeseen circumstances into account and reserve the right to re-schedule the campaign and all associated activities in the months and weeks prior to the November burn window.

TECHNICAL SPECIFICATIONS FOR Rx-CADRE LiDAR AND WASP DATA ACQUISITION

(TASKS 1-3, ABOVE)

Rx-CADRE Acquisition Areas

The acquisition area will consist of units located on Range B70 on the western side of Eglin Air Force Base (Figure 1). Table 1 includes details on each unit covered by Tasks 1-3. Shapefiles will be provided on request.

All Rx-CADRE units are contiguous (Figure 1). The ideal scenario would be to burn units B70EL2G and B70EL2F in a single day (morning and afternoon, respectively). If logistics are not suitable, these units would be burned on separate days. Unit B70CL1G will be burned on a separate day.

The LiDAR data will include at least a 200 ft buffer around the units. The WASP data will be captured at a sufficient altitude that the entire width of the unit along the flight path will be contained in each image (WASP has a 45 degree angle of view). The purpose of this requirement is that both pre-fire background and cool-down periods will be captured for the entire burn area.

Figure 1. The Rx-CADRE units (see Table 1). Also shown are five of the 30 plots in Task 4.

Table 1. Rx-CADRE Units, their sizes, the data required from them, and expected flight duration.

Unit Area in hectares Area in acres Data required

Expected WASP flight duration (including round trip from airport)

B70ES 214 529 Task 1 (pre- and post-fire LiDAR) NA

B70EL2G 234 577 Task 1 (pre- and post-fire LiDAR) & Task 2 (WASP) 2 hours

B70EL2F 263 649 Task 1 (pre- and post-fire LiDAR) & Task 2 (WASP) 4 hours

B70CL1G 457 1128 Task 1 (pre- and post-fire LiDAR) & Task 2 (WASP) 2 hours

307B 548 1353 Task 3 (LiDAR)

Rx-CADRE LiDAR Specifications (Tasks 1 and 2)

1. Purpose of Study:

The data products will be primarily used for the generation of LiDAR derived surface vegetation structural metrics both pre- and post-fire (for estimating fuel consumption) and for maps of instantaneous and integrated heat release.

2. Potential acquisition problems:

There is a limited window of time for acquisition and a need for close coordination between the contractor and RIT and the contractor and Eglin AFB flight control. The planned burn is 2-19 November. The pre-fire LiDAR data capture would occur after the 15th of October and before the burn on a particular unit is conducted. Post-fire LiDAR data acquisition would occur up to 2 weeks after the burn on a particular unit has been conducted. It is not possible to fly LiDAR of surface structures while smoke is still in the air because of returns from smoke. Thus, 1-2 days wait after a burn will probably be required before post-fire LiDAR can be flown. Fire management will typically be able to provide at least 3 days notice as weather conducive to prescribed burning develops. Weather is uncertain and the contractor must be prepared for changing conditions and plans.

There is a strong preference for a two-hole aircraft so that the LiDAR and WASP camera system can be installed in the aircraft simultaneously for quick turnaround from a ‘LiDAR mission’ to an ‘Infrared camera mission’. See details on WASP deployment, below.

Figure 1. Rx-CADRE units (see Table 1). Also shown are 10 of the 25 plots in Task 4.

3. Air-space restrictions:

Potential limitations to minimum and maximum altitude over EAFB and access:

• Coordination with a Twin Otter smoke sampling aircraft flying at ~3000 ft AGL and three unmanned aerial vehicles (UAVs) flying below 3000 ft AGL.

• Contractor will coordinate with Eglin flight control to gain access and plan flights.

• Operational conditions dictate when aircraft can enter EAFB airspace and where they can fly. Airspace for LiDAR flights will be reserved by EAFB staff.

4. Pre- and post-fire LiDAR collection

A. Data acquisition & Completeness

LiDAR mapping will be conducted for the large and small burn units (see above). The table below outlines the desired acquisition parameters. The data will be routinely evaluated for completeness.

Data acquisition Survey Design Minimum requirements1

Wavelength 900- 1600 nm discrete return Returns per Pulse > 4 returns per pulse first 3 & then last On-ground diameter ca. 25 cm < 50 cm Scan angle ± 13 degrees ≤ ± 20 degrees Aircraft altitude For vendor to determine Aircraft speed For vendor to determine Ground swath width For vendor to determine Swath overlap 50% sidelap (100% overlap) 30% - 50% sidelap No voids between swaths. No voids because of cloud cover or instrument failure < 10 % no-overlap area for the project. No arbitrary 1km x 1km square with >50% no overlap area

Aggregate pulse density 8 plus pulses m-2 Barring non-reflective areas (e.g. open water, wet asphalt):

- > 90 % design pulse density for project area

Flight line direction Opposing GPS base line length < 50 km GPS PDOP ≤ 3.0, ≥ 6 satellites in view ≤ 3.5, ≥ 6 satellites in view.

Ground Survey Summer 2012 USFS Surveyor

1. Local relief, turbulence, inability to maintain an exact flying height, and aircraft and instrument availability routinely lead to departures from the survey design. Minimum requirements listed here are the minimum acceptable under this contract.

B. Accuracy:

Accuracy Survey Design

Vertical accuracy 30 cm at 95% CI

Horizontal accuracy At least 0.5 at 95% CI

Between swath reproducibility ≤ 15 cm vertical on horizontal surfaces

Ground Control Number of points to be determined

C. Spatial reference framework:

Vertical datum Ellipsoid Height (GRS80)

Horizontal datum NAD83 (2011)

Projection UTM zone 16N

Units meters

D. Deliverables:

Contractor shall provide the Deliverables no later than 120 calendar days after completion of flying.

5. Deliverables: data, reports, processing, and media.

Report of survey Text report that describes survey methods, equipment, accuracy assessments, including internal consistency and absolute accuracy; and metadata. Should include list documenting the deliverable files (.pdf, or .doc format).

Aircraft trajectories Aircraft position (easting northing and direction) and attitude (heading, pitch, roll) and GPS time recorded at regular intervals of 1 second or less.

May include addition attributes (ASCII text or .shp format)

All-return point cloud List of all valid returns. For each return GPS week, GPS second, easting, northing, elevation, intensity, return #, return classification1. May include additional attributes. No duplicate entries. ASCII text and .LAS format.

1/64th USGS 7.5 minute quadrangle (0.9375 minute by 0.9375 minute) tiles.

Ground point cloud2 List of X, Y, Z coordinate of all identified ground points. ASCII text and

.LAS 1/4th USGS 7.5 minute quadrangle (0.375 minute by 0.375 minute)

Ground surface model2 Raster of ground surface, interpolated via triangulated irregular network from identified ground points. No unavoidable point misclassification.

ESRI floating point grid, 1 m cell size, snapped to (0,0). 1/4th USGS 7.5 minute quadrangle (0.375 minute by 0.375 minute) tiles. Surface model should have no tiling artifacts and no gaps between tile boundaries. Areas outside of survey boundary shall be coded as NoDATA. Internal voids may be coded as NoDATA.

Supporting shapefiles A shapefile of the tiling tessellation (polygon feature) and a shapefile with the tracking of the individual flightlines and flightline swaths (line and polygon features). Files shall conform to a consistent naming scheme Files shall have consistent internal formats.

GPS report Report on GPS ground control processing including equipment used and location and duration of occupation of base stations

QA/QC Statistics and reporting including fieldwork.

Deliverable Media USB Hard Drives (3)

2 This contract specifies for the collection and validation of a raw point cloud. Please provide an option for the classification of these raw points into ground and non-ground returns and also the creation of a 1m digital elevation model as specified above.

Active-fire WASP infared data collection (Task 3)

Details on Acquisition area are provided above (e.g., Table 1)

1. Purpose of study and background

WASP imagery is used to provide a time sequence of fire radiative flux density (FRFD) measurements.

FRFD relates to total heat release which affects smoke column development and FRFD relates directly to fire behavior and fire effects. The WASP sensor platform was originally developed under a NASA grant to investigate new airborne sensor technologies for wildfire detection and mapping. The system has been flying since 2003 and has undergone a number of significant upgrades during that time period.

It is now suitable for use as a general purpose multispectral mapping system capable of delivering high resolution color or thermal infrared, georeferenced images in near real-time after the aircraft lands or while in flight using a digital radio link. WASP was flown successfully during Rx-CADRE 2011 and on other research campaigns (e.g., CONSUME project).

2. Potential acquisition problems

Limited window of time for acquisition and a need for close coordination between the contractor and RIT and the contractor and Eglin AFB flight control. The contractor will work closely with fire operations though their RIT point of contact in order to coordinate their work. Within the burn window (2-19 November), fire management will typically be able to provide at least 3 days notice as weather conducive to prescribed burning develops. Weather is uncertain and the contractor must be prepared for changing conditions and plans.

The contractor must also coordinate with RIT to either retrieve the WASP system from Rochester or to accept delivery of the WASP system from RIT. RIT staff will install the camera in the aircraft. There is a strong preference for a two-hole aircraft so that the LiDAR and WASP camera system can be installed in the aircraft simultaneously for quick turnaround from a ‘LiDAR mission’ to an ‘Infrared camera mission’.

3. Air-space restrictions:

Potential limitations to minimum and maximum altitude over EAFB and access:

• Coordination with a Twin Otter smoke sampling aircraft flying at ~3000 ft AGL and three unmanned aerial vehicles (UAVs) flying below 3000 ft AGL.

• Contractor will coordinate with Eglin flight control to gain access and plan flights.

• Operational conditions dictate when aircraft can enter EAFB airspace and where they can fly. Airspace for WASP flights will be reserved by EAFB staff.

4. Technical specifications

System Description

The WASP system can be installed in a 20-21 inch hole. The WASP sensor suite includes 4 cameras mounted to a common framework (Figure 2). Each camera covers a different portion of the electromagnetic spectrum, allowing users to view a scene in any combination of color (or color-infrared), short wave infrared, midwave infrared, and long wave infrared (Table 2). The cameras provide high spatial resolution, able to resolve objects as small as 4" in color (color-infrared) or 24" in the infrared. Temperature sensitivity in the thermal infrared (mid wave and long wave) is about 0.05 K. The nominal field of view for each camera is about 35 deg providing a ground swath of about 2,000' at an altitude of 3,000' AGL. Installation of an optional pointing gimbal assembly allows the WASP sensor to capture a swath four miles wide at an altitude of 10,000' AGL.

Table 2. WASP Camera Specifications

Color (RGB or

CIR)

Shortwave Midwave Longwave

Imager array size 4000 x 4000 640 x 512 640 x 512 640 x 512 Pixel size (microns) 9 25 25 25 Focal length (mm) 55 25 25 25 FOV (deg) 37.5 37 37 37 GSD at 2,000' AGL 4" (0.1m) 24" (0.6m) 24"(0.6m) 24"(0.6m) Wavelength range 400 - 900 nm 1100 - 1700 nm 3000 - 5000 nm 8000 - 9200 nm Temperature Sensitivity 0.05K 0.05K 0.05K

Figure 2. WASP Sensor Suite of 4 Cameras

Mapping Capability

WASP can deliver high mapping accuracy without ground control using a precision inertial navigation system (INS), a POS/AV 310 from Applanix. The INS combined with precision calibration of each camera allows the WASP system to provide geolocation accuracy errors without ground control of < 1 m when using differential GPS. RIT has also developed a streamlined automated data processing workflow that produces ortho-photos in real-time onboard the aircraft.

Thermal Mapping Capability

WASP employs a unique in-flight thermal calibration capability that allows the thermal infrared cameras (midwave and long wave) to measure scene temperature directly from the imagery within the limits of knowledge about target emissivity and atmospheric effects.

Limitations and Constraints

Environmental: While the WASP system has demonstrated robustness over a wide range of environmental conditions, the system should not be operated in precipitation or conditions with high levels of airborne contaminants (heavy dust or smoke).

Altitude/Speed: To avoid gaps in coverage, there is an altitude-dependent maximum ground speed that is a result of the relatively slow frame rate of the high resolution color camera. The maximum frame rate for the currently installed camera is about 1 frame every 4 seconds. This results in a minimum altitude of 2,000' AGL when operating at a ground speed of 110 kts. Higher ground speeds would require a higher operating altitude or lower altitude would require lower ground speed.

Weight: The WASP system as configured (cameras, INS, electronics) weighs about 250 lbs.

Power Requirements: The WASP system uses aircraft-standard 28VDC. The normal operating current is 10 amperes, however upon start-up of the internal calibrators, up to 25 amperes may be drawn from the supply.

Data acquisition & Completeness

The WASP data will be captured at a sufficient altitude that the entire width of the unit along the flight path will be contained in each image (WASP has a 45 degree angle of view). Typical altitudes range from 3,500 to 10,000 ft AGL. RIT will use the raw imagery to generate a mosaic from multiple images for each pass made by the aircraft. The aircraft will make passes as quickly as possible over the fire.

Typical return times have been 3-6 minutes depending on the size of the unit and flight altitude. Return time will be no more than 10 minutes. The pilot will be in communication with the RIT ground staff and will be notified when to take off from the nearest airport. The plane will be over the fire as close to the initiation of ignition operations as possible and will continue making passes over the fire for as long as sufficient fuel lasts to make a safe transit to the airport. The pilot will coordinate with the WASP camera operator supplied by RIT to determine altitude, flight lines, and any in-air adjustments.

Accuracy

The flight lines and flight altitude must be maintained so that the entire burn unit (or some pre-determined portion of a large burn unit) will be covered on each pass. Spatial gaps in the dataset result in poor estimates of integrated heat release.

Spatial reference framework:

Spatial reference information for the WASP system is supplied internally by an Applanix IMU. The contractor has no requirements in this regard.

Deliverables

In close coordination with RIT staff and others, the contractor will fly two prescribed fires as part of the RX-CADRE project at EAFB (see above). Data acquisition during flights will be the responsibility of RIT. The WASP system will be delivered to either RIT or to an airport from which RIT staff can conveniently transport the system.

TECHNICAL SPECIFICATIONS FOR LiDAR ACQUISITION FOR THE BIODIVERISTY

PROJECT (TASK 4)

1. Acquisition area and timing:

The acquisition area totals ~120 ha composed of 25 square (4-ha) blocks centered over 25 hexagonal (1-

ha) monitoring plots. The 4-ha blocks include the 60 m buffer area. The plots are located on the western side of EAFB. The total size of EAFB is ~500,000 acres. Figure 3 shows the locations of the plots.

Shapefiles including locations of these units will be provided on request.

There are no time restrictions on LiDAR acquisition for the Biodiversity Project except those imposed by the end of the performance period for the contract. However, it is expected that the collection would be done coincident with the Rx-CADRE LiDAR data collection (roughly mid-October to the end of November 2012.

2. Purpose of study:

The data products will be mainly used for the generation of LiDAR-derived canopy and surface vegetation structural metrics.

3. Potential acquisition problems:

None anticipated except for those related to air-space restrictions (see below).

4. Air-space restrictions:

Contractor will coordinate with Eglin flight control to gain access and plan flights. Operational conditions dictate when aircraft can enter EAFB airspace and where they can fly. Airspace for LiDAR flights will be reserved by EAFB staff.

5. LiDAR collection

Specifications will be identical to those outlined for the Rx-CADRE LiDAR collection (Tasks 1 and 2, above) with the exception that, instead of requiring overlap, the lidar may be collected in a single pass near nadir (< +5 scan angle); if this makes 8 pulses m-2 unrealistic, then a relaxed point density of 6 plus pulses m-2 may be used to reduce flight time (and cost).

Figure 3. Location of the 25 plots for which LiDAR data are required (Task 4) as part of the Biodiversity Project.

SECTION D--PACKAGING AND MARKING

{For this Solicitation, there are NO clauses in this Section}

SECTION E--INSPECTION AND ACCEPTANCE

E.1 FAR 52.246-4 Inspection of Services - Fixed-Price. (AUG 1996)

(a) Definition: "Services," as used in this clause, includes services performed, workmanship, and material furnished or utilized in the performance of services.

(b) The Contractor shall provide and maintain an inspection system acceptable to the Government covering the services under this contract. Complete records of all inspection work performed by the Contractor shall be maintained and made available to the Government during contract performance and for as long afterwards as the contract requires.

(c) The Government has the right to inspect and test all services called for by the contract, to the extent practicable at all times and places during the term of the contract. The Government shall perform inspections and tests in a manner that will not unduly delay the work.

(d) If the Government performs inspections or tests on the premises of the Contractor or a subcontractor, the Contractor shall furnish, and shall require subcontractors to furnish, at no increase in contract price, all reasonable facilities and assistance for the safe and convenient performance of these duties.

(e) If any of the services do not conform with contract requirements, the Government may require the Contractor to perform the services again in conformity with contract requirements, at no increase in contract amount. When the defects in services cannot be corrected by reperformance, the Government may -

(1) Require the Contractor to take necessary action to ensure that future performance conforms to contract requirements; and

(2) Reduce the contract price to reflect the reduced value of the services performed.

(f) If the Contractor fails to promptly perform the services again or to take the necessary action to ensure future performance in conformity with contract requirements, the Government may -

(1) By contract or otherwise, perform the services and charge to the Contractor any cost incurred by the Government that is directly related to the performance of such service; or

(2) Terminate the contract for default.

(End of clause)

E.2 452.246-70 INSPECTION AND ACCEPTANCE (FEB 1988)

(a) The Contracting Officer or the Contracting Officer's duly authorized representative will inspect and accept the supplies and/or services to be provided under this contract.

(b) Inspection and acceptance will be performed randomly by the USDA Forest Service.

SECTION F--DELIVERIES OR PERFORMANCE

F.1 FAR 52.252-2 Clauses Incorporated by Reference (FEB 1998)

This contract incorporates one or more clauses by reference, with the same force and effect as if they were given in full text. Upon request, the Contracting Officer will make their full text available. Also, the full text of a clause may be accessed electronically at this/these addresses:

www.arnet.gov/far/ www.usda.gov/procurement/policy/agar.html

FEDERAL ACQUISITION REGULATION (48 CFR CHAPTER 1) CLAUSES

52.242-15 Stop Work Order (AUG 1989) 52.242-17 Government Delay of Work (APR 1984)

F. 2 AGAR 452.211-74 Period of Performance (FEB 1988)

The period of performance of this contract is from approximately November 2012 to September 2014.

(End of Clause)

F.3 DELIVERABLES

In close coordination with RIT staff and others, the contractor will fly two prescribed fires as part of the RX-CADRE project at EAFB. Data acquisition during flights will be the responsibility of RIT. The WASP system will be delivered to either RIT or to an airport from which RIT staff can conveniently transport the system.

Contractor shall provide the Deliverables no later than 120 calendar days after completion of flying.

Deliverables: data, reports, processing, and media.

Report of survey Text report that describes survey methods, equipment, accuracy assessments, including internal consistency and absolute accuracy; and metadata. Should include list documenting the deliverable files (.pdf, or .doc format).

Aircraft trajectories Aircraft position (easting northing and direction) and attitude (heading, pitch, roll) and GPS time recorded at regular intervals of 1 second or less.

May include addition attributes (ASCII text or .shp format)

All-return point cloud List of all valid returns. For each return GPS week, GPS second, easting, northing, elevation, intensity, return #, return classification1. May include additional attributes. No duplicate entries. ASCII text and .LAS format.

1/64th USGS 7.5 minute quadrangle (0.9375 minute by 0.9375 minute) tiles.

http://www.arnet.gov/far/ http://www.usda.gov/procurement/policy/agar.html

Ground point cloud2 List of X, Y, Z coordinate of all identified ground points. ASCII text and

.LAS 1/4th USGS 7.5 minute quadrangle (0.375 minute by 0.375 minute)

Ground surface model2 Raster of ground surface, interpolated via triangulated irregular network from identified ground points. No unavoidable point misclassification.

ESRI floating point grid, 1 m cell size, snapped to (0,0). 1/4th USGS 7.5 minute quadrangle (0.375 minute by 0.375 minute) tiles. Surface model should have no tiling artifacts and no gaps between tile boundaries. Areas outside of survey boundary shall be coded as NoDATA. Internal voids may be coded as NoDATA.

Supporting shapefiles A shapefile of the tiling tessellation (polygon feature) and a shapefile with the tracking of the individual flightlines and flightline swaths (line and polygon features). Files shall conform to a consistent naming scheme Files shall have consistent internal formats.

GPS report Report on GPS ground control processing including equipment used and location and duration of occupation of base stations

QA/QC Statistics and reporting including fieldwork.

Deliverable Media USB Hard Drives (3)

2 This contract specifies for the collection and validation of a raw point cloud. Please provide an option for the classification of these raw points into ground and non-ground returns and also the creation of a 1m digital elevation model as specified above.

SECTION G--CONTRACT ADMINISTRATION DATA

G. 1 AGAR 452.215-73 Post Award Conference (NOV 1996)

A post award conference with the successful offeror is required. It must be scheduled within ten (10) days after the date of contract award. Point of contact is Matthew Dickinson at 740-368-0096; or mbdickinson@fs.fed.us

G. 2 DESIGNATION OF CONTRACTING OFFICER'S REPRESENTATIVE

The Contracting Officer designates the Contracting Officer's Representative (COR). The COR is responsible for administering the performance of work under this contract. In no event, however, will any understanding, agreement, modification, change order, or other matter deviating from the terms of this contract be effective or binding upon the Government unless formalized by proper contractual documents executed by the Contracting Officer prior to completion of the contract.

The Contracting Officer should be informed, as soon as possible, of any actions or inactions by the Contractor or the Government which will change the required delivery or completion times stated in the contract, and the contract will be modified accordingly. (This does not apply to individual task assignments which were issued by the COR, provided they do not affect the delivery schedule or performance period stated in the contract.)

On all matters that pertain to the contract terms, the Contractor must communicate with the Contracting Officer. Whenever, in the opinion of the Contractor, the COR requests effort outside the scope of the contract, the Contractor should so advise the COR. If the COR persists & there still exists a disagreement as to proper contractual coverage, the Contracting Officer should be notified immediately, preferably in writing if time permits. Proceeding with work without proper contractual coverage could result in nonpayment or necessitate submittal of a contract claim.

G. 3 PROJECT MANAGER

The offeror is requested to designate a Project Manager to be contacted for prompt contract administration: (Name) _________________________________________

Telephone Number (including cell phone if available): _________________________________

The contractor shall provide a Project Manager who shall have the authority to make any no-cost contract technical, hiring and dismissal decisions, or special arrangements regarding this contract. This individual shall be responsible for the overall management and coordination of this contract and shall act as the central point of contact with the Government. The Project Manager, or a designated representative, shall have full authority to act for the Contractor in the performance of the required services. The Project Manager, or a designated representative, shall meet with the Contracting Officer’s Representative (COR) to discuss problem areas as they occur. The Project Manager or his/her representative shall respond within four hours after notification of the existence of a problem. The Project Manager shall be able to fluently read, write, and speak the English language.

G. 4 INVOICE REQUIREMENTS

Monthly payments, in arrears, will be issued. The COR will inspect and accept work. Contractor is to keep a record of dates worked with total hours, and location of work. These records must be submitted with the monthly invoice. Please indicate if no work was required in a particular month. Please forward an original proper invoice to the Contracting Officer's attention at the below address in Paragraph G.6.

The following is guidance for submitting a proper invoice for payment. A Sample Proper Invoice is also attached.

G.5 GUIDANCE FOR SUBMITTING A PROPER INVOICE FOR PAYMENT

In accordance with Prompt Payment Act (Public Law 97-177), contractors are to submit proper invoices for payment. The invoice must contain specific information as listed below or the invoice shall be returned to the contractor within seven days after receipt, noting reasons why it is not a proper invoice.

The agency payment office will no longer “hold” or “pen and ink” the invoice in an attempt to correct it.

The contractor must correct and resubmit the invoice to the payment office where it will again be date stamped upon receipt.

A proper invoice includes:

• Name and address of the Contractor

• Invoice date and invoice number

• Contract/order number

• Taxpayer Identification Number (TIN)

• Description, quantity, unit of measure, unit price, and extended price

• Shipping and payment terms (unless mutually agreed that this information is only required in the contract)

• Name (where practicable), title, phone number, and mailing address of person to notify in the event of a defective invoice.

G.6 SUBMIT INVOICE BY MAIL TO:

1.) USDA Forest Service – Northern Research Station ATTN: Apryl Pierce 11 Campus Blvd, Suite 200 Newtown Square, PA 19073 BY E-MAIL TO: apierce@fs.fed.us BY FAX TO: 610-557-4224

2.) USDA Forest Service – Northern Research Station ATTN: Matthew Dickinson 359 Main Road Delaware, OH 43015 BY E-MAIL TO: mbdickinson@fs.fed.us BY FAX TO: 740-368-0152

Once a proper invoice has been received and approved, payment will be processed in accordance with the Prompt Payment Act and contract terms.

mailto:apierce@fs.fed.us

SECTION H--SPECIAL CONTRACT REQUIREMENTS

CLAUSE INCORPORATED BY FULL TEXT

H.1 452.224-70 CONFIDENTIALITY OF INFORMATION (FEB 1988)

(a) Confidential information, as used in this clause, means --

(1) information or data of a personal nature, proprietary about an individual, or (2) information or data submitted by or pertaining to an organization.

(b) In addition to the types of confidential information described in (a)(1) and (2) above, information which might require special consideration with regard to the timing of its disclosure may derive from studies or research, during which public disclosure of primarily invalidated findings could create an erroneous conclusion which might threaten public health or safety if acted upon.

(c) The Contracting Officer and the Contractor may, by mutual consent, identify elsewhere in this contract specific information and/or categories of information which the Government will furnish to the Contractor or that the Contractor is expected to generate which is confidential. Similarly, the contracting Officer and the Contractor may, by mutual consent, identify such confidential information from time to time during the performance of the contract. Failure to agree will be settled pursuant to the "Disputes" clause.

(d) If it is established that information to be utilized under this contract is subject to the Privacy Act, the Contractor will follow the rules and procedures of disclosure set forth in the Privacy Act of 1974, 5 U.S.C. 552a, and implementing regulations and policies, with respect to systems of records determined to be subject to the Privacy Act.

(e) Confidential information, as defined in (a)(1) and (2) above, shall not be disclosed without the prior written consent of the individual, institution or organization.

(f) Written advance notice of at least 45 days will be provided to the Contracting Officer of the Contractor's intent to release findings of studies or research, which have the possibility of adverse effects on the public or the Federal agency, as described in (b) above. If the Contracting Officer does not pose any objections in writing within the 45 day period, the contractor may proceed with disclosure.

Disagreements not resolved by the Contractor and Contracting Officer will be settled pursuant to the "Disputes" clause.

(g) Whenever the Contractor is uncertain with regard to the proper handling of material under the contract, or if the material in question is subject to the Privacy Act or is confidential information subject to the provisions of this clause, the Contractor shall obtain a written determination from the Contracting Officer prior to any release, disclosure, dissemination, or publication.

(h) The provisions of paragraph (e) of this clause shall not apply when the information is subject to conflicting or overlapping provisions in other Federal, State or local laws.

H.2 AGAR 452.228-71 INSURANCE COVERAGE (NOV 1996)

Pursuant to FAR clause 52.228-5, Insurance-Work on a Government Installation, the Contractor will be required to present evidence to show, as a minimum, the amounts of insurance coverage indicated below:

(a) Workers Compensation and Employer's Liability. The Contractor is required to comply with applicable Federal and State workers' compensation and occupational disease statutes. If occupational diseases are not compensable under those statutes, they shall be covered under the employer's liability section of the insurance policy, except when contract operations are so commingled with a Contractor's commercial operations that it would not be practical to require this coverage. Employer's liability coverage of at least $100,000 shall be required, except in States with exclusive or monopolistic funds that do not permit worker's compensation to be written by private carriers.

(b) General Liability. The Contractor shall have bodily injury liability insurance coverage written on a comprehensive form of policy of at least $500,000 per occurrence

(c) Automobile Liability. The Contractor shall have automobile liability insurance written on a comprehensive form of policy. The policy shall provide for bodily injury and property damage liability covering the operation of all automobiles used in connection with performing the contract. Policies covering automobiles operated in the United States shall provide coverage of at least $200,000 per person and 500,000 per occurrence for bodily injury and $20,000 per occurrence for property damage or loss.

(d) Aircraft Public and Passenger Liability. When aircraft are used in connection with performing the contract, the Contractor shall have aircraft public and passenger liability insurance. Coverage shall be at least $200,000 per person and $500,000 per occurrence for bodily injury, other than passenger injury. Coverage for passenger injury shall be at least $200,000 multiplied by the number of seats or passengers, whichever is greater.

(End of Clause)

H.3 AGAR 452.237-74 KEY PERSONNEL (FEB 1988)

(a) The Contractor shall assign to this contract the following key personnel:

- Project Principal

(b) During the first ninety (90) days of performance, the Contractor shall make no substitutions of key personnel unless the substitution is necessitated by illness, death, or termination of employment. The Contractor shall notify the Contracting Officer within 15 calendar days after the occurrence of any of these events and provide the information required by paragraph (c) below. After the initial 90-day period, the Contractor shall submit the information required by paragraph (c) to the Contracting Officer at least 15 days prior to making any permanent substitutions.

(c) The Contractor shall provide a detailed explanation of the circumstances necessitating the proposed substitutions, complete resumes for the proposed substitutes, and any additional information requested by the Contracting Officer. Proposed substitutes should have comparable qualifications to those of the persons being replaced. The Contracting Officer will notify the Contractor within 15 calendar days after receipt of all required information of the decision on substitutions. The contract will be modified to reflect any approved changes of key personnel.

(End of Clause)

H.4 SAFETY

FAR 52.236-13 Accident Prevention (Nov 1991)

a) The Contractor shall provide and maintain work environments and procedures which will --

(1) Safeguard the public and Government personnel, property, materials, supplies, and equipment exposed to Contractor operations and activities;

(2) Avoid interruptions of Government operations and delays in project completion dates; and

(3) Control costs in the performance of this contract.

(b) For these purposes on contracts for construction or dismantling, demolition, or removal of improvements, the Contractor shall --

(1) Provide appropriate safety barricades, signs, and signal lights;

(2) Comply with the standards issued by the Secretary of Labor at 29 CFR Part 1926 and 29 CFR Part 1910; and

(3) Ensure that any additional measures the Contracting Officer determines to be reasonably necessary for the purposes are taken.

(c) If this contract is for construction or dismantling, demolition or removal of improvements with any Department of Defense agency or component, the Contractor shall comply with all pertinent provisions of the latest version of U.S. Army Corps of Engineers Safety and Health Requirements Manual, EM 385-1-1, in effect on the date of the solicitation.

(d) Whenever the Contracting Officer becomes aware of any noncompliance with these requirements or any condition which poses a serious or imminent danger to the health or safety of the public or Government personnel, the Contracting Officer shall notify the Contractor orally, with written confirmation, and request immediate initiation of corrective action. This notice, when delivered to the Contractor or the Contractor’s representative at the work site, shall be deemed sufficient notice of the noncompliance and that corrective action is required. After receiving the notice, the Contractor shall immediately take corrective action. If the Contractor fails or refuses to promptly take corrective action, the Contracting Officer may issue an order stopping all or part of the work until satisfactory corrective action has been taken. The Contractor shall not be entitled to any equitable adjustment of the contract price or extension of the performance schedule on any stop work order issued under this clause.

(e) The Contractor shall insert this clause, including this paragraph (e), with appropriate changes in the designation of the parties, in subcontracts.

Alternate I (Nov 1991). If the contract will involve (a) work of a long duration or hazardous nature, or (b) performance on a Government facility that on the advice of technical representatives involves hazardous materials or operations that might endanger the safety of the public and/or Government personnel or property, add the following paragraph (f) to the basic clause:

(f) Before commencing the work, the Contractor shall --

(1) Submit a written proposed plan for implementing this clause. The plan shall include an analysis of the significant hazards to life, limb, and property inherent in contract work performance and a plan for controlling these hazards; and

(2) Meet with representatives of the Contracting Officer to discuss and develop a mutual understanding relative to administration of the overall safety program.

H.5 SUBMITTAL OF A SAFETY PLAN

Upon notification of intent to award the contract, the contractor shall submit a Safety Plan in accordance with the Occupational Health and Safety Administration (OSHA) regulations to ensure that the working conditions of their employees are not unsanitary, hazardous, or dangerous to their health and safety. The contractor Safety Plan shall also comply with the regulations set forth in 29 CFR 1910; 29 CFR 1926 (Construction) – if applicable; and 29 CFR 1960. A statement of compliance to those regulations shall be included in the Safety Plan. In addition, the following guidelines shall be applied to the Safety Plan:

• Any subcontract entered into pursuant to the contract shall similarly provide a work environment that is sanitary and not hazardous.

• Contractors must initiate and maintain an accident prevention program, which includes frequent and regular inspections of the project site, materials, and equipment.

• Accidents resulting in death, occupational disease, disabling injury, or property damage must be reported to the Contracting Officer.

• Contractors must assess appropriate risk management regarding contractor and contractor employee safety; and public safety. Examples include: experience of equipment and motor vehicle operators to handle road and terrain conditions getting to the worksite and at the worksite; public access conditions and requirements; traffic control needs; and coordination with other forest users and private land owners.

• Contractors shall identify all Personal Protective Equipment (PPE) to be used/that is applicable to their specific contract.

• Contractors shall abide by all state regulations regarding vehicle safety and licensure to operate a motor vehicle.

PLEASE NOTE: Forest Service employees will not inspect or accept the work under conditions where hazards or unsanitary conditions have not been mitigated to the extent required by OSHA.

The following websites may be helpful:

http://www.osha.gov http://www.osha.gov/dcsp/smallbusiness/index.html http://www.osha.gov/ http://www.osha.gov/dcsp/smallbusiness/index.html

PART II--CONTRACT CLAUSES

SECTION I--CONTRACT CLAUSES

FAR 52.252-2 Clauses Incorporated by Reference (FEB 1998)

This contract incorporates one or more clauses by reference, with the same force and effect as if they were given in full text. Upon request, the Contracting Officer will make their full text available. Also, the full text of a clause may be accessed electronically at this/these addresses:

www.arnet.gov/far/ www.usda.gov/procurement/policy/agar.html

52.202-1 Definitions (JAN 2012) 52.203-3 Gratuities (APR 1984) 52.203-5 Covenant Against Contingent Fees (APR 1984) 52.203-6 Restrictions on Subcontractor Sales to the Government (SEP 2006) 52.203-7 Anti-Kickback Procedures (OCT 2010) 52.203-8 Cancellation, Rescission, and Recovery of Funds for Illegal or Improper Activity (JAN 1997) 52.203-10 Price or Fee Adjustment for Illegal or Improper Activity (JAN 1997) 52.203-12 Limitation on Payments to Influence Certain Federal Transactions (OCT 2010) 52.204-4 Printed or Copied Double-Sided on Recycled Paper (MAY 2011) 52.204-9 Personal Identity Verification of Contractor Personnel (JAN 2011) 52.209-10 Prohibition on Contracting With Inverted Domestic Corporations (May 2012) 52.212-4 Contract Terms and Conditions -- Commercial Items (FEB 2012) 52.215-2 Audit and Records – Negotiation (OCT 2010) 52.215-8 Order of Precedence - Uniform…