Interreg IVB Numericanal

Size: px

Start display at page:

Download "Interreg IVB Numericanal"

Dayna Clementine Higgins
6 years ago
Views:

Interreg IVB Numericanal WP 4 - Action 12 Design & development of pilot Control Centre in the Netherlands (Eindhoven) 0. Introduction 1. Program of requirements.

1 Interreg IVB Numericanal WP 4 - Action 12 Design & development of pilot Control Centre in the Netherlands (Eindhoven) 0. Introduction 1. Program of requirements. 2. Stakeholders. 3. Project partners. 4. Organisation city of Eindhoven. 5. Feasibility study. 6. Design. 7. Build & Implementation. 8. Management and maintenance.

2 0. Introduction In the Berzob study done by RWS is a.o. proposed to improve the shipment from Veghel to Eindhoven by upgrading the canals.(zuid-willemsvaart, Wilhelminakanaal en Beatrixkanaal) In the future it is allowed for ships on these canals with a length upto 110 m1. The waterbounded companies in Eindhoven expect an increase in cargo throughput in tonnage from now ca tons to tons. Also they promised a modal shift from trucks to ships. The city of Eindhoven manages the Beatrixcanal and wants a secure, safe channel for the users and good administrative processing of shipping. For this reason we developed during this project a Control Centre with APP. 1. Program of requirements.(cc=control center) The CC should be suitable for computer, cell phones and tablet. The CC maintenance, it is assumed that is done by a specialised field assistant on behalf of the area manager. 1. General information waterway users. a. floor plan with channel data, length width-depth-bridge heightsfacilities b Indication nearest hospital, doctor, practices center with phone data and dentist c. Indicate where the garbage e.o. d. Indicate place where one can load water. e. Place for car loading.(see map) 2. Data concerning safety. 1. information about shipping realtime and the expectation when for example a ship passes by a. AIS, speed data. b. thermal cameras, for example at the canoe club, start of the Beatrixcanal and next to the Marina. c. sensors 2. data relating to veilig varen doe je samen.

3 3. Reporting complaints of user channel 1. reporting complaints of various kinds (pollution, damage etc.) under the general number and link to contact form of the municipality of Eindhoven. 2. Link to buitenbeter app 4. reporting work and calamities 1. an administrator places messages/information from various sources on the CC or various administrators (surface water administrator, area managers, etc.). 2. Information about the police or fire department ( diver in the water or other activities in the canal. 3. There should be a calendar with work and activities. 4. Separate reporting calamities with messages to ships. 5. Collecting canal tax With the collection of canaltax by means of the CC, there need to be a port regulation in which the skipper has a bring duty/hailing. This is a normal use in various ports in Netherlands. This regulation for the use of the port should also be placed on the CC. The skipper should at least have the possibility to report, either through the CC or by phone to address details. Notification via the water-bounded companies and/or municipal administrator. Details of SA-ship and cargo are digitally transmitted, processed and invoiced. 6. management & maintenance - Port regulation with rates list. - Contacts companies - Contracts companies - Technical data 7. tourist information -Check whether there is a link with existing information/apps. -Marina and Canoeclub have websites with a lot of information. 2. Stakeholders. Directly involved and APP users:

4 - Waterbounded companies - Freight skippers - Marina - Canoe club - Scouting Indirectly involved: - Rijkswaterstaat - MCA - Vereniging van havenbedrijven - City of Best - Waterschap de Dommel - Schuttevaer 3. Project partners. - CRT Canal and River Trust (leadpartner) - VNF Voies Navigables de France - Gemeente Eijsden-Margraten, Netherlands - Stichting Recreatietoervaart Nederland (SRN), is now Waterrecreatie Nederland. - CETIC Centre d'excellence en Technologies de l'information et de la Communication Belgium - Gemeente Eindhoven, Netherlands 4. Organisation city of Eindhoven. The project is managed by: - Projectleader - Waterway advisor - Technical advisor - Finance controller - Technical designer - Aerea manager - Communication manager When the CC and APP are fully operational the following employees will be involved: - Waterway manager

5 - Area manager - Financial employee - administrators 5. Feasibility study. The program of requirements has been defined and translated in a proof on concept, including UI, in a feasibility study. The purpose of this study is to define the (feasibility of) use cases as well as study the technical feasibility. 5.1 User applications & scenario s Users (non professional) of the canal will use a mobile application or the monitors at the harbor or canoe club Input forms for: Viewing the current usage of the canal by boating, freighters, or canoes Registering canal usage Registering complaints/issues The Area manager will have an addition dashboard for: Viewing the current usage of the canal by boating, freighters, or canoes Registering general information or activities, including time period, location (via interactive map) Defining the way information coming from user registrations on canal usage and complaint registration should be distributed to relevant third parties. Defining the addressees of information about ships entering the canal and observed via AIS Automation & rules: In addition to the dashboard there will be an option to automate an alert to optional traffic signs, based on presence of freighters, their GPS location and direction. Figure 5.1 Illustrates an example of the proof of concept UI. It illustrates the user interface for canal users on a large screen and smartphone, showing generic information as well as presence on the canal of other ships.

6 Figure 5.1 User interface for canal users on a large screen and smartphone 5.2 Information owners & workflows Based on the user applications, information flows have been identified, including owners, the input and output fields. See table 5.1, for an overview. Page Input Source owner Output/action Target owner Remarks Area information overview Area information - quick info Traffic overview - traffic today Traffic overview - detailed traffic overview Calendar - Calendar Overview of other pages. Concise information Input field in admin page Freight: AIS API; Boating and recreation: Input field in app City of Eindhoven City of Eindhoven Freight: Marinetraffic; Boating and recreation: users idem idem Input field in admin page (x3) Area Manager, Jacht, Kano Calendar - Today idem idem Combination of information from other screens Information is visible per zone Three accounts or all through area manager?

7 Report Channel Usage - Your channel usage History from local storage user user Log of your indicated canal usage. Report Channel Usage - Register channel usage freight Input from freight user Mail to area manager City of Eindhoven Report Channel Usage - Register channel usage - boating/recreational Input from boating and recreation user Send complaint - Your history History from local storage user user Log of your complaints Send complaint - Send complaint Input fields in user Mail/text to user and person contacted Area Manager defines actions in dashboard Calendar - (Training schedule) Dashboard field by Kanoclub Kanoclub - AIS API Marinetraffic Mail with ENInumber user Area Manager Rule in admin dashboard Table Information flows, owners, inputs, and outputs 5.3 Technical feasibility The overall system is build on top of the middleware solution of OpenRemote (see figure 5.2). Existing elements are a controller which manages the protocol adapters, message flows between different sensors and user interfaces, and facilitates the messaging services. The messaging service enables the area manager to set rules for notifications, based on different sensor inputs or user inputs (complaints or registration) The user interface applications is build on an HTML5/JS framework enabling responsive designs for smartphones, tablets and kiosk/monitors at harbor and canoe club. For the interaction with the controller, the controller API will be used. Two technical feasibility studies are carried out: - Tracking different ship types. Freight ships can be monitored using AIS. However quality of the signal on the Beatrix canal was very limited, so during the implementation it was decided to install an extra AIS antenna with own software, to increase the reliability - Tracking canoes and pleasure boats is possible via GPS trackers. We have done a brief study on this and tested a few trackers. In the first evaluation we

8 decided that presence of canoes and pleasure boats will be done (for now) by manual registration. The reason is twofold: o Adding digital trackers will create a false sense of safety to freighters if not all ships/canoes carry them. o As we can t enforce the use of trackers at this stage it is safer to communicate clearly to waterway users that they should manually register themselves to be noticed by freighters. Figure 5.2 Technical system set-up Beatrix canal Control Center 6. Design. In the design phase we created: - Design of user interfaces & visual design for end-user applications and area manager - Definition of all points of interest to be visible on map (by City of Eindhoven) - Design database & input forms (registration, complaint, static information) - Design Interactive maps with objects, forms & AIS For the Design for the end-user kiosk we refer to (view with Google Chrome or IE11): This design is made fully responsive, so reducing the browser dimensions will also show the design for smartphones. For the Design of the area manager application see figure 6.1 and 6.2.

9 Figure 6.1 Design of Area manager application: marker management

10 Figure 6.2 Design of Area manager application: regels

11 7. Build & Implementation. We have implemented the following pieces Control Center as a cloud service on a dedicated server within the City of Eindhoven: - Integration of AIS and controller API - Set-up controller API for user applications - Set up of monitoring for controller performance - Implementation workflow rules, automation and messaging service The kiosk user interfaces for canal users at the Marina and Canoe Club, functioning as the user interface for end-users, containing the following elements: - an overview map with an overview of markers (information on POI s, Attention items, Agenda items) - number and type of ships present in the canal, with live data on location of freighters, - reporting on canal usage by pleasure boating, canoes and freighters, - send complaint notification system, including relevant categories The mobile applications for Android and ios, functioning as the mobile user interface for end-users, containing the following elements: an introduction explaining objective and use of the mobile application an overview map with an overview of markers (information on POI s, Attention items, Agenda items) number and type of ships present in the canal, with live data on location of freighters, reporting on canal usage by pleasure boating, canoes and freighters, send complaint notification system, including relevant categories A webserver running the area manager application, linked to the OpenRemote messaging service. The above kiosk user interface and mobile applications will be linked with the back-end controller to enable notifications to the persons registered in the area manager dashboard.

12 8. Management and maintenance. For management and maintenance the following services have been put in place. The area manager has his own dashboard allowing him to change and maintain: - Information markers within the map - Define rules and contacts to define where and when messages related to canal registration or complaints are being send For management and monitoring of the controller and AIS services, the following is in place: - a remote monitoring service, allowing for active alerts in case of system failures - remote access to the controller, allowing remote maintenance and debugging - a service contract for 3 years, for technical maintenance Evaluation of the system by users: - regular reviews will be held with canal users to receive feedback on functionality and user friendliness - updates are planned for the coming 3 years, allowing for changes or additions to the system with the purpose to improve it s functionality

Intergraph Mobile GeoSpatial Products. Bradley Skelton

Intergraph Mobile GeoSpatial Products Bradley Skelton The Mobile Revolution Everyone has a mobile or tablet device People always have their mobile device with them Mobile market growing exponentially People