harmonisation and service packs (hsp) project

Harmonisation and Service Packs (HSP) Project

Market Participant Planning Workshop17th April, 2012

Alexander Hotel, Fenian Street, Dublin 2

(V1.2 Updated 29 May 2012 – see change history at end of presentation)

17 April, 2012 (Updated 29/5/2012) HSP MP Workshop

AgendaTopic Time Opening and HSP Project Overview 10:00

Agenda, Objectives, Logistics Market Design Change and ROI Impact

HBL Overview , Design Clarifications and ROI Impacts, Q&A

Lunch Break

Technical Replacement Programme 14:00

Programme Overview, EMMA spec and config, ROI Webforms Demo, Q&A

Assurance & MP Support Programmes

Market Assurance and IPT

MP Communications and Support

Q&A, Wrap-Up, Close 16:00


Workshop Objectives

1. Assess the impact of the HSP Project on their own business and technical operations

2. to kick-start their project planning, if not already under way, for the detailed implementation work required.

Allow Market Participants to:


HSP Project Overview • Project Objectives

– Implementation for the ROI Retail Market of the agreed Harmonised Baseline (HBL) and a new operational technical messaging platform, shared with and operational in the NI Retail Market

• Scope – HBL implementation for ROI Market with consequent design and

operational impacts – MPCC replacement by new EMMA on-ramp service – Technical Service Packs upgrade of ESBN Central Market Systems

(no impact on MPs)– CR357 – increased validation on 030 Market Message – Inclusion of Load Profile on Supplier Extranet

• Key Exclusions – Merging of the ROI and NI Retail markets (MPs still need to licence and

qualify separately) – Changes to the ROI Market Business Processes (with exception of the

new 131 Meter Works Message)


HSP Project Time Line

Apr 2012 Oct 2012

23 Sep, 2012

Single Market Hub (NI and ROI) and EMMA server (NI and ROI)goes live

(All ROI MPs must participate)

Jul - AugROI IPT

Sep - OctPost Go-live

support

Jun - SepEMMA Installation &

Comms setup for ROI MPs

MayParticpant Questionnaire

Sep - SepCutover Period

JunFinal IPT Scenarios and Plan

(ROI IPT MPs must participate) JunDraft Cutover Plan

17/04/2012MP Planning Workshop


Market Design Change and ROI Impacts of HSP Project



1. Harmonised BaseLine (HBL) and ROI-specific documentation – scope and nature of impact

2. Design Clarifications – interpretation by HSP team of some key design points arising from HBL

3. ROI Extended Impact Summary – message-by-message, field-by-field impact assessment summary sheet

Assessing the impacts of the HSP Project should be approached top-down by reviewing, in stages, the Harmonised Baseline, Design Clarifications and the ROI Extended Impact Summary


HBL Background

• In September 2009, the CER and NIAUR initiated the Retail Market Harmonisation Project

• Objective was to encourage competition in supply markets and to improvine the quality of service to all customers

• The Harmonisation Working Group (HWG), operating under oversight from a Harmonisation Steering Group (HSG), has produced the definition of and industry agreement to a common set of Harmonised market messages, data codes and definitions, which has culminated in a single retail market design

• This common set of definitions is called the Harmonised Baseline or HBL.

The HBL is a product of the Harmonisation Programme, jointly sponsored by the CER and NIAUR


HBL Structure and EnforcementThe HBL sets out the rules for constructing all Market Messages and is technically underpinned and enforced by the Harmonised Schema (available from today for ROI-only MPs)

010 Schema RO

I-O

nly

NI-

Onl

y

Sha

red

Data Codes(Common definition of

all coded elements, most shared but many

unique to ROI or NI)

Data Definitions (Common definition of

all elements, most shared but some unique

to ROI or NI)

Market Messages(Common definition of

91 Messages, most shared but some unique

to ROI or NI)

030 – Meter Works Request

Appointment Date

MPRN

Meter Configuration Code

Appointment Timeslot

Etc.

HBL Components Example 030 Message

MCC01MCC02MCC03Etc...N001N002N003Etc...

Harmonised Schema (Version 10, draft 10)(Set of rules governing the structure, type and content of individual Market Messages; single Schema

serves both ROI and NI; human and machine readable for programmatic validation of Messages)


HBL Impact – Message Design

• Market Messages / Data Definitions / Codes – Modelled largely on existing ROI elements– Key changes include:

• 1 new message (131 Work Status) • Extended options for Customer Service Special Needs• Central Market Systems validation for non-ROI codes (new

DIJ rejection code) • Numerous field length changes • Several changes in message name• Several changes in field optionality (required <=> optional)• A small number of new codes are introduced for ROI • All Boolean Flags on outbound messages now equal 0/1

The introduction of the HBL impacts on both the ROI Message design components and the existing ROI Schema


HBL Impact - Schema

• Harmonised Schema – Modelled largely on existing ROI schema (v9.0)– Key changes include:

• 2 new messages (131 and 140 (NI only))• Numerous new fields on several messages (NI only) • Numerous extensions of existing code sets (but for NI

only usage)• Several message names changed to align with

harmonised Interval / Non-interval naming convention

The introduction of the HBL impacts on both the ROI Message design and the existing ROI Schema


HBL and ROI-Specific Documentation

ROI Impact Document

Harmonised Baseline (HBL) Core Components

Go

vern

ance

. M

arke

t M

eeti

ng

s &

Ch

ang

e C

on

tro

l

Bas

elin

e C

han

ge

His

tory

& A

rch

ive

Original Harmonisation Workshop Outputs

Data Codes Data Definitions Market Messages

NI Message Guides

x 8

NI Message Guides

x 8

NI Message Guides

ROI Message Guides x 10ROI Message

Guides x 10ROI Message Guides

Start your impact assessment by reviewing the current HBL (V2.3, 22 Feb, 2012) and specific impact documentation for ROI MPs on the HRDS Website at http://www.rmdservice.com/hrds/default.htm

http://www.rmdservice.com/hrds/default.htm


ROI HSP - Design Clarifications

Topic Description Impacts on? Doc.

Invalid MPRNs ESBN processing of inbound Market Messages with MPRNs that are not valid in the RoI Retail Market Central Market Systems

All MPs

NI Codes on ROI inbound messages The approach to handling NI codes inbound to ROI

All MPs

Multiple Customer Service Codes on 010, 013, 016 and 017

MCR1028 Submission of multiple Customer Service Codes on 010, 013, 016 and 017MMs

All MPs serving Non-Interval Metered Market

Boolean variables on inbound and outbound messages

The approach to Boolean Values in Market Messages in RoI All MPs

Recipient ID Changes Recipient ID in message header changed to (a) “TSO” for EirGrid 341/342 message or (b) “Sxx” for Supplier Nominated messages 342/594/597 (per WP12)

EirGrid and Nominated Suppliers

Load Profile on Extranet Inclusion of (Standard) Load Profile on MPRN Enquiry screen of ROI Supplier Extranet Site (formatting of field to be confirmed)

All MPs

NI Codes on ROI inbound messages (single DIJ)

Provision of single DIJ code on 101R and 102R messages regardless of number of DIJ errors on 010 messages

All MPs

Invalid MPRNs

NI Codes in ROI

Multiple CSSNs

Boolean Variables

Recipient ID

Continue the impact assessment by reviewing the relevant design clarifications issued by the HSP Project

Load Profile

Single DIJ on 101R and 102R


ROI Extended Impact Summary

• Extended ROI Impact Summary – New impact planning aid for ROI MPs, not part of HBL– Based on approved HBL V2.3 ROI Impact Column Update– Simplified by removing all “No Impact” items – Extended by including:

• All current design clarifications (up to IGG on 23rd May 2012)• CR357 – Increased validation on 030 Market Message• Implementation Notes from the Project• References to helpful additional information sources

• Content Overview – All impacts on ROI messages and data items are categorised by the

nature of change (new message, new codes for ROI, field length change, etc.)

– Separate tabs provide views of the impacts by category, – message or data item and user-defined view

Use the ROI Extended Impact Summary to review detailed impacts (or to cross-check any impacting work already done). Extent of usage will vary by nature of Supply business and degree of your systems integration.

ROI Extended Impact Summary V1.1


HBL and HSP Change Management

• HBL changes before HSP go-live (ROI & NI impact)

– HWG of 22 Feb, 2012 agreed that no further HBLs would be published until after HSP go-live

– Any mandatory changes will be documented, brought to the HWG for approval and published as riders to the current HBL and published by HRDS

• Pending changes to HBL / Schema (ROI & NI impact) – DR1114 has been opened to gather pending changes– DR will not be brought to market until after HSP go-live

• Further HSP Project changes (ROI impact only) – Any changes impacting MPs will continue to be communicated

through the IGG and published by RMDS

While the likelihood of further design change is low and diminishing, keep abreast of any further changes to ensure your impact assessment remains current


Summary and MP Q&A

• Summary – The HSP Project introduces substantial change but

the impact of change will vary – Suppliers need to individually assess the impacts on

their own business processes and plan appropriately – there is no “do nothing” option

– Start the planning early to ensure that you can keep pace with the Market-wide change programme

• Questions ?


Technical Replacement Programme


Technical Workshop Objectives

• Systems Architecture and Components

• EMMA configuration options

• EMMA min spec

• MPCC to EMMA Cutover

• ROI Webforms Demo

• Multiple Supplier Codes


NIE + ESBN TIBCO

Central HUBNIE SAP PI

ESBN SAP PICentral Market System

NIE SAP IS-UESBN SAP IS-U

Central Market System

Test EMMA (Note connects to Test

HUB. Not shown for simplicity)

ProductionEMMA



ProductionEMMA



ProductionEMMA

VPN

ROI only Supplier

Encrypted

Packages over Internet

Connections

NI only Supplier

Dual Supplier

Encrypted


Connections

XML over VPN


NIE + ESBN TIBCO

Central HUB

ESBN SAP PICentral Market System

ESBN SAP IS-UCentral Market System



ProductionEMMA



ProductionEMMA

VPN

ROI only Supplier

Encrypted


Connections

Dual Supplier

Encrypted


Connections

XML over VPN NI

Market


TIBCO EMMA

• ESB HSP will provide Market Participants with TIBCO partner software (EMMA) to replace the current MPCC. This software will support the following 2 forms of communication with the Central Messaging Hub:– MPs automatically uploading and downloading

messages to/from the Central Hub– MPs manually keying transactions (messages) via

WebForms


EMMA ComponentsThe EMMA is based on standard TIBCO software components. The

components in use are as follows

• General Interface (GI) 3.9.1: This is the TIBCO component that is used to create the Webforms.

• Business Works (BW) 5.9.2: This is the TIBCO component that is used to: a) validate outbound messages against schema and, if valid, forward the

message to Business Connectb) receive inbound messages and deliver to destination folder on EMMA.

• BusinessConnect (BC) 5.3.3: This is the TIBCO component that is used to:a) Wrap the outbound message in an AS2 envelope and send over HTTPS to

the receiver’s EMMAb) Unwrap the AS2 envelope from the inbound message and forward to

Business Works.


EMMA Components• TIBCO BusinessConnect DMZ Dedicated DMZ Servlet – specifically designed to sit in your DMZ as an

entry point for inbound messages. Leaves the other main TIBCO components on the secure network

• BusinessConnect console in TIBCO Administrator This can be used for a number of tasks including:

– Viewing audit/data logs from BusinessConnect when sending messages.


EMMA Configuration Options

• There are three main deployment options namely single-server, distributed or dual-clustered.


Preferred TIBCO Network Setup

Note: If there is an existing proxy server, it is also possible to setup the architecture so that outbound messages can also be sent through it, rather than directly from the TIBCO Interior server through the DMZ.


Preferred TIBCO Network Setup


Preferred TIBCO Network Distributed Setup


Single Server

• Best practice is to use the TIBCO DMZ Component but it is possible to have a single TIBCO Interior server in the DMZ with no TIBCO DMZ component.


EMMA Minimum Spec

DMZ Server Spec: – Virtual & Physical environments supported– Processor - Single CPU (Quad Core)– RAM - 2GB– Disk - 30GB:

• C:\ - 5 – 10GB (OS)• D:\ - 5 – 10GB (TIBCO software)

– Operating System - Windows 2008

• Note: On a DMZ server a large amount of space isn’t required as this

server is only used for routing messages.


EMMA Minimum SpecTIBCO Interior Server:• Virtual & Physical environments supported• All 3 Main Configurations require:

– Database - Oracle – TIBCO Server Spec - 4 GB RAM– Operating System - Windows 2008 Server (IIS)– Browser - IE 8.0 for PC’s using webforms– Network

– Static IP Address– Permanent Network Connection (min. 1MB bandwidth)– Firewall restrictions, TIBCO uses port 443, Webforms

ports 80, 8087– Protocol – HTTPS, Uses digital certs.


EMMA Minimum Spec

• The differences between the Minimum Specifications for the three main configurations are as follows -


EMMA Minimum SpecTIBCO Hardware Setup – Single Server:• Single Server for application, DB & messages

– TIBCO Server – Spec– 2 CPU

– 560 GB Hard Disk

– C:\ - Operating System (suggested size 30 to 50 GB)– D:\ - Application & Database (suggested size 100 GB)– E:\ - Message Store (suggested size 250 GB or

remainder of disk)


EMMA Minimum SpecTIBCO Hardware Setup – Single Server Distributed:Two main variants:

– Application on single server, database on dedicated DB server & messages on SAN

– Application & messages on single server, database on dedicated DB server

• TIBCO Server – Spec• 2 CPU• SAN

• For this configuration the hard disk should be partitioned as follows: • Variant a)

» C:\ Operating System - suggested size 30 to 50 GB» D:\ Application - suggested size 100 GB» SAN - E:\ Message Store» Database on dedicated server

• Variant b)» C:\ Operating System - suggested size 30 to 50 GB» D:\ Application - suggested size 100 GB» E:\ Message Store - suggested size 250 GB or remainder of disk» Database on dedicated server


EMMA Minimum SpecTIBCO Hardware Setup – Dual Clustered:• Application on 2 fault tolerant servers, DB on dedicated database

server & messages on SAN• TIBCO Servers – Spec

• - 2 x 2 CPU• - SAN

• For this server setup the hard disk should be partitioned as follows:– Server 1

C:\ Operating System - suggested size 30 to 50 GB D:\ Application - suggested size 100 GB

– Server 2 C:\ Operating System - suggested size 30 to 50 GB D:\ Application - suggested size 100 GB

– SAN - E:\ Message Store– Database on dedicated server


MPCC to EMMA Cutover examples

• ROI only Supplier with only Production EMMA

• Dual Supplier with Production & Test EMMAs

• ROI only with Test & Production


MPCC Schema 9R

OI L

ive

RO

I T

est

Ne

w

Ha

rmo

nis

ed

(Sep

t L

ive

)

Ne

w

Ha

rmo

nis

ed

(2b

Te

st)

ROI Go-Live Post Go-Live

Retire Machine

Disable MPCC

NI Go-Live ROI IPTCurrent

Tibco EMMANI & ROI

LiveSchema 10

Tibco EMMANI & ROI

Test Schema 10

NI T

es

t N

I L

ive

Ne

w

Ha

rmo

nis

ed

(Ma

y g

o-L

ive

)

MPCC Schema 9

MPCC Schema 9


MPCC Schema 9R

OI L

ive

RO

I Tes

t N

ew

Har

mon

ised

(Sep

t Liv

e)

New

H

arm

onis

ed(2

b Te

st)


Retire Machine

Disable MPCC


MPCC Schema 9

Disable MPCCRetire

Machine

Existing EMMALive

Existing EMMA Test

TibcoEMMA NI

LiveSchema 10

Tibco EMMA NI

TestSchema 10

TibcoEMMA NI

Live

Schema 10

Tibco EMMA NI

TestSchema 10

Retire Machine

Tibco EMMANI & ROI

TestSchema 10

NI T

est

NI L

ive

New

H

arm

onis

ed(M

ay g

o-Li

ve)

Retire Machine

MPCC Schema 9

MPCC Schema 9

MPCC Schema 9

MPCC Schema 9

Tibco EMMANI & ROI

LiveSchema 10

Tibco EMMANI & ROI

TestSchema 10

Retire Machine


MPCC Schema 9R

OI L

ive

RO

I Tes

t N

ew

Har

mo

nis

ed(S

ept

Liv

e)

New

H

arm

on

ised

(2b

Tes

t)


Retire Machine

Disable MPCC


Tibco EMMANI & ROI

LiveSchema 10

Tibco EMMANI & ROI

Test Schema 10

NI T

est

NI L

ive

New

H

arm

on

ised

(May

go

-Liv

e)

MPCC Schema 9

MPCC Schema 9

MPCC Schema 9

MPCC Schema 9

MPCC Schema 9

Tibco EMMANI & ROI

Test Schema 10

Disable MPCCRetire

Machine


ROI Webforms

• Webforms are broadly similar to existing MPCC Webforms

• Demo - http://virtdmz051s/webforms

http://virtdmz051s/webforms


ROI Webforms• Folder structure


Pending

Outbound Processing

Invalid

Failed Unsent

Archive

Ackerr

Ack

WebformsTransaction

No Ack.

Automatic Process

Supplier Back End System

Webforms


Multiple Supplier Codes

• Same MP, different Supplier Codes in NI and ROI

• Same MP, different divisions in one or both markets


ROI Webforms• Folder structure (in this example, S98 is the primary Supplier Code; S90 is the secondary. Note:

the Pending, Processing and Outbound folders are shared between both Codes)


Market Assurance and MP Support Programmes


MP Support Programme

• Project Status and Design Updates – Market Communiqués issued at key junctures in the project– Regular updates at IGG Meetings on project progress and any design clarifications – If not attending IGG, watch for minutes on RMDS Calendar for meeting date– Latest approved HBL and Change Request log are on the existing HRDS website

• EMMA Installation Support Programme– On-site or remote access installation and comms setup by HSP technical specialists – Provision of technical and user documentation

• IPT Test Support – Pre-booked slot per MP ensures appropriate resources and priorities are in place

when needed – Test scripts graded by size and nature of MP business

• HRDS Email service– Email-based query submission and response service at [email protected]

• HSP Project Folder– All key project documents in one place (RMDS Calendar for 23 September)

The HSP Project has devised a programme of MP-focussed deliverables and support activities running throughout the project

mailto:[email protected]

http://www.esbextra.ie/RMDS/

HSP MP Workshop

Assurance for the Irish

Electricity Market

Harmonisation Project

Peter VarleyNiemesh Amin

Workshop 17th April 2012


Who are Gemserv?

• Appointed as a service provider to conduct independent market assurance reviews

• Have been involved in RoI electricity since market opening

• Assurance approach and techniques have evolved with market design changes and incorporating market feedback/lessons learned

• Satellite office located in Fitzwilliam Hall, Dublin


Assurance Approach• Self-Assessment

– Initial short questionnaire to verify that changes are known about and project has been initiated

– Later, more detailed questionnaire to verify that changes have been analysed, impacts assessed and actions initiated accordingly

• Formal Assessment (Central Systems only)

– Site visit to verify that project is on track and activities (particularly specification, testing, reviews and authorisations) are being carried out effectively


Assurance Approach• Message Exchange Testing

– Sample of each market message exchanged EMMA-Hub-Central and vice-versa to verify all message paths correctly configured and active

– Will be carried out immediately following commissioning of EMMA by EMMA installation team

– Evidence will be taken and sent to HRDS for collation and forwarded to Gemserv


Assurance Approach• Inter-Participant Testing (IPT)

– Tests carried out using the full market infrastructure (EMMA, network, Hub, Central Systems) and Participant systems (incl. Webforms)

– Tests are defined as storyboards that set out:• Initial conditions• Actions and events• Final conditions

– Requires pre-requisite data to be set-up (may be just identification of MPRN in appropriate state)

– Evidence to be taken at each step and sent to HRDS for collation and forwarding to Gemserv

– Gemserv reviews and assesses outcome


Assurance Approach• IPTs

– Large Suppliers• 29 test conditions to be tested

• With variations and overlap this results in 33 scenarios

• Some scenarios are sector-specific (e.g. Unmetered)

• Grouping expected to reduce per large supplier scenario count to about 15

– Small Suppliers• Aim is to verify that Webforms working in line with requirements

• 11 scenarios aiming to exercise most common messages

• Some scenarios will involve 2 suppliers (gaining and losing)

• Grouping expected to reduce per small supplier scenario count to about 6


Assurance Milestones

HSP MP Workshop 17 April, 2012 (Updated 29/5/2012)

Questions & Discussion


MP Next Steps

• Business and Systems Impact Assessment – Scope and plan project to implement required changes in time for agreed

IPT slot • EMMA Implementation

– Review technical spec and configuration options– Deploy server(s) and base software– Provide HSP with details of:

• chosen EMMA server configuration • choice of Oracle DB (XE or EE) • registered external IP address (for HSP test EMMA)• (ES MPs only) which EMMA will remain on as test server post-HSP golive

• Stay Informed – Attend IGG meetings / review minutes / watch for further HSP updates

from [email protected] and on the RMDS Calendar – Expect to be contacted shortly to confirm details above and to agree IPT

slot and test case workload

MPs should ensure that the full business and systems impacts are understood and appropriate project resources deployed in line with the HSP project schedule

mailto:[email protected]

http://www.esbextra.ie/RMDS/


MP Q&A

• Questions?


Wrap-Up and Close


Back up Slides


HSP Project Folder on RMDS Calendar


List of approved Change Requests on RMDS Website


List of approved Code Change Requests on RMDS Website


Webforms

• Example Screenshots


Change History

Version Change Summary

Version 1 (17 April, 2012) Original

Version 1.1 (23 May, 2012) • Page 14 – new PDF for new design clarifications from project • Page 16 – added V2 of ROI Extended Impact Summary spreadsheet

Version 1.2 (29 May, 2012) • Page 32 – new disk partitioning for DMZ server. Overall disk space requirements remain unchanged

harmonisation and service packs (hsp) project

Documents

roi retail market

roi market business

hsp team

market participants

project planning

consequent design

agreed harmonised baseline

ni retail markets mps