Time zone ID (as per the IANA time zone database, http://www.iana.org/time-zones, for example: Europe/Amsterdam) indicating the UTC offset that applies to the Period referenced in this message. Although the time zone is a market-wide fixed value, making this assumption explicit in each message is important for validation purposes, allowing implementations to reject messages with an errant UTC offset. A connection that the AGR want the CRO to update EntityAddress of the Connection entity being updated. The first Period hat the AGR represents the prosumer at this Connection. The last Period that the AGR represents the prosumer at this Connection, if applicable. Time zone ID (as per the IANA time zone database, http://www.iana.org/time-zones, for example: Europe/Amsterdam) indicating the UTC offset that applies to the Period referenced in this message. Although the time zone is a market-wide fixed value, making this assumption explicit in each message is important for validation purposes, allowing implementations to reject messages with an errant UTC offset. The Period for which the AGR requests the portfolio information. Time zone ID (as per the IANA time zone database, http://www.iana.org/time-zones, for example: Europe/Amsterdam) indicating the UTC offset that applies to the Period referenced in this message. Although the time zone is a market-wide fixed value, making this assumption explicit in each message is important for validation purposes, allowing implementations to reject messages with an errant UTC offset. The Period that the portfolio is valid. EntityAddress of the CongestionPoint. Indicates whether the DSO accepts mutual exclusive FlexOffers on this CongestionPoint. Indicates which party is responsible for day-ahead redispatch. Indicates which party is responsible for intraday ahead redispatch, AGR or DSO. If not specified, there will be no intraday trading on this CongestionPoint. EntityAddress of the Connection.