-
SCADA Subsystem
-
MDM Subsystem
-
Customer Metering Subsystem
SCADA Subsystem
There are three basic types of meters:
- Pressure meters
- Flow meters
- Ultrasonic meters
Flow meters installed in outlets of tanks provide continuous measurements. In this case power supply is provided. In other cases, in order to speed up installation process and avoid problems with power supply and communication of meters, they equipped with battery pack power supply and communication via SMS/e-mail to SCADA.
Meters send data to SCADA in adjusted time intervals (e.g. 4 hours for main pipes and 12 hours for inlets to distribution network). In this case batteries are enough for 3-5 years of works without maintenance. Clocks of meters are synchronised.
Communication between SCADA and most of meters base on the GSM communication. Throw the GSM SMS or e-mail, current reading of flow meter is transmitted to SCADA. There is also a possibility to send data of continuous measurements to SCADA by MQTT.
The SCADA provide visualization of the state of the meters and equipment being controlled. It enables the user to collect and archive analogue and binary data, control the process and be alerted in case of emergency. It contains tools necessary to analyse the gathered data and generate reports.
MDM Subsystem
MDM Subsystem is provided to meet following requirements:
- Organize all metering data from all sensors into one central database
- Prepare balances of water consumption.
Data processing in MDM is organized into logical business processes (data flows) which can be setup at customization stage according to business requirements. Examples of such processes are:
- Balancing
- Billing of water services
More different processes can be introduced in the future.
Raw metering data can be imported in different formats from many sources (external systems). Adapters allow to use following types of communication:
- Import files from filesystem
- Import files from FTP/FPTs/SFTP servers
- Import data through web service API (Restful or SOAP)
- Load data manually using system graphical user interface
All incoming metering data is validated. System runs validation as continuous tasks basing on streaming or batch processes. Schedule of batch processes are possible to adjust by system user. Validation is divided into 2 main groups:
- Master data compliance validation
- Reading data validation.
System allow to run estimation of missing readings in order to provide all input data to balancing tool. Estimation rules can be assigned to each metering point or group of metering points.
System allow to manually enter readings into the system or change existing values. Values from SCADA should not be changeable as those data are gathered from electronic high reliability sensors and meters.
Proposed IT system allow to store all readings in one database with possibility to browse historical data of metering point. Metering data is available for metering points which are assigned to:
- Households,
- commercial/industrial customers,
- network/technical metering points.
System store information about metering objects. Metering objects are defined as physical devices which can register reading data and logical representations of metering points which are used to secure reading data continuity regardless of physical devices changes. System support object types includes:
- MP – metering point – object where physical or virtual meter is installed,
- MET – meter – end device which measure physical values according to its specification and design.
Calculation of billing determinants is done according to settlement schedule. Settlement schedule is provided from the billing system and should be defined as billing interval and billing phase. The first step of billing data calculation is a calculation of water consumption. Consumption is calculated basing on reading data sequence sorted by reading date as a difference between the readings.
- MP – metering point – object where physical or virtual meter is installed,
- MET – meter – end device which measure physical values according to its specification and design.
MDM Analytics is an extension of basic core MDM Subsystem. This part of the system allow to support following key functions: Balancing and Reporting.
- MP – metering point – object where physical or virtual meter is installed,
- MET – meter – end device which measure physical values according to its specification and design.
Customer Metering Subsystem
The main function of the Subsystem is managing the process of metering data acquisition from all meters which are not connected to SCADA communication network. The process consist following steps:
- Prepare the acquisition routes
- Prepare the reading orders according to reading cycles and reading areas
- Distribute reading orders to data collectors (utility employees)
- Gather reading data from collectors
- Monitor and report acquisition process efficiency.
System is based on meters already installed at customer’s connection points. New meters are installed only for balancing purpose and data from those new meters are acquired using SCADA Subsystem.
System allow to manage utility area by splitting this area into smaller metering data acquisition zones (here and after DAZ). According to reading cycles and reading phases system allow to create reading orders which are defined as list of metering points from selected one or more DAZ to be collected by meter data collectors within provided expected reading date. Created orders are split into smaller packages which will be assigned to available collectors. System support register of reading data collectors register and their work plan to be used in data acquisition planning process.
- Master data compliance validation
- Reading data validation.
The Customer metering subsystem allow to monitor the progress of data collection basing on synchronized reading orders. The system inform the users by visual representation all completed reading orders, all reading orders with incoming due date.
In a case when reader collector add annotation to reading value about detected leakage then proper message is displayed on system console and there should be and option to trigger inspection control. Trigger is sent to Workforce management system which should be responsible for management od field employees who will run further investigation and survey of distribution network.