SOLICITATION NOTICE
D -- Mission Planning Applications (MPA) to Support Special Operation Forces (SOF) Mission Planning
- Notice Date
- 8/8/2013
- Notice Type
- Presolicitation
- NAICS
- 541511
— Custom Computer Programming Services
- Contracting Office
- ACC-RSA-FT EUSTIS - (SPS),, Building 401, Lee Boulevard, Fort Eustis, VA 23604-5577
- ZIP Code
- 23604-5577
- Solicitation Number
- W91215-13-R-0007
- Response Due
- 9/10/2013
- Archive Date
- 10/7/2013
- Point of Contact
- steven.nerenberg, 7578780104
- E-Mail Address
-
ACC-RSA-FT EUSTIS - (SPS)
(steven.l.nerenberg.civ@mail.mil)
- Small Business Set-Aside
- N/A
- Description
- REQUEST FOR INFORMATION (RFI) # W91215-13-R-0007 Mission Planning Applications (MPA) to Support Special Operation Forces (SOF) Mission Planning 1.0 General. This document requests information for follow-on design, development, and maintenance of the Mission Planning Applications, (MPA), as required by, the Special Operations Mission Planning and Execution Program Office, Fort Eustis, Virginia. The MPA effort will develop, modernize, and sustain mission planning software modules based upon Special Operations Forces requirements and technology enhancements. 2.0 Definitions. 2.1 Flight Performance Modules (FPMs): A digital representation of aircraft performance, as depicted by charts from operator manuals, flight test data, and other documentation. FPMs calculate aircraft takeoff, landing, cruise, hover, weight, wind speed, range, torque available, and other pertinent data. FPMs files are generally developed/delivered as.dll files and included in an executable software application (i.e. PPC, PPC#, or PX3) 2.2 Point Performance Planner (PPP/PX3) Modules: Executable software that incorporates FPM calculations via a Graphic User Interface (GUI), interfaces with PFPS mission planning software, displays any warnings/errors, and prints pilot kneeboard pages for specific aircraft. PX3 is currently used on SOF fixed wing aviation platforms. 2.3 Performance Planning Calculator (PPC): Executable software that incorporates FPM calculations via a user GUI, interfaces with PFPS mission planning software, displays any warnings/errors, and prints pilot kneeboard pages for specific aircraft. PPC is currently used on SOF rotary wing aviation platforms. 2.5 Take Off and Landing Data (TOLD): A printable card with pertinent aircraft info/data. The format is usually referenced by a specific form (i.e. United States Army Special Operations Command (USASOC Form 4887-R)), or may be designed by the user. Generally speaking, TOLD refers to a fixed-wing card, while Performance Planning Card (PPC) refers to a rotary wing card. 2.6 Point Performance Planner Sharp (PPC#): Executable software that incorporates FPM calculations via a user GUI, interfaces with Portable Flight Planning Software (PFPS) mission planning software, displays any warnings/errors, and prints pilot kneeboard pages for specific aircraft. PPC# was developed as a follow-on to PPC, with the intent to enhance performance of the software calculations. PPC# is currently used on SOF rotary wing aviation platforms. 2.7 Portable Flight Planning Software (PFPS): A suite of software tools that allows DoD and other organizations to plan executable missions and routes, utilizing the FalconView mission planning graphical viewer, and numerous 3rd party tools. This is accomplished via multiple map overlays, GPS data transfer modules, weight & balance tools, geospatial editors, targeting software, and other applications. Development is underway to implement enhanced versions of PFPS tools. This development effort is entitled Execution Plan, or simply XPlan. 3.0 Background. 3.1 The Special Operations Mission Planning Environment (SOMPE) program provides an integrated software suite of mission planning and execution tools for time critical command and control of globally distributed Special Operations Forces (SOF). The SOMPE Program automates time-intensive planning activities and provides enhanced situational awareness capabilities. SOMPE also provides an interoperable environment for adaptive war planning to collaborate, horizontally, vertically and in parallel, the development of the various components of mission plans. SOMPE spans multiple USSOCOM elements, to include SOF warfighters and their warfighting platforms. The SOMPE program develops, integrates, fields, trains and sustains advanced software applications. Under this effort, Advanced Mission Planning Tools (to include flight performance modules (FPMs), platform performance planning modules, platform data transfer modules, etc.) will be developed, modernized and sustained to support SOF requirements and technology enhancements. 3.2 The current Flight Performance Module Software (PPC and PPC# for rotary wing, PX3 for fixed wing) is under development by QinetiQ-North America (QNA), Huntsville, AL. The contract expires in May 2014. The purpose of this Request For Information (RFI) is to query industry in order to locate companies that have the capability to continue development and modernization of the Flight Performance Module Software. The paragraphs below state the tentative requirements. 4.0. Task 1 Software Development and Test Support 4.1. System/Software Requirements and Architecture Analysis 4.1.1 The Contractor shall document and analyze derived Special Operations mission planning system/software requirements and make implementation recommendations to include architectural approaches for satisfying user requirements/mission planning needs. The Contractor shall recommend allocation of Special Operations mission planning system requirements to platform specific software modules, core mission planning applications, and other tools/elements (e.g., flight performance models, configuration files, etc.). The Contractor shall analyze the Special Operations mission planning architecture as it evolves. The Contractor shall analyze existing mission planning software and recommend design and architecture enhancements. The Contractor shall also analyze existing software applications for migration to future systems. 4.1.2 The Contractor shall analyze the software for compliance with commercial and DOD Information Assurance (IA) requirements. The Contractor shall use the latest version of the Security Technical Implementation Guide (STIG), and the USSOCOM Gold Disk, as guide to determine compliance. The Contractor shall develop software that is compliant with DoD IA guidance to reduce vulnerabilities. The software shall operate on a DoD Network. The software will not be quote mark net dependent quote mark. The software will operate on the Windows 7 operating system. 4.2. Software Development 4.2.1 The Contractor shall develop/enhance/upgrade software modules, components, and/or tools as directed by the Special Operations Mission Planning Office (SOMPO) to include, but not limited to: core mission planning software, performance planning modules and other mission planning software. Specifically, the Contractor shall develop/enhance/upgrade Flight Performance Models (FPMs) for rotary and fixed-wing aircraft. The FPM models shall be an accurate digital representation of the performance data presented in each aircraft's operators manual. This includes rotary wing, fixed wing, and Non Standard Aviation (NSAV) platforms, among others. 4.2.2 Additionally, the Contractor shall develop Performance Planning Calculator (PPC), Point Performance Planner (PX3), or similar software executable applications, to visually display FPM performance calculations and print kneeboard-style pilot cards (such as USASOC Form 4887-R, AF IMT Form 4064, etc). These software applications shall display Take Off and Landing Data (TOLD) and PPC cards, for the respective fixed, or rotary-wing aircraft. 4.2.3 The Contractor shall design customer-specific aircraft software modules that interface with the PPC/PX3 application, FPM, and Portable Flight Planning Software (PFPS)/XPlan environment. 4.2.4 The Contractor shall review, define and document issues regarding software interfaces and implement improvements as directed by SOMPO. Proposed software modules shall be developed/enhanced using commercially accepted practices. The Contractor shall develop software tools that are compliant with Government-furnished interface documentation, as required. The Contractor shall provide pre-release (Beta) software prototypes to the Government for analysis and evaluation. All software products shall be designed for maximum code reuse. 4.3. Software Testing 4.3.1 The Contractor shall perform Formal Qualification Testing (FQT) for each software product in accordance with Contractor procedures prior to delivery to the Government. Contractor FQT shall assess the software tool's basic functionality, maturity, reliability and verify that all requirements have been met. The Contractor shall deliver a test report with each software product. The Contractor shall also support Government testing, as needed. 4.4. Software Documentation 4.4.1 The Contractor shall provide software documentation as required by the SOMPE Test and Evaluation Master Plan (TEMP). Such documentation includes, but is not limited to: Software Requirements Specification (SRS), Software Version Description (SVD) with Release Notes, Software (including executable and source code), Software User's Manual (SUM) and Software Test Report (STR). The Contractor shall document software source code using commercially accepted methods. Software documentation shall be upgraded to coincide with platform and/or mission planning upgrades/enhancements. 4.5. Data Rights 4.5.1 The Government will have unlimited rights to the software, modules, and interfaces developed under this effort. The Contractor shall use existing Government-furnished software as a departure point for further development. Final software deliverables shall include: Executable and installable software on a CD/DVD All software source code in this effort All software items not developed under this effort but required to compile and build a working install for a deliverable product All documentation associated with a particular product Must be installable over a Local Area Network (LAN) 5.0. Task 2 Software Project Management and Maintenance 5.1. Software Project Management. The Contractor shall plan, organize, staff, schedule, and manage software efforts using commercially accepted program management practices. The Contractor shall also coordinate with other developers and interface with the Government as necessary for successful integration and maintenance activities. The Contractor shall ensure technical and schedule data flow is maintained between all activities to prevent technical and schedule incompatibilities. 5.2. Software Sustainment 5.2.1 The Contractor shall maintain/sustain mission planning software modules, components, and/or tools as directed by the SOMPO. The software shall be maintained using commercially accepted practices. The Contractor shall maintain software that is compliant with Government furnished Interface Control Documents (ICDs), as required. The Contractor shall provide pre-release (Beta) software to the Government for analysis and evaluation. The maintained software tools shall be designed for maximum code reuse. 6.0 Government Furnished Information 6.1 Upon contract award, the following Government Furnished Information (GFI) will be provided to accomplish development of specific requirements and products described below to include, but not limited to current Aircraft Technical Manuals/Orders, flight performance data, MPAS installations, access to aircraft platform subject matter experts, current versions of the existing software source code, software documentation for maintenance tasking, and aircraft limitation waivers. 7.0 This RFI is the initiation of market research under Federal Acquisition Regulation (FAR), Part 10, and does not constitute a Request for Proposal (RFP) or a promise to issue a RFP in the future. This announcement is for informational and planning purposes only and should not be construed as a commitment by the Government to procure such software development support of the Government-furnished software. The Government does not intend to award a contract on the basis of this RFI or to pay for any information, or otherwise reimburse responders for any costs associated with their respective submissions in response to this RFI. All submissions will be treated as information only. Respondents will not be notified of the results of any review of this RFI; however, clarification of submissions may be requested by the Contracting Officer. Not responding to this RFI does not preclude participation in any future RFP, if any is issued. In accordance with FAR 15.201(e), responses to this notice are not offers and cannot be accepted by the Government to form a binding contract. It is the responsibility of the interested parties to monitor this site for additional information pertaining to this RFI or any subsequent issued RFP, if any. Responders are solely responsible for all expenses associated with responding to this inquiry. All products must comply with the Buy American Act and participation in this effort is strictly voluntary. 8.0 Proprietary Materials Protection This notice is part of Government Market Research, a continuous process for obtaining the latest information from industry with respect to their current and near-term abilities to support an acquisition of this magnitude. The information collected may be used by the Government to explore acquisition options and strategies for the possible approaches within the military. All information received in response to this RFI that is properly marked as quote mark proprietary quote mark will be handled accordingly. The Government shall not be liable for, or suffer any consequential damages, for any proprietary information not properly identified. RFI responses which contain information that is marked as proprietary will be protected as proprietary information. Such information will be reviewed by a team comprised of Government as well as contractor personnel designated to provide technical assistance for the Government's preparation of an acquisition strategy. All members of the team will be reminded of their obligation to protect such information to the maximum extent permitted or required by the Economic Espionage Act, 18 U.S.C. 1831 et seq., and other applicable statutes or regulations. In addition, Government members will be reminded of their obligations to afford protection under the Trade Secrets Act, 18 U.S.C. 1905. All contractor members are required to protect the information by the terms of their contracts. The Government will make a determination whether or not contractor personnel have organizational conflicts of interest that could adversely affect protection of the information. Responses to this RFI will be deemed as consent to release this information to support contractors. 9.0 RFI Response 9.1 Responses to this RFI are requested by 3:00 p.m. E.T., 10 September 2013, with 1 quote mark margins, a font of not less than 12 points, and are not to exceed 20 pages in length including all appendices. Responses are requested to address the following: 9.1.1 Respondents shall provide a description of its existing or developmental products that have potential to meet the sought capability. 9.1.2. For existing products that may provide sought capability, a description of the current uses of this software, including if commercial or military. 9.1.3. Information must include complete descriptions of the existing system that will be available for delivery within the timeframe indicated above and must include sufficient documentation to support any claims that the system performance will meet the minimum performance capabilities contained in the specification. Please identify current status and location where the Government can witness a demonstration of your proposed system. Such documentation may include system technical specifications, product brochures and related literature, performance test data, system drawings and/or photographs, or any other data to support the state of system development and or production readiness. 9.1.4. Corporate capabilities (i.e., available facilities and assets to include existing personnel, software tools, development environments) and company profile (i.e., company type, US or non-US ownership, Cage code, DUNs number, size and status as listed in the Central Contractor Registration). 9.1.5. Corporate research initiatives undertaken relative to programs that may have this capability to include a discussion of internally funded Research, Development, Testing and Evaluation activities along with the maturity levels for those efforts. 9.1.6. Past and current relevant performance information. 9.1.7. Name, telephone number, fax number, street address and e-mail address for Program, Technical and Cost points of contact information. 9.2 Responses should be submitted electronically via the U.S. Army Aviation and Missile Research Development and Engineering Center (AMRDEC) Safe Access and File Exchange website (https://safe.amrdec.army.mil/safe/) in Microsoft Office format or as a portable document format ( quote mark.pdf quote mark ) file. Use the following distribution email address as prompted by the site: steven.l.nerenberg.civ@mail.mil. 9.3 Responses from U.S. firms will be accepted to this RFI. Responses to questions from interested parties will be promptly answered and posted on this FedBizOpps (FBO) website, unless some release of proprietary information is involved or the answer addresses a question peculiar to a Company or that Company's response. Post submittal, one-on-one information sessions with respondents are not contemplated; however, they may be offered to responders to clarify the Government's understanding of their submittal, the capability ramifications, or to discuss their business approach. 9.4 Verbal questions will NOT be accepted. Respondents are advised to submit questions via email to the above Government POC. All questions will be answered via posting answers to this FBO website; except as provided above. The Government reserves the right to not address questions received after 12:00 p.m. E.T., 6 September 2013. 9.5 Disclaimer and Notice: This is NOT a solicitation for proposals, applications, proposal abstracts, or quotations. Per FAR clause 52.215-3, (a) the Government does not intend to award a contract on the basis of this RFI or to otherwise pay for the information solicited except as an allowable cost under other contracts as provided in subsection 31.205-18, Bid and proposal costs, of the FAR. (b) Responses will be treated as information only. It shall not be used as a proposal. (c) This solicitation is issued for the purpose of obtaining knowledge and information for project planning purposes only.
- Web Link
-
FBO.gov Permalink
(https://www.fbo.gov/notices/68b62553a7c681ec7d29d6d6ee14b91e)
- Place of Performance
- Address: ACC-RSA-FT EUSTIS - (SPS), Building 401, Lee Boulevard Fort Eustis VA
- Zip Code: 23604-5577
- Zip Code: 23604-5577
- Record
- SN03142807-W 20130810/130809000019-68b62553a7c681ec7d29d6d6ee14b91e (fbodaily.com)
- Source
-
FedBizOpps Link to This Notice
(may not be valid after Archive Date)
| FSG Index | This Issue's Index | Today's FBO Daily Index Page |