Solicitation - N6449826Q5242.pdf

REQUEST FOR QUOTATION

(THIS IS NOT AN ORDER)

THIS RFQ IS IS NOT A SMALL BUSINESS SET-ASIDE

15. DATE OF QUOTATION

16. SIGNER

a. NAME (Type or print)

c. TITLE (Type or print)

b. TELEPHONE

AREA CODE

NUMBER

STANDARD FORM 18 (REV. 6-95)

Prescribed by GSA-FAR (48 CFR) 53.215-1(a)

AUTHORIZED FOR LOCAL REPRODUCTION

Previous edition not usable

8. TO:

b. COMPANYa. NAME

c. STREET ADDRESS

d. CITY e. STATE f. ZIP CODE

9. DESTINATION

a. NAME OF CONSIGNEE

b. STREET ADDRESS

c. CITY

d. STATE e. ZIP CODE

7. DELIVERY

FOB DESTINATION

OTHER

(See Schedule)

10. PLEASE FURNISH QUOTATIONS TO THE

ISSUING OFFICE IN BLOCK 5a ON OR BEFORE CLOSE OF BUSINESS (Date)

IMPORTANT: This is a request for information and quotations furnished are not offers. If you are unable to quote, please so indicate on this form and return it to the address in Block 5a. This request does not commit the Government to pay any costs incurred in the preparation of the submission of this quotation or to contract for supplies or service. Supplies are of domestic origin unless otherwise indicated by quoter. Any representations and/or certifications attached to this Request for Quotation must be completed by the quoter.

11. SCHEDULE (Include applicable Federal, State and local taxes)

ITEM NO.

(a)

SUPPLIES/ SERVICES

(b)

QUANTITY

(c)

UNIT

(d)

UNIT PRICE

(e)

AMOUNT

(f)

12. DISCOUNT FOR PROMPT PAYMENT

a. 10 CALENDAR DAYS (%) b. 20 CALENDAR DAYS (%) c. 30 CALENDAR DAYS (%) d. CALENDAR DAYS

NUMBER PERCENTAGE

NOTE: Additional provisions and representations are are not attached.

13. NAME AND ADDRESS OF QUOTER

a. NAME OF QUOTER

b. STREET ADDRESS

c. COUNTY

d. CITY e. STATE f. ZIP CODE

14. SIGNATURE OF PERSON AUTHORIZED TO

SIGN QUOTATION

PAGE OF PAGES

1. REQUEST NO. 2. DATE ISSUED 3. REQUISITION/PURCHASE REQUEST NO. 4. CERT. FOR NAT. DEF.

UNDER BDSA REG. 2

AND/OR DMS REG. 1

RATING

5a. ISSUED BY 6. DELIVER BY (Date)

5b. FOR INFORMATION CALL (NO COLLECT CALLS)

NAME TELEPHONE NUMBER

AREA CODE NUMBER

Section A - Solicitation/Contract Form

Impedances Measurement Device (IMD)

N6449826Q5242

Section B - Supplies or Services & Prices or Costs

Additional Information/Notes

Item Supplies/Service Quantity Unit Unit Price Amount

0001 Modeling and Simulation Analysis

Pricing Arrangement: Firm Fixed Price

1 Job

Section C - Description/Specifications/Statement of Work SSxM Lab Power Corridor Demonstration Background In support of the ONR power corridor concept, NSWCPD plans to set up a demonstration of a number of existing SSxM power converters. Figure 1 shows a proposed first stage of this project. Therein, a topology is shown with SSCMs in parallel and one SSIM along with the Egston power supply.

In this proposed work, the system can be modeled in detail using Matlab Simulink. Also, the simulation can be used to program the SSCM and SSIM converters in the lab. Then, this system can be configured in one rack of the cabinets located in the flex lab at NSWCPD. This setup would be used to demonstrate start-up and dynamic operation of the system.

Figure 1. Topology of the stage 1 SSxM setup.

In the next stage, four SSCM converters are added to the system as shown in Figure 2. The Egston power supply will output 1kVdc, demonstrating medium-voltage operation. The SSCM paralleling algorithms used in stage 1 will be applied to the added SSCM converters. As with stage 1, the system will be modeled in detail and configured in the laboratory. The added SSCM modules can be configured in an adjacent rack of the cabinet.

This system would demonstrate 200kW of power which is the limit of the Egston power supply. Less power will flow to the loads considering SSxM efficiency. Due to the series connection of the two stages, SSxM converters are passing 400 kVA of power. Considering the rating of the SSxM converters, this demonstrates 640 kVA of installed power. It should be noted that there is a substantial amount of work involved in creating the systems of stage 1 and stage 2. Besides programing and testing the SSxM converters, there is an extensive amount of cabling as well as a thermal chiller loop and CAN communication connections.

Figure 2. Topology of the stage 2 SSxM setup.

As a future endeavor, stage 1 and stage 2 can be simply reconfigured and an added four SSCMs can make a more expansive system as shown in Figure 3. Likely, this would be in on cabinet. Also, a power supply larger than the Egston would be needed to supply the 500 kW of load power.

Figure 3. Topology of the stage 3 SSxM setup.

By copying the system of stage 3 and supplying it from the same 1kV source, the system of Figure 4 can be created. This would demonstrate 1 MW of load power. The second half of the system could be housed in a separate cabinet.

Figure 4. Topology of the stage 4 SSxM setup.

After successful operation of stage 4, the two cabinets housing each half of the system can be configured as shown in Figure 5. With a cable tray in the back to connect the cabinets, the total system would resemble the power corridor.

Figure 5. Configuration of the SSxM cabinets in a power corridor configuration.

Scope of Work For this project, the goal is to pursue the power corridor implementation as far as possible. Ideally, this would be stage 2 implementation in 2026.

Below, is a high-level list of what steps would be carried out by NSWCPD and Corzine Engineering (CE):

Carry out modeling and coding Create a detailed model of the stage 1 and stage 2 systems (CE) Write extended CAN code to control multiple SSxM converters (CE) Test in the Power Electronics lab (first occasion) Program the SSCM to include paralleling control, pre-charge connection, and unique CAN bus commands (CE) Carry out a full-voltage low-power test on parallel SSCMs (800V to 600V) showing CAN communication, pre-charge operation, individual start-up (ramp output voltage), and step change in load (CE/NSWCPD) Carry out a full-voltage low-power test of the SSIM showing CAN, pre-charge, start-up, and step load (CE/NSWCPD) Test in the flexible lab (first occasion) Move SSCMs and SSIM to the flex lab (NSWCPD) Connect the cooling system (NSWCPD) Run the required electrical cables on the back of the cabinet (NSWCPD) Connect the CAN network wires (NSWCPD) Connect the stage 1 system to Egston and load (NSWCPD) Test one SSCM at full power (NSWCPD/CE) Test two SSCMs at full power the bring on SSIM (NSWCPD/CE) Test in the Power Electronics lab (second occasion) Carry out full-voltage low-power test of three SSCMs in parallel (CE/NSWCPD) Carry out full-voltage low-power test of four SSCMs in parallel (CE/NSWCPD) Test in the flexible lab (second occasion) Move four SSCMs to the flex lab (NSWCPD) Connect added cooling, power cabling, and CAN bus (NSWCPD) Connect to Egston and an 800V load (NSWCPD) Test four SSCMs in parallel feeding an 800V load (NSWCPD/CE) Connect to previous system for full stage 2 test (NSWCPD/CE) As seen above, CE will carry out the modeling and programming work. CE will participate in the Power Electronics and flex lab experiments through three business trips to NSWCPD.

Budget The estimated cost for CE engineering services detailed above is . This is based on 360 projected hours at a rate of per hour. The salary rate is based on equivalent government wage rates for scientific and other professional personnel with specialized expertise in the field of power electronics.

Further to this approximately is needed for travel to make three week-long trips to NSWC Philadelphia. It is estimated that this work will be completed by 12/30/2026.

Statement of Work (SOW) for

ONR SSxM Hardware Support

1.0 INTRODUCTION

1.0.1 The Naval Surface Warfare Center Philadelphia Division (NSWCPD) is a Department of Defense entity responsible for research and development, test and evaluation, engineering and fleet support organization for the Navy's ships, submarines, military watercraft and unmanned vehicles. This requirement is for NSWCPD Code 321, which is responsible for supporting ONR 331 program deliverables.

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

1.0.3 Government/Contractor Relationship

1.0.3.1 The services to be delivered under this Contract/Task Order are non-personal services and the parties recognize and agree that no employer-employee relationship exists or will exist under the Contract/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.

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

1.0.3.3 Contractor personnel under this Contract/Task Order shall not engage in any of the inherently Governmental functions listed at FAR Subpart 7.5 or DFARS Subpart 207.5.

1.0.4 Employee Relationship:

1.0.4.1 The services to be performed under this Contract/Task 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.

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

1.0.4.3 Inapplicability of Employee Benefits: This Contract/Task Order does not create an employer-employee relationship. Accordingly, entitlements and benefits applicable to such relationships do not apply.

1.0.4.4 It is the Contractor's, as well as the Government's, responsibility to monitor Contract/Task Order activities and notify the Contracting Officer if the Contractor believes that the intent of this Section has been or may be violated.

1.0.4.4.1 The Contractor shall notify the Contracting Officer in writing via letter or email 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 Contractor's estimated date when, absent a response, cost, schedule or performance will be impacted.

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

(i) Confirm the conduct is in violation and when necessary direct the mode of further performance,

(ii) Countermand any communication regarded as a violation,

(iii) Deny that the conduct constitutes a violation and when necessary direct the mode of further performance, or

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

1.1 BACKGROUND

Naval Surface Warfare Center, Philadelphia Division (NSWCPD) Code 321 has received funding from ONR 331 in support of the Power Electronics Power Distribution Systems (PEPDS) program to construct a proof-of-concept Navy Integrated Power and Energy Corridor (NiPEC) utilizing legacy SSxM power converter/inverter modules. The SSxM modules have required some level or refurbishment and re-design to their control boards and power supplies, as well as module impedance characterization, previously aided under contract N6449823P5392. Continued support is required to develop control and cabinet design to operate several SSxM module together to meet the NiPEC-like prototype requirements outlined by ONR 331 in support of the PEPDS program.

1.2 SCOPE OF WORK

The Contractor shall provide engineering and technical services required for the design, development, documentation, testing and evaluation of legacy SSxM power converters inverters for use at NSWCPD. The contractor shall prepare all models and control code and documentation off-site and shall be required to travel to NSWCPD for testing and evaluation of the physical equipment.

2.0 APPLICABLE DOCUMENTS

n/a

3.0. REQUIREMENTS

ENSURE THAT TASKS ARE CLEARLY DEFINIED IN ORDER TO ENABLE ACCEPTANCE OF WORK AND ARE

APPROPRIATELY TIED TO CLINS AT THE LOWEST LEVEL POSSIBLE.

3.1 Carry out modeling and coding for multiple SSxM operation.

Modeling efforts for this project shall pursue the SSxM-based power corridor implementation as far as possible. Specifically, to stage 2 implementation in 2026, as outlined in the contractor provided SOW.

3.1.1 The Contractor, Corzine Engineering (CE) shall:

- Carry out modeling of multiple SSxM module and develop coding for their control

- Create a detailed model of the stage 1 and stage 2 systems (see contractor provided SOW)

- Write extended CAN code to control multiple SSxM converters

- Provide model description and control documentation.

3.2 Testing and evaluation of all deliverables shall be conducted by the contractor with the help of C321 at NSWCPD to validate and verify successful operation on SSxM hardware CDRL A001.

3.2.1 The Contractor shall:

1. Test in the Power Electronics lab (first occasion)

- Program the SSCM to include paralleling control, pre-charge connection, and unique CAN bus commands (CE)

- Carry out a full-voltage low-power test on parallel SSCMs (800V to 600V) showing CAN communication, pre-charge operation, individual start-up (ramp output voltage), and step change in load (CE/NSWCPD)

- Carry out a full-voltage low-power test of the SSIM showing CAN, pre-charge, start-up, and step load (CE

/NSWCPD)

2. Test in the flexible (FLEX) lab (first occasion)

- Test one SSCM at full power (CE/NSWCPD)

- Test two SSCMs at full power the bring on SSIM (CE/NSWCPD)

3. Test in the Power Electronics lab (second occasion)

- Carry out full-voltage low-power test of three SSCMs in parallel (CE/NSWCPD)

- Carry out full-voltage low-power test of four SSCMs in parallel (CE/NSWCPD)

4. Test in the FLEX lab (second occasion)

- Test four SSCMs in parallel feeding an 800V load (CE/NSWCPD)

- Connect to previous system for full stage 2 test (CE/NSWCPD)

5. Provide a final report outlining:

- The SSxM models and controls prepared in Section 3.1

- Results from hardware testing used to validate and verify the above models and controls

- A list of any tasking that was unable to be completed during the period of performance of the contract

CE will carry out the modeling and programming work and will participate in the Power Electronics and FLEX lab experiments through three business trips to NSWCPD.

3.3 Manufacturing Phase-Out or Discontinuation of Production, Diminishing Sources, and Obsolete Materials or Components (Note: Insert in Section C of all requirements (supply or service))

3.3.1 The contractor shall notify the contracting officer immediately upon determining the unavailability of obsolete materials or components. The contractor may recommend a solution to include the impact on the contract price and delivery. The contractor shall not initiate any item redesign or incur any additional costs without the express, written authorization of the contracting officer.

4.0 DATA REQUIREMENTS

4.1 CDRL A001 Technical Report (FINAL)

5.0 SECURITY REQUIREMENTS

. The Contractor is responsible for completing all required Government mandated training to maintain 5.1 SECURITY TRAINING security and network access to government sites and IT systems to include but not limited to: Antiterrorism Level 1 Awareness;

Records Management in the DON: Everyone's Responsibility; Training and Readiness: The Active Shooter; NAVSEA Introduction to Controlled Unclassified Information; Operations Security (OPSEC); NAVSEA Counterintelligence Training; Privacy and Personally Identifiable Information (PII) Awareness Training; NAVSEA Physical Security training and Cybersecurity 101 Training. Certificates of successful completion shall be sent to the COR and as otherwise specified in the contract.

5.1.1 In accordance with the National Industrial Security Program Operating Manual (NISPOM) (37 CFR Part 117), Contractor personnel that require access to Department of Navy (DON) information systems and/or work on-site require an open investigation or favorable adjudicated Tier 3 investigation. An interim clearance is granted by DCSA and recorded in the Defense Information System for Security (DISS). Must have a favorable fingerprint an open or closed investigation with a favorable adjudication in DISS is required prior to issuance of a badge providing access to NSWCPD buildings. Furthermore, if the Navy Central Adjudication Facility has made an unfavorable determination, access will be denied. For Common Access Card (CAC) you must have an open investigation and/or a favorably adjudicated investigation. Interim security clearance is acceptable for a CAC.

Access will be denied for anyone that has eligibility pending in DISS. Vetting through the National Crime Information Center, Sex Offender Registry, and the Terrorist screening database shall be process for a contractor that does not have a favorable adjudicated investigation.

5.2 Contractor personnel that require a badge to work on-site at one of the NSWCPD sites must provide an I-9 ON SITE WORK.

form to verify proof of citizenship. The I-9 form should be signed by the company Facility Security Officer or the company Human Resource Department. In addition to the I-9 form, Contractors shall also bring their birth certificate, current United States Passport or naturalization certificate and state issued REAL ID to the NSWCPD Security Officer at the time of badge request to verify citizenship. Any contractor that has unfavorable information that has not been favorably adjudicated, by Department of Defense Central Adjudication Facility (DOD CAF) will not be issued a badge. Finally, contractors shall supply a copy of their OPSEC Training Certificate or other proof that the training has been completed.

5.2.1 RESERVED

5.2.4 Reserved

5.3 DD254 REQUIREMENT.

n/a

5.4 OPERATIONS SECURITY (OPSEC)

5.4.1 The Contractor shall protect critical information associated with this contract to prevent unauthorized disclosure. The NSWC Philadelphia Division's (NSWCPD) Critical Information List (CIL)/ CIIL (Critical Indicators and information list) will be provided on site, if warranted. Performance under this contract requires the contractor to adhere to OPSEC requirements, which may include the NSWCPD Contractor OPSEC Plan. When the NSWCPD Contractor OPSEC Plan is required, the contractor shall return acknowledgment of the plan within 15 days of receipt. During the period of this contract, the Contractor may be exposed to, use, or produce, NSWCPD Critical Information (CI) and/or observables and indicators which may lead to discovery of CI. NSWCPD's CI will not be distributed to unauthorized third parties, including foreign governments, or companies under Foreign Ownership, Control, or Influence (FOCI) unless such FOCI has been appropriately mitigated through measures approved by the Defense Counterintelligence and Security Agency. Questions concerning these requirements shall be directed to the PCO.

5.4.2 CUI correspondence transmitted internally on the contractor's unclassified networks or information systems, and externally, shall be protected per NIST SP-800-171, Protecting Controlled Unclassified Information (CUI) in Non-federal Systems and Organizations.

Assembled large components/systems being transported to and from testing areas, other production or government facilities (whether or not on public roadways) shall be in an enclosed van trailer or covered flatbed trailer. Component/System outside storage, staging, and test areas shall be shielded/obscured from public view wherever physically possible.

5.4.3 NSWCPD's CI shall not be publicized in corporate wide newsletters, trade magazines, displays, intranet pages or public facing websites. Media requests related to this project shall be directed to the PCO, and the COR who will forward the required to the NSWCPD Public Release Authority for review.

5.4.4 Any attempt by unauthorized third parties to solicit, obtain, photograph, or record, or; incidents of loss/compromise of government Classified or CI, Business Sensitive, Company Proprietary information related to this or other program must be immediately reported to the contractor's Facility Security Officer and Cognizant Security Office and/or the Naval Criminal Investigative Service, and the NSWC PD Security Division (Code 105).

5.4.5 This SOW has been reviewed against the requirements of SECNAVINST 4200.35. SAIRC controls are not required

5.5 All RECEIPT, STORAGE, AND GENERATION OF CONTROLLED UNCLASSIFIED INFORMATION (CUI) Controlled Unclassified Information (CUI) associated with this contract must follow the minimum marking requirements of DoDI 5200.48, Section 3, paragraph 3.4.a, and include the acronym "CUI" in the banner and footer of the document. In accordance with DoDI 5200.48, CUI must be safeguarded to prevent Unauthorized Disclosure (UD). CUI export controlled technical information or other scientific, technical, and engineering information must be marked with an export control warning as directed in DoDI 5230.24, DoDD 5230.25, and Part 250 of Title 32, CFR. Nonfederal information systems storing and processing CUI shall be protected per

, or subsequent revisions. All transmissions to personal email accounts (AOL, Yahoo, Hotmail, Comcast, etc.) and NIST SP-800-171 posting on social media websites (Facebook, Instagram, Twitter, LinkedIn, etc.) are prohibited. Destroy CUI associated with this contract by any of the following approved methods: A cross-cut shredder listed on the "NSA/CSS Evaluated Products List for High Security Crosscut Paper shredders"; a certified commercial destruction vendor; a central destruction facility; incineration; chemical decomposition; pulverizing, disintegration; or methods approved for classified destruction.

. 5.6 Planning, Programming, Budgeting and Execution (PPBE) Data

When contractor employees, in the performance of their duties, are exposed to Planning, Programming, Budgeting and Execution (PPBE) data, a Non-Disclosure Agreement (NDA) with all affected contactor personnel must be executed in coordination with the COR and PCO to ensure safeguarding disclosure of this data.

5.7 U-NNPI SECURITY REQUIREMENTS

5.7.1 Security Classification Guidance is as follows of portions of the tasking on this contract when invoked in the task order statement of work:

5.7.1.1 Contractor requires access to information and equipment classified at the Confidential National Security Information (NSI) level in order to provide industrial support services within facilities that actively supports the Navy Nuclear Propulsion Program (NNPP).

5.7.1.2 All contractor personnel accessing classified information or classified material associated with the performance of work related to the resultant contract must be United States citizens, and shall have and maintain at a minimum Confidential security clearance.

5.7.1.3 The Contractor is responsible for completing all required government mandated training to maintain security and network access to government sites and IT systems, as necessary to support.

5.8 U-NNPI

5.8.1 Purpose The Contractor hereby agrees that when provided documents (specifications, drawings, etc.) that are marked as containing NOFORN sensitive information that must be controlled pursuant to Federal law, the information contained therein and generated as part of the inquiry shall be used only for the purpose stated in the contract and shall in no case be transmitted outside the company (unless such transmittals comply with the detailed guidance of the contract) or to any foreign national within the company.

While in use, the documents shall be protected from unauthorized observation and shall be kept secure so as to preclude access by anyone not having a legitimate need to view them. The documents shall not be copied unless done in conformance with the detailed guidance of the contract. All the documents shall be promptly returned in their entirety, unless authorized for proper disposal or retention, following completion of the contract.

5.9.2 Specific Requirements for Protecting U-NNPI

a) Only U.S. citizens who have a need to know required to execute the contract shall be allowed access to U-NNPI.

b) When not in direct control of an authorized individual, U-NNPI must be secured in a locked container (e.g., file cabinet, desk, safe). Access to the container must be such that only authorized persons can access it, and compromise of the container would be obvious at sight. Containers should have no labels that indicate the contents. If removed from the site, U-NNPI must remain in the personal possession of the individual. At no time should U-NNPI be left unsecured (e.g., in a home or automobile, or unattended in a motel room or sent with baggage).

c) U-NNPI documents will have the word NOFORN at the top and bottom of each page. The cover sheet will have the warning statement shown below. Documents originated in the course of work that reproduce, expand or modify marked information shall be marked and controlled in the same way as the original. Media such as video tapes, disks, etc., must be marked and controlled similar to the markings on the original information.

d) U-NNPI may not be processed on networked computers with outside access unless approved by CNO (N00N). If desired, the company may submit a proposal for processing NNPI on company computer systems. Personally owned computing systems, such as personal computers, laptops, personal digital assistants, and other portable electronic devices are not authorized for processing NNPI.

Exceptions require the specific approval of the cognizant DAA and CNO (N00N).

e) U-NNPI may be faxed within the continental United States and Hawaii provided there is an authorized individual waiting to receive the document and properly control it. U-NNPI may not be faxed to facilities outside the continental United States, including military installations, unless encrypted by means approved by CNO (N00N).

f) U-NNPI may be sent within the continental United States and Hawaii via first class mail in a single opaque envelope that has no markings indicating the nature of the contents.

g) Documents containing U-NNPI shall be disposed of as classified material.

h) Report any attempts to elicit U-NNPI by unauthorized persons to the appropriate security personnel.

i) Report any compromises of U-NNPI to the appropriate security personnel. This includes intentional or unintentional public release via such methods as theft, improper disposal (e.g., material not shredded, disks lost), placement on Web site, transmission via email, or violation of the information system containing U-NNPI.

j) The only approved storage for U-NNPI is CDMS NOFORN.

6.0 PLACE OF PERFORMANCE

6.1 The contractor's primary place of performance shall be at Corzine Engineering, with three business trips to government facilities in Philadelphia, PA (NSWCPD). It is estimated that 20% of the work will occur on-site at the NSWCPD facility and 80% of the work will occur off-site at the contractor facility.

6.1.1 Performance will occur at the following government sites: NSWCPD

7.0 TRAVEL

7.1 The Contractor may be required to travel from the primary performance location when supporting this requirement. The estimated number of trips is _3_for the entire period of performance.

The contractor shall be required to travel CONUS (any state in USA) to accomplish the tasks contained in this contract. Travel in support of this requirement is anticipated to include, but may not be limited to, the following alternate performance locations:

CONUS/OCONUS ORIGIN: DESTINATION: Number of Days Per Trip Number of Trips Number of People

CONUS CA Philadelphia, PA 5 3 1

7.2 The number of times the Contractor may be required to travel to each location cited above may vary as program requirements dictate, provided that the total estimated travel cost is not exceeded. The numbers of trips and types of personnel traveling shall be limited to the minimum required to accomplish work requirements. All travel shall be approved before travel occurs. Approval may be via email by the Contracting Officer (PCO), the Contacting Officer's Representative (COR) or the fully executed Technical Instruction (TI) signed by the Contracting Officer.

7.2.1 In accordance with the TI instructions, before initiating any travel the Contractor(s) shall submit a detailed and fully-burdened estimate that includes the number of employees traveling, their expected travel costs for airfare, lodging, per diem, rental car, taxi /mileage and any other costs or actions requiring approval. The travel estimate shall be submitted to the Contracting Officer's Representative (COR) and Contract Specialist. Actuals cost, resulting from the performance of travel requirements, shall be reported as part of the Contractor's monthly status report. The reportable cost shall also be traceable to the Contractor's invoice

7.4 Travel Costs

7.4.1 The current "maximum per diem" rates are set forth in the (i) Federal Travel Regulations for travel in the Continental United States; (ii) Joint Travel Regulations for Overseas Non-Foreign areas (e.g., Alaska, Hawaii, Guam, Puerto Rico, etc.); and (ii) Department of State (DOS) prescribed rates for foreign overseas locations.

7.5 Reserved

8.0 GOVERNMENT FURNISHED PROPERTY

n/a

9.0 GOVERNMENT FURNISHED INFORMATION

n/a

10.0 PURCHASES

n/a

11.0 Counterfeit Material Prevention

n/a

12.0 PERSONNEL

n/a

13.0 n/aNSWCPD Electronic Cost Reporting and Financial Tracking (eCRAFT) System

14.0 SPECIAL REQUIREMENTS

n/a

Requirements Impedances Measurement Device (IMD)

Additional Regulation or Supplemental Clauses Incorporated by Full Text

C-204-H001 USE OF NAVY SUPPORT CONTRACTORS FOR OFFICIAL CONTRACT FILES (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.

(End of Text)

C-211-H018 APPROVAL BY THE GOVERNMENT (NAVSEA) (JAN 2019) (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-215-H002 CONTRACTOR PROPOSAL (NAVSEA) (OCT 2018) (Oct 2018)

(a) Performance of this contract by the Contractor shall be conducted and performed in accordance with detailed obligations to which the Contractor committed itself in Proposal dated in response to NAVSEA Solicitation No.

N6449826Q5242 .

(b) The technical volume(s) of the Contractor's proposal is(are) hereby incorporated by reference and made subject to the "Order of Precedence" (FAR 52.215-8) clause of this contract. Under the "Order of Precedence" clause, the technical volume(s) of the Contractor's proposal referenced herein is (are) hereby designated as item (f) of the clause, following "the specifications" in the order of precedence.

(End of Text)

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

(JUL 2021)

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

(End of Text)

C-233-H001 DOCUMENTATION OF REQUESTS FOR EQUITABLE ADJUSTMENT--BASIC

(NAVSEA) (OCT 2018)

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

(End of Text)

C-247-H001 PERMITS AND RESPONSIBILITIES (NAVSEA) (DEC 2018) (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

Section E - Inspection and Acceptance

FAR Clauses Incorporated by Reference

Number Title Effective Date

Alternate/ Deviation

Variation Effective Date

52.246-4 Inspection of Services-Fixed-Price. Aug 1996

Overall Contract Inspection/Acceptance Locations

Inspection and Acceptance Location

Both Destination Instructions: Please Contact TPOC prior to delivery for instructions.

DoDAAC: N64498 CountryCode: USA

NSWC PHILADELPHIA DIV

1601 LANGLEY AVE BUILDING 542, PHILADELPHIA PA 19112

PHILADELPHIA, PA 19112

UNITED STATES

Christian Schegan, TPOC Email: Christian.m.schegan.civ@us.navy.mil Telephone: (215) 897-7825

Section F - Deliveries or Performance

Overall Contract Delivery Period

Contractor Destination

Line Item Delivery Schedule Quantity Address and POC

Delivery Period From 05 Jun 2026 to 30 Dec 2026

Period of Performance From 30 Jul 2026 To 31 Jul 2027

1 Job Ship To DoDAAC: N64498

NSWC PHILADELPHIA

5001 South Broad Street, BLDG 4 Philadelphia PA USA

FAR Clauses Incorporated by Reference

Number Title Effective Date

Alternate/ Deviation

Variation Effective Date

52.247-34 F.o.b. Destination. Jan 1991

Section G - Contract Administration Data

DFARS Clauses Incorporated by Reference

Number Title Effective Date

Alternate/ Deviation

Variation Effective Date

252.232-7003 Electronic Submission of Payment Requests and Receiving Reports. Dec 2018

DFARS Clauses Incorporated by Full Text

252.232-7006 Wide Area WorkFlow Payment Instructions. (Jan 2023)

WIDE AREA WORKFLOW PAYMENT INSTRUCTIONS (JAN 2023)

(a) As used in this clause- Definitions.

"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) The WAWF system provides the method to electronically process vendor payment requests and receiving reports, as Electronic invoicing.

authorized by Defense Federal Acquisition Regulation Supplement (DFARS) 252.232-7003, Electronic Submission of Payment Requests and Receiving Reports.

(c) To access WAWF, the Contractor shall- WAWF access.

(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) The Contractor should follow the training instructions of the WAWF Web-Based Training Course and use the Practice WAWF training.

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) Document submissions may be via web entry, Electronic Data Interchange, or File Transfer WAWF methods of document submission.

Protocol.

(f) The Contractor shall use the following information when submitting payment requests and receiving reports in WAWF payment instructions.

WAWF for this contract or task or delivery order:

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

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

(Contracting Officer: Insert applicable invoice and receiving report document type(s) for fixed price line items that require shipment of a deliverable.)

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

Invoice 2in1 for Services

(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 financing, submit a commercial 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) The Contractor shall use the information in the Routing Data Table below only to fill in applicable fields in WAWF Document routing.

when creating payment requests and receiving reports in the system.

Routing Data Table*

Field Name in WAWF Data to be entered in WAWF

Pay Official DoDAAC N64500

Issue By DoDAAC N64498

Admin DoDAAC N64498

Inspect By DoDAAC N64498

Ship To Code N64498

Ship From Code ____

Mark For Code N64498

Service Approver (DoDAAC) N64498

Service Acceptor (DoDAAC) N64498

Accept at Other DoDAAC ____

LPO DoDAAC ____

DCAA Auditor DoDAAC ____

Other DoDAAC(s) ____

(*Contracting Officer: Insert applicable DoDAAC information. If multiple ship to/acceptance locations apply, insert "See Schedule" or "Not applicable.")

(**Contracting Officer: If the contract provides for progress payments or performance-based payments, insert the DoDAAC for the contract administration office assigned the functions under FAR 42.302(a)(13).)

(4) The Contractor shall ensure a payment request includes documentation appropriate to the type of payment request in Payment request.

accordance with the payment clause, contract financing clause, or Federal Acquisition Regulation 52.216-7, Allowable Cost and Payment, as applicable.

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

(g) WAWF point of contact.

Christian M. Schegan

Christian.m.schegan.civ@us.navy.mil

(1) The Contractor may obtain clarification regarding invoicing in WAWF from the following contracting activity's WAWF point of contact.

N64498 - Caitlin Tamase email: caitlin.i.tamase.civ@us.navy.mil, (215) 756-2962

GAM Mailbox - email: NSWCPD_WAWF_GAM@navy.mil"

(Contracting Officer: Insert applicable information or "Not applicable.")

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

(End of clause)

Additional Regulation or Supplemental Clauses Incorporated by Full Text

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

2019)

(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 break down 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). Shouldthe 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.

(End of Text)

G-242-H001 GOVERNMENT CONTRACTADMINISTRATION POINTS-OF-CONTACT AND

RESPONSIBILITIES (NAVSEA) (OCT 2023)

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