The following changes are being introduced with the new eMarket:

1. Participants must submit a unit's Real Time High Operating Limit (RTHOL) value along with its dispatch limits as part of the schedule detail parameter data, pursuant to Market Rule III.13.6.4.1 and to Market Operation Manual M11, §2.5.3 item 27.
2. Some offer parameters must be submitted at the asset level, e.g. unit offer and ARD bid parameters. They must be submitted as part of the schedule detail parameters. Specifically, the dispatch limits must be submitted as part of the schedule detail data; that is: Emergency Minimum, Economic Minimum, Economic Maximum, and Real Time High Operating limits for generators; Minimum Consumption and Maximum Consumption limits for dispatchable Asset-Related Demands (ARDs). This change is introduced to eliminate the precedence confusion that currently exists where a default value is defined at the asset-level, which can optionally be overridden with a daily value in a schedule detail, which in turn can optionally be overridden for a given market day on an hourly basis with hourly override values.
3. All time values that appear in the data exchange messages and XML data files are specified using the lexical representation specified by the ISO 8601 standard, including the time zone indicator, and expressed in Eastern Standard Time. For example, with the lexical representation yyyy-mm-ddThh:mm:ss-hh:mm, 2011-02-01T11:00:00-05:00 represents 11am EST of February 2, 2011. Furthermore, all time values are formulated to represent market hour beginning rather than market hour ending. Thus the value in the example above represents the 12th hour of the market day, with 2011-02-01T00:00:00-05:00 representing the 1st hour of market day 2011 02 01.
4. The maximum number of price-sensitive demand bids that can be submitted for a given hour of a market day has been increased to ten (10).
5. The maximum number of Increment offers or Decrement bids that can be submitted for a given hour of a market day is now limited to fifty (50).
6. New messages are defined to perform explicit deletes using web services or XML file uploads. The following explicit delete operations are defined:
   • Delete an asset schedule, subject to certain restrictions
   • Delete a Load Response Offer
   • Delete a portfolio
     
     Implicit delete operations are supported with submit data messages that contain either hourly or curve data by submitting a message containing an empty container element. Implicit delete operations can be performed with the following submit data messages:
     
     
   • ARD Hourly Override data
   • ARD Ramp Rate data
   • ARD Schedule Bid data
   • Unit Hourly Override data
   • Unit Ramp Rate data
   • Unit Schedule Bid data
   • Unit Regulation Hourly data
   • Demand Bid data
7. The need to specify segment IDs when submitting multi-segmented curve data messages in web services or XML file upload is eliminated and the ability to delete a single segment of data is eliminated. The data can be submitted in any order and eMarket will save it in the required order. To delete a single segment, a whole new set of data without the data segment to eliminate must be submitted. Data sets that fit this curve data model are unit energy offers and ARD energy bids in schedule offer/bid messages. The same principle is applied to price-sensitive demand bids and virtual (Inc/Dec) demand bids although there is no need for eMarket to order the data submitted.

The new eMarket application is enhanced to provide more extensive validation of Participant offers and bids, in particular conflicting parameter offer/bid values. For example,

1. eMarket will ensure that if a unit has a non-zero CSO value, its Economic Maximum dispatch limit is non-zero.
2. eMarket will ensure that the dispatch limits are properly nested while taking into account daily offer values with hourly overrides; i.e., on an hour-by-hour basis, ensure that
   0 ≤ Emergency Min ≤ Economic Min ≤ Economic Max ≤ Real Time High Operating limits.
3. eMarket will ensure that the startup and notification time offer values are properly nested, i.e., "Hot" times ≤ "Intermediate" times ≤ "Cold" times, and that transition times are also properly nested, i.e. Hot-to-Cold time ≥ Hot-to-Intermediate time.
4. eMarket will check that when a unit is flagged as Must Run for an hour, it is not flagged Unavailable for a subsequent hour before its Minimum Run Time is elapsed, and conversely when a unit is flagged as Unavailable for an hour, it is not flagged as Must Run for a subsequent hour before its Minimum Down Time is elapsed. A warning will be returned to the user if either of the rules is violated.
5. eMarket will perform various checks of the Maximum Daily Energy value when one is submitted for a unit and the unit is self-scheduled for any interval of time during the market day. A warning will be returned to the user if any of the rules is violated.

In the XML downloads of Hourly Updates data reports using the old eMarket, you would get limit values for each hour of the market day whether hourly updates had been entered or not. If hourly updates had not been entered, the values being reported were the default values entered at the Asset (Unit or ARD) Manager level and they did not take into consideration whether or not these default values were superseded by values entered at the Schedule Detail level and the report could not take into consideration the situation where a Participant submits different schedules for the Day-Ahead and the Real-Time (aka Balancing) markets.

With the new eMarket, default limit values must be entered at the Schedule Detail level and can no longer be entered at the Asset Manager level. The asset's default dispatch availability status (Economic/Must Run/Unavailable flag) remains entered at the Asset Manager level with no capability to be overridden at the Schedule Detail level. Since a Participant can submit different schedules to be used in the Day-Ahead and in the Real-Time (aka Balancing) markets, the XML download of Hourly Updates data report had to change. They have been changed to report values only for those where an hourly override has been entered by the Participant; if no override has been entered, a NULL value is reported for the value, i.e. the element in the XML report is tagged with the attribute 'xsi:nil="true"'.  This is true for both limit values and the dispatch availability status. To get the asset's applicable limits and dispatch availability status for a market hour where the reported value is NULL, you need to use the value from the applicable schedule (Day-Ahead, Real-Time or Mitigation) report in the case of limits or from the asset report in the case of the availability status.

This design has been implemented for all hourly updates XML download reports: Unit Hourly, ARD Hourly and Regulation Hourly.

The new eMarket has been enhanced to validate more extensively the Participant generation offers and report warnings on inconsistencies within the offer data and on offer data that violates market Monitoring thresholds and thereby expose the overall offer to mitigation.

Data Inconsistency Warnings

1. Claim 10 – A warning is issued if the asset is registered as a Claim 10 resource and the offered Claim 10 value is zero (0), or greater than the demonstrated Claim 10 Capability (CAP) value (if one is defined), or greater than the offered Claim 30 value.
2. Claim 30 – A warning is issued if the asset is registered as a Claim 30 resource and the offered Claim 30 value is zero (0), or greater than the demonstrated Claim 30 Capability (CAP) value (if one is defined).
3. Claim 10 vs startup and notification times – A warning is issued for Claim 10 resources if the sum of the cold startup and notification times is greater than 10 minutes. The warning is to remind the Participant that by submitting such time values, the off-line reserve capability of the unit will not be recognized if it is designated to satisfy the Participant's obligation in the Forward Reserve Market
4. Claim 30 vs startup and notification times – A warning is issued for Claim 30 resources if the sum of the cold startup and notification times is greater than 30 minutes. The warning is to remind the Participant that by submitting such time values, the off-line reserve capability of the unit will not be recognized if it is designated to satisfy the Participant's obligation in the Forward Reserve Market
5. Minimum Run and Minimum Down times for units registered as Claim 10 or Claim 30 resources – A warning is issued if a unit is registered as a resource with off-line reserve capability (i.e. Claim 10 or Claim 30 capable) and non-zero values are submitted for Claim 10 or Claim 30 and values greater than one hour are submitted for Minimum Run and Minimum Down times. The warning is to remind the Participant that by submitting time values greater than one, the off-line reserve capability of the unit will not be recognized if it is designated to satisfy the Participant's obligation in the Forward Reserve Market
6. Automatic (Regulation) Ramp Rate (ARR) – A warning is issued if the submitted value exceeds the demonstrated Automatic Ramp Rate Capability (CAP) value if one is defined.
7. Unit Ramp Rate – A warning is issued if the submitted value exceeds the demonstrated Ramp Rate Capability (CAP) value if one is defined.
8. Economic Maximum limit verso unit's CSO – A warning is issued if the submitted value for the Economic Maximum limit for a unit, in either a schedule detail or in an hourly update, is less than the unit's Capacity Supply Obligation (CSO) when the unit has a non-zero CSO.
9. Must Run vs Minimum Run Time – A warning is issued when a unit's Must Run status is not set for a number of consecutive hours to cover its Minimum Run time within a market day.
10. Unavailable vs Minimum Down Time – A warning if issued when a unit's Unavailable status is not set for a number of consecutive hours to cover it Minimum Down time within a market day.
11. Maximum Daily Energy
    • When a non-NULL value is submitted for a unit's Maximum Daily Energy, a warning is issued if the value submitted is not greater than the Economic Minimum limit x Minimum Run Time for values submitted in the unit's schedule detail and in the hourly updates.
    • When a non-NULL value is submitted for a unit's Maximum Daily Energy and the unit is self-scheduled for a number of hours (not necessarily consecutive and taking into consideration its default dispatch availability status and the hourly override of the status), a warning is issued if the value submitted is not the Economic Minimum limit x the total number of self scheduled hours.

Market Monitoring Threshold Violation Warnings

A warning is issued whenever any of the following offer parameters submitted by a Participant exceeds the threshold associated with the reference value for the parameter set by the ISO-NE Market Monitor:

• Hot / Intermediate / Cold Startup cost
• No Load cost
• Economic Maximum limit
• Economic Minimum limit
• Emergency Minimum limit

Pursuant to the revisions of the Market Rule Appendix A for automation of the mitigation of Participant offers, the new eMarket has been enhanced to reject offers for the following parameters that violate the threshold on the reference value set by the ISO-NE Market Monitor:

• Hot / Intermediate / Cold Startup time
• Hot / Intermediate / Cold Start Notification time
• Hot to Cold time
• Hot to Intermediate time
• Minimum Down time
• Minimum Run time
• Sum of Startup, Notification, Minimum Run and Minimum Down time offer values exceeds the sum of the same reference values by more than a threshold value for each set of the Hot, Intermediate, Cold values.

The eMarket application can be accessed through Internet web browsers that support SSL 3.0 secured 128-bit encryption. The following web browsers have been verified to work with the new eMarket Market User Interface (MUI):

• Microsoft Internet Explorer v8.0

  Although eMarket has been verified to work with Internet Explorer v7.0, performance in rendering certain web pages is poor. It has not been verified with Internet Explorer v6 since that version is no longer supported by Microsoft and it is expected that performance would be worse with this version. It is therefore highly recommended that users of Internet Explorer upgrade to version v8.0. eMarket has not yet been verified to work with Internet Explorer v9.0.

• Mozilla Firefox version v11.0
• Google Chrome v16.0