14-R-0122_RFP_Amendment.docx

N68936-14-R-0122

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION A - SOLICITATION/CONTRACT FORM

The standard size code 500 has been added.

The required response date/time has changed from 31-Aug-2015 12:00 AM to 04-Sep-2015 12:00 PM.

SECTION B - SUPPLIES OR SERVICES AND PRICES

CLIN 0001

The CLIN extended description has changed from:

Stimulus Cabinet Enclosure (P/N 40354-41105-50) in accordance with the Statement of Work in Section C.

To:

Stimulus Cabinet Enclosure (P/N 40354-41105-50) in accordance with the Statement of Work in Section C. Specification R40354-00139.

The FOB has changed from Origin to Destination.

CLIN 0002

Synthetic Source Instruments (P/N 40354-41110-50) in accordance with the Statement of Work in Section C.

To:

Synthetic Source Instruments (P/N 40354-41110-50) in accordance with the Statement of Work in Section C. Specification R40354-00054.

CLIN 0003

Maintenance Alignment Cabinet (P/N 40354-41100-50) in accordance with the Statement of Work in Section C.

To:

Maintenance Alignment Cabinet (P/N 40354-41100-50) in accordance with the Statement of Work in Section C. Specification R40354-00138.

CLIN 0004

CLIN 0005

Mini-A2Pats in accordance with the Statement of Work in Section C.

To:

Mini-A2Pats (P/N 40354-40320-40) in accordance with the Statement of Work in Section C. Specification R40508-00001.

CLIN 0006

Integrated EW Cabinet System (P/N 40354-40150-20) in accordance with the Statement of Work in Section C.

To:

Integrated EW Cabinet System (P/N 40354-40150-20) in accordance with the Statement of Work in Section C. Specification R40354-00041, Rev B.

CLIN 0007

The unit of issue has changed from Lot to Each.

CLIN 0010

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

The following have been modified:

PERFORMANCE WORK STATEMENT

Performance Work Statement (PWS) For Electronic Warfare Systems Integration Test Environment (EW SITE) System Upgrade for the Electronic Combat Simulation and Evaluation Laboratory (ECSEL)

1.0 BACKGROUND/SCOPE

1.1 BACKGROUND. The Electronic Combat Simulation and Evaluation Laboratory (ECSEL), code 45P300E, 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 ECSEL 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 Electronic Warfare 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 RF frequency, phase, amplitude, and time based modulations that represent threat radars. Adding additional test assets to the ECSEL 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 of time with visibility into system performance which is not available on an aircraft during flight. This will result in expanded capabilities and allow the ECSEL 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 production and development of EW SITE systems and sub-system components for domestic and FMS customers. This will result in expanded capabilities and allow the ECSEL 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 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 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.

2.1 Military Standards

2.2 Instructions and Guides

OPNAVINST 3432.1A

DoN Operations Security

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

2.3 Industry Standards

IEEE 1278.1-1995

Interactive Simulation - Application Protocols

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 and N68936-13-C-0161. 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 STIMULUS CABINET (SC) (CLIN 0001)

The SC shall be comprised of the following hardware:

3.2.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.2.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.2.3 The cabinet shall provide power for the VME rack enclosures.

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

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

3.3 SYNTHETIC SOURCE INSTRUMENT (SSI) (CLIN 0002)

The SSI shall be comprised of the following hardware:

3.3.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 totally 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.3.2 The contractor shall provide SSIs capable of generating current radar system signals. The SSIs shall be capable of being installed into Stimulus Enclosures. Stimulus Enclosures shall capable of being installed into a 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.3.3 The SSIs shall, using industry standards, create current simulations of radar parameters including: RF Frequency, Pulse Repetition Interval (PRI), Pulse widths, scan characteristics, and be capable of synchronizing with other SSIs.

3.3.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.3.5 The SSIs shall be interchangeable with the NAWCWD current -50 EW SITE system(s).

3.3.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 1 and 2 to this PWS.

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

3.3.8 Intrapulse Modulations; Linear and non-linear, sawtooth, 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.9 Operator Selected Antenna Patterns; Linear and non-linear, sawtooth, sinusoidal, linear ramp up and down, triangular, exponential, user defi ned, discrete FMOP/PMOP/AMOP, intentional FMOP/PMOP/AMOP, unintentional FMOP/PMOP/AMOP, discrete PMOP, frequency modulated continuous wave, FSK.

3.4 MAINTENANCE/ALIGNMENT CABINET (MAC) (CLIN 0003)

The MAC shall be comprised of the following hardware:

3.4.1 The MAC contains the master clock and distribution system, this includes the workstation computers that are the human interface for the overall system. The MAC 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. (P/N: 40354‐41100‐50, Specification R40354-00138)

3.4.2 The workstation computers shall consist of a Scenario Controller 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 BIT, report system errors and allow the operator to perform alignment on the system. The workstations shall be connected to the MAC over Ethernet.

3.4.3 The Contractor shall deliver a maintenance alignment cabinet capable of providing the necessary signals or data to perform calibration and check out of the alignment of the stimulus cabinets that are installed.

3.5 RF SWITCH MATRIX (CLIN 0004)

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

3.5.1 The RF Switch Matrix is a set of unique panel assemblies mounted to the face of the Stimulus Electronic enclosure of an 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.6 Mini-A2PATS (CLIN 0005)

3.6.1 The Mini-A2PATS is a scaled down configuration of A2PATS circuit assemblies, packaged into a single VME enclosure. The system provides a low-cost entry level (Amplitude AOA only) solution for EW Simulation.

Like other aspects of A2PATS technology, the Mini-A2PATS is modular and expandable. The base configuration is 4 SSIs on four Ports. Additional SSIs may be installed, and may either be combined to increase pulse density, or may be brought out as parallel ports (P/N: 40354-40320-40, Specification R40508-00001).

3.7 Integrated EW Cabinet System (CLIN 0006)

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

3.7.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.7.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.7.3 The workstation computers shall consist of a Scenario Controller 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 BIT, report system errors and allow the operator to perform alignment on the system.

3.7.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.8 SPARES (CLIN 0007)

3.8.1 The contractor will hold Government Furnished Equipment (GFE) spare components to support the EW SITE system. 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.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 4 – Specifications, including Tables 1 and 2to ensure all threat signal simulations fall within the parameters required for adequate accuracy measured by the 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.

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 in like fashion. 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.

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

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 MANGEMENT

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 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. This support shall be performed by a qualified Contractor technician. 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 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 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 FACTORY ACCEPTANCE TEST. The contractor shall perform a formal Factory Acceptance Test (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 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 ECSEL on an as-needed basis during normal operating hours. The contractor shall provide a list to the ECSEL manager of the personnel with the “need to know” for access to the ECSEL. Contractor personnel performing these tasks will require access to classified facilities, and must have appropriate clearances on file with the NAWCWPNS 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 ECSEL 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 TASK ORDER 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.

7.0 CONTRACT PERFORMANCE SUREVEILLANCE

The contractor’s performance will be monitored by the Government via the COR’s periodic completion of a Surveillance Activity Checklist (SAC). The SAC will be provided to the contractor as a courtesy for informational purposes only.

Cost – Assess the contractor’s effectiveness in forecasting, managing, and controlling contract cost. Is the contractor experiencing cost growth or under run? If so, discuss the causes and contractor-proposed solutions for the cost overruns. In addition, the extent to which the contractor demonstrates a sense of cost responsibility, through the efficient use of resources in each work effort will be assessed.

Schedule – Assess the contractor’s adherence to the required delivery schedule by assessing the contractor’s efforts during the assessment period that contribute to or effect the schedule variance. Also address significance of scheduled events, discuss the causes of any delays, and assess the effectiveness of contractor corrective actions.

Quality – Assess the contractor’s effort to transform operational requirements into an integrated solution. Areas of focus may include the planning and management of program tasks, the quality of support provided throughout all phases of contract execution, the integration of program management specialties, management of interfaces, and the management of a totally integrated effort of all program management concerns to meet cost, performance, and schedule objectives. Assess how successfully the contractor meets the program quality.

Management – Assess the timeliness, completeness and quality of problem identification, corrective action plans, proposal submittals (especially responses to change orders, Engineering Change Proposals or undefinitized contract actions), the contractor’s history of reasonable and cooperative behavior, effective business relations, and customer satisfaction. Consider the contractor’s responsiveness to the program as it relates to meeting contract requirements during the period covered by the report.

Data Standards – Assess the contractor’s accuracy and timeliness of each data deliverable. Assess the contractor’s adherence with respect to following the applicable DID and format cited in each CDRL.

SECTION D - PACKAGING AND MARKING

HEADER

CLIN PACKAGING AND MARKING INFORMATION

The hardware provided for under CLINS 0001, 0002, 0003, 0004, 0005, 0006, 0007, 0008 and 0010 shall be packaged in accordance with NAVAIR Clauses 5252.247-9508, 5252.247-9509, and 5252.247-9510.

CLINs 0009 and 0011: Not applicable

CLIN 0012: Data shall be packaged and marked in accordance with NAVAIR Clause 5252.247-9507 and Contract Data Requirements Lists, DD 1423, Exhibit A.

SECTION E - INSPECTION AND ACCEPTANCE

INFORMATION TO OFFERORS

CLIN INSPECTION AND ACCEPTANCE TERMS

CLINs 0001, 0002, 0003, 0004, 0005, 0006, 0007, 0008 and 0010: Source inspection of the hardware, incidental services, and materials shall be conducted at Contractor facility. Final inspection and acceptance shall be in accordance with FAR Clause 52.246-2, FAR Clause 52.246-5, and the Acceptance Test Plan provided by the Contractor in accordance with CDRL A003 and shall be evidenced by Government execution of a Material Inspection and Receiving Report, DD Form 250, submitted through the Wide Area Workflow (WAWF) system.

CLINs 0009 and 0011: Not applicable

CLIN 0012: Destination inspection and acceptance of the data called for hereunder shall be in accordance with Exhibit A, Contract Data Requirements List, DD Form 1423, DFARS Clause 252.246-7000, and NAVAIR Clause 5252.246-9514..

SECTION F - DELIVERIES OR PERFORMANCE

The following have been deleted:

SECTION H - SPECIAL CONTRACT REQUIREMENTS

*This clause will be incorporated and filled in under each incrementally-funded task order.

SECTION I - CONTRACT CLAUSES

The following have been deleted:

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

L – 1 CONTENT OF PROPOSALS (SUPPLIES OR SERVICES)(JUN 2011) (June 2014)

PART A GENERAL INSTRUCTIONS

1.0 GENERAL

Clarity and completeness of the proposal are of the utmost importance. The proposal must be written in a practical, clear and concise manner. It must use quantitative terms whenever possible and must avoid qualitative adjectives to the maximum extent possible. Proposal volumes must be internally consistent or the proposal may be considered unrealistic and may be considered unacceptable.

The Offeror must include any data that illustrates the adequacy of the various assumptions, approaches, and solutions to problems. Failure to address a specific factor or sub factor clearly may be considered a deficiency. There is no need to repeat information in more than one volume if an overlap exists; the detailed information must be included in the most logical place and summarized and referenced in other areas. Unnecessarily elaborate brochures or other presentation materials beyond that sufficient to present a complete and effective proposal is neither necessary nor desired.

Any data previously submitted in response to another solicitation will be assumed unavailable to the Government. This data must not be incorporated into any portion of the proposal by reference.

2.0 PROPOSAL FORMAT

Proposal must be formatted using a Times New Roman 12 pt normal font, double-spaced with 1-inch margins all around, and formatted for standard 8.5 x 11 inch paper. All pages should be numbered with section and page numbers. Drawings may be provided separately and may be any size. Graphs shall be presented in no smaller than 10 pt font and should contain a grid.

The Offeror will provide one complete electronic copy of the proposal via email to the Contract Specialist fully compatible with Microsoft Office 2003. For information not supported by MS Office products, provide in a PDF format. The Offeror will ensure that the Price/Cost Volume includes a Microsoft Excel spreadsheet, including all formulas. All proposal documents should be unlocked.

The Offeror must present proposal information in a manner that facilitates a one-to-one comparison between the information presented and this Proposal Instruction. Proposal information must be structured such that its paragraph number/letter is identical to the Proposal Instruction’s paragraph number to which it is responding, although the Offeror may add lower tier subparagraphs. The Offeror must provide reasons it will not provide information for a particular paragraph. The proposal information instructions are structured by paragraph numbers where first, second, third, and fourth parts correspond to the volume, book, section, and element, etc… in the Offeror’s proposal.

3.0 PROPOSAL CONTENT AND VOLUMES

Each volume of the proposal shall be submitted as one electronic copy as specified in the table below. All volumes shall be delivered to the address provided in Section 4.0 prior to the closing date/time stated in this solicitation. Page limitations for each volume, if any, are also specified in the table below; title and table of contents pages do not count towards page limits.

Information submitted as an Annex to the proposal includes manuals, specifications, plans, procedures, and policies that exist as an official document of the company or facility, as well as other information request in Part B Specific Instructions. Annexes do not have page limitations. The authorized volumes are summarized in the table below.

Each volume shall contain the following information:

The Offeror shall submit a Cross Reference Matrix (CRM) for the Technical Volume, similar to the example below, to help ensure that all solicitation requirements are addressed and to facilitate the evaluators’ review of the Offeror’s proposal. The CRM should be a single integrated matrix and cross-reference the proposal volumes and paragraphs to specific RFP requirements, as well as other parts of the proposal that contain relevant information. The Offeror’s CRM may be identical to the example below or revised such as to add columns to indicate the page number on which information may be found, identify where other relevant information in the proposal is located, or provide other comments. The CRM does not count against any of the proposal page limitations.

EXAMPLE OF A CROSS REFERENCE MATRIX (CRM)

Volume 2 Technical Example: Para 3.1 Note: This column shall address all paragraphs in Sections xx and xy of the Performance Specification

Volume 2 Technical

Volume 2 Technical

4.0 PROPOSAL SUBMISSION

Clearly label all documents with the solicitation number. The submission date for the original proposal shall be no later than the date and time specified in Block 9 of Standard Form 33 of the RFP.

Offeror shall submit proposals electronically to sierra.trepanier@navy.mil. Offeror shall not submit proposals by facsimile.

All communications (email, written) shall include the following:

Solicitation Number: N68936-14-R-0122

5.0 CLASSIFIED DATA

All proposals must be UNCLASSIFIED

PART B SPECIFIC INSTRUCTIONS

1.0 VOLUME 1: EXECUTIVE SUMMARY/GENERAL INFO

Note: This volume shall not contain any reference to cost or price.

The purpose of the Executive Summary is to provide the evaluators with an overview of the Offeror’s proposal and strategy. The Offeror shall include the following in this volume:

a. A concise abstract of the Offeror’s strategy for each of the non-cost evaluation criteria contained in the solicitation.

2.0 VOLUME 2: TECHNICAL

Note: This volume shall not contain any reference to cost or price.

(a) Specifications. The Offeror must provide specifications for CLINs 0001 through 0006

(b) Compliance Matrix. The Offeror must provide a matrix detailing plans for compliance with all elements of the Statement of Work (SOW).

(c) Exceptions, Deviations, and Waivers. In this Volume, the Offeror must certify that it contains all exceptions, deviations, and waivers that the Offeror takes from the provisions of the solicitation and its applicable documents. An “exception” is where an Offeror states it will not comply with a requirement, usually involving contract terms and conditions. A “deviation” is where an Offeror states it will not comply with a requirement but proposes an alternative to meet the intent of the requirement, usually involving a specification. A “waiver” is where an Offeror requests authorization for the Government to accept an item, which will depart from, specified requirements, but would nevertheless be considered suitable. Exceptions, deviations, and requests for waivers may cause proposals to be considered deficient. An assumption or condition shall not be considered an exception, deviation, or request for waiver as defined herein.

Provide a detailed description for each exception, deviation, or request for waiver, as applicable. The Offeror shall indicate the Offeror’s difficulty with the applicable requirement and the Offeror’s proposed solution. The Offeror shall specifically identify the portion of the solicitation and the Offeror’s proposal which are affected. If there are no exceptions, deviations or waivers, the Offeror shall provide a one-page Executive Summary stating so.

(c) Security. The contractor shall provide a rationale or plan to implement the security requirements to their proposed work force in support of PWS paragraph 5.1.

3.0 VOLUME 3: PRICE/COST PROPOSAL

(a) The Offeror must propose an hourly rate for each labor category proposed. The rate information must consist of specific rates provided each year for the Offeror and all subcontractors. Individual consultants must be proposed as subcontractors. The proposal shall clearly demonstrate the individual cost elements from which the composite rate is developed.

(b) All proposed costs must be consistent and demonstrate a clear understanding as to how both prime and subcontractor hours and rates were derived. Inconsistencies in the proposal between prime and subcontractor hours and rates may be considered a risk to the Government.

(c) All proposed costs must be adequately supported. The proposal must include sufficient background to show derivation. If the cost proposal cannot be understood, it may result in the entire proposal being found to be unacceptable and thus eliminated from award.

(d) Hardware. The offeror shall insert the unit price for each quantity amount (if unit pricing differs, offeror shall indicate unit price by fiscal or calendar year)

(e) Labor Hours. The Offeror shall use the hours outlined in section B, Clause 5252.211-9503 “Level of Effort”. If the Offeror does not agree with the labor hours, the Offeror shall include a detailed explanation and supporting documentation regarding labor hours. Subcontractor labor hours shall be included in the Labor Hour Cost Element and specifically identified.

(f) Other Direct Costs. The Government has estimated the following Other Direct Costs:

Travel - $80,000 and Material - $85,000.plus any applicable G&A or handling fees. The Offeror is encouraged to propose realistic amounts for ODCs. If amounts proposed are different than estimated by the Government, the Offeror shall provide a written rationale including a break out of costs.

(g) Offerors shall fully disclose the elemental breakdown of all proposed estimated cost elements for each CLIN. For the Direct labor categories, the offeror is required to submit labor rates for proposed individuals. If composite or category averages are proposed, provide a breakdown of how rates are developed. If necessary provide a narrative to describe derivation of labor rates, use of uncompensated overtime, pools to which indirect rates are applied, historical /provisional billing rates for indirect rates for the last 3 years and description, and amount of proposed other direct costs. Additionally, provide:

(h) Reasonableness and Consistency between the Technical and Price/Cost Volumes. Demonstrate that the unit prices and the total proposed price/cost are reasonable, realistic, and commensurate with the work required by the solicitation and the technical and management approaches identified in the Technical Volume of the proposal. Show traceability with the CLINS and PWS, proposed effort, proposed manning levels, and the prices/costs. Refer to specific sections in the Technical Volume as needed to illustrate the consistency between the Price/Cost Volume and the Technical Volume. The Offeror shall explain any inconsistency between promised performance and price/cost, as well as any appearance of unbalanced pricing, in the proposal.

(i) Subcontracting Plan. The Offeror shall submit its subcontracting plan with proposals, as applicable.

(a) Strategies for using Small Business (SB) Concerns. Offeror shall address their strategies for utilizing SB concerns in the performance of this contract, whether as a joint venture, teaming arrangement or subcontractor.