Transcript
I-SEM – Technical Liaison Group Ref: TLG.001
24th February 2016
1
Agenda Welcome and house-keeping Terms of Reference Proposed Process & Schedule Technical Delivery Schedule Technical Overview of Proposed Market Balancing Market – Interfaces Overview AOB
2
Agenda Welcome and house-keeping Terms of Reference Proposed Process & Schedule Technical Delivery Schedule Technical Overview of Proposed Market Balancing Market – Interfaces Overview AOB
3
Agenda Welcome and house-keeping Terms of Reference Proposed Process & Schedule Technical Delivery Schedule Technical Overview of Proposed Market Balancing Market – Interfaces Overview AOB
4
Terms of Reference “Technical Liaison Group – serves as the principal forum for engagement with industry on topics of a technical nature, such as connectivity and interface specifications.” The Technical Liaison Group (TLG) is the I-SEM forum for communication, consultation and coordination with Market Participants regarding the technical aspects of I-SEM implementation. The principal focus of the TLG is to provide technical input into technical specifications, particularly those related to participant interfaces. EirGrid is undertaking the design of the technical solution to support the I-SEM implementation. The TLG facilitates communication and feedback of relevant aspects of the I-SEM technical design. The TLG is not a technical design authority but will consider input from market participants. The TLG will also serve as a forum for Market Participants to communicate with each other regarding business challenges they face in the implementation of their own processes, procedures, systems and organisational changes, thereby assisting their own readiness programmes for market go-live. 5
TLG Membership The Technical Liaison Group membership is open to all participant I-SEM projects. Members are expected to be Technical Architects or Technical Delivery Leads of their organisation’s I-SEM Project. To manage numbers, participants are asked to limit attendance at meetings to a single representative per organisation. Participant representatives may nominate an alternate including a third party to represent them.
6
TLG Objectives Communication • To share relevant technical information related to the I-SEM with Market Participants. A key objective is to ensure that participants are in a position to implement the required changes, within their own companies, in order that they are able to successfully interface with central market processes and systems. Consultation • To provide a mechanism for participants to offer input and provide feedback on technical matters related to central market processes and systems.
Coordination • To facilitate the effective coordination of industry-wide technical activities.
7
TLG Operating Principles The TLG will meet on a regular basis (approximately 6 weeks) and will be chaired and supported by EirGrid's I-SEM Participant Engagement and Market Readiness (PEMR) work stream. Notification of meeting locations and times will be provided in advance of each meeting. The I-SEM Project Webpage (http://www.sem-o.com/isem/Pages/Home.aspx) will be used to communicate Agendas, Meeting Notes and Issues Log for TLG meetings, as well as relevant documents and calendars. E-mail distribution lists will be used for communication with and amongst TLG members. All significant announcements will be e-mailed to these lists. The frequency of meetings are scheduled in line with I-SEM Project milestones and deliverables.
8
Agenda Welcome and house-keeping TLG Terms of Reference TLG Process & Schedule Technical Delivery Schedule Technical Overview of Proposed Market Balancing Market – Interfaces Overview AOB
9
I-SEM Central Systems and Services Team Morris Lyness – I-SEM Central Systems and Services Workstream Manager Michael Harrington – I-SEM Central Systems and Services Technical Team Lead Tony Brennan – I-SEM Central Systems and Services Technical Architect Severin Garanzuay – I-SEM Central Systems and Services Project Manager
10
Proposed Process
In Session
Offline
• Presentation of meeting content (including participant requested agenda items) • Q&A on individual items • Requests for agenda items in subsequent sessions • Flag areas of concerns, interest • Review of items/responses on previous session items
• Submission of comments • Review of material on website • Off-line response to queries distributed
11
Proposed TLG Schedule Session
Proposed Agenda
Topics proposed for subsequent sessions
TLG 1
Introduction to TLG Balancing Market Introduction
Connectivity for Market Trials
Day Ahead/Intra Day Market Introduction
User Management
TLG 2
Pre-requisites for client devices
Data dictionary overview TLG 3
TLG 4
FTR overview Preview of Balancing Market Interface Specification Review and discussion on Balancing Market Interface Specification
Guide for interface toolkit Test Data protocols Cutover approach
12
Agenda Welcome and house-keeping Terms of Reference Proposed Process & Schedule Technical Delivery Schedule Technical Overview of Proposed Market Balancing Market – Interfaces Overview AOB
13
Central Systems and Services Overview of Major Market Systems and Services
14
Market Participant Update Document The MPUD is a set of documents that evolve over time with the design, implementation, and updates to the market. It contains functional and technical information related to interfaces, reports, and connectivity requirements. Release
Planned Rel. Date
Focus
MPUD 1
June 2016
Balancing Market: interfaces, connectivity requirements (type 2/3) AOLR: interfaces, connectivity requirements (type 2)
Sep 2016
DA/ID Market: interfaces, connectivity requirements (type 2/3), Balancing Market: reports AOLR: reports
MPUD 3
Dec 2016
Balancing Market: participant interface toolkit DA/ID: reports FTR: reports, interfaces, connectivity requirements (type 2/3, where applicable) Information in preparation for Connectivity (CCQT) testing CRM: interfaces, reports, connectivity requirements (type 2/3)
MPUD 4
Mar 2017
Information in preparation for Market Trial
MPUD 5
June 2017
Information in preparation for Go-Live
MPUD 2
15
Agenda Welcome and house-keeping Terms of Reference Proposed Process & Schedule Technical Delivery Schedule Technical Overview of Proposed Balancing Market Balancing Market – Interfaces Overview AOB
16
I-SEM Design Principles Select standard hardware and software components Utilise existing IS infrastructure - where appropriate Design to minimise operational downtime Build in resilience across the architecture for critical functions Use an Enterprise Service Bus for interfaces - where appropriate Maximise service availability Security is a priority requirement Ensure operational ease of use Minimise custom development Avoid duplication of functionality across architecture Maintain integrity of data Minimise cost where possible Comply with relevant regulatory requirements Adhere to industry standards Adoption of ITIL Service standards 17
Integration Principles Area
Approach
Re-use
Re-use existing web-services where appropriate
Standardisation
Adopt Industry standards where they exist e.g. ENTSO-E, ISO 20022. IS Guidelines – Web-services XML over SOAP
Loose coupling
Adopt Publish and Subscribe pattern where required
Delivery Assurance
Receipt acknowledgement handshake as standard. None received ownership remains with source application.
Security
Encryption is proposed Continuing use of existing certificates.
Audit Trail
Audit logs to be created at end point systems and in middleware.
Monitoring
Enterprise monitoring of all key systems.
Unique Common Identifiers
All end-points should communicate based on an agreed set of common identifiers for all significant business data entities.
Data field mapping
The service bus will perform mapping of source and destination fields based on an agreed common data model across applications.
18
Solution Overview
19
Solution Overview Multiple vendor solutions to fulfil I-SEM operations ABB contracted for Balancing Market NEMO Service Provider selected – contracting April CRM – Re-use of existing vendor FTR – Use of JAO platform Integration is complicated Near to real-time operation – Balancing Market. Higher availability requirement (99.95%) – Balancing Market Separate interfaces for engagement on NEMO FTR will be fulfilled by Joint Allocation Office Proposing to use standard interface mechanisms Maintain existing interfaces where possible Re-using existing MPI for accessing new registration system for BM, NEMO & CRM Continue with certain current SEM design characteristics 20
Agenda Welcome and house-keeping Terms of Reference Proposed Process & Schedule Technical Delivery Schedule Technical Overview of Proposed Market Balancing Market – Interfaces Overview AOB
21
Balancing Market Interfaces Overview
Remove
Remove Remove Remove
22
High Level Balancing Market Information Balancing Market Systems vendor is ABB
Technical infrastructure design direction is similar to the current SEM Both new infrastructure and some existing EirGrid infrastructure will be utilised. EirGrid's two primary datacentre locations will be used – as is the current SEM External application load balancers Active - Active application design 99.95% availability 24x7x365 design requirement Web based XML over SOAP Interfaces Digital Certificate based authentication Type 2 & Type 3 URL based addresses for interaction
23
Balancing Market Interfaces Overview – current view Maintaining the existing MPI web service Type 2 & 3 Data schema extended for new functionality Existing certificate management process will continue New certificates required. New URL’s
New I-SEM Public website Access to reports Access to query/issue management Access to dynamic reporting
24
Balancing Market Interfaces Overview – MPI Data Schemas Design team is working on interface design
Intention is to re-use interfaces that do not need to change, where possible (e.g. VTOD process) Party and Participant identifiers – no intention to change GU and SU IDs – no intention to change
25
Agenda Welcome and house-keeping Terms of Reference Proposed Process & Schedule Technical Delivery Schedule Technical Overview of Proposed Market Balancing Market – Interfaces Overview AOB
26
Questions ?
27
I-SEM Project – Contact Details
Web:
http://www.sem-o.com/ISEM/
Email:
[email protected]
Subject: TLG – your topic
Thank you 28
