What the software is for

To populate a Data Interchange environment with Baseline Data, use pdrBatcher by downloading to pdrMonitor

The Participant Data Replication Batcher (pdrBatcher) application is responsible for moving files between remote and local directory locations. The application is multi-threaded and allows each thread to be configured to move a subset of files between the remote and local directory locations.

A prime use for the pdrBatcher is a simple interface to wholesale market system to collect .CSV files published to a participant’s directory on the participant file server. A companion product, the Participant Data Replication Loader (pdrLoader), can parse those files into a local database instance implementing the Electricity or Gas Data Model.

You can also use pdrBatcher to submit files to the AEMO market systems processing.

AEMO Gateway Software

The AEMO Gateway software provides an AEMO‑supplied gateway that supports data exchange with the AEMO IDX Hub for power quality data using IDX patterns. It also supports current legacy data‑exchange patterns.

Purple squares with white text AI-generated content may be incorrect.
The software consolidates the existing MSATS Participant Batcher and pdrBatcher capabilities and supports interaction with the IDX patterns proposed for the BPQD interface.

5.1.1 Key features

The AEMO Gateway Software:

  • Provides standard gateway capabilities, including efficient protocol conversion.

  • Supports new participants during the transition by maintaining compatibility with legacy protocols.

  • Offers backward compatibility with payload conversion capabilities to aid change and transition management.

  • Aligns with the IDAM roadmap by software support for the latest IDAM patterns, ensuring secure and efficient identity and access management.


5.1.2 Connectivity

The connectors available to use are:

  • Event Channel Connector: Client code to establish an event notification channel (Web Sockets) for outbound messages.

  • Restful API: Includes client code for calling a Restful API.

  • File Connector: A connector to manage File-based connections (SFTP, FTP, blob storage etc.) and Integration.

  • AMQP Connector

  • Other Connectors: As per Industry requirements.

  • Support for Legacy Patterns: Support for legacy Hokey Pokey FTP file exchange patterns.

5.1.3 Payload Handling & Transformation

Payload transformation framework

  • Supports payload transformation & file compression.

  • Performs text manipulation (head, tail, replace, etc).

  • Zip/Unzip payloads.

  • Re-names the files etc.

Framework supports custom transformation modules to be plugged in.

Validation framework

  • Performs schema validations.

  • Framework supports custom Validation modules to be plugged in.

Logging

Provides intuitive file-based logging for each step performed and a flexible logging framework based on participant preference (DB etc.).

Flow-Control

Manages control mechanisms to handle Flow-Control events.

Message retrieval

Manages outbound messaging pull based on event metadata and priority configuration