GeoSistema de apoyo para el

emplazamiento del sistema i-flow

GeoSystem support for the location

the i-flow networkthe i-flow network

Txingudiko Zerbitzuak

Servicios Txingudi

Agenda

o ERLEA model

o I-flow system

o Geosystem support for the location

the i-flow networkthe i-flow network

• Network topology

• Workflow

• Tools

• Network Creator

• GeoStreet for ArcGIS

• Network Manager

IKOR METERING

IFLOW SYSTEM

SMART METERING SOLUTIONS FOR WATER & GAS METERS

• AMI wireless Solution.

• ZIGBEE wireless technology.

• Fixed Network, two-way and sincronous

transmission.

• Universal System. Technology for different meters.

• Comprises, Reading Modules, Collectors and

Gateways.

• Different IT Tools for Data Capturing and Monitoring.

IKOR METERING

IFLOW SYSTEM

• MESH network, very flexible and

adaptable to different scenarios.

• Dymanic routing

• Multihop capability

• Free Frecuency Band 2,4Ghz.

• Storage capability in all devices.

• Mechanisms to guarantee 100% of

the data.

• Two-way communication.

IKOR METERING

IFLOW SYSTEM Gateway

• GPRS

• Up to 12 collectors

• Up to 900 modulesModules

• Zigbee

• Battery powered

• Universal concept

ColLector

• Zigbee

• Battery powered

• Up to 90 modules

GeoSystem support

for the location the i-

flow networkflow network

Network topology

Gateway

Group 1

Group 3

Group 2 Group 5

Group 6

Group 7

�Number of groups per gateway: 7

�Distances between collectors:

Group 4

Sensor 1

Sensor 2 Sensor 3

Sensor 4 Sensor 5

Collector 6

�in line of sight: 200 m

�without line of sight: 40 m

�Distances between sensors:

�In line of sight: 100 m

�Without line of sight: 30 m

�Maximum customers:

�by collector: 50

�by gateway: 300

ToolsTasks

Workflow

Automatic pre-location

Fixed network

Review location

Input Data

Network Creator

GeoStreet for ArcGIS

Input data

Review location

(without going outside)

updating and checking

network model

SAREA

GeoStreet for ArcGIS

Network Manager

ArcMap

GeoSystem has three tools:

o Network Creator: ArcGIS Desktop Plugin that allows us to realize an

automatic location of devices (sensors, collectors and gateways)

considering a number of prerequisites.

GeoStreet for ArcGIS: ArcGIS Desktop Plugin to check the location of the

Tools

o GeoStreet for ArcGIS: ArcGIS Desktop Plugin to check the location of the

network without going outside, by using 360° images (GM2).

o Network Manager: to define the fixed network, through updating groups

of sensors and collectors, and even the position of these.

The Network Creator requires the following input information:

o Potential customers

Input information

Network Creator

o Rush

o Counters, buildings, house numbers

Preliminary requirements

Setting

�Distances between sensors:

�In line of sight: 100 m

�Without line of sight: 30 m

�Distances between collectors:�Distances between collectors:

�in line of sight: 200 m

�without line of sight: 40 m

�Maximum customers:

�by collector: 50

�by gateway: 300

�Number of groups per gateway: 7

Initial checking

Checking input data

Initial phase: determination of the locations of the sensors in

the facade.

Warning signs indicate that these

steps have already been executed and

the program will remove this data (if

you ticked)

Location of sensors

At the end of the process displays a

message indicating that the process

ended (with or without errors) for

each of the parties

Note: The user should review and relocate those sensors that the process did not find a

location in facade (Class: SENSOR_SIN_FACHADA).

• Contadores_Ubicacion (counters_location): "View" that determines the

location of the counters: inside or outside.

• ClientesPo (potential customers): View with potential customers by house

numbers, with the location of their counters.

• Clientes_Acometida (customer_rush): Gets the customers that are on the

beginning or end of a rush.

Location of sensors II

• Preparar edificios (make_buildings): Gets the external facades of buildings

to locate the sensors in them. You also get what will be the class

"edificios_interseccion" which will be later used to determine the visibility

between network elements.

• Ubicar clientes en fachada (customers in facade): Gets the intersections of

the rush of customers (Clientes_Acometida) with facades.

To group up of sensors,

Grouping sensors

Warning signs indicate that these

steps have already been executed and

the program will remove this data (if

you ticked)

At the end of the process displays a

message indicating that the process

ended (with or without errors) for

each of the parties

Grouping sensors: to determine groups of sensors considering

the values established in the setting.

Grouping sensors II

Set Collectors & Gateways: Determines which sensor of the

group becomes a collector and groups up the sensors to define

which of them is associated to a particular Gateway.

Results

Once the pre-automatic location of fixed network is

established, this tool is used to validate its location

in the terrain without going outside.

GeoStreet

Plugin that displays 360° images in ArcMap.

GeoStreet

GeoStreet

GeoStreet

Check distances and values used in the calculations:

Setting

Network manager

�Distances between sensors:

�In line of sight: 100 m

�Without line of sight: 30 m

�Distances between collectors:�Distances between collectors:

�in line of sight: 200 m

�without line of sight: 40 m

�Maximum customers:

�by collector: 50

�by gateway: 300

�Number of groups per gateway: 7

It initializes the fixed network allowing us to define groups of

sensors and to asign collectors and gateways to the groups.

Network initialize

It allow us to create group of sensor and to asign the gateway to

the group

Grouping sensors

It makes the following checks:

1. Check the connectivity between the sensor marked as

collector and the gateway (or one of its collectors).

2. Check the number of customers of the gateway considering

the new set of sensors.

3. Check the number of collectors of the gateway.

Grouping sensors II

4. Check the number of customers in the group of sensors.

5. Specifies whether you can access from the sensor

corresponding to at least one other sensors in the group,

taking into account the distances defined in the

configuration.

6. Indicates whether the entire group was validated or not.

7. Allows the user to select a sensor (on the map) to be added

8. to the list.

It allows us to check gateways and collectors.

Data checking