N6449823Q5180.pdf
PDF 483 KB Posted
- Attached to
- LHD/A EP Switchboard Communication Non-Recurring Engineering Federal contract opportunity
- Solicitation number
- N6449823Q5180
About this file
This document is a request for quotations issued by the Naval Surface Warfare Center Philadelphia Division for non-recurring engineering services associated with LHD/A class electric plant switchboard communications software. The Navy requires configuration of fourteen SEL 3350 RTAC devices to concentrate data from SEL-311 relays and send it to an electrical plant machinery control system via Modbus TCP protocol. The contractor shall provide program management, requirements development, software design, testing documentation, and participate in project meetings and design reviews. The response due date is July 17, 2023. The contract type is fixed-price.
View the file
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
NAVAL SURFACE WARFARE CENTER PHILA
JOSEPH EVERLY
NSWC PHILADELPHIA DIVISION
NSLC DETACHMENT
1601 LANGLEY AVE BLDG 542
PHILADELPHIA PA 19112
TEL: (215) 897-7266 FAX:
1301087522
REQUEST FOR QUOTATIONS
(THIS IS NOT AN ORDER) 1
PAGE OF PAGES
1. REQUEST NO. 2. DATE ISSUED RATING
N6449823Q5180 29-Jun-2023 5a. ISSUED BY
8. TO: NAME AND ADDRESS, INCLUDING ZIP CODE
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 services. Supplies are of domestic origin unless otherwise indicated by quoter. Any representations and/or certifications attached to this
Request for Quotations 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) (f)
SEE SCHEDULE
AMOUNT
% No. %
NOTE: Additional provisions and representations [ ] are [ ] are not attached.
13. NAME AND ADDRESS OF QUOTER (Street, City, County, State, and ZIP Code)
14. SIGNATURE OF PERSON AUTHORIZED TO
SIGN QUOTATION
15. DATE OF
QUOTATION
16. NAME AND TITLE OF SIGNER (Type or print) (Include area code)
TELEPHONE NO.
AUTHORIZED FOR LOCAL REPRODUCTION STANDARD FORM 18 (REV. 6-95)
PREVIOUS EDITION NOT USABLE Prescribed by GSA FAR (48 CFR) 53.215-1(a)
THIS RFQ [ ] IS X[ ] IS NOT A SMALL BUSINESS SET-ASIDE
6. DELIVER BY (Date)
SEE SCHEDULE
AND/OR DMS REG. 1
UNDER BDSA REG. 2
4. CERT. FOR NAT. DEF.3. REQUISITION/PURCHASE
REQUEST NO.
NAVAL SURFACE WARFARE CENTER PHILA
CODE 0231, FRANK VENNELL
215-897-1337, FRANK.VENNELL@NAVY.MIL
5001 SOUTH BROAD STREET
PHILADELPHIA PA 19112
9. DESTINATION (Consignee and address, including ZIP Code)
7. DELIVERY
[ ]X FOB
DESTINATION
[ ] OTHER
(See Schedule)
17-Jul-2023(Date)
PLEASE FURNISH QUOTATIONS TO THE ISSUING OFFICE IN BLOCK 5a ON OR BEFORE CLOSE OF BUSINESS:10.
215-897-1337FRANK VENNELL
(Name and Telephone no.) (No collect calls)5b. FOR INFORMATION CALL:
d. CALENDAR DAYSc. 30 CALENDAR DAYSb. 20 CALENDAR DAYS12. DISCOUNT FOR PROMPT PAYMENT a. 10 CALENDAR DAYS
N6449823Q5180
Section B - Supplies or Services and Prices
ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT
0001 1 Lot Engineering Services
FFP
LHD/A EP Switchboard Communication Non-Recurring Engineering See Section C Statement of Work FOB: Destination
VENDOR PART NR: 100001919224-0020
PURCHASE REQUEST NUMBER: 1301087522
PSC CD: R425
NET AMT
Section C - Descriptions and Specifications
STATEMENT OF WORK
Statement of Work (SOW) for LHD/A SCD 25536 Electric Plant Switchboard Communications Software Non-Recurring Engineering
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 446, which is responsible for LCS, MMSC, LHD, LHA, CG, and USV Class shipboard electrical power and electrical propulsion systems.
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 is non-personal services and the parties recognize and agree that no employer-employee relationship exists or will exist under the Contract 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 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 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 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 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
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 446, which is responsible for LCS, MMSC, LHD, LHA, CG, and USV Class shipboard electrical power and electrical propulsion systems.
This requirement is for non-recurring engineering associated with proposed LHD/A SCD 25536 Electric Plant Switchboard Communications Software.
1.2 SCOPE OF WORK
The contractor shall provide non-recurring engineering associated with LHD/A Class SCD 25536 Electric Plant Switchboard Communications Software. The Electric Plant consists to 14 4kV Switchboards that will contain the SEL SDN Switch and SEL RTAC. These devices have been selected for 1) dimensional constraints, and 2) direct compatibility with the 55 installed SEL- 311N relays. Hardware procurement is out of the scope of this request for proposal but configuration details are available. The SEL-2032 collects and distributes data SEL-311N relays that are installed and are operating with Revision I settings using the SEL Communications Protocol. SEL RTAC collection of data from the SEL-311N will be based on metered values and statuses consistent with data collected by the existing SEL-2032 with modifications. The SEL RTAC shall be connected with up to 5 SEL-311Ns. For commonality of the interface definitions address space shall be common among all switchboard interfaces. The RTAC shall be configured to auto detect the switchboard it is located within, where SEL-311N data is used to identify then the SEL RTAC shall use all relay identifiers to confirm the location to prevent misconfiguration due to relay faults or maintenance.
2.0 APPLICABLE DOCUMENTS
Not applicable
3.0. REQUIREMENTS
3.1 The contractor shall provide program management
3.1.1 The Contractor shall provide a POAM of GFI Review, Requirements development, software design, and testing.
3.1.2 The Contractor shall support up to 2 hours per week for teleconference meetings with NSWCPD to discuss topics including Project Management, Development Status, Technical Requirements Discussion, and Risk Management activities. These meetings shall occur until the Contractor has finished all tasking identified in this SOW and provided it to the Government.
3.1.3 The Contractor shall hold a Preliminary Design Review virtual meeting and associated brief upon completion of GFI Review.
3.1.4 The Contractor shall hold a Critical Design Review virtual meeting and associated brief prior to Software Development.
3.1.5 The contractor shall demonstrate requirement traceability from GFI Requirement ID to Factory Acceptance Test Step(s) within an MS Excel compatible file format. The purpose of the traceability is to provide a quick lookup index that each requirement is tested in at least one test step.
3.2 The contractor shall provide non-recurring engineering associated with LHD/A Class SCD 25536 Electric Plant Switchboard Communications Software to include “Protection Grade” communications speed, security, and reliability necessary to meet the performance and latency requirements for electrical system fault protection.
3.2.1 The contractor shall develop SEL SDN Switch shall provide the communications interconnectivity for the EPMCS to communicate with each other and the subordinate devices to monitor and control 4kV switchboard sources, feeders, and bus interconnection. The EPMCS will monitor and display bus voltage, current, breaker status, and protection and system health and security statuses provided from the SEL RTAC. The signals will be used for SCADA and plant control sequences and shall update no slower than 500ms update with a goal of down to 80ms update rate from the SEL RTAC for SCD 25536 Electric Plant Switchboard Communications.
3.2.2 The contractor shall develop Software to meet all requirements identified in the government furnished information provided in section 9 of this statement of work including the following:
1. Functional Design Specification (FDS)
• Overall description of the Electric Plant Protection and Control system.
• Description of the hardware solution to upgrade the existing SEL-2032 based system to an SEL-RTAC based system.
• Design for automatic detection of SEL-RTAC / Switchboard connection.
• Communication parameters, including Serial and Ethernet based devices.
• Communication protocol maps.
2. RTAC Programming
• SEL-RTAC settings for fourteen (14) RTACs that will automatically configure themselves for the switchboard they are connected to.
• Develop logic to detect and flag configuration or connection errors.
• Operational procedure to load a factory new SEL-RTAC into service.
3. Design Review
• SEL ES will support up to two (2) four-hour meetings of preliminary design review including slides and document review with remote participation by the sponsors and/or system interfaces engineering teams for the customer.
• SEL ES will support up to two (2) four-hour meetings of critical design review including slides and document review with remote participation by the sponsors and/or system interfaces engineering teams for the customer.
• Travel is not anticipated, and as such, no travel expenses are included in this item.
4. RTAC Factory Acceptance Test
• SEL-RTAC testing shall be performed as a unit test for acceptance.
• SEL-311N protective relays at latest official revision will be connected to the RTAC for unit testing.
3.2.3 The contractor shall provide the RTAC Programing Software source code, executables files, and loading procedures required to install onboard a ship.
3.3 The contractor shall provide non-recurring engineering associated with LHD/A Class SCD 25536 Electric Plant Switchboard Communications for the RTAC.
3.3.1 The contractor shall develop SEL RTAC program to be connected with up to 5 SEL- 311Ns. For commonality of the interface definitions address space shall be common among all switchboard interfaces. The RTAC shall be configured to auto detect the switchboard it is located within, where SEL-311N data is used to identify then the SEL RTAC shall use all relay identifiers to confirm the location to prevent misconfiguration due to relay faults or maintenance.
3.3.2 The contractor shall develop Software to meet all requirements identified in the government furnished information provided in section 9 of this statement of work including the following:
The List of Maintenance Tasks that shall be permitted are as follows, Load an application to the EPMCS controller, in order to detect available controllers the application may use beacons to announce itself.
Retrieve periodic backups of files from the EPMCS controller Send and receive variable files to the control Read/Write live data updates with one or more EPMCS Controllers, up to 6.
Windows diagnostics shall be available to verify connectivitiy with the ping command, at a minimum.
The collection of SER logs and Event Logs from the Relays via the RTAC using an external laptop connected at the Primary or Secondary host EPMCS controller.
Configuration of a Replacement RTAC The acceptance of time synchronization from a Primary and Secondary EPMCS HMI The indication of broken or inactive network links.
3.3.3 The contractor shall provide the RTAC Programing to define all requirements for SEL-2032 Communications Processor to SEL Real-Time Automation Controller conversion and describe strategies used to meet the objective.
3.3.4 The contractor shall provide the RTAC communication parameters including serial and Ethernet based devices, communication protocol maps and loading procedures required to install onboard a ship.
4.0 DATA REQUIREMENTS
4.1 All products, documentation, data files and masters for products/reports etc. developed to support the requirements established in this SOW are the property of the Government and shall be turned over to NSWCPD.
4.1.1 Deliverables shall be developed and submitted in accordance with the Contract Data Requirements Lists (CDRLs) and the specific requirements of each Contract.
4.1.2 Both electronic and hard copy deliverables may be required.
4.1.3 Work products shall be submitted in media (e.g., DOC, XLS, PDF, etc.) as mutually agreed upon prior to submission.
4.1.3.5 Software Development, Documentation, and QA including; POAM (CDRL A001), Traceability Matrix (CDRL A002), Preliminary Design Review (CDRL A003) and Critical Design Review Brief (CDRL A004).
5.0 SECURITY REQUIREMENTS
5.1 SECURITY TRAINING. The Contractor is responsible for completing all required Government mandated training to maintain 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) (DoDM 5220.22), 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 by the Vetting Risk Operations Center (VROC). An interim clearance is granted by VROC and recorded in the Defense Information System for Security (DISS). An open or closed investigation with a favorable adjudication is required prior to issuance of a badge providing access to NSWCPD buildings. Furthermore, if the Navy Central Adjudication Facility, have 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 are 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.1.2 Within 30 days after contract award, the contractor shall submit a list of all contractor personnel, including subcontractor employees, who will have access to DON information systems and/or work on-site at one of the NSWCPD sites to the appointed Contracting Officer Representative (COR) via email. The contractor shall provide each employee's first name, last name, contract number, the NSWCPD technical code, work location, whether or not the employee has a CAC and or Standard Access Control Badge (SACB), the systems the employee can access (i.e., NMCI, RDT&E), and the name of the Contractor's local point of contact, phone number and email address. Throughout the period of performance of the contract, the Contractor shall immediately provide any updated information to the COR when any Contractor personnel changes occur including substitutions or departures.
5.2 ON SITE WORK.
N/A, work will occur at contractor’s facility
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. The Contractor may not impose OPSEC requirements on its subcontractors unless NSWCPD approves the OPSEC requirements. 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.5 RECEIPT, STORAGE, AND GENERATION OF CONTROLLED UNCLASSIFIED
INFORMATION (CUI) All 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 NIST SP-800-171, or subsequent revisions. All transmissions to personal email accounts (AOL, Yahoo, Hotmail, Comcast, etc.) and 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; 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.
6.0 PLACE OF PERFORMANCE
6.1 The primary place of performance for this Contract shall be at the Contractor’s facilities in Charlotte North Carolina.
7.0 TRAVEL
7.1 N/A
7.4 Travel Costs
7.4.1 N/A
7.5 OCONUS Contractor Personnel Travel During COVID-19
N/A, OCONUS travel is not anticipated
8.0 GOVERNMENT FURNISHED PROPERTY
There is no government furnished material associated with this Contract.
9.0 GOVERNMENT FURNISHED INFORMATION
9.1 The following documents are to be provided by the government:
EPMCS Requirements - Reference III – RTAC IO Sheet
10.0 PURCHASES
10.1 This contract is being awarded on a firm-fixed price basis to support configuration for (14) SEL 3350 RTACs to concentrate the data from SEL-311 Relays to send to Electrical Plant Machinery Control System (EPCMS) system. The Communication protocol between EPCMS and RTACs shall be Modbus TCP. The contractor shall include in their proposal all costs associated with material necessary to complete all elements of this contract within the established period of performance.
11.0 COUNTERFEIT MATERIAL PREVENTION
Not applicable
12.0 PERSONNEL
Not applicable
13.0 NSWCPD ELECTRONIC COST REPORTING AND FINANCIAL TRACKING
(ECRAFT) SYSTEM
Use of ECRAFT is not applicable.
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 non-significant 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-227-H006 DATA REQUIREMENTS (NAVSEA) (OCT 2018)
The data to be furnished hereunder shall be prepared in accordance with the Contract Data Requirements List, DD Form 1423, Exhibit(s) A001-A004, attached hereto.
(End of Text)
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-246-H003 LIMITATION OF LIABILITY--HIGH VALUE ITEMS (NAVSEA) (OCT 2018)
The following items are subject to the clause of this contract entitled "Limitation of Liability--High Value Items" (FAR 52.246-24 Alternate I):
CLIN
C-247-H001 PERMITS AND RESPONSIBILITIES (NAVSEA) (DEC 2018)
The Contractor shall, without additional expense to the Government, be responsible for obtaining any necessary licenses and permits for complying with any applicable Federal, State, and Municipal laws, codes, and regulations for shipping and transportation including, but not limited to, any movement over public highways of overweight/over dimensional materials.
Section D - Packaging and Marking
D-211-H001 PACKAGING OF DATA (NAVSEA) (FEB 2022)
Data to be delivered by Integrated Digital Environment (IDE) or other electronic media shall be as specified in the contract.
All unclassified data to be shipped shall be prepared for shipment in accordance with best commercial practice.
Classified reports, data, and documentation shall be prepared for shipment in accordance with National Industrial Security Program Operating Manual (NISPOM), 32 CFR Part 117.
D-211-H002 MARKING OF REPORTS (NAVSEA) (OCT 2018)
All reports delivered by the Contractor to the Government under this contract shall prominently show on the cover of the report:
(1) name and business address of the Contractor
(2) contract number
(3) sponsor:
(Name of Individual Sponsor)
(Name of Requiring Activity)
(City and State)
Section E - Inspection and Acceptance
INSPECTION AND ACCEPTANCE TERMS
Supplies/services will be inspected/accepted at:
CLIN INSPECT AT INSPECT BY ACCEPT AT ACCEPT BY
0001 Destination Government Destination Government
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-H014 INSPECTION AND ACCEPTANCE OF ENGINEERING SERVICES (NAVSEA) (OCT 2018)
Item(s) 0001 - Inspection and acceptance shall be made by the Contracting Officer’s Representative (COR) or a designated representative of the Government.
Section F - Deliveries or Performance
DELIVERY INFORMATION
CLIN DELIVERY DATE QUANTITY SHIP TO ADDRESS DODAAC /
CAGE
0001 POP 17-MAY-2023 TO
17-MAY-2024
N/A NAVAL SURFACE WARFARE CENTER
PHILA
JOSEPH EVERLY
NSWC PHILADELPHIA DIVISION
NSLC DETACHMENT
1601 LANGLEY AVE BLDG 542
PHILADELPHIA PA 19112
(215) 897-7266 FOB: Destination
N64498
CLAUSES INCORPORATED BY REFERENCE
52.242-15 Stop-Work Order AUG 1989
F-247-H001 DELIVERY OF DATA (NAVSEA) (OCT 2018)
All data to be furnished under this contract shall be delivered prepaid to the destination(s) and at the time(s) specified on the Contract Data Requirements List(s), DD Form 1423.
Section G - Contract Administration Data
252.232-7006 WIDE AREA WORKFLOW PAYMENT INSTRUCTIONS (JAN 2023)
(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.
(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.
(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*
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) ____
Service Acceptor (DoDAAC) ____
Accept at Other DoDAAC ____
LPO DoDAAC ____
DCAA Auditor DoDAAC ____
Other DoDAAC(s) ____
(**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) 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.
Kimberly Villano Kimberly.Villano@navy.mil 215‐897‐2433
(1) The Contractor may obtain clarification regarding invoicing in WAWF from the following contracting activity’s WAWF point of contact.
Byron J. Roth
215-897-1121 byron.j.roth.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
Contract/Order Payment Clause
Type of Payment Request
Su pp ly
Se rv ic e
C on st ru ct io n
Payment Office 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
Cost Voucher X X N/A Line item specific proration. If there is more than one ACRN within a deliverable line or deliverable subline item, the funds will be allocated in the same proportion as the amount of funding currently unliquidated for each ACRN on the deliverable line or deliverable subline item for which payment is requested.
52.232-1, Payments Navy Shipbuilding Invoice (Fixed Price)
X N/A N/A Line Item specific by fiscal year. If there is more than one ACRN within a deliverable line or deliverable subline item, the funds will be allocated using the oldest funds. In the event of a deliverable line or deliverable subline item with two ACRNs with the same fiscal year, those amounts will be prorated to the available unliquidated funds for that year.
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
Invoice X X N/A Line Item Specific proration. If there is more than one ACRN within a deliverable line or deliverable subline item, the funds will be allocated in the same proportion as the amount of funding currently unliquidated for each ACRN on the deliverable line or deliverable subline item for which payment is requested.
Contract/Order Payment Clause
Type of Payment Request
Su pp ly
Se rv ic e
C on st ru ct io n
Payment Office Allocation Method
52.232-5, Payments Under Fixed-Price Construction Contracts
Construction Payment Invoice
N/A N/A X Line Item specific by fiscal year. If there is more than one ACRN within a deliverable line or deliverable subline item, the funds will be allocated using the oldest funds. In the event of a deliverable line or deliverable subline item with two ACRNs with the same fiscal year, those amounts will be prorated to the available unliquidated funds for that year.
52.232-16, Progress Payments
Progress Payment*
X X N/A Contract-wide proration. Funds shall be allocated in the same proportion as the amount of funding currently unliquidated for each ACRN. Progress Payments are considered contract level financing, and the “contract price” shall reflect the fixed price portion of the contract per FAR 32.501-3.
52.232-29, Terms for Financing of Purchases of Commercial Items;
52.232-30, Installment Payments for Commercial Items
Commercial Item Financing*
X X N/A Specified in approved payment. The contracting officer shall specify the amount to be paid and the account(s) to be charged for each payment approval in accordance with FAR 32.207(b)(2) and 32.1007(b)(2).
52.232-32, Performance- Based Payments
Performance- Based Payments*
X X N/A Specified in approved payment. The contracting officer shall specify the amount to be paid and the account(s) to be charged for each payment approval in accordance with FAR 32.207(b)(2) and 32.1007(b)(2).
252.232-7002, Progress Payments for Foreign Military Sales Acquisitions
Progress Payment*
X X N/A Allocate costs among line items and countries in a manner acceptable to the Administrative Contracting Officer.
*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):
Section (a) does not apply. This entire contract is fixed price.
G-232-H005 SUPPLEMENTAL INSTRUCTIONS REGARDING INVOICING (NAVSEA) (JAN 2019)
(a) For other than firm fixed priced contract line item numbers (CLINs), the Contractor agrees to segregate costs incurred under this contract/task order (TO), as applicable, at the lowest level of performance, either at the sub line item number (SLIN) or CLIN level, rather than at the total contract/TO level, and to submit invoices reflecting costs incurred at that level. Supporting documentation in Wide Area Workflow (WAWF) for invoices shall include summaries of work charged during the period covered as well as overall cumulative summaries by individual labor categories, rates, and hours (both straight time and overtime) invoiced; as well as, a cost breakdown of other direct costs (ODCs), materials, and travel, by technical instruction (TI), SLIN, or CLIN level. For other than firm fixed price subcontracts, subcontractors are also required to provide labor categories, rates, and hours (both straight time and overtime) invoiced; as well as, a cost breakdown of ODCs, materials, and travel invoiced. Supporting documentation may be encrypted before submission to the prime contractor for WAWF invoice submittal.
Subcontractors may email encryption code information directly to the Contracting Officer and Contracting Officer Representative (COR). Should the subcontractor lack encryption capability, the subcontractor may also email detailed supporting cost information directly to the Contracting Officer and COR; or other method as agreed to by the Contracting Officer.
(b) Contractors submitting payment requests and receiving reports to WAWF using either Electronic Data Interchange (EDI) or Secure File Transfer Protocol (SFTP) shall separately send an email notification to the COR and Contracting Officer on the same date they submit the invoice in WAWF. No payments shall be due if the contractor does not provide the COR and Contracting Officer email notification as required herein.
G-242-H001 GOVERNMENT CONTRACT ADMINISTRATION POINTS-OF-CONTACT AND
RESPONSIBILITIES (NAVSEA) (OCT 2018)
(a) The Government reserves the right to administratively substitute any of the points of contact listed below at any time.
(b) The contracting officer is the only person authorized to change this contract or orders issued thereunder. The Contractor shall not comply with any order, direction or request of Government personnel
- that would constitute a change - unless it is issued in writing and signed by the Contracting Officer or is pursuant to specific authority otherwise included as part of this contract. If, in the opinion of the contractor, an effort outside the existing scope of this contract is requested, the contractor shall promptly comply with the Notification of Changes clause of this contract.
(c) The points of contact are as follows:
(i) The Procuring Contracting Officer (PCO) is:
(ii) The Contract Specialist is:
(iii) The Administrative Contracting Officer (ACO) is:
(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:
(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:
(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:
(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:
(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:
(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:
(k) The Contractor's point of contact for performance under this contract is:
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 H - Special Contract Requirements
H-209-H003 REQUIRED DISCLOSURE OF ORGANIZATIONAL CONFLICT OF INTEREST (NAVSEA)
(NOV 2022)
(a) "Organizational Conflict of Interest" means that because of other activities or relationships with other persons, a person is unable or potentially unable to render impartial assistance or advice to the Government, or the person's objectivity in performing the contract work is or might be otherwise impaired, or a person has an unfair competitive advantage. "Person" as used herein includes Corporations, Partnerships, Joint Ventures, and other business enterprises.
(b) The Contractor warrants that to the best of its knowledge and belief, and except as otherwise set forth in the contract, at the time of execution of this contract the Contractor does not have any organizational conflict of interest(s) as defined in paragraph (a).
(c) The Contractor agrees that, if after award, it discovers an actual or potential organizational conflict of interest, it shall make immediate and full disclosure in writing to the Contracting Officer. The notification shall include a description of the actual or potential organizational conflict of interest, a description of the action which the Contractor has taken or proposes to take to avoid, mitigate, or neutralize the conflict, and any other relevant information that would assist the Contracting Officer in making a determination on this matter. Notwithstanding this notification, the Government may terminate the contract for the convenience of the Government if determined to be in the best interest of the Government.
(d) Notwithstanding paragraph (c) above, if the Contractor was aware, or should have been aware, of an organizational conflict of interest prior to the award of this contract or becomes, or should become, aware of an organizational conflict of interest after award of this contract and does not make an immediate and full disclosure in writing to the Contracting Officer, the Government may terminate this contract for default.
(e) If the Contractor fails to take action required by this requirement, or required by the Contracting Officer upon receipt of the Contractor’s disclosure required by paragraph (c), the Government may terminate this contract for default.
(f) The Contracting Officer's decision as to the existence or nonexistence of an actual or potential organizational conflict of interest shall be final.
(g) The Contractor shall promptly notify the Contracting Officer, in writing, if it has been tasked to evaluate or advise the Government concerning its own products or activities, those of its subcontractors, those of one of its prime contractors (to which the contractor is a subcontractor), or those of a competitor in order to ensure proper safeguards exist to guarantee objectivity and to protect the Government's interest.
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .