This is a request for information (RFI) only, as defined in FAR 15.201(e). It does not constitute a Request for Proposal (RFP) or a promise to issue an RFP in the future. Responses to this notice shall not be construed as offers and cannot be accepted by the government to form a binding contract. The U.S. government will not pay for any information or administrative cost incurred in response to this RFI. All costs associated with responding to this RFI will be solely at the interested partys expense. Not responding to this RFI will not preclude participation in any future RFP, if issued. The release of Product ManagerForce Protection Systems (PM-FPS) documentation is limited to United States corporations and United States citizens. The information provided herein is subject to change and in no way binds the government to solicit for or award a competitive contract.
The Product ManagerForce Protection Systems (PM-FPS), under the Joint Program Manager Guardian and Joint Program Executive Officer for Chemical and Biological Defense, provides affordable, modular, scalable and supportable tactical force protection capabilities to forward deployed forces while simultaneously providing state of the art physical security equipment to Army installations worldwide. In execution of this responsibility PM-FPS is seeking to leverage recent experiments and technology demonstrations to establish the Integrated Ground Security, Surveillance and Response Capability (IGSSR-C) program to produce uncluttered, accurate, and actionable, near real time (NRT) status and warnings for display on a Common Operational Picture (COP).
Historically, equipment and systems procured for physical security of military installations have operated independently, requiring numerous operators to monitor the situation. The lack of a common environment and integrated display also inhibits the full potential of wide area surveillance with overlapping sensor coverage, especially in high-threat environments. Technology risk reduction in systems integration, data fusion, and automation have demonstrated the feasibility of producing a system that allows operators to focus more on responding to threats and less on equipment and data management.
The United States Army Research Development and Engineering Command (RDECOM), on behalf of PM-FPS, is seeking qualified business candidates, capable of building a security system that provides data fusion capability, automates selected functions, integrates advanced sensors using standard schema, and interfaces with legacy sensors and other existing force protection equipment. A functional description of the desired capability is detailed in the attached document. RFI responses will be reviewed, with other information, in forming the IGSSR-C acquisition strategy with emphasis on possibilities for acquiring data fusion and automation capabilities. The review of responses is not for the purpose of narrowing down to one source or to eliminate sources.
Interested parties are requested to provide an information package consisting of:
Company Profile - not to exceed one page, including point-of-contact, and summary performance history. If citing contracts, please focus primarily on DoD contracts and identify the customer, contract number, and total dollar value. Also identify whether the company participated as the prime contractor or a subcontractor. Identify company qualification for any of the following categories: Competitive 8(a), HUBZone, Emerging Small Business, Partial Small Business, Total Small Business, Veteran-Owned Small Business, and Service-Disabled Veteran-Owned Small Business. Identify the companys CMMI certifications, if any.
Capabilities Statement - not to exceed five pages, single-spaced, minimum 12-point Times New Roman (or equivalent), describing corporate experience working with the Department of Defense (DoD) Enterprise Architecture and DoD Architecture Framework. Describe experience with interoperability testing and certification for both classified and unclassified networks. Describe experience integrating disparate systems and technologies into a single, integrated, family of systems. Describe experience with decision support systems, data correlation/fusion, and operational displays employing geographical information systems.
Description of Products Available - through the company, not to exceed one-half page per product, single spaced, minimum 12-point Times New Roman (or equivalent), that support one or more of the functions identified in the functional description and that could be integrated into an enterprise system. Identify the basic functions the product performs, interface standards, current uses, and any major test events or demonstrations at which it received an evaluation or assessment. For software not previously delivered to the government or delivered only with limited data rights, identify any constraints on government procurement of restricted data rights (FAR 52.227-14, Alternate III).
Respondents are urged to limit marketing material in order to provide more substantive information in their response. The government will not review any pages beyond the limits stated for each section or information including appendices, marketing brochures, catalogs, etc. The Army will evaluate the responses to help identify interest and the ability of the vendor community to provide support in the areas outlined in this RFI. All information received in response to this notice will be marked PROPRIETARY and handled accordingly. Proprietary information will be safeguarded in accordance with applicable government regulations.
1. Operational Employment. IGSSR-C should enable a layered approach to security and force protection operations in the Fixed Site and Semi-Fixed Site/Expeditionary Operational Environments throughout the full spectrum of operations. The system should minimize additional logistics and support requirements at these operating locations, which are often constrained for such basic services as electrical power, space, environmental conditioning, and network access. The system should not increase the number of operators required to perform FP functions.
2. Incremental design. The IGSSR-C acquisition strategy reflects incremental development to allow early deployment of an initial capability. At least two increments follow to add new capability as additional resources are secured and lengthy testing and certifications can be completed. Potential increments are:
a. Increment 1. Includes integration of FP sensors and sub-systems with fusion and automation enhancements to create an accurate FP COP, improve situational awareness, and enable a quick, precise response. Includes net-ready interoperability capabilities.
b. Increment 2. Adds interoperability with tactical, classified networks and systems. Improves CBRN integration using CBRN Common Systems Interface (CCSI). Adds additional fusion capabilities to improve situational awareness.
c. Increment 3. Additional fusion capabilities to include enemy Course of Action (COA) prediction and friendly COA analysis and recommendation. Adds enhancements to Consequence Management capabilities
3. Standards. Security Equipment Integration Working Group (SEIWG) Interface Control Document (ICD) 0100 series and Chemical, Biological, Radiological, and Nuclear (CBRN) Common Systems Interface (CCSI) are the newest standards for exchange of security-related sensor data and control information.
4. Data. IGSSR-C should support both the standard XML schema for exchange of sensor data and proprietary interfaces for many legacy sensors. The latter may require adapters to translate proprietary formats into XML. Sensor types may include cameras, radar, gunfire location, tripwire, fence line, and point detection of magnetic, seismic, acoustic, electro-optical, chemical, and radiological signatures. Most sensors process these signatures into object information (e.g., detection of a vehicle, person, or chemical) and do not report raw signature data. Other data may include locations of friendly forces, terrain features, barriers, roads, defended assets, etc., as well as information stores of adversary and friendly capabilities.
5. Control. IGSSR-C should support the standard XML schema for exchange of control information. This should allow simultaneous control of multiple remote equipment items, by either operator command or automated procedures. Many legacy equipment items may require adapters to translate proprietary formats into and from XML. Examples of remote equipment include unmanned vehicles, unattended sensors, remotely-operated weapons, and point-tilt-zoom cameras. Each instance of IGSSR-C should allow multiple controls, which can be individually configured for different watch stations, and should resolve contention among operators and automated procedures for control of individual remote equipment items.
6. Interoperability. To facilitate data exchange and communication with other FP C2 and information systems, IGSSR-C must comply with Global Information Grid (GIG) technical guidance and DOD Information Assurance requirements including availability, integrity, authentication, confidentiality, and non-repudiation. It must complete interoperability testing and certification in accordance with CJCSI 6212.01E, Interoperability and Supportability of Information Technology and National Security Systems. IGSSR-C must also comply with Net Centric Data Strategy, Net Centric Services Strategy, and the principles and rules identified in the DoD Information Enterprise Architecture to facilitate enterprise ownership and sharing of data.
7. Automation. IGSSR-C should automate tasks to reduce operator workload. Rules for automation should be tailorable for each instance of IGSSR-C to best suit local conditions. Automation examples include selecting and focusing cameras on point sensor detections, movement of unmanned vehicles to pre-determined overwatch positions, system-generated messages and warnings, and display management based on priority of sensor detections for a particular situation such as change in Force Protection Condition.
8. Fusion. IGSSR-C should fuse multiple information sources, as described by JDL fusion levels 1, 2 and 3, to provide improved assessments of individual objects, situation, and threat. Systems administrators will be able to apply the fusion rules best suited to the local conditions. Examples of level 1 fusion include suppression of sensor activations from friendly activity, correlation of multiple detections of the same entity into one, and discrimination of friendly and hostile gunfire by correlating gunfire detection with friendly force locations. An example of level 2 fusion is prediction of an adversarys path based on a sequence of point detections and terrain. An example of level 3 fusion is recommendation of a defensive action based on an estimate of an adversarys intent and the resources available to respond.
9. Common Operational Picture (COP). IGSSR-C should include a Force Protection(FP) COP which can use a variety of map terrain backgrounds and be able to distribute data to populate IGSSR-C system information, detections, and warnings on other FP COP systems. The COP should include FP Asset locations and nodes, sensor activations, graphics and control measures, and BLUFOR element locations and tracking. The COP should be tailorable, enabling individual operators to display only information relevant to their duties.
10. Displays. . In addition to the COP Situational Awareness display, the system should show camera views and access and display forms, references, checklists, and report formats. The system should support desktop and mobile laptop monitors for all display requirements. Displays should allow windowing. Each instance of IGSSR-C should support multiple displays which can be individually configured for different watch stations.
11. Scalability. IGSSR-C should be scalable, modular and tailorable to support an indeterminate number of attached sensors and remotely operated equipment over a variable geographic area. The system will be capable of interoperating with displays for other IGSSR-C instances at adjacent commands.
INSTRUCTIONS FOR RESPONDANTS
Submit requested information by e-mail:
Deadline for submission is 4:00 PM EST, July 28, 2010.
Formats should be viewable in Microsoft Word 2007 or Adobe Reader 9.
No telephonic discussions will be held.
Set-aside code: N/A
Place of performance:
RDECOM Contracting Center - Natick R&D (RDECOM-CC) ATTN: AMSRD-ACC-N, Natick Contracting Division (R and BaseOPS), Building 1, Kansas Street Natick MA
Contact: Bruce MacFarlane, 407-208-5604
" target="blank"> Link To Document
Email: RDECOM Contracting Center - Natick R&D (RDECOM-CC) (email@example.com)
Updated on 2010/07/13