ROI HSP Design Clarification

Data Format Changes

(aligning with existing live Harmonised Design in NI)

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:

1. Changes in naming convention for XML Messages

2. Dropping of leading zeroes in Transaction Reference Number in Message Header on all outbound from Supplier messages created by Webforms

3. 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.

Mxxxx_YYYYMMDDHHMMSSSSS

To-Be

Outbound from Supplier (via Webforms)

• 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)

MIM_xxxx_sssssssssssss_pppp

As-Is

1. Change in Market Message File Naming convention

Inbound to Supplier

Mxxxx_YYYYMMDDHHMMSSSSS

MM Number MM Number

MM Number

Seconds since base date

TIBCO Process ID

Date and Time

DSO_MIM_xxxx_sssssssssssss_pppp

(Inbound Folder)

(Archive/Inbound Folder)

MIM_xxxx_sssssssssssss_pppp

MM Number

DSO_MIM_xxxx_sssssssssssss_pppp

(Pending or Outbound Folder)

(Archive/Outbound Folder)

Date and Time

Seconds since base date

TIBCO Process ID

2. Dropping of leading zeros in Transaction Reference Number (TxRefNbr) in Header Segment on all messages outbound from

Supplier created by Webforms

S98_20120627090105001

As-Is (assuming message is from S98)

To-Be (assuming message is from S98) S98_20120627915001

MIM YYYYMMDD HHMMSSSSS

MPID YYYYMMDD

• 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

HHMMSSSSS

3.1 Change in format of MarketTimeStamp in Header segment of all messages – Inbound to Supplier

2012-06-01T10:15:20.07Z

As-Is

To-Be YYYYMMDD

WinterTime

• 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

SummerTime

HH:MM:SS.TT TimeZone

2012-01-01T10:15:20.07Z

YYYYMMDD HH:MM:SS.TT TimeZone

2012-06-01T10:15:20.073+00:00

YYYYMMDD HH:MM:SS.SSS

2012-01-01T10:15:20.073+00:00

YYYYMMDD HH:MM:SS.SSS TimeZone TimeZone

3.2 Change in format of MarketTimeStamp in Header Segment of all messages – Outbound from Supplier (by

Webforms)

2012-06-01T10:15:20

As-Is

To-Be YYYYMMDD

WinterTime

• 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

SummerTime

HH:MM:SS

2012-01-01T10:15:20

YYYYMMDD HH:MM:SS

2012-06-01T10:15:20.073+01:00

YYYYMMDD HH:MM:SS.mmm

2012-01-01T10:15:20.073+00:00

YYYYMMDD HH:MM:SS.mmm TimeZone TimeZone