ez2view v7.4.5.665 release notes

This is the first post in this timeline for a while, as while we’ve been releasing many updates to ez2view we haven’t kept up with the release notes. The most recent build of ez2view is v7.4.5.665, released on 6 July 2020. The main new feature is an improvement to the display of generator and interconnector MW quantities in time-travel. ez2view now shows and uses the end-of-dispatch-interval value for metered MW when available in three key widgets – Schematic, Notifications and Generation Change. In addition, the schematics have been brought up to date with the new stations in pre-production and commissioning. Since the last post here (December 2018) there have been several significant new widgets added to ez2view in other interim releases.

You can download the installer for ez2view here

(A)  About the installer

As noted here for the previous interim builds, users should be aware that this interim build has not completed the end-to-end process required for us to promote it as a major release.  Specifically:
Task #1)  All builds that we have provided to clients have passed our automated test process; but
Task #2)  We have not invested the time to run (supplementary) manual test passand
Task #3)  Neither have we (yet)updated documentation in relation to these changes, such as the dedicated online help pages specific to the widgets that have been enhanced.

As before, this interim build (v7.4.5.665) provides you early access.  You are very welcome to use this, and we would certainly appreciate any feedback you can provide on that basis.  However, please keep in mind that it has (deliberately) not had Task #2 and Task #3 completed yet.

(B)  End-of-interval metered MW data – new in v7.4.5.665

This is explored in more detail on WattClarity here.

The specific widgets updated are the Schematics, Notifications (for the generation-change and generation on/off notifications), and the Gen Change widget.

This update addresses a long-standing confusion many users found between displayed MW generation quantities at the start and end of a dispatch interval. This was most evident in time-travel mode in the schematic widgets. A dispatch (5-minute) or trading (30-minute) interval is referred to by its “ending” time – so 10:10 means the 5-minute period between 10:05 and 10:10, where the 10:10 dispatch instruction is published by AEMO at around 10:05. The 10:30 trading interval is 10:00 to 10:30, including the 10:05 to 10:30 dispatch intervals. The diagram below shows how ez2view moves through a dispatch interval.

Not all data is available in real-time for each dispatch interval. The total MW dispatched across regions, the target interconnector flows and the dispatch prices are all available, as these are calculated by the dispatch process on a forecast for the end of the 5 minute period, but the actual generation and metered interconnector flows aren’t available – as they haven’t happened yet! The best we can do in ez2view is provide the “initial” value – which is a snapshot of the measured value at the very end of the previous interval.


ez2view also has a “time-travel” mode that takes the data (forecasts included) back to a point in time. There’s more detail on that here. When travelling back in time to dig into what really went on, providing the “initial” value like this for the generation quantity can be confusing, as usually we’d want to know what happened during that interval, with reference to the prices for that interval, not what happened during the one before.

Version v7.4.5.665 of ez2view addresses this by providing the most up-to-date information available. In the Schematics widgets in real-time mode it now displays the “initial” value for generation, and when time-travelled the “final” value, which is the generation snapshot at the end of the interval. The “initial” value is shown in grey to indicate it’s preliminary, while the “final” value is displayed in black. In the tooltips (the detail that pops up when hovering over a data point) the generation data is further labelled with “(start)” or “(end)” to indicate which value it is. This approach then spills over into the Generation-Change widget (listing the most significant movements of generators), and the notifications on generation change, so that these widgets show what changed during the interval.

Here’s how it looks in real-time – note that the MW are shown in grey as they are the start-of-interval values for 15:50:

and the previous interval (15:45) in time-travel mode, showing the end-of-interval values in black, and in the notification noting the change is to the end of the interval:

In addition, we’re making more interconnector information available. Throughout ez2view (and in AEMO’s MMS database), the interconnector target flow (i.e. what the dispatch process would like the interconnector to do) is referred to as “Flow”. However, this often isn’t what actually happened, as generation and demand across the regions can turn out not quite as dispatched. The metered MW data (the actual flow) for interconnectors is now available in ez2view through the tooltips in the schematic widgets (hover over the interconnector to see the text pop up). This metered MW data has the same initial / final issue as the generation data, and so is also shown with “(start)” or “(end)” next to it.

(C)  Other new widgets, added before v7.4.5.665

Other widgets new since December 2018 worth checking out (search for them in the search bar in ez2view explorer when adding new widgets):

  • Forecast Convergence – a graphical representation of the evolution of forecasts of demand, price, available generation, intermittent generation, constraints and more.
  • Unit Dashboard – enter the DUID in the ez2view explorer search bar, and choose the corresponding “Unit Dashboard”, to see a dashboard-like view of recent generation performance.
  • NEM Prices (Beta) – including FCAS prices and both settlement and physical prices during intervention pricing.
  • Swim Lanes – build your own table of key values to monitor over a short timeframe.

Give us a call (+61 7 3368 4064) to discuss other improvements we’re working on in 2020.