N00024-17-R-5152-0004_Conformed.pdf

N0002416NR41773

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 reason for Amendmnet 0004 is to update section L 1.4 Proposal Delivery Information.

1. CONTRACT ID CODE PAGE OF PAGES

V 1 61

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

16C. DATE SIGNED

BY 30-Nov-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 N0002417R5152

X 9B. DATED (SEE ITEM 11)

04-Aug-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, 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

30-Nov-2017

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:

N0002417R5152

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 - TABLE OF CONTENT

SECTION TITLE PAGE

SECTION L - TABLE OF CONTENT 2

SECTION L – SPECIFIC INFORMATION FOR PREPARATION OF

PROPOSAL 5

1.0 GENERAL 5

2.0 CONTENTS OF THE OFFER 9

3.0 PROPOSAL REQUIREMENTS 11

1.1 Use of Navy Support Contractors 6

1.2 Point of Contact 7

1.3 Solicitation Security Classification 8

1.4 Proposal Delivery Information 8

1.5 Packing Instructions 9

4.0 PROPOSAL: VOLUMES I THROUGH VIII 17

4.1.1 ACB 20 Integration with Hardware Technology Insertion 16 (HTI-16) (CLIN 1000) Technical Approach 17

4.1.2 Software Adaptation to HTI-12 (CLIN 1001) Technical Approach 20

4.1.3 Software Adaptation to HTI-12H (CLIN 1002) Technical Approach 20

4.1.4 Software Adaptation to HTI-16TR (CLIN 1003) Technical Approach 20

4.1.5 LOE Task Technical Capabilities and Corporate Experience (CLIN 0010- 0059) 21

4.1.6 Sample Problems 22

4.1.6.1 Sample Problem 1. SSDS Integrated Combat System (ICS) Advanced Electro-Optical InfraRed (EO/IR) Sensor Integration 22

4.1.6.2 Sample Problem 2. SSDS ICS Cybersecurity for Rogue Nodes 23

4.1.6.3 Sample Problem 3. SSDS ICS Notional Electronic Warfare (EW) Interoperability Upgrade 24

4.1.7 Staffing Plan and Key Personnel 25

4.3.1 System Engineering Management Plan (SEMP) (MS Word) 30

4.3.2 Software Development Plan (SDP) (MS Word) 30

4.3.3 Risk Management Plan (RMP) (MS Word) 31

4.3.4 Program Protection Implementation Plan (PPIP) (MS Word) 31

4.3.5 Contract-wide Quality Assurance Program Plan (MS Word) 31

4.3.6 Contract-wide Integrated Master Schedule (MS Project) 32

4.3.7 Contract-wide Contract Work Breakdown Structure (CWBS) (MS Excel) 32

4.3.8 Contract-wide Staffing Plan (MS Excel) 33

3.1 Solicitation Response Requirements 12

3.2 Cross-Reference Matrix 15

3.3 Glossary of Abbreviations and Acronyms 16

3.4 Summary 16

4.1 VOLUME I: Technical Approach (Technical Factor) 17

4.2 VOLUME II: Data Rights 26

4.3 VOLUME III: Supplemental Information (Technical Factor) 29

4.3.9 Key Personnel Resumes and Letters of Intent 33

4.3.10 Completion CLIN Attachments 34

4.3.10.1 Build Plan 34

4.3.10.2 Preliminary SCN 34

4.3.10.3 Basis of Estimates (BOEs) 35

4.3.10.3.1 Software Estimating (ESLOC) 38

4.3.11 Investment 38

4.3.12 Small Business 39

4.3.13 Program Management Plan (PMP) 39

4.4.1 Management Plan 40

4.4.2 Management Process 40

4.4.3 Subcontractor Management 40

4.6.1 Volume VI.1: Completed Section B (Prime Offeror only) 42

4.6.2 Volume VI.2: Cost and Software Data Reporting 42

4.6.3 Volume VI.3: Total Cost/Price Build Up 42

4.6.4 Volume VI.4: Substantiating Cost Narrative and Information 44

4.6.5 Volume VI.5: Investment (if applicable) 46

4.8.1 Supplemental Information Concerning Teaming Agreements 50

4.8.2 Rights in Noncommercial TD, Noncommercial CS, and Noncommercial CSD51

4.8.3 Rights in Commercial TD, Commercial CS, and Commercial CSD. 52

4.8.4 Rights in Background Inventions. 52

APPENDIX 1 TO SECTION L - PREVIOUS CONTRACT INFORMATION54

COMMANDER 54

4.4 VOLUME IV: Management Approach (Management Factor) 40

4.5 VOLUME V: Past Performance 40

4.6 VOLUME VI: Total Cost/Price (Price Factor) 41

4.7 VOLUME VII: Classified Annexes 50

4.8 VOLUME VIII: Other Proposal Items 50

APPENDIX 2 TO SECTION L – GOVERNMENT ESTIMATED LABOR

MIX (LOE CLINS) 56

APPENDIX 3 TO SECTION L – LABOR CATEGORY DEFINITIONS 57

APPENDIX 4 TO SECTION L – SAMPLE STAFFING PLAN 60

APPENDIX 5 TO SECTION L – TOTAL COST/PRICE BUILD UP 61

SECTION L – SPECIFIC INFORMATION FOR PREPARATION OF PROPOSAL

1.0 GENERAL

Offerors 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 removed 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 herein.

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

https://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. Access to Bidder Library materials is through the information and processes provided in the CSEA NSERC TOUA file on FEDBIZOPPS and Section J, Attachment 11.

Offerors may electronically submit written questions requesting clarification of solicitation requirements by sending an email to Michelle Greene, michelle.a.greene@navy.mil and Courtney Ryan, courtney.ryan@navy.mil. All such questions should be received in writing within ten (10) 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. Questions received after the time set https://www.fbo.gov/ forth above will not result in an extension to the proposal due date. It is the Government’s intention that questions and responses will be distributed to all Offerors via RFP amendment(s). Information provided with each question should include the document name, document date, specific page, paragraph, clause or other definitive citation requiring clarification. Questions concerning classified attachments shall be submitted in accordance with the DD Form 254 and the DoD 5220.22M NISPOM. NAVSEA will answer all non-classified questions (publishing both the question and the answer) via Federal Business Opportunities (FBO) at http://www.fbo.gov. Questions and answers can be accessed via fbo.gov by following the link “Opportunities” and entering keyword/solicitation # for “N00024-17-R-5152” in the box. Company-specific information will be omitted from all questions and answers.

Access to classified and other restricted information being made available to this solicitation can be obtained by submitting a written request to the Contract Specialist Courtney Ryan at Courtney.ryan@navy.mil. The written request must include data on the company facility and identify a classified point of contact (POC). The classified POC shall be responsible for keeping a classified access personnel registry, auditable by the Government. The Offeror’s classified POC shall submit a written request containing the following: facility security clearance level, issuing Government agency, and expiration date; facility security office phone/fax numbers;

facility storage level, cage code, and complete destination address’ personnel for whom access to classified data is requested to include full name; security clearance level, issuing Government agency, and expiration date; date of birth; and city/state of birth. Once a prospective Offeror’s classified POC’s “need-to-know” and security clearance is verified, classified information will be provided. Access to these materials will be granted solely for the purpose of preparing a proposal under this solicitation, and does not establish a common “need-to-know” with any other program, contract, or effort.

Please note that pursuant to FAR 52.215-1, the Government intends to award a contract on the basis of proposal submission without conducting discussions with Offerors, but reserves the right to conduct discussions in accordance with FAR 15.306 if determined by the Contracting Officer to be necessary [see paragraph (4) of FAR 52.215-1(f)]. Each Offeror shall submit only one proposal which represents its best approach to meeting the requirements of the solicitation.

Offerors are permitted to propose both as a Prime contractor and also as a major subcontractor on a competing offer. However, Offerors are required to adhere to all statutes and regulations, including FAR Part 3 and anti-trust laws. No alternate proposals will be accepted. Therefore, the Offeror’s proposal submissions shall contain the Offeror’s best terms from a cost/price and technical standpoint. The Government reserves the right to conduct discussions if the Procuring Contracting Officer determines them to be necessary. The proposal submissions will have requirements for originals (paper), hardcopy (paper) and ‘Electronic Media’ (DVD-R or DVD+R), as detailed in subsequent paragraphs.

1.1 Use of Navy Support Contractors

Government Support Contractors may assist the Source Selection Organization. The Source Selection Advisory Council (SSAC), Source Selection Evaluation Board (SSEB), and Cost/Price http://www.fbo.gov/

Analysis Team (CPAT) will be composed of Government employees. The Government Support Contractors may participate as Advisors to the Source Selection Organization and/or as administrative support.

The following firms may assist in the technical proposal evaluation process in an advisory capacity only and may provide administrative support to the source selection process, but will not evaluate proposals:

COMPANY NAME AREA(S) OF EXPERTISE TO BE USED

Johns Hopkins University Applied Physics Lab Combat System Performance Quantitative Modeling and Analysis

For contact information for the contractors listed above, contact:

Courtney Ryan

SEA 02513R

TEL: (202) 781-4158

Email: courtney.ryan@navy.mil

NAVSEA presently has organizational conflict of interest clauses as well as proprietary data protection clauses in the Navy’s contract with these contractors. Please provide written notification to the PCO no later than thirty (30) calendar days after issuance of the RFP stating the Offeror consents or does not consent to the use of each of the contractors listed above in the proposal evaluation process. Submission of a proposal without such objection will be considered as consent to the specified use of each of the firms listed above.

1.2 Point of Contact

The Procuring Contracting Officer is the sole point of contact for this acquisition; however, the following Contract Specialist may be designated to contact Industry on the Procuring Contracting Officer’s behalf: Courtney Ryan, courtney.ryan@navy.mil.

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

1.3 Solicitation Security Classification

The solicitation is unclassified, although some information provided in conjunction with this solicitation may be classified. All employees of the Offeror working on the classified portion of its proposal shall have active SECRET clearances or above. Offerors are required to provide a copy of a properly executed DD 254 form, in order to gain access to and handle Secret//NOFORN materials. Classified responses are allowed, but offerors shall provide all classified information (i.e., Classified Annexes) in Volume VII (see 3.1 below for all proposal Volume requirements) and refer to it when necessary. The use of coded pointers such as “c1”, “c2” or other means should be employed when feasible to keep the bulk of the proposal content unclassified and legible. Note the Classified Annex will count as a part of the proposal and be subject to the volume page limitations, and it is the responsibility of the Offeror to ensure classified data handling does not impact successful delivery of the proposal within the due date as prescribed. OFFERORS SHALL NOT PLACE ANY CLASSIFIED INFORMATION IN

ANY PORTION OF ITS PROPOSAL OTHER THAN THE CLASSIFIED ANNEXES

(VOLUME VII).

1.4 Proposal Delivery Information

Although NAVSEA will make the RFP and amendments available electronically on the INTERNET, proposals in response to this RFP WILL NOT be accepted via electronic transmission. Only hard-copy (including specified Electronic Media copies) proposals submitted in accordance with Section L of this RFP will be accepted. Any proposals received electronically will be deleted and will not be available for NAVSEA review or consideration.

Responses not received at the place and time specified in Block 9 of the Standard Form 33 will be considered late, as defined by FAR 52.215-1. Responses and response modifications shall not be faxed or e-mailed. Responses and response modifications (which will only be accepted prior to the deadline date for receipt of responses) shall be submitted in sealed envelopes or packages to the address shown below and marked with the following information on the outer wrapper.

Offerors should include the Offeror’s name and return address, the address shown below, the solicitation number, and a statement that “Source Selection Materials Contained Inside – DO

NOT OPEN IN MAIL ROOM.”

SUBMISSION OF PROPOSALS: All copies of the proposal (Volumes I through VIII) shall be submitted to the PCO or Contract Specialist at the address below by 11:00 a.m. local time for the Naval Sea Systems Command on the proposal due dates. NAVSEA will not accept electronic submission of proposals.

Commander, Naval Sea Systems Command Department of the Navy ATTN: Michelle Greene, SEA02513 17214 Avenue B, Suite 130 Dahlgren, VA 22448-5147

All offers shall be hand carried. All offers shall be delivered in accordance with the following:

(a) Offerors hand carrying proposals shall call the contracting officer or contract specialist at least 48 hours prior to arriving at the address above to make arrangements. Packages should not be sealed as they are subject to inspection. Classified material shall be prepared in accordance with current security requirements. The contracting officer or contract specialist may receive the proposal and provide the offeror a receipt with the time and date of delivery.

(b) All offerors shall mark each RFP package with the name of the contracting officer and the contract specialist, their codes and phone numbers. In the event you have not been provided with this information contact the person listed in block 5 of the SF 26 or block 7 of the SF 33.

1.5 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 media 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. These packing instructions also apply to all subcontractor submissions.

The Offeror is responsible for the condition of its delivered proposal and bears the burden if the Government misunderstands the Offeror’s proposal because the binders were damaged in transit.

The Government is not responsible for proper reassembly of binders and their contents that are broken apart or received in a disorderly fashion. The Government is not responsible for proper reassembly of these binders. Thus binders may not be reassembled as originally sent. If there are any discrepancies between the proposal volume hardcopies and the proposal volume Electronic Media (i.e. DVD), the electronic submission shall take precedence.

2.0 CONTENTS OF THE OFFER

The offer consists of and must include the following:

a. Standard Form 33, “Solicitation, Offer and Award,” with blocks 13 through 18 completed by the Offeror and submitted in Volume VI. (Note - This information is exempt from the font and spacing requirements identified under paragraph 3.1 below).

b. Small Business Subcontracting Plan. The Offeror’s attention is directed to Section I clauses FAR 52.219-9 and DFARS 252.219-7003 entitled “Small Business Subcontracting Plan” and FAR 52.219-16 entitled “Liquidated Damages – Small Business Subcontracting Plan.” As prescribed in FAR 19.708, Offerors other than small business concerns shall submit a subcontracting plan as part of Volume III and that plan, once approved, shall be made part of any contract resulting from this solicitation. In accordance with DFARS Part 219.708(B), the government will include DFARS clause 252.219-7004, Small Business Subcontracting Plan (Test Program) in response to this solicitation. (Note - This information is exempt from the font and spacing requirements identified under paragraph 3.1 below).

c. Technical Approach, Data Rights, Supplemental Information, Management Approach, and Past Performance Volumes. Offerors shall submit their hardcopies and Electronic media copies of their Technical Approach, Data Rights, Supplemental Information, Management Approach, and Past Performance Volumes. Offerors shall submit the Past Performance information in the format specified.

d. Basis of Estimates (Electronic Submittal Only)

e. Total Cost/Price Proposal Volume: Offerors shall submit cost information required in Volume VI.

f. Other Proposal Items Volume: Offerors shall submit other non-technical information required in Volume VIII.

g. RFP Sections A through K “Solicitation, Offer and Award”: Offerors must fill in all areas of the RFP listed as Offeror fill-ins, including proposed costs and fees for each line item in Section B. Offeror must complete “Representation, Certifications and Other Statements of Offerors” in Section K. These proposal materials are to be submitted in Volume VI. (Note - This information is exempt from the font and spacing requirements identified under paragraph 3.1 below).

h. Offeror’s Statement: Offerors shall include a signed statement, on the company’s letterhead, stating the accompanying Proposal. The Offeror’s statement shall be submitted in Volume VI. (Note - This information is exempt from the font and spacing requirements identified under paragraph 3.1 below):

1. Is for all requirements as stated in the solicitation (including all attachments, appendices, and amendments thereto),

2. Is made without qualification or exception to any terms and conditions appearing in the solicitation; and

3. Is valid for a period of three hundred and sixty (360) days from the date established for the receipt of proposals.

In addition, the Statement must contain the following certification regarding the classified and other restricted information made available through NSERC/SharePoint, or via the contract specialist:

I, [insert signatory’s name, title, company], hereby certify that [company] will ensure that, if [company] is excluded from the competitive range or not selected for award of this contract, any and all copies, notes, or other materials produced using the classified or other restricted information provided in connection with solicitation N00024-17-R-5251, will be destroyed within one hundred and twenty

(120) days from receipt of notice that [company] was excluded from the competitive range or not selected for award of under this solicitation.

3.0 PROPOSAL REQUIREMENTS

This section delineates general information and requirements to be followed in the preparation of the offeror’s proposal. If an offeror fails to comply with the content requirements, this will be considered during evaluation and may result in a lower evaluated rating or ineligibility for award.

An offeror’s proposal shall be sufficiently detailed to enable Government evaluation board members to make a thorough evaluation against specific factors established in Section M, 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. Discussions of each topic in the proposal shall exhibit continuity and logical progression. Data shall be organized to enable Government personnel to thoroughly evaluate the proposal. A concise, legible, neat, orderly and comprehensive proposal is required. Elaborate brochures, artwork, expensive paper and bindings, or expensive visual or other presentation aids beyond those sufficient to present a complete and comprehensive written proposal are not desired.

An offeror’s proposal shall be so specific, detailed and complete as to clearly demonstrate the offeror has a thorough comprehension of the total technical requirements, including compliance with System Specifications, the Statement of Work (SOW), and all other requirements contained in the solicitation. Offerors should assume 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 (e.g., data or services previously submitted or performed for the Government), cannot be considered as part of the proposal unless physically incorporated into 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.

General statements such as that the Offeror: “can or will comply with the requirements,” “standard procedures will be used,” “well known techniques will be used,” or statements that paraphrase the Statement of Work (SOW) for the SSDS effort, (hereafter referred to as the SOW), the SSDS ICS Requirements Document (hereafter referred to as the SIRD) in whole or in part will be considered inadequate and do not demonstrate or constitute compliance with these requirements concerning the content of the technical proposals. Failure to conform to the requirements of this RFP may form the basis to reject the proposal.

The Offeror’s proposal must contain a precise description of all terms and conditions of the Offeror’s proposal and must address all topics described below. Each volume of the proposal shall be self-contained. The information provided in the proposal shall appear in the same volume order as listed below.

3.1 Solicitation Response Requirements

The solicitation response will be contained in eight (8) separate volumes as follows:

I. Technical Approach II. Data Rights III. Supplemental Information IV. Management Proposal V. Past Performance VI. Price Proposal VII. Classified Annex VIII. Other Proposal Items

For each volume, the number of copies required and the page limits are shown in the table below.

Volume Title Page Limit Original (Paper)

Additional Copies (Paper)

MS Office or other electronic file(s) (Electronic

Media*) I Technical Approach 200 1 2 5

II Data Rights 5 1 2 5

III Supplemental Information None 1 2 5

IV Management Approach 30 1 2 5

V Past Performance 15 1 2 5 VI Total Cost/Price None 1 2 5 VII Classified Annex Pages Applicable to Each Volume Are Counted

Against the Page Limit for that

Volume

1 2 5

VIII Other Proposal Items

None 1 2 5

Each proposal shall be bound separately into eight (8) volumes, and shall not exceed the page limitation cited above. Pages in excess of the applicable page limit will not be read or evaluated, and will be removed by the Procuring Contracting Officer from the back of the respective volume prior to evaluation. In presenting material in these volumes, offerors are advised that the quality of information is significantly more important than quantity. It is not necessary to supply the maximum number of pages allowed for each volume; fewer pages may be submitted. Index pages and tabs are required and shall be cross referenced to the table of contents. All pages within volumes shall be consecutively numbered within each volume (e.g., Volume I-1, Volume

I-2, Volume I-3, etc.) Sectional page numbering is allowed for volumes with no page limit.

Each volume shall contain a glossary of abbreviations used, with an explanation of each. The information and format of the proposal shall be identical on electronic copies (i.e. DVD) and hard copy submissions. If there is a discrepancy between the hardcopy submission and the electronic copy (i.e. DVD), the electronic submission shall take precedence. Cost/Price information shall be completely omitted from the technical proposal volumes.

The narrative material in the written and price proposal volumes of an offeror’s 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 by 11 inch paper. Text line spacing shall be 1.5 lines, with a minimum of one (1)-inch page margins around the page. Text within tables, diagrams, pictorial charts, or graphic material may use single-space 8-point fonts that are legible on printed pages of the paper size specified in this solicitation.

Fold out pages may be used for diagrams, charts or graphic material only and may not exceed 11 inches by 17 inches. Fold out pages will be counted as two (2) pages. Foldouts for the entire proposal are limited to a total of twenty (20). Foldouts for the Integrated Master Schedule, described in Section L-4.3.6; SLOC Table, Attachment J-24; and CSEA Cost Table, Appendix 5 to Section L do not count against the twenty (20) foldout page limits. Fold out pages may only include narrative sufficient to describe the diagram, chart or graphic material. Every paragraph, figure, and table shall be numbered.

A date shall be placed on each page of the proposal corresponding to the date of the initial proposal.

The proposal shall be accompanied by a cover letter prepared on the company's letterhead stationery. The cover letter shall state that the proposal is valid for three hundred and sixty

(360) days, identify the Offeror’s Cage Code; DUNS Number; all enclosures being transmitted;

state the facility’s level of approved security clearance; clearance level of storage capability;

address of the cognizant security office, name of the security representative, and address(es) of the location(s) at which the Offeror intends to perform the proposed effort including subcontractors. The cover letter is not subject to the page limits and the Government will review it to make sure it contains the preceding information. The cover letter shall be submitted with the Price Proposal Volume VI.

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, cross reference matrix, glossary of abbreviations and acronyms, index, and lists of tables which may be combined with illustrations. 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, will be numbered. If the proposal exceeds the page limit identified, the Government will remove all pages exceeding the specified page count from the back of the proposal volume prior to the evaluation.

The Offeror shall submit the volumes in both hardcopies and as electronic files on Electronic Media. Hardcopies of each volume of the proposal shall be bound in three ring binders with ring size no greater than 4” (O-Ring or D-Ring are acceptable), to permit removal of sections with each major part tabbed. The Technical Approach and Total Cost/Price volumes of the proposal contain a number of individual parts. These shall be labeled with the appropriate volume and section information (e.g. ACB 20 Integration with Hardware Technology Insertion 16 (HTI-16) (CLIN 1000) Technical Approach). The Offeror’s company name shall appear at the top of each page. Legibility, clarity, and compliance with the requirements of the solicitation are essential.

Failure to provide the requested information may adversely affect the Government’s evaluation of the Offeror. The page count shall include all material with printed matter and figures.

Five (5) complete sets of Electronic Media shall be provided, one marked “MASTER” and the others marked “BACKUP.” Electronic proposal submissions and supporting information shall be submitted on DVD-R or DVD+R suitable for reading in a standard PC compatible DVD drive. DVD-RW WILL NOT BE ACCEPTED. All files shall be compatible with Microsoft Office 2010. The electronic files shall be uncompressed, except for PDF files, formatted compatible with Microsoft® Windows 7™ applications; text, spreadsheets, worksheets, or workbooks shall be prepared using Microsoft® Office 2010 compatible applications (i.e., Microsoft® Word ™, Excel ™, and PowerPoint ™ compatible applications). All spreadsheets shall be in Microsoft Excel format such that each mathematical equation utilized for calculations is visible and working. All text shall be in Microsoft Word. All schedules shall be in Microsoft Project. No fields shall be password protected. Offeror shall not embed sound or video files into the electronic files. Graphics, tables, photographs, and other data beyond the capability of Microsoft® Word ™, Microsoft® PowerPoint ™, Microsoft® Excel ™, or not in currently NMCI supported applications may be submitted in Adobe Acrobat format. Electronic cost data sheets must be submitted in Excel. Specific instructions are provided under paragraph 4.6. All submitted files shall conform to Windows and Adobe extensions naming conventions; examples are listed below.

.docx for Microsoft® Word 2010™ compatible files, .xlsx for Microsoft® Excel 2010™ compatible files, .pptx for Microsoft® PowerPoint 2010™ compatible files, and

.mpp for Microsoft® Project 2010™ compatible files, and

.pdf for Adobe® Acrobat XI™ compatible files.

The DVDs shall be labeled to indicate the Offeror’s name, the solicitation number and associated volume numbers. Offerors shall screen all DVDs for computer viruses prior to submittal.

Offerors shall submit Unclassified Volumes I, II, III, IV, V, and VIII on a single DVD-R or DVD+R if possible. Volume VI (Cost) and Volume VII (Classified Annex) shall be provided on a separate Electronic Media DVD-R or DVD+R with appropriate security classification markings. Each Electronic Media shall be labeled as follows:

N00024-17-R-5152 Volume # Offeror Company Name, City, State Offeror POC Offeror POC Phone # Date Format(s) of Files

The cover page of each Proposal Volume shall contain:

• Volume Number and Title (e.g., Volume I – Technical)

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

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

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

UNDER NO CIRCUMSTANCES SHALL CONTRACT COST AND PRICING DATA

BE INCLUDED IN OTHER VOLUMES OTHER THAN VI. In the event that cost and pricing data is included in Volumes I through V, VII, or VIII, the page that has the cost or pricing data shall be removed and not evaluated, inclusive of any content attached to the page containing the cost or pricing data.

In the event that any portion of the proposal is written by anyone who is not a bona fide employee of the firm (e.g., outside proposal development consultants, that are not directly a teammate/subcontractor involved in the proposed effort) submitting the proposal, a certificate to this effect shall be furnished which must be signed by an authorized official of the Offeror and shall indicate the person’s name, employment capacity, firm name, relationship of that firm to the Offeror, and which portion of the proposal was written by that person. This certificate requirement applies to both the prime and any subcontractors. The certification will not count against page count and shall be provided in Volume VIII.

The forwarding letter shall identify all enclosures being transmitted, and shall list all subcontractors identified in the Offeror’s proposal. Forwarding letters are merely instruments for transmitting the submitted proposals; they are not part of the page count and will not be evaluated.

Classified information presented in Volume VII as a supplement to any volume will count towards the page limitation. Classified information shall be classified no higher than SECRET and bound in a red binder if Secret or blue binder if Confidential. Control markings shall be used in the banner line following the classification level to identify special control systems that provide additional access control or physical protection for the information (e.g. SECRET//NOFORN). No unclassified volume will be bound in a red or blue binder. Specific pages and paragraphs that contain proprietary information shall be indicated. Classification markings shall be in accordance with the guidance is provided by the DD Form 254 (Attachment J-03) and the DoD 5220.22M NISPOM.

3.2 Cross-Reference Matrix

Cross referencing between factors within Volumes I-V, or between Volume VII and any other volume, is permitted where its use would conserve space without impairing clarity. The cross-reference matrix shall remain unclassified. However, each factor of Volumes I-V of the proposal shall be written to the greatest extent possible on a stand-alone basis so 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 Offeror’s 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, paragraph, table, or figure for reference. The Government is not responsible for cross referencing information that the Offeror has failed to identify in the appropriate factor. Information required for each factor not found in its designated factor or properly cross referenced will be assumed to have been omitted from the proposal.

The following Cross Reference Matrices shall be provided:

a. Show the tracking of Government solicitation requirements to the Offeror’s proposal (i.e., traceability).

b. Show the relationship between the Classified Annexes and the unclassified volumes

A complete set of Cross Reference Matrices shall be provided in the front of each volume. The RFP cross-reference matrix for each volume must indicate the proposal volume section, subsection, and paragraph, cross-referenced with the appropriate SOW paragraphs, applicable RFP instructions, evaluation criteria, and Contract Data Requirements Lists (CDRLs), as applicable.

3.3 Glossary of Abbreviations and Acronyms

At the end of each volume of the proposal, offerors shall provide a glossary of all abbreviations and acronyms used, with an explanation for each. Glossaries do not count against page limitations for their respective volumes.

3.4 Summary

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

When evaluating an offer, the Government will consider how well the Offeror complied with these instructions. The Government will consider any failure on the part of an Offeror to comply with these instructions to be an indication of how the contractor will comply with contract requirements during contract performance. Therefore, the Government encourages offerors to contact the Contract Specialist via e-mail with copy to the PCO in order to request an explanation of any aspect of these instructions for which the Offeror needs clarification/guidance.

Because National Security is involved, the PCO may request the cognizant security office to verify any or all security information for an offeror at any time prior to award. Such verification shall not be deemed to be “discussions” and shall in no case allow an offeror to revise or change its proposal.

4.0 PROPOSAL: VOLUMES I THROUGH VIII

The proposal Volumes, titles, page distribution, hardcopies required, and other related information are listed below. Maximum page counts are provided for each volume of the proposal and are listed in the table in section L-3.1. Offerors must comply with the submission requirements specified above. Non-conformance with the specified organization, content, and page limitations may result in an unfavorable evaluation of the proposal. The proposal shall be valid for no less than three hundred and sixty (360) days from the required submission date. The award date of this procurement is planned to be February 2019.

4.1 VOLUME I: Technical Approach (Technical Factor)

The Technical Approach Volume shall enable technical/engineering personnel to make a thorough evaluation and arrive at a sound determination of whether or not the proposal meets the requirements of the RFP. To this end, the Technical Volume shall be specific, detailed, and complete technical approach to demonstrate clearly and fully that the Offeror understands the SSDS CSEA contract objectives and has a thorough understanding of the solicitation requirements for, and technologies involved with, and the knowledge to accomplish the SSDS efforts under this solicitation. The Technical Approach Volume must be in sufficient detail to demonstrate how the Offeror proposes to comply with the Government's requirements and include a full explanation of the methodology and procedures to be followed. Additionally, the Offeror must clearly state any and all assumptions made to develop the proposed technical approach, including the use of any GFI or GFP not listed in Attachments J-08 or J-09.

The Government intends for Volume I to be a targeted discussion of the Offeror’s proposed approach to performing each of the CLINs. Therefore, while the Government requires several general plans and processes as well as contract-wide documents in Volume III, these documents must describe a single cohesive technical approach for each CLIN. Therefore, all aspects of the Offeror’s proposed approach shall be consistent with and traceable to the other corresponding aspects. For example, the proposed software coding approach shall be consistent with and traceable to the relevant sections of the Integrated Master Schedule, Staffing Plan, Build Plan, Basis of Estimate, and other related sections. Any inconsistency, whether real or apparent, between any of these documents and the technical approach described in Volume I may indicate a lack of understanding of the requirements or otherwise increase the risk of unsuccessful contract performance.

4.1.1 ACB 20 Integration with Hardware Technology Insertion 16 (HTI-16) (CLIN 1000)

Technical Approach

The Offeror shall describe its technical approach to the development, integration, testing, and fielding of ACB 20 onto the HTI-16 configuration resulting in the SSDS Build 12 configurations incorporating the new capabilities of the Enterprise Air Surveillance Radar (EASR), Evolved Sea Sparrow Missile (ESSM) Block 2, Surface Electronic Warfare Improvement Program (SEWIP) Block 3 integration with the SSDS Element, modifications to integrated training, and modifications to associated Cyber Enhancements to ensure the concepts of cyber resilience, defense in depth, hardening against cyber-attack, cyber situational awareness, and active response to cyber-attack are incorporated into every facet of the system (Section C, Paragraph 3.3.3.1).

The Offeror shall provide details addressing the following ACB 20 Initial Capability Requirements in their technical approach; explicitly specify section, paragraph, table or figure when referencing supplemental information in Volume III:

a. The Offeror shall identify all the critical schedule risk items and technical risks involved in implementing the ACB 20 integration with the HTI-16 Completion Effort. The Offeror shall determine the three (3) most critical schedule risk items and the top three

(3) technical risks to further explain the consequences and mitigations for them. The Offeror shall discuss key elements of its technical approach and activities that would be completed to obtain margin early in critical risk areas (performance, schedule, and budget).

b. The Offeror shall describe how EASR (V)1 and (V)2, and SEWIP Block 3 would change the composite track processing to support an ESSM Block 2 engagement. The Offeror shall discuss their design modification to the existing SSDS composite track processing and proposed changes to the CEC interface.

c. The Offeror shall describe their proposed system architecture with focus on the SSDS element and how this architecture would lend to the development of modular software that can be upgraded, scaled, and modified to easily accommodate future capabilities.

The Offeror shall discuss how their architecture maximizes the similarities and minimizes the differences between integrating the EASR (V)1 and integrating the EASR (V)2.

d. The Offeror shall describe key interface changes, both logical and physical, to the SSDS element for incorporating the ACB 20 capabilities onto the HTI-16 configuration.

e. The Offeror shall identify and explain the use of Government and/or Government-approved models and test beds to support their initial design efforts and then mature that design into its own bench test system. The Offeror shall also explain additional models it plans to use (other than Government GFM), how it will integrate the results of its own models and other models into a complete system model, and how it plans to maintain the system model to support design, development, and test efforts. The Offeror’s plan shall encompass all subcontractor modeling and simulation efforts to provide a single, integrated bench test system and shall address the accreditation of the Offeror’s models.

f. The Offeror shall describe how their approach would enable the delivery of the ACB 20 software with no new defects. The Offeror shall detail their approach to defect control of software products throughout the development. The Offeror shall provide metric evidence of software reliability improvement and quality metrics in terms of build stability prior to delivery. The Offeror shall discuss their recommended metrics to be used to determine software product quality.

g. The Offeror shall describe their approach to ensure the ACB 20 SSDS implementation preserves the ability to compile and build legacy SSDS builds/versions (Build 9 and beyond) from a unified software code base (i.e. software resource library construct) to support deliveries to ships that have not received the ACB 20 build. The result of the Offeror’s approach shall not change the software resource library modules/SCs such that older/legacy systems can no longer be compiled.

h. The Offeror shall detail their test approach that would enable efficiency gains without losing effectiveness in all aspects and stages of testing from unit testing through at-sea testing.

i. The Offeror shall describe its proposed use of Contractor-owned and Government-furnished facilities and test-bed systems and the roles of these facilities (See Section H, 5252.245-9106 FACILITIES TO BE GOVERNMENT-FURNISHED (COST-

REIMBURSEMENT)(SEP 2009), 5252.245-9108 Government-Furnished Property (Performance) (SEP 1990) and 5252.245-9115 Rent-Free Use of Government Property (SEP 1990)). The Offeror shall describe all plans for expansion and retooling to meet the requirements for the SSDS CSEA effort.

a. The Offeror shall provide specific details for equipment and test beds for each phase of the SSDS ACB 20: development, integration, and test. The Offeror shall discuss how they plan to utilize land-based facilities, focused on the use of existing facilities (e.g. Surface Combat Systems Center (SCSC) Wallops Island, Integrated Combat System Test Facility (ICSTF), Self Defense Test Ship (SDTS) or the Distributed Engineering Plant (DEP)) as well as the Contractor provided facilities to aid in combat system development, integration, and testing. The Offeror shall describe contractor use (indicate specific baseline and the level of testing), roles, and installation support (including connectivity, installation, light off, test suites, etc.), at SCSC to support in-service and new ACB development baselines. The Offeror shall identify any equipment required at Government facilities beyond what is identified as Government-furnished in this solicitation.

The Offeror shall describe the procurement timeline of Attachment J-07 “Contractor Acquired Property (CAP) (i.e. commercial hardware and software procurements)” for the software development and test environment.

j. The Offeror shall describe the use of its system security engineering (SSE) process in specifying and designing a system that is protect against external threats and hardware/software vulnerabilities.

a. As a part of describing this SSE process, the Offeror shall describe the criticality analysis process used in their Program Protection Implementation Plan (in Volume III) to determine Mission-Critical Functions and the protection techniques (countermeasures and sub-countermeasures) used to achieve system protection and mission effectiveness.

b. The Offeror shall describe what steps are planned or taken to include system security engineering (SSE) as an integral part of its overall software development approach that will be used to deliver the required system capability.

c. The Offeror shall describe their plan to prevent, detect, and respond to supply chain risk including malicious insertion of malware into the program’s supply chain for critical function components. The Offeror shall describe their approach in coordinating and testing of 3rd-party applications to mitigate software vulnerabilities and detect malicious or dead code during development and throughout the Contractor's Information Assurance Vulnerability Management (IAVM) process that will be developed for inclusion into an ACB.

4.1.2 Software Adaptation to HTI-12 (CLIN 1001) Technical Approach

The Offeror shall provide their technical approach to the integration, testing, fielding and certification of Build 12 to execute on HTI-12 configuration. The Government requires the same insight into the Offeror’s proposed approach to CLIN 1001 as it does to CLIN 1000, but recognizes that much of the information provided in Section L, Paragraph 4.1.1 for CLIN 1000 is equally applicable to CLIN 1001.