Armored Multi-Purpose Vehicle (AMPV) Part Task Trainer (PTT)

****Please visit the TReX RFS website for additional information, at: https://nstxl.org/opportunity/family-of-maintenance-trainers-product-line-fmt-pl-armored-multi-purpose-vehicle-ampv-part-task-trainer-ptt/ Request for Solutions Family of Maintenance Trainers (FMT) Product Line Armored Multi-Purpose Vehicle (AMPV) Part Task Trainer (PTT) 13 March 2020 1. Purpose and Authority This Request for Solutions (RFS) is issued to identify and select capable vendors with the ability to develop an Armored Multi-Purpose Vehicle (AMPV) Part Task Trainer (PTT). The PTT will be incorporated into and extend the existing Family of Maintenance Trainers (FMT) Product Line (PL) and will therefore, utilize and build upon the FMT-CC DTT PL architecture including the FMT-CC TMS, FMT-CC IOS, Network Attached Storage (NAS), and FMT-CC User Interfaces (UI). The purpose of this effort is to analyze existing FMT-Common Core (FMT-CC) architecture, baseline, design documentation, and the AMPV requirements in order to develop and successfully demonstrate a prototype trainer with troubleshooting lessons for the new AMPV PTT which utilizes the FMT-Common Core (FMT-CC) architecture. The AMPV PTT includes the power pack (including the Cummins VTA903E-T675 engine and the L-3 HMPT-800 transmission), the driver's compartment and all interfaces with the power pack. The AMPV PTT Prototype project is unclassified but will require the utilization of technical data/information. The RFS scope is limited to the development of the FMT PL AMPV PTT prototype demonstration unit and a study for a mobile configuration. The FMT PL Diagnostic/Troubleshooting Trainers (DTT), Part Task Trainers, and Hands-On-Trainers (HOT) include shared components such as the Training Management System (TMS) and Instructor Operator Station (IOS). Any information regarding other variants of maintenance training systems is provided for FMT PL shared components, PL compliance, and reference only. The Government will evaluate the solutions with the intent of awarding an Other Transaction Agreement (OTA) in accordance with 10 U.S. Code - 2371b. 2. Summary and Background 2.1 Overview The FMT-CC PL standardizes the Army's vehicle maintenance trainers with a common core architecture, software baseline, and common equipment. The FMT-CC DTT PL effort established the CC architecture and baseline which will be used on all FMT PL trainers (DTTs, HOTs, and PTTs). FMT-CC PL includes, but is not limited to the Stryker, Abrams, AMPV, and Joint Light Tactical Vehicle (JLTV) maintenance trainers. 2.1.1 Legacy Maintenance Trainers This section describes the general system level architecture of legacy Army maintenance training systems. Prototypes developed under this OTA shall satisfy the requirements and provide the capabilities identified in the Technical Supplement (TS), FMT-CC design documentation, and this RFS. Legacy maintenance trainers are comprised of three (3) distinct classes of devices: DTTs, PTTs, and HOTs. These systems provide Military Occupational Specialty (MOS) skill level development for system operation, fault diagnosis, troubleshooting, adjustments, component removal/replacement, and other servicing and repair tasks for the respective vehicles. Each of these variants, targets specific training goals but share common training elements. The DTTs are computer based system simulations; no actual physical vehicle hardware is employed. Navigation and interaction with the DTTs is handled via keyboard, mouse, and touchscreen inputs. The PTT and HOT trainers integrate virtual training with physical hardware. In the case of the PTT, a specific subsystem, such as the brakes or engine, is targeted, and realistic (fabricated or Government Furnished Equipment (GFE) components of that system are instrumented to be an active part of the emulation. There are a few existing legacy HOTs which are not instrumented, for example: the Bradley A2 HOT and the Abrams SEP V2 HOT. The HOT expands upon the PTT concept. The hardware in a HOT is part of a more completely integrated environment that may contain more than one subsystem. The HOT is instrumented in the same manner as the PTT, with the hardware interacting with the virtual software simulation. In all classes, the legacy trainers are comprised of an Instructor Operators Station (IOS) and one or more student workstations (SWS). In addition, a TMS provides record storage and classroom management utilities. The IOS, SWSs, and TMS are connected by an Ethernet or wireless network and high-speed switches. In the case of the PTTs and HOTs, the SWSs are connected by hardware linkage to additional Input/Outputs (I/O) used to instrument the physical representations of the specific device trainers. The IOS controls the simulation state and the behavior of the simulation. The SWSs run the actual models that provide the virtual trainer capabilities. The PTT IOS has a similar software package as the DTT but the lessons are focused on interaction with actual vehicle components or components that approximate the real vehicle with high fidelity. 2.1.1.1 Software Real-Time software includes the software models that simulate the vehicle systems and the executive software which controls the iteration rate of the simulation and schedules the models to run at the appropriate frequencies. The IOS software provides control of the simulation, to include: freeze, lockstep, lesson plan control, and communication control. The TMS software provides support for: classroom management functions, student record archiving and lesson plan maintenance. The Display and Control software is the interface between the student's or instructor's actions at a display and the effect it has on the simulation. In addition to the simulation software, a Software Support Environment (SSE) provides the resources for performing post deployment software support activities, including identifying, documenting, and correcting system software faults, implementing system software upgrades, managing databases, and providing configuration management. 2.1.2 Common Software Baseline Historically, although the current trainers have common classifications of software within a variant (i.e., within vehicle types), there was no commonality between platforms (e.g. Abrams, Stryker). Each variant's software architecture and source code is unique and stove-piped. The Army is in the process of establishing a FMT-CC software baseline to replace the current stove-piped software architecture with a common product line architecture which completely supports the entire FMT PL. This first effort established the CC baseline using the DTT. The FMT-CC PL includes a set of plug-and-play applications that are applicable across the FMT product portfolio of legacy and future combat/tactical vehicle training systems without a loss of current functionality. The FMT CC DTT design documentation is not complete but is expected to be mature at the time of agreement award. This effort will utilize that CC baseline and ensure maintenance lessons are incorporated into the AMPV PTT as part of the PL. While the instantiation of the FMT-CC PL was started with the DTT development, in support of the DoD objective to rapidly acquire quality products in an evolutionary approach, further improvements to the CC PL are desired (including new technology insertion) and should be proposed for the AMPV PTT. The FMT-CC vehicle specific software, assets, digital information, and documentation will reside on the Live Training Transformation (LT2) portal. The LT2 portal is an Army repository for data and standards for the live training community created under the Consolidated Product Line Management (CPM) Next contract. Information uploaded by the vendor onto the LT2 portal may be available to other contractors/vendors on a need-to-know basis to perform work for the Army. The vendor shall provide a plan that documents a path to conformance to the LT2 Product Line Operations and Configuration Management (CM) Guide and existing FMT-CC documentation. The LT2 portal and guides are located at https://www.lt2portal.mil. A Common Access Card (CAC) is required to access this portal. For potential vendors without CACs, the LT2 Product Line Operations and CM Guide is being provided as Government Furnished Information (GFI). All software code developed with this effort and with the FMT-CC DTT resides in the Independent Development Environment (IDE) portion of the LT2 portal. Access to the IDE requires a secret clearance. If a vendor does not have someone with a secret clearance to access the portal, alternate methods can be made by the Government. However, the vendor must include its need for alternate methods of access within the solution. 3.0 Training and Readiness Accelerator (TReX) Vendors interested in responding to this RFS must be members of TReX or teamed with a TReX member. Information about membership can be found at the following webpage: https://nstxl.org/membership/. This project will be managed by the U.S. Army Program Executive Office for Simulation, Training, and Instrumentation (PEO STRI), Project Manager Soldier Training (PM ST), Product Manager Virtual Training Systems (PdM VTS). **** Please visit the TReX RFS website for additional information, at: https://nstxl.org/opportunity/family-of-maintenance-trainers-product-line-fmt-pl-armored-multi-purpose-vehicle-ampv-part-task-trainer-ptt/****