INT153 - Demand Forecast

Trigger type	Event triggered
Published	Production of nodal demand forecast
Audience	Public
Output file name	int153_v[n]_demand_forecast_rpt_[p]~yyyymmddhhmmss.csv

Report purpose

This report is created each time AEMO Australian Energy Market Operator generates and saves a demand forecast. Note this may occur many times prior to the running of a schedule as AEMO tests the feasibility of the different variables used in a schedule. The report provides:

• the total uncontrollable withdrawal quantity that may be used as input in the production of a schedule

• the quantity (positive or negative) by which AEMO deems it necessary to adjust Market participant submissions in order to maintain system security.

Participants may use this report to gauge AEMO’s schedulers view of the current day situation and whether the aggregate of all Participants demand forecasts sum to an adequate demand value and/or profile given AEMO’s perspective of the system demands of the gas day.

Audience notes

As not every saved forecast demand generated is used in the scheduling process, Market participants need to reference INT108 Schedule Run Log to determine which Demand The amount of power consumed at any time Forecast was actually used in scheduling.

The INT108 forecast_demand_version will specify which INT053 rows will provide information that was used by AEMO in its scheduling processes.

Content notes

This report is generated each time AEMO generates and saves a demand forecast. Each report provides details of all the demand forecasts created up to the report generation time on the current gas day.

A given report may contain demand forecasts that are for:

• the current day

• 1 day ahead

• 2 days ahead

• 3 days ahead

By comparing the forecast_date with the current_date, users will be able to determine the type of forecast for a particular forecast (version_id) (i.e. whether it is for the current day or a day ahead schedule)

Each row in a report provides the forecast demand and the AEMO override (in GJ Gigajoule: a unit of measure of energy equal to 10 to the power 9 joules.) for the specified hour of the gas day of the specified demand forecast. Therefore, there will be 24 rows in the report for each demand forecast.

Data content

Name	Data Type	No Nulls	Primary Key	CQ	Comments
forecast_date	varchar 20	True	True	N	gas date of forecast e.g. 30 Jun 2007
version_id	integer	True	True	N	Forecast version used to identify which forecast was used in the schedule (reference INT108)
ti	integer	True	True	N	Time interval (1-24)
forecast_demand_gj	integer	True	False	Y	forecast total hourly demand (in GJ/hour) potentially used as input in the MCE
vc_override_gj	integer	False	False	Y	Quantity (in GJ) of nay AEMO override (can be either positive or negative)
current_date	varchar 20	True	False	N	Date and time report produced.