Bidding Validation Messages
The following validation messages are examples only and may differ from the ones you see in:
- API responses
- The Markets Portal interface
- In the ack/cpt for FTP Bid submissions
|
Status |
Error Code |
Error Title |
Error Detail |
More information |
|---|---|---|---|---|
|
NEW |
NEM-BIDDING-VALIDATION-DAILYENERGYCONSTRAINTERROR |
Invalid DailyEnergyConstraint |
Daily energy constraint must be null or an integer not less than 0 and less than 24 X DUID Dispatchable Unit Identifier MAXCAPACITY. |
|
|
NEW |
NEM-BIDDING-VALIDATION-INVALIDRECALLPERIOD |
Recall Period Violation |
Recall Period applies only for ENERGY and MNSP Bids. Recall Period must be an integer or a decimal number with no more than two decimal places, between 0 and {MaxRecallPeriod} in periodid {PeriodID}. MaxRecallPeriod is 24000. |
|
|
NEW |
NEM-BIDDING-VALIDATION-BANDAVAILEXCEEDSLOADMAXCAPACITY |
Band Availability exceeds Max Load capacity |
Band Availability must be <= Registered Maximum Load Capacity {1} |
Your Bid is rejected because the BDU Energy Bid Direction is LOAD for the associated Energy Periods and the Band Availability (1 to 10) is greater than the Registered Maximum Load Capacity. The Band Availability must be less than or equal to the Registered Maximum Load Capacity for the DUID. Or the BDU Energy Bid MLF-adjusted Price Bands must monotonically increase from LOAD Band Availability (1 to 10) to GEN Band Availability (1 to 10). They must increase from lowest to highest |
|
NEW |
NEM-BIDDING-VALIDATION-FIXEDLOADPROVIDEDFORGENANDLOADISNOTALLOWED |
Fixed Load violation |
Fixed Load cannot be provided for GEN and LOAD DUID {0} |
Your Bid is rejected because the optional Fixed Load value for the Energy Periods is for both directions: LOAD and GEN. For a BDU, if you provide the value, it is only allowed for a LOAD or GEN direction at a time |
|
NEW |
NEM-BIDDING-VALIDATION-PRICESNOTINCREASEDMONOTONICALLYISNOTALLOWED |
Monotonically Increased Prices violation |
Prices must increased monotanically for DUID {0} |
Your Bid is rejected because your BDU Energy Bid for a Trading Day must include the Direction: LOAD or GEN. You must separate the Energy Bid and associated Energy Periods for the Load and Generation side of the BDU. Or the MLF-adjusted Price Bands do not monitonically increase for LOAD (1 to 10) and GEN Band Availability (1 to 10). They must increase from lowest to highest. |
|
NEW |
NEM-BIDDING-VALIDATION-UNITREGISTEREDASSEMI-SCHEDULEDCANNOTHAVEFASTSTARTPROFILE |
FastStartProfile unit requirement violation |
Unit registered as Semi-Scheduled cannot have FaststartProfile in the Bid for DUID {0} |
Your Bid is rejected because the Fast Start Profile associated with the Energy Bid has a value. A Fast Start Profile is not required for a Semi-Scheduled Generating Unit |
|
NEW |
NEM-BIDDING-VALIDATION-NOFSFORBDU |
Invalid Faststart details |
Unit registered as BDU cannot have FaststartProfile in the bid for DUID {0} |
Your Bid is rejected because the Fast Start Profile associated with the Energy Bid has a value. A Fast Start Profile is not required for a Bidirectional Unit |
|
NEW |
NEM-BIDDING-VALIDATION-MINIMUMMAXIMUMPRICEBANDVIOLATION |
Minimum/Maximum Price Band Violation |
Prices bands must be with in Market Floor Price {0}, Market Price Cap {1}, for DUID {2} |
Your Bid is rejected because the Prices Bands must be within the Market Floor Price and Market Price Cap for the DUID |
|
NEW |
NEM-BIDDING-VALIDATION-ERRORINVALIDDIRECTIONFORUNIT |
Invalid Direction |
The Direction for DUID {1} is not matching the registration details in {0} the Bid |
Your Bid is rejected because the conditional Direction value: GEN, LOAD, or BIDIRECTIONAL, associated with the Energy Bid, does not match the allowable combination for the DUID or Bid type, or both |
|
NEW |
NEM-BIDDING-VALIDATION-ERROR-MISSING-{0}-Bid |
Missing {0} Direction in the Bid |
Missing {0} Direction in the {1} Bid for DUID {2} |
Your Bid is rejected because you did not enter a Direction value. You must enter a value for BDU Energy and Regulation FCAS Bids with one of the following values: GEN, LOAD, or BIDIRECTIONAL. A Direction value is optional for all other DUID types |
|
NEW |
NEM-BIDDING-VALIDATION-ERROR-MISSING-Bid |
Missing Bid |
BDU submission must have both LOAD and GEN Bids for DUID {0} |
Your Bid is rejected bacause you did not enter Direction values for both sides. For a Bidirectional Unit (BDU), the Direction value associated with the Energy Bid or Energy Period determines if it is LOAD or GEN. For BDU Energy and Regulation FCAS bids, you must provide a value for both directions, and that value must be different for both sides. A Direction value is optional for all other DUID types and BDU contingency FCAS |
|
NEW |
NEM-BIDDING-VALIDATION-INVALIDUNITDISPATCHTYPE |
Invalid unit disptach type |
Unit {0} is not registered as a BDU |
Your Bid is rejected because energy or FCAS bid parameters are only allowable for a BDU and the DUID is not registered as a BDU |
|
NEW |
NEM-BIDDING-VALIDATION-CANNOTPROVIDEENERGYLIMITFORNONBDU |
Energy limit violation |
Unit {0} is not registered as a BDU and cannot provide Energy limit. |
Your Bid is rejected because you did not enter a value for the Energy Limit for a non-BDU DUID associated with the Energy Bid or Energy Period. The Energy Limit value is optional for BDU DUID Energy Bids For more information, see Energy Limit Validation |
|
NEW |
NEM-BIDDING-VALIDATION-ENERGYLIMITCRITERIAVIOLATIONFORBDU |
Energy limit violation |
BDU {0} is violating Energy Limit criteria for direction {1}, in periodId {2} |
Your Bid is rejected because the BDU value violates the Energy Limit for the Direction in Period ID {2} |
|
NEW |
NEM-BIDDING-VALIDATION-CONVEXITYCRITERIAVIOLATIONFORBDU |
Convexity violation |
BDU {0} is violating Convexity criteria in Load band avail[{1}] and Gen band avail[{2}], in periodId {3} |
Your Bid is rejected is because the BDU Energy Bid MLF-adjusted prices for effective Bid bands do not increase monotonically from LOAD bandAvail1 to bandAvail10 to GEN bandAvail1 to bandAvail10. |
|
NEW |
NEM-BIDDING-VALIDATION-NODAILYENERGYCONSTRAINTFORBDU |
Invalid DailyEnergyConstraint details |
Daily energy constraint must not be provided for BDUs in the bid for DUID {0} |
Your Bid is rejected because you have provided the DailyEnergyConstraint field for BDU. This field is only required for energyBids |
|
EXISTING |
NEM-BIDDING-VALIDATION-INVALID-UNIT-ID |
Invalid unit ID |
UnitId {0} is invalid . |
|
|
EXISTING |
NEM-BIDDING-VALIDATION-INVALIDNUMBEROFSUBMISSIONFORDUID |
Invalid number of Submission |
Invalid number of Submission for Duid:{0}, Trading Date:{1} |
|
|
NEW |
NEM-BIDDING-VALIDATION-STANDARDTRAPEZIUMSIZEVIOLATION |
Standard trapezium size violation |
Standard trapezium size violation in periodid {0}, for DUID {1} |
Your Bid is rejected because the following conditions are not met: |
|
NEW |
NEM-BIDDING-VALIDATION-CHECKLIMITITEMISPOSTIVE |
Value is Positive |
{0} cannot be positive in periodId {1} |
Your Bid is rejected because the Direction value associated with the Energy Bid is LOAD and the FCAS Periods with: Enablement Min, Enablement Max, Low BreakPoint, or High BreakPoint have positive values. The values must be negative or 0. |
|
NEW |
NEM-BIDDING-VALIDATION-CHECKLIMITITEMISNEGATIVE |
Value is Negative |
{0} cannot be negative in periodId {1} |
Your Bid is rejected because the Direction value associated with the Energy Bid is Gen and the Energy Bids with: Enablement Min, Enablement Max, Low BreakPoint, or HighBreakPoint has negative values. The values must be positive or 0. |
|
NEW |
NEM-BIDDING-VALIDATION-INVALIDFCASSERVICEBDU |
Invalid FCAS service |
{0} Duid cannot have invalid fcas service {1} |
Your Bid is rejected because the DUID is not registered to provide FCAS service. Please check the DUID's registration details. |
|
NEW |
NEM-BIDDING-VALIDATION-SUMOFMAXAVAILEXCEEDSMAXCAPACITY |
Sum of max avail exceeds max capacity |
Sum of max avail from GEN and LOAD must be <= unit {0} max capacity {1} |
Your Bid is rejected because the BDU Energy or FCAS Bid summed values with Max Availability for the LOAD and GEN Direction is greater than the DUID's Registered Maximum Capacity. Sum of Band Availabilities must be less than or equal to the Registered Maximum Capacity of the DUID for the direction. |
|
NEW |
NEM-BIDDING-VALIDATION-NONIDENTICALREBIDEXPLAINATIONSFORGENANDLOADINBDUOFFER |
Non identical rebid values |
Rebid values not identical for Direction LOAD and GEN, unit {0} |
You BDU Energy or FCAS Bid is rejected because the 5 field values associated with rebidExplanation array for LOAD and GEN (direction) are not indentical. |
|
NEW |
NEM-BIDDING-VALIDATION-BDUFCASREGBANDAVAILSUMEXCEEDSMAXCAPACITY |
BDU FCAS Regulation Band Availability violation |
Sum of Band Availabilities of GEN and LOAD must be >= Maximum Capacity {0} for the direction GEN and LOAD. |
Your Bid is rejected because the sum of the BDU Regulation FCAS Availabilities for Band Availabilty (1 to 10) for the FCAS Periods for both the LOAD and GEN Direction is greater than the Registered Maximum Capacity of the DUID. |
|
NEW |
NEM-BIDDING-VALIDATION-BDUFCASREGNETTRAPEZIUMGAPVIOLATION |
Net Trapezium Gap Violation |
Both GEN and LOAD trapeziums should not have any gaps in them i.e. GEN enablementMin=0 and LOAD enablementMax=0, for DUID {0} in periodid {1} |
Your Bid is rejected because there is a gap in the combined GEN and LOAD trapezium. When both sides have availability, the individual trapeziums should meet at 0 MW |
|
NEW |
NEM-BIDDING-VALIDATION-BDUFCASREGNETTRAPEZIUMUPPERANGLEVIOLATION |
Net Trapezium Upper Angle Violation |
Both GEN and LOAD trapeziums should have the same upper angles, instead of GEN upper angle {2} and LOAD upper angle {3}, for DUID {0} in periodid {1} |
Your Bid is rejected because the GEN and LOAD trapezium must have the same upper angle. |
|
NEW |
NEM-BIDDING-VALIDATION-BDUFCASREGNETTRAPEZIUMLOWERANGLEVIOLATION |
Net Trapezium Lower Angle Violation |
Both GEN and LOAD trapeziums should have the same lower angles, instead of GEN lower angle {2} and LOAD lower angle {3}, for DUID {0} in periodid {1} |
Your Bid is rejected because the GEN and LOAD trapezium must have the same lower angle |
|
NEW |
NEM-BIDDING-VALIDATION-BDUFCASREGNETTRAPEZIUMUPPERANGLELESSTHANNINETYVIOLATION |
Net Trapezium Upper Angle Less Than 90° Violation |
When upper angle {4} is less than 90°, bid high {3} and low {2} breakpoints on the generation trapezium must be zero, for DUID {0} in periodid {1} |
Your Bid is rejected because both Low Breakpoint and High Breakpoint for GEN must be 0 when upper angle is less than 90° |
|
NEW |
NEM-BIDDING-VALIDATION-BDUFCASREGNETTRAPEZIUMLOWERANGLELESSTHANNINETYVIOLATION |
Net Trapezium Lower Angle Less Than 90° Violation |
When lower angle {4} is less than 90°, bid high {3} and low {2} breakpoints on the generation trapezium must be zero, for DUID {0} in periodid {1} |
Your Bid is rejected because both Low Breakpoint and High Breakpoint for LOAD must be 0 when lower angle is less than 90° |
|
.EXISTING |
NEM-BIDDING-VALIDATION-CONFLICTINGSTARTTYPE |
Conflicting Start Type |
DUID {0} has conflicting registration information(start type) and an energy Bid cannot be accepted. |
|
|
EXISTING |
NEM-BIDDING-VALIDATION-CONFLICTINGDISPATCHTYPE |
Registration violation |
Unit {0} is not registered as a recognised dispatchable type |
Check the generating unit details = registration details |
|
EXISTING |
NEM-BIDDING-VALIDATION-UNITNOTREGISTEREDFORENERGYTYPE |
Registration type issue |
DUID {0} is not registered for ENERGY |
DUID must be registered for the energy service type |
|
EXISTING |
NEM-BIDDING-VALIDATION-DAILYENERGYCONSTRAINTERROR |
Invalid DailyEnergyConstraint |
Daily energy constraint must be less than 1 million MWh |
|
|
EXISTING |
NEM-BIDDING-VALIDATION-MROPSFFORNONGENUNIT |
MRPriceScalingFactor Issue |
MR Bid Scaling Factor found for non - generation unit |
|
|
EXISTING |
NEM-BIDDING-VALIDATION-MROPSFVALUERANGE |
Invalid MR Scaling factor |
MR Bid Scaling Factor must be between 0 and 9 |
|
|
EXISTING |
NEM-BIDDING-VALIDATION-MROPSFDECIMALVALUES |
Invalid MR Bid Scaling Factor |
MR Bid Scaling Factor cannot be greater than 4 decimal places. |
|
|
EXISTING |
NEM-BIDDING-VALIDATION-MROPSFINITIALOFFERPOSTCUTOFFTIME |
MR Bid Past Cut-off Time |
Initial MR Bid is past the MR Bid Cut-off time. |
|
|
EXISTING |
NEM-BIDDING-VALIDATION-5MSBIDCUTOFFTRADINGDAY |
Bids with trading dates before cut-off date |
You cannot submit 5-min Bids before the 5MS commencement date [{0}]. Please revert to 30-min Bids. |
|
|
EXISTING |
NEM-BIDDING-VALIDATION-MROPSFOFFERPOSTCUTOFFTIME |
MR Factor change post cut-off time |
MR Factor cannot be changed past the MR Bid Cut-off time. |
|
|
EXISTING |
NEM-BIDDING-VALIDATION-EXPECTEDMRCAPACITYNOTMET |
MR Capacity missing |
Failed to find expected MR Capacity |
|
|
EXISTING |
NEM-BIDDING-VALIDATION-RAMPUPRATEEXCEEDEDMAX |
Invalid Rampuprate |
Ramp Rate must be <= registered max Ramp Rate {0} |
Ramp up rate <= registered maximum ramp rate |
|
EXISTING |
NEM-BIDDING-VALIDATION-RAMPUPRATERANGEERROR |
Invalid Rampdownrate |
Ramp Rate must be <= registered max Ramp Rate {0} |
|
|
EXISTING MODIFIED |
NEM-BIDDING-VALIDATION-RAMPUPRATELESSTHANMAXREASON |
Reason missing for Ramprateup voilation |
Reason required for Ramp Rate lower than registered minimum ramp up rate of {0} |
Your Bid is rejected because the value provided is less than the registered minimum value. The validation message provides additional information comparing the minimum ramp rate and the value in the Bid |
|
EXISTING MODIFIED |
NEM-BIDDING-VALIDATION-RAMPDOWNRATELESSTHANMAXREASON |
Reason missing for Rampratedown voilation |
Reason required for Ramp Rate lower than registered minimum ramp down rate of {0} |
Your Bid is rejected because the value provided is less than the registered minimum value. The validation message provides additional information comparing the minimum ramp rate and the value in the Bid |
|
EXISTING MODIFIED |
NEM-BIDDING-VALIDATION-REASONFORRAMPUPLESSTHANNERCALC |
Reason missing for ramprateup violation |
Reason required for Ramp Rate lower than registered minimum ramp up rate of {0} |
Your Bid is rejected because the value provided is less than the registered minimum value. The validation message provides additional information comparing the minimum ramp rate and the value in the Bid |
|
EXISTING MODIFIED |
NEM-BIDDING-VALIDATION-REASONFORRAMPDOWNLESSTHANNERCALC |
Reason missing for rampratedown violation |
Reason required for Ramp Rate lower than registered minimum ramp down rate of {0} |
Your Bid is rejected because the value provided is less than the registered minimum value. The validation message provides additional information comparing the minimum ramp rate and the value in the Bid |
|
EXISTING |
NEM-BIDDING-VALIDATION-NOFSFORSLOWSTARTUNITS |
Invalid Faststart details |
Faststart details must not be provided for slow start units |
|
|
EXISTING |
NEM-BIDDING-VALIDATION |
Invalid Faststart details |
Fast start details must be non-blank for fast start units |
Check fast start details |
|
EXISTING |
NEM-BIDDING-VALIDATION-FS-MINVALUE-FASTSTARTNONBLANK |
Invalid FS min load value |
Fast start min. load must not be negative |
|
|
EXISTING |
NEM-BIDDING-VALIDATION-FASTSTARTT1NEGATIVE |
Invalid FS T1 value |
Value for T1 parameter must not be negative |
Check the fast start T1 is positive or zero |
|
EXISTING |
NEM-BIDDING-VALIDATION-FASTSTARTT2NEGATIVE |
Invalid FS T2 value |
Value for T2 parameter must not be negative |
Check the fast start T2 is positive or zero |
|
EXISTING |
NEM-BIDDING-VALIDATION-FASTSTARTT3NEGATIVE |
Invalid FS T3 value |
Value for T3 parameter must not be negative |
Check the fast start T3 is positive or zero |
|
EXISTING |
NEM-BIDDING-VALIDATION-FASTSTARTT4NEGATIVE |
Invalid FS T4 value |
Value for T4 parameter must not be negative |
Check the fast start T4 is positive or zero |
|
EXISTING |
NEM-BIDDING-VALIDATION-FST1ANDT2MUSTNOTEXCEED30 |
Invalid Fast Start details |
Fast start T1 + T2 must be <= 30 minutes |
Sum of fast start T1 + T2 <= 30 minutes |
|
EXISTING |
NEM-BIDDING-VALIDATION-FST1T2T3T4MUSTNOTEXCEED60 |
Invalid Fast Start details |
Fast start T1 + T2 + T3 + T4 must be < 60 minutes |
Sum of fast start T1 + T2 + T3 + T4 < 60 minutes |
|
EXISTING |
NEM-BIDDING-VALIDATION-FSMIINEXCEEDREGMAX |
Invalid Fast Start details |
Fast start minimum Load cannot exceed registered maximum capacity of unit. |
Fast start minimum load is < = registered maximum capacity |
|
EXISTING |
NEM-BIDDING-VALIDATION-OFFEREDLOWBRKPTLESSTHANMAXAVAIL |
Invalid Low Break point value |
Offered FCAS trapezium must not be outside the registered FCAS trapezium |
Check high break point or low break point value |
|
EXISTING |
NEM-BIDDING-VALIDATION-OFFEREDHIGHBRKPTLESSTHANMAXAVAIL |
Invalid High Break point value |
Offered FCAS trapezium must not be outside the registered FCAS trapezium |
|
|
EXISTING |
NEM-BIDDING-VALIDATION-UNITNOTREGISTEREDFORFCASTYPE |
Registration validation error |
DUID {0} is not registered for {1} |
Check DUID details are consistent with registration details |
|
EXISTING |
NEM-BIDDING-VALIDATION-PRICEBANDVALEXCEEDSVOLL |
Price validation error |
Band prices must be less than or equal to market price cap {0} |
|
|
EXISTING |
NEM-BIDDING-VALIDATION-PRICEBANDVALLESSTHANFLOORPRICE |
Price band value violation |
Price band value must be greater than or equal to market price floor ({0}) |
Price bands >= market floor price |
|
EXISTING |
NEM-BIDDING-VALIDATION-ERRORPOSTREBIDCUTOFFTIME |
REBID-TIME-1 |
Cannot Process Participant Bid |
Bid is after the rebid cut-off time |
|
EXISTING |
NEM-BIDDING-VALIDATION-PRICEBANDLESSTHANMINIMUMPRICE |
Price violation error |
Band prices must increase monotonically |
|
|
EXISTING |
NEM-BIDDING-VALIDATION-PRICEBANDMORETHANMAXPRICE |
Band price beyond cap price |
Cannot correct Over Voll Rebid - Band Price 9 must monotonically decrease from artificial Effective Cap Price {0} |
|
|
EXISTING |
NEM-BIDDING-VALIDATION-REBIDREASONFORINFLEXIBILITY |
Reason missing for Inflexibility |
Reason required for fixed load |
Provide a reason for fixed load |
|
EXISTING |
NEM-BIDDING-VALIDATION-REBIDREASONLENGTHERROR |
Rebid Reason Length violation |
The rebid reason must be less than or equal to {0} characters in length |
|
|
EXISTING |
NEM-BIDDING-VALIDATION-NOTLEGACYCOMPLIANT |
Period differs from Base Period (not 30-minute legacy compliant) |
Until 5MS active Periods must be consistent across 30-minute ranges - Base Period {1} |
|
|
EXISTING |
NEM-BIDDING-VALIDATION-BANDAVAILEXCEEDSMAXCAPACITY |
Band Availability exceeds Max capacity |
Band Availability must be <= Maximum Capacity {1} |
Band availability is less than or equal to the maximum capacity |
|
EXISTING |
NEM-BIDDING-VALIDATION-BANDAVAILEXCEEDSLOADMAXCAPACITY |
Band Availability exceeds Max Load capacity |
Band Availability must be <= Registered Maximum Load Capacity {1} |
|
|
EXISTING MODIFIED |
NEM-BIDDING-VALIDATION-BANDAVAILSUMEXCEEDSMAXCAPACITY |
Band Availability violation |
Sum of Band Availabilities must be >= Maximum Capacity {0} for the direction {1} |
Your Bid is rejected because the sum of Energy FCAS Bid Availabilities (1 to 10) is greater than the Registered Generation or Load Capacity of the DUID. This validation is applied to all DUIDs, including BDUs and is associated with the LOAD or GEN Direction of the Bid |
|
EXISTING |
NEM-BIDDING-VALIDATION-RAMPUPANDDOWNNOTINRANGE |
Ramprate violation |
Rate of change up or down beyond respective registered bounds of {0} and {1} |
Rate of change up or down is within respective registered bounds |
|
EXISTING |
NEM-BIDDING-VALIDATION-MRCAPACITYFORALLBIDS |
MR Capacity missing |
MR Capacity must be offered for all periods when a MR Factor is submitted |
|
|
EXISTING |
NEM-BIDDING-VALIDATION-MRCAPACITYSPECIFIEDFORNONGENERATINGUNIT |
MR Capacity violation |
MR Capacity found for non-generation unit |
|
|
EXISTING |
NEM-BIDDING-VALIDATION-MRCAPACITYMORETHANMAXAVAIL |
MR Capacity violation |
MR Capacity cannot be greater than MaxAvail |
|
|
EXISTING |
NEM-BIDDING-VALIDATION-MRCAPACITYMORETHANMAX |
MR Capacity violation |
MR Capacity cannot be greater than 999999 |
|
|
EXISTING |
NEM-BIDDING-VALIDATION-MRCAPACITYMORETHAN30XROCDOWN |
MR Capacity violation |
MR Capacity cannot be greater than 30 x ROC-DOWN |
|
|
EXISTING |
NEM-BIDDING-VALIDATION-MRCAPACITYFIXEDLOADPERIODS |
MR Capacity violation |
MR Capacity cannot be offered for fixed load periods |
|
|
EXISTING |
NEM-BIDDING-VALIDATION-INITIALBIDCUTOFFTIME |
Bid Cutoff time violation |
Initial Bid is past the BidCutOffTime. |
|
|
EXISTING MODIFIED |
NEM-BIDDING-VALIDATION-PRICECHANGEFORREBID |
Rebid Price violation |
Band prices cannot be changed for a rebid direction {0}. |
Your Bid is rejected because the band prices must remain same for a rebid |
|
EXISTING |
NEM-BIDDING-VALIDATION-NOMRPSFFORANACCEPTEDOFFER |
MROPSF value violation |
Failed to find MR Bid Scaling Factor when an Accepted MR Bid exists |
|
|
EXISTING |
NEM-BIDDING-VALIDATION-MRCAPACITYWITHOUTMRPSF |
MRCapacity violation |
Found offered MR Capacity with no MR Scaling Factor |
|
|
EXISTING |
NEM-BIDDING-VALIDATION-BANDPRICEVALUENEGATIVE |
Negative Band Availabilities |
Band availability figures cannot be negative. |
Band availabilities are positive or zero |
|
EXISTING |
NEM-BIDDING-VALIDATION-PRICEBANDEXCEEDSMAXLOSSADJPRICE |
Price violation |
Band prices must be less than or equal to market price cap {0} |
|
|
EXISTING |
NEM-BIDDING-VALIDATION-ERROR |
Internal service Error |
Unable to process the submission. Please contact AEMO for further support |
Check submission and contact Support Hub, if required |
|
EXISTING |
NEM-BIDDING-VALIDATION-MRCPACITYGREATERTHANROCUPOPPOSITELINK |
MR capacity violation |
MR Capacity cannot be greater than 30 x ROC-UP for Opposite Link {0} |
|
|
EXISTING |
NEM-BIDDING-VALIDATION-DISPATCHABLEUNITINACTIVE |
DU Invalid |
DUID {0} is invalid or not active |
Check the dispatchable unit details |
|
EXISTING |
NEM-BIDDING-VALIDATION-INVALIDPARTICIPANTID |
Invalid Participant Id |
ParticipantId cannot be null. Please provide a valid participantId |
Check your Participant ID |
|
EXISTING |
NEM-BIDDING-VALIDATION-INACTIVEMNSPPARTICIPANTID |
Inactive Participant Id |
PID {0} is not authorised to submit bids for interconnector {1} |
|
|
EXISTING |
NEM-BIDDING-VALIDATION-INACTIVEPARTICIPANTID |
Inactive Participant Id |
This participant ID is not active |
The Participant ID is not active |
|
EXISTING |
NEM-BIDDING-VALIDATION-INVALIDSUBMISSIONREQUEST |
Invalid Request |
Invalid input request |
|
|
EXISTING |
NEM-BIDDING-VALIDATION-ERRORINVALIDUNITREGISTRATION |
DUID registration issue |
DUID {0} has conflicting registration information (start type) and an energy Bid cannot be accepted. |
|
|
EXISTING |
NEM-BIDDING-VALIDATION-ERRORCHECKSUBMISSIONTIMEISBAD |
Bid Processing time violation |
The trading day for this bid has ended |
Check the trading date |
|
EXISTING |
NEM-BIDDING-VALIDATION-ERRORNOPERIODSINBID |
Period Info missing |
No periods defined in bid |
Bid has period IDs 1–288 |
|
EXISTING |
NEM-BIDDING-VALIDATION-ERRORINCORRECTFIRSTPERIODID |
Period data violation |
The first trading interval in the section must be period 1, the period Id mentioned is: {0} |
Check the first trading interval is period 1 |
|
EXISTING |
NEM-BIDDING-VALIDATION-ERRORINCORRECTLASTPERIODID |
Period data violation |
The last trading interval in the section must be period 288, the period Id mentioned is: {0} |
Check the last trading interval is period 288 |
|
EXISTING |
NEM-BIDDING-VALIDATION-ERRORINCORRECTPERIODCOUNT |
Period data violation |
Bid must contain period ID 1 to 288 |
Bid has period ID 1–288 |
|
EXISTING |
NEM-BIDDING-VALIDATION-ERRORPERIODCOUNTLESSTHANZERO |
Period data violation |
Trading interval must exceed zero. Trading interval mentioned is {0} |
|
|
EXISTING |
NEM-BIDDING-VALIDATION-ERRORPERIODCOUNTMORETHAN288 |
Period data violation |
Trading interval cannot exceed 288. Trading interval mentioned is {0} |
Check the trading interval |
|
EXISTING |
NEM-BIDDING-VALIDATION-AVAILABILITYVSMAXISBAD |
Max Availability violation |
Max Availability must be <= Maximum Capacity {1} |
|
|
EXISTING |
NEM-BIDDING-VALIDATION-PASAAVAILABILITYVSOFFEREDMAXISBAD |
PASA Availability violation |
PASA Availability must be >= Max Availability |
PASA availability >= maximum availability |
|
EXISTING |
NEM-BIDDING-VALIDATION-PASAAVAILABILITYVSMAXISBAD |
PASA Availability violation |
PASA availability of {0} exceeds maximum capacity of {1} |
PASA availability not > maximum capacity |
|
EXISTING |
NEM-BIDDING-VALIDATION-CHECKLIMITITEMISNEGATIVE |
Value is Negative |
{0} cannot be negative |
|
|
EXISTING |
NEM-BIDDING-VALIDATION-FIXEDLOADAGAINSTMAXAVAILISBAD |
Fixed Load violation |
Fixed Load cannot exceed maximum availability for the DUID {0} |
Fixed load not is < = maximum availability |
|
EXISTING |
NEM-BIDDING-VALIDATION-PRICEBANDDIFFERS |
Rebid Price Change |
Band Price {0} value {1} differs from last Bid value {2} |
|
|
EXISTING |
NEM-BIDDING-VALIDATION-PRICEBANDSNOTMONOTONIC |
Price violation |
Band prices must increase monotonically |
|
|
EXISTING |
NEM-BIDDING-VALIDATION-PRICEBANDSLESSTHANZERO |
Price violation |
Band prices must be greater than or equal to zero |
|
|
EXISTING |
NEM-BIDDING-VALIDATION-PRICEBANDSUMERROR |
Price violation |
Price band value must be greater than -9999.99 |
|
|
EXISTING |
NEM-BIDDING-VALIDATION-PRICEBAND1LESSTHANNEGATIVEOFBAND1FORWARDFLOW |
MNSP Convex rule violation |
Band prices violate MNSP convexity rule |
|
|
EXISTING |
NEM-BIDDING-VALIDATION-INACTIVEMNSPLINK |
MNSP Link inactive |
MNSP Link {0} invalid or not active. |
Check MNSP link details |
|
EXISTING |
NEM-BIDDING-VALIDATION-INACTIVEINTERCONNECTORID |
IC registration violation |
Interconnector {0} is invalid or not active |
Check interconnector details |
|
EXISTING |
NEM-BIDDING-VALIDATION-ERRORMROPSFRANGE |
MROPSF value violation |
MR Bid Scaling Factor must be between 0 and 9 |
|
|
EXISTING |
NEM-BIDDING-VALIDATION-ERRORMROPSFINVALIDDECIMALS |
MROPSF value violation |
MR Bid Scaling Factor cannot be greater than 4 decimal places. |
|
|
EXISTING |
NEM-BIDDING-VALIDATION-MRCUTOFFTIME |
MR Bid cutofftime violation |
Initial MR Bid is past the MR Bid Cut-off time. |
|
|
EXISTING |
NEM-BIDDING-VALIDATION-NOREBIDREASON |
Rebid Reason missing |
Reason required for rebid |
Provide a reason for the Rebid |
|
EXISTING |
NEM-BIDDING-VALIDATION-NOREBIDEVENTTIME |
Rebid Event time missing |
Event time required for rebid |
|
|
EXISTING |
NEM-BIDDING-VALIDATION-ERRORMRFACTORCHAGEPOSTCUTOFFTIME |
MR Factor value violation |
MR Factor cannot be changed past the MR Bid Cut-off time |
|
|
EXISTING |
NEM-BIDDING-VALIDATION-MISSINGOPPOSITEMNSPLINK |
MNSP bid missing |
Missing MNSP bid for {0} |
Opposite MNSP bid is missing |
|
EXISTING |
NEM-BIDDING-VALIDATION-ERRORPARTICIPANTFORINTERCONNECTOR |
Unauthorized submission |
{0} cannot submit file for link {1} |
Participant ID cannot submit bids for this Interconnector |
|
EXISTING |
NEM-BIDDING-VALIDATION-INVALIDEXPORTLINKTYPE |
Invalid Link Type |
The direction provided for this Link ID {0} is not correct |
Check the interconnector direction |
|
EXISTING |
NEM-BIDDING-VALIDATION-INVALIDIMPORTLINKTYPE |
Invalid Link Type |
The direction provided for this Link ID {0} is not correct |
|
|
EXISTING |
NEM-BIDDING-VALIDATION-ERRORNOINTERCONNECTORFORPARTICIPANT |
MNSP Registration Issue |
{0} cannot submit bid for link {1} as related interconnector participant cannot be found |
Participant ID cannot submit bids for this Interconnector |
|
EXISTING |
NEM-BIDDING-VALIDATION-PARTICIPANTCANNOTSUBMITBIDFORANOTHER |
Unauthorized submission |
PID {0} is not authorised to submit bids for DUID {2} on {3} for service {4} |
Participant ID can submit bids for this DUID |
|
EXISTING |
NEM-BIDDING-VALIDATION-PARTICIPANTCANNOTSUBMITBIDFORANOTHER |
Unauthorized submission |
PID {0} is not authorised to submit bids for interconnector {2} |
|
|
EXISTING |
NEM-BIDDING-VALIDATION-ERRORINVALIDFCASUNITREGISTRATION |
Internal service error |
Missing registration bid details for {0}.Please contact the helpdesk. |
|
|
EXISTING |
NEM-BIDDING-VALIDATION-IMPROPERTRADINGDATE |
Trading date format violation |
Improper trading date format |
Trading date format is one of: yyyy-mm-dd, for example, 2021-04-23 yyyy-mm-dd 00:00:00, for example, 2021-04-23 00:00:00 |
|
TBC |
TBC To be confirmed | TBC |
Cannot correct MPC Rebid - price bands must increase progressively |
Each price band is > previous price band |
| TBC | TBC | TBC |
Daily energy constraint must be less than 1 million MWh |
Daily energy constraint < 1 million MWh |
| TBC | TBC | TBC |
DUID {0} has conflicting registration information (start type) and an energy Bid cannot be accepted |
DUID start type is consistent with registration details |
| TBC | TBC | TBC |
Fast start details must not be provided for slow start units |
Fast start details because they are not permitted for slow start units |
| TBC | TBC | TBC |
Fast start minimum load cannot be negative |
Fast start minimum load is a positive value |
| TBC | TBC | TBC |
Max Availability must be <= Maximum Capacity {0} |
Maximum availability is <= maximum capacity |
| TBC | TBC | TBC |
Missing registration bid details for {0}. Please contact the Support Hub |
DUID details are consistent with registration details |
| TBC | TBC | TBC |
PID {0} is not authorised to submit bids for interconnector {1} or {2} |
Participant ID can submit bids for this Interconnector |
| TBC | TBC | TBC |
Price band {0} value {1} differs from last Bid value {2} |
Rebid price bands = the initial Bid |
| TBC | TBC | TBC |
Price bands cannot be changed for a rebid |
Rebid price bands = the initial Bid |
| TBC | TBC | TBC |
Price bands must be greater than or equal to market floor price |
Price bands >= market floor price |
| TBC | TBC | TBC |
Price bands must be greater than or equal to zero |
Price bands >= zero |
| TBC | TBC | TBC |
Price bands must be less than or equal to market price cap {0} |
Price bands <= market price cap |
| TBC | TBC | TBC |
Price bands violate MNSP convexity rule |
Check the price bands do not violate the MNSP convexity rule |
| TBC | TBC | TBC |
Reason required for low Ramp Rate |
Provide a reason for low ramp up or down rate |
| TBC | TBC | TBC |
The rebid reason must be less than or equal to 500 characters in length |
Rebid reason <= 500 characters |