Table: BIDOFFERFILETRK

BIDOFFERFILETRK

Name

BIDOFFERFILETRK

Comment

BIDOFFERFILETRK shows an audit trail of all files submitted containing ENERGY/FCAS/MNSP bid, including corrupt bids and rebids.


Description

BIDOFFERFILETRK data is confidential to the submitting participant.

The new ancillary service arrangements require availability and prices for each Frequency Control Ancillary Service to be bid on a similar basis to energy. Three new tables facilitate ancillary service bidding. The new tables (BIDOFFERFILETRK, BIDDAYOFFER and BIDOFFERPERIOD) are similar in structure to energy bidding tables (OFFERFILETRK, DAYOFFER and PEROFFER). The significant differences with the new tables are.

· The OFFERDATE field reflects the time the bid was loaded and this field alone provides the key for versioning of bids. The VERSIONNO field is retained for participant use as information only.

· The new tables support bids for multiple services. The BIDTYPE field defines the service to which the bid applies.

· There are no default bids. In the absence of a bid for a specific settlement date, the latest bid submitted for a previous settlement date applies.

Source

This data is updated as bids are processed. It includes all bids submitted including corrupt bids.

Volume

Approximately 100,000 records per year

Note

Confirmation is via CSV bid acknowledgement file


Primary Key Columns

Name

FILENAME


Primary Key Columns

Name

OFFERDATE

PARTICIPANTID


Index Columns

Name

LASTCHANGED


Content

Name

Data Type

Mandatory

Comment

PARTICIPANTID

VARCHAR2(10)

X

Unique participant identifier

OFFERDATE

TIMESTAMP(3)

X

Time this bid was processed and loaded

FILENAME

VARCHAR2(80)

X

Submitted file name

STATUS

VARCHAR2(10)

 

Load status [SUCCESSFUL/CORRUPT]

LASTCHANGED

DATE

 

Last date and time record changed

AUTHORISEDBY

VARCHAR2(20)

 

Participant agent who created the Offer

AUTHORISEDDATE

DATE

 

When the Offer was processed - synonymous with LastChanged

TRANSACTION_ID

VARCHAR2(100)

 

A GUID used to identify the submission transaction in AEMOs systems

REFERENCE_ID

VARCHAR2(100)

 

A participant provided reference, which is required to be unique per submission (for a PARTICIPANTID)

SUBMISSION_TIMESTAMP

DATE

 

The participant provided date/time for the submission

COMMENTS

VARCHAR2(1000)

 

A participant provided comment

SUBMISSION_METHOD

VARCHAR2(20)

 

Method by which this submission was made typically FTP, API, WEB