A gricultural M anagement S ystem

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 worker’s work habits. Each worker, and the entire business efficiency can be measured!

3. Current situation Most managers rarely use any computerized system in measuring workers. 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.

4. The Proposed solution 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 PC and mobile phone.

5. Functional Requirements The system will have both a PC GUI and a cellular GUI, each interface the system will offer: • Login for authorized users • Receiving Business reports. • Receiving real-time statues reports. • Receive alerts and Work related notes . • Managing data in the DB

6. Functional Requirements Graphical reports : Present data by tables, graphs and diagrams. Giving the user other prospective for viewing results and allows to compare different parameters: • Team’s efficiency in a specific plot or for in a specific action • Plot’s actions statistics • Every combination of plot, team and action

7. Functional Requirements Geographical Graphs: Using Google Maps API, the system will enable the user to get reports using Real Area Maps: • Real time report - teams position (based on last report), trees and sections covered today by each team. • Tasks report - area covered for each team for current task. • Plot report – general data displayed on the plot, best and worst teams or actions.

8. Functional Requirements Database functionalities • Querying from two different databases, depend on type of data wanted: • Raw data for real time analysis. • Analyzed data for old data. • Recognizing and adding “Alerts” into reports • Breaks • Exceptions in working time for a specific task. • Best and worst

9. Functional Requirements Database functionalities • Creating daily database - Stores all daily summary in the forms of teams, tasks, and times. This reduces query time for most reports. • Manipulating data in the DB: • Simulating events to test the system • Adding and removing parameters such as plots, actions and users.

10. BIRT - Graphical reports BIRT - Business Intelligence and Reporting Tools is an eclipse plug-in tool which creates and displays charts and graphs from a database, BIRT functionality: • Can be Connecteddirectly to data source. • Creates rptdesign files that can be deployed in a every application & environment. • Allows creating dynamic reports – parameters can be passed in runtime.

11. BIRT - Graphical reports

12. Google maps Google maps allows a simple API to display maps and objects like polygons and tool tips on them. var map = new GMap2(document.getElementById("map_canvas")); var polygon = new GPolygon([new GLatLng(31.7718,34.7043), new GLatLng(31.7685,34.7155), new GLatLng(31.7717,34.7168), new GLatLng(31.7750,34.7054), new GLatLng(31.7718,34.7043) ], "#DDDD00", 5, 1, "#FF0000", 0.2); map.addOverlay(polygon); example

13. System Architecture

14. System Architecture Web UI Google Maps Report Server BIRT Report Engine DATABASE Data Manager + Events Simulator

15. System Architecture GUI - • PC Users - a JSP based website. • Mobile phone users (XHTML). Report Server - • Connection with relevant BIRT report. • Passing Google map code • For the cellular users- in charge of passing a relevant parameters for query to the databases, and to generate a textual report back to the GUI. Will be written in java on eclipse platform, accessing databases will be using JDBC.

16. System Architecture DB manager – • Execute queries and return their results Databases - We will be using two databases on MySQL server. • ScanTask events database - store all events received from workers terminals • Daily database - store daily reports summary.

17. Main classes

18. Main classes Report server - • For pc users – connection with relevant BIRT report for user request. • Creating and passing report ALERTS. • For the cellular users – in charge of generate a textual reports using connection with data source, and pass reports back to the cellular GUI. Will be written in java on eclipse platform, accessing databases will be using JDBC.

19. Main classes DB manager - Query - executes queries based on the parameters passed by the report server. Simulate – inserts new events into the database Manage – manage parameters such as plot, action and team. Analyze– creates a daily database for improved runtime.

20. User interface PC - • PC GUI will be accessed through the web, allowing a simple user to perform queries, the report server will determine which report to load based on the parameters. • Administrator user will be able to manage the database parameters through the GUI • The PC interface is based on JSP/J2EE that enables to access the report server.

21. UI Example

22. User interface Cellular - • Users can perform queries from their cellular from a GUI based on XHTML • Since it’s a limited platform the results to this queries will be textual.

23. Task list • Full PC functionality – 4/6 • Testing PC functionality -4/6 • Report server and db manager support for cellular queries – 10/6 • Testing Report server and db manager support for cellular queries -11/6 • Cellular GUI on XHTML – 22/6 • Testing – 30/6

24. THE END AMS