DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING
System Design on
Greenhouse Control and Monitoring System using IoT
Submitted by
Arjun S. 1MS13CS031
Nibras Ahmed 1MS13CS070
Kshitij Ch. 1MS13CS058
Bachelor of Engineering in Computer Science & Engineering
[Link] INSTITUTE OF TECHNOLOGY
(Autonomous Institute, Affiliated to VTU)
BANGALORE-560054
2017-2018, [Link],
TABLE OF CONTENTS
Introduction -----------------------------------------------------------------------------------3
PURPOSE -----------------------------------------------------------------------------------3
SYSTEM OVERVIEW ----------------------------------------------------------------------------3
DESIGN CONSTRAINTS ------------------------------------------------------------------------4
ROLES AND RESPONSIBILITIES ---------------------------------------------------------------5
PROJECT REFERENCES ------------------------------------------------------------------------5
SYSTEM ARCHITECTURE ----------------------------------------------------------------------6
DATABASE DESIGN ----------------------------------------------------------------------------7
HARDWARE AND SOFTWARE DETAILED DESIGN--------------------------------------------8
SYSTEM SECURITY AND INTEGRITY CONTROLS --------------------------------------------9
Introduction -----------------------------------------------------------------------------------3
This System Design Document has been created to outline the proposed system design for
Greenhouse Control and Monitoring System (GCMS). The GCMS is intended to replace the
Traditional monitoring system currently used by most of the population and general public.
By designing, testing,and deploying the GCMS, we will improve its capabilities to continuously
monitor the climatic parameters and control the output devices to ease greenhouse management.
This document and the technical specifications listed herein comply with all technical standards
and infrastructure.
PURPOSE -----------------------------------------------------------------------------------3
The purpose of this System Design Document is to provide a description for how the GCMS will
be constructed. The Systems Design Document was created to ensure that the GCMS design
meets the requirements specified in the GCMS project requirements documentation referencing
improvements to existing methodology and tools. The System Design Document provides a
description of the system architecture, software, hardware, database design, and security.
SYSTEM OVERVIEW ----------------------------------------------------------------------------3
The Agriculture and Farming groups have historically faced many challenges and shortcomings
in monitoring and maintenance of metrics, tracking, and reporting. The proposed GCMS tool
will utilize existing infrastructure and hardware to provide an tool which will standardize and
improve the efficiency of Monitoring and control capabilities.
The GCMS tool is also compatible with existing Android software [Link] project will
provide various user interfaces which will allow data entry, updates, monitoring, and control
action generation. It will also allow users to export data to various existing software tools like
MS Excel for various uses. One of the primary benefits of the GCMS tool is its ability to
consolidate all monitored data and generate real-time reports and control actions. Until now we
have relied upon manual monitoring with various data constraints and limited user interfaces
which has resulted in poor reporting, tracking, and management as well as a general lack of
continuity among the users.
The new GCMS tool will provide the following capabilities:
● Pre-designed automated reporting at various time intervals as well as manually generated
reports.
● Integration of all monitored data which allows for real-time data reports and simplifies
management of all maintenance activities.
● Enhanced and additional user interfaces which provide users with much simpler data
monitoring and control.
● Data export capabilities which allow users to export data to various software tools for
simplified reporting and presentation capability.
DESIGN CONSTRAINTS ------------------------------------------------------------------------4
The GCMS Project Team identified several constraints which will impact and limit the design of
the tool. These constraints are beyond the scope of the GCMS Project but must be carefully
factored into the system design. To date, the following constraints have been identified:
● GCMS must be compatible with existing referenced infrastructure to include network
tools and applications, security requirements, server capabilities, and network
management hardware.
● GCMS must comply with all industry regulatory policies and [Link] policies
and guidelines will impact the tool by requiring certain standards of coding, user
interfaces, security, and management of the tool.
● Each individual section has to be unit tested before it is integrated into the final design. A
fully integrated prototype should be built and bench tested to ensure proper functionality
before installation into the greenhouse. The system should perform as designed and
should be able to remotely monitor and control the greenhouses
temperature,humidity,water level and light intensity.
● The GCMS tool must be compatible with existing user software suites. This will require
the team to design and code the GCMS in a manner in which data can be seamlessly
imported and exported between the GCMS and existing software tools.
ROLES AND RESPONSIBILITIES ---------------------------------------------------------------4
The following table defines the MMS System Design roles and responsibilities. This matrix also
serves as the list of points of contact for issues and concerns relating to the GCMS System
Design.
Name(USN) Role Phone email
Arjun S. Research and +91 95 91 073649 arjun.subramanya230@[Link]
(1MS13CS031) Testing
Nibras A. Design and Project +91 77 60 248306 nibras.nizar2311@[Link]
(1MS13CS070) Management
Kshitij C. Testing and Project +91 96 11 232609 kshitijchou@[Link]
(1MS13CS058) Management
PROJECT REFERENCES ------------------------------------------------------------------------5
The GCMS tool is designed in accordance with several organizational guidelines, standards,
analyses, and findings. These references serve as the basis for the requirement of a new
monitoring and control system. The following is a list of references. It should be noted that some
of these documents are periodically updated and if more detailed information is needed, they
should be referred to individually.
● A Model for Smart Agriculture Using IoT | K. A. Patil, N. R. Kale | 2016
[Link]
● Cloud Service Oriented Architecture (CSoA) for Agriculture through Internet of Things
(IoT) and Big Data | Pamidi Srinivasulu, R Venkat, M. Sarath Babu, K Rajesh | 2017
[Link]
● Automation and Monitoring of Greenhouse | Olakunle Elijah, Tharek Abdul Rahman,
Igbafe Orikumhi, Chee Yen Leow and MHD Nour Hindia | 2018
[Link]
● Automated Soil Nutrient Monitoring for Improved Agriculture | Akhil R, Gokul M S,
Sruthi Menon and Lekshmi S Nair | 2018
[Link]
ing_for_Improved_Agriculture
● Remote Sensing and Controlling of Greenhouse Agriculture Parameters based on IoT |
Pallavi S., Jayashree D. Mallapur, Kirankumar Y. Bendigeri | 2017
[Link]
SYSTEM ARCHITECTURE ----------------------------------------------------------------------5
A system architecture is a conceptual model that defines the structure and behaviour of a system,
this project consists of the following components, which when integrated together provides the
system architecture:
➔ Arduino Board
➔ Wireless Connectivity Module (WCM)
➔ Temperature Sensor (LM35)
➔ Humidity Sensor
➔ Water Level Sensor
➔ LDR (Light Dependent Resistor)
➔ 4-Channel Relay Board
➔ Cooler
➔ Light
➔ Sprinkler
➔ Pump
Figure 1: System Architecture
The architecture diagram above shows how the system is modelled. It also gives a detailed idea
on the working procedure of the system. We use various sensors to assist the condition of the
greenhouse and the sensor data obtained is recorded in the Arduino Board which is connected to
the WCM. This data is sent to the smart phone via Internet for continuous monitoring of the
climatic parameters obtained from the sensors. With the help of IOT, we can control the inside
atmosphere of the green house by turning on the output devices by using the android
Application.
DATABASE DESIGN ----------------------------------------------------------------------------6
The GCMS tool will incorporate monitored data into a new enhanced database with additional
capabilities such as searchable and sortable fields and various enhanced reporting functions. The
GCMS database will also have the capability of importing and exporting data from/to MS Office
applications. Structured data stored in the database will be searchable and sortable in order to
meet both automated and manual reporting and control requirements.
HARDWARE AND SOFTWARE DETAILED DESIGN--------------------------------------------7
Hardware :
❏ Arduino - The Arduino Uno is a microcontroller board based on the ATmega328
(datasheet).
● Microcontroller - ATmega328
● Operating Voltage - 5V Input Voltage (recommended) 7-12V
● Input Voltage (limits) 6-20V
● Digital I/O Pins 14 (of which 6 provide PWM output)
● Analog Input Pins 6 DC Current per I/O Pin 40 mA
● DC Current for 3.3V Pin 50 mA
● Flash Memory 32 KB of which 0.5 KB used by bootloader
● SRAM 2 KB EEPROM 1 KB Clock Speed 16 MHz
● Power The Arduino Uno can be powered via the USB connection or with an
external power supply. The power source is selected automatically. External
(non-USB) power can come either from an AC-to-DC adapter (wall-wart) or
battery.
● Memory The Atmega328 has 32 KB of flash memory for storing code (of which
0,5 KB is used for the bootloader); It has also 2 KB of SRAM and 1 KB of
EEPROM (which can be read and written with the EEPROM library)
● Communication The Arduino Uno has a number of facilities for communicating
with a computer, another Arduino, or other microcontrollers. The ATmega328
provides UART TTL (5V) serial communication.
❏ IOT Module (WCM)
❏ Temperature Sensor
❏ Humidity Sensor
❏ Water Level Sensor
❏ LDR
❏ 4 Channel Relay Board
❏ DC Motor
❏ LED Strip
Software:
There are a number of smartphone platforms for developers, such as iOS, Symbian, Android, and
Windows Mobile. The iPhone with the iOS operating system was the first chosen for this
research but rejected because of limitation of Apple on using hardware for programming
especially with the ports related to the Bluetooth. The Apple just allows the commercial program
to communicate via Bluetooth with non-Apple devices based on an agreement. Android has been
chosen in this project since it is easy to customize and open to Work with different hardware
specially IOT.
SYSTEM SECURITY AND INTEGRITY CONTROLS --------------------------------------------9
The GCMS tool design incorporates several security and integrity controls to ensure that the
system and its data are continually protected. This is done through a multi-tiered approach to
ensuring data integrity is achieved through only authorized user functions and assignments.
● The first design consideration is user authorization or permissions. All GCMS users will
be assigned an authorization level and permissions within which they will operate. These
users will be unable to perform any GCMS transactions outside of their assigned areas.
Managers will provide authorization levels and operating boundaries for each of their
assigned users.
● The next design consideration is to establish control points. As the GCMS is a network
tool, firewalls will be placed to partition the functions in each group is able to perform
within the GCMS. The purpose of this is to reinforce assigned work areas, permissions,
and access with physical barriers to prevent any duplication, unintentional changes, or
malicious changes of maintenance data.
● The next design consideration is data backup. If there is extensive damage to a wide
portion of the database due to catastrophic failure, such as a disk crash, the recovery
method restores a past copy of the data such as threshold values that was backed up to
archival storage (typically tape) and reconstructs a more current state by reapplying or
redoing the operations of committed transactions from the backed up log, up to the time
of failure.