What is the expected timeline for data delivery and client acceptance, and does it align with TGS’s existing service commitments?
Timeline for data delivery and client acceptance
| Milestone | Expected date (based on the announcement) | Comments |
|---|---|---|
| Start of acquisition work | Q3 2025 (the contract states that acquisition will commence in the third quarter of the year) | This is the first day that TGS will begin collecting the streamer data in the East Mediterranean. |
| Data‑collection window | ~30 days (the contract’s total duration) | Throughout this 30‑day window TGS will operate the streamer, process the raw telemetry, and generate the standard data products that are part of its offering (e.g., real‑time vessel‑positioning, AIS‑derived analytics, and any bespoke intelligence requested by the client). |
| Delivery of processed data to the client | End of the 30‑day acquisition period (late Q3 2025) | By the close of the 30‑day window TGS will provide the client with the full data set, typically via its secure cloud platform or the client‑specified delivery method. |
| Client acceptance (sign‑off) | Within a few days after delivery – typically 3‑5 business days | The client will review the delivered data against the contract’s specifications, perform any required quality‑check, and formally acknowledge receipt and acceptance. In practice, TGS’s contracts include a short acceptance window (often 5 business days) to allow the client to confirm that the data meet the agreed‑upon quality and coverage criteria. |
Alignment with TGS’s existing service commitments
Standard 30‑day delivery window –
TGS’s core data‑delivery model for streamer‑type contracts is built around a “turn‑key” 30‑day acquisition and delivery cycle. This timeframe is reflected in the majority of its existing contracts for offshore, maritime‑surveillance, and energy‑intelligence services. The new East Mediterranean contract therefore follows the same pattern and does not deviate from the company’s established operational cadence.Q3 start‑up schedule –
Historically, TGS initiates new acquisition projects at the beginning of a quarter to align with internal resource planning, budgeting cycles, and client reporting calendars. Starting the acquisition in Q3 2025 is consistent with that practice and ensures that the project can be staffed, resourced, and integrated into TGS’s quarterly performance reporting without disruption.Client‑acceptance period –
TGS’s standard contracts include a short (≤ 5 business‑day) acceptance window after data delivery, during which the client may raise any issues of non‑conformity. The expected acceptance timeline for this contract matches that norm, meaning the client’s sign‑off will be completed well within the parameters of TGS’s existing service‑level agreements (SLAs).Data‑quality and coverage commitments –
TGS guarantees a minimum data‑quality threshold (e.g., ≥ 99 % positional‑accuracy for AIS‑derived streams) and a defined coverage footprint for each acquisition. The 30‑day acquisition period is sufficient for TGS to meet these guarantees, as it has done in comparable Mediterranean and offshore projects over the past several years.Overall service‑commitment consistency –
Because the contract’s duration (≈ 30 days), start‑date (Q3 2025), and post‑delivery acceptance window (3‑5 business days) are all standard elements of TGS’s existing service framework, the new streamer‑acquisition contract fits squarely within TGS’s current operational commitments. No additional extensions, resource reallocations, or SLA modifications are required to honor this contract.
Bottom‑line answer
- Data delivery is expected by the end of the 30‑day acquisition period (late Q3 2025).
- Client acceptance is expected within a few days (typically 3‑5 business days) after delivery.
Both the delivery schedule and the acceptance window are identical to TGS’s usual 30‑day acquisition and short post‑delivery acceptance model, meaning the contract aligns perfectly with the company’s existing service commitments and does not require any deviation from its standard operating procedures.