RFQ 70Z0G326QAMVER001 - AMEND 1 KO.pdf

Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended, by one of the following methods:

(a) By completing items 8 and 15, and returning or (c) By separate letter or electronic communication which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by letter or electronic communication, provided each letter or electronic communication makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

E. IMPORTANT: Contractor is not is required to sign this document and return copies to the issuing office.

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT 1. CONTRACT ID CODE

3. EFFECTIVE DATE 4. REQUISITION/PURCHASE REQUISITION NUMBER 5. PROJECT NUMBER (If applicable)

7. ADMINISTERED BY (If other than Item 6) CODE

STANDARD FORM 30 (REV. 11/2016)

Prescribed by GSA FAR (48 CFR) 53.243

FACILITY CODE

9A. AMENDMENT OF SOLICITATION NUMBER

9B. DATED (SEE ITEM 11)

10A. MODIFICATION OF CONTRACT/ORDER NUMBER

10B. DATED (SEE ITEM 13)

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offers is extended. is not extended.

12. ACCOUNTING AND APPROPRIATION DATA (If required) copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NUMBER AS DESCRIBED IN ITEM 14.

CHECK ONE A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE CONTRACT ORDER

NUMBER IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation data, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(b).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15C. DATE SIGNED

15A. NAME AND TITLE OF SIGNER (Type or print)

16C. DATE SIGNED

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

PAGE OF PAGES

6. ISSUED BY CODE

8. NAME AND ADDRESS OF CONTRACTOR (Number, street, county, State and ZIP Code) (X)

CODE

15B. CONTRACTOR/OFFEROR

(Signature of person authorized to sign)

16B. UNITED STATES OF AMERICA

(Signature of Contracting Officer)

Previous edition unusable

2. AMENDMENT/MODIFICATION NUMBER

70Z0G326QAMVER001 AMEND 1

Distribution of answers to questions submitted by vendors by 12pm (EST) on 02/12/2026

Daniel R. Larussa, Contracting Officer

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

The USCG received eight questions in reference to this solicitation (# 70Z0G326QAMVER001). Page 2 of this SF-30 contains the questions submitted by interested vendors and the answers to those questions from the USCG.

70Z0G3 70Z0G3 C5I Contract Operations Div II USCG C5ISC-MARTINSBURG, 408 Coast Guard Drive Kearneysville, WV 25430, US

70Z0G3 C5I Contract Operations Div II USCG C5ISC-MARTINSBURG, 408 Coast Guard Drive Kearneysville, WV 25430, US

70Z0G326QAMVER001

1 2

02/13/2026

02/05/2026

70Z0G326QAMVER001 AMEND 1 Questions (Q) & Answers (A)

1. Q: Is the Government open to receiving data that provides equivalent information content but uses different field names, data types, or reference code systems than those specified in Attachment 2?

A: No, we need the field names, types, and reference code systems to stay the same.

2. Q: Does the Government require the contractor to be the originating source of the data, or may the contractor aggregate and deliver data licensed from third-party providers?

A: It is not a requirement that the vendor be the originator of the data.

3. Q: Can the Government clarify the definition of “pre-maiden voyage data”? Does this refer to newbuilding data for vessels under construction, or data associated with a vessel prior to its first AMVER enrollment?

A: The manufacturer's ID until the vessel get a full registered IMO and Name, e.g., the type of engine, its expected speed, build spec. -- length, breadth, etc.

4. Q: Approximately how many unique vessels are currently maintained in the AMVER ship characteristics database?

A: 204,000

5. Q: Is data delivery currently expected via flat text files on an SFTP server, and would alternative delivery methods (e.g., API-based delivery) be acceptable if security and compliance requirements are met?

A: We require delivery via flat file to an SFTP server. API-based delivery is not feasible.

6. Q: What data rights does the Government require for the delivered data (e.g., Government Purpose Rights, Unlimited Rights, or licensed commercial use only)?

A: USCG Internal Use only

7. Q: If the awarded vendor is not the current data provider, does the Government anticipate a transition or data validation period prior to full operational use?

A: If the data meets the requirements and parameters requested the government does not expect a need for a validation period.

8. Q: Are the reference code sets specified in Attachment 2 required to be delivered exactly as listed, or may equivalent industry-standard code sets be mapped to AMVER requirements?

A: The reference code sets specified must be delivered exactly as listed.