N00024-16-R-6231_Amendment_5.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

See Continuation Page(s).

1. CONTRACT ID CODE PAGE OF PAGES

S 1 12

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

16C. DATE SIGNED

BY 07-Jul-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 N00024-16-R-6231

X 9B. DATED (SEE ITEM 11)

07-Apr-2016

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer is extended, X is not extended.

Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing Items 8 and 15, and returning 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

07-Jul-2016

CODE

NAVAL SEA SYSTEMS COMMAND (HQ)

1333 ISAAC HULL AVE SE

WASHINGTON NAVY YARD DC 20376-2050

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

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

N00024-16-R-6231

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

The following items are applicable to this modification:

SUMMARY OF CHANGES

SECTION SF 30 - BLOCK 14 CONTINUATION PAGE

The following have been added by full text:

Solicitation N00024-16-R-6231 Q&A

Amendment 5 Question 52 1. Please confirm that the cost data detail required by Section 3.2.1.1.1 is to be provided in cost volume section 3.2.2.8 in accordance with Section L-3.2.1.1.1 and L-3.2.2.8, rather than under Section L-3.2.1.1 (Section 1.1).

2. Is the solicitation asking for a summary table of the detailed L-3.2.2.8 (Section 2.8) Cost Summaries to be included in “Chapter 1.0 Summary Cost Data”?

3. Is the government expecting this quantity of tabular detail data? If not please provide guidance on how the data should be collapsed that may be acceptable.

4. If the entirety of the cost data detail specified by Section 3.2.1.1.1 are to be provided in full, will the Government permit submittal of this large quantity of supporting cost data detail (Section 2.8) in an electronic format only, and specify either PDF or Excel format? All other sections would still be provided in both paper and CD-ROM.

Answer 52 The Government does not intend for Section L-3.2 Volume II Cost/Price Proposal to prescribe a method of organizing the Cost/Price data offerors shall provide. Rather, this section is to prescribe the cost/price data offerors shall include in a response to this solicitation. Offerors are encouraged to present cost information efficiently and concisely. However, all information and data described in Volume II must be provided in order to be responsive to the solicitation.

Section L-3.2 Volume II Cost/Price Proposal is modified in this amendment to clarify the Government’s intent for this section.

In accordance with the modification to Section L in this amendment, the cost volume shall be submitted on CD only.

SECTION G - CONTRACT ADMINISTRATION DATA

The following have been modified:

252.232-7006 WIDE AREA WORKFLOW PAYMENT INSTRUCTIONS (MAY 2013)

(a) Definitions. As used in this clause--

Department of Defense Activity Address Code (DoDAAC) is a six position code that uniquely identifies a unit, activity, or organization.

Document type means the type of payment request or receiving report available for creation in Wide Area WorkFlow (WAWF).

Local processing office (LPO) is the office responsible for payment certification when payment certification is done external to the entitlement system.

(b) Electronic invoicing. The WAWF system is the method to electronically process vendor payment requests and receiving reports, as authorized by DFARS 252.232-7003, Electronic Submission of Payment Requests and Receiving Reports.

(c) WAWF access. To access WAWF, the Contractor shall--

(1) Have a designated electronic business point of contact in the System for Award Management at https://www.acquisition.gov; and

(2) Be registered to use WAWF at https://wawf.eb.mil/ following the step-by-step procedures for self-registration available at this Web site.

(d) WAWF training. The Contractor should follow the training instructions of the WAWF Web-Based Training Course and use the Practice Training Site before submitting payment requests through WAWF. Both can be accessed by selecting the “Web Based Training” link on the WAWF home page at https://wawf.eb.mil/.

(e) WAWF methods of document submission. Document submissions may be via Web entry, Electronic Data Interchange, or File Transfer Protocol.

(f) WAWF payment instructions. The Contractor must use the following information when submitting payment requests and receiving reports in WAWF for this contract/order:

(1) Document type. The Contractor shall use the following document type(s).

COST VOUCHER - APPLICABLE TO ITEMS 0001, 0002, 0101, 0102, 0201-0211, 0301-0311, 0401-0411, 0501- 0511, 0601-0611, and 0701-0711.

INVOICE AND RECEIVING REPORT (COMBO) - APPLICABLE TO ITEM 0006.

(2) Inspection/acceptance location. The Contractor shall select the following inspection/acceptance location(s) in WAWF, as specified by the contracting officer.

SEE SECTION E “INSPECTION AND ACCEPTANCE TERMS.”

(3) Document routing. The Contractor shall use the information in the Routing Data Table below only to fill in applicable fields in WAWF when creating payment requests and receiving reports in the system.

Routing Data Table* Field Name in WAWF Data to be entered in WAWF Pay Official DoDAAC TBD Issue By DoDAAC N00024 Admin DoDAAC TBD Inspect By DoDAAC TBD Ship To Code SEE SECTION F Ship From Code N/A

Mark For Code TBD Service Approver (DoDAAC) TBD Service Acceptor (DoDAAC) N/A Accept at Other DoDAAC N/A LPO DoDAAC N/A DCAA Auditor DoDAAC TBD Other DoDAAC(s) N/A

(4) Payment request and supporting documentation. The Contractor shall ensure a payment request includes appropriate contract line item and subline item descriptions of the work performed or supplies delivered, unit price/cost per unit, fee (if applicable), and all relevant back-up documentation, as defined in DFARS Appendix F, (e.g. timesheets) in support of each payment request.

(5) WAWF email notifications. The Contractor shall enter the email address identified below in the “Send Additional Email Notifications” field of WAWF once a document is submitted in the system.

COR IN SECTION G.

(g) WAWF point of contact.

(1) The Contractor may obtain clarification regarding invoicing in WAWF from the following contracting activity's WAWF point of contact.

NAVSEA HQ WAWF HELPDESK: WAWFHQ@NAVY.MIL

(2) For technical WAWF help, contact the WAWF helpdesk at 866-618-5988.

(End of clause)

SECTION I - CONTRACT CLAUSES

The following included by reference have been revised:

252.204-7015 Disclosure of Information to Litigation Support Contractors FEB 2014 252.219-7003 (Dev) Small Business Subcontracting Plan (DOD Contracts)

(Deviation 2013-O0014)

OCT 2014

252.225-7013 Duty-Free Entry--Basic (Nov 2014) NOV 2014

The following included by full text have been revised:

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.

mailto:WAWFHQ@NAVY.MIL

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 security measures when the Contractor reasonably determines that such 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.

http://dx.doi.org/10.6028/NIST.SP.800-171 mailto:osd.dibcsia@mail.mil

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

http://dibnet.dod.mil/ http://iase.disa.mil/pki/eca/Pages/index.aspx

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

(End of clause)

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

Section 1.1 “Solicitation Response Requirements” second paragraph and table are hereby modified:

From:

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

Volume / Title Page Limit NAVSEA DCMA DCAA I. Technical Proposal 250 7 Paper & 14 CDs 1 Paper & 2 CD 1 Paper & 2 CD II. Cost / Price Proposal None 1 Paper & 4 CD 1 Paper & 2 CD 1 Paper & 2 CD III. Solicitation Package None 2 Paper & 4 CD 1 Paper & 2 CD 1 Paper & 2 CD

To:

For Volumes I, II, and III the number of copies required and the page limit are shown in the table below. For each volume, one paper copy and one CD shall be marked “original.”

Volume / Title Page Limit NAVSEA DCMA DCAA I. Technical Proposal 250 7 Paper & 14 CDs 1 Paper & 2 CD 1 Paper & 2 CD II. Cost / Price Proposal None 0 Paper & 4 CD 0 Paper & 2 CD 0 Paper & 2 CD III. Solicitation Package None 2 Paper & 4 CD 1 Paper & 2 CD 1 Paper & 2 CD

Section 3.2 “Volume II: Cost/Price Proposal” fourth paragraph is hereby modified:

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

PageNo. Description i Title Page ii Table Of Contents iii List Of Figures iv List Of Tables v List Of Appendices vi Glossary Of Abbreviations And Acronyms

CHAPTER 1.0 SUMMARY COST/PRICE DATA

Section 1.1 Cost/Price Summaries

CHAPTER 2.0 SUPPORTING COST DATA

Section 2.1 Work Week Assumptions Section 2.2 Direct Costs Section 2.3 Indirect Costs Section 2.4 Inter- and Intra-Divisional Transfers Section 2.5 Subcontractor Costs Section 2.6 Contractor Self-Assessment of Cost Risk Section 2.7 Key Personnel Section 2.8 Cost Summary Tables

CHAPTER 3.0 USE OF EXISTING GOVERNMENT FURNISHED PROPERTY

CHAPTER 4.0 OFFEROR’S ACCOUNTING, PURCHASING, ESTIMATING, AND EARNED VALUE

SYSTEMS AND OFFEROR’S DISCLOSURE STATEMENT

CHAPTER 5.0 DCAA, DCMA, AND OTHER COGNIZANT GOVERNMENT AGENCY OFFICES

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

PageNo. Description i Title Page ii Table Of Contents iii List Of Figures iv List Of Tables v List Of Appendices vi Glossary Of Abbreviations And Acronyms

CHAPTER 1.0 COST/PRICE DATA FORMAT AND INSTRUCTIONS

Section 1.1 Cost/Price Data Format and Instructions by CLIN

CHAPTER 2.0 SUPPORTING COST DATA

Section 2.1 Work Week Assumptions

Section 2.2 Direct Costs Section 2.3 Indirect Costs Section 2.4 Inter- and Intra-Divisional Transfers Section 2.5 Subcontractor Costs Section 2.6 Contractor Self-Assessment of Cost Risk Section 2.7 Key Personnel Section 2.8 Cost Summary Tables

CHAPTER 3.0 USE OF EXISTING GOVERNMENT FURNISHED PROPERTY

CHAPTER 4.0 OFFEROR’S ACCOUNTING, PURCHASING, ESTIMATING, AND EARNED VALUE

SYSTEMS AND OFFEROR’S DISCLOSURE STATEMENT

CHAPTER 5.0 DCAA, DCMA, AND OTHER COGNIZANT GOVERNMENT AGENCY OFFICES

Section 3.2.1 “Summary Cost Data” is hereby modified:

3.2.1 CHAPTER 1.0 – SUMMARY COST DATA

3.2.1.1 Section 1.1 – Cost/Price Summaries

Cost/Price summaries shall be provided by offeror fiscal year and contain the cost/price summary information.

3.2.1 CHAPTER 1.0 – COST/PRICE DATA FORMAT AND INSTRUCTIONS

3.2.1.1 Section 1.1 – Cost/Price Data Format and Instructions by CLIN Offerors shall follow all instructions and present Cost/Price data for all CLINs as described below.

Section 3.2.1.1.2 “CPFF Engineering Service CLINS 0210, 0310, 0410, 0510, 0610, and 0710” is hereby modified:

3.2.1.1.2 CPFF Engineering Service CLINS 0210, 0310, 0410, 0510, 0610, and 0710 Using Table L-2 “CPFF CLINs” for guidance, the Offeror shall provide cost summaries by cost element for each offeror fiscal year. Table L-2 provides the level of detail required of Offerors in pricing each CLIN. Offerors may organize or truncate the presentation of the cost elements differently from that in Table L-2 provided that the cost summary for each CLIN shows each cost element proposed by offeror’s fiscal year, base, rate, and total. The Offeror shall propose a fee percentage not to exceed 8 percent (8%).

3.2.1.1.2 CPFF Engineering Service CLINS 0210, 0310, 0410, 0510, 0610, and 0710 Using Table L-2 “CPFF CLINs” for guidance, the Offeror shall provide cost summaries by cost element for each offeror fiscal year. Table L-2 provides the level of detail required of Offerors in pricing each CLIN. Offerors may organize or truncate the presentation of the cost elements differently from that in Table L-2 provided that the cost summary for each CLIN shows each cost element proposed by offeror’s fiscal year, base, rate, and total. The Offeror shall propose a fee percentage not to exceed 8 percent (8%).

Offerors shall provide the supporting cost data detailed in Chapter 2.0.

Section 3.2.2 “CHAPTER 2.0 – SUPPORTING COST DATA FOR CPIF AND CPFF CLINS 0001, 0002, 0101, 0102, 0201-0210, 0301- 0310, 0401-0410, 0501- 0510, 0601- 0610, and 0701-0710” is hereby modified:

3.2.2 CHAPTER 2.0 – SUPPORTING COST DATA FOR CPIF AND CPFF CLINS 0001, 0002,

0101, 0102, 0201-0210, 0301- 0310, 0401-0410, 0501- 0510, 0601- 0610, and 0701-0710

Poor or inadequate supporting cost data may negatively impact the Government’s evaluation of the Offeror. Omitted data may result in Government assumptions regarding the omitted data. Such assumptions may be detrimental to the Offeror. Therefore, Offerors are encouraged to submit complete disclosures of their pricing methodologies.

Offerors shall round dollar amounts to the nearest whole dollar. The final dollar amount per CLIN in Section B of the offer shall be rounded to the nearest dollar. Offerors shall round ratios, factors, and decimal numbers to four decimal places to the right of the decimal point.

An Offeror’s proposal is presumed to represent its best effort to respond to the solicitation. Accordingly, the Offeror is required to fully explain any inconsistencies between the various volumes of their proposal. If an Offeror makes a “management reduction” or challenge which makes their Offer, or portions of their Offer, below actual anticipated costs, the Offeror shall identify the management reductions and the Offeror’s plan for achieving these reductions.

The supporting cost data shall be organized by section as described below. Each section shall be titled and tabbed for easy identification. The Offeror shall provide cost and price data, and supporting explanations and rationale, in an orderly, organized, and easy-to-follow format.

3.2.2 CHAPTER 2.0 – SUPPORTING COST DATA FOR CPIF AND CPFF CLINS 0001, 0002,

0101, 0102, 0201-0210, 0301- 0310, 0401-0410, 0501- 0510, 0601- 0610, and 0701-0710

Poor or inadequate supporting cost data may negatively impact the Government’s evaluation of the Offeror. Omitted data may result in Government assumptions regarding the omitted data. Such assumptions may be detrimental to the Offeror. Therefore, Offerors are encouraged to submit complete disclosures of their pricing methodologies.

The final dollar amount per CLIN in Section B of the offer shall be rounded to the nearest dollar. Offerors shall round ratios, factors, and decimal numbers to four decimal places to the right of the decimal point.

An Offeror’s proposal is presumed to represent its best effort to respond to the solicitation. Accordingly, the Offeror is required to fully explain any inconsistencies between the various volumes of their proposal. If an Offeror makes a “management reduction” or challenge which makes their Offer, or portions of their Offer, below actual anticipated costs, the Offeror shall identify the management reductions and the Offeror’s plan for achieving these reductions.

The Offeror shall provide cost and price data, and supporting explanations and rationale, in an orderly, organized, and easy-to-follow format.

Section 3.2.2.1 “Material” is hereby modified:

3.2.2.2.1 Material

The Offeror shall provide a detailed Bill of Material (BOM) for each CLIN. Identify and discuss the types and quantities of the proposed direct material. Identify how each item is purchased and the methodology used to price each item such as:

a) Vendor quotations;

b) Prior purchase orders;

c) Catalog prices;

d) Engineering estimate;

e) Sole source; and

f) Competitive purchases.

Provide rationale and history for any estimates and factors used in the calculations of the proposed cost of the BOMs.

3.2.2.2.1 Material

The Offeror shall provide a detailed Bill of Material (BOM) for each CLIN (and for each quantity within each CLIN if stepladder priced). Identify and discuss the types and quantities of the proposed direct material. Identify how each item is purchased and the methodology used to price each item such as:

a) Vendor quotations;

b) Prior purchase orders;

c) Catalog prices;

d) Engineering estimate;

e) Sole source; and

f) Competitive purchases.

Provide rationale and history for any estimates and factors used in the calculations of the proposed cost of the BOMs.

(End of Summary of Changes)