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 "Customer Transfer" application Detail - The use of the term customer is somewhat incorrect in that no customer data is manipulated by these transactions. Rather, they are intended to manipulate the standing data associated with NMIs, and allow the necessary changes to be performed when a cusmoter transfers. The heart of these transactions is the NMIStandingData definition. The structure is entirely optional, allowing application level logic to decide what elements need to appear according to the transaction context. At the same time, the schema does say WHERE a given data item should appear if it is to be provided, and WHAT should be provided in terms of data format. Because the NMIStandingData definition declares it to be abstract, derived definitions must be generated for each fuel type. Transaction instances must indicate, via the use of the xsi:type attribute, the fuel specific structure being provided. The "CATS Change Request" transaction exchange allows the updating of a portion of the standing data. The exchange consists of a CATSChangeRequest and a resulting CATSChangeResponse. The "CATS Change Request Withdrawal" transaction exchange allows the withdrawal of a previously submitted change request. It consists of a CATSChangeWithdrawal, with the acknowledgement carrying the success or otherwise of the request. The "CATS Objection Request" transaction exchange allows the lodgement of an objection to a chnage request. The exchange consists of a CATSObjectionRequest and a resulting CATSObjectionResponse. The "CATS Objection Withdrawal" transaction exchange allows the withdrawal of a previously submitted objection. It consists of a CATSObjectionWithdrawal, with the acknowledgement carrying the success or otherwise of the request. The "CATS Notification" transaction exchange provides notification of a change of state of a change request or an objection submission or withdrawal against a change request. It consists of a CATSNotification transaction. The "CATS Data Request" transaction exchange allows the repository of NMI standing data to request aarbitrary subset of the data for a NMI. It consists of a CATSDataRequest. Depending on the task to be performed, multiple transaction exchanges will be necessary for its completion. For instance, multiple notification transaction exchanges will occur wth interested parties each type a change request changes state. Similarly, a data request will trigger a separate change request, that will actually provide the requested data to the NMI standing data repository. Purpose - Uniquely identify each change request MSATS Data Model Column - RequestD Purpose - Identify the type of change request MSATS Data Model Column - CRCode Detail - The change request is the key piece of information in a change request. It drives the logic to determine what other data items are required and the extent of involvement of other parties as the request is processed. Purpose - Describe the types of change request MSATS Data Model Column - CRDesc Detail - The description is intended to assist in identification of the correct type. The mapping between codee and descriptions will be provided to participants via the Table Replication transaction exchanges. Purpose - Identify the current status of a change request MSATS Data Model Column - CRStatusCode Detail - Each status represents a particular point in the lifecycle of a change request. Purpose - Describe a change request type MSATS Data Model Column - CRStatusDesc Detail - The description is intended to assist in identification of the correct code. The mapping between codes and descriptions will be provided to participants via the Table Replication transaction exchanges. Purpose - indicate the type of meter read desired for the chnage request MSATS Data Model Column - ReadTypeCode Detail - This field provides information to the meter data provider as to the type of read required for a change request, e.g. estimated read or next scheduled read. It should not be confused with the ReadTypeCode included in the meter register data. Purpose - Describe a change request read type code MSATS Data Model Column - ReadTypeDesc Detail - The description is intended to assist in identification of the correct code. The mapping between codes and descriptions will be provided to participants via the Table Replication transaction exchanges. Purpose - Uniquely identify each objection MSATS Data Model Column - ObjectionID Purpose - Indicate the reason for objecting to a change request MSATS Data Model Column - ObjectionCode Purpose - Describe the reason for objecting to a change request MSATS Data Model Column - ObjectionDesc Detail - The description is intended to assist in identification of the correct code. The mapping between codes and descriptions will be provided to participants via the Table Replication transaction exchanges. Purpose - indicate on a notification whether an objection is raised or withdrawn. MSATS Data Model Column - ObjectionAction Purpose - Indicates of the the role is currently being played (C) or is proposed to be played (N). MSATS Data Model Column - RoleStatus Purpose - Maximum number of business days permitted in the objection logging period MSATS Data Model Column - ObjLogPeriod Purpose - Maximum number of business days permitted in the objection clearance period MSATS Data Model Column - ObjClearPeriod Purpose - Maximum number of business days that must elapse after the proposed change date if no actual change date supplied before retailers should be notified MSATS Data Model Column - NotificationPeriod Purpose - Maximum number of business days in the past for which a retrospective change may occur MSATS Data Model Column - RetrospectiveDays Purpose - Maximum number of business days into the future for a proposed or actual change date MSATS Data Model Column - ProspectiveDays Purpose - Internal code used to identify trasnactions within the various rule tables that are used to validate transactions MSATS Data Model Column - TransTypeCode MSATS Data Model Column - TransTypeDesc Purpose - Used as part of change request validation to determine what requirements are to be placed on data fields for completion of the change request MSATS Data Model Column - DataSourceCode MSATS Data Model Column - DataSourceDesc Purpose - Data provided via a change request Purpose - Data provided on a notification with respect to a change request Purpose - Data provided via an objection Purpose - Data provided on a notification with respect to an objection Application - Customer Transfer TransactionExchange - CATS Change Request TransactionGroup - CATS Priority - Medium Purpose - Submit a change request Application - Customer Transfer TransactionExchange - CATS Change Request TransactionGroup - CATS Priority - Medium Purpose - Provide the results of submitting a change request Detail - The primary purpose of this response transaction is to provide the unique identifier allocated by the system to the request. At least one Event element must be present in the response to indicate the success or otherwise of the change request. Application - Customer Transfer TransactionExchange - CATS Change Request Withdrawal TransactionGroup - CATS Priority - Medium Purpose - Withdraw a change request Application - Customer Transfer TransactionExchange - CATS Objection Request TransactionGroup - CATS Priority - Medium Purpose - Submit a objection request Application - Customer Transfer TransactionExchange - CATS Objection Request TransactionGroup - CATS Priority - Medium Purpose - Provide the results of submitting an objection request Detail - The primary purpose of this response transaction is to provide the unique identifier allocated by the system to the objection. At least one Event element must be present in the response to indicate the success or otherwise of the objection request. Application - Customer Transfer TransactionExchange - CATS Objection Withdrawal TransactionGroup - CATS Priority - Medium Purpose - Withdraw an objection request Detail - Logically, all that is needed here is the objectionID much as all that is provided to withdraw a change request is the requestID. The remaining fields are purely for cross-validation that the correct objectionID has been provided, and exist purely because of the structure of the MSATS functional specification. Application - Customer Transfer TransactionExchange - CATS Notification TransactionGroup - CATS Priority - Medium Purpose - Provide details of an accepted change request or objection This is what the Jurisdiction code would be after CR completes (if the jurisdiction code is being changed in the CR) This is what the NMI Classification code would be after CR completes (if the NMI Classification code is being changed in the CR) Will be populated only in notifications of CRs which are for transfer of de-energised NMIs. This would be the current value of the NMI Classification code. It could be different than what the NMI Classification code would be after CR completes (if the NMI Classification code is also being changed in the CR - which currently is not allowed in tranfer CRs) Application - Customer Transfer TransactionExchange - CATS Data Request TransactionGroup - CATS Priority - Medium Purpose - Request the provision of a subset of the standing data for a NMI