RFI_INFRARED_SENSOR.pdf

REQUEST FOR INFORMATION for PURCHASE OF ONE INFRARED SENSOR UNIT

Solicitation Number: Special Notice Number: SN‐2017‐02

Agency: United States Department of Agriculture (USDA)

Office: Forest Service

Location: National Interagency Fire Center – Boise, ID

RFI Issue Date: November 10, 2016

RFI Response Date: December 1, 2016

Submittal of information:

The information requested by this RFI shall be provided, in writing (hard‐copy or electronic), by close of business (4:30 p.m. Mountain Time) December 1, 2016 to the following address:

U.S. Forest Service National Interagency Fire Center (NIFC) 3833 South Development Avenue, Owyhee Building 106, Suite 1101‐1 Attn: Mr. Michael McFarlane, SN‐2017‐02 Boise, Idaho 83705‐5354

Or michaelmcfarlane@fs.fed.us

Synopsis: This Request for Information is for Market Research and Planning purposes only.

Classification Code: 5855 Night Vision Equipment, Emitted and Reflected Radiation

NAICS Code: 334511 Search, Detection, Navigation, Guidance, Aeronautical, and Nautical System and Instrument

Manufacturing

Size Standard: 1,250 employees

THE GOVERNMENT DOES NOT INTEND TO AWARD A CONTRACT ON THE BASIS OF THIS RFI OR TO OTHERWISE PAY FOR THE INFORMATION SOLICITED. This RFI does not constitute a solicitation for proposals or the authority to enter into negotiations to award a contract. No funds have been authorized, appropriated, or received for this contemplated effort. This RFI is for planning purposes only and shall not be considered as a request for proposal or as an obligation on the part of the Government to acquire any products or services. No entitlement to payment of direct or indirect costs or charges by the Government will arise as a result of contractor submission of responses to this RFI or the Government’s use of such information. The Government reserves the right to reject, in whole or in part, any contractor’s input resulting from this RFI. Responses to this RFI will not be returned.

Whatever information is provided in response to this RFI may be used to assess tradeoffs and alternatives available for future needs. The information provided may be utilized by the US Forest Service in developing its acquisition strategy and in its Statement of Objective, Statement of Work, and/or Performance Specifications. The information resulting from this RFI may be included or combined with other submissions in one or more options considered in the analysis of alternatives. Any proprietary information that is submitted may be used in establishing requirements of the future system but specific information will be safeguarded as proprietary.

Contracting Office Address:

Owyhee Building – MS 1100 3833 S. Development Ave.

Boise, ID 83705

Primary Point of Contact:

Michael McFarlane, Contracting Officer michaelmcfarlane@fs.fed.us 208‐387‐5695

Technical Point of Contact Zachary Holder zsholder@fs.fed.us

406‐214‐6178

Description: The purpose of this announcement is to obtain market research regarding interested vendors/contractors who are capable of providing and installing a persistent wide‐area Infrared Sensor system into a Government owned and operated King Air 200.

Background:

(a) WO‐FAM has initiated the Aerial Firefighting Use and Efficiency (AFUE) program. Objectives of the program include developing and implementing performance metrics to analyze the use of aerial assets that have the ability to deliver water or wildland fire chemicals to meet incident objectives. The Aviation component of the study captures aerial firefighting aircraft (airtanker, helicopter and water scooper) drops from above using an infrared (IR) sensor(s). Data collection consists of the recording of incident radio communications, documenting and calculating overall fire behavior, targeted repeated observations of aerial drop footprints, drop coverage, and fire behavior before, during, and after interactions with drops.

(b) The primary platform, a government‐owned and operated Beechcraft King Air 200 (N182Z SN BB‐402, 1978) fixed‐wing aircraft, is to be modified and equipped with a sensor system meeting the described requirement to support the AFUE Mission.

(c) Modifications to the aircraft shall facilitate AFUE mission components such the imager and workstation to be installed and removed by agency aviation maintenance personnel allowing the platform to perform other agency missions, such as personnel transport and Air Tactical Group Supervisor (ATGS).

(d) Within this statement of work the term “System” consists of the following elements:

System Installation

System Hardware

Imager

Workstation

Software, User Interface, and Products

Audio Recorder

Weather Sensor

Data Link

(e) All system requirements must be met simultaneously under the described operational condition. For example, a system achieving the Field of View (FOV) requirement by operating at a higher altitude, or increased slant angle which results in a below requirement Ground Sample Distant (GSD) under such conditions are considered unacceptable.

(f) Background

(1) The AFUE program has previously contracted and evaluated several sensor systems in support of

AFUE’s mission requirements to quantitatively measure changes in fire behavior related to aerial firefighting efforts. Through evaluation and operation experience, AFUE’s internal and external

Technical Specialist and Subject Matter Experts have developed detailed requirements to allow the commercial market to design and offer systems to support AFUE.

(2) While many systems exist that can meet a requirement independently of another requirement, few exist which can meet requirements simultaneously as a system. For example, a traditional Full Motion

Video (FMV) camera is capable of achieving the require coverage area by operating at a higher altitude

AGL or viewing the area of interest (AOI) at an oblique angle. However, in doing so, the resolution and

GSD required are no longer within the specified requirements.

(3) A mid‐wave infrared (IR) Wide Area Motion Imagery (WAMI) system is required to meet these business needs. WAMI is also referred to as Wide Area Airborne Surveillance (WAAS), Wide Area

Persistent Surveillance (WAPS), Persistent Wide Area Surveillance (PWAS), Wide Area Surveillance

(WAS), and Large Volume Streaming Data (LVSD).

Figure 1: Right; Simple Illustration of a typical WAMI System Concept of Operations (ConOps). Left; Simple illustration demonstrating the coverage area difference between a FMV and a WAMI sensor under the same operational conditions to produce equivalent GSD

IMAGER REQUIREMENTS:

(a) The sensor system shall possess the following imagery capabilities:

(1) Mid‐Wave Infrared (MWIR) Wide Area Motion Imager which is capable of providing persistent motion imagery (temporal and spatial data) over wildland fire incidents. Imagers shall have multi‐ axis stabilization. Collect 16‐bit images and be suited to identify and characterize: active fire spread, drop footprints, and drop/fire interaction during daytime environmental conditions associated with wildfire activities.

(i) In addition to the required MWIR, Short‐wave infrared (SWIR) is desired. All additional bands shall meet the minimum requirement of the MWIR imager.

(2) When the system is operating at an altitude of 12,500 feet Above Ground Level (AGL) imager shall:

(i) Possess an oblique coverage area greater than one mi2 (2.58 km2, 640 ac.).

Note: Imagers which possess the maximum persistent coverage area available greatly enhance AFUE’s capabilities. As such, systems which produce larger coverage area while meeting all other requirements will be assessed more favorably than those meeting the minimum.

(ii) Provide oblique Ground Spatial Distance (GSD) of 2 meters or less (GSD ≤ 2 meters) at all locations across the persistent area.

Note: The actual GSD of each pixel is not uniform throughout the raw image and varies significantly with terrain height and other factors. Within this document, GSD is assumed to be the value computed using the calibrated camera focal length and camera height above average horizontal terrain. Imagers which possess a smaller GSD over the equal coverage areas will be assessed more favorably.

Figure 2

(3) Infrared detector cooling (if applicable) shall be a closed‐loop, self‐contained system.

(4) Detect 1‐meter diameter spot fire at a temperature of 600 degrees Celsius. See Figure 3 for temperature and nominal wavelength relationship.

Wavelength and Temperature Relationships

Source Temperature (C) Nominal Wavelength

Background 25 10

Fuel Ignition 275 5

Glowing 550 4

Cool Fire 725 3

Hot Fire 1200 2

Source:

http://nirops.fs.fed.us/docs/upload/Infrared_Field_Users_Guide_November_2014.pdf

Figure 3

(5) Imager shall have a collection rate of 1‐5 Hertz. Collection rates slower than 1‐5 Hertz are permitted only when the increased collection rate supports onboard Multiple‐frame Super

Resolution* (SR) compression resulting in 1‐5 hertz mission imagery. SR is a desired feature.

*Multiple‐frame Super Resolution is a technique which uses the sub‐pixel shifts between multiple lower resolution images of the same scene to create an improved resolution image by fusing information from all lower resolution images to create higher resolution images of the scene

IMAGER INSTALLATION:

(a) The Imager shall be mounted to the provided airframe within a belly pod in a manner which maximizes imagery capabilities while minimizing performance impacts to the aircraft. The aircraft shall be capable of maneuvering in both right and left‐hand orbits without degrading data acquisition quality/or availability.

Persistent Orbit

Off‐set Presistent Orbit

Strip Mapping Area of Interest Path (Perimeter)

Area Orbit Off‐set Area

Orbit

Figure 4

(b) The Belly Pod shall be configured for removal and reinstallation by agency aviation maintenance personnel to allow the aircraft to perform other agency missions. The FAA Form 337 must include a provision to allow this reconfiguration as a minor alteration via a logbook entry.

(c) Belly Pod configuration must comply with one of the following:

(1) A primary imager in a multi‐axis stabilized 360‐degree gimbal. Imager shall have an unobstructed continuous pan view from 10 degrees below the lowest horizontal plane of the aircraft (in‐flight), and throughout downward pointing angle(s) to the earth's surface directly (perpendicular/nadir) below the aircraft at level (0) pitch, roll, and yaw. [Imager shall have free, 360‐degree rotation throughout the horizontal plane parallel to the ground in straight and level flight. In the plane perpendicular to this, X X

X imager shall have free rotation from the vertical down position upward to within ten degrees of parallel to the horizontal axis, in either planar direction from vertical. This equates to a total of 160 degrees of freedom in this axis.]

(2) A primary imager in a multi‐axis stabilized 360‐degree gimbal. Imager shall have an unobstructed continuous pan view from 10 degrees below the lowest horizontal plane of the aircraft (in‐flight), and throughout downward pointing angle(s) to the earth's surface directly (perpendicular/nadir) below the aircraft at level (0) pitch, roll, and yaw. Additionally, pod shall accommodate an additional Forest Service imager. Example systems include USFS Phoenix, USFS Firemapper, LiDAR, TMAP, AMS, and WAI.

(3) A primary imager in a Look‐Down‐Gimbal (LDG). LDG Imager shall have an unobstructed view throughout the LDG’s range of motion.

(4) A primary imager in a Look‐Down‐Gimbal (LDG) with a secondary FMV imager in retractable or non‐ retractable multi‐axis stabilized 360‐degree gimbal. LDG Imager shall have an unobstructed view throughout the LDG’s range of motion. FMV Imager shall have an unobstructed continuous pan view from 10 degrees below the lowest horizontal plane of the aircraft (in‐flight), and throughout downward pointing angle(s) to the earth's surface directly (perpendicular/nadir) below the aircraft at level (0) pitch, roll, and yaw.

WORKSTATION REQUIREMENTS:

(a) (a) The AFUE mission workstation(s) configuration shall support 2 Sensor Operators (SO) in the aft of the aircraft and one Flight Manager (FM) in the right front seat of the aircraft. Workstation configuration and capabilities for the AFUE mission are vital to mission success and shall aim to enhance CRM principles:

situational awareness, self‐awareness, leadership, assertiveness, decision making, flexibility, adaptability, event and mission analysis, and communication.

(b) All workstations must have transmit and receive capabilities across all installed radios (2 VHF‐AM, 3

VHF‐FM)

Figure 5 is for reference only. Workstation, equipment, cargo, fuel, personnel, etc. must be accounted for to ensure proper weight and balance and aircraft performance.

(c) Workstation Configuration

(1) Sensor Operator Position

(i) SO positions shall have full control of all system’s operation components, including power, applicable fuses, and user interfaces.

(ii) SO positions shall support the operation of the entire system from either workstation independently, i.e. the system shall be fully functional with one SO position vacant, regardless of which is vacant, or two SOs are collaboratively operating the system through task segregation.

(iii) Each SO position must have a minimum of 1 dedicated monitor (touch screen desired), mouse, and keyboard. The monitor shall be no less than 22 inches diagonally.

(iv) Monitors which support Multi‐Stream Transport to allow “Daisy Chaining” of additional monitor(s) are desired.

(2) Flight Manager (FM) Position

(i) FM position shall not interfere with flight controls or indicator visibility to pilot or the flight manager.

(ii) FM workstation shall be touch screen tablet, 10‐12.5 inch class, which connects to the system’s control interfaces wirelessly (installation of in aircraft Wi‐Fi required by the Data Link

Section paragraph (b)).

(iii) FM shall have full control and access to sensor pointing, moving map, data attribution, and imagery recording.

(iv) FM workstation mount is desired. FM position will not be filled by a qualified pilot. As such, offered mounting solution shall be approved for a non‐pilot operation while not obstructing pilot’s instrument visibility and may not be affixed to flight controls.

(3) Dismounted workstation.

(i) A minimum of two (2) laptop style portable workstations is required. If both aircraft SO positions are operated through docking units, a total of 3 units is required. i.e., two associated with SO positions and one for data analysis when not staffing the aircraft.

(ii) Dismount workstation(s) shall possess the functionality of aircraft’s SO workstations except sensor pointing controls unless the portable system is "dockable" within the aircraft at SO position.

(b) Workstation Installation.

(1) Workstations shall not impede emergency exits or routes to exits.

(2) Workstations shall be connected through bulkhead mounted connectors with the exception of the audio connector. Bulkhead connectors shall have attached dust covers for protection when not in

AFUE configuration.

(3) Workstations shall be designed to support removal and reinstallation by agency aviation maintenance personnel to allow the aircraft to perform other agency missions. The FAA Form 337 must include a provision to allow this reconfiguration as a minor alteration via a logbook entry.

(4) Workstations shall support modular component additions and upgrades.

SOFTWARE AND USER INTERFACE REQUIREMENTS:

(a) All software/User interface and process updates shall be applied to all instances of the system workstation.

(b) The user interface shall provide a continuously visible view of the user selected live motion images at a scale and resolution in which viewer/operator can easily identify drops, fire behavior, and situational targets under variable lighting and environmental conditions associated with the mission. In this context, variable lighting, and environmental conditions at both the observed location and inside the aircraft are considered to be associated with the mission, and the user interface shall accommodate both.

(c) The system must possess the ability for the operator to select/adjust imager detection characteristics, as presets, and image display characteristics to facilitate optimization of the image based on terrain, day/night, smoke/haze, and fire intensity.

(d) The user interface shall provide a continuously visible moving map in which aircraft location and sensor

FOV footprint are displayed and recorded along with sensor metadata over a base map. The base map shall have the ability to be toggled on and off. Required base maps are 1:150k to 1:24k scales, seamless, USGS topographical with transparent background and NAIP imagery for Alaska and the continental United

States (CONUS).

(e) Base maps must be stored on the aircraft’s workstation server.

(f) Base maps and imagery layers shall display in the following order starting with the background: NAIP, Sensor Imagery, and topo.

(g) User interface shall support the importing and viewing of external vector data. Required support formats are Shapefile, KML, and KMZ.

(h) User interface shall support the collection of AFUE specific geospatial vector data and attributes.

(i) All vector products shall possess the corresponding image frame and time‐stamped attributes.

(j) Raster associated with the creation of a vector feature shall be saved in a ESRI raster catalog called

“Vector_Rasters” in order to ensure that corresponding vector and raster object can be readily identified.

(k) The government will provide an ESRI XML, and HTML schema file containing exact feature and attribute specification in which system shall collect precisely.

(l) Aircraft schema is required to have versioning and track changes logs. Figures 6‐9 are representative of the

AFUE data schema for scoping purposes. Exact schema that will be provided at the time of award which vendor must match exactly.

Figure 6: High‐level overview of AFUE Aerial Vector Data Schema

Figure 7: Point features and attributes. Editable attributes are user or aerial system input. Non‐editable attributes are set by system configuration, calculated downstream or external data sources by AFUE personnel.

Attributes Type Within GUI

IncidentNumber Text Editable

ID Text Editable

WxName Text Editable

StartTime Date Editable

Lat Text Non‐Editable

Long_ Text Non‐Editable

Sheltering Domain Editable

FuelType Domain Editable

FuelModel Domain Editable

DataSource Domain Editable

Comments Text Editable

ReviewFlag Domain Editable

GlobalID Text Non‐Editable created_user Text Non‐Editable created_date Date Non‐Editable last_edited_user Text Non‐Editable last_edited_date Date Non‐Editable

Season Domain Non‐Editable

SHAPE Text Non‐Editable

ID_Old Text Non‐Editable

OBJECTID Text Non‐Editable

Attributes Type Within GUI

Name Text Editable

InciNumber Text Editable

JobCode Text Editable

FiscalYear Text Editable

Complex Domain Editable

Jurisdiction Domain Editable

StartDate Date Editable

EstSize Domain Editable

ActPerim Domain Editable

SpreadPotential Domain Editable

ProbSuccess Domain Editable

DispatchLevel Domain Editable

InciContainment Date Editable

InciObjective Text Editable

Comments Text Editable

IrwinID Text Editable

Lat Text Non‐Editable

Long_ Text Non‐Editable

Season Domain Non‐Editable

ID Text Non‐Editable

GlobalID Text Non‐Editable created_user Text Non‐Editable created_date Date Non‐Editable last_edited_user Text Non‐Editable last_edited_date Date Non‐Editable

SHAPE Text Non‐Editable

OBJECTID Text Non‐Editable

Attributes Type Within GUI

IncidentNumber Text Editable

Name Text Editable

ObsTime Date Editable

RefType Domain Editable

Comments Text Editable

GlobalID Text Non‐Editable created_user Text Non‐Editable created_date Text Non‐Editable last_edited_user Date Non‐Editable last_edited_date text Non‐Editable

Season Domain Non‐Editable

SHAPE Text Non‐Editable

OBJECTID Text Non‐Editable

Attributes Type Within GUI

AircraftID Text Editable

AircraftType Domain Editable

FillTime Date Editable

Lat Text Non‐Editable

Long_ Text Non‐Editable

LiqDisp Domain Editable

FillVolume Text Editable

FAACode Text Editable

FillSiteName Text Editable

Season Domain Non‐Editable

GlobalID Text Non‐Editable

SHAPE Text Non‐Editable created_user Text Non‐Editable created_date Date Non‐Editable last_edited_user Text Non‐Editable last_edited_date Date Non‐Editable

OBJECTID Text Non‐Editable

PrePlanned Domain Editable

FireCamp Domain Editable

PubProtection Domain Editable

CollectionMethod Domain Editable

Comments Text Editable

ReviewFlag Domain Editable

AirTaskID Text Editable

CampaignID Text Editable

DropID Text Non‐Editable

Structure Domain Non‐Editable

HistCult Domain Non‐Editable

Watershed Domain Non‐Editable

TESpecies Domain Non‐Editable

CommSite Domain Non‐Editable

Pipelines Domain Non‐Editable

Powerline Domain Non‐Editable

WindTurbine Domain Non‐Editable

Range Domain Non‐Editable

Timber Domain Non‐Editable

Mine Domain Non‐Editable

Lat Text Non‐Editable

Long_ Text Non‐Editable

Slope Text Non‐Editable

Speed Text Non‐Editable

CalcHeight Text Non‐Editable

CalcDropFuelType Domain Non‐Editable

CalcDropFuelModel Domain Non‐Editable

DropTally Text Non‐Editable

LastDropTime Date Non‐Editable

WeatherObsFK Text Editable

Season Domain Non‐Editable

CurrentDay Domain Non‐Editable

GlobalID Text Non‐Editable created_user Text Non‐Editable created_date Date Non‐Editable last_edited_user Text Non‐Editable last_edited_date Date Non‐Editable

SHAPE Text Non‐Editable

OBJECTID Text Non‐Editable

Attributes Type Within GUI

IncidentNumber Text Editable

AircraftType Domain Editable

HeliSys Domain Editable

AircraftID Text Editable

Requestor Domain Editable

RequestTime Date Editable

AicraftOnScene Date Editable

DropTime Date Editable

LoadReturn Domain Editable

DropObj Domain Editable

ReinforceReason Domain Editable

DropOutcome Domain Editable

FireReachingDrop Date Editable

FireOvercomesDrop Date Editable

DropPlan Domain Editable

DropTactic Domain Editable

Coverage Domain Editable

LiqDisp Domain Editable

SplitLoad Domain Editable

Shadowing Domain Editable

DropFuelType Domain Editable

DropFuelModel Domain Editable

Continuity Domain Editable

AirDropTargeting Domain Editable

AirDropHeight Domain Editable

GroundDropTargeting Domain Editable

GroundDropHeight Domain Editable

LocDesig Text Editable

LocFire Domain Editable

ATGS_CC Domain Editable

ASM_CC Domain Editable

Lead_CC Domain Editable

HLCO_CC Domain Editable

AirToAir_CC Domain Editable

AirToGround_CC Domain Editable

EffectOnROS Domain Editable

EffectOnFL Domain Editable

SpreadCharacteristic Domain Editable

SpreadInsideDrop Domain Editable

D

RO

P PO

IN

T CO

N

TIN

U

ED

Figure 8: Line features and attributes. Editable attributes are user or aerial system input. Non‐editable attributes are set by system configuration, calculated downstream or external data sources by AFUE personnel.

Lines

Drop Line ATU Drop Line

Fire Behavior

Line

Ground Task Line

Reference Line

Attributes Type Within GUI

IncidentNumber Text Editable

AircraftID Text Editable

AircraftType Domain Editable

DropTime Date Editable

Lat Text Non‐Editable

Long_ Text Non‐Editable

Speed Text Editable

LiqDisp Domain Editable

Coverage Domain Editable

SplitLoad Domain Editable

Heading Text Editable

Altitude Text Editable

DropGal Text Editable

Comments Text Editable

Season Domain Non‐Editable

GlobalID Text Non‐Editable

SHAPE Text Non‐Editable created_user Text Non‐Editable created_date Date Non‐Editable last_edited_user text Non‐Editable last_edited_date Date Non‐Editable

OBJECTID Text Non‐Editable

SHAPE_Length Text Non‐Editable

Attributes Type Within GUI

IncidentNumber Text Editable

GroundTaskID Text Editable

ID Text Editable

StartTime Date Editable

EndTime Date Editable

FireOvercomesObj Domain Editable

GroundTactic Domain Editable

GroundTaskAssignment Domain Editable

LocDesig Text Editable

LocFire Text Editable

Crews Domain Editable

Engine Domain Editable

Equipment Domain Editable

Firefighters Domain Editable

GrndFuelType Domain Editable

GrndFuelModel Domain Editable

GrndObjOutcome Domain Editable

SpreadCharacteristic Domain Editable

CollectionMethod Domain Editable

Comments Text Editable

ReviewFlag Domain Editable

CampaignID_FK Text Editable

CampaignID Text Non‐Editable

CalcDropFuelType Domain Non‐Editable

CalcDropFuelModel Domain Non‐Editable

Season Domain Non‐Editable

GlobalID Text Non‐Editable created_user Text Non‐Editable created_date Date Non‐Editable last_edited_user Text Non‐Editable last_edited_date Date Non‐Editable

SHAPE Text Non‐Editable

OBJECTID Text Non‐Editable

SHAPE_Length Text Non‐Editable

Attributes Type Within GUI

ID Text Editable

ObsTime Date Editable

IncidentNumber Text Editable

LocOnFire Domain Editable

Slope Text Non‐Editable

FuelTypeCalc Domain Non‐Editable

FuelModelCalc Domain Non‐Editable

CanopyCover Domain Non‐Editable

CanopyCoverCalc Domain Non‐Editable

FlameLength Text Editable

RateOfSpread Text Editable

DirectionOfSpread Text Editable

SpreadCharacteristic Domain Editable

Comments Text Editable

ReviewFlag Text Editable

GlobalID Text Non‐Editable created_user Text Non‐Editable created_date Date Non‐Editable last_edited_user Text Non‐Editable last_edited_date Date Non‐Editable

CurrentDay Domain Non‐Editable

Season Domain Non‐Editable

SHAPE Text Non‐Editable

OBJECTID Text Non‐Editable

SHAPE_Length Text Non‐Editable

Attributes Type Within GUI

IncidentNumber Text Editable

Name Text Editable

ObsTime Date Editable

RefType Domain Editable

Comments Text Editable

GlobalID Text Non‐Editable created_user Text Non‐Editable created_date Date Non‐Editable last_edited_user Text Non‐Editable last_edited_date Date Non‐Editable

Season Domain Non‐Editable

SHAPE Text Non‐Editable

OBJECTID Text Non‐Editable

SHAPE_Length Text Non‐Editable

Attributes Type Within GUI

IncidentNumber Text Editable

AircraftType Domain Editable

HeliSys Domain Editable

AircraftID Text Editable

Requestor Domain Editable

RequestTime Date Editable

AicraftOnScene Date Editable

DropTime Date Editable

LoadReturn Domain Editable

DropObj Domain Editable

ReinforceReason Domain Editable

DropOutcome Domain Editable

FireReachingDrop Date Editable

FireOvercomesDrop Date Editable

DropPlan Domain Editable

DropTactic Domain Editable

Coverage Domain Editable

LiqDisp Domain Editable

SplitLoad Domain Editable

Shadowing Domain Editable

DropFuelType Domain Editable

DropFuelModel Domain Editable

Continuity Domain Editable

AirDropTargeting Domain Editable

AirDropHeight Domain Editable

GroundDropTargeting Domain Editable

GroundDropHeight Domain Editable

LocDesig Text Editable

LocFire Domain Editable

ATGS_CC Domain Editable

ASM_CC Domain Editable

Lead_CC Domain Editable

HLCO_CC Domain Editable

AirToAir_CC Domain Editable

AirToGround_CC Domain Editable

EffectOnROS Domain Editable

EffectOnFL Domain Editable

SpreadCharacteristic Domain Editable

SpreadInsideDrop Domain Editable

PrePlanned Domain Editable

FireCamp Domain Editable

PubProtection Domain Editable

CollectionMethod Domain Editable

Comments Text Editable

ReviewFlag Domain Editable

AirTaskID Text Editable

CampaignID Text Editable

DropID Text Non‐Editable

Structure Domain Non‐Editable

HistCult Domain Non‐Editable

Watershed Domain Non‐Editable

TESpecies Domain Non‐Editable

CommSite Domain Non‐Editable

Pipelines Domain Non‐Editable

Powerline Domain Non‐Editable

WindTurbine Domain Non‐Editable

Range Domain Non‐Editable

Timber Domain Non‐Editable

Mine Domain Non‐Editable

Lat Text Non‐Editable

Long_ Text Non‐Editable

Slope Text Non‐Editable

Speed Text Non‐Editable

CalcHeight Text Non‐Editable

CalcDropFuelType Domain Non‐Editable

CalcDropFuelModel Domain Non‐Editable

DropTally Text Non‐Editable

LastDropTime Date Non‐Editable

WeatherObsFK Text Editable

Season Domain Non‐Editable

CurrentDay Domain Non‐Editable

GlobalID Text Non‐Editable created_user Text Non‐Editable created_date Date Non‐Editable last_edited_user Text Non‐Editable last_edited_date Date Non‐Editable

SHAPE Text Non‐Editable

OBJECTID Text Non‐Editable

SHAPE_Length Text Non‐Editable

Figure 9: Polygon features and attributes. Editable attributes are user or aerial system input. Non‐editable attributes are set by system configuration, calculated downstream or external data sources by AFUE personnel.

Product Requirements:

(a) All products shall conform to applicable industry standards. Examples include Open Geospatial Consortium (OGC), Motion Imagery Standards Board (MISB), and American Society of Photogrammetry and Remote Sensing (ASPRS).

(1) Geo‐referenced video streams will meet the following minimum MISB standards:

(i) Motion Imagery Standards Profile ‐ MISP 2016

(ii) Motion Imagery Sensor Minimum Metadata Set – MISB ST 902

(iii) MISB Standard for Compression for Infrared Motion Imagery (MISB ST 404)

(iv) Recommend H.264 Compression (H.265 is an emerging standard but not fully supported at this point – but at some time they may want to move to H.265)

(2) Sequential time‐based and extracted imagery products will meet the following minimum standards:

(i) Imagery should be in form NITFS 2.1 (MIL‐STD‐2500C) or GeoTIFF

(ii) Recommend Support JPEG 2000 compression

(b) Rasters shall be horizontally accurate in the X‐Y plane at a 95% confidence level (489.5 cm) utilizing Root Mean Square Error Statistics. American Society of Photogrammetry and Remote Sensing (ASPRS) 2014 200 cm class or equivalent to the legacy ASPRS 1990 standard of Class 2 for one (1) meter ortho imagery pixels.

(1) Systems shall utilize a Structure from Motion process to produce a high confidence, high‐density point cloud in Web Mercator WGS 1984 coordinate system (102113, epsg 3785).

(c) Raw mission file format with all associated metadata in a mission directory which facilitates mission playback in the portable workstation or other instances of the system’s user interface.

(1) Mission files include: vector, raster imagery, rasterized point‐cloud, weather and audio.

(2) Provided documentation shall describe mission file structure and path at a level of detail which supports additional processing, display, and search and discover, etc. utilizing server‐based geospatial intelligence products. Example: gdal, ENVI, Jagwire, Socet GPX, Pixia, etc. (examples provided for reference only)

(d) Geospatial products must be extractable in a format supported by ESRI geospatial software.

(1) Raster data must be extractable in an ESRI‐supported file geodatabase utilizing the following structure:

(2) Rasters shall be exportable as a geo‐referenced image set within a user‐defined temporal and spatial binding area.

(3) Vector data shall be extractable in an ESRI‐supported file geodatabase utilizing the following structure:

(e) Vector features shall be extractable as ESRI supported shapefiles format

(f) Vector feature classes shall be extractable in ESRI REST API JSON structure with sync functionality. Web Mercator WGS 1984 coordinate system (102113, epsg 3785) must be utilized.

(g) When initiated by the SO, fire perimeter polygons are to be autonomously extracted from raster imagery and written to the Fire Polygon vector feature on a user‐defined temporal interval. Based on operational experience, it is anticipated the desired temporal interval will range between 30 seconds ‐ 1 hour. (Full fire area in FOV)

(h) When initiated by the SO, fire behavior lines are to be autonomously extracted from raster imagery and written to the fire behavior vector feature on a user‐defined temporal interval. (Partial Fire area in FOV)

(i) When initiated by the SO, aerial drop footprint polygons are to be autonomously extracted from raster imagery and written to the drop polygon vector feature.

Audio System Requirements:

(a) A fourth ACU6101 audio control panel shall be installed at the forward left side of the cabin directly across from the third audio panel on the right. This audio panel and installation must be configured identically to the third audio panel.

(b) Provisions for fifth and sixth ACU6101 audio control panels shall be installed in the right and left SO workstations and function identically to the forward cabin positions. The SOs must have full use of their respective audio panels while the workstations are installed.

(c) Cover plates shall be provided with attached dummy plugs to allow operation with either the two forward cabin audio panels removed or the two workstations removed. These must be designed to replace the audio controllers using the existing DZUS mounting and connectors. The aircraft audio connections to the workstations must use the same plug as the audio controller and allow the cover plates to be mechanically and electrically interchangeable between the forward cabin positions, with the workstations installed, and the SO positions, with the workstations removed.

(d) The original EM6100 External Memory Module must be permanently labeled “STD” and configured with the cabin audio panels in the forward positions with the workstations removed. A second EM6100 shall be provided by the contractor, permanently labeled “IR” and configured with the cabin audio panels in the installed workstations. Cabin headset positions must follow the on‐side audio controllers in both configurations.

(e) An audio recording system shall be installed and meet the following requirements.

(1) Recording of cabin ICS and all communications radios is required.

(2) Output recording is to be timestamped in UTC in synchronicity with collected motion imagery.

(3) Output recording shall be playable codec supported by standard Commercial‐Off‐The‐Shelf (COTS) software of which at least one codec is supported by MS Media Player.

(4) Removable media, or ports to download data, must be accessible from the cabin or cockpit without the use of tools. Downloads will be performed after flight.

(5) A multitrack recorder and mixing deck with independent tracks for cabin ICS and each of the five

AM and FM radios is desired. The recorders must present a 600 Ohm load to the cabin ICS Ring

Line and each of the transceiver audio outputs to ensure audio quality is not degraded. In previous deployments, 2‐channel audio recordings have resulted in tracks where multiple radios have had simultaneous traffic resulting in an inaudible collection of key information.

(6) Audio Playback within the system raster and vector user interface are desired. (i.e., portable workstation)

Weather Sensor Requirements:

(a) The Contractor shall procure and install an AIMMS‐30 or equivalent aerial weather sensor. Aerially collected weather data is utilized in conjunction with vector and raster data to describe the condition in which documented events occurred. Link to recommended sensor:

http://aventech.com/products/aimms30.html

(b) The sensor must have a collection rate no less the 1 Hertz.

(c) Data must be formatted in a mission/flight file which can be modeled in the Weather Research Forecast (WRF) model and Microsoft Excel file format.

Standard Meteorology Packet Aircraft‐State Data Packet

Time (UTC), hours Time (UTC) – hour

Time (UTC), minutes Time (UTC) – minute

Time (UTC), seconds Time (UTC) – second

Temperature (deg. C) – lsb Latitude (deg.) ‐ byte 1 (lowest byte)

Temperature – msb Latitude – byte 2

Relative humidity (fraction from 0 to 1) – lsb Latitude – byte 3

Relative humidity –msb Latitude – byte 4 (highest byte)

Barometric pressure (Pa) – lsb Longitude (deg.) – byte 1 (lowest byte)

Barometric pressure – msb Longitude – byte 2

Wind flow vector N component (m/s) – lsb Longitude – byte 3

Wind flow vector N component – msb Longitude – byte 4 (highest byte)

Wind flow vector E component (m/s) – lsb Altitude (m above geoid) – lsb

Wind flow vector E component – msb Altitude – msb

Wind speed (m/s) ‐ lsb Velocity, north component (m/s) – lsb

Wind speed (m/s) ‐ msb Velocity, north component – msb

Wind direction (deg. true) – lsb Velocity, east component (m/s) – lsb

Wind direction (deg. true) – msb Velocity, east component – msb

Status flag: bit 0 (wind status) 0 = not valid;1 = valid Velocity, down component (m/s) – lsb

Status flag: bit 1 (purge status)

0 = purge off, 1 = purge ON

Velocity, down component – msb

Roll angle (deg) – lsb

Status flag: bit 2 (GPS solution status)

0 = GPS solution bad, 1 = GPS solution good

Roll angle – msb

Pitch angle (deg) – lsb

Pitch angle – msb

Yaw angle (heading) (deg. true) – lsb

Yaw angle – msb

True airspeed (m/s) – lsb

True airspeed – msb

Vertical wind – lsb

Vertical wind – msb

Sideslip angle (deg) – lsb

Sideslip angle ‐ msb

AOA pres. differential (dimensionless)‐lsb

AOA pres. differential – msb

Sideslip differential (dimensionless) – lsb

Sideslip differential – msb

Figure 10: AIMMS‐30 Data Fields

(d) The Weather Sensor shall be installed so that data is available to support all missions including those without the pod.

Data Link Requirements:

(a) (LAN Network – Wave Relay (Persistent Systems) Mesh Network Node(s).

Utilization of existing government wave relay equipment for coordinating aerial and terrestrial data collection within AFUE does not imply this configuration to be a “standard” beyond the scope of the AFUE program.

(1) Avwatch Air Kit AIR300.2 (Kit) or equivalent hardware configuration.

(2) Persistent Systems Wave Relay MPU 5 S‐Band radios integrated with 4G and VPN capabilities.

(3) Installation shall include four (4) Persistent Systems 2.3‐2.5GHz blade antennas (3 on the bottom of the aircraft and 1 on top of the aircraft) and one (1) 4G antenna on the bottom of the aircraft. Persistent Systems Antennas shall be connected to the Kit via low loss high‐quality aviation grade cabling equivalent to LMR 400 cables using custom length cable terminated with RP TNC on one end and SMA on the other end. Cable length shall be minimized to the greatest extent possible and shall not exceed 12' in length.

(4) Installation shall allow the operator to easily select between using the top blade antenna or a bottom blade antenna based on mission requirements.

(5) Data Link Installation. Must be installed so that it is available to support all missions including those without the pod.

(b) In cabin Wi‐Fi is required to support FM workstation and connection to the LAN Network.

(c) The aircraft must be certified as tolerant to T‐PEDs in accordance with FAA Regulations and

RTCA/DO‐307 without limitations based on the phase of flight. Limitations during abnormal or emergency procedures are acceptable.

(1) The certification must include a flight manual supplement clearly stating that the aircraft is T‐PED tolerant and include the technologies evaluated.

(2) The following are the minimum portable technologies which must be evaluated

(i). Bluetooth

(ii). Cellular

(iii). Wi‐Fi (802.11 b/g/n/ac)

(iv). VHF transceivers (136‐174 MHz at 6W)

(v). UHF transceivers (380‐520 MHz at 5W and 764‐870 MHz at 3W)

(vi). Wireless intercom adapters (1.92‐1.93 GHz at 115mW)

Requested Information:

General Details:

Vendors/contractors who respond to this Request for Information (RFI) are requested to provide all of the following information in writing and in accordance with the directions below:

1. Company name

2. Company mailing address

3. Company point of contact (name & title)

4. Point of contact’s telephone numbers (office & fax)

5. Additional details pertaining to specific items requested below

6. Company’s size standard for the NAICS identified above

Note:

You may provide any other pertinent information that may contribute to efficiencies related to this RFI that will assist the Government in developing specification for future requirements.

Cost Details:

Vendors/contractors shall provide a Rough Order of Magnitude (ROM) that includes the following costs:

Estimated Cost of the Sensor System with Data Link Weather Sensor, and Audio Recorder Requirements included

Estimated Cost of installation into Government provided King Air 200

Estimated Maintenance cost of the system and hourly support cost for Technical Support and for Maintenance of the system

Technical Details:

Vendors/contractors shall provide the following information:

1. Description of the available Sensor Capabilities and their ability to meet the above requirements

2. Information on the ability to install the sensor into the FS King Air and the FAA approval process most likely pursued

3. Overall weight of the system (weight for the entire modification to the aircraft to support this effort)

4. Estimated time required for the installation process and approval

5. Potential issues related to the sensor system and/or installation of the sensor system

6. Subcontracts required to support the contract

7. Description of the estimated training that would be required for effective operation of the sensor system