Business Requirement Document -Florja – V1 – Sprint1

Business Requirements Document (BRD)

Florja AI
March 2021
Version 2

Date Version Document Changes

 Number
24/03/2021 1 Initial Draft (Vaibhav Agarwal, Project Manager, Cloud Certitude)
30/03/2021 2 Revised Draft (Vaibhav Agarwal, Project Manager, Cloud Certitude)

1 Approvals
Role Name Title Signature Date
Project Sponsor

Business Owner

Project Manager
 Business Requirement Document -Florja – V1 – Sprint1

2 Introduction
2.1 Project Summary
2.1.1 Objectives
Develop an Intelligent Plant Management Tool that will provide end-to-end solution for
horticultural and agricultural organizations to benefit from technical capabilities of IOT, AI/ML.
To integrate suitable sensors, external Data sources, existing systems. The App is going to be
quite easy to use from smart phone, tablet, and desktop.
 AWS platform to be used for IOT and development purposes.
 Sensor Integration and Management.
 External data integration
 All data archival
 Multi-tenant Users
 Objects: Plants, Irrigation Units, Sensors
 AI integration
 Analytics: Dashboards, reports, warnings
 CRM activities: B2B, B2C, Support, Contact
 Social: Pictures, videos

2.1.2 Current State

The current application is developed on SFDC platform leveraging customized data model and
API’s. Current System has following items in scope for further enhancements:
1. Higher retention cost of SFDC Infrastructure.
2. Static single long form for multiple sensors, many of which fields are not usable for one type
of sensors. UI/UX for rest of the modules can also be more dynamic.
3. Multi-Tenant users not available.
4. A lot of manual work that can be automated.
5. Limitations of AI/ML capabilities in SFDC.
2.1.3 Business Drivers
Regardless of farm size, farmers need to grow healthier, more productive plants. They face
increasing pressures from climate change, soil erosion and biodiversity loss, and from
consumers’ changing tastes in food and concerns about how it is produced.
Smart farming practices are accelerating innovation in agriculture as we all move towards a
more sustainable future. From healthy soil to better vegetables on the shelf, from farmers’
incomes to fair corporate practices, Florja work can bring positive change to people’s lives.
 Farmers are looking for better ways to grow their crops and sit peacefully when technology is taking
care of their farms.
 Industries requires to monitor the farms they have invested in and take appropriate actions when
required. Florja enables them to track the farms’ status, future warnings by utilizing the latest
technologies.
 Clients requires a scalable solution to track the farms with options to add multiple users to take
actions on respective farms.
 Using past data, we can predict the future instances that will help reduce the damages that can
occur. Thus, increasing the production.

2.2 Project Scope

The below points contain the overall project scope. Any point can be related to multiple pages.
The descriptions of these points are expanded in the pages in separate sections below:
1. Platform transition from SFDC to AWS.
2. Application rewrite with UI/UX Improvement
3. Multi-Tenant System Management
4. Sensor Management (Onboarding, Offboarding, Controls, Rule Engine etc.)
5. Irrigation Management (Onboarding, Offboarding, Controls, Rule Engine etc.)
6. Plant Management (Onboarding, Offboarding, Controls, Rule Engine etc.)
7. Graphs - Basic and Advanced Analytics
8. Automations (Rule Engine) & AI/ML
9. Mobile apps: Android and iOS
10. Notifications
11. Multiple Languages

2.2.1 Platform Transition from SFDC to AWS

Following product stack of AWS can provide complete solution for given scope of application.
1. AWS S3 Bucket: AWS s3 will be used for all kinds of data storage (code to be deployed to some DNS
or related things to be saved).
2. AWS API Endpoint and Gateway: This module will be used for communication from and to backend,
also to store in data base.
3. AWS MongoDB Atlas: Used for backend, MongoDB Atlas clusters scale-out and can span multiple
geographic regions with control over data sovereignty.
4. AWS lambda Functions: It is compute service that lets you run scalable code without provisioning or
managing servers. It runs your code only when needed and pay only when it runs.
5. AWS Relational Database Service (RDS): It allows us to set up, operate, and scale a relational
database in the cloud. It provides cost-efficient and resizable capacity while automating time-consuming
administration tasks.
6. AWS IoT Core: AWS IoT Core will let us connect IoT devices to the AWS cloud without the need to
provision or manage servers.
7. AWS IoT Analytics: AWS IoT Analytics will allow us to run and operationalize sophisticated analytics
on massive volumes of IoT data.
8. AWS Sagemaker: Amazon SageMaker will help us to prepare, build, train, and deploy machine
learning (ML) models that will be used to forecast data.
2.2.2 Application rewrite with UI/UX Improvement
1. Login Page/Signup

2. Home Page - Different for SuperAdmin/Tenant/User/Academia?

a. All sensors Summary
b. Graphs
c. Sensors Location
d. Current Irrigation Status
3. Super-admin - Tenant Management Page

4. Super-admin - Academia Management Page

5. Tenant - User management Page

6. User - Profile Page

7. Measurements Page
a. Edit/Delete Measurement
 b. Measurement Detail Page

8. Sensors Page
a. Add / Edit /Delete Sensor
b. Sensor Detail Page

9. Plants Page
a. Add/Edit/Delete Plant Detail
b. Plant Detail Page
10. Irrigation Page
a. Add/Edit/Delete Irrigation Unit
b. Irrigation Detail Page
c. Edit/Delete Irrigation Measurements
d. Irrigation Measurement Detail Page
e. Irrigation Status Page

11. Advanced Visualization (New)

a. Forecasting Graphs
b. Insights
12. Automation (New)
a. Toggle Automation actions
b. Define steps to be automated and criteria

13. Notification Management

a. Plant Care
b. Sensors
c. Irrigation Unit
d. Others
14. Social Page (Need to clarify)
a. Post farm pics, videos
b. Integrate social platform like FB, Instagram Twitter
c. Tenant - User messaging

15. Contact Page

a. Emergency Contact
b. General Contact form
 (The UI images are for reference purpose only. These will be upgraded as per requirement.)

2.2.3 Multi-Tenant System

 Super-admin: All options, Add Tenants, Tenant Management
 Tenants: All options available, Add users, Users Management
 Users: Options related to access provided
 Academicians

2.2.4 Sensors
There are currently four types of sensors used in the system, but future system should be ready to
handle more standard sensors.
 Moist Sensor
 Water Meter Sensor
 GPS Sensor
 Weather Station Sensor
(Please refer Sensor Actions document for details)

2.2.5 Irrigation Unit - Actions

Following actions are performed at Irrigation Unit for the irrigation:
 Basic Actions
 Black-Out Timers
 Quick Black-Out
 Scheduling Irrigation
 Dry Alarm Irrigation
 Ad hoc Irrigation
 Intelligent Field Irrigation
(Please refer Actions at Irrigation Unit document for details)

2.2.6 Graphs
The List of Graphs at multiple places:
 Homepage: Historical data line graphs
  Sensors Current Data Graphs

2.2.7 Automations - AI/ML

 Automated Irrigation actions based on sensors data
 Forecast sensors data based on historical data
 Check Device Status and notify in case of wrong status (Online - Offline)
 Recommendations

2.2.8 Mobile Apps

Develop Mobile apps for two platforms:
 iOS
 Android

2.2.9 Notifications
The automated Notifications to be included are as follows:
 New Measurement Added
 Device Status goes online or offline
 User has used an action button on irrigation unit.
 Someone has posted in social group.

2.2.10 Languages
The web and mobile apps must be in total of six languages as follows:
 English
 German
 Dutch
 Italian
 Spanish
 French

Base language of Application would be English and machine translation tool (Google Translator or
similar) would be used to show application UI in other required languages.

2.3 System Perspective

Few Assumptions and risks for the project:

2.3.1 Assumptions
 Sensors/Irrigation units dummy API would be available for testing during development.
 Current system is fully working end to end. (With obvious limitations)

2.3.2 Risks

3 Business Process Overview
We will be following the below business process for the whole development of the system. The process can be
modified in between development after consideration from all authorial members. The process is described
below.
1. Florja will be able to do CRUD operations for Tenant and Universities.
2. The data to be exposed to universities is managed by Florja.
3. A tenant can do CRUD operations on Users. Also, can directly manage Plant and take actions.
4. A user can do CRUD operations on Plants and its relevant devices and parameters.
The process overview of automation and data forecasting is shown in the diagram below. This section is
proposed plan. The process can be modified in between development after consideration from all authorial
members. The process is described below.
1. The Sensors generate the data as measurements.
2. The data is sent to the AI. The AI has some user’s pre-defined criteria of when to act. The AI will also
recommend users on criteria. (AI model can be defined on large historical data. If lack of data, then
rule based AI will run and model will be created when large data is accumulated.)
3. The AI also learns from the criteria defined by multiple users and starts recommending the criteria to
other users.
4. The AI then calls action on the irrigation unit and sends notification to relevant users.
5. The sensor data is sent to Analytics unit where it runs understands the data and plots it.
6. The Analytics data is further sent to Forecasting Engine running on Machine Learning Algorithms. This
generated data is then sent to UI for plotting and presenting.
7. The data and actions history are saved, and automated reports are sent to users weekly or monthly
as required.
4 Business Requirements
The requirements in this document are prioritized as follows:

Value Rating Description

1 Critical This requirement is critical to the success of the project. The project will not be possible without this requirement.
2 High This requirement is high priority, but the project can be implemented at a bare minimum without this requirement.
3 Medium This requirement is somewhat important, as it provides some value, but the project can proceed without it.
4 Low This is a low priority requirement, or a “nice to have” feature, if time and cost allow it.
5 Future This requirement is out of scope for this project and has been included here for a possible future release.

4.1 Functional Requirements

Req# Priority Description Rationale

General / Base Functionality

Makes the system easily scalable and utilize AWS advanced

FR-G-001 1 The complete platform on AWS.
technologies.

FR-G-002 1 Sensors/Irrigation Unit IOT connections For real-time connection and data

FR-G-003 1 Login/Signup Page Basic

Home Page - Different for SuperAdmin/Tenant/User/Academia as they have

different logins and different purposes.
 All sensors Summary
FR-G-004 1  Graphs
 Sensors Location
 Current Irrigation Status
 Req# Priority Description Rationale

FR-G-005 1 Super-admin - Tenant Management Page To manage the companies login and help from backend.

FR-G-006 1 Super-admin - Academia Management Page To manage University links and access to data.

FR-G-007 1 Tenant - User management Page For Companies to manage Users.

FR-G-008 1 User - Profile Page For user to update personal information.

Measurements Page All the data from sensor is first updated in this page and regulated.
FR-G-009 1  Edit/Delete Measurement
 Measurement Detail Page

Sensors Page For sensors CRUD operations

FR-G-010 1  Add / Edit /Delete Sensor
 Sensor Detail Page

Plants Page For plants CRUD operations

FR-G-011 1  Add/Edit/Delete Plant Detail
 Plant Detail Page

Irrigation Page For irrigation units CRUD operations

 Add/Edit/Delete Irrigation Unit
FR-G-012 1  Irrigation Detail Page
 Edit/Delete Irrigation Measurements
 Irrigation Measurement Detail Page
 Irrigation Status Page

FR-G-013 1 Advanced Visualization (New) For relevant analytical graphs made from both real time and
forecasted data.
 Forecasting Graphs
 Req# Priority Description Rationale

 Insights

Automation (New) To automate the manual actions in irrigation units. And

recommendations to users.
FR-G-015 1  Toggle Automation actions
 Define steps to be automated and
criteria

Notification Management To manage the points of notifications and on which devices those
are required.
 Plant Care
FR-G-016 1  Sensors
 Irrigation Unit
 Others

Social Page For users and tenant to interact. And post the photos and videos to
internal and external social media.
 Post farm pics, videos
FR-G-017 1  Integrate social platform like FB,
Instagram Twitter
 Tenant - User messaging

Contact Page For emergency or general queries

FR-G-018 1  Emergency Contact
 General Contact form

FR-G-019 1 Implementing Business Rules The inter-relation of data and actions.

FR-G-020 1 Developing Mobile apps For information and actions on the go.

Multiple Language Support (English + 5 Required as to be released in multiple countries.

FR-G-021 1
More)
 Req# Priority Description Rationale

Security Requirements

Only admin can add/manage Tenant. And Florja will not have any power over functions of a company.
FR-S-001 1 alter plant/sensor or other relevant details or
take any action.

The Tenant can add/manage user. The The tenant(company) will have all power over all operations.
FR-S-002 1 Tenant can view and do all operations as
User.

The User can add/manage plants, sensors, A User can add plants and manage those.
FR-S-003 1
irrigation unit and perform actions.

FR-S-004 1 Only admin can add/manage Academia. The Academia can only view and download data.

Reporting Requirements

The system shall generate automated To record and keep stakeholders updated.
FR-R-001 2
daily/weekly/monthly Reports.

Usability Requirements

User interface for the Florja shall be For better user experience.
FR-U-001 1 responsive, allowing for proper display on
tablet, laptop, and desktop devices.

Audit Requirements

Any action taken by a user or tenant shall be History of actions to be recorded for audit purposes.
FR-A-001 1
appended with ID and date/time stamp.
4.2 Non-Functional Requirements

ID Requirement

NFR-001 The Florja platform shall accommodate N users concurrently and able to scale up as and when required.

NFR-002 Browser compatibility – Chrome, Safari, Firefox, Edge and all leading web browsers.

NFR-003 Data Performance – Data from sensor cloud to AWS in N ms. Data from AWS to UI in N ms. All data to be backed up.

NFR-004 Website/Mobile Performance – Response time of application pages should be less than 1 seconds.
Current Questions:
S.No. Question Date Assigne Date of Response Comment
Raised d to Response
The structure of
administration is 24-03-2021 Client 27-03-2021 The entire development has to be Ok
as follows: administered from Admin Florja.
Admin (Florja) ---> After that the owner of the tenant
Multi-Tenant ---> (customer) needs to have full
Multi- Users ---> right on his/her instance. On the
1
Multi-Plants ---> individual tenant instance there
Multiple Irrigation should be users who can work,
units edit, add and change all records
assigned to them, a read-only
users and overall admin users

The current data 24-03-2021 Client 27-03-2021 Right now, we have a handful Ok
sources are the WLAN and LoRaWAN sensors,
data from sensors. and one external data source
2 What are the other (weather.com)
external data
sources and But any new sensor could and
expected in future? will be added, same with external
data sources.

The University will 24-03-2021 Client 27-03-2021 This will be a tenant within in the Need clarity on
have a separate multi-tenant structure. the data to be
login and data will shared with
be exposed to Will be many going forward. University.
them in tabular
format and graphs.
What will be data
3
policy? And which
data to include and
which to exclude
from sharing? Also
does the tenant
have to approve
data sharing?

The 24-03-2021 Client 27-03-2021 Yes - needs to be defined, for

homepage/dashbo starters let us assume there will
ard will be different be max 20 different reports.
for
4
SuperAdmin/Tena
nt/User/Academia,
what must be
shown in each?

What are the 24-03-2021 Client 27-03-2021 Yes - needs to be defined, for
relevant analytical starters let us assume there will
graphs that can be be max 20 different graphs and
represented in 2-3 dashboards.
5
either the
dashboard or in
the Visualizations
page?

6 Using Machine 24-03-2021 Client 27-03-2021 Needs more work. From client or
 Learning we can our side?
do the forecasting.
There can be too
many
possibilities for this
based on data. We
must map it with
the problem we
are trying to solve.
What can those
problems be?

Automation can be 24-03-2021 Client 27-03-2021 Right now, the automation is Automation
done from sensors sensor(s) to irrigation unit, BUT parameters
data to action in there will be many more in the needs to be
irrigation. What near future. defined.
7
actions can be
automated and
what parameters
can be followed?

For users and 30-03-2021 Client

tenant to interact.
And post the
photos and videos
to internal and
8
external social
media. An internal
social media
platform needs to
develop?

App for only user 30-03-2021 Client

9
or Tenant too?