STS RFI Attachment 1 - STS Log Development PWS 1 July 2024_Updated Control.docx

CUI

Performance Work Statement (PWS) For Sustainment Transport System (STS)

ARMY CONTRACTING COMMAND (ACC) – ABERDEEN PROVING GROUND (APG)

ABERDEEN PROVING GROUND, MD, 21005

Version 01

1 July 2024

PROGRAM EXECUTIVE OFFICE

COMMAND, CONTROL, COMMUNICATIONS – TACTICAL

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

Table of Contents

1.0 Scope

This Performance Work Statement (hereinafter referred to as “PWS”) describes tasks the Contractor shall perform in order to provide logistics documents and services to the Government in support of the Sustainment Transport System (STS). The STS program consists of three systems: STS Satellite Communications (SATCOM), STS Line of Sight (LOS), and STS Wireless Fidelity (Wi-Fi). STS is the Army’s Program of Record (PoR) which enables communications resources to sustainment forces operating independently in forward and dispersed locations. STS provides global access to over 120,000 Sustainment Information System (SIS) and Enterprise Resource Planning (ERP) (e.g., Global Command Support System-Army (GCSS-A) and Integrated Personnel and Pay System-Army (IPPS-A)) application users who rely on sustainment communications connectivity to transmit and receive data to support the warfighter. STS provides critical connectivity on the battlefield where the Integrated Tactical Network (ITN) and other communication systems do not extend to dispersed and forward deployed sustainment units.

The Product Management (PdM) Unified Network Capabilities and Integration (UNCI) office procured Low-Rate Initial Production (LRIP) quantities of the STS hardware and associated software. Support described within this PWS will include documentation and services to inform logistics and sustainment efforts for both the LRIP configurations and future Full-Rate Production (FRP) configurations. In addition to future FRP configurations, it is expected the Contractor shall perform updates to applicable Logistics Documentation (to include but not limited to Technical Manuals, Level of Repair Analysis, Maintenance Allocation Charts, Training Material, etc.) following Government approval of Engineering Change Proposals (ECPs).

1.1 System Overview

The STS program consists of three (3) systems. Below are summary descriptions of each current LRIP STS systems. Future production configurations (such as FRP) shall be updated in the Logistics Documentation, as required.

Sustainment Transport System Satellite Communications (STS SATCOM)

Summary Description:

STS SATCOM LRIP configuration includes satellite and baseband transport equipment which consists of one (1) STS SATCOM terminal capable of accessing X-band, Ka-band, and Ku-band satellites. The terminal is comprised of a 1.2M hard-dish Antenna, Tripod, X-band Feed, Ka-band Feed, Ku-band Feed, Satellite Modem, and Pointing-Assist Tablet. STS SATCOM consists of baseband equipment consisting of one (1) server, two (2) switches, one (1) manager laptop, and baseband cabling.

Table 1.0 STS SATCOM Description

Sustainment Transport System Line of Sight (STS LOS)

Summary Description:

The STS LOS LRIP configuration includes one radio, one antenna, one mast, and spectrum licenses which resides in four transit cases that provides a flexible network extension capability (i.e., point-to-point, and multi-point configurations) to extend transport connectivity and services to a minimum of 30 kilometers (km) and a minimum of 25 megabits per second (Mbps) network capacity.

Table 2.0 STS LOS Description

Sustainment Transport System Wireless Fidelity (STS Wi-Fi)

Summary Description:

STS Wi-Fi includes wireless and baseband transport equipment which consists of two (2) Wi-Fi Access Points, one (1) manager laptop, one (1) switch, one (1) server, and baseband cabling to provide secure and increased wireless communications and data transmissions using 802.11ax standards within unit networks. STS Wi-Fi will provide wireless sustainment network connectivity and services to a minimum of 300 meters and a minimum of 50 megabits per second (Mbps) network capacity.

Table 3.0 STS Wi-Fi Description This PWS includes logistics documentation and logistics services. Logistics services include program logistics support requirements and management support services (programmatic, quality and configuration) required for the STS program.

Documentation The Government requires support in the development and/or updating of logistic documentation required to establish and maintain Sustainment Support Packages (SSPs) for each system and configuration. In Accordance With (IAW) Contract Data Requirements List (CDRL) E001, the Sustainment Support Package Component List (SSPCL) will be utilized as the primary source document to identify and verify all required major items of support, such as: technical and training manuals, drawing packages (electronic format and printed materials), and updates to older materials as needed.

Services Tasks on this effort shall include updating Logistics/maintainability analysis, provisioning, and development of technical data packages (will be deliverables on this contract).

The contractor shall also provide the Government with sustainment management support services to help the Government to sustain the systems once fielding is complete. Task efforts associated with this include (but are not limited to) quality assurance, configuration management, engineering change support and security/software documentation. In order to help the Government manage the terminal programs through their development, production, and fielding process 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 agreements are to be established and the costs associated with establishing those agreements need to be accurately captured in their proposed costs.

1.2 Period of Performance

The period of performance shall be one 12-month base period and three 12-month option periods from date of award.

1.3 Place of Performance

The work to be performed under this contract will be performed at the Contractor’s facility.

2.0 General Information

2.1 Non-disclosure Agreements

All Contractor employees assigned to or reviewing STS products shall sign a non-disclosure agreement, which will be provided by the Government. Updated agreements are forwarded to the Contracting Officer.

2.2 Federal Holidays:

The Government will observe Federal Holidays IAW the Office Of Personnel Management’s (OPM) holiday calendar; which can be viewed at: https://www.opm.gov/policy-data-oversight/pay-leave/federal-holidays/. These days will not count as business days for the Government, with the exception of Inauguration Day (2025).

2.3 Contractor Operations

The Contractor shall be available during normal business hours (8 hour per day, 5 days a week) to ensure availability to Government POCs and attendance at recurring meetings, unless otherwise specified in the PWS. Core Government business hours are typically between 0800 – 1600 Eastern Standard Time (EST). Any deviation from these core hours shall be discussed with PdM UNCI Government Points of Contact (POCs).

The Contractor must always maintain an adequate workforce for the uninterrupted performance of all tasks defined within this PWS. The stability and continuity of the Contractor workforce are essential; therefore, the Contractor shall ensure there are no interruptions in service, especially when hiring personnel.

2.4 Point of Contact Information

Technical POC:

Megan Newsome PdM UNCI Product Support Manager Email: megan.e.newsome2.civ@army.mil Phone: 520-672-6549 Mobile: 270-484-3294

The Contracting Officer’s Representative (COR) will also be the POC for CDRL deliverables. The Contract shall submit all CDRLs to the following POC in addition to the COR listed on the 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 Equipment (GFE), 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/or conditions of the resulting order or contract.

3.0 Requirements

3.1 Contract Management

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 this PWS. The Contractor shall control, use, preserve, protect, repair, and maintain all Government Property IAW FAR 52.245-1.

AN/TSC-277(V)1

The Property Management Plan provided at solicitation IAW FAR 45.201(c)(4) shall be a description of the property management system to be used in managing Government property. No later than 60 calendar days after contract award, the Contractor shall submit the Property Management System procedures IAW CDRL B002 and FAR 52.245-1(f). Changes thereafter to the Property Management System must be approved by the Property Administrator prior to implementation.

The Contractor shall submit a Government Property (GP) Inventory Report IAW CDRL B002, Government Property (GP) Inventory Report. This report describes the status and supply data about Government Furnished Property (GFP) and Contractor Acquired Property (CAP) which the Contractor has received or acquired under the contract. This report will be used to review the condition, installation, and effectiveness of the GP.

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 in Appendices B and C.

3.4 Government Furnished Information (GFI)

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

Description

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 (such as Microsoft Teams) 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 calendar 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 7calendar days prior to each meeting. The Contractor shall document all planned meetings on the Integrated Master Schedule (IMS). The Contractor shall facilitate meetings with the Government and each of the OEMs separately on a monthly basis at a minimum, or more frequently as needed. The Contractor shall provide meeting minutes after each meeting to the Government within 48 hours of meeting. The Contractor shall ensure the appropriate Government POCs are available for meetings.

3.5.1.2. Integrated Master Schedule

The Contractor shall prepare and maintain throughout the life of the contract, an IMS in accordance with CDRL C001. The IMS shall be created in Microsoft Project and 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 and provide a get-well plan for any schedule slips or delays in deliverable items. 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 monthly Contractor’s Progress, Status and Management Report in accordance with CDRL A003-101. As part of the Monthly Status Report (MSR), the Contractor shall report progress against metrics that will provide the Government insight into: program progress, critical path items, key pacing events, Government furnished equipment, status report and overall status (schedule, performance, risk) of STS 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 STS 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 a Level of Repair Analysis (LORA) to determine the optimal maintenance concept for the terminals using the United States Army Material Command’s (USAMC) Logistics Data Analysis Center (LDAC) Computerized Optimization Model for Predicting and Analyzing Support Structures (COMPASS) tool (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 of the three STS hardware baselines, per CDRL H004, Military Standard (MIL-STD) MIL-STD-40051 and its reference materials.

3.5.2.3 Logistics Family Tree

The Contractor shall prepare and submit a Family Tree per CDRL H001 for each baseline, IAW the Documentation Requirement Matrix (Appendix A). 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 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.5 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. Percentage of work complete will be measured as follows:

· 30%: Initial draft Work Package and TM outline, initial family tree, MAC, data for FMECA, and data for LORA

· 70%: Final MAC and final family tree

· 100%: Validation just after Provisioning Conference

3.5.2.5.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.5.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 Contractor shall submit DCNs for any changes that affects the part number of a part, an assembly that is listed in the PTD, 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 aforementioned provisioning documentation.

3.5.2.5.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 Department of Defense (DoD) 4100.39-M.

3.5.2.5.4 Packaging Data

The contractor shall develop cost efficient, “Military Preservation”, level A or B packaging data for all newly provisioned items with a Source, Maintenance & Recoverability (SMR) code beginning with “P”, excluding “PR” and “PZ”, IAW MIL-STD-2073-1. The Contractor shall develop this data utilizing the item classification definitions in MIL-STD-2073-1. This data shall be prepared IAW DI-SESS 81758 Logistics Product Data and DI-SESS-81759 Logistics Product Data Summaries; and deliver IAW CDRL K001. It shall be documented and delivered in Logistics Support Analysis (LSA) 025 reports IAW GEIA-STD-0007, SAE GEIA-HB-0007, and TA-HB-0007. Requirements for bar coding, marking, warning labels and tags shall be IAW MIL-STD-129.

The packaging data generated shall reflect one increment of the provisioned Unit of Issue. For packaging data development purposes, the Quantity per Unit Pack (QUP) shall equal one (001).

3.5.2.5.4.1 Special Packaging Instructions (SPI’s)

Packaging requirements too complex to be specifically and accurately coded shall require a Special Packaging Instruction (SPI). The SPI shall be prepared IAW DI-PACK-80121C and DI-MISC-81499A. The Kit Contents List shall be prepared and attached to applicable Special Packaging Instruction and delivered IAW CDRL K002. Additionally, a DD Form 2169 and 2169 (Continuation form) IAW DA PAM 700-32 and Appendix E of MIL-STD-2073-1 shall be required for each SPI.

All Wood Boxes, Wood Skids, Wood Filler Assemblies, Wood Dunnage Assemblies, and Wood Pallets shall be International Standards for Phytosanitary Measures No. 15 (ISPM-15) Compliant.

3.5.2.5.5 Repair Parts & Special Tools List (RPSTL)

The Contractor shall prepare RPSTLs per Appendix E (Annex 4) of this PWS and CDRL H008. The RPSTL shall be a part of the Technical Manual as a -12&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 12 level Technical Manual.

3.5.2.6 Training Material

3.5.2.6.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; all training material shall be delivered via digital download on the Government funded Contract Management MEARS portal. IAW 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. Per DFARS 252.227-7015, the Government is entitled to an “unrestricted rights” license to commercial data necessary for operation, maintenance, installation, or training. The 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 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, as stated in PWS section 3.5.2.5 and CDRL B001. Prior to the meetings, the Contractor shall discuss the agenda with the Government training representative. At 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 the required equipment and facilities. The Contractor and the Government will coordinate the timing of meetings. A 100% verification of the training documentation shall be conducted after technical manual verification at the Contractor’s facility.

The Contractor shall develop all courses using Military Performance Specification (MIL-PRF) MIL-PRF-29612B and TRADOC Regulation 350-70 as guidance. The courses shall adhere to TRADOC Army Learning Policy and Systems (ALPS) with emphasis on both the 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% of each course is devoted to practical exercises.

3.5.2.7 Interactive Electronic Technical Manuals (IETM)

The Contractor shall update, 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.

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

3.5.2.7.1 Technical Manuals (TM)

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

3.5.2.7.1.1 Operator and Field Level Maintenance Manuals

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 -12&P Operator and Field Maintenance Manual including a Repair Parts and Special Tools List in accordance with MIL-STD-40051-1D, as determined by the Government.

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.7.2 Interactive Electronic Technical Manuals (IETM)

For Interactive Electronic TMs (IETM) Contractor shall use Extensible Mark-up Language (XML) tagged data files using the current 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 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 F of this PWS. A RPSTL shall be incorporated as part of the TM as a -12&P Operator and Field Maintenance Manual including a Repair Parts and Special Tools List in accordance with MIL-STD-40051-1D, as determined by the Government.

3.5.2.7.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 J001. 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 and include Software Administrator content.

The scope of the manuals shall include all information required for operation and field support of the three terminals variants, 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.7.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 component contained in the terminals when approved by the Government. The (TM) shall take precedence for the user in any discrepancies between the O&M Manual and any of the COTS manuals for system level operations, preventive maintenance, maintenance, installation, set up, alignment procedures, and teardown and preparation for stow and transportation.

3.5.2.7.2.3 Copyright Release Statement for Commercial Manuals The Contractor shall obtain copyright release statements and reproduction rights for COTS manuals. The Contractor shall provide the manuals with each system and deliver as per the Government’s chosen means of delivery (i.e., digital download, DVD, etc.). The Contractor shall digitize any paper-only, existing commercial manuals and convert them into electronic products.

The Contractor shall provide the following Release Statement with all commercial manuals submitted under this contract:

(NAME) DATE:

(ADDRESS) (SALUTATION) RELEASE

The U.S. Army Communications Electronics Lifecycle Management Command (CECOM-LCMC) has an “unlimited rights” license or an “unrestricted rights” license (as defined in DFARS 252.227-7013 and DFARS 252.227-7015, respectively) to identify each commercial manual by equipment, number, and title. CECOM-LCMC may include this publication in the printing materials submitted to the Government Printing Office (GPO) to be published for Government purposes. The Release is royalty free. A credit line (is) (is not) requested.

(Name of copyright holder or authorized agent) By (Title)

3.5.2.7.3 Source Data

The Contractor shall develop the TMs according to the source data listed in this section. The Contractor shall package and deliver to the Government all source material, defined as operating plans, standard procedures, computer programs, and residual material to include computer disks, computer tapes, and all other media containing digital files developed to fulfill the requirements of this PWS.

· Applicable Engineering Change Order (ECOs)/Engineering Change Proposals (ECPs)

· Existing manuals

· Existing digital files

· Maintenance Allocation Chart (MAC)

· Target Audience Descriptions

· Front Matter “Boilerplate”

· Appendices “Boilerplate”

3.5.2.7.4 Technical Manual In-Process Reviews

The Contractor shall coordinate Technical Manual In-Process Reviews when approximately 30%, 70%, and 100% of the technical manuals are developed, as stated in PWS section 3.5.2.5. Unless directed otherwise by the Government, the Contractor shall coordinate In-Process Reviews as in-person events held at the Contractor’s facility or another facility at the Government’s approval. Throughout the entirety of the Technical Manul IPR, the Contractor shall be prepared to perform live edits/corrections of the materials to the maximum extent possible during the event and will record and track all TM changes on a Comment Resolution Matrix (CRM), to be made available to the Government during the development and review process of the manual.

3.5.2.7.5 Validation

The Contractor shall conduct TM validations at the Contractor’s facilities. In addition to content validation, the Contractor shall validate all Electronic Technical Manual (ETM) functional features as operational and correct. The Contractor’s validation records shall be available for Government inspection at any time. The Government reserves the right to witness the Contractor validation. In such instances, the Contractor shall be prepared to perform live edits/corrections of the materials to the maximum extent possible during the event and will record and track all technical manual changes on a CRM, to be made available to the Government.

3.5.2.7.6 Verification

The Government will perform a verification of all final draft TMs after the completion of the validation event to include incorporation of all comments and correction actions throughout the development and review process. The Government will verify the TMs by performing a 100% check of the operating and maintenance procedures using target audience personnel to perform all documented procedures. The Government will conduct a 100% desk review of those portions of the publication not subject to hands-on performance (e.g., table of contents, theory, index, etc.). The Government will verify that all functional features identified in the TMs are operationally accurate and representative. The Contractor shall be prepared to host the verification at their facility unless directed otherwise by the Government. The Contractor shall be prepared to perform live edits/corrections of the materials to the maximum extent possible during the event and will record and track all technical manual changes on a CRM made available to the Government during event. The Contractor shall provide (at the verification site) copies of each final draft TM to be verified, an appropriate office or work space with sufficient hardware to read each TM, a working copy of the equipment to be verified (including applicable hardware and software), personnel necessary to document changes to the publications and resolve hardware and software issues, and all tools and test equipment required, according to the Maintenance Concept/MAC, to perform all procedures in each TM. The Contractor shall correct all errors found in Extensible Markup Language (XML) instance and graphics during verification, at no additional cost to the Government.

The Contractor shall:

a. Record and maintain records during the verification process (via a CRM).

b. Provide assistance to the Technical Manager or their designated representative during the verification and provide the Government with a copy of the discrepancies revealed.

c. Make necessary corrections to discrepancies revealed during the verification process.

d. Provide the Technical Publications Representative or their designated representative with a report of the corrective actions taken.

e. Provide administrative support for completion of the verification.

3.5.2.7.7 Incorporation of Comments

The CECOM-LCMC is the Government publications acceptance activity for this contract. The Contractor shall forward any publications comments received from other Government activities to the address provided at the Government Guidance Meeting.

3.5.2.7.8 Technical Manual/Interactive Electronic Technical Manual Delivery Requirements

The Contractor shall deliver IETMs digitally to the Contracting Officer’s Representative (COR) IAW CDRL J001. The Contractor is required to provide hard copies of the TMs for all events during this effort to include TM and Training IPRs, TM and Training verification events and the Logistics Demonstration. The Contractor shall provide the source data for any IETM development efforts with any deliveries made in support of IPRs or final CDRL submissions.

3.5.2.7.9 Format

The Contractor shall submit the TMs in hardcopy and submit the IETMs per the Government’s chosen delivery method (i.e., digital download, DVD, etc.). The IETM format shall be searchable in Adobe Acrobat PDF format with embedded fonts, and in the native format of the software used for preparation. Native format shall be XML, IAW MIL-STD-40051-1D and reference materials. The Contractor shall deliver XML source data with the delivery of the PDF formatted manuals. These deliveries need to be to the proper naming format and have dataset and include table of contents, source graphics and style sheets. The TMs and IETMs shall be prepared in a suitable authoring environment that conforms to the specifications contained in MIL-STD-40051-1D. In addition, the Contractor shall contact the Government to determine if the Government will require delivery of one licensed copy of the authoring software. The Contractor shall deliver validated manuals in PDF and XML file formats to the most current Logistics Data Analysis Center with approved stylesheets upon successful completion of a Verification event attended by the Government. The manuals shall be written in XML and also be readable in Interactive Authoring and Display Software (IADS).

3.5.2.7.10 Final Material Review

The Government will conduct a review of the final material to ensure the material meets the requirements of the PWS and that the Contractor incorporated all comments previously provided. In the event that the Government rejects the material as a result of final copy review, the Government will notify the contractor of the rejection by official letter, including the specific rejection comments. The Contractor shall address all comments noted in the rejection letter and provided updated materials for another final review. The Government will notify the Contractor of acceptance by official correspondence (letter or email).

3.5.3 Task 3 - Security

3.5.3.1 National Institute of Standards and Technology Certification

The Contractor shall obtain and maintain National Institute of Standards and Technology (NIST) Federal Information Processing Standards (FIPS) 140-2 certification under the Cryptographic Module Validation Program on appropriate components such as routers and switches implementing encryption.

3.5.3.2 Information Assurance Vulnerability Alerts (IAVA) Release and Security

The Contractor shall verify all IAVAs or Security Technical Implementation Guides (STIG) which apply to Original Equipment Manufacturer (OEM) developed hardware, associated firmware, and OEM proprietary source code that has a network presence. The Contractor shall notify the Government when these items are affected. The Contractor shall maintain a record of all hardware, firmware, and proprietary source code approved mitigations that the Contractor has applied. The Contractor shall make this information available to the Government on a bi-weekly (minimum) or as need basis if required more frequently. The Contractor shall verify OEM’s developed non-network presence hardware, its associated firmware, and OEM’s proprietary source code must meet Army Regulation (AR) 25-2 “Army Cybersecurity”, DoDI 8500.1 “Cybersecurity”, NIST SP 800 series publications, and DoDI 8510.01 standards. However, the Contractor does not need to report these items to the Government, unless requested.

3.5.3.3 Information Security

The Government will provide and the Contractor shall follow information security (INFOSEC) guidance contained within the PM TN Security Classification Guide (SCG), as directed in the DD Form 254. The Contractor shall ensure that this requirement flows down to all sub-contractors.

3.5.3.4 Cyber Security/Information Assurance Certification and Training

The Contractor shall meet the Cybersecurity/Information Assurance Technical (IAT) certification level and training required to perform elevated system administrative capabilities.

In discharging its responsibility under the contract, the Contractor shall only use fully trained, experienced, appropriately certified, and technically proficient personnel. Consistent with the DFARS 252.239-7001, Information Assurance Contractor Training and Certification, the contractor shall ensure that personnel accessing information systems have the proper and current cybersecurity (also known as Information Assurance (IA)) certification required to perform IA functions IAW DoD 8570.01-M, Information Assurance Workforce Improvement Program. The Contractor shall meet the current and applicable DoD and Army cybersecurity/IA certification requirements, including:

a. DoD-approved cybersecurity/IA workforce baseline certifications appropriate for each category and level as listed in the current version of DoD 8570.01-M that provides the implementation guidance for DoDD 8140.01 Cyberspace Workforce Management, August 11, 2015.

b. The Contractor shall provide documentation supporting the Cybersecurity/IA certification status of personnel performing IA functions. The contractor is required to properly register and ensure unit alignment is entered for all their personnel performing under the contract with the Army Training and Certification Tracking System (ATCTS) upon contract award by coordinating for registration of their personnel with the Government Information System Security Manager (ISSM) having purview over the applications, networks, and systems they support. The contractor must ensure they complete the mandated Annual Cyber Awareness Challenge Training, and the IA contractor workforce must ensure they complete Cyber Security Fundamentals training in ATCTS. The Contractor must work with the Government ISSM to ensure all information and forms in ATCTS are accurate, including contract/task order numbers and task order period of performance dates. The appropriate network access must be completed prior to accessing any Government systems. All access documents must be approved or verified by Government ISSM before access is granted. This is a requirement for those individuals that perform IA duties.

c. Contractor personnel who do not have proper and current certifications shall be denied access to DoD information systems for the purpose of performing cybersecurity/IA functions and shall not be permitted to perform under this contract. The Contractor is responsible for making sure that their personnel properly maintain their training record in ATCTS, as directed by the Government ISSM.

3.5.4 Task 4 - Engineering

3.5.4.1 Safety Assessment Report

The Contractor shall develop and update a Safety Assessment Report (SAR) IAW this PWS, Task 301 of MIL-STD-882E and CDRL G001, for each terminal. The SAR shall document the safety risk associated with the system prior to training, test or operation of the terminals. The SAR shall identify all safety features of the system hardware and software configurations, specific controls or precautions followed in the use of the terminals and shall provide verification of compliance to all safety requirements. Non-compliance of specified safety requirements shall be documented and justified (justification for noncompliance is not to be construed as approval by the Government; noncompliance requires separate written approval by the Government).