Thank you to everyone who joined us for the webinar A Lap Around TROLIE 1.0! Please see the recap below, including the Q&A.

1.0.0 Release

With this release the project is committing to a stable specification and any modifications will update the version per the versioning strategy, but there will be no breaking changes going forward in the TROLIE 1.0 project.

Accordingly, the permanent location for the specification is now trolie.energy/spec-1.0. (Existing links to trolie.energy/spec will redirect.) The next phase of the project is integration and testing of TROLIE implementations, and we anticipate needing minor updates to the specification. These will not be breaking changes, as stated, so expect to see the spec version to change accordingly. When all is said and done the TROLIE 1.0 project’s API specification may have a version number of 1.1.8, but that will be considered TROLIE 1.0. Again, we refer the reader to the versioning strategy for more details.

Webinar Recap

Q&A

Is the Java client the underlying engine for GE’s LEP product?

The GE Vernova Limit Exchange Portal does make use of the Java client.

Is a .NET client sdk also being considered or just create our own based on how the java sdk is done?

A .NET client would be a fantastic contribution to the project, but it is not currently on the roadmap. If this is something you are interested in helping get off the ground, please contact the maintainers.

Is there a TO-to-TO ratings clearinghouse for shared facilities similar to the RC-to-RC seams process that was discussed? Local “global” ratings will need to be determined.

If a TO is within an RC footprint, then TROLIE’s expectation is for the Reliability Coordinator (RC) to host the Clearinghouse, such that TO-to-RC-to-TO will serve all the coordination needs. Transmission Owners can obtain detailed limits snapshots from their RC’s Clearinghouse to obtain the ratings that were provided by their neighboring Transmission Owners.

Some Transmission Providers/RCs may also have the underlying seasonal ratings from each Transmission Owner in the detailed seasonal ratings snapshot, unless that seasonal rating determination is made by the TOP and contributed directly by them.

However, if a TO is also serving RC responsibilities, as may be required of a vertically-integrated utility, then this same RC-to-RC process may be used to coordinate with that TO’s neighbors.

I would love to see more examples of what it will look like from a utility side and break down the payloads that [Ratings Providers] will be sending in to [their RC].

Watch this space: better forecast submission examples and detailed walkthrough · Issue #216 · trolie/spec.