Download presentation
Presentation is loading. Please wait.
Published byPauliina Väänänen Modified over 5 years ago
1
TAG Agenda – April 6th 2006 Minutes from last TAG meeting – 13.45 MPCC Upgrade – 13.50 Review of message reconciliation and issue identification process – 14.00 Error identification messages on MPCC – 14:15 Update from TLG – 14.45 XML Schema Release – 15:00 Planned Outages – 15.20 Next Steps – 15.30
2
Minutes Minutes from last TAG meeting – February 23rd 2006
3
MPCC Release
4
MPCC v11 upgrade All but two MPs now live at Version 11
Issues preventing upgrade are on the participant side and are unrelated to the upgrade No issues relating to the MPCC release in any MP site since Go-Live in February Receipt Acknowledgements have been received for all messages sent by ESBN since Go-Live. Proposing to close this item
5
Review of Message Reconciliation and issue identification processes
6
Message Reconciliation Process
Procedures discussed at last TAG have now been documented and agreed across all relevant teams Emphasis placed on communication to MPs where issues arise Essential that 602 reconciliation is carried out at MP site
7
Message Reconciliation Process
ISC run queries first thing each morning to determine the number of messages sent and received by SAP MOIEX run queries to determine messages in and out of the hub Both figures are reconciled and corrective actions taken if necessary
8
Issue identification Previous issues and the way with which they were dealt have been reviewed RMDS team added to ISC contact lists in case of unplanned outages, message issues etc RMDS will notify Market Participants where issues arise with market impact
9
Issue identification – 602 errors
Queuing delays with the audit data Delays in data written to the audit queues should not impact as the message is generated 2 ½ hours after the reconciliation period (change applied late last year) Should this occur, RMDS will notify MPs
10
Issue identification – 602 errors
Messages issuing through the night Larger than usual volumes may mean that messages are running up to the 4 AM reconciliation time If a message is sent at 3:59:59 it will appear on the 602 message although the MP may not have received it till slightly after the 4AM cut-off time Where messages run late, RMDS will notify MPs
11
Issue identification – Pre-Production messages reaching Production
Errors occurred when rebuilding Pre-Production from Production following a disk problem with one routing table not successfully updated There are no further hub amendments which can prevent this Procedures on the SAP side have been refined and documented to ensure that routing tables are appropriately updated when a new client is built
12
Error identification messages
13
Error identification messages
Issue raised by MPs in advance of Version 11 of the MPCC Number of changes made by Version 11 to make error messages less generic Need to determine if this is still an issue?
14
Update from TLG
15
Update from TLG Forum for:
Communication and consultation around technical design proposals and plans for SEM Co-ordination of industry-wide technical activities such as testing Communication with other MPs regarding common implementation issues
16
Update from TLG Second Technical Liaison Group meeting held on March 23rd Reviewing items such as: Data Access Model Data Standards Readiness Assessment
17
Update from TLG Overlap in attendance between both groups
RMDS will attend the TLG to monitor items with Retail Market impact These will be discussed at the TAG Important that MPs also raise any issues for concern/questions/proposals
18
Update from TLG Three options for data access:
Web service Web Page Forms Web Download The next TLG (April 20th) will focus on a demonstration of sample schema There will be a design freeze in place from June 7th
19
June Schema Release
20
June Schema Release Test version of schema to issue to MPs this week
Release to production intended for June 24th Includes the following: MCR TSO/SSA requirement for customer details on change from NQH to QH MCR Addition of Effective from date to 114 message MCR Addition of effective date of previous CoS to 102R message MCR 0077 – Removal of GUID from webforms (No schema impact)
21
June Schema Release Detailed Cutover and on the day plans to issue closer to the time Assurance requirements to be determined by Gemserv
22
June Schema Release Essential that all MPs upgrade on Saturday June 24th Messages sent by ESB Networks after this date will be V 5.1 instead of V 5.0 If an MP does not upgrade on June 24th any messages to issue to them after the upgrade would fail All messages sent by MPs would fail validation in the hub For most MPs even one day of lost data would cause significant issues MOIEX will channel all resources available into upgrading on the day – after this, all resources will be focussed on monitoring the first few days of live operations
23
Planned Outages and Maintenance Activities
Market Gateway Archive Procedure: Last archive carried out on April 1st Saturday’s 602 message did not issue No other known issues Next archive planned for early June
24
Planned Outages and Maintenance Activities
Site Switch: Next site switch of central Market systems planned this weekend All messages sent to or from the market gateway will be processed once the site switch completes
25
Planned Outages and Maintenance Activities
Calendar of events: Calendar issued on March 31st Shows all currently known outages, site switches etc Updates will be provided to MPs when available
26
Notice Board MPCC single installation:
Testing continuing and progressing well Expecting to issue in advance of next release in June Will update at conference call
27
Next Steps A list of items for discussion were received from MPs via CER These items are all now in progress MPs should continue to raise issues they would like to see addressed via
28
Next Steps Proposed Diary dates for subsequent meetings
May 18th June 22nd (Pre V 5.1 meeting) August 10th September 21st Propose to continue with TAG update at conference call every two weeks
Similar presentations
© 2024 SlidePlayer.com. Inc.
All rights reserved.