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

Warfighter Machine Interface -Common Crew Station & WMI Software Layer

BIA Number: 15716

Pricing Information
The Program anticipates a funding level of up to $95,000 for the contract award(s) related to the common crew station tasks and $50,000 for each award related to WMI software architecture tasks.

Detailed Description of Effort and Task
The Warfighter Machine Interface (WMI) consists of two major components, a Common Crew Station and the WMI Layer of the software architecture. The WMI Software Layer is an integral part of the FCS Software Architecture that integrates the FCS warfighter's visualization and interaction needs for data and services across all manned ground vehicles and associated off-vehicle equipment. The Common Crew Station is a common subsystem for all manned ground vehicles. The WMI concept must also be extended to control unmanned vehicles and non-developmental vehicles. The Common Crew Station comprises hardware and software for speech I/O, helmet-mounted displays, multifunction head-down displays, multiple control options, seating, workspace and accommodations, storage, and human-computer interface equipment associated with the crew and dismounts as well as both embedded or off vehicle interfaces for Dismounted Soldiers, C4ISR, Training, and Supportability.

All components will be based on an open system architecture and facilitate block upgrades and spiral development throughout the life of the system and associated FCS platforms and equipment. A key characteristic will be the ability to separate the WMI Software Layer provided to the FCS warfighter from the generation of data and services within the underlying applications. System requirements and architecture will be provided at the start of the contract.

The WMI component integrator(s) shall assist the LSI in establishing innovative concepts and defining, developing, and documenting the WMI architecture, hardware and software requirements. Effort also will support the integration of the WMI hardware and software with the FCS platform computing architecture, so that the resulting system has common look and feel for displays and controls. Note: The common computing architecture / Vetronics architecture development are outside the scope of this BIA although harmonization will be required with the groups doing that work.

A human centered design process should be applied to establish the necessary WMI requirements. Consideration should be given to defining and using a common, perhaps natural language, front-end to provide a crew command language that operates across FCS vehicle types and command stations. Processes need to be defined which consider both short and long term impacts of use and integration of COTS/MOTS technology, open systems architecture, technology migration and insertion, and/or Pre-Planned Product Improvements (P3I). Rapid prototyping and/or spiral development processes and lessons learned should also be considered.

Some of the services for which the WMI must provide an interface include:

Dismounted Soldier

  • An interface must be provided to allow teleoperation of the vehicle up to a specified distance
  • Situation awareness for the dismounted soldier to include appropriate access to C2 and/or C4ISR services such as COP/CROP

Platform/Vehicle

  • Control and performance/health monitoring of vehicle systems & sensors
  • Control and operation of mobility systems
  • Autonomous operation of unmanned vehicles/platforms and, in some cases, of manned vehicles/platforms (this includes mobility, mission and information control of unmanned systems)
  • Control and operation of weapons systems
  • Control and operation of self-protections systems
  • Control and operation of specialized mission systems not covered elsewhere
  • Awareness of threats, cautions, and warnings not covered elsewhere
  • Communication, Sensor fusion, decision aids, database management, track fusion not covered elsewhere

Command & Control

  • Presentation and interaction with mission planning data and services
  • Presentation and interaction with mission preparation data and services
  • Presentation and interaction with mission execution data and services
  • Presentation and interaction with mission assessment data and services
  • Presentation and interaction with mission alert data and services
  • Brokered access to vehicle/platform systems for C2 usage
  • C2 interface to C4ISR, UAV/UGV operation, and other off-vehicle entities
  • C2 interfaces to legacy applications for interoperability

C4ISR

  • Access to and communication with C4ISR functions
  • Control and operation of C4ISR specialized mission systems
  • Awareness of C4ISR threats, cautions, and warnings
  • Brokered access to vehicle/platform systems for C4ISR usage
  • Communication, Sensor fusion, decision aids, database management, information management, information assurance, ISR, and track fusion .

Training

  • Embedded and external training systems

Supportability

  • Embedded and external supportability systems

Specific Tasks
For the purpose of this BIA, tasks 1-5 are associated with the WMI software layer component, and tasks 6-18 are associated with the Common Crew Station. Proposers must clearly identify which tasks they are proposing to perform in their submittals.

Task 1
Analyze FCS System software architecture and data and services interface requirements for WMI layer design requirements and architecture. Identify applicable derived WMI requirements based on historical lessons learned, subject matter expert interviews, human engineering databases, usability design guidelines, and task analyses.

Task 2
Assist LSI in the assessment of WMI software visualization and interaction method concepts and technologies and make recommendation for incorporation into FCS architecture and specifications.

Task 3
Assist LSI in the synthesis of WMI requirements and allocation to selected software control and display method concepts.

Task 4
Assist LSI in writing the WMI Software architecture, design and interface description, specification, and ROM cost models. The LSI will provide a preliminary version of these documents and specification for augmentation by the supplier.

Task 5
Define a recommended WMI software development approach and planning parameters to support PDR readiness 30 days after start of SDD. Provide an initial WMI software engineering and development plan appropriate for SDD, including applicable processes, standards, metrics, and risk assessment and mitigation.

Task 6
Define Common Crew Station hardware/software design definition capable of meeting the performance and interface requirements provided by the LSI. A Crew Station WBS should be developed, with common components and variant specific components.

Task 7
Provide Common Crew Station subsystem-level functional schematics

Task 8
Provide CAD Envelope Models/Layout of all system elements sufficient to define subsystem-to-vehicle and human-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 9
Review and revise available human performance analyses.

Task 10
Contribute in the development of risk mitigation plans and strategies for SDD.

Task 11
Contribute in the establishment of Common Crew Station metrics and processes, including past project lessons learned.

Task 12
Recommend Common Crew Station component, subsystem, and system interface definitions.

Task 13
Provide ROM Subsystem-Level Reliability Assessment

Task 14
Provide preliminary repair/maintenance concepts associated with Common Crew Station design.

Task 15
Provide description of the critical subsystem failure modes; support definition of safety hazards, hazard causes, and hazard mitigations.

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

Task 17
Provide subsystem attribute sensitivity (i.e., weight, volume, power, cooling) to potential growth in subsystem performance requirements as specified by the LSI.

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

Task 19
Offeror shall support SDD WBS development.

Meeting 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, WA or Long Beach, CA
  3. Possibly support demonstrations or lab evaluations, as needed

Schedule Milestones
Subcontract Start Date - 10/9/02
Initial Coordination Meeting - 10/9/02
Interim Coordination Meeting - 10/31/02
Interim Coordination Meeting - 12/02/02
Subcontract Completion Date - 12/16/02

Data Requirements

Contractor format

Deliverables Tasks 1-5

The due dates shall be:
Initial Draft 11/01/02;
Final Draft 11/27/02

  1. Warfighter Machine Interface (WMI) Software Architecture, Design and Interface Description that identifies relationship between WMI and vetronics and C4ISR architecture
  2. Warfighter Machine Interface (WMI) Software Specification.
  3. Warfighter Machine Interface (WMI) Software ROM cost models .
  4. Warfighter Machine Interface (WMI) Software Engineering and Development Plan for SDD.

Deliverables Tasks 6-18

10/14/02

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

10/21/02

  1. Initial hardware/software functional schematics

10/31/02

  1. Initial report which includes results from tasks 6, 7, 9, 11, and 17.
  2. CAD models from task 8.

11/22/02

  1. Issues/concerns with updated Common Crew Station requirements and interface requirements provided by the LSI
  2. Top (potential) integration issues
  3. Common Crew Station risk areas update

12/02/02

  1. Final report which includes status results from all Common Crew Station tasks.
  2. CAD models from task 8.

12/16/02

  1. Revised report which includes status results from all Common Crew Station tasks.
  2. CAD models from task 8.

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 (7-page (21,000-character) limit):

  • Approach to interface hardware and software design into 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
  • Approach to human-centered design.

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