Pre-production: Wednesday 12 December 2018 Production: Wednesday 30 January 2019

Transcription

1 1.00 Draft December 2018 Pre-production: Wednesday 12 December 2018 Production: Wednesday 30 January 2019 Release series: MSATS AEMO 2018 MSATS Release Schedule - January

2 PURPOSE & AUDIENCE This document describes the technical changes required to participant s systems for the MSATS - Release Schedule - January The Australian Energy Market Operator (AEMO) provides this information as a service targeting business analysts and IT staff in participant organisations. It provides guidance about the changes to their market systems under the National Gas or Electricity Rules (Rules), as at the date of publication. HOW TO USE THIS DOCUMENT If you have questions about the business aspects of these changes, please see Consultations on AEMO s website. The references listed throughout this document are primary resources and take precedence over this document. Unless otherwise stated, you can find resources mentioned in this guide on AEMO's website. Text in this format, indicates a reference to a document on AEMO s website. This document is written in plain language for easy reading. Where there is a discrepancy between the Rules and information or a term in this document, the Rules take precedence. Glossary Terms are capitalised and have the meanings listed against them in the Glossary. Italicised terms are defined in the Rules. Any rules terms not in this format still have the same meaning. PRIVACY AND LEGAL NOTICES The material in this publication may be used in accordance with the privacy and legal notices on AEMO s website. TRADEMARK NOTICES Microsoft, Windows and SQL Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. Oracle and Java are registered trademarks of Oracle and/or its affiliates. UNIX is a registered trademark of The Open Group in the US and other countries Google Inc, used with permission. Google and the Google logo are registered trademarks of Google Inc. DISTRIBUTION Available to the public. DOCUMENT IDENTIFICATION Prepared by: AEMO Market Systems Last update: Wednesday, 5 December :22:00 VERSION HISTORY 1.00 Initial creation DOCUMENTS MADE OBSOLETE The release of this document changes only the version of MSATS Release Schedule - January FURTHER INFORMATION For further information, please visit AEMO s website or contact: AEMO s Support Hub Phone: 1300 AEMO 00 ( ) and follow the prompts. supporthub@aemo.com.au FEEDBACK Your feedback is important and helps us improve our services and products. To suggest improvements, please contact AEMO's Support Hub Australian Energy Market Operator Limited. The material in this publication may be used in accordance with the copyright permissions on AEMO s website.

3 Introduction 1. Introduction Summary Schedule Proposed timeline Approval to change Related resources Glossary New transactions and subtypes Life Support Request Life Support Notification Schema, Procedure, and Rule Changes B2B AseXML Schema B2B Procedure: Customer and Site Details Notification process v National Electricity Rule 2017 No Interfaces B2B Browser FTP, APIs, Batch Handlers, and Participant Batcher How to see and access the new transactions B2B Transforms Transform criteria Transform scenarios Applying a Transform Validation Life Support Request validation Life Support Notification validation Special Notes validation Validation Module software Validation Module Matrix B2B Responder Recommended parsers AEMO 2018 MSATS Release Schedule - January 2019 iii

4 Introduction 1.1 Summary This Release Schedule describes the changes to participant systems to enable participants to meet their obligations under AEMC rule change, Rule 2017 No 3 -Strengthening protections for customers requiring life support equipment. For this release there is a new B2B asexml schema change to r38. The key areas of change are: Two new B2B transactions to exchange life support information between participants. A new B2B asexml schema, r38 from r Schedule Scheduled for implementation in: Pre-production: Wednesday 12 December 2018 Production: Wednesday 30 January Proposed timeline The dates for the User Group Meetings are tentative. We will provide an invitation one week prior to the meeting. Milestone Date Description Approval required None required No approval is required because this schema change is mandated by regulation. User group meeting: initial Revised Release Schedule 19 December December December 2018 January 2019January 2019January 2019 Market systems user group meeting to discuss items on this Release. Further details of the changes to assist IT staff with their own technical implementation. AEMO 2018 MSATS Release Schedule - January

5 Introduction Milestone Date Description Pre-production refresh Pre-production implementation Pre-production available Production implementation No pre-production refresh required 3 December December December 2018 Wednesday 12 December 2018 Wednesday 12 December January January January 2019 Refresh of the pre-production system with data refreshed from the production system. An outage of up to five days can occur to the pre-production environment during this period. Participant access is not restricted, however, AEMO do not guarantee the preproduction data content or system availability. During the refresh, access to other AEMO systems such as AWEFS, EMMS, OPDMS, and STTM may be intermittently affected. AEMO implements components of the Release to preproduction for participant testing. AEMO has full access to the system during this period. Participant access is not restricted; however, the data content or system availability is not guaranteed. Testing period begins for participants. AEMO implements the release to production during the normal 2-hour maintenance window. Production systems available User group meeting: postimplementation review Wednesday 30 January December December February 2019 Production systems available to participants Market systems user group meeting to review the implementation of the production release. 1.4 Approval to change No approval is required from participant change controller because this schema change is mandated by regulation. 1.5 Related resources Rules National Electricity Rules: Rule 2017 No3 - Strengthening protections for customers requiring life support equipment. Effective 1 February AEMO 2018 MSATS Release Schedule - January

6 Introduction AEMO website asexml_r38.zip, to obtain the schema, see Systems/aseXML_standards. There are updates to the final version since AEMO published the draft version for consultation. Participants should remove any previous versions and replace it with the latest version. B2B Mapping to asexml: Maps the electricity B2B Business Documents and Signals to their asexml Transactions and Acknowledgements. B2B Procedure: Customer and Site Details Notification process: Published by AEMO in accordance with clause of the NER. It specifies the standard process and data requirements for the communication, updates, and reconciliation of Customer and Site details. B2B Procedure: Technical Delivery Specification: Published by AEMO in accordance with clause of the NER. It specifies the technical requirements for the delivery of B2B Transactions using the e-hub. B2B SMP Technical Guide: Provides participants with the technical specifications for the Delivery of B2B transactions using the e-hub. Connecting to AEMO s Electricity IT Systems: Explains the IT interfaces available for electricity participants and how to connect to them. Guide to MSATS and B2B Terms: Assists participants of the Retail National Electricity Market (NEM) to understand the terms used in the retail electricity market procedures and the Market Settlement and Transfer Solution (MSATS) participant IT system. Guide to MSATS B2B: Provides information about the b2b e-hub functions available in the market settlement and transfer System (MSATS). Guide to User Rights Management: assists Participant Administrators (PAs) to provide access rights to AEMO s participant IT systems for their Participant Users. Participant Batcher Software and Guide: Provides a simple batch interface to MSATS and B2B by removing the detail of the file handshaking and leaving participants to deal with the raw.zip files only. The Participant Batcher software transfers files using FTP from and to the MSATS and B2B participant file shares. The Participant Batcher software does the entire message acknowledgement and file manipulations as required by the batch file interfaces. Validation Module Software and Guide: An application participants can embed in their B2B systems allowing them to validate an XML file before it is deployed to the MSATS B2B Web Portal AEMO s Support Hub Phone: 1300 AEMO 00 ( ) and follow the prompts. AEMO 2018 MSATS Release Schedule - January

7 Introduction Glossary For help with other abbreviations and terms, see Guide to MSATS and B2B Terms. Abbreviation or term Definition LSN Life Support Notification LSR Life Support Request Business Document asexml Transaction AEMO 2018 MSATS Release Schedule - January

8 New transactions and subtypes The following new transactions are created under the CUST transaction group to enable retailers and network operators to request and transmit details about customers using life support equipment. 2.1 Life Support Request There is a new transaction, Life Support Request (LSR) allowing participants to request information from other participants. The Initiator sends an LSR and the Recipient responds with an LSN. The Life Support Request utilises all existing fields in the current B2B schema, r36. For all transaction fields, see B2B Procedure: Customer and Site Details Notification process v Life Support Notification There is a new transaction, Life Support Notification (LSN) allowing participants to transfer information between themselves. The Recipient sends an LSN to the Initiator in response to an LSR. The LSN utilises existing fields in the current schema, r36 and introduces new fields in r38. When a participant needs to notify another participant of life support information or there is a change to life support information, participants can send an LSN without a corresponding LSR New LSN fields Key M = Mandatory (must be provided in all situations). R = required (if this information is available or has changed). O = Optional (may be provided). N = Not relevant (not to be provided). AEMO 2018 MSATS Release Schedule - January

9 New transactions and subtypes Field Format Use Definition/Comments DateRequired DATE M/N For a registration of Life Support, this date is the date Life Support protections commence at the premises. For a deregistration of Life Support, this date is the date Life Support protection ceases to be provided at the premises. For response to a Life Support Request, this is the effective date of the Life Support registration in the participant s system. Not required when Status is None. Equipment VARCHAR(50) R/N Allowable values: Oxygen Concentrator Intermittent Peritoneal Dialysis Machine Kidney Dialysis Machine Chronic Positive Airways Pressure Respirator Crigler Najjar Syndrome Phototherapy Equipment Ventilator for Life Support Other: means an equipment that a registered medical practitioner certifies is required for a person residing at the customer s premises for life support and is not already listed above Not required when Status is Deregistered No Medical Confirmation Deregistered Customer Advice Deregistered No Customer Response None LSContact Address VARCHAR(100) R/N Must be the address of the person who is the contact for the management of Life Support requirements where the initiator has obtained Explicit Informed Consent for the use of the address. Not required when Status is: Deregistered No Medical Confirmation Deregistered Customer Advice Deregistered No Customer Response None AEMO 2018 MSATS Release Schedule - January

10 New transactions and subtypes Field Format Use Definition/Comments LSContactName PERSONNAME R/N Must be the name of the person who is the contact for the management of Life Support requirements. Refer to B2B Procedure: Technical Delivery Specification. Contact Details are mandatory if the Postal Address is provided. Not required when Status is: Deregistered No Medical Confirmation Deregistered Customer Advice Deregistered No Customer Response None LSPostalAddress ADDRESS R/N Must be the customer s postal address for Life Support requirements. Refer to B2B Procedure: Technical Delivery Specification Not required when Status is: Deregistered No Medical Confirmation Deregistered Customer Advice Deregistered No Customer Response None PreferredContactMethod VARCHAR (20) O Allowable values: Postal Address Site Address Address Phone RegistrationOwner YES NO M/N Value of YES must be used, where the Initiator of the LSNLifeSupportNotification is the Life Support registration process owner. Not required where Status is None. LifeSupportStatus VARCHAR (50) M Allowable values: Registered: No Medical Confirmation Registered: Medical Confirmation Deregistered: No Medical Confirmation Deregistered: Customer Advice Deregistered: No Customer Response None: Means the premises does not have a current Life Support requirement AEMO 2018 MSATS Release Schedule - January

11 Schema, Procedure, and Rule Changes 3.1 B2B AseXML Schema This project introduces a new B2B schema from r36 to r38 enabling retailers and network operators to request and transmit details about customers using life support equipment. There are no changes to the MSATS B2M asexml schema. The r38 schema has the following additions: Description Use asexml type Schema ContactMethod Define the basic set of contact methods Simple Enumerated list CustomerDetails_r38.xsd LifeSupportData LifeSupportNotification transactions Complex CustomerDetails_r38.xsd LifeSupportEqType Define the fixed life support equipment types used in Life Support notificationlsns Enumerated list ElectricityEnumerations.xsd LifeSupportNotification Transaction message Complex Transactions_r38.xsd CustomerDetails_r38.xsd LifeSupportRequest Transaction message Complex Transactions_r38.xsd CustomerDetails_r38.xsd LifeSupportRequestReason LifeSupport transactions Define the fixed life support request reasons for a Life Support Request LSR Simple Enumerated list CustomerDetails_r38.xsd LifeSupportType LifeSupport transactions Simple Enumerated list CustomerDetails_r38.xsd Release identifier Release identifier Simple Events_r38.xsd AEMO 2018 MSATS Release Schedule - January

12 Schema, Procedure, and Rule Changes Description Use asexml type Schema Status Define the fixed life support status used in Life Support notificationlsns Simple Enumerated list CustomerDetails_r38.xsd UpdateReason Define the reasons for provision of details notification Simple Enumerated list CustomerDetails_r38.xsd Complex types LifeSupportData Elements Type NMI NMI SiteAddress Address Reason UpdateReason RegistrationOwner YesNo AEMO 2018 MSATS Release Schedule - January

13 Schema, Procedure, and Rule Changes Elements Status DateRequired Equipment Type Status xsd:date LifeSupportEqType ManagementContactDetail CustomerDetail PreferredContactMethod SpecialNotes1 SpecialNotes2 SpecialNotes3 LastModifiedDateTime ContactMethod SpecialComments SpecialComments SpecialComments xsd:datetime LifeSupportRequest Elements NMI Reason Type NMI LifeSupportRequestReason SpecialNotes SpecialComments AEMO 2018 MSATS Release Schedule - January

14 Schema, Procedure, and Rule Changes Life Support Notification Name Elements Type LifeSupportNotification LifeSupportData LifeSupportData Simple types: Enumerated lists List Status Values Registered - No Medical Confirmation Registered - Medical Confirmation Deregistered - No Medical Confirmation Deregistered - Customer Advice Deregistered - No Customer Response AEMO 2018 MSATS Release Schedule - January

15 Schema, Procedure, and Rule Changes List LifeSupportEqType Values Oxygen Concentrator Intermittent Peritoneal Dialysis Machine Kidney Dialysis Machine Chronic Positive Airways Pressure Respirator Crigler Najjar Syndrome Phototherapy Equipment Ventilator for Life Support Other LifeSupportRequestReason Confirm Life Support Data Quality Issue No response to rejected LSN Other UpdateReason ContactMethod Update Reconciliation Postal Address Site Address Address Phone Roles The following roles can create and receive the new transactions: FRMP LNSP MDP MPB RP What happens if I do not update my schema Participants not updating their B2B schema from r36 to r38 cannot send or receive Life Support Transactions. AEMO 2018 MSATS Release Schedule - January

16 Schema, Procedure, and Rule Changes 3.2 B2B Procedure: Customer and Site Details Notification process v3.2 Published by AEMO in accordance with clause of the NER. This Procedure specifies the standard process and data requirements for the communication, updates, and reconciliation of Customer and Site details. 3.3 National Electricity Rule 2017 No 3 Strengthening protections for customers requiring life support equipment: Effective 1 February AEMO 2018 MSATS Release Schedule - January

17 Interfaces 4.1 B2B Browser Participants can create, acknowledgement, accept, reject, and search for the two new transactions using the MSATS B2B Browser menus: New Transaction: create new transaction. B2B Inbox: create and search for FTP protocol transactions and acknowledgements. B2B Outbox: search for FTP protocol received transactions. B2B Hub Queue: Search and acknowledge API protocol transactions. Search Hub Transaction Log: search API protocol transactions. Upload File: use to upload.zip and.xml files directly to your B2B Inbox based on your protocol preference, API or FTP. The following screenshots provide examples of the interfaces. AEMO 2018 MSATS Release Schedule - January

18 Interfaces Create New Transaction Create Life Support Request Transaction ID Transaction Date NMI NMI Checksum Reason Special Notes 1 Special Notes 2 Special Notes 3 AEMO 2018 MSATS Release Schedule - January

19 Interfaces Create: Create the transaction. Validate: Perform validations. Download: Allows opening or saving the transaction as an XML file. Reset: Return the fields to its original state Create Life Support Notification Part 1 Transaction ID Transaction Date Initiating Transaction ID Registration Owner Reason Life Support Status Last Modified Date Last Modified Time Date Required NMI NMI Checksum Life Support Equipment Life Support Contact Name AEMO 2018 MSATS Release Schedule - January

20 Interfaces Life Support Phone Numbers Address (Site Address) Postal Address (Postal Address) Special Notes Create: Create the transaction. Validate: Perform validations Download: Allows to open or save the transaction as XML file. Reset: Return the screen to its original state Part 2 AEMO 2018 MSATS Release Schedule - January

21 Interfaces Part Successful FTP transaction Successful API transaction AEMO 2018 MSATS Release Schedule - January

22 Interfaces Example of validation failure Search transactions in the B2B outbox Search transaction Search for the Life Support Transaction in your B2B Inbox and select it. To view the Transaction, click the Filename in the search results. AEMO 2018 MSATS Release Schedule - January

23 Interfaces Delete or download a transaction To view the transaction details, click the Transaction ID View transaction Acknowledge transaction in the B2B outbox Acknowledgement success AEMO 2018 MSATS Release Schedule - January

24 Interfaces 4.2 FTP, APIs, Batch Handlers, and Participant Batcher Participants can acknowledgement, accept, and reject the two new transactions using: 1. FTP to the Participant File Server. For help, see Connecting to AEMO s Electricity IT Systems. 2. APIs to the B2B e-hub. For help, see B2B SMP Technical Guide Participant Batcher software At pre-production release time, participants can find a new version of the Participant Batcher software (ParticipantBatcherv zip) on AEMO s website: The download is a single ZIP file containing the compiled software, supporting libraries and source code: asexml classes lib log sample src contains source code crypt.bat pbenvironment.bat sample.bat stop.bat sample.properties README.txt lists the ZIP file contents and version history 4.3 How to see and access the new transactions To see the new transactions in the B2B Browser and to access them via FTP, Batch Handlers, and Participant Batcher, Participant Users require their company s Participant Administrator (PA) to provide access in the MSATS Administration menu. Participant Administrators (PA) are set up during the registration process. If you don t know who your company s PA is, contact AEMO s Support Hub. AEMO 2018 MSATS Release Schedule - January

25 Interfaces The user rights entities required are: B2B Life Support Notification B2B Life Support Request For help with User Rights Management (URM), see Guide to User Rights Management. AEMO 2018 MSATS Release Schedule - January

26 B2B Transforms If required, participants can send and receive B2B files in a different version of supported schemas. For this project, participants can apply transforms between schema versions r36 and r38, and vice versa. 5.1 Transform criteria MSATS will pass through and not transform B2B transactions submitted in versions lower than r36. For help with B2B Transforms, see Guide to MSATS B2B. If the transformation result is schema valid, then the transformed file or message is delivered, otherwise MSATS delivers the sent version. The transformation is independent of the Transaction Group (CUST, SORD, MTRD etc) and Protocol preference (API or FTP). 5.2 Transform scenarios Scenario Schema sent to Inbox Received preference Delivered to Outbox Comments No Life Support Transaction r36 r36 r36 No transformation required r37 r36 r37 No transformation required r38 r36 r36 Transformation applied from r38 to r36. No Life Support Transaction r36 r38 r38 Transformation applied from r36 to r38. r37 r38 r37 No transformation required r38 r38 r38 No transformation required No Life Support Transaction r36 r_any r36 No transformation required r37 r_any r37 No transformation required r38 r_any r38 No transformation required AEMO 2018 MSATS Release Schedule - January

27 B2B Transforms Scenario Schema sent to Inbox Received preference Delivered to Outbox Comments Life Support Transaction r38 r36 r38 Transformation applied from r38 to r36, but the schema validation fails because the Life Support Transaction is not supported in r36. AEMO delivers the original file. r38 r38 r38 No transformation required r38 r_any r38 No transformation required 5.3 Applying a Transform To apply a transform, in MSATS, go to the B2B Browser > B2B Transforms and Protocol. AEMO 2018 MSATS Release Schedule - January

28 Validation In addition to the validations below, as per standard validations in MSATS are: From, To, MessageID, Transaction Group, Message Date, Priority, Market, Transaction ID, Transaction Date. 6.1 Life Support Request validation No Field Format Use Definition & notes 1. NMI CHAR(10) M NMI 2. NMI Checksum CHAR(1) O NMI Checksum 3. Reason VARCHAR (30) M Allowed Values: Confirm Life Support Data Quality Issue No response to rejected LSN Other Notes: Confirm Life Support: The Retailer or DNSP requires confirmation the Connection Point has a Life Support requirement. Data Quality Issue: Although the data may be technically correct, it may not be fit for purpose (e.g. phone number is ). The Retailer or DNSP must detail the specific data they are querying in the Special Notes field. No response to rejected LSN: A Retailer or DNSP has rejected a previous LSN where it was reasonably expected the Retailer or DNSP would send through a new LSN with updated or correct information that has not been received. Other: only used for scenarios not covered by the specified allowed values. The Retailer or DNSP must provide the details in the Special Notes field. 4. SpecialNotes1 VARCHAR(80) O M Any additional information the Initiator wants to convey to the Recipient. Mandatory if Reason is Other. 5. SpecialNotes2 VARCHAR(80) O None AEMO 2018 MSATS Release Schedule - January

29 Validation No Field Format Use Definition & notes 6. SpecialNotes3 VARCHAR(80) O None 6.2 Life Support Notification validation For more details, see B2B Procedure: Technical Delivery Specification. No Field Format Use Definition & notes 1. NMI CHAR(10) M NMI 2. NMI Checksum CHAR(1) O NMI Checksum 3. SiteAddress ADDRESS O Site Address 4. Reason VARCHAR (14) M Allowable Values: Update Reconciliation 5. RegistrationOwner YESNO M N Value of YES must be used, where the Initiator of the LifeSupportNotification is the Life Support registration process owner. Not required where Status is None. 6. Status VARCHAR (50) M Allowable Values: Registered - No Medical Confirmation Registered - Medical Confirmation Deregistered No Medical Confirmation Deregistered Customer Advice Deregistered No Customer Response None: The premises do not have a current Life Support requirement. AEMO 2018 MSATS Release Schedule - January

30 Validation No Field Format Use Definition & notes 7. DateRequired DATE M N For a registration of Life Support, this date is the date Life Support protections commence at the premises. For a deregistration of Life Support, this date is the date Life Support protection ceases at the premises. For response to a Life Support Request, this is the effective date of the Life Support registration in the participant s system. Not required when Status is None. 8. Equipment VARCHAR(50) R N Allowable values: Oxygen Concentrator Intermittent Peritoneal Dialysis Machine Kidney Dialysis Machine Chronic Positive Airways Pressure Respirator Crigler Najjar Syndrome Phototherapy Equipment Ventilator for Life Support Other: An equipment that a registered medical practitioner certifies is required for a person residing at the customer s premises for life support and is not already listed above. Not required when Status is Deregistered No Medical Confirmation Deregistered Customer Advice Deregistered No Customer Response None Note: Where more than one allowable value is required, select one of the allowable values and provide the additional allowable value in the Special Notes field. AEMO 2018 MSATS Release Schedule - January

31 Validation No Field Format Use Definition & notes 9. LSContactName PERSONNAME R N Must be the name of the person who is the contact for the management of Life Support requirements. Not required when Status is Deregistered No Medical Confirmation Deregistered Customer Advice Deregistered No Customer Response None Contact Details are mandatory if Postal Address is provided. 10. LSPostalAddress ADDRESS R N 11. LSPhoneNumber1 TELEPHONE R N 12. LSPhoneNumber2 TELEPHONE R N Must be the customer s postal address for Life Support requirements. Not required when Status is Deregistered No Medical Confirmation Deregistered Customer Advice Deregistered No Customer Response None Must be the phone number of the person who is the contact for the management of Life Support requirements. Not required when Status is Deregistered No Medical Confirmation Deregistered Customer Advice Deregistered No Customer Response None Must be the phone number of the person who is the contact for the management of Life Support requirements. Not required when Status is Deregistered No Medical Confirmation Deregistered Customer Advice Deregistered No Customer Response None AEMO 2018 MSATS Release Schedule - January

32 Validation No Field Format Use Definition & notes 13. LSContact Address VARCHAR(100) R N Must be the address of the person who is the contact for the management of Life Support requirements where the Initiator has obtained Explicit Informed Consent for the use of the address. Not required when Status is Deregistered No Medical Confirmation Deregistered Customer Advice Deregistered No Customer Response None 14. PreferredContactMethod VARCHAR (20) O Allowable values: Postal Address Site Address Address Phone 15. SpecialNotes1 VARCHAR (80) O M Any additional information the Initiator wants to convey to the Recipient. Mandatory when Equipment is Other 16. SpecialNotes2 VARCHAR (80) O 17. SpecialNotes3 VARCHAR (80) O 18. LastModifiedDateTime DATETIME M Date and time the record was updated in the Initiator s system. 6.3 Special Notes validation LifeSupportRequest Special Note 1 is Required if Reason = OTHER. Special Note 2 and Special Note 3 are optional LifeSupportNotification: Special Note1 is Required if Equipment is OTHER. AEMO 2018 MSATS Release Schedule - January

33 Validation Special Note 2 and Special Note 3 are optional. 6.4 Validation Module software The B2B Validation Module is updated to include the two new transactions for validation before sending them to the B2B e-hub. For help, see Guide to Validation Module Software. At pre-production release time, participants can find a new version of the Validation Module software (ValidationModulev1.1.zip) and the Validation Module Matrix on AEMO s website: The download is a single ZIP file containing the compiled software, supporting libraries and source code: doc lib META-INF PropertiesFiles samples src contains source code build.bat runtest.bat runtesttype2.bat README.txt lists the ZIP file contents and version history 6.5 Validation Module Matrix The Validation Module Matrix is updated to include the two new transactions and their validations. 6.6 B2B Responder The B2B Responder is upgraded to receive B2B transactions in r38. AEMO 2018 MSATS Release Schedule - January

34 Validation 6.7 Recommended parsers AEMO tests the samples on the following parsers: MSXML 4.0 SP1 Xerces Xerces XMLSpy 2004 AEMO 2018 MSATS Release Schedule - January