NEM Rebid Log Book Entry or Late-Rebid Contemporaneous Record

Internal NEM trading-desk rebid records: trading log / log book entries and the late-rebid contemporaneous record that a Generator must make under NER cl 3.8.22(ca). These entries carry the material conditions behind a rebid, the event, aware and decision times (AER Rebidding and Technical Parameters Guideline s 3.4 fields eventTime, awareTime, decisionTime), the P/A/F/E rebid category and the fuller narrative behind a published "SL" / "see log" rebid reason. Distinct from au-nem-bid-file, which detects AEMO MMS bid tables, Dispatch Bidding API JSON keys and bid filenames; this classifier covers the trader's reasoning record, which is never published.

Type: regex
Engine: boost_regex
Confidence: medium
Confidence justification: Medium: the phrases come from NER cl 3.8.22(ca) and the AER guideline and also appear in that guideline, AER enforcement material and training decks, so enforce tiers require populated log fields (clock-valued event/aware/decision times or the published HHMM~category~ reason form). The HHMM~category~ form also appears in next-day public bid data, which is excluded only when the AEMO PUBLIC header or bid table marker is within the window, so extracts pasted without headers can reach 75. 85/75 are heuristic evidence tiers, not measured accuracy.
Jurisdictions: au
Regulations: National Electricity Rules, AER Rebidding and Technical Parameters Guideline (October 2024), Security of Critical Infrastructure Act 2018 (Cth)
Frameworks: ISO 27001
Data categories: energy-market, trading, business
Scope: narrow
Risk rating: 8
Platform compatibility: Purview: Compatible, GCP DLP: Compatible, Macie: Compatible, Zscaler: Compatible, Palo Alto: Degraded, Netskope: Unsupported

Pattern

(?i)\b(?:rebid\s+(?:log|reason|record|narrative)|late\s+rebid(?:ding)?(?:\s+period)?|contemporaneous\s+record|trading\s+log(?:\s+book)?|log\s+book\s+entry|see\s+log|(?:bidding|offer)\s+strategy)\b

Corroborative evidence keywords

DUID, price band, pre-dispatch, RRP, dispatch interval, trading interval, MAXAVAIL, rebid

Proximity: 300 characters

Should match

Trading log book entry - Callide Ridge Power Station DUID: CRIDGE2 Event time: 14:02:00 Aware time: 14:04:30 Decision time: 14:06:00 Category: A Material conditions: 30MIN PD RRP for QLD1 interval ending 1430 fell from $412 to $96 after the 1400 run; shifted 180 MW from price band 9 to band 3. Rebid reason submitted: 1402~A~PD price lower than forecast - SL — Populated log entry with event, aware and decision times plus DUID and price band - intended 85
Late rebid contemporaneous record Trader: Casey Teston Aware time: 16:41 Decision time: 16:44 Conditions: unit 2 mill C trip reduced available capacity to 310 MW; rebid 60 MW into band 10 for the 1700 dispatch interval. — Late-rebidding-period contemporaneous record with aware and decision times and dispatch interval - intended 85
Rebid log 23/09/2026 - Northbank Energy 0915~P~Boiler tube leak unit 1 reduced capacity to 240MW - SL Narrative: operator reported rising drum level alarm, maintenance confirmed leak at 0909. — Rebid log line in the HHMM~category~ form with a see-log suffix - intended 75
Contemporaneous record for rebid at 05:47 Category: F The desk moved volume to the price floor after the counterparty cap position was recalculated overnight; reviewed by the trading manager. — Contemporaneous record with a populated category field - intended 75

Should not match

Rebidding and Technical Parameters Guideline. 3.4 Form of rebid. The eventTime, category, reason, awareTime and decisionTime fields should be submitted in the following form: eventTime the time, in 24-hour format (HHMMSS). Relevant participants should record further information in their log book and include see log or SL in the rebid reason. A contemporaneous record must be made for a rebid in the late rebidding period. — Published AER guideline text naming the fields without values
C,NEMP.WORLD,BIDMOVE_COMPLETE,AEMO,PUBLIC,2026/09/24,04:42:10 I,BID,BIDDAYOFFER_D,3,SETTLEMENTDATE,DUID,BIDTYPE,PARTICIPANTID,REBIDEXPLANATION D,BID,BIDDAYOFFER_D,3,2026/09/23,CRIDGE2,ENERGY,NBEXAMPLE,"0915~P~Boiler tube leak - SL" — Next-day public BIDMOVE file with AEMO PUBLIC header and a published rebid reason
Rebid log template Event time: __:__ Aware time: __:__ Decision time: __:__ Category (P/A/F/E): ____ Rebid reason: ______________ — Blank rebid log template
Training exercise: write a contemporaneous record for a late rebid. Record the aware time and decision time and explain the material conditions and circumstances. Answers are discussed in the session. — Training material without populated values
The AER has commenced proceedings alleging a generator's late rebid reasons were false or misleading, the regulator said in a media release on Tuesday. — News / enforcement media release

Known false positives

The AER Rebidding and Technical Parameters Guideline and AER enforcement reports and media releases quote the field names and example rebid reasons. Mitigation: Enforce tiers require clock-valued time fields or a category field; the guideline title, AER reports and media releases are excluded within the proximity window.
AEMO next-day public bid files (BIDMOVE_COMPLETE, Yesterdays_Bids_Reports) carry published rebid reasons in the HHMM~category~ form. Mitigation: The ",AEMO,PUBLIC," header, PUBLIC_BIDMOVE filename and I,BID,BIDDAYOFFER_D table marker are excluded; header-less extracts can still reach 75.
Blank log templates and training exercises. Mitigation: Placeholder clock values (__:__) do not satisfy the time-field regex and the template-exclusion dictionary applies to every tier.