Intelis Gas Meters

Note: In the following topics, all Intelis Gas Meters are referred to using the general name "Intelis Gas Meters." These include the original Intelis Gas Meter, the Gen5 Intelis Gas Meter, and the Intelis 250 and 425 Gas Meters (which are shown in the FDM user interface as "Intelis Gas OW Riva").

Intelis Gas Meters can operate in a Mobile communication protocol or a Network communication protocol. When in Mobile communication protocol, the endpoint operates like a 100-series endpoint in SCM+ communication standards. When in Network communication protocol, it operates in COSEM communication standards.

The meter will listen for either a ChoiceConnnect (SCM+) signal or for a beacon (COSEM). The signal the meter receives determines the communication protocol in which the endpoint will operate.

Intelis Gas Meters can be configured as having either four or five digits as well as other display configurations. The four or five digit configuration is defined by the configuration file type–either the Intelis Gas 4 digit/dial or the Intelis Gas 5 digit/dial. The other display configurations are properties contained within each configuration. Whether using the 4 digit or 5 digit configuration, the other properties within those configurations are identical, (though their values can differ). For more information, see Intelis Gas Meter Configuration Properties.

The Device Configurations view details screen for an Intelis Gas Meter lets you enable configuration packages, attach one or more configuration packages, attach one or more firmware versions, attach configuration packages containing pre-configured values, and make them available to your business unit.

For completing workflows for meters operating in Network communication protocol, it is necessary to have a configuration package, a configuration file, and a configuration package with pre-configured values uploaded along with the workflow package.

To add an Intelis Gas Meter configuration to a business unit, you must configure its operating parameters and attach the appropriate configuration files, firmware, and preconfigured values to the configuration. The configuration accomplishes the following:

• Saves the FSR from configuring the operating parameters while they are in the field.

Attaching endpoint firmware accomplishes the following:

• Allows the FDM server to send the files to the business unit’s mobile devices during synchronization.

The firmware that is synchronized to the mobile devices is available for FSR selection while completing field work.

You must have Override Business Unit Device Configurations permissions for the applicable business unit to add or modify a device configuration.