1 / 11

ROI HSP Project Update

ROI HSP Project Update. Conor Garrigan. HSP Agenda Items. Project Plan Update Design Clarifications (Extranet and Data Formats). High Level Schedule. ROI HSP Design Clarification. Standard Load Profile on Supplier Extranet.

ebony
Télécharger la présentation

ROI HSP Project Update

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ROI HSP Project Update Conor Garrigan

  2. HSP Agenda Items • Project Plan Update • Design Clarifications (Extranet and Data Formats)

  3. High Level Schedule

  4. ROI HSP Design Clarification Standard Load Profile on Supplier Extranet

  5. Final position and format for new Standard Load Profile field on Extranet

  6. ROI HSP Design Clarification Data Format Changes (aligning with existing live Harmonised Design in NI)

  7. Data Format Changes in Market Messages to Support new TIBCO-based Communications Background The introduction of the new TIBCO-based communications technology requires a number of changes in the contents and/or format of certain fields in some Market Messages. Summary of Impact Changes are being introduced in the following areas: • Changes in naming convention for XML Messages • Dropping of leading zeroes in Transaction Reference Number in Message Header on all outbound from Supplier messages created by Webforms • Change in format of MarketTimeStamp field in Header Segment on all Messages to conform with UTC format These changes are described fully overleaf. All of these changes 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.

  8. 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 Seconds since base date Seconds since base date MM Number TIBCO Process ID To-Be MM Number TIBCO Process ID (Pending or Outbound Folder) MIM_xxxx_sssssssssssss_pppp (Inbound Folder) MIM_xxxx_sssssssssssss_pppp DSO_MIM_xxxx_sssssssssssss_pppp (Archive/ Inbound Folder) DSO_MIM_xxxx_sssssssssssss_pppp (Archive/ Outbound Folder)

  9. 2. Dropping of leading zeros in Transaction Reference Number (TxRefNbr) in Header Segment on all messages outbound from Supplier created by Webforms MIM YYYYMMDD HHMMSSSSS As-Is (assuming message is from S98) • Planning and Implementation Notes • Change applies only to outbound messages to Networks created by Webforms • Leading zeroes are dropped from HH, MM and SS but not from milliseconds • This field is populated automatically on messages created by Webforms users • This field is unchanged on all outbound to MPs messages • Validation rules for this field on inbound to Networks messages are unchanged • This field is not to be confused with the MP Business Reference field in the body of many Market Messages (that field remains unchanged by this change) • This change does not impact on the HBL or Harmonised Schema S98_20120627090105001 To-Be (assuming message is from S98) MPID YYYYMMDD HHMMSSSSS S98_20120627915001

  10. 3.1 Change in format of MarketTimeStamp in Header segment of all messages – Inbound to Supplier WinterTime SummerTime • Planning and Implementation Notes • Change applies only to the MarketTimeStamp field and not to other timestamp fields in the message body such as those for IntervalPeriodTimestamp in 341, 342 and aggregation messages • 602 Message: the existing StartTime and EndTime timestamps are both in the format “DD-MMM-YY HH:MM:SS” so are not impacted by this change • This change does not impact on the HBL or Harmonised Schema • Note: As-Is TimeZone does not change with Wintertime/Summertime changes As-Is YYYYMMDD HH:MM:SS.SSS TimeZone TimeZone YYYYMMDD HH:MM:SS.SSS 2012-01-01T10:15:20.073+00:00 2012-06-01T10:15:20.073+00:00 To-Be YYYYMMDD HH:MM:SS.TT TimeZone YYYYMMDD HH:MM:SS.TT TimeZone 2012-01-01T10:15:20.07Z 2012-06-01T10:15:20.07Z

  11. 3.2 Change in format of MarketTimeStamp in Header Segment of all messages – Outbound from Supplier (by Webforms) WinterTime SummerTime • Planning and Implementation Notes • MarketTimeStamp is populated automatically on all messages created by Webforms • Validation rules for this field on inbound from Supplier messages are unchanged • This change does not impact on the HBL or Harmonised Schema As-Is YYYYMMDD HH:MM:SS.mmm TimeZone TimeZone YYYYMMDD HH:MM:SS.mmm 2012-01-01T10:15:20.073+00:00 2012-06-01T10:15:20.073+01:00 To-Be YYYYMMDD HH:MM:SS YYYYMMDD HH:MM:SS 2012-01-01T10:15:20 2012-06-01T10:15:20

More Related