1. Presented by Kennedy Subramoney Specification – Project Leader Resources & Strategy (A Division of Eskom) CR&D Department XMLVend (Online Vending Specification) Towards an Industry Standard (NRS009-6-10)

2. 1.XMLVend Background 2.Online Vending - Context 3.XMLVend Specification Overview 4.Road Map 5.Some implementation insights 6.XMLVend 2.0 7.Conclusions 8.XMLVend in Action Discussion Points

3. Background The requirements for an Online Vending Specification were: Curb the use of Proprietary Systems. Specify minimum security, communication, & interoperability standards. Must be platform independent, extensible and adaptable. Support existing prepayment standards, STS and CVS (NRS009 Series). Ensure industry support and ownership. Utilize existing industry technology standards. Development tool set support Existing Developer Skills base.

4. Online Vending Centralized Multiuser Database Centralized Vending Business Logic Centralized Security Modules (STS Token Generation) “Thin” Client / Server Architecture

5. Specification Overview Web Service Interoperability Organization (WS- I) – Ensures interoperability. ML file used to define the contract by which the Web Service Providers and Consumers interact, i.e. Vending Servers and Vending Clients. WSDL - XML file used to define the contract by which the Web Service Providers and Consumers interact, i.e. Vending Servers and Vending Clients. XML file used to define message contents and message element data types and constraints. XML Schema - XML file used to define message contents and message element data types and constraints.

6. Web Services layer – (XML and SOAP) Content Compression uses GZIP. Application layer uses HTTP. Security - SSL / TLS authentication and encryption. TCP/IP – Network Communications layer. Link / Physical Layer Specification Overview

7. XMLVend Road Map v1.0 (5/03/2004) 1 st Release v1.1 (11/06/2004) Fixes minor Issues. Server RFP v1.22 (28/01/2005) Major Update KCT schema type Tax Details v2.0 May/June ‘06 Major Update New Use Cases. O.O.

8. Implementation Insights Eskom Server RFP and Pilot Results. Extensive Testing of Use Cases – updates identified. Implementation of SSL / TLS. Implementation of GZIP Compression.

9. Security (SSL / TLS) Technology easily implemented, however the required supporting PKI is still to be tested. Mandatory “Client ID” Authentication on every financial request. Secure SSL Channel Client ID-123

10. Compression - GZIP Average saving - 1156 bytes Average % Impact of GZIP - 38%.

11. Compression - GZIP Average Overhead – 53% Vend Use Case overhead – 47%

12. Illustrative Message Costs* Assuming GPRS cost of R2-00 per MB The cost of a Vend and EBSST transactions are – 0.41 cents and 0.39 cents resp. The average cost of all transactions – 0.38 cents. Note: These costs only indicate the cost per transaction and not the Total Cost of Operating an Online Vending System.

13. XMLVend 2.0 The following new Use Cases have been identified: Credit Update Statement STS Engineering Tokens Auto-Reprint Last Transaction Debt Recovery Bank (“Create Deposit Slip”) Customer Fault Reporting Account Payments Reprint Deposit Slip

14. XMLVend 2.0 Improved Object Oriented Design. Message size optimization. HTTP Header optimization. Specification Reference Implementation. Specification Test Suite Release.

15. Conclusions XMLVend ensures that there is the continued standardization of prepayment vending. XMLVend1.0 has been produced with significant contributions from several vending equipment suppliers, which demonstrates the level of maturity within the industry. XMLVend has matured into a robust and stable specification, with significant support to become an Industry Standard.

16. XMLVend in Action

17. Thank you and Acknowledgement of all contributors to XMLVend - a specification for industry, by the industry. kennedy.subramoney@eskom.co.za http://www.nrs.eskom.co.za/xmlvend