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 by the "NMI Data Access" application Detail - The "NMI Discovery" transaction exchange allows searches for NMIs to be conducted. The exchange consists of a NMIDiscoveryRequest and a resulting NMIDiscoveryResponse. The "NMI Standing Data" transaction exchange allows the retrieval of the current data associated with a NMI. The exchange consists of a NMIStandingDataRequest and a resulting NMIStandingDataResponse. Application - NMI Data Access TransactionExchange - NMI Discovery TransactionGroup - NMID Priority - High Purpose - Request a search of the NMI Standing Data Detail - The JurisdictionCode is mandatory as it is used to determine jurisdictional limitations on the types of searches allowed and the maximum number of matching rows returned for any one search. The remaining elements allow for provision of the various search parameters. For electricity, searches are possible on the basis of meter serial number or address or DPID. Application - NMI Data Access TransactionExchange - NMI Discovery TransactionGroup - NMID Priority - High Purpose - Provide the results of a search of the NMI Standing Data Detail - Usage of the NMIStandingData type allows the transaction to carry variable content according to fuel and jurisdictional requirements. At least one Event element must be present in the response to indicate the success or otherwise of the search. Application - NMI Data Access TransactionExchange - NMI Standing Data TransactionGroup - NMID Priority - High Purpose - Request the current standing data for a particular NMI Detail - The checksum should be provided with the NMI. Application - NMI Data Access TransactionExchange - NMI Standing Data TransactionGroup - NMID Priority - High Purpose - Provide the results of a request for the current standing data for a particular NMI Detail - Usage of the NMIStandingData type allows the transaction to carry variable content according to fuel and jurisdictional requirements. At least one Event element must be present in the response to indicate the success or otherwise of the search. Schema - MeterDataManagement