1. UNC Mod 006 - Implementation Paul Gallagher September 2006

2. UNC006 Implementation Seminar : 11/09/06 Overview  Aim to publish near to real time flow data from Terminals, Sub-Terminals and storage sites  Data provided by the sub-terminal or storage operators  System uses existing measurement and telemetry systems (same data seen by NG control room)  National Grid will carry out the configuration processes to ensure the data is displayed in line with the UNC requirements  Information provided to users via the Internet in an open, non-discriminatory way  System provides flexible ways of accessing the data  System Go Live : 3 rd October 2006

3. UNC006 Implementation Seminar : 11/09/06 System Design  Requirements of mod 006 deliver a step change in the granularity and timeliness of the data being provided via the NG website.  Existing NG website infrastructure inappropriate for the new requirements  Publication will be via a new purpose built web publication system called Gas Market Reporting System (GMRS)  Receives telemetered data direct from the integrated Gas Management System (iGMS) via a new Data Publication Hub  Data sent continuously through Oracle AQ Interface (message based interface) every 2 minutes

4. UNC006 Implementation Seminar : 11/09/06 Infrastructure Overview  Data sent from iGMS to GMRS  Data processed and stored within GMRS  GMRS also contains the logic for receiving user web report requests and generating database queries  Minimises impact upon iGMS  Internal area where tables & graphs are configured

5. UNC006 Implementation Seminar : 11/09/06 Timeliness of Data Publication  Delivers ‘near real time sub-terminal flow information’, measured in mcm/day  Data at 2 minute resolution, delivered to the internet every 12 minutes  Data Published with a latency of approx. 2 minutes *  E.g. the following data would be published at around 12:00  Shows flow information at specific times * batch job for collating/publishing the data starts at 1 minute after last snapshot

6. UNC006 Implementation Seminar : 11/09/06 System Performance  The system is designed to manage up to 375 concurrent data requests from users.  Concurrent data requests split by the following ratio:  265 requests for latest data snapshot, plus  110 requests for historical and user specified data  System will deliver a screen response time of approximately 5 seconds for the latest 12 minute data snapshot (but user perception will be also be impacted by speed of individual internet link)  Many more users will be able to have the screens ‘open’ at any one time

7. UNC006 Implementation Seminar : 11/09/06 System Performance – Downloads  Downloads available from page 1 and page 3  Page 1 for latest 12 minute data  Page 3 for flexible download facility  Allows user to define date range  Any combination of sub – terminals can be viewed or downloaded  Up to 2 years historical data will eventually by available, although obviously there will be no ‘history’ on day 1  Maximum file download size restricted to 20MB  Approx. 2 weeks of data for 30 entry points  Approx. 40 days of data for 10 entry points  Approx 10 minutes to download largest filesize  Dependent upon users internet link/broadband speed etc.

8. UNC006 Implementation Seminar : 11/09/06 Resilience and Support  System designed for 99.9% availability (excluding planned outages)  Weekly planned outage window on Sundays 04:00 – 06:00  Dual redundancy and full load balancing across NG Internet servers  Auto-failover between duty system & standby system in case of major system failure within 30 minutes  System monitored and supported on a 24/7/365 basis  GMRS has functionality to raise alerts automatically if no flow data received and for publication failures / delays  Queries regarding system functionality to be directed to the e-mail address, telephone number below or via the IE3 feedback form  E-mail : Sysop.centre.reporting@uk.ngrid.com  Telephone : 01926 654639 (answer-phone outside of normal hours)  Feedback form within Operational Data on IE3 website

9. UNC Mod 006 – Using the system Nigel Bradbury September 2006

10. UNC006 Implementation Seminar : 11/09/06 Information Location  Available from the National Grid website www.nationalgrid.com  Located with other market data provided by National Grid within the Operational Data area of the site www.nationalgrid.com/uk/gas/data  Situated on a new button entitled  Energy – Flow Data,  or at URL www.nationalgrid.com/uk/gas/data/EFD  Information made available in 3 complimentary ways across 3 pages

11. UNC006 Implementation Seminar : 11/09/06 Website Screens  Page 1 (Instantaneous Flows)  Latest 12 minute data in tabular and graphical form  Always shows the most currently available data  Page 2 (Entry Zone Graphs)  Up to last 24hrs data in graphical form by terminal / type  Can be used to monitor trends  Period selectable by user  Page 3 (User Defined downloads)  Provides flexible data download facility  Allows user to define download period, and  Any combination of sub–terminals/terminals

12. UNC006 Implementation Seminar : 11/09/06 Data Downloads  Downloads available from pages 1 and 3  Provided in.csv format  Data provided to 6 decimal places  Page 1  Provides latest 12 minute data snapshot  Not definable by user  Contains data quality flags  Page 3  User defined download  Variable period and content

13. UNC006 Implementation Seminar : 11/09/06 Application Programming Interface  API’s will allow data snapshots to be delivered to users via a programmed script  Avoids the requirement for ‘screen scraping’  2 APIs developed  API to provide latest published data/notes  On demand data delivery through request\ response mechanisms  Supports HTTP Compression  User benefits – quicker delivery of data  Data provided in XML format  Remove requirement for automated screen scrapers.  API to provide last publication time  Safeguard against duplicate data download.  Optimal Bandwidth usage.  Compliance with Web service standards  supports multiple platform J2EE,.NET

14. UNC006 Implementation Seminar : 11/09/06 Notes  Displayed on page 1  These will be used to provide additional information to users regarding :  System maintenance (e.g. planned outages)  Configuration of sites (e.g. new sites, aggregation changes)  Data issues of a significant nature  System updates  Ad-hoc information  Information will be dated and time-stamped and visible for 2 years  Latest notes will be included automatically within API downloads (but not user defined data downloads)

15. UNC006 Implementation Seminar : 11/09/06 Example of Screen Layout – Page 1 6 snapshots of data at 2 minute intervals updated every 12 minutes Graph of latest flow data by subterminal Data issues highlighted Feedback Form Telephone Helpline: 01926 65 4639 Latest relevant note Historical notes System entry point names and flows shown for illustration purposes only

16. UNC006 Implementation Seminar : 11/09/06 Example of Screen Layout – Page 1 (Cont) Latest total daily flow into NTS Graph of latest flows for terminal System entry flows shown for illustration purposes only

17. UNC006 Implementation Seminar : 11/09/06 Example of Screen Layout – Page 2 Selectable time period Feedback Form Telephone Helpline: 01926 65 4639 Contact details for technical assistance 1 graph per ASEP or storage category (10 in total) System entry flows shown for illustration purposes only

18. UNC006 Implementation Seminar : 11/09/06 Example of Screen Layout – Page 2 (last 24 hours) Feedback Form Telephone Helpline: 01926 65 4639 Selectable time period – last 24 hours selected System entry flows shown for illustration purposes only

19. UNC006 Implementation Seminar : 11/09/06 Example of Screen Layout – Page 3 Feedback Form Telephone Helpline: 01926 65 4639 Selectable time period Select original or amended data Select sites of interest Selected data displayed graphically System entry flows shown for illustration purposes only

20. UNC006 Implementation Seminar : 11/09/06 Data can be also be received in.csv format. Flags are used to show how data values are derived When Published SiteValueTime CSV Download Quality Flags System entry flows shown for illustration purposes only

21. UNC006 Implementation Seminar : 11/09/06 HELP ! What is available for users :  Helptext / Definitions available on each page  E-mail address, website feedback form and phone number for technical questions :  E-mail : sysop.centre.reporting@uk.ngrid.com  Feedback form available within Operational Data on the IE3 website  Telephone : 01926 654639 (answer-phone outside of normal office hours)  FAQs  Available on the Operational Data page  Notes and Website News updated as necessary

22. UNC006 Implementation Seminar : 11/09/06 Queries and Feedback  All questions to NG regarding the system will be handled by the NG Operational Data team to ensure consistency of response.  We can help with queries about the functionality of the system and how to get the most from it  We welcome feedback about your experiences of the system and how we can develop it going forwards  Also please let us know if you are having problems with the system or concerns about the accuracy of the data contained therein  We cannot however provide explanation or interpretation of trends or changes within the data – unless this is due to a specific data problem that we are aware of for example. we cannot gives reasons why the flow from a specific sub-terminal dropped by 5mcm/day at 14:42 this afternoon  Please do not contact the NG Gas Control Room to discuss the data being published

23. UNC Mod 006 - Data Issues Paul Gallagher September 2006

24. UNC006 Implementation Seminar : 11/09/06 Configuration  Zone Supply table will show  all sub-terminals that are capable of flowing >=10mcm/day  Aggregated values for sub-terminals totalling >=10mcm/day capability within a single ASEP or storage category  All LNG storage sites  Zone Supply table will NOT show  Aggregated values for sub-terminals totalling <10mcm/day capability within a single terminal or storage category  Some sub-terminal data will not be included within the Zone Supply table in individual or aggregated form

25. UNC006 Implementation Seminar : 11/09/06 Initial Configuration  The initial Zone Supply table will be configured as follows

26. UNC006 Implementation Seminar : 11/09/06 Configuration  Terminal Supply table will show all sub terminals associated with the respective terminal – irrespective of whether shown in the Zone Supply Table  Total Supply table will show the combined total supply for all Sub-terminals, Interconnectors & Storage Sites - irrespective of whether shown in the Zone Supply table

27. UNC006 Implementation Seminar : 11/09/06 Configuration updates  Sub-terminal capability levels and aggregation rules will be reviewed annually as part of the Transporting Britains Energy (TBE) process  Review carried out during late summer  Any changes to the Zone Supply table as a result of the TBE process will be published within the NG website news pages and notes at least 4 weeks ahead of reconfiguration on the site  New sites, or new capacity at existing sites, will be included within year as the new capacity comes on line, again with a suitable period of warning to users  For example, Teesside PX will not initially be included in the Zone Supply table as capability is currently below 10mcm/day, however it will be included later in the winter as the LNG importation facility becomes operational and increases the capability

28. UNC006 Implementation Seminar : 11/09/06 Data Quality  Data is being provided in real time directly from the iGMS system  There are always potential ‘quality’ issues when dealing with real time data e.g. Meter errors, communication failures, system faults  We have adopted the philosophy that the market will see the same data that the NG control room sees  Data quality indicators will automatically be displayed on screen for specific situations  Downloaded data files and API will also give indicators of data quality  NG control room may, at their discretion, carry out amendments to clearly erroneous data if appropriate and timescales allow

29. UNC006 Implementation Seminar : 11/09/06 Data quality indicators The following quality indicators will be provided  Amended  data is manually amended and time stamped  Late  data for time slot was received late  Expired  Failure in telemetry  Substituted  data is missing. Last know good value used  In many cases more than 1 indicator will apply.  There will be instances where existing data quality issues are not flagged, for example if a third party meter is providing spurious data.  Users may believe it necessary to do additional data validation to confirm the acceptability of the data for their own use, for example it should be fairly straightforward to look for unchanging non zero values, data outside of expected ranges etc

30. UNC006 Implementation Seminar : 11/09/06 Historical Data  Data stored for a period of 2 years  Data available in originally published and latest available form  Where data has been amended more than once, only the finally amended position will be available  Data quality indicators will also be stored for the defined period  Historical data will be available for all individual sites and aggregated groups that have been published over the period, not just for the current configuration of sites  Historical data should be reviewed with reference to Notes, due to the potential confusion that could be caused by configuration changes and other ad-hoc issues

31. UNC006 Implementation Seminar : 11/09/06 Historical Data – configuration changes  For example, ASEP A may contain 3 sub-terminals : A1, A2 and A3  What is published may vary with time as capabilities change

32. UNC006 Implementation Seminar : 11/09/06 Interpreting the data  Interpreting, and devising action strategies based on the data will be an issue for users  Care should be taken before making decisions based on the data, and where possible the data should be cross referenced with other available information  Sudden changes in flow rates are not necessarily caused by major problems and may be for benign reasons that do not require action by users  Changes to flow rate may be due to a number of different reasons, for example:  Shipper re-nomination as new demand forecasts become available  Capacity or locational actions by the system operator  Response to short term Terminal Flow Advice (TFA)  Off-shore or terminal technical difficulties  Response to price signals  Many of these reasons will not be obvious to users from the information available on the system

33. UNC006 Implementation Seminar : 11/09/06 Interpreting data  Other sources of information which may help interpretation are, for example :  ANS messages  Will provide info on some national issues and NG actions / requirements  GBA status  May be updated within day following major losses of greater than 25mcm  Comparison with NTSAFF report  Shows forecasted EOD supplies based on DFNs rather than current flow rates  Latest PCLP forecast  Compare with PCLP trend  Other sites and sources of information  eg IUK site, Centrica’s storage site etc  Experience of the data provided from the system over time will also help users to interpret the type of issues that are being seen

34. Mod 006 - Examples of Flow variations Frank Gracias September 2006

35. Pressure Constraint

36. UNC006 Implementation Seminar : 11/09/06 Flow restriction due to pressure constraint at Terminal 1

37. UNC006 Implementation Seminar : 11/09/06 Pressure constraint continues Supplies switched to Terminal 2

38. UNC006 Implementation Seminar : 11/09/06 Terminal 1 flow reduces due to further flow restriction Second terminal increases flow rate to compensate

39. UNC006 Implementation Seminar : 11/09/06 Continuing flow restrictions at Terminal 1 Reduction in flow possibly due to downward nomination

40. UNC006 Implementation Seminar : 11/09/06 Increase possibly due to late upward nomination

41. Loss of Storage Site Example

42. UNC006 Implementation Seminar : 11/09/06 Flow variations due to problems at storage site

43. UNC006 Implementation Seminar : 11/09/06 Storage Site ceases to flow Demand forecast reduces supply requirement and so Terminal reduces flow

44. UNC006 Implementation Seminar : 11/09/06 Terminal responds to Storage export loss as Shippers resource supply

45. UNC006 Implementation Seminar : 11/09/06 Supplies lost due to failure of the storage site are replaced by beach gas

46. Major Offshore Supply loss example

47. UNC006 Implementation Seminar : 11/09/06

48. Normal Summer Day example

49. UNC006 Implementation Seminar : 11/09/06

52. High Demand example

53. UNC006 Implementation Seminar : 11/09/06

54. NG Website - Operational Data Overview Paul Gallagher September 2006

55. UNC006 Implementation Seminar : 11/09/06 Operational Data Overview

56. UNC006 Implementation Seminar : 11/09/06 GBA, ANS & Demand Gas Balancing Alerts for current day and D +1 Will detail any Non- Routine ANS messages A free text field for any relevant information The demand table provides data for the current gas day (D), the previous gas day (D+1) and the next gas day (D-1) Refresh Frequency The user uploads Storage spreadsheet. At beginning of gas day ANS warning changes on NG website. Beginning of gas day The user updates the note section. Actual demand at 11:30. Within day forecast hourly. Day ahead demand at 00:00,13:00,16:00,0

57. UNC006 Implementation Seminar : 11/09/06 Flows into NTS, Linepack, Transporter Interruption The interruption table summarises the latest likelihood to interrupt position for the current gas day Current gas day’s opening linepack level, Predicted closing linepack (PCLP1) and the change in linepack is displayed Contains data in line with the latest national supply in mcm from NTSAFF report Refresh Frequency Hourly User update of interruptions section. Daily at 1400

58. UNC006 Implementation Seminar : 11/09/06 Storage, Supply, Price Market Prices Latest system entry position, and provides an indication of the latest flows compared to the max, min and average flows. Based on submissions by storage operators, this provides latest opening storage position. Also an indication of the period until a safety monitor breach takes place if gas was withdrawn Refresh Frequency By 16:00 each day. 11:00 daily (for D+2) 11:00 daily

59. Changes for 2006/7 Paul Gallagher July 2006

60. UNC006 Implementation Seminar : 11/09/06 Daily Summary Report  What is being changed for winter 2006/7  Gas Balancing Alert (GBA) trigger level to be shown explicitly  New D-2 to D-5 demand forecasts  SMS/e-mail messaging facility for GBA Alert  More comprehensive ANS messages  Timestamps added to graphs  Link to ‘Near real time flow data’  Larger notes field

61. UNC006 Implementation Seminar : 11/09/06 Demand Forecast (D-2 to D-5) Click here for D-2 to D-5 forecast data New Option to view D-2 to D-5 forecasts Ability to view key data on one screen of critical importance Click here for historical D-2 to D-5 forecast report Latest Demand Forecast D-2 to D-5 09/06/06 16:00 +/- 40335 Demand Forecast D-413/06/06 09/06/06 16:00 +/- 35340 Demand Forecast D-312/06/06 09/06/06 16:00 +/- 45370 Demand Forecast D-514/06/06 09/06/06 16:00 +/- 30360 Demand Forecast D-211/06/06 90% Confidence Interval (mcm) Demand (mcm) Use of pop-up to meet requirement D-2 to D-5 historical report accessed here

62. UNC006 Implementation Seminar : 11/09/06 Other changes to the website  Revised menu structure  To improve ease of navigation  e.g. specific menu tab for storage data  Additional data items  Historical SND information  Priority site aggregated demand  Revised help information  Standard formats  More comprehensive  New supplemental help menu

63. UNC006 Implementation Seminar : 11/09/06 Capacity Summary - New

64. UNC006 Implementation Seminar : 11/09/06 Storage Information - New

65. UNC006 Implementation Seminar : 11/09/06 Misc System Info - Changes

66. UNC006 Implementation Seminar : 11/09/06 Supplementary Help - New