Greenhouse Management Pilot – Extended Version

Greenhouse Management Pilot – Extended Version


Login Form. The user logs into his private space User location is identified via his IP. A calendar facilitates organization of everyday tasks Important alerts are raised to the user. Suggestions are provided by a built – in expert system Information about the status of the greenhouse Sensors monitoring information. Green: The sensor operates correctly, Red: The sensor malfunctions or reports abnormal values, Grey: The sensor is absent Graphical representation of old values Alternate visualization Visualization of older values per sensor. Big dataset spans 5 days, normal dataset 2 days and mini dataset the last couple of hours. Presentation of billing information (per – service) A dedicated page for browsing and registration of third party, value added services Automatic location identification through IP (default procedure) Manual location identification by the user Manual settings override automatic location. Synchronization across all pages Dedicated page facilitating software upgrade of the local hardware infrastructure A service provider is logging in the portal Registration of a service Billing information provided Registered services ready for consumption. The user can register by clicking the “Register” button A dedicated page appears. The user adds the service anywhere he wants Service Consumption … and after a couple of clicks 5 clicks with 0.1 euro per click sum to 0.5 euros Service Deregistration with a single click The cloud proxy has Internet connectivity and reports everything to the FMS controller Internet connection is down (a cable is unplugged) The controller identifies the problem The cloud proxy stops reporting values. User interface is switched to a bare minimum level of functionalities supported by the low-end device (values, notifications, alerts) Connection is restored. The cloud proxy transmits all data to the cloud A sensor is manually removed from the board Seconds later, the system identifies the problem and reports to the farmer The information is also depicted on the monitoring application The Soil Moisture and the Temperature sensors are attached at the board The board supports the Temperature sensor but not the Soil Moisture one The farmer selects the firmware The upgrade procedure is triggered The portal notifies the user regarding the status of the update process Transmission Transmission finalized Booting the new firmware The sensor starts reporting values. Readings are erroneous because the sensor is dry The user is notified either through the portal or through email … and now , we “fix” the readings of new Soil Moisture (SM) sensor

Leave a Reply

Leave a Reply

Your email address will not be published. Required fields are marked *