N6449820Q5018.docx

N6449820Q5018

Section B - Supplies or Services and Prices

PUMP UNIT 50GPM

FFP

VS-50 Oil-Water Separator (OWS) System OWS Pumps: Moyno 2000 Pumps PN:3950096001 2 VS-50 Oil-Water Separator FOB: Destination

NSN: 4320015677195

VENDOR PART NR: 100001459787-0040

PURCHASE REQUEST NUMBER: 1300814471-0001

PSC CD: 4320

NET AMT

SHIPPING

FFP

SHIPPING

FOB: Destination

VENDOR PART NR: 100001459787-0040

PURCHASE REQUEST NUMBER: 1300814471-0001

PSC CD: 4320

NET AMT

Section C - Descriptions and Specifications

CLAUSES INCORPORATED BY FULL TEXT

C-202-H001 ADDITIONAL DEFINITIONS–BASIC (NAVSEA) (OCT 2018)

(a) Department means the Department of the Navy.

(b) Commander, Naval Sea Systems Command means the Commander of the Naval Sea Systems Command of the Department of the Navy or his duly appointed successor.

(c) References to The Federal Acquisition Regulation (FAR) All references to the FAR in this contract shall be deemed to also reference the appropriate sections of the Defense FAR Supplement (DFARS), unless clearly indicated otherwise.

(d) National Stock Numbers Whenever the term Federal Item Identification Number and its acronym FIIN or the term Federal Stock Number and its acronym FSN appear in the contract, order or their cited specifications and standards, the terms and acronyms shall be interpreted as National Item Identification Number (NIIN) and National Stock Number (NSN) respectively which shall be defined as follows:

(1) National Item Identification Number (NIIN). The number assigned to each approved Item Identification under the Federal Cataloging Program. It consists of nine numeric characters, the first two of which are the National Codification Bureau (NCB) Code. The remaining positions consist of a seven digit nonsignificant number.

(2) National Stock Number (NSN). The National Stock Number (NSN) for an item of supply consists of the applicable four-position Federal Supply Class (FSC) plus the applicable nine-position NIIN assigned to the item of supply.

(End of text)

C-204-H001 USE OF NAVY SUPPORT CONTRACTORS FOR OFFICIAL CONTRACT FILES (NAVSEA) (OCT 2018)

(a) NAVSEA may use a file room management support contractor, hereinafter referred to as "the support contractor", to manage its file room, in which all official contract files, including the official file supporting this procurement, are retained. These official files may contain information that is considered a trade secret, proprietary, business sensitive or otherwise protected pursuant to law or regulation, hereinafter referred to as “protected information”. File room management services consist of any of the following: secretarial or clerical support; data entry; document reproduction, scanning, imaging, or destruction; operation, management, or maintenance of paper-based or electronic mail rooms, file rooms, or libraries; and supervision in connection with functions listed herein.

(b) The cognizant Contracting Officer will ensure that any NAVSEA contract under which these file room management services are acquired will contain a requirement that:

(1) The support contractor not disclose any information;

(2) Individual employees are to be instructed by the support contractor regarding the sensitivity of the official contract files;

(3) The support contractor performing these services be barred from providing any other supplies and/or services, or competing to do so, to NAVSEA for the period of performance of its contract and for an additional three years thereafter unless otherwise provided by law or regulation; and,

(4) In addition to any other rights the contractor may have, it is a third party beneficiary who has the right of direct action against the support contractor, or any person to whom the support contractor has released or disclosed protected information, for the unauthorized duplication, release, or disclosure of such protected information.

(c) Execution of this contract by the contractor is considered consent to NAVSEA's permitting access to any information, irrespective of restrictive markings or the nature of the information submitted, by its file room management support contractor for the limited purpose of executing its file room support contract responsibilities.

(d) NAVSEA may, without further notice, enter into contracts with other contractors for these services. Contractors should enter into separate non-disclosure agreements with the file room contractor. Contact the Procuring Contracting Officer for contractor specifics. However, any such agreement will not be considered a prerequisite before information submitted is stored in the file room or otherwise encumber the government.

C-211-H016 SPECIFICATIONS AND STANDARDS (NAVSEA) (OCT 2018)

(a) Definitions.

(i) A "zero-tier reference" is a specification, standard, or drawing that is cited in the contract (including its attachments).

(ii) A "first-tier reference" is either: (1) a specification, standard, or drawing cited in a zero-tier reference, or (2) a specification cited in a first-tier drawing.

(b) Requirements. All zero-tier and first-tier references, as defined above, are mandatory for use. All lower tier references shall be used for guidance only unless specifically identified below.

None

C-211-H018 APPROVAL BY THE GOVERNMENT (NAVSEA) (JAN 2019)

Approval by the Government as required under this contract and applicable specifications shall not relieve the Contractor of its obligation to comply with the specifications and with all other requirements of the contract, nor shall it impose upon the Government any liability it would not have had in the absence of such approval.

C-233-H001 DOCUMENTATION OF REQUESTS FOR EQUITABLE ADJUSTMENT--BASIC (NAVSEA) (OCT 2018)

(a) For the purposes of this special contract requirement, the term "change" includes not only a change that is made pursuant to a written order designated as a "change order" but also (1) an engineering change proposed by the Government or by the Contractor and (2) any act or omission to act on the part of the Government in respect of which a request is made for equitable adjustment.

(b) Whenever the Contractor requests or proposes an equitable adjustment of $100,000 or more per vessel in respect to a change made pursuant to a written order designated as a "change order" or in respect to a proposed engineering change and whenever the Contractor requests an equitable adjustment in any amount in respect to any other act or omission to act on the part of the Government, the proposal supporting such request shall contain the following information for each individual item or element of the request:

(1) A description (i) of the work required by the contract before the change, which has been deleted by the change, and (ii) of the work deleted by the change which already has been completed. The description is to include a list of components, equipment, and other identifiable property involved. Also, the status of manufacture, procurement, or installation of such property is to be indicated. Separate description is to be furnished for design and production work. Items of raw material, purchased parts, components and other identifiable hardware, which are made excess by the change and which are not to be retained by the Contractor, are to be listed for later disposition;

(2) Description of work necessary to undo work already completed which has been deleted by the change;

(3) Description of work not required by the terms hereof before the change, which is substituted or added by the change. A list of components and equipment (not bulk materials or items) involved should be included. Separate descriptions are to be furnished for design work and production work;

(4) Description of interference and inefficiencies in performing the change;

(5) Description of each element of disruption and exactly how work has been, or will be disrupted:

(i) The calendar period of time during which disruption occurred, or will occur;

(ii) Area(s) aboard the vessel where disruption occurred, or will occur;

(iii) Trade(s) disrupted, with a breakdown of manhours for each trade;

(iv) Scheduling of trades before, during, and after period of disruption;

(v) Description of measures taken to lessen the disruptive effect of the change;

(6) Delay in delivery attributable solely to the change;

(7) Other work attributable to the change;

(8) Supplementing the foregoing, a narrative statement of the direct "causal" relationship between any alleged Government act or omission and the claimed consequences therefor, crossreferenced to the detailed information provided as required above; and

(9) A statement setting forth a comparative enumeration of the amounts "budgeted" for the cost elements, including the material costs, labor hours and pertinent indirect costs, estimated by the Contractor in preparing its initial and ultimate proposal(s) for this contract, and the amounts claimed to have been incurred and/or projected to be incurred corresponding to each such "budgeted cost" elements.

(c) Each proposal in excess of $100,000 submitted in support of a claim for equitable adjustment under any requirement of this contract shall, in addition to the information required by paragraph (b) hereof, contain such information as the Contracting Officer may require with respect to each individual claim item.

(d) It is recognized that individual claims for equitable adjustment may not include all of the factors listed in paragraph (b) above. Accordingly, the Contractor is required to set forth in its proposal information only with respect to those factors which are comprehended in the individual claim for equitable adjustment. In any event, the information furnished hereunder shall be in sufficient detail to permit the Contracting Officer to cross-reference the claimed increased costs, or delay in delivery, or both, as appropriate, submitted pursuant to paragraph (c) of this requirement, with the information submitted pursuant to paragraph (b) hereof.

C-247-H001 PERMITS AND RESPONSIBILITIES (NAVSEA) (DEC 2018)

The Contractor shall, without additional expense to the Government, be responsible for obtaining any necessary licenses and permits for complying with any applicable Federal, State, and Municipal laws, codes, and regulations for shipping and transportation including, but not limited to, any movement over public highways of overweight/over dimensional materials.

(End of text)

Section D - Packaging and Marking

D-211-H004 IDENTIFICATION MARKING OF PARTS--BASIC (NAVSEA) (OCT 2018)

For all parts not subject to the marking requirements in DFARS 252.211-7003 – Item Unique Identification and Valuation, marking shall be accomplished in accordance with the following:

(1) Parts shall be marked in accordance with generally accepted commercial practice.

(2) In cases where parts are so small as not to permit identification marking as provided above, such parts shall be appropriately coded so as to permit ready identification.

D-247-H002 PACKAGING OF SUPPLIES—BASIC (NAVSEA) (OCT 2018)

Item(s) 0001-0002 The supplies furnished hereunder shall be packaged in accordance with ASTM-D-3951-15 approved 1 December 2015, Standard Practice for Commercial Packing.

D-247-W001 PROHIBITED PACKING MATERIALS (NAVSEA) (OCT 2018)

The use of asbestos, excelsior, newspaper or shredded paper (all types including waxed paper, computer paper and similar hygroscopic or non-neutral material) is prohibited. In addition, the use of yellow wrapping or packaging material is prohibited except where used for the containment of radioactive material. Loose fill polystyrene is prohibited for shipboard use.

Section E - Inspection and Acceptance

INSPECTION AND ACCEPTANCE TERMS

Supplies/services will be inspected/accepted at:

E-246-H016 INSPECTION AND ACCEPTANCE OF F.O.B. DESTINATION DELIVERIES (NAVSEA) (OCT 2018)

Item(s) 0001-0002 - Inspection and acceptance shall be made at destination by a representative of the Government.

E-246-H023 QUALITY REQUIREMENT FOR SOFTWARE DEVELOPMENT OR PRODUCTION (NAVSEA) (JAN 2019)

The contractor's software quality program shall be an integral part of the overall Quality Management System. Software quality program controls shall be applicable to all project software that is developed, maintained, or modified within the following categories:

(a) All deliverable software

(b) All deliverable software that is included as part of deliverable hardware or firmware.

(c) Non deliverable software (commercially available or user-developed) used for development, fabrication, testing, or acceptance of deliverable software or hardware (includes automated fabrication, test, and inspection/acceptance equipment software and software design, test, and inspection tools).

(d) Commercially available, reusable, or Government software designated as part of a deliverable item.

E-246-W002 CERTIFICATE OF COMPLIANCE (NAVSEA) (OCT 2018)

(a) A certification of material shall be provided by the Contractor, one (1) copy to accompany the shipment (in the packing list envelope) and (l) copy mailed to arrive at time of receipt of the shipment. Mark all certificates to the attention of Code 00Q.

(b) The certificate shall state compliance of material with drawing specification and contract/order requirements. The certificate shall as a minimum state the company name, contract/order number, drawing or specification number, and date. The certificate shall state, above the signature of a legally authorized representative of the company, the following:

This certification concerns a matter within the jurisdiction of an agency of the United States and the making of a false, fictitious, or fraudulent certification may render the maker subject to prosecution under Title 18, United States Code, Section 1001.

(c) Failure to provide certification at the time of shipment may result in material being rejected and returned at the contractor's expense.

(d) The certificate shall read as follows:

I certify that on ______ [insert date], the ____ [insert Contractor’s name] furnished the supplies called for by the Order/Contract No._____ via ____ [Carrier] on ________ [identify the bill of lading or shipping document] in accordance with all applicable requirements. I further certify that the supplies or services are of the quality specified and conform in all respects with the contract requirements, including specifications, drawings, preservation, packaging, packing, marking requirements, and physical item identification (part number), and are in the quantity shown on this document.

Date of Execution: ________________________________ Signature: _______________________________________ Typed Name: ____________________________________ Title: ___________________________________________

Section F - Deliveries or Performance

DELIVERY INFORMATION

MIGUEL MORA-TORRES

NSWC PHILADELPHIA DIVISION

1601 LANGLEY AVENUE

BLDG 1000

PHILADELPHIA PA 19112

215-897-2051 FOB: Destination N64498

31-DEC-2019

FOB: Destination N64498

Section G - Contract Administration Data

252.232-7006 WIDE AREA WORKFLOW PAYMENT INSTRUCTIONS (DEC 2018)

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

“Payment request” and “receiving report” are defined in the clause at 252.232-7003, Electronic Submission of Payment Requests and Receiving Reports.

(b) Electronic invoicing. The WAWF system provides the method to electronically process vendor payment requests and receiving reports, as authorized by Defense Federal Acquisition Regulation Supplement (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.sam.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 shall use the following information when submitting payment requests and receiving reports in WAWF for this contract or task or delivery order:

(1) Document type. The Contractor shall submit payment requests using the following document type(s):

(i) For cost-type line items, including labor-hour or time-and-materials, submit a cost voucher.

(ii) For fixed price line items—

(A) That require shipment of a deliverable, submit the invoice and receiving report specified by the Contracting Officer.

COMBO___________________________________________________________

(B) For services that do not require shipment of a deliverable, submit either the Invoice 2in1, which meets the requirements for the invoice and receiving report, or the applicable invoice and receiving report, as specified by the Contracting Officer.

(iii) For customary progress payments based on costs incurred, submit a progress payment request.

(iv) For performance based payments, submit a performance based payment request.

(v) For commercial item financing, submit a commercial item financing request.

(2) Fast Pay requests are only permitted when Federal Acquisition Regulation (FAR) 52.213-1 is included in the contract.

[Note: The Contractor may use a WAWF “combo” document type to create some combinations of invoice and receiving report in one step.]

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

(4) Payment request. The Contractor shall ensure a payment request includes documentation appropriate to the type of payment request in accordance with the payment clause, contract financing clause, or Federal Acquisition Regulation 52.216-7, Allowable Cost and Payment, as applicable.

(5) Receiving report. The Contractor shall ensure a receiving report meets the requirements of DFARS Appendix F.

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

Kimberly Villano (215) 897-2433 Kimberly.villano@navy.mil

(2) Contact the WAWF helpdesk at 866-618-5988, if assistance is needed.

(End of clause)

G-232-H002 PAYMENT INSTRUCTIONS AND CONTRACT TYPE SUMMARY FOR PAYMENT OFFICE (NAVSEA) (JUN 2018)

(a) The following table of payment office allocation methods applies to the extent indicated.

THIS ENTIRE CONTRACT IS FIRM FIXED PRICE

G-232-H005 SUPPLEMENTAL INSTRUCTIONS REGARDING INVOICING (NAVSEA) (JAN 2019)

(a) For other than firm fixed priced contract line item numbers (CLINs), the Contractor agrees to segregate costs incurred under this contract/task order (TO), as applicable, at the lowest level of performance, either at the sub line item number (SLIN) or CLIN level, rather than at the total contract/TO level, and to submit invoices reflecting costs incurred at that level. Supporting documentation in Wide Area Workflow (WAWF) for invoices shall include summaries of work charged during the period covered as well as overall cumulative summaries by individual labor categories, rates, and hours (both straight time and overtime) invoiced; as well as, a cost breakdown of other direct costs (ODCs), materials, and travel, by technical instruction (TI), SLIN, or CLIN level. For other than firm fixed price subcontracts, subcontractors are also required to provide labor categories, rates, and hours (both straight time and overtime) invoiced; as well as, a cost breakdown of ODCs, materials, and travel invoiced. Supporting documentation may be encrypted before submission to the prime contractor for WAWF invoice submittal. Subcontractors may email encryption code information directly to the Contracting Officer and Contracting Officer Representative (COR). Should the subcontractor lack encryption capability, the subcontractor may also email detailed supporting cost information directly to the Contracting Officer and COR; or other method as agreed to by the Contracting Officer.

(b) Contractors submitting payment requests and receiving reports to WAWF using either Electronic Data Interchange (EDI) or Secure File Transfer Protocol (SFTP) shall separately send an email notification to the COR and Contracting Officer on the same date they submit the invoice in WAWF. No payments shall be due if the contractor does not provide the COR and Contracting Officer email notification as required herein.

G-242-H001 GOVERNMENT CONTRACT ADMINISTRATION POINTS-OF-CONTACT AND RESPONSIBILITIES (NAVSEA) (OCT 2018)

(a) The Government reserves the right to administratively substitute any of the points of contact listed below at any time.

(b) The contracting officer is the only person authorized to change this contract or orders issued thereunder. The Contractor shall not comply with any order, direction or request of Government personnel - that would constitute a change - unless it is issued in writing and signed by the Contracting Officer or is pursuant to specific authority otherwise included as part of this contract. If, in the opinion of the contractor, an effort outside the existing scope of this contract is requested, the contractor shall promptly comply with the Notification of Changes clause of this contract.

(c) The points of contact are as follows:

(i) The Procuring Contracting Officer (PCO) is:

[ Karen Morris ] Address:

[ 5001 South Broad St ] [ Philadelphia, PA, 19112 ] Phone: (215) 897-1114 E-mail: karen.morris@navy.mil

(ii) The Contract Specialist is:

William H. Morton Address:

[ 5001 South Broad St ] [ Philadelphia, PA, 19112 ] Phone: (215) 897-2350 E-mail: William.h.morton1@navy.mil

(iii) The Administrative Contracting Officer (ACO) is:

Name: [ * ] Address:

[ *Street ] [ *City, State, Zip ] Phone: (Area Code) xxx- [xxxx];

E-mail: [ * ]

(d) The Contracting Officer’s Representative (COR) is the contracting officer’s appointed representative for technical matters. The COR is not a contracting officer and does not have the authority to direct the accomplishment of effort which is beyond the scope of the contract or to otherwise change any contract requirements. An informational copy of the COR appointment letter, which provides a delineation of COR authority and responsibilities, will be provided upon award of this contract.

The Contracting Officer’s Representative (COR) is:

Name: [ * ] Address:

[ *Street ] [ *City, State, Zip ] Phone: (Area Code) xxx- [xxxx]; FAX: (Area Code) xxx- [xxxx] E-mail: [ * ]

(e) The Alternate Contracting Officer’s Representative (ACOR) is responsible for COR responsibilities and functions in the event that the COR is unavailable due to leave, illness, or other official business. The ACOR is appointed by the contracting officer; a copy of the ACOR appointment will be provided upon award of this contract.

The Alternate Contracting Officer’s Representative (ACOR) is:

Name: [ * ] Address:

[ *City, State, Zip ] Phone: (Area Code) xxx- [xxxx]; FAX: (Area Code) xxx- [xxxx] E-mail: [ * ]

(f) The Technical Point of Contact (TPOC) is the contracting officer’s representative for technical matters when a COR is not appointed. The TPOC is responsible for technical issues of contract administration, such as providing all items of Government Furnished Information (GFI), Government Furnished Material (GFM) and Government Furnished Equipment (GFE) if specified in the contract as well as the inspection and acceptance of all contract deliverables.

The Technical Point of Contact (TPOC) is:

Name: [Miguel Mora-Torres ]

NSWC PHILADELPHIA DIVISION

1601 LANGLEY AVENUE

BLDG 542

PHILADELPHIA PA 19112

(215) 897-2051 E-mail: miguel.mora-torres@navy.mil

(g) The Alternate Technical Point of Contact (ATPOC) is responsible for TPOC responsibilities and functions in the event that the TPOC is unavailable due to leave, illness, or other official business.

The Alternate Technical Point of Contact (ATPOC) is:

Name: [ * ] Address:

[ *City, State, Zip ] Phone: (Area Code) xxx- [xxxx]; FAX: (Area Code) xxx- [xxxx] E-mail: [ * ]

(h) The Ombudsman will review complaints from the contractors and ensure that all contractors are afforded a fair opportunity to be considered, consistent with the procedures in the contract.

The Ombudsman is:

Name: [ * ] Address:

[ *Street ] [ *City, State, Zip ] Phone: (Area Code) xxx- [xxxx];

E-mail: [ * ]

(i) The Authorized Ordering Person(s) for Per-Call Maintenance is responsible for issuing and maintaining records for any per-call orders for remedial maintenance placed under this contract. No per-call order shall be placed outside the scope of this contract and the cumulative total of all orders shall not be in excess of any not-to-exceed amount specified in the contract. Per-call orders shall not, in any way, modify any terms and conditions of the contract.

(j) The Authorized Ordering Person(s) for Per-Call Maintenance is:

Name: [ * ] Address:

[ *Street ] [ *City, State, Zip ] Phone: (Area Code) xxx- [xxxx];

E-mail: [ * ]

(k) The Contractor's point of contact for performance under this contract is:

Name: [ * ] Title: [ * ] Address:

[ *Street ] [ *City, State, Zip ] Phone: (Area Code) xxx- [xxxx]; FAX: (Area Code) xxx- [xxxx] E-mail: [ * ]

[ * ] To be completed at contract award

G-242-W001 CONTRACT ADMINISTRATION FUNCTIONS (NAVSEA) (OCT 2018)

(a) In accordance with FAR 42.302(a) all functions listed are delegated to the ACO except the following items to be retained by the PCO:

[ List specific functions that will be retained by the PCO]

(b) In accordance with FAR 42.302(b), the following additional functions are delegated to the ACO:

[ List any additional functions that will be delegated to the ACO]

(End of text)

Section I - Contract Clauses

CLAUSES INCORPORATED BY REFERENCE

52.212-5 CONTRACT TERMS AND CONDITIONS REQUIRED TO IMPLEMENT STATUTES OR EXECUTIVE ORDERS—COMMERCIAL ITEMS (DEVIATION 2018-O0021) (OCT 2019)

(a) Comptroller General Examination of Record. The Contractor shall comply with the provisions of this paragraph (a) if this contract was awarded using other than sealed bid, is in excess of the simplified acquisition threshold, and does not contain the clause at 52.215-2, Audit and Records—Negotiation.

(1) The Comptroller General of the United States, or an authorized representative of the Comptroller General, shall have access to and right to examine any of the Contractor’s directly pertinent records involving transactions related to this contract.

(2) The Contractor shall make available at its offices at all reasonable times the records, materials, and other evidence for examination, audit, or reproduction, until 3 years after final payment under this contract or for any shorter period specified in FAR Subpart 4.7, Contractor Records Retention, of the other clauses of this contract. If this contract is completely or partially terminated, the records relating to the work terminated shall be made available for 3 years after any resulting final termination settlement. Records relating to appeals under the disputes clause or to litigation or the settlement of claims arising under or relating to this contract shall be made available until such appeals, litigation, or claims are finally resolved.

(3) As used in this clause, records include books, documents, accounting procedures and practices, and other data, regardless of type and regardless of form. This does not require the Contractor to create or maintain any record that the Contractor does not maintain in the ordinary course of business or pursuant to a provision of law.

(b)(1) Notwithstanding the requirements of any other clauses of this contract, the Contractor is not required to flow down any FAR clause, other than those in this paragraph (b) (1) in a subcontract for commercial items. Unless otherwise indicated below, the extent of the flow down shall be as required by the clause—

(i) 52.203-13, Contractor Code of Business Ethics and Conduct (Oct 2015) (41 U.S.C. 3509).

(ii) 52.203-19, Prohibition on Requiring Certain Internal Confidentiality Agreements or Statements (Jan 2017) (section 743 of Division E, Title VII, of the Consolidated and Further Continuing Appropriations Act, 2015 (Pub. L. 113-235) and its successor provisions in subsequent appropriations acts (and as extended in continuing resolutions)).

(iii) 52.204-23, Prohibition on Contracting for Hardware, Software, and Services Developed or Provided by Kaspersky Lab and Other Covered Entities (Jul 2018) (Section 1634 of Pub. L. 115-91).

(iv) 52.204-25, Prohibition on Contracting for Certain Telecommunications and Video Surveillance Services or Equipment. (Aug 2019) (Section 889(a)(1)(A) of Pub. L. 115-232).

(v) 52.219-8, Utilization of Small Business Concerns (Oct 2018) (15 U.S.C. 637(d)(2) and (3)), in all subcontracts that offer further subcontracting opportunities. If the subcontract (except subcontracts to small business concerns) exceeds $700,000 ($1.5 million for construction of any public facility), the subcontractor must include 52.219-8 in lower tier subcontracts that offer subcontracting opportunities.

(vi) 52.222-17, Nondisplacement of Qualified Workers (MAY 2014) (E.O. 13495). Flow down required in accordance with paragraph (l) of FAR clause 52.222-17.

(vii) 52.222-21, Prohibition of Segregated Facilities (APR 2015).

(viii) 52.222-26, Equal Opportunity (Sept 2016) (E.O. 11246).

(ix) 52.222-35, Equal Opportunity for Veterans (Oct 2015) (38 U.S.C. 4212).

(x) 52.222-36, Equal Opportunity for Workers with Disabilities (July 2014) (29 U.S.C. 793).

(xi) 52.222-37, Employment Reports on Veterans (FEB 2016) (38 U.S.C. 4212).

(xii) 52.222-40, Notification of Employee Rights Under the National Labor Relations Act (Dec 2010) (E.O. 13496). Flow down required in accordance with paragraph (f) of FAR clause 52.222-40.

(xiii) 52.222-41, Service Contract Labor Standards (Aug 2018) (41 U.S.C. chapter 67).

(xiv)(A) 52.222-50, Combating Trafficking in Persons (Mar 2015) (22 U.S.C. chapter 78 and E.O. 13627).

(B) Alternate I (Mar 2015) of 52.222-50 (22 U.S.C. chapter 78 and E.O. 13627).

(xv) 52.222-51, Exemption from Application of the Service Contract Act to Contracts for Maintenance, Calibration, or Repair of Certain Equipment-Requirements (May 2014) (41 U.S.C. chapter 67).

(xvi) 52.222-53, Exemption from Application of the Service Contract Act to Contracts for Certain Services-Requirements (May 2014) (41 U.S.C. chapter 67).

(xvii) 52.222-54, Employment Eligibility Verification (Oct 2015) (E.O. 12989).

(xviii) 52.222-55, Minimum Wages Under Executive Order 13658 (Dec 2015).

(xix) 52.222-62 Paid Sick Leave Under Executive Order 13706 (Jan 2017) (E.O. 13706).

(xx)(A) 52.224-3, Privacy Training (JAN 2017) (5 U.S.C. 552a).

(B) Alternate I (JAN 2017) of 52.224-3.

(xxi) 52.225-26, Contractors Performing Private Security Functions Outside the United States (Oct 2016) (Section 862, as amended, of the National Defense Authorization Act for Fiscal Year 2008; 10 U.S.C. 2302 Note).

(xxii) 52.226-6, Promoting Excess Food Donation to Nonprofit Organizations (May 2014) (42 U.S.C. 1792). Flow down required in accordance with paragraph (e) of FAR clause 52.226-6.

(xxiii) 52.247-64, Preference for Privately Owned U.S.-Flag Commercial Vessels (Feb 2006) (46 U.S.C. Appx. 1241(b) and 10 U.S.C. 2631). Flow down required in accordance with paragraph (d) of FAR clause 52.247-64.

(2) While not required, the contractor may include in its subcontracts for commercial items a minimal number of additional clauses necessary to satisfy its contractual obligations.

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):

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

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 Defense Federal Acquisition Regulation (48 CFR Chapter 2) clause with an authorized deviation is indicated by the addition of "(DEVIATION)" after the name of the regulation.

252.211-7003 ITEM UNIQUE IDENTIFICATION AND VALUATION (MAR 2016)

(a) Definitions. As used in this clause-

Automatic identification device means a device, such as a reader or interrogator, used to retrieve data encoded on machine-readable media.

Concatenated unique item identifier means--

(1) For items that are serialized within the enterprise identifier, the linking together of the unique identifier data elements in order of the issuing agency code, enterprise identifier, and unique serial number within the enterprise identifier; or

(2) For items that are serialized within the original part, lot, or batch number, the linking together of the unique identifier data elements in order of the issuing agency code; enterprise identifier; original part, lot, or batch number; and serial number within the original part, lot, or batch number.

Data Matrix means a two-dimensional matrix symbology, which is made up of square or, in some cases, round modules arranged within a perimeter finder pattern and uses the Error Checking and Correction 200 (ECC200) specification found within International Standards Organization (ISO)/International Electrotechnical Commission (IEC) 16022.

Data qualifier means a specified character (or string of characters) that immediately precedes a data field that defines the general category or intended use of the data that follows.

DoD recognized unique identification equivalent means a unique identification method that is in commercial use and has been recognized by DoD. All DoD recognized unique identification equivalents are listed at http://www.acq.osd.mil/dpap/pdi/uid/iuid_equivalents.html.

DoD item unique identification means a system of marking items delivered to DoD with unique item identifiers that have machine-readable data elements to distinguish an item from all other like and unlike items. For items that are serialized within the enterprise identifier, the unique item identifier shall include the data elements of the enterprise identifier and a unique serial number. For items that are serialized within the part, lot, or batch number within the enterprise identifier, the unique item identifier shall include the data elements of the enterprise identifier; the original part, lot, or batch number; and the serial number.

Enterprise means the entity (e.g., a manufacturer or vendor) responsible for assigning unique item identifiers to items.

Enterprise identifier means a code that is uniquely assigned to an enterprise by an issuing agency.

Government's unit acquisition cost means--

(1) For fixed-price type line, subline, or exhibit line items, the unit price identified in the contract at the time of delivery;

(2) For cost-type or undefinitized line, subline, or exhibit line items, the Contractor's estimated fully burdened unit cost to the Government at the time of delivery; and

(3) For items produced under a time-and-materials contract, the Contractor's estimated fully burdened unit cost to the Government at the time of delivery.

Issuing agency means an organization responsible for assigning a globally unique identifier to an enterprise, as indicated in the Register of Issuing Agency Codes for ISO/IEC 15459, located at http://www.aimglobal.org/?Reg_Authority15459.

Issuing agency code means a code that designates the registration (or controlling) authority for the enterprise identifier.

Item means a single hardware article or a single unit formed by a grouping of subassemblies, components, or constituent parts.

Lot or batch number means an identifying number assigned by the enterprise to a designated group of items, usually referred to as either a lot or a batch, all of which were manufactured under identical conditions.

Machine-readable means an automatic identification technology media, such as bar codes, contact memory buttons, radio frequency identification, or optical memory cards.

Original part number means a combination of numbers or letters assigned by the enterprise at item creation to a class of items with the same form, fit, function, and interface.

Parent item means the item assembly, intermediate component, or subassembly that has an embedded item with a unique item identifier or DoD recognized unique identification equivalent.

Serial number within the enterprise identifier means a combination of numbers, letters, or symbols assigned by the enterprise to an item that provides for the differentiation of that item from any other like and unlike item and is never used again within the enterprise.

Serial number within the part, lot, or batch number means a combination of numbers or letters assigned by the enterprise to an item that provides for the differentiation of that item from any other like item within a part, lot, or batch number assignment.

Serialization within the enterprise identifier means each item produced is assigned a serial number that is unique among all the tangible items produced by the enterprise and is never used again. The enterprise is responsible for ensuring unique serialization within the enterprise identifier.

Serialization within the part, lot, or batch number means each item of a particular part, lot, or batch number is assigned a unique serial number within that part, lot, or batch number assignment. The enterprise is responsible for ensuring unique serialization within the part, lot, or batch number within the enterprise identifier.

Type designation means a combination of letters and numerals assigned by the Government to a major end item, assembly or subassembly, as appropriate, to provide a convenient means of differentiating between items having the same basic name and to indicate modifications and changes thereto.

Unique item identifier means a set of data elements marked on items that is globally unique and unambiguous. The term includes a concatenated unique item identifier or a DoD recognized unique identification equivalent.

Unique item identifier type means a designator to indicate which method of uniquely identifying a part has been used. The current list of accepted unique item identifier types is maintained at http://www.acq.osd.mil/dpap/pdi/uid/uii_types.html.

(b) The Contractor shall deliver all items under a contract line, subline, or exhibit line item.

(c) Unique item identifier. (1) The Contractor shall provide a unique item identifier for the following:

(i) Delivered items for which the Government's unit acquisition cost is $5,000 or more, except for the following line items:

Contract line, subline, or exhibit line item No. Item description

(ii) Items for which the Government's unit acquisition cost is less than $5,000 that are identified in the Schedule or the following table:

Contract line, subline, or exhibit line item No. Item description

(If items are identified in the Schedule, insert ``See Schedule'' in this table.)

(iii) Subassemblies, components, and parts embedded within delivered items, items with warranty requirements, DoD serially managed reparables and DoD serially managed nonreparables as specified in Attachment Number ----.

(iv) Any item of special tooling or special test equipment as defined in FAR 2.101 that have been designated for preservation and storage for a Major Defense Acquisition Program as specified in Attachment Number ----.

(v) Any item not included in paragraphs (c)(1)(i), (ii), (iii), or

(iv) of this clause for which the contractor creates and marks a unique item identifier for traceability.

(2) The unique item identifier assignment and its component data element combination shall not be duplicated on any other item marked or registered in the DoD Item Unique Identification Registry by the contractor.

(3) The unique item identifier component data elements shall be marked on an item using two dimensional data matrix symbology that complies with ISO/IEC International Standard 16022, Information technology--International symbology specification--Data matrix; ECC200 data matrix specification.

(4) Data syntax and semantics of unique item identifiers. The Contractor shall ensure that--

(i) The data elements (except issuing agency code) of the unique item identifier are encoded within the data matrix symbol that is marked on the item using one of the following three types of data qualifiers, as determined by the Contractor:

(A) Application Identifiers (AIs) (Format Indicator 05 of ISO/IEC International Standard 15434), in accordance with ISO/IEC International Standard 15418, Information Technology--EAN/UCC Application Identifiers and Fact Data Identifiers and Maintenance and ANSI MH 10.8.2 Data Identifier and Application Identifier Standard.

(B) Data Identifiers (DIs) (Format Indicator 06 of ISO/IEC International Standard 15434), in accordance with ISO/IEC International Standard 15418, Information Technology--EAN/UCC Application Identifiers and Fact Data Identifiers and Maintenance and ANSI MH 10.8.2 Data Identifier and Application Identifier Standard.

(C) Text Element Identifiers (TEIs) (Format Indicator 12 of ISO/IEC International Standard 15434), in accordance with the Air Transport Association Common Support Data Dictionary; and

(ii) The encoded data elements of the unique item identifier conform to the transfer structure, syntax, and coding of messages and data formats specified for Format Indicators 05, 06, and 12 in ISO/IEC International Standard 15434, Information Technology-Transfer Syntax for High Capacity Automatic Data Capture Media.

(5) Unique item identifier.

(i) The Contractor shall--

(A) Determine whether to--

(1) Serialize within the enterprise identifier;

(2) Serialize within the part, lot, or batch number; or

(3) Use a DoD recognized unique identification equivalent (e.g. Vehicle Identification Number); and

(B) Place the data elements of the unique item identifier (enterprise identifier; serial number; DoD recognized unique identification equivalent; and for serialization within the part, lot, or batch number only: Original part, lot, or batch number) on items requiring marking by paragraph (c)(1) of this clause, based on the criteria provided in MIL-STD-130, Identification Marking of U.S. Military Property, latest version;

(C) Label shipments, storage containers and packages that contain uniquely identified items in accordance with the requirements of MIL-STD-129, Military Marking for Shipment and Storage, latest version; and

(D) Verify that the marks on items and labels on shipments, storage containers, and packages are machine readable and conform to the applicable standards. The contractor shall use an automatic identification technology device for this verification that has been programmed to the requirements of Appendix A, MIL-STD-130, latest version.

(ii) The issuing agency code--

(A) Shall not be placed on the item; and

(B) Shall be derived from the data qualifier for the enterprise identifier.

(d) For each item that requires item unique identification under paragraph (c)(1)(i), (ii), or (iv) of this clause or when item unique identification is provided under paragraph (c)(1)(v), in addition to the information provided as part of the Material Inspection and Receiving Report specified elsewhere in this contract, the Contractor shall report at the time of delivery, as part of the Material Inspection and Receiving Report, the following information:

(1) Unique item identifier.

(2) Unique item identifier type.

(3) Issuing agency code (if concatenated unique item identifier is used).

(4) Enterprise identifier (if concatenated unique item identifier is used).

(5) Original part number (if there is serialization within the original part number).

(6) Lot or batch number (if there is serialization within the lot or batch number).

(7) Current part number (optional and only if not the same as the original part number).

(8) Current part number effective date (optional and only if current part number is used).

(9) Serial number (if concatenated unique item identifier is used).

(10) Government's unit acquisition cost.

(11) Unit of measure.

(12) Type designation of the item as specified in the contract schedule, if any.

(13) Whether the item is an item of Special Tooling or Special Test Equipment.

(14) Whether the item is covered by a warranty.

(e) For embedded subassemblies, components, and parts that require DoD unique item identification under paragraph (c)(1)(iii) of this clause, the Contractor shall report as part of, or associated with, the Material Inspection and Receiving Report specified elsewhere in this contract, the following information:

(1) Unique item identifier of the parent item under paragraph (c)(1) of this clause that contains the embedded subassembly, component, or part.

(2) Unique item identifier of the embedded subassembly, component, or part.

(3) Unique item identifier type.**

(4) Issuing agency code (if concatenated unique item identifier is used).**

(5) Enterprise identifier (if concatenated unique item identifier is used).**

(6) Original part number (if there is serialization within the original part number).**

(7) Lot or batch number (if there is serialization within the lot or batch number).**

(8) Current part number (optional and only if not the same as the original part number).**

(9) Current part number effective date (optional and only…