Skip to content

November 2026 NRT Transition

Purpose

The November 2026 EIS introduces an updated MED-WAV NRT implementation (WAM physics update to ST6) while keeping the public filename format and product identity stable.

The operational challenge is not a new filename format; it is the double-dissemination period, during which the existing and new dataset TAGs must both be delivered.

Key milestones

Date Milestone
~06 Oct 2026 PU-MDS interface readiness gate
12 Oct 2026 internal pre-operational testing
03 Nov 2026 start double dissemination
24 Nov 2026 EIS
12 Jan 2027 end double dissemination / retire previous TAG

The exact new TAG must be confirmed from the authoritative release/PIT information before live delivery.

Delivery requirement

During double dissemination, the uploader must process two dataset/TAG targets for each production cycle.

The planned implementation treats datasets=(...) as a list and executes:

upload files -> DNT -> response

for each dataset/TAG independently.

This is safer than uploading all datasets first and processing all DNTs later because one target can fail without corrupting the state of the other.

Node parity

Both the primary HCMR node and JUNO must be able to deliver the new TAG using the production path before the operational gate is considered passed.

The readiness test should retain evidence for each node:

  • generated DNT;
  • successful response;
  • successful ingestion result;
  • remote S3/CMT listing;
  • operational log/notification evidence.

Failover during double dissemination

Double dissemination increases traffic and makes duplicate activity more dangerous.

Until the coordinator is proven, the operational plan should use an explicitly documented failover rule rather than assuming that the current progress-log mechanism provides safe automatic arbitration.

Monitoring impact

The monitoring data model must include dataset/TAG as part of the run/delivery identity. A cycle can no longer be represented only as:

date + cycle

It should instead support at least:

date + cycle + dataset/TAG + node

This prevents responses and events for the two parallel deliveries from being mixed.