Modeling, Simulation and Integration (MS&I) 2014
Department of the Air Force, Air Force Materiel Command | Published October 24, 2014 - Deadline December 10, 2014
SECTION I: SYNOPSIS
THIS REQUEST FOR INFORMATION (RFI) IS FOR INFORMATION AND PLANNING PURPOSE ONLY. This a Government Market Research effort in accordance with Federal Acquisition Regulations (FAR) Part Ten (10) and Far Part Fifteen (15) "Contracting by Negotiation". This synopsis does not constitute a Request for Proposal (RFP) or an Invitation for Bids (IFB), nor does its issuance in any way restrict the Government as to its ultimate acquisition approach. The Government will neither award a contract solely on the basis of this notice, nor will it reimburse the contractor for any costs associated with preparing or submitting a response to this notice. Any information provided by the Government at this time is preliminary and may be updated or changed prior to a formal release of an RFP (if any is issued).
This action falls under NAICS code 511330 with a size standard of $38.5M. Under this NAICS code, please specify if you are a Small Business, Small Disadvantaged Small Business, Section 8a Small Business, Woman-owned Small Business and Service Disabled Veteran-owned Small Business or HubZone Small Business. Please indicate all that apply.
The purpose of this RFI is to determine industry availability of Contractor facility to perform Modeling, Simulation and Integration (MS&I) work at a multi-level classified environment. The facility must be capable of performing medium to high fidelity virtual real-time simulations, with both manned and digital simulations, across multiple scenario environments supporting Integrated Air and Missile Defense (IAMD) objectives. MS&I activities will be directed by the Government sponsor. The simulation capabilities at the contractor facility must address components of the Department of Defense's (DoD) current and future kill-chain architectures for IAMD.
The Contractor shall plan, implement, execute and maintain a multi-service security environment to support the classified MS&I development and demonstration activity.A. Program Security: The Prime Contractor shall establish, implement and maintain program security in accordance with a contract DD254 and subsequent delivery order DD254(s). This shall include the management of personnel, documentation, Automated Information Systems (AIS), facility controls, and all subcontractors. The Contractor shall also provide security technical documentation to ensure contract compliance. The Contractor shall flow down these security requirements to the appropriate subcontractors through established relationships.
B. Technical Support: The Contractor shall provide expertise and support to develop integrate maintain, demonstrate and analyze the performance of kill-chain weapon systems within the contractor facility, both for existing and future system capabilities. Individual weapon system models may be Government-provided through associate relationships with development contractors. Government-provided models will be Distributed Interactive Simulation (DIS) compliant. The Contactor shall provide the simulation environment and the network architecture to support real-time, virtual exercise events that accommodates DIS compliant models. The simulation environment shall include selected unmanned and manned system models (both hardware and software components) in addition to providing the operating environment for the manned systems. The simulation environment may support distributed, multi-level operations with other virtual facilities.
The Contractor shall provide a simulation environment that supports multi-level secure operation to allow systems to function at its unique security levels while maintaining the integrity of system-specific information. The simulation environment should be capable of, and approved for, distributed operations with other virtual facilities which may be at their own unique security levels.
The contactor shall have primary responsibility for implementation of Government-provided scenarios (both blue and red force) based on event requirements. The Contractor shall also provide the capability to collect, store and distribute data for each demonstration, integration and test event, and provide that data to the Government sponsor. Data collected will be from the Government sponsored test event and used for stakeholder decisions.
C. Integration and Test Events: The Contractor shall support technical integration meetings as well as simulation integration and test events as designated by the Government. The Contractor shall incorporate, update and manage the schedule for Government activities, and shall coordinate with the government concerning schedule conflicts or facility issues. For planning purposes, the Contractor should be prepared to support 4-6 simulation events annually. Each event is typically one week and is normally preceded by 2-3 dedicated integration test weeks spaced over a 1-2 month timeframe. The facility and environment should be prepared to support 50-60 manned entities, 500-1000 non-manned entities, and Government-provided threat data or models. The threat environment must support air-breathing, missile, and surface and ground-based air defenses.
D. Facilities. See MS_I2014 RFI Facilities description attachment.
SECTION II: QUESTIONS FOR POTENTIAL RESPONDERS:
1. Does your facility currently support virtual simulation events? If so, what simulation protocols are employed (e.g., Distributed Interactive Simulation, High Level Architecture)?
2. What experience does your facility have with virtual, operator in the loop simulation events? How many events have you held? Have you hosted or participated in any DoD simulation events or exercises? If so, when did these events take place, what events did you participate in, and what was your level of involvement?
3. Does your facility currently have a Special Access Program (SAP) Facility? If so, how many rooms are available and what is the associated square footage?
4. Does your facility have Sensitive Compartmented Information (SCI) spaces (i.e., a SCI Facility)? If so, how many rooms are available and what is the associated square footage?
5. Do you currently conduct modeling for Ballistic Missile Defense (BMD)? If so, what capabilities are modeled?
6. Do you currently model Electronic Warfare (EW) effects? If so, what types of EW effects are modeled? Do you have plans to expand your EW modeling?
7. Do you currently model offensive and/or defensive cyber effects?
8. Do you currently model IR sensors and weapons? What environmental factors are considered?
9. What visualization and analysis tools can your facility provide (e.g. replay, simulation executing monitoring, top-level summary statistics, survey / comment collection, etc.)?
10. What is the internal process by which facility utilization is managed? What is your management approach to accommodating multiple customers and any internal company requirements?
11. How many of your current facility employees maintain SECRET or TOP SECRET clearances? How many of each?
12. How many operators, support personnel, and visitors can your facility support during an event?
13. What does your facility offer for briefings/debriefings and for high level meetings and discussions?
14. What is your ability to expand if more space/people are needed?
15. Can your facility currently support concurrent multi-level security (MLS) events? What networks are available for distributed, MLS operations? If so, how many concurrent events can you support and at what security levels? For example, can your facility execute a simulation in "Area A" at a particular security level and simultaneously operate a second simulation in "Area B" at a different security level? Also, within any given simulation event, do you have the ability to have multiple operators each operating at their own security level? For example, can you allow the F-15C operators and F-22 operators, both participating in the same event, to view information at a security level common to their platforms?
16. What system representations do you currently model within your facility? Are they currently integrated into your simulation environment? What is the level of fidelity for each representation?
17. What sensor systems are included in the system models (Infrared (IR) Radio Frequency (RF), Radar Warning Receiver (RWR), Identification, Friend or Foe (IFF), other)?
18. Do you model Electronic Attack (EA) and/or Electronic Protection (EP) capabilities? If so, which systems include EA/EP? How is EA/EP modeled from a simulation perspective? Have these EA/EP capabilities been validated or approved? By whom?
19. What functionality is included for multi-role systems such as Patriot and Aegis? Do you model aircraft, cruise missiles, ballistic missiles, and unmanned threats?
20. How are missile models integrated with host combat systems (air, ground, sea)?
21. Have models been validated? What is the approval process for these representations? Are threat system representations traceable to approved Intelligence Community models and/or data?
22. How do you model behavior for unmanned systems (scripted only, logic-based reactions, etc.)?
23. What threat Integrated Air Defense Systems (IADS) capabilities are modeled (surface, land, sea)?
24. What digital data links are modeled and at what level of fidelity? Specifically, do you currently model Link-16? If so, what simulation standard do you follow for Link-16 message exchange? Is propagation modeled? Is EA modeled? Can you model both red and blue networks concurrently?
25. Do you model voice communications? If so, how? Do you have chat capability? How flexible are both the voice communications and chat capabilities to accommodate different communications plans? Are the radios attached to specific entities? Is propagation modeled? Is EA represented?
26. What environmental factors are addressed and at what level (e.g. terrain, weather, electronic environment)?
27. Can you ensure the following combat systems (either constructive or operator-manned) are currently integrated to participate in events, with or without EA/EP: F-15C, F-15E, E-3, CRC, Aggressors, Cyber, F-22, F-35, TPS-59, TPS-80, EA-18G, F-18E/F, E-2D, CEC, Aegis, THAAD, Army Ground-Based Air Defense (GBAD) (i.e., Patriot, Sentinel and Multi-Mission Launcher)? How many can you have ready by 1 April 2016?
28. Can your facility be fully capable of executing a simulation, which includes the previously mentioned models, by 1 May 2016?
SECTION III: POINTS OF CONTACT:
Questions related to various aspects of this RFI may be e-mailed to: AFLCMC.HNJJ.HNJJ-MS-RFI@us.af.mil.
The Government requests that interested businesses submit a capability package via e-mail to the following address: AFLCMC.HNJJ.HNJJ-MS-RFI@us.af.mil.
Questions regarding this RFI will be answered during an Industry Day to be held in Crystal City, VA on 24 Nov 2014. If you plan to attend the Industry day, you must reply (RSVP), via phone, to Ms. Karen McCord at 781-225-9682 no later than 4:00 PM Eastern Time on 7 Nov 2014. Please include the number of attendees. Meeting time and location will be provided upon your request. The Industry Day is planned as a plenary event. Depending on the number of attendees, we may or may not have time for private side sessions.
Responses to this RFI must be submitted no later than 4:00 PM Eastern Time 10 Dec 2014 and should not exceed 25 one-sided pages, 8.5" x 11" white paper with font no smaller than 10 pitch with a minimum of one (1) inch margins. Be advised that all submissions become Government property and will not be returned.
The Government and Government-directed FFRDC and contractor personnel may evaluate all received responses. The Government shall appropriately protect company proprietary information as described 41 USC 423.