Future Combat Systems FCS Home Boeing Home Integrated Defense Systems FCS Home Boeing Home SAIC Phantom Works home

Survivability System

BIA Number: 15712

Pricing Information
The Program anticipates a funding level of up to $100,000 for the contract award(s) resulting from this BIA.

Detailed Description of Effort and Task
The FCS Survivability System will be comprised of several common Survivability Subsystems that are used across the FCS ground platforms. The Survivability Subsystems may be tailored for each vehicle type, and they may, or may not, be installed on each type. Submissions covering only some of the subsystems detailed below may be considered at a reduced subcontract value. Partial submissions must cover an entire subsystem area to receive consideration.

All components will be based on an open system architecture and facilitate block upgrades spiral development throughout the life of the vehicle.

Initial subsystem requirements and architecture will be provided at the start of the contract.

The following technology areas define the subsystems making up the platform survivability system:

  1. Add-on or appliqué armor
    This armor will provide additional protection over the inherent ballistic protection in the vehicle hull. It will be field-installable (e.g. tiles or panels) over the vehicle hull, and may include passive or active solutions.

  2. Countermeasures and active protection
    This subsystem includes active countermeasures that intercept incoming threat weapons (i.e. active protection systems), provide visible, NIR, IR, RF, or acoustic jamming of threat sensors, decoy incoming threat weapons (visible, NIR, IR, RF, or acoustic), or provide visible, NIR, IR, or RF obscuration either locally or at range from the target vehicle.

  3. Sensors
    These sensors will provide passive and active threat detection and environment sensing functions. Sensors capable of operating in the visible, NIR, IR, RF, acoustic, and magnetic bands are desired. Both single-use and multiple use sensors are sought, as are single-spectrum and multi-spectrum systems. Sensor fusion capabilities or systems otherwise capable of performing more than one function, or in more than one spectrum are desirable. Threat detection should include one or more of the following capabilities: detection of weapon firing or launch, in-flight weapons, mines, threat sensor systems, threat vehicles, etc. Environment sensors should provide data regarding the immediate vehicle environment, such as ground conditions, background or foreground clutter, ambient lighting, temperature, humidity, local surroundings, etc.

  4. Signature management
    This subsystem will provide detection avoidance capabilities within the visible, NIR, infrared, radar, acoustic, electronic, and magnetic signature bands.

  5. Vulnerability reduction
    The vulnerability reduction subsystem may include items such as vulnerability analysis, redundant capability specifications, fire suppression mechanism, critical item identification and protection, etc.

  6. Survivability processor
    The survivability processor will integrate, manage, deploy, or apply the other survivability subsystems and perform threat identification and characterization, saliency, immediacy, and response/consequence assessment calculations. It will coordinate and/or perform other survivability subsystem processing functions and derive local environment data from onboard or off-board sensors. It will provide an interface to the Integrated Vehicle Health Management System, which includes platform and crew condition and status sensing, and diagnostic/prognostic/anomaly sensing and reporting capabilities.

Task 1
Define subsystem hardware/software design requirements capable of meeting the performance and interface requirements provided by the LSI. Support refinement to the subsystem performance and interface requirements.

Task 2
Provide subsystem level functional schematics.

Task 3
Provide 3D CAD Envelope Models and 2D layouts of Envelope Models/Layouts of the preferred subsystem arrangements for the major subsystem elements sufficient to define subsystem-to-vehicle interfaces and to show compliance with interface requirements. Provide 3D CAD envelope model datasets to be either PRO Engineer version 2001 or CATIA V4. If not available in either of these CAD formats, a STEP format file shall be submitted. 2D layouts to be contractor CAD dataset format and one 36" wide paper plot.

Task 4
Provide simulation models of subsystem performance to support vehicle performance simulation assessments such as:

  • Simulation models from the appropriate codes to simulate subsystem performance within a given technology area.
  • Simulations in the contractor software development environment.
  • EASY5 or MATLAB/Simulink for subsystem level analyses.
  • DADS for Dynamic Mechanical Systems & Mechanisms Analysis.

Task 5
Provide ROM Subsystem-Level Reliability Assessment

Task 6
Provide preliminary repair/maintenance concepts associated with subsystem design.

Task 7
Provide description of the critical subsystem failure modes.

Task 8
Provide SDD Test and Evaluation roadmap for the subsystem elements necessary to validate simulation models and verify subsystem performance and RAM-D requirements.

Task 9
Provide subsystem attribute sensitivity (e.g., weight, volume, power, cooling, aperture size, mounting requirements) to potential growth in subsystem performance requirements as specified by the LSI.

Task 10
Provide a fabrication concept that addresses building and assembling the subsystem components in sufficient detail to support manufacturing plan development.

Task 11
Offeror shall support SDD WBS development.

Schedule Duration of on-site support

  1. Weekly Telecons to report Schedule Status, Accomplishments, Significant Findings/Conclusions/Recommendations, Problems with mitigation plans, integration issues needing resolution, etc.
  2. Three 2 day meetings held in Seattle

Initial Coordination Meeting - 10/7/02
Interim Coordination Meeting - 10/31/02
Interim Coordination Meeting - 12/02/02

Schedule Milestones
Subcontract Start Date - 10/7/02
Subcontract Completion Date - 12/16/02

Data Requirements
Initial input - 10/31/02
Final input - 12/02/02
Revised Input - 12/16/02

Deliverables

10/14/02

  1. Issues/concerns with initial subsystem requirements and interfaces provided by the LSI
  2. Top (potential) integration issues that need resolution with vehicle integrators
  3. Top system risk areas

10/21/02

  1. Initial hardware/software functional schematics

10/31/02

  1. Initial system report which includes results from tasks 1, 2, 4 (gross performance estimates), 9, and 10.
  2. CAD models from task 3.

11/22/02

  1. Issues/concerns with updated subsystem requirements and ICD provided by the LSI
  2. Top (potential) integration issues
  3. Subsystem risk areas update

12/02/02

  1. Final system report which includes status results from tasks 1, 2, 4 (initial performance models), 5, 6, 7, 8, 9, and 10.
  2. CAD models from task 3.

12/16/02

Revised system report which includes status results from tasks 1, 2, 4 (performance models), , 5, 6, 7, 8, and 9.

CAD models from task 3.

Evaluation Criteria
Supplier proposal will be evaluated in each of the broad categories listed below. Each category is allocated a maximum page count for consideration. Each category must be addressed by the proposal. The sub-bullets are intended to provide insight into the key areas of interest for each category. Proposal submittals shall address these areas as well as others that demonstrate significant category expertise that demonstrate capability to execute the statement of work.

Technical Approach (8-page (24,000-character) limit):

  • Approach to survivability subsystem(s) design interface with platform concept
  • Approach to developing concepts into preliminary design with evolving requirements
  • Approach to multi-platform design commonality
  • Approach to assess technology readiness for integration into platform subsystem design
  • Approach to spiral upgrade development and implementation

Understanding of the Technical Challenges (4-page (12,000-character) limit)

  • Identification of top technology challenges
  • Identification of top integration challenges
  • Identification of top supportability challenges
  • Identification of top reliability issues
  • Plan and processes for execution of the above statement of work.

Key Program Challenge Mitigation Plans (3-page (9,000-character) limit)

  • Mitigation plan to address identified technology, integration, and supportability challenges.
  • Risk management approach/process
  • Weight management approach/process