{{title}}
{{contactOpenText}}
Contact a Customer Care Representative

We’ll get back to you within 24 hours or the following business day.

Prefer to call?
Customer Care representatives are available by phone Monday–Friday, from 9am–5pm CST.

(800) 616–3837

We're here to help
Contact a Customer Care Representative

We’ll get back to you within 24 hours or the following business day.

Prefer to call?
Customer Care representatives are available by phone Monday–Friday, from 9am–5pm CST.

(800) 616–3837

January 11, 2023

5 Important Questions to Ask When Selecting a Meter Data Management (MDM) Solution

Metering data solutions are important investments, so it’s critical that utilities ask the right questions when vetting possible providers. Here are a few important questions utilities should ask a potential provider during the evaluation process.
Person accessing water meter data information on their phone and desktop
The adoption of more advanced metering technologies means more data—and the need to better manage it. Whether a water utility is using automated meter reading (AMR), advanced metering infrastructure (AMI) or a mix of the two, there are solutions that can do much more with metering data than just send bills.

Software as a Service (SaaS) technologies for meter data management (MDM) offer opportunities to do exactly that. But before choosing a provider, utilities first need to understand their options. Here are a few questions utilities should ask a potential provider during the evaluation process:

1. Is the SaaS interoperable with other systems?

There are many ways that a utility can collect its metering data, and the right SaaS should work seamlessly with that technology or method, whether it’s AMR, AMI or a combination of technologies. For small or mid-sized utilities, budgets may be tight—and replacing incompatible meters is expensive. Ensuring that the SaaS system will work with the existing meters and communications network is an essential first step to determining if the solution is right.

2. Does the solution offer more than just water usage data?

The basic premise of MDM is that it can quickly and accurately show water usage data for an endpoint or service area—but it's capable of so much more than just generating bills. Utilities should consider whether the SaaS offers all, or most, of the following:

  • Multiple leak detection processes. The SaaS should offer a variety of ways of detecting leaks. For example, algorithms can use data to detect flows of 1 gallon per hour or more that occur for more than 24 hours. Alternatively, users can be alerted when a particular endpoint has higher than normal usage for an extended period of time. Water utilities should also be able to flag areas with a high risk of leaks, such as those with old pipes or new developments, so that the system can send alerts of sudden upticks in flow rates.
  • Diurnal demand reporting. This helps utilities understand when peak demand occurs and move water accordingly, which saves money and conserves water.
  • District metering areas. The ability to compare supply meters to demand meters serves two key purposes. One is to detect potential areas of non-revenue water (NRW) in the system. The second is to right-size the budget by only sending as much water as needed into different parts of the water system.
  • Reduction goal setting. Utilities that need to reduce water consumption, particularly those in drought-stricken areas, should be able to set reduction goals for regions or endpoints. Users must be able to sort the data to quickly identify areas that have met established goals and those that have not, so that action can be taken accordingly.

3. Can the SaaS solution provide enough data to glean meaningful insights?

Many SaaS solutions offer hourly data displays. This is much more insightful than monthly reads, but it may not show enough granular detail for utilities that need to right-size their revenue or meet conservation goals. Additional data intervals provide more accurate mathematical averages, as well as more precise timelines of flow rate changes. For example, utilities can observe if a change in usage during evening or dinner hours is sudden and abrupt or if it increases gradually.

4. Can the solution make an impact on water reduction and conservation goals?

Nearly all the features mentioned above—from leak detection to reduction goal setting—are key to ensuring that any utility can meet necessary conservation targets. In addition, the right SaaS should allow users to sort or filter by the largest demand endpoints and regions in order to target them for communication or other action.

Water conservation isn’t limited to drought-stricken areas. Many utilities are tasked with reducing water usage for a variety of reasons, including mitigating stress on distribution or wastewater infrastructure. Therefore, any SaaS should have conservation tools that are accessible and meaningful for users in any circumstance.

5. Is the SaaS reliable and secure?

One major concern for many utilities is cybersecurity. As a web-based platform, any SaaS must show that its security features are on par with, or better than, a locally run software solution. For the most part, SaaS providers are highly motivated to ensure they are using the best available security protocols, as a breach could potentially impact any or all of their customers. Teaming with reliable cloud-server partners, such as Amazon Web Services, is one way of demonstrating this commitment.

Metering data solutions are important investments, so it’s critical that utilities ask the right questions when vetting possible providers. Finding a solution that is compatible with the existing technologies and features a comprehensive set of data management tools can help a utility reduce costs and achieve maintenance and conservation goals.

Learn More

We're here to help
Contact a Customer Care Representative

We’ll get back to you within 24 hours or the following business day.

Prefer to call?
Customer Care representatives are available by phone Monday–Friday, from 9am–5pm CST.

(800) 616–3837