1 Request for Solutions: Family of Maintenance …...Page 1 of 23 1 Request for Solutions: 2 Family of Maintenance Trainers (FMT) Product Line 3 Armored Multi-Purpose Vehicle (AMPV)

Page 1 of 23

Request for Solutions: 1

Family of Maintenance Trainers (FMT) Product Line 2

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

13 March 2020 4

1. Purpose and Authority 5

This Request for Solutions (RFS) is issued to identify and select capable vendors with 6 the ability to develop an Armored Multi-Purpose Vehicle (AMPV) Part Task Trainer 7 (PTT). The PTT will be incorporated into and extend the existing Family of Maintenance 8 Trainers (FMT) Product Line (PL) and will therefore, utilize and build upon the FMT-CC 9 DTT PL architecture including the FMT-CC TMS, FMT-CC IOS, Network Attached 10 Storage (NAS), and FMT-CC User Interfaces (UI). The purpose of this effort is to 11 analyze existing FMT-Common Core (FMT-CC) architecture, baseline, design 12 documentation, and the AMPV requirements in order to develop and successfully 13 demonstrate a prototype trainer with troubleshooting lessons for the new AMPV PTT 14 which utilizes the FMT-Common Core (FMT-CC) architecture. The AMPV PTT includes 15 the power pack (including the Cummins VTA903E-T675 engine and the L-3 HMPT-800 16 transmission), the driver’s compartment and all interfaces with the power pack. The 17 AMPV PTT Prototype project is unclassified but will require the utilization of technical 18 data/information. 19 20 The RFS scope is limited to the development of the FMT PL AMPV PTT prototype 21 demonstration unit and a study for a mobile configuration. The FMT PL 22 Diagnostic/Troubleshooting Trainers (DTT), Part Task Trainers, and Hands-On-Trainers 23 (HOT) include shared components such as the Training Management System (TMS) 24 and Instructor Operator Station (IOS). Any information regarding other variants of 25 maintenance training systems is provided for FMT PL shared components, PL 26 compliance, and reference only. The Government will evaluate the solutions with the 27 intent of awarding an Other Transaction Agreement (OTA) in accordance with 10 U.S. 28 Code § 2371b. 29

2. Summary and Background 30

2.1. Overview 31

The FMT-CC PL standardizes the Army’s vehicle maintenance trainers with a common 32 core architecture, software baseline, and common equipment. The FMT-CC DTT PL 33 effort established the CC architecture and baseline which will be used on all FMT PL 34 trainers (DTTs, HOTs, and PTTs). FMT-CC PL includes, but is not limited to the 35 Stryker, Abrams, AMPV, and Joint Light Tactical Vehicle (JLTV) maintenance trainers. 36 37

Legacy Maintenance Trainers 38

This section describes the general system level architecture of legacy Army 39 maintenance training systems. Prototypes developed under this OTA shall satisfy the 40 requirements and provide the capabilities identified in the Technical Supplement (TS), 41 FMT-CC design documentation, and this RFS. 42 43

Page 2 of 23

Legacy maintenance trainers are comprised of three (3) distinct classes of devices: 44 DTTs, PTTs, and HOTs. These systems provide Military Occupational Specialty (MOS) 45 skill level development for system operation, fault diagnosis, troubleshooting, 46 adjustments, component removal/replacement, and other servicing and repair tasks for 47 the respective vehicles. Each of these variants, targets specific training goals but share 48 common training elements. The DTTs are computer based system simulations; no 49 actual physical vehicle hardware is employed. Navigation and interaction with the DTTs 50 is handled via keyboard, mouse, and touchscreen inputs. 51 52 The PTT and HOT trainers integrate virtual training with physical hardware. In the case 53 of the PTT, a specific subsystem, such as the brakes or engine, is targeted, and realistic 54 (fabricated or Government Furnished Equipment (GFE) components of that system are 55 instrumented to be an active part of the emulation. There are a few existing legacy 56 HOTs which are not instrumented, for example: the Bradley A2 HOT and the Abrams 57 SEP V2 HOT. The HOT expands upon the PTT concept. The hardware in a HOT is 58 part of a more completely integrated environment that may contain more than one 59 subsystem. The HOT is instrumented in the same manner as the PTT, with the 60 hardware interacting with the virtual software simulation. In all classes, the legacy 61 trainers are comprised of an Instructor Operators Station (IOS) and one or more student 62 workstations (SWS). In addition, a TMS provides record storage and classroom 63 management utilities. The IOS, SWSs, and TMS are connected by an Ethernet or 64 wireless network and high-speed switches. In the case of the PTTs and HOTs, the 65 SWSs are connected by hardware linkage to additional Input/Outputs (I/O) used to 66 instrument the physical representations of the specific device trainers. 67 68 The IOS controls the simulation state and the behavior of the simulation. The SWSs 69 run the actual models that provide the virtual trainer capabilities. The PTT IOS has a 70 similar software package as the DTT but the lessons are focused on interaction with 71 actual vehicle components or components that approximate the real vehicle with high 72 fidelity. 73 74 2.1.1.1. Software 75

Real-Time software includes the software models that simulate the vehicle systems and 76 the executive software which controls the iteration rate of the simulation and schedules 77 the models to run at the appropriate frequencies. The IOS software provides control of 78 the simulation, to include: freeze, lockstep, lesson plan control, and communication 79 control. The TMS software provides support for: classroom management functions, 80 student record archiving and lesson plan maintenance. The Display and Control 81 software is the interface between the student’s or instructor’s actions at a display and 82 the effect it has on the simulation. 83 84 In addition to the simulation software, a Software Support Environment (SSE) provides 85 the resources for performing post deployment software support activities, including 86 identifying, documenting, and correcting system software faults, implementing system 87 software upgrades, managing databases, and providing configuration management. 88 89

Page 3 of 23

Common Software Baseline 90

Historically, although the current trainers have common classifications of software within 91 a variant (i.e., within vehicle types), there was no commonality between platforms (e.g. 92 Abrams, Stryker). Each variant’s software architecture and source code is unique and 93 stove-piped. The Army is in the process of establishing a FMT-CC software baseline to 94 replace the current stove-piped software architecture with a common product line 95 architecture which completely supports the entire FMT PL. This first effort established 96 the CC baseline using the DTT. The FMT-CC PL includes a set of plug-and-play 97 applications that are applicable across the FMT product portfolio of legacy and future 98 combat/tactical vehicle training systems without a loss of current functionality. The FMT 99 CC DTT design documentation is not complete but is expected to be mature at the time 100 of agreement award. This effort will utilize that CC baseline and ensure maintenance 101 lessons are incorporated into the AMPV PTT as part of the PL. 102 103 While the instantiation of the FMT-CC PL was started with the DTT development, in 104 support of the DoD objective to rapidly acquire quality products in an evolutionary 105 approach, further improvements to the CC PL are desired (including new technology 106 insertion) and should be proposed for the AMPV PTT. 107 108 The FMT-CC vehicle specific software, assets, digital information, and documentation 109 will reside on the Live Training Transformation (LT2) portal. The LT2 portal is an Army 110 repository for data and standards for the live training community created under the 111 Consolidated Product Line Management (CPM) Next contract. Information uploaded by 112 the vendor onto the LT2 portal may be available to other contractors/vendors on a need-113 to-know basis to perform work for the Army. The vendor shall provide a plan that 114 documents a path to conformance to the LT2 Product Line Operations and 115 Configuration Management (CM) Guide and existing FMT-CC documentation. The LT2 116 portal and guides are located at https://www.lt2portal.mil. A Common Access Card 117 (CAC) is required to access this portal. For potential vendors without CACs, the LT2 118 Product Line Operations and CM Guide is being provided as Government Furnished 119 Information (GFI). All software code developed with this effort and with the FMT-CC 120 DTT resides in the Independent Development Environment (IDE) portion of the LT2 121 portal. Access to the IDE requires a secret clearance. If a vendor does not have 122 someone with a secret clearance to access the portal, alternate methods can be made 123 by the Government. However, the vendor must include its need for alternate methods 124 of access within the solution. 125

3. General information 126

3.1. Training and Readiness Accelerator (TReX) 127

Vendors interested in responding to this RFS must be members of TReX or teamed with 128 a TReX member. Information about membership can be found at the following 129 webpage: https://nstxl.org/membership/. This project will be managed by the U.S. Army 130 Program Executive Office for Simulation, Training, and Instrumentation (PEO STRI), 131 Project Manager Soldier Training (PM ST), Product Manager Virtual Training Systems 132 (PdM VTS). 133

http://www.lt2portal.mil/

https://nstxl.org/membership/

Page 4 of 23

All Government participants and advisors in the evaluation process will be required to 134 sign non-disclosure agreements (NDAs). 135

3.2. Allowable Costs and Teaming 136

An individual vendor may not submit more than one comprehensive response to this 137 RFS as a Prime. A vendor may participate as a sub-vendor to multiple responses. The 138 cost of preparing and submitting a response is not considered an allowable direct 139 charge to any Government contract or agreement. Non-compliance with the submission 140 instructions provided herein may preclude the vendor from being considered for award. 141

3.3. Non-Government Advisors 142

This is to advise you that non-Government advisors will assist in the evaluation. The 143 use of non-Government advisors will be strictly controlled. Non-Government advisors 144 will be required to sign a Non-Disclosure Agreement (NDA) prior to working the AVTS 145 effort. Agreements Officer will review NDAs for conflict prior to allowing access to 146 source selection information. 147

All non-Government advisors will only have access to the information corresponding to 148 their area(s) of expertise. Advisors will not have access to the Price Volume of the 149 response. The companies identified herein have agreed not to engage in the 150 manufacture or production of hardware/services/R&D that is related to this effort, and to 151 refrain from disclosing proprietary information to unauthorized personnel. 152 The following companies will have non-Government personnel advising: 153 154

ECS Federal, LLC 155 2750 Prosperity Ave Suite 600 156 Fairfax, VA, 22031-4312 157 CAGE Code: 1T1E5 158 159

OST, INC. 160 2101 L St NW Suite 800 161 Washington, DC, 20037-1657 162 CAGE Code: 1NCB1 163

4. GFI/GFE/GFP 164

The Government will make available vehicle operation and maintenance documentation 165 for use during solution preparation to the extent available. In order to obtain the 166 documentation, the contractor shall submit a request in writing to 167 [email protected], with “FMT AMPV PTT” used in the subject line. 168 The GFI will contain the Distribution C or D. The TReX member/team will require 169 processing and approval prior to being authorized to receive any project exhibits to 170 include GFE/GFI such as technical documentation, software, data packages, etc. All 171 exhibits will be considered “As Is” upon being transferred. 172 173 The Distribution Agreement will provide further guidance regarding the handling of GFI 174 after OTA award. The Government will provide additional GFI for the effort no later than 175 15 days after award of agreement. The GFI will include vehicle drawings, technical 176

mailto:[email protected]

Page 5 of 23

manuals and supplements, operator user manuals, if available. Government Furnished 177 Property (GFP) for Technical Objective #3 will be provided after successful completion 178 of a mutually agreed upon milestone or at the times agreed upon by the Government. 179 180

4.1. Government Property 181

The awarded vendor shall meet the following requirements upon receipt of GFP. The 182 vendor shall have a system of internal controls to manage (control, use, preserve, 183 protect, repair, and maintain) Government property in its possession. The Vendor shall 184 create and maintain records of all Government property accountable to the agreement. 185 The Vendor shall investigate and report to the Government all incidents of property loss 186 as soon as the facts become known. The Government shall have access to the 187 Vendor’s premises and all Government property, at reasonable times, for the purposes 188 of reviewing, inspecting and evaluating the Vendor’s property management plan(s), 189 systems, procedures, records, and supporting documentation that pertains to 190 Government property. The Vendor shall include the requirements of this paragraph in 191 all subcontracts under which Government property is acquired or furnished for 192 subcontract performance. The Government shall retain title to all Government-furnished 193 property. The Vendor shall promptly disclose and report Government property in its 194 possession that is excess to agreement performance. The Vendor assumes the risk of, 195 and shall be responsible for, any loss of Government property upon its delivery to the 196 Vendor as Government-furnished property. However, the Vendor is not responsible for 197 reasonable wear and tear to Government property or for Government property properly 198 consumed in performing this agreement. 199

4.2. Applicability of Technical Supplements and FMT CC Design Documents 200

The characteristics of this prototype system and the Government concept for its 201 development are included in the technical supplements and FMT CC design 202 documentation. Vendors are encouraged to tailor the technical supplement in its 203 individual solutions and should articulate any suggested additions or major 204 discrepancies between the technical supplements and the proposed technical solution. 205 The technical supplement and FMT CC design documents are: 206

Technical Supplement for the US Army Armored Multi-purpose vehicle (AMPV) 207 FMT PTT Prototype, PRF-PT-740 208

FMT-CC Interface Control Document, PGM-FMT-0032 209

FMT-CC System Subsystem Specification (SSS), PGM-FMT-0029 210

FMT-CC Software Design Description (SDD), PGM-FMT-0011 211

FMT-CC Interface Design Description (ICD), PGM-FMT-0012 212

If tailored, vendors are to submit the technical supplements with tracked changes to 213 reflect the solution and approach proposed. 214

5. Solution Responses 215

Solution submissions should clearly address planned documentation deliverables 216 (including format and content) and any planned demonstrations, design reviews, and 217 management reviews. A proposed IMS shall be provided in a Microsoft Project format. 218

Page 6 of 23

Responses shall be submitted in an editable/executable (not scanned) Word/Adobe 219 PDF format and limited to no more than 20* standard size (8 ½” X 11”) pages for the 220 total volume count (see table below), using standard 12-point Arial font. Charts or 221 figures are not bound by the 12-point font requirement but shall be clearly legible. Page 222 size of 11”X17” are allowed for charts or figures only and each page will be counted 223 towards the 20* page limit (see Table 1). If the solution exceeds the page limitation, the 224 Government may choose not to read any information exceeding the 20* page limit and 225 the information may not be included in the evaluation the solution. 226 227

Volume Section Format**

Counted towards page limit Page

Limit Yes No

General

Cover Page

Word/PDF

X

5

Nontraditional Status X

FOCI Status X

OCI & Mitigation Plan X

Data Rights X

Security Requirements X

Company Information X

Technical

Cover Page Word/PDF X

15

Sub-Vendor List Word/PDF X

Solution Paper Word/PDF X

Schedule (IMS) MS Project X

Personnel, Manpower, Resource Allocation

Word/PDF X

Labor & Pricing

Cover Page Word/PDF X

Labor Hours & Pricing Excel X

BOE Excel/Word/PDF X

ROM Word/PDF X

Table 1- Page Limits 228

*The Cover Pages, OCI & Mitigation Plan, Data Rights Assertion, IMS, Labor Hours and Pricing, BOE and 229 ROM are not included in the 20 page total. 230

**ALL PDF’s will be editable (not locked). 231

232

Page 7 of 23

Any additional information the vendor deems pertinent may be incorporated into the 233 solution but the total submission shall not exceed the 20 page limitation identified in 234 Table 1 above. 235

5.1. RFS Solution Responses 236

Interested parties shall provide a RFS solution response. The RFS solution response 237 shall contain separate General, Technical, and Price Volumes. No pricing detail shall be 238 provided in any volume other than the Price Volume. As appropriate, vendors shall mark 239 their submissions with proprietary, confidential, etc. The volumes shall consist of: 240

General Volume Contents List 241

o Cover Page 242 o Nontraditional Status 243 o Foreign Owned, Controlled or Influenced (FOCI) status 244 o Organizational Conflicts of Interest (OCI) and Mitigation Plans 245 o Company Information 246

Technical Volume Contents List 247

o Cover Page 248 o Sub-Vendor List 249 o Solutions Submission 250 o Schedule which include proposed Integrated Master Schedule (IMS) for 251

the entire PTT Prototype effort 252 o Personnel, Manpower, Resource Allocation and Involvement 253 o Data Rights in Technical Data and Computer Software (as described in 254

Section 5.1.2.7.2 of this RFS) 255

Labor & Pricing Volume Contents List 256

o Cover Page 257 o Labor and Pricing 258 o Basis of Estimate (BOE) 259 o Rough Order of Magnitude (ROM) 260

261 General Volume 262

If the vendor fails to meet the minimum requirements, the solution may be denied 263 further evaluation at the Governments discretion. 264

5.1.1.1. Cover Page 265

The cover page shall include the title, vendor’s name, Commercial and Government 266 Entity (CAGE) Code (if available), Data Universal Numbering System (DUNS) number, 267 Business Size, address, primary point of contact (phone number & email), and status of 268 U.S. ownership. The North American Industry Classification System (NAICS) Code for 269 this effort is 541512, Computer System Design Services. 270

5.1.1.2. Nontraditional Status 271

Nontraditional Definition - An entity that is not currently performing and has not 272 performed, for at least one-year period preceding the solicitation of sources by the 273

Page 8 of 23

Department of Defense (DoD) for the procurement or transaction, any contract or 274 subcontract for the DoD that is subject to full coverage under the cost accounting 275 standards prescribed pursuant to 41 U.S.C §1502 and the regulations implementing 276 such section. 277

The vendor shall provide its nontraditional business status or its ability to meet the 278 eligibility requirements of 10 U.S.C. §2371b. The vendor shall check one of the 279 following boxes – with appropriate justification, if needed. 280

281 □ There is at least one nontraditional defense contractor or nonprofit research 282

institution participation to a significant extent in the project. 283 284

□ All significant participants in the transaction other than the Federal Government 285 are small businesses or nontraditional defense contractors. 286 287

□ At least one third of the total cost of the project is to be provided by sources other 288 than the Federal Government. 289

If the vendor is not a nontraditional defense contractor (NDC), additional information is 290 needed. Vendor shall provide the name and CAGE code and DUNS number for the 291 NDC. Additionally, the vendor shall provide what portion of the work the NDC is 292 performing and an explanation of how the prototype would not succeed based on the 293 portion of work performed by the NDC. 294

5.1.1.3. Foreign Owned, Controlled or Influenced (FOCI) Status 295

In accordance with RFS Attachment 13, Security Process for Vetting Contractors, the 296 General Volume must include certification that the vendor (and subcontractor(s)) are not 297 Foreign Owned or under USA FOCI status (and are not in merger or purchasing 298 discussions for a Foreign company or USA FOCI Company). Should a prospective 299 vendor be unable to so certify, they will be ineligible for award unless the mitigating 300 circumstances in Attachment 13 Security Process for Vetting Contractors are met. In 301 such a case, these mitigating circumstances shall be detailed in an appendix to the 302 General Volume. 303

Security Vetting: All vendors who want to compete, bid or team with others for this effort 304 must be willing to comply with the PEO STRI Security Process for Vetting. All vendors 305 (Prime and Subs) must be vetted for eligibility, suitability, national status e.g. FOCI prior 306 to the receipt of any award instrument. 307

5.1.1.4. Organizational Conflicts of Interest and Mitigation Plan 308

Vendors will submit an OCI Mitigation Plan via an appendix to its General Volume. In 309 the event there are no real or perceived OCI, simply state so and annotate what actions 310 would be taken in the event that one is realized. The OCI mitigation plan is not part of 311 the solution page count. 312

5.1.1.5. Company Information 313

Within this section, the vendor may include relevant or other miscellaneous information 314 the company wishes to express to the Government (e.g. previous work, partnerships, 315 awards, company structure, etc.). 316

Page 9 of 23

Technical Volume 317

5.1.2.1. Cover Page 318

The cover page shall include the title, vendor’s name, Commercial and Government 319 Entity (CAGE) Code (if available), Data Universal Numbering System (DUNS) number, 320 Business Size, address, primary point of contact (phone number & email), and status of 321 U.S. ownership. 322

5.1.2.2. Sub-Vendor List 323

Vendor shall provide a list of all sub-vendors involved and their role within the 324 performance of your submission as an appendix to Technical Volume. The list shall 325 include FOCI status and OCI. 326

5.1.2.3. Solution Submission 327

The vendor’s proposed technical solution shall describe its approach to providing the 328 solution based on the technical objectives identified in Section 5.1.2.7.1, with the 329 system characteristics described in the Technical Supplement for the AMPV FMT PTT 330 Prototype (Attachment 5). Vendors are encouraged to tailor the technical supplement in 331 individual solutions and should articulate any suggested additions or major 332 discrepancies between the technical supplements and the proposed technical solution. 333 If tailored, vendors are to submit the technical supplements with tracked changes to 334 reflect the solution and approach proposed. 335

The solution shall describe how the vendor plans to provide all of the major capabilities 336 as well as a: 337 338

1. A design approach that demonstrates a thorough understanding of desired product 339 line system architecture, prototype objectives, and modular approach to key 340 subsystems. 341

2. One or more design solution(s) that can support training at the point of need. The 342 vendors are encourage to include how its design could meet future requirements (e.g. 343 transportability, vehicle platform upgrades). 344

3. Description of the team composition and sub-vendor involvement. 345

4. A detailed approach to demonstrate the required facilities, capabilities, and 346 management of the follow-on production activities described in Section 8 and 347 capability to manage simultaneous development and production efforts. 348

349 The above capabilities are not listed in any specific order of priority and are provided to 350 help focus vendor responses. In addition to describing the approach to delivering these 351 capabilities, the technical solution shall also include full discussions of: 352 353 a) Anticipated development risks. 354

b) Proposed timeline tied to milestone activities for the 18 month period of performance. 355

Page 10 of 23

5.1.2.4. Schedule 356

This section should include an anticipated delivery schedule: The vendor is to include 357 the anticipated delivery dates with their solution that includes all FMT AMPV PTTs 358 capabilities and completion dates for key design reviews, test events, Integrated 359 Product Team collaboration activities, cybersecurity completion events, and other tasks 360 and deliverables as described herein. 361

5.1.2.4.1. Integrated Master Schedule (IMS) 362

An IMS is to be created using Microsoft Project. The IMS should be resource loaded 363 with each task including a predecessor (if applicable), and correlate to the Basis of 364 Estimates (BOE). The IMS may be attached as an appendix file. The IMS is not 365 included in the total page count and page count is unlimited. 366

5.1.2.5. Personnel, Manpower, Resource Allocation and Involvement 367

5.1.2.5.1. Key Personnel (KP) List 368

The vendor is to provide a list of key program personnel by labor category, title, and 369 experience. Key Personnel consist of Lead Hardware Engineers, Lead Technical 370 Engineers, Lead Software Engineers, and Program Managers. Vendors will specify KP 371 experience with tracked vehicle and engine maintenance trainers for the prime and all 372 sub-vendors. Describe experience with design of trainers equipped with, fire 373 suppression systems, diesel engines, and Controller Area Network architecture used in 374 a training environment similar to the planned AMPV PTT. Experience should be within 375 the last three years. 376

5.1.2.5.2. Manpower Allocation 377

Reasonableness of the Manpower Allocation (labor categories and hours by month) and 378 schedule in relation to the IMS for the entire effort. Reasonableness includes the 379 appropriate distribution of labor categories and hours associated with each milestone. 380 The manpower allocation document will be in excel format. 381

5.1.2.5.3. Resource Allocation & Involvement 382

5.1.2.6. Data Rights 383

Government desired rights are described in Section 5.1.2.8 of this RFS. For data rights 384 other than unlimited or government purpose rights, the vendor shall assert each 385 instance with justification within the Data Rights Assertions tables in Attachment #14. 386

5.1.2.7. AMPV Prototype 387

The prototype developed under this OTA should satisfy the requirements and provide 388 the capabilities identified in the Technical Supplement and FMT-CC design 389 documentation. 390 391 The Government will require a demonstration of the functionality and utility of the AMPV 392 PTT prototype unit at the vendor’s facility and at Ft. Benning. Unless specifically noted 393 as GFE, the solution shall provide all equipment (for example: network cables, 394 computers, monitors, etc.). The solution shall also include any wireless equipment 395 including switches and any equipment/systems required to demonstrate the prototype 396 unit will seamlessly integrate with the on-site TMS. The vendor shall update the 397

Page 11 of 23

Notional GFE list (Attachment # 9) with any changes, including additions/deletions and 398 include with its solution. The vendor will update the GFE list after award. The 399 Government will provide GFE for the prototype demonstration unit with a minimum of 90 400 days’ notice prior to need. 401 402 The prototype shall include all applicable draft safety and cybersecurity RMF controls 403 sufficiently documented to enable the Government to obtain a Safety Release, Health 404 Hazard Approval, and an Authority to Operate (ATO). 405 406 The FMT PL AMPV PTT prototype approach includes a single phase, with multiple 407 technical objectives, as well as potential follow-on production activities outlined in 408 Section 8: “Follow-on Production Activities.” The varying completion criteria established 409 for each technical objective may be considered a Decision Point (DP) for entry into 410 subsequent technical objectives and/or follow-on OT production efforts. Separate 411 pricing is required for each technical objective. The Government may, at its discretion, 412 use a DP to stop the effort if the vendor is unable to successfully perform. 413 414 To ensure FMT PL concurrency with fielded FMT PL products as well as concurrent 415 FMT PL efforts, Associate Vendor/Contractor Agreements (ACAs) will be required for all 416 FMT PL contractors, with the existing vendor for exchange of technical information. 417 418 The potential production PTTs will be installed at Ft. Benning, GA, Ft. Lee, VA, and 419 Camp Shelby, MS. The FMT PL existing common equipment may be located in a 420 different location within the same building or in other buildings. The PTTs must have 421 connectivity to the common equipment within the same building. The storage and 422 operational location may differ between locations. Therefore, the prototype design must 423 take into consideration the multiple locations. An initial site visit/survey to each fielding 424 location will be required during the prototype development to ensure the building 425 requirements are met for installation and operation of the trainers. The site visit/survey 426 will be properly documented within a Training Facilities Report (TFR). 427 428 For the potential production PTTs, Government facility space and facility power will be 429 provided by the Government. Any modifications required to the facility space, including 430 power and duct work, will be required to be identified in a TFR. Any reference, in this 431 RFS or supporting documentation, to network capabilities refers only to the networking 432 between or within the prototype training devices (for example: DTT to DTT, PTT to DTT, 433 PTT to PTT, PTT to HOT, etc.); the FMT PL prototype training devices DO NOT and 434 WILL NOT connect to the facility network or the internet. The Internet Protocol (IP) 435 addressing for the production PTTs will conform to the IP addressing plan in the FMT-436 CC Risk Management Framework (RMF). 437

5.1.2.7.1. Prototype Phase 438

This prototype phase consists of four (4) Technical Objectives (TO), the TOs explain the 439

high-level scope and deliverables required prior to proceeding to the subsequent TO. 440

Within 2 weeks of award the vendor will submit a draft Integrated Master Schedule 441

(IMS). The vendors IMS will include the date of expected completion for each TO. The 442

Government review and Configuration Control Board (CCB) and/or Core Asset Working 443

Page 12 of 23

Group (CAWG) approval of the proposed architecture will be required prior to 444

proceeding to the next Technical Objective. 445

The Government has the right to deny or approve entry into the next TO. The 446 Government reserves the right to reject any deliverables. At the Governments 447 discretion, the vendor may be required to revise and resubmit deliverables. If the 448 Government determines that the vendor has not successfully met the TOs and/or has 449 not produced the required (approved) technical documentation, the Government may 450 terminate the prototype effort at any DP. 451

The phase is considered complete upon the successful demonstration of the collective 452 TOs and the approval of all deliverables. However; the Government, at its discretion, 453 may choose to proceed into subsequent TOs or production prior to approval of TO 454 objectives and/or deliverables. The potential production follow-on DP will not occur 455 prior to TO #3 completion. 456

457 Suggested formatting for deliverables can be found at the Acquisition Streamlining and 458 Standardization Information System (ASSIST) website 459 (https://quicksearch.dla.mil/qsSearch.aspx) by using the ASSIST Search Tool for the 460 document type. Contractor Format is acceptable. 461

Estimated Timeline: The Government anticipates that the total period of performance 462

for this effort, which consists of one phase, will not to exceed 18 months total. 463

The timeline below identifies the suggested/estimated completion of each TO 464

milestones. The vendor will present its own timeline for approval within the delivered 465

IMS prior to the Kickoff meeting. 466

TO#1Complete

TO#2 Complete

TO#3 Complete

TO#4Complete

2 Weeks 2 Months 4 Months 10 Months 2 Months

1st Sub.IMS Due

Award1

Kickoff Meeting/Start of Work

Government Estimated Phase Timeline

1

Analysis of Requirements Planning, Design & Development Prototype Verification/Validation

467

5.1.2.7.1.1. Technical Objective #1: 468

1. Analyze the latest FMT-CC software and hardware architecture, FMT-CC 469

design documentation, FMT PL guidelines and standards, GFI, and the AMPV 470

Technical Supplement to develop a generic prototype architecture and design 471

approach for PTTs that will be adopted into the FMT PL. Vendor shall identify 472

recommended improvements to the current FMT-CC PL. 473

474

2. The vendor shall deliver a mobile PTT study. The mobile PTT will be 475

transported to various fielding locations and remain at those locations for 6 476

months to one year before being moved to another location. The mobile PTT 477

https://quicksearch.dla.mil/qsSearch.aspx

Page 13 of 23

shall maximize the reuse of the fixed PTT design which is being developed 478

under this agreement. Completion study will require working group discussion 479

with the Government to define the requirements and present a minimum of two 480

(2) viable options with estimated timelines and budgetary pricing. 481

482

3. Develop a FMT AMPV PTT PL prototype system architecture that will: 483

a. Satisfy the functional and performance requirements of the FMT-CC design 484

documents and Technical Supplement. 485

b. Leverage FMT-CC software components. 486

c. Minimize life cycle costs to establish and sustain the Family of Maintenance 487

Trainers Product Line. 488

d. Support or incorporate the integration of new technologies. 489

e. Be compatible with the LT2 constructs and guidelines described in Section 490

2.1.2 of this RFS. 491

5.1.2.7.1.1.1 Technical Objective #1 Deliverable Outcomes: 492

5.1.2.7.1.1.2 Decision Point for Technical Objective #1 493

The Government will hold a DP meeting and determine whether the Government will 494 proceed into TO #2 or terminate the agreement. 495 496


Based on the Approved TO #1 Deliverables, the vendor will develop: 498

1. All troubleshooting/maintenance lessons with their respective troubleshooting 499

paths as identified in the AMPV Technical Supplement to be implemented on each 500

of the PTTs. Note: The troubleshooting paths will be developed with input and 501

agreement from the Government provided Subject Matter Experts (SMEs). 502

2. A list of all required GFE, including dates required. 503

3. Technical manual work package identification and method to introduce faults for 504 the lessons to be implemented on the PTT. 505

Document Title Submission

AMPV PTT System Architecture Description (SAD) Initial

AMPV PTT System/Subsystem Specification (SSS) Initial

FMT- CC design document updates (if applicable) Initial

Requirements Traceability Verification Matrix (RTVM) Initial

Training Facility Report for each fielding site Initial

Page 14 of 23


507


AMPV PTT System Architecture Description (SAD) 2nd Submission

AMPV PTT System/Subsystem Specification (SSS)

Note: The troubleshooting paths will require Government

acceptance/approval prior to incorporation into the (SS)

2nd Submission

FMT- CC design document updates (if applicable) 2nd Submission

Requirements Traceability Verification Matrix (RTVM) 2nd Submission

Trainer Facilities Report (TFR) 2nd Submission


The Government will hold a DP meeting and determine whether the Government will 509 proceed into TO #3 or terminate the agreement. 510


Based on the accepted Deliverables from TOs #1 and #2 and AMPV documentation, 512

the vendor will develop an AMPV PTT prototype. The approach should maximize reuse 513

and modularity to the maximum extent possible. For example, the design should 514

include common/reusable components that could be used for any AMPV variant with 515

minimum internal reconfiguration required. The prototype shall include all applicable 516

safety and RMF controls implemented to enable the Government to obtain both a Safety 517

Release and an ATO. 518


520


AMPV PTT System Architecture Description (SAD) 3rd Submission or Final

AMPV PTT System/Subsystem Specification (SSS) 3rd Submission or Final

Requirements Traceability Verification Matrix (RTVM) 3rd Submission or Final

PTT Prototype Technical Data Package (TDP) (Design documents, source code, drawings, etc.)

Initial

Verification/Validation Documentation

(Test Procedures) Initial

Cybersecurity RMF Documentation Initial

Draft System Safety Assessment Report (SSAR) Initial

Health Hazard Analysis Report (HHAR) Initial

Page 15 of 23

Software Design Description (SDD) Initial

Software Product Specification (SPS) Initial


The Government will hold a DP meeting and determine whether the Government will 522 proceed into TO #4 or terminate the agreement. 523


Successful verification & validation of the AMPV prototype PTT which meets 525

stakeholder’s requirements and full system demonstration and integration of the AMPV 526

PTT prototype, including the FMT-CC IOS and TMS at the Ft. Benning facility. 527

Technical Objective #4 includes all the integration tasks and equipment required to 528

demonstrate a fully functional prototype unit at Ft. Benning after successful 529

demonstration to the Government at the contractor’s facility. The integration and 530

demonstration will be coordinated with the Government for proper and timely 531

coordination between stakeholders, and to ensure scheduling needs are met. 532


534


AMPV PTT System Architecture Description (SAD) Final

AMPV PTT System/Subsystem Specification (SSS) Final

Requirements Traceability Verification Matrix (RTVM) Final

PTT Prototype Technical Data Package (TDP) (Design

documents, source code, drawings, NET package, Item Unique

Identifier (IUID), etc.)

Final

Verification/Validation Documentation

(Test Procedures, Test Reports)

Final

Cybersecurity/RMF Documentation and Reports Final

System Safety Assessment Report (SSAR) Final

Hazard Analysis Report (HHAR) Final

Training Facilities Report (TFR) Final

Software Description Final

Software Product Specification (SPS) Final

Page 16 of 23

Configuration Audit Report Final

Logistics Product Data Final

Software Product Package Final

Product Baseline Index Final

Training Conduct Support Documents Final

Course Conduct Information Package Final

5.1.2.7.1.4.2 Decision Point for TO #4 535

The Government will hold a DP meeting and determine whether the Government will 536 proceed into production. 537

5.1.2.8. Government Desired Rights in Technical Data and Computer Software 538

For the purposes of this RFS and final award document, the Government will use the 539 data rights and computer software related terms defined in Attachment #16, Data Rights 540 and Computer Software License Terms and Definitions 541

Vendors shall complete the Data Rights Assertions tables in Attachment #14, including 542 any assertions of its subcontractors or suppliers must be submitted as an attachment to 543 its solution response. The tables must be completed in the format set forth in the 544 attachment, dated and signed by an official authorized to contractually obligate the 545 vendor. If additional space is necessary, additional pages may be included. There is no 546 page limit for the Data Rights Assertions Tables and they do not count against the 547 proposed technical solution page limitation. If the proposed solution under this 548 transaction contains data rights other than unlimited or government purpose rights, the 549 vendor shall assert each instance with justification within the Data Rights Assertions 550 tables in Attachment #14. 551

The Government requires Government Purpose Rights (GPR) to all development and 552 deliverables of technical data and computer software developed exclusively with 553 Government funds under the transaction agreement, for at least a five-year period. At 554 the end of the five year period, unlimited rights shall transfer to the government. This 555 includes but is not limited to the following: 556

(a) Studies, analyses, test data, or similar data produced for this contract, when the 557 study, analysis, test, or similar work was specified as an element of performance; 558

(b) Form, fit, and function data; 559

(c) Data necessary for installation, operation, maintenance, or training purposes (other 560 than detailed manufacturing or process data); 561

(d) Corrections or changes to technical data furnished to the Vendor by the 562 Government; 563

(e) Data otherwise publicly available or which has been released or disclosed by the 564 Vendor or Vendor partners without restrictions on further use, release or disclosure, 565

Page 17 of 23

other than a release or disclosure resulting from the sale, transfer, or other assignment 566 of interest in the technical data to another party or the sale or transfer of some or all of a 567 business entity or its assets to another party; Commercial Computer Software 568

If the Government has a need for rights not conveyed under the license customarily 569 provided to the public, the Government must negotiate with the third party software 570 vendor(s) to determine if there are acceptable terms for transferring such rights. The 571 specific rights granted to the Government shall be enumerated in the license agreement 572 or an addendum thereto. 573

The Government shall only have the rights specified in the license for the commercial 574 computer software and its related commercial computer software documentation for the 575 software listed in the tables below. The terms of any End User License Agreements 576 apply only to the extent they are consistent with law and Attachment 15, Data Rights 577 Information. 578

All rights in Technical Data and Computer Software, developed exclusively at private 579 expense, are negotiable based on the vendor’s proposed solution. 580

The vendor shall describe the intellectual property rights being provided to the 581 Government in terms of technical data, both in software and hardware, clearly outlining 582 the appropriate assertion of rights within technical data, computer software and software 583 documentation that will be delivered with your solution(s), and any rights restrictions. If 584 the proposed solution includes commercial software, copies of any applicable End User 585 License Agreements (EULAs) must be submitted with the response. It is the 586 Government’s intent to plan for the maintenance and modification of the system(s) using 587 Government personnel and third party contractors. The EULA submissions have no 588 page limit and do not count against the proposed technical solution page limitation. If 589 additional pages are needed, data rights assertions may be submitted as an appendix, 590 which has no page limit and does not count against the proposed technical solution 591 page limitation. 592

The vendor shall make every effort to analyze feasible non-proprietary solutions and 593 incorporate them when applicable to the effort. This includes, but is not limited to, 594 software rights, data, source code, drawings, manuals, warranties, and integration 595 efforts. The vendor shall clearly state all assumptions made during development of 596 responses. 597

5.1.2.9. Operations Security 598

For Operations Security (OPSEC) requirements, see the Attachment 12; OPSEC 599 requirements document. 600

5.1.2.9.1. Cybersecurity 601

The prototype shall meet all applicable RMF (cybersecurity requirements) required for 602 the Government to obtain an ATO. 603

Labor & Pricing Volume 604

5.1.3.1. Cover Page 605

The cover page shall include the title, vendor’s name, Commercial and Government 606 Entity (CAGE) Code (if available), Data Universal Numbering System (DUNS) number, 607

Page 18 of 23

Business Size, address, primary point of contact (phone number & email), and status of 608 U.S. ownership. 609

5.1.3.2. Labor Hours & Pricing 610

Vendors shall submit a firm, fixed-price amount for its solution, further divided into 611 severable milestones. The Government is not dictating a specific price mechanism. 612 However, proposed payments should be linked to clearly definable, detailed milestones 613 for the prototype. It should be clear, with sufficient detail, what is being delivered at 614 each milestone. The vendor’s pricing milestones may vary from the defined decision 615 points, depending on the proposed solution. Labor Hours and labor category by 616 Technical Objective (TO) should be included in the pricing breakdown. Pricing 617 submission shall be submitted in Excel format with all Excel formula’s and pricing 618 information used during calculation. Milestones should be established and priced in a 619 manner that prohibits milestone efforts from being worked concurrently. Each milestone 620 price should reflect the anticipated value the Government will receive toward 621 accomplishment of the OTA goals and objectives at the time the milestone is 622 completed. The Labor Hours & Pricing has no page number limitation. 623

5.1.3.3. Basis of Estimates (BOE) 624

Vendors shall include a basis of estimates which covers manpower allocation for the 625 entire scope of this effort, validates the labor hours & Pricing Breakdown and is 626 correlated to the vendors proposed IMS. The BOE shall include a detailed Bill of 627 Materials (BOM) 628

5.1.3.4. Rough Order of Magnitude (ROM) 629

Vendors shall provide a ROM pricing for potential follow-on production activities as 630 described in Section 8. The ROM pricing shall state all assumptions and methodology 631 used to obtain the ROM. The ROM quantities shall be 1-6 permanently stationed units 632 and 1-3 mobile units. The mobile units intended use is to be easily transportable from 633 site to site, for the use as new equipment trainers. The Government estimates these 634 quantities should take approximately 18 months. Please note: the Follow-On ROM will 635 assist in future planning efforts for the potential follow-on efforts. The Follow-On ROM 636 is not part of the evaluation. 637

5.2. RFS Response Instruction 638

There will be an open period for the submittal of questions relating to the RFS. All 639 questions related to this RFS shall be submitted electronically using the real time 640 Question and Answer application, Slido. Access to Slido is established by following the 641 link: www.slido.com. The access code for the FMT AMPV PTT event is: #Q739. All 642 questions must be submitted with company name and POC information. The 643 Government will remove the company name and POC information before the questions 644 are posted to industry The Government will provide all responses to submitted 645 questions through the Slido application. The Government will make every attempt to 646 answer all submitted questions as soon as possible, but no later than 1:00 PM EDT, 3 647 April 2020 after the deadline for question submittal. 648

The questions and answer period using Slido and electronic submission, will be open 649 until 20 March 2020 at 1:00 PM EDT, Questions received after the deadline may not be 650 answered. Questions shall not include proprietary data. 651

http://www.slido.com/

Page 19 of 23

Note: the Government reserves the right to post submitted questions and answers to 652 facilitate vendor solution responses. 653

The Government may also establish a WebEx session, as appropriate, to communicate 654 with industry. If the Government decides to utilize WebEx, a date, time and title of the 655 event will be posted no later than two (2) weeks before solutions are due. 656

Written solutions shall be submitted no later than 1:00 PM EDT 9 April 2020 via the 657 “Submit a Solution” button on the NSTXL website. Any submissions received after the 658 deadline may be rejected as late and not considered. 659

6. Evaluation and Selection Process 660

6.1. Evaluation 661

The evaluation will consist of evaluation of the written solution response. If further 662 information is required after the completion of the evaluations of the written solution 663 responses, the Government may request presentations and/or demonstrations or enter 664 into communications with vendors. 665

The Government will evaluate the degree to which the submission provides a thorough, 666 flexible, and sound approach to fulfill the requirements. 667

In performing the initial review of the Technical Volume, the Government evaluators will 668 only review the enclosures and other proposal information if the response describes a 669 technical approach that the Government evaluators find sufficiently viable and effective 670 based on the Focus Areas described below. 671

If the other supporting documents are reviewed, the Government evaluators will 672 consider the extent to which the supporting documents are consistent with the 673 remaining technical response. If the supporting documents are not consistent, the 674 overall evaluation of the vendor’s solution may be negatively affected. 675

The Government recognizes the need for flexibility in its evaluation process. The 676 following represents the Government’s planned approach to evaluating submissions in 677 response to this RFS. 678

Written solution responses will be evaluated with consideration given to the vendor’s 679 ability to provide a clear description of the proposed solution, the overall technical merit 680 of the response and the total project risk with consideration aimed at the Technical and 681 Labor & Pricing Volumes, with respect to the Focus Areas referenced below and the 682 ability to fulfill the requirements in the Technical Supplement and FMT-CC design 683 documents identified in the Technical Attachments 1-9 and 11. The Government 684 evaluators will consider the written solution response when selecting the preferred 685 approach to achieving the Government’s objectives. 686

After the evaluation of written solution responses, it is anticipated that the Government 687 will begin Statement of Work (SOW) collaboration with the selected vendor. 688

The Technical and Labor & Pricing Volumes of the Written Solution Response will be 689 evaluated based upon the following focus areas. 690

Page 20 of 23

Focus Areas: In evaluating the viability and overall effectiveness, the Government 691 evaluators will consider the following focus areas, in no specific order of importance. 692

Focus Area Focus Area Description

1 Technical Merit

2 Demonstrated Experience

3 Solution Feasibility of Implementation

4 Solution Price

6.1.1.1. Focus Area 1 – Technical Merit 693

The technical merit of the vendor’s technical solution and design approach for all 694 phases and objectives as described in Sections 5.1.2.7. 695

6.1.1.2. Focus Area 2 – Demonstrated Experience 696

Clearly communicate how past experience in creating maintenance trainers, such as, 697 PTT will demonstrate the technical capabilities of this effort. Communicate experience 698 in development, production, and fielding of PTT maintenance trainers. Communicate 699 experience with development of trainers for include engine, transmission, driver 700 compartments, and Controller Area Network (CAN) architecture. Communicate 701 experience with establishing product lines and Army track vehicle maintenance to 702 include engine, transmission and driver compartments. 703

6.1.1.3. Focus Area 3 – Solution and Feasibility of Implementation 704

Clear, concise, and well-developed solution with streamlined approach of being 705 implemented into the FMT PL, ease of adapting the final design solution to reuse (for 706 example: the instructor controls could be reused) in order to expand the product line 707 and fielded within schedule. 708

6.1.1.4. Focus Area 4 – Solution Price 709

Clear pricing & cost data which accurately reflects level of effort derived from proposed 710 Technical Volume, and IMS. Rational price breakdown for each major milestone 711 activity. Detailed man-hours by month for each labor category, and detailed bill of 712 material. 713

714 6.2. Selection Process 715

716 The Government anticipates awarding one OT prototype project, through TReX, to the 717 vendor that proposes a solution that best satisfies the Government’s objectives. 718 719 The Government will review each vendor’s submittal against the focus areas and make 720 award to the vendor whose solution is determined to be the most advantageous to the 721 Government in terms of price, schedule and technical risks. Assessment of risk is 722 subjective. If the risk is obvious or the schedule seems overly aggressive, the 723 Government will consider that in the total risk assessment. Vendors are responsible for 724 identifying risks within their submissions, as well as providing specific mitigation 725

Page 21 of 23

solutions. If sufficient validation of the proposed information is not provided, the 726 Government may reject the submission. 727 728 Unsupported assertions will be discounted by the evaluators. 729 730 In making the final decision it may become necessary to compare the proposals of each 731 vendor against the other, but the Government anticipates that its decision is more likely 732 to be made based on each vendor’s submittal as evaluated against the elements 733 described above and a determination of which proposal is determined to be the most 734 advantageous to the Government. 735

7. Additional Information 736

7.1. Statement of Work 737

The proposed solution will be used to collaboratively negotiate a Statement of Work 738 (SOW) after selection for award. The SOW will be incorporated into the OTA agreement 739 as part of the award. 740

7.2. Export Controls 741

Research findings and technology developments arising from the efforts may constitute 742 a significant enhancement to the national defense and to the economic vitality of the 743 United States. As such, in the conduct of all work related to this effort, the recipient will 744 comply strictly with the International Traffic in Arms Regulation (22 C.F.R. §§ 120-130), 745 the National Industrial Security Program Operating Manual (DoD 5220.22-M) and the 746 Department of Commerce Export Regulation (15 C.F.R. §§ 730-774). 747

7.3. Interaction and/or Disclosure 748

The Vendor should comply with foreign disclosure processes IAW US Army Regulation 749

(AR) 380‐10, Foreign Disclosure and Contacts with Foreign Representatives; 750 Department of Defense Directive (DoDD) 5230.11, Disclosure of Classified Military 751 Information to Foreign Governments and International Organizations; and DoDD 752 5230.20, Visits and Assignments of Foreign Nationals. All submissions shall be 753 unclassified. Submissions containing data that is not to be disclosed to the public for 754 any purpose or used by the Government except for evaluation purposes shall include 755 the following sentences on the cover page: 756

“This submission includes data that shall not be disclosed outside the Government, 757 except to non-Government personnel for evaluation purposes, and shall not be 758 duplicated, used, or disclosed -- in whole or in part -- for any purpose other than to 759 evaluate this submission. If, however, an agreement is awarded to this Company as a 760 result of -- or in connection with – the submission of this data, the Government shall 761 have the right to duplicate, use, or disclose the data to the extent agreed upon by both 762 parties in the resulting agreement. This restriction does not limit the Government's right 763 to use information contained in this data if it is obtained from another source without 764 restriction. The data subject to this restriction are contained in sheets [insert numbers or 765 other identification of sheets]” 766

Page 22 of 23

Each restricted data sheet should be marked as follows: 767 “Use or disclosure of data contained on this sheet is subject to the restriction on the title 768 page of this submission.” 769

8. Follow-On Production Activities 770

It is anticipated that potential follow-on production OTAs or contracts will be awarded 771 which use the FMT-CC PL PTT architecture and software/hardware, developed under 772 this prototyping effort. Potential follow-on production OTAs or contracts may be either 773 sole source, based on successful completion of the prototype project within the scope of 774 this document, or competed at the discretion of the Government. The Government 775 intends to use Government estimates to determine price reasonableness. Follow-on 776 production activities could include system and software updates to address 777 obsolescence, concurrency with the weapons platform, evolving training requirements, 778 and technology insertion. 779

Anticipated follow-on activities may include, but are not limited to the following: 780

1. Production of additional models and lessons for the AMPV PTT which are 781

compliant with the approved FMT-CC architecture and the vehicle specific 782

training requirements. 783

2. Production of one to six (1-6) additional PTTs for the AMPV which are 784

compliant with the approved FMT-CC architecture and the vehicle specific 785

training requirements. 786

3. Production of one to three (1-3) transportable PTTs to allow moving to 787

different regional training locations. 788

4. Perform software and hardware updates to existing AMPV PTT MTSs as 789

required. 790

791

Follow-on Products: Follow-on products will include software design description, 792 source code, interface capability and interface design documents (ICD/IDD), production 793 level technical data package, and system specifications, interim contractor support 794 (ICS), and new equipment training (NET). 795

The Government will provide GFE for the potential follow-on production effort with a 796 minimum of 90 days’ notice, prior to need. 797

Estimated Timeline: FY22-FY23 798

The estimated value of all potential follow-on production activities is $6 million dollars. 799

800 9. Attachment 801 The characteristics of this prototype system and the Government concept for its 802 development are included in the attached technical supplement and FMT-CC design 803 documentation (Attachments 1-5). 804

805 Attachment #1 - FMT-CC Software Design Description (SDD), PGM-FMT-0011 806

Page 23 of 23

Attachment #2 - FMT-CC Interface Design Description (IDD), PGM-FMT-0012, 807 Attachment #3 - FMT-CC System Subsystem Specification (SSS), PGM-FMT-0029 808 Attachment #4 - FMT-CC Interface Control Document (ICD), PGM-FMT-0032 809 Attachment #5 - Technical Supplement for the AMPV FMT PTT Prototype 810 Attachment #6 - LT2 Operations Guide, 08 Oct 2019 811 Attachment #7 - AMPV Interactive Electronic Manual (IETM) 812 Attachment #8 - LT2 Product Line Configuration Management Guide, 25 Feb 2019 813 Attachment #9 - Notional GFE List 814 Attachment #10 - Vendor GFI Tech Data Distribution Agreement, 22 Jan 2020 815 Attachment #11 - DoDM 5100.76, April 17, 2012, Physical Security of Sensitive 816

Conventional Arms, Ammunition, and Explosives, Enclosure 9 817 Attachment #12 - OPSEC Requirements, 23 May 2019 818 Attachment #13 - Security Process for Vetting Vendors 819 Attachment #14 - Data Rights Assertions Tables 820 Attachment #15 - Data Rights Information 821 Attachment #16 - Data Rights and Computer Software License Terms and Definitions 822 823

Attachments 1-9 are considered GFI and will be provided in accordance with Section 4 824 of this document. 825