Position Manager in EML-CTS

[William Cox <wtcox@coxsoftwarearchitects.com>]

Background:

EML-CTS is an open source implementation of the Common Transactive Services and is at https://github.com/EnergyMashupLab/eml-cts .

The code may be viewed as an application profile, guiding definition and evolution of CTS message-based interactions.

The Position Manager is described in the project wiki at https://github.com/EnergyMashupLab/eml-cts/wiki/Position-Manager :

Position Manager

See packages org.theenergymashuplab.cts.controller.payloads, .model, .dao, and .repository for details.

The Position Manager uses JPA to store its information. The REST API for the PositionManager RestController is

1. POST: /position/{positionParty}/add adds a position for a particular Party and time interval, creating a database row if not present.
2. GET: /position/{positionParty}/getPosition retrieves the position for a specific Party and time interval

Position Manager Model

PositionManagerModel represents the database table.

Position Repository

PositionRepository contains all the native SQL queries.

      The notion is that previous purchases and sales are reflected in
      summary in the position for a particular instrument (time
      interval, implicit product) and can be used to determine what's
      already committed and compare to what's needed.

In other words, the user/building/controller using the position manager can say "I need 20 kWh in this time period" and the User Agent could say "you already have bought 30, so I'll sell 10", or "you have 10, so I'll buy another 10".

This is not presently used in the EML-CTS implementation (source code at https://github.com/EnergyMashupLab/eml-cts) but is planned for optional future use.

Thanks!

bill cox

--

William CoxÂ

Email: wtcox@CoxSoftwareArchitects.comÂ

Web: http://www.CoxSoftwareArchitects.comÂ

+1 862 485 3696 mobile