{"CONFIGURATION": {"comment": "MMS Data Model Configuration Management and Control", "table_names": ["MMS_DATA_MODEL_AUDIT"]}, "ANCILLARY_SERVICES": {"comment": "Ancillary Service Contract Data", "table_names": ["CONTRACTAGC", "CONTRACTLOADSHED", "CONTRACTREACTIVEPOWER", "CONTRACTRESTARTSERVICES", "CONTRACTRESTARTUNITS"]}, "ASOFFER": {"comment": "Offer data for Ancillary Service Contracts", "table_names": ["OFFERAGCDATA", "OFFERASTRK", "OFFERLSHEDDATA", "OFFERRESTARTDATA", "OFFERRPOWERDATA"]}, "BIDS": {"comment": "Energy and Market Based FCAS Offers", "table_names": ["BIDDAYOFFER", "BIDDAYOFFER_D", "BIDOFFERFILETRK", "BIDOFFERPERIOD", "BIDPEROFFER_D", "MNSP_BIDOFFERPERIOD", "MNSP_DAYOFFER", "MTPASA_OFFERDATA", "MTPASA_OFFERFILETRK"]}, "BILLING_CONFIG": {"comment": "Configuration data for the Billing Process", "table_names": ["BILLINGCALENDAR", "GST_BAS_CLASS", "GST_RATE", "GST_TRANSACTION_CLASS", "GST_TRANSACTION_TYPE", "SECDEPOSIT_INTEREST_RATE", "SECDEPOSIT_PROVISION"]}, "BILLING_RUN": {"comment": "Results from a published Billing Run. The settlement data and billing run data are updated daily between 6am and 8am for AEMO's prudential processes. In a normal week, AEMO publishes one PRELIM, one FINAL and two REVISION runs in addition to the daily runs.Each billing run is uniquely identified by contract year, week no and bill run no.", "table_names": ["BILLING_APC_COMPENSATION", "BILLING_APC_RECOVERY", "BILLING_CASHSEC_INTEREST_PAY", "BILLING_CO2E_PUBLICATION", "BILLING_CO2E_PUBLICATION_TRK", "BILLING_DAILY_ENERGY_SUMMARY", "BILLING_DIR_FINAL_AMOUNT", "BILLING_DIR_FINAL_RECOVERY", "BILLING_DIR_PROV_AMOUNT", "BILLING_DIR_PROV_RECOVERY", "BILLING_DIR_RECOVERY_DETAIL", "BILLING_DIRECTION_RECON_OTHER", "BILLING_EFTSHORTFALL_AMOUNT", "BILLING_EFTSHORTFALL_DETAIL", "BILLING_ENERGY_GENSET_DETAIL", "BILLING_ENERGY_TRAN_SAPS", "BILLING_ENERGY_TRANSACTIONS", "BILLING_FCAS_REG_AMT", "BILLING_FCAS_REG_RESIDAMT", "BILLING_FPP", "BILLING_GST_DETAIL", "BILLING_GST_SUMMARY", "BILLING_IRSR_NSP_ALLOCATION", "BILLING_NMAS_MANUAL_PAYMENT", "BILLING_NMAS_MANUAL_RECOVERY", "BILLING_NMAS_TST_PAYMENTS", "BILLING_NMAS_TST_RECOVERY", "BILLING_NMAS_TST_RECVRY_RBF", "BILLING_NMAS_TST_RECVRY_TRK", "BILLING_SECDEP_INTEREST_PAY", "BILLING_SECDEP_INTEREST_RATE", "BILLING_SECDEPOSIT_APPLICATION", "BILLING_SUBST_DEMAND", "BILLING_SUBST_RUN_VERSION", "BILLING_WDR", "BILLING_WDR_DETAIL", "BILLINGAPCCOMPENSATION", "BILLINGAPCRECOVERY", "BILLINGASPAYMENTS", "BILLINGASRECOVERY", "BILLINGDAYTRK", "BILLINGFEES", "BILLINGFINANCIALADJUSTMENTS", "BILLINGINTERRESIDUES", "BILLINGINTRARESIDUES", "BILLINGIRAUCSURPLUS", "BILLINGIRAUCSURPLUSSUM", "BILLINGIRFM", "BILLINGIRNSPSURPLUS", "BILLINGIRNSPSURPLUSSUM", "BILLINGIRPARTSURPLUS", "BILLINGIRPARTSURPLUSSUM", "BILLINGPRIORADJUSTMENTS", "BILLINGREALLOC", "BILLINGREALLOC_DETAIL", "BILLINGREGIONEXPORTS", "BILLINGREGIONFIGURES", "BILLINGREGIONIMPORTS", "BILLINGRUNTRK", "BILLRESERVETRADERPAYMENT", "BILLRESERVETRADERRECOVERY", "BILLWHITEHOLE"]}, "DEMAND_FORECASTS": {"comment": "Regional Demand Forecasts and Intermittent Generation forecasts.", "table_names": ["DEMANDOPERATIONALACTUAL", "DEMANDOPERATIONALFORECAST", "INTERMITTENT_CLUSTER_AVAIL", "INTERMITTENT_CLUSTER_AVAIL_DAY", "INTERMITTENT_DS_PRED", "INTERMITTENT_DS_RUN", "INTERMITTENT_GEN_FCST", "INTERMITTENT_GEN_FCST_DATA", "INTERMITTENT_GEN_FCST_P5_PRED", "INTERMITTENT_GEN_FCST_P5_RUN", "INTERMITTENT_GEN_FCST_PRED", "INTERMITTENT_GEN_FCST_RUN", "INTERMITTENT_GEN_LIMIT", "INTERMITTENT_GEN_LIMIT_DAY", "INTERMITTENT_GEN_SCADA", "INTERMITTENT_P5_PRED", "INTERMITTENT_P5_RUN", "MTPASA_INTERMITTENT_AVAIL", "MTPASA_INTERMITTENT_LIMIT", "PERDEMAND", "RESDEMANDTRK", "ROOFTOP_PV_ACTUAL", "ROOFTOP_PV_ACTUAL_PRED", "ROOFTOP_PV_ACTUAL_RUN", "ROOFTOP_PV_FCST_P5_PRED", "ROOFTOP_PV_FCST_P5_RUN", "ROOFTOP_PV_FCST_PRED", "ROOFTOP_PV_FCST_RUN", "ROOFTOP_PV_FORECAST"]}, "DISPATCH": {"comment": "Results from a published Dispatch Run", "table_names": ["CONSTRAINTRELAXATION_OCD", "DISPATCH_AGC_DATA", "DISPATCH_CONSTRAINT_FCAS_OCD", "DISPATCH_FCAS_REQ_CONSTRAINT", "DISPATCH_FCAS_REQ_RUN", "DISPATCH_INTERCONNECTION", "DISPATCH_LOCAL_PRICE", "DISPATCH_MNSPBIDTRK", "DISPATCH_MR_SCHEDULE_TRK", "DISPATCH_PRICE_REVISION", "DISPATCH_ROOFTOP_PV_FCST_TRK", "DISPATCH_UNIT_CONFORMANCE", "DISPATCH_UNIT_SCADA", "DISPATCHBLOCKEDCONSTRAINT", "DISPATCHCASESOLUTION", "DISPATCHCONSTRAINT", "DISPATCHINTERCONNECTORRES", "DISPATCHLOAD", "DISPATCHOFFERTRK", "DISPATCHPRICE", "DISPATCHREGIONSUM", "INTERMITTENT_FORECAST_TRK", "NEGATIVE_RESIDUE"]}, "FORCE_MAJEURE": {"comment": "Market Suspensions and administer pricing event data", "table_names": ["APEVENT", "APEVENTREGION", "IRFMAMOUNT", "IRFMEVENTS", "MARKET_SUSPEND_REGIME_SUM", "MARKET_SUSPEND_REGION_SUM", "MARKET_SUSPEND_SCHEDULE", "MARKET_SUSPEND_SCHEDULE_TRK", "OVERRIDERRP", "REGIONAPC", "REGIONAPCINTERVALS"]}, "GD_INSTRUCT": {"comment": "General Dispatch Instruction data", "table_names": ["GDINSTRUCT", "INSTRUCTIONSUBTYPE", "INSTRUCTIONTYPE"]}, "GENERIC_CONSTRAINT": {"comment": "Generic Constraint Standing Data and Invocations", "table_names": ["EMSMASTER", "GENCONDATA", "GENCONSET", "GENCONSETINVOKE", "GENCONSETTRK", "GENERICCONSTRAINTRHS", "GENERICEQUATIONDESC", "GENERICEQUATIONRHS", "PASA_CONTINGENCY_DEFINITION", "SPDCONNECTIONPOINTCONSTRAINT", "SPDINTERCONNECTORCONSTRAINT", "SPDREGIONCONSTRAINT"]}, "IRAUCTION": {"comment": "Inter-regional Residue Auction data", "table_names": ["AUCTION", "AUCTION_CALENDAR", "AUCTION_IC_ALLOCATIONS", "AUCTION_REVENUE_ESTIMATE", "AUCTION_REVENUE_TRACK", "AUCTION_RP_ESTIMATE", "AUCTION_TRANCHE", "RESIDUE_BID_TRK", "RESIDUE_CON_DATA", "RESIDUE_CON_ESTIMATES_TRK", "RESIDUE_CON_FUNDS", "RESIDUE_CONTRACTS", "RESIDUE_FUNDS_BID", "RESIDUE_PRICE_BID", "RESIDUE_PRICE_FUNDS_BID", "RESIDUE_PUBLIC_DATA", "RESIDUE_TRK", "RESIDUECONTRACTPAYMENTS", "RESIDUEFILETRK", "SRA_CASH_SECURITY", "SRA_FINANCIAL_AUC_MARDETAIL", "SRA_FINANCIAL_AUC_MARGIN", "SRA_FINANCIAL_AUC_RECEIPTS", "SRA_FINANCIAL_AUCPAY_DETAIL", "SRA_FINANCIAL_AUCPAY_SUM", "SRA_FINANCIAL_RUNTRK", "SRA_OFFER_PRODUCT", "SRA_OFFER_PROFILE", "SRA_PRUDENTIAL_CASH_SECURITY", "SRA_PRUDENTIAL_COMP_POSITION", "SRA_PRUDENTIAL_EXPOSURE", "SRA_PRUDENTIAL_RUN", "VALUATIONID"]}, "MARKET_CONFIG": {"comment": "Standing data for the market", "table_names": ["AREA", "BIDTYPES", "BIDTYPESTRK", "FCAS_REGU_USAGE_FACTORS", "FCAS_REGU_USAGE_FACTORS_TRK", "INTERCONNECTOR", "INTERCONNECTORALLOC", "INTERCONNECTORCONSTRAINT", "INTRAREGIONALLOC", "LOSSFACTORMODEL", "LOSSMODEL", "MARKET_PRICE_THRESHOLDS", "REGION", "REGION_AREA", "REGIONSTANDINGDATA", "TRANSMISSIONLOSSFACTOR"]}, "MARKET_NOTICE": {"comment": "Market Notice data", "table_names": ["MARKETNOTICEDATA", "MARKETNOTICETYPE", "PARTICIPANTNOTICETRK"]}, "METER_DATA": {"comment": "Wholesale market aggregated Meter data", "table_names": ["METERDATA_AGGREGATE_READS", "METERDATA_INDIVIDUAL_READS", "METERDATA_INTERCONNECTOR", "METERDATA_SAPS", "METERDATA_WDR_READS"]}, "MTPASA": {"comment": "Results from a published Medium Term PASA Run and region-aggregate offered PASA Availability of scheduled generators", "table_names": ["MTPASA_CASERESULT", "MTPASA_CONSTRAINTRESULT", "MTPASA_CONSTRAINTSUMMARY", "MTPASA_DUIDAVAILABILITY", "MTPASA_INTERCONNECTORRESULT", "MTPASA_LOLPRESULT", "MTPASA_REGIONAVAIL_TRK", "MTPASA_REGIONAVAILABILITY", "MTPASA_REGIONITERATION", "MTPASA_REGIONRESULT", "MTPASA_REGIONSUMMARY"]}, "P5MIN": {"comment": "Results from a published Five-Minute Predispatch Run", "table_names": ["P5MIN_BLOCKEDCONSTRAINT", "P5MIN_CASESOLUTION", "P5MIN_CONSTRAINTSOLUTION", "P5MIN_FCAS_REQ_CONSTRAINT", "P5MIN_FCAS_REQ_RUN", "P5MIN_INTERCONNECTORSOLN", "P5MIN_INTERMITTENT_FCST_TRK", "P5MIN_INTERSENSITIVITIES", "P5MIN_LOCAL_PRICE", "P5MIN_PRICESENSITIVITIES", "P5MIN_REGIONSOLUTION", "P5MIN_ROOFTOP_PV_FCST_TRK", "P5MIN_SCENARIODEMAND", "P5MIN_SCENARIODEMANDTRK", "P5MIN_UNITSOLUTION"]}, "PARTICIPANT_REGISTRATION": {"comment": "Participant registration data", "table_names": ["ADG_DETAIL", "AGGREGATE_DISPATCH_GROUP", "BIDDUIDDETAILS", "BIDDUIDDETAILSTRK", "DISPATCHABLEUNIT", "DUALLOC", "DUDETAIL", "DUDETAILSUMMARY", "GENMETER", "GENUNITS", "GENUNITS_UNIT", "MNSP_INTERCONNECTOR", "MNSP_PARTICIPANT", "PARTICIPANT", "PARTICIPANTACCOUNT", "PARTICIPANTCATEGORY", "PARTICIPANTCATEGORYALLOC", "PARTICIPANTCLASS", "PARTICIPANTCREDITDETAIL", "PASA_DUID_SUBSTATION_MAPPING", "PASA_INTERCONNECTOR_BOUNDARY", "PASA_INTERCONNECTOR_MAPPING", "PASA_INTERZONAL_BOUNDARY", "PASA_INTERZONAL_MAPPING", "PASA_SUBSTATION_ZONE_MAPPING", "PASA_ZONE_REGION_MAPPING", "PMS_GROUP", "PMS_GROUPNMI", "PMS_GROUPSERVICE", "STADUALLOC", "STATION", "STATIONOPERATINGSTATUS", "STATIONOWNER", "STATIONOWNERTRK"]}, "PRE_DISPATCH": {"comment": "Results from a published Predispatch RunStorage optionsThere are 2 ways to define the Pre-dispatch table primary keys (PKs) to define which data is loaded to the database and which data is retained:Option 1 (default)Overwrite older records when they are succeeded by later versions for the same entity and period. This is the Data Model default and results in the consumption of far less storage. Data Model updates issued by AEMO target this configuration so participants implementing option 2a or 2b must maintain their changes when AEMO releases a new Data Model version.PredispatchLoad: DateTime, DUIDPredispatchInterconnectorRes: DateTime, InterconnectorID,PredispatchPrice: DateTime, RegionIDPredispatchPriceSensitivities: DateTime, RegionIDPredispatchInterSensitivities: InterconnectorID, DateTimePredispatchRegionsum: DateTime, RegionIDOption 2aRetain only the Pricing records for tables relating to Price data and Physical records for tables relating to Physical data (e.g. targets). Approximately 50 times more storage volumes than option 1.PredispatchLoad: PredispatchSeqNo, DateTime, DUIDPredispatchInterconnectorRes: PredispatchSeqNo, DateTime, InterconnectorID,PredispatchPrice: PredispatchSeqNo, DateTime, RegionIDPredispatchPriceSensitivities: PredispatchSeqNo, DateTime, RegionIDPredispatchInterSensitivities: PredispatchSeqNo, DateTime, InterconnectorIDPredispatchRegionsum: PredispatchSeqNo, DateTime, RegionIDOption 2bRetain both Physical and Pricing data for Intervention runs. If Intervention cases are stored in entirety, you must select the data carefully. The logic is the same as for Dispatch, i.e. Intervention Pricing is always where Intervention = 0 and Physical data is where Intervention = PredispatchCaseSolution.Intervention for the same PredispatchSeqNo.Doubles the storage of option 2a but ONLY for Intervened cases.PredispatchLoad: PredispatchSeqNo, Intervention, DateTime, DUIDPredispatchInterconnectorRes: PredispatchSeqNo, Intervention,DateTime, InterconnectorID,PredispatchPrice: PredispatchSeqNo, Intervention, DateTime, RegionIDPredispatchPriceSensitivities: PredispatchSeqNo, Intervention, DateTime, RegionIDPredispatchInterSensitivities: PredispatchSeqNo, Intervention, DateTime, InterconnectorIDPredispatchRegionsum: PredispatchSeqNo, Intervention, DateTime, RegionIDNotes:The data in the PredispatchIS file is always ordered so the pdrLoader writes the relevant data first and discards the subsequent irrelevant data, or writes the subsequent data, depending on how the PKs are defined.You may order the PKs in a different order, depending on your local requirements. Any decision to change the PK column composition or order must consider the functional and performance impacts to existing applications or queries.The pdrLoader caches PK definitions for performance reasons so any change to the PKs requires a restart of the application.The TRANSACTION_TYPE default in the PDR_REPORT_RECORDS management tables for PREDISPATCH* tables is UPDATE-INSERT. You can modify this to INSERT for Option 2b, as the attempt to first perform an update becomes redundant. This can improve load performance.", "table_names": ["PD_FCAS_REQ_CONSTRAINT", "PD_FCAS_REQ_RUN", "PD_INTERMITTENT_FCST_TRK", "PD_ROOFTOP_PV_FCST_TRK", "PREDISPATCH_LOCAL_PRICE", "PREDISPATCH_MNSPBIDTRK", "PREDISPATCHBLOCKEDCONSTRAINT", "PREDISPATCHCASESOLUTION", "PREDISPATCHCONSTRAINT", "PREDISPATCHINTERCONNECTORRES", "PREDISPATCHINTERSENSITIVITIES", "PREDISPATCHLOAD", "PREDISPATCHOFFERTRK", "PREDISPATCHPRICE", "PREDISPATCHPRICESENSITIVITIES", "PREDISPATCHREGIONSUM", "PREDISPATCHSCENARIODEMAND", "PREDISPATCHSCENARIODEMANDTRK"]}, "RESERVE_DATA": {"comment": "Energy and FCAS reserve requirements", "table_names": ["MTPASA_RESERVELIMIT", "MTPASA_RESERVELIMIT_REGION", "MTPASA_RESERVELIMIT_SET"]}, "SETTLEMENT_CONFIG": {"comment": "Configuration and input data for the Settlements Process", "table_names": ["ANCILLARY_RECOVERY_SPLIT", "MARKET_FEE_CAT_EXCL", "MARKET_FEE_CAT_EXCL_TRK", "MARKET_FEE_EXCLUSION", "MARKET_FEE_EXCLUSIONTRK", "MARKETFEE", "MARKETFEEDATA", "MARKETFEETRK", "PARTICIPANT_BANDFEE_ALLOC", "REALLOCATION", "REALLOCATIONINTERVAL", "SETCFG_PARTICIPANT_MPF", "SETCFG_PARTICIPANT_MPFTRK", "SETCFG_SAPS_SETT_PRICE", "SETCFG_WDR_REIMBURSE_RATE", "SETCFG_WDRRR_CALENDAR"]}, "SETTLEMENT_DATA": {"comment": "Results from a published Settlements Run. The settlement data and billing run data are updated daily between 6am and 8am for AEMO's prudential processes. In a normal week, AEMO publishes one PRELIM, one FINAL and two REVISION runs in addition to the daily runs.", "table_names": ["DAYTRACK", "SET_APC_COMPENSATION", "SET_APC_RECOVERY", "SET_ANCILLARY_SUMMARY", "SET_ENERGY_GENSET_DETAIL", "SET_ENERGY_REGION_SUMMARY", "SET_ENERGY_TRAN_SAPS", "SET_ENERGY_TRANSACTIONS", "SET_FCAS_CLAWBACK_REQ", "SET_FCAS_CLAWBACK_RUN_TRK", "SET_FCAS_CLAWBACK_UNITSOLN", "SET_FCAS_PAYMENT", "SET_FCAS_RECOVERY", "SET_FCAS_REG_AMOUNT", "SET_FCAS_REG_DEF_AMT", "SET_FCAS_REG_DEF_RESIDAMT", "SET_FCAS_REG_RESIDAMT", "SET_FCAS_REGULATION_TRK", "SET_FPP", "SET_IRSR_DIRECTIONAL_LINK", "SET_IRSR_LOOP_NETTRADE_AMOUNT", "SET_IRSR_LOOP_NSP_ALLOCATION", "SET_IRSR_LOOP_REGION_SUMMARY", "SET_NMAS_MANUAL_PAYMENT", "SET_NMAS_RECOVERY", "SET_NMAS_RECOVERY_RBF", "SET_RECOVERY_ENERGY", "SET_SUBST_RUN_VERSION", "SET_SUBSTITUTE_DEMAND", "SET_WDR_RECON_DETAIL", "SET_WDR_TRANSACT", "SETFCASREGIONRECOVERY", "SETINTRAREGIONRESIDUES", "SETIRAUCSURPLUS", "SETIRNSPSURPLUS", "SETIRPARTSURPLUS", "SETIRSURPLUS", "SETLOCALAREAENERGY", "SETLOCALAREATNI", "SETLSHEDPAYMENT", "SETLSHEDRECOVERY", "SETMARKETFEES", "SETREALLOCATIONS", "SETRESERVERECOVERY", "SETRESTARTPAYMENT", "SETRESTARTRECOVERY", "SETRPOWERPAYMENT", "SETRPOWERRECOVERY"]}, "STPASA_SOLUTION": {"comment": "Results from a published Short Term PASA Run", "table_names": ["STPASA_CASESOLUTION", "STPASA_CONSTRAINTSOLUTION", "STPASA_DUIDAVAILABILITY", "STPASA_FNM_CASESOLUTION", "STPASA_FNM_CONSTRAINTSOLUTION", "STPASA_FNM_DUIDAVAILABILITY", "STPASA_FNM_INTERCONNECTORSOLN", "STPASA_FNM_INTERZONALSOLUTION", "STPASA_FNM_REGIONSOLUTION", "STPASA_FNM_REGIONSUMMARY", "STPASA_FNM_ZONESOLUTION", "STPASA_FNM_ZONESUMMARY", "STPASA_INTERCONNECTORSOLN", "STPASA_REGIONSOLUTION"]}, "TRADING_DATA": {"comment": "30 minute Trading interval results", "table_names": ["AVERAGEPRICE30", "TRADINGINTERCONNECT", "TRADINGPRICE"]}, "HISTORICAL TABLES": {"comment": "These tables are no longer used", "table_names": ["APCCOMP", "APCCOMPAMOUNT", "APCCOMPAMOUNTTRK", "BIDPEROFFER", "BILLADJUSTMENTS", "BILLING_CSP_DEROGATION_AMOUNT", "BILLING_DIRECTION_RECONCILIATN", "BILLING_MR_PAYMENT", "BILLING_MR_RECOVERY", "BILLING_MR_SHORTFALL", "BILLING_MR_SUMMARY", "BILLING_RES_TRADER_PAYMENT", "BILLING_RES_TRADER_RECOVERY", "BILLINGCPDATA", "BILLINGCPSUM", "BILLINGCUSTEXCESSGEN", "BILLINGEXCESSGEN", "BILLINGGENDATA", "BILLINGINTERVENTION", "BILLINGINTERVENTIONREGION", "BILLINGRESERVERECOVERY", "BILLINGRESERVEREGIONRECOVERY", "BILLINGRESERVETRADER", "BILLINGRESERVETRADERREGION", "BILLINGSMELTERREDUCTION", "BILLINTERVENTIONRECOVERY", "BILLINTERVENTIONREGIONRECOVERY", "BILLSMELTERRATE", "CONNECTIONPOINT", "CONNECTIONPOINTDETAILS", "CONNECTIONPOINTOPERATINGSTA", "CONTRACTGOVERNOR", "CONTRACTRESERVEFLAG", "CONTRACTRESERVETHRESHOLD", "CONTRACTRESERVETRADER", "CONTRACTUNITLOADING", "CONTRACTUNITUNLOADING", "DAYOFFER", "DAYOFFER_D", "DEFAULTDAYOFFER", "DEFAULTOFFERTRK", "DEFAULTPEROFFER", "DELTAMW", "DISPATCH_FCAS_REQ", "DISPATCHBIDTRK", "DISPATCHCASE_OCD", "DISPATCHCASESOLUTION_BNC", "DISPATCHLOAD_BNC", "DISPATCHTRK", "FORCEMAJEURE", "FORCEMAJEUREREGION", "GENUNITMTRINPERIOD", "INTCONTRACT", "INTCONTRACTAMOUNT", "INTCONTRACTAMOUNTTRK", "INTERCONNMWFLOW", "MARKETSUSPENSION", "MARKETSUSREGION", "MAS_CP_CHANGE", "MAS_CP_MASTER", "METERDATA", "METERDATA_GEN_DUID", "METERDATA_TRK", "METERDATATRK", "MNSP_FILETRK", "MNSP_OFFERTRK", "MNSP_PEROFFER", "MR_DAYOFFER_STACK", "MR_EVENT", "MR_EVENT_SCHEDULE", "MR_PEROFFER_STACK", "MTPASA_CASE_SET", "MTPASA_CASESOLUTION", "MTPASA_CONSTRAINTSOLUTION", "MTPASA_INTERCONNECTORSOLUTION", "MTPASA_REGIONSOLUTION", "MTPASA_RESERVELIMITSOLUTION", "MTPASACONSTRAINTSOLUTION_D", "MTPASAINTERCONNECTORSOLUTION_D", "MTPASAREGIONSOLUTION_D", "OARTRACK", "OFFERFILETRK", "OFFERGOVDATA", "OFFERULOADINGDATA", "OFFERUNLOADINGDATA", "P5MIN_FCAS_REQUIREMENT", "PASACASESOLUTION", "PASACONSTRAINTSOLUTION", "PASAINTERCONNECTORSOLUTION", "PASAREGIONSOLUTION", "PEROFFER", "PEROFFER_D", "PREDISPATCH_FCAS_REQ", "PREDISPATCHBIDTRK", "REALLOCATIONDETAILS", "REALLOCATIONINTERVALS", "REALLOCATIONS", "REGIONFCASRELAXATION_OCD", "RESERVE", "SET_CSP_DEROGATION_AMOUNT", "SET_CSP_SUPPORTDATA_CONSTRAINT", "SET_CSP_SUPPORTDATA_ENERGYDIFF", "SET_CSP_SUPPORTDATA_SUBPRICE", "SET_MR_PAYMENT", "SET_MR_RECOVERY", "SET_RUN_PARAMETER", "SETAGCPAYMENT", "SETAGCRECOVERY", "SETAPCCOMPENSATION", "SETAPCRECOVERY", "SETCPDATA", "SETCPDATAREGION", "SETFCASCOMP", "SETFCASRECOVERY", "SETGENDATA", "SETGENDATAREGION", "SETGOVPAYMENT", "SETGOVRECOVERY", "SETINTERVENTION", "SETINTERVENTIONRECOVERY", "SETIRFMRECOVERY", "SETLULOADPAYMENT", "SETLULOADRECOVERY", "SETLUNLOADPAYMENT", "SETLUNLOADRECOVERY", "SETRESERVETRADER", "SETSMALLGENDATA", "SETVICBOUNDARYENERGY", "SETVICENERGYFIGURES", "SETVICENERGYFLOW", "STPASA_SYSTEMSOLUTION", "STPASA_UNITSOLUTION", "TRADINGLOAD", "TRADINGREGIONSUM"]}, "PDPASA": {"comment": "The PDPASA package provides a 30-minute solving process to the Market systemsThe current methodology for calculating reserves in the PreDispatch timeframe is determined in a post processing step using a heuristic calculation based the results and Interconnector limits from the PreDispatch run.The calculation is a reserve assessment based on the PASA solver similar to existing ST and MT PASA business processesThe process reflects all intra-regional and inter-regional network constraints as an input to the process", "table_names": ["PDPASA_CASESOLUTION", "PDPASA_CONSTRAINTSOLUTION", "PDPASA_DUIDAVAILABILITY", "PDPASA_FNM_CASESOLUTION", "PDPASA_FNM_CONSTRAINTSOLUTION", "PDPASA_FNM_DUIDAVAILABILITY", "PDPASA_FNM_INTERCONNECTORSOLN", "PDPASA_FNM_INTERZONALSOLUTION", "PDPASA_FNM_REGIONSOLUTION", "PDPASA_FNM_REGIONSUMMARY", "PDPASA_FNM_ZONESOLUTION", "PDPASA_FNM_ZONESUMMARY", "PDPASA_INTERCONNECTORSOLN", "PDPASA_REGIONSOLUTION"]}, "PRUDENTIALS": {"comment": "Prudential Management", "table_names": ["BANK_GUARANTEE", "CASH_SECURITY", "PRUDENTIALCOMPANYPOSITION", "PRUDENTIALRUNTRK"]}, "MCC_DISPATCH": {"comment": "Results from the Marginal Constraint Cost (MCC) re-run of the dispatch process. The MCC forms part of the part of the AER\u201fs \u201cElectricity transmission network service providers Service target performance incentive Scheme\u201d", "table_names": ["MCC_CASESOLUTION", "MCC_CONSTRAINTSOLUTION"]}, "NETWORK": {"comment": "Configuration data for the physical network", "table_names": ["NETWORK_EQUIPMENTDETAIL", "NETWORK_OUTAGECONSTRAINTSET", "NETWORK_OUTAGEDETAIL", "NETWORK_OUTAGESTATUSCODE", "NETWORK_RATING", "NETWORK_REALTIMERATING", "NETWORK_STATICRATING", "NETWORK_SUBSTATIONDETAIL"]}, "VOLTAGE_INSTRUCTIONS": {"comment": "Instructions for MVAr Dispatch", "table_names": ["VOLTAGE_INSTRUCTION", "VOLTAGE_INSTRUCTION_TRK"]}, "PD7DAY": {"comment": "Results from a published Predispatch 7 Day Run", "table_names": ["PD7DAY_CASESOLUTION", "PD7DAY_CONSTRAINTSOLUTION", "PD7DAY_INTERCONNECTORSOLUTION", "PD7DAY_MARKET_SUMMARY", "PD7DAY_PRICESOLUTION"]}, "FPP": {"comment": "Results from a published Frequency Performance Payments (FPP) Run. The FPP calculation runs performs every trading interval (typically 5 minutes, but different for P5MIN / PREDISPATCH) and input data feeding into the calculations. The output data from the calculations is published on that same interval. There are some tables that operate on different frequencies (e.g. P5MIN / PREDISPATCH) as well as some data becoming public the following market day. For further details please see the FPP procedure and supporting documentation.", "table_names": ["FPP_CONSTRAINT_FREQ_MEASURE", "FPP_CONTRIBUTION_FACTOR", "FPP_EST_COST", "FPP_EST_PERF_COST_RATE", "FPP_EST_RESIDUAL_COST_RATE", "FPP_FCAS_SUMMARY", "FPP_FORECAST_DEFAULT_CF", "FPP_FORECAST_RESIDUAL_DCF", "FPP_HIST_PERFORMANCE", "FPP_HIST_REGION_PERFORMANCE", "FPP_P5_FWD_EST_COST", "FPP_P5_FWD_EST_RESIDUALRATE", "FPP_PD_FWD_EST_COST", "FPP_PD_FWD_EST_RESIDUALRATE", "FPP_PERFORMANCE", "FPP_RCR", "FPP_REGION_FREQ_MEASURE", "FPP_RESIDUAL_CF", "FPP_RESIDUAL_PERFORMANCE", "FPP_RUN", "FPP_UNIT_MW", "FPP_USAGE"]}, "SYSTEM_SECURITY_MANAGEMENT": {"comment": "Package for ISF (Improving Security Frameworks) for Electricity Power System Security procurement (not related to IT security)", "table_names": ["SSM_CONTRACT_UNIT_AVAIL", "SSM_ENABLEMENT_COSTS", "SSM_ENABLEMENT_PERIOD", "SSM_INDICATIVE_ROLL_DUID", "SSM_INDICATIVE_ROLL_REGION", "SSM_INSTRUCTION", "SSM_SCHEDULE", "SSM_SCHEDULED_AVAILABILITY"]}}