Interagency Fuels Treatment Decision Support System (IFTDSS)
PURPOSE: The Department of Interior (DOI) Acquisition Services Directorate (AQD) on behalf of the DOI Office of Wildland Fire (OWF) [and partners] is seeking to obtain market research from vendors to assist the Government in understanding the capabilities available in the Strategic Software Vehicle industry. The focus in on continued operations and improvement of Interagency Fuels Treatment Decision Support System (IFTDSS). Additionally, the market research will assist the Government in determining how small business could fit into the acquisition strategy.
The Office of Wildland Fire (OWF), coordinates the DOIs wildland fire program with other Federal (principally USDA Forest Service) and non-federal partners on wildland fire programs, policies, budgets, and information technology enterprise systems and decision support tools.
BACKGROUND: OWF [and partners] (more information available at http://www.doi.gov/pmb/owf/index.cfm and http://www.fs.fed.us/fire/ ) is working to improve and strengthen the wildland fire program by providing reliable data, authoritative sources, common standards, and integrated systems that support decisions, program direction and policies.
The Interagency Fuels Treatment Decision Support System (IFTDSS) is a web-based software and data integration framework that organizes previously existing and newly developed fire and fuels software applications to make fuels treatment planning and analysis more efficient and effective. It is a scalable fuels management planning system that utilizes appropriate fire behavior modeling, economic principles, and information technology to support effective risk-based fuels management planning. (System Architecture Information can be found here: http://www.frames.gov/documents/iftdss/IFTDSS_phaseIV_final_Report.pdf)
IFTDSS provides access to a variety of data and models, all in one place, through one user interface. IFTDSS provides planners with the structure to pass data (inputs and outputs) easily between models, to reuse and share their work products, and provides a consistent analysis framework for all users.
The Joint Fire Science Program (JFSP) sponsored the design, prototype, early development, and evaluation of IFTDSS beginning in 2008 and continuing through 2013. JFSP worked closely with fuels managers throughout that time period garnering feedback to ensure that IFTDSS was focused on user needs and priorities. These efforts were recently acknowledged when the Wildland Fire Information and Technology (WFIT) Executive Board formally approved IFTDSS on May 30, 2014 for further development and eventual operational deployment. IFTDSS version 2.0 Beta is currently available and will be managed in beta test mode for the next two years, with full operational deployment planned for 2017 (Background information on the history of the project can be found here: http://www.frames.gov/partner-sites/iftdss/iftdss-home )
Extensive guidance from a broad range of fuels treatment specialists over the last five years has resulted in the identification of four critically important workflow processes:
1.Hazard Analysis
2.Risk Assessment
3.Fuels Treatment Assessment
4.Prescribed Burn Planning
Business Need
Fire Manager Challenges
Unlike wildfire response and preparedness, fuels treatment management and planning across the federal fire agencies does not have a common approach. The dis-integrated tasks that fire managers are asked to complete in order to plan and implement fuels treatments do not currently stem from a programmatically stated business requirements. The business need for implementing a Fuels Management Decision Support System is based on the following four challenges facing fire managers:
1.No existing widely accepted risk management-based fuel treatment decision support process
2.No Interagency archive database for fuels management planning or implementation activities
3.Fire managers and planners are not trained to a) complete landscape or unit level risk-based assessments or b) plan for effective fuels treatments
4.Fuels treatment planning data and information is not aligned with wildfire response decision support tools or information
The implementation and development of IFTDSS will address and meet each of these fire management challenges:
-IFTDSS will provide a consistent end-to-end risked based fuels treatment planning process that can be used across the fire management and fuels planning community
-IFTDSS will support an enterprise architecture B?to beB? paradigm characterized by an emphasis on risk management; standards, predictable processes; shared data & outcomes across a broad community
-IFTDSS will allow the use of authoritative data/systems; integrated tools; focused planning & support; integral training; and shared knowledge
NOTICE: This RFI is being issued solely for information and planning purposes. It does not constitute a Request for Proposal (RFP) or a promise to issue an RFP in the future. This RFI does not commit the Government to a contract for any supply or service whatsoever. Furthermore, the Government is not at this time seeking proposals and will not accept unsolicited proposals. Responders are advised that the Government will not reimburse for any information or administrative costs incurred in response to this RFI; all costs associated with responding to this RFI will be solely at the interested partiesB? expense. Not responding to this RFI does not preclude participation in a future RFP, if one is issued.
Sources Sought: This RFI is seeking responses from vendors to address the questions below. OWF is looking for a Software Strategic Source for the IFTDSS web applications environment which will provide users with an interface to workflows supporting fuels treatment decision support actions that use existing (and future) fire and fuels software applications and scientific models to make fuels treatment planning and analysis more efficient and effective. This web-based application is tied to a Scientific Modeling Framework (SMF) where approved models and databases are housed allowing access by users. The Scientific Modeling Framework is designed to allow researchers and developers to test existing models within the SMF but also to develop new fire management related models, tools and applications in a B?playgroundB? environment. Links to source documentation are provided throughout this RFI. Additionally, OWF is seeking information pertaining to the questions identified below.
Marketing brochures and/or generic company literature will not be considered. Not addressing all the requested information may result in the Government determining the responder is not capable of performing the scope of work required.
Government Questions:
1. What are the benefits and drawbacks of using a single source vs. multiple sources for development of the described IFTDSS application? Would a single source be capable of providing the support for all of the vision/extent identified for IFTDSS in the provided links?
2. IFTDSS is intended to be a secure web-based application available to multiple federal agencies, as well as state and private users. We anticipate at least 3 levels of access (Administrative, National/Regional, and local) and intend for users from disparate agencies (Structured with a username/password unique to IFTDSS) to be able to collaborate online on specific projects.
a. Have you developed a web based system which adheres to federal IT security standards and requirements? If so, please describe and provide the list of efforts.
b.Describe the general approach you would take, citing functional existing examples, to ensure access for a variety of classes of users.
3. IFTDSS is designed as a software integration framework that organizes and integrates different models and data sets used in fire and fuels planning giving direct access to multiple individual software tools and models through and single web-based interface. The current software integration framework for IFTDSS, known as the Scientific Modelling Framework (SMF), has been independently developed over the past 5 years as part of the broader IFTDSS application development.
a. Have you developed and implemented other integration systems (linking and/or incorporating other systems and models)? If so, please provide the list as well as the points of contact for each.
b. Would you recommend continued development of the existing SMF as IFTDSS moves forward or development/ incorporation/conversion to a more current service oriented architecture package? Briefly explain your logic.
4. Integration of future, current, and legacy data sets and the ability to B?push and pullB? data is a key functionality desire within IFTDSS.
a. Federal Wildland Fire Management has several data systems [Wildland Fire Decision Support System (WFDSS), LANDFIRE, National Fire Plan Operations and Reporting System (NFPORS), etc.] and models (BehavePlus, FlamMap, FARSITE, FOFEM, NEXUS, etc.) from which IFTDSS could push and pull data and analyses. From the contract material provided, how would you envision that this data integration and system interoperability be implemented in IFTDSS?
b. How would you describe this issue to potential developers in order for them to evaluate and understand the nature of the work (business terminology, requirements, etc.) of legacy dataset integration being advertised?
c. Federal Fire Management Systems are just beginning to explore more seamless integration between systems. There are many opportunities for utilizing cloud services and testing better technologies to assist with info sharing that reducing redundant data entry requirements and presents end users with the latest and most accurate information. As legacy systems merge, split and evolve over time, developers will need to be flexible in regards to how data is shared. IFTDSS will require its own unique native database, will pull vital inputs and information from other established systems and will push outputs to external systems of record. Do you have examples from other work with the federal, state, or municipal government or the private sector where the contract and scope of work were able to successfully define this dynamic environment? If so, please describe the scope or provide example language.
5. Most of the source code for federal wildland fire management applications is dynamic, evolving and changing (fire behavior models in particular). Software is written in different coding or software languages, legacy software or code was built B?on the flyB? and can be expansive and difficult to break into simple stand-alone code blocks that can be quickly plugged into new systems. The SMF is one attempt to build some agility into the coding work, and efforts are underway to run the most utilized models on a single cloud server. In the meantime, legacy code may have to be integrated into native applications.
a. Do you have experience with prior projects which required understanding of the domain business logic and necessitated flexibility in making efficient changes as the system evolved? If yes, please describe.
b. How would you describe this issue to potential developers in order for them to evaluate and understand the nature of the work (business terminology, requirements, etc.) of legacy dataset integration being advertised?
6. What is the typical pricing structure for the Industry?
7. Describe the challenges you see in this project both in terms of technical challenges and in terms of the dynamic nature of government policies and priorities.
8. OWF is considering a Best value/Trade-off approach for this. If this requirement becomes a formal solicitation, what should OWF consider when trying to determine what is the best proposal including the evaluation factors? Please explain the recommendations. The following are several examples, but firms are encouraged to elaborate further by commenting on the value of the factors being considered, suggest others, or recommend eliminating.
-Key Personnel
-Past Performance
-Percentage of items Vendor can support
-Management Plan / Project Management
-Implementation Plan
-Technical Approach
9. If OWF decides to conduct oral presentations as part of the source selection process, what do firms believe is an effective way of evaluating offers during oral presentations?
-A software or website demonstration.
-A scenario provided with the solicitation and having firms brief the solution.
-Or describe another approach
Submission: Providers with the capability to provide the requirements referenced herein are invited to submit, in writing, information within the page limitation specified. This information should be responsive to the request for information as well as any technical questions, as indicated herein. Submissions for the information must be organized and identifiable per the information in this RFI, e.g. responses to questions are numbered by question and follow the same sequence.
Questions from Interested Providers
Please refer all questions/comments to the Contracting Officer, Ms. Kimberly Luke at Kimberly_Luke@ibc.doi.gov. FedBizOps will be the sole repository for all information related to this RFI. Vendor questions and Government responses will be posted to FedBizOps. No questions will be addressed via oral communication.
All requests for clarification must be in writing, to the address listed below, and shall be in electronic format, and submitted via email. All submissions must reference this RFI title. All requests for RFI clarification are due no later than 2:00 ET, Thursday, February 5, 2015.
Requests transmitted via facsimile (fax) will not be accepted. Should any request for clarification be received after the date stated and time stated above, the Government reserves the right not to provide an answer. If, however, in the GovernmentB?s opinion, the request for clarification cites an issue of significant importance, the Government may provide written responses to all potential providers. Please note, questions and comments will not be protected, by the Government, as proprietary.
RFI Response Length and Format
All interested providers should construct responses in twenty (20) pages or less and in Microsoft Word format. Appended materials, such as Provider brochures or information, are permitted and will be excluded from the twenty (20) page limitation. Submissions should be in a Microsoft Office compatible format (i.e., Microsoft Word, PowerPoint, Excel, etc.) or Adobe Acrobat
A page is defined as an 8.5 inch by 11 inch sheet of paper with no less than one-inch margins on all four sides; All pages shall be single-spaced, single-sided, with a font no less than 12 points for text and no less than 10 points for tables and graphics; Spacing before and after the line shall be no less than 3 point; the following page types do NOT count towards the page limitations:
-Section dividers
-Blank pages, which must be marked B?This page intentionally left blankB?
-Fold-outs shall be counted as the appropriate number of pages based upon an 8.5 inch by 11 inch sheet of paper; partial pages shall be rounded up (e.g., 1.5 pages will be treated as 2 pages.);
RFI Responses
Interested providers are requested to submit a response no later than 2:00 PM ET on Tuesday, February 24, 2015 to the Contracting Officer, Mrs. Kimberly Luke at Kimberly_Luke@ibc.doi.gov. Submissions shall be submitted electronically and not exceed twenty (20) pages. Paper copies will not be accepted. The responses must include the business size of the vender under NAICS code 511210 (Service Disabled-Veteran Owned Small Business, Veteran-Owned Small Business, Women-Owned Small Business, HUBZone Small Business, Small Disadvantaged Small Business, Historically Black College and University/Minority Institution, Small Business Joint Venture, Consortium, Team Partnering, or Large Business).
Additional Information
This RFI is issued solely for information purposes and does not constitute a solicitation or obligation on the part of the Government. Neither unsolicited proposals nor any other kind of offers will be considered in response to this RFI. Providers will not be reimbursed any costs associated with developing responses and/or providing information in response to this RFI and/or any follow-up information requests.
Proprietary information and trade secrets, if any, must be clearly marked on all materials. All information received that is marked Proprietary will be handled accordingly. Please be advised that all submissions become Government property and will not be returned. All Government and contractor personnel reviewing RFI responses will have signed non-disclosure agreements and understand their responsibility for proper use and protection from unauthorized disclosure of proprietary information as described in 41 USC 423. The Government shall not be held liable for any damages incurred if proprietary information is not properly identified.
No telephone calls will be accepted requesting a bid package or solicitation. There is no bid package or solicitation. In order to protect the procurement integrity of any future procurement, if any, that may arise from this announcement, information regarding technical point of contact will not be given and no appointments for presentations will be made.
Luke, Kimberly
