COMBINED_SYNOPSIS_SOLICITATION_16-T-4203_Edited_PDB.docx

MILITARY SEALIFT COMMAND

N10 - CONTRACTS AND BUSINESS MANAGEMENT DIRECTORATE

COMBINED SYNOPSIS/SOLICITATION TEMPLATE

Military Sealift Command Combined Synopsis and Solicitation Notice Information

1. This is a combined synopsis/solicitation for commercial items prepared in accordance with Subpart 12.6, as supplemented with additional information included in this notice. This announcement constitutes the only solicitation; proposals are being requested and a written solicitation will not be issued.

2. Solicitation number is N32205-16-T-4203 and is being issued as a Request for Quotes (RFQ).

3. The solicitation document and incorporated provisions and clauses are those in effect through Federal Acquisition Circular 2005-94 effective 19 Jan 2017. See http://farsite.hill.af.mil/vffara.htm for this information.

4. The associated NAICS code is 488390 and this procurement:

|X| is not being set-aside for small businesses. The size standard is $38.5 Millions.

|_| is being set-aside for small businesses.

5. Military Sealift Command intends to award a firm fixed price purchase order for the procurement of two lifeboat systems, each consisting of one (1) Safety of Life at Sea (SOLAS) totally enclosed 120-person lifeboat, one (1) SOLAS lifeboat davit, one (1) SOLAS lifeboat winch and shall also include spare parts, technical manuals and testing. The statutory authority permitting full and open competition under simplified acquisitions is FAR Part 13.5, Title 41 U.S.C. § 1901 Test program for Certain Commercial Items.

The table below lists the Contract Line Item Number(s) (CLIN(s)) and items, quantities and units of measure, inclusive of any applicable options:

1 Lot

WPM Compliance

Total

6. STATEMENT OF WORK

See the attachment for complete statement of work. Contact Tommy Hale at tommy.a.hale@navy.mil for drawings.

7. The period of performance is upon award to February 1, 2018. Delivery and acceptance will occur at the installing location at the beginning of the installation period. Projected schedule is: USNS ZEUS on the East Coast early February 2018.

Estimated Delivery Date if Different than Requested Date____________ Are items being imported? ________ If so, from what country? ____________

8. The provision at FAR 52.212-1, Instructions to Offerors – Commercial Itmes (Oct 2015) applies to this acquisition and is amended as follows:

52.212-1 (ADDENDUM) ADDITIONAL INSTRUCTIONS TO OFFERORS--COMMERCIAL ITEMS

a. This procurement is a FAR Part 12 acquisition being conducted under FAR Subpart 13.5. Accordingly, simplified acquisitions procedures apply. After receipt of quotes, the Government may without notice, negotiate with and, if desired, seek a quote revision from as many or as few quoters as it, in its discretion, deems appropriate.

b. The term “offeror” or “offer” as used in FAR 52.212-1 shall be understood to mean “quoter” and “quote,” respectively. Further, the term “award” shall be understood to describe the Government’s issuance of an purchase order.

c. The following paragraphs in FAR 52.212-1 shall not apply to this RFQ: b, c, f (except f(4)), and l.

d. The Government will consider all quotes that are timely received and may consider late quotes. Failure of a quote to address any items required in the submission package may make a quote unacceptable.

e. SUBMISSION PACKAGE

1. The quote shall contain the following:

a. Price quote which identifies the requested item(s), unit price, and extended price.

b. Shipping Price (The Government requests that shipping costs be incorporated into the price of each item rather than a separate line for total shipping costs. The Government will spread the shipping costs across all lines upon award if quoted as a separate line item.)

c. Total Price

d. Prompt Payment Terms

e. Remittance address, Tax identification Number, DUNS number and Cage Code

All quoters must include a completed copy of FAR 52.212-3, Offeror Representations and Certifications – Commercial Items with its offer.

2. Responses to this solicitation are due 09 May 2017 at 0800 local time, Norfolk, VA. LATE QUOTES MAY NOT BE CONSIDERED FOR EVALUATION. Quotes may be emailed to tommy.a.hale@navy.mil or faxed via 757-443-5982 Attn: Tommy Hale. Please reference the solicitation number on your quote.

3. Offers/quotes submitted in response to this solicitation shall not contain nor be subject to the offeror's/vendor's standard commercial terms and conditions. Any offer/quote submitted in response to this solicitation which includes the offeror's/vendor's standard commercial terms and conditions may be considered a material defect and may be rejected as being non-responsive to the solicitation.

4. BASIS FOR AWARD:

Award will be made to the responsible, technically acceptable quoter, whose quote, conforming to the Request for Quotation, offers the lowest evaluated price.

9. Provision 52.212-2 Evaluation – Commercial Items (Oct 2014) applies to this acquisition and is incorporated by reference. The evaluation and award procedures in FAR 13.106 apply.

Quoters shall submit quotes:

Technical Quotes Past Performance Price Quote – Should be submitted separate from Technical and Past Performance.

Technical Quotes Quoter must meet the below technical evaluators factors.

Vendor can provide lifeboats, davits and winches that are USCG 160.135, 160.132 and 160.115 certified and SOLAS/LSA compliant.

Vendor can provide lifeboats and davits that fit within the space constraints listed in paragraph 2.6.

Vendor can provide lifeboats that are delivery ready for installation and operation.

Vendor can provide a lifeboat with a capacity of at least 120 people.

Vendor can provide a lifeboat with engine(s) that are marine diesel-type and capable of efficient operation with marine gas oil/distillate fuel marine as fuel.

Vendor addresses all other requirements of the specification as stated or with technically viable solution.

Past Performance Quoters are requested to provide information on up to three (3) previous Government/Commercial contracts whose effort is/was recent and relevant to the effort required by this solicitation.

1. “Recent” is defined as a contract in-progress or completed within the last three (3) years. If the quoter has not had three (3) Government contracts within the last three (3) years, information on recent and relevant subcontracts and/or commercial contracts may be submitted.

1. “Relevant” is defined as a contract that is of similar scope, magnitude, complexity to the requirements as set forth in this solicitation.

1. Scope: Experience in the areas defined in PWS.

1. Magnitude: The measure of the similarity of the volume, dollar value and/or duration of the work actually performed under the quoter’s submitted contracts to the PWS.

1. Complexity: The measure of the similarity of technical difficulty, managerial intricacy and/or required coordination of efforts and disciplines performed by the quoter in its submitted contracts to the PWS. For complexity, not only will the tasks performed by the quoter be considered, but also the offeror’s ability to coordinate tasks (e.g., concurrent performance requirements).

A Past Performance Data Sheet (Attachment 1) is requested to be submitted for each contract to be considered as past performance. Quoters shall provide a detailed explanation demonstrating the similarity of the contracts to the requirements of this solicitation; a detailed description of the work performed for the contract; and the role performed, including whether the quoter acted as a prime contractor or a subcontractor. Quoters are responsible for the accuracy of all data provided. Past performance information regarding predecessor companies, key personnel who have relevant experience and subcontractors that will perform major or critical aspects of the requirement may be provided as past performance submissions.

For each of the contracts the quoter describes in a Performance Data Sheet (Attachment 1), the quoter is requested to provide a Past Performance Questionnaire (Attachment 2) to a reference at the organization that awarded the contract. It is requested that the reference, not the quoter, email or fax the completed Past Performance Questionnaire (Attachment 2) BEFORE THE DUE DATE FOR PROPOSALS directly to Tommy Hale, Military Sealift Command, 471 East C Street-Bldg SP-64, Norfolk, VA 23511, e-mail: tommy.a.hale@navy.mil; The quoter, NOT THE GOVERNMENT, is responsible for ensuring that the Government receives a sufficient number of questionnaires.

All quoters are required to address historical compliance with the requirements of FAR Part 52.219-8 (Utilization of Small Business Concerns) in the Performance Data Sheet (Attachment 1).

(End of Addendum)

10. Provision 52.212-3 Offeror Representations and Certifications -- Commercial Items (Apr 2016) applies to this acquisition and is incorporate by reference. The offeror shall complete only paragraphs (b) of this provision if the Offeror has completed the annual representations and certification electronically via the System for Award Management (SAM) Web site accessed through http://www.acquisition.gov . If the Offeror has not completed the annual representations and certifications electronically, the Offeror shall complete only paragraphs (c) through (r) of this provision.

11. Clause FAR 52.212-4, Contract Terms and Conditions -- Commercial Items (May 2015) applies to this acquisition. Inspection/ Acceptance – FOB Destination.

12. Clause FAR 52.212-5, Contract Terms and Conditions Required to Implement Statutes or Executive Orders -- Commercial Items (Mar 2016) and Devision 2013 – O0019 (Mar 2016) applies to this acquisition and isincorporated by reference.

52.212-5 Contract Terms and Conditions Required to Implement Statutes or Executive Orders – Commercial Items

(End of clause)

52.222-42 STATEMENT OF EQUIVALENT RATES FOR FEDERAL HIRES (MAY 2014)

In compliance with the Service Contract Labor Standards statute and the regulations of the Secretary of Labor (29 CFR part 4), this clause identifies the classes of service employees expected to be employed under the contract and states the wages and fringe benefits payable to each if they were employed by the contracting agency subject to the provisions of 5 U.S.C. 5341 or 5332.

THIS STATEMENT IS FOR INFORMATION ONLY: IT IS NOT A WAGE DETERMINATION

Employee Class Monetary Wage-Fringe Benefits

(End of clause)

52.233-2 SERVICE OF PROTEST (SEP 2006)

(a) Protests, as defined in section 33.101 of the Federal Acquisition Regulation, that are filed directly with an agency, and copies of any protests that are filed with the Government Accountability Office (GAO), shall be served on the Contracting Officer (addressed as follows) by obtaining written and dated acknowledgment of receipt from Patrick Brown, Military Sealift Command Norfolk, 471 East C Street, Bldg SP-64, Code N401-A2, Norfolk, Va 23511-2419.

(b) The copy of any protest shall be received in the office designated above within one day of filing a protest with the GAO.

(End of provision)

Addendum to 52.233-2 SERVICE OF PROTEST

Interested parties may request an independent review of their protest as an alternative to consideration by the contracting officer or as an appeal of the contracting officer's decision on their protest. See FAR 33.103. Requests for independent review shall be addressed to Code N10 or N10X, Military Sealift Command, 471 East C Street, BLDG Sp-64, Norfolk, VA 23511. MSC encourages potential protesters to discuss their concerns with the contracting officer prior to filing a protest.

252.203-7998 Prohibition on Contracting with Entities that Require Certain Internal Confidentiality Agreements—Representation (DEVIATION 2015-O0010) (FEB 2015)

(a) In accordance with section 743 of Division E, Title VIII, of the Consolidated and Further Continuing Resolution Appropriations Act, 2015 (Pub. L. 113-235), Government agencies are not permitted to use funds appropriated (or otherwise made available) under that or any other Act for contracts with an entity that requires employees or subcontractors of such entity seeking to report fraud, waste, or abuse to sign internal confidentiality agreements or statements prohibiting or otherwise restricting such employees or contactors from lawfully reporting such waste, fraud, or abuse to a designated investigative or law enforcement representative of a Federal department or agency authorized to receive such information.

(b) The prohibition in paragraph (a) of this provision does not contravene requirements applicable to Standard Form 312, Form 4414, or any other form issued by a Federal department or agency governing the nondisclosure of classified information.

(c) Representation. By submission of its offer, the Offeror represents that it does not require employees or subcontractors of such entity seeking to report fraud, waste, or abuse to sign or comply with internal confidentiality agreements or statements prohibiting or otherwise restricting such employees or contactors from lawfully reporting such waste, fraud, or abuse to a designated investigative or law enforcement representative of a Federal department or agency authorized to receive such information.

(End of provision)

52.252-2 CLAUSES INCORPORATED BY REFERENCE (FEB 1998)

This contract incorporates one or more clauses by reference, with the same force and effect as if they were given in full text. Upon request, the Contracting Officer will make their full text available. Also, the full text of a clause may be accessed electronically at this/these address(es):

http://acquisition.gov/far http://www.acq.osd.mil/dpap/dars/dfarspgi/current

(End of clause)

52.252-6 AUTHORIZED DEVIATIONS IN CLAUSES (APR 1984)

(a) The use in this solicitation or contract of any Federal Acquisition Regulation (48 CFR Chapter 1) clause with an authorized deviation is indicated by the addition of "(DEVIATION)" after the date of the clause.

(b) The use in this solicitation or contract of any Department of the Navy Acquisition Regulations (48 CFR Chapter 1) clause with an authorized deviation is indicated by the addition of "(DEVIATION)" after the name of the regulation.

(End of clause)

252.203-7999 Prohibition on Contracting with Entities that Require Certain Internal Confidentiality Agreements (DEVIATION 2015-O0010)(FEB 2015)

(a) The Contractor shall not require employees or subcontractors seeking to report fraud, waste, or abuse to sign or comply with internal confidentiality agreements or statements prohibiting or otherwise restricting such employees or contactors from lawfully reporting such waste, fraud, or abuse to a designated investigative or law enforcement representative of a Federal department or agency authorized to receive such information.

(b) The Contractor shall notify employees that the prohibitions and restrictions of any internal confidentiality agreements covered by this clause are no longer in effect. (c) The prohibition in paragraph (a) of this clause does not contravene requirements applicable to Standard Form 312, Form 4414, or any other form issued by a Federal department or agency governing the nondisclosure of classified information.

(d)(1) In accordance with section 743 of Division E, Title VIII, of the Consolidated and Further Continuing Resolution Appropriations Act, 2015, (Pub. L. 113-235), use of funds appropriated (or otherwise made available) under that or any other Act may be prohibited, if the Government determines that the Contractor is not in compliance with the provisions of this clause.

(2) The Government may seek any available remedies in the event the Contractor fails to perform in accordance with the terms and conditions of the contract as a result of Government action under this clause.

(End of clause)

252.204-7008 COMPLIANCE WITH SAFEGUARDING COVERED DEFENSE INFORMATION CONTROLS (OCT 2016)

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

Controlled technical information, covered contractor information system, covered defense information, cyber incident, information system, and technical 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 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 service or system operated on behalf of the Government (see 252.204-7012(b)(2))--

(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) that are in effect at the time the solicitation is issued or as authorized by the contracting officer 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 are 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.

(End of provision)

252.204-7012 SAFEGUARDING COVERED DEFENSE INFORMATION AND CYBER INCIDENT REPORTING (OCT 2016)

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

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 unclassified 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 controlled technical information or other information, as described in the Controlled Unclassified Information (CUI) Registry at http://www.archives.gov/cui/registry/category-list.html, that requires safeguarding or dissemination controls pursuant to and consistent with law, regulations, and Governmentwide policies, and is--

(1) Marked or otherwise identified in the contract, task order, or delivery order and provided to the contractor by or on behalf of DoD in support of the performance of the contract; or

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

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.

Information system means a discrete set of information resources organized for the collection, processing, maintenance, use, sharing, dissemination, or disposition of information.

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 covered defense information is recorded, stored, or printed within a covered contractor 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.

Rapidly report 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--Noncommercial 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 on all covered contractor information systems. To provide adequate security, the Contractor shall implement, at a minimum, the following information security protections:

(1) For covered contractor information systems that are part of an information technology (IT) service or system operated on behalf of the Government, the following security requirements apply:

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

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

(2) 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) of this clause, the following security requirements apply:

(i) Except as provided in paragraph (b)(2)(ii) of this clause, the covered contractor information system shall be subject to 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'' (available via the internet at http://dx.doi.org/10.6028/NIST.SP.800-171) in effect at the time the solicitation is issued or as authorized by the Contracting Officer.

(ii)(A) The Contractor shall implement NIST SP 800-171, as soon aspractical, but not later than December 31, 2017. For all contracts awarded prior to October 1, 2017, the Contractor shall notify the DoD Chief Information Officer (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.

(B) The Contractor shall submit requests to vary from NIST SP 800-171 in writing to the Contracting Officer, for consideration by the DoD CIO. The Contractor need not implement any security requirement adjudicated by an authorized representative of the DoD CIO to be nonapplicable or to have an alternative, but equally effective, security measure that may be implemented in its place.

(C) If the DoD CIO has previously adjudicated the contractor's requests indicating that a requirement is not applicable or that an alternative security measure is equally effective, a copy of that approval shall be provided to the Contracting Officer when requesting its recognition under this contract.

(D) If the Contractor intends to use an external cloud service provider to store, process, or transmit any covered defense information in performance of this contract, the Contractor shall require and ensure that the cloud service provider meets security requirements equivalent to those established by the Government for the Federal Risk and Authorization Management Program (FedRAMP) Moderate baseline (https://www.fedramp.gov/resources/documents/) and that the cloud service provider complies with requirements in paragraphs (c) through (g) of this clause for cyber incident reporting, malicious software, media preservation and protection, access to additional information and equipment necessary for forensic analysis, and cyber incident damage assessment.

(3) Apply other information systems security measures when the Contractor reasonably determines that information systems security measures, in addition to those identified in paragraphs (b)(1) and (2) of this clause, may be required to provide adequate security in a dynamic environment or to accommodate special circumstances (e.g., medical devices) and any individual, isolated, or temporary deficiencies based on an assessed risk or vulnerability. These measures may be addressed in a system security plan.

(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 and identified in the contract, 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. When the Contractor or subcontractors discover and isolate malicious software in connection with a reported cyber incident, submit the malicious software to DoD Cyber Crime Center (DC3) in accordance with instructions provided by DC3 or the Contracting Officer. Do not send the malicious software to 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 covered defense information, including subcontracts for commercial items, without alteration, except to identify the parties. The Contractor shall determine if the information required for subcontractor performance retains its identity as covered defense information and will require protection under this clause, and, if necessary, consult with the Contracting Officer; and

(2) Require subcontractors to--

(i) Notify the prime Contractor (or next higher-tier subcontractor) when submitting a request to vary from a NIST SP 800-171 security requirement to the Contracting Officer, in accordance with paragraph (b)(2)(ii)(B) of this clause; and

(ii) Provide the incident report number, automatically assigned by DoD, to the prime Contractor (or next higher-tier subcontractor) as soon as practicable, when reporting a cyber incident to DoD as required in paragraph (c) of this clause.

252.232-7006 WIDE AREA WORKFLOW PAYMENT INSTRUCTIONS (JUN 2012)

(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 Central Contractor Registration 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).

INVOICE

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

GOVERNMENT

(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 N32205 Issue By Admin Inspect By Ship To Code N62387 Ship From Code Mark For Code Service Approver Service Acceptor Accept at Other

LPO

DCAA Auditor Other

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

NOT APPLICABLE

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

MSCHQ_WAWF@navy.mil

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

252.232-7010 LEVIES ON CONTRACT PAYMENTS (DEC 2006)

(a) 26 U.S.C. 6331(h) authorizes the Internal Revenue Service (IRS) to continuously levy up to 100 percent of contract payments, up to the amount of tax debt.

(b) When a levy is imposed on a payment under this contract and the Contractor believes that the levy may result in an inability to perform the contract, the Contractor shall promptly notify the Procuring Contracting Officer in writing, with a copy to the Administrative Contracting Officer, and shall provide--

(1) The total dollar amount of the levy;

(2) A statement that the Contractor believes that the levy may result in an inability to perform the contract, including rationale and adequate supporting documentation; and

(3) Advice as to whether the inability to perform may adversely affect national security, including rationale and adequate supporting documentation.

(c) DoD shall promptly review the Contractor's assessment, and the Procuring Contracting Officer shall provide a written notification to the Contractor including--

(1) A statement as to whether DoD agrees that the levy may result in an inability to perform the contract; and

(2)(i) If the levy may result in an inability to perform the contract and the lack of performance will adversely affect national security, the total amount of the monies collected that should be returned to the Contractor; or

(ii) If the levy may result in an inability to perform the contract but will not impact national security, a recommendation that the Contractor promptly notify the IRS to attempt to resolve the tax situation.

(d) Any DoD determination under this clause is not subject to appeal under the Contract Disputes Act.

MSC SPECIFIC WIDE AREA WORKFLOW (WAWF) INSTRUCTIONS (AUG 2012)

The information contained in this instruction is supplemental to DFARS 252.232-7006.

The information contained in the table in DFARS 252.232-7006 is for WAWF purposes only. Information included in DFARS 252.232-7006 and this WAWF instruction apply only to WAWF Invoicing and WAWF Receiving Reports. Contradictory information elsewhere in this contract, e.g. Ship to DoDAAC, shall be followed per the terms and conditions of the contract.

When entering the invoice into WAWF, the Contractor shall fill in the DoDAAC fields or DoDAAC extensions exactly as shown in the table in DFARS 252.232-7006. Fields that should not be filled in when entering the invoice into WAWF will be indicated with the direction, "Leave Blank."

In some situations the WAWF system will pre-populate the "Pay DoDAAC," "Admin By DoDAAC" and "Issue By DoDAAC." The Contractor shall verify that those DoDAACs automatically entered by the WAWF system match the information in the table in DFARS 252.232-7006. If these DoDAACs do not match, then the Contractor shall correct the field(s).

If Receiving Reports are required, ensure that the "Inspection" and "Acceptance" defaults of "destination" for both fields are not changed in the WAWF online interface.

The CLINs on the WAWF invoice shall be entered exactly as set forth in the contract document including CLIN number (e.g. 0001), Quantity (may be adjusted for actual quantity or dollar value delivered and invoiced), and Unit Price (e.g. $1.00). The dollar amounts on each CLIN or SubCLIN on the WAWF invoice shall reflect final performance values, but in no instance can the dollar amount for each CLIN or SubCLIN exceed what is specified in the contract document. The Contractor shall bill to the lowest level, e.g., the SubCLIN level. The Quantity and Unit of Measure fields must be filled out exactly as indicated in the CLINs and SubCLINs to reduce the possibility of the invoice being delayed or rejected during processing.

Before closing out of an invoice session in WAWF, but after submitting the document or documents, the Contractor will be given the option to send additional email notifications by clicking on the "Send More Email Notifications" link that appears on the page. The Contractor shall click on this link and add the Technical Point of Contact's (TPOC) or Contracting Officer's Representative's (COR) email address in the first email address block and add any other additional email addresses desired in the following blocks. This additional notification to the Government is important to ensure the acceptor/receiver is aware that the invoice documents have been submitted into the WAWF system.

SHIP & BASE ACCESS

Vendors are responsible for correctly submitting forms/applications. Vendors are encouraged to monitor email using “Request a Read Receipt” function and to confirm receipt of facsimile transmissions.

Due to enhanced security measures, ship and base access is required for pre-award ship visits (e.g. ship-check) and for contract performance. Specifically the following permissions are required:

1. El Paso Intelligence Center (EPIC) personnel screening requirement

2. Base/Repair Facility Access Request

3. Vehicle Access Request

4. Ship Access List (vendor-provided)

All forms are available for download on the MSC contracts webpage at http://www.msc.navy.mil. Click on “Contracts” in the upper right corner. “EPIC template” is under “Reference” subheading. Click on “Online Library of Common Documents” for all other forms.

EPIC: Required for access to MSC vessels. Complete EPIC form strictly adhering to format requirements and forward to (CONUS East Coast repairs) msc.norfolk.epic@navy.mil (CONUS West Coast and HI repairs) MSC.SSUSD.EPIC@NAVY.MIL. EPIC personnel screening requests are desired seven calendar days prior to performance start date. Requests will be managed as expeditiously as circumstances permit. Vendor will be notified by MSFSC of personnel who are denied access to the vessel.

Base/Repair Facility Access: Permit is required to access Navy facilities. Base/Repair Facility Access Request is desired seven days prior to ship check or performance start date. Submit forms per the document instruction and to the Port Engineer. A courtesy copy (CONUS West Coast performance locations only) to Ermanno Magliulo, Engineering Director, at ermanno.magliulo@navy.mil will be appreciated.

RAPIDGate® is being implemented for access to DoD facilities in CONUS, HI, Guam and Puerto Rico. Vendor is responsible to acquire RAPIDGate® status and destination base individual access badge(s) activation prior to performance start date. Delays that may result from inadequate planning are contractor responsibility. Vendor instructions and program information is available at http://www.RAPIDGate.com or tel. 877.727.4342. RAPIDGate® access requires (in succession) (1) Individual Base Commander approval for vendor to access base, (2) Successful vendor RAPIDGate® company annual enrollment, (3) Company employee individual enrollment and possession of RAPIDGate® identification badge for single base or multiple base (enterprise) access. Vendor is responsible to confirm that each employee held annual RAPIDGate® badge is active for the specific facility and performance period in accordance with RAPIDGate® User Agreement (http://www.RAPIDGate.com).

Additional access permissions may be required such as Navy Base Point Loma “Enclave Access request form”.

Vehicle Access: Required for vehicle access to Navy facilities. Follow supplemental instructions on Base Access forms or base-specific vehicle access forms.

Ship Access List* (Vendor-Provided): On company letterhead attachment via email, the vendor is required to provide the ship master (courtesy copy the Port Engineer) with an accurate, current list of performing personnel prior to being admitted aboard the vessel. Under no circumstances will a hand-delivered list be accepted.

WOOD PACKAGING MATERIAL (WPM) - ADDITIONAL DELIVERY INSTRUCTIONS

In accordance with the requirements of International Standards for Phytosanitary Measures (ISPM) 15, the following commercial heat treatment process has been approved by the American Lumber Standards Committee (ALSC) and is required for all Wood Packaging Material (WPM). WPM is defined as wood pallets, skids, load boards, pallet collars, wooden boxes, reels, dunnage, crates, frames, and cleats. Packaging materials exempt from the requirements are materials that have undergone a manufacturing process such as corrugated fiberboard, plywood, particleboard, veneer and oriented strand board. All WPM shall be constructed from Heat Treated (HT to 56 degrees Centigrade for 30 minutes) lumber and certified by an accredited agency recognized by the ALSC in accordance with Wood Packaging Material Policy and Wood Packaging Material Enforcement Regulations (see URL: http://www.alsc.org). All materials must include certification markings in accordance with ALSC standards and be placed in an unobstructed area that will be readily visible to inspectors. Pallet markings shall be applied to the stringer or block on diagonally opposite sides and ends of the pallet and be contrasting and clearly visible. All dunnage used in configuring and/or securing the load shall also comply with ISPM 15 and be marked with an ALSC approved "DUNNAGE" stamp. Failure to comply with the requirements of this restriction may result in refusal, destruction, or treatment of materials at the point of entry.

Enterprise-Wide Contractor Manpower Reporting Application (ECMRA)

The contractor shall report contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for the Military Sealift Command via a secure data collection site. Contracted services excluded from reporting are based on Product Service Code (PSCs). The excluded PSCs are:

(1) W, Lease/Rental of Equipment;

(2) X, Lease/Rental of Facilities

(3) Y, Construction of Structures and Facilities;

(4) S, Utilities ONLY ; and

(5) V, Freight and shipping ONLY.

The contractor is required to completely fill in all required data fields using the following web address:

https://doncmra.nmci.navy.mil.

Reporting inputs will be for the labor executed during the period of performance during each Government fiscal year (FY), which runs October 1 through September 30. While inputs may be reported any time during the FY, all data shall be reported no later than October 31 of each calendar year, beginning with 2013. Contractors may direct questions to the help desk at: https://doncmra.nmci.navy.mil.

252.209-7991 Representation by Corporations Regarding an Unpaid Delinquent Tax Liability or a Felony Conviction under any Federal Law—Fiscal Year 2016 Appropriations.

(a) In accordance with section 101(a) of the Continuing Appropriations Act, 2016 (Pub. L. 114-53) and any subsequent FY 2016 appropriations act that extends to FY 2016 funds the same restrictions as are contained in sections 744 and 745 of division E, title VII, of the Consolidated and Further Continuing Appropriations Act, 2015 (Pub. L. 113-235), none of the funds made available by this or any other Act may be used to enter into a contract with any corporation that—

(1) Has any unpaid Federal tax liability that has been assessed, for which all judicial and administrative remedies have been exhausted or have lapsed, and that is not being paid in a timely manner pursuant to an agreement with the authority responsible for collecting the tax liability, where the awarding agency is aware of the unpaid tax liability, unless the agency has considered suspension or debarment of the corporation and made a determination that this further action is not necessary to protect the interests of the Government; or

(2) Was convicted of a felony criminal violation under any Federal law within the preceding 24 months, where the awarding agency is aware of the conviction, unless the agency has considered suspension or debarment of the corporation and made a determination that this action is not…