Attachment 4_T2C2 PWS 27Oct2022.docx

Performance Work Statement (PWS) For Transportable Tactical Command Communications (T2C2) Family of Terminals (FoTs) Logistics Documentation

27 October 2022

1. SCOPE

This Performance Work Statement (hereinafter referred to as “PWS”) describes the tasks the Contractor shall perform in order to provide services to the Government in support of the Transportable Tactical Command Communications (T2C2) Family of Terminals (FoTs) Logistics Documentation. The T2C2 program requirements have expanded from consisting of variations of the Transportable Tactical Command Communications (T2C2) (Heavy and Lite) and the Scalable Class of Unified Terminals (SCOUT) (Small and Medium) to include the Ultra Lite, previously known as the Global Rapid Response Information Package (GRRIP), providing required Satellite Communications (SATCOM) capabilities utilizing a family of terminals (FOTs) material solution strategy to satisfy a variety of operational needs associated with providing the fusion of maneuver, fires, intelligence, operations support and sustainment information for select teams/small units at the front edge of the battlefield. This is critical to the Army's ability to conduct Unified Land operations over extended distances in all tactical terrains. The Army will deploy T2C2 FoT capabilities to remote tactical elements whose organic tactical network cannot meet time-sensitive Situational Awareness (SA) or reporting mission requirements.

The T2C2 program terminal portfolio will consist of seven (7) terminal variants each with multiple configurations. These terminal variants operate during all phases of joint operations to augment Line-of-Sight (LOS) and narrowband Beyond Line-of-Sight (BLOS) networks by providing wideband BLOS connectivity with higher echelons. Wideband BLOS connectivity assures more robust synchronized maneuver, fires, space, maneuver support data, rapid information, and data exchange to support intelligence, sustainment, and stability operations in all operational conditions. Below are summary descriptions of each T2C2 FoT variant:

T2C2 1.2M Inflatable Satellite Antenna (ISA) Terminal – Common Name: T2C2 Lite

Summary Description:

The T2C2 Lite supports small teams operating within the tactical network throughout all phases of Joint Operations Command Post (CP) deployed in remote locations without network infrastructure. The terminal consists of Commercial-Off-The-Shelf (COTs) communications and network equipment that includes an inflatable 1.2M Antenna, IDirect Modem, KG-250XS Encryption Device and baseband enclaves that provide Beyond-Line-of-Site Non-classified Internet Protocol (NIPR), SECRET Internet Protocol (SIPR) voice and data via tri-band communications across the Wideband Global Satellite Communications (WGS) constellation (X-Band, Ka Band, Ku Band).

Table 1.0 T2C2 1.2M Inflatable Satellite Antenna (ISA) Terminal T2C2 2.4M ISA Terminal – Common Name: T2C2 Heavy

Summary Description:

The T2C2 Heavy provides satellite communications with robust voice and data capabilities throughout all phases of Joint Operations to company levels and small unit CPs. The T2C2 ISA Heavy supports Mission Command applications and services and will provide DoDIN access while at-the-halt on military satellites or commercial satellites. The terminal consists of COTs communications and network equipment that includes an inflatable 2.4M Antenna, NCW Modem, KG-250X-FC Encryption Device and baseband enclaves that provide Beyond-Line-of-Site Non-classified Internet Protocol (NIPR), SECRET Internet Protocol (SIPR) voice/data via tri-band communications across the Wideband Global Satellite Communications (WGS) constellation (X-Band, Ka Band, Ku Band).

Table 2.0 T2C2 2.4M Inflatable Satellite Antenna (ISA) Terminal

T2C2 1.2M ISA Terminal w/Enhanced Baseband Kits– Common Name: T2C2 Lite Enhanced

Summary Description:

The T2C2 Lite Enhanced is a T2C2 Lite terminal modified to include enhanced baseband capabilities that expands units’ ability to host users from 3 user per secure enclave (6 total) to a total of 21 users per enclave (42 total) at Battalion or above echelon. They are specifically being fielded to Army Brigade Combat Teams (BCTs) designated for the Integrated Tactical Network (ITN). These terminals will provide Beyond-Line-of-Site capabilities down to the battalion level in these units. The terminal consists of COTs communications and network equipment that includes an inflatable 1.2M Antenna, IDirect Modem, KG-250X-FC Encryption Device and baseband enclaves that provide Non-classified Internet Protocol (NIPR), SECRET Internet Protocol (SIPR) voice/data via tri-band communications across the Wideband Global Satellite Communications (WGS) constellation (X-Band, Ka Band, Ku Band).

Table 3.0 T2C2 1.2M ISA Terminal with Enhanced Baseband

T2C2 .65M/.95M Scalable Class of Unified Terminals (SCOUT) – Common Name: SCOUT Small

Summary Description:

The SCOUT small is a sub-one meter SATCOM terminal that provides lightweight, portable satellite communications delivering high-speed broadband access for a wide range of critical missions to austere environments that were once limited to rear echelon assets. The Army directed the fielding of these terminals specifically to Security Force Assistance Brigades (SFABs) to provide Beyond-Line-of-Site capabilities down to the company and team levels in these units. The terminal consists of COTs communications and network equipment that includes a .65M/.95M configurable rigid antenna, CBM-400 Modem, KG-175D Encryption Device and baseband enclaves that provide Non-classified Internet Protocol (NIPR), Secure but Unclassified (SBU) and SECRET Internet Protocol (SIPR) voice/data via tri-band communications across the Wideband Global Satellite Communications (WGS) constellation (X-Band, Ka Band, Ku Band).

Table 4.0 T2C2 .65M/.95M SCOUT Small Terminal T2C2 1.3M SCOUT – Common Name: SCOUT Medium

Summary Description:

The SCOUT medium provides satellite communications that deliver high-speed broadband access for a wide range of critical missions to austere environments that were once limited to rear echelon assets. The Army directed the fielding of these terminals to Security Force Assistance Brigades (SFABs) and ITN designated BCTs to provide Beyond-Line-of-Site capabilities at the brigade level and down to the battalion levels in these units. The terminal consists of Commercial off the Shelf communications and network equipment that includes a 1.3M configurable rigid antenna, CBM-400 Modem (SFAB only), IDirect Modem (ITN BCTs only), KG-175D Encryption Device (SFAB only), KG-250X-FC (ITN BCTs only) and baseband enclaves that provide Non-classified Internet Protocol (NIPR), Secure But Unclassified (SBU) and SECRET Internet Protocol (SIPR) voice/data via tri-band communications across the Wideband Global Satellite Communications (WGS) constellation (X-Band, Ka Band, Ku Band).

Table 5.0 T2C2 1.3M SCOUT Medium Terminal

T2C2 1.3M SCOUT w/Small form Baseband Kits – Common Name: SCOUT Medium -Expeditionary

Summary Description:

The SCOUT Expeditionary will be a new variant that is the direct replacement for the T2C2 Lite. The SCOUT Expeditionary terminal will continue to provide support to small teams operating within the tactical network throughout all phases of Joint Operations CPs deployed in remote locations without network infrastructure. The terminal consists of COTS communications and network equipment that includes a 1.3M rigid antenna, IDirect Modem, KG-250XS Encryption Device and baseband enclaves that provide Beyond-Line-of-Site Non-classified Internet Protocol (NIPR), SECRET Internet Protocol (SIPR) voice/data via tri-band communications across the Wideband Global Satellite Communications (WGS) constellation (X-Band, Ka Band, Ku Band).

Table 6.0 T2C2 1.3M SCOUT Medium Expeditionary

T2C2 Sub 1.0M Terminal – Common Name: T2C2 Ultra Lite

Summary Description:

The T2C2 Ultra Lite is a replacement for the COTS Global Rapid Response Information Package (GRRIP), AN/PSC-15. The Ultra Lite is a small suitcase size communications and computing package that provides secure voice, data and video communication services over satellite links to the Intelligence and Command and Control (C2) communities for 1-4 man teams. The Ultra Lite consists of COTS communications and network equipment that includes a BGAN L-Band antenna, black and red enclaves for NIPR and SIPR connectivity, and a KG-250XS Encryption Device.

Table 7.0 T2C2 Ultra Lite

This Performance Work Statement (PWS) includes both program logistics support requirements and management support services (programmatic, quality and configuration) required for the T2C2 FoT programs. The Government requires logistics support for the development of the logistic documentation required to establish and maintain Sustainment Support Packages (SSPs) for each terminal variant and configuration. This includes technical and training manuals, drawing packages (electronic format and printed materials), and updates to older materials as needed. Tasks on this effort will include Logistics/maintainability analysis, provisioning, technical manuals, training, and development of technical data packages. The Government is providing a Documentation Requirements Matrix (Appendix A) to more clearly define the types of documentation associated with each terminal and the level of development required for each product (new development or updates) for the base year effort. Additionally, in table 1.0 below the Government has identified a summary of all the expected changes required in the contract base year for the different terminal configurations. The Government will also provide additional Government Furnished Information (GFI) associated with the program FRP5 Engineering Change Proposals (ECPs) which are the basis for the base year requirements. The Government will define the requirements for each subsequent option year based on the consolidated ECP package the Government develops for that year’s production efforts and to address any defined obsolescence changes that effect fielded baselines. The Government expects that all documentation after the base year will require content changes that do not exceed 25% of the identified documentation associated with each baseline. The Contractor shall plan to support other service support requirements to include program management, security, engineering and configuration management tasks in each of the subsequent option years when exercised unless directed otherwise by the Government.

Base Year Logistics Documentation Requirements

The scope of this effort also includes providing the Government with key sustainment management support services. The Government requires this support to allow them to manage the terminal programs through their development, production and fielding processes. It also allows the Government to sustain the program once fielding is complete. Tasks efforts associated with this include quality assurance, configuration management, engineering change support and security/software sustainment. The Contractor shall establish required relationships with the Original Equipment Manufacturers (OEMs), sub-contractors, sub-suppliers, or other vendors to comply with or suitably tailor the same requirements as listed in this PWS. The Contractor’s proposal shall identify up-front what vendor relationships are to be established and costs associated with establishing those agreements need to be accurately captured in their proposed costs.

2.0 General Information

2.1 Nondisclosure Agreements

Non-Disclosure Agreement (NDA). Contractor signs agreement: Updated agreements are forwarded to the Contracting Officer.

2.2 Recognized Holidays:

New Year’s Day Martin Luther King Jr.’s Birthday President’s Birthday Memorial Day Juneteenth Day Independence Day Labor Day Columbus Day Veterans Day Thanksgiving Day Christmas Day

2.3 Hours of Operation

The contractor shall be responsible for conducting business on an 8 hour per day, 5 days a week schedule unless otherwise specified in the PWS. The Contractor must at all times maintain an adequate workforce for the uninterrupted performance of all tasks defined within this PWS when the Government is in operation. When hiring personnel, the Contractor shall keep in mind that the stability and continuity of the workforce are essential.

3.0 Requirements

3.1 Point of Contact Information

Technical Point of Contact (POC) CPT Felix Bravo PdM SATCOM

APM, T2C2

Email: felix.a.bravo.mil@army.mil

Phone: 443-395-3060 Mobile: 443-619-9133

A Contracting Officer’s Representative (COR) will also be the POC for Contract Data Requirements List (CDRL) deliverables. The Contract shall submit all CDRLs to the following in addition to the COR listed on the basic contract:

The COR/ACOR monitors all technical aspects of the contract and assists in contract administration The COR/ACOR is authorized to perform the following functions: assure that the Contractor performs the technical requirements of the contract: perform inspections necessary in connection with contract performance: maintain written and oral communications with the Contractor concerning technical aspects of the contract: issue written interpretations of technical requirements, including Government drawings, designs, specifications: monitor Contractor's performance and notifies both the Contracting Officer and Contractor of any deficiencies; coordinate availability of government furnished property, and provide site entry of Contractor personnel. A letter of designation issued to the COR/ACOR, a copy of which is sent to the Contractor, states the responsibilities and limitations of the COR/ACOR, especially with regard to changes in cost or price, estimates or changes in delivery dates. The COR/ACOR is not authorized to change any of the terms and conditions of the resulting order/contract.

3.1.1 Contract Data Requirements Lists

CDRLS are identified on the DD Form 1423 incorporated as an attachment to this PWS. CDRLS under this effort are as follows:

3.1.2 Data Management

The contractor shall utilize the Government provided application called Multi-User Engineering Change Proposal Automated Review System (MEARS) to submit Data Management documentation, CDRLS, Engineering Change Proposals (ECP), and Request for Variance (RFV).

MEARS is a Government-Off-The-Shelf (GOTS) application repository hosted on a .mil domain and meets all RMF and encryption requirements to store government data.

3.2 Government Furnished Equipment (GFE)

The Government will provide the GFE delineated below to support the requirements identified in the delivery order.

3.3 Government Furnished Software (GFS)

The Government will provide the Contractor with the Government Furnished Software (GFS) for all terminal configurations supported by this PWS and as identified in the software configuration baselines included as Appendices B and C)

3.4 Government Furnished Information (GFI)

The Government will provide the Contractor with the Government Furnished Information for the development of required logistics document.

Description

Level of Repair Analysis (LORA) Data – T2C2 Lite AN/TSC-232B (V)1

LORA Data – T2C2 Heavy AN/TSC-233B (V)1

LORA Data - SCOUT Medium AN/TSC-243A(V)2 & AN/TSC-243B(V)2

LORA Data - T2C2 Lite Enhanced AN/TSC-232A(V)2 & AN/TSC-232B(V)2

Maintenance Allocation Chart (MAC) T2C2 Lite (includes all fielded baselines)

MAC T2C2 Heavy (includes all fielded baselines)

MAC T2C2 SCOUT Small (includes all fielded baselines)

MAC T2C2 SCOUT Medium (includes all fielded baselines)

MAC T2C2 Lite Enhanced (includes all fielded baselines)

Logistics Family Tree T2C2 Lite – AN/TSC-232(V)1

Logistics Family Tree T2C2 Lite – AN/TSC-232A(V)1

Logistics Family Tree T2C2 Lite – AN/TSC-232B(V)1

Logistics Family Tree T2C2 Heavy – AN/TSC-233(V)1

Logistics Family Tree T2C2 Heavy – AN/TSC-233A(V)1

Logistics Family Tree T2C2 Heavy – AN/TSC-233B(V)1

Logistics Family Tree T2C2 Heavy – AN/TSC-233C(V)1

Logistics Family Tree T2C2 Lite Enhanced – AN/TSC-232(V)2

Logistics Family Tree T2C2 Lite Enhanced – AN/TSC-232A(V)2

Logistics Family Tree T2C2 SCOUT Small – AN/TSC-243A(V)1

Logistics Family Tree T2C2 SCOUT Medium – AN/TSC-243A(V)2

Logistics Family Tree T2C2 SCOUT Medium – AN/TSC-243B(V)2

Logistics Family Tree T2C2 SCOUT Medium – AN/TSC-243C(V)2

Disposal Plan – T2C2 Lite

Disposal Plan – T2C2 Heavy

Disposal Plan – T2C2 SCOUT Small/Medium

Disposal Plan – T2C2 Lite Enhanced

Provisioning Parts List (PPL) T2C2 Lite (includes all fielded baselines)

PPL T2C2 Heavy (includes all fielded baselines)

PPL T2C2 Lite Enhanced (includes all fielded baselines)

PPL SCOUT Small

PPL SCOUT Medium (includes all fielded baselines)

Training Support Package (TSP) – T2C2 Lite

TSP – T2C2 Heavy

TSP – T2C2 Lite Enhanced

TSP – SCOUT Small

TSP – SCOUT Medium

Technical Data Package – SCOUT Small

Technical Data Packages – SCOUT Medium (includes all fielded baselines)

Full Rate Production (FRP) 5 Engineering Change Proposals (ECPs)

Software Hardware Lists (SHLs)

Safety Assessment Report (SAR) T2C2 Lite and Heavy

SAR T2C2 Lite Enhanced

SAR SCOUT Small and Medium

HSI Plan T2C2 Lite & Heavy

HSI Plan SCOUT Small and Medium

Technical Manual (TM) SCOUT Medium 1.3M: TM 11-5895-2101-13&P

TM SCOUT Small .65M/.95M: TM 11-5895-2102-13&P

TM SCOUT Small/Medium: TM 11-5895-2101-SAM

TM T2C2 Heavy: TM11-5895-2097-13&P

TM T2C2 Lite: TM 11-5895-2098-13&P

TM T2C2 Heavy: TM 11-5895-2097-SAM

TM T2C2 Lite: TM 11-5895-2098-SAM

Item Unique Identification (IUID) Plan T2C2 SCOUT Medium

IUID Plan T2C2 SCOUT Medium Expeditionary

IUID Plan T2C2 Ultra Lite

CF-19 GRRIP Bill of Materials

CF-20 GRRIP Bill of Materials

COTS Manuals

AN/PSC-15 A.K.A Global Rapid Response Information Package Reset Operator Course

3.5 Integrated Support Tasks

3.5.1 Task 1 Program Management

3.5.1.1 Meetings

The Contractor shall host and attend quarterly in-process reviews (IPR) at the Contractor’s facility. Alternate locations or methods for conduct of the IPR shall require prior approval by the Government. The Contractor shall be prepared to conduct an initial kick-off meeting no later than (NLT) 30 days after the award of the delivery order unless the Government specifies a later date for the meeting. The Contractor shall prepare and provide to the Government an agenda not later than 14 days prior to each meeting. The Contractor shall document all planned meetings on the Integrated Master Schedule. The Contractor shall facilitate bi-weekly meetings with each of the OEMs separately with the Government. The Contractor shall provide meeting minutes after each meeting to the Government within 48 hours of meeting.

3.5.1.2. Integrated Master Schedule

The Contractor shall prepare and maintain throughout the life of the contract, an Integrated Master Schedule (IMS) in accordance with CDRL C001. The IMS shall reflect all development efforts in support of the tasks identified in the PWS. The IMS shall also identify dates for all CDRL deliverables, start and completion, Program Status Reviews, IPRs, and other contractual events. The Contractor shall notify the Government of proposed changes to the IMS. Submission of a proposed change to the IMS does not assume Government concurrence or agreement to schedule changes for contract deliveries or events.

3.5.1.3 Contractor’s Progress, Status and Management Report

The Contractor shall prepare and submit a Contractor’s Progress, Status and Management Report in accordance with CDRL A003-101. As part of the MSR, the Contractor shall report progress against metrics that will provide the Government insight into the program progress, critical path items, key pacing events, government furnished equipment status report and overall status (schedule, performance, risk) of T2C2 FOT efforts performed by the Contractor.

3.5.2. Task 2 Logistics

3.5.2.1 Level of Repair Analysis

The Contractor shall develop and update maintenance models for all T2C2 terminal configurations. The model will support the Army's Two-Level Maintenance (TLM) concept (replace forward, repair rear). Organic maintainers (Soldiers) will perform all field level repairs (i.e., replacement of Line Replaceable Units (LRUs)). The maintenance concept shall consider ease of accessibility to failed components and maximize commercially available built-in-tests, self-diagnostics, and common tool sets.

The Contractor shall develop Level of Repair Analysis (LORA) to determine the optimal maintenance concept for the terminals using the United States Army Material Command (USAMC) Logistics Data Analysis Center (LDAC) Computerized Optimization Model for Predicting and Analyzing Support Structures (COMPASS) (available at https://www.aesip.army.mil/irj/portal). Using the outputs from COMPASS, the Contractor shall identify the major maintenance cost drivers, i.e., those costs that account for over 85 percent of maintenance costs. The Contractor shall submit the data per GEIA-STD-0007C and CDRL H003.

3.5.2.2 Maintenance Allocation Chart

The Contractor shall prepare a Maintenance Allocation Chart (MAC) that will identify the maintenance functions that must be performed, the maintenance level responsible for the function, and the active repair time, tools, and test equipment necessary to perform the function for each repairable assembly and subassembly of the terminal variants. The Contractor shall submit the MAC for each end item per CDRL H004 and MIL-STD-40051 and its reference materials. MACs must comply with the military standard version identified for the applicable technical manual identified in PWS section 3.5.2.9.

3.5.2.3 Logistics Family Tree

The Contractor shall prepare and submit a Family Tree per CDRL H001 for every baseline in accordance with (IAW) the Documentation Requirement Matrix. In Contractor format, the Contractor shall develop a Family Tree for the system that graphically depicts the generation of a top-down breakdown structure of the terminals from the end item down to the lowest repairable assembly and includes all additional critical support hardware. At a minimum, the Contractor shall identify each system item by name/nomenclature, part number and Functional Group Code (FGC) which indicates its relationship to its next higher assembly. FGC assignment shall correspond to the top-down breakdown sequence of the system/end item.

3.5.2.4 RESERVED

3.5.2.5 Disposal Plan

The Contractor shall develop or update a disposal plan for each terminal variant that address all the identified configurations in accordance with DA PAM 700-127 and CDRL D001. The plan shall outline the disposal of system components in compliance with national and foreign environmental laws and regulations.

3.5.2.6 RESERVED

3.5.2.7 Provisioning

The Contractor shall develop or update the provisioning for the Government consistent with the Government-approved MAC and Repair Parts and Special Tools List (RPSTL). The Contractor shall attend an initial Provisioning Guidance meeting concurrent with the Kick-Off meeting. At this time, the Government Provisioning Representative will provide any additional guidance necessary for the Contractor to support the provisioning effort. The Contractor shall support additional Provisioning Meetings, including 30%, 70% and 100% reviews of the Provisioning Technical Documentation (PTD) specified herein during regularly scheduled IPRs or via teleconference.

3.5.2.7.1 Provisioning Parts List

The Contractor shall prepare a Provisioning Parts List (PPL) per CDRL H005 and Appendix E Annex 1 of this PWS.

3.5.2.7.2 Design Change Notice (DCN)

The Contractor shall submit revisions to the PTD for established baselines as a DCN. The Contractor shall prepare and submit DCNs per the requirements of this PWS and CDRL H006. The Contract shall submit DCNs for any changes that affects the part number of a part or assembly that is listed in the PTD or: any change that affects the listing of piece parts for a repairable assembly and any change that affects the technical manuals. The Contractor shall provide DCN data to the Government on the required medium IAW the data requirements format of Appendix E and the other applicable provisioning requirements of the appendix. DCNs are not required for changes that have no impact on the provisioning documentation.

3.5.2.7.3 Engineering Data for Provisioning

The Contractor shall submit Engineering Data for all items on the PPL, which do not have National Stock Numbers (NSNs) assigned, per Appendix E Annex 2 of this PWS, CDRL H007 and DoD 4100.39-M.

3.5.2.7.4 Repair Parts & Special Tools List

The Contractor shall prepare RPSTLs per Annex 5 to Appendix E of this PWS and CDRL H008. The RPSTL shall be a part of the Technical Manual as a -13&P, developed to support all the maintenance tasks in the Maintenance Allocation Chart, Technical Manual and Provisioning Parts List. This document will be supportive of the 13 level Technical Manual.

3.5.2.8 Training Material

3.5.2.8.1 User Training Materials

The Contractor shall conduct a Training Task and Skill analysis IAW Training and Doctrine Command (TRADOC) Regulation 350-70 to identify all system operational and maintenance tasks and provide a basis for the selection or non-selection for training. The analysis shall include the following factors: criticality of correct performance, training emphasis rating, and difficulty of performance. The Contractor shall utilize the results of the analysis for the development of the training materials.

The Contractor shall develop and provide Training Materials in accordance with CDRL B001. The Contractor shall provide Training Materials in support of each training course conducted in support of this development effort and shall also provide a Digital Video Disc (DVD) with each terminal delivered. In accordance with Defense Federal Acquisition Regulation Supplement (DFARS) 252.227-7013, the Government is entitled to an “unlimited rights” license in non-commercial data necessary for operation, maintenance, or training, and the Government is entitled to an “unrestricted rights” license to commercial data necessary for operation, maintenance, installation, or training under DFARS 252.227-7015. Government shall be provided with an “unlimited rights” (or “unrestricted rights”) license to the Operator & Maintainer (O&M) training material.

Training Material shall support the O&M Training Material tasks to include:

· Introductory Training Brief

· Operator Training

· Installation Training

· O&M Training (Preventive and Corrective)

· O&M Training Troubleshooting

· Quick Start Guide

Training materials developed by the Contractor shall be reusable for refresher training, institutional training and Distance Learning. Commercially available materials may be used as well as newly developed materials where none exist. The Contractor shall provide the following training materials and/or updates, as necessary for any training courses conducted in support of this development effort. The Contractor shall deliver all training material in Microsoft Office Suite:

· Program of Instruction

· Test Package i.e., Written/Performance Test

· Instructional Media Package i.e., Instructional Media Guide

· Lesson Plan

· Student Training Guide

· Practical/Performance Exercises

The Contractor shall provide one hardcopy Student Training Guide for each student in each class. The Contractor shall ensure that all training material developed under this contract is compatible with the Shareable Courseware Object Reference Model (SCORM)/reusable content.

The Contractor shall conduct three Training Meetings at the Contractor facility. These meetings are to align with the development of approximately 30 %, 70 % and 100 % of the materials per CDRL B001. Prior to the meetings, the Contractor shall discuss the agenda with the Government training representative. As a minimum, the Contractor shall have their training developer at all Training Meetings. The purpose of the Training Meetings is to allow the Government representatives to review training materials, schedules, and required equipment and facilities. The Contractor and the Government will coordinate the timing of the meetings. A 100% verification of the training documentation shall be conducted during the Technical Manual validation and verification held at the Contractor’s facility.

The Contractor shall develop all courses using MIL-PRF-29612B and TRADOC Regulation 350-70 as guidance. The courses shall adhere to the TRADOC Army Learning Policy and Systems (ALPS) emphasis on analysis, design, development, implementation, and evaluation (ADDIE) process and Training Development Capabilities (TDC) process (http://TDC.army.mil/). The Contractor shall structure each training course so that no less than 60 percent of each course is devoted to practical exercises.

3.5.2.8.2 DELETED

3.5.2.9 Electronic Technical Manuals (ETM) and Interactive Electronic Technical Manuals (IETM)

The Contractor shall develop, format, review, quality control and maintain system level Operator and Field Level Maintenance Manuals and Software Users/Administrators Manuals for each of the terminal variants as detailed in the paragraphs that follow.

In accordance with DFARS 252.227-7013, the Government is entitled to an “unlimited rights” license in non-commercial data necessary for operation, maintenance, or training, and the Government is entitled to an “unrestricted rights” license to commercial data necessary for operation, maintenance, installation, or training under DFARS 252.227-7015. Thus, the Government shall be provided with an “unlimited rights” (or “unrestricted rights”) license to the TMs.

3.5.2.9.1 Electronic Technical Manuals (ETM)

The Government will provide guidance for tailoring of TM contents during the Post Award Technical Manual start of work meeting. The Contractor shall develop technical manual content updates in keeping with the appropriate Content Matrixes provided in Appendix A of MIL-STD-40051-2C as detailed in Appendix F of this PWS.

3.5.2.9.1.1 Operator and Field Level Maintenance Manuals-Page Based.

The Contractor shall develop updates, format, review, quality control and maintain system level Operator and Field Level Maintenance Manuals for each of the applicable terminal variants identified in the Document Requirements Matrix (Appendix A) and IAW CDRL J001. A RPSTL shall be incorporated as part of the TM as a -13&P Operator and Field Maintenance Manual Including Repair Parts and Special Tools List.

The scope of the manuals shall include all information required for operation and field support of the terminals, including system and equipment operation and maintenance, installation, setup, alignment, Preventive Maintenance Checks and Services (PMCS), fault isolation, LRU removal and replacement procedures, de-installation, and preparation for transportation. The maintenance information shall reflect the Maintenance Concept as presented in the standard MAC. The Contractor shall provide other information necessary to implement the required logistics support strategy, including, but not limited to, warranty procedures (if applicable) and instructions for the repair and return of unserviceable LRUs. The Contractor shall also provide updates to reflect any configuration changes throughout the life of the contract.

3.5.2.9.1.2 Software Users and Software Administrators Manuals-Page Based.

The Contractor shall develop updates, format, review, quality control and maintain system level Software Administrators Manual for each of the applicable terminal variants identified in the Document Requirements Matrix (Appendix A) and IAW CDRL J002.

The scope of the SUM/SAM shall include all information required for software related procedures to include configure, update/patch, and troubleshoot software related issues. The software maintenance information shall reflect the Maintenance Concept as presented in the standard MAC. The Contractor shall also provide updates to reflect any configuration changes throughout the life of the contract.

3.5.2.9.2 Interactive Technical Manuals (IETM)

For Interactive Electronic TMs (IETM) Contractor shall use Extensible Mark-up Language (XML) tagged data files using MIL-STD- 40051-1, Document Type Definitions (DTDs) and style sheets in accordance with MIL-STD-45001-1 (latest version) using guidance found in MIL-HDBK-1222 (latest version), MIL-STD-3031/ASD, MIL-PRF-63002 (latest version), and MIL-PRF- 63033 (latest version). “Latest version” throughout this PWS means the most current version of the MILSTD or PRF.

The Government will provide guidance for tailoring of TM contents during the Post Award Technical Manual start of work meeting. The Contractor shall develop technical manual content in keeping with the appropriate Content Matrixes provided in Appendix A of MIL-STD-40051-1D and as detailed in Appendix G of this PWS. A RPSTL shall be incorporated as part of the TM as a -12&P Operator and Field Maintenance Manual Including Repair Parts and Special Tools List in accordance with MIL-STD-40051-1D, as determined by the Government.

3.5.2.9.2.1 Operator and Field Level Maintenance Manuals – IETM

The Contractor shall develop, format, review, quality control and maintain system level Operator and Field Level Maintenance Manuals for each of the applicable terminal variants identified in the Document Requirements Matrix (Appendix A) and IAW CDRL J003. A RPSTL shall be incorporated as part of the TM as a -13&P Operator and Field Maintenance Manual Including Repair Parts and Special Tools List and include Software Administrator content.

The scope of the manuals shall include all information required for operation and field support of the terminals, including system and equipment operation and maintenance, installation, setup, alignment, Preventive Maintenance Checks and Services (PMCS), fault isolation, LRU removal and replacement procedures, de-installation and preparation for transportation. The scope of the manual shall also include all software related procedures to include configure, update/patch, and software related troubleshooting. The maintenance information shall reflect the Maintenance Concept as presented in the standard MAC. The Contractor shall provide other information necessary to implement the required logistics support strategy, including, but not limited to, warranty procedures (if applicable) and instructions for the repair and return of unserviceable LRUs. The Contractor shall also provide updates to reflect any configuration changes throughout the life of the contract.

3.5.2.9.2.2 Use of Commercial Manuals

The Contractor may supplement the O&M manuals with copies of all Commercial-off-the-Shelf (COTS) manuals for each major commercial…