MIMS

We have added a new subsystem to NEOmobile called MIMS which stands for MITC Information Management System. While mostly of interest to TNSPs we are making it generally available for a limited time – feedback as always is welcome! For background under the AER’s MITC scheme, TNSPs are financially punished by between $4k and $15k (varies for each TNSP) for every constraint related to the outage that binds with an absolute marginal value greater than or equal to $10.

The MIMS system monitors and reports on network outages and associated Generic Constraint sets. You can find the MIMS events on Overview 1 of NEOmobile. The types of information you will find in the MIMS events include:

• A network outage is starting or is scheduled to start in the near future.
• Any constraints sets that are associated with the outage.
• A constraint set invocation that is associated with a network outage is starting or scheduled to start in the near future.
• A constraint set associated with a network outage has constraints with a high marginal value in dispatch, p5min, or predispatch.

Data used by MIMS

MIMS monitors a number of tables to generate its event messages. These include:

• NETWORK_OUTAGEDETAIL – Schedule of network outages.
• NETWORK_SUBSTATIONDETAIL – Substation details associated with outage.
• NETWORK_OUTAGECONSTRAINTSET – Generic constraint sets associated with an outage.
• GENCONSETINVOKE – Invocations of generic constraints.
• GENCONSETID – Generic constraints associated with a Generic constraint set.
• GENCONDATA – Generic constraint information.
• SPDREGIONCONSTRAINT – Region terms in the LHS of a generic constraint.
• SPDCONNECTIONCONSTRAINT – Trader terms in the LHS of a generic constraint.
• SPDINTERCONNECTORCONSTRAINT – Link terms in the LHS of a generic constraint.
• DISPATCHCONSTRAINT – constraint solution data from dispatch.
• P5MIN_CONSTRAINTSOLUTION – constraint solution data from P5MIN.
• PREDISPATCHCONSTRAINT – constraint solution data from predispatch.
• DUDETAILSUMMARY – unit details.
• INTERCONNECTOR – Interconnector details.

Example messages

Outage

Outage 813871 will start in 8 hours (2018-11-28 08:00 - 2018-11-28 16:00) on equipment: 275KV_879 (LINE), substation = H13_ROSS, owner = Powerlink, region = QLD1; 275KV_879 (LINE), substation = H35_STHM, owner = Powerlink, region = QLD1. Related invocation: 158338 (2018-11-28 08:05 - 2018-11-28 16:00), on set Q-SMRS, affecting regions [QLD1]

• The given outage will start in 8 hours, 1 hour, or immediately.
• Equipment involved in the outage is listed.
• A related generic constraint invocation is given (if available).

Invocation (directly related to an outage)

Generic constraint set invocation 158338 starting in 8 hours (2018-11-28 08:05 - 2018-11-28 16:00), Set Q-SMRS, regions [QLD1]. Related outage: Outage 813871 (2018-11-28 08:00 - 2018-11-28 16:00), on equipment [275KV_879]

• The given generic constraint invocation will start in 8 hours, 1 hour, or immediately.
• The sets and associated affected regions are listed
• The related outage is given.

Invocation (indirectly related to an outage)

Generic constraint set invocation 157443 starting in 8 hours (2018-11-28 07:05 - 2018-11-29 17:00), Set S-WE_MWP4_RB, regions [SA1, VIC1]. Possible related outage: Outage 814562 (2018-11-28 11:00 - 2018-11-29 14:00), on equipment [4CAP_4B_66], affecting region [VIC1]

• The given generic constraint invocation will start in 8 hours, 1 hour, or immediately.
• The sets and associated affected regions are listed
• Outages possibly related to the invocation are listed. There may be more than one outage listed.

High Marginal Value

High constraint marginal value detected in predispatch. ID = F_T+FASH1_2C_RREG, 2018-11-27 16:00, MV = -21.77348, region: [TAS1], limit type = Unit Zero - FCAS, description: Out = Farrell to Sheffield No.1 or 2 line; John Butters, Tribute and Reece 1, 2 unavailable for raise FCAS. Invocation 158186 [F-T-FASH_1_2_C] 2018-11-27 08:05 - 2018-11-27 16:00

• A constraint (possibly) associated with an outage has a marginal value outside the range +/- 10 in predispatch, p5min, or dispatch.
• The constraint ID is given with the time(s) and marginal value(s), with details about the constraint.
• The constraint set invocation is given.

Relating Outages to Constraint Set Invocations

Note that not all outages are directly related to a generic constraint set invocation via the NETWORK_OUTAGECONSTRAINTSET table. In these cases an indirect association is attempted based on the following criteria:

• The start-end dates of the invocation and outage roughly match
• There is some intersection between the regions associated to the invocation and the outage

Note that indirect matches between outages and invocations are suggestions only.