N6449822Q4267.docx

N6449822Q4267

Section B - Supplies or Services and Prices

Microm Support 1

FFP

First Year of Microm Support to include:

FOB: Destination

VENDOR PART NR: 100001769051-0040

PURCHASE REQUEST NUMBER: 1301024679

PSC CD: 7A20

NET AMT

MICROM SUPPORT 2

FFP

Second Year of Microm Support to include:

FOB: Destination

VENDOR PART NR: 100001769051-0040

PURCHASE REQUEST NUMBER: 1301024679

PSC CD: 7A20

NET AMT

Section C - Descriptions and Specifications

STATEMENT OF WORK

Performance Work Statement (PWS) for Mircom Non-Recurring Engineering Services (NRE) for LHD/A Machinery Control Systems (MCS) Fire Alarm Control Panel

1) INTRODUCTION

i) This contract is for non-personal services. It does not create employment rights with the U.S. Government whether actual, inherent, or implied.

Government / Contractor Relationship

ii) The services to be performed under this purchase order are non-personal services and the parties recognize and agree that no employer-employee relationship exists or will exist under the task order between the Government and the Contractor's personnel. Therefore, it is in the best interest of the Government to provide both parties a full understanding of their respective obligations.

iii) The Contractor employees shall identify themselves as Contractor personnel by introducing themselves or being introduced as Contractor personnel and displaying distinguishable badges or other visible identification for meetings with Government personnel. In addition, Contractor personnel shall appropriately identify themselves as Contractor employees in telephone conversations and in formal and informal written correspondence.

iv) Contractor personnel under this purchase order shall not engage in any of the inherently Governmental functions listed at FAR Subpart 7.5 or DFARS Subpart 207.5.

v) Employee Relationship:

(1) The services to be performed under this purchase order do not require the Contractor or its personnel to exercise personal judgment and discretion on behalf of the Government. Rather the Contractor's personnel will act and exercise personal judgment and discretion on behalf of the Contractor.

(2) Rules, regulations, directives, and requirements that are issued by the U. S. Navy and NSWCPD under its responsibility for good order, administration, and security are applicable to all personnel who enter a Government installation or who travel on Government transportation. This is not to be construed or interpreted to establish any degree of Government control that is inconsistent with a non-personal services contract.

vi) Inapplicability of Employee Benefits: This task order does not create an employer-employee relationship. Accordingly, entitlements and benefits applicable to such relationships do not apply.

vii) Notice. It is the Contractor's, as well as the Government's, responsibility to monitor task order activities and notify the Contracting Officer if the Contractor believes that the intent of this Section has been or may be violated.

The Contractor should notify the Contracting Officer in writing within three (3) calendar days from the date of any incident that the Contractor considers to constitute a violation of this Section. The notice should include the date, nature, and circumstances of the conduct; the name, function, and activity of each Government employee or Contractor official or employee involved or knowledgeable about such conduct; identify any documents or substance of any oral communication involved in the conduct; and the estimate in time by which the Government must respond to this notice to minimize cost, delay, or disruption of performance.

The Contracting Officer will, within five (5) calendar days after receipt of notice, respond to the notice in writing. In responding, the Contracting Officer will either:

Confirm the conduct is in violation and when necessary direct the mode of further performance, Countermand any communication regarded as a violation, Deny that the conduct constitutes a violation and when necessary direct the mode of further performance, or In the event the notice is inadequate to make a decision, advise the Contractor what additional information is required, and establish the date by which it should be furnished by the Contractor.

2) BACKGROUND

The LHD/A Machinery Control System (MCS) Land-Based Test Facility (LBTF) is a mixture of Tactical, units that are identical to those supplied with the shipboard MCS, and “non-tactical” equipment, units that emulate shipboard MCS equipment and/or emulate systems that are controlled and monitored by the MCS, that emulates a fully functional MCS, for the purpose of testing and integration of MCS software during development, testing and integration of the MCS Local Area Network (LAN), duplication of the MCS operating environment to support troubleshooting during shipboard integration testing and trials, testing and integration of changes to MCS software and/or hardware and training in MCS Operation and Maintenance.

The LHD/A MCS Tech Refresh Program is responsible for the prototyping, developing, testing and evaluating components that will, if successful, be used to replace ageing legacy shipboard components. The LHDA MCS team intend to use Mircom’s already established experience and expertise with fire alarm control panels to customize a solution that will satisfy shipboards safety requirements. This will ensure the Tech Refresh team has the knowledge necessary to effectively and efficiently develop and test prototypes to be incorporated into the shipboard environment.

3) SCOPE OF WORK

The Contractor shall provide Non-Recurring Engineering (NRE) support services to modify fire alarm control panel in order for it to suitable for shipboard integration.

· NRE Support, up to 80 hours annually

· Mircom will provide 1 hour conference call with LHD/A MCS staff as requested with 5 business days’ notice.

· Call will be open forum to discuss any NSWCPD items/issues including training on fire panel, feature enhancements requests, or escalated support requests.

· Develop and maintain a custom NSWCPD System Configuration Utility

· Mircom to issue and maintain a configuration utility customized to the NSWCPD’s specific requirements outlined in Schedule ‘B’ of Ref. A.

· General Software, Firmware, Hardware Updates

· Mircom to issue software, firmware, and hardware customized to NSWCPD requirements when major version changes are released to production on Mircom’s side at the NSWCPD’s request.

The LHD/A MCS Team will take ownership of the completed deliverables and retain the right to use said deliverables through the consideration of a suitable manufacturer. The Contractor shall acknowledge that they retain no right to the completed deliverables.

4) REFERENCE DOCUMENTS

Reference A: Product Support Agreement-Mircom

5) DESIGN REQUIREMENTS

LHD/A MCS has requested to use Mircom’s system without the use of a USB key to manage licensing and programming changes in the system configuration utility. In order to eliminate the need for a USB key to manage licensing and programming changes in the system configuration utility, Mircom has prepared the following initial framework for discussion and finalization in collaboration with the LHD/A MCS team. A custom branded configuration utility software shall be issued with the following properties:

a) USB Key is not required to manage the panel programming;

b) Custom logo (320px x 80px) will appear on the LHD/A MCS panel displays similar to below.

c) Custom icon to launch the configuration utility will be provided similar to the icon below.

d) LHD/A MCS configurator will be compatible with LHD/A MCS panels exclusively and can not be used for generally programming other fire alarm systems.

e) LHD/A MCS configurator can be installed on any number of laptops desired.

f) Mircom will use all commercially reasonable efforts to deliver the configurator within 90 days of the Effective Date of this Agreement.

6) CDRLS

Status Report: (CDRL A001)

i) Contractor shall provide status reports as needed.

7) SECURITY REQUIREMENTS

Not Applicable.

8) PLACE OF PERFORMANCE

Work under this contract is to be performed at the Contractor’s facility or any location of the Contractor’s choosing.

9) PERIOD OF PERFORMANCE

From date of Award to 2 years after Award.

10) TRAVEL

Not Applicable.

11) TECHNICAL POINT OF CONTACT (TPOC)

Point of Contact:

Jenny Pang NSWC Philadelphia Division Code 515 LHD/A MCS Program Lead 1000 Kitty Hawk Avenue BLDG 77L Room 1111 Philadelphia, PA, 19112 Phone: (215) 897-8544

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-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-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 A001 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-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-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 _____ 36 C.F.R. § 1194.26 - Desktop and portable computers _____ 36 C.F.R. § 1194.31 - Functional Performance Criteria __X _ 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.

Section E - Inspection and Acceptance

INSPECTION AND ACCEPTANCE TERMS

Supplies/services will be inspected/accepted at:

CLAUSES INCORPORATED BY REFERENCE

E-246-H013 INSPECTION AND ACCEPTANCE OF DATA (NAVSEA) (OCT 2018)

Inspection and acceptance of all data shall be as specified on the attached Contract Data Requirements List(s), DD Form 1423.

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

22-JAN-2024

MITCHELL SOPER

NSWC PHILADELPHIA DIVISION

NSLC DETACHMENT

1601 LANGLEY AVE BLDG 542

PHILADELPHIA PA 19112

215-897-2468 FOB: Destination N64498

22-JAN-2025

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-1523 Kimberly.villano@navy.mil

Send additional notifications to:

Erica L. Treichel 215-897-2019 erica.l.treichel.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 AND CONTRACT TYPE SUMMARY FOR PAYMENT OFFICE (NAVSEA) (JUN 2018)

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

For Government Use Only

Allocation Method

52.212-4 (Alt I), Contract Terms and Conditions—Commercial Items 52.216-7, Allowable Cost and Payment 52.232-7, Payments under Time-and-Materials and Labor-Hour Contracts

52.232-1, Payments;

52.232-2, Payments under Fixed-Price Research and Development Contracts;

52.232-3, Payments under Personal Services Contracts;

52.232-4, Payments under Transportation Contracts and Transportation-Related Services Contracts; and 52.232-6, Payments under Communication Service Contracts with Common Carriers

52.232-29, Terms for Financing of Purchases of Commercial Items;

52.232-30, Installment Payments for Commercial Items

*Liquidation of Financing Payments. Liquidation will be applied by the payment office against those ACRNs which are identified by the payment instructions for the delivery payment and in keeping with the liquidation provision of the applicable contract financing clause (i.e., progress payment, performance-based payment, or commercial item financing).

(b) This procurement contains the following contract type(s):

*CR – Cost-Reimbursement FP – Fixed Price

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

(a) This procurement contains the following contract type(s):

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.

(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: Mitch Soper Address: [1601 Langley Ave Bldg 542] [Philadelphia, PA 19112] Phone: (215) 897-2468 E-mail: robert.m.soper7.civ@us.navy.mil

(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: [ * ] Address: [ *Street ] [ *City, State, Zip ] Phone: (Area Code) xxx- [xxxx]; FAX: (Area Code) xxx- [xxxx] E-mail: [ * ]

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

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:

Name: [ * ] Address:

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

(ii) The Contract Specialist is:

Name: [ * ] Address:

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

(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: [ * ] Address: [ *Street ] [ *City, State, Zip ] Phone: (Area Code) xxx- [xxxx]; FAX: (Area Code) xxx- [xxxx] E-mail: [ * ]

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

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