This schema file is part of the aseXML schema set, and is subject to the terms and conditions that are detailed in the aseXML_r*.xsd schema file with which this file is used Purpose - Define the contents of the aseXML message header Detail - Every aseXML message carries a header. It is used to indicate information pertaining to the message as a whole. Purpose - Uniquely identify every message generated by the message sender Detail - Note that message identifiers do not have to be globally unique, only unique to a particular sender. However, the length has been chosen such that UUIDs can be used as message identifiers if considered appropriate, guaranteeing global uniqueness. A message acknowledgement identifies which message it is acknowledging by providing the message identifier as an attribute. Purpose - Provide the transaction group to which all the contained transactions or transaction acknowledgments belong Detail - The target application is at liberty to reject any transactions within the message that do not belong to the stated TransactionGroup. Where only message acknowledgements are carried, a transaction group of "MSGS" should be used. The following groups are B2B process related: FLTS - Faults and Outages SORD - Service order, planned works NETB - Network billing MTRD - Meter data CUST - Customer related NOTF - Notifications (broadcast) MKTW - Wholesale market operations HSMD - High Speed Monitoring system OWNP - Own Way Notification Purpose - Provide the processing priority desired by the sender Detail - The sender can indicate their preference in terms of timeliness of processing for the payload. It is left to the discretion of the receiver to determine whether and how to honour the requested priority. Purpose - Provide the processing priority desired by the sender Detail - The sender can indicate information needed by the receiver to determine whether or not the sender is authorised to submit the transactions within the message. For the Market Settlement And Transfer System (MSATS), this will be used to hold the participant userid from which the context for transaction processing is determined. Purpose -Indicate the energy market to which the message belongs Detail - Markets are currently defined for the National Electricity Market, the NSW Gas Market and the Victorian Gas Market. Purpose - Define the contents of the aseXML message header Detail - Every aseXML message carries a header. It is used to indicate information pertaining to the message as a whole. When not provided, a default value of NEM will be assumed for the market.