PWS.docx

Performance Work Statement (PWS) For Electronic Warfare Systems Integration Test Environment (EW SITE) System Upgrade for the Electronic Warfare Integrated Laboratories (EWIL)

Performance Work Statement (PWS) For Electronic Warfare Systems Integration Test Environment (EW SITE) System Upgrade for the Electronic Warfare Integrated Laboratories (EWIL)

1.0 BACKGROUND/SCOPE

1.1 BACKGROUND. The Electronic Warfare Integrated Laboratories (EWIL), code 45Q000E, at the Naval Air Warfare Center Weapons Division (NAWCWD), Point Mugu, California currently utilizes an existing Electronic Warfare Systems Integration Test Environment (EW SITE) radar environment simulator to support system performance evaluation and integration of various Electronic Warfare (EW) systems.

1.1.1 The EWIL utilizes an existing EW SITE radar environment simulator to support system performance evaluation and integration of various Electronic Warfare (EW) systems. The EW SITE system is used to test EW systems of the EA-6B, EA-18G, F/A-18, MH-60, E-2C, P-8A and F-35 (JSF) platforms, and corresponding systems and subsystems. The EW SITE provides digitally controlled Radio Frequency (RF), phase, amplitude, and time based modulations that represent threat radars. Adding additional test assets to the EWIL provides a more robust threat environment in the form of a high pulse density, dynamic, simulated flight environment. Testing in a lab environment allows for the generation of more scenarios and denser scenarios. These scenarios represent real threats the various platforms will face in hostile circumstances and cannot be generated during flight test. A laboratory test environment that emulates the pulse density and characteristics of EW Flight Test Threat Ranges allows testing of systems for extended periods with visibility into system performance, which is not available on an aircraft during flight. This will result in expanded capabilities and allow the EWIL to continue to efficiently develop and test current and future EW systems and capabilities in support of aircraft platform integration and test.

1.2 SCOPE. The proposed contract will provide for the development of EW SITE systems and sub-system components for domestic and FMS customers. This will result in expanded capabilities and allow the EWIL to continue to efficiently develop and test current and future EW systems and capabilities in support of aircraft platform integration and test. EW SITE system supports System Configuration Sets (SCS)’s from multiple platforms and provides consistency with the Advanced Weapons Laboratory at China Lake, CA.

1.2.1. This contract will also provide incidental services for on-call and on-site maintenance, repair and system upgrades, including replacement parts for existing systems as well as the newly acquired systems. Incidental services provided under this contract include but are not limited to maintenance, training, and repairs.

2.0 APPLICABLE DOCUMENTS

The following documents are applicable to this PWS. Specific references will be included in individual task orders. If later versions are applicable, use latest version.

2.1 Military Standards

Use with electrical and electronic equipment

2.2 Instructions and Guides

OPNAVINST 3432.1A

DoN Operations Security

Instruction: Risk Management Framework (RMF) for DoD Information Technology (IT)

NSDD 298

2.3 Industry Standards

IEEE 1278.1-1995

Interactive Simulation - Application Protocols

2.4 Non-Government Documents

Doc Number 380-9170001

SIMNET TCS System/Subsystem Specification, Amherst

3.0 TECHNICAL REQUIREMENTS

3.1 EW SITE COMPONENTS

3.1.1 The contractor shall deliver, install and test EW SITE components as defined below and in accordance with individual orders.

3.1.2 The EW SITE components shall be compatible with the government’s existing EW SITE LITE system delivered under contracts N68936-09-C-0138, N68936-13-C-0161 and N68936-16-D-0001. Same configuration compatibility with existing EW SITE system components is required to enable sharing of hardware components between existing threat simulators and leveraging of existing government-developed threat scenario software.

3.1.3 The EW SITE components shall simulate threat and friendly radar systems, communications, and Data Link systems for the purpose of performing systems integration and test on EA-6B, EA-18G, F/A-18, MH-60, E-2C, P-8A and F-35 (JSF) platforms, and corresponding systems and sub-systems.

3.1.4 Each EW SITE components shall be capable of expansion for future EW SITE systems.

3.1.5 The threat parametric programming interface shall have the growth capability to receive flight path and emitter locations/parametrics from external sources.

3.2 SYNTHETIC SOURCE INSTRUMENT (SSI) (CLIN 0001)

The SSI shall be comprised of the following hardware:

3.2.1 The Synthetic Source Instruments (SSI’s) are hardware components that when installed, perform the RF signal generation, and simulation functions of the EW SITE System. The SSIs are fast switching, low phase noise, truly phase-coherent RF sources. Each SSI covers the RF frequency range of 20MHz to 22GHz. Each SSI is completely independent and fully reprogrammable for pulse width, pulse repetition interval, scan and amplitude, frequency, phase, and time of arrival. The SSIs are composed of (Versa Module Eurocard (VME) cards (i.e. RF Controller, Base Band Expander, RF Up Converter and Harmonic Filter Amplifier circuit card assemblies)). (P/N: 40354-41110-50, Specification R40354-00054)

3.2.2 The contractor shall provide SSIs capable of generating current radar system signals. The SSIs shall be capable of being integrated into Stimulus Enclosures. Stimulus Enclosures shall be capable of being integrated into a Stimulus Cabinet (SC). The SC houses the interconnections required for a Maintenance/Alignment Cabinet host computer to communicate to each of the SSIs or a group of SSIs.

3.2.3 The SSIs shall, using industry standards, create current simulations of radar parameters including: RF, Pulse Repetition Interval (PRI), Pulse widths, scan characteristics, and be capable of synchronizing with other SSIs.

3.2.4 The SSIs shall simulate scan characteristics of new generation Airborne Intercept (AI) radars and create high fidelity Barker code with variable transition times and dwell periods, i.e. pauses between bursts of received RF information, being simulated.

3.2.5 The SSIs shall be interchangeable with the NAWCWD current -50 EW SITE system(s).

3.2.6 The SSIs shall provide threat environment density and generation of precise emitter pairs for real-time correlation, which meet the specifications found in Attachments 3 in Section J of the basic contract.

3.2.7 The SSIs shall be able to create a realistic RF environment in the controlled space of an integration laboratory.

3.2.8 Intrapulse Modulations; Linear and non-linear, saw tooth, sinusoidal, linear ramp up and down, triangular, exponential, user defined, discrete Frequency Modulation on Pulse (FMOP)/Phase Modulation on Pulse (PMOP)/Amplitude Modulation on Pulse (AMOP), intentional FMOP/PMOP/AMOP, unintentional FMOP/PMOP/AMOP, discrete PMOP, frequency modulated continuous wave, Frequency Shift Keying (FSK).

3.2.9 Operator Selected Antenna Patterns; Linear and non-linear, saw tooth, sinusoidal, linear ramp up and down, triangular, exponential, user defined, discrete FMOP/PMOP/AMOP, intentional FMOP/PMOP/AMOP, unintentional FMOP/PMOP/AMOP, discrete PMOP, frequency modulated continuous wave, FSK.

3.3 RF SWITCH MATRIX (CLIN 0002)

The RF Switch Matrix shall be comprised of the following hardware:

3.3.1 The RF Switch Matrix is a set of unique panel assemblies mounted to the face of the Stimulus Electronic enclosure of an Advanced Architecture Phase Amplitude and Time Simulator (A2PATS) product. The purpose of these panels is to provide the customer the ability to manually select the number of SSI sets per RF port. Changing RF port/SSI is currently performed externally from the RF panel output. The intent of this RF Switch Matrix allows the number of SSI per RF port to be selected without the addition of external combiners and switches. The number of SSI’s per port can be 1, 2, 4, or 8. The panel will be constructed as a chassis plate mounted into housing with an RF output panel. (P/N: 40354-40500-10, Specification 40354-40500).

3.4 Integrated EW Cabinet System (CLIN 0003)

The Integrated EW Cabinet System shall be comprised of the following hardware:

3.4.1 The Integrated EW Cabinet System also known as the A2PATS Single-Cabinet System can house up to sixteen SSIs, along with maintenance alignment capability, in one 19-inch cabinet. (P/N: 40354-40150-20, Specification R40354-00041, Rev B)

3.4.2 The Integrated EW Cabinet System contains the master clock and distribution system; this includes the workstation computers that are the human interface for the overall system. The Integrated EW Cabinet System contains one modular VME enclosure; a Run Time Simulator/Maintenance enclosure. The enclosure is a self-contained removable assembly with its own power supply and cooling fans. The cabinet also interfaces to an RF power meter for external amplitude alignment.

3.4.3 The workstation computers shall consist of a Scenario Controller Personal Computer (PC) and a Maintenance PC. The Scenario Controller PC shall be used to create, modify, statically test signal models, and run dynamic simulations. The Maintenance PC shall perform Built in Test (BIT_), report system errors and allow the operator to perform alignment on the system.

3.5 STIMULUS CABINET (SC) (CLIN 0004)

The SC shall be comprised of the following hardware:

3.5.1 The SC houses four (4) identical Stimulus Enclosures and a distribution assembly for clock, sync, and Ethernet distribution throughout the cabinet. Each Stimulus Enclosure is capable of housing 8 SSIs. The Stimulus Enclosure also contains a Stimulus Controller, power supply, cooling fans, and power combiners. (P/N: 40354-41105-50, Specification R40354-00139)

3.5.2 The contractor shall provide a SC capable of holding a maximum of four (4) VME enclosures (with up to 40 slots each) to house the SSIs. The cabinet shall provide the interconnections required to communicate with an external Host computer.

3.5.3 The cabinet shall provide power for the VME rack enclosures.

3.5.4 The cabinet shall provide a precision clock time signal, sync signal, and Ethernet distribution to each SSI enclosure.

3.5.5 The cabinet shall provide an interconnection methodology for all the SSIs to communicate with a host computer or supplied maintenance functions.

3.5.4 The Integrated EW Cabinet System (-20) houses two (2) Stimulus Enclosures and a distribution assembly for clock, sync, and Ethernet distribution throughout the cabinet. The identical Stimulus Enclosures are capable of housing 8 SSIs each for a maximum total of 16 SSIs. The Stimulus Enclosure also contains a Stimulus Controller, power supply, cooling fans, and power combiners. (P/N: 40354-40150-20, Specification R40354-00041, Rev B)

3.6 SPARES (CLIN 0005)

3.6.1 The contractor will hold Government Furnished Equipment (GFE) spare components to support the EW SITE system and other Government systems as defined in individual Task Orders. The spare components will be agreed upon by the contractor and the Government. The Government may amend the list and quantities of spare components maintained by the contractor at the Governments risk. At the end of contract performance, the Contractor shall deliver all unused spares to the Government.

3.7 Advanced Architecture Desktop Signal Generator (A2DSG) (CLIN 0006)

3.7.1 The A2DSG is a further scaled down configuration of A2PATS circuit assemblies, packaged into a reduced single VME desktop enclosure. The system provides a low-cost entry level Unintentional Modulation on Pulse (UMOP), and simultaneous amplitude simulation capabilities.

The A2DSG is an entry level Electronic Warfare RF Simulator that supports the frequency range from 20 MHz to 22 GHz. The base system will support two radio frequency synthesizers and is expandable by adding an additional desktop unit to support four synthesizers (P/N: 40354-40320-40, Specification R40508-00001).

3.8 A2DRI - Advanced Architecture Data Recorder / Injector (A2DRI) (CLIN 0007)

3.8.1 The A2PATS – SSC Interface expands upon previously completed efforts to interface A2PATS to the Next Generation Electronic Warfare Environment Generator (NEWEG) Digital Generator (DGEN). The A2PATS shall be capable of interfacing with the DGEN, accepting DGEN generated Pulse Descriptor Words (PDWs) (Defined to the own-ship centroid), and producing RF pulses at each antenna element with the correct Phase, Amplitude and Time Angle of Arrival (AOA) information.

3.9 MAINTENANCE/REPAIRS/MODIFICATIONS (CLIN 0008)

3.9.1 REPAIRED COMPONENT RF PERFORMANCE

3.9.1.1 The contractor shall meet the accuracy requirements in contract Attachment 3 – Specifications, including Tables 1 and 2 to ensure all threat signal simulations fall within the parameters required for adequate accuracy measured by the System Under Test (SUT).

3.9.2 REPAIR SERVICES

3.9.2.1 The contractor shall provide support for hardware and software repair. Repair services shall consist of technical telephone services, trouble reporting, parts repair evaluation, parts repair, and on-site hardware and/or software problem support when required. (CDRL A002, A006)

3.9.2.2 Telephone and Email Support (Helpdesk). The contractor shall be available to provide technical support services Monday through Friday, 8:00 a.m. to 5:00 p.m. EST (except Federal Holidays) via telephone and electronic mail services. A Trouble Report shall be created for each telephone and email incident. (CDRL A005)

3.9.2.3 Trouble Report. Utilization of the Helpdesk service (whether via email or telephone) will generate a Trouble Report for each incident. Incidents will be tracked through completion. All incidents will be reported in the month they occur, regardless of status (open or closed). Completed items will fall on the next monthly report, open items will carry forward to resolution. Maintenance data collection for repair parts will be collected and maintained. A summary of all incidents, open or closed, will be maintained for the duration of the Contract. (CDRL A005)

3.9.2.4 Information included in Trouble Reports will be defined by the Contractor (not to include classified information) under individual Task Orders and approved by the Government. Trouble Reports should include, at a minimum the following information: failure description, part number, serial number, error messages, date of failure, failure site, repair facility’s evaluation results, failed components, serial numbers, repair action, date of repair, shipment information, and other details deemed relevant to continuous improvement. (CDRL A005)

3.9.2.5 Repair Procedures. The Contractor shall provide on-call support to the Government after telephone and/or electronic mail (email) notification by the Technical Point of Contact (TPOC) indicating equipment is inoperative. The Contractor shall inform the TPOC in a timely manner of the problem(s) with the equipment and the proposed solution with a time frame for repair. (CDRL A004)

3.9.2.6 Upon receipt of the inoperative component, the Contractor shall provide part repair evaluation, complete repair, functional test and return of repairable defective EWSITE components. (CDRL A006)

3.9.2.7 When a component is returned for repair, the Contractor shall inspect, test and evaluate to determine the extent of the repair required to make the component ready-for-issue. The cost for these repairs will be proposed to the Government. The cost will be negotiated and when approved by the Government through execution of a task order, the Contractor shall perform the repair.

3.9.2.8 The Contractor shall test all repaired assets to insure all original specifications are met and in accordance with the specification attachments?. The Contractor shall system test all repaired assets as specified in each individual task order. Contractor shall utilize a Contractor furnished EWSITE system with a similar configuration of the Government’s EWSITE to support testing of repaired items.

3.9.2.9 The Contractor shall provide Full Time Employee (FTE) on-site support if necessary to meet operational requirements. FTE requirements will be identified in individual Task Orders.

3.9.3 MODIFICATION SERVICES

3.9.3.1 The contractor shall furnish all material, parts, components, and engineering and technical services necessary to modify and/or develop variants of the system.

3.9.3.2 On receipt of a new requirement, the Government will provide the contractor with a Performance Work Statement (PWS) and a revised performance specification and/or drawing (if applicable). The PWS will specify if existing equipment will be modified to meet the Government’s operational needs. The Contractor shall complete a Facility Acceptance Test Plan to ensure the Governments new parameters are met within scope. (CDRL for FATP?)

3.9.3.3 Upon receipt of the PWS and revised performance specification and/or envelope drawing, the contractor shall provide a short technical narrative as to how the modification requirement will be incorporated into the existing design together with a cost and schedule proposal in accordance with 5252.216-9534 task order procedures for the subject effort. The Government will review the proposal for acceptability and enter into discussions with the contractor, if necessary. Upon completion of this process, the Government may issue a cost plus fixed fee task order under (CLIN 0008). Once the contractor receives the executed order, the contractor shall complete the effort within the negotiated schedule.

3.9.4 PROGRAM MANAGEMENT

3.9.4.1 The contractor shall report and document monthly status of the contract. (CDRL A00A)

3.10 SYSTEM TRAINING (CLIN 0009)

Training shall be provided for up to twenty (20) technical personnel on-site at Point Mugu, CA. Training shall include system operation, move and set-up between labs, maintenance/calibration of the systems to include both periodic (monthly) and quarterly/yearly. Training shall include threat simulation and scenario design. (CDRL A009)

3.11 MATERIALS (CLIN 0010)

3.11.1 Materials. The Contractor shall provide parts and materials to repair and/or replace failed equipment unless stated otherwise. All Beyond-Economical-Repair (BER) items will be reported to the Government when known by the Contractor. If the total cost of repair (labor and parts) total more than 100% of the item purchase price, the item should be deemed BER and replaced with a new item. The Contractor shall have thirty (30) calendar days to notify the Government after receipt of the failed material stating whether it can repair the item or if the item is BER. The Contractor shall repair and/or replace defective software media or firmware for the aforementioned equipment unless stated otherwise. The Contractor shall provide updates for software problems. (CDRL A006)

3.11.2 Shipping. The contractor shall provide return shipping for items to be repaired as needed between Hunt Valley, MD and Point Mugu, CA, or a designated destination provided in writing by the COR, as specified in each individual order.

3.11.3 During performance of a task order, the Contractor may be required to acquire material in support of incidental services. The Contractor shall identify materials requirements needed for this contract as defined in individual task orders. In the event that additional materials are required after task order award, the contractor shall obtain written approval from the Contracting Officer's Representative (COR) for purchases up to $3,000 for supplies and $2,500 for services. For Purchases above these amounts, the contractor must obtain prior written approval from the Procuring Contracting Officer.

3.12 TRAVEL (CLIN 0011)

3.12.1 Travel during the performance of this PWS may be required to support the tasking. The list below represents the estimated annual travel requirements.

The contractor shall submit a request for travel in support of this contract. Each request shall be submitted at least one (1) week in advance to the Government Contracting Officer’s Representative (COR) for approval. Each travel request shall minimally consist of:

Date of Request Delivery order number Employee(s) Date and duration of proposed travel Purpose of travel Destination Cost estimate (airfare, per diem, car rental, miscellaneous expenses) Total travel allowance on the TO Total travel cost expended to date Approval signatures

Upon completion of each trip, the contractor shall submit a trip report. (CDRL A007)

3.12.2 SITE VISITS FOR REPAIR OF EQUIPMENT

The contractor shall provide on-site repair services support to address unscheduled maintenance actions beyond the scope of Helpdesk support. On-site support shall include troubleshooting and corrective actions as required. Individual T.O.s will define travel requirements. (CDRL A007)

3.12.3 SITE VISITS FOR SCHEDULED MAINTENANCE SUPPORT

The contractor shall provide on-site support to perform scheduled maintenance. On-site support shall include software upgrades and the installation of new hardware due to equipment upgrades. On-site support shall be performed by a qualified Contractor technician as required. A minimum of two, five-day (including travel) site visits shall be performed per year. Individual T.O.s will provide specific travel details. (CDRL A007)

3.12.4 SITE VISITS FOR ACCEPTANCE TEST

The contractor shall support a Site Acceptance Test (SAT) at Pt. Mugu. The purpose of SAT testing is to verify that the system still performs as designed at Pt. Mugu. The SAT testing shall be a sub-set of the Factory Acceptance Test (FAT) testing as agreed between the Government and the contractor. The contractor shall develop the SAT procedures and submit it for Government review / modification and approval 60 days prior to the start of SAT. The contractor shall document test results in a final acceptance test plan. (CDRL A003)

3.13 DOCUMENTATION (CLINs 0003, 0005)

3.13.1 The contractor shall provide documentation for the delivered (and catalog hardware) EW SITE systems that describes system operation, software users’ manual, maintenance procedures, alignment procedures, and detailed specifications. Component documentation shall include any changes that have occurred during production. (CDRL A001)

3.14 COMPONENT TESTING (CLIN 0001, 0002, 0003, 0004, 0005, 0006)

3.14.1 The contractor shall be responsible for testing the component to verify that it is ready for system integration and testing in accordance with Acceptance Test Procedures. (CDRL A003)

3.14.2 The contractor shall perform a formal FAT of the component. The purpose of the FAT shall be to demonstrate compliance of the component to an agreed component acceptance test procedure (ATP). The contractor shall develop the component ATP and submit to the Government for review / modification and approval 60 days prior to the start of ATP. (CDRL A003) The Contractor shall support documentation of test results in a separate acceptance test plan for the component. (CDRL A003)

4.0 DATA DELIVERABLES (CLIN 0012)

Specific items of reports, test plans, procedures, technical support documents, meeting minutes, and progress reports will be provided in accordance with the applicable Contract Data Requirements List (CDRLs) per contractor format.

5.0 SPECIAL CONSIDERATIONS

5.1 SECURITY

Personnel Security

The contractor shall provide personnel with the appropriate security clearance levels for the work to be performed. Access to SECRET information (on-site) is required in the performance of this contract and shall be in accordance with Department of Defense (DoD) 5220.22-M, National Industrial Security Program Operating Manual (NISPOM) and applicable DoD Personnel Security regulations. The contractor shall maintain sufficiently cleared personnel to perform the tasks required by this PWS IAW the DD Form 254, and the contract. All contractor personnel shall possess a clearance and need-to-know commensurate with the requirements of their positions.

Information Security

Direct support contractor personnel working under the purview of a Department of Navy (DoN) Commanding Officer/Commander shall comply with the local security provisions and the requirements of SECNAV M-5510.36 (series). The contractor shall implement and maintain security procedures and controls to prevent unauthorized disclosure of controlled unclassified information and to control distribution of controlled unclassified information in accordance with DoD 5220.22-M, National Industrial Security Program Operating Manual (NISPOM), and SECNAV M-5510.36.

For Official Use Only (FOUO) Information

FOUO information generated or provided under this contract shall be marked and safeguarded as specified in DoDM 5200.01 (DoD Information Security Program: Controlled Unclassified Information (CUI)) Vol. 4 (enclosure 3 pages 11-18), available at http://www.dtic.mil/whs/directives/corres/pdf/520001_vol4.pdf and DoD 5400.7-R, Freedom of Information Program Chapter 3 (pages 31-42), available at http://www.dtic.mil/whs/directives/corres/pdf/ 540007r.pdf.

Information Assurance (IA)

The contractor shall comply with the IA security requirements for accessing U.S. Government IT systems. The contractor shall adhere to the DoN Information Assurance Program prescribed methodologies for the protection of information to support DoN Missions.

Operations Security (OPSEC)

All work is to be performed in accordance with DoD and DoN OPSEC requirements per the National Security Decision Directive 298, DoDD 5205.02, DoD Operations Security Program, DoD 5205.02-M, DoD Operations Security Program Manual, and OPNAVINST 3432.1A DoN Operations Security. As applicable, the contractor will be responsible for subcontractor implementation of the OPSEC program requirements for this contract. (CDRL A00B)

5.2 PLACE OF PERFORMANCE

System development and repairs will be performed at the contractor’s facility in Hunt Valley, MD. System installation will be performed at NAWCWD Point Mugu, CA.

5.3 GOVERNMENT FURNISHED EQUIPMENT (GFE) / GOVERNMENT FURNISHED INFORMATION (GFI)

5.3.1 Contractor Access to GFE. The Government will furnish access to the EWIL on an as-needed basis during normal operating hours. The contractor shall provide a list to the EWIL manager of the personnel with the “need to know” for access to the EWIL. Contractor personnel performing these tasks will require access to classified facilities, and must have appropriate clearances on file with the NAWCWD Security Office. The government reserves the right to control the laboratory schedule and use of documentation required for performance of this contract.

5.3.2 Contractor Access to GFI. The contractor will be allowed access to the EWIL during normal operating hours. The contractor shall provide to the government a list of personnel with “need to know” access to EW SITE controlled data.

The Government shall furnish the contractor with all existing available EW SITE documentation and software required during contract performance.

6.0 PERFORMANCE STANDARDS AND EVALUATION

6.1.0 Performance Indicator/ Evaluation:

A Surveillance Activity Checklist (SAC) is attached for information purposes. Contractor performance on the service tasks will be evaluated on a periodic basis as described in the SAC. Monthly status reports (CDRL A00A) submitted to the Contracting Officer Representative (COR) will identify the work that had been performed during the month, deliverables that have been submitted, and the name of the Government representative that have received the deliverable.