FMT RFP Attachment 01 BASE SOW 25 NOV 24.pdf

25 November 2024

SOW-2024-041

Distribution Statement A. Approved for public release: distribution is unlimited.

BASE STATEMENT OF WORK (SOW)

FOR THE

FAMILY OF MAINTENANCE TRAINERS (FMT)

PRODUCT LINE (PL)

ID/IQ

U.S. Army Program Executive Office Simulation, Training, and Instrumentation (PEO STRI)

12211 Science Drive Orlando, FL 32826-3276

Approved by

Product Director Virtual Training Systems (PD VTS)

Page ii

TABLE OF CONTENTS

1 SCOPE

1.1 OBJECTIVES

1.2 BACKGROUND

2 REFERENCE DOCUMENTS

2.1 GOVERNMENT DOCUMENTS

2.2 NON-GOVERNMENT DOCUMENTS

3 REQUIREMENTS

3.1 PROGRAM MANAGEMENT

3.1.1 Contractor Work Breakdown Structure (CWBS)

3.1.2 Integrated Master Plan (IMP)

3.1.3 Integrated Master Schedule (IMS)

3.1.4 Monthly Status Report (MSR)

3.1.5 Contractor Manpower Reporting

3.1.6 Risk Management

3.1.7 Subcontractor Management

3.1.8 Associate Contractor Agreements

3.1.9 Obsolescence Management

3.1.10 Financial Management

3.1.11 Reviews and Meetings

3.1.12 Data Rights

3.1.13 Government Furnished Information (GFI)

3.1.14 Government Furnished Property (GFP)

3.1.15 Organizational Conflicts of Interest (OCI)

3.2 CONFIGURATION MANAGEMENT (CM)

3.2.1 Training Device Configuration Control Board (CCB)

3.2.2 Common Core CCB

3.2.3 Engineering Change Proposals (ECP) & Variances

3.2.4 Software and Hardware Item Database

3.3 INTEGRATED DIGITAL ENVIRONMENT (IDE)

3.3.1 IDE Capabilities

3.3.2 IDE Administration

3.3.3 IDE Data Management

3.3.4 IDE Data Base Maintenance

3.4 SYSTEMS ENGINEERING

3.4.1 System Design

3.4.2 Hardware Engineering

Page iii

3.4.3 Software Engineering

3.4.4 System Integration

3.4.5 Standardization

3.4.6 Reliability, Availability and Maintainability (RAM) Engineering

3.4.7 Producibility Engineering

3.4.8 Quality Engineering

3.4.9 Human Factors Engineering

3.4.10 Electromagnetic Environmental Effects (E3)

3.4.11 Contaminate and Corrosion Control

3.4.12 Product Definition Data (PDD)

3.4.13 Facility Engineering

3.5 CYBERSECURITY (CS)

3.6 LOGISTICS

3.6.1 Logistics Product Data (LPD)

3.6.2 Materiel Components List (MCL)

3.6.3 TADSS Cataloging Report

3.6.4 Initial Spares List

3.6.5 Special Tools Test and Test Equipment

3.6.6 Obsolescence Management Planning (OMP)

3.6.7 Technical Publications (TP)

3.6.8 Item Unique Identification (IUID)

3.6.9 Software Support Environment

3.6.10 Training and Training Products

3.6.11 Training System Support

3.7 PROGRAM SECURITY

3.7.1 Protection Policy & Procedures

3.7.2 Access to Government Information Systems

3.7.3 Common Access Card (CAC) Policy

3.7.4 Performance or Delivery in a Foreign Country

3.7.5 Facility Clearance Level (FCL)

3.7.6 Security Training

3.7.7 Remanence Security

3.8 ENVIRONMENT, SAFETY, AND OCCUPATIONAL HEALTH (ESOH)

3.8.1 Safety Engineering

3.9 SITE RELATED ACTIVITIES

3.9.1 Site Survey

3.9.2 Site Preparation

3.9.3 Installation Tools and Test Equipment

3.9.4 Installation Spares

Page iv

3.9.5 Removal of Equipment

3.9.6 FMS Considerations

3.10 DATA DELIVERABLES

3.11 QUALITY ASSURANCE (QA)

3.11.1 Quality Control

3.11.2 Quality Assurance Surveillance Program (QASP)

3.11.3 Qualification And Test

3.12 DELIVERY ORDER SPECIFIC REQUIREMENTS

APPENDIX A: REPRESENTATIVE DATA DELIVERABLES

Page v

REVISION HISTORY

Revision Number Date List and Description of Changes

1.0 25 NOV 2024 Initial Release

1 SCOPE

Product Director Virtual Training Systems (PD VTS) has a requirement for technology refresh, concurrency upgrades, development, and production of maintenance training simulation systems that provide institutional and operational unit maintenance training.

This document establishes the scope for the Family of Maintenance Trainers (FMT) Product Line (PL) Indefinite Delivery, Indefinite Quantity (ID/IQ) contract. The requirements defined herein establish the scope of tasks, products, and services that may be acquired through program-specific Delivery Orders (DOs). The training system tasks include analysis, design, development, production, installation, integration, test, concurrency upgrades, technology refresh, trainer modifications, skills sustainment, cybersecurity, and instruction. Training system performance parameters will be defined by requirements unique to each platform and system specific mission training needs. Detailed requirements for existing and new training systems in the PL will be thoroughly documented in requirements documents, specifications, and Statement of Work (SOW) as part of each individual

DO.

The FMT PL training systems shall provide initial familiarization training, skills progression, and skills sustainment training that fulfill maintenance training requirements for military platforms. The FMT PL systems shall provide capabilities that allow students to become familiar with maintenance of the tactical platform and its components, including sensors, switches, weapons systems, engines, mechanical components, software, and Line Replaceable Units (LRU), as specified in each DO.

The FMT PL ID/IQ contract will cover all maintenance training systems and products procured or supported by PEO STRI.

The FMT PL ID/IQ contract may be utilized to support Foreign Military Sales (FMS) through the PEO STRI Project Lead International Programs Office (PL IPO).

1.1 OBJECTIVES

The FMT PL contract facilitates the development, evolution, and maturity of the products and capabilities across the entire life cycle of all FMT PL training systems. The FMT PL contract will ensure program relevancy via a consolidated, streamlined approach that protects, leverages, and matures the FMT PL investment while supporting US Army modernization efforts. The FMT PL contract will provide efficient, effective, and agile processes to accomplish required maintenance training system acquisition and sustainment tasks. The FMT PL contract will facilitate the following objectives:

a) Elimination of duplication across development and sustainment efforts

b) Managing the configuration of hardware and software baselines

c) Maximizing reuse and commonality of subsystems to include:

1) Virtual training environment hardware and software

2) Models, special effects, and animations

3) Aural and visual cues

4) Training Task List (TTLs)

5) Training Management System (TMS)

6) Network Attached Storage (NAS)

7) Instructor/Operator software and interface

8) Input/Output (I/O) subsystem

9) Common Software Libraries (CSL)

10) Computational and networking hardware

d) Use of a consistent set of tools and processes across the FMT PL DOs

e) Maintaining standardization and concurrency of Operating Systems across the PL

f) Achieving and maintaining Authorities to Operate (ATO) for PL training systems through the RMF process

g) Managing the purchase, grant, or lease of FMT PL articles or services by a country or international organization through the PEO STRI Project Lead International Programs Office (PL IPO) Foreign Military Sales (FMS) group.

An objective of the FMT PL ID/IQ is to integrate new technologies across existing legacy systems’ computational components, optimize development, production, obsolescence planning, performance, and operational readiness of new systems while reducing total ownership costs of existing systems. It is the objective of the contract to develop a hardware and software solution for the FMT PL that maximizes standardization, commonality, and core asset reuse of current products and system components across platforms. This effort will include dynamic mechanisms for multi-phase configuration management, development, support, and growth of all FMT PL training systems.

The FMT PL contract will support the core business goals of PD VTS, including:

a) Standardizing configuration management

b) Managing product tools & methodologies

c) Capturing and analyzing engineering & management metrics

d) Reducing development cost & complexity

e) Integrating innovative technologies

f) Implementing common standards and interfaces

g) Reducing life cycle support costs

h) Establishing and standardizing a governance process whereby PD VTS business processes for the FMT PL are designed, executed, monitored, and improved

i) Cooperating and collaborating with PEO STRI Foreign Military Sales (FMS) programs

j) Promoting small business participation in PEO STRI contracts

The Contractor shall provide efficient, effective, and agile processes to accomplish development, production, fielding, tech refresh, obsolescence management, concurrency upgrades, sustainment, and disposal of legacy, obsolete hardware as needed for FMT PL training systems. The requirements defined herein shall form the basis for all work performed as part of the DOs the Government will issue under the FMT PL ID/IQ multi-award contract. Each individual DO SOW will define the work to be accomplished and the products and data to be delivered during the DO period of performance.

The general categories of work to be performed include, but are not limited to:

a) Technology Refresh The Contractor shall design, procure, develop, fabricate, integrate, test, validate, deliver, and install technology refreshes on existing FMT PL systems. Technology refresh efforts shall conform to all Cybersecurity (CS) requirements. Technology Refresh shall utilize the latest version of Common

Core software (e.g., GUI, CSL, TMS). Hardware and Software designs shall meet or exceed all requirements identified in the individual FMT PL DO SOW and specifications.

b) Training Products As specified in individual DOs, the Contractor shall provide training solutions including, but not limited to, training materials, training devices, product data and documentation, operational equipment, instructors, support systems, operations and maintenance services, and support personnel.

These products may include Diagnostic Troubleshooting Trainers (DTTs), Part Task Trainers (PTTs) Hands-On Trainers (HOTs), classroom equipment, auxiliary training material, and other hardware and software resources to support institutional, operational unit, and embedded on-platform maintenance training.

c) Design Concept, Prototype Development, and Production The Contractor shall design, procure, prototype, develop, fabricate, integrate, test, validate, deliver, and install new FMT PL training devices as defined in individual DO SOWs and requirements documentation. These efforts may include new simulator production, front end evaluations, technology/product evaluations, technology assessments and forecasts, training effectiveness evaluations, integrated risk assessments, tactical platform data evaluations, supportability analyses, cost and schedule estimates, and device/subsystem evaluation.

d) Concurrency Upgrades The Contractor shall design, procure, develop, fabricate, integrate, test, validate, deliver, and install upgrades to the existing FMT PL simulators to maintain concurrency with the tactical platform capabilities, as defined in individual DO SOWs and requirements documentation. Concurrency upgrades may require upgrading training systems and components to reflect the evolution of weapon system designs, employment, tactics, intelligence data, and maintenance procedures.

e) Risk Management Framework (RMF) As specified in the applicable DO, the Contractor shall support Government Risk Management Framework (RMF) and Cybersecurity (CS) efforts including Assess & Authorize, and Connectivity or Interconnectivity activities to certify or recertify FMT PL systems as required to obtain or maintain an Authority to Operate (ATO). This effort may include annual Federal Information Security Modernization Act (FISMA) reviews and RMF recertification as required by individual DOs. In addition, the Contractor shall establish accounts on the Government Enterprise Mission Assurance Support Service (eMASS) application and use the accounts to enter and manage RMF data for relevant DO training devices as directed by the Government representatives.

f) Contractor Logistics Support (CLS) As specified in individual DOs, the Contractor shall provide CLS on a full-time, on-site, or on-call basis. Training system operation and maintenance services may be included under the CLS umbrella.

Individual DOs may also require the Contractor to provide Interim Contractor Support (ICS) at fielding locations following Government Acceptance Testing. The scope and timing of ICS shall be subject to negotiation between the Government and the Contractor. During the specified ICS period of performance, the Contractor shall provide product support and management of site logistical operations until the system fully transitions to a Government designated CLS organization.

g) Upgrades and Modifications Upgrades and modifications to FMT PL devices may be required under the FMT PL ID/IQ contract.

Each individual DO shall provide detailed training system upgrade and modification requirements.

The Contractor may be required to develop, manage, and/or update a modification program schedule.

As specified in individual DOs, the Contractor shall upgrade training system hardware components due to parts obsolescence, technological advances, cybersecurity, or other evolving hardware requirements. Individual DOs may also require software modifications to include, but not limited to, Common Core baseline improvements, changes to training device lesson content, updates necessary to maintain Interactive Electronic Technical Manual (IETM) or platform concurrency, and to maintain the system Cybersecurity accreditation.

h) Training Enhancements Individual DOs may include training enhancements. Training enhancements refers to modification of FMT products and components required to enhance training capabilities. Such enhancements may include, but are not limited to, Instructor Operator Station (IOS) and Training Management System (TMS) upgrades, transfer of lessons to computer-based training (CBT) or multimedia presentations, cloud-based training, embedded training capabilities, remote instructor/Telemaintenance capabilities, and incorporation of new technologies such as extended reality (XR) (mixed reality, augmented reality, or virtual reality) and artificial intelligence. The Contractor shall explore integration of innovative solutions and transition technologies from laboratory environments into delivered simulation systems. Alternate design/development proposals shall be submitted to the Government for review. The implementation of any modification will require Government approval prior to implementation.

i) Instructional Services As specified in individual DOs, the Contractor shall provide a systematic Instructional System Development process for developing curriculum and courseware and providing instructional programs to ensure personnel are taught the knowledge, skills, and attitudes essential for successful job performance. The following is a potential list of tasks that may be required by individual DOs under the FMT PL ID/IQ contract: instruction/training, training management, curriculum and /or courseware development, multimedia studio, classroom equipment, training materials and training aids.

j) CC Updates and Configuration Management The Contractor shall develop and deliver updates to the FMT CC, to include software and technical data deliverables. The Contractor shall provide and maintain a software integration test bed and other engineering tools and laboratory equipment necessary to support the CC H/W and S/W baselines. The Contractor shall establish and utilize configuration management system and processes to maintain configuration control of the CC.

1.2 BACKGROUND

The U.S. Army Program Executive Office for Simulation, Training, and Instrumentation (PEO STRI), Product Director Virtual Training Systems (PD VTS) intends to procure, develop, retrofit, integrate, refresh, upgrade capabilities, test, field, and support Safety Confirmation and Risk Management Framework (RMF) processes for the FMT PL. The FMT PL provides institutional maintenance training systems and supports operational units with skills sustainment training. The objective efficiencies to be provided through this effort include hardware/software reuse and commonality, common architectures and standards, reduction of development and sustainment costs, acquisition and development streamlining, and inherent agility to react to platform changes. The FMT PL ID/IQ contract is key to meeting the Army’s maintenance training challenge.

The contract for FMT PL will utilize an ID/IQ multiple-award contract (MAC) approach in support of the requirements described in this SOW. PD VTS plans to manage, develop, sustain, and evolve the FMT PL assets under the FMT PL multi-award contract. This SOW defines the general requirements of the FMT PL contract. A SOW will define the detailed requirements to be accomplished under each DO to be awarded under the FMT PL contract.

PEO STRI, PD VTS plans to competitively award multiple FMT PL ID/IQ contracts to streamline and standardize maintenance training system acquisition and sustainment processes. Whether it is the acquisition or sustainment phase of a training system, emphasis remains on rapid delivery and optimized training system performance. To meet the challenge of executing an increasing number of programs with ever-changing technical challenges and technological advancements, the FMT PL contract will “pre-qualify” a pool of both large and small business contractors that can execute training system tasks.

Through Training Tasks Lists (TTLs) and Free play capabilities, the FMT PL systems shall provide familiarization and advanced training for soldiers’ skills critical for successfully maintaining military platform readiness. The FMT PL systems shall permit the Instructor/Operator (I/O) to monitor student’s mechanical skills and performance during lesson execution.

2 REFERENCE DOCUMENTS

Unless otherwise specified, the following documents and the version in effect on the date of the contract award form a part of this SOW to the extent specified herein. The intent of these lists is to identify only the documents referenced in this SOW. Not every document will necessarily be referenced within individual DO Performance Works Statements (SOW). Individual DOs may have additional reference documents unique to a specific program.

The Defense Security Cooperation Agency (DSCA) Manual 5105.38-M provides the general guidance for FMT FMS acquisitions. While all FAR and Defense FAR Supplement (DFARS) clauses apply to FMS procurements, Table C6.T1. of DSCA 5105.38-M lists selected sections with unique application to FMS that may have relevance for FMT PL ID/IQ acquisitions.

2.1 GOVERNMENT DOCUMENTS

Army Directive 2014-05 Policy and Implementation Procedures for CAC Credentialing and Installation Access for Uncleared Contractors

AR 25-2 Army Cybersecurity

AR 380-10 Foreign Disclosure and Contracts with Foreign Representatives https://www.acquisition.gov/dfars

AR 381-12 Threat Awareness and Reporting Program

AR 530-1 Operations Security

AR 702-20 Counterfeit Risk Management Product Assurance

DFARS 246.870 Contractors Counterfeit Electronic Part Detection and Avoidance

DFARS 252.225.7043 Antiterrorism/Force Protection for Defense Contractors outside the US

DFARS 252.239-7001 Information Assurance Contractor Training and Certification

DFARS 252.246-7007 Contractor Counterfeit Electronic Part Detection and Avoidance System

DODD 8140.01 Cyberspace Workforce Management

DODI 8500.01 Cybersecurity (CS)

DODI 8500.02 Identification, Tracking, and Reporting of Cyberspace Workforce Requirements

DODM 8140.03 Cyberspace Workforce Qualification & Management Program

DODI 8510.01 Risk Management Framework for DOD Information Technology

DOD 8570.01-M Information Assurance Workforce Improvement Program

DODI 8582.01 Security of Unclassified DOD Information on Non-DOD Info Systems

FAR clause 52.204-9 Personal Identity Verification of Contractor Personnel

FIPS 140-2 Federal Information Processing Standards (FIPS) Publication 140-2 Security Requirements for Cryptographic Modules

Version 4.4, 23 FEB 2024 Common Core (CC) Configuration Management (CM) Process

MIL-STD-31000B Technical Data Packages

2.2 NON-GOVERNMENT DOCUMENTS

ANSI/EIA-748 Earned Value Management

CNSSI 1253F Committee on National Security Systems Instruction (CNSSI)

ISO/IEC/IEEE15288 System Life Cycle Processes

NFPA 70

National Fire Protection Association (NFPA 70 National Electrical Code, 2017 Edition (Copies of this document are available from (http://www.nfpa.org/Catalog/) or National Fire Protection Association, 11 Tracy Drive, Avon, MA 02322)

NIST SP 800-53

National Institute of Standards and Technology (NIST) Special Publication (SP) 800-53: Security and Privacy Controls for Federal Information Systems and Organizations

NIST SP 800-171 Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations

ANSI-Z400.1

American National Standard for Hazardous Workplace Chemicals

– Hazard Evaluation and Safety Data Sheet and Precautionary Labeling Preparation

3 REQUIREMENTS

The following subsections contain high level descriptions of efforts that a Contractor may be required to perform during the execution of a DO under the FMT ID/IQ contract. Each awarded DO will include a SOW that stipulates whether each of the following SOW requirements is applicable for that DO. Each DO SOW may contain additional details or tailoring guidance for each applicable high-level requirement presented in this subsection of the SOW. The contractor shall notify the Government of any perceived conflicts between the requirements presented in this SOW and the requirements presented in a DO SOW.

3.1 PROGRAM MANAGEMENT

The Contractor shall provide all program management functions necessary to meet cost, schedule, and technical requirements specified in the relevant DO SOW and Specifications. This will include managing the development, acquisition, and sustainment of training systems. The Contractor shall develop and maintain a database to capture product support metrics. Tasks shall include, but are not limited to, evaluation of training requirements, leveraging innovative technologies and solutions to enhance capabilities/increase efficiencies/decrease costs, performing system designs and audits, participation in design and management reviews, risk management in accordance with (IAW) the Contractor’s Risk Management Plan (RMP), cost/schedule status tracking, configuration and data management activities, logistics planning, and sustainment activities as specified in individual DOs.

Individual DOs may also require Associate Contractor Agreements (ACAs). Details for the ACAs will be provided within each applicable DO.

The Contractor shall provide the overall management and administrative effort necessary to ensure the requirements of each awarded DO are accomplished. The Contractor shall track program progress utilizing metrics. The Contractor shall consider life cycle costs while conducting trade studies and evaluating design alternatives. The Contractor shall define and monitor metrics and Technical Performance Measures (TPMs) to evaluate each critical technical and management process and the conformance of evolving products with contractual requirements and objectives. The Contractor shall identify progress, issues, and status of the program. The Contractor shall identify problem areas and corrective actions required to eliminate or reduce schedule impacts. The Contractor shall, at a minimum, report the following:

a) Problems and solutions

b) Timelines and schedules

c) Plan of next month activities

d) Development and fabrication progress

e) Expenditures to date and cost projections

Data delivery requirements will be specified in a Contract Data Requirement List (CDRL) to be included with each DO.

3.1.1 Contractor Work Breakdown Structure (CWBS)

The Contractor shall utilize a CWBS that defines program tasks and the lower-level components of what is to be procured and includes all the product elements (hardware, software, data, or services), which are the Contractor’s responsibility. The CWBS shall serve as the framework for contract planning, budgeting, and reporting of cost and schedule status. The Contractor shall identify major elements of subcontracted work in the CWBS. The Contractor may propose changes to the CWBS to enhance its effectiveness in satisfying program objectives.

3.1.2 Integrated Master Plan (IMP)

The Contractor shall implement, manage, update, and maintain an IMP for each awarded DO. The Contractor shall develop the system in accordance with the IMP. The IMP shall be used throughout the contract as a management tool to assess progress and determine success in achieving program requirements. The Contractor shall report on work in progress in accordance with the IMP at each program review, at selected technical reviews, and at government discretion. The IMP shall utilize the CWBS as the basis for all program planning.

3.1.3 Integrated Master Schedule (IMS)

The Contractor shall develop, implement, manage, update, and maintain an IMS for each awarded DO. All contract schedule information delivered or presented at program reviews shall originate from the IMS, shall be traceable to the IMP, and shall contain all critical events and exit criteria, accomplishments, predecessors and successors events, and their dependencies. The IMS shall address total program activities including activities performed by major subcontractors. The IMS shall portray the sequence and relationship of activities corresponding to the DO CWBS. The IMS shall be implemented on a computer-based program management control system which utilizes critical path method network analysis, accepts parametric data input, and can be utilized to determine the status of the program progress. The program IMS data shall be updated to reflect accomplished activities and any resulting changes to the overall program plan and schedule. The Contractor shall conduct critical path analysis of the tasks and identify problem areas and corrective actions required to eliminate or reduce schedule impacts.

3.1.4 Monthly Status Report (MSR)

The Contractor shall provide an MSR that describes the status of each DO. The MSR shall include a summary of all work accomplished to date, all program activities for the period, a forecast of work to be accomplished during the upcoming six months, all work outstanding, and a schedule of all deliverables. The Contractor shall identify actions being taken to correct all schedule deficiencies.

All changes from previous MSRs shall be highlighted and explained. The Contractor shall report any problems requiring immediate action by the Government using the most expeditious means (phone or e-mail) and shall document the problem in the MSR.

3.1.5 Contractor Manpower Reporting

The Contractor shall report all contractor labor hours including subcontractor labor hours required for performance of services provided under individual DOs via a secure data collection site. The Contractor is required to complete all required data fields at https://www.sam.gov.

Reporting records will be for the labor executed during the period of performance for each Government Fiscal Year (FY), which runs 1 October through 30 September. Reporting of manpower may be submitted at any time during the FY. All data submitted shall occur no later than 31 October of each calendar year (CY). Contractors may direct questions to the System for Award Management (SAM) Help Desk.

3.1.6 Risk Management

The Contractor shall establish, implement, and maintain a risk management program to identify risks related to the DO project. The Contractor shall identify and track all risks and corrective actions required to mitigate the risks. The Contractor shall define and implement a risk assessment methodology that includes not only an understanding of cost, schedule, and performance impacts on risk areas, but also provides a periodic reassessment of these impacts on risk areas. The Contractor shall update, maintain, and execute program metrics to monitor issues and to determine the likelihood of risks occurring. The Contractor shall ensure that the risk management process is utilized to manage risks across all facets of the contract, including subcontractor activities.

3.1.6.1 Counterfeit Risk Management

As required by individual DO, the Contractor shall establish, implement, and maintain a counterfeit electronic part detection and avoidance system IAW DFARS 252.246-7007 to prevent procurement of counterfeit electronic parts or end items, components, parts, or assemblies that contain electronic parts. Failure to do so may result in disapproval of the purchasing system by the contracting officer and/or withholding of payments. In conjunction with this requirement, the Contractor shall adhere to DFARS 246.870-2 when procuring electronic parts or end items, components, parts, or assemblies that contain electronic parts.

3.1.7 Subcontractor Management

The Contractor shall manage and have agreements with subcontractors and partners as required. The Contractor shall integrate subcontractors and partners into program IPTs. The Contractor shall ensure the requirements of the contract apply to all subcontracts and associate contracts.

3.1.8 Associate Contractor Agreements

As required by individual DO, The Contractor shall enter into Associate Vendor/Contractor Agreements (ACA) for any portion of a DO requiring collaboration or joint participation in the https://www.sam.gov/ accomplishment of the Government’s requirement and achieving FMT PL goals. The ACA shall include the basis for sharing information, data, technical knowledge, expertise, and/or resources essential to accomplishing the DO tasks. The ACA shall be structured to facilitate the greatest degree of cooperation for the development and support of all maintenance trainers in accordance with the terms of the agreement. Associate contractors are those awarded a DO under the FMT PL ID/IQ which require collaboration or joint participation.

ACAs shall include the following general information:

1. Identify the associate vendors or contractors and their relationships.

2. Define the specific roles and responsibilities of each party to the agreement.

3. Identify the programs involved and the relevant Government agreement or contract of the parties to the ACA.

4. Identify arbitration processes to be followed for dispute resolution.

5. Specify the categories of information to be exchanged or support to be provided.

6. Identify timelines and guidelines for responding to requests for information or support.

7. Include the expiration date (or event) of the ACA.

8. Identify potential conflicts between relevant Government agreements or contracts and the

ACA, along with mitigation plans.

9. Include agreements on protection of proprietary data and restrictions on employees.

A copy of such agreement shall be provided to the Contracting Officer for review and approval before execution of the document by the cooperating vendors or contractors.

The vendor is not relieved of any contractual requirements or entitled to any adjustments to the contract terms because of a failure to resolve a disagreement with an associate contractor.

Liability for the improper disclosure of any proprietary data contained in or referenced by any ACA shall rest with the parties to the agreement, and not the Government.

All costs associated with the ACA are included in the negotiated cost of the applicable DO. ACAs may be amended at any time during the agreement period and a copy of each amendment shall be provided to the Contracting Officer for review.

ACA dispute resolution is the responsibility of the Contractors. The Contractor(s) shall notify the Government immediately whenever a dispute arises. If disputes are not resolved informally within 15 calendar days of initial notification, the Contractors shall immediately initiate formal arbitration proceedings (at their own expense). Contractors shall achieve resolution of disputes within 30 calendar days of initiating arbitration proceedings and shall provide a supporting written opinion from a neutral third-party arbitrator to the Government for review and recording in the contract file. During arbitration, the Contractor shall allow the Government access to mediators for the purpose of status updates and situational awareness.

The Government will include QASP requirements for meeting the terms of the ACA and meeting response and resolution timelines. The Contractor shall adhere to the collaborative performance requirements in the QASP for each DO requiring an ACA.

3.1.9 Obsolescence Management

The Contractor shall implement an obsolescence management program. The Contractor shall analyze and recommend solutions after identifying any obsolete parts. The recommended solution shall be reviewed and approved by the Government. The Contractor shall maintain awareness of end-of-life dates for components within their supported systems and notify the Government of anticipated obsolescence issues NLT six (6) months prior to its end-of-life date.

3.1.10 Financial Management

The Contractor shall maintain a financial management program that allows effective tracking of each project’s schedule and cost. The level of cost tracking required will vary depending on the type of contract utilized (i.e FFP vs COST). The scheduling management system shall provide for all specific work compatible with contract milestones and meaningful in terms of the technical and support requirements of the contract. The Contractor shall interface scheduling with other planning and control systems to the extent necessary for measurement and evaluation of contract status and submit schedules in a government standard format.

The Contractor shall plan, budget, schedule, and control the resources allocated to meet the requirements of the contract. The Contractor shall document and track the status of all appropriated funds associated with the contract to include payments, cancellations and invoices against each contract line item and subline item. The Contractor shall continually update an integrated database during contract performance with pertinent records and data that underlie and support the cost and schedule data reported.

3.1.10.1 Earned Value Management (EVM)

The Contractor shall develop, implement, maintain, and use an EVM system that complies with Industry Guidelines ANSI/EIA-748 and meets contractual requirements. The Contractor shall document the integrated cost and schedule status of work progress on the contract and relate technical performance with cost and schedule accomplishment using procedures for planning work, controlling costs, and measuring performance based on ANSI/EIA-748.

3.1.10.2 Integrated Baseline Review

The Contractor shall participate with the Government in the assessment of program risk and the degree to which the following have been established:

a) Technical scope of work is fully included and is consistent with authorizing documents

b) Project schedule key milestones are identified and supporting schedules reflect a logical flow to accomplish the work

c) Resources (budget, facilities, personnel, skills, etc.) are available and are adequate for the assigned tasks

d) Tasks are planned and can be measured objectively relative to the technical progress

e) Rationales underlying the review are reasonable

f) Management processes support successful execution of the project

3.1.11 Reviews and Meetings

The Contractor shall plan for and participate in reviews, conferences, meetings, and teleconferences.

The Contractor shall support these meetings at a location and frequency as specified in individual DOs or as directed by the Government.

The Contractor shall conduct the meetings and reviews described in the following subsections.

3.1.11.1 Post Award Conference (PAC) / Start of Work Meeting

As specified by DO, the Contractor shall conduct a PAC/Start of Work Meeting held at a date and location mutually agreed upon with the Government. The purpose of the conference shall be to establish the framework of the Contractor and Government interaction during the performance period of the contract. The Contractor shall place emphasis on the operating procedures, methodologies, and processes used in the execution of the contract. The meeting shall include the Contractor’s key team members with emphasis on top level management of the program, agreement on metrics used as management indicators during the program, and the planned partnering approach. The Contractor shall present the program IMS, Integrated Product Team (IPT) structure, management concept, organizational structure, and the interfaces with the Government that will be employed to meet the objectives of the DO. The Contractor shall document action items, responsible individuals, and due dates and shall coordinate resolution of all action items until closure.

3.1.11.1.1 Base Award Joint Post Award Conference (PAC) / Start of Work Meeting The Contractor shall participate in a single joint PAC/Start of Work Meeting hosted by PEO STRI and held at a date mutually agreed upon with the Government. The joint PAC/Start of Work Meeting will include PEO STRI FMT teams/personnel as well as representatives from all FMT PL ID/IQ awardees.

The purpose of the conference shall be to establish the framework of the Contractor and Government interaction during the performance period of the contract. The Contractor shall develop a Microsoft PowerPoint presentation that addresses the following topics:

• Overview of the Contractor’s organization and capabilities

• Management Concept/Approach

• Areas of interest in supporting the FMT PL through the ID/IQ

• Organizational Chart with identification of key team members

• Identification of functional roles and responsibilities of key team members

• Points of Contact (POC) including name, role, phone number, and email address

• Identification of any current partnerships and/or subcontractors that will support FMT PL efforts The Contractor’s PAC presentation shall contain no more than 20 slides, not including Title and Closing/Questions slides, and use fonts no smaller than 10pt. The Contractor shall deliver the PAC presentation to the Government IAW the DD 1423. The Contractor shall be responsible for generating minutes of the meetings for their portion of the Joint PAC/Start of Work Meeting and deliver them to the Government IAW the DD 1423. The Contractor shall document action items for which they are responsible, including suspense dates, and shall coordinate resolution of all action items until closure.

Action item closure shall require Government approval.

(DI-ADMIN-81373) Presentation Materials (DI-ADMN-81250C) Meeting Minutes

3.1.11.2 Program Management Reviews (PMRs)

The Contractor shall conduct PMRs in accordance with the contractual requirements as specified in each individual DO. The Government and Contractor shall mutually agree upon the review location.

The Management Reviews shall provide an accurate program overview and a detailed discussion of pre-selected topics.

The Government and the Contractor shall mutually agree upon the location and frequency of the PMRs. The required frequency of PMRs will be specified in each DO SOW, If the PMR is conducted at a Contractor location, the Contractor shall coordinate and provide all facilities and infrastructure for Government-Contractor meetings and separate breakout rooms for Government only meetings during the PMR.

Contractor shall be responsible for generating minutes of the meetings and provide them to the Government for approval. The Contractor shall document action items, due dates, coordinate resolution, and tracking of action items until closure.

3.1.11.3 Integrated Product Team (IPT) Meetings

As specified in individual DOs, the Contractor shall establish an IPT structure to address major areas (e.g., systems, hardware, and software engineering, integrated logistics support, testing, Cybersecurity (CS), etc.). The Contractor shall establish IPT charters and shall host and participate in regularly scheduled IPT meetings with Government representatives to address the full spectrum of the program concerns including system engineering, schedule, financial, integrated logistics support, CS, and testing as necessitated by the requirements of each individual DO. The Contractor shall prepare the meeting agendas, document action items, record meeting minutes, document due dates, coordinate resolution, and track action items until closure. Action item closure shall require Contractor and Government approval.

3.1.11.4 Technical Interchange Meetings (TIMs)

As specified in individual DOs, the Contractor shall conduct and participate in TIMs to be held at either Contractor or Government facilities as required for the execution of individual DOs. The specific locations, dates, and durations of the meetings shall be specified in the IMS. The meetings shall be co-chaired by a Government and Contractor representative. The Contractor shall explain the reasoning, assumptions, and methodologies in arriving at design decisions, recommendations, or alternatives in the accomplishment of the requirements of the contract. The Contractor shall prepare drawings and other data to aid in the presentations. The Contractor shall have all the required personnel and resources present. The Contractor shall make available facilities for Government-only meetings. The Contractor shall prepare the meeting agendas and document the meeting results.

3.1.11.5 Technical Reviews

As specified in individual DOs, the Contractor shall conduct reviews, with Government participation, to include design reviews (system, subsystem, component, life cycle processes, test readiness, production approval) and audits (functional and physical configuration), for the purpose of assessing technical progress. The Contractor shall document the results of the review, including any resulting action items. Normally, a design review shall be conducted at the completion of each phase of the system-engineering process. Each review shall accomplish the following:

a) Assess the system requirements and allocations to ensure that requirements are unambiguous, consistent, complete, feasible, verifiable, and traceable to top-level system requirements

b) Assess the design maturity based on technical development goals, IMS events and accomplishments, and empirical analysis and test data supporting progress to date

c) Present the risks associated with a continued development effort

d) Assess the life cycle processes and infrastructure necessary for product sustainment throughout the system life cycle

e) Identify resources required for continued development

f) Determine whether to proceed with the next application of the systems engineering process, to discontinue development, or to take corrective actions before proceeding with the development effort

Depending on the complexity of the system, lower-level reviews may be needed. Trade-off analysis and verification results shall be available during design reviews to substantiate design decisions.

Reviews may result in the need to iterate through the system engineering process to resolve identified deficiencies before progressing further into the development activity. Component, subsystem, and system functional- and design-configuration audits shall be performed to ensure that supporting documentation has been satisfactorily completed, that qualification tests for each specification requirement have been completed, all requirements are satisfied, and products comply with final drawings.

At design reviews, if applicable, the Contractor shall present the systems security design, initial security risk assessment, security test approach, security training approach, and any other security relevant information.

3.1.11.5.1 System Requirements Review (SRR)

As specified in individual DOs, the Contractor shall conduct an SRR with the Government to assess and ensure that the system and performance requirements derived from the SOW and Specification are defined, verifiable, and consistent with the system solution and available technologies. The Contractor shall address schedule requirements to ensure that all system and performance requirements can be met within the approved schedule for the effort. As a part of the SRR, the Contractor shall identify any risks to the program and a plan for mitigating each risk. SRR entry and exit criteria and SRR products will be defined in individual DOs. Successful completion of the SRR shall be a prerequisite for proceeding into the preliminary design phase.

3.1.11.5.2 Preliminary Design Review (PDR)

As specified in individual DOs, the Contractor shall conduct a PDR to present the results of the Preliminary Design phase of the Systems Engineering effort. The Contractor shall document action items with due dates and coordinate resolution until closure. Action item closure shall require the approval of both the Contractor and the Government. PDR entry and exit criteria and PDR products will be defined in individual DOs. Successful completion of the PDR shall be a prerequisite for proceeding into the critical design phase.

3.1.11.5.3 Critical Design Review (CDR)

As specified in individual DOs, the Contractor shall conduct a CDR to present the results of the Detailed Design phase of the Systems Engineering effort. The Contractor shall have CDR materials delivered to the Government at least five working days prior to CDR event. The Contractor shall document action items with due dates and coordinate resolution until closure. Action item closure shall require the approval of both the Contractor and the Government. The Contractor shall address design changes made since the PDR. CDR entry and exit criteria and CDR products will be defined in individual DOs.

After the Government has approved the design presented at CDR, the Contractor shall submit an Engineering Change Proposals (ECPs) to the Government for review and approval, prior to implementing the proposed changes to the configuration management baseline. Successful completion of the CDR shall be a prerequisite for proceeding into the development phase.

3.1.11.6 Visitor Support

The Contractor shall host Very Important Person (VIP) visits, arrange for, and provide demonstrations of system performance, program progress, and other system characteristics when notified and requested by the Government. The Government will provide no less than 24 hours advance notice for VIP visits.

3.1.12 Data Rights

The Contractor shall adhere to data rights requirements as stated in 10 USC 3771. The Contractor shall notify the Government of all items to be delivered with less than unlimited data rights.

The Contractor shall obtain and deliver a minimum of Government Purpose Rights for all CDRLs, technical data, metrics, non-commercial software, and hardware provided via a DO under this contract, and funded at least partially by the Government, such that the Government can:

a) Use, maintain, modify, reproduce, release, perform, display, or disclose technical data within the Government without restriction.

b) Release or disclose technical data outside the Government and authorize persons to whom disclosure has been made to use, maintain, modify, reproduce, release, perform, display, or disclose that data for United States Government purposes.

c) Produce, maintain, repair, modify, and/or upgrade a FMT PL system using Government personnel or other Government Contractors.

d) Compete future FMT PL DOs.

The Contractor shall disclose, for any part of their design, data items for which the Government does not have the minimum of Government Purpose Rights.

3.1.13 Government Furnished Information (GFI)

The Government will provide available technical data necessary to accomplish the objectives of each DO upon Contractor request, or at the earliest possible opportunity. The Contractor shall secure alternate data collection or generation methods if the Government is unable to provide the technical data. The Contractor shall be responsible to secure, protect, and maintain the data provided as GFI.

3.1.14 Government Furnished Property (GFP)

GFP will be provided only at the individual DO level in accordance with clauses to be included in the DO. Upon DO award, the Contractor shall inventory all GFP and subsequently maintain records of all GFP. The Contractor shall submit inventory reports to the Government as specified in each individual DO. The Contractor shall be responsible for the maintenance, custody, control, movement, disposal, and storage of all GFP as directed by the Government. The Contractor shall maintain the equipment in the same functional and physical state as received except for normal wear and tear.

FAR Part 52.245-1, Government Property, shall determine the definitions, clauses, policies, and procedures for Government Property, unless otherwise specified in the applicable DO. In addition, Government property in the possession of the Contractor shall be maintained and serviced in a fully operational state.

3.1.15 Organizational Conflicts of Interest (OCI)

As required by DO, the Contractor shall develop, maintain, and implement an OCI mitigation plan to identify and mitigate any actual or potential OCIs, that cannot be neutralized or avoided, while performing efforts under the FMT ID/IQ. The Contractor’s OCI mitigation plan shall be submitted to the KO for review and approval NLT 30 calendar days after DO award. The Government will monitor Contractor activities to ensure compliance with the OCI mitigation plan.

3.1.15.1 Organizational Firewalls

If the Government determines an OCI exists between FMT efforts, the Contractor shall implement organizational firewalls to create a distinct separation of personnel and duties within their organization to handle conflicting FMT efforts independently. Through this organizational delineation, the independent groups within the Contractor shall operate similar to separate contractors collaborating when necessary. The Contractor shall provide a WBS depicting the delineation of personnel and duties to the KO for review.