Known Limitations with the ‘Transition Release’ of ez2view on 27th May 2024

On Monday 27th May 2024 we published this Release Note about the ‘ez2view ‘Transition Release’ in preparation for IESS’.

Because that note was already long enough (and hence to aid in readability), we have posted this separate article about the Known Limitations with the Transition Release of ez2view on 27th May 2024′ at the same time.


What you will see

Your ‘Transition Release’ copy of ez2view will have this banner displayed in the top-right of the application:

That link in the software will link through the the Release Notes above, from which you can navigate through to this list of known limitations.


Listing of known limitations

In this section we describe some of the ‘known limitations’ alluded to in this banner message.

Immediately following the release of this Transition Release, we are continuing the development of ez2view to address these limitations and add in other functionality. As noted above, these will be progressively released here as v9.9.4.*.

Known Limitations Details of the Known Limitations in with v9.9.3.351
Predispatch bids in real time not displayed from Private Data Our testing has belatedly (on Mon 27th May 2024) uncovered that real-time display of bids in predispatch (i.e. for those clients pointing ez2view to a Private MMS:

  • Will display real-time bids for the current Market Day;
  • But won’t display the bids in Predispatch.


Note that this issue was already rectified from v9.9.4.7 as described in the note ‘Enhancements already made, beyond the Transition Release of ez2view’.

You will need to install the ‘Latest & Greatest’ to access this.

Temporary double-counting of Maximum Capacity for existing batteries. There is likely to be a short period (i.e. the duration where both forms of DUIDs are registered for batteries in AEMO systems as they transition from 2 DUIDs to 1 DUIDs) where Maximum Capacity for existing batteries will be double counted.  This will appear in places like:

  • ‘Station Dashboard’ widget (where Maximum Capacity scales the chart)
  • ‘Schematics’ widgets (where Maximum Capacity scales the chart)

Note that:

  • This is a special case that we decided not to try to write code to deal with what might arise, given some uncertainties about the AEMO’s planned transition process.
  • From what we know of the AEMO’s intended transition process, it seems that this temporary period will be different for each of the 26 x batteries that have to transition…

On 8th May 2024, the AEMO advised us:

‘While registrations for new BDUs can technically begin from the IESS Rule effective date, i.e., 3 June 2024, the first BDU registration is not expected until the end of June 2024 at the earliest. This means that while the changes to the production environment to cater for registrations will be in the system, the first BDU will not be seen in the environment until the end of June. Existing BESS that must cutover from the current two-DUID model to the single BDU DUID model will begin from mid-July (26 batteries transitioning through March 2025), from which time they will also start to appear in production’

… so (for instance) this period might last from end-of-June to mid-July for the first batteries to transition.


Note that (on 16th June) we published an update in ‘What to expect (in ez2view) when bi-directional units emerge’.

Bid Stack for BDUs for Regulation FCAS bids Under IESS, BDUs submit two bids (Gen and Load side) for Raise and Lower Regulation FCAS services.

Whilst this is consistent with their bidding behaviour while registered as two DUIDs (G, L) the information published in dispatch for “Actual Availability” for FCAS enablement is now a single value rather than one for Gen side and Load side.

Note that:

  • We have as yet been unable to verify how to apply that single availability number across both sides of the bid – a step we take on our way to presenting a bid stack as it was dispatched (visible in our various bid focused widgets, plus the Unit Dashboard).
  • We are following this up under GR Case 6755.

As a result our transitional implementation for presenting Regulation Bid Stacks is intentionally simplified.

  • We have been able to find a small number of intervals in the (admittedly unreliable) pre-prod MMS data that suggest our transitional implementation logic is incorrect, but in the absence of a better solution, have decided to release it as per the above in the transition release.
  • We are aiming to clarify the logic by which BDUs Regulation Bids are combined and release an improved implementation in our next release
Export to CSV
temporarily disabled
in ‘Bids & Offers’ widget
In the same way as noted below for the ‘Bid Details’ widget, the ‘Export Data’ menu items are temporarily disabled while we update logic to account for BDUs.

This has been noted by clients as:

  • GR Case 6782
‘Bids Details’ widget On the Chart tab within this widget:

  • The ‘Export Data’ menu items are temporarily disabled while we update logic to account for BDUs

On the Table within this widget:

  • Still shows “raw” volumes as bid, so Loads get positive volumes and Availability – which is inconsistent with their negatively signed counterparts in the Chart tab.

For BDUs with this ‘Transition Release’ we know:

  • The Single Bid View only allows the viewing of a single bid direction at a time. This decision was taken so as to preserve the current bid comparison capability – which assumes 10 price bands only.
  • Will only show the Gen side of the bid:
    • For ENERGY bids
    • For FCAS bids

In both cases, this limitation will be highlighted in an informational banner at the top of the Single Bid and Bid Comparison widgets for Bids of those types.

‘Unit Dashboard’ widget With this widget, there are a number of enhancements not yet completed for the ‘Transition Release’, including:

  • Some data points (e.g. ‘Target + Raise’ and ‘Spare’) have been temporarily removed from the table pending fuller scoping for bi-directional units.
  • Ramp rates have been removed temporarily, as we implement the capability to show the correct ramp rate – whether this is from the bid or (on some occasions) from the SCADA system.
    • This was requested by a client (GR Case 6092).
    • Note that the ramp rate in the bid can still be accessed from this widget by clicking through to the specific Offer Date link to the Bid Details widget.
  • We have had client requests for our estimation of ‘Conformance Status’ to be overwritten if the data in the EMMS for that unit is accessible in that copy of ez2view.  This has not yet been implemented.

More generally we have larger enhancements to this widget sketched out that will be pursued, now that this ‘Transition Release’ has been made available.

Because this work has not yet been finalised, we’ve not yet updated the Help Page for this widget.

‘Station Dashboard’ widget In the ‘Transition Release’ this widget remains closely related to the ‘Unit Dashboard’ widget.

However, we have sketched designs that would take this (aggregate-level) widget in a different direction, and hence allow it to be used for any {user filtered} aggregate view of units.  For instance, this might be applied to Aggregate Dispatch Groups (ADG).

Also note that the re-naming of this widget (i.e. from ‘Station Details’ to ‘Station Dashboard’) has not been fully completed.

Because this work has not yet been finalised, we’ve not yet updated the Help Page for this widget.

‘Constraint Dashboard’ widget We have other work sketched out to make the direction of ‘contribution’ clearer (especially for BDUs) … this has not yet been implemented.

As such, known limitations include:

  • BDUs only show their Gen side Availability
  • BDUs can show a negative target against a positive availability (always Gen side).
  • Target / Available column uses an incorrect MaxCapacity for BDUs, which causes the bar chart within that cell to be scaled incorrectly.

Because this work has not yet been finalised, we’ve not yet updated the Help Page for this widget.

Trends Engine In the note ‘April 2024 (starting) enhancements to ‘Trends Engine’ inside of ez2view, in preparation for IESS’ we explained that we’d implemented some of the changes we have identified.



Note that Trends has been further enhanced, as described in the note ‘Enhancements already made, beyond the Transition Release of ez2view’.

‘Swim Lanes’ Widget For this widget:

  • Data shown does not include load side availability for BDUs
  • Always presents the Gen side for selection “Availability MW”
  • Initial and Target might show wrong sign for BDUs
‘NEM Map’ Widget For this widget there are some questions we have not yet fully resolved about what we should do when certain DUIDs present with negative values for InitialMW (i.e. in terms of the fuel type aggregates).

We also have an open question about whether we should be adding Aggregated Load as a Metric.

Fuel Type for DC-coupled hybrid (If and) when the DC-coupled hybrid units appear in the AEMO data, any of the pre-existing fuel types won’t be an accurate match for their fuel type.

So they will, at present implementation, be added as Fuel Type = “Other”.

No ‘CPD Price’ during certain OCD periods Because of the complexity of the dispatch process during Over-Constrained Dispatch (OCD), the required data to calculate the CPD Price for DUIDs:

  • Is not wholly available in the EMMS, even next day
  • But can be calculated (on most occasions) from other data the AEMO publishes on a next-day basis.

A non-trivial amount of development effort is required to make this data available to ez2view clients on a ‘next day public’ basis.

This development work was deferred whilst we worked on the ez2view ‘Transition Release’ for IESS.  With its release, this work can be assigned a priority in amongst other other development initiatives.

‘NEM Summary Stats’ Widget Emissions by region chart will be wrong if a BDU is charging (consuming therefore negative intialMW) and has a non-zero emission factor (would reduce aggregate emissions).

Loads having emission factors would also make the total wrong.

However, we have broader questions about the usefulness of this particular widget.

‘[REGION] Summary Stats’ Widgets The ‘Zonal Generation’ data in the trends in this widget does not yet include the output of BDUs in the aggregation.

However, we have broader questions about the usefulness of this particular widget.


The above list is not comprehensive (though long), but is aimed to give clients some idea of what we’re aware about, as at Monday 27th May 2024 with the release of the ez2view ‘Transition Release’ for IESS.