N00019-15-R-0081-0005.pdf

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:

1) Extend the proposal due date to 30 November 2015 at 2:00 p.m. local time (Eastern Standard Time)

2) Add NAVAIR Clause 5252.232-9516 (NAVAIR)(JUL 1985) ALT I (OCT 2005) to Section H.

3) Add Clause 252.204-7012 (DEVIATION 2016-O0001)(OCT 2015) to Section I.

4) Address alternate proposals; add SPN-50 funding profile and Offeror's monthly funding profile requirement to Section L.

5) Add Clause 252-204-7008 (DEVIATION 2016-O0001)(OCT 2015) to Section L.

6) Change the mailing address for the delivery of proposals (See Section L 4.1)

1. CONTRACT ID CODE PAGE OF PAGES

1 28

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

16C. DATE SIGNED

BY 14-Oct-2015

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

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

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

X 9B. DATED (SEE ITEM 11)

18-Sep-2015

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer X 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 1 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

14-Oct-2015

CODE

NAVAL AIR SYSTEMS COMMAND

AIR-2.4.1.2 SUITE 256 BLDG 2272

47123 BUSE ROAD UNIT IPT

PATUXENT RIVER MD 20670

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

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

N00019-15-R-0081

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION A - SOLICITATION/CONTRACT FORM

The required response date/time has changed from 04-Nov-2015 02:00 PM to 30-Nov-2015 02:00 PM.

The following have been modified:

CLARIFICATION: SUM OF CHANGES

Clarification and further specification to the Summary of Changes in Section A are as follows:

"The Government has changed this solicitation. For informational purposes, these changes generally appear as track changes. The offeror remains responsible for complying with the solicitation, including all changes whether or not such changes appear as track changes."

252.207-7012 Safeguarding of Unclassified Controlled Technical Information (NOV 2013) has been deleted from the list of cluases incorporated by reference in Section I.

252.204-7012 Safeguarding Covered Defense Information and Cyber Incident Reporting (OCT 2015) has been added by full text in Section I.

252.204-7008 Compliance with Safeguarding Covered Defense Information Controls (OCT 2015) has been added by full text in Section L.

SECTION H - SPECIAL CONTRACT REQUIREMENTS

The following have been added by full text:

5252.232-9516 ALLOTMENT OF FUNDS - INCREMENTALLY FUNDED COST-REIMBURSEMENT

CONTRACT OTHER THAN COST-SHARING CONTRACT (NAVAIR)(JUL 1985) - ALT

I (OCT 2005)

For the purposes of paragraph (b) of the “Limitation of Funds” clause of this contract-

(a) The amount available for payment and allotted to this incrementally funded contract is:

Funded Cost $ TBD

Funded Fee $ TBD

TOTAL FUNDS $ TBD

(b) This contract is incrementally funded and the amount currently available for payment is limited to $to be determined which includes a fixed fee amount of $to be determined. Subject to the provisions of the clause entitled

“Limitation of Funds” (FAR 52.232-22) of the General Provisions of the Contract, no legal liability on the part of the Government for payment in excess of the revised total shall arise unless additional funds are made available and incorporated in a contract modification.

(c) the items covered by such amount are Item(s) TBD; and

(d) the period of performance for which it is estimated the allotted amount will cover is [insert the period of performance (calendar date)].

SECTION I - CONTRACT CLAUSES

252.204-7012

252.204-7012 Safeguarding Covered Defense Information and Cyber Incident Reporting.

As prescribed in 204.7304(c), use the following clause:

SAFEGUARDING COVERED DEFENSE INFORMATION AND CYBER INCIDENT

REPORTING (DEVIATION 2016-O0001)(OCT 2015)

(a) Definitions. As used in this clause—

“Adequate security” means protective measures that are commensurate with the consequences and probability of loss, misuse, or unauthorized access to, or modification of information.

“Compromise” means disclosure of information to unauthorized persons, or a violation of the security policy of a system, in which unauthorized intentional or unintentional disclosure, modification, destruction, or loss of an object, or the copying of information to unauthorized media may have occurred.

“Contractor attributional/proprietary information” means information that identifies the contractor(s), whether directly or indirectly, by the grouping of information that can be traced back to the contractor(s) (e.g., program description, facility locations), personally identifiable information, as well as trade secrets, commercial or financial information, or other commercially sensitive information that is not customarily shared outside of the company.

“Contractor information system” means an information system belonging to, or operated by or for, the Contractor.

“Controlled technical information” means technical information with military or space application that is subject to controls on the access, use, reproduction, modification, performance, display, release, disclosure, or dissemination.

Controlled technical information would meet the criteria, if disseminated, for distribution statements B through F using the criteria set forth in DoD Instruction 5230.24, Distribution Statements on Technical Documents. The term does not include information that is lawfully publicly available without restrictions.

“Covered contractor information system” means an information system that is owned, or operated by or for, a contractor and that processes, stores, or transmits covered defense information.

“Covered defense information” means unclassified information that—

(i) Is—

(A) Provided to the contractor by or on behalf of DoD in connection with the performance of the contract; or

(B) Collected, developed, received, transmitted, used, or stored by or on behalf of the contractor in support of the performance of the contract; and

(ii) Falls in any of the following categories:

(A) Controlled technical information.

(B) Critical information (operations security). Specific facts identified through the Operations

Security process about friendly intentions, capabilities, and activities vitally needed by adversaries for them to plan and act effectively so as to guarantee failure or unacceptable consequences for friendly mission accomplishment

(part of Operations Security process).

(C) Export control. Unclassified information concerning certain items, commodities, technology, software, or other information whose export could reasonably be expected to adversely affect the United

States national security and nonproliferation objectives. To include dual use items; items identified in export administration regulations, international traffic in arms regulations and munitions list; license applications; and sensitive nuclear technology information.

(D) Any other information, marked or otherwise identified in the contract, that requires safeguarding or dissemination controls pursuant to and consistent with law, regulations, and Governmentwide policies (e.g., privacy, proprietary business information).

“Cyber incident” means actions taken through the use of computer networks that result in an actual or potentially adverse effect on an information system and/or the information residing therein.

“Forensic analysis” means the practice of gathering, retaining, and analyzing computerrelated data for investigative purposes in a manner that maintains the integrity of the data.

“Malicious software” means computer software or firmware intended to perform an unauthorized process that will have adverse impact on the confidentiality, integrity, or availability of an information system. This definition includes a virus, worm, Trojan horse, or other code-based entity that infects a host, as well as spyware and some forms of adware.

“Media” means physical devices or writing surfaces including, but is not limited to, magnetic tapes, optical disks, magnetic disks, large-scale integration memory chips, and printouts onto which information is recorded, stored, or printed within an information system.

‘‘Operationally critical support’’ means supplies or services designated by the Government as critical for airlift, sealift, intermodal transportation services, or logistical support that is essential to the mobilization, deployment, or sustainment of the Armed Forces in a contingency operation.

“Rapid(ly) report(ing)” means within 72 hours of discovery of any cyber incident.

“Technical information” means technical data or computer software, as those terms are defined in the clause at

DFARS 252.227-7013, Rights in Technical Data-Non Commercial Items, regardless of whether or not the clause is incorporated in this solicitation or contract. Examples of technical information include research and engineering data, engineering drawings, and associated lists, specifications, standards, process sheets, manuals, technical reports, technical orders, catalog-item identifications, data sets, studies and analyses and related information, and computer software executable code and source code.

(b) Adequate security. The Contractor shall provide adequate security for all covered defense information on all covered contractor information systems that support the performance of work under this contract. To provide adequate security, the Contractor shall—

(1) Implement information systems security protections on all covered contractor information systems including, at a minimum—

(i) For covered contractor information systems that are part of an Information Technology (IT) service or system operated on behalf of the Government—

(A) Cloud computing services shall be subject to the security requirements specified in the clause 252.239-7010, Cloud Computing Services, of this contract; and

(B) Any other such IT service or system (i.e., other than cloud computing) shall be subject to the security requirements specified elsewhere in this contract; or

(ii) For covered contractor information systems that are not part of an IT service or system operated on behalf of the Government and therefore are not subject to the security requirement specified at paragraph (b)(1)(i) of this clause—

(A) The security requirements in National Institute of Standards and Technology (NIST)

Special Publication (SP) 800-171, “Protecting Controlled Unclassified Information in Nonfederal Information

Systems and Organizations,” (see http://dx.doi.org/10.6028/NIST.SP.800-171) that is in effect at the time the solicitation is issued or as authorized by the Contracting Officer with the exception of the derived security requirement 3.5.3 “Use of multifactor authentication for local and network access to privileged accounts and for network access to non-privileged accounts”, which will be required not later than 9 months after award of the contract, if the Contractor notified the contracting officer in accordance with paragraph (c) of the provision 252.204-

7008, Compliance with Safeguarding Covered Defense Information Controls (DEVIATION 2016-O0001)(OCT

2015); or

(B) Alternative but equally effective security measures used to compensate for the inability to satisfy a particular requirement and achieve equivalent protection approved in writing by an authorized representative of the DoD Chief Information Officer (CIO) prior to contract award; and

(2) Apply other information systems security measures when the Contractor reasonably determines that information systems security measures, in addition to those identified in paragraph (b)(1) of this clause, may be required to provide adequate security in a dynamic environment based on an assessed risk or vulnerability.

(c) Cyber incident reporting requirement.

(1) When the Contractor discovers a cyber incident that affects a covered contractor information system or the covered defense information residing therein, or that affects the contractor’s ability to perform the requirements of the contract that are designated as operationally critical support, the Contractor shall—

(i) Conduct a review for evidence of compromise of covered defense information, including, but not limited to, identifying compromised computers, servers, specific data, and user accounts. This review shall also include analyzing covered contractor information system(s) that were part of the cyber incident, as well as other information systems on the Contractor’s network(s), that may have been accessed as a result of the incident in order to identify compromised covered defense information, or that affect the Contractor’s ability to provide operationally critical support; and

(ii) Rapidly report cyber incidents to DoD at http://dibnet.dod.mil.

(2) Cyber incident report. The cyber incident report shall be treated as information created by or for DoD and shall include, at a minimum, the required elements at http://dibnet.dod.mil.

(3) Medium assurance certificate requirement. In order to report cyber incidents in accordance with this clause, the Contractor or subcontractor shall have or acquire a DoD-approved medium assurance certificate to report cyber incidents. For information on obtaining a DoD-approved medium assurance certificate, see http://iase.disa.mil/pki/eca/Pages/index.aspx.

(d) Malicious software. The Contractor or subcontractors that discover and isolate malicious software in connection with a reported cyber incident shall submit the malicious software in accordance with instructions provided by the Contracting Officer.

(e) Media preservation and protection. When a Contractor discovers a cyber incident has occurred, the

Contractor shall preserve and protect images of all known affected information systems identified in paragraph

(c)(1)(i) of this clause and all relevant monitoring/packet capture data for at least 90 days from the submission of the cyber incident report to allow DoD to request the media or decline interest.

(f) Access to additional information or equipment necessary for forensic analysis. Upon request by DoD, the Contractor shall provide DoD with access to additional information or equipment that is necessary to conduct a forensic analysis.

(g) Cyber incident damage assessment activities. If DoD elects to conduct a damage assessment, the

Contracting Officer will request that the Contractor provide all of the damage assessment information gathered in accordance with paragraph (e) of this clause.

(h) DoD safeguarding and use of contractor attributional/proprietary information. The Government shall protect against the unauthorized use or release of information obtained from the contractor (or derived from information obtained from the contractor) under this clause that includes contractor attributional/proprietary information, including such information submitted in accordance with paragraph (c). To the maximum extent practicable, the Contractor shall identify and mark attributional/proprietary information. In making an authorized release of such information, the Government will implement appropriate procedures to minimize the contractor attributional/proprietary information that is included in such authorized release, seeking to include only that information that is necessary for the authorized purpose(s) for which the information is being released.

(i) Use and release of contractor attributional/proprietary information not created by or for DoD.

Information that is obtained from the contractor (or derived from information obtained from the contractor) under this clause that is not created by or for DoD is authorized to be released outside of DoD—

(1) To entities with missions that may be affected by such information;

(2) To entities that may be called upon to assist in the diagnosis, detection, or mitigation of cyber incidents;

(3) To Government entities that conduct counterintelligence or law enforcement investigations;

(4) For national security purposes, including cyber situational awareness and defense purposes

(including with Defense Industrial Base (DIB) participants in the program at 32 CFR part 236); or

(5) To a support services contractor (“recipient”) that is directly supporting Government activities under a contract that includes the clause at 252.204-7009, Limitations on the Use or Disclosure of Third-Party

Contractor Reported Cyber Incident Information.

(j) Use and release of contractor attributional/proprietary information created by or for DoD. Information that is obtained from the contractor (or derived from information obtained from the contractor) under this clause that is created by or for DoD (including the information submitted pursuant to paragraph (c) of this clause) is authorized to be used and released outside of DoD for purposes and activities authorized by paragraph (i) of this clause, and for any other lawful Government purpose or activity, subject to all applicable statutory, regulatory, and policy based restrictions on the Government’s use and release of such information.

(k) The Contractor shall conduct activities under this clause in accordance with applicable laws and regulations on the interception, monitoring, access, use, and disclosure of electronic communications and data.

(l) Other safeguarding or reporting requirements. The safeguarding and cyber incident reporting required by this clause in no way abrogates the Contractor’s responsibility for other safeguarding or cyber incident reporting pertaining to its unclassified information systems as required by other applicable clauses of this contract, or as a result of other applicable U.S. Government statutory or regulatory requirements.

(m) Subcontracts. The Contractor shall—

(1) Include the substance of this clause, including this paragraph (m), in all subcontracts, including subcontracts for commercial items; and

(2) Require subcontractors to rapidly report cyber incidents directly to DoD at http://dibnet.dod.mil and the prime Contractor. This includes providing the incident report number, automatically assigned by DoD, to the prime Contractor (or next higher-tier subcontractor) as soon as practicable.

(End of clause)

The following have been deleted:

252.204-7012 Safeguarding of Unclassified Controlled Technical

Information

NOV 2013

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

252.204-7008

252.204-7008 Compliance with Safeguarding Covered Defense Information Controls.

As prescribed in 204.7304(a), use the following provision:

COMPLIANCE WITH SAFEGUARDING COVERED DEFENSE INFORMATION

CONTROLS (DEVIATION 2016-O0001)(OCT 2015)

(a) Definitions. As used in this provision—

“Controlled technical information,” “covered contractor information system,” and “covered defense information” are defined in clause 252.204-7012, Safeguarding Covered Defense Information and Cyber Incident Reporting

(DEVIATION 2016-O0001)(OCT 2015).

(b) The security requirements required by contract clause 252.204-7012, Safeguarding Covered Defense

Information and Cyber Incident Reporting (DEVIATION 2016-O0001)(OCT 2015) shall be implemented for all covered defense information on all covered contractor information systems that support the performance of this contract.

(c) If the Offeror anticipates that additional time will be necessary to implement derived security requirement 3.5.3 “Use of multifactor authentication for local and network access to privileged accounts and for network access to non-privileged accounts” within National Institute of Standards and Technology (NIST) Special

Publication (SP) 800-171, “Protecting Controlled Unclassified Information in Nonfederal Information Systems and

Organizations (see http://dx.doi.org/10.6028/NIST.SP.800-171), the Offeror shall notify the Contracting Officer that they will implement the requirement within 9 months of contract award.

(d) If the Offeror proposes to deviate from any of the security requirements in NIST SP 800-171that is in effect at the time the solicitation is issued or as authorized by the Contracting Officer, the Offeror shall submit to the

Contracting Officer, for consideration by the DoD Chief Information Officer (CIO), a written explanation of—

(1) Why a particular security requirement is not applicable; or

(2) How an alternative, but equally effective, security measure is used to compensate for the inability to satisfy a particular requirement and achieve equivalent protection.

(e) An authorized representative of the DoD CIO will approve or disapprove offeror requests to deviate from NIST SP 800-171 requirements in writing prior to contract award. Any approved deviation from NIST SP 800-

171 shall be incorporated into the resulting contract.

(End of provision)

The following have been modified:

CONTENTS OF PROPOSAL

PART A - GENERAL INSTRUCTIONS

1.0 GENERAL

Offerors are required to submit a written proposal as part of this solicitation. Offerors shall respond to all requirements in Section L. Do not alter or rearrange the solicitation unless specifically requested. The Offerors are advised that the Government may incorporate into the final contract any part of the Offeror’s proposal deemed beneficial to the Government. No cost information shall be included in the Technical Volume.

Clarity, brevity and logical organization shall be emphasized during proposal preparation. It is the responsibility of the Offeror to present enough information to allow the areas of Section L to be meaningfully evaluated for compliance without discussions. Alternate proposals are not acceptable.

Failure to clearly address a specific factor may cause a proposal to be deemed unacceptable. There is no need to repeat information in more than one volume if an overlap exists. Unnecessarily elaborate brochures or other presentation beyond that sufficient to present a complete and effective proposal is neither necessary nor desired.

Offerors are expected to comply with all requirements of the Request for Proposal (RFP). The Government advises

Offerors that taking exception or deviating from any term or condition of the RFP shall make an offer Unacceptable and the Offeror ineligible for award.

Throughout these instructions, Offeror is defined as the prime contractor with its CAGE/NCAGE code identified in

Block 15A on Standard Form (SF) 33, Solicitation, Offer, and Award. A “Joint Venture” (JV) is a partnership or teaming arrangement that is formed for the purpose of responding to this solicitation when the prime contractor consists of more than one legal entity. A “JV Team Member” is defined as one of the entities that make up a JV or any other partnership or teaming arrangement formed for the purpose of responding to this solicitation. The term

“entity” is used to mean any or all of the following: prime contractor, JV, critical team members, JV team members, any subcontractor, and corporate parent, division, subsidiary, or affiliate (e.g., any contractor with a different

CAGE/NCAGE code/DUNS than the Offeror). A “principal subcontractor” is defined as a subcontractor who provides at least 20% of the proposed total price (excluding the Offeror’s profit/fee) for the contract. “Critical team member” is defined as one of the entities of the Offeror that perform a critical technical function (i.e.

Security/Safeguarding, MAUS inspections and aircraft X-Rays) in the performance of the resulting contract.

The Offeror shall certify, in its proposal cover letter, that all electronic proposal information has been checked and is virus free, and specify the software, version, and virus definition used to check the data. With each subsequent submission of proposal information (e.g., responses to Evaluation Notices, Final Proposal Revisions, etc.), the

Offeror shall ensure and certify that its files are virus free.

The Offeror shall not embed sound or video (e.g., MPEG) files within the proposal submission.

The SPN-50 estimated funding profile by fiscal year is provided in the table below and is for informational purposes only. The offeror is not required to propose in accordance with the funding profile.

2.0 PROPOSAL FORMAT

1) Technical: Proposals must be formatted using a Times New Roman 12 point normal font (no reduction permitted), single-spaced with 1-inch margins all around and formatted for/printed on standard 8.5 x 11 inch paper.

All pages shall be numbered with section and page numbers. When foldout pages are used they must not exceed 11 x 17 inches and will be counted as 1 page. Tables must be formatted using a 10 point normal font (no reducton permitted). Drawings may be provided separately and may be any size but shall be folded to approximately 8.5 x

11 inch standard size and will count as 1 page. Graphs shall be presented in no smaller than a 10 point font and should contain a grid that allows values to be read directly from the graph to the same accuracy that a 10 x 10 to the

½ inch grid provides. Graphic resolution shall be consistent with the purpose of the data presented. Each Volume or Book shall be provided separately in a 3-ring binder. The binders shall be of an appropriate thickness for the number of pages it contains.

The Offeror will provide one complete copy of the proposal to the PCO as electronic files fully compatible with

Microsoft Office 2010 and/or Adobe Acrobat Reader 11.0.10 on a CD-ROM. The Offeror will ensure that the Price

Volume is provided on a separate CD-ROM. If a discrepancy exists between the original paper copy of the proposal and the disk copy, the paper copy will take precedence. Instructions for the format and content of the Cost/Price

Volume are contained in Part B – Specific Instructions, paragraph 2.0 (Volume 2 – Price Proposal).

3.0 PROPOSAL CONTENT AND VOLUMES

General: The Offeror must present its proposal information in a manner that facilitates a one for one comparison between the information presented and this Proposal Instruction. Proposal information must be structured such that the paragraph number/letter is identical to the Proposal Instructions paragraph number to which it is responding, although the Offeror may add lower tier sub paragraphs. Each volume of the proposal shall be submitted as one original and additional copies as specified in the table below. Submission of all volumes of the Original proposal to the address provided in Part A, Section 4.0 (Proposal Submission) will determine timeliness of receipt. Not-to-exceed (NTE) page counts for each volume are specified in the table below as follows (title and table of contents pages do not count towards page limit).

Volume Number Volume Title Suggested Page

Count

Copies Required

Vol 1 TECHNICAL - Schedule (IMS), Key System Performance

Requirements, Small Business

Strategy

100 Pages

(Supporting data, such as test data, operating curves, tables, plots, or substantiating data for the

Performance model is not included in the

100 page count)

1 Original/7 Copies

Vol 2 Cost/Price No limit 1 Original/2 Copies

Vol 3 Executive Summary 10 Pages 1 Original/2 Copies

Each volume must contain the following information:

Cover and title page

Title of proposal and proposal number as applicable

Offeror’s name, address and POC

RFP number

Proposal volume/book number

Copy number

Table of Contents (The table of contents must provide sufficient detail to enable easy location of important elements)

Use tabs and dividers

The Cross Reference Matrix (CRM), required for the Technical volume and as needed for other volumes, is provided below as guidance to help ensure that all requirements are addressed, are easily accessible to the evaluators, and to facilitate the Offeror’s completion of the CRM of its proposal. The Offeror’s CRM shall provide a single integrated matrix. The Offeror’s CRM shall cross-reference its proposal volumes and paragraphs to specific

RFP requirements, as well as other parts of the proposal that contain relevant information. The CRM shall be provided, as a minimum, in the Technical proposal volume and is not included in the NTE page count. The

Offeror’s CRM may be identical to the one provided or revised to add columns to indicate the page number on which information may be found, identify where other relevant information in the proposal is located, or provide other comments. Areas indicated with shaded gray do not require separate write-up and are for identification of section only.

CROSS REFERENCE MATRIX (CRM) for Technical Volume 1

Volume Sect L

Para

Title of Annex Government

SOW

SATR System

Spec

Sec M

Criteria

Government

Referenced

Attachments

Technical

(Volume 1)

1.1 Integrated Master

Schedule

5.2 N/A IIA Section J, Attachment 1

1.2 Key System

Performance

Requirements

N/A .2.1, .2.2.1.1, .2.2.1.2, .2.2.1.3, .2.3.1, .2.3.2, .2.4, .2.4.1, .2.4.2, .2.5.4., .2.5.5, .2.5.6,.2.5.7, .2.8.1, .2.9.2, .2.9.2.1, .2.9.2.2, .2.9.2.3 .7.2, .7.2.1, .7.2.2, .7.2.3, 7.3, .7.4, .7.4.1, .7.4.2, .8.2, .8.2.1, .8.2.2, .8.2.3, .8.2.4, .8.2.5, and

.8.2.6

IA, IIA Section J, Attachment 2

4.0 PROPOSAL SUBMISSION

Clearly mark all packages with the solicitation number. The submission date for all Volumes shall be no later than the date and time specified in Block 9 of Standard Form 33 of the RFP.

4.1 Unclassified Data

Method of delivery, such as by hand, United States Postal Service or commercial carrier, shall be coordinated with the Procuring Contracting Office (PCO) and/or contract specialist listed below. Proposals shall be submitted using the address provided below. Initial and Final Proposals shall not be submitted by facsimile or electronically via email.

Contract Specialist

AIR 2.2.4.1.5 Mrs. Virginia Perry-Aldridge

(301) 342-9920 virginia.perry-aldri@navy.mil

Contracting Officer

AIR-2.2.1.2 Mr. William D. Gentry

(301) 757-7069 william.gentry@navy.mil mailto:Benjamin.Washburn@navy.mil

Naval Air Systems Command

(ATTN: Mr. William D. Gentry / Mrs. Virginia Perry-Aldridge)

Solicitation Number: N00019-15-R-0081

Building 460

Floor 1

Room 107

Patuxent River, MD 20670

5.0 PROPOSAL PACKAGING

The Offerors shall package the proposal volumes in cartons or equivalent packaging containers in the most efficient manner possible grouping like volumes to the maximum extent possible. Also each carton shall be single person portable. However, the Master Set, as described below, shall be packaged separately and marked as the Master Set.

Each box shall identify its contents by including a packing slip detailing the requirement, each volume number and title and copy number. Also, each box shall be stamped or marked “For Official Use Only” and “Source Selection

Information – See FAR-2.101 and 3.104.”

The Master Set shall include all original proposal volumes, all proposal volumes on CD-ROM, a completed and original signed Standard Form 33; acknowledgement of all solicitation amendments, if applicable; and

Representations, Certifications and Other Statements of Offerors (Section K of this RFP) and other applicable fill-ins.

6.0 TECHNICAL LIBRARY/DATA

(1) Technical Library

A Technical Library of information directly related to the requirements of this contract will be provided in a

Compact Disc media format with the RFP (or emailed directly), upon request.

To request electronic copies of the solicitation materials, contact:

Mr. William D. Gentry, AIR- 2.2.1.2

Phone: (301) 757-7069.

Email: William.Gentry@navy.mil

For any changes and additional information to the solicitation please go to website:

http://www.fbo.gov

PART B - SPECIFIC INSTRUCTIONS

1.0 VOLUME 1: TECHNICAL – Integrated Master Schedule (IMS), Key System Performance

Requirements

This volume consists of the proposed schedule for meeting the delivery dates and key system performance requirements. The Offeror shall not contain any reference to price aspects of the offer in this volume. The Offeror shall address the following in the proposal:

1.1 Integrated Master Schedule (IMS)

The Offeror shall provide an Integrated Master Schedule (IMS) that delineates the planned activities/events listed below, along with contractor established activities deemed necessary for management of the program. The schedule shall cover the activities necessary to execute the program requirements outlined in Statement of Work (SOW) paragraph 5.2 (Contract Line Item Numbers (CLINs) 0001-0004) and achieve the delivery dates specified in Section

F. The IMS shall be submitted electronically in Microsoft Project 2010 version and in a written copy in the technical volume. Any additional schedule information can be submitted within a schedule narrative provided in hardcopy and electronic format. The IMS shall be based on the following:

mailto:William.Gentry@navy.mil http://www.fbo.gov/

Notes: Provide the number of hours required for system and subsystem development (for both hardware and software) and verification hours. The Offeror shall use a calendar consistent with the company’s work schedule. A listing of company holidays, for each year of the proposed plan, shall also be included in the schedule narrative.

1.2 Key System Performance Requirements

Offerors are advised that they must present proof in their proposal (e.g. test data, modeled data where applicable, analysis, and any required supporting data) showing how it meets the Shipboard Air Traffic Radar (SATR) performance requirements for SATR in a relevant environment based on actual testing or modeled analysis and any required supporting data; otherwise, the Offeror’s proposal will be deemed unacceptable and not be evaluated any further.

1.2.1 The Offeror’s demonstrated performance in a shipboard environment shall be supported by applicable test results to meet the System Specification requirements in the following section: REQ.2.8.1

1.2.2 The Offeror’s predicted performance and known limitations for the AN/SPN-50(V)1SATR in the post CDR configuration shall be supported by applicable test results or with the results of modeling and simulation or other predictive analysis tools A description of the tools, their validation with test and appropriateness to the proposed system should also be provided. The performance presented shall be in accordance with the external environmental conditions presented in the specification. The Offeror shall provide sufficient detail including actual radar test data, calculated data and performance curves to conclusively substantiate the ability of their proposed system to meet the following System Specification requirements:

a. Service Volume: Capable of meeting the requirements as specified in the system specification, REQ.2.2.1.1

b. Service Volume: Capable of meeting the requirements as specified in the system specification, REQ.2.2.1.2

c. Service Volume: Capable of meeting the requirements as specified in the system specification, REQ.2.2.1.3

d. Constraints: Capable of meeting the requirements as specified in the system specification, REQ.2.9.2, REQ.2.9.2.1, REQ.2.9.2.2, and REQ.2.9.2.3

e. Range and Azimuth Resolution: Capable of meeting the requirements as specified in the system specification, REQ.2.4, REQ.2.4.1, and REQ.2.4.2

f. Azimuth Accuracy: Capable of meeting the requirements as specified in the system specification, REQ.2.3.2.

g. Update Rate: Capable of meeting the requirements as specified in the system specification, REQ.2.1.

h. Reliability: Capable of meeting the requirements as specified in the system specification, REQ.8.2, REQ.8.2.1, REQ.8.2.2, REQ.8.2.3, REQ.8.2.4, REQ.8.2.5, and REQ.8.2.6 - Analysis shall be submitted in a format readable by Raptor or Windchill

i. Dimensions: Capable of meeting the requirements as specified in the system specification, REQ.7.2, REQ.7.2.1, REQ.7.2.2, REQ.7.2.3, REQ.7.3, REQ.7.4, REQ.7.4.1, and REQ.7.4.2

j. Range Accuracy: Capable of meeting the requirements as specified in the system specification, REQ.2.3.1.

k. Target Detection: Capable of meeting the requirements as specified in the system specification, REQ.2.5.4.

l. Target Detection: Capable of meeting the requirements as specified in the system specification, REQ.2.5.5, REQ.2.5.6, REQ.2.5.7.

If the Offeror’s proposed system does not currently meet all of the performance specifications, they shall identify where deficiencies exist, conclusively demonstrate how they will achieve the specification and reflect the cost in the

Cost Volume.

1.3 Small Business Subcontracting Plan

Large Business Offerors shall provide one of the following types of small business subcontracting plans: a

Comprehensive Subcontracting Plan approved in accordance with DFARS 252.219-7004; a Master Small Business

Subcontracting Plan with subcontracting goals applicable to the SPN-50 effort covered by this solicitation; OR an

Individual Small Business Subcontracting Plan for the SPN-50 effort covered by this solicitation. If the offeror provides either a Master Small Business Subcontracting Plan with subcontracting goals applicable to the SPN-50 effort covered by this solicitation or an Individual Small Business Subcontracting Plan for the SPN-50 effort covered by this solicitation, this plan shall be prepared in accordance with the provisions of FAR 19.704 and

DFARS 219.704. Please see FAR 19.702(a)(1) “Statutory requirements", regarding failure of the apparent successful Offeror to submit an approved Comprehensive Subcontracting Plan, a Master Small Business

Subcontracting Plan with subcontracting goals applicable to the SPN-50 effort covered by this solicitation, OR an

Individual Small Business Subcontracting Plan for the SPN-50 effort covered by this solicitation. The successful

Offeror’s approved Subcontracting Plan will be incorporated into the contract.

1.4 Use of Government Furnished Equipment

Offerors requiring any GFE other than EDM # 1 and EDM # 2 in the Pre-CDR configuration as described at

5252.245-9500, “Government Property for the Performance of this Contract (NAVAIR) (MAY 2104)” on page 15 of this RFP will not be deemed technically acceptable.

2.0 VOLUME 2 – COST/PRICE PROPOSAL

2.1 General Information

The following is a list of the Section L Cost Attachments that the Offeror shall utilize to provide cost information as required for this Volume:

Section L, and (10) Cost Attachments, which includes the following:

Cost Attachment 1 (CA-1) Program Work Breakdown Structure (PWBS) and PWBS Dictionary

Cost Attachment 2 (CA-2) Cost Cross Reference Matrix (CRM)

Cost Attachment 3 (CA-3) N0019-15-R-0081, DD Form 2794 CSDR Contract Plan

Cost Attachment 4 (CA-4) N0019-15-R-0081, Resource Distribution Table (RDT)

Cost Attachment 5 (CA-5) Modified DD Form 1921 Example

Cost Attachment 6 (CA-6) Modified DD Form 1921-1 Example

Cost Attachment 7 (CA-7) Cost Substantiation

Cost Attachment 8 (CA-8) Software

Cost Attachment 9 (CA-9) Systems Engineering/Program Management

Cost Attachment 10 (CA-10) Skill Mix/Composite Direct Labor Rate

All costs shall be contained in RFP Section B, and the cost/price proposal. The Government is required to evaluate each proposal relative to the cost/price criteria submitted in response to Section M. Proper presentation and adequate supporting documentation will ensure the cost/price proposal is efficiently evaluated and all assumptions are understood. The burden of proof for cost credibility rests with the Offeror.

The information required in this cost instruction applies to both the Offeror and to any Principal subcontractors, as defined in paragraph one (1) of the General Proposal Instruction, and is required to meet the requirements of this solicitation. Due to the proprietary nature of company rates, rate information may be presented separately for each

Offeror and principal subcontractor. Each principal subcontractor that provides a separate cost/price volume shall follow the same format as described in this instruction.

In developing the cost proposal, the Offeror shall develop a CLIN 0003 Cost Work Breakdown Structure (CWBS) and CWBS Dictionary that aligns to the Government provided CLIN 0003 Program Work Breakdown Structure

(PWBS) contained in Cost Attachment 1. Tailoring of the CWBS is encouraged and allowed at levels below the

PWBS to reflect the Offeror's specific design.

Any adjustments shall be clearly described in the Ground Rules and Assumptions portion of the Offeror’s Summary of Estimating Methodology (see paragraph 2.3.1.2). Any adjustments must be cross-referenced to the Offeror’s

CLIN 0003 CWBS, SOW, and CLIN 0003. The estimate must be easily traceable from the lowest level at which the

Offeror’s estimate was substantiated to CLIN 0003.

The proposal provided by the Offeror shall follow the format provided in paragraph 2.3, Cost/Price Proposal

Instructions.

2.2 Cost/Price Proposal Guidelines

Cost information shall be submitted in Then Year dollars (TY$) based on the Government’s fiscal year (1 October through 30 September) with the escalation formula provided for each year. The Offeror shall also provide a summary level of the Cost/Price Proposal in Constant Fiscal Year 2016 (FY16$) by Fiscal Year and CWBS using escalation/de-escalation factors supported by their rates and factors used in their cost/price proposal. Please provide this summary based on a Level 2 CWBS plus Level 3 and 4 for elements within CLIN 0003 of the AN/SPN-50(V)1

Program.

The Offeror shall prepare and submit the cost proposal narrative substantiation and rationale in Microsoft Word

2010 format and any numerical data in a Microsoft Excel 2010 format on CD-ROM. Files received in a format other than requested are unacceptable. Portable Document Format (PDF) is not acceptable, except when provided in addition to Microsoft Word or Excel formats. Within all Excel spreadsheets, the Offeror shall use formulas and functions to the maximum extent possible and avoid using "value only" cells. If external links are utilized, supply those referenced files. The cost proposal shall be unprotected and unlocked, with formulas intact to show mathematical operations. Ensure that the electronically submitted filenames are directly traceable to the hard copy submittals.

2.3 Cost/Price Proposal Instructions

The proposal provided by the Offeror shall follow the format below:

Section 1 – Engineering Manufacturing Design NRE Cost for CLIN 0003

1.1 – Programmatic Information

1.1.1 – Post CDR System Description

1.1.2 – Ground Rules and Assumptions

1.1.3 – CLIN 0003 CWBS and CWBS Dictionary

Cost Attachment 1, CLIN 0003 Program Work Breakdown Structure (PWBS) and PWBS

Dictionary

1.1.4 – EMD Cost and Software Data Reporting (CSDR) Plan

Cost Attachment 3, N0019-15-R-0081, DD Form 2794 CSDR Contract Plan

1.1.5 – Level of Effort (LOE) Work Years (WYs) by Year

Cost Attachment 9, Systems Engineering/Program Management

1.1.6 – Subcontracts, Interdivisional transfers

Cost Attachment 4, N0019-15-R-0081, Resource Distribution Table (RDT)

1.1.7 – Special Tooling and Special Test Equipment (ST/STE)

1.2 – Summary of Estimating Methodology

Cost Attachment 2, Cost Cross Reference Matrix

1.3 – Cost Summaries

1.3.1 –DD Form 1921

Cost Attachment 5, Modified DD Form 1921 Example

1.3.2 –DD Form 1921-1

Cost Attachment 6, Modified DD Form 1921-1 Example

1.4 – Detailed Estimating Methodology

1.4.1 – Labor

Cost Attachment 7, Cost Substantiation

1.4.2 – Software Form

Cost Attachment 8, Software

1.4.3 – Material

Cost Attachment 7, Cost Substantiation

1.4.4 – Other Direct Charges/Travel

Cost Attachment 7, Cost Substantiation

1.5 – Fee

Section 2 – Contractor Rates

2.1 – Indirect rates

2.2 – Direct rates

2.2.1 – Direct Labor Rate

2.2.2 – Skill Mix

Cost Attachment 10, Skill Mix/Composite Direct Labor Rates

2.3 – Cost to Sell Equations

2.4 – Escalation

Section 3 – Other Cost/Price Impacts

Section 4 – Model Contract

2.3.1 SPECIFIC INSTRUCTIONS FOR SECTION 1 ENGINEERING & MANUFACTURING NRE COST

(CLIN 0003)

The following instructions apply to Section 1 costs. Offeror is expected to follow the instructions in each section and number according to the outline provided in Section 2.3 above.

The Government assessment will address the sum of the resources required to realistically conduct the program proposed by the Offeror. Of primary importance to this process are the Offeror’s actual expenditures for tasks comparable to those found in the CWBS and CWBS Dictionary and historical data from analogous efforts. Where this is not provided/available, the Government may consider historical data from previously executed programs as is deemed necessary in order to conduct the evaluation.

In all cases, documentation is required for each Offeror’s CWBS element priced out for the SOW contained in the solicitation, which shall provide the basis of estimate for labor, material, and purchased components. If there is any information requested that does not apply to the Offeror's proposal (e.g., non-recurring, manufacturing) then indicate with the letters ‘N/A’ (Not Applicable) on any forms where a space is provided.

The following guidelines and sample formats/attachments are provided to assist the Offeror in preparing clear, concise, comprehensive, and traceable proposals.

The Offeror shall cost the CWBS and ensure that it is cross-referenced to the SOW and CLINs. All totals shall agree. Substantiation shall be provided at the lowest level for which the Offeror developed estimates.

Ensure consistency between the information/data in this Volume and that provided in the Technical

Volume.

Historical data from comparable or analogous systems/subsystems shall be used to substantiate the

Offeror's estimate where possible. When using historical cost data from comparable systems/subsystems, all assumptions affecting the Offeror's cost proposal are to be fully documented (e.g., escalation methodology, make or buy decisions, etc.). A summary with a programmatic and technical description of the historical system shall be provided along with the actual cost data for the historical system, a comparison to the proposed system, and any adjustments made to derive the proposed estimate. The following shall be considered:

1) Programmatic description related to the acquisition aspects of any system identified by the Offeror as comparable/analogous. This includes, for example, the years the item was procured, production rates, quantities procured by year and definition of system composition, sole source or competitive procurement, and the development time period.

2) Technical description including the performance and physical aspects of the system. This describes the system in terms of the number of parts, physical configuration, type of material, technology, and physical/performance parameters.

3) Actual cost data including the cost account, narrative description of the effort, and the actual cost data (material and person-hours). The cost data shall be provided in terms of total dollars actually spent by fiscal year and by unit cost.

4) When using historical data, the Offeror should describe why the system is comparable to the proposed program. This includes a functional and technical comparison explaining the differences as well as similarities between the historical and the proposed system. Also include an explanation of the relationship between the analogous element cost and the total program cost.

5) The Offeror shall provide the basis and document any adjustments applied to the historical data

(e.g., complexity factors and normalization methods), which reflect the characteristics of the proposed system. This includes an audit trail sufficient for the Government to reconstruct the proposed estimate and judge its credibility.

a. General statements such as “estimates were derived from engineering analysis or engineering judgments” are unacceptable. If a level of effort task is the basis for projecting labor hour requirements, the data substantiation shall include task duration, man-loading, number of times the task is repeated (if applicable), time-phased hours and associated costs, and the relationship between the historical system and the system under review.