SF 1449 - N6449825Q0026.pdf
PDF 2 MB Posted
- Solicitation number
- N6449825Q0026
About this file
This is a Standard Form 1449 (SF 1449) solicitation/contract for the procurement of 10 Rockwell Automation RS Studio 5000 Professional Edition software licenses for the Naval Surface Warfare Center Philadelphia Division (NSWCPD). The solicitation, numbered N6449825Q0026, is set aside for Women-Owned Small Business (WOSB) and is being conducted using simplified acquisition procedures. The procurement is specifically for supporting the In-Service Engineering Agent (ISEA) maintenance and troubleshooting efforts for Hull & Deck Machinery Systems Maintenance Laptop Ships (HDMS-ML-SHIPS) and the Machinery Control Consolidated Maintenance System (MCCMS).
The solicitation specifies a delivery date of 31 October 2025, with quotes due by 2:00 PM on 7 August 2025. The contract will be awarded on a firm-fixed-price basis, with the contract to be administered by the NSWC Philadelphia Division located in Philadelphia, Pennsylvania. The North American Industry Classification System (NAICS) code is 334611, with a size standard of 500 employees. Offerors must submit pricing information, including recent sales data, catalog prices, and a statement that the proposed prices do not exceed prices charged to the offeror's most favored customer for similar items under comparable conditions.
View the file
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
WOMEN-OWNED SMALL
BUSINESS (WOSB)
SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL PRODUCTS AND COMMERCIAL SERVICES
1. REQUISITION NUMBER PAGE 1 OF
2. CONTRACT NUMBER 3. AWARD/EFFECTIVE
DATE
4. ORDER NUMBER 5. SOLICITATION NUMBER 6. SOLICITATION ISSUE
DATE
7. FOR SOLICITATION
INFORMATION CALL:
a. NAME b. TELEPHONE NUMBER (No collect calls)
8. OFFER DUE DATE/
LOCAL TIME
9. ISSUED BY
13b. RATING
14. METHOD OF SOLICITATION
CODE
15. DELIVER TO 16. ADMINISTERED BY CODE
18a. PAYMENT WILL BE MADE BY CODE17a. CONTRACTOR/
OFFEROR
CODE
FACILITY
CODE
CODE
TELEPHONE NUMBER
17b. CHECK IF REMITTANCE IS DIFFERENT AND PUT SUCH ADDRESS IN
OFFER
18b. SUBMIT INVOICES TO ADDRESS SHOWN IN BLOCK 18a UNLESS BLOCK
BELOW IS CHECKED
REQUEST
FOR QUOTE
(RFQ)
INVITATION
FOR BID
(IFB)
REQUEST
FOR
PROPOSAL
(RFP)
SEE ADDENDUM
19.
ITEM NUMBER
20.
SCHEDULE OF SUPPLIES/SERVICES
21.
QUANTITY
22.
UNIT
23.
UNIT PRICE
24.
AMOUNT
(Use Reverse and/or Attach Additional Sheets as Necessary)
25. ACCOUNTING AND APPROPRIATION DATA 26. TOTAL AWARD AMOUNT (For Government Use Only)
28. CONTRACTOR IS REQUIRED TO SIGN THIS DOCUMENT AND RETURN
COPIES TO ISSUING OFFICE. CONTRACTOR AGREES TO FURNISH
AND DELIVER ALL ITEMS SET FORTH OR OTHERWISE IDENTIFIED ABOVE AND
ON ANY ADDITIONAL SHEETS SUBJECT TO THE TERMS AND CONDITIONS
SPECIFIED
29. AWARD OF CONTRACT: REFERENCE OFFER
DATED . . YOUR OFFER ON SOLICITATION
(BLOCK 5), INCLUDING ANY ADDITIONS OR CHANGES WHICH ARE
SET FORTH HEREIN, IS ACCEPTED AS TO ITEMS:
30a. SIGNATURE OF OFFEROR/CONTRACTOR
30b. NAME AND TITLE OF SIGNER (Type or print) 30c. DATE SIGNED
31a. UNITED STATES OF AMERICA (SIGNATURE OF CONTRACTING OFFICER)
31b. NAME OF CONTRACTING OFFICER (Type or print) 31c. DATE SIGNED
AUTHORIZED FOR LOCAL REPRODUCTION
PREVIOUS EDITION IS NOT USABLE
STANDARD FORM 1449 (REV. 11/2021)
Prescribed by GSA - FAR (48 CFR) 53.212
10. THIS ACQUISITION IS UNRESTRICTED OR
NORTH AMERICAN
INDUSTRY CLASSIFICATION
STANDARD (NAICS):
SIZE STANDARD:
13a. THIS CONTRACT IS A
RATED ORDER UNDER
THE DEFENSE PRIORITIES
AND ALLOCATIONS
SYSTEM - DPAS (15 CFR 700)
SET ASIDE: % FOR:
11. DELIVERY FOR FREE ON
BOARD (FOB) DESTINATION
UNLESS BLOCK IS MARKED
SEE SCHEDULE
12. DISCOUNT TERMS
ARE ARE NOT ATTACHED
ARE ARE NOT ATTACHED
27a. SOLICITATION INCORPORATES BY REFERENCE (FEDERAL ACQUISITION REGULATION) FAR 52.212-1, 52.212-4. FAR 52.212-3
AND 52.212-5 ARE ATTACHED. ADDENDA
27b. CONTRACT/PURCHASE ORDER INCORPORATES BY REFERENCE FAR 52.212-4. FAR 52.212-5 IS ATTACHED. ADDENDA
8(A)
ECONOMICALLY
DISADVANTAGED
WOMEN-OWNED SMALL
BUSINESS (EDWOSB)
SERVICE-DISABLED
VETERAN-OWNED
SMALL BUSINESS
(SDVOSB)
HUBZONE SMALL
BUSINESS
SMALL BUSINESS
NOTE: OFFEROR TO COMPLETE BLOCKS 12, 17, 23, 24, AND 30.
Section A - Solicitation/Contract Form
Studio 5000 Professional Edition
Product Service Code: 7A21
N6449825Q0026
Section B - Supplies or Services & Prices or Costs
Additional Information/Notes
Item Supplies/Service Quantity Unit Unit Price Amount
RSLOGIX 5000 PROFESSIONAL EDITION, ENGLI
NOTE: The requirements in DFARS 252.211-7003, Item Identification and Valuation, are applicable for this line item. The contractor shall provide DoD unique identification or a DoD recognized unique identification equivalent.
Internal Number: 1018366148 Pricing Arrangement: Firm Fixed Price PR Number: NOPR PR Line Item Number: 0001
10 Each
Section C - Description/Specifications/Statement of Work
Statement of Work (SOW) for
Code 433 Rockwell RS Studio 5000 Professional Software Procurement
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 433, which is responsible for Launch and Recovery handling Systems and Crane 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 are 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 with 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 Launch, Recovery and Hydraulic Systems Branch (Code 433) of the Naval Surface Warfare Center Philadelphia Division (NSWCPD) is a Department of Defense (DoD) entity responsible for research and development, test and evaluation, engineering and fleet support for the Navy's ships, submarines, military watercraft and unmanned vehicles. This contract requires the contractor to provide RS Studio 5000 Professional licenses to NSWCPD Code 433 in support of performing In-Service Engineering Agent (ISEA) duties for systems aboard the LCS ship class, including but not limited to Hull & Deck Machinery Systems Maintenance Laptop Ships (HDMS-ML-SHIPS) and the Machinery Control Consolidated Maintenance System (MCCMS).
1.2 SCOPE OF WORK
The contractor shall provide RS Studio 5000 Professional software licenses to be installed in shipboard maintenance laptops used on LCS ship class systems.
2.0 APPLICABLE DOCUMENTS - (not applicable)
3.0. REQUIREMENTS
3.1 Rockwell Automation, the original equipment manufacturer (OEM) of the RS Studio 5000 Professional software licenses, shall provide ten (10) of these software licenses to NSWCPD in support of ISEA maintenance and troubleshooting efforts for the Hull & Deck Machinery Systems Maintenance Laptop Ships (HDMS-ML-SHIPS) and Machinery Control Consolidated Maintenance System (MCCMS).
3.2 Manufacturing Phase-Out or Discontinuation of Production, Diminishing Sources, and Obsolete Materials or Components - (Not Applicable)
3.3 Diminishing Manufacturing Sources and Material Shortages Management (DMSMS) Contract Requirements - (Not Applicable)
3.4 Parts Obsolescence - (Not Applicable)
4.0 DATA REQUIREMENTS - (Not Applicable)
5.0 SECURITY REQUIREMENTS
5.1 SECURITY TRAINING - (Not Applicable)
5.2 ON SITE WORK - (Not Applicable)
5.3 DD254 REQUIREMENT - (Not Applicable)
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 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 - (Not Applicable)
6.0 PLACE OF PERFORMANCE - (Not Applicable)
7.0 TRAVEL - (Not Applicable)
8.0 GOVERNMENT FURNISHED PROPERTY - (Not Applicable)
9.0 GOVERNMENT FURNISHED INFORMATION - (Not Applicable)
10.0 PURCHASES - (Not Applicable)
11.0 COUNTERFEIT MATERIAL PREVENTION - (Not Applicable)
12.0 PERSONNEL - (Not Applicable)
Requirements Studio 5000 Professional Edition
Additional Regulation or Supplemental Clauses Incorporated by Full 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-212-W002 COMMERCIAL SUPPLIER AGREEMENTS (NAVSEA) (MAR 2019) (Mar 2019)
(a) Commercial Supplier Agreement means End User License Agreement (EULA), Terms of Service (TOS), or similar legal instrument or agreement.
(b) Any Commercial Supplier Agreement must be provided in full text as part of a quote or offer without hyperlinks.
(c) The contract/order Schedule and Federal Acquisition Regulation (FAR) 52.212-4, Contract Terms and Conditions-- Commercial Items, shall take precedence over any conflicting provisions in a Commercial Supplier Agreement.
(d) If any requirement in the Commercial Supplier Agreement conflicts with Federal law or regulations (see FAR 12.212(a)), the following shall apply:
(i) Any such requirement is unenforceable against the Government.
(ii) Neither the Government nor any Government authorized end user shall be deemed to have agreed to such requirement by virtue of it appearing in the Commercial Supplier Agreement. If the Commercial Supplier Agreement is invoked through an "I agree" click box or other comparable mechanism (e.g., "click-wrap" or "browse-wrap" agreements), execution does not bind the Government or any Government authorized end user to such requirement.
(iii) Any such requirement is deemed to be stricken from the Commercial Supplier Agreement.
(e) Automatic renewals. License Agreements will expire at end of the term identified in the Purchase Order /Contract. Automatic renewals are not permitted and any such provision is void.
(f) Changes to the Commercial Supplier Agreement. Unilateral changes of the Commercial Supplier Agreement are impermissible and any requirement authorizing such changes is unenforceable. Changes must be in writing and executed by both parties to be effective.
(g) Third Part License (Embedded Software).
(i) The Contractor agrees that it has obtained all necessary licenses for the Government for any third party materials (including without limitation all Open Source licenses) provided within the product.
(ii) Contractor agrees that it complies with and shall continue to comply with all of its obligations under Third Party Licenses (including without limitation all Open Source licenses) associated with any third party materials provided within each product.
(iii) To the extent that the Government's use of the software products licensed herein is in compliance with the Contractor's Commercial Supplier Agreement, the Government's use will also be in compliance with any Third Party Licenses.
(h) Audits. In lieu of any audit provisions in the Commercial Supplier Agreement, the Government agrees that, no more than once every twelve (12) months or within a reasonable time after a transfer, the Contractor shall, upon reasonable notice, have the right to require that the Government conduct an internal audit to ascertain and verify the number of licenses in use and to verify that the Government's use of the product is in conformity with this Agreement. The Government is not required to use any tools provided by the Contractor to conduct the audit and shall not be required to pay for any tools provided by the Contractor to conduct the audit. The results of any such audit shall be kept confidential.
If verification discloses that the Government's use is not in conformity with this Agreement, the Government agrees to resolve any noncompliance by either removing or correcting the unlicensed installation and use of the software identified by the audit as not in conformity with this Agreement.
(i) Confidentiality. Commercial Supplier Agreements' terms and the final contract pricing may not be deemed confidential. Other marked confidential information will be appropriately guarded.
(j) Assignment. The Government shall have the right, without the prior written consent of the Contractor or its authorized resellers, to assign, reassign, or transfer software licenses among Government employees or the Government's rights in the Contractor's product to any governmental organization that is managed, operated, or controlled by the Government.
Such authorization includes sublicensing, and assignment or transfer among or between authorized users. In the event authorized users are reorganized or restructured such that their responsibilities and operations are transferred to another government agency, the agency shall have the right to assign the affected program licenses to a successor agency. The licensed agency and the successor agency agree to be bound to the Commercial Supplier Agreement as modified. The transferee shall be bound by the license metrics and limitations in this license. Government shall complete any documentation required by the Contractor to facilitate the transfer of this license, and continuation of support shall be the responsibility of the transferee.
For the avoidance of doubt, any assignment or transfer of licenses of the Contractor's products is also subject to all other terms of the Commercial Supplier Agreement, as well as the Contractor's policies governing product dependencies and version compatibility. Reassignment does not require that the license be under maintenance or support in order to execute a transfer.
(k) Litigation. Any requirement insisting that the commercial supplier or licensor control any litigation arising from the government's use of the contractor's supplies or services is deleted and unenforceable.
(l) Equitable Remedies. Equitable remedies, injunctive relief, and binding arbitration requirements shall not be enforced unless explicitly authorized by agency guidance or statute.
(m) Venue. Any claim or dispute shall be resolved under the Contract Disputes Act and FAR 52.233-1. The forum for resolution of disputes and applicable statutes of limitation shall be governed by federal law.
(n) Applicable law. In accordance with FAR 52.233-4, United States law shall apply to resolve any claim of breach of this contract and such actions shall be handled in the applicable Federal court of jurisdiction.
(End of Text)
C-227-H010 COMPUTER SOFTWARE AND COMPUTER DATA BASES DELIVERED TO OR
RECEIVED FROM THE GOVERNMENT (NAVSEA) (JAN 2019)
(Jan 2019)
(a) The Contractor agrees to test for viruses, malware, Trojan Horses, and other security threats such as those listed in NIST Special Publication 800-12 Rev 1, An Introduction to Computer Security, The NIST Handbook, Chapter 4, in all computer software and computer data bases (as defined in the clause entitled "Rights In Noncommercial Computer Software and Noncommercial Computer Software Documentation" (DFARS 252.227-7014)), before delivery of that computer software or computer data base in whatever media and on whatever system the computer software or data base is delivered whether delivered separately or imbedded within delivered equipment. The Contractor warrants that when delivered any such computer software and computer data base shall be free of viruses, malware, Trojan Horses, and other security threats such as those listed in NIST Special Publication 800-12 Rev 1.
(b) The Contractor agrees that prior to use under this contract, it shall test any computer software and computer data base received from the Government for viruses, malware, Trojan Horses, and other security threats listed in NIST Special Publication 800-12 Rev 1, An Introduction to Computer Security, The NIST Handbook, Chapter 4.
(c) Any license agreement governing the use of any computer software or computer software documentation delivered to the Government as a result of this contract must be paid-up, irrevocable, world-wide, royalty-free, perpetual and flexible (user licenses transferable among Government employees and personnel under Government contract).
(d) The Contractor shall not include or permit to be included any routine to enable the contractor or its subcontractor(s) or vendor(s) to disable the computer software or computer data base after delivery to the Government.
(e) No copy protection devices or systems shall be used in any computer software or computer data base delivered under this contract with unlimited or Government purpose rights (as defined in DFARS 252.227-7013 and 252.227-7014) to restrict or limit the Government from making copies.
(f) It is agreed that, to the extent that any technical or other data is computer software by virtue of its delivery in digital form, the Government shall be licensed to use that digital-form data with exactly the same rights and limitations as if the data had been delivered as hard copy.
(g) Any limited rights legends or other allowed legends placed by a Contractor on technical data or other data delivered in digital form shall be digitally included on the same media as the digital-form data and must be associated with the corresponding digital-form technical data to which the legend(s) apply to the extent possible. Such legends shall also be placed in human-readable form on a visible surface of the media carrying the digital-form data as delivered, to the extent possible.
(End of Text)
C-227-H007 SOFTWARE DEVELOPMENT REQUIREMENTS (NAVSEA) (OCT 2018) (Oct 2018)
(a) The contractor shall define a general Software Development Plan (SDP) appropriate for the computer software effort to be performed under this contract. The SDP shall be delivered to the Government for concurrence under CDRL and shall not vary significantly from that proposed to the Government for evaluation for award. The contractor shall follow the Government concurred with SDP for all computer software to be developed or maintained under this effort. Any changes, modifications, additions or substitutions to the SDP also require prior Government concurrence.
(b) The SDP shall, at a minimum:
(1) Define the contractor's proposed life cycle model and the processes used as a part of that model. In this context, the term "life cycle model" is as defined in IEEE Std. 12207:2017;
(2) Contain the information defined by ISO/IEC/IEEE 15289:2017, section 7.3 "Plan - generic content" and Table 2 "Mapping of ISO/IEC 12207:2008 (IEEE Std. 12207:2008) Clauses to Information Items for Each Software Life Cycle Process." In all cases, the level of detail shall be sufficient to define all software development processes, activities, and tasks to be conducted for this contract;
(3) Identify the specific standards, methods, tools, actions, strategies, and responsibilities associated with development and qualification;
(4) Document all processes applicable to the system to be acquired, including the Primary, Supporting, and Organizational life cycle processes as defined by IEEE Std. 12207:2017 as appropriate. Such processes shall be equivalent to those articulated by CMMI(r);
(5) Adhere to the characteristics defined in ISO/IEC/IEEE 15289:2017 section 6.1 "Life-cycle data characteristics," as appropriate;
(6) Be in accordance with the framework defined in IEEE Std. 12207:2017, including, but not limited to, defining the processes, the activities to be performed as a part of the processes, the tasks which support the activities, and the techniques and tools to be used to perform the tasks;
(7) Contain a level of information sufficient to allow the use of the SDP as the full guidance for the developers. In accordance with ISO/IEC/IEEE 15289:2017 Section 7.3, such information shall at a minimum contain, specific standards, methods, tools, actions, reuse strategy, and responsibility associated with the development and qualification of all requirements, including safety and security.
(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-239-W001 ELECTRONIC AND INFORMATION TECHNOLOGY (EIT) ACCESSIBILITY
STANDARDS/SECTION 508 COMPLIANCE (NAVSEA) (OCT 2018)
(Oct 2018)
(a) Requirements for accessibility based on Section 508 of the Rehabilitation Act of 1973 (29 U.S.C. 794d) are determined to be relevant for product(s)/service(s) procured under this solicitation.
(b) Each Electronic and Information Technology (EIT) item or service provided under this contract shall comply with the EIT Accessibility Standards listed below:
__ __ 36 C.F.R. (S) 1194.21 - Software applications and operating systemsX
_____ 36 C.F.R. (S) 1194.22 - Web-based and internet information and applications
_____ 36 C.F.R. (S) 1194.23 - Telecommunications products
_____ 36 C.F.R. (S) 1194.24 - Video and multimedia products
_____ 36 C.F.R. (S) 1194.25 - Self-contained, closed products
_____ 36 C.F.R. (S) 1194.26 - Desktop and portable computers
_____ 36 C.F.R. (S) 1194.31 - Functional Performance Criteria
_____ 36 C.F.R. (S) 1194.41 - Information, Documentation, and Support
(c) For more information on Voluntary Product Accessibility Template (VPAT) and Government Product/Service Accessibility Template (GPAT) please refer to: http://www.buyaccessible.gov/ or http://www.section508.gov/content/sell/vpat.
(d) The Contractor shall comply with the VPAT or GPAT document submitted. If the Contracting Officer determines that any item or service delivered under this contract does not comply with the EIT Accessibility Standards, the Contracting Officer will notify the Contractor in writing accordingly. If the Contractor fails to promptly correct or replace the nonconforming products or services with conforming products or services within the delivery schedule contained in the contract, the Government will have the rights and remedies contained in the basic contract.
(End of Text)
Section D - Packaging and Marking
Additional Regulation or Supplemental Clauses Incorporated by Full Text
D-246-H002 WARRANTY NOTIFICATION FOR ITEM(S) —BASIC (NAVSEA) (OCT 2018) (Oct 2018)
The Contractor shall apply a permanent warranty notification stamping or marking on each warranted deliverable end item and its container. The notification shall be placed in close proximity to other required stamping or markings so as to be easily readable by personnel. The warranty notification shall read:
THIS ITEM WARRANTED UNDER CONTRACT TO CONFORM TO DESIGN,
MANUFACTURING, AND PERFORMANCE REQUIREMENTS AND BE FREE FROM DEFECTS IN
MATERIAL AND WORKMANSHIP FOR FROM DATE OF ACCEPTANCE. IF
ITEM IS DEFECTIVE NOTIFY AND PCO.
(End of Text)
D-247-H002 PACKAGING OF SUPPLIES—BASIC (NAVSEA) (DEC 2020) (Dec 2020)
Item(s) The supplies furnished hereunder shall be packaged in accordance with ASTM-D-3951-18, Standard Practice for 0001 Commercial Packing.
(End of Text)
Section E - Inspection and Acceptance
Additional Regulation or Supplemental Clauses Incorporated by Full Text
E-246-H023 QUALITY REQUIREMENT FOR SOFTWARE DEVELOPMENT OR PRODUCTION
(NAVSEA) (JAN 2019)
(Jan 2019)
The contractor's software quality program shall be an integral part of the overall Quality Management System. Software quality program controls shall be applicable to all project software that is developed, maintained, or modified within the following categories:
(a) All deliverable software
(b) All deliverable software that is included as part of deliverable hardware or firmware.
(c) Non deliverable software (commercially available or user-developed) used for development, fabrication, testing, or acceptance of deliverable software or hardware (includes automated fabrication, test, and inspection/acceptance equipment software and software design, test, and inspection tools).
(d) Commercially available, reusable, or Government software designated as part of a deliverable item.
(End of Text)
Overall Contract Inspection/Acceptance Locations
Inspection and Acceptance Location
Both Destination Instructions: Items will be inspected and accepted upon the arrival at the Government facility
DoDAAC: N64498 CountryCode: USA
NSWC PHILADELPHIA DIV
1601 LANGLEY AVE BUILDING 542, PHILADELPHIA PA 19112
PHILADELPHIA, PA 19112
UNITED STATES
Anthony Tirri, Technical Point Of Contact Email: Anthony.w.tirri.civ@us.navy.mil Telephone: (267) 827-0027
Section F - Deliveries or Performance
Contractor Destination
Line Item Delivery Schedule Quantity Address and POC Special Handling/Notes
Delivery Requested By Delivery Date 31 Oct
10 Each Ship To DoDAAC: N64498 CountryCode: USA
NSWC PHILADELPHIA DIV
1601 LANGLEY AVE BUILDING 542,
PHILADELPHIA PA 19112
PHILADELPHIA, PA 19112
UNITED STATES
Anthony Tirri, Technical Point of Contact Email: Anthony.w.tirri.civ@us.navy.mil Telephone: (267) 827-0027
FoB Details Contractor Destination
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 WAWF payment instructions.
in 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.
COMBO
(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.
(Contracting Officer: Insert either "Invoice 2in1" or the applicable invoice and receiving report document type(s) for fixed price line items 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 Document routing.
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 ____
Service Approver (DoDAAC) ____
Service Acceptor (DoDAAC) ____
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.
(1) The Contractor may obtain clarification regarding invoicing in WAWF from the following contracting activity's WAWF point of contact.
_Caitlin Tamas caitlin.i.tamase.civ@us.navy.mil (215) 756-2962 Dimple Amleshvarwala-thaker, dimple.k.amleshvarwala-thaker.civ, (215) 897-
(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-H002 H002 PAYMENT INSTRUCTIONS (NAVSEA) (FEB 2024) (Feb 2024)
Payment office allocation methods can be found in the table at DFARS PGI 204.7108(b)(2) (https://www.acq.osd.mil/dpap /dars/pgi/pgi_htm/current/PGI204_71.htm#payment_instructions).
(End of 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. If, in the opinion of the contractor, an effort outside the existing scope of this contract is requested, the contractor shall promptly comply with the Notification of Changes clause of this contract.
(c) The points of contact are as follows:
(i) The Procuring Contracting Officer (PCO) is:
Name: Jillian Randazzo Email: jillian.randazzo.civ@us.navy.mil Contracting Officer Naval Sea Systems Command (NAVSEA) Naval Surface Warfare Center Philadelphia Division 5001 South Broad Street Philadelphia, PA 19112-5083 Cell: 267-990-6035
(ii) The Contract Specialist is:
William H. Morton III Philadelphia, PA 19112 5001 South Broad Street (Cell phone) 484-358-2255 Naval Surface Warfare Center Philadelphia Division Naval Sea Systems Command (NAVSEA) Contract Specialist william.h.morton39.civ@us.navy.mil
(iii) The Administrative Contracting Officer (ACO)is:
Name: [ * ] Address:
[ *Street ] [ *City, State, Zip ] Phone: (Area Code) xxx- [xxxx] E-mail: [ * ]
(d) The Contracting Officer's Representative (COR) is the contracting officer's appointed representative for technical matters. The COR is not a contracting officer and does not have the authority to direct the accomplishment of effort which is beyond the scope of the contract or to otherwise change any contract requirements. An informational copy of the COR appointment letter, which provides a delineation of COR authority and responsibilities, will be provided upon award of this contract.
The Contracting Officer's Representative (COR) is:
Name: [ * ] Address:
[ *Street ] [ *City, State, Zip ] Phone: (Area Code) xxx- [xxxx] E-mail: [ * ]
(e) The Alternate Contracting Officer's Representative (ACOR) is responsible for COR responsibilities and functions in the event that the COR is unavailable due to leave, illness, or other official business. The ACOR is appointed by the contracting officer; a copy of the ACOR appointment will be provided upon award of this contract.
The Alternate Contracting Officer's Representative (ACOR) is:
Name: [ * ] Address:
[ *City, State, Zip ] Phone: (Area Code) xxx- [xxxx] E-mail: [ * ]
(f) The Technical Point of Contact (TPOC) is the contracting officer's representative for technical matters when a COR is not appointed. The TPOC is responsible for technical issues of contract administration, such as providing all items of Government Furnished Information (GFI), Government Furnished Material (GFM) and Government Furnished Equipment (GFE) if specified in the contract as well as the inspection and acceptance of all contract deliverables.
The Technical Point of Contact (TPOC) is:
Name: [ * ] Address: [ *Street ] [ *City, State, Zip ] Phone: (Area Code) xxx- [xxxx] E-mail: [ * ]
(g) The Alternate Technical Point of Contact (ATPOC) is responsible for TPOC responsibilities and functions in the event that the TPOC is unavailable due to leave, illness, or other official business.
The Alternate Technical Point of Contact (ATPOC) is:
Name: [ * ] Address:
[ *City, State, Zip ] Phone: (Area Code) xxx- [xxxx] E-mail: [ * ]
(h) The Authorized Ordering Person(s) for Per-Call Maintenance is responsible for issuing and maintaining records for any per-call orders for remedial maintenance placed under this contract. No per-call order shall be placed outside the scope of this contract and the cumulative total of all orders shall not be in excess of any not-to-exceed amount specified in the contract. Per-call orders shall not, in any way, modify any terms and conditions of the contract.
(i) The Authorized Ordering Person(s) for Per-Call Maintenance is:
Name: [ * ] Address:
[ *Street ] [ *City, State, Zip ] Phone: (Area Code) xxx- [xxxx];
E-mail: [ * ]
(j) The Contractor's point of contact for performance under this contract is:
Name: [ * ] Address:
[ *Street ] [ *City, State, Zip ] Phone: (Area Code) xxx- [xxxx] E-mail: [ * ]
(End of Text)
G-242-W001 CONTRACT ADMINISTRATION FUNCTIONS (NAVSEA) (OCT 2018) (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 to be retained by PCO_ _ [ List specific functions that will be retained by the PCO]
(b) In accordance with FAR 42.302(b), the following additional functions are delegated to the ACO:
_All functions to be retained by PCO__ _ [ List any additional functions that will be delegated to the ACO]
(End of Text)
Section H - Special Contract Requirements
Section I - Contract Clauses
FAR Clauses Incorporated by Reference
Number Title Effective Date
Alternate/ Deviation
Variation Effective Date
52.203-19 Prohibition on Requiring Certain Internal Confidentiality Agreements or Statements. Jan 2017 52.204-13 System for Award Management Maintenance. Oct 2018 52.204-18 Commercial and Government Entity Code Maintenance. Aug 2020
52.204-23 Prohibition on Contracting for Hardware, Software, and Services Developed or Provided by Kaspersky Lab Covered Entities.
Dec 2023
52.204-25 Prohibition on Contracting for Certain Telecommunications and Video Surveillance Services or Equipment.
Nov 2021
52.204-27 Prohibition on a ByteDance Covered Application. Jun 2023 52.209-10 Prohibition on Contracting with Inverted Domestic Corporations. Nov 2015 52.212-4 Contract Terms and Conditions-Commercial Products and Commercial Services. Nov 2023 52.222-50 Combating Trafficking in Persons. Nov 2021 52.223-23 Sustainable Products and Services. May 2024 52.225-13 Restrictions on Certain Foreign Purchases. Feb 2021 52.226-8 Encouraging Contractor Policies to Ban Text Messaging While Driving. May 2024 52.227-1 Authorization and Consent. (Alternate I) Jun 2020 Alternate I Apr 1984 52.227-1 Authorization and Consent. Jun 2020 52.227-2 Notice and Assistance Regarding Patent and Copyright Infringement. Jun 2020 52.227-14 Rights in Data-General. May 2014 52.232-33 Payment by Electronic Funds Transfer-System for Award Management. Oct 2018 52.232-40 Providing Accelerated Payments to Small Business Subcontractors. Mar 2023 52.233-3 Protest after Award. Aug 1996 52.233-4 Applicable Law for Breach of Contract Claim. Oct 2004
52.240-1 Prohibition on Unmanned Aircraft Systems Manufactured or Assembled by American Security Drone Act-Covered Foreign Entities.
Nov 2024
DFARS Clauses Incorporated by Reference
Number Title Effective Date
Alternate/ Deviation
Variation Effective Date
252.203-7000 Requirements Relating to Compensation of Former DoD Officials. Sep 2011 252.203-7002 Requirement to Inform Employees of Whistleblower Rights. Dec 2022
252.204-7018 Prohibition on the Acquisition of Covered Defense Telecommunications Equipment or Services.
Jan 2023
252.223-7008 Prohibition of Hexavalent Chromium. Jan 2023 252.225-7001 Buy American and Balance of Payments Program. Feb 2024 252.225-7002 Qualifying Country Sources as Subcontractors. Mar 2022 252.225-7056 Prohibition Regarding Business Operations with the Maduro Regime. Jan 2023
252.225-7060 Prohibition on Certain Procurements from the Xinjiang Uyghur Autonomous Region.
Jun 2023
252.225-7967 Prohibition Regarding Russian Fossil Fuel Business Operations (Deviation 2024-O0006, Revision 1)
Feb 2024 Deviation 2024-O0006 Feb 2024
252.227-7003 Termination. Aug 1984
252.227-7013 Rights in Technical Data-Other Than Commercial Products and Commercial Services.
Jan 2025
252.227-7014 Rights in Other Than Commercial Computer Software and Other Than Commercial
Jan 2025
252.227-7015 Technical Data-Commercial Products and Commercial Services. Jan 2025 252.227-7027 Deferred Ordering of Technical Data or Computer Software. Apr 1988 252.227-7030 Technical Data-Withholding of Payment. Mar 2000 252.227-7037 Validation of Asserted Restrictions on Technical Data. Jan 2025 252.232-7010 Levies on Contract Payments. Dec 2006 252.239-7018 Supply Chain Risk. Dec 2022 252.244-7000 Subcontracts for Commercial Products or Commercial Services. Nov 2023 252.246-7008 Sources of Electronic Parts. Jan 2023 252.247-7023 Transportation of Supplies by Sea. Oct 2024
FAR Clauses Incorporated by Full Text
52.212-5 Contract Terms and Conditions Required to Implement Statutes or Executive Orders - Commercial Products and Commercial Services.
(DEVIATION 2025-O0003 and 2025-O0004)
(Jan 2025) Deviation 2025-O0004 (Mar 2025)
CONTRACT TERMS AND CONDITIONS REQUIRED TO IMPLEMENT STATUTES OR EXECUTIVE ORDERS-COMMERCIAL PRODUCTS AND COMMERCIAL SERVICES (MAR 2025) (DEVIATION 2025-O0003 AND 2025-O0004)
(a) The Contractor shall comply with the following Federal Acquisition Regulation (FAR) clauses, which are incorporated in this contract by reference, to implement provisions of law or Executive orders applicable to acquisitions of commercial products and commercial services:
(1) 52.203-19, Prohibition on Requiring Certain Internal Confidentiality Agreements or Statements (section 743 of Division E, Title (JAN 2017) VII, of the Consolidated and Further Continuing Appropriations Act, 2015 (Pub. L. 113-235) and its successor provisions in subsequent appropriations acts (and as extended in continuing resolutions)).
(2) 52.204-23, Prohibition on Contracting for Hardware, Software, and Services Developed or Provided by Kaspersky Lab Covered Entities (DEC (Section 1634 of Pub. L. 115-91).2023)
(3) 52.204-25, Prohibition on Contracting for Certain Telecommunications and Video Surveillance Services or Equipment. (Section (NOV 2021) 889(a)(1)(A) of Pub. L. 115-232).
(4) 52.209-10, Prohibition on Contracting with Inverted Domestic Corporations .(NOV 2015)
(5) 52.232-40, Providing Accelerated Payments to Small Business Subcontractors (31 U.S.C. 3903 and 10 U.S.C. 3801).(MAR 2023)
(6) 52.233-3, Protest After Award (31 U.S.C. 3553).(AUG 1996)
(7) 52.233-4, Applicable Law for Breach of Contract Claim (Public Laws 108-77 and 108-78 ( 19 U.S.C. 3805 note)).
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 .