MSATS / B2B Retail Market Transaction
Detects AEMO MSATS retail-market transaction content - aseXML transaction names (CATSChangeRequest, NMIDiscoveryRequest/Response, ServiceOrderRequest/Response, MeterDataNotification), CATS change-request codes (e.g. CR1000/CR1060, CR4050/1, CR5050/1), and role-coded NMI standing data (FRMP/LNSP/MDP with an NMI). These artefacts carry customer transfer, metering and consumption context regulated under the retail market procedures.
- Type
- regex
- Engine
- boost_regex
- Confidence
- medium
- Confidence justification
- Medium confidence: aseXML transaction names are near-unique to AEMO retail market messaging; the role-acronym+NMI arm is looser and relies on proximity. Procedure documents legitimately use the same vocabulary, so enforcement needs volume thresholds or data-bearing corroboration.
- Jurisdictions
- au
- Regulations
- National Energy Retail Rules / NER Ch 7 (metering), Privacy Act 1988 (Cth)
- Frameworks
- ISO 27001
- Data categories
- energy-market, personal, business
- Scope
- narrow
- Risk rating
- 6
- Platform compatibility
- Purview: Compatible, GCP DLP: Compatible, Macie: Compatible, Zscaler: Compatible, Palo Alto: Compatible, Netskope: Unsupported
Pattern
\b(?:aseXML|CATSChangeRequest|CATSNotification|NMIDiscoveryRequest|NMIDiscoveryResponse|ServiceOrderRequest|ServiceOrderResponse|MeterDataNotification|MeterDataHistoryRequest)\b|\bCATS\s+(?:CR|change\s+request)\s*#?\s*[0-9]{4}\b|\b(?:FRMP|LNSP|MDP|ENM|RoLR)\b[\s\S]{0,80}\bNMI\b
Corroborative evidence keywords
MSATS, change request, meter data, datastream, retail transfer, standing data, B2B
Proximity: 300 characters
Should match
<ase:Transaction><CATSChangeRequest><NMI>3120000000</NMI></CATSChangeRequest>— aseXML CATS change request payloadlodge a ServiceOrderRequest so the FRMP is allocated in MSATS— B2B service order transaction nameCATS CR 1060 raised to correct the standing data— Labelled CATS change request codethe FRMP for this NMI transfers on the next business day— Role acronym in proximity to NMI
Should not match
the CR 1060 form is in the HR folder— CR code without CATS labellingsend the service order to the plumber tomorrow— Generic service-order proseFRMP is one of several market roles— Role acronym without NMI proximity or transaction vocabulary
Known false positives
- AEMO procedure documents, participant training packs and vendor integration guides quote transaction names and CR codes without customer data. Mitigation: Require corroborative keywords, use count thresholds in DLP rules, and exclude published procedure repositories by location scoping.
References
- AEMO B2B Procedure: Service Order Process v3.8
- AEMO MSATS technical guides - change requests, CATS and NMI discovery