W15QKN16X05OQ_Attachment_001.xlsx
XLSX spreadsheet 15 KB Posted
- Attached to
- Single Net Solution/Remote Deployment Device
- Solicitation number
- W15QKN-16-X-05OQ
About this file
SNS/RDD Capability Question and Answer Sheet
View the file
Other files
| File | Type | Posted |
|---|---|---|
| SNS-RDD_NDA_Template.docx | DOCX document | |
| DD2345.pdf | ||
| SNS-RDD_NDA_Template.docx | DOCX document | |
| AMSTA-AR-1350.docx | DOCX document |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Sheet1
| Para | Requirement | Question | Answer | Description - Explanation - Evidence | ||
| 3.5.1 | Transformation and activation methods | How does the system deploy in front of a targeted vehicle? | ||||
| Is the system capable of transformation (be reconfigured) | Remotely | Yes | ||||
| from the standby mode (letting vehicles pass) to the capture mode (denying access)? | Manually | No | ||||
| 3.5.1.1 | Remote connection method | When deployed at a checkpoint or vehicle access point, can the system be hard wired to a device for remote activation? | ||||
| 3.5.2 | Remote device | Can the remote device be activated by either hand or foot? | Yes | |||
| No | ||||||
| 3.5.2.1 | Remote device readiness and availability | Is the remote device able to enable activation and provide a visual indication of readiness? | NA | |||
| 3.5.3 | Power supplies | How is the proposed solution powered? | ||||
| Is the system power supply self-contained? | ||||||
| Does the system rely on an external power source? | ||||||
| Is the system power supply single User replaceable? | ||||||
| 3.5.3.1 | Battery types | If batteries are used as a power source, are they commercially available or military common? | ||||
| 3.5.3.2 | Battery life | When batteries are used as a power source, are they capable of operating for 25 system activations and deployments before requiring recharge or replacement? | ||||
| 3.5.4 | System Portability | How was the system designed to address Portability? | ||||
| 3.5.4.1 | System element portability | Will the proposed system meet the requirement of MIL-STD-1427 in that the weight and size of the heaviest & largest non-divisible system element (unpackaged and packaged) be portable by no more than two (2) Soldiers? | ||||
| 3.5.4.2 | System portability | Is the total system portable for setup and transport by no more than two (2) soldiers per MIL-STD-1472? | ||||
| 3.5.5 | System transportability | What are the external dimensions (footprint) of the complete system in the transportation configuration? | ||||
| 3.6.1, 3.8.2 | Climate, storage and transportation | What is the system shelf-life and service life (number of deployments) and are there any restrictions on storage or operation? | ||||
| Can the system be stored & operated in all climactic categories, Hot, Basic & Cold as defined in AR 70-38? | ||||||
| 3.6.2 | Chemical resistance. | Address capability of proposed system to resist the effects of chemicals, fluids, and vapors that may occur in a military operational environments. | ||||
| 3.7.1 | Primary Capability | What are the vehicle weight and speed limitations of your vehicle stopping system? | ||||
| 3.7.2.1 | Deployment positioning | Can the system (in the stand-by mode) be setup on either side of the roadway/entry point and activated in the vehicle travel path to the capture mode? | ||||
| 3.7.2.2 | Deployment activation standoff | What is the maximum standoff distance in (meters) enabling system transformation from standby to capture mode? | ||||
| 3.7.2.3 | Deployment speed | How long does in take (in seconds) for the System to transform from the standby mode to the capture mode? | ||||
| 3.7.2.4 | Mode cycling | Can the system deploy no less than 25 times cycling between stand-by mode, capture mode, and then stand-by mode without affecting system availability? | ||||
| 3.7.2.5 | Installation and setup | Can the system be setup from the storage configuration by 2 Users in less than 15 minutes? | ||||
| 3.7.2.6 | Recovery. | Can the system be recovered from both the stand-by mode and capture mode to the packaged configuration by no more than two (2) Soldiers within 15 minutes? | ||||
| 3.7.3.1 | Vehicle reversal prevention | Can the system provide entanglement to prevent vehicle reversal out of a capture? | ||||
| 3.7.4 | Lane coverage | What is the lane coverage of your system in feet? | ||||
| 3.7.5 | Delivered force | Will the proposed system meet the peek force requirement of less than 3-g deceleration delivered to seat belted vehicle occupants? | ||||
| 3.7.6, 3.8.7 | Safety | Describe steps/methodology for mitigation of safety risks to operator/User during maintenance, transportation, handling, setup and recovery, including the use of nonflammable and nontoxic materials. | ||||
| 3.7.7 | Overt/covert employment | Can the system be deployed overtly (clearly visible to approaching vehicles) and covertly? | ||||
| 3.7.8 | Detachment | Does the system capture apparatus (portion of the system that stops a vehicle) separate from the deployment system within 10 feet from point of vehicle engagement? | ||||
| 3.8.1 | Reliability | Describe any test results concerning probability of capture for your system. Include types of vehicles, number of tests and successful captures. | ||||
| 3.8.3.1 | Maintenance | Describe the maintenance plan and any supporting documentation that currently exists for the proposed system. | ||||
| 3.8.3.2 | Maintenance Plan | Does the maintenance plan incorporate current Army doctrine of two-level maintenance (Field/Sustainment) in accordance with Army DA PAM 750- 1, Commanders’ Maintenance Handbook? | ||||
| 3.8.4 | Preventive maintenance checks & services (PMCS). | Describe preventive maintenance procedures, estimate frequency and duration for 2 trained Users to complete. | ||||
| 3.8.5 | Operational Availability | Describe any efforts to determine Operational Availability and results* for the proposed system, including testing, modeling & simulation, etc. | ||||
| 3.8.6 | Production Traceability | Does the proposed system meet the requirement for threshold ($5000) for unique serialization to identify systems in accordance with DFARS 2.11.274 Item unique Identification and Valuation Requirements? | ||||
| Describe the organization's process for identifying systems and production lot numbers for traceability in the event of a defect discovered after delivery. | ||||||
| M2 VLAD Compatibiilty | Can your system be made compatible with, i.e. deploy an M2 VLAD? |
*the degree (expressed as a decimal between 0 and 1, or the percentage equivalent) to which one can expect a piece of equipment or weapon system to work properly when it is required, that is, the percent of time the equipment or weapon system is available for use
File details come from the government source that posted it. Updated .