Examples of Testing Participant in a sentence
Section X11.8 of the Code specifies that Section H14 of the Code (Testing Services) and the Enduring Testing Approach Document shall apply in respect of testing under a SEC Variation Testing Approach Document as if such testing was a Testing Service under Section H14.34 (Modification Implementation Testing); and each participant in such testing shall be deemed to be a Testing Participant for such purposes.
Where the Testing Participant disagrees with the DCC’s determination pursuant to Section H14.41 of the matters set out at Section H14.39(c) (but not otherwise), then the Testing Participant may request that the DCC refers the matter to the Secretary of State.
Except in the circumstances set out in Clause 14.5, where a disagreement exists pursuant to Clause 14.2, the determination of the DCC including assigned Testing Issue severity shall remain and be included in any evaluation until the TAG reaches its determination and notifies the DCC and the Testing Participant for the purposes of this Code.
Such notice shall provide the DCC with reasonable detail on the manner in which the Testing Participant will utilise Migration DUST.
Where that Testing Participant chooses not to configure test Devices it shall notify the DCC.
The process set out in Section H14.37 onwards of the Code shall apply for the purposes of Testing Issue resolution during SIT, UTS, SCT, and MT; subject to Clause14.2 and Clause 14.3. Where a Testing Participant disagrees with a determination by the DCC pursuant to Section H14.39(a) (with regards to the severity level only) then the matter may be referred to the TAG, whose decision will be final and binding for the purposes of this Code.
Where the DCC provides test Devices, the Testing Participant shall configure, where the configuration tool is available, the test Devices in accordance with the settings provided in the SMETS1 Supporting Requirements prior to Migration within Migration DUST.
Where a Testing Participant provides test Devices for use in Migration DUST that Testing Participant may determine whether or not, prior to Migration, the Devices are configured in accordance with the settings provided in the SMETS1 Supporting Requirements.
The DCC shall only be required to make available Migration DUST to a Testing Participant where the DCC has received at least 40 Working Days’ notice from that Testing Participant of its intention to undertake Migration DUST, or such lesser notice that the DCC reasonably agrees.
Where a Testing Participant disagrees with a determination by the DCC pursuant to Section H14.39(a) (with regards to the severity level only) then the matter may be referred to the TAG, whose decision will be final and binding for the purposes of this Code.