EASR_Solicitation_Amendment_05.pdf

N0002415NR42027

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect

15A. NAME AND TITLE OF SIGNER (Type or print)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83)

Prescribed by GSA

FAR (48 CFR) 53.243

The purpose of this amendment is to correct the proposal validity date and the destruction of solicitation materials date.

1 CONTRACT ID CODE PAGE OF PAGES

L 1 45

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY 15-Oct-2015

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X N00024-15-R-5370

X 9B. DATED (SEE ITEM 11)

14-Aug-2015

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14 The hour and date specified for receipt of Offer is extended, X is not extended

Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing Items 8 and 15, and returning 2 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers FAILURE OF YOUR ACKNOWLEDGMENT TO BE

RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN

REJECTION OF YOUR OFFER If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE

CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

2 AMENDMENT/MODIFICATION NO 5 PROJECT NO (If applicable)

6 ISSUED BY

3 EFFECTIVE DATE

15-Oct-2015

CODE

NAVAL SEA SYSTEMS COMMAND (HQ)

1333 ISAAC HULL AVE SE

WASH NGTON NAVY YARD DC 20376-2011

N00024 7 ADMINISTERED BY (If other than item 6)

4 REQUISITION/PURCHASE REQ NO

CODE

See Item 6

FACILITY CODECODE

EMA L:TEL:

N00024-15-R-5370

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

SECTION L

PERSONNEL AND FACILITY SECURITY CLEARANCE REQUIREMENTS

(1) This program will require access and utilization of classified information that is Collateral and/or

Compartmented at the CONFIDENTIAL, SECRET OR TOP SECRET security level. However, classified information that is classified above Collateral SECRET security level SHALL NOT be included in the Offeror’s proposal submission. The security classification of this procurement is specified in the Contract Security

Classification specification, DD Form 254, attached hereto.

(2) In order to be awarded a contract the Offeror shall meet the minimum security criteria:

(a) The Offeror shall be a United States Contractor, licensed, chartered, or incorporated in the United

States. If the contractor is under foreign ownership, control or interest (FOCI), the contractor is not eligible for a facility security clearance until the FOCI factors have been favorably resolved through mitigation. Special Security

Agreement (SSA), Proxy Agreement (PA) or Voting Trust Agreement (VTA) is used to mitigate FOCI cases where companies are effectively owned or controlled by a foreign entity.

(b) The Offeror shall possess a facility security clearance issued by the Defense Security Service (DSS) at the TOP SECRET level and meeting the Director of Central Intelligence Directive (DCID) 6/9 security requirements by time of award.

(c) The Offeror shall possess an accredited Sensitive Compartmented Information Facility (SCIF). The

Offeror may elect to rent from another Contractor in order to fulfill this requirement. If so, the Offeror must provide written evidence of the rental agreement. If the Offeror’s SCIF is utilized for performance of contracts on behalf of other agencies of the Federal Government (non Department of Defense), the Offeror must provide written evidence that the other agency/agencies will sign a Memorandum of Agreement as specified in Defense Intelligence Agency

Manual (DIAM) 50-5 to allow the Offeror to utilize the SCIF for performance of the contract.

(d) The above security related responsibility qualification criteria are the only security criteria pertaining to this RFP and are subject to a “Pass/Fail” evaluation as described in Section M of this RFP.

GENERAL

The purpose of this solicitation is to obtain competitive proposals for the Enterprise Air Surveillance Radar (EASR)

Engineering and Manufacturing Development phase and initial Production for up to 16 production systems. The objective of the EMD phase is to complete the engineering necessary to develop an EASR Engineering

Development Model (EDM) and complete all testing necessary to validate the requirements. Additionally this solicitation will obtain options for up to 16 production systems.

Proposals submitted in response to the Request for Proposal (RFP) must contain a complete description of all pertinent aspects of the effort proposed by the Offeror. Offerors shall not assume that previously submitted data or prior experience presumed to be known to the Government (e.g., previous projects performed for the Government) will be considered as part of the proposal.

The proposal must be sufficiently detailed and complete to demonstrate an understanding of and the ability to comply with the requirements of this RFP. The proposal shall demonstrate such understanding and ability in a concise, logical manner, and shall not contain superfluous material that is not directly related to this acquisition.

Technical sections of the proposal shall demonstrate the Offeror’s thorough comprehension of the EASR mission, requirements, functions, and required capabilities. General statements such as that the Offeror: “can or will comply with the requirements,” “standard procedures will be used,” “well known techniques will be used,” or statements that paraphrase the Statement of Work (SOW) for the EASR Engineering and Manufacturing Development and initial Production (hereafter referred to as the SOW), the EASR Systems Requirements Document (SRD) (hereafter referred to as the SRD) in whole or in part will not demonstrate or constitute compliance with these requirements concerning the content of the technical proposals. Discussions of each topic in the proposal shall exhibit continuity and logical progression. Failure to conform to the requirements of this RFP may form the basis to reject the proposal.

Although the overall quality of the proposal in terms of clarity, completeness and conciseness will be evaluated;

brochuremanship is not desired. A concise, legible, neat, orderly and comprehensive proposal is required. Elaborate brochures, artwork, expensive paper and bindings, or expensive visual or other presentation aids beyond those sufficient to present a complete and comprehensive written proposal are unnecessary. Clarity is essential. The use of brochures shall be minimized and if used will be included in the page count.

The amount of detail to be presented in response to each section of the outline presented herein is left to the discretion of the Offeror, but information must be presented in the order specified and in s sufficient depth for the

Government to make a comprehensive evaluation of the Offeror’s understanding of and capability to meet the requirements of this RFP. Each volume of the proposal shall be self contained. Data shall be organized to enable

Government personnel to thoroughly evaluate the proposal against specific factors established in Section M.

Please note that pursuant to FAR 52.215-1, the Government intends to award a contract on the basis of proposal submission without conducting discussions with Offerors, but reserves the right to conduct discussions in accordance with FAR 15.306 if determined by the Contracting Officer to be necessary [see paragraph (4) of FAR

52.215-1(f)]. Each Offeror shall submit only one proposal. No alternate proposals will be accepted. Therefore, the

Offeror’s proposal submissions shall contain the Offeror’s best terms from a price and technical standpoint.

However, the Government may contact any or all or a limited number of Offerors with questions concerning their proposals as permitted under FAR Part 15. The Government reserves the right to conduct discussions if the

Procuring Contracting Officer determines them to be necessary. At the end of discussions, if they occur, the

Government will request Final Proposal Revisions (FPRs) from all Offerors still within the competitive range. Each

Offeror is required to complete Attachments L-C and L-D in their entirety and provide them along with the proposal submission in the Price Volume VII.

The Procuring Contracting Officer is the sole point of contact for this acquisition; however, the following Contract

Specialist may be designated to contact Industry on the Procuring Contracting Officer’s behalf: Sheila Utz, sheila.utz1@navy mil

FORMAT AND COMPOSITION FOR EACH SUBMITTAL

VOLUME TITLE PAGE LIMIT COPIES

I Executive Summary 5 2 Digital Versatile Disc (DVD)*

An original hard copy and 3 Paper Copies

II Technical Proposal 350 2 DVD

An original hard copy and 4 Paper Copies

III Data Rights Proposal 10 2 DVD *

IV Management Proposal 40 2 DVD *

V Past Performance See Volume 2 DVD

Description An original hard copy and 2 Paper Copies

VI Energy Proposal 5 2 DVD *

VII Price Proposal None 2 DVD

An original hard copy and 2 Paper Copies

*Submit Volumes on a single DVD if possible.

Paper copies of the proposal shall be divided into seven (7) volumes, subject to the number of copies indicated above. In presenting material in these volumes, the Offeror is advised that the quality of information is significantly more important than quantity. In this respect, the page limitation must be strictly observed. Pages in excess of the applicable page limit shall not be read or evaluated, and will be removed by the Procuring Contracting Officer from the back of the respective volume prior to evaluation. It is not necessary to supply the maximum number of pages allowed for each volume; fewer pages may be submitted. Index pages and tabs are required and shall be cross referenced to the table of contents. All pages subject to page limits of volumes I, III, and IV and all pages within volumes V, VI, and VII shall be consecutively numbered within each volume (e.g., 1,2,3....).

Information requested in the paragraphs below shall be provided in the volumes indicated. If additional information is provided in other sections, reference shall be made to those sections where this information can be found.

All information relating to contract cost or pricing data shall be included only in the section of the proposal designated by the Government as the Price Proposal Volume (Volume VII). UNDER NO CIRCUMSTANCES

SHALL CONTRACT COST AND PRICING DATA BE INCLUDED IN VOLUMES I THROUGH VI. In the event that cost and pricing data is included in Volumes I through VI, the page that has the cost or pricing data shall be removed to include any page attached to the page containing the cost or pricing data.

In the event that any portion of the technical proposal is written by someone who is not an employee of the Offeror submitting the proposal, a certificate to this effect shall be signed by a responsible officer of the Offeror and shall show the person's name, employment capacity, the name of this person's firm, the relationship of the firm to the

Offeror's, and the portion of the technical proposal written by that person.

The following firms may assist in the proposal evaluation process in an advisory capacity. The Government may also employ administrative and engineering support services contractors in the handling of solicitation documentation for purposes of security and document control. All such personnel will be required to execute a statement to preserve and protect from disclosure any source selection and contractor proprietary information disclosed to them during the course of these evaluations. It is anticipated that the following firms will assist:

a. The Johns Hopkins University Applied Physics Laboratory (JHU/APL)

b. David P. Maunder Consulting Services, Inc. (DPMC)

c. Technology Service Corporation (TSC)

d. Systems Planning and Analysis, Inc. (SPA)

e. Innovative Concepts Engineering (ICE)

f. United Research Services (URS)

g. Technomics

h. California Analysis Center Inc. (CACI)

i. Tech-Marine Business Inc.

If an Offeror has concerns with the firms listed above assisting during the evaluation process, please advise the PCO in writing no later than 10 days after receipt of the RFP.

Submission of an offer under this solicitation will constitute a grant of authority by the submitting company to the

Government to allow access by individuals of these firms to any source selection information and information that may constitute material within the ambit of the Trade Secrets Act, 18 U.S.C. § 1905. These individuals will be performing under Government contracts that contain appropriate restrictions on the use and disclosure of information provided to the contractors (e.g., non-disclosure requirements) or will have executed Government disclosure agreements that are intended to ensure that the individuals under these contracts handle the information properly and in accordance with applicable law and regulation.

Accordingly, all proposal volumes shall be separately bound in standard size three ring binders (O-Ring or D-Ring are acceptable) with ring size no greater than 4”. Only material in these binders will be evaluated. All Classified volumes shall also be two (2) hole punched on the top of each page. Only material in these binders will be evaluated. The technical and cost volumes of the proposal will contain a number of individual parts. These may be bound separately but shall be labeled with the appropriate volume information.

Page Size and Format

The following guidance shall be followed unless specific guidance is provided under each volume.

The narrative material in each proposal shall be single spaced, typed or printed in Times New Roman font with type no smaller than 12-point font. Paper, excluding foldouts, shall be 8 1/2 X 11 inches (standard size) with a minimum margin of 1 inch around the page. Any type contained on graphics pages shall not be smaller than 8-point font.

Electronic proposal submissions and supporting information shall be submitted on DVD suitable for reading in a standard PC compatible DVD drive. All files shall be compatible with Microsoft Office 2010. All view graphs shall be in Microsoft PowerPoint. All spreadsheets shall be in Microsoft Excel format such that each mathematical equation utilized for calculations is visible and working. All text shall be in Microsoft Word. All schedules shall be in Microsoft Project. No fields shall be password protected. Offerors shall not embed sound or video files into the electronic files. The DVDs shall be labeled to indicate the Offeror’s name, the solicitation number and associated volume numbers. The Offeror shall screen all DVDs for computer viruses prior to submittal.

Information shall be presented on single sided pages (a double sided page will count as two pages) only and in a single column on each page. Each volume shall contain a glossary of abbreviations used, with an explanation of each. The information and format of the proposal shall be identical on electronic copies, DVD, and hard copy submissions. If there is a discrepancy between the hardcopy submission and the electronic copy or DVD, the electronic submission shall take precedence.

Foldouts. Foldouts may be used for charts and graphs where necessary to depict organization, layout or implementation schedules. Extensive written text or tabular data, beyond that reasonably required for clarity shall not be included in the material presented on the foldout sheet. Foldout pages shall fold entirely within the volume and shall be limited in size to no more than two (2) standard size pages. Each foldout shall contain printed material on only one side of the foldout. Foldouts for the entire proposal are limited to a total of fifty (50). Foldouts for the

Integrated Master Schedule, Section J, Attachment J-18 SLOC Table and Price Volume Cost Tables, Section L, Attachments L-G through L-N do not count against the fifty (50) foldout page limit. A Foldout page will count as two (2) standard sized pages. The maximum number of foldouts for the executive summary volume is one (1).

Cover Letter. The proposal shall be accompanied by a cover letter prepared on the company's letterhead stationery.

The cover letter shall also state that the proposal is valid for 270 days, identify the Offeror’s Cage Code; DUNS

Number; all enclosures being transmitted; state the facility’s level of approved security clearance; clearance level of storage capability; address of the cognizant security office, name of the security representative, and address(es) of the location(s) at which the Offeror intends to perform the proposed effort including subcontractors. The cover letter is not subject to the page limits and the Government will review it to make sure it contains the preceding information. The cover letter shall be submitted with the Price Volume.

PROPOSAL CLASSIFICATION

If the Technical Volume contains classified information, it shall be classified no higher than COLLATERAL

SECRET and bound in a red binder if Secret or blue binder if Confidential. No unclassified volume will be bound in a red or blue binder. Specific pages and paragraphs that contain proprietary information shall be indicated.

Classification markings shall be in accordance with the Radar General Security Classification Guide (SCG).

Further guidance is provided by the DD Form 254 (Attachment J- 04) and the DoD 5220.22M NISPOM.

Classified pages will count against the page limits and format restrictions previously defined.

SUMMARY

Each Offeror shall submit an offer/proposal and other written information in strict accordance with these instructions.

When evaluating an offer, the Government will consider how well the Offeror complied with these instructions. The

Government will consider any failure on the part of an Offeror to comply with these instructions to be an indication of how the contractor will comply with contract requirements during contract performance. Therefore, the

Government encourages Offerors to contact the Contract Specialist via e-mail with copy to the PCO in order to request an explanation of any aspect of these instructions for which the offeror needs clarification/guidance.

Because National Security is involved, the PCO may request the cognizant security office to verify any or all security information for an Offeror at any time prior to award. Such verification shall not be deemed to be

“discussions” and shall in no case allow an Offeror to revise or change its proposal.

There may be an acknowledged companion contract at a higher security classification which will be issued under a separate RFP. Any resulting award from this solicitation is not a promise or a guarantee of an award of a companion contract.

Attachment J-06 provides the WBS and data dictionary, and it shall be utilized by the Offeror for the costing of the offer/proposal as well as the basis for the creation of the contractor WBS. Attachment J-15 provides the Cost and

Software Data Reporting (CSDR) plan template to be utilized per the SOW.

SUBMISSION OF PROPOSALS: NAVSEA will not accept electronic submission of proposals. All copies of the proposal (Volumes I through VII) shall be submitted to the PCO or Contract Specialist at the address below by

11:00 a m. local time for the Naval Sea Systems Command on the proposal due dates:

Commander, Naval Sea Systems Command

Department of the Navy

ATTN: John N. Butto, SEA02532

1333 ISAAC HULL AVENUE SE, MS2040, Bldg. 197, Room 5W-1740

WASHINGTON NAVY YARD, DC 20376

Hand carried offers shall be delivered by carrier to: (See HQ L-2-0013 SPECIAL PROPOSAL RECEIPT

REQUIREMENTS (NAVSEA) (SEP 2009) (MODIFIED) (JAN 2013) for special instructions)

Unsuccessful Offeror(s) shall destroy all Government furnished solicitation materials associated with this RFP within 180 calendar days of award.

WRITTEN QUESTIONS

NOTE: Offerors may submit written questions requesting clarification of RFP requirements via electronic mail to the following addresses: john.butto@navy mil and sheila.utz1@navy mil. It is requested that all questions be received by September 25, 2015 to allow the Government adequate time to prepare and issue responses to all

Offerors prior to the date and time set for receipt of proposals. Questions concerning classified attachments shall be submitted in accordance with the DD Form 254 and the DoD 5220.22M NISPOM.

The Navy will continue to accept questions up to the closing time of the solicitation; however, time may not permit responses to questions received after September 25, 2015. Only written questions will receive a response. Offerors’ questions must be submitted utilizing Attachment L-A to this RFP. For ease of Government review and to reduce time, Offerors must submit this form in a Word format and not in a Portable Document Format (PDF). It is the

Government’s intention that questions and responses will be distributed to all Offerors via RFP amendment(s). Information provided with each question shall include the document name, document date, specific page, paragraph, clause or other definitive citation requiring clarification as per Attachment L-A. All questions shall be directed to the e-mail addresses referenced above. NAVSEA will answer all questions (publishing both the question and the answer) via Federal Business Opportunities (FBO) at http://www fbo.gov. Questions and answers can be accessed via fbo.gov by following the link “Opportunities” and entering keyword/solicitation # for “N00024-

15-R-5370” in the box. Company-specific information will be omitted from all questions and answers.

EXECUTIVE SUMMARY - VOLUME I

The Executive Summary Volume shall be limited to five (5) pages. Title Pages, cover pages, glossaries, tabbed dividers, and table of contents shall not be subject to the page limitations, will not be evaluated, and shall not be numbered.

The Executive Summary Volume shall summarize the Offeror’s planned approach to satisfy the Government’s requirements. Key elements of the proposal shall be highlighted for both technical and management perspective.

The Executive Summary Volume shall be unclassified. The Executive Summary Volume will not be formally evaluated and will not be incorporated as part of the contract awarded to the successful Offeror. Price information shall be completely omitted from the Executive Summary Volume.

Proposal Cross Reference Matrix - The Offeror shall provide a cross reference matrix that maps Section M of the

RFP criteria to the SOW section(s) and the applicable section(s) of the Offeror’s proposal. If this matrix conflicts with any other portion of this solicitation, such other reference shall take precedence over this matrix. A cross reference matrix to the Evaluation Criteria of Section M is for informational purposes only and should not be relied upon as evidence that such Criteria have, in fact, been satisfied. In addition, this matrix does not limit the

Government review to the cited RFP and proposal locations for any given evaluation factor. The Government will evaluate the proposal as a whole. This matrix does not count toward the Executive Summary Volume page count limit.

TECHNICAL PROPOSAL - VOLUME II (TECHNICAL FACTOR)

Technical Proposal Volume shall enable technical/engineering personnel to make a thorough evaluation and arrive at a sound determination of whether or not the proposal meets the requirements of the RFP. To this end, the

Technical Proposal Volume shall be specific, detailed, and complete. Proposals shall include the block diagrams, flow diagrams, sketches, drawings, schematics, and interface descriptions required to describe the Offeror's proposed concept. Integrated Master Schedule (IMS) shall be created and submitted using Microsoft Project 2010.

The technical section must be sufficient to show how the Offeror proposes to comply with the Government's requirements and include a full explanation of the methodology and procedures to be followed. Technical Proposal sections, as detailed below, shall include details of the differences between the proposed Variant 1 and Variant 2

EASR systems where applicable.

The Technical Proposal Volume shall be limited to the page count as identified above. Pages in excess of the page limit will not be read or evaluated. Title Pages, cover pages, glossaries, tabbed dividers, and table of contents shall not be subject to the page limitations, will not be evaluated, and shall not be numbered. Price information shall be completely omitted from the Technical Proposal Volume. If price or cost information is found on any page(s) within the Technical Proposal, the entire page(s) to include any attached page(s) will be removed and will not be evaluated. Price and cost information includes the mention of any dollar values associated with capital investment, expenditures, etc. The following is an outline of the information required to be addressed in the Technical Volume:

Title page

Table of contents (including Figures, Tables, and Appendices)

Glossary of acronyms and abbreviations

Part 1 – EASR System Architecture, Development, Integration, and Maturity

1.0 Introduction

2.0 Technical Proposal Content

2.1 EASR System Design and Integration

2.1.1 Requirements

2.1.1.1 System Requirements Documentation

2.1.1.2 Assessment of Technical Performance Measures (TPMs)

2.1.2 System Design

2.1.3 Multimission Design

2.1.4 Electromagnetic Interoperability CONOPS

2.1.5 EMD and Production Schedules

2.1.6 Integration and System Performance Verification Approach and Plans

2.1.6.1 Ship Integration Approach

2.1.6.2 Combat System Integration Approach

2.1.6.3 EASR System Testing

2.1.6.3.1 System/Subsystem Testing

2.1.6.3.2 Land Based Test Site (LBTS) Testing

2.1.6.4 Environmental Qualification Plan

2.1.6.5 Modeling and Simulation Plan

2.1.6.6 Anti-Tamper Implementation Plan

2.2 EASR Hardware Architecture and Development

2.2.1 EASR Hardware Description

2.2.1.1 Antenna Subsystems

2.2.1.2 Other Subsystems

2.2.1.3 System Calibration Approach

2.2.2 EASR HM&E Interfaces

2.2.3 EMD and Production Manufacturing

2.2.3.1 EMD Manufacturing

2.2.3.2 Production Manufacturing

2.3 EASR Software Architecture and Development

2.3.1 Detailed Software Description

2.3.2 Key Architectural Products

2.3.3 Algorithm Mapping

2.3.4 Signal Processing Software

2.3.5 Software Development Approach and Plans

2.3.6 External Configuration Items and Maintenance Manual Development

2.4 Life Cycle Support Concept

2.5 Open Architecture Concept

Appendix A to Volume II Part 1 – Software Development Plan

Part 2 – Redacted Bases of Estimates (Electronic Submittal Only)

The following provides a description of the information required to be addressed in the Technical Volume:

Part 1 – EASR System Architecture, Development, Integration, and Maturity (350 pages)

Title page

Table of contents (including Figures, Tables, and Appendices)

Glossary of acronyms and abbreviations

1.0 Introduction

Provide a short narrative description of the Offeror’s technical approach.

2.0 Technical Proposal Content

2.1 EASR System Design and Integration

2.1.1 Requirements

2.1.1.1 System Requirements Documentation

The Offeror shall provide a detailed discussion of system requirements including all mission level requirements, all driving requirements and all functional requirements deemed significant to the architecture and design for the EASR. The Offeror shall provide information to demonstrate the maturity of the proposed system design. The Offeror shall include discussion of previously developed systems leveraged in the Offeror’s design and include a description of the changes required for EASR. The Offeror shall provide a preliminary EASR A-

Specification (using System/Subsystem Specification (SSS), DI-IPSC-81431A) based upon the EASR SRD. The A-

Specification shall include a flowdown matrix of requirements from the EASR SRD. The A-Specification will not count against the total page count of Part 1 of the Technical Proposal. A compliance matrix showing compliance to all requirements contained in the EASR SRD shall be provided. The compliance matrix shall include a column that provides the predicted value that will be achieved by the Offeror’s proposed system for each requirement, a column describing the basis for the predicted value, and a column indicating any margin in excess of the stated requirement.

This compliance matrix will not count against the total page count as part of the Technical Proposal.

For requirements specified in terms of dB in the EASR SRD the Offeror shall provide risk mitigation plans for margins less than 1 dB. For requirements specified as percentages at or higher than 0.95 in the EASR SRD, the

Offeror shall provide risk mitigation plans when margin M <= 0.2, where

M = (Vp-Vr) / ((1-Vr)^2)

Vp = predicted percentage as a decimal value (e.g. 0.98), and

Vr = required percentage as a decimal value.

For requirements specified as percentages at or lower than 0.05 in the EASR SRD, the Offeror shall provide risk mitigation plans when margin M <= 0.2, where

M = (Vr-Vp) / (Vr^2)

Vp = predicted percentage as a decimal value (e.g. 0.98), and

Vr = required percentage as a decimal value.

For requirements with values of 1dB or less in the EASR SRD, the Offeror shall provide risk mitigation plans for margins less than 0.25 dB. For all other requirements in the EASR SRD, the Offeror shall provide risk mitigation plans for margins less than 5%. In addition, the Offeror shall provide a risk mitigation plan for any cases which the

Offeror deems marginal.

2.1.1.2 Assessment of Technical Performance Measures (TPMs)

The Offeror shall provide an assessment of system performance against the Technical Performance

Measures (TPMs) described in Attachment J-21. Applicable “shall” numbers included in Attachment J-21 are referenced to the EASR SRD. Each assessment must include a clear description for the basis of the assessment, e.g.

simulated, modeled, predicted, measured, etc. In addition to the assessment, the Offeror shall provide the threshold value for the TPM, a flowdown of the associated requirements to B-Specifications and budgets, and any additional justification necessary to support its assessment.

2.1.2 System Design

The Offeror shall provide a description of their system design including architecture and interfaces for each mission area (AAW, SuW, Air Traffic Control (ATC), and Electronic Protection) as applicable for each area listed below. The Offeror shall describe each of the major drivers to the radar development. The Offeror shall describe the physical implementation of the major hardware elements.

a. Overall Concept of Operations

b. Blake sheets

c. Loss Budgets

d. Waveforms

e. Beam Lattice

f. Update rates

g. Key Algorithms

1. Signal Processing

2. Tracking

3. EP Logic

2.1.3 Multi-Function Design

The Offeror shall provide a description of the multi-function design. The description shall address:

a. Overall Concept of Operations

b. The compatibility of function area designs

c. Resource management and scheduling design

d. Key proposed algorithms

e. Graceful degradation in overload conditions

f. Approach for addressing combat system driven tasking and prioritization approach

2.1.4 Electromagnetic Interoperability CONOPS

The Offeror shall provide a description of the design features, algorithms and other methods used to ensure

Electromagnetic Interoperability with other sea and land based assets identified in the EASR SRD. The effect of these assets on the Offeror’s proposed system and vice versa shall be described.

2.1.5 EMD and Production Schedules

The Offeror shall provide an EMD schedule from contract award to completion. The Offeror may reference the Integrated Master Schedule provided as Appendix B to Volume IV. The schedule shall clearly identify activity for each subsystem including at a minimum transition to production activities, assembly, test, and delivery.

Critical Paths shall be identified. If referenced, the IMS will not count against the Technical Volume page count.

The Offeror shall provide a Production schedule from option exercised to completion. The Offeror may reference the Integrated Master Schedule provided as Appendix B to Volume IV. The schedule shall clearly identify activity for each subsystem including at a minimum transition to production activities, assembly, test, and delivery.

Critical Paths shall be identified. If referenced, the IMS will not count against the Technical Volume page count.

2.1.6 Integration and System Performance Verification Approach and Plans

2.1.6.1 Ship Integration Approach

The Offeror shall discuss the approach that will be followed for integration of the EASR into the ship systems. The Offeror shall discuss the integration of the mechanical, electrical, and cooling interfaces. The Offeror shall discuss any special considerations that will be required in order to complete this integration. The Offeror shall discuss any risks that have been identified with this integration.

2.1.6.2 Combat System Integration Approach

The Offeror shall discuss the approach that will be followed for integration of EASR with the Combat

System, Air Traffic Control, and CEC. The Offeror shall discuss the use of simulation or emulations necessary.

The Offeror shall discuss any risks that have been identified with this integration.

2.1.6.3 EASR Radar System Testing

2.1.6.3.1 System/Subsystem Testing

The Offeror shall describe the testing that will be conducted to demonstrate the individual system component performance and software/firmware/hardware readiness for systems integration and test. This description shall cover test events, facilities, and assumptions required to satisfy all test objectives.

2.1.6.3.2 Land Based Test Site (LBTS) Testing

The Offeror shall describe the testing that will be conducted to demonstrate the system performance and software/firmware/ hardware readiness for systems testing at SCSC. This description shall cover test events, facilities, and assumptions required to satisfy all test objectives. The Offeror shall describe the integration testing for the EASR.

2.1.6.4 Environmental Qualification Plan

The Offeror shall describe the plan for environmental qualification testing that will be performed to verify all man-made, and natural shipboard environmental requirements contained in the EASR SRD. The Offeror shall identify which subsystems/CIs (including both off and on array equipment) will be used to verify each requirement and in which test phase (e.g. System/subsystem testing, LBTS, Production FAQT, Production FAT) each requirement will be verified. The Offeror shall identify the level of testing/analysis to be performed for each of the radar subsystems/CIs.

2.1.6.5 Modeling and Simulation Plan

The Offeror shall describe the plan for meeting the M&S requirements as identified in the SOW. A summary of the M&S plan shall be provided including M&S strategy at the radar and combat system/ATC integration level, the M&S capability required to support all design and I&T phases, the current state of the

Offeror’s M&S capabilities and development plans to achieve the required M&S capabilities, and the proposed

VV&A activities to gain acceptance of the Offeror’s M&S. Any model or simulation that has less than Government

Purpose Rights shall be identified.

2.1.6.6 Anti-Tamper Implementation Plan

The Offeror shall describe the plan for meeting the Anti-Tamper requirements as identified in the SRD and

SOW.

2.2 EASR Hardware Architecture and Development

2.2.1 EASR Hardware Description

The Offeror shall provide a detailed description of the EASR hardware design. This description shall include the allocation of system requirements to hardware requirements. The Offeror’s allocation shall demonstrate that the proposed hardware will meet system requirements. The Offeror shall include a clear description for the basis of the assessment (e.g. simulated, modeled, predicted, measured, etc) and include margin. The Offeror shall provide information to demonstrate the maturity of the proposed hardware. The Offeror shall include discussion of past hardware developed by the Offeror that is mature and of similar performance to that needed for EASR. In addition, the discussion shall include any additional development and/or changes required for EASR.

2.2.1.1 Antenna Subsystems

The Offeror shall provide a detailed discussion of all aspects of the proposed antenna design. At a minimum, the detailed discussion shall include allocated requirements, a description of the architecture, hardware maturity, and performance projections for the overall antenna as well as the following antenna subsystems:

a. Radome

b. Radiator

c. Transmit & Receive Module(s)

d. Beamforming

e. Beam Steering

f. Power System

g. Cooling System

g. Receiver

h. Exciter

i. Physical Characteristics and Packaging

j. Pedestal and Rotating Mechanism (Variant 1 Only).

2.2.1.2 Other Subsystems

The Offeror shall provide a detailed discussion of all aspects of other subsystems that includes at a minimum a comprehensive system design description, requirements, and performance projections.

2.2.1.3 System Calibration Approach

The Offeror shall provide a detailed description, requirements, and performance projections of the System

Calibration approaches:

a. Array Calibration

b. Receiver/Exciter Calibration and Synchronization

c. Reference Target RCS Calibration

d. Time Sidelobe Calibration

e. Sensor Registration Approach.

2.2.2 EASR HM&E Interfaces

The Offeror shall describe each of the interfaces to the ship systems (Size, Weight, Power, Mechanical, Cooling both liquid and air) at the system and sub-system level. Any special requirements relative to the ship design shall be included.

2.2.3 EMD and Production Manufacturing

2.2.3.1 EMD Manufacturing

The Offeror shall describe the manufacturing and manufacturing processes necessary to build the EASR

EDM. Describe any special testing. Describe special test fixtures. Describe planned EMD activities to support manufacturing readiness assessment including pilot process/line development, proof of manufacturing units, and transition to production activities. Describe the process of assembling the antenna. Describe the manufacturing aspects of maintaining the EDM system. The Offeror shall include a EMD Long Lead Material List that must be procured prior to Hardware CDR. The list shall include a description and required ordering date for each item.

2.2.3.2 Production Manufacturing

The Offeror shall describe the manufacturing and manufacturing processes necessary to build the EASR

Production units. Describe any additional efforts, test fixtures, special testing, manufacturing capability, and assembly processes that are different from EDM manufacturing. Describe planned Production activities to support manufacturing readiness assessment including pilot process development, proof of manufacturing, and transition to production activities.

2.3 EASR Software Architecture and Development

2.3.1 Detailed Software Description

The Offeror shall provide a description of the overall EASR software concept, including architecture and, interfaces. The Offeror shall describe each of the major drivers to the radar software development. The Offeror shall describe the partitioning of the software elements including the interfaces between each element. This description shall discuss the adequacy of the software design in meeting the allocated requirements. In addition, the

Offeror shall provide a detailed description of the following functions:

a. Local Track Management,

b. Composite Track Management,

c. Resource Management/Scheduling,

d. Electronic Protection,

e. Signal processing, and

f. Data processing.

The Offeror shall provide information to demonstrate the maturity of the proposed software. The Offeror shall include discussion of previously developed software leveraged in the Offeror’s design and include a description of the changes required for EASR.

2.3.2 Key Architectural Products

The Offeror shall provide a description of the process utilized to capture the system design into the software designs to the element level. A discussion of the activity and sequence diagrams shall be included.

2.3.3 Algorithm Mapping

The Offeror shall provide a detailed mapping of the functions to the software elements. The Offeror shall identify its proposed key algorithms. The Offeror shall describe its key algorithms including any benchmarks and modeling results.

2.3.4 Signal Processing Software

The Offeror shall provide a description of the proposed Signal Processing Software. This includes a description of algorithms, algorithm performance, benchmarking results and extrapolation/relevance to the tactical design. The

Offeror shall provide a description of work required in EMD to demonstrate this capability in the tactical software environment.

2.3.5 Software Development Approach and Plans

The Offeror shall provide a proposed Software Development Plan (SDP) and processes to be implemented.

This proposed SDP will form the basis for a completed SDP to be delivered after contract award as a CDRL deliverable subject to government review and approval. The SDP shall be provided as Appendix A to Technical

Volume Part I and will not count against the Technical Volume and Technical Volume Part I page limits. The information content of the SDPs shall follow the framework of IEEE/EIA Standard 12207 regarding subject content, level of detail, and completeness. Discuss how the software engineering function will be integrated with the system engineering functions. Discuss the approach that will be used to provide a seamless and efficient flow of information between the system engineers and the software engineers. Summarize software challenges of the EASR. The

Offeror shall include an SDP Rationale which describes why the specific approach defined in the SDP is appropriate for the EASR system. This rationale shall address at a minimum OA, assurances (systems, software, information), and prospective Critical Program Information (CPI) with current protection rationale.

The Offeror shall provide a build and I&T strategy and schedule that shows how and when key functionality is demonstrated.

The Offeror shall provide Source Line of Code (SLOC) estimates showing new/modified/reused code along with justification for the underlying assumptions. The Offeror shall categorize its SLOC estimates in accordance with the definitions provided in Attachment J-18.

The Offeror shall provide a plan for long term software sustainment.

The Offeror shall address configurability and adaptability of the software architecture and algorithms.

2.3.6 External Configuration Items and Maintenance Manual Development

The Offeror shall provide a description of the proposed concept for the External CIs and Maintenance

Manual that will be developed. The Offeror shall describe the approach for developing the requirements for the

External CIs and Maintenance Manual A and B Specifications and obtaining government concurrence. The Offeror shall describe the approach for developing the software. The Offeror shall describe the proposed test program to validate these requirements. The Offeror shall discuss the interaction necessary with the combat system elements in support of this development. Refer to the SOW for definitions of the External CIs and Maintenance Manual.

2.4 Life Cycle Support Concept

The Offeror shall discuss the concept that will be followed to meet the RM&A requirements identified in the SRD. The Offeror shall discuss the design features in the system architecture that support the RM&A requirements. The Offeror shall identify the life cycle support philosophy, including FD/FI Approach, Maintenance

Tempo, Reliability Growth, and Sustainment. The Offeror shall discuss the approach to minimize Total Ownership

Cost (TOC). The Offeror shall not include cost information in addressing its TOC approach.

2.5 Open Architecture Concept

The Offeror shall describe the proposed approach to implementing open architecture. The Offeror shall summarize the Open Systems Management Plan. The Offeror shall describe its approach for minimizing inter-component dependencies, reuse philosophy, and overall functional partitioning. The Offeror shall describe the extent to which its proposed hardware and software is modular and can be upgraded, scaled, or otherwise modified to provide future growth capability.

As a demonstration of the proposed systems’ modularity and openness, the Offeror shall describe the proposed approach to maintaining common components for the two Variants specified in the EASR SRD.

Part 2 – Redacted Bases of Estimates (BOEs) (Electronic Submittal Only)

The Offeror and its major subcontractors (as defined as subcontractors equal to or greater than $15 million in CLIN

0001 or equal to or greater than $12.5 million in any single LLM, Production or First Article CLIN/SLIN and hereinafter referred to as “major subcontractor”) shall submit its BOEs with all cost information redacted for CLINs

0001, 0303, 0304, 0401AA, 0401AB, 0402AA, 0402AB, 0402AC, 0402AD, 0403, 0404AA, 0404AB, 0407, 0408, 0501, 0502AA, 0502AB, 0503, 0504AA, 0504AB, 0601, 0602AA, 0602AB, 0701, 0702AA, 0702AB, 0703, 0704AA, 0704AB, 0801, 0802AA, and 0802AB.

DATA RIGHTS PROPOSAL – VOLUME III (DATA RIGHTS FACTOR)

The Data Rights Volume shall define how the Offeror will offer data rights for the work required by this solicitation.

It shall describe in detail the proposed rights for hardware, software, and interfaces to be developed as required by this solicitation. The Data Rights Volume shall be limited to 10 pages. Price information shall be completely omitted from the Data Rights Proposal Volume.

1.0 DATA RIGHTS PROPOSAL SUMMARY

1.1 Introduction

2.0 DATA RIGHTS

2.1 Non-Commercial Data Rights

2.2 Commercial Data Rights

1.0 DATA RIGHTS PROPOSAL SUMMARY

It is the Government’s intent and goal that all non-commercial technical data (TD) and computer software/computer software documentation (CS/CSD), other than TD, CS, and CSD developed at Government expense, be delivered with Government Purpose Rights. If such non-commercial TD/CS/CSD contains elements generated previously with Offeror’s own capital, it is the Government’s goal that the TD/CS/CSD be delivered with a minimum of Government Purpose Rights (as defined in DFARS 252.227-7013 and -7014). If the Offeror proposes to deliver commercial TD/CS/CSD, it is the Government’s desire to obtain a license to the commercial TD/CS/CSD that would grant the Government the equivalent of Government Purpose Rights. In the event an Offeror proposes to deliver any commercial or non-commercial TD/CS/CSD with less than such rights, the Government will evaluate the adverse impact on the Government’s ability to use, modify, release, or disclose such TD, CS, or CSD. The Data

Rights offered (7017 list, 7028 list , and/or Supplemental Information—Noncommercial Technical Data, Noncommercial Computer Software, Noncommercial Computer Software Documentation) shall be provided as attachments to Volume III and will become Attachments J-08, J-09, and J-10 to the Contract. The attachments requested shall not count against the page limit for Volume III.

2.0 DATA RIGHTS

The Offeror shall provide the following information as attachments to its offer:

2.1 Non-Commercial Data Rights

The Offeror shall provide the following information related to Rights in Non-Commercial TD, Non-

Commercial CS, and Non-Commercial CSD.

a. The 7017 List. The Offeror shall attach to its offer a list identifying all non-commercial TD, CS, and CSD that it asserts will be delivered with other than unlimited rights. Specific instructions and requirements concerning this list are set forth in the DFARS 252.227-7017 “Identification and

Assertion of Use, Release, or Disclosure Restrictions” (Jun 1995) provision incorporated at

Section L of this solicitation. If the Offeror is awarded a contract, the 7017 List shall be attached to the contract in Section J as Attachment J-08.

Duty to submit negative list – If there is no non-commercial data or software to be identified in the

7017 list, the Offeror shall submit the list and enter “None” as the body of the list.

b. The 7028 List. The Offeror shall attach to its offer a list identifying all non-commercial TD, CS, and CSD that it intends to deliver with other than unlimited rights and that are identical or substantially similar to TD, CS, or CSD that the Offeror has delivered to, or is obligated to deliver to, the Government under any contract or subcontract.