About this document · Web viewCMOS will process the inbound transaction and send a T102.M...

Pro forma document that applicants should use to completetheir corresponding Participant detailed MEAT plan.

Pro forma Participant Detailed Market Entry Assurance Test Plan

04 March 2016

[Market Participant] detailed MEAT plan

About this document

This document should be read in conjunction with the MOSL detailed Market Entry Assurance Testing (MEAT) plan. It is a template that applicants should use to complete their own corresponding Participant detailed MEAT plan.

Details of how to do this are contained within here and the MOSL detailed MEAT plan.

Confidentiality

Any information provided through the Participant detailed MEAT plan will be held securely and will only be used for the purposes defined in this request. MOSL will fully respect any level of confidentiality marking attached to your information and in so doing will comply fully with the provisions of the Data Protection Act 1998.

Page | 2

1. Participant detailed MEAT planPlease complete this application and e-mail it to: [email protected].

2. MEA Testing ObjectivesThe objective of MEA testing is to ensure that market applicants and MOSL can prove that they can successfully communicate between systems and obtain MEAC to enable trading to commence.

MEAT is made up of two levels of testing:

1. Interface and Data Transaction Testing (IDTT).

2. Market Scenario Testing

Page | 1MOSL Ref:

Applicant Company Name:

[Applicant company name]

Applicant Market Role: [Wholesaler or Retailer]Applicant Responsible Tester:

[Your name]

Applicant Responsible

Tester Contact Details:

[Your email][Your contact number]

Applicant Accountable

Owner:

[Accountable tester name]

Date: [Plan submission date]

MEAT Plan Version & Status:

0.1 Draft

MOSL Test Analyst: [To be provided by MOSL]


3. Test ApproachApplicants should document how they will implement the test approach within the MOSL detailed market entry assurance test plan. This should cover the design, build, execution and evaluation stages as set out in the MOSL detailed MEAT plan.

3.1 MEAT design & build

3.1.1 Creating required test data

The MOSL Test Analyst will provide a list of the test data required to be set up in an applicant’s system, set up in CMOS via IDTT and the data values required to be submitted during market scenario testing.

Applicant’s should include in this section their approach to setting up test data in their systems ready for IDTT and market scenario testing.

Further information on creating test data is contained in Section 3.8 of the MOSL detailed MEAT plan.

Page | 2

MOSL Ref:


3.1.2 Processing market scenarios

In this section applicants should set out the steps that will be undertaken to complete the Market Scenario Testing, the expected result and the evidence they intend to provide in support of this.

The following pages provide a list of generic market scenario test cases. In the Applicant Information Return, applicants will have identified which of these are applicable to their situation. In the Participant detailed MEAT plan applicants are required to make these test cases specific to them, by setting out each step through their systems they will follow to achieve the action and what they expect their system to do in response. This should then be a complete representation of the end to end tests a market applicant will complete.

For instance, taking Market Scenario #1: - Register new supply point (SPID) and Step 1 for a Wholesaler, the generic step is:

As a Wholesaler, in order to register a SPID, I will submit a valid T101.W with the Retailer specified and the eligible premises have a paired SPID.

The applicant specific equivalent of this might be:

In system A, carry out B to generate a T101.W Manually enter C Carry out D to submit the valid T101.W to CMOS

This should be represented by adding steps to and otherwise customising the generic market scenarios, for instance:

Generic Step Ref

Generic Action

Specific Actions Expected Result

1 As a Wholesaler, in order to register a SPID, I will submit a valid T101.W with the Retailer specified and the eligible premises have a paired SPID.

- In system A, carry out B T101.W generated on screen- Manually enter C T101.W populated on screen- Carry out D to submit the valid T101.W to CMOS

T101.W submitted and “Form submitted” message received

The customised scenarios should include all steps the applicant will need to undertake, including the corresponding steps to be carried out by MOSL (representing the counterpart of Wholesaler or Retailer as included already) and processing of the expected results received from the CMOS system.

Page | 3

MOSL Ref:


Finally, applicants should include the evidence they intend to provide for each step, to demonstrate that their systems have performed the expected result. It is up to applicants what format this evidence is provided in, and is expected to depend on the nature of their systems. Appropriate formats could for instance be screenshots or log files.

Evidence is not required for every sub-step, but should be provided to an appropriate level to demonstrate that the documented market scenario test case has been followed.

A completed example for the Market Scenario #1: - Register new supply point (SPID) and Step 1 for a Wholesaler might be:

Generic Step Ref

Generic Action

Specific Actions Expected Result Evidence Provided


- In system A, carry out B T101.W generated on screen

Screenshot of generated T101.W

- Manually enter CT101.W populated on screen

- Carry out D to submit the valid T101.W to CMOS

T101.W submitted and “Form submitted” message received

Screenshot of sent items section, showing submitted T101.W

CMOS will validate the inbound transaction and send a T109.M transaction confirming receipt to the Wholesaler.

- Receive T109.M in system A

T109.M shown on screen Screenshot of receipt of T109.M

- Process T109.M in system B

System B shows “Form received by CMOS”

CMOS will process the inbound transaction and send a T102.M transaction to the relevant Wholesaler and Retailer, to notify the partial registration.

- Receive T102.M in system A

T102.M shown on screen Screenshot of receipt of T102.M

- Process T102.M in system B

System B shows “SPID partially registered”

Screenshot of “SPID partially registered”

Applicants should submit their market scenario test cases in a standardised format such as Microsoft Word or Excel. Page | 4

MOSL Ref:


3.1.2.1Market Scenario #1: - Register new supply point (SPID)Whether the Market Applicant is a Wholesaler or Retailer, they will be expected to carry out the relevant steps, all other roles will be undertaken by MOSL.

Step Action

(Market Applicant to describe how they will do this via their systems)

Expected Result

(Market Applicant to describe how they will process this via their systems)


CMOS will:

Validate the inbound transaction and send a T109.M transaction confirming receipt to the Wholesaler.

Process the inbound transaction and send a T102.M transaction to the relevant Wholesaler and Retailer, to notify the partial registration.

2 As a Retailer, in order to accept the partially registered SPID, I will send a valid T103.R transaction to CMOS.

CMOS will:

Validate the inbound transaction and send a T109.M transaction confirming receipt to the Retailer.

Process the inbound transaction and send a T103.M transaction to the relevant Wholesaler and Retailer, to notify the partial registration acceptance.

3 As a Retailer, in order to submit a Yearly volume estimate for the new supply point, I will submit a valid T146.R transaction to CMOS.

CMOS will:


Process the inbound transaction and send a T146.M transaction to the relevant Wholesaler and Retailer, to notify the yearly volume estimate.

4 As a Retailer, in order to submit Occupancy Status for the new supply point, I will submit a valid T112.R transaction to CMOS.

CMOS will:


Process the inbound transaction and send a T112.M transaction to the relevant Wholesaler and Retailer, to notify the Occupancy Status.

Page | 5

MOSL Ref:


Step Action


Expected Result


5 As a Retailer, in order to submit Retailer Meter Location Data for the new supply point, I will submit a valid T160.R transaction to CMOS.

CMOS will:


Process the inbound transaction and send a T160.M transaction to the relevant Wholesaler and Retailer, to notify the Retailer Meter Location Data.

6 As a Retailer, in order to submit Billing Address for the new supply point, I will submit a valid T156.R transaction to CMOS.

CMOS will:


Process the inbound transaction.

7 As a Retailer, in order to submit Customer Core Data for the new supply point, I will submit a valid T132.R transaction to CMOS.

CMOS will:


Process the inbound transaction and send a T132.M transaction to the relevant Wholesaler and Retailer, to notify the Customer Core Data.

8 As a Wholesaler, in order to complete connection of the new SPID, I will submit a valid T107.W.

CMOS will:


Process the inbound transaction and send a T107.M transaction to the relevant Retailer, to notify the completed connection.

Page | 6

MOSL Ref:


3.1.2.2Market Scenario #2: - Transfer registration (Gain/Loss)Whether the Market Applicant is a Wholesaler or Retailer, they will be expected to carry out the relevant steps, all other roles will be undertaken by MOSL.

Step Action


Expected Result


1 As the Incoming Retailer, in order to initiate a Transfer, I will send a valid T108.R transaction to CMOS.

CMOS will:

Validate the inbound transaction and send a T109.M transaction confirming receipt to the incoming retailer.

Process the inbound transaction and send a T108.M transaction to the relevant outgoing Retailer and Wholesaler, to notify the transfer registration has started.

Send the following transaction to the Incoming Retailer providing information on the SPID to be transferred, where relevant from the following list: T112.M, T132.M, T149.M, T152.M, T153.M, T154.M, T133.M, T156.M, T157.M, T163.M, T139.M, T140.M, T144.M, T145.M, T147.M, T158.M, T159.M, T129.M, T138.M, T150.M, T104.M, T136.M, T160.M, T121.M, T123.M, T168.M, T128.M, T167.M, T149.M

In live operation a 5 day wait period would now start, but for MEAT purposes this will not occur.

2 As the Incoming Retailer, in order to submit the transfer meter read, I will send a valid T105.R transaction to CMOS.

CMOS will:


Process the inbound transaction and send a T105.M transaction to the relevant outgoing Retailer and Wholesaler, to notify the transfer meter read details.

Where the market applicant is a retailer, they will now take on the role of outgoing retailer, and MOSL will assume the role of Incoming retailer. The same SPID will be transferred to another retailer.

Page | 7

MOSL Ref:


Step Action


Expected Result


3 As the Incoming Retailer (MOSL), in order to initiate a Transfer, I will send a valid T108.R transaction to CMOS.

CMOS will:



Send the following transaction to the Incoming Retailer providing information on the SPID to be transferred, where relevant from the following list: T112.M, T132.M, T149.M, T152.M, T153.M, T154.M, T133.M, T156.M, T157.M, T163.M, T139.M, T140.M, T144.M, T145.M, T147.M, T158.M, T159.M, T129.M, T138.M, T150.M, T104.M, T136.M,T160.M, T121.M, T123.M, T168.M, T128.M, T167.M, T149.M

4 As the Incoming Retailer (MOSL), in order to submit the transfer meter read, I will send a valid T105.R transaction to CMOS.

CMOS will:


Process the inbound transaction and send a T105.M transaction to the relevant outgoing Retailer and Wholesaler, to notify the transfer meter read details.

Page | 8

MOSL Ref:


3.1.2.3Market Scenario #3: - Cancellation of transfer registration (Gain/Loss)

Whether the Market Applicant is a Wholesaler or Retailer, they will be expected to carry out the relevant steps, all other roles will be undertaken by MOSL.

Step Action


Expected Result


1 As the Incoming Retailer, in order to initiate a Transfer, I will send a valid T108.R transaction to CMOS.

CMOS will:




2 As the outgoing retailer (MOSL), in order to cancel the transfer, I will send a valid T110.R transaction to CMOS.

CMOS will:

Validate the inbound transaction and send a T109.M transaction confirming receipt to the Outgoing Retailer (MOSL).

Process the inbound transaction, and send a T111.M transaction to the relevant outgoing Retailer (MOSL), Incoming Retailer and Wholesaler, to notify the transfer cancellation.

Cancel transfer and reinstate Outgoing Retailer.

Where the market applicant is a retailer, they will now take on the role of outgoing retailer, and MOSL will assume the role of Incoming retailer. A new SPID will be transferred to another retailer.

Page | 9

MOSL Ref:


Step Action


Expected Result


3 As the Incoming Retailer (MOSL), in order to initiate a Transfer, I will send a valid T108.R transaction to CMOS.

CMOS will:




4 As the outgoing retailer, in order to cancel the transfer, I will send a valid T110.R transaction to CMOS.

CMOS will:

Validate the inbound transaction and send a T109.M transaction confirming receipt to the Outgoing Retailer.

Process the inbound transaction, and send a T111.M transaction to the relevant outgoing Retailer, Incoming Retailer (MOSL) and Wholesaler, to notify the transfer cancellation.

Cancel transfer and reinstate Outgoing Retailer.

Page | 10

MOSL Ref:


3.1.2.4Market Scenario #4: - Wholesaler adds a meterWhether the Market Applicant is a Wholesaler or Retailer, they will be expected to carry out the relevant steps, all other roles will be undertaken by MOSL.

Step Action


Expected Result


1 As the Wholesaler, in order to add a meter I will send a valid T104.W transaction to CMOS

CMOS will:


Process the inbound transaction and send a T104.M transaction to the Retailer and Wholesaler.

3.1.2.5Market Scenario #5: - Remove a meter and disconnectWhether the Market Applicant is a Wholesaler or Retailer, they will be expected to carry out the relevant steps, all other roles will be undertaken by MOSL.

Step Action


Expected Result


1 As the Wholesaler, in order to remove a meter I will send a valid T105.W transaction to CMOS

CMOS will:

Validate the inbound transaction and send a T109.M transaction confirming receipt.


2 As a Wholesaler, in order to permanently disconnect the supply point, I will send a valid T115.W transaction to CMOS

CMOS will:



3.1.2.6Market Scenario #6: - Meter ExchangeWhether the Market Applicant is a Wholesaler or Retailer, they will be expected to carry out the relevant steps, all other roles will be undertaken by MOSL.

Page | 11

MOSL Ref:


Step Action


Expected Result


1 As the Wholesaler, in order to exchange a meter (like for like) I will send a valid T117.W

CMOS will:



3.1.2.7Market Scenario #7: - Submission of Meter Reads from a wholesalerWhether the Market Applicant is a Wholesaler or Retailer, they will be expected to carry out the relevant steps, all other roles will be undertaken by MOSL.

Step Action


Expected Result


1 As a Wholesaler, in order to submit a meter read, I will send a valid T105.W transaction, with meter read type of (X) to CMOS.

CMOS will:


Process the inbound transaction and send a T105.M transaction to the Retailer and Wholesaler, to notify them of the meter read.

3.1.2.8Market Scenario #8: - Submission of Meter Reads from a retailerWhether the Market Applicant is a Wholesaler or Retailer, they will be expected to carry out the relevant steps, all other roles will be undertaken by MOSL.

Step Action


Expected Result


1 As a Retailer, in order to submit a Regular Cyclic meter read, I will send a valid T105.R transaction, with meter read type of (C) to CMOS.

CMOS will:


Process the inbound transaction and send a T105.M transaction

Page | 12

MOSL Ref:


Step Action


Expected Result


to the Retailer and Wholesaler, to notify them of the meter read.

3.1.2.9Market Scenario #9: - SettlementsWhether the Market Applicant is a Wholesaler or Retailer, they will be expected to carry out the relevant steps, all other roles will be undertaken by MOSL.

Step Action


Expected Result


1 As Market Operator, in order to run a Settlement for the market applicant, I will run a selective settlement run for the Wholesaler or Retailer

CMOS will:

Validate the Settlements scheduler parameters and run the required Settlement processing.

Send the Settlement Report to the required Retailer or Wholesaler.

3.1.2.10 Market Scenario #10: - Wholesaler Data correctionWhether the Market Applicant is a Wholesaler or Retailer, they will be expected to carry out the relevant steps, all other roles will be undertaken by MOSL.

Step Action


Expected Result


1 As a Wholesaler, in order to submit a Meter Chargeable Details correction, I will send a valid TCORR114.W transaction to CMOS.

CMOS will:


Process the inbound transaction and send a TCORR114.M transaction to the Retailer and Wholesaler, to notify them of the correction.

Page | 13

MOSL Ref:


3.1.2.11 Market Scenario #11: - Retailer Data correctionWhether the Market Applicant is a Wholesaler or Retailer, they will be expected to carry out the relevant steps, all other roles will be undertaken by MOSL.

Step Action


Expected Result


1 As a Retailer, in order to submit a meter read correction, I will send a valid TCORR171.R transaction to CMOS.

CMOS will:


Process the inbound transaction and send a TCORR171.M transaction to the Retailer and Wholesaler, to notify them of the correction.

3.1.2.12 Market Scenario #12: - Corrective SettlementsWhether the Market Applicant is a Wholesaler or Retailer, they will be expected to carry out the relevant steps, all other roles will be undertaken by MOSL.

Step Action


Expected Result


1 As Market Operator, in order to run a Corrective Settlement for the market applicant, I will re-run a settlement run for the Wholesaler or Retailer using the same parameters as before.

CMOS will:

Validate the Settlements scheduler parameters and run the required Settlement processing.

Send the corrected Settlement Report to the required Retailer or Wholesaler.

Page | 14

MOSL Ref:


3.2 MEAT execution

Applicants should detail their method of evaluating the test results and creating evidence.

3.2.1 Test results analysis approach

Applicants should detail their method of evaluating the test results, specifically:

Who will be involved in evaluating actual test results? Who will be responsible for carrying out any fixes? Who will be involved in any required re-testing (either within the two-week testing window

where time remains, or in Remedial MEA)?

3.2.2 Test governance approach

Applicants should document the organisational structure within their company for providing test governance, including key names and positions.

3.3 MEAT evaluation & notification

3.3.1 Exit criteria

Applicants should explain how they will validate the exit criteria as documented within the MOSL detailed MEAT plan.

3.3.2 Defect management

Applicants should detail their method of defect management, specifically:

How will they capture, triage and manage defects through to closure? How will they provide evidence to MOSL that this has been achieved?

Page | 15

MOSL Ref:


4. High Level PlanAs part of the Controls of MEAT, each stage (Design & Build, Execution, Evaluation & Notification) will be tracked against an agreed day-by-day test schedule.

Applicants should set out this day-by-day schedule for carrying out Market Entry Assurance Testing below.

The MEAT Design & Build can commence once the Participant detailed MEAT plan has been agreed with MOSL.

The Interface & Data Transaction Testing (and subsequent tasks) should fall within the two week testing window assigned by MOSL (in response to the Market Entry Assurance Plan (MEAP)).

Approximate durations for each task are included below.

5. Approvals

5.1 Document history

Applicants should use this section to track the version of their MEAT plan.

Version Date Created

Author Reason for Update & Changes Made

Page | 16

MOSL Ref:

Task Duration (days) Start Date End DateMEA Test Design & Build 10

2 Week Testing Window: 10[Assigned by

MOSL through MEAP]

Interface & Data Transaction Testing

2

Interface & Data Transaction Testing Evaluation

1

Scheduling of Market Scenario Testing

1

Market Scenario Testing 4Market Scenario Testing Evaluation

1


5.2 Document review/approval

Market participants and MOSL should sign off this document once the approach has been agreed.

Name Role Input Required Email Sign-off

Date Rec’d

[Accountable tester name]

Market Applicant Accountable Tester

Accountable / Sign off

[To be provided by MOSL]

MOSL Test Analyst Sign off

Page | 17

MOSL Ref:

About this document · Web viewCMOS will process the inbound transaction and send a T102.M...

Documents

Transcript of About this document · Web viewCMOS will process the inbound transaction and send a T102.M...