{"type": "object", "properties": {"OFFERDATE": {"type": "string", "format": "date-time", "description": "Time this bid was processed and loaded"}, "PARTICIPANTID": {"type": "string", "description": "Unique participant identifier"}, "AUTHORISEDBY": {"type": "string", "description": "Participant agent who created the Offer"}, "AUTHORISEDDATE": {"type": "string", "examples": ["2026/01/20 00:05:00"], "format": "date-time", "description": "When the Offer was processed - synonymous with LastChanged\nWARNING: Despite what the name suggests, this is a datetime, not a date."}, "COMMENTS": {"type": "string", "description": "A participant provided comment"}, "FILENAME": {"type": "string", "description": "Submitted file name"}, "LASTCHANGED": {"type": "string", "examples": ["2026/01/20 00:05:00"], "format": "date-time", "description": "Last date and time record changed"}, "REFERENCE_ID": {"type": "string", "description": "A participant provided reference, which is required to be unique per submission (for a PARTICIPANTID)"}, "STATUS": {"type": "string", "description": "Load status [SUCCESSFUL/CORRUPT]"}, "SUBMISSION_METHOD": {"type": "string", "description": "Method by which this submission was made typically FTP, API, WEB"}, "SUBMISSION_TIMESTAMP": {"type": "string", "examples": ["2026/01/20 00:05:00"], "format": "date-time", "description": "The participant provided date/time for the submission"}, "TRANSACTION_ID": {"type": "string", "description": "A GUID used to identify the submission transaction in AEMOs systems"}}, "required": ["OFFERDATE", "PARTICIPANTID", "FILENAME"], "description": "BIDOFFERFILETRK shows an audit trail of all files submitted containing ENERGY/FCAS/MNSP bid, including corrupt bids and rebids.\nBIDOFFERFILETRK data is confidential to the submitting participant.\n\nThe new ancillary service arrangements require availability and prices\nfor each Frequency Control Ancillary Service to be bid on a similar\nbasis to energy. Three new tables facilitate ancillary service bidding.\nThe new tables (BIDOFFERFILETRK, BIDDAYOFFER and BIDOFFERPERIOD) are\nsimilar in structure to energy bidding tables (OFFERFILETRK, DAYOFFER\nand PEROFFER). The significant differences with the new tables are.\n\n\u00b7 The OFFERDATE field reflects the time the bid was loaded and this\nfield alone provides the key for versioning of bids. The VERSIONNO field\nis retained for participant use as information only.\n\n\u00b7 The new tables support bids for multiple services. The BIDTYPE field\ndefines the service to which the bid applies.\n\n\u00b7 There are no default bids. In the absence of a bid for a specific\nsettlement date, the latest bid submitted for a previous settlement date\napplies.\n\nSource\n\nThis data is updated as bids are processed. It includes all bids\nsubmitted including corrupt bids.\n\nVolume\n\nApproximately 100,000 records per year\n\nNote\n\nConfirmation is via CSV bid acknowledgement file"}