NEM Energy/FCAS Bid Submission

Detects AEMO NEM dispatch bid/offer submission artefacts - the MMS bidding table vocabulary (BIDDAYOFFER, BIDOFFERPERIOD, BIDOFFERFILETRK, MNSP day-offer tables), the Dispatch Bid/Offer Submissions JSON payload fields (energyBids, fcasBids, mnspBids, rebidExplanation), and the participant FTP bid filename convention (<PARTICIPANTID>_<x>BID<x>_<timestamp>.zip/.json). Pre-dispatch bids, price bands and rebid reasoning are commercially critical trading data for market participants.

Type

regex

Engine

boost_regex

Confidence

medium

Confidence justification

Medium confidence: the table and JSON member names are highly distinctive, but the same vocabulary appears in AEMO's public MMS data-model documentation and in next-day public bid archives republished from NEMWEB. Corroborative rebid/trading keywords and absence of documentation framing raise precision; enforcement should target pre-publication submissions, not the public archive.

Jurisdictions

au

Regulations

National Electricity Rules cl 3.8 (bidding and dispatch), Competition and Consumer Act 2010 (Cth)

Frameworks

ISO 27001, SOCI Act 2018 (Cth)

Data categories

energy-market, trading, business

Scope

narrow

Risk rating

8

Platform compatibility

Purview: Compatible, GCP DLP: Unsupported, Macie: Unsupported, Zscaler: Compatible, Palo Alto: Unsupported, Netskope: Unsupported

Pattern

\b(?:BIDDAYOFFER|BIDOFFERPERIOD|BIDPEROFFER|BIDOFFERFILETRK|MNSP_DAYOFFER|MNSP_BIDOFFERPERIOD|DISPATCHOFFERTRK|PREDISPATCHOFFERTRK)\b|\b(?:energyBids|fcasBids|mnspBids|rebidExplanation)\b|(?<![A-Za-z0-9])[A-Z0-9]{3,15}_[A-Za-z0-9]*BID[A-Za-z0-9]*_[0-9]{8,14}\.(?:zip|json|tmp)(?![A-Za-z0-9])

Corroborative evidence keywords

rebid, trading day, price band, dispatch, DUID, AEMO, participant file server, self-forecast, ADPBA1, ADPMH1, ADPPV1, ADPPV2, ADPPV3, AGLHAL, AGLSOM, ALDGASF1, ANGAST1, APPIN, ARWF1, AVLSF1 (+584 more)

Proximity: 300 characters

Should match

• INSERT INTO BIDDAYOFFER (DUID, SETTLEMENTDATE, OFFERDATE) VALUES ... — MMS bidding table loader statement
• {"energyBids":[{"tradingDay":"2026-08-01","dailyEnergyConstraint":11000}],"rebidExplanation":{"reason":"plant availability change"}} — Dispatch Bid/Offer Submissions JSON payload with rebid explanation
• uploaded STANW1_FCASBIDFTP_20260801123045.zip to the Export\Bids folder — Participant FTP bid filename convention
• BIDOFFERPERIOD extract joined to PREDISPATCHOFFERTRK for the audit — 5MS bidding table names in an analysis note

Should not match

• the team submitted a competitive bid for the construction tender — Prose procurement bidding, no AEMO bidding vocabulary
• BIDDAY_REPORT_2026.xlsx attached for the sales meeting — Near-miss token that is not an AEMO bidding table or filename
• place your bids before the auction closes on Friday — Generic auction prose

Known false positives

• AEMO's public MMS data-model documentation, training material, and next-day public bid archives (NEMWEB) legitimately contain the same table names. Mitigation: Require corroborative trading keywords, and exclude documentation or tutorial framing from enforcing tiers; treat published next-day archives as public by policy scoping.
• Data Interchange schema files and pdrLoader configuration mention bidding tables without containing bid values. Mitigation: Keep confidence at medium; combine with volume/count thresholds in DLP rules so schema-only mentions do not enforce.

References

• AEMO Guide to FTP Energy, FCAS and MNSP Bids and Offers v1.00 (Aug 2021)
• AEMO MMS Data Model - BIDDAYOFFER / BIDOFFERPERIOD / BIDOFFERFILETRK