Swap a water meter and keep the water module

This section explains how to create an MDI file to swap an existing water meter that has an OpenWay Riva Water Module attached to it. The water module will remain and the water meter will be removed and replaced with a new water meter. In this example, the water meter and the water module are installed at the servcie point 'RivaWaterSP1'.

The following XML sample provides the information for the installation of the new meter at the same service point on 2018-06-01T00:00:00 UTC. When the applications load this MDI file they will end the links or update the information for the meter as appropriate. In this XML sample, the Account, Address, Channel, and Device information is not provided since it is assumed to be the same information that was previously uploaded for the meter being replaced.

In the XML file, a new relationship is created between the endpoint and the meter at the time set in the DeviceLinkRange element's Start attribute.

In the field, a new endpoint is installed at the meter location.

Prerequisites

To be successfully installed on a meter in Collection Manager, the water module needs to first be provisioned using the shipping files from the factory. A provisioning file is sent with the water module. This file must be uploaded to tell Collection Manager that water modules contained within that file are now owned by the utility and are ready to be installed. These water modules will exist in the Collection Manager database, but they are not connected to any service points and their status is not active. If an MDI file adding an water module is sent to the Collection Manager before the water module has been added to the Collection Manager via the factory provisioning file, the file will fail to load and will log an error.

Performance Manager and Itron Analytics do not require the OpenWay Riva Water Module to have been pre-provisioned to process the installation MDI.

Source of the MDI file

Customer work order system or FDM work orders
CIS
MDM
For Itron Analytics, the MDI file should always come from OpenWay Operations Center - Collection Manager.

Workflow

Provisioning files are imported into Collection Manager.
The field service representative (FSR) goes to the physical location and programs the ERT module if necessary.
The MDI file is imported into Collection Manager.
Collection Manager automatically sends the MDI file to Itron Analytics using secure FTP.
Collection Manager also send the MDI file data to Performance Manager.
Itron Analytics imports the MDI file. Itron Analytics will report if the file imports successfully or if there are any errors during the import.
Performance Manager imports the MDI file data. Success or failure of the data import will appear in the Performance Manager user interface.

The ERT module will register and start sending data even if the MDI file import is delayed. Collection Manager will collect the data, but because the MDI file has not been imported with the Unit and Decode information, the data will be stored as raw. When the MDI file is imported, Collection Manager will correct the raw data with the Unit and Decode values and will send the corrected data to the Itron Analytics and the MDM.

Related scenarios

The following scenarios are related to installing a water ERT module:

Best practices

When using the MDI file to install ERT modules into the Collection Manager, provision the ERT modules by importing the factory provisioning file before importing the MDI installation file.

Troubleshooting

If you have imported the MDI file into your OpenWay Riva solution and the ERT module is appearing as expected in Performance Manager and Itron Analytics, but is not appearing in Collection Manager, the ERT module provisioning file from the factory may not have been imported first. Make sure the factory provisioning file is imported without errors, then import the MDI file again.

Elements and attributes

For information about the use of special characters, see Special characters.

The following table shows the elements and attributes included in the XML sample.

Required = This element/attribute is required for this specific scenario. It may not be required in other scenarios.
Recommended = Itron recommends that you use this element/attribute in this particular scenario.
Optional = This element/attribute is optional for this scenario and is only required if you want a specific outcome described in the element/attribute definition. To see the element/attribute description, click on the element/attribute in the table or in the XML sample.
Blank = The application does not use this element and any value in it will be ignored.

Element	Attribute/child element	Collection Manager	Performance Manager	Itron Analytics	Operations Optimizer
SetServicePoint		Required	Required	Required	Required
SetServicePoint	ServicePointId	Required	Required	Required	Required
SetMeter		Required: For Collection Manager, you must use one of the following SetMeter attributes: MeterId, MeterNumber, or MeterSerialNumber.It is not necessary to use more than one of these attributes. Whichever attribute you choose to use should be used consistently.	Required	Required	Required
	MeterSize			Required	Required
	MeterType	Optional	Optional	Optional	Optional
	MeterId	Required	Required	Required	Required
	MeterNumber	Required	Required	Required	Required
	MeterSerialNumber	Required	Required	Required.	Required.
	MeterInstallationDate	Optional	Optional	Optional	Optional
	EndpointInstallationDate	Optional	Optional	Optional	Optional
SetChannel		Required		Required	Required
	ChannelNumber	Required		Required. At least one channel must be configured for auto-channel creation. Set the `ChannelNumber` value to `1` when creating a dummy channel. For more information, see Auto-channel creation.	Required. At least one channel must be configured for auto-channel creation. Set the `ChannelNumber` value to `1` when creating a dummy channel. For more information, see Auto-channel creation.
	Unit
	HasIntervalData			Required	Required
SetDevice		Required		Required	Required
SetDevice	DeviceId	Required: In this scenario, this is the new endpoint's ID. the endpoint being removed does not need to be referenced.	Required	Required	Required
DeviceLinkRange		Required if the SetDevice element is included in the file.	Required if the SetDevice element is included in the file.	Required if the SetDevice element is included in the file.	Required if the SetDevice element is included in the file.
	Start	Optional		Optional	Optional
	End	Required if the SetDevice element is included in the file.	Required if the SetDevice element is included in the file.	Required if the SetDevice element is included in the file.	Required if the SetDevice element is included in the file.
MeterLinkRange		Required	Required	Required	Required
	Start
	End	Required	Required	Required	Required

XML sample

<?xml version="1.0" encoding="utf-8"?>
<MasterDataImport
    xmlns:xsd = "http://www.w3.org/2001/XMLSchema"
    xmlns:xsi = "http://www.w3.org/2001/XMLSchema-instance"
    xmlns = "http://www.itron.com/masterdata/2013/03">
    <SetServicePoint
	ServicePointId = "RivaWaterSP1">
	<SetMeter
	    MeterType = "Itron Flostar FLO50F_Version2"
	    MeterSerialNumber = "0BLJAD05403"
	    MeterId = "ItronWaterMeterID1"
	    MeterSize = "55"
	    MeterInstallationDate = "2018-06-01T00:00:00Z"
	    EndpointInstallationDate ="2018-06-01T00:00:00Z">
	    <SetChannel
		ChannelNumber = "1"
		Unit = "CCF"
		HasIntervalData = "True">
		<SetDevice
		    DeviceId = "0BLJAB4502">
		    <DeviceLinkRange
		        Start = "2018-06-01T00:00:00Z"
		        End = "EOT"/>
		</SetDevice>
	    </SetChannel>
	    <MeterLinkRange
		Start = "2018-06-01T00:00:00Z"
		End = "EOT"/>
	</SetMeter>
    </SetServicePoint>
</MasterDataImport>