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 transaction exchanges needed for delivery of meter data Details - The "Meter Data Delivery" transaction exchange allows interval and consumption meter data and profile shapes to be provided. It consists of a MeterDataNotification transaction and a resulting MeterDataResponse transaction. The "Settlement Data Delivery" transaction exchange provides information to the Market Settlement process. It consists of SettlementDataNotification transaction, with no response transactions. Purpose - Identify the submission of meter data via a MeterDataNotification transaction Detail - This identifier is assigned via MDM to each block of data provided via a MeterDataNotification transaction. This is a method of grouping meters that belong to either one end-use customer (NMI), one Builder via all portable meters being defined as belonging to one Site (the builders address even though these meters are temporarily installed at building sites), or finally for a large company (eg Water Corp) by grouping all the Meters into one or more Routes (Route ID). Values used by WA market are NMI, SITE or ROUTE. This element is used to define the ID associated with the Meter Reading Group Type. Schema - MeterDataManagement Schema - MeterDataManagement Schema - MeterDataManagement Schema - MeterDataManagement Schema - MeterDataManagement Schema - MeterDataManagement Schema - MeterDataManagement Application - Meter Data Management TransactionExchange - Meter Data Delivery TransactionGroup - MDMT for VicGas and SAWA Gas Priority - Low Purpose - Provide meter data Detail - Only one type of meter data can be delivered within a given transaction. Transaction Group: MTRD NEM - B2B Electricity National Electricity B2B Process Tranche 1 Build Pack; Only CSVConsumptionData and CSVIntervalData used. Purpose - Deliver consumption meter data (also called basic meter data). Detail - The following column headings will be employed in the default order as listed for each energy market. NEM NMI - 10 characters Suffix - 2 characters MDPVersionDate - YYYYMMDDHHMMSS FromDate - YYYYMMDD ToDate - YYYYMMDD Status - A or E Reading - in kiloWattHours, no leading/trailing zeros VICGAS NMI NMI_Checksum RB_Reference_Number Reason_For_Special_Read Gas_Meter_Number Gas_Meter_Units Previous_Index_Value Previous_Read_Date Current_Index_Value Current_Read_Date Volume_Flow Average_Heating_Value Pressure_Correction_Factor Consumed_Energy Type_of_Read Estimation_Substitution_Type Estimation_Substitution_Reason_Code Meter_Status Next_Scheduled_Read_Date Hi_Low_Failure Meter_Capacity_Failure Adjustment_Reason_Code Energy_Calculation_Date_Stamp Energy_Calculation_Time_Stamp For further details on VICGAS requirements refer to VENCorp Participant Build Pack 3 B2B ELECTRICITY Contains embedded data in CSV format for basic meters. This is the standard file format for basic meter data defined in a valid MDFF. Purpose - Deliver interval meter data Detail - The following column headings will be employed in the default order as listed for each energy market. NEM NMI - 10 characters Suffix - 2 characters MDPVersionDate - YYYYMMDDHHMMSS SettlementDate - YYYYMMDD Status - 48 characters, 1 per interval, A or E Period01 - in kiloWattHours, no leading/trailing zeros Period02 - in kiloWattHours, no leading/trailing zeros ... Period48 - in kiloWattHours, no leading/trailing zeros. B2B ELECTRICITY Contains embedded data in CSV format for interval meters. This is the standard file format for interval meter data defined in a valid MDFF. Purpose - Deliver profile shape data Detail - The following column headings will be employed in the default order listed for each energy market. NEM ProfileName - as per MDM MDPVersionDate - YYYYMMDDHHMMSS SettlementDate - YYYYMMDD Period01- in kiloWattHours, no leading/trailing zeros Period02 - in kiloWattHours, no leading/trailing zeros ... Period48 - in kiloWattHours, no leading/trailing zeros Application - Meter Data Management TransactionExchange - Meter Data Delivery TransactionGroup - MDMT Priority - Low Purpose - Provide acknowledgment of the loading of meter data into MDM Detail - Any errors are reported via Event elements. Application - Meter Data Management TransactionExchange - Settlement Data Delivery TransactionGroup - MDMT Priority - Low Purpose - Provide settlement data Detail - Only one type of settlement data can be delivered within a given transaction. Purpose - Deliver aggregated settlement data Detail - The following column headings will be employed in the default order listed for each energy market. NEM TNI - as per MDM FRMP - as per MDM LR - as per MDM MDP - as per MDM SettlementDate - YYYYMMDD Period01- in kiloWattHours, no leading/trailing zeros Period02 - in kiloWattHours, no leading/trailing zeros ... Period48 - in kiloWattHours, no leading/trailing zeros Purpose - Deliver non-aggregated settlement data Details - The following column headings will be employed in the default order listed for each energy market. NEM TNI - as per MDM FRMP - as per MDM LR - as per MDM MDP - as per MDM NMI - 10 characters Suffix - 2 characters SettlementDate - YYYYMMDD Period01- in kiloWattHours, no leading/trailing zeros Period02 - in kiloWattHours, no leading/trailing zeros ... Period48 - in kiloWattHours, no leading/trailing zeros For a given Reading Group Type (NMI, Site or Route), this transaction is used by an external system to request details of the meters related to the group id, such that an external system can accept meter readings and perform basic validation before submission to the Meter Reading System.