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

This amendment enacts the follow ing: a) Extends the deadline for proposal submission; b) In Section L, Clause Ddl-L40, extends the date for submission of questions about this Solicitation; c) In Sections I and K, replaces or adds Cybersecurity provision and clauses.

1. CONTRACT ID CODE PAGE OF PAGES

1 20

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

16C. DATE SIGNED

BY 08-Jan-2016

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 N00178-16-R-3000

X 9B. DATED (SEE ITEM 11)

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

08-Jan-2016

CODE

NSWCDD

ATTN: PHIL MAKELY, CODE 0251

PHILLIP.MAKELY@NAVY.MIL

17632 DAHLGREN ROAD STE 157

DAHLGREN VA 22448-5110

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

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

N00178-16-R-3000

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION A - SOLICITATION/CONTRACT FORM

The required response date/time has changed from 22-Jan-2016 02:00 PM to 29-Feb-2016 02:00 PM.

SECTION I - CONTRACT CLAUSES

The following have been added by full text:

252.204-7012 SAFEGUARDING COVERED DEFENSE INFORMATION AND CYBER INCIDENT

REPORTING (DEC 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 a compromise or 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 computer-related 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,” 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, as soon as practical, but not later than December 31, 2017. The Contractor shall notify the DoD CIO, via email at osd.dibcsia@mail.mil, within 30 days of contract award, of any security requirements specified by NIST SP 800-171 not implemented at the time of contract award; or

(B) Alternative but equally effective security measures used to compensate for the inability to satisfy a particular requirement and achieve equivalent protection accepted in writing by an authorized representative of the DoD CIO; 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 this clause, including this paragraph (m), in subcontracts, or similar contractual instruments, for operationally critical support, or for which subcontract performance will involve a covered contractor information system, including subcontracts for commercial items, without alteration, except to identify the parties; and

(2) When this clause is included in a subcontract, 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.

252.204-7009 LIMITATIONS ON THE USE OR DISCLOSURE OF THIRD-PARTY CONTRACTOR

REPORTED CYBER INCIDENT INFORMATION (DEC 2015)

(a) Definitions. As used in this clause—

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

“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 defense information” means unclassified information that—

(1) Is—

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

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

(2) Falls in any of the following categories:

(i) Controlled technical information.

(ii) 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).

(iii) 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.

(iv) 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 a compromise or an actual or potentially adverse effect on an information system and/or the information residing therein.

(b) Restrictions. The Contractor agrees that the following conditions apply to any information it receives or creates in the performance of this contract that is information obtained from a third-party’s reporting of a cyber incident pursuant to DFARS clause 252.204-7012, Safeguarding Covered Defense Information and Cyber Incident Reporting (or derived from such information obtained under that clause):

(1) The Contractor shall access and use the information only for the purpose of furnishing advice or technical assistance directly to the Government in support of the Government’s activities related to clause 252.204-7012, and shall not be used for any other purpose.

(2) The Contractor shall protect the information against unauthorized release or disclosure.

(3) The Contractor shall ensure that its employees are subject to use and non-disclosure obligations consistent with this clause prior to the employees being provided access to or use of the information.

(4) The third-party contractor that reported the cyber incident is a third-party beneficiary of the non-disclosure agreement between the Government and Contractor, as required by paragraph (b)(3) of this clause.

(5) A breach of these obligations or restrictions may subject the Contractor to—

(i) Criminal, civil, administrative, and contractual actions in law and equity for penalties, damages, and other appropriate remedies by the United States; and

(ii) Civil actions for damages and other appropriate remedies by the third party that reported the cyber incident, as a third party beneficiary of this clause.

(c) Subcontracts. The Contractor shall include this clause, including this paragraph (c), in subcontracts, or similar contractual instruments, for services that include support for the Government’s activities related to safeguarding covered defense information and cyber incident reporting, including subcontracts for commercial items, without alteration, except to identify the parties.

The following have been deleted:

252.204-7008 Compliance With Safeguarding Covered Defense Information

Controls

AUG 2015

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

SEP 2015

SECTION K - REPRESENTATIONS, CERTIFICATIONS AND OTHER STATEMENTS OF OFFERORS

The following have been added by full text:

252.204-7008 COMPLIANCE WITH SAFEGUARDING COVERED DEFENSE INFORMATION CONTROLS

(DEC 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.

(b) The security requirements required by contract clause 252.204-7012, Covered Defense Information and Cyber Incident Reporting, shall be implemented for all covered defense information on all covered contractor information systems that support the performance of this contract.

(c) For covered contractor information systems that are not part of an information technology (IT) service or system operated on behalf of the Government (see 252.204-7012(b)(1)(ii))—

(1) By submission of this offer, the Offeror represents that it will implement the security requirements specified by 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), not later than December 31, 2017.

(2)(i) If the Offeror proposes to vary from any of the security requirements specified by NIST SP 800- 171 that 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—

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

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

(ii) An authorized representative of the DoD CIO will adjudicate offeror requests to vary from NIST SP 800-171 requirements in writing prior to contract award. Any accepted variance from NIST SP 800-171 shall be incorporated into the resulting contract.

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

Ddl-L10 PROPOSAL PREPARATION REQUIREMENTS

Offerors are required to prepare their proposals in accordance with the following organization, content and format.

a) SOLICITATION, OFFER AND AWARD DOCUMENTS (SF 33 - RFP)

1) This document, which may be used as part of the contract award document, shall be fully executed and returned as a separate document from the technical/management and cost proposals. Special attention should be taken to accurately enter the prices required in Section B, complete the fill-ins in Section(s) K, complete all Representations and Certifications in Section K, and ensure that an authorized person signs the offer in Block 17 of Page 1. This document shall not be embellished with any covers or binding.

2) Offerors are encouraged not to take exceptions to this solicitation, however, any exceptions taken to the specifications, or terms and conditions of this solicitation shall be identified in a cover letter and explained in detail in the appropriate Section of the technical proposal.

b) TECHNICAL PROPOSAL

1) The technical proposal shall not contain any reference to cost and shall be prepared in accordance with the following guidelines and the TECHNICAL PROPOSAL specific requirements below.

2) The technical proposal should be written so that management and engineering oriented personnel can make a thorough evaluation and arrive at a sound determination as to whether the proposal meets the requirements of this solicitation. To this end, the proposal shall be so specific, detailed and complete as to clearly and fully demonstrate that the prospective Contractor has a thorough understanding of the technical requirements contained in Section C of this solicitation. The technical proposal (Volumes I through III as described herein) shall not exceed 150 pages in its discussion. Additional pages will be allowed for matrices.

3) Statements such as "the Offeror understands", "will comply with the statement of work," "standard procedures will be employed", "well known techniques will be used" and general paraphrasing of the statement of work are considered inadequate. The technical proposal must provide details concerning what the Contractor will do and how it will be done. This includes a full explanation of the techniques, disciplines, and procedures proposed to be followed.

4) Unnecessarily elaborate brochures or other presentations beyond that sufficient to present a complete and effective proposal are not desired and may be construed as an indication of the Offeror's lack of cost consciousness.

Elaborate art work, expensive paper and bindings, or expensive visual and other presentation aids are neither necessary nor desired.

5) In the event any portion of the technical proposal is written by anyone who is not a bona fide employee of the firm submitting the proposal, a certificate to this effect shall be furnished. It must be signed by a responsible officer of the Offeror and shall show the author's name, employment capacity, the name of the person's firm, the relationship of that firm to the Offeror's, and the portion of the technical proposal he/she wrote.

6) Technical information previously submitted, if any, may not be considered by the Government; hence, any such information should not be relied upon or incorporated in the technical proposal by reference.

c) PAST PERFORMANCE HISTORY

The Past Performance History should be written so that management and engineering oriented personnel can make a thorough evaluation and arrive at a sound determination based on previous experience as to the ability of the Offeror to successfully perform the contract requirements. Relevance of past performance will also be taken into consideration.

d) COST OR PRICE PROPOSAL

The cost proposal shall provide full supporting detail for the prices listed in Section B of the proposal and shall be prepared in accordance with the Ddl-L31 (Cost Proposal for FFP Orders) and Ddl-L33 (Cost Proposal for CPFF Completion Orders) specific requirements listed below.

e) MARKING OF PROPOSALS

Proposals shall be submitted as separate Sections, as follows:

Section A, Solicitation, Offer, and Award (SF 33) – One Original and One Copy

Section B, Technical Proposal for Overall Contract SOW– One Original and Six Copies containing:

Introduction – Mandatory Requirements Volume I – PPTA Production Capability and Approach Volume II – PPTA Design Approach Volume III – PPTA Management and Lifecycle Approach

Section C, Volume IV - Past Performance - One Original and One Copy

Section D, Volume V - Cost and Price Proposal – One Original and One Copy

The original of each Section shall be clearly identified as the "ORIGINAL" and bear original signatures. The copies shall be complete and clearly identified as "COPY."

Ddl-L24 WRITTEN PROPOSAL INSTRUCTIONS

ORGANIZATION AND MINIMUM CONTENT OF THE WRITTEN TECHNICAL PROPOSAL - SECTION B

In order to facilitate evaluation, it is desired that the Written Technical Proposal be structured into the following components:

a) Introduction - Mandatory Requirements

The Introduction shall address whether each element of the Mandatory Requirements found in Section C.4 of the SOW have been met.

Potential Offerors are advised that the data contained in the PRDD discussed in Section C.3.1.1 is marked with a Distribution Statement D that contains technical data in which export is restricted by the Arms Export Control Act (Title 22, U.S.C. Sec. 2751 et seq. or Executive Order 12470). Violators of these export laws are subject to severe criminal penalties.

b) Procurement Requirements Digital Download (PRDD)

PRDD distribution is authorized to Department of Defense and U.S. DoD contractors ONLY for the sole purpose of proposal preparation in accordance with the terms and conditions of solicitation N00178-16-R-3000. Offerors requesting a copy of the PRDD must provide a written request prior to 5 January 2016. Other requests for this document that is not intended for the use of a proposal submission will not be authorized. The Distribution Statement D requirement, as found in DoD Directive 5230.24, is available at http://www.dtic.mil/whs/directives/corres/pdf/523024p.pdf.

The written request shall contain the following information:

1). Offeror’s Name and Address. If the Offeror is a subsidiary, list the names and addresses of the subsidiary and the parent companies.

2). Point of Contact information containing the name, address, e-mail address, and phone number.

3). Offeror’s CAGE and DUNS number and a statement that the Offeror is a DoD and/or U.S. DoD Contractor.

4). A list of all personnel that will have access to the PRDD and a statement that all personnel that will access the PRDD are U.S. Citizens.

The request shall be sent via email to the following POCs:

TO: Mr. Phillip Makely – Phillip.makely@navy.mil CC: Mr. Charles Thompson- Charles.e.thompson@navy.mil

Upon the Government 's approval of the Offeror’s written request, the Government will release the PRDD documents through the AMRDEC SAFE web tool to the POC designated in the requestor’s initial e-mail. A separate notification of access e-mail containing web tool instructions shall be sent from the AMRDEC web tool.

c) Volume I – PPTA Production Capability and Approach (Evaluation Factor 1)

Volume I shall contain a discussion of the Contractor’s PPTA equipment production capabilities and approach for each of the devices listed in the SOW Section C.3.1 table and PRDD. It is desired that the following technical aspects of the production capabilities and approach be addressed.

Subfactor 1.1 Hardware Production Approach

1) The Offeror shall provide a proposed manufacturing plan and a work flowchart demonstrating throughput and major process activities beginning with contract award through shipment of the first assembly, including inspection, component level testing, and production acceptance testing. The Offeror shall also address the required technologies, equipment, and/or specialized skills required to produce PPTA equipment.

2) The Offeror shall populate a Contract Work Breakdown Structure (CWBS) that identifies the work allocation for this procurement as required in Section C.

3) The Offeror shall describe its system for acquisition of material, material control, and monitoring delivery status of material previously ordered. The Offeror shall describe its plan to ensure complete compliance to the Critical Item Development Specification (CIDS) and the requirements of the SOW prior to ordering material and prior to release of material for manufacturing.

4) The Offeror shall describe its proposed Configuration Management Plan and how it complies with the SOW.

The Offeror shall demonstrate an understanding of the CM requirements for this acquisition and describe how it will implement a CM Program. The Offeror shall demonstrate how its process manages changes or deviations to the production baseline that may be submitted via the CM process. The Offeror shall provide examples of how it has successfully initiated Configuration Management on a previous program of similar complexity.

5) The Offeror shall describe its proposed Production Acceptance Test Plan and Production Acceptance Test procedures used to verify functionality of the equipment produced under this contract. The Offeror shall describe how this will be implemented in its facility, identify any testing requirements that cannot be performed in the present facility, and provide a work around plan for any such requirements.

6) The Offeror shall describe its proposed Quality Assurance Program Plan and address how it intends to ensure the manufacturing quality of its Subcontractors and other vendors. The Offeror shall address its adherence to the applicable elements of ISO 9001-2008. The Offeror shall ensure that its approach adheres to the quality requirements in the SOW.

7) The Offeror shall describe its Make or Buy Program, which shall be submitted in accordance with the requirements set forth in the Make or Buy provision contained in Section L above at HQ L-2-0004.

8) The Offeror shall describe its proposed DMSMS process, including proposed plans to mitigate engineering and lifecycle impacts.

Subfactor 1.2 Production Facility

The Contractor shall describe the following:

1) Site Manufacturing/Fabrication Capabilities:

Machining and Weld Metal Capabilities Cabling Manufacturing Capabilities Wire Harness Fabrication Capabilities Circuit Board/Electronics Fabrication Capabilities Assembly Capabilities Paint/Coat Capabilities

2) Manufacturing Processes:

Manufacturing Planning/Execution Capabilities Work Flow Maturity/Usage Workforce Training/Capabilities/Certifications Material/Manufacturing/Test Discrepancy Procedures/Systems Process Control Program/Systems Incoming Materials/Components Inspection Program Part Tracking System Stocking Capabilities/System ID Parts Capabilities/System Calibration Procedures Production Traveler/Pick List Examples Final Test Capabilities/System(s) Quality Assurance/Quality Control Systems Managing Risks Capabilities/System Lean/Six Sigma Principles Examples Manufacturing/Measurement Repeatability/Reproducibility Assurances Packaging/Handling/Shipping/Transportation Program

3) Production Line – Capacity and Cycle Time

4) Test Line – Capacity and Cycle Time

d) Volume II – PPTA Equipment/Hardware Design Approach (Evaluation Factor 2)

Volume II shall contain a discussion of the design approach for both First Article Unit (FAU) production and ensuing full PPTA production for each of the devices listed in the SOW Section C.3.1 Table.

It is required that the following technical aspects of the design approach be addressed.

1) The Offeror shall demonstrate the ability to produce MIL-STD 31000C equivalent Level III Technical Data Packages suitable for commercially equivalent, functionally representative systems and components.

2) The Offeror shall provide a plan for development of a MIL-STD 31000C equivalent Level III Technical Data Packages for the equipment covered by this statement of work. Assume the following inputs:

A) Critical Item Design Specification (CIDS) for each piece of equipment

B) Government selection of major electronic components (i.e Edge Switch, 1U Processor, 3U Processor (used where additional PCIe capacity is needed), Disk Drive, Remote Access Server, System Environmental Monitor, and Power Controller.)

3) The Offeror shall provide details on the technical challenges identified and the approaches to solve those challenges prior to production.

4) The Offeror shall describe the process and manner in which equipment upgrades will be developed and the methods used to qualify those upgrades for implementation.

5) The Offeror shall provide their proposed approach to identify and establish standardized guidelines for the detection and avoidance of counterfeit materiel into equipment developed under this contract.

6) The Offeror shall demonstrate their ability to identify, track, manage, and report DMSMS cases including their ability to manage subcontractor’s DMSMS management programs.

7) The Offeror shall provide their strategy and plan to proactively mitigate obsolescence and DMSMS issues identified during development and production and provide cost-effective solutions. The Offeror shall describe their processes/approaches for continuous DMSMS monitoring and surveillance of the Bill of Materials (BOMs) and assessment of DMSMS impacts both at the item level and higher levels of assembly.

e) Volume III – PPTA Management and Lifecycle Approach (Evaluation Factor 3)

Volume III shall discuss the Offeror’s management program in a manner that clearly defines how the PPTA efforts will be managed and controlled for each of the devices listed in the SOW Section C.3.1 Table. The Offeror shall discuss how its proposed management system supports successful execution of PPTA Design and Production. The Offeror shall demonstrate the ability to predict obsolescent material and methods by which the Offeror will qualify upgraded components for form, fit, and functional replacement within installed end item units produced under this solicitation.

Subfactor 3.1 Management Plan

1) The Offeror shall provide an organizational chart and shall describe the organization that will manage the overall contract, including subcontractors.

2) The Offeror shall provide its proposed plan to meet design, production, and delivery milestones for providing fully qualified production PPTA equipment as specified in the SOW.

3) The Offeror shall provide details on how it will communicate with the COR, the PCO, CDSADN staff, other Contractors, and subcontractors (to include lines of authority, responsibility and communication flows) in order to identify and resolve problems. The Contractor shall provide an organization chart that highlights the above relationships and responsibilities.

4) The Offeror shall provide their proposed management approach to operating the overall contract work under a coherent and collaborative management teaming structure. Describe how the approach eliminates or avoids the need for dedicated management and separated teams.

5) The Offeror shall identify key cost, performance, and technical risks and why these were identified as risks. The Contractor shall discuss the risks, including dependencies and mitigation for each identified risk.

Subfactor 3.2 Lifecycle Support Approach

1) The Offeror shall describe their system and/or processes to capture failure data that will be provided to Department of Defense (DoD) databases.

2) The Offeror shall describe their DMSMS and Obsolescence management processes and how the outcomes of those processes will be implemented to ensure lifecycle support of Next Generation PPTA equipment.

3) The Offeror shall demonstrate their ability to implement item unique identification (IUID) using unique item identifier (UII) in accordance with DoD Instruction 8320.04 for authoritative life-cycle traceability and authentication.

4) The Offeror shall describe their processes for tracking commercial warranties and implementing repairs/replacement of commercial items under those standard commercial warranties.

5) The Offeror shall demonstrate their ability to track the warranties using the IUID registry for the duration of the active warranty period in accordance with DoD Instruction 8320.04 for authoritative life-cycle traceability and authentication.

Subfactor 3.3 Approach to Reliability, Availability and Maintainability (RAM)

The Offeror shall describe how they will meet the RAM requirements of the solicitation and describe all activities considered to be necessary for ensuring the development of a maintainable product. For each activity, the bidder shall describe the objective, rationale for selection, method of implementation, methods of assessing results, and any associated documentation, including:

1) The Offeror shall provide their proposed approach in assisting the Government in establishing a RAM Program.

2) The Offeror shall show how the following objectives will be met:

A) design for accessibility;

B) design for human factors;

C) minimize number of special tools (design so faults can be readily and confidently detected and isolated);

D) design for ease of inspection and incorporate provisions for non-destructive inspection;

E) verification of requirements;

3) The Offeror shall show how the results of the included activities will be used to support other activities, such as logistics planning, safety analyses, etc.

Ddl-L26 TECHNICAL PROPOSAL – SPECIFIC REQUIREMENTS – PAST PERFORMANCE

ORGANIZATION AND MINIMUM CONTENT OF PAST PERFORMANCE INFORMATION - SECTION C

In order to facilitate evaluation, it is desired that the Past Performance Information be labeled as the following component:

a) Volume IV – Past Performance (Evaluation Factor 4)

Volume IV of the proposal shall contain information concerning the Offeror’s experience in performance of contracts for similar deliverables of the variety and magnitude set forth in this RFP. This information should include data as to the scope of work required under such contracts, the term of those contracts, number and types of personnel furnished, the contracting agencies/offices that awarded the contracts, applicable contract numbers, and any other applicable information. Information regarding past performance may be obtained from several sources, as indicated below.

b) Past Performance Reference List: All Offerors shall prepare and submit a Past Performance Reference List containing up to three references as part of the written Technical Proposal. The Past Performance Reference List shall contain the following information for each relevant contract completed within the last three years and those currently in progress:

1) Contract Number

2) Contract Amount/Value

3) Description of Work Performed to include approximate number of direct man-years per year provided.

4) Identification of the SOW functional area(s) (e.g, C.xx -- XXXXX) for which the referenced contract demonstrates past performance.

5) Note if performed as a prime or subcontractor

6) Name, address and phone number of the Contracting Officer and of the COR

c) If submitting a proposal for subject acquisition as a prime Contractor, the Offeror is encouraged to include Past Performance reference(s) where they performed as a prime Contractor. If subcontractors are proposed for subject acquisition, the Offeror is encouraged to include Past Performance reference(s) where they, as the prime Contractor, subcontracted a portion of the effort. Further, if subcontractors are proposed for this requiremenet, past performance references may be cited for current and previous customers of the proposed subcontractors.

d) Contract Listed in CPARS. The Government intends to review Contractor Performance Assessment Reporting System (CPARS) data and other existing past performance rating on relevant contracts.

e) All Offerors may provide any other information regarding their past performance of contracts similar to the Government’s requirement that they would like the Government to consider. Such information may be in the nature of:

1) Additional information which the Government has readily available, for example, a synopsis of data in the CPARS system;

2) Information which the Offeror considers essential to the Government’s evaluation of Section M factors and/or subfactors; or

3) Explanatory information of substandard or poor performance and the corrective actions taken to prevent a recurrence.

f) Past performance will be used as both an evaluation factor and as a source of information for a responsibility determination. Offerors are encouraged to provide information on problems encountered on the identified contracts and the offeror's corrective actions taken.

ORGANIZATION AND MINIMUM CONTENT OF THE COST AND PRICE PROPOSAL - SECTION D

In order to facilitate evaluation, it is desired that the Cost and Price Proposal be labeled as the following component:

a) Volume V – Cost and Price Proposal (Evaluation Factor 5)

Each Offeror is required to submit a cost volume, for the proposed Cost/Price information for all priced CLINs.

This volume will be separate from the other volumes, in the required number of copies and paper/electronic media format. NO COST INFORMATION SHALL BE SUBMITTED IN ANY VOLUME OTHER THAN THIS COST VOLUME V. Electronic copies of the cost volume shall be submitted on separate media, using MS Word/MS Excel as applicable. All MS Excel files must have formulas clearly evident, editable, and functioning. MS Excel spreadsheets must be linked to other cells within the same workbook or worksheet

(e.g., direct labor = hours x direct labor rate). Cells may not be linked to cells in other workbooks (i.e., separate files).

b) The Offeror shall follow the ensuing instructions for submission of the Volume V Cost and Price Proposal as listed herein at Ddl-L31, Ddl-L33, and Ddl-L36.

Ddl-L33 COST PROPOSALS – SPECIFIC INSTRUCTIONS – COST REIMBURSEMENT CONTRACTS -

CLIN 0001 (CPFF) AND CLIN 0002 (COST ONLY)

The following instructions apply to the preparation of your Cost Proposal. The instructions herein apply equally to the prime Contractor and to any consultants and/or subcontractors.

a) Offerors shall populate Section B CLIN pricing pricing for CLIN 0001 and CLIN 0002.

b) Overall Project

1) Identify your cognizant DCAA and ACO (DCMA) offices. Provide the name of a point of contact for each and provide current phone numbers.

2) Your accounting system must be approved by DCAA for cost type contracts. Please indicate whether or not your accounting system has been approved. If it has not, contact your cognizant DCAA as soon as possible to arrange for this review; this can add as much as 8-12 weeks to the contract award process.

A) FAR 16.301-3(a)(1) requires that a Contractor’s accounting system be adequate for determining costs applicable to the contract in order to be eligible for a cost reimbursement type contract. This is understood to mean that the accounting system must have been reviewed and approved by the Defense Contract Audit Agency (DCAA).

B) This requirement applies equally to the prime Contractor as well as their subcontractors who are proposed for cost-reimbursement or time and materials (T&M) contracts. T&M contracts are considered to be a form of cost reimbursement contracting because of the manner in which materials and ODCs are priced (actual cost plus indirect burdens). Subcontractors without approved accounting systems should be contracted using firm fixed price or labor hour contracts.

C) The prime Contractor is solely responsible for verifying that subcontractors proposed for cost reimbursement contracts (including T&M), have DCAA-approved accounting systems. They shall require subcontractors to provide a copy of DCAA’s most recent review/approval letter. A copy of this letter shall be provided to the Government.

D) The prime Contractor shall also provide a copy of DCAA’s most recent review/approval of their accounting system. The status of actions taken as a result of DCAA recommendations shall be addressed. Any unresolved issues shall be identified and their impact on this requirement shall be discussed.

3) Identify the range of months that comprise your fiscal year.

4) Where copies of documents/data are requested in the following instructions, they should be submitted with the hard (paper) copies of the proposal submission.

c) Direct Labor (CLIN 0001)

1) Provide a table which identifies all proposed hours by proposed task/subtask and contract period, if applicable.

These hours should be identified by labor category. Separately identify hours to be provided by consultants or subcontractors. This information shall facilitate our evaluation of the proposed hours and labor mix for the completion-based tasking and prototype article production.

2) Provide copies of current payroll records to support proposed base hourly rates.