RFI for Combat Air Forces (CAF) Advanced Live Operational Training (ALOT)

Request for Information: This request for information (RFI) constitutes neither a Request for Proposal or an Invitation for Bid. It does not restrict the Government to an ultimate acquisition approach. This RFI should not be construed as a commitment by the Government for any purpose. THIS IS NOT A SOLICITATION; this is an RFI only in accordance with Federal Acquisition Regulation (FAR) 52.215-3 - Request for Information or Solicitation for Planning Purposes (Oct 1997). This RFI is issued solely for information and planning purposes. It does not constitute a Request for Proposal (RFP) or a guarantee to issue an RFP in the future. This RFI does not commit the Government to contract for any supply or service whatsoever. The Government is interested in applicable vendor demonstration of technologies and systems (Technology Readiness Level (TRL) 3, 4, 5, 6, 7, 8, or 9 as defined at: http://www.acq.osd.mil/ddre/publications/docs/TRA2011.pdf , pages 2-13 and 2-14). Interested parties are encouraged to respond to this RFI. The Government will not pay for information, materials, and/or demonstrations received in response to this RFI and is in no way obligated by any information received. - 1. Background and Scope: AFLCMC/XZ: The Program Development and Integration Directorate, headquartered at Wright-Patterson AFB, with Operating Locations at multiple locations executes Development Planning (DP) and early acquisition and integrated systems assessments in support of emerging warfighter requirements. AFLCMC/XZ performs rigorous early systems engineering, cost estimating, early acquisition protection and modeling, and simulation and analysis. AFLCMC/XZ is the single AFLCMC point of entry for MAJCOM Core Function Lead Integrators (CFLIs). AFLCMC/XZ works closely with the CFLIs to complete concept development studies and trade space analyses across the aerospace, weapons, and C2ISR domains in order to launch high-confidence, sustainable programs. As weapon systems have become increasingly complex, so have the environments in which they are expected to operate. The global development and proliferation of technologies that pose a credible threat to 5th Generation aircraft have created the desire to analyze ways in which aircrews can effectively train by engaging in Advanced Live Operational Training (ALOT). The ALOT capability will use constructive entities injected into airborne training participants to replicate the anticipated complex threat environment and maximize live training effectiveness with consideration to expansion to include virtual entities. Initially, ALOT will include Live aircraft and Constructive elements with consideration to expansion to include virtual entities. ALOT is anticipated to eventually evolve beyond the scope of this RFI and integrate with other CAF weapon systems and virtual training opportunities in Distributed Mission Operations (DMO) to create a Live, Virtual and Constructive Operational Training environment (LVC OT). The ALOT system, or system of systems, is expected to include three major components: (1) a Source of Constructive Injects (e.g., Ground-based, Airborne, Lead Ship) with a capability to generate a Common Operating Picture (COP), including constructive entities (2) a waveform to pass COP information to all training participants, and (3) an aircraft capability that would translate the COE information into aircraft-specific useable information. The COP will operate with Government Furnished Equipment standards. The resultant Training System must operate with GFE standards and provide for individualized, group and team training environments. The COP must be capable of incorporating live, virtual, and constructive environments, including local and distributed training, throughout the training continuum. The COP must be interoperable with USAF, USMC, and USN distributed mission training capability implementation. The COP must provide a continuous learning environment for aircrew and maintainers including briefing, debriefing, mission planning, and mission task rehearsal. The COP must integrate self-assessment tools that provide feedback to the user and input to the training management system. The resultant Training System must provide for individualized, group, and team training environments. The COP must be capable of incorporating live and constructive environments (with expansion capabilities to include virtual entities) including local and distributed training throughout the training continuum. The COP must provide a continuous learning environment including briefing, debriefing, mission planning, and mission task rehearsal. The COP must integrate self-assessment tools that provide feedback to the user and input to the training management system. - 2. Capability Requirements: The purpose of this RFI is to determine existing and emerging Developmental, Commercial-off-the Shelf (COTS), or Government-off -the-shelf (GOTS) technology solutions to address a source or sources of constructive injects capable of generating a COP and the Live Operational Training scenario. This component(s) is expected to include, but is not limited to, the ability to: Generate constructive threats with sufficient realism to enhance the training of 5th Gen fighter pilots Generate and manage constructive blue and red forces as well as white and gray constructive entities Manage live blue and red forces Manage the timing and spatial representation of all entities, both live and constructive, including all observable state changes State change estimation (e.g. dead reckoning) to mitigate latency and synchronization issues Extensible to accommodate a range of training scenarios from one-on-one engagements to large force exercises involving many different weapon systems For the purpose of this RFI, the government is interested in information associated with a capability to generate a COP for a live operational training scenario (full systems, sub-systems, components, sensors, etc.) and a system of systems architecture for the ALOT capability. Any technology development effort that falls within a TRL designation of three through nine is of interest under this RFI. The RFI response should also indicate the use of the GFE waveform or a specific waveform that a respondent would like to include in their response. Cost information requested should accompany and /or be associated with the technical input provided. The Government prefer that any proposed systems or subsystems submitted within the RFI is accompanied with a Cost Element Structure (CES) or Work Breakdown Structure (WBS); refer to MilStd Handbook 881C to better understand the level of information requested for each element addressed. Within the responses, please highlight if these systems and/or components have been used by the government before. Submission should include the ground rules and assumptions used to derive such estimates; if actual (vice estimates) data is provided, please notate whether cost information comes from a DCAA approved (therefore certified) accounting system. It is important to understand how the cost estimates are derived; please include any applicable cost and risk drivers for the parameters given. All technical and descriptive information is welcomed to include size, weight, power requirements of proposed system, estimated Source Lines of Code (SLOC) of Effort, Software Integration efforts. For each software module proposed, please describe the technical approach to fulfill the functional requirements. Explain whether the approach is to use new code, reuse code, apply a COTS/GOTS solution, or any combination thereof. Please quantify combinations with percentages. Also, describe the current maturity of the solution, or parts of the solution, in common metrics, such as Technology Readiness Level (TRL). Please characterize magnitude and complexity of the required software; requesting estimate of the software size by Computer Software Configuration Item (CSCI) in Source Lines of Code (SLOC). When providing the software sizing estimate, provide the software language that will be used, as well as, percentage new software, percentage modified software, percentage reused software, and percentage auto-code software. If the approach assumes use of Off-the-Shelf (OTS) software, please provide an estimate of the licensing fees and integration cost required. In addition, any insight into the fuel and/or energy implication of your system (e.g. power, cooling), how you envision system operations, and logistical footprint required for the system is also welcomed. Each RFI response should include a roadmap identifying the timeline for technology development. - 3. Instructions to Potential Respondents: This is NOT a Request for Proposal. Interested vendors who desire to participate in this market survey and demonstration event are encouraged to submit white papers that demonstrate they presently have the concepts, technology, and qualifications to satisfy the capability requirements as described above. White papers should be prepared in Microsoft Word format using 1-inch margins and font size not less than 11pt. An example white paper format is attached. White papers for each technology should be no more than 10 pages in length and should address at a minimum the following topics: - Discuss how the technology addresses the capability requirement - Discuss limitations the vendor foresees with the use of their technology White papers should discuss their technologies (TRL 3, 4, 5, 6, 7, 8, or 9) and, as applicable, discuss the ability to produce, deliver, and sustain existing technologies (TRL 7, 8, or 9). A rough order magnitude (ROM) of unit cost is desirable. White papers should indicate if the proposed technology has been sold or licensed to the US Government and/or any other organization or if it has been tested by a DoD Agency or independent third party. Papers should include relevant points of contact for each organization. The white paper should indicate if the technology was developed under a Small Business Innovation Research (SBIR), Small Business Technology Transfer (STTR), or other government-funded contract vehicle and declare details of the effort including the contract number and funding amount. RESPONSES ARE DUE 13 APRIL 2015 at 03:00 PM EST. White papers should be submitted electronically to Mr. Jonathan Fredrick and Mr. Dallas Strawsburg via email at Jonathan.Fredrick.2@us.af.mil and Dallas.Strawsburg@us.af.mil. Responses shall include the following information: 1. Company/Institute name 2. Address 3. Point of Contact 4. Cage Code 5. DUNS Number 6. Phone Number 7. E-mail Address 8. Web page URL 9. All prospective contractors must be registered in the System for Award Management (SAM) database to be awarded a DoD contract. The North American Industry Classification System (NAICS) Code for this action is 334511, size standard 750 employees. Based on the NAICS Code, state whether your company qualifies as a: a. Small Business (Yes/No) b. Woman Owned Small Business (Yes/No) c. Small Disadvantaged Business (Yes/No) d. 8(a) Certified (Yes/No) e. HUB Zone Certified (Yes/No) f. Veteran Owned Small Business (Yes/No) g. Service Disabled Small Business (Yes/No) h. Economically Disadvantaged Women-Owned Small Business (Yes/No) i. Statement as to whether your company is domestically or foreign owned (if foreign owned, please indicate country of ownership). j. Provide prospective small business utilization percentages (if the acquisition is not set- aside for small business) Companies may be contacted if we need further information to fully understand the marketplace. AFLCMC/XZ is not at this time seeking proposals, and will not accept unsolicited proposals. Responders are advised that the US Government will not pay for any information or administrative cost incurred in response to this RFI. Please be advised that all submissions become Government property and will not be returned. All costs associated with responding to this RFI will be solely at the responding party's expense. Not responding to this RFI does not preclude participation in any future RFP, if any is issued. Small Businesses are encouraged to provide responses to this RFI in order to assist AFLCMC in determining potential levels of competition available in the industry, as well as helping to establish a basis for developing any subsequent potential subcontract plan goal percentages. The acquisition strategy is still being determined. Market research results will assist the Air Force in determining whether this requirement will be a full and open, a small business set aside, or a sole source acquisition. If it is a small business set-aside, FAR 52.219-14, Limitations on Subcontracting will apply. Therefore, small businesses that want to be considered for a small business set-aside should demonstrate how they could comply. If there is sufficient demonstrated interest and capability among small business contractors, a key factor in determining if an acquisition will be a Small Business Set-Aside is that two or more potential small business prime contractors must be capable of performing at least 50% of the effort, as defined in FAR 52.219-14, Limitations on Subcontracting. If it is determined that a small business set-aside is appropriate, and your company anticipates submitting a proposal as the prime contractor for a small business set-aside, please provide specific details and rationale as to how compliance with FAR 52.219-14 would be achieved, including specific details regarding teaming arrangements, etc. If subcontracts are to be used, provide anticipated percentage of effort to be subcontracted and whether small or large businesses will be used. Teaming and/or subcontracting arrangements should be clearly delineated and previous experience in teaming must be provided. If this effort is not set-aside for small business, small business utilization will be considered. Large and small businesses should provide a reasonable expectation for small business utilization as a percent of total contract value as well as supporting rationale for the recommended percentage. In accordance with FAR 15.201(e), responses to this notice are not offers and cannot be accepted by the US Government to form a binding contract. It is the responsibility of the interested parties to monitor the FedBizOpps (FBO) site for additional information pertaining to this RFI. Respondents should indicate which portions of their responses are proprietary and should mark them accordingly. All information received in response to this RFI that is properly marked as "proprietary" will be handled accordingly. Proprietary information must be clearly marked on the outside container and on the materials inside. The Government shall not be liable for, or suffer any consequential damages, for any proprietary information not properly identified. Interested parties shall be responsible for any costs associated with preparing responses to this market research and demonstrating their technologies. Vendors that submit white papers that demonstrate viable ALOT ground-based capabilities to enable or enhance ALOT ground-based capabilities may be invited to participate in one or more events to demonstrate their technologies. Specific information regarding technology demonstration events will be based on the number of white papers received and technologies selected for demonstration. The Government reserves the right to not conduct technology demonstrations. All requests for further information must be made in writing or via email. Telephone requests for additional information will not be honored. All questions and answers regarding this RFI will be posted as updates to this notice. The Government reserves the right to not address questions received after 27 March 2015.