N0002416R6247_RFP_Amendment_3.pdf

N0002416NR94617

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 revise Section L Section 1.2 regarding cost/pricing inclusion. Accordingly, the Solicitation is amended as follow s:

1. CONTRACT ID CODE PAGE OF PAGES

S 1 28

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

16C. DATE SIGNED

BY 10-May-2017

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-16-R-6247

X 9B. DATED (SEE ITEM 11)

17-Feb-2017

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

10-May-2017

CODE

NAVAL SEA SYSTEMS COMMAND (HQ)

1333 ISAAC HULL AVE SE

WASHINGTON NAVY YARD DC 20376-2060

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

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

N00024-16-R-6247

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

Instructions, Conditions and Notices to Bidders

SECTION L-3

1.0 General

The Offeror shall submit all information required by this RFP. Failure to comply with the terms and conditions of the RFP may result in the Offeror being disqualified from consideration for award. The Offeror’s proposal shall be based on the requirements contained in this RFP (including those documents, exhibits, and other attachments to the RFP identified in Section J). Offerors are required to submit a proposal encompassing all items listed in Section B of this RFP.

The solicitation will be made available only through the internet at:

http://www.fbo.gov

Offerors are hereby notified that from time to time, the Government may post additional information to the web site relating to this solicitation (e.g. responses to questions, amendments, etc.). It is the Offeror’s responsibility to check the web site for any such information. The drawings and the classified performance specifications may be obtained by contacting the Contract Specialist Karen Giunta. Offerors shall provide their physical address, classified address, CAGE code, and a point of contact for the above-mentioned documents. Once the security approval has been obtained the information will be emailed or mailed to the Offeror. Offerors shall request classified documents within 10 calendar days of RFP release.

Offerors may electronically submit written questions requesting clarification of solicitation requirements by sending an email to the Contract Specialist, Brad Watson at john.b.watson1@navy.mil and copy (CC:) to the PCO Debra Mackall at debra.mackall@navy.mil. Offeror’s comments and/or questions must contain at a minimum: Document Description; Page numbers; Section/Paragraph; Question or Comment; proposed action or change (if applicable); or other definitive citation requiring classification. All such questions should be received by email within 20 calendar days after release of the RFP to allow the Navy adequate time to prepare and issue responses to all Offerors prior to the date and time set for receipt of proposals. Only questions transmitted electronically will receive a response. The Navy will continue to accept questions up to the closing date and time of the solicitation; however, time may not permit responses to be issued prior to proposal receipt. Questions received after the time set forth above may not result in an extension to the proposal due date. It is the Government’s intention that questions and responses will be distributed electronically to all Offerors.

Handling and marking procedure for classified questions (or questions related to classified specification sections) must comply with the following procedures. Any Classified questions shall be packaged in accordance with Chapter 9 of SECNAV M-5510.36, June 2006, and submitted within 20 calendar days of the RFP release via secured mail on an appropriately marked CD and sent to the following address:

(Outer envelope or container address) Naval Sea Systems Command Attn: SEA 02622

1333 Isaac Hull Avenue SE, Stop 2050 Washington Navy Yard, DC 20376-2050

(Inner envelope or container address) Naval Sea Systems Command, (SEA02) Attn: Debra Mackall, SEA 02622 1333 Isaac Hull Avenue SE, Stop 2050 Washington Navy Yard, DC 20376-2050

Questions and answers to classified information will be securely mailed to all bidders who are appropriately cleared.

Classified questions and answers are prohibited from public release and therefore interested Offerors must make a specific request for obtaining said questions and answers. Should classified questions be submitted, all interested Offerors will be informed of such questions.

1.1 Special Notice to Offerors

Upon receipt, all proposals become Government property. After contract award, the unsuccessful Offerors will be required to return to the Government all information, data, drawings, specifications, etc., provided to the Offerors by the Government.

The Government will utilize Government Subject Matter Experts (SMEs) in each SUBFACTOR category in order to ensure technical competency during the evaluation.

1.2 Solicitation Response Requirements

The solicitation response shall be contained in three separate Volumes, delivered by the date of the closing of the solicitation which, unless an extension has been granted, will be as specified in Block 9 of Section A (SF-33 Form) of this RFP:

Volume I - Technical Proposal Volume II - Cost/Price Proposal Volume III - Solicitation Package

For Volumes I, II, and III the number of copies required and the page limit are shown in the table below.

Volume / Title Page Limit NAVSEA DCMA and DCAA I. Technical Proposal 150 6 hardcopy & 6 CDs 2 hardcopy & 2 CDs II. Cost / Price Proposal None 6 hardcopy & 6 CDs 2 hardcopy & 2 CDs III. Solicitation Package None 2 hardcopy & 2 CDs 2 hardcopy & 2 CDs

Appendix Documents*

Document Page Limitation Table of Contents Unlimited Cure Notices, Show Cause Letters, or Letters of Concern for the contracts provided by the Offeror under Past Performance

Unlimited

Resumes 10 pages (2 pages per Resume)

WBS Dictionary 10 pages Software Development Plan 40 pages Integrated Master Schedule Unlimited Teaming Arrangement Unlimited

OCI Mitigation Plan Unlimited

Small Business Subcontracting Plan Unlimited

Section L Cross Reference Matrix Unlimited

Systems Engineering Management Plan (already required just adding to this table) 40 pages

*Appendix documents identified above do not count towards the page limit of Volume I – Technical Proposal page limit but shall observe the page limitations specified.

Electronic proposal submissions and supporting information shall be submitted on CD-ROM suitable for reading in a standard PC compatible CD-ROM drive. All view graphs shall be in Microsoft PowerPoint 2010 (or compatible).

All spreadsheets or mathematical computations (cost data) shall be in Microsoft Excel 2010 (or compatible) format and shall be working versions, including formulas and computations. Submission of locked spreadsheets is not acceptable. All text shall be in Microsoft Word 2010 (or compatible) or searchable Adobe Acrobat Portable Document Format (PDF). All schedules, including Integrated Master Schedule (IMS), shall be in Microsoft Project 2010 (or compatible). The electronic proposal material shall not contain any information not contained in the hard copy format. In the event of disparities between hardcopies and electronic information, the hardcopy governs.

The narrative material shall consist of the following:

Hardcopy proposal shall be typed or printed in a font with the type no smaller than size 12 Times New Roman font on standard 8-1/2 x 11 inch paper.

Text line spacing shall be single spaced. One-inch minimum margins on each side, including top and bottom are required.

Text within tables, diagrams, pictorial charts, or graphic material may use 8-point Times New Roman font.

Fold out pages may be used for diagrams, charts or graphic material only and may not exceed 11 inches by

17 inches. Of the 150 page count limitation, 10 of the pages may be fold out pages in the Volume I Technical Proposal submission. Fold out pages may only include narrative sufficient to describe the diagram, chart, or graphic material.

Every subsection paragraph, figure, and table shall be numbered.

Pages in excess of the page count limitation will be removed prior to the evaluation. If the proposal exceeds the page limit identified in the table above, the Government will remove all pages exceeding the specified page count from the back of the substantive proposal volume (not the appendices or any other content excluded from the Volume I – Technical Proposal page limitation) prior to the evaluation of the proposal and will not be reviewed or evaluated. Pages will not be removed from the index or from any appendices provided at the back of the proposal.

Proposal material shall be presented on double-sided pages only and in a single column on each page (refer to Section I, FAR 52.204-4). Each double-sided page counts as 2 pages.

Pages are to be numbered sequentially and tabs are to be used for chapter breaks. It is not acceptable to restart numbers in subsequent chapters within the proposals.

A date shall be placed on each page of the proposal corresponding to the date of the initial proposal. Any pages that may be revised as a result of discussions (if required) shall contain revision numbers and dates.

Each volume shall be bound separately and shall not exceed the page limitation cited above including both classified and unclassified data. Each hard-copy volume of the proposal shall be bound in three ring binders to permit removal of sections with each major part tabbed.

For the purposes of compliance with the page limitation, classified information (if applicable) shall be supplied separately as a supplement. The page count shall include all material with printed matter and figures except cover pages, title pages, Table of Contents (TOC), lists of illustrations, tab pages, appendices, index and lists of tables.

Pages excluded from the page count must contain only material pertinent to the page heading or be blank and marked "Intentionally Left Blank." Index pages and Tabs are required and shall be cross-referenced to the TOC.

Every page, except those marked as blank, must be numbered.

In addition to the hardcopies, the Offeror shall provide Volumes I, II and III on separate CD-ROMs in the format described above. If a classified supplement is included it shall be provided separately in printed form only with appropriate security classification markings. Each disk shall be labeled as follows:

Volume Number

Offeror Company Name, City, State Offeror POC Offeror POC Phone Number The cover page of each Proposal Volume shall contain:

Volume Number and Title (e.g., Volume I - Technical Proposal) Item Nomenclature and Request For Proposal (RFP) Number Company Name of the Offeror Offeror's Position on Disclosure of Proposal Data Security Classification of the Volume Serial Number/Copy Number

Proposal submission shall be as follows:

1) All copies of all proposal volumes (including electronic copies) shall be submitted at the location and at or before the time specified in Block 9 of the SF 33.

2) No cost or pricing information shall be included in the Offeror's cover letter or in any part of its submitted volumes except the Cost/Price and Solicitaion Volumes. Cover letters are merely instruments for transmitting the submitted proposals; they are not part of the page count and will not be evaluated.

3) Although legible, neat, orderly, and comprehensive proposal(s) are required, elaborate brochures or other presentations beyond that sufficient to present a complete and effective explanation are not desired. Elaborate artwork, expensive visual or other presentation aids are neither necessary nor desired.

4) The Proposal shall contain all the pertinent information in sufficient detail to permit evaluation. The proposal should be so detailed and complete as to clearly demonstrate that the Offeror has a thorough comprehension of all technical and other requirements. If an Offeror fails to comply with content requirements its proposal may be downgraded or disqualified for failure to follow instructions.

1.3 Solicitation Responsiveness

Offerors are advised to submit proposals that are complete, clear, and consistent in all respects without the need for additional explanation or information. Offerors are cautioned against the use of general, vague, or unsubstantiated statements which prevent concise proposal evaluation.

1.4 Competitive Range

It is the Government’s intent to make a contract award based on initial proposals. However, if an award is not made based on initial proposals, the Contracting Officer will make the determination as to which proposals are in the “Competitive Range.” The competitive range shall be determined based on the results of the evaluation of initial proposals, considering all evaluation criteria, and shall include the most competitive proposals. The number of proposals within the competitive range may also be reduced if the Contracting Officer determines the number of most competitive proposals that might otherwise be included within the competitive range exceeds the number at which an efficient competition can be conducted.

1.5 Discussions and Final Proposal Revision (FPR)

Pursuant to FAR 52.215-1, the Government intends to award contract(s) based upon the initial proposals. Therefore, the Offeror’s proposal 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 Offeror’s with written 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. If discussions are held, Offerors selected to participate in the discussion shall be advised of weaknesses, deficiencies and risks in their proposals as well as adverse past performance ratings to which the Offeror has not had an opportunity to respond. The Government may also advise Offerors of strengths in their proposals. Offerors shall be offered a reasonable opportunity to correct or resolve such weaknesses, deficiencies, and risks and to submit such technical and cost information, or other revisions to their proposals, that may result from such discussions. At the end of discussions (if conducted), the Government will request Final Proposal Revisions (FPRs) from all Offerors still within the competitive range. If it is determined that an Offeror is no longer in the competitive range, they will not be given an opportunity to submit an

FPR.

2.0 CONTENTS OF THE OFFER

The offer consists of and must include the following to be eligible for award:

Volume I, Technical Proposal:

See Section L, Section 3.1 for the content and format requirements of the Technical Proposal

Volume II, Cost Price Proposal:

See Section L, Section 3.2 for the content and format requirements of the Cost/Price Proposal.

Volume III, Solicitation Package:

See Section L, Section 3.3 for the content and format requirements of the Solicitation Package Proposal.

3.0 PROPOSAL CONTENTS

3.1 VOLUME I: TECHNICAL/MANAGEMENT PROPOSAL

The Contracting Officer reserves the right to request such additional information regarding scheduling, manpower, facilities, and management organization and capabilities as may be necessary to determine the Offeror’s qualifications for award of a contract, to determine the relative merit of the Offeror’s proposal, or to otherwise clarify any aspect of the proposal.

Offerors shall note that if awarded a contract based upon this solicitation, the Offeror’s Technical Proposal or portion thereof may be incorporated into the contract by reference.

Release of Technical Information: All technical information submitted pursuant to this solicitation is for the exclusive use of Government representatives, will be treated as business confidential, and will not be publicly disclosed, provided that, where a request for disclosure of such technical information is submitted to the Government pursuant to the Freedom of Information Act (5 U.S.C. 552a), the Government will not disclose the Offeror’s technical information if public disclosure of information would substantially harm the Offeror in its competitive position. In order to help ensure non-disclosure, the title page of the technical proposal and other sheets of proposal data shall be marked with restrictive legends and the technical proposal shall be enclosed and marked

“TECHNICAL INFORMATION – NOT TO BE PUBLICLY DISCLOSED”.

The format and content of the proposal shall contain a response to each of the evaluation Factors and Sub-factors outlined below. Information presented shall appear in the same order as outlined below. Factors are listed in descending order of their relative importance to each other. Factor 1.0 is more important than Factor 2.0, which is more important that Factor 3.0, which is more important that Factor 4.0. Additionally, all Sub-factors within each Factor are listed in descending order of their relative importance to each other.

(NO COST/PRICE INFORMATION IS TO BE PRESENTED IN VOLUME I)

Factor 1.0 – Technical Approach

Sub-factor 1.1 – Prime Item Performance Specification Requirements Sub-factor 1.2 – Systems Engineering Approach Sub-factor 1.3 – Integrated Logistics Support Sub-factor 1.4 – Test Equipment and Testing Approach Sub-factor 1.5 – Manufacturing Processes, Throughput, and Facilities

Factor 2.0 – Data Rights

Factor 3.0 – Management Approach

Sub-factor 3.1 – Program Management Sub-factor 3.2 – Quality Management Sub-factor 3.3 – Subcontracting or Teaming Management Sub-factor 3.4 – Small Business Participation

Factor 4.0 – Past Performance

3.1.1 Factor 1.0 – Technical Approach

The Offeror shall provide a Section L Cross Reference Matrix for all Section L evaluation criteria within the Technical Approach factor. The Section L Cross Reference Matrix in Table L-1 is provided as an example for this requirement.

Table L-1: Cross Reference Matrix

Note: This is an example ONLY, Offeror to submit in accordance with its proposal. The Offerors’s narrative shall take precedence in the event there is a conflict with the Offeror’s Cross Reference Matrix.

3.1.1.1 Sub-factor 1.1 – Prime Item Performance Specification (PIPS) Offerors shall demonstrate how the proposed design will meet performance requirements of the solicitation during all phases of the device’s function life. The Offeror shall describe how they will meet the requirements defined in the Prime Item Performance Specification (PIPS) Attachment 1. The requirements of the PIPS are not limited to Section 5 of the document as listed below in (a) through (l) below. Offerors are not required to provide a detailed explanation into implementing the Interface Requirements Specification (IRS) references in the

PIPS.

a. The Offeror shall describe how they will meet the Sequential Development/Production/Testing requirements identified in Section 3.0 of the PIPS.

b. The Offeror shall describe how they will meet the Cybersecurity and Anti-Tamper (AT) requirements identified in Section 5.1 of the PIPS.

c. The Offeror shall describe how they will meet the Modular Open Systems Architecture (MOSA) requirements identified in Section 5.2 of the PIPS.

d. The Offeror shall describe how they will meet the Item Definition requirements identified in Section 5.3 of the PIPS.

e. The Offeror shall describe how they will meet the Characteristics requirements identified in Section 5.4 of the PIPS.

f. The Offeror shall describe how they will meet the Environmental Requirements identified in Section 5.5 of the PIPS.

g. The Offeror shall describe how they will meet the Reliability requirements identified in Section

5.6 of the PIPS.

h. The Offeror shall describe how they will meet the Maintainability requirements identified in Section 5.7 of the PIPS.

Section L- Instructions

Section M- Evaluation

Factor

SOW Reference PIPS Proposal Reference

CLIN

Sub-factor X.X Sub-factor X.X

Para X.X.X, Data Management Note: This column shall address applicable SOW paragraph

Para X.X.X, Data

Management Note: This column shall address applicable PIPS paragraph Note: This column only applies to Sub-factor 1.1

Vol II - Technical (X of X) page XX Note: Refer to page number in Offeror’s written proposal.

i. The Offeror shall describe how they will meet the Construction requirements identified in Section

5.8 of the PIPS.

j. The Offeror shall describe how they will meet the Analysis and Testing requirements identified in Section 5.9 of the PIPS.

k. The Offeror shall describe how they will meet the Quality Assurance Provisions requirements identified in Section 6.0 of the PIPS.

l. The Offeror shall describe how they will meet the Verification Cross Reference Indices (VCRI) requirements identified in Section 7.0 of the PIPS.

3.1.1.2 Sub-factor 1.2 – Systems Engineering Approach

Offerors shall demonstrate how the proposed design will meet engineering requirements defined in the SOW Attachment 7 section 3.2 by addressing the following information and appendices:

a. The Offeror shall provide their Systems Engineering Management Plan (SEMP) in accordance with Section 3.2.1 of the SOW.

b. The Offeror shall describe their approach to System Engineering and Design Analysis

c. The Offeror shall describe their Problem Trouble Report (PTR) System and the process of sharing information regarding identified problems with the government.

d. The Offeror shall describe their approach to Human Systems Integration (HSI) and how HSI efforts will meet the requirements of the SOW.

e. The Offeror shall describe their approach to Configuration Management (CM) which meet the requirements identified within the SOW. The Offeror shall describe their configuration management organization, including configuration control boards, or group and material review boards and explain how these manage product baseline.

f. The Offeror shall describe their approach to Systems Engineering Technical Reviews. This description shall be consistent with the SEMP approach.

g. The Offeror shall describe their approach to Safety including the systems and processes to meet the requirements of the SOW.

h. The Offeror shall describe their approach to System Software and the requirements identified in the SOW. The Offeror shall submit a Software Development Plan (SDP) that at a minimum addresses the requirements of the SOW.

i. The Offereor shall provide an Integrated Master Schedule (IMS) as an appendix which includes all systems engineering efforts and milestones.

3.1.1.3 Sub-factor 1.3 – Integrated Logistics Support (ILS)

Offerors shall demonstrate how the proposed design will meet performance requirements defined in the SOW Attachment 7 section 3.4. Offerors shall provide the following:

a. The Offeror shall describe how the ILS program will be developed for the products used in the ADC MK 5. Describe how all hardware and software products delivered under this contract will be fully supportable throughout their life cycle.

b. The proposal shall include details of how the Offeror will ensure compliance with the life-cycle logistics requirements of the ADC MK 5.

c. The Offeror shall document all ILS milestones in the Integrated Master Schedule (IMS).

3.1.1.4 Sub-factor 1.4 – Test Equipment Design and Testing Approach Offerors shall demonstrate how the proposed design will meet performance requirements defined in the SOW Attachment 7 section 3.3. Offerors shall describe the following:

a. The Offeror shall describe its entire test program, including functional, performance, interface, environmental qualification testing, first article testing, and factory acceptance testing.

b. The Offeror’s description of the designs and development strategy, certification, and usage of factory test equipment and tools.

c. The Offeror’s shall identify all required Government Furnished Property or Facilities needed for testing and design.

d. The Offeror shall describe how it plans to verify that the subcontractor’s products meet requirements.

e. The Offeror shall describe plans for contractor support at the Naval Undersea Warfare Center (NUWC) Division Newport.

f. Offeror shall describe the Test and Evaluation (T&E) procedures used to evaluate all released software.

g. The Offeror shall document all milestones in the Integrated Master Schedule (IMS).

3.1.1.5 Sub-factor 1.5 – Manufacturing Processes, Throughput, and Facilities

Offerors shall describe the facilities and manufacturing processes required to accomplish all work requirements defined in the SOW Attachment 7. Offerors shall describe the following:

a. The Offerer shall describe the facilities necessary for the following work:

i. acoustic

ii. hydrodynamic

iii. model development

iv. prototype fabrication

v. software activities

vi. simulation efforts

b. The Offeror shall describe the process at these facilities for controlling classified information;

including hardware, software, firmware and other classified data.

c. The Offeror will provide its plans to establish and maintain a facility to meet security requirements identified in in the SOW.

3.1.2 Factor 2.0 – Data Rights

The Government desires Government Purpose Rights (GPR) in all Data (Data includes Technical Data, Computer Software and Computer Software Documentation as defined in DFARS 252.227-7013 "Rights in Technical Data Noncommercial Items” (FEB 2014) and/or DFARS 252.227-7014 "Rights in Noncommercial Computer Software and Noncommercial Computer Software Documentation" (FEB 2014) (as applicable) used or generated in performance of this contract. The Data also includes all data relating to commercial items or commercial computer software (hereinafter Commercial Data) used, generated, and delivered in performance of this contract.

a. The Offeror shall propose the extent to which the rights in technical data (TD), computer software (CS), computer software documentation (CSD), and inventions/patents offered to the Government ensure unimpeded, innovative, and cost effective production, operation, maintenance, and upgrade of the ADC MK 5 throughout its life cycle; and allow for open and competitive procurement of ADC MK 5 enhancements.

b. The Offeror shall describe its plan for making design and interface information available as soon as possible after it is defined or established. The Offeror shall describe how it intends to provide all licenses, executable code, object code, source code, drawings, repair and engineering documentation to the Government and third-party contractors at specified key events or at defined intervals.

c. An Offeror whose proposed solution does not provide GPR shall describe how its proposed ADC MK 5 design allows for unimpeded, innovative, and cost effective production, operation, maintenance, and upgrade of the ADC MK 5 throughout its life cycle and allows for open and competitive procurement of ADC MK 5 enhancements.

d. The Data Rights and Patent Rights offered shall be provided as attachments to the proposal. The Offeror shall cite specific examples of the Government's Intellectual Property Rights (IPR) that illustrate the tenets of the offer, including an overview of the information provided in the following required attachments, as well as a discussion of how the information contained in the attachments impacts or illustrates the tenets of the proposal.

The Offeror shall provide the following information as attachments to its offer: (Note: These attachments are not included in the Technical Volume page count.)

a. Rights in Noncommercial TD, Noncommercial CS, and Noncommercial CSD.

i. The 7017 List. The Offeror shall attach to its offer a list identifying all noncommercial TD, CS, and CSD that it asserts should 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” (JAN 2011) provision incorporated at Section K of this solicitation. If the Offeror is awarded a contract, the 7017 List shall be attached to the contract.

ii. The 7028 List. The Offeror shall attach to its offer a list identifying all noncommercial 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. 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” (June 1995) provision incorporated at Section K of this solicitation. Additionally, if there is no 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. If the Offeror is awarded a contract, the 7028 List shall be attached to the contract.

iii. Supplemental Information. The Offeror shall attach to 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 or other non-standard rights (as discussed at DFARS 252.227-7013 “Rights in Technical Data – Noncommercial Items” (FEB 2014) and/or DFARS 252.227-7014 “Rights in Noncommercial Computer Software and Noncommercial Computer Software Documentation” (FEB 2014)), sets forth a complete description of all such proposed non-standard restrictions on the Government’s ability to use, modify, release, perform, display, or disclose such TD, CS, or CSD. This information may be provided by referencing any proposed nonstandard license agreement that is attached to the statement. The Offeror shall submit the statement as an attachment to its offer, 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 attached to the contract.

b.Rights in Commercial TD, Commercial CS, and Commercial CSD. The Offeror shall attach to its offer a list, entitled “Commercial Technical Data, Commercial Computer Software, and Commercial Computer Software Documentation-Government Use Restrictions” (the Commercial Restrictions List), that provides the following information regarding all commercial TD, CS, and CSD that the Offeror (including its sub-Offerors or suppliers, or potential sub- Offerors or suppliers, at any tier) intends to deliver with other than unlimited rights:

(1) identification of the data or software; (2) basis for asserting restrictions, such as licensed products including open source; (3) asserted rights category (e.g. GPR or restricted rights); and (4) name of the entity asserting restrictions. For any item designated as Non-Developmental Item (NDI), the Offeror is requested to provide details of the Agency and level therein that paid for development and the contract number(s) and dates wherein payments were received. For each entry in the list citing an asserted rights category other than the standard license rights applicable to commercial TD as set forth in the DFARS 252.227-7015 “Technical Data – Commercial Items” (FEB 2014) clause, the Offeror shall provide a complete description of the asserted rights (e.g., a specially negotiated license, open source, or the license customarily offered to the public); this information may be provided by referencing any proposed non-standard or commercial license agreement that is attached to the list, but in all cases, the non-standard or commercial license will be attached for Government review. The Offeror shall submit the Commercial Restrictions List as an attachment to its offer, dated and signed by an official authorized to contractually obligate the Offeror. If there is no information to be included in the Commercial Restrictions List, the Offeror shall submit the list and enter “None” as the body of the list. If the Offeror is awarded a contract, the Commercial Restrictions List shall be attached to the contract.

3.1.3 Factor 3.0 – Management Approach

The Offeror shall provide a Section L Addendum 2 Cross Reference Matrix for all Section L evaluation criteria within the Management Approach factor. The Section L Cross Reference Matrix in Table L-1 is provided as an example for this requirement in section 3.1.1.

3.1.3.1 Sub-factor 3.1 – Program Management

Offerors shall demonstrate how the proposed design will meet performance requirements defined in the SOW Attachment 7 section 3.1. Offerors shall describe the following:

a. The Offeror shall provide a comprehensive management plan that contains the following information:

i. An organization chart showing the proposed project organization, names of key personnel and their functions.

ii. A description of how the proposed organization will participate in the Navy Systems Engineering Integrated Product Team (IPT).

iii. A description of the program manager's authority and responsibility.

iv. The Offeror's approach to risk management.

v. Provide a Contract Work Breakdown Structure (CWBS) across the task elements specified in the SOW. The Offeror’s CWBS must include lower breakdown levels where they identify risk associated with technical issues or resources.

vi. A description of the methodology employed to develop plans, budgets, schedules, and work authorization packages.

b. The Offeror shall provide a Staffing Plan matrix that supports the requirements specified in SOW.

i. The Staffing plan shall clearly identify all proposed key personnel.

ii. Key Personnel shall be leads for each proposed functional area, to include a full time dedicated Program Manager.

c. All Key Personnel shall have a minimum of 10 years of experience in their respective field demonstrating specific capability, knowledge, and relevant experience for contract(s) of similar scope and complexity. The Offeror shall provide a resume, not to exceed 2 pages, for up to 5 Key Personnel in an appendix. This appendix does not count towards the overall page count. The Offeror’s resumes shall contain the following information, at a minimum:

i. The individual’s current title, position, and, length of time with the organization.

ii. The individual’s proposed title/job position and level of participation the individual will devote to this contract.

iii. A brief description of specific duties and responsibilities to be performed by the individual.

iv. A description of all relevant positions held (title, dates of employment, employee’s major duties, responsibilities, and accomplishments).

v. The individual’s education, training, licenses, certifications, and any other relevant information.

vi. The Offeror’s proposal shall include the following attestation for each key personnel:

“We attest to the accuracy of the information contained herein and that an agreement has been reached regarding salary, position and work commitment to this project:” signed and dated by both the key personnel and a company official.

d. The Offeror shall provide a WBS Dictionary

e. The Offereor shall integrate project management into the Integrated Master Schedule (IMS) requested in Systems Engineering sub-factor 1.2 and identify the critical path.

3.1.3.2 Sub-factor 3.2 – Quality Management

Offerors shall demonstrate how the proposed design will meet performance requirements defined in the SOW Attachment 7 section 3.5. Offerors shall describe the following:

a. The Offeror shall identify the quality assurance personnel and how they are integrated into design, manufacturing, and product assurance activities.

b. The Offeror shall describe internal quality assurance methods and processes including how quality assurance methods and processes identify, assess, mitigate, implement and document substandard workmanship or nonconforming products. Describe any ISO or AS9100C certifications.

c. The Offeror shall identify the failure resolution process to be applied to identify/document failure root cause analysis.

d. The Offeror shall identify how root cause analysis and reporting will be conducted during each phase and for each product identified in the SOW.

e. The Offeror shall provide detailed description or process flow diagrams identifying test and inspection points for each functional item, and for test and inspection of the ADC MK 5. The proposal shall demonstrate how production will be accomplished utilizing continuous improvement to reduce manufacturing defects.

3.1.3.3 Sub-factor 3.3 – Subcontracting or Teaming Management

a. If teaming or subcontracting is contemplated, the Offeror shall provide a full description of:

i. The proposed subcontractors or team members, and procedures used for vendor selection.

ii. Method for the selection of subcontractors or team members.

iii. The planned division of tasks with the team.

iv. The benefits to the Government of the teaming agreements.

v. The management structure for coordinating and controlling subcontractors and/or team members.

vi. Subcontracting deliveries to the prime, team deliveries to the prime, surveillance of product quality, and payment tracking and reporting. Controls used to ensure consistent quality and compliant product deliveries from subcontractors.

b. A copy of any Teaming Arrangement shall be provided in an appendix.

3.1.3.4 Sub-factor 3.4 – Small Business Participation

a. The Offeror shall submit a written proposed subcontracting plan in accordance with the clause entitled “SMALL BUSINESS SUBCONTRACTING PLAN” (FAR 52.219-9).

b. The Offeror shall describe the extent to which its company has identified and committed to provide for participation by small business, including veteran-owned small business, service-disabled small business, HUBZone small business, small disadvantaged business (SDB), women-owned small business, and historically black colleges and universities, and minority institutions for the performance of this contract. Of special interest is the amount and type of work to be performed by the subcontractors.

c. For Small Businesses proposing as Prime Contractors, information relative to the overall breakout to subcontracting partners is required under this section.

d. The Offeror shall provide sufficient information to demonstrate that the tasks assigned to the aforementioned businesses and institutions are meaningful, technical, and/or sustainable.

e. The plan shall include the Congressionally mandated five percent (5%) goal for small disadvantaged business concerns.

3.1.4 Factor 4.0 – Past Performance

The Offeror shall demonstrate, through its use of previously developed similar technologies, the Offeror’s ability to meet the design, development, testing, and production requirements of this Solicitation. The Government will assess the Offeror’s and the Offeror’s significant subcontractors’ performance on previous contracts of similar type and complexity to the work required herein. For the purposes of this proposal, a significant subcontractor is defined as one whose effort is proposed to be 10 percent or greater of the total proposed contract value. Assessment of the Offeror’s past performance will be one means of evaluating the credibility of the Offeror’s proposal and relative capability to meet performance requirements. The Government’s evaluation of Past Performance will consist of a review of past performance information to determine, among other areas, the Offeror’s: quality of product or service, cost management /cost control, delivery to schedule, management, and customer relations/customer satisfaction.

Offerors are advised that in evaluating an Offeror’s past performance, the Government may, in its sole discretion, consider information from sources outside the Offeror’s proposal. For example, the Government may consider information based on its own experience with the Offeror and/or may contact the parties for whom the Offeror performed contracts and consider their response when evaluating the Offeror’s proposal. The Government intends to review Contract Performance Assessment Reporting System (CPARS) ratings on relevant contracts, regulatory agency databases, past performance questionnaires, information submitted by each Offeror with its proposal, and other existing past performance information contained in either local or other supervisor files, or from other Government sources or non-Government sources. The Government reserves the right to use any such information received as part of its evaluation of the Offeror’s past performance. The Government reserves the right to directly solicit input on the Offeror’s past performance from other sources and the Government may use any other data available to its evaluators, including the personal knowledge of those individuals; and if the Offeror omits projects of which the Government evaluation team is aware of or becomes aware, customer assessments may be sought from the relevant organizations. Any information obtained will be used for both the responsibility determination and the best value decision. General trends in a Offeror’s performance may also be considered.

The Offeror shall submit at least three (3) and up to five (5) descriptions of previous Government contracts (most recent prime and significant subcontracts received, or in performance, during the past three (3) to five (5) years) each in excess of $15M as the Prime or $5M as the subcontractor, which are most relevant to the effort required by this solicitation. The Offeror shall provide information, which depicts its (and any significant subcontractors’) depth of experience and qualification under similar contracts that have helped to establish its management and technical capability for the scope of work for this RFP. The Government will also consider such factors as performance quality and schedule timeliness. The Offeror shall place particular emphasis on both recent (past three (3) to five (5) years) and current on-going efforts. Commercial or state and local contracts may be included if necessary. The description shall include the following information in the following format:

a. The Offeror’s (and/or subcontractor’s) CAGE and DUNS numbers.

b. Government or commercial contracting activity, address, and telephone number.

c. Procuring Contracting Officer’s (PCO’s) name and telephone number.

d. Government or commercial contracting activity technical representative, or COR, and telephone number.

e. Government or commercial contract administration activity, and the name and telephone number of the

Administrative Contracting Officer (ACO).

f. A description as to whether the Offeror was the prime or a subcontractor on the effort

g. Contract Number.

h. Contract award Date.

i. Contract type.

j. Awarded Cost/Price.

k. Final, or projected final, Cost/Price.

l. Original and Final or projected final, delivery schedule.

m. Identify in specific detail for each previous contract listed, why or how the Offeror considers the effort relevant or similar to the effort required by this solicitation.

n. The Offeror shall provide a self-assessment of performance under each contract identified. The self-assessment shall address:

1. Quality of the services provided;

2. Schedule delivery performance;

3. Cost control measures utilized;

4. Customer satisfaction;

5. A summary of all award fee scores (if any) received on these contracts;

6. The degree to which the Offeror managed the impact of changing requirements and evolving technology on the system’s ability to continue to satisfy improved capabilities over time;

7. All cost growth, quality problems, labor problems and facility problems experienced on these contracts. The Offeror shall demonstrate how it was able to resolve (or why it could not resolve) special or unexplained problems as well as difficulties in meeting performance or cost parameters;

8. Any quality awards or recognition received;

9. Whether any changes were negotiated which relieved the Offeror from the scope of any of the originally awarded contract work.

o. For any Government contracts that did not or do not meet original requirements with regard to either cost, schedule or technical performance, provide a brief explanation of the reason(s) for such shortcomings and any demonstrated corrective actions taken to avoid recurrence. The Offeror shall also provide a copy of any cure notices or show cause letters received on each previous contract listed and a description of any corrective action by the Offeror or proposed subcontractor.

p. The Offeror shall also provide the above required information for any and all contracts where, as a prime contractor or subcontractor, it has been terminated in whole or in part, for default or cause during the past ten (10) years, to include those currently in the process of such termination as well as those which are not similar to the proposed effort. The Offeror shall list each time the delivery schedule was revised and provide an explanation of why the revision was necessary.

q. New corporate entities may submit data on prior contracts involving its officers and employees.

However, in addition to the other requirements in this section, the Offeror shall describe in detail the role performed by such persons in the prior contracts cited.

r. The Offeror shall be concise and specific in detailing past performance in design, development, testing, evaluation, production, and maintenance activities with elements of similar naval systems.

3.2 VOLUME II: COST/PRICE PROPOSAL

The cost/price volume shall demonstrate a complete understanding of the effort necessary to perform this planned contract. Sufficient supporting data shall be provided to permit the Government to perform a review and analysis of the proposed contract line items. The cost/price volume of the proposal shall present the Offeror’s understanding of the solicitation’s requirements and the Offeror’s ability to organize and execute the contract efficiently.

An Offeror's proposal is presumed to represent the Offeror's best efforts to respond to the solicitation. Furthermore, the systems that are priced in the Cost/Price Volume must be consistent with the systems described in the technical volume of the proposal. The Offeror’s proposal shall demonstrate that the unit prices and the total proposed cost is realistic and commensurate with the work required by the solicitation and the technical and management approaches identified in the Technical Volume of the proposal. Show traceability with the CLINS, the SOW, proposed effort, proposed manning levels, and the prices/costs. Refer to specific sections in the Technical Volume as needed to illustrate the consistency between the Price/Cost Volume and the Technical Volume. The Offeror shall explain any inconsistency between promised performance and price/cost, as well as any appearance of unbalanced pricing, in the proposal. Inconsistency, if unexplained, raises a fundamental issue of the Offeror's understanding of the nature and scope of the work required and its ability to perform the contract.

All pricing information submitted in response to this RFP is for the exclusive use of Government representatives.

The information shall be marked "COST BREAKDOWN – NOT TO BE PUBLICLY DISCLOSED."

This volume shall consist of the following and is not subject to any page limitations:

PageNo.