N6449824R4076.docx

N6449824R4076

Section B - Supplies or Services and Prices

DUROPC 2U LOW PROFILE PROCESSOR

FFP

Part Number: R700-2-140002 DuroPC Model R700-2-140002 2U Low Profile 3rd Gen Xeon Rackmount Computer FOB: Destination

NSN: 7G201022996281

VENDOR PART NR: 100002039797-0040

PURCHASE REQUEST NUMBER: 1301137663

PSC CD: 5962

NET AMT

ETHERNET CARD

Part Number: 207835 DuroPC PN 207835 4-Port 10/100/1000 Ethernet Card FOB: Destination

NSN: 7K201018718820

VENDOR PART NR: 100002039797-0040

NET AMT

Removeable Hard Drive Tray for DuroPC R7

Part Number: 218288 DuroPC PN 218288 Removeable Hard Drive Tray for DuroPC R700-2 FOB: Destination

NSN: 75201000000862

VENDOR PART NR: 100002039797-0040

NET AMT

Section C - Descriptions and Specifications

CLAUSES INCORPORATED BY FULL TEXT

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.

(End of text)

C-212-W002 COMMERCIAL SUPPLIER AGREEMENTS (NAVSEA) (MAR 2019)

(a) Commercial Supplier Agreement means End User License Agreement (EULA), Terms of Service (TOS), or similar legal instrument or agreement.

(b) Any Commercial Supplier Agreement must be provided in full text as part of a quote or offer without hyperlinks.

(c) The contract/order Schedule and Federal Acquisition Regulation (FAR) 52.212-4, Contract Terms and Conditions—Commercial Items, shall take precedence over any conflicting provisions in a Commercial Supplier Agreement.

(d) If any requirement in the Commercial Supplier Agreement conflicts with Federal law or regulations (see FAR 12.212(a)), the following shall apply:

(i) Any such requirement is unenforceable against the Government.

(ii) Neither the Government nor any Government authorized end user shall be deemed to have agreed to such requirement by virtue of it appearing in the Commercial Supplier Agreement. If the Commercial Supplier Agreement is invoked through an “I agree” click box or other comparable mechanism (e.g., “click-wrap” or “browse-wrap” agreements), execution does not bind the Government or any Government authorized end user to such requirement.

(iii) Any such requirement is deemed to be stricken from the Commercial Supplier Agreement.

(e) Automatic renewals. License Agreements will expire at end of the term identified in the Purchase Order/Contract. Automatic renewals are not permitted and any such provision is void.

(f) Changes to the Commercial Supplier Agreement. Unilateral changes of the Commercial Supplier Agreement are impermissible and any requirement authorizing such changes is unenforceable. Changes must be in writing and executed by both parties to be effective.

(g) Third Part License (Embedded Software).

(i) The Contractor agrees that it has obtained all necessary licenses for the Government for any third party materials (including without limitation all Open Source licenses) provided within the product.

(ii) Contractor agrees that it complies with and shall continue to comply with all of its obligations under Third Party Licenses (including without limitation all Open Source licenses) associated with any third party materials provided within each product.

(iii) To the extent that the Government’s use of the software products licensed herein is in compliance with the Contractor’s Commercial Supplier Agreement, the Government’s use will also be in compliance with any Third Party Licenses.

(h) Audits. In lieu of any audit provisions in the Commercial Supplier Agreement, the Government agrees that, no more than once every twelve (12) months or within a reasonable time after a transfer, the Contractor shall, upon reasonable notice, have the right to require that the Government conduct an internal audit to ascertain and verify the number of licenses in use and to verify that the Government’s use of the product is in conformity with this Agreement. The Government is not required to use any tools provided by the Contractor to conduct the audit and shall not be required to pay for any tools provided by the Contractor to conduct the audit. The results of any such audit shall be kept confidential.

If verification discloses that the Government’s use is not in conformity with this Agreement, the Government agrees to resolve any noncompliance by either removing or correcting the unlicensed installation and use of the software identified by the audit as not in conformity with this Agreement.

(i) Confidentiality. Commercial Supplier Agreements’ terms and the final contract pricing may not be deemed confidential. Other marked confidential information will be appropriately guarded.

(j) Assignment. The Government shall have the right, without the prior written consent of the Contractor or its authorized resellers, to assign, reassign, or transfer software licenses among Government employees or the Government’s rights in the Contractor’s product to any governmental organization that is managed, operated, or controlled by the Government.

Such authorization includes sublicensing, and assignment or transfer among or between authorized users. In the event authorized users are reorganized or restructured such that their responsibilities and operations are transferred to another government agency, the agency shall have the right to assign the affected program licenses to a successor agency. The licensed agency and the successor agency agree to be bound to the Commercial Supplier Agreement as modified. The transferee shall be bound by the license metrics and limitations in this license. Government shall complete any documentation required by the Contractor to facilitate the transfer of this license, and continuation of support shall be the responsibility of the transferee.

For the avoidance of doubt, any assignment or transfer of licenses of the Contractor’s products is also subject to all other terms of the Commercial Supplier Agreement, as well as the Contractor’s policies governing product dependencies and version compatibility. Reassignment does not require that the license be under maintenance or support in order to execute a transfer.

(k) Litigation. Any requirement insisting that the commercial supplier or licensor control any litigation arising from the government’s use of the contractor’s supplies or services is deleted and unenforceable.

(l) Equitable Remedies. Equitable remedies, injunctive relief, and binding arbitration requirements shall not be enforced unless explicitly authorized by agency guidance or statute.

(m) Venue. Any claim or dispute shall be resolved under the Contract Disputes Act and FAR 52.233-1. The forum for resolution of disputes and applicable statutes of limitation shall be governed by federal law.

(n) Applicable law. In accordance with FAR 52.233-4, United States law shall apply to resolve any claim of breach of this contract and such actions shall be handled in the applicable Federal court of jurisdiction.

C-227-H007 SOFTWARE DEVELOPMENT REQUIREMENTS (NAVSEA) (OCT 2018)

(a) The contractor shall define a general Software Development Plan (SDP) appropriate for the computer software effort to be performed under this contract. The SDP shall be delivered to the Government for concurrence under CDRL and shall not vary significantly from that proposed to the Government for evaluation for award. The contractor shall follow the Government concurred with SDP for all computer software to be developed or maintained under this effort. Any changes, modifications, additions or substitutions to the SDP also require prior Government concurrence.

(b) The SDP shall, at a minimum:

(1) Define the contractor's proposed life cycle model and the processes used as a part of that model. In this context, the term "life cycle model" is as defined in IEEE Std. 12207:2017;

(2) Contain the information defined by ISO/IEC/IEEE 15289:2017, section 7.3 “Plan - generic content” and Table 2 “Mapping of ISO/IEC 12207:2008 (IEEE Std. 12207:2008) Clauses to Information Items for Each Software Life Cycle Process.” In all cases, the level of detail shall be sufficient to define all software development processes, activities, and tasks to be conducted for this contract;

(3) Identify the specific standards, methods, tools, actions, strategies, and responsibilities associated with development and qualification;

(4) Document all processes applicable to the system to be acquired, including the Primary, Supporting, and Organizational life cycle processes as defined by IEEE Std. 12207:2017 as appropriate. Such processes shall be equivalent to those articulated by CMMI®;

(5) Adhere to the characteristics defined in ISO/IEC/IEEE 15289:2017 section 6.1 “Life-cycle data characteristics,” as appropriate;

(6) Be in accordance with the framework defined in IEEE Std. 12207:2017, including, but not limited to, defining the processes, the activities to be performed as a part of the processes, the tasks which support the activities, and the techniques and tools to be used to perform the tasks;

(7) Contain a level of information sufficient to allow the use of the SDP as the full guidance for the developers. In accordance with ISO/IEC/IEEE 15289:2017 Section 7.3, such information shall at a minimum contain, specific standards, methods, tools, actions, reuse strategy, and responsibility associated with the development and qualification of all requirements, including safety and security.

C-227-H010 COMPUTER SOFTWARE AND COMPUTER DATA BASES DELIVERED TO OR RECEIVED FROM THE GOVERNMENT (NAVSEA) (JAN 2019)

(a) The Contractor agrees to test for viruses, malware, Trojan Horses, and other security threats such as those listed in NIST Special Publication 800-12 Rev 1, An Introduction to Computer Security, The NIST Handbook, Chapter 4, in all computer software and computer data bases (as defined in the clause entitled “Rights In Noncommercial Computer Software and Noncommercial Computer Software Documentation” (DFARS 252.227-7014)), before delivery of that computer software or computer data base in whatever media and on whatever system the computer software or data base is delivered whether delivered separately or imbedded within delivered equipment. The Contractor warrants that when delivered any such computer software and computer data base shall be free of viruses, malware, Trojan Horses, and other security threats such as those listed in NIST Special Publication 800-12 Rev 1.

(b) The Contractor agrees that prior to use under this contract, it shall test any computer software and computer data base received from the Government for viruses, malware, Trojan Horses, and other security threats listed in NIST Special Publication 800-12 Rev 1, An Introduction to Computer Security, The NIST Handbook, Chapter 4.

(c) Any license agreement governing the use of any computer software or computer software documentation delivered to the Government as a result of this contract must be paid-up, irrevocable, world-wide, royalty-free, perpetual and flexible (user licenses transferable among Government employees and personnel under Government contract).

(d) The Contractor shall not include or permit to be included any routine to enable the contractor or its subcontractor(s) or vendor(s) to disable the computer software or computer data base after delivery to the Government.

(e) No copy protection devices or systems shall be used in any computer software or computer data base delivered under this contract with unlimited or Government purpose rights (as defined in DFARS 252.227-7013 and 252.227-7014) to restrict or limit the Government from making copies.

(f) It is agreed that, to the extent that any technical or other data is computer software by virtue of its delivery in digital form, the Government shall be licensed to use that digital-form data with exactly the same rights and limitations as if the data had been delivered as hard copy.

(g) Any limited rights legends or other allowed legends placed by a Contractor on technical data or other data delivered in digital form shall be digitally included on the same media as the digital-form data and must be associated with the corresponding digital-form technical data to which the legend(s) apply to the extent possible. Such legends shall also be placed in human-readable form on a visible surface of the media carrying the digital-form data as delivered, to the extent possible.

C-227-H014 PROTECTION OF DEPARTMENT OF NAVY TRADEMARKS - BASIC (NAVSEA) (JUL 2021)

(a) The contractor shall not assert any claim, in any jurisdiction, based on trademark or other name or design-based causes of action that are based on rights the contractor believes it has in the term(s) [contracting officers shall list terms(s) (Government assigned or approved nomenclature)] (the “Designation(s)”), against the Government or others authorized by the Government to use the Designation(s) (including the word(s), name, symbol, or design) acting within the scope of such authorization (i.e. claims for trademark infringement, dilution, trade dress infringement, unfair competition, false advertising, palming off, passing off, or counterfeiting). Such authorization shall be implied by the award of a Government contract to any party for the manufacture, production, distribution, use, modification, maintenance, sustainment, or packaging of the products and services identified under this contract, and the scope of such implied authorization is defined as the use of the Designation(s) in performance under such contract by the prime contractor and its subcontractors and suppliers at any tier. In all other cases, the scope of the authorization will be defined by the Government in writing.

(b) The contractor shall notify the contracting officer at least 30 days before asserting rights in, or filing an application to register, any one of the Designation(s) in any jurisdiction within the United States. Any such notification shall be in writing and shall identify the Designation(s) (including the word(s), name, symbol, or design), provide a statement as to its intended use(s) in commerce, and list the particular classes of goods or services in which registration will be sought.

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-239-W001 ELECTRONIC AND INFORMATION TECHNOLOGY (EIT) ACCESSIBILITY STANDARDS/SECTION 508 COMPLIANCE (NAVSEA) (OCT 2018)

(a) Requirements for accessibility based on Section 508 of the Rehabilitation Act of 1973 (29 U.S.C. 794d) are determined to be relevant for product(s)/service(s) procured under this solicitation.

(b) Each Electronic and Information Technology (EIT) item or service provided under this contract shall comply with the EIT Accessibility Standards listed below:

_____ 36 C.F.R. § 1194.21 - Software applications and operating systems _____ 36 C.F.R. § 1194.22 - Web-based and internet information and applications _____ 36 C.F.R. § 1194.23 - Telecommunications products _____ 36 C.F.R. § 1194.24 - Video and multimedia products _____ 36 C.F.R. § 1194.25 - Self-contained, closed products _ X _ 36 C.F.R. § 1194.26 - Desktop and portable computers _____ 36 C.F.R. § 1194.31 - Functional Performance Criteria _____ 36 C.F.R. § 1194.41 - Information, Documentation, and Support

(c) For more information on Voluntary Product Accessibility Template (VPAT) and Government Product/Service Accessibility Template (GPAT) please refer to: http://www.buyaccessible.gov/ or http://www.section508.gov/content/sell/vpat.

(d) The Contractor shall comply with the VPAT or GPAT document submitted. If the Contracting Officer determines that any item or service delivered under this contract does not comply with the EIT Accessibility Standards, the Contracting Officer will notify the Contractor in writing accordingly. If the Contractor fails to promptly correct or replace the nonconforming products or services with conforming products or services within the delivery schedule contained in the contract, the Government will have the rights and remedies contained in the basic contract.

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) (DEC 2020)

Item(s) 0001-0003 The supplies furnished hereunder shall be packaged in accordance with ASTM-D-3951-18, Standard Practice for Commercial Packing.

D-247-H004 MARKING AND PACKING LIST(S) – BASIC (NAVSEA) (FEB 2022)

(a) Marking. Shipments, shipping containers and palletized unit loads shall be marked in accordance with ASTM-D-3951-18 approved 1 May 2018, Standard Practice for Commercial Packing.

(b) Packing List(s). A packing list (DD Form 250 Material Inspection and Receiving Report may be used) identifying the contents of each shipment, shipping container or palletized unit load shall be provided by the Contractor with each shipment. When a contract line item identified under a single stock number includes an assortment of related items such as kit or set components, detached parts or accessories, installation hardware or material, the packing list(s) shall identify the assorted items. Where assortment of related items is included in the shipping container, a packing list identifying the contents shall be furnished.

(c) Master Packing List. In addition to the requirements in paragraph (b) above, a master packing list shall be prepared where more than one shipment, shipping container or palletized unit load comprise the contract line item being shipped. The master packing list shall be attached to the number one container and so identified.

(d) Part Identification. All items within the kit, set, installation hardware or material shall be suitably segregated and identified within the unit pack(s) or shipping container by part number and/or national stock number.

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:

CLAUSES INCORPORATED BY REFERENCE

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.

Section F - Deliveries or Performance

DELIVERY INFORMATION

FOB: Destination

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*

Service Approver (DoDAAC)

Service Acceptor (DoDAAC)

(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 Send additional notifications to:

Irina Schvarzman Irina.G.Schvarzman.CIV@US.Navy.Mil

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

(End of clause)

G-232-H002 PAYMENT INSTRUCTIONS (NAVSEA) (FEB 2024)

Payment office allocation methods can be found in the table at DFARS PGI 204.7108(b)(2) (https://www.acq.osd.mil/dpap/dars/pgi/pgi_htm/current/PGI204_71.htm#payment_instructions).

THIS ENTIRE CONTRACT IS FIRM FIXED PRICE

(End of Text)

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

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

Jillian Randazzo Contract Specialist Naval Sea Systems Command (NAVSEA) Naval Surface Warfare Center Philadelphia Division 5001 South Broad Street Philadelphia, PA 19112-5083 Phone: 215-897-2235 Email: jillian.randazzo@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

(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: Nyebeju Kpodi Address: [ 1601 Langley Ave Bldg 542] [Philadelphia, PA 19112] Phone: (215) 897-1036 E-mail: Nyebeju.J.Kpodi.CIV@US.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] E-mail: [ * ]

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

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

Name: [ * ] Address:

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

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

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

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

[ * ] To be completed at contract award (End of Text)

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:

All functions will be retained by the PCO

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

All functions will be retained by the PCO

Section I - Contract Clauses

CLAUSES INCORPORATED BY REFERENCE

52.209-4 FIRST ARTICLE APPROVAL--GOVERNMENT TESTING (SEP 1989)

(Contracting Officer shall insert details)

(a) The Contractor shall deliver unit(s) of Lot/Item within calendar days from the date of this contract to the Government at (insert name and address of the testing facility) for first article tests. The shipping documentation shall contain this contract number and the Lot/Item identification. The characteristics that the first article must meet and the testing requirements are specified elsewhere in this contract.

(b) Within calendar days after the Government receives the first article, the Contracting Officer shall notify the Contractor, in writing, of the conditional approval, approval, or disapproval of the first article. The notice of conditional approval or approval shall not relieve the Contractor from complying with all requirements of the specifications and all other terms and conditions of this contract. A notice of conditional approval shall state any further action required of the Contractor. A notice of disapproval shall cite reasons for the disapproval.

(c) If the first article is disapproved, the Contractor, upon Government request, shall submit an additional first article for testing. After each request, the Contractor shall make any necessary changes, modifications, or repairs to the first article or select another first article for testing. All costs related to these tests are to be borne by the Contractor, including any and all costs for additional tests following a disapproval. The Contractor shall furnish any additional first article to the Government under the terms and conditions and within the time specified by the Government. The Government shall act on this first article within the time limit specified in paragraph (b) of this clause. The Government reserves the right to require an equitable adjustment of the contract price for any extension of the delivery schedule or for any additional costs to the Government related to these tests.

(d) If the Contractor fails to deliver any first article on time, or the Contracting Officer disapproves any first article, the Contractor shall be deemed to have failed to make delivery within the meaning of the Default clause of this contract.

(e) Unless otherwise provided in the contract, the Contractor--

(1) May deliver the approved first article as a part of the contract quantity, provided it meets all contract requirements for acceptance and was not consumed or destroyed in testing; and

(2) Shall remove and dispose of any first article from the Government test facility at the Contractor's expense.

(f) If the Government does not act within the time specified in paragraphs (b) or (c) of this clause, the Contracting Officer shall, upon timely written request from the Contractor, equitably adjust under the Changes clause of this contract the delivery or performance dates and/or the contract price, and any other contractual term affected by the delay.

(g) The Contractor is responsible for providing operating and maintenance instructions, spare parts support, and repair of the first article during any first article test.

(h) Before first article approval, the acquisition of materials or components for, or the commencement of production of, the balance of the contract quantity is at the sole risk of the Contractor. Before first article approval, the costs thereof shall not be allocable to this contract for (1) progress payments, or (2) termination settlements if the contract is terminated for the convenience of the Government.

(i) The Government may waive the requirement for first article approval test where supplies identical or similar to those called for in the schedule have been previously furnished by the Offeror/Contractor and have been accepted by the Government. The Offeror/Contractor may request a waiver.

52.212-4 CONTRACT TERMS AND CONDITIONS--COMMERCIAL PRODUCTS AND COMMERCIAL SERVICES (NOV 2023)

(a) Inspection/Acceptance. The Contractor shall only tender for acceptance those items that conform to the requirements of this contract. The Government reserves the right to inspect or test any supplies or services that have been tendered for acceptance. The Government may require repair or replacement of nonconforming supplies or reperformance of nonconforming services at no increase in contract price. If repair/replacement or reperformance will not correct the defects or is not possible, the Government may seek an equitable price reduction or adequate consideration for acceptance of nonconforming supplies or services. The Government must exercise its post-acceptance rights-

(1) Within a reasonable time after the defect was discovered or should have been discovered; and

(2) Before any substantial change occurs in the condition of the item, unless the change is due to the defect in the item.

(b) Assignment. The Contractor or its assignee may assign its rights to receive payment due as a result of performance of this contract to a bank, trust company, or other financing institution, including any Federal lending agency in accordance with the Assignment of Claims Act (31 U.S.C. 3727). However, when a third party makes payment (e.g., use of the Governmentwide commercial purchase card), the Contractor may not assign its rights to receive payment under this contract.

(c) Changes. Changes in the terms and conditions of this contract may be made only by written agreement of the parties.

(d) Disputes. This contract is subject to 41 U.S.C. chapter 71, Contract Disputes. Failure of the parties to this contract to reach agreement on any request for equitable adjustment, claim, appeal or action arising under or relating to this contract shall be a dispute to be resolved in accordance with the clause at Federal Acquisition Regulation (FAR) 52.233-1, Disputes, which is incorporated herein by reference. The Contractor shall proceed diligently with performance of this contract, pending final resolution of any dispute arising under the contract.

(e) Definitions. The clause at FAR 52.202-1, Definitions, is incorporated herein by reference.

(f) Excusable delays. The Contractor shall be liable for default unless nonperformance is caused by an occurrence beyond the reasonable control of the Contractor and without its fault or negligence such as, acts of God or the public enemy, acts of the Government in either its sovereign or contractual capacity, fires, floods, epidemics, quarantine restrictions, strikes, unusually severe weather, and delays of common carriers. The Contractor shall notify the Contracting Officer in writing as soon as it is reasonably possible after the commencement of any excusable delay, setting forth the full particulars in connection therewith, shall remedy such occurrence with all reasonable dispatch, and shall promptly give written notice to the Contracting Officer of the cessation of such occurrence.

(g) Invoice.

(1) The Contractor shall submit an original invoice and three copies (or electronic invoice, if authorized) to the address designated in the contract to receive invoices. An invoice must include--

(i) Name and address of the Contractor;

(ii) Invoice date and number;

(iii) Contract number, line item number and, if applicable, the order number;

(iv) Description, quantity, unit of measure, unit price and extended price of the items delivered;

(v) Shipping number and date of shipment, including the bill of lading number and weight of shipment if shipped on Government bill of lading;

(vi) Terms of any discount for prompt payment offered;

(vii) Name and address of official to whom payment is to be sent;

(viii) Name, title, and phone number of person to notify in event of defective invoice; and

(ix) Taxpayer Identification Number (TIN). The Contractor shall include its TIN on the invoice only if required elsewhere in this contract.

(x) Electronic funds transfer (EFT) banking information.

(A) The Contractor shall include EFT banking information on the invoice only if required elsewhere in this contract.

(B) If EFT banking information is not required to be on the invoice, in order for the invoice to be a proper invoice, the Contractor shall have submitted correct EFT banking information in accordance with the applicable solicitation provision, contract clause (e.g., 52.232-33, Payment by Electronic Funds Transfer—System for Award Management, or 52.232-34, Payment by Electronic Funds Transfer--Other Than System for Award Management), or applicable agency procedures.

(C) EFT banking information is not required if the Government waived the requirement to pay by EFT.

(2) Invoices will be handled in accordance with the Prompt Payment Act (31 U.S.C. 3903) and Office of Management and Budget (OMB) prompt payment regulations at 5 CFR part 1315.

(h) Patent indemnity. The Contractor shall indemnify the Government and its officers, employees and agents against liability, including costs, for actual or alleged direct or contributory infringement of, or inducement to infringe, any United States or foreign patent, trademark or copyright, arising out of the performance of this contract, provided the Contractor is reasonably notified of such claims and proceedings.

(i) Payment.--

(1) Items accepted. Payment shall be made for items accepted by the Government that have been delivered to the delivery destinations set forth in this contract.

(2) Prompt payment. The Government will make payment in accordance with the Prompt Payment Act (31 U.S.C. 3903) and prompt payment regulations at 5 CFR part 1315.

(3) Electronic Funds Transfer (EFT). If the Government makes payment by EFT, see 52.212-5(b) for the appropriate EFT clause.

(4) Discount. In connection with any discount offered for early payment, time shall be computed from the date of the invoice. For the purpose of computing the discount earned, payment shall be considered to have been made on the date which appears on the payment check or the specified payment date if an electronic funds transfer payment is made.

(5) Overpayments. If the Contractor becomes aware of a duplicate contract financing or invoice payment or that the Government has otherwise overpaid on a contract financing or invoice payment, the Contractor shall--

(i) Remit the overpayment amount to the payment office cited in the contract along with a description of the overpayment including the--

(A) Circumstances of the overpayment (e.g., duplicate payment, erroneous payment, liquidation errors, date(s) of overpayment);

(B) Affected contract number and delivery order number, if applicable;

(C) Affected line item or subline item, if applicable; and

(D) Contractor point of contact.

(ii) Provide a copy of the remittance and supporting documentation to the…