Service and Terms Advertisement, In or Out?

On the border between EMIX and WS-Calendar, there a number of constraints on requests one cam make to a service. These constraints appear in EMIX in the Terms schema.

 

Terms are abstracted away from the generation characteristics of generation resources as defined by the IEC TC57. Constraints define restrictions on invoking a service. As defined in EMIX:

 

Operating Terms

 

Term

Description

Minimum Response Duration

The shortest Duration for which a request will be accepted.

Maximum Response Duration

The longest Duration for which a request will be accepted.

Minimum Recovery Duration

The minimum Duration after completion of a response before a new response can be begun.

Minimum Duration Between Invocations

The minimum Duration between successive responses that will be accepted.

Minimum Notification Duration

The minimum Duration in advance of a proposed response that a notification will be accepted.

Maximum Notification Duration

The maximum Duration in advance of a proposed response that a notification will be accepted.

Response Time

Duration required from receipt of a request to supplying the full requested level of response; i.e., notification time plus
 response time.

Maximum Invocations Per Duration

Maximum number of requests for response that will be accepted during a Duration.

Maximum Consecutive Durations

Maximum consecutive Durations in which a notification will be accepted; e.g., it will not accept requests on more than three
 consecutive days.

Maximum Run Duration

Maximum acceptable Duration for a proposed response

Minimum Run Duration

Minimum acceptable Duration for a proposed response

 

 

Schedule Terms

 

Term

Description

Availability Schedule

A schedule of time windows during which a response may be scheduled. A scheduled Duration must be entirely within a single instance of an availability window.

Unavailability Schedule

A schedule of time windows for which no request for response will be accepted. No part of a requested Duration must coincide with an unavailability window.

Notification Schedule

A schedule of time windows during which requests can be made.

 

 

Market Requirements (A door to a whole set of interesting oBIX 2.0 issues)

 

Market Requirement

Description

Market Granularity

The size of a market “bundle”. For example, a Market with a granularity of 10 MW, will only accept tenders, process transactions, and pay for delivery of Power in multiples of 10MW.

Minimum Economic Requirement

Minimum net remuneration for any single response

Required Startup Remuneration

Minimum remuneration required for initiating a response.

Minimum Starts Per Duration 

The fewest requests that the resource will accept during any Duration.

Minimum Remuneration Rate

Minimum remuneration acceptable per stated Duration of response. For example, a minimum remuneration of $100 per hour.

 

 

I leave it to committee members whether it would be useful to define a lobby point for _expression_ of terms in oBIX 2.0…

 

tc

 

 

"You can cut all the flowers but you cannot keep spring from coming."

-Pablo Neruda

Toby Considine

Chair, OASIS oBIX TC

Editor, OASIS EMIX, Energy Interoperation

Finance & Administration IT

University of North Carolina

Chapel Hill, NC

  

Email: 
Toby.Considine@ unc.edu

Phone: (919)962-9073 

http://www.oasis-open.org 

http://www.NewDaedalus.com