N00024-18-R-5308-0003_SPQ-9B_DA.pdf

N0002418NR420000

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

Admin PR#: N00024-19-MR-22530

ERP PR#: N/A

The purpose of this modification is to update Section L Table: L-3-1 Proposal Page Limitation to increase the page limitimation of Volume II Technical Approach from 50 pages to 60 pages, as show n herein.

1. CONTRACT ID CODE PAGE OF PAGES

U 1 22

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

16C. DATE SIGNED

BY 11-Feb-2019

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 N0002418R5308

X 9B. DATED (SEE ITEM 11)

15-Jun-2018

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

11-Feb-2019

CODE

NAVAL SEA SYSTEMS COMMAND (HQ)

1333 ISAAC HULL AVE SE

WASHINGTON NAVY YARD DC 20376-2030

N00024 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

N0002418R5308

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

Tab G

GENERAL

The purpose of this effort is to provide Design Agent Engineering Services in support of AN/SPQ-9B Radar production and fielding efforts. Offerors are encouraged to demonstrate their ability to provide innovative approaches toward achieving and sustaining the requirements of this solicitation while demonstrating their ability to support all requirements of the SOW. Offeror should assume a contract award date of third quarter Government Fiscal Year 2019. Offerors should use the information contained within this Request for Proposal (RFP) including Section L and Section M to formulate their response.

Please note that pursuant to FAR 52.215-1, the Government intends to award a contract on the basis of a proposal submission without conducting discussions with Offerors, but reserves the right to conduct discussions if determined by the Contracting Officer to be necessary (see paragraph (4) of FAR 52.215-1 (f)). Therefore, the Offeror shall submit only one proposal which contains the Offeror’s best terms from a price and technical standpoint. No alternative proposals will be accepted by the Government. The Offeror is required to submit a proposal which is sufficiently detailed and complete to fully demonstrate understanding of, compliance with, and for substantiating the validity of stated claims of all requirements of this RFP. The proposal shall contain only material directly related to this acquisition. The Government may contact any or all or a limited number of Offerors with questions concerning their proposals as permitted under FAR Part 15.

General statements such as “the Offeror understands,” “the Offeror can or will comply with the requirements,” “standard procedures will be used,” “well-known techniques will be used,” or statements that merely paraphrase the RFP in whole or in part DO NOT constitute compliance with the requirements for proposal content. Offerors should assume that the Government has no prior knowledge of their facilities and experience, and will base its evaluation on the information presented in the Offeror’s proposals. Data previously submitted, or presumed to be known (such as data or services previously submitted or performed for the Government), cannot be considered as part of the proposal unless actually included in the proposal. The Government does not assume the duty to search for data to cure problems it finds in proposals. Failure to conform to all requirements of this solicitation may form the basis for rejection of the proposal.

GUIDELINES FOR CONTENT

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

An Offeror’s proposal shall be sufficiently detailed to enable Government evaluation board members to make a thorough evaluation and to arrive at a sound determination as to whether or not the prospective Offeror will be able to perform in accordance with the stated requirements.

The Offeror’s proposal shall be sufficiently specific, detailed and complete as to clearly demonstrate that the Offeror has a comprehensive approach to the total technical requirements, the SOW and solicitation requirements. Proposal content, packaging, and delivery requirements shall be flowed down from the Prime to the major subcontractors, and major subcontractors shall identify the prime contractor associated with their subcontractor proposals on the cover of their submissions. Additionally, the subcontractor shall identify a point of contact, address, and telephone number for each physical location where the work will be performed.

Major subcontractors are defined as any subcontractor performing 10% or more of the total hours under the contract;

however, where otherwise minor subcontractors cumulatively perform more than 20% of the total hours under the contract or cumulatively perform more than $10M of work under the contract, all subcontractors are considered major subcontractors and must propose as such. All subcontractors that do not meet the definition of major subcontractor above are minor subcontractors.

Table: L-3-1. Proposal Page Limitations

Volume Title Page Limit Total Copies

I

Introduction (Unclassified)

• Tab A: Cover Letter**

• Tab B: Table of Contents**

• Tab C: Executive Summary

6 Unclassified softcopies 1 Unclassified hardcopies

II

Technical Approach (Unclassified):

• Tab D: System Performance Approach and

Technical Knowledge

• Tab E: Sample Scenario

• Tab F: Personnel o Key Personnel Resumes* o Staffing Plan**

6 Unclassified softcopies 1 Unclassified hardcopies

III

Management Approach (Unclassified)

• Tab G: Engineering Management Plans and

Processes

• Tab H: Program Management Process

6 Unclassified softcopies 1 Unclassified hardcopies

IV

Data Rights (Unclassified)

• Tab I: Data Rights**

6 Unclassified softcopies 1 Unclassified hardcopies

V Past Performance (Unclassified)

6 Unclassified softcopies 1 Unclassified hardcopies

VI Cost/Price (Unclassified)** Unlimited 6 Unclassified softcopies 1 Unclassified hardcopies

VII Exceptions, Deviations & Waivers 10 6 Unclassified softcopies 1 Unclassified hardcopies

*Key Personnel Resumes are not counted against the page limits above, but each is limited to two pages per resume.

** See Page Count Exceptions below.

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 Cost/Price Proposal Volume (Volumes VI ). UNDER NO

CIRCUMSTANCES SHALL CONTRACT COST AND PRICING DATA BE INCLUDED IN VOLUMES I

THROUGH V and VII. In the event that cost and pricing data is included in Volumes I through V and VII, that data will be excluded from the evaluation.

**Page Count Exceptions

Each page of the written volumes, including appendices and annexes, will be counted towards the total page count, with the following exceptions:

Transmittal letters, teaming agreements, letters of intent, subcontract agreements, Small Business Subcontracting Plan.

Cover pages, title pages, tabbed dividers.

Section K, Representations and Certifications Blank pages. Pages the Offeror intentionally left blank for formatting purposes (e.g. back of page before a section break), shall be marked with “this page intentionally left blank” and the annotated pages will not be counted towards page limits.

Tables of contents. No substantive text shall be included in the document Table of Contents.

Lists of figures and tables, glossaries of abbreviations and acronyms, and cross-reference matrices The Staffing Plan (Attachment J-S3) The 7017 List, 7028 List, and Commercial Restrictions List (Volume IV. Tab I) Key Personnel Letter of Intent Contractor Award Information (J-S6)

Binding

Each volume of the proposals shall contain a glossary of all abbreviations and acronyms used, with an explanation for each. Each volume shall be contained in a separate, loose-leaf, three-ring binder, which lies flat when open, with tabs for each major Section and Subsection identified in table L-3-1 of this document. Staples, spiral or glued bindings shall not be used. Each binder shall have a front cover containing the volume number, title, copy number, solicitation number and the Offeror's name. The same identifying data shall be placed on the spine of each binder.

Should any Volume be divided into more than a single binder, the cover shall identify the binder number in addition to the Volume number, e.g., “Volume II – Technical Approach, Binder One of Two.” Each volume shall be labeled and numbered sequentially for the required number of copies starting with Copy 1. The original paper copy shall be labeled “Original: Copy 1.” The Offeror shall apply all appropriate markings including those prescribed IAW FAR 52.215-1(e) “Restriction on Disclosure and Use of Data,” and FAR 3.104-4 “Disclosure, Protection, and Marking of Contractor Bid or Proposal Information and Source Selection Information.”

To aid in the evaluation, all proposals shall follow the same general format. Page limitations on the proposal are described in Table L-3-1. All pages submitted by an Offeror in excess of the limitations contained in these instructions shall not be read or evaluated, and will be removed by the 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. Pages not in the page count shall be numbered with Roman numerals (e.g., iv) and shall not contain additional or inappropriate information, and if such is found, these pages will be removed by the Contracting Officer and will not be read or evaluated.

Page Size and Format

A page is defined as each face of an 8-1/2 x ll-inch sheet containing information. Two pages may be printed on one sheet of paper, with the front and back counted as two pages. Foldout pages may be used for large tables, charts, graphs, diagrams and schematics, not for pages of text. Foldout pages are defined as the face of an 11 x 17-inch sheet containing information. Foldout pages shall fold entirely within the volume. Each printed side of a foldout page will count as two pages, and must be numbered accordingly. All information on a page must be provided within an image area of 7 x 9 inches (9 x 15-1/2 inches for foldout pages), except for classification headings, footings, and page numbers. All material must be contained within the page limit identified for each volume, unless otherwise specified. Partial pages count as a full page for page limitation purposes. All pages within a page-limited volume shall be consecutively numbered, starting at page one, and not exceeding the page limitation. The Contracting Officer will remove any pages submitted by Offerors not in compliance with formatting requirements.

These limitations shall apply to both electronic and hard copy proposals.

The information regarding electronic products presented below should not be construed as Government endorsement for these particular products. Efforts by the Government to clarify and install electronic proposal submissions in accordance with FAR 15.207(c) will not be considered discussions. In the event of inconsistencies between the hardcopy and electronic versions of a proposal, the electronic version shall take precedence. Page limits for electronic versions shall be consistent with printed page requirements stated in table L-3-1.

Electronic proposal submission and supporting information shall be submitted on CD-ROM or DVD discs suitable for reading in a standard PC compatible DVD drive. All files shall be compatible with Microsoft Office 2010. All spreadsheets shall be in Microsoft Excel format such that each mathematical equation utilized for calculations is visible and working. Before submitting spreadsheets, the Offeror shall remove or disable macros, but retain all computational functionality and embedded links and formulas. All text documents shall be in Microsoft Word 2010.

The Offeror shall not embed sound or video files into the electronic files. The Offeror shall screen all discs for computer viruses prior to submittal. The information and format of the proposal shall be identical on electronic copies, discs, and hard copy submissions.

All CD or DVD discs shall be read only and shall not be password protected. The cost proposal disc files shall be submitted with unrestricted access permissions. Unclassified volumes shall be submitted on unclassified discs. The discs shall be labeled with the following information:

Offeror Name Name of Effort Solicitation Number Date of Proposal Submission Proposal Volume Number(s) and Name(s) Classification Level Disc Number (e.g., l of 3) Copy Indicator Number Restrictive marking (FAR 52.215-1(e)) “Source Selection Information” (FAR 3.104-4).

Volumes I, II, III, IV, V and VII may be submitted together on one disc. If submitted on separate discs, the submission shall not exceed more than one disc per volume. Volume VI, labeled “Cost/Price,” must be submitted on a separate disc from all other proposal information.

Subcontractor media submissions, if provided, shall be labeled with the same information listed above, and shall also include the name of the prime Offeror.

The electronic copy of each proposal must contain hyperlinks or cross-references where reference is made to other sections, tables, or figures within that document. Offerors must highlight the presence of hyperlinks or cross-references through use of different font colors and/or underlining. Each Microsoft Word electronic document shall contain a table of contents, for sections, subsections, tables, and figures, as appropriate with hyperlinks to facilitate navigation within each proposal document. The features that are native to Microsoft Office 2010 applications should be used for this purpose. Hyperlinks or cross-references must not be used to link items between different documents or proposal items or external sources.

Text

Proposals must be prepared using the 12-point Times New Roman font. Text lines must be single-spaced, and must not exceed 46 lines per column, per page, including headings. Line spacing before and after a heading must be double-spaced. Typesetting, font compression, and other techniques to reduce character size or spacing are not permitted, and will be considered a deliberate attempt to circumvent the page limitations. No pen-and-ink changes are allowed. Two-column presentation and use of bold face type for paragraph headings is acceptable. The font size for illustrations and tables must be no less than:

Art: 8-point Tables: 8-point Titles: 10-point, bold, title case

Cross-Reference Matrix

Cross referencing between factors within Volumes I-V is permitted where its use would conserve space without impairing clarity. However, each factor of Volumes I -V of the proposal shall be written to the greatest extent possible on a stand-alone basis so that its content may be evaluated with minimal cross referencing to other factors within Volumes I -V of the proposal. The Cross-Reference Matrices shall clearly identify the location(s) in the Offerors proposal that address or respond to each numbered requirement in Sections L and M. Where cross referencing is necessary, the Offeror must cite the specific factor, page number, section or paragraph for reference.

Information required for each factor, which is not found in its designated factor or properly cross referenced, will be assumed to have been omitted from the proposal.

The Offeror shall at a minimum provide a Cross Reference Matrix showing the traceability of Government solicitation requirements to the Offeror’s proposal.

A complete set of Cross-Reference Matrices shall be provided in the front of each volume.

Packing Instructions

Proposal binders must be packed in boxes. The boxes must be sequentially numbered with the box numbers placed on all sides of each box, and written on all sides of the outside wrapper, if necessary. Box 1 must include the electronic copy CDs, and the master packing list. The master packing list must list the contents (i.e., volume number, copy number, and volume name) of each box, by box number.

The Offeror is responsible for the condition of its delivered proposal. Binders and their contents that are broken apart or received in a disorderly fashion will be reassembled by the Government. The Government is not responsible for proper reassembly of these binders.

Furthermore, telegraphic, facsimile, or e-mail modifications of offers, or withdrawals of offers, will not be considered.

Point of Contact

The Procuring Contracting Officer (PCO) is the sole point of contact for this acquisition; however, designated Contract Specialist(s) may contact Industry on the PCO’s behalf.

Procuring Contracting Officer

KATE ROBB

SEA 02532

TEL: 202-781-2445

Email: kate.robb@navy.mil

Contract Specialist

CAMILLE ONATE

SEA 02532O

TEL: (202) 781-4032

Email: camille.onate@navy.mil

Cost Data

Cost data shall ONLY be included in Volume VI Cost/Price Proposal. Any pages with cost information contained in volumes other than Volume VI Cost/Price will be removed and destroyed by the Contracting Officer without being evaluated.

Written Questions

Offerors may submit written questions requesting clarification of RFP requirements using Attachment J-S2, Solicitation Question Submittal Form in Excel format with the subject line: “AN/SPQ-9B Radar Design Agent Bidder Question” to the following two e-mail addresses: kate.robb@navy.mil and camille.onate@navy.mil. Potential Offerors may submit multiple Bidders Questions per Bidder Question Submittal Form by adding a row for each question.

Communications with any Government employees other than the point of contact listed above are strictly prohibited.

Information provided with each question should include a document name, document date, specific page, paragraph, clause or other definitive citation requiring clarification. It is the Government’s intention that all question and responses will be distributed to all Offerors via RFP amendment(s). The Government will publish all questions and responses submitted via the website at https://www.fbo.gov/.

Should there be an inquiry submitted that the potential Offeror believes addresses a subject that is specific to the company (and/or addresses anything that is believed to be proprietary in nature) then the inquiry shall be marked accordingly. If the Government concurs with this identification, the Government will respond only to that potential Offeror although the Government may decline to answer such questions. Offerors are therefore encouraged to submit questions that do not contain company-specific information. If the Government does not concur with that identification, it shall inform the submitter and not provide any further response. Only written questions will receive a response and Company-specific information will be omitted from responses if released to all Offerors.

Classified questions shall be submitted in accordance with (IAW) the DD Form 254 and DoD 5220.22M NISPOM in hard copy format using the Bidders Questions Submittal Form to the PCO care of the COR. Potential Offerors shall mark each package as follows:

Marked: Bidders Question N00024-18-R-5308 Naval Sea Systems Command 1333 Isaac Hull Ave SE Washington Navy Yard, DC 20376 Attn: Kate Robb SEA02532 Procuring Contracting Officer C/O Steven Wert PEO IWS 2R1B DO NOT OPEN IN MAIL ROOM CONTACT: Steven Wert, 202-781-2976

Alternate POC Clinton May, PEO IWS 2R1C DO NOT OPEN IN MAIL ROOM CONTACT: 202-781-3683

All security related requests for Classified Material pertaining to this contract shall be submitted in writing using the Classified Material Request Form, Attachment J-S5, by the contractor's Facility Security Officer (FSO) to the individual identified in block 16(a) of DD-254 Attachment J-1.

All questions should be received within twenty (20) calendar days after receipt of RFP 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.

All other publication of classified questions and answers in response to this solicitation will be mailed to potential Offerors who have completed the RFP Classified Material Request Form, Attachment J-S5, and signed the certification in accordance with the RFP.

SUBMISSION OF PROPOSAL: NAVSEA will not accept electronic submission of proposals. All copies of the proposal (Volumes I through VII) shall be submitted to the PCO at the address below by 4:00 p.m. local time at the Naval Sea Systems Command on the proposal due date.

Commander, Naval Sea Systems Command Department of the Navy

ATTN: KATE ROBB, SEA 02532

1333 ISAAC HULL AVENUE SE, MS2040, Bldg. 197

WASHINGTON NAVY YARD, DC 20376

a) It is recommended that proposals be mailed in accordance with RFP instructions. Failure to adhere to the procedures provided herein will not be considered an exception to timely proposal delivery as addressed in FAR 52.215-1.

(b) All Offerors shall mark each RFP package with the name of the Procurement Contracting Officer and the Contract Specialist, their codes and phone numbers.

DESTRUCTION OF RESTRICTED MATERIAL

By submitting a proposal, Offerors certify that they will destroy restricted information obtained in connection with this solicitation and any and all copies, notes, or other materials produced using the classified or other restricted information provided in connection with this solicitation 90 days from contract award if they are deemed an unsuccessful Offeror.

Proposal Requirements

PROPOSAL VOLUMES I THROUGH VII

VOLUME I: Introduction

Tab A: Cover Letter

The proposal shall be accompanied by a cover letter prepared on the company’s letterhead stationery and shall state the following:

The proposal is valid for 365 days from the solicitation closing date The Offeror’s Cage Code and DUNS Number All enclosures being transmitted

The Cover Letter shall be signed by an authorized representative of the Offeror who has the authority to bind the Offeror and shall include the Offeror’s authorized point of contact.

Tab B: Table of Contents

The proposal shall list the sections, subsections, and page numbers for both electronic and hard copy versions in a Table of Contents.

Tab C: Executive Summary

The proposal shall include an overview and summary of the Offeror’s proposal in an executive summary. The executive summary shall be limited to two (2) pages and shall be unclassified. This shall not contain material that is not otherwise included within the proposal. No cost information shall be contained in the executive summary.

Offerors should organize the Executive Summary according to the Offeror’s own judgment so as to best present its case to the Government in support of selection for contract award. The Executive Summary shall demonstrate the Offeror’s understanding of the Government’s requirements for the AN/SPQ-9B Radar Design Agent and may summarize the Offeror’s proposed solution. The Executive Summary, in accordance with Section M of this solicitation, will not be separately evaluated.

VOLUME II: Technical Approach The Offeror shall submit a Technical Proposal as outlined below that demonstrates the credibility of its offer. The Technical Proposal must be sufficiently specific, detailed, and complete to demonstrate clearly and fully that the Offeror understands the AN/SPQ-9B Radar Design Agent SOW requirements and technologies involved. The Technical Proposal must reflect the capability of the Offeror’s organization to perform the resulting contract.

Technical Proposals must also address risks associated with the Offeror’s proposed approach.

In addition, the Offeror’s proposal must:

Demonstrate its understanding of and experience with the technologies, standards, statutes, policies, and regulations governing the efforts under this contract.

Demonstrate its understanding of AN/SPQ-9B Radar engineering and capability requirements.

Demonstrate its understanding of all portions of the SOW and its capability to execute all portions of the SOW.

The Offeror shall organize its Volume II proposal into the following tabs:

Tab D – System Performance Approach and Technical Knowledge Tab E – Sample Scenario Tab F - Personnel

Tab D: System Performance Approach and Technical Knowledge

Within Tab D, Offeror shall discuss its or its subcontractors’ knowledge of radar technologies including, but is not limited to: 1) slotted antenna array technologies, 2) receivers, 3) processors, 4) transmitters, 5) Linux Real Time Operating Systems (ROTS), 6) digital signal processing, 7) pulse de-interleaving, 8) EMI mitigation techniques, 9) threat libraries, 10) trackers, and 11) displays. Technical knowledge can be demonstrated through past experience implementing relevant processes or solutions to technical problems, including those that resulted in reduced total ownership cost to the Government or an improvement in system performance.

The Offeror’s proposal shall also demonstrate its proposed technical approach to, its understanding of, and its experience (to include relevant examples) performing in the following areas:

System Engineering Support (SOW paragraph 3.1)

Software Development and Modification (SOW paragraph 3.2)

Hardware Design and Modification (SOW paragraph 3.3)

Installation Support (SOW paragraph 3.4)

Safety Support (SOW paragraph 3.5)

Test Support (SOW paragraph 3.6) The offerors proposal shall specifically demonstrate its proposed use of simulators and stimulators, scheduling of assets, and support for events.

Logistics Product Data (LPD) Updates (SOW paragraph 3.7) The offeror’s proposal shall specifically describe its proposed processes and data collection to use/update design analysis and artifacts to affect LPD.

Configuration Management Support (SOW paragraph 3.8)

Tab E: Sample Scenario

Each Offeror shall describe the application of proposed technical approach it provides in Volume II Tab D to the following sample scenario. This sample scenario is provided only for proposal purposes and will not necessarily reflect the actual work required in performance.

Scenario:

PEO IWS 2.0 has fielded a new AN/SPQ-9B Radar system on DDG, CG, LPD, LHA, LHD, CVN, and Coast Guard Medium Cutters (WMSL) US ship classes. The Program Office must obtain all analysis, data, test results and related information necessary to ensure the system is meeting performance requirements and determine any risks. Over the past several years, there has been an increasing Electronic Attack (EA) threat to Fleet radars in the form of Digital Radio Frequency Memory (DRFM). The DRFM can generate multiple false firm track targets along the same threat bearing as the real target. Since the radar’s firm tracks are passed directly to the combat system (CS), the potential for combat system track overload or engagement on a false target threat are a major concern. In order to counter the effects of DRFM jamming, the Program Office is requesting the Offeror to develop, test, and implement an Electronic Protection (EP) technique into the radar.

Answer the following eight (8) questions applying the technical approach proposed in Volume II Tab D. Clearly describe the application of the proposed technical approach in reaching the answers in addition to providing the impacts to AN/SPQ-9B Radar subsystems and CS interfaces.

Questions:

i. Discuss your approach to characterize DRFM threats and tactics.

ii. Discuss your approach for implementing software and hardware changes?

iii. What engineering tools will be utilized in your approach, and how would they be used? Specifically, what tools are already at your disposal? What tools will need to be developed or modified?

iv. What programmatic tools will be utilized in your approach?

v. Identify any GFI and GFE required in preparation and/or execution of testing.

vi. How will you demonstrate, measure, and analyze the final product to determine that an effective system improvement is delivered to the Fleet?

vii. Describe the necessary analysis and studies to be performed in order to build a notional technical and programmatic road map to implement the proposed approach, associated risks and mitigation techniques, and cost trades. Provide Plan Of Action and Milestones (POA&M).This includes any external information and/or decision dependencies and the associated stakeholders. Identify the personnel/Subject Matter Experts (SME) by labor category selected to conduct the analysis and develop alternatives for implementation of engineering changes.

viii. Describe the approach for assimilating disparate data sets from multiple Government sources and contractors and the subsequent analysis.

ix. Offerors shall include an estimate for the number of hours required to complete the task. The hours estimate shall be comprised of a skill mix that represents the expertise and experience required to complete the sample task. Offerors shall use the labor categories (e.g. Program Manager, Engineering Personnel, Administrative Support, etc.) identified under Table L1 – LOE Skill Mix (below) and shall annotate the labor mix levels; Senior, Mid-Level, Junior. NOTE:

Offerors shall not include any cost or price information associated with the hours estimate.

Tab F: Personnel

The Offeror’s proposed personnel (Key Personnel Resumes and Staffing Plan) shall demonstrate the Offeror’s proposed staffing to achieve the proposed technical and management approach described in the other portions of the offeror’s proposal. The Key Personnel Resumes and Staffing Plan will be consistent with each other and with all other portions of the Offeror’s proposal.

Key Personnel Resumes

Offerors shall only propose Key Personnel resumes for individuals that, at the time of proposal submission, the offeror has a good faith expectation of providing at award. Additionally, the Government requires the submission of Letters of Intent for proposed contingent Key Personnel. The Letter of Intent is considered to be material to the proposal since these Letters of Intent demonstrate the offeror's ability to hire personnel with the qualifications bid at the salary proposed.

The Offeror shall provide a detailed resume, not to exceed 2 pages, for every one of its proposed Key Personnel.

The Offeror’s proposal will be considered nonresponsive if any Key Personnel positions are “pending,” lack a resume, or lack a Letter of Intent. Each resume should best demonstrate the Key Personnel’s qualifications to complete the functions for which the Offeror has proposed that person. Read together with the other parts of the Offeror’s Technical Approach Volume, these resumes shall demonstrate the Offeror’s ability to successfully meet the requirements of this solicitation.

Key Personnel resumes must provide, as a minimum, the following information:

(a) Name, years of experience, training, unique or special qualification, positions held and tenure with the firm

(b) Degrees held by each individual and/or other pertinent education. Includes date(s), degree(s), and respective college or university from which the degree(s) were received

(c) Work history (including dates) of each person as it relates to the anticipated statement of work task(s) to be assigned to that individual

(d) Security Clearance Level

(e) Citizenship

All Key Personnel shall possess at least a SECRET security clearance.

Separate individuals shall be proposed for each of the Key Personnel positions noted below. No single individual shall be proposed for more than one Key Personnel position. The Government required Key Personnel are as follows:

Program Manager Required: Ten (10) or more years of experience performing program or project management on a similar development effort for a US DoD Component.

Strongly Desired: Navy Support: 10 Years of experience. Financial Management: 15-20 years of experience. Program Management: 15-20 years of experience. Master’s degree in Business or Engineering.

Project Management Professional (PMP) certification or equivalent. Five years of experience running a large Professional Support Services contract with multiple subcontractors.

Lead Systems Engineer Required: Ten (10) or more years of experience performing system engineering on a similar development effort for a US DoD Component.

Strongly Desired: Navy Support: 10 Years of experience. System Engineering: 15-20 years of experience.

Master’s degree in Engineering. Five years of experience working a large US DoD Component contract with multiple subcontractors.

Lead Software Engineer Required: Ten (10) or more years of experience performing software engineering on a similar development effort for a US DoD Component.

Strongly Desired: Navy Support: 10 Years of experience. Software Coding: 15-20 years of experience.

Master’s degree in Computer Science. Five years of experience working a large US DoD Component contract with multiple subcontractors.

Lead Hardware Engineer

Required: Ten (10) or more years of experience performing hardware engineering on a similar development effort for a US DoD Component.

Strongly Desired: Navy Support: 10 Years of experience. Hardware Engineering: 15-20 years of experience. Master’s degree in Mechanical Engineering. Five years of experience working a large US DoD Component contract with multiple subcontractors.

Radio Frequency (RF) SME Required: Ten (10) or more years of experience performing RF engineering on a similar development effort for a US DoD Component.

Strongly Desired: Navy Support: 10 Years of experience. Hardware Engineering: 15-20 years of experience. Master’s degree in Electrical Engineering. Five years of experience working a large US DoD Component contract with multiple subcontractors.

Signal Processing SME Required: Ten (10) or more years of experience performing signal processing engineering on a similar development effort for a US DoD Component.

Strongly Desired: Navy Support: 10 Years of experience. Hardware or Software Engineering: 15-20 years of experience. Master’s degree in Electrical Engineering or Computer Science. Five years of experience working a large US DoD Component contract with multiple subcontractors.

Staffing Plan Offerors shall provide a Staffing Plan (without cost), by SOW paragraph/task area, of all proposed personnel by labor category supporting each of the task areas specified in the statement of work. The Offeror shall provide their Staffing Plan (without cost) in the Microsoft Excel format described by Attachment J-S3, which consists of the following information set:

a. Individual's Name

b. Employer (employee's company name)

c. Labor Category

d. Proposed Position

e. Task Area

f. Key Personnel

g. Number of labor hours proposed for each base and option year, in accordance with the Cost/Price Summary

h. Years of related professional experience

i. Highest Educational Degree Obtained

j. Degree area

k. Relevant Certificates Attained

l. Security Clearance level

m. Citizenship

n. Work location

o. Mapping to Company-Specific Labor Categories

p. Notes & Risk Mitigation

q. Description of relevant experience that maps to the technical requirements

Offerors should list “TBD” in the name column and the minimum qualifications of the relevant Government labor category in any positions for which the Offeror does not have a firm candidate identified to provide at award.

Where the Government labor category definitions allow for degrees to off-set years of experience, Offerors shall consider the minimum qualifications for the labor category to be those requiring the least advanced degree. Offerors should follow this procedure for positions for which Offerors or subcontractors only propose labor categories or example individuals.

Offerors should preface the names of contingent hires with “Contingent -;” for example, “Contingent – Jane.”

Offerors should list the prospective employer in the “Employer” Column of the Staffing Plan.

NOTE: From a U.S. Government proposal evaluation perspective, proposal risk may increase with high levels of individuals proposed as TBD or contingent. Nevertheless, in the Staffing Plan column p, Notes & Risk Mitigation, Offerors may describe actions they have taken to mitigate the impact of these risks to the Government.

NOTE: From a U.S. Government proposal evaluation perspective, higher levels of education and relevant experience in a proposed work force indicate a richer labor mix. Proposing a richer labor mix, in appropriate tasks under this solicitation, may reduce the performance risk that the Government bears in accepting an Offeror’s proposal. Offerors may discuss the potential benefits of the richness of their proposed labor mix in the Staffing Plan narrative, but should clearly describe how a richer labor mix reduces the performance risk to the Government.

When read together with the other parts of the Offeror’s Technical Approach Volume, the Offeror’s Staffing Plan should demonstrate the Offeror’s ability to successfully meet the requirements of this solicitation. The Offeror shall not be penalized for use of subcontractors, but shall describe in the narrative how the proposed team provides optimal balance between size, manageability, and support capability while maintaining an integrated approach.

Level of Effort and Labor Mix Estimate The Offeror shall propose their overall allocation of personnel labor resources in accordance with the required allocations of senior, mid-level and junior personnel described in the table below. The Offeror’s resulting labor allocation shall include all Key Personnel. Any deviation from Table L-1 below will result in an Offeror’s proposal being evaluated as unacceptable.

Table L1 – LOE Skill Mix

Labor Categories: Labor Mix

CLIN

CLIN

CLIN

CLIN

CLIN

Program Manager, Engineering Personnel, T&E, Installation, Safety

Senior Level (incl. Key Personnel)

8,082 8,328 7,799 7,637 7,621

Mid Level 9,346 9,632 9,020 8,832 8,814

Junior Level 1,869 1,926 1,804 1,766 1,763

Logistics, Configuration Management

Senior Level 1,449 1,493 1,399 1,370 1,367 Mid Level 1,812 1,867 1,748 1,712 1,708 Junior Level 362 373 350 342 342

Administrative Support

Mid Level 134 138 129 127 126 Junior Level 134 138 129 127 126

Total 23,188 23,895 22,378 21,913 21,865

Government Labor Category Definitions

1) Program Manager, Engineering Personnel, T&E, Installation, Safety (Senior, Mid-level, and Junior)

Senior: a high school degree and more than twenty (20) years of relevant experience, or a bachelor's degree in a relevant field and fifteen (15) years of relevant experience, or a master's degree in a relevant field and ten (10) years of relevant experience.

Mid-Level: a high school degree and ten (10) years of relevant experience, or a bachelor's degree in a relevant field and five (5) years of relevant experience, or a master's in a relevant field.

Junior: a high school degree and three (3) years of relevant experience, or a bachelor's degree in a relevant field, or a master's degree in a relevant field.

2) Logistics & Configuration Management (Senior, Mid-level, and Junior)

Senior: at least eight years of relevant logistics experience.

Mid-level: at least three years of relevant logistics experience.

Junior: an Associate’s degree or higher, or at least one year of relevant logistics experience.

3) Administrative Personnel (Mid-level, and Junior) Mid-level: at least three years of relevant administrative experience.

Junior: an Associate’s degree, or higher, or at least one year of relevant administrative experience.

The Offeror shall provide a mapping of any company-specific labor categories it, or one of its subcontractors, proposes in the Staffing Plan to the Government labor categories defined above. This mapping, detailed in Column

o. of the staffing plan (J-S3), must include a description, similar in detail to the Government labor categories, of the requirements/qualifications associated with each company-specific labor category contained in the Offeror’s Staffing Plan, including company-specific labor categories proposed by subcontractors.

VOLUME III - Management Approach The Offeror’s Management Approach proposal shall demonstrate sufficient management processes to successfully perform the effort in accordance with the Technical Approach Volume. The Management Approach proposal shall address:

• Tab G: Engineering Management Plans and Processes

• Tab H: Program Management Process

Tab G: Engineering Management Plans and Processes

The Offeror shall describe its proposed plan for allocating facilities, equipment, development environment, and testing assets. The Offeror shall describe how they will achieve and maintain processes and procedures that are at least equivalent to a minimum Capability Maturity Model Integration (CMMI) Level 3 or higher as required in SOW 3.2.

The Offeror shall describe its management plan for participation in the definition and development of external interface and control software requirements including aligning with the external system developments. The Offeror shall describe how its proposed engineering and software management process is appropriate for the scope of work contained in Section C and how it will provide early design disclosure directly to the Government.

Tab H: Program Management Process

The Offeror shall describe its corporate organization, management organization for implementation of the Design Agent contract, a description of the PMs authority and control, project organization, quality policy, company-wide processes, standard practices, policies and procedures that will be applied to this effort as well as management of program risk, identification of subcontractors and associated tasking, management of subcontractors, and communications with the Navy and other external organizations to satisfactorily complete all tasks.

VOLUME IV – Data Rights

Tab I: Data Rights 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 ten (10) pages. Price information shall be completely omitted from the Data Rights Proposal Volume.

DATA RIGHTS PROPOSAL SUMMARY

1.0 Introduction

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 (GPR). If such non-commercial TD/CS/CSD contains elements generated previously with Offeror’s own capital, it is the Government’s intent that non-commercial TD/CS/CSD be delivered with a minimum of GPR (as defined in DFARS 252.227-7013 (MAR 2011) and DFARS 252.227-7014 (MAR 2011)). 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 GPR. 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 — Non-commercial Technical Data, Non-commercial Computer Software, Non-commercial Computer Software Documentation), Supplemental Information, and Commercial Restrictions List shall be provided as attachments to Volume IV and will become Attachments J-5, J-6, J-7 and, J-8 to the Contract. The attachments requested shall not count against the page limit for Volume IV.

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

Non Commercial Data Rights

The Offeror shall provide the following information related to Rights in Noncommercial TD, Noncommercial CS, and Noncommercial CSD.

The 7017 List. The Offeror shall list all noncommercial 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 K of this solicitation. If the Offeror does provide assertions, this paragraph shall also serve as the Contracting Officer’s request for Offeror submission of evidence and information to evaluate and validate listed assertions. Additionally, if there is no data or software to be identified in the 7017 list, the Offeror shall submit the list and enter "None" in the body of the list. If the Offeror is awarded a contract, the 7017 List shall be incorporated into the contract as Attachment J-5.

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.

The 7028 List. The Offeror shall list all noncommercial TD, CS, and CSD that it intends to deliver with other than unlimited rights and that are identical or substantially similar to noncommercial TD, CS, or CSD that the Offeror has delivered to, or is obligated to deliver to, the Government under any contract or subcontract. Specific instructions and requirements concerning this list are set forth in the DFARS 252.227-7028 “Technical Data or Computer Software Previously Delivered to the Government” (Jun 1995) provision incorporated at Section K of this solicitation. If the Offeror is awarded a contract, the 7028 List shall be attached to the contract in Section J as Attachment J-6.

Duty to submit negative list – If there is no non-commercial data or software to be identified in the 7028 list, the Offeror shall submit the list and enter “None” as the body of the list.

Supplemental Information. The Offeror shall include in its offer a statement, entitled “Supplemental Information— Noncommercial Technical Data, Noncommercial Computer Software, Noncommercial Computer Software Documentation” (the statement) that, for each item of noncommercial TD, CS, or CSD that the Offeror asserts should be delivered with specifically-negotiated license rights (as discussed at DFARS 252.227-7013 “Rights in Technical Data – Noncommercial Items” (NOV 1995) and/or DFARS 252.227- 7014 “Rights in Noncommercial Computer Software and Noncommercial Computer Software Documentation” (JUN 1995), sets forth a complete description of all such proposed restrictions on the Government’s ability to use, modify, release, perform, display, or disclose such TD, CS, or CSD. This information shall be provided by referencing and delivering any and all proposed license agreements that are attached to the statement. The Offeror shall submit the statement dated and signed by an official authorized to contractually obligate the Offeror. If there is no information to be included in the statement, the Offeror need not submit the statement. If the Offeror is awarded a contract, any statement provided will be incorporated into the contract as Supplemental Information Attachment J-7.

Duty to submit negative response– If there is no data to be identified in the Supplemental Information, the Offeror shall submit “None” as the information.

Commercial Data Rights

The Offeror shall…