# DSOPortfolioUpdate
The DSOPortfolioUpdate is used by the DSO to indicate on which congestion points it wants to engage in flexibility trading.
```
/>
/>
```
| | |
|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Metadata | The metadata for this message. For details, see [metadata attributes](metadata-attributes.md). |
| CongestionPoint | |
| ⇥ EntityAddress | Entity Address of the CongestionPoint entity being updated. |
| ⇥ StartPeriod | The first Period that the DSO is trading on this CongestionPoint. |
| ⇥ EndPeriod | The last Period that the DSO is trading on this CongestionPoint. |
| ⇥ MutexOffersSupported | Indicates whether the DSO accepts mutual exclusive FlexOffers on this CongestionPoint |
| ⇥ DayAheadRedispatchBy | Indicates which party is responsible for day-ahead redispatch, AGR or DSO. |
| ⇥ IntradayRedispatchBy | Indicates which party is responsible for intraday ahead redispatch, AGR or DSO. If not specified, there will be no intraday trading on this CongestionPoint. |
| ⇥ Connection | |
| ⇥ ⇥ EntityAddress | Entity Address of a Connection that is part of this CongestionPoint. |
| ⇥ ⇥ StartPeriod | The first Period that the Connection is part of this CongestionPoint. Notes:
- The StartPeriod of a Connection should be greater than or equal to the StartPeriod of the CongestionPoint.
- The StartPeriod of a Connection should be smaller than or equal to the EndPeriod of the CongestionPoint.
- CRO implementors may choose to explicitly check for this and reject updates that do not comply.
|
| ⇥ ⇥ EndPeriod | The last Period that the Connection is part of this CongestionPoint. Notes: - The EndPeriod of a Connection should be null if and only if the EndPeriod of the CongestionPoint is null.The EndPeriod of a Connection should be greater than or equal to the StartPeriod of the CongestionPoint.
- The EndPeriod of a Connection should be smaller than or equal to the EndPeriod of the CongestionPoint.
- CRO implementors may choose to explicitly check for this and reject updates that do not comply.
|