CSS0130_Draft PWS for RFI.docx

Performance Work Statement (PWS)

FOR

Satellite Communications as a Managed Service (SATaaMS)

AT

[PERFORMANCE LOCATION]

09 July, 2024 Version 1.0

DRAFT

Controlled by: Commercial Satellite Communications Office (CSCO) CUI Category: PROCURE Distribution: NONE POC: Antoine Myers, antoine.u.myers.civ@mail.mil

Sustainment Transport COMSATCOM Network

CUI

Contents

SECTION I

1.0 DESCRIPTION OF SERVICES

The US Army is seeking a highly reliable and secure communication network for the Army with worldwide coverage. The communication network will ensure uninterrupted data transfer, voice communication for the warfighter. The offeror must meet at least a 6 Mbps download and a 2 Mbps upload. These are only the very minimum requirements, but the Army seeks higher and cost-effective data plans. All SATaaMS (hardware and services) requirements are outlined in sections two thru seven.

In addition, the US Army seeks a vendor to supply iDirect SATCOM terminals will be used for the Sustainment Transport System (STS) Program. The SATaaMS portion to STS will provide: multiband-capable SATCOM terminals, SATCOM terminal training, and maintenance of SATCOM terminals. All SATaaMS for STS requirements will be outlined in section eight (8).

1.1 General

The goal of this effort is to establish a managed subscription service (marketplace) that encompasses SATCOM capabilities that are currently being used in private industry. PEO C3T would like for industry to bring their innovative ideas to the Army marketplace based on modern and efficient business models for acquiring needed SATCOM capabilities. The “marketplace” in essence entails a contractual vehicle for which individual or enterprise funding can be placed to order within the scope capabilities for a base period of twelve (12) months with four (4) option periods of twelve months each, giving a total potential period of five years.

1.2 Scope

The scope of this blanket purchase agreement (BPA) will provide global end to end managed subscription services, Post Deployment Software Support (PDSS) and logistics services to support connectivity to commercial teleports and internet services in accordance with section 6 and its technical specifications and leased terminal requirements to support services offered to the U.S. Army. Each task/call order offered during the life cycle and otherwise within the scope of this BPA shall be up to one year of service.

The Government may require surge support during the base or any option period, and surge modifications will be within the scope of the task order and provide increased support worldwide. Surge support over the life of the task order will not exceed 25 percent of the contractor’s total proposed price for the base and all option periods, excluding any 6-month extension of services pursuant to FAR 52.217-8.

1.3 Background

The U.S. Army Program Executive Office for Command, Control and Communications-Tactical (PEO C3T) directly supports American National Security interest worldwide. One facet of their mission is to maintain operational capacity at the small unit level in order to maintain readiness at all times, this includes fast data rates (transmit and receive), resilient and secure commercial satellite communications capacity to assist in meeting mission needs. PEO C3T requires a marketplace where they can acquire the necessary equipment and/or bandwidth promptly and seamlessly to support the United States (U.S.) Army Units.

SECTION II

2.0 TASK DESCRIPTIONS FOR SATaaMS

All performance requirements (tasks) written below are critical to the requested services. Offers are encouraged to demonstrate innovative solutions that provide additional value in program efficiencies.

2.1 Task 1 General Service and Capability Requirements

The offeror shall be capable of supplying a global satellite communications capability, providing seamless coverage across the globe. The Army seeks a Satellite Network (or network-of-networks) that can provide service to all combatant commands including those shown in the picture below.

This might involve the offeror to use satellites in multiple orbits for redundancy and to mitigate the risk of outages due to technical failures or intentional disruptions.

The system must have robust capabilities to safeguard sensitive Army communications from unauthorized access or interference. The system should be able to ensure command and control continuity to the Army's command structure.

The vendor must be able to meet the Army's current needs but be flexible if requirements change to can accommodate future growth and needs of the Army SATCOM system. The proposed solution should be adaptable to incorporate new technologies, satellites, and functionalities as requirements change over time.

2.2 Network Monitoring (NetOps)

The contractor shall be capable of collecting and delivering the near real-time monitoring, fault/incident/outage reporting, and availability consistent with commercial best practice. The contractor shall also immediately report faults, incidents, and outages to the RSSC-West at Peterson Air Force Base, Colorado and the COR. The contractor shall monitor Operational Availability of all satellites that are being used within this PWS. The contractor shall report on availability per day of each satellite to the COR monthly. The contractor’s NetOps monitoring capability should address the following metrics at a minimum:

· Satellite anomalies likely to disrupt service – satellite

· Interference data – satellite

· Spectrum data – satellite

· Network utilization monitoring of leased services

· Security anomaly status monitoring and reporting, for example identification if a terminal is being jammed, spoofed, or interfered with – satellite and network

2.3 Task 2 Technical Performance Requirements

A Technical Specification with terminal information is included in Appendix A – Technical Specification of this PWS.

2.4 Required Managed Data Rates and Subscription Service

2.4.1 Data Rates

The Government requires two managed subscription data rates plans to support terminals on Geostationary orbits and Medium and/or Low Earth orbits. The contractor shall provide a turn-key managed network service provided on the contractor’s commercial network to include all bandwidth, network infrastructure inclusive of hub, teleport, space, power, Radio Frequency (RF), Heating, Ventilation and Air Conditioning (HVAC), etc., along with internet connectivity and network management.

The solution should be end-to-end to include software, hardware, and service, in addition to any software licenses required. The service shall be capable of supporting terminals at the halt and terminals may be relocated through the lifecycle of this contract. Committed information rates (CIR) and maximum information rate (MIR) are specified below:

Data Rate Plan A (Mbps) [Geostationary and/or High orbits] CIR: 6 down x 2 up (Mbps) MIR: 10 x 4 (Mbps)

Data Rate Plan B (Mbps) [Medium and/or Low Earth orbits] CIR: 15 x 5 (Mbps) MIR: 30 x 10 (Mbps)

To address emerging requirements, the Government may define new service plans with CIRs ranging between 1 and 100 Mbps down and 1 and 50 Mbps up.

2.4.2 Subscription Plans

The contractor shall provide monthly data allowance subscription plans of 100 GB, 500 GB, 2,000 GB, and Unlimited GB. Subscription plans with GB limits shall have continuous overage ability up to 100 GB past cap with no change in service. The contractor will notify COR and end user when subscription plan reaches 75% usage. The government shall have the option to upgrade plans as needed with 5 business days’ notice to contractor. The Government shall have the option to upgrade service plans for the current month at no cost above that of the predefined monthly cost for the upgraded service plan.

Data usage shall strictly be calculated from traffic sourced to or from Army nodes. Traffic resulted from terminals and devices provided by the vendor, including but not limited to management, synchronization, status, and maintenance traffics shall not deduct from data usage allocation provided to the Army.

Deliverable :

*Standard Distribution: 1 copy of the transmittal letter without the deliverable to the Contracting Officer; 1 copy of the transmittal letter with the deliverable to the Primary COR.

2.4.3 Portability

For LEO and MEO services the contractor shall offer the opportunity to port bandwidth from one region to another in order meet mission requirements. Portability will also include the option to switch from one orbit or constellation to another, if necessary (the ability to transfer from LEO/MEO to GEO when LEO/MEO is unavailable or any other services that are unavailable). When portability is exercised, evidence of equivalent net present value shall be provided by the contractor. The contractor shall invoice ported bandwidth at the appropriate rate for the area and mission, in accordance with the contract line-item number (CLIN) list.

2.4.4 Required Space Segment Coverage

Coverage is only primarily required for land masses across the globe, unless otherwise specified by a requirement. The vendor shall provide coverage maps for each orbit (LEO, MEO, GEO, and HEO) leveraged in the vendor solution.

2.4.5 NetOps and User Near Real-Time Usage Reporting Portal

The contractor shall be capable of collecting and delivering the near real-time usage, monitoring, fault/incident/outage reporting, notification, notification tracking, and information access to ensure effective and efficient operations, performance, and availability consistent with commercial best practice. Near real-time usage refers to the timeliness of data or information that has been delayed only by the time required for electronic communication and automatic data processing. Near real time is defined as no greater than 5 minutes.

The contractor shall design the Portal with minimum protections following DFARS Clause 252.204-7012, NIST SP 800-171, and NIST SP 800-172 to ensure all information processed, stored, or transmitted is secure. The contractor shall prevent unauthorized access to the Web Tool by implementing CUI protections as described in DFARS Clause 252.204-7012, NIST SP 800-171, and NIST SP 800-172 for each authorized user. The contractor shall provision the COR and other users accounts as directed by the COR and/or the COR’s delegate(s).

The Contractor Portal and all corresponding monitoring and control tools shall reside on the contractor’s servers. The contractor shall implement, install, configure, operate, and maintain automated network tools that provide an online account and network management capability within their solution to report Blanket Purchasing Agreement (BPA) usage, both aggregated and for each user account and terminal. Usage information shall be updated near real time. The contractor’s tool solution shall allow users to track the network configuration; monitor status and performance; detect, diagnose and resolve network problems; identify capacity requirements, and query their usage data over a user-specified period. The contractor’s solution shall provide the Government the ability to manage users’ access to tool data through a user access hierarchy while using Government Furnished Equipment.

At a minimum, users shall have the ability to access the following information, presented simply and intuitively:

· Terminal type (with serial numbers)

· Plan type with CIR (with contract line item number (CLIN))

· Subscription period of performance (PoP)

· Data Limit for that terminal

· Current signal to noise ratio or Eb/No

· End-to-End packet loss statistics (less than 1% required), current month and cumulative

· End-to-end jitter (less than 300 milliseconds required)

· End-to-end latency (less than 1 second required)

· End-to-end availability, averaged over a 30-day period, calculated daily for the previous 30 calendar days.

· Availability=uptime/(uptime+downtime)

· CIR availability determined from average throughput per minute

· Data Usage – throughput available, data transmitted, data received

· Downtime due to no signal received, network issue, terminal failure, etc.

The contractor shall manage user access to the web tool for both contractor and Government personnel. The contractor shall administer and assign all usernames and passwords to the portal for both contractor and Government personnel as defined at the order level and approved by the COR.

2.4.6 Web Monitoring Portal

The contractor shall have continuous, uninterrupted, near real time transparency via a monitoring and situational awareness portal. The contractor shall report bandwidth utilization for all bandwidth ordered under the subject contract at a minimum of near real time. Availability reports shall be accompanied by associated coverage maps. The contractor shall manage all data within the tool and ensure that it is up-to-date in accordance with the proposed interval of reports. Reporting capabilities shall include:

· Search capabilities to track and account for utilization by assigned user

· Ability to export data to a Microsoft Excel file

· Ability to view the expected average bandwidth usage per terminal

· Ability to export forecast data to a CSV or Microsoft Excel file

· Accommodates a minimum of 25 simultaneously logged on users

· Contains a historical database of monitored data collected and stored over the past 30 days

· Allows the user to view all ongoing and scheduled maintenance events

· Allows for the posting and downloading of files for the purpose of disseminating information pertinent to the US Army users. Information includes but is not limited to all deliverable reports, operating procedures, usage reports, and satellite footprint files in a format that will allow for display with Google Earth Software, transmission plans and frequency matrices. Real-time monitoring for satellite anomalies, interference data, and spectrum data disrupting the service, including Electro Magnetic Interference (EMI) / Radio Frequency Interference (RFI) identification, characterization, and geo-location compliant with the EMI/RFI Reporting Checklist. Fault, incident, degradation, and outage reporting. Incident management and service resolution, and trouble tickets for out-of-tolerance and carrier-related alarms.

2.4.6.1 The Contractor shall provide a portal accessible to the Contracting Officer's Representative (COR) and US Army Planners and Technical Team via Hyper Text Transfer Protocol with Secure Sockets Layer (HTTPS). The Portal must be accessible through public internet network. The Contractor Portal and all corresponding monitoring and control tools shall reside on the contractor's servers. Web portal shall be provided no later than 90 days after contract award.

2.4.6.2 Web Portal access may be required through Secret Internet Protocol Router Network (SIPR). Contractor shall identify their commercial requirements to support a SIPR instance of their web portal and any limitations from such operation (i.e. no access to coverage maps, etc.)

2.4.6.2 The contractor shall manage user access to the Web Tool for both contractor and government personnel. The contractor shall administer and assign all usernames and passwords to the portal for both Contractor and Government personnel. The contractor shall provide multifactor authentication to access the Web Tool. The contractor shall manage user access to the Web Tool for the Government and shall provide access only to users approved by the designated Government POC; this may include Contractors working on behalf of the Government,

2.4.6.3 Web Tool Security. The contractor shall design the web-based monitoring tool to provide a minimum protection following DFARS Clause 252.204-7012 and NIST SP 800-171, to ensure all information transmitted is secure, and provide password protected access to the Web Tool. The contractor shall prevent unauthorized access to the Web Tool by implementing CUI protections as described in DFARS Clause 252.204-7012 and NIST SP 800-171 for each authorized user. The contractor shall provide a hierarchy of users, roles, and assigned domains. The contractor shall control access to the Web Tool by an administrator. Administrative features shall include the capability of recording any items created, edited, and deleted. These records shall be retained and accessible to the Government for the duration of the contract. The contractor shall provide different levels of access to the Web Tool to the users based on the level of appropriate authorization to data and resources, and also based on the credentials of the authenticated user as described by the Government.

2.4.6.4 Web Tool Training. The contractor shall develop a curriculum for Web Tool user training. The curriculum shall be delivered within 90 calendar days after initial task order start date. The contractor shall provide two virtual training session during initial standup. Training sessions shall be scheduled after the Web Tool and training curriculum have been delivered and accepted by the Government. Initial training shall be conducted within 90 days of contract award. The training schedule will be approved by the Government at least 30 calendar days in advance of each training session. The contractor shall be prepared to conduct virtual refresher training at the Government location through the life of the contract at the Government's request.

2.4.6.5 Web Tool Design Demonstration. The contractor shall demonstrate their proposed Web Tool solution at the Kick-Off Meeting. If the Government determines updates need to be made, the contractor shall provide an updated version of the tool as requested by the Government.

2.4.6.6 Web Tool Delivery. The Web Tool shall be accessible on-line and ready for use within 90 calendar days after BPA start date. The Web Tool will be formally accepted by the Government after meeting all of the requirements of Section 2.8

2.5 API Interface for status and performance information

The contractor shall provide all API Interface information for all status and performance data elements in order for the Government to ingest this data into the Government’s Network Monitoring Tool.

2.6 Leased Terminal Equipment

The contractor shall provide leased SATCOM terminals consisting of all radio frequency, modem configurations, intermediate frequency, and ancillary equipment necessary for turnkey operation of the terminal (such as cabling and connectors) see Table 3 - Terminal Equipment Requirements. All equipment shall be factory tested, and appropriately packed for shipment.

Shipping shall be billed under a separate CLIN as a pass-through charge. The contractor shall provide warranty maintenance and service plan for contractor-provided terminals, being operated both CONUS and OCONUS, in writing within 30 calendar days after receipt of order (ARO). This shall include contingency plans for broken equipment to meet the required availability. The proposed terminals shall be appropriate for the requested service plans. The contractor shall ensure that equipment is certified for use with the specified satellite constellation. Terminals shall be available for shipment 30 calendar days prior service start date.

Terminals shall meet the terminal requirements in Section 6.3. It is acceptable for an individual terminal to support more than one service plan.

2.6.1 Terminal kit must be form-factored for transit cases to facilitate transport via palletized, vehicular, or commercial airline checked baggage means.

2.6.2 Transit cases shall be configured to accommodate a two-person lift.

2.6.3 Terminal transit kit cases must not exceed 80 total linear inches (combined length, width, and height) each.

2.6.4 Physical hardware setup and teardown of the user terminal shall not exceed the need for more than 2 people and 30-minutes. Setup does not include connecting to the satellite.

2.6.5 The contractor shall provide satellite terminals capable of being operated by both skilled SATCOM operators and operators not experienced in SATCOM.

Deliverable:

Frequency is event-driven

Frequency is Event driven

*Standard Distribution: 1 copy of the transmittal letter without the deliverable to the Contracting Officer; 1 copy of the transmittal letter with the deliverable to the Primary COR and Mission Partner.

2.6.6 The contractor shall prepare and submit with each Terminal type a Terminal Safety Assessment Report (TSAR) in contractor format and in accordance with (IAW) MIL-STD-882E, which shall evaluate the safety risk being assumed prior to test or operation of the equipment delivered under this contract. The TSAR shall identify all safety features of the system hardware and software design, specific controls or precautions to be followed in the use of the system and shall provide verification of compliance to applicable nationally recognized product safety standards. The contractor shall address any industry safety certifications (e.g. Underwriters Laboratories Listing, Federal Communications Commission Licensing, etc) and shall identify testing completed to ensure the system remains safe during adverse weather conditions. The contractor shall attach a completed System Safety Design Verification Checklist (available through the CECOM Directorate for Safety), a hazard log, and Material Safety Data Sheets for all hazardous materials to the TSAR. The TSAR shall address all hazardous and environmentally-unacceptable materials used in the system, any possible alternative materials, and recommended actions to eliminate or reduce the use of hazardous materials IAW the Pollution Prevention Objectives. The TSAR shall address any exposure concerns to personnel during operational or maintenance procedures to include fabrication, transportation, setup and tear down, or resulting from damage to the equipment. Any special disposal procedures shall be addressed, and any disposal costs shall be the responsibility of the contractor. All equipment being offered by the performer will have a complete TSAR submitted with the contractor’s proposal. Additional capabilities and the associated TSARs will be accepted at the beginning of each option year.

2.6.7 Terminal Equipment shall support the use of VPN connections from terminal to commercial data center.

50-60 Hertz (Hz)

Table 3. Terminal Equipment Requirements.

*UPS are external from number of transit cases requirement. UPS output powering any outdoor equipment shall incorporate Ground Fault Circuit Interrupter (GFCI) protection.

Deliverable:

Frequency is event-driven

*Standard Distribution: 1 copy of the transmittal letter without the deliverable to the Contracting Officer; 1 copy of the transmittal letter with the deliverable to the Primary COR and Mission Partner.

2.7 Ease of Use

The SATaaMS terminal must have ease of use features allowing it to be installed and operated by a general-purpose users with no requirement for special tools. A general-purpose user shall be capable of monitoring system status: operational, over-loaded, or offline.

2.8 Global Positioning System (GPS) Support

The SATaaMS systems that integrate any GPS equipment shall be compliant with the lates approved DoD standards and policies governing GPS, including M-code and that GPS capability may be provided by either an internal or external device.

2.9 Provisioning Laptop

The contractor shall provide one laptop per terminal to assist users with initial configuration for the terminal web-based user interface for configuration. The laptop will be used for any software installation or updating to the Satellite terminal. The laptop will also be used for pointing the antenna to the proper satellite providing SaaMS service.

2.10 Training and Training Material

2.11.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:

2.13 Program of Instruction

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

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

2.16 Lesson Plan

2.17 Student Training Guide

2.18 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 per 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 the meetings. A 100% verification of the training documentation shall be conducted after the 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 the 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.

2.12.2 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.

2.12.3 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-2 and as detailed in Appendix F of this PWS.

2.12.4 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-2, 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.

2.12.5 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-1 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-1, as determined by the Government.

2.12.6 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 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.

2.12.7 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.

1.12.8 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)

2.12.9 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”

2.12.10 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. 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.

2.12.11 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.

2.12.12 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.

2.12.13 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.

2.12.14 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.

2.12.15 Format

The Contractor shall submit the TMs in hardcopy and submit the IETMs on as 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-1 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-1. 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).

2.12.16 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 int eh rejection letter and provided updated materials for another final review. The Government will notify the Contractor of acceptance by official correspondence (letter or email).

Training materials shall be provided at least 10 calendar days prior to training events. Training will be conducted at Government site(s), to be specified by the Government in order(s) for training. Training may be required OCONUS, but will not be requested for austere or hostile locations. Class sizes shall be no more than ten students. The contractor shall propose the number of instructors per class.

Travel for training shall be invoiced via a separate CLIN. When training is included on a potential order, the contractor shall submit an estimate for the cost of the travel and shall not coordinate or depart on travel without Government approval and acceptance of the travel request. The Government will reject payment for travel that is invoiced without prior authorization. The contractor shall provide a trip report with supporting documentation to the COR within five (5) business days of completion of travel detailing the work completed. For training requiring contractor travel to a remote location inaccessible through commercial air transportation, the contractor shall work with the COR (or other DoD office, if stipulated in the order) to arrange provision of DoD travel to the remote site. The contractor will not be penalized for performance or service delays resulting from delays in DoD transportation availability.

Deliverables:

Govt requires 14 days to review and provide any comments prior to final submission

*Standard Distribution: 1 copy of the transmittal letter without the deliverable to the Contracting Officer; 1 copy of the transmittal letter with the deliverable to the Primary COR and Mission Partner.

2.13 Reliability/Availability

The contractor shall meet an operational availability for transponded bandwidth of 99.999 percent as specified over each 30-day period, calculated daily for the previous 30 calendar days. The contractor shall meet a link availability of 99.5 percent for time division multiple access (TDMA) satellite links throughout the life of the task order.

The contractor shall provide leased terrestrial backhaul to the point of presence identified in section 2.3. The commercial teleport shall meet an operational availability of 99.95 percent over each 30-calendar day period. The terrestrial connectivity from the commercial teleport to each Government point of presence shall maintain a 99.95 percent operational availability over each 30-calendar day period. The contractor shall deliver terrestrial segment capabilities that are compatible with and of sufficient quantity, to interface with the applicable space segment and commercial teleports. The contractor shall provide all equipment and services from the closest contractor demarcation point for up and down linking end user terminals. If required by an engineering change proposal, the contractor shall provide the user connection from the teleport to the public Internet via a US-based commercial Internet service provider (ISP).

The contractor shall meet a service availability of 99.5 percent. Solutions shall offer links capable of supporting the user requirement with link margins that are adequate to overcome degradation that may be caused by equipment or the local environment. The entire coverage area must be met throughout the contract. Space segment must be offered on a satellite(s) that is currently on-orbit and operational. To assist in mission planning, the contractor shall provide an availability map outlining the coverage area that meets the service availability. The availability map shall outline where coverage is provided for each user terminal for their supported service plans. Contractors may submit a single availability map reflecting both throughput levels and terminal types, or separate availability maps with each map reflecting unique throughput and terminal types.

The material availability impacts the Army readiness needs. The total Army SATaaMS assets population will be no less than 85% threshold and 95% optimal operational. Systems must be mission ready with working assets with services available.

Deliverables:

Frequency is event-driven

*Standard Distribution: 1 copy of the transmittal letter without the deliverable to the Contracting Officer; 1 copy of the transmittal letter with the deliverable to the Primary COR and Mission Partner.

2.14 Frequency Clearances (FC) and Approvals Comment by Fuentes, Carlos D CTR DISA OPS (USA): HNA

The contractor shall support Host Nation Agreement (HNA) efforts in obtaining international approvals for radio spectrum operations under this task order in foreign nations. The contractor shall ensure that international services provided under this task order may be provided as scheduled with the full approval of each affected host nation. Typical services may include, but are not limited to: host nation approvals, landing rights, operating agreements, site licenses, and FCs. Contractor shall provide a consolidated table with their estimated schedule to obtain HNA or FC for all threshold and objective country requiring FC. If host nation support becomes necessary during the life of the task order, contract line item numbers will be added to the order at the time they are required, and shall be invoiced at pass-through rates. The contractor may be required to provide HNAs for any nation covered within the limits defined in the coverage area, as needed by the user. A temporary FC shall be requested in order to meet the service start date requirement while the permanent license is processed. FCs shall be requested for the maximum time period allowed by the host nation, up to the life of the contract. The contractor shall provide the Government with copies of regulatory licenses and approvals obtained to operate and use the spectrum for countries within the required service region.

2.15 Electro Magnetic Interference (EMI)/Radio Frequency Interference (RFI) Identification, Characterization, and Geo-location

The contractor shall provide legible EMI/RFI identification, characterization, and geo-location in accordance with the EMI/RFI Reporting Checklist. Such services include the ability to identify and characterize sub-carrier EMI/RFI being transmitted underneath an authorized carrier, and the ability to geo-locate the source of any and all EMI/RFI. The contractor shall also immediately report the existence of EMI/RFI to the RSSC-West and the COR. Additionally, the contractor shall make best efforts to geo-locate the source of the interference and report findings in accordance with guidance (as documented in the EMI/RFI Reporting Checklist). The contractor shall support Government exercises focused on the resolution of EMI/RFI interference scenarios as directed, no more frequently than quarterly.