The server can be operated in two different deployment configurations: a research configuration, and a tournament configuration.

Core entities of the Power TAC environment with their dependency relationships and responsibilities.

Communication between the Server and Broker agents is by exchange of "command" instances, packaged as payloads in messages transported via ApacheMQ.

What gets logged, and how are logfiles managed? What exceptions are we using, which ones are recoverable, how does the server recover from exceptions, and where are they raised and handled?

Game visualizer overview, technology overview and description.

How simulation time is measured and managed.

Tariffs are published and revoked by the brokers. Customers can subscribe or negotiate a published tariff. A subscribed tariff is a contract and lasts one or more days. As the accounting service is responsible for storing tariffs and logging contract relationships it acts as an intermediary entity between brokers and customers.

Also known as "Demand-Side Management." Customers may have some portion of their consumption, production, or storage capacity that can be remotely controlled by the DU for balancing purposes, or by a Broker for cost reasons.

How the server is configured, how configuration information is represented and communicated to the server.

Structure and operation of customer models. There's also information on specific customer models.

Ideas for implementing a broker framework in the R language.

A collection of operational scenarios to help clarify and understand how the server works.