120 likes | 283 Views
ROI HSP Project Update. Conor Garrigan. HSP Agenda Items. Project Plan Update Design Clarifications Trailing/Leading zeroes File naming convention EULA Approval of Cutover Approach. High Level Schedule. ROI HSP Design Clarification.
E N D
ROI HSP Project Update Conor Garrigan
HSP Agenda Items • Project Plan Update • Design Clarifications • Trailing/Leading zeroes • File naming convention • EULA • Approval of Cutover Approach
ROI HSP Design Clarification Truncation of Leading and Trailing Zeros in Decimal Fields
Data Changes in Market Messages to Support new TIBCO-based Communications Background The introduction of the new TIBCO-based communications technology requires a change in the way decimal fields are handled. Summary of Impact Where a field is defined as decimal within the harmonised schema, then any leading or trailing zeros are not populated. This change is outlined overleaf. This change will be added to the ROI Extended Impact Summary spreadsheet as presented at the ROI MP Planning Workshop on 17 April 2012. The updated presentation will be Version 1.3 and will be replaced in the HSP Project Folder on the RMDS Calendar.
Truncation of leading and trailing zeros on all decimal fields in outbound to Supplier messages Trailing Leading Interval Value (total digits = 9, post-decimal digits = 3) TransformerLossFactor (total digits = 6, post-decimal digits = 4) • Planning and Implementation Notes • See the attached list of all decimal fields on all Outbound Messages (Source: HBL V2.3) • This change does not impact on the HBL or Harmonised Schema • All affected decimal fields contain a decimal point in the XML message • Validation rules for decimal fields on inbound messages are unchanged • The schema rules for total number of digits and post-decimal digits for all decimal fields are unchanged • This is a feature of the new TIBCO applications and is already working this way in the NI market. ESBN will also adopt this new feature upon Harmonisation go live in the ROI As-Is (field value in 341 message) 03.1415 27.300 TransformerLossFactor (total digits = 6, post-decimal digits = 4) Interval Value (total digits = 9, post-decimal digits = 3) To-Be (field value in 341 message) 3.1415 27.3
ROI HSP Design Clarification File Naming Conventions (fully replaces previous clarification issued to IGG on 27th June, 2012)
1. Change in Market Message File Naming convention Inbound to Supplier Outbound from Supplier (via Webforms) As-Is • Planning and Implementation Notes • This change does not impact on the HBL or Harmonised Schema • This change is separate from the12 message name changes in the Harmonised Schema (see the category “Message Name Changed” in the ROI Extended Impact Summary spreadsheet on page 16 of the MP Planning Workshop slide deck) MM Number Date and Time MM Number Date and Time Mxxxx_YYYYMMDDHHMMSSSSS Mxxxx_YYYYMMDDHHMMSSSSS To-Be Seconds since base date ROI Mkt MM Number TIBCO Process ID In add folders - Pending, Outbound, Inbound and all archive folders. 602 and 601 MMs do not have the DSO_ prefix. DSO_MIM_xxxx_sssssssssssss_pppp
EULA Reminder • EULA issued to all Market Participants • Required to return 2 signed copies in advance of your IPT slot • Last date for signing by last IPT participant is the 14th August !!
Approval of ROI Market cutover approach • Key market steps outlined within the document circulated last week includes the high level NIE cutover tasks for completeness
Cutover Headlines • Central Market system inc Extranet will be disabled at 18:00hrs Friday 21st September, i.e., no further messages to be sent by Suppliers • Supplier tasks • Friday between 20:00hrs- 21:00hrs carry out message reconciliation • Saturday PM apply changes to your back end systems (following confirmation from HRDS) • Sunday AM validate your connectivity via test message • Detailed tasks and timings are based on previous dress rehearsals so are subject to revision and any changes will be communicated via the normal channels.