Development of a Mobil Device App for Calculation of Firefighter Safety Zone Size

INTENT TO AWARD Single Source: The Rocky Mountain Research Station Fire Sciences Lab located in Missoula, MT is looking for a contractor to develpment of a mobile device APP for calculation of Firefighter Safety Zone Size. Period of Performance will be approximately 8/1/2014 -07/31/2015. 1.0 Background: Firefighter safety is associated with both increased understanding of the fire and the variables that affect its intensity and spread. Recent work focused on the development of new firefighter safety zone rules has attempted to link safety zone size with terrain slope and wind affecting fire. Thus as firefighters assess the effectiveness of a potential safety zone, they need to consider the effect of wind and terrain on fire intensity and the overall impact on safety zones. This contract is focused on providing funding to support the development of a mobile device application that will calculate safe separation distance from fires to prevent burn injury. Recent studies have shown that the specification of safe separation distance is a multivariate complex problem that is not conducive to simple calculation. Rather it requires reference to wind, slope, fire intensity to determine the distance. The objective is to develop a mobile device application that will allow the user to perform the required calculations from remote locations with only an android or apple device. Ideally the app could be run in two modes: 1) connected-where data defining wind, terrain, and fire would be available from a specified server and 2) unconnected where user would enter minimum data needed to calculate SSD. The application will allow the user enter a specific location, vegetation type, terrain slope, wind exposure, and fire intensity. The core calculation is a distance, but ideally the outputs can be displayed using a GeoPDF or similar display, showing potential locations in the area that might meet the distance requirements. The application will be free for use and will be made available on the typical access sites. 1.1 Location: USDA Forest Service, Rocky Mountain Research Station, Missoula Fire Sciences Laboratory, Missoula, MT 1.2 Contracting Officer's Technical Representative (COR): Karen Iverson, USDA Forest Service, Rocky Mountain Research Station, Missoula Fire Sciences Laboratory, Missoula, MT. 1.3 Technical Contact: Bret Butler, USDA Forest Service, Rocky Mountain Research Station, Missoula Fire Sciences Laboratory, Missoula, MT. 1.4 Purchasing Agent: Susan Rasmussen, , USDA Forest Service, Rocky Mountain Research Station, Missoula Fire Sciences Laboratory, Missoula, MT. 2.0 Task Objectives: 1. GUI design and system setup. 2. Build mobile application for (Android). 3. Test android based app and modify based on feedback. 4. Build mobile application for IOS based on Android app. 5. Deploy beta version for testing, modify app for both OS based on feedback. 6. Develop documentation for mobile app 3.0 Requirements: A. Summary: There is need to develop a digital software application for assessing the safe separation distance (SSD) needed to prevent injury to firefighters from fire. The SSD defines what is commonly termed a safety zone, with SSD being the radius of a circular area. Recent work assessing newest data and simulations for SSD in the context of fire intensity, wind and slope suggests that the solution is multidimensional and cannot be easily addressed without a calculator. This document outlines the functional requirements for such an application. In the following we define digital application by the term "app". Ideally the app could be run in two modes: 1) connected-where data defining wind, terrain, and fire would be available and 2) unconnected where user would enter minimum data needed to calculate SSD. B. OS: Initially the system will be developed for Android, it will then be extended to IOS once the basic functional requirements have been tested. C. Data: In locations where the user has connectivity the app could access data regarding terrain slope, vegetation coverage, forecast winds, etc. Where connectivity was limited or did not exist the app must utilize existing baseline data and user inputs to calculate the SSD. D. User input: a. Position: The app should either allow user to input a specific location or determine the position of the user (using mobile device GPS) and determine terrain slope. Options for definition location may include: i. Digitizing a point on a base map using topographic or other available data as background reference. ii. Using the GPS location determined by the mobile device, including the ability to show this on the map as reference for the user. This will help the user determine how accurate the GPS location is. iii. Select and move the user location (point) to reflect a more accurate location. The initial location may be defined either by digitizing on map, or device GPS. b. Vegetation: : Ideally it would also access vegetation coverage data to either automatically assess vegetation type, height, and some metric of flammability. This data could also be manually entered by user. Options include: i. Having vegetation or surface fuels data automatically available on the device as baseline data. Other vegetation and landscape related information, such as conventional canopy characteristics (canopy ceiling height, canopy bulk density, canopy base height, canopy cover density, slope, aspect, elevation), will be preloaded using the best available public sources. This data is essential for calculating the necessary fire behavior outputs, such as fire intensity (i.e. flame length, fireline intensity, etc.) ii. Options will be provided for the user to override the default baseline vegetation and landscape data with user input values. Fire behavior outputs would be created with user input values if defined by the user. c. Wind: The user would specify a wind speed and direction. The app would then either automatically calculates if the specified position was aligned with the wind. Or the user could specify wind alignment. Options include: i. Automatic download of NWS (or other) weather observation data using the available connection. ii. If no connection exists, the user would have to key in the wind speed and direction values. d. Fire Intensity: Ideally, given fuel, wind, slope and some other basic parameters the app would calculate fire intensity. i. Other model parameters can be accommodated through user interface input menus to supplement any of the fire behavior outputs that are generated (i.e. flame length, fireline intensity etc.). Specifics to be defined jointly by the project technical team. e. Terrain: Digital elevation data would be accessed by the server. a. Language: The initial development would occur in Android with intent that a beta version available for testing. This would operate in a web browser environment. Once user input has been received and the basic design evaluated apps in native Android and IOS would be developed. Optional HTML5/Javascript version might be considered. b. Timeline: Beta version available for Android devices 45 days after contract initiated. Depending on time of year user testing would occur for 60 days. The native versions would be developed in the next 60-90 days. c. Contractor Qualifications: d. The specific contractor for this project must be well versed in the following requirements: e. Proven experience developing web and mobile applications using GIS/mapping capabilities for wildland fire. f. Subject matter expertise in fire behavior modeling and risk analysis including previous experience developing and deploying custom software applications. g. Experience implementing fire behavior science into operational models for wildland fire operations. E. Source Code: Developer will provide all source code to US Forest Service. All source code would be owned by the US Forest Service and will be distributed for free to any interested parties. F. GUI: The GUI will be developed jointly between GCS and the Forest Service representatives. Ideally it will be as simple as possible. G. Security: The device application should have some kind of user registration to limit use either to government employees or in some other way monitor who can access the server. The specifications for this can be developed through joint communication between GCS and USFS. H. The technical contact and the COR will determine if experience and knowledge is sufficient for the task. 4.0 Deliverables: All work must be delivered to the COR. 4.1 Accomplishment report with each invoice for payment. Dates determined below will be adjusted based on contract initiation date. 4.2 Completion of mockup of GUI and logical process for client server interaction within 4 weeks of contract initiation. 4.3 Functional demonstration of Mobile App on one OS within 10 weeks of initiation of contract. 4.4 Functional demonstration of Mobile App on both Droid and IOS within 20 weeks of contract initiation. 4.5 Testing of beta version of APP on both OS within 30 weeks of initiation of contract. 4.6 Delivery of all source code to USFS within 52 weeks of initiation of contract. 5.0 Government Furnished Resources: 5.1 For the bulk of the work the contractor will work at the contractor's facility. 5.2 Forest Service shall provide contractor identification cards and keys as necessary for access to government offices, research facilities and field study sites -if required by the assigned tasks. 5.3 The Forest Service shall provide all field and analytical equipment -if required by the assigned tasks. 5.4 Prior Use Requirements: Contractor is required to successfully complete the USDA Computer Security Awareness Training and the USDA Privacy Basics training. The Forest Service will provide any access to training course(s) requirements such as the use of Government computer-Security Training and any other Safety or Security requirements required for the use of Government Property, Services, and Equipment prior to use. 6.0 Dependency Factors: Proposed time schedules and work priorities will be made by the Forest Service. Weather scenarios will be provided by the Forest Service. 7.0 Acceptance Criteria: 7.1 Schedule. Most work will be cooperative efforts between Forest Service headquarters, field units, and other contractors. 7.2 Delivery Instructions. As each task is completed updated source code will be delivered to US Forest Service Technical Contact. Technical Contact will communicate with the COR if changes are required in order to meet the obligations. 8.0 Travel and Training: 8.1 If overtime is anticipated, approval for the number of hours and schedule must be approved by the CO depending on the rationale, once the request is submitted by the contractor. 8.2 If travel and per diem are needed to fulfill the requirements of this task, lodging, per diem and mileage reimbursements shall not exceed the Government rate(s) and regulatory requirements established by GSA. Contract employee will be reimbursed by the contractor, at actual cost, not exceeding the Government rate(s) and regulatory requirements established by GSA (FTR). Travel vouchers and receipts shall be submitted to the COR for approval. The COR will certify total travel cost along with the monthly invoice. 8.3 Work requested under this task order is not intended to improperly supplement the Forest Service staff and not intended to be used as a "personal services." Further, the unit will assure that a "personal services" relationship will not be allowed to develop between using agency officials and contractor employees during the performance of any work under this task order. (Reference FAR section 37.104 regarding prohibited "personal services.")