1. Agricultural Management System System Developers: Ishay Levy Eran Brill AMS

2. Introduction In today's industrial and business world, Computerized management systems is becoming more and more common, and can be found even in small and medium scale businesses. Many managers and employers use such tools to help them measure and study their workers’ work habits: Sales Shops: Tagging each sale for a Sales person, all sales are recorded, Manager can rate his workers by efficiency. Telemarketing, Costumer Services : each call data is recorded and rated by length & outcome. Industrial Factories: Each Machine (and its operators) production is recorded, duration of actions can be measured. Each Worker, and the entire business, efficiency can be measured !

3. Introduction A manager can use this tool for: Making management decisions: Which worker needs to be “pushed”, to be fired or maybe to be promoted. Understanding the real “picture” of the business: How long does it take to do a certain job? How much did we sell today? produced today ? what is the production rate this week?

4. Problem Domain Situation in Small and medium scale Agriculture: Most managers rarely use any computerized system in measuring Workers efficiency. Main Reasons: Outdoor business. workers scattered in teams across a big field. The “Producing Machine” is the land. Attaching measuring tools to the machinery in use, is not affordable. Technophobia.

5. Managing in Agriculture Some Problems in Agricultural Managing: Workers scattered in teams across a big field – where are they now? Most workers are foreign – communication problems Work rate is usually measured only by eye assessment. Productivity can be measured only in retrospective view. Problems are known to the manager only if the workers report them.

6. Vision The agricultural field management system (AMS) will be a helping tool for management of small and medium scale agricultural. Using ScanTask terminal technologies, the system will collect field workers productivity data, analyze the data collected, and will give reports to the Farmer. these reports will include concrete business data for real-time, and for retrospective view, allowing the employer to get a complete view of his workers productivity and work habits. An employer using the system should be able to enhance productivity, and reduce the cost of field workers management.

7. The Proposed solution The system: Scan Task Terminal (touch pads) are to be used to record each workers team action. Each action is sent to ScanTask server by GPRS (General Packet Radio Service) where it is tagged and saved as an event in ScanTask Event Database. Our System will be using the ScanTask Events database, And will implement The GUI, Allowing the user to get all relevant business data in the form of reports. The User will be able to access the System by Web Browsing, via both Desktop browser (PC), and mobile phone browsing technologies.

8. System Architecture

9. The System we are developing will consist of 3 main components: 1.GUI : A Website implemented for the 2 optional users: PC Users ( an HTML based website) Mobile phone users (XHTML based) 2.Report Server : The main core of the system, in charge of querying from databases, data analysis, generating reports, and saving some data. Will be written on java on eclipse platform, accessing databases will be using JDBC. 3.Databases: we will be using two databases (MySQL based). A.ScanTask Events Database: store all events received from Workers Terminals) B.Daily Database: Store daily reports summary.

10. Functional Requirements Reports: 1. Data reports (Tables). 2. Graphs. 3. Geographical reports. Data Reports (filtered): 1.Daily reports: A summary of each team work along a day. (type of action, Area/Trees covered, Avg. times per tree, avg. time between trees). 2.Reports per period (same as 1, per period). 3.Task report (for a certain task): Trees covered, avg. times, per plot, per teams, expected time for completion. 4.Efficiency reports: avg. time on tree, avg. time between trees, breaks, task completion. (Result will refer for a day, period, task, plot and team). 5.Real Time Reports.

11. Functional Requirements Graphical Reports : Presents data By graphs and Diagrams. Giving the user other prospective for viewing results: 1.Comparative output Graphs for daily, periodic and task reports. A.Comparative graphs for teams' efficiency. B.Comparative graph per task or period (comparing number of trees per day). 2.Pie diagrams : comparing quantities per team, per plots, per days, all from the total. Geographical Graphs: Used Using Google Maps API. After setting Coordinates for trees, Enable the User to get work reports using Real Area Maps. 1.Real time report: Teams position (based on last report), trees and sections covered today by each team. 2.Tasks report: Area covered for each team for current task.

12. Geographical report example חלקה 48 3% הושלמו לפעולת ריסוס 3 עובדים פעילים : 654 789 321 654789321

13. Functional Requirements Report Server functionalities 1.Generating reports: Querying from 2 databases: dependent on type of data wanted. 2.Saving Daily reports into Daily database. 3.Recognizing and adding “Alerts” into reports. (breaks, exceptions in working time for a specific task) 4.Setting an saving user settings (what data to present on each report, When to generate the daily summary, what is the time quanta for a specific task). Daily database 1.Stores all daily summary in the forms of teams, tasks, and times. 2.Reduces query time for most reports.

14. System Interfaces ScanTask Events Database will be accessible, but only to complete developed system. – For developing we will build a Simulator, and a copy of the ScanTask events Database. – The Simulator will allow simulating all relevant events as well as test boundary cases. Geographical reports are to be generated using Google Maps API.

15. Event - structure and content Terminal ID Action Type Location Time Extra Field

16. Non-functional requirements Portability Other then a standard Website, Some features of the system can be accessed from the mobile phone using XHTML. Usability The user of our system is a simple user, with no former knowledge about databases report, queries or even using a website. The website will be friendly and “flat”. Availability Because our users don’t have a fixed schedule and may use it through their cellular's, the system will always be available.

17. Main Usage

18. Get Report Actor:User (PC or Mobile Phone) through WEB Description:Getting Report (general) Pre-Conditions: 1. Report Server is Online 2. User Logged in Post-Conditions:Report Presented to User Flow of events:1. User chooses type of report, time interval, fields 2. calls get report function in Report Server 3. The report server, finds the relevant Database to use 4. The report server execute a SQL quarry 5. The Report Server generate the report from the data received from database. According to the type of report the user wanted. 6. report server appends notes regarding "Alerts" to the report 7. The GUI Present the Report for the user

19. Get Report

20. Geographic Report

21. Creating the Daily Report Actor:Report Server Description:Generating Daily - report Pre-Conditions: 1. Report Server is Online 2. User Logged in 3. Google Maps API is Online Post- Conditions: Real-time Presented to User Flow of events:1. User chooses type of report, time interval, fields 2. calls get report function in Report Server (type geographical) 3. The report server execute a SQL quarry on the ScanTask Database 4. The Report Server generate the report from the data received from database. 5. The report server summarize result and transform them to SQL relations 6. The report server adds the result to the Daily database

22. Risks Abandonment The people that will use the system are not technology-oriented people, if the system will not be friendly and the users will feel that the “old days” were better, they will abandon the system and will not use it. Connectivity The system depends on a stable connection to ScanTask systems, if this connection will be slow and unreliable the entire system will suffer from slow queries and reports that are not updated.

23. The Prototype The Prototype will include: Basic report Creation: data, geographical, graphs. Creation Real- time and periodic reports. Daily database. The Basic Website features- including cellular access. Simulator