Attachment 0001 - Performance Work Statement (PWS).pdf

PRODUCT MANAGER (PDM)

WIDEBAND ENTERPRISE SATELLITE SYSTEMS (WESS)

PROJECT OFFICE SATELLITE BASEBAND SYSTEMS

ENTERPRISE DIGITAL INTERMEDIATE FREQUENCY MULTI-

CARRIER (EDIM) MODEM

PERFORMANCE WORK STATEMENT

11 NOVEMBER 2022

PROCUREMENT SENSITIVE

i

Table of Contents

1. General

1.1. Description of Services/Introduction

1.2. Applicable Documents

1.3. Background and Objective

1.4. Scope

2. Configuration Management

2.1. Configuration Baseline

2.2. Engineering Change Proposal (ECP)

2.3. Product Change Notices (PCNs)

2.4. Warranty

3. Engineering

3.1. Technical Data Package (TDP)

3.2. Interface Control Document (ICD)

3.3. Product Specification

3.3.1. Product Specification System and Hardware Topics

3.4. BLANK

3.5. Software

3.5.1. Software Design

3.5.2. Software Development

3.5.3. Software Testing

3.5.3.7.1. Contractor Participation and Responsibilities

3.5.3.7.2. Software Configuration Audit Documentation

3.5.3.7.3. Software FCA

3.5.3.7.4. Software PCA

4. Test and Evaluation

4.1. First Article Test (FAT)

4.1.1. FAT Plan

4.1.2. FAT Procedures

4.1.3. FAT Report

ii

4.1.4. Notification to Start FAT

4.1.5. Dry-Run FAT Testing

4.1.6. Test Readiness Review (TRR)

4.1.7. FAT Acceptance

4.1.8. Certifications

4.2. Production Qualification Test (PQT)

4.2.1. Production Qualification Test (PQT) Plan

4.2.2. PQT Procedures

4.2.3. PQT Report

4.2.4. PQT Failure Reporting

5. Integrated Logistic Support

5.1. Maintenance Repair and Replacement Service

5.1.1. Maintenance Repair and Replacement Scope

5.1.2. Maintenance Repair

5.2. Packaging and Handling

5.3. Logistics Data Products

5.3.1. COMPASS Requirements

5.3.2. Level of Repair Analysis (LORA)

5.3.3. Maintenance Allocation Chart (MAC)

5.3.4. Engineering Data for Provisioning (EDFP)

5.3.5. Provisioning Parts List (PPL)

5.3.6. Repair Parts and Special Tools List (RPSTL)

5.4. Electronic Technical Manual (ETM)

5.4.1. Illustration

5.4.2. Preparation and Delivery of Technical Documentation Data

5.4.3. Contractor Personnel Participation

5.4.4. ETM Submission and Technical Manual In-Process Review (TM IPRs)

5.4.5. ETM Validation Plan

5.4.6. ETM Verification

5.4.7. Final Reproducible Copy (FRC) Submission Review and Acceptance

5.4.8. Changes to ETM/Publications

iii

5.5. Safety Engineering

5.5.1. Safety Markings and Labels

5.5.2. Safety Assessment Report (SAR)

5.5.3. Safety Inspection/Verification

5.6. Instructor Key Personnel (IKP) Training

5.6.1. New Equipment Training and Training Program Structure Documents

5.7. Item Unique Identifier (IUID)

5.7.1. IUID Marking

5.7.2. IUID Listing

5.7.3. IUID Registry and Submission

5.7.4. Wide Area Workflow (WAWF) Users and IUID Registry

5.8. Maintenance Engineering Evaluation (MEE)

5.8.1. Support and Responsivities

5.8.2. ETM Update and Tracking

5.8.3. Follow-On Evaluation

5.9. Logistics Demonstration (LOG DEMO)

6. Meetings and Reviews

6.1. Post Award Conference

6.2. Quarterly Program Reviews (QPR)

6.3. Preliminary Design Review (PDR)

6.4. Critical Design Review (CDR)

6.5. Weekly Status Teleconference

6.6. Technical Interchange Meeting (TIM)

7. Cybersecurity

7.1. Cybersecurity Engineering

7.2. Software Code Review

7.3. Assessment Testing

7.4. Cybersecurity Working Group

7.5. Cybersecurity Contractor Training and Certification

8. Technical Study

9. Post Production Software Support iv

10. Quality Assurance (QA)

10.1. Quality Assurance Requirements

10.2. Quality Control

11. Management

11.1. Data Management

11.1.1. Data Repository

11.1.2. Data Delivery Media

11.1.3. Digital File Format

11.2. Program Management Documents

11.2.1. Monthly Status Report (MSR)

11.2.2. Integrated Master Schedule (IMS)

12. Personnel Security and Training Requirements

13. Enterprise Contractor Manpower Reporting Application (eCMRA)

14. Exhibit A CDRL List

1. General

The mission of Program Executive Office Enterprise Information Systems (PEO EIS), Project Manager Integrated Enterprise Network (PM IEN), Product Manager Wideband Enterprise Satellite Systems (PdM WESS) is to acquire, deliver, and sustain superior enterprise (strategic) wideband military satellite communications and payload control capabilities for the Department of Defense (DoD) and the Joint Warfighting Community. The Enterprise Digital Intermediate Frequency Multi-Carrier (EDIM) Modem contract will provide design, development, testing, documentation, fabrication, and delivery of production units, hardware and software sustainment, including Information Assurance (IA) and performance capability enhancements for the EDIM Modem, as a replacement to the aging Enhanced Bandwidth Efficient Modem (EBEM) currently supporting Tri-services Satellite Communication (SATCOM) users. The EDIM Modem supports the gradual migration of SATCOM terminals and baseband equipment to a digital Intermediate Frequency (IF) architecture. The EDIM Modem will be employed as the DoD’s SATCOM modem by the Army and other Services and Agencies.

1.1. Description of Services/Introduction

The Contractor shall provide all personnel, equipment, supplies, facilities, transportation, tools, materials, supervision, other items, and non-personal services necessary to deliver a EDIM Modem that meets all the performance requirements addressed in the EDIM Modem System Specification and all the other standards specified in this Performance Work Statement (PWS).

1.2. Applicable Documents

a. EDIM Modem System Specification Revision 1.0, dated 08 September 2022

b. National Institute of Standards and Technology (NIST) certification per Federal

Information Processing Standards (FIPS) 140-3

c. System Safety Design Verification Checklist (SEL Form 1183)

d. Material Safety Data Sheets (OSHA Form 20 or DD Form 1813)

e. Code of Federal Regulations (CFR) Title 49 part 171.8

f. ANSI Z535.4

g. Army Regulation (AR) 525-13

h. AR 530-1

i. AR 700–139

j. AR 710–3

k. ASTM D3951-98 (2004)

l. Department of Defense Instruction (DoDI) 8510.01

m. DoD Manual 8570.01-M

n. Institute of Electrical Engineers (IEEE) STD 1016-2009 – Systems Design –

Software Design Descriptions

o. IEEE 15288.2

p. International Organization for Standardization (ISO) 9001:2015

q. ISO/International Electrotechnical Commission (IEC)/IEEE 2991 – Software and

Systems Engineering – Software Testing

r. ISO/IEC/IEEE 12207-2017:2017 Systems and Software Engineering – Software Life

Cycle Processes

s. Military Handbook (MIL-HDBK)-1222-F

t. Military Standard (MIL-STD)-130

u. MIL-STD-882E

v. MIL-STD-40051-2D Change 1

w. MIL-STD-31000B

x. NIST Special Publication (SP) 800-37

y. UL 969

z. UL 1950

aa. UL 60950-1

bb. TB 43-0134

1.3. Background and Objective

The Government has deployed over 2,500 EBEM modems since 2007, and its processor and memory capacities cannot be upgraded without substantial hardware modifications. Some of the EBEM’s critical components are also becoming obsolete, and the vendor can no longer fabricate and manufacture EBEM’s due to critical parts obsolescence. Similar modems are available in the commercial market, but lack the ability to expand or meet emergent technical adaptations.

There are significant advantages to incorporating a digital IF architecture in a simplified modem design, to include reducing noise associated with analog/digital conversion, increasing data processing speed, lowering costs, and enabling multiple carrier capacity.

PdM WESS will develop the EDIM Modem program to replace the aging EBEM, incorporate matured digital IF technology, and implement multiple carrier capacity.

1.4. Scope

This PWS establishes requirements for the Contractor to provide technical solutions to meet all the EDIM Modem System Specification requirements for software/hardware design and development engineering support, configuration management, equipment production and testing, logistics support, associated Contract Data Requirement List (CDRL) deliverables, enhancement design for growth, trouble analysis/help desk support, repair and maintenance, IA support, technical and program review meetings, and program management support for the EDIM Modem.

Formal Qualification Phase - the Contractor shall develop and fabricate the number of First Article Test (FAT) units described in contract Section B and perform FAT to verify the design solution complies with all EDIM Modem System Specification requirements.

Production Phase – the Contractor shall fabricate and deliver production EDIM Modem quantities, as ordered in the individual delivery orders.

Sustainment and Growth Support Phase – the Contractor shall provide required services in order to maintain deployed EDIM Modem in an acceptable state of readiness. The Contractor shall provide warranty support, technical support, depot support, IA support, Post-Production Software Support (PPSS), and capability growth/enhancement support, as required.

2. Configuration Management

2.1. Configuration Baseline

The EDIM Modem configuration baseline shall be changed each time a new function/capability is added as a result of a contract modification implementing an Engineering Change Proposal

(ECP).

a. The initial functional configuration baseline for equipment supplied under this contract is the EDIM Modem System Specification (Attachment 1). The Contractor shall be responsible for the development of all EDIM Modem hardware, software configuration items and associated documentation, and for compliance with the EDIM Modem System Specification requirements. The functional configuration can be updated as the result of an ECP.

b. The product configuration baseline for equipment supplied under this contract shall be defined as the most recent version of hardware, software, and associated documentation for which the FAT report was approved and accepted by the Government.

The Contractor shall establish and maintain a documented Configuration Management procedure to ensure that all of the Contractor’s activities have access to and exercise the use of the configuration baseline, approved changes, and effectivity data. The documented procedure and data in use shall be made available, upon request, for Government review, and shall be discussed during Technical Reviews. Any changes to the established/approved design shall be presented and submitted to the Government for review and approval.

2.2. Engineering Change Proposal (ECP)

An ECP is a formally recommended change to the EDIM Modem configuration that would affect form, fit, function, performance, reliability, maintainability, survivability, interoperability, interchangeability, interface characteristics, electromagnetic characteristics, supportability, or other critical or major characteristics identified in the EDIM Modem System Specification.

All EDIM Modem enhancements shall be executed and implemented as an ECP. The Government will provide an updated EDIM Modem PWS with the EDIM Modem System

Specification describing the enhancement requirements via formal modifications during the life of the EDIM Modem contract.

2.3. Product Change Notices (PCNs)

The Contractor shall submit PCNs documenting changes to the EDIM Modem equipment baseline in accordance with (IAW) CDRL A001. The PCN shall address those hardware and software changes that impact the EDIM Modem functional or product baseline, as well as the EDIM Modem system requirements. The PCN shall include the reasons for the change, to include whether it is a solution to a problem, a new feature, or change to the current configuration baseline.

2.4. Warranty

The DD 250 will be signed by the Government upon successful completion of the Production Qualification Test (PQT). The Contractor shall deliver the hardware by Free on Board (FOB) destination. The Contractor shall provide the Government with a 12-month warranty for all equipment supplied under this contract, beginning on the date of equipment receipt and acceptance at the destination. If any subcontractor or component vendor provides a commercially available warranty, or a warranty in excess of the Contractor warranty as part of the component purchase, the Contractor shall pass on that particular warranty coverage to the Government. The Contractor shall identify the equipment, vendor, and terms of all warranties provided with the equipment delivery. The Contractor shall keep a record of all items under all warranties, and shall make such records available to the Government, upon request. The Contractor shall index and identify all items under warranty with an Item Unique Identification (IUID) label, as described in PWS, paragraph 5.7, “Item Unique Identifier (IUID)”). The Contractor shall include the status of all EDIM Modem hardware warranties in the Monthly Status Report after the initial warranty period starts until it expires.

The warranty shall include the costs of shipping equipment covered by the warranty to the Contractor for repair and returning it to the Government. The Contractor shall provide a point of contact for the status of equipment failures, repairs, spares orders, site maintenance services, and technical services with respect to all equipment.

2.5 Optional Extended Warranty

The Contractor shall provide the Government with an optional extended warranty for each item of the equipment supplied under this contract. If exercised, the optional extended warranty shall:

(1) be 12-months; (2) begin on the day after the warranty described in paragraph 2.4 expires or, if procured after the initial warranty expires, on the day the contract is modified to exercise the optional warranty; and (3) be provided under the same terms and conditions as the warranty described in paragraph 2.4.

3. Engineering

3.1. Technical Data Package (TDP)

The Contractor shall produce and maintain a Product TDP, as defined in CDRL A002, which contains the pertinent specifications, standards, Quality Assurance provisions, packaging data, and/or various types of samples, models, and/or associated lists that will enable the Government to operate, manage, maintain, and support the EDIM Modem throughout its lifecycle.

The TDP shall depict the physical and functional characteristics of the Government-approved baseline of the EDIM Modem configuration and its subordinate assemblies, subassemblies, and parts. The TDP elements shall include product drawings, associated lists, and specifications. The TDP shall depict the physical and virtual characteristics of the Contractor solution for all future specification capabilities identified by the Contractor solution.

The Contractor shall provide the Government with access to the TDP through the data repository, upon request. After receiving a request from the Government, the Contractor shall post the requested TDP documentation to the data repository within two business days. The Contractor shall advise the Government of the list of components of the TDP that have been posted and the detailed path or directory on the data repository where the information can be obtained.

The EDIM Modem technical documentation may require updates due to implementation of an ECP. The existing EDIM Modem technical documentation shall be used as the baseline for updating such documentation on this contract.

3.2. Interface Control Document (ICD)

The Contractor shall develop and deliver the EDIM Modem ICD IAW CDRL A003. Electrical interfaces shall be specified in quantitative terms, such as input and output voltages, levels, timing, waveforms, and impedances. All interface connector type and pin assignments shall be specified. References to industry interface standards and specifications shall be included. The document shall address all EDIM Modem interface characteristics necessary to successfully connect to the baseband and terminal equipment described in the EDIM Modem System Specification and its subsections. The ICD shall also address the remote Monitor and Control (M&C) computer hardware/software requirements and M&C message protocols.

IAW EDIM System Specification, paragraph 3.2.5.2.2, “Support for Higher Rates,” if the Contractor implements DVB-S2X Hub waveform, the ICD shall include an attachment to address the DVB-S2X hub waveform constructs and processes necessary to establish interoperability with the EDIM Modem in this DVB-S2X emulation, exceeding content already published in ETSI EN 302 307-1 and -2. Such constructs and processes may include, but are not necessarily limited to:

a. Data traffic encapsulation details for each data traffic encapsulation method offered IAW EDIM Modem System Specification, paragraph 3.2.5.2.2.2.2, “Data Traffic Encapsulation,”

b. Bulk encryption for cover IAW EDIM Modem System Specification 3.2.5.2.2.2.3, “Bulk Encryption for Cover,”

c. Signaling methods in support of ETSI EN 302 307-2 section D.5, “Signaling of reception quality via return channel (Normative for Adaptive Coding and Modulation (ACM)),” for selectable ACM, Dynamic Resource Allocation (DRA), or any other applicable feature IAW EDIM Modem System Specification 3.2.5.2.2.2.4, “DVB-S2X Feature Support.”

3.3. Product Specification

The Contractor shall generate, submit, and maintain, as part of the configuration baseline, a Product Specification IAW this paragraph and CDRL A004. The Product Specification shall detail the design and performance of EDIM Modem hardware used in meeting the requirements of the EDIM Modem System Specification.

3.3.1. Product Specification System and Hardware Topics

The Product Specification shall include the following system and hardware topics:

a. Complete listing of all major components that comprise the EDIM Modem, including Line Replaceable Units (LRU) and Shop Replaceable Unit (SRU)

b. Drawing family tree identifying part numbers and relationships of EDIM Modem components and assemblies

c. A comprehensive description of overall EDIM Modem functionality

d. A comprehensive description of the functional characteristics of each major EDIM Modem component

e. Functional schematic and flow diagrams establishing the general relationship between EDIM Modem components

f. Definition of internal and external functional and physical interfaces, with references to the EDIM Modem ICD

g. Detailed Bit Error Rate (BER) and acquisition performance specifications for selectable modulation and coding formats

h. Reliability specifications allocated to EDIM Modem components

i. Thermal control features

j. Electromagnetic Interface mitigation features

k. Timing functions and relationships

l. Diagnostic features, including all fault and alarm databases

m. Control features, parameters, and protocols

n. Front panel indicators

o. Control Ethernet parameters

p. Remote monitor and control specification

q. Physical characteristics

r. AC power and AC-DC power supply requirements

3.4. RESERVED

3.5. Software

3.5.1. Software Design

The Contractor shall generate an EDIM Modem Software Design Document (SDD) following the guidelines set forth in ISO/IEC/IEEE 12207-2017:2017 Systems and Software Engineering – Software Life Cycle Processes and IEEE STD 1016-2009 – Systems Design – Software Design Descriptions. The SDD shall provide the design for each software item. The design pertaining to the software item’s interface design and database design descriptions shall be included in the SDD. The SDD shall be submitted IAW CDRL S005.

3.5.2. Software Development

3.5.2.1. Software Development Plan

The Contractor shall generate an EDIM Modem Software Development Plan (SDP) following the guidelines set forth in ISO/IEC/IEEE 12207-2017:2017 Systems and Software Engineering – Software Life Cycle Processes and ISO/IEC/IEEE 24748-5-2017 – Systems and Software Engineering – Life Cycle Management—Part 5: Software Development Planning. The SDP shall provide the processes to be followed for software development, the methods to be used, the approach to be followed for each activity, and the project schedules, organization, and resources.

The SDP shall be submitted IAW CDRL S001.

3.5.2.2. Software Data Rights

The Government will have unlimited rights to all software, documents, and material, except the Commercial-Off-The-Shelf (COTS)/modified COTS elements, produced under this contract.

Any customization done to a COTS solution shall become the sole property of the Government and shall remain non-proprietary and open ended to the maximum extent practical. Deviation from such policy shall be submitted to the Contracting Officer for approval prior to any work being performed.

The Contractor shall submit the EDIM Modem Software Government Data Rights (SGDR) document IAW CDRL S002. The SGDR shall list all software necessary to execute the requirements of this PWS, and to produce and operate the EDIM Modem.

For each listed item, the SGDR shall identify the associated data rights being provided to the Government. For any item identified and asserted as having restricted or limited rights, the

SGDR shall provide a justification for the assertion and an Analysis of Alternatives (AoA) documenting alternatives considered, the criteria for the selection of the software item, and the strategy and estimated cost for the life cycle support of that item. All assertions will be verified by the Contracting Officer.

3.5.2.3. Computer Software Purchase

The Contractor shall attempt to obtain all COTS software and software licenses via US Army Computer Hardware and Enterprise Software Solutions (CHESS) program. The Contractor shall coordinate with the Government on these purchases. The Contractor shall acquire an Information Technology Approval System (ITAS) account to facilitate the COTS software and software licenses procurement process.

The Contractor shall generate a Software License Requirements List IAW CDRL S003.

3.5.2.4. Software Requirements

The Contractor shall generate an EDIM Modem Software Requirements Specification (SRS) following the guidelines set forth in ISO/IEC/IEEE 12207-2017:2017 Systems and Software Engineering – Software Life Cycle Processes and ISO/IEC/IEEE 29148-2018 – Systems and Software Engineering – Software Life Cycle Processes – Requirements Engineering. The SRS shall provide the requirements for each software item and the methods to be used to ensure that each requirement has been met. The requirements pertaining to the software item’s external interfaces shall be included in the SRS. The SRS shall be submitted IAW CDRL S004.

3.5.3. Software Testing

The Contractor shall conduct a software test program following the guidelines set forth in ISO/IEC/IEEE 2991 – Software and Systems Engineering – Software Testing.

3.5.3.1. Software Qualification Test (SQT)

As part of the software test program, the Contractor shall conduct a Government witnessed Software Qualification Test (SQT). The SQT shall be conducted IAW the Government-approved SQT Software Test Plan and SQT Software Test Description to verify that the integrated EDIM Modem software meets its intended functionality and the requirements set forth in the EDIM Modem SRS.

As part of the SQT, the Contractor shall execute the Software Build Instructions documented in the EDIM Modem Software Product Specification (SPS) and the Software Installation Instructions documented in the EDIM Modem Software Version Description (SVD).

To the extent practical, the Contractor will automate the configuration of the test environment, the execution of the SQT test steps, and the verification of the SQT test results to be consistent with the goals of gaining efficiencies and cost savings over the life cycle of the EDIM Modem.

3.5.3.2. Software Test Plan (STP)

The Contractor shall generate and submit a Software Test Plan (STP) IAW CDRL S006. The STP shall describe plans for performing the qualification testing of the EDIM Modem software.

The STP shall also describe any plans to utilize automation during the SQT and the processes and methods for the Government to verify the adequacy of the test automation prior to use.

3.5.3.3. SQT Software Test Description (STD)

The Contractor shall generate and submit a Software Test Description (STD) IAW CDRL S007.

The STD shall describe the test preparations, test cases, and test procedures to be used to perform the EDIM Modem SQT. The Contractor shall provide methods for the Government to verify the quality and accuracy of automation utilized during the SQT in the STP.

3.5.3.4. Software Test Report (STR)

The Contractor shall generate and submit a Software Test Report (STR) IAW CDRL S008. The STR shall document the results of the SQT.

3.5.3.5. Software Version Description (SVD)

The Contractor shall generate and submit an EDIM Modem Software Version Description (SVD) IAW CDRL S009 to identify and describe the version under test and ultimately being provided in response to this PWS.

3.5.3.5.1. Bare Metal Installation Procedures

In addition to the software installation procedures that will be utilized to field the EDIM Modem, the Contractor shall generate and provide bare metal installation procedures as part of the SVD.

The bare metal installation procedures shall document how to install and configure each software component separately onto the hardware devices that are part of the EDIM Modem system.

The operation system installation part should not be integrated with other software components, such as .Net Framework or McAfee (anti-virus software component). Each software component should have a separate installation procedure. There should be a separate installation procedure for the operating system and its lockdowns, as well as for each software component (e.g., Net Framework, McAfee, MS SQL Server, etc.).

For a bare metal installation, no software components shall have to be removed. The new software component shall be added to the installation procedure. The software component no longer being used shall not be added. There shall be no need to perform any type of removal procedure. The installation procedure shall address the hardware/software drivers required for the EDIM Modem specific hardware components. Any tailoring to the software or hardware components shall be included in the installation procedures. All software included in the bare metal procedure installation will be delivered on electronic media.

3.5.3.6. Software Product Specification (SPS)

The Contractor shall generate an EDIM Modem Software Product Specification (SPS) following the guidelines set forth in ISO/IEC/IEEE 12207-2017:2017 Systems and Software Engineering –

Software Life Cycle Processes and IEEE STD 1016-2009 – Systems Design – Software Design Descriptions. The SPS shall provide the executable software, source files, and software support information, including the “as built” design information and compilation, build, and modification procedures, for each software item. The SPS shall be submitted IAW CDRL S010.

3.5.3.7. Software Configuration Audits

Configuration audits shall be used to verify that each released EDIM Modem software baseline version is accurate, complete and will meet specified program needs. Both Functional Configuration Audits (FCA) and the Physical Configuration Audits (PCA) must be satisfactorily completed by the Government and the Contractor as a prerequisite to establishing the product baseline. The Contractor shall conduct the Software FCA during the FAT before the start of Wideband Global Satellite (WGS) certification test. The Contractor shall conduct the Software PCA after the FAT report is approved by the Government.

3.5.3.7.1. Contractor Participation and Responsibilities

The Contractor shall be responsible for supporting Government conducted configuration audits IAW the following requirements.

a. The Contractor shall be responsible for ensuring that subcontractors, vendors, and suppliers participate in Government configuration audits, as appropriate.

b. The configuration audits shall be conducted at the Contractor's facility, or at a designated subcontractor facility, if approved by the Government. Accordingly, the Contractor shall be required to provide the necessary resources and materials to perform the audit effectively.

3.5.3.7.2. Software Configuration Audit Documentation

The Contractor shall submit a Configuration Audit Plan IAW CDRL S011. For each EDIM Modem software release, the Contractor shall submit a Configuration Audit Report IAW CDRL S012 at the conclusion of the Software FCA, and again at the conclusion of the Software PCA.

3.5.3.7.3. Software FCA

The Software FCA is an examination of Contractor software test results against the EDIM Modem Software Requirements Specification. The software FCA is a requirement for both new EDIM Modems and EDIM Modem enhancements, and it is conducted by Government personnel at the Contractor’s facility prior to the hardware/software integration phase, with the understanding that there may be some test results that are not available until after the software/hardware integration phase. A software FCA requires engineering personnel skilled in the particular language(s) being used on the project, as well as familiarity with the governing specifications and standards imposed by the contract.

3.5.3.7.4. Software PCA

The Software PCA is an examination of the as-coded total EDIM Modem system software against its design or deliverable documentation. For EDIM-unique software, this involves a comparison of source code documents with actual coding on applicable media. For COTS software, this involves verification of correct documentation to support use of the software versions being delivered on the applicable media. Adequacy of identification and marking of all deliverable software media shall be IAW best commercial practices and shall be included in the PCA. The PCA shall be conducted by Government personnel and supported by the Contractor.

The Contractor personnel supporting a software PCA shall be engineers skilled in applicable software languages and conventions for documenting and utilizing software products and shall be familiar with applicable specifications and standards. The PCA shall also verify that the software being delivered is the same software that was used to build the media for the conduct of the SQT and the verification of the bare metal installation procedures.

4. Test and Evaluation

Acceptance Inspection Equipment (AIE) Information:

(a)Acquisition, maintenance, and disposition of inspection equipment shall be in accordance with NCSL Z540.3 or ISO 10012:2003.

(b)The Contractor shall provide all Acceptance Inspection Equipment (AIE) necessary to assure conformance of components and end items to contract requirements. The Contractor shall identify all required AIE 30 days prior to the start of First Article testing.

(c) All AIE shall be available for use prior to First Article submission, or prior to initiation of production under this contract.

(d) AIE designs utilized for inspection of characteristics that are classified as Minor require approval by the Government Quality Assurance Representative (QAR). AIE design documentation for inspection of characteristics listed as Critical, Special, or Major shall be submitted to the Government for review.

(e) Resubmission of AIE design documentation for approval on a follow-on contract is not required provided inspection characteristic parameters specified in the current technical data package and the previously approved AIE design documentation remain unchanged. The contractor shall provide the contract number and identify previously approved AIE documentation that meets the above prerequisites.

(f) The Government reserves the right to disapprove at any time during performance of this contract, use of any AIE not meeting the requirements of the approved design documentation.

The Contractor shall test and validate that the EDIM Modem design meets all requirements specified in the EDIM Modem System Specification.

a. The Contractor shall test the EDIM Modem FAT units identified in contract Section B using Government-approved FAT plans and procedures. The Contractor shall conduct preliminary or dry-run tests using Government-approved FAT procedures to ensure that the subsequent official FAT will proceed efficiently and IAW the published schedule.

The Contractor shall conduct a Test Readiness Review (TRR) with Government participation to ensure that all preparations for FAT are complete. FAT shall not commence until the Government agrees with the TRR content and provides written concurrence.

b. The Contractor shall prepare the FAT Report documenting all FAT tests. Government acceptance of FAT units shall be contingent upon Government acceptance of the FAT Report.

c. The Contractor shall conduct SQT, as described in PWS, paragraph 3.5.3.1, “Software Qualification Test,” in conjunction with FAT. The Contractor shall successfully pass both FAT and SQT prior to beginning EDIM Modem production.

d. The Contractor shall test the production EDIM Modem units and EDIM Modem Line Replaceable Units (LRUs) identified in Government-approved PQT Plans and Procedures. The PQT Plans and Procedures should be comprised primarily of a subset of previously approved FAT Plans and Procedures. The PQT report shall aggregate the results of all PQT tests of EDIM Modem units and EDIM Modem LRUs conducted during a given month and shall be submitted monthly IAW Paragraph 4.2.3.

4.1. First Article Test (FAT)

The Contractor shall perform FAT in order to verify that the EDIM Modem and its components satisfy all the requirements of EDIM Modem System Specification. The complement of FAT equipment shall be employed to verify the EDIM Modem performance requirements identified in the EDIM Modem System Specification Verification Cross Reference Matrix (VCRM), Appendix C.

a. The Contractor shall perform FAT IAW Federal Acquisition Regulations (FAR) 52.209-3, First Article Approval – Contractor Testing, and the PWS.

b. The Contractor shall provide the requisite number of FAT units, all ancillary equipment, and the test equipment necessary to run FAT.

c. The Contractor shall develop the FAT Plan, as specified in PWS Paragraph 4.1.1, and FAT Procedures, as specified in PWS Paragraph 4.1.2, to demonstrate that these units conform to the requirements established by the applicable specification(s) and other technical data provided in this contract.

d. The Contractor shall provide a FAT Report that documents FAT results, as specified in Paragraph 4.1.3.

4.1.1. FAT Plan

The Contractor shall develop and submit a complete FAT Plan IAW CDRL A006. The FAT Plan shall address the Contractor’s specific approach to verifying that the EDIM Modem equipment meets the EDIM Modem System Specification requirements. The Contractor shall also include the Expanded Verification Cross Reference Matrix (See EDIM Modem System Specification, Paragraph 4.2, “Expanded Verification Cross Reference Matrix (EVCRM)”) in the FAT Plan.

The Contractor shall submit the FAT Plan 120 business days before the start of FAT.

4.1.2. FAT Procedures

The Contractor shall develop and submit complete FAT Procedures to address all FAT testing to be conducted on this contract. FAT Procedures shall be submitted 80 business days before the start of FAT IAW CDRL A007. The FAT Procedures shall expand upon the submitted and approved FAT Plan by addressing, in detail, all tests necessary to adequately evaluate the performance of the FAT units.

The FAT Procedures shall include copies of all data sheets to be used in recording test data. The Contractor may use automated test techniques for each test script, provided a one-time demonstration of at least three manual test data points are shown to correlate to an automated test point per script. Final Government approval of test procedures calling for automated test techniques shall be subject to the successful completion of the one-time manual test data points demonstration.

4.1.3. FAT Report

The Contractor shall prepare and submit the FAT Report 20 business days after the completion of FAT IAW DI-NDTI-80809B and CDRL A008.

a. The FAT Report shall include copies of all test data recorded in the course of the FAT, inclusive of all tests and demonstrations. The Contractor’s testing official and the Government witness shall sign all data sheets.

b. The FAT Report shall present the results of all inspections required by the EDIM Modem System Specification, as outlined in the VCRM.

c. The FAT Report shall include all analyses required by the EDIM Modem System Specification, as outlined in the VCRM.

d. The FAT Report shall provide a cross-reference that identifies the test data sheets corresponding to each line on the VCRM that stipulates a test.

e. The FAT Report shall include complete documentation of all problems and anomalies discovered during the course of FAT, their resolution, and the associated regression tests data.

4.1.4. Notification to Start FAT

The Contractor shall inform the Contracting Officer’s Representative (COR) no later than 20 business days prior to start of FAT. The notification shall include a detailed test schedule.

The Government shall have the right to witness any or all of FAT. The Contractor shall advise the COR at least 5 business days in advance of changes to the published FAT schedule.

Government witnesses shall be furnished with a copy of the latest approved FAT Procedures before the FAT commences.

4.1.5. Dry-Run FAT Testing

The Contractor shall perform preliminary (dry-run) testing prior to conducting the formal FAT to resolve any EDIM Modem equipment problems and increase confidence that FAT can be successfully concluded within the planned schedule. Dry-run testing may proceed without a Government witness, but the Government shall have the opportunity to observe such tests at its discretion.

4.1.6. Test Readiness Review (TRR)

A TRR shall be conducted at the Contractor’s facility no less than 5 business days prior to the start of FAT. This review will ascertain the Contractor’s readiness to conduct FAT testing.

a. The TRR shall be conducted after the system integration is completed, the Government approves the draft FAT Procedures, and the dry-run FAT testing is successfully concluded.

b. Government representatives will participate in the TRR and make the final determination as to the Contractor’s readiness to begin FAT.

c. Upon successful completion of the TRR process, a baseline of the FAT Procedures shall be established and placed under configuration management.

4.1.7. FAT Acceptance

The FAT units shall meet all contractual requirements. After the FAT is completed, the FAT units may require refurbishment. The Contractor shall perform PQT on all FAT units before delivery to the Government. FAT acceptance on a DD Form 250 will be contingent upon the Government’s acceptance of a complete and comprehensive FAT Report.

4.1.8. Certifications

4.1.8.1. Transmission Security (TRANSEC)

The Contractor shall perform all required tests and arrangements for NIST certification per FIPS 140-3 requirements, as defined in the EDIM Modem System Specification. The Contractor shall also conduct NIST re-certification for software configuration and baseline modification. The FIPS testing shall be incorporated as part of the FAT testing.

4.1.8.2. Wideband Global Satellite (WGS)

During FAT, the Contractor shall support WGS Certification for transmission over WGS satellites IAW WGS Modem Certification requirements per U.S. Army Space and Missile Defense Command (SMDC). The WGS Modem Certification requirements are addressed in the EDIM Modem System Specification, paragraph 4.1.3.1.2. WGS Modem Certification allows the modem to gain access to the WGS constellation, as authorized, managed, and controlled by the SMDC, in support of specific Joint Staff validated requirements. WGS Modem Certification testing shall be supported as follows.

Phase 0/1 WGS Certification Testing shall be completed as part of the FAT to be conducted at the Contractor’s facility. In addition to submitting the EDIM Modem FAT Report, as described in PWS Paragraph 4.1.3, “FAT Report,” the Contractor shall also support the modem certification process, as defined in the SMDC Modem Certification Checklist.

Upon successful completion of EDIM Modem FAT at the Contractor’s facility, the Contractor shall provide a minimum of 5 FAT EDIM Modems in support of Phase 2 WGS Modem Certification Testing. Government personnel will conduct Phase 2 WGS Modem Certification Testing at the SMDC authorized test facility. Phase 2 WGS Modem Certification Testing will take approximately 40 business days to complete. Contractor personnel shall provide engineering support for 10 business days at the test facility for equipment installation, and for the training of test personnel on EDIM Modem operation. The Contractor shall provide on-call support for the remaining 30 business days of the test period. Phase 2 WGS Modem Certification Testing affirms that the tested modem meets all modem performance thresholds required for certification. The Government will develop the Phase 2 WGS certification test report to be submitted for formal WGS Modem Certification. The Government will accept the FAT baseline upon FAT Report approval and formal WGS Modem Certification from SMDC.

4.2. Production Qualification Test (PQT)

The Contractor shall perform PQT on each EDIM Modem IAW the Government-approved test documents to verify compliance with the EDIM Modem System Specification. All functions designated for PQT in the EDIM Modem System Specification, Table XI VCRM, shall be verified during the PQT for all units.

4.2.1. Production Qualification Test (PQT) Plan

The Contractor shall develop and submit a complete PQT Plan IAW CDRL A009. The PQT Plan shall address the Contractor’s specific approach to verifying that EDIM Modem production lot equipment meets the EDIM Modem System Specification requirements. The PQT Plan shall describe testing techniques and protocols utilized for FAT to the maximum extent practical.

Plans and procedures used to test production modems shall be a subset of those used for FAT.

4.2.2. PQT Procedures

The Contractor shall develop and submit PQT Procedures to address EDIM Modem production units and spares testing to be ordered on this contract. PQT Procedures shall be submitted IAW CDRL A010. The PQT Procedures shall expand upon the submitted and approved PQT Plan by addressing all tests necessary to adequately evaluate the performance of EDIM Modems and spares, thereby providing the Government a basis for acceptance. The Contractor shall perform acceptance testing on each unit or spare, as depicted by the VCRM table in the EDIM Modem System Specification, prior to the acceptance of the production unit by the Government.

4.2.3. PQT Report

The Contractor shall develop and submit the PQT Report IAW CDRL A011. The PQT Report shall document the results of all PQTs performed. The PQT Report shall include all data sheets, signed by the Contractor’s testing official and the Government witness (if applicable). The PQT Report shall indicate National Stock Number (NSN), part number, serial number, and revision level of each item and software configuration item.

4.2.4. PQT Failure Reporting

All PQT failures shall be documented in the PQT Report and Failure Reporting, Analysis, and Corrective Action System (FRACAS) report. Should a production unit fail any acceptance test, the Contractor shall eliminate its cause and prevent reoccurrence of the failure mode. If the Contracting Officer determines the failure mode warrants a retrofit or replacement of the affected equipment or components, whether already accepted or not, then the Contractor shall perform the replacement or retrofit of the equipment or components. The Government reserves the right to withhold acceptance of those units identified as containing a systemic problem until the corrective action is implemented. The Contractor shall bear all costs associated with the correction of individual and systemic acceptance test failures.

4.2.4.1. FRACAS

The Contractor shall perform failure analysis on all hardware and software problems detected during the Contractor phase of testing. Documentation of failures, results of failure analysis, corrective action taken, and retesting shall be documented. For any failure, the Contractor shall determine the cause and recommend a course of corrective action. Upon approval by the Government, the course of corrective action shall be implemented by the Contractor. The Contractor shall include fix, retest, and regression testing as an integral part of the test and evaluation program. In addition to analyzing single failures, the Contractor shall also analyze patterns of failures in order to detect trends and latent design deficiencies. The Contractor shall develop the FRACAS report IAW CDRL A012 when systemic failures or a failure that affects multiple units occur.

5. Integrated Logistic Support

The Contractor shall provide EDIM Modem sustainment support over its life cycle using spare and repair parts, tools and test equipment, training, on-site maintenance, Contractor depot services, and technical and logistical documentation procured on this contract.

5.1. Maintenance Repair and Replacement Service

5.1.1. Maintenance Repair and Replacement Scope

The Contractor shall provide Depot Level repair of EDIM Modems. Depot Level repair refers to repairing LRU of EDIM Modems. LRUs are defined as a component that the Government returned to Contractor for repair.

The Contractor shall provide the Government a list of all repairable items with the Hardware Logistical Analysis Data (HLAD) submitted IAW CDRL D001, and shall include their Maintenance concept, with proposed subcontractor support (if required), and procedures for requesting repairs.

5.1.2. Maintenance Repair

The Contractor shall perform maintenance repair to the returned inoperative EDIM Modem equipment. The Contractor shall repair or replace equipment returned to the depot. The Contractor shall provide calibration, maintenance, and replacement services to support the EDIM Modems. If the repair cost of a returned item is more than 65% of its unit purchase price, the Contractor shall document and discard that item IAW PWS, paragraph 5.1.2.4, requirements.

5.1.2.1. Parts Pricing

The Contractor shall develop and submit the Logistic Support Analysis Record (LSAR) Pricing Plan IAW CDRL D002, to include repair parts pricing. The Contractor shall separate test and inspection pricing from the total repair price.

5.1.2.2. Turn Around Time

Turn-around time is defined as the time from the Contractor’s receipt of inoperative EDIM Modem equipment to the delivery of the repaired item to the Government. EDIM Modem repair turn-around time shall be within 20 business days from the time the Contractor receives the equipment. If the quantity of equipment returned for repair is more than 10 units, the Contractor shall repair and return a minimum of 10 units per month until all units are repaired and returned.

5.1.2.3. Shipment of Repaired and Replacement Equipment

The Contractor will receive the EDIM Modem with a DD Form 1348-1, DoD Single Line Item Requisition System Document (Manual), or a DD Form 1348-1A, Issue Release/Receipt Document. The Contractor shall ship all repaired, replacement, updated, and modified serviceable end items with a DD Form 1149, Re-requisition and Invoice/Shipping Document, IAW the shipping instructions provided by the Government. In order to perpetuate asset visibility, the DD Form 1149, block 6, entitled "Requisition Number," shall contain the original document number provided on the DD Form 1348-1, block numbers 30-43, or the DD Form 1348-1A, block number 24. The DD Form 1348-1 or DD Form 1348-1A is the official shipping document from a Government depot or other Government designated location to the Contractor's repair facility. The Contractor shall bare the cost of shipping repair/replace items FOB Destination.

5.1.2.4. Disposition of Uneconomically Repairable Items

The Contractor shall submit a letter of notification addressing items considered uneconomical to repair or update/modify to the COR for disposition instructions. The COR shall provide the instructions within 10 business days after receipt of the notification. If a determination is not provided within 10 business days, the Contractor shall dispose of item locally and provide documentation of the disposal to the COR.

5.1.2.5. Maintenance Records

The Contractor shall maintain a record of all repair/replacement actions performed during this contract. This maintenance record shall identify returned equipment by name, part number, serial number, equipment received and return dates, and returned equipment warranty status. The Contractor shall also submit the maintenance repair summary in the Monthly Status Report.

5.1.2.6. Repair Warranty

The Contractor shall provide the Government with a warranty period of 120 business days for all repaired LRUs and end items.

a. The Contractor shall be responsible for correcting all latent defects at no cost to the Government.

b. Warranties shall become effective based upon the date of receipt and acceptance at the destination, unless specifically negotiated in a separate agreement between the Government and the Contractor.

c. All pertinent data required for the Government to pursue warranty provisions, remedies, and relief for each item shall be maintained by the Contractor for the duration of the warranty period. All warranty claims and transactions shall be documented and made available for Government review, upon request, or during scheduled meetings and/or reviews.

d. The Contractor shall ensure that subcontractor and/or vendor warranties provide the same coverage and are passed through to the end item

5.2. Packaging and Handling

The Contractor shall arrange and be responsible for shipping the EDIM Modem hardware to the destination(s) stipulated in the contract. The Contractor shall be responsible for the preservation and packaging of all items to be delivered under the terms of the contract. Packaging shall be IAW the best commercial practices of ASTM D3951-98 (2004). The Contractor shall mark all items for shipment and storage IAW best commercial practices for shipments within the Continental United States (CONUS). The Contractor shall coordinate shipping dates with the Government to ensure the destination facility is prepared to receive the shipment.

The Contractor shall make maximum use of the packaging materials in which the equipment was originally received when packaging repaired equipment.