Amendment_0004__SAH.doc

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION SF 30 - BLOCK 14 CONTINUATION PAGE

The following have been added by full text:

AMENDMENT 0004

The following are questions received by this Agency and our answers:

1. Question: The following clauses in Section I of the RFP have a date that is older than what is in the current FAR at http://farsite.hill.af.mil/vffar1.htm:

52.204-10 - Reporting Executive Compensation and First-Tier Subcontract Awards

52.219-8 - Utilization of Small Business Concerns

52.222-19 - Child Labor - Cooperation with Authorities and Remedies

252.204-7000 - Disclosure Of Information

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

252.245-7004 - Reporting, Reutilization, and Disposal

Answer: The RFP has been updated with the newer version of the clauses above and the older versions have been deleted.

2. Question: CDRLs T003 and T004 both reference SOW paragraph 3.3.3 for the Production Acceptance Test Report. Section 3.3.3 does not indicate a reference to the Production Acceptance Test Report. A search of the SOW .pdf file indicates T003 is referenced in SOW 3.2.4, 3.2.2.8, and 3.3.4 while T004 is only referenced in SOW 3.3.4.

Answer: CDRLs T003 and T004 SOW references are revised as shown below. Additionally, for CLINs 0020 and 0021, the SOW paragraph references listed in the CLIN extended descriptions have been revised as shown below in Section B.

CDRL T003 Block 5 is revised as follows:

From:

5. Contract Reference SOW Paragraphs 3.2.2.8 & 3.3.3

To:

5. Contract Reference SOW Paragraphs 3.1.4, 3.2.2.8 & 3.3.4

CDRL T004 Block 5 is revised as follows:

From:

5. Contract Reference SOW Paragraphs 3.3.3

To:

5. Contract Reference SOW Paragraphs 3.3.4

3. Question: With reference to the technical specification, Golden model: where is the position of the front (driving wheels)?

Answer: Drive wheels are not depicted on the Golden Model. Placement is to be determined by the offeror while meeting all other requirements of the performance specification (including the requirement of a zero turning radius).

4. Question: With reference to the technical specification, having the need to use small wheels with high load capacity: what is the tire pressure (nitrogen?) that can be handled on a carrier?

Answer: Nitrogen is used for inflation. Aircraft tire inflation test pressures of up to 385 psi are used. The shipboard nitrogen servicing cart has much more pressure capability. Other requirements of the performance specification such as deck load limits are to be taken into account with tire pressures, tire patch size and tire loading.

5. Question: With reference to the technical specification, on the actual SD2: what is the installed engine power and torque?

Answer: The SD-2 uses a Detroit Diesel 3-53N engine with rated gross power = 98 BHP @ 2800 RPM and maximum torque = 205 lb-ft @ 1800 RPM.

6. Question: With reference to the technical specification paragraph 3.2.1.3 b (4), we need the drawings 1117AS242 and 1117AS243.

Answer: Instructions on how to obtain drawings are provided in the RFP on page 28 and updated in Amendment 0001 that was posted on 07 Dec 2016.

7. Question: With reference to the technical specification paragraph 3.2.1.9 b "2 red LED flood lights… to illuminate the area under the aircraft"... However, some (not all!) pictures of the SD2 show white flood lights on the front, red lights on the end ?

Answer: The requirement for red LED floodlights in both locations is correct.

8. Question: With reference to the technical specification paragraph 3.2.2 b: where we can find the "further aircraft interface details provided as attachment (1)”?

Answer: The golden models included with the RFP are Attachment 1 and include aircraft interface details.

9. Question: With reference to the technical specification paragraph 3.2.2 f: we need information/dimension of A-A-59545 Type II jacks

Answer: The specification A-A-59545 is publicly available on the internet and can be downloaded from sites such as http://www.everyspec.com.

10. Question: With reference to the technical specification paragraph 3.2.2 g: we need information/drawing of ALBAR tow bar 1479AS200-1

Answer: Instructions on how to obtain drawings are provided in the RFP on page 28 and updated in Amendment 0001 that was posted on 07 Dec 2016.

11. Question: With reference to the technical specification paragraph 3.2.4 d: Can the ramp height be less than 2,75 inches?

Answer: The requirement of 4 inches for the ramp height is correct.

12. Question: With reference to the technical specification paragraph 3.2.7 d (2) emergency stop: activation should stop the tractor movement without killing the engine?

Answer: Emergency stop is to shut down engine.

13. Question: With reference to the technical specification paragraph 3.2.2 g (3) what is the coefficient of friction applicable for this request (min. drawbar pull not less than 3,070 lbs)?

Answer: Coefficient of friction between the deck and the material of the SAH tires will remain the same in all drawbar pull calculations. Only the normal force on the drive tires will vary.

SECTION B - SUPPLIES OR SERVICES AND PRICES

CLIN 0020

The CLIN extended description has changed from:

Production Acceptance Test Plan & Procedures in accordance with SOW Paragraphs 3.2.2.8 & 3.3.3 and Contract Data Requirements List (CDRL) T003.

To:

Production Acceptance Test Plan & Procedures in accordance with SOW Paragraphs 3.1.4, 3.2.2.8 & 3.3.4 and Contract Data Requirements List (CDRL) T003..

CLIN 0021

The CLIN extended description has changed from:

Production Acceptance Test Report in accordance with SOW Paragraph 3.3.3 and Contract Data Requirements List (CDRL) T004.

To:

Production Acceptance Test Report in accordance with SOW Paragraph 3.3.4 and Contract Data Requirements List (CDRL) T004..

SECTION I - CONTRACT CLAUSES

The following have been added by reference:

The following have been added by full text:

252.204-7000 252.204-7000

DISCLOSURE OF INFORMATION (OCT 2016)

(a) The Contractor shall not release to anyone outside the Contractor's organization any unclassified information, regardless of medium (e.g., film, tape, document), pertaining to any part of this contract or any program related to this contract, unless—

(1) The Contracting Officer has given prior written approval;

(2) The information is otherwise in the public domain before the date of release; or

(3) The information results from or arises during the performance of a project that involves no covered defense information (as defined in the clause at DFARS 252.204-7012) and has been scoped and negotiated by the contracting activity with the contractor and research performer and determined in writing by the contracting officer to be fundamental research (which by definition cannot involve any covered defense information), in accordance with National Security Decision Directive 189, National

Policy on the Transfer of Scientific, Technical and Engineering Information, in effect on the date of contract award and the Under Secretary of Defense (Acquisition, Technology, and Logistics) memoranda on Fundamental Research, dated May 24, 2010, and on Contracted Fundamental Research, dated June 26, 2008 (available at DFARS PGI 204.4).

(b) Requests for approval under paragraph (a)(1) shall identify the specific information to be released, the medium to be used, and the purpose for the release. The Contractor shall submit its request to the Contracting Officer at least 10 business days before the proposed date for release.

(c) The Contractor agrees to include a similar requirement, including this paragraph (c), in each subcontract under this contract. Subcontractors shall submit requests for authorization to release through the prime contractor to the Contracting Officer.

252.204-7012 252.204-7012 SAFEGUARDING COVERED DEFENSE INFORMATION AND CYBER INCIDENT INFORMATION (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 as practical, 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.

52.204-10 52.204-10

REPORTING EXECUTIVE COMPENSATION AND FIRST-TIER SUBCONTRACT AWARDS (OCT 2016)

(a) Definitions. As used in this clause:

“Executive” means officers, managing partners, or any other employees in management positions.

“First-tier subcontract” means a subcontract awarded directly by the Contractor for the purpose of acquiring supplies or services (including construction) for performance of a prime contract. It does not include the Contractor’s supplier agreements with vendors, such as long-term arrangements for materials or supplies that would benefit multiple contracts and/or the costs of which are normally applied to a Contractor’s general and administrative expenses or indirect cost.

“Month of award” means the month in which a contract is signed by the Contracting Officer or the month in which a first-tier subcontract is signed by the Contractor.

“Total compensation” means the cash and noncash dollar value earned by the executive during the Contractor’s preceding fiscal year and includes the following (for more information see 17 CFR 229.402(c)(2)):

(1) Salary and bonus.

(2) Awards of stock, stock options, and stock appreciation rights. Use the dollar amount recognized for financial statement reporting purposes with respect to the fiscal year in accordance with the Financial Accounting Standards Board’s Accounting Standards Codification (FASB ASC) 718, Compensation-Stock Compensation.

(3) Earnings for services under non-equity incentive plans. This does not include group life, health, hospitalization or medical reimbursement plans that do not discriminate in favor of executives, and are available generally to all salaried employees.

(4) Change in pension value. This is the change in present value of defined benefit and actuarial pension plans.

(5) Above-market earnings on deferred compensation which is not tax-qualified.

(6) Other compensation, if the aggregate value of all such other compensation (e.g., severance, termination payments, value of life insurance paid on behalf of the employee, perquisites or property) for the executive exceeds $10,000.

(b) Section 2(d)(2) of the Federal Funding Accountability and Transparency Act of 2006 (Pub. L. No. 109-282), as amended by section 6202 of the Government Funding Transparency Act of 2008 (Pub. L. 110-252), requires the Contractor to report information on subcontract awards. The law requires all reported information be made public, therefore, the Contractor is responsible for notifying its subcontractors that the required information will be made public.

(c) Nothing in this clause required the disclosure of classified information.

(d)

(1) Executive compensation of the prime contractor. As a part of its annual registration requirement in the System for Award Management (SAM) database (FAR provision 52.204-7), the Contractor shall report the names and total compensation of each of the five most highly compensated executives for its preceding completed fiscal year, if—

(i) In the Contractor’s preceding fiscal year, the Contractor received—

(A) 80 percent or more of its annual gross revenues from Federal contracts (and subcontracts), loans, grants (and subgrants), cooperative agreements, and other forms of Federal financial assistance; and

(B) $25,000,000 or more in annual gross revenues from Federal contracts (and subcontracts), loans, grants (and subgrants), cooperative agreements, and other forms of Federal financial assistance; and

(ii) The public does not have access to information about the compensation of the executives through periodic reports filed under section 13(a) or 15(d) of the Securities Exchange Act of 1934 (15 U.S.C. 78m(a), 78o(d)) or section 6104 of the Internal Revenue Code of 1986. (To determine if the public has access to the compensation information, see the U.S. Security and Exchange Commission total compensation filings at http://www.sec.gov/answers/execomp.htm.)

(2) First-tier subcontract information. Unless otherwise directed by the contracting officer, or as provided in paragraph (g) of this clause, by the end of the month following the month of award of a first-tier subcontract with a value of $30,000 or more, the Contractor shall report the following information at http://www.fsrs.gov for that first tier subcontract. (The Contractor shall follow the instruction at http://www.fsrs.gov to report the data.)

(i) Unique entity identifier for the subcontractor receiving the award and for the subcontractor’s parent company, if the subcontractor has a parent company.

(ii) Name of the subcontractor.

(iii) Amount of the subcontract award.

(iv) Date of the subcontract award.

(v) A description of the products or services (including construction) being provided under the subcontract, including the overall purpose and expected outcomes or results of the subcontract.

(vi) Subcontract number (the subcontract number assigned by the Contractor).

(vii) Subcontractor’s physical address including street address, city, state, and country. Also include the nine-digit zip code and congressional district.

(viii) Subcontractor’s primary performance location including street address, city, state, and country. Also include the nine-digit zip code and congressional district.

(ix) The prime contract number, and order number if applicable.

(x) Awarding agency name and code.

(xi) Funding agency name and code.

(xii) Government contracting office code.

(xiii) Treasury account symbol (TAS) as reported in FPDS.

(xiv) The applicable North American Industry Classification System code (NAICS).

(3) Executive compensation of the first-tier subcontractor. Unless otherwise directed by the Contracting Officer, by the end of the month following the month of award of a first-tier subcontract with a value of $30,000 or more, and annually thereafter (calculated from the prime contract award date), the Contractor shall report the names and total compensation of each of the five most highly compensated executives for that first-tier subcontractor for the first-tier subcontractor’s preceding completed fiscal year at https://www.fsrs.gov , if—

(i) In the subcontractor’s preceding fiscal year, the subcontractor received—

(A) 80 percent or more of its annual gross revenues from Federal contracts (and subcontracts), loans, grants (and subgrants), cooperative agreements, and other forms of Federal financial assistance; and

(B) $25,000,000 or more in annual gross revenues from Federal contracts (and subcontracts), loans, grants (and subgrants), cooperative agreements and other forms of Federal financial assistance; and

(ii) The public does not have access to information about the compensation of the executives through periodic reports filed under section 13(a) or 15(d) of the Securities Exchange Act of 1934 (15 U.S.C. 78m(a), 78o(d)) or section 6104 of the Internal Revenue Code of 1986. (To determine if the public has access to the compensation information, see the U.S. Security and Exchange Commission total compensation filings at http://www.sec.gov/answers/execomp.htm.)

(e) The Contractor shall not split or break down first-tier subcontract awards to a value less than $30,000 to avoid the reporting requirements in paragraph (d) of this clause.

(f) The Contractor is required to report information on a first-tier subcontract covered by paragraph (d) when the subcontract is awarded. Continued reporting on the same subcontract is not required unless one of the reported data elements changes during the performance of the subcontract. The Contractor is not required to make further reports after the first-tier subcontract expires.

(g)

(1) If the Contractor in the previous tax year had gross income, from all sources, under $300,000, the Contractor is exempt from the requirement to report subcontractor awards.

(2) If a subcontractor in the previous tax year had gross income from all sources under $300,000, the Contractor does not need to report awards for that subcontractor

(h) The FSRS database at http://www.fsrs.gov will be prepopulated with some information from SAM and FPDS databases. If FPDS information is incorrect, the contractor should notify the contracting officer. If the SAM database information is incorrect, the contractor is responsible for correcting this information.

52.222-19 52.222-19

CHILD LABOR--COOPERATION WITH AUTHORITIES AND REMEDIES (OCT 2016)

(a) Applicability. This clause does not apply to the extent that the Contractor is supplying end products mined, produced, or manufactured in—

(1) Canada, and the anticipated value of the acquisition is $25,000 or more;

(2) Israel, and the anticipated value of the acquisition is $50,000 or more;

(3) Mexico, and the anticipated value of the acquisition is $77,533, or more; or

(4) Armenia, Aruba, Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hong Kong, Hungary, Iceland, Ireland, Italy, Japan, Korea, Latvia, Liechtenstein, Lithuania, Luxembourg, Malta, Moldova, Montenegro, Netherlands, New Zealand, Norway, Poland, Portugal, Romania, Singapore, Slovak Republic, Slovenia, Spain, Sweden, Switzerland, Taiwan, Ukraine, or the United Kingdom and the anticipated value of the acquisition is $191,000 or more.

(b) Cooperation with Authorities. To enforce the laws prohibiting the manufacture of importation of products mined, produced, or manufactured by forced or indentured child labor, authorized officials may need to conduct investigations to determine whether forced or indentured child labor was used to mine, produce, or manufacture any product furnished under this contract. If the solicitation includes the provision 52.222-18, Certification Regarding Knowledge of Child Labor for Listed End Products, or the equivalent at 52.212-3(i), the Contractor agrees to cooperate fully with authorized officials of the contracting agency, the Department of the Treasury, or the Department of Justice by providing reasonable access to records, documents, persons, or premises upon reasonable request by the authorized official.

(c) Violations. The Government may impose remedies set forth in paragraph (d) for the following violations:

(1) The Contractor has submitted a false certification regarding knowledge of the use of forced or indentured child labor for listed end products.

(2) The Contractor has failed to cooperate, if required, in accordance with paragraph (b) of this clause, with an investigation of the use of forced or indentured child labor by an Inspector General, Attorney General, or the Secretary of the Treasury.

(3) The Contractor used forced or indentured child labor in its mining, production, or manufacturing processes.

(4) The Contractor has furnished under the contract end products or components that have been mined, produced, or manufactured wholly or in part by forced or indentured child labor. (The Government will not pursue remedies at paragraph (d)(2) or paragraph (d)(3) of this clause unless sufficient evidence indicates that the Contractor knew of the violation.)

(d) Remedies.

(1) The Contracting Officer may terminate the contract.

(2) The suspending official may suspend the Contractor in accordance with procedures in FAR Subpart 9.4.

(3) The debarring official may debar the Contractor for a period not to exceed 3 years in accordance with the procedures in FAR Subpart 9.4.

The following have been deleted:

(End of Summary of Changes)