AG-3604-S-12-0039_Amend_00001_Package.pdf
PDF 171 KB Posted
- Solicitation number
- AG-3604-S-12-0039
About this file
Amendment 000001
View the file
Other files
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
AG-3604-S-12-0039
Amendment 000001
The following questions were received and are hereby answered by this amendment:
Q1: Is there a fee of any kind from RIT for using the WASP system? We understand that RIT will install the system, provide an operator, and process the raw data, but are there other costs for flying the system (other than flight operations) we should be aware of?
A1: Power Requirements:
24VDC to 28VDC (+/- 2VDC) @ 1KW utilizing a Amphenol 22-22s (WASP Side Connector) - vendor must supply a power cable with proper connectors. Must be a true 24V aircraft capable of supplying full power near idle: 12VDC->24VDC up-converters are not acceptable due to their switcher noise and inductive loading of the instrument. All power connections must be pre-tested by RIT personnel utilizing a scope with a running aircraft to verify power quality integrity.
Dimensions:
Electronics case: Nominally 28" Wide, 30" Deep, 36" High - 192 LBS self-contained shock-mount system, requires 4 luggage tie-down points to support strapping in a criss-cross configuration Sensor Head: Nominally 24" Wide, 22" Deep, 20" Tall - 101 LBS. Requires a 20 inch diameter hole no deeper than 9 inches. Vendor must supply an interface plate with a 6 bolt direct-bolt interface.
Maximum distance between sensor head & electronics rack - 4 feet.
Dual Engine aircraft configuration only:
Due to the thermally-sensitive nature of the sensor's sampling bands, Dual engine aircraft will only be considered. Single engine planes with exhaust "turn-outs" are not acceptable as they do not adequately place the engine's exhaust far enough from the field of view of the sensor. Must be capable/comfortable flying in the range 100 - 130 knots ground speed (not indicated).
GPS Antenna:
Dual Frequency L1/L2 with a built in pre-amplifier, gain not to exceed 26dB (unless unusually long GPS cable runs are present in the aircraft); notionally a Novatel GPS-512 or equivalent.
Flight Management:
Vendor must provide flight management system - System/Pilots must be capable of maintaining +/- 50ft flightline over possibly *highly* turbulent air induced from the actively burning fire. Aircraft must be equipped with a standard cabin intercom system to facilitate communication between the pilot and sensor operator.
Minimum fuel capacity:
4 Hours
Integration & Checkout:
Initial integration feasibility checks require that accurate aircraft dimensions be sent to RIT for analysis no later than 10 days prior to scheduled integration. All integration activity must be completed at the KROC airport; inclement weather may require renting hanger space for integration work; minimum integration time - 2 business days, to happen no later than 2 weeks before the first possible collection day. A flight checkout in the local Rochester, NY area will be required, minimum of 2 hours airtime, to verify proper operation and GPS antenna lever-arm calibration. Final integration feasibility and acceptance will be determined by the Senior RIT WASP Design/Integration/Flight engineer.
Integration support:
RIT engineering support for system analysis, system integration, verification testing, and flight planning will be provided at a fully burdened rate of $115 per hour.
Insurance:
There may be a need to complete an insurance certification form.
Q2: Is USFS open to other means of thermal infrared and spectral data collection (i.e. using our sensors rather than the WASP system)?
A2: We would consider other sensors besides WASP. However, we would need enough information about the sensor to make a decision.
Q3: On page 16 of RFP (top) a number of parameters are given for estimating flight time for the WASP acquisition, including that passes should be made as quickly as possible, and that the plane should remain collecting data (multiple passes) for as long as possible during the fire. I am wondering how we are to determine the probable flight time associated with the WASP flights in order to provide a cost quote as these parameters together are rather open ended/not specific. Can you clarify?
A3: Table 1 of the solicitation (page 8) has our estimate active fire (WASP) flight time. The total over three burns is 8 hours including travel time to the local airport.
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)
Section B2 – Schedule of Items, page 3, is hereby amended as follows:
BASE PERIOD (Approximately November 2012 to September 2013)
ITEM DESCRIPTION QUANTITY UNIT PRICE
1001 LiDAR & WASP Mapping 1 Job $____________
1002 LiDAR only 1 Job $ ____________
OPTION PERIOD 1 (Approximately October 2013 to September 2014)
ITEM DESCRIPTION QUANTITY UNIT PRICE
2001 LiDAR & WASP Mapping 1 Job $_____________
2002 LiDAR only 1 Job $ ____________
TOTAL (Items 1001 and 2001) = ______________
TOTAL (Items 1002 and 2002) = ______________
Section C – DESCRIPTION/SPECIFICATONS/WORK STATEMENT, page 6, paragraph 2 is hereby amended to add the following:
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. However, a bid for only the LiDAR portion of the contract would be considered.
File details come from the government source that posted it. Updated .