eric/cariflex
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add extracted tools: CitrineOS, OpenOCPP, ShapeShifter

Browse Source 
- CitrineOS core extracted (CSMS OCPP 2.0.1)
- OpenOCPP extracted (firmware OCPP 1.6J/2.0.1)
- ShapeShifter library installed (pip install -e)
- ShapeShifter specification extracted
- EVerest extracted

TODO updated with progress
This commit is contained in:
Eric F
2026-06-08 00:38:27 -04:00
parent 468cfeaa50
commit d398a6ced2
7326 changed files with 1177561 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

42
tools/shapeshifter-specification-main/docs/about/levels-of-compliancy.md Normal file
View File

@@ -0,0 +1,42 @@
<!--
SPDX-FileCopyrightText: 2020-2023 Contributors to the Shapeshifter project
SPDX-License-Identifier: Apache-2.0
-->
# Levels of compliancy
UFTP has mandatory components and optional components.
The tables below list all core and optional components.
Support of core components is mandatory for all implementations.
Optional components are signaled throughout the document.
Optional components in messages are always prefixed with [optional].
| Core UFTP components | USEF 2015 | UFTP | Signaled in CRO? |
| ------------------------------------ | :-------: | :----: | :--------------: |
| **UFTP process:** | | | |
| Day-ahead Flex trading | o | o | - |
| Redispatch responsibility choice | - | o | Y |
| Baseline choice | - | o | Y |
| **Market messages:** | | | |
| FlexRequest | o | o | - |
| FlexOffer | o | o | - |
| FlexOfferRevocation | o | o | - |
| FlexOrder | o | o | - |
| FlexSettlement | o | o | - |
| Optional UFTP components | USEF 2015 | UFTP | Signaled in CRO? |
|--------------------------------------|:---------:|:------:|:----------------:|
| **UFTP Process:** | | | |
| Intraday Flex Trading | o | o | N |
| Availability contracts (FlexOptions) | ~[^1] | o | N |
| Dynamic pooling | - | future | ? |
| **Market messages:** | | | |
| D-prognosis | o | o | Y |
| FlexReservationUpdate | - | o | N |
| FlexOffer: mutual exclusive offers | - | o | Y |
| FlexOffer: unsolicited offers | - | o | - |
| FlexOffer: partial activation | - | o | - |
[^1]: Availability contracts were mentioned in USEF2015, but not all details were worked out

12
tools/shapeshifter-specification-main/docs/about/purpose.md Normal file
View File

@@ -0,0 +1,12 @@
<!--
SPDX-FileCopyrightText: 2020-2023 Contributors to the Shapeshifter project
SPDX-License-Identifier: Apache-2.0
-->
# Purpose
The USEF Flex Trading protocol (UFTP) is a subset of the USEF framework.
Focused specifically on the exchange of flexibility between Aggregators (AGRs) and DSOs, it describes the corresponding market interactions between them to resolve grid constraints by applying congestion management or grid-capacity management.
UFTP can be used as a stand-alone protocol for flexibility forecasting, offering, ordering, and settlement processes.
Its purpose is to support the use of flexibility markets for grid-congestion issues and standardize the set-up and operation of these markets across different DSOs.

34
tools/shapeshifter-specification-main/docs/about/reading-guideline.md Normal file
View File

@@ -0,0 +1,34 @@
<!--
SPDX-FileCopyrightText: 2020-2023 Contributors to the Shapeshifter project
SPDX-License-Identifier: Apache-2.0
-->
# Reading guideline
The USEF Flexibility Trading Protocol Specification is accompanied by ‘USEF: The Framework explained’ [^B4] which provides insight into the background, scope and concepts underpinning USEF.
It is strongly advised that the USEF document is read in advance of this UFTP specification document.
[^B4]: USEF Foundation, "USEF: The Framework Explained," USEF Foundation, Arnhem, 2015.
USEF follows the principle of privacy & security by design and therefore the specifications are accompanied by a privacy & security guideline [^B5] which is applicable to the entire design, implementation and operation of USEF and derived products, services and solutions.
[^B5]: USEF Foundation, "USEF: The Privacy and Security Guideline," USEF Foundation, Arnhem, 2015. Available: [https://www.usef.energy/app/uploads/2016/12/USEF_PrivacySecurityGuideline_3nov15.pdf](https://www.usef.energy/app/uploads/2016/12/USEF_PrivacySecurityGuideline_3nov15.pdf)
The UFTP specifications consist of three main elements:
- [General description](../general-description/index.md)
Informative description about usage of the protocol and process description for USEF’s market-based coordination mechanism
- [Use case descriptions](../use-case-descriptions/scope.md)
Detailed descriptions of each process step of the process model, incl. scope & level, goal in context, preconditions, primary and secondary actors, the main scenario, etc.
- [Message transport & descriptions](../message-descriptions/scope.md)
Syntax descriptions of all the messages required for the interfaces described in the framework, as well as detailed requirements for exchanging those messages.
A process description, including the specifications and rules that apply to each process, are provided.
A motivation for the design is included, wherever it is assumed beneficial.
!!! success "Recommended Practice:"
In order to make the universal descriptions of the framework applicable in practice and more comprehensible the specifications are accompanied by recommended practices.
These paragraphs are clearly indicated, in blue, throughout the specifications.

68
tools/shapeshifter-specification-main/docs/about/scope.md Normal file
View File

@@ -0,0 +1,68 @@
<!--
SPDX-FileCopyrightText: 2020-2023 Contributors to the Shapeshifter project
SPDX-License-Identifier: Apache-2.0
-->
# Scope
## Constraint management services
Constraint management services help grid operators (TSOs and DSOs) to optimize grid operation according to physical and market constraints.
USEF [^B1] distinguishes four different flexibility services within the constraint management category: grid capacity management, congestion management, voltage control and controlled islanding.
UFTP can be used for the first two of these.
[^B1]: USEF, "Flexibility Value Chain (update 2018)," 8 10 2018. [Online]. Available: [https://www.usef.energy/app/uploads/2018/11/USEF-White-paper-Flexibility-Value-Chain-2018-version-1.0_Oct18.pdf](https://www.usef.energy/app/uploads/2018/11/USEF-White-paper-Flexibility-Value-Chain-2018-version-1.0_Oct18.pdf).
### Grid capacity management
Grid capacity management refers to the use of explicit demand-side flexibility (by the DSO or TSO) to increase operational efficiency without impacting freedom of dispatch, trade and connect (copper plate principle).
It is primarily used to defer grid reinforcements, optimize asset operational performance, reduce grid losses, or support planned maintenance.
The implication is that AGRs (and prosumers) participate in the product on a voluntary basis; i.
e.
motivated by appropriate financial incentives.
### Congestion management
Congestion management refers to the use of flexibility to reduce peak loads, in order to avoid system overload and the associated component or system failures.
Contrary to grid capacity management, it will typically limit freedom of dispatch, trade and/or connect.
It is primarily used in unanticipated overload situations; e.
g.
those which could not be forecast during long-term grid planning processes, or where load/ generation increases have outpaced grid reinforcement efforts.
Congestion management is a temporary solution (typically until grid reinforcement takes place) and is a highly-regulated mechanism.
At present, it is only available to TSOs in most European member states although it may be offered to DSOs in the future.
The two mechanisms differ in the freedom of dispatch, trade and/or connect and this is handled via contracts and will have impact on the settlement components.
## Bilateral trading and trading via a market platform
![](../assets/images/image3.emf.odg.svg.png)
UFTP is designed for bilateral trading between the AGR and DSO.
Trading via market platforms can bring added value, see [^B2].
In UFTP, market platforms may take the role of trading counterparty, hence serving as a DSO proxy in trades with the AGR, and as an AGR proxy in trades with the DSO.
When trading via a platform, the role of FlexRequests from DSOs to AGRs is less obvious; i.e., a DSO has free choice of the available FlexOffers.
In addition, FlexOffers and FlexRequests do not need to be directly related and so UFTP supports unsolicited FlexOffers without requiring a reference to an underlying FlexRequest.
## TSO/DSO coordination
![](../assets/images/image4.emf.odg.svg.png)
USEF assumes that a DSO or TSO can freely and independently trade flexibility with AGRs.
Any potential goal conflicts can be settled through the market mechanism.
Alternatively, TSO and DSO requests can be aligned, resulting in a TSO/DSO coordination platform where TSOs and DSOs coordinate the tendering, trading, activation and/or settlement of flexibility for their own purposes ( i. e. ancillary services).
See [^B2] for a discussion on this topic.
[^B2]: USEF, "White paper: Flexibility Platforms," 2 november 2018. [Online]. Available: [https://www.usef.energy/app/uploads/2018/11/USEF-White-Paper-Flexibility-Platforms-version-1.0_Nov2018.pdf](https://www.usef.energy/app/uploads/2018/11/USEF-White-Paper-Flexibility-Platforms-version-1.0_Nov2018.pdf).
UFTP can be applied without any further changes in a configuration where there is TSO/DSO coordination.
## Alternative use
The text, graphs and examples in this document assume flex trading between AGR and DSO.
However, UFTP can equally be used for grid constraint services between an AGR and TSO.
The messages defined in UFTP can also be used for flexibility trading in the plan phase between an AGR and BRP.
See the USEF Framework Specifications [^B3] for a complete description of this alternative use.
[^B3]: USEF, "USEF - The FrameWork Specifications 2015," 2015. [Online].