Solicitation - N0018926QL358.pdf

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.

Solicitation/Contract Form Continuation

USFFC (MDA) - Strategic Maritime and Logistics Intelligence Resource

N0018926QL358

Continuation of Supplies or Services and Prices/Costs

Additional Information/Notes

Item Supplies/Service Quantity Unit Unit Price Amount

0001 Maritime Domain Awareness (MDA) Subscriptions IAW PWS

Pricing Arrangement: Firm Fixed Price

2 Each

Continuation of Description Performance Work Statement Strategic Maritime and Logistics Intelligence Resource In Support of US Fleet Forces MDA

1. Scope:

USFFC Maritime Domain Awareness (MDA) requires a multi-source maritime fusion and maritime trade analytic resource that is web-based, non-classified, non-PKI commercial maritime information to provide near-real time, relevant and reliable data and information pertaining to the commercial maritime industry and provided by the commercial industry. Required data and information should be included but is not limited to Section 2 below.

United States Fleet Forces Command (USFFC) N3 Maritime Domain Awareness, provides 24/7/365 support to the Fleet Command Center Battle Watch, Navy Fleet assets, United States Northern Command, and interagency partners. Our focus is behavioral and predictive analysis of information and data pertaining to vessels, people, cargo, infrastructure and events in the maritime domain.

2. Requirements

2.1. Ship Data and Information, such as:

2.1.1. News stories

2.1.2. Adverse media reports

2.1.3. Registration

2.1.4. Ownership - seven levels of ownership, ultimate beneficial ownership data for maritime and non-maritime companies, and financial beneficiaries

2.1.5. Commercial history

2.1.6. Classification society information

2.1.7. Surveys and inspections

2.1.8. Construction details

2.1.9. Cargo and gear specifications

2.1.10. Machinery specifications

2.1.11. Photographs and imagery

2.1.12. Insurance information

2.1.13. Maritime industry economic performance indicators

2.2. Trade Intelligence and Analytics

2.2.1. Trade flow maps depicting cargo flows and market trends

2.2.2. Dashboard capabilities to build user-defined views

2.2.3. Built-in AI analytical capability to identify trends, anomalies, and operational impacts

2.2.4. Trade news, market intelligence, and webinar access

2.2.5. Risk and compliance data for vessels, cargoes, flag states, ports, and regulatory authorities

2.2.6. Cargo, Oil & Gas, LNG, and refinery inventories

2.2.7. Voyage calculators and routing analysis

2.2.8. Container tracking capabilities

2.3. Vessel Information, such as:

2.3.1. Multi-source AIS including satellite, terrestrial, and shipborne feeds with six (6) or more years of historical data

2.3.2. Movement and history tracking (30, 60, 90, 180, and 365 days)

2.3.3. Dynamic vessel navigation data (course / projected course, speed, latitude, longitude, time and date of last reporting)

2.3.4. Behavioral risk indicators

2.3.5. Static vessel data (flag, IMO, call sign, MMSI, vessel type, cargo, status)

2.3.6. Identification discrepancies (false IMO, invalid MMSI, multiple registrations)

2.3.7. Destination information (port, ETA, reported destination)

2.3.8. Vessel look-up searches and advanced queries

2.3.9. Record matching and saved search functionality

2.3.10. Exporting results to CSV, Excel, PDF, and KML

2.3.11. Exportable vessel profiles and AIS activity reports

2.3.12. Ship search capabilities using static and dynamic criteria

2.3.13. Historical vessel records including detentions, inspections, and safety violations

2.3.14. Multiple vessel photographs

2.3.15. Company records including owners, charterers, operators, and insurers

2.3.16. Automated report generation

2.3.17. Advanced search and query capabilities

2.3.18. Comparative analysis of selected vessels

2.3.19. Historical ownership, flag, and name change records

2.3.20. Day-to-day sanctions screening

2.3.21. Ship and ownership research capabilities

2.3.22. Compliance support documentation

2.3.23. Monitoring and alerting for vessels calling sanctioned jurisdictions

2.3.24. Detection of deceptive shipping practices consistent with OFAC maritime advisories

2.4. Maritime Industry Companies Information

2.4.1. Company search and overview

2.4.2. Due diligence screening for maritime and non-maritime companies

2.4.3. Sanctions screening for companies and vessels

2.4.4. Behavioral network analysis and associations

2.4.5. Shipping companies and vessels owned

2.4.6. Fleet lists

2.4.7. Trading areas

2.4.8. Related company records

2.4.9. Reports

2.4.10. Company watchlists

2.4.11. Relationships with other companies

2.4.12. Personnel information

2.4.13. Fleet size

2.4.14. Ship and ownership research

2.4.15. Port State Control event monitoring

2.4.16. Ownership hierarchy identification

2.4.17. Monitoring of ships operating in high-risk zones

2.4.18. Casualty and risk-event searches

2.5. Tracking Vessel Movements

2.5.1. Movement searches

2.5.2. Creating and sharing vessel watchlists

2.5.3. Movement alerts

2.5.4. User-defined trigger areas and alerts

2.5.5. Timeline search

2.5.6. Anomalous behavior analysis

2.5.7. Behavioral analysis and associated risk scoring

2.5.8. Recall of five (5) or more years of vessel activity data integrated with near real-time tracking

2.5.9. Historical playback capability

2.5.10. Vessel meeting detection

2.5.11. AIS gap and dark activity detection

2.5.12. Identity manipulation detection

2.5.13. Route deviation detection

2.5.14. Pattern-of-life analysis

2.5.15. High-risk zone monitoring

2.5.16. Ship-to-ship transfer detection

2.5.17. Understanding of the specific cargoes involved in dark activities or ship-to-ship transfers

2.6. Port and Port Congestion Intelligence

2.6.1. Port risk assessment

2.6.2. Search by country, port code, location, and name

2.6.3. Port mapping

2.6.4. Port particulars including latitude, longitude, and maximum draft

2.6.5. Pre-arrival information

2.6.6. Port descriptions

2.6.7. Address and contact information

2.6.8. Images

2.6.9. Ships in port

2.6.10. Port call history

2.6.11. Port congestion monitoring and analytics

2.6.12. Port throughput trend analysis

2.6.13. Vessel wait-time analysis

2.6.14. Canal and transit route performance monitoring

2.6.15. Infrastructure stress indicators

2.6.16. Infrastructure resilience assessment

2.7. Analysis Functions

2.7.1. Automated vessel activity detection

2.7.2. Trading area analysis

2.7.3. User-defined areas of interest

2.7.4. Company analysis and behavioral risk identification

2.7.5. Company and ownership due diligence analysis

2.7.6. Automated reports and alerts, including vessel, ownership, and risk reports

2.7.7. Vessel movement analysis

2.7.8. Historical analysis utilizing seven (7) or more years of accessible data

2.7.9. Identification, monitoring, and forecasting of sanctions and security risks

2.7.10. Verification of vessels operating in designated waters

2.7.11. Identification of vessels operating in high-risk areas

2.7.12. Monitoring of offshore, coastal, and port areas

2.7.13. Monitoring vessels within custom-designated zones

2.7.14. Viewing near real-time and historical vessel tracks

2.7.15. Risk event analysis

2.7.16. Behavioral and geographic searches utilizing multi-layer filtering

2.7.17. Behavioral trend analysis

2.8. Geo-Visual Display

2.8.1. Map and satellite view

2.8.2. Support for government and commercial data integration

2.8.3. Imagery overlays

2.8.4. Digital nautical chart view

2.8.5. Weather overlays

2.8.6. Distance measurement and voyage calculators

2.8.7. Upload and customize vessel list displays

2.8.8. Heat signature displays by vessel type

2.8.9. Customized alerts

2.8.10. Vessel color keys

2.8.11. User-defined shapes and trigger areas

2.8.12. Imagery measurement tools

2.8.13. Critical infrastructure overlays

2.8.14. Oil and Gas infrastructure overlays

2.8.15. Maritime boundaries and user-defined areas of interest

2.8.16. Laden or unladen (ballast) status for every vessel, based on data or assessment

2.9. Technical Requirements

2.9.1. Web-based service accessible through a standard browser

2.9.2. No software installation required

2.9.3. Role-based user access controls

2.9.4. Secure cloud-hosted architecture

2.9.5. Export capabilities for reports and analytical products

2.9.6. API access for authorized users

2.9.7. Ability to integrate data with multiple existing USG tools and workflows, to include Maven Smart Systems (MSS)

2.9.8. User-configurable dashboards and alerting

2.9.9. Ability to query data sets via embedded natural-language Artificial Intelligence (AI) interface

2.9.10. Ability to query data sets via AI model context protocol (MCP) capability to combine tool data with USG and other data for richer, more holistic analysis

2.10. Cargo Intelligence

2.10.1. Global commodity trade flow monitoring, including at least crude oil, refined products, liquefied natural gas, liquefied petroleum gas, dry bulk cargo, and containerized cargo.

2.10.2. Commodity flow mapping and visualization

2.10.3. Cargo origin, movement forecasting and destination prediction

2.10.4. Cargo ownership, buyer, seller, and charterer visibility

2.10.5. Historical cargo movement analysis

2.10.6. Cargo diversion detection and analysis

2.11. Refinery and Energy Infrastructure Intelligence

2.11.1. Global refinery monitoring

2.11.2. Refinery ownership and operator identification

2.11.3. Refinery utilization tracking

2.11.4. Refinery operational status monitoring

2.11.5. Refinery feedstock sourcing analysis

2.11.6. Refinery outage and disruption assessment

2.12. Energy Storage and Inventory Intelligence

2.12.1. Global crude oil inventory monitoring

2.12.2. Satellite-derived crude oil storage assessments

2.12.3. Floating storage monitoring

2.12.4. LNG inventory monitoring

2.12.5. Strategic petroleum reserve monitoring

2.12.6. Inventory draw and build analysis

2.13. Supply Chain Intelligence

2.13.1. Strategic material sourcing analysis

2.13.2. Commodity origin and destination tracing

2.13.3. Import and export dependency analysis

2.13.4. Trade route disruption monitoring

2.13.5. Supply chain bottleneck identification

2.13.6. Chokepoint vulnerability assessment

2.13.7. Critical infrastructure dependency analysis

2.13.8. Transportation network disruption assessment

2.13.9. Economic sanctions impact analysis

3. Required Period of Performance Base Period: One (1) year from date of award.

4. Point of Contact To be provided by the Contracting Officer and/or Requiring Activity at award.

Contractor Unclassified Access to Federally Controlled Facilities, Sensitive Information, Information Technology (IT) Systems or Protected Health Information

Executive Order 13467, Reforming Processes Related to Suitability for Government Employee, Fitness for Contractor Employees and Eligibility for Access to Classified National Security Information, Homeland Security Presidential Directive (HSPD)-12, requires government agencies to develop and implement Federal security standards for Federal employees and contractors. The 5 CFR 32 Part 157 in concert with DoD Manual 1000.13, Vol 1, implements the Federal Standards.

APPLICABILITY

This text applies to all DoD sponsored individuals who require CAC eligibility (or login and P/W if acceptable per contract) for: Physical access to DoD facilities or non-DoD facilities on behalf of DoD; Logical access to information systems (whether on site or remotely); or remote access to DoD networks that use only the CAC logon for user authentication, or access to sensitive and protected information. This applies to the Office of the Secretary of Defense, the Military Departments, the Office of the Chairman of the Joint Chiefs of Staff and the Joint Staff, the Combatant Commands, the Office of the Inspector General of the DoD, the Defense Agencies, the DoD Field Activities and all other organizational entities within the DoD (hereinafter referred to collectively as the "DoD Components").

Each contractor employee providing services at a Navy Command under this contract is required to obtain a Department of Defense Common Access Card (DoD CAC). Additionally, depending on the level of computer/network access, the contract employee will require a successful investigation as detailed below.

ACCESS TO FEDERAL FACILITIES

Per HSPD-12 and implementing guidance, all contractor employees working at a federally controlled base, facility or activity under this clause will require a DoD CAC. When access to a base, facility or activity is required contractor employees shall in-process with the Command's Security Manager upon arrival to the Command and shall out-process prior to their departure at the completion of the individual's performance under the contract.

START-UP PERIOD

All contractor resource onboarding documents must be submitted via the prime contractor. The prime contractor shall make all necessary preparations to assume full responsibility for productive performance of the performance start date.

Definition of "productive":

a. Visit Authorization Request (VAR)

b. Contractor Information Sheet (CIS)

c. Completed EQIP (Electronic Investigation)

d. All contractor resource(s) must have an active JPAS profile.

e. Common Access Card (CAC)

Note (1): Invoicing by the contractor will begin as of the commencement of the performance period of services and no reimbrusement will be paid by the government for efforts expended during the start-up period.

Note (2): Foreign Nationals are not allowed access to the functional/system side of Enterprise Resource Planning (ERP).

ACCESS TO DOD INFORMATION TECHNOLOGY ( IT) SYSTEMS

In accordance with (IAW) Secretary of the Navy (SECNAV) M-5510.30, contractor employees who require access to DoN or DoD networks are categorized as IT-I, IT-II, or IT-III. The IT-II level, defined in detail in SECNAV M-5510.30, includes positions which require access to sensitive information. Sensitive information includes information protected under the Privacy Act, to include Protected Health Information (PHI). All contractor employees under this contract who require access to Privacy Act protected information are therefore categorized no lower than IT-II. IT Levels are determined by the requiring activity's Command Information System Security Manager (ISSM)/Information Assurance Manager (IAM).

Contractor employees requiring privileged or IT-I level access, (when specified by the terms of the contract) require a Single Scope Background Investigation (SSBI) or T5 or T5R equivalent investigation , which is a higher level investigation than the National Agency Check with Law and Credit (NACLC)/T3/T3R described below. Due to the privileged system access, an investigation suitable for High Risk national security positions is required. Individuals who have access to system control, monitoring, or administration functions (e.g. system administrator, database administrator) require training and certification to Information Assurance Technical Level 1, and must be trained and certified on the Operating System or Computing Environment they are required to maintain.

Access to sensitive IT systems is contingent upon a favorably adjudicated background investigation. When access to IT systems is required for performance of the contractor employee's duties, such employees shall in-process with the Navy Command's CSM and ISSM/IAM upon arrival to the

Navy command and shall out-process prior to their departure at the completion of the individual's performance under the contract. Completion and approval of a System Authorization Access Request Navy (SAAR-N) form is required for all individuals accessing Navy Information Technology resources. The decision to authorize access to a government IT system/network is inherently governmental. The contractor supervisor is not authorized to sign the SAAR-N; therefore, the government employee with knowledge of the system/network access required or the COR shall sign the SAAR-N as the "supervisor".

The SAAR-N shall be forwarded to the Command's Security Manager at least 30 days prior to the individual's start date. Failure to provide the required documentation at least 30 days prior to the individual's start date may result in delaying the individual's start date.

When required to maintain access to required IT systems or networks, the contractor shall ensure that all employees requiring access complete annual Cyber Awareness training, and maintain a current requisite background investigation. The Contractor's Security Representative shall contact the Command Security Manager for guidance when reinvestigations are required.

INTERIM ACCESS

The Command's Security Manager may authorize issuance of a DoD CAC and interim access to a DoN or DoD unclassified computer/network upon a favorable review of the investigative questionnaire and advance favorable fingerprint results. When the results of the investigation are received and a favorable determination is not made, the contractor employee working on the contract under interim access will be denied access to the computer network and this denial will not relieve the contractor of his/her responsibility to perform.

DENIAL OR TERMINATION OF ACCESS

The potential consequences of any requirement under this clause including denial or termination of physical or system access in no way relieves the contractor from the requirement to execute performance under the contract within the timeframes specified in the contract. Contractors shall plan ahead in processing their employees and subcontractor employees. The contractor shall insert this clause in all subcontracts when the subcontractor is permitted to have unclassified access to a federally controlled facility, federally-controlled information system/network and/or to government information, meaning information not authorized for public release.

CONTRACTOR'S SECURITY REPRESENTATIVE

The contractor shall designate an employee to serve as the Contractor's Security Representative. Within three work days after contract award, the contractor shall provide to the requiring activity's Security Manager and the Contracting Officer, in writing, the name, title, address and phone number for the Contractor's Security Representative. The Contractor's Security Representative shall be the primary point of contact on any security matter.

The Contractor's Security Representative shall not be replaced or removed without prior notice to the Contracting Officer and Command Security Manager.

BACKGROUND INVESTIGATION REQUIREMENTS AND SECURITY APPROVAL PROCESS FOR CONTRACTORS ASSIGNED TO

NATIONAL SECURITY POSITIONS OR PERFORMING SENSITIVE DUTIES

Navy security policy requires that all positions be given a sensitivity value based on level of risk factors to ensure appropriate protective measures are applied. Contractor employees under this contract are recognized as Non-Critical Sensitive [ADP/IT-II] positions when the contract scope of work require physical access to a federally controlled base, facility or activity and/or requiring access to a DoD computer/network, to perform unclassified sensitive duties. This designation is also applied to contractor employees who access Privacy Act and Protected Health Information (PHI), provide support associated with fiduciary duties, or perform duties that have been identified as National Security Positions. At a minimum, each contractor employee must be a US citizen and have a favorably completed NACLC or T3 or T3R equivalent investigation to obtain a favorable determination for assignment to a non-critical sensitive or IT-II position. The investigation consists of a standard NAC and a FBI fingerprint check plus law enforcement checks and credit check. Each contractor employee filling a non-critical sensitive or IT-II position is required to complete:

SF-86 Questionnaire for National Security Positions (or equivalent OPM investigative product) Two FD-258 Applicant Fingerprint Cards (or an electronic fingerprint submission) Original Signed Release Statements

Failure to provide the required documentation at least 30 days prior to the individual's start date shall result in delaying the individual's start date.

Background investigations shall be reinitiated as required to ensure investigations remain current (not older than 10 years) throughout the contract performance period. The Contractor's Security Representative shall contact the Command Security Manager for guidance when reinvestigations are required.

Regardless of their duties or IT access requirements ALL contractor employees shall in-process with the CSM upon arrival to the command and shall out-process prior to their departure at the completion of the individual's performance under the contract. Employees requiring IT access shall also check-in and check-out with the Navy Command's ISSM/IAM. Completion and approval of a System Authorization Access Request Navy (SAAR-N) form is required for all individuals accessing Navy Information Technology resources. The SAAR-N shall be forwarded to the Navy Command's Security Manager at least 30 days prior to the individual's start date. Failure to provide the required documentation at least 30 days prior to the individual's start date shall result in delaying the individual's start date.

The contractor shall ensure that each contract employee requiring access to IT systems or networks complete annual Cyber Awareness training, and maintain a current requisite background investigation. Contractor employees shall accurately complete the required investigative forms prior to submission to the Command Security Manager. The Command's Security Manager will review the submitted documentation for completeness prior to submitting it to the Office of Personnel Management (OPM); Potential suitability or security issues identified may render the contractor employee ineligible for the assignment. An unfavorable determination is final (subject to SF-86 appeal procedures) and such a determination does not relieve the contractor from meeting any contractual obligation under the contract. The Command's Security Manager will forward the required forms to OPM for processing. Once the investigation is complete, the results will be forwarded by OPM to the DoD Central Adjudication Facility (CAF) for a determination.

If the contractor employee already possesses a current favorably adjudicated investigation, the contractor shall submit a Visit Authorization Request (VAR) via the Joint Personnel Adjudication System (JPAS) or a hard copy VAR directly from the contractor's Security Representative. Although the contractor will take JPAS "Owning" role over the contractor employee, the Navy command will take JPAS "Servicing" role over the contractor employee during the hiring process and for the duration of assignment under that contract. The contractor shall include the IT Position Category per SECNAV M-5510.30 for each employee designated on a VAR. The VAR requires annual renewal for the duration of the employee's performance under the contract.

BACKGROUND INVESTIGATION REQUIREMENTS AND SECURITY APPROVAL PROCESS FOR CONTRACTORS ASSIGNED TO

OR PERFORMING NON-SENSITIVE DUTIES

Contractor employee whose work is unclassified and non-sensitive (e.g., performing certain duties such as lawn maintenance, vendor services, etc. ...)

and who require physical access to publicly accessible areas to perform those duties shall meet the following minimum requirements:

Must be either a US citizen or a US permanent resident with a minimum of 3 years of legal residency in the United States (as required by The Deputy Secretary of Defense DTM 08-006 or its subsequent DoD instruction) and Must have a favorably completed National Agency Check with Written Inquiries (NACI) or T1 investigation equivalent including a FBI fingerprint check prior to installation access.

To be considered for a favorable trustworthiness determination, the Contractor's Security Representative must submit for all employees each of the following:

SF-85 Questionnaire for Non-Sensitive Positions Two FD-258 Applicant Fingerprint Cards (or an electronic fingerprint submission) Original Signed Release Statements

The contractor shall ensure each individual employee has a current favorably completed National Agency Check with Written Inquiries (NACI) or T1 equivalent investigation, or ensure successful FBI fingerprint results have been gained and investigation has been processed with OPM

Failure to provide the required documentation at least 30 days prior to the individual's start date may result in delaying the individual's start date.

* Consult with your CSM and ISSM/IAM for local policy when IT-III (non-sensitive) access is required for non-US citizens outside the United States.

Requirements USFFC Maritime Domain Awareness (MDA) requires a multi-source maritime fusion and maritime trade analytic resource that is web-based, non-classified, non-PKI commercial maritime information to provide near-real time, relevant and reliable data and information pertaining to the commercial maritime industry and provided by the commercial industry.

Continuation of Packaging and Marking

Continuation of Inspection and Acceptance

Overall Contract Inspection/Acceptance Locations

Inspection and Acceptance Location

Both Destination Instructions: See Statement of Work (SOW) or Performance Work Statement (PWS) for Acceptance/inspection criteria.

DoDAAC: N00060 CountryCode: USA

U S FLEET FORCES COMMAND

1562 MITSCHER AVE, SUITE 250, NORFOLK VA 23511-2487

NORFOLK, VA 23511-2487

UNITED STATES

Justin Kanter, Solicitation Manager Email: 757-443-1275 Telephone: justin.w.kanter.civ@us.navy.mil

Continuation of Deliveries or Performance

Overall Contract Delivery Period

Contractor Destination

Line Item Delivery Schedule Quantity Address and POC

Delivery Schedule From date of lead time event to completion of performance 1 Calendar Year Date of Award

2 Each Ship To DoDAAC: N00060 CountryCode: USA

U S FLEET FORCES COMMAND

1562 MITSCHER AVE, SUITE 250, NORFOLK VA

23511-2487

NORFOLK, VA 23511-2487

UNITED STATES

Justin Kanter, Solicitation Manager Email: 757-443-1275 Telephone: justin.w.kanter.civ@us.navy.mil

Continuation of Accounting and Appropriation Data

Contract Clauses

FAR Clauses Incorporated by Reference

Number Title Effective Date

Alternate/ Deviation

Variation Effective Date

52.204-13 System for Award Management-Maintenance. (Deviation 2026-O0038) Feb 2026 52.203-19 Prohibition on Requiring Certain Internal Confidentiality Agreements or Statements. Jan 2017 52.222-19 Child Labor-Cooperation with Authorities and Remedies. (Deviation 2026-O0038) Mar 2026 52.222-35 Equal Opportunity for Veterans. (Deviation 2026-O0038) Feb 2026 52.222-36 Equal Opportunity for Workers with Disabilities. (Deviation 2026-O0038) Feb 2026 52.222-37 Employment Reports on Veterans. (Deviation 2026-O0038) Feb 2026 52.226-8 Encouraging Contractor Policies to Ban Text Messaging While Driving. May 2024 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. (Deviation 2026-O0038) Feb 2026 52.233-4 Applicable Law for Breach of Contract Claim. (Deviation 2026-O0038) Feb 2026

52.212-4 Terms and Conditions-Commercial Products and Commercial Services. (Deviation 2026- O0038)

Feb 2026

DFARS Clauses Incorporated by Reference

Number Title Effective Date

Alternate/ Deviation

Variation Effective Date

252.203-7002 Requirement to Inform Employees of Whistleblower Rights. Dec 2022 252.203-7000 Requirements Relating to Compensation of Former DoD Officials. Sep 2011 252.204-7015 Notice of Authorized Disclosure of Information for Litigation Support. Jan 2023

252.204-7018 Prohibition on the Acquisition of Covered Defense Telecommunications Equipment or Services.

Jan 2023

252.204-7022 Expediting Contract Closeout. May 2021

252.209-7004 Subcontracting with Firms that are Owned or Controlled by the Government of a Country that is a State Sponsor of Terrorism.

May 2019

252.232-7003 Electronic Submission of Payment Requests and Receiving Reports. Dec 2018 252.232-7010 Levies on Contract Payments. Dec 2006 252.247-7023 Transportation of Supplies by Sea. Oct 2024 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.223-7008 Prohibition of Hexavalent Chromium. Jan 2023

FAR Clauses Incorporated by Full Text

52.219-4 Notice of Price Evaluation Preference for HUBZone Small Business Concerns. (Deviation 2026-O0038)

(Feb 2026)

NOTICE OF PRICE EVALUATION PREFERENCE FOR HUBZONE SMALL BUSINESS CONCERNS (FEB 2026) (DEVIATION 2026- O0038)

Evaluation preference.(a)

Offers will be evaluated by adding a factor of 10 percent to the price of all offers, except-(1)

(i) Offers from HUBZone small business concerns that have not waived the evaluation preference; and

(ii) Otherwise successful offers from small business concerns.

(b) . A HUBZone small business concern may choose to waive the evaluation preference. If the concern waives Waiver of evaluation preference the preference, the factor will be added to its offer for evaluation purposes.

Offeror chooses to waive the evaluation preference.

(c) A HUBZone joint venture agrees that, in the performance of the contract, at least 40 percent of the aggregate work performed by Joint venture.

the joint venture shall be completed by the HUBZone small business parties to the joint venture. Work performed by the HUBZone small business parties to the joint venture must be more than administrative functions.

(End of provision)

52.219-28 Postaward Small Business Program Rerepresentation. (Deviation 2026-O0038) (Feb 2026)

POSTAWARD SMALL BUSINESS PROGRAM REREPRESENTATION (FEB 2026) (DEVIATION 2026-O0038)

(a) . As used in this clause-Definitions

Long-term contract means a contract of more than five years in duration, including options. However, the term does not include contracts that exceed five years in duration because the period of performance has been extended for a cumulative period not to exceed six months under the clause at 52.217-8, Option to Extend Services, or other appropriate authority.

Small business concern-

(1) Means a concern, including its affiliates, that is independently owned and operated, not dominant in its field of operation, and qualified as a small business under the criteria in 13 CFR part 121 and the size standard in paragraph (c) of this clause.

(2) , as used in this definition, means business concerns, one of whom directly or indirectly controls or has the power to control the others, Affiliates or a third party or parties control or have the power to control the others. In determining whether affiliation exists, consideration is given to all appropriate factors including common ownership, common management, and contractual relationships. SBA determines affiliation based on the factors set forth at 13 CFR 121.103.

(b) If the Contractor represented that it was a small business concern, a small disadvantaged business concern, or a joint venture that was any of the small business concerns identified in 19.000(a)(3) prior to award of this contract, the Contractor shall rerepresent its size and socioeconomic status according to paragraph (e) of this clause or, if applicable, paragraph (g) of this clause, upon occurrence of any of the following:

(1) Within 30 days after execution of a novation agreement or within 30 days after modification of the contract to include this clause, if the novation agreement was executed prior to inclusion of this clause in the contract.

(2) Within 30 days after a merger or acquisition that does not require a novation or within 30 days after modification of the contract to include this clause, if the merger or acquisition occurred prior to inclusion of this clause in the contract.

(3) For long-term contracts-

(i) Within 60 to 120 days prior to the end of the fifth year of the contract; and

(ii) Within 60 to 120 days prior to the date specified in the contract for exercising any option thereafter.

(c) The Contractor shall rerepresent its size status in accordance with the size standard in effect at the time of this rerepresentation that corresponds to the North American Industry Classification System (NAICS) code(s) assigned to this contract. The small business size standard corresponding to this NAICS code(s) can be found at https://www.sba.gov/document/support--table-size-standards.

(d) The small business size standard for a Contractor providing an end item that it does not manufacture, process, or produce itself, for a contract other than a construction or service contract, is 500 employees, or 150 employees for information technology value-added resellers under NAICS code 541519, if the acquisition-

(1) Was set aside for small business and has a value above the simplified acquisition threshold;

(2) Used the HUBZone price evaluation preference regardless of dollar value, unless the Contractor waived the price evaluation preference; or

(3) Was an 8(a), HUBZone, service-disabled veteran-owned, economically disadvantaged women-owned, or women-owned small business set-aside or sole-source award regardless of dollar value.

(e) Except as provided in paragraph (g) of this clause, the Contractor shall make the representation(s) required by paragraph (b) of this clause by validating or updating all its representations in the Representations and Certifications section of the System for Award Management (SAM) and its other data in SAM, as necessary, to ensure that they reflect the Contractor's current status. The Contractor shall notify the contracting officer in writing within the timeframes specified in paragraph (b) of this clause, that the data have been validated or updated, and provide the date of the validation or update.

(f) If the Contractor represented that it was other than a small business concern prior to award of this contract, the Contractor may, but is not required to, take the actions required by paragraphs (e) or (g) of this clause.

(g) If the Contractor does not have representations and certifications in SAM, or does not have a representation in SAM for the NAICS code applicable to this contract, the Contractor is required to complete the following rerepresentation and submit it to the contracting office, along with the contract number and the date on which the rerepresentation was completed:

(1) The Contractor represents that it is, is not a small business concern under NAICS Code assigned to contract number.____ ____

(2) [ .] The Contractor represents Complete only if the Contractor represented itself as a small business concern in paragraph (g)(1) of this clause that it is, is not, a small disadvantaged business concern as defined in .13 CFR 124.1001

(3) . The Contractor represents that it is, is not a Women-owned small business (WOSB) joint venture eligible under the WOSB Program joint venture that complies with the requirements of 13 CFR 127.506(a) through (c). [ The Contractor shall enter the name and unique entity ____ identifier of each party to the joint venture: __.]

(4) . The Contractor represents that it is, is not a joint Economically disadvantaged women-owned small business (EDWOSB) joint venture venture that complies with the requirements of 13 CFR 127.506(a) through (c). [ The Contractor shall enter the name and unique entity identifier ____ of each party to the joint venture: __ .]

(5) . The Contractor represents that it Service-disabled veteran-owned small business (SDVOSB) joint venture eligible under the SDVOSB Program is, is not an SDVOSB joint venture eligible under the SDVOSB Program that complies with the requirements of 13 CFR 128.402. [ The ____ Contractor shall enter the name and unique entity identifier of each party to the joint venture: __.]

(6) [ ] The HUBZone joint venture eligible under the HUBZone Program. Complete only if the offeror is a HUBZone small business concern.

offeror represents, as part of its offer, that It is, is not a HUBZone joint venture that complies with the requirements of 13 CFR 126.616(a) through (c). [ The Contractor shall enter the name and unique entity identifier of each party to the joint venture: .] Each HUBZone small business ____ concern participating in the HUBZone joint venture must be certified as a HUBZone concern. [ Contractor to sign and date and insert authorized ____ signer's name and title.]

(End of clause)

DFARS Clauses Incorporated by Full Text

252.211-7003 Item Unique Identification and Valuation. (Jan 2023)

ITEM UNIQUE IDENTIFICATION AND VALUATION (JAN 2023)

(a) . As used in this clause- Definitions

"Automatic identification device" means a device, such as a reader or interrogator, used to retrieve data encoded on machine-readable media.

"Concatenated unique item identifier" means-

(1) For items that are serialized within the enterprise identifier, the linking together of the unique identifier data elements in order of the issuing agency code, enterprise identifier, and unique serial number within the enterprise identifier; or

(2) For items that are serialized within the original part, lot, or batch number, the linking together of the unique identifier data elements in order of the issuing agency code; enterprise identifier; original part, lot, or batch number; and serial number within the original part, lot, or batch number.

"Data matrix" means a two-dimensional matrix symbology, which is made up of square or, in some cases, round modules arranged within a perimeter finder pattern and uses the Error Checking and Correction 200 (ECC200) specification found within International Standards Organization (ISO)/International Electrotechnical Commission (IEC) 16022.

"Data qualifier" means a specified character (or string of characters) that immediately precedes a data field that defines the general category or intended use of the data that follows.

"DoD recognized unique identification equivalent" means a unique identification method that is in commercial use and has been recognized by DoD. All DoD recognized unique identification equivalents are listed at . https://www.acq.osd.mil/asda/dpc/ce/ds/unique-id.html

"DoD item unique identification" means a system of marking items delivered to DoD with unique item identifiers that have machine-readable data elements to distinguish an item from all other like and unlike items. For items that are serialized within the enterprise identifier, the unique item identifier shall include the data elements of the enterprise identifier and a unique serial number. For items that are serialized within the part, lot, or batch number within the enterprise identifier, the unique item identifier shall include the data elements of the enterprise identifier; the original part, lot, or batch number; and the serial number.

" Enterprise " means the entity (e.g., a manufacturer or vendor) responsible for assigning unique item identifiers to items.

" Enterprise identifier" means a code that is uniquely assigned to an enterprise by an issuing agency.

"Government's unit acquisition cost" means-

(1) For fixed-price type line, subline, or exhibit line items, the unit price identified in the contract at the time of delivery;

(2) For cost-type or undefinitized line, subline, or exhibit line items, the Contractor's estimated fully burdened unit cost to the Government at the time of delivery; and

(3) For items produced under a time-and-materials contract, the Contractor's estimated fully burdened unit cost to the Government at the time of delivery.

"Issuing agency" means an organization responsible for assigning a globally unique identifier to an enterprise, as indicated in the Register of Issuing Agency Codes for ISO/IEC 15459, located at http://www.aimglobal.org/?Reg_Authority15459.

"Issuing agency code" means a code that designates the registration (or controlling) authority for the enterprise identifier.

"Item" means a single hardware article or a single unit formed by a grouping of subassemblies, components, or constituent parts.

" Lot or batch number" means an identifying number assigned by the enterprise to a designated group of items, usually referred to as either a lot or a batch, all of which were manufactured under identical conditions.

"Machine-readable" means an automatic identification technology media, such as bar codes, contact memory buttons, radio frequency identification, or optical memory cards.

"Original part number" means a combination of numbers or letters assigned by the enterprise at item creation to a class of items with the same form, fit, function, and interface.

"Parent item" means the item assembly, intermediate component, or subassembly that has an embedded item with a unique item identifier or DoD recognized unique identification equivalent.

"Serial number within the enterprise identifier" means a combination of numbers, letters, or symbols assigned by the enterprise to an item that provides for the differentiation of that item from any other like and unlike item and is never used again within the enterprise.

"Serial number within the part, lot, or batch number" means a combination of numbers or letters assigned by the enterprise to an item that provides for the differentiation of that item from any other like item within a part, lot, or batch number assignment.

"Serialization within the enterprise identifier" means each item produced is assigned a serial number that is unique among all the tangible items produced by the enterprise and is never used again. The enterprise is responsible for ensuring unique serialization within the enterprise identifier.

"Serialization within the part, lot, or batch number" means each item of a particular part, lot, or batch number is assigned a unique serial number within that part, lot, or batch number assignment. The enterprise is responsible for ensuring unique serialization within the part, lot, or batch number within the enterprise identifier.

"Type designation" means a combination of letters and numerals assigned by the Government to a major end item, assembly or subassembly, as appropriate, to provide a convenient means of differentiating between items having the same basic name and to indicate modifications and changes thereto.

"Unique item identifier" means a set of data elements marked on items that is globally unique and unambiguous. The term includes a concatenated unique item identifier or a DoD recognized unique identification equivalent.

"Unique item identifier type" means a designator to indicate which method of uniquely identifying a part has been used. The current list of accepted unique item identifier types is maintained at .https://www.acq.osd.mil/asda/dpc/ce/ds/unique-id.html

(b) The Contractor shall deliver all items under a contract line, subline, or exhibit line item.

(c) Unique item identifier.

(1) The Contractor shall provide a unique item identifier for the following:

(i) Delivered items for which the Government's unit acquisition cost is $5,000 or more, except for the following line items:

Contract Line, Subline, or

Exhibit Line Item Number Item Description

(ii) Items for which the Government's unit acquisition cost is less than $5,000 that are identified in the Schedule or the following table:

Contract Line, Subline, or

Exhibit Line Item Number Item Description

(If items are identified in the Schedule, insert "See Schedule in this table.)

(iii) Subassemblies, components, and parts embedded within delivered items, items with warranty requirements, DoD serially managed reparables and DoD serially managed nonreparables as specified in Attachment Number .____

(iv) Any item of special tooling or special test equipment as defined in FAR 2.101 that have been designated for preservation and storage for a Major Defense Acquisition Program as specified in Attachment Number .____

(v) Any item not included in (i), (ii), (iii), or (iv) for which the contractor creates and marks a unique item identifier for traceability.

(2) The unique item identifier assignment and its component data element combination shall not be duplicated on any other item marked or registered in the DoD Item Unique Identification Registry by the contractor.

(3) The unique item identifier component data elements shall be marked on an item using two dimensional data matrix symbology that complies with ISO/IEC International Standard 16022, Information technology - International symbology specification - Data matrix; ECC200 data matrix specification.

(4) The Contractor shall ensure that- Data syntax and semantics of unique item identifiers.

(i) The data elements (except issuing agency code) of the unique item identifier are encoded within the data matrix symbol that is marked on the item using one of the following three types of data qualifiers, as determined by the Contractor:

(A) Application Identifiers (AIs) (Format Indicator 05 of ISO/IEC International Standard 15434), in accordance with ISO/IEC International Standard 15418, Information Technology - EAN/UCC Application Identifiers and Fact Data Identifiers and Maintenance and ANSI MH

10.8.2 Data Identifier and Application Identifier Standard.

(B) Data Identifiers (DIs) (Format Indicator 06 of ISO/IEC International Standard 15434), in accordance with ISO/IEC International Standard 15418, Information Technology - EAN/UCC Application Identifiers and Fact Data Identifiers and Maintenance and ANSI MH

10.8.2 Data Identifier and Application Identifier Standard.

(C) Text Element Identifiers (TEIs) (Format Indicator 12 of ISO/IEC International Standard 15434), in accordance with the Air Transport Association Common Support Data Dictionary; and

(ii) The encoded data elements of the unique item identifier conform to the transfer structure, syntax, and coding of messages and data formats specified for Format Indicators 05, 06, and 12 in ISO/IEC International Standard 15434, Information Technology - Transfer Syntax for High Capacity Automatic Data Capture Media.

(5) . Unique item identifier

(i) The Contractor shall-

(A) Determine whether to-

Serialize within the enterprise identifier; (1)

Serialize within the part, lot, or batch number; or (2)

Use a DoD recognized unique identification equivalent (e.g. Vehicle Identification Number); and (3)

(B) Place the data elements of the unique item identifier (enterprise identifier; serial number; DoD recognized unique identification equivalent; and for serialization within the part, lot, or batch number only: original part, lot, or batch number) on items requiring marking by paragraph (c)(1) of this clause, based on the criteria provided in MIL-STD-130, Identification Marking of U.S. Military Property, latest version;

(C) Label shipments, storage containers and packages that contain uniquely identified items in accordance with the requirements of MIL-STD-129, Military Marking for Shipment and Storage, latest version; and

(D) Verify that the marks on items and labels on shipments, storage containers, and packages are machine readable and conform to the applicable standards. The contractor shall use an automatic identification technology device for this verification that has been programmed to the requirements of Appendix A, MIL-STD-130, latest version.

(ii) The issuing agency code-

(A) Shall not be placed on the item; and

(B) Shall be derived from the data qualifier for the enterprise identifier.

(d) For each item that requires item unique identification under paragraph (c)(1)(i), (ii), or (iv) of this clause or when item unique identification is provided under paragraph (c)(1)(v), in addition to the information provided as part of the Material Inspection and Receiving Report specified elsewhere in this contract, the Contractor shall report at the time of delivery, as part of the Material Inspection and Receiving Report, the…