Technical Assistance support to the Lebanese Ministry of … · Delegation of the European Union to Lebanon - 490, Harbour Drive Building - Charles Helou Avenue - Beirut - Lebanon

1

SPECIFIC TERMS OF REFERENCE

“Technical Assistance support to the Lebanese Ministry of Agriculture for Designing and Developing the Agriculture Management information system

(AMIS)”

FWC BENEFICIARIES 2013 LOT 3: Telecommunications and information technologies

1. BACKGROUND 1.1. Beneficiary

Ministry of Agriculture - Embassies Street, Bir Hassan - Beirut – Lebanon 1.2. Contracting Authority

Delegation of the European Union to Lebanon - 490, Harbour Drive Building - Charles Helou Avenue - Beirut - Lebanon 1.3. Country background and current situation in the sector

The Ministry of Agriculture (MOA) is the institution responsible for setting the agriculture strategic, legal and regulatory framework, formulating and implementing policies/programs for the development of the sector in Lebanon, and enhancing infrastructure development to promote investment and improve agricultural production and marketing. MOA also plays an important role in the management of natural resources of the country (agricultural land, irrigation water, forests, fisheries, pasturelands) and contributes to rural development programs. The agricultural sector in Lebanon still suffers from chronic structural weaknesses, thereby necessitating the adoption of adjustment programs at different levels. In this context, MOA’s Strategic Framework for the period 2010-2014 was formulated in December 2009, and built around eight pillars setting forth interventions at the central and local levels, using a combination of programs/projects and policy measures aiming at decreasing production costs and at improving the quality of Lebanese agricultural products. Currently, MOA has developed a very small number of internal systems and programs for some Directorates through their own budget or with an external support (i.e. FAO) with no integration or data exchange between them. They cover part of the business needs; while some new applications are under development and final testing before being deployed in a live mode. This is leading to a situation whereby manual work is still the predominant tool for the treatment of information. The business applications that are implemented at the MOA can be summarized as follows:

1- CSPro: is an open source system used for data entry and reporting found at Service of

Statistics and Economic Studies. CSPro holds all farmer information from census 2010.

CSPro enables you to collect information through a data entry screen. Also CSPro enables

you to do tabular reports where you can do self-service reporting. Currently there is

2

information on around 160,000 farmers that can be exported to Excel. This data must be

exported to SPSS for further analysis. A Register of Agricultural Holders/Enterprises web

application should be developed.

2- DWF (Document Workflow): common document workflow for all of the ministry

directorates where each process is registered in the system and gets an automatic serial

number. The process is scanned and proceeds in a workflow until it is finished. The DWF is

developed using SharePoint and SQL server.

3- DIS (Domestic inspection System): is a web based application that includes the following

dynamic modules:

Reference Survey Module to provide reference for each survey;

Inspection Task Alert Module: System alert scheduling inspection tasks;

Surveys Data Entry Module: data entry screen to enter survey details;

Survey Evaluation Modules: report that compares data entered in inspection

modules;

Inspection Mission Module: data entry screen to fill mission tasks and inspectors;

Mission report Modules: data entry screen to fill data related to inspection minutes;

Sample Modules: data entry screen to fill data related to samples, laboratories and

test results;

Reporting Module: several dynamic reports;

License Module: report to issue official license;

Administrator module: allow full system administration;

This application is available on tablets. The application is developed using .net

technologies and Microsoft SQL server.

4- Programs and Projects Service System: is a web based application that handles all

projects data including objectives, activities, areas of intervention, targeted regions, etc.

The application allows adding new projects and updating them. Project managers can enter

and update projects with ability to upload attachments. The application allows funding

agencies to be informed about the areas of interventions of each other to collaborate and

avoid duplication. The application is developed using .net technologies and Microsoft SQL

server.

5- Agricultural Extension System: a web based application that is used to provide electronic

services to all the extension centers in Mohafaza and Caza and all other users.

The application provides the following:

Enter and maintain extension documents by the MOA and NGO’s;

Collect information on NGO’s & other extension service providers;

Gather information about extension activities undertaken by projects;

Classify the extension information, documents, activities…

Search for technical information by type of crop.

Search for agricultural experts and service providers by technical or geographical

area.

3

Issue reports

Provide communication, information and lessons learned.

The application is developed using .net technologies and Microsoft SQL server.

6- Forestry Centers System: is a web application that tracks and monitors citizens requests to register cutting, pruning, charring and other activities in forests, to issue licenses or grant approvals, and tracks numbers, citizen name and place. Also the system allows keeping information of the records and irregularities at field level. The request can be sent from MOA regional offices to head office. The application is developed using .net technologies and Microsoft SQL server.

7- Employees System: an application that deals with personnel (employees and workers) and all files and information related to them (i.e. personal information, administrative situation). The application is owned and developed by the Civil Service Board as common application for all government entities.

8- Agriculture Prices Statistics Systems: is a web application that allows data collection

and data processing for tracking and analyzing the agriculture prices. Data is recorded on

monthly basis and entered according to Mohafaza. Simple analysis of the data is carried

out in terms of calculating averages that were recorded in the different Mohafazas. Also

prices of agricultural products (wholesale and retail prices) are aggregated for Lebanon.


9- Cost of production Statistics System: is a web application that collects data on the cost

of production of different agricultural products in order to analyze cost structures of

agricultural activities. This survey covers major agricultural products (crops and livestock)

products at the level of Mohafazas. The application is developed using .net technologies

and Microsoft SQL server.

10- Import/Export Management System (IEMS):

a. System

Data management of imported and exported animal products;

Risk Assessment Calculation Engine;

Samples Module: data entry screen to fill data related to samples, laboratories and

test results;

Reporting Modules;

Administrator Module.

b. Import/Export permission and Stock Management of Specific Products

Importers and exporters registration;

Production registration;

Stock Tracking;

Import/Export permit;

Import/Export permit printing.

c. Milk and Cheese Management

4

Factories registration;

Importers registration;

Product registration;

Stock Tracking;

Import Permit;

Import Permit Printing.


11- Lebanese Pesticide Stock Management System (LPSMS):

a. Registration

Addition of active ingredients;

Registration of pesticide formulation;

Registration of commercial names;

Registration of importers, exporters, formulators, re-packagers, distributors, retailers

and prescribers;

Licensing.

b. Control of pesticide import, export, distribution and use:

Pesticide import permit;

Pesticide import permit report;

Barcode module;

Checking for conformity at border point;

Samples Modules;

Prescription forms;

Pesticide movement tracking;

Alert system.

c. Survey and control of users, warehouses and stocks of pesticides:

Reference pesticide users survey and control module;

Pesticide users surveys and control data entry module;

Pesticide users and control evaluation module;

Survey and control mission module;

Samples module.

d. General management

Reporting modules;

Administrator module.

e. Phytosanitary index web interface and mobile application

Phytosanitary web interface;

Phytosanitary mobile application.


5

12- Lebanese Electronic Register of Varieties-Seeds (LERV):

Register importers, exporters, merchants, processors, analysts (authorized

laboratories), breeders and nurseries of propagating materials;

Survey and control of breeders and nurseries of propagating materials;

Registration of varieties;

Control at border points;

Reporting;

System administration.


13- Fisheries Licensing System (FLS) where licenses are given to fishing vessels. FLS

produces statistical monthly reports. The application is developed using .net

technologies and Microsoft SQL server.

14- Crop Management Application is a web application that is used to register agricultural

land use where location of farmer land including Mohafaza, Caza, village… is registered.

Then each plot is identified by a generated serial number used for product marketing.

This application also includes a module to track farmer information in addition to several

dynamic reports. The application is developed using .net technologies and Microsoft

SQL server.

15- Bees Management Application: is a web application that is used to manage bee’s

owners and honey amounts produced each year. Several statistical reports exist.


An ICT/AMIS contract has been concluded to implement a document workflow/archiving system for the MOAHQs, 7 regional offices and 10 exit/entry centres and an e-library. In addition, MOA has developed many database/programs not limited to: Programs and projects service system, Agriculture extension system, Agriculture forestry centres system, Agriculture prices statistics system, Cost of productions systems; a Human Resource (HR) database application has been developed by the Civil Service Boarding of Lebanon (CSB). The creation of a new MOA portal, a National e-government pilot project and enlarging WAN & Internet LAN capacities are in progress. This Framework Contract TA will be implemented under the Agriculture and Rural Development Programme (ARDP), which has been designed to address the agricultural sector needs in Lebanon, in accordance with the strategic priorities identified in MoA’s Plan of Action 2010-2014. ARDP is funded by the EU through the European Neighbourhood and Partnership Instrument (ENPI) and is implemented by MoA. The general objective of ARDP is to improve the overall performance of the agricultural sector and to improve the livelihoods of rural and farming communities to achieve sustainable agriculture and rural development. The specific objectives are: (i) to strengthen the capacity of national institutions to work on a coherent agricultural/rural development vision and to better implement agriculture strategic orientations, and (ii) to support and empower local rural actors

6

(farmers as well as cooperatives) by increasing access to credit and by supporting rural development initiatives consistent with local development priorities.

2. DESCRIPTION OF THE ASSIGNMENT 2.1. Global objective The overall objective of this project is to enhance the performance of MoA. 2.2. Specific objective The specific objective of this contract is to improve the flow of information within MoA by establishing an Integrated Agriculture Management Information System (AMIS) to support decision-making as well as the implementation and monitoring of the sectors’ policies and of the strategy of MoA.

2.3. Requested services

The project will design and implement an Agriculture Management Information System (AMIS) for MoA and train staff to use the new applications. There are 2 main results to be achieved by the consultant:

1. Increased level of automation within the MOA.

2. Improved accuracy and reliability of internal and external information produced by MoA while minimizing the paper work.

2.4. Required outputs 2.4.1. Geographical area to be covered

Lebanon. 2.4.2. Target groups

Ministry of Agriculture, Directorates, Services, Departments and decentralized offices (i.e.

Regional centres, Agriculture schools, Forestry centres, etc.)

2.4.3. Description of the assignment The scope of the TA support foreseen under this project will cover the following:

7

1. Develop new applications to complete the automation of MoA’s information system (the new applications will complement to the existing ones);

2. Integrate all applications (existing and new) within a portal to provide consolidated and centralized data allowing for the generation of static and dynamic reports.

The portal will:

Be the entry point to the applications, based on the users’ access rights privileges to simplify the process, increase efficiency and for better decision making;

Generate alerts between applications when certain conditions are met;

Integrate the Document Work Flow (DWF) within the portal.

This portal will be an intranet that brings information together from diverse sources in a uniform way. Usually, each information source gets its dedicated area on the page for displaying information; often, the user can configure which ones to display. It will:

Allow adding links to external web sites (not from the portal) through Ministry web site by special user account. Each agriculture department will receive a username and password to have access to a dynamic search;

Allow publishing of files through a dynamic form with additional details on uploaded files so they can be searched later. The published files should be accessible by specific services or persons Example, agreements archiving;

Integrate all needed applications to the Register of Agricultural Holders/Enterprises application (A new web application to be developed that includes basic information on farmers/agricultural enterprise;

The integration between the different applications does not include any real-time interfacing and data dependency between applications in a way that one application depends on another. This integration is more about sending or sharing reports and / or information between one application and the other (as shown in the Target AMIS of the MOA figure).

The portal will provide a consistent look and feel with access control and procedures for multiple applications and databases, which otherwise would have been different applications altogether.

Users will be allowed to add documents to the portal from their applications to be viewed by other MOA’s users according to group’s privilege. Each group should have different privileges or rules that allow it to see or share different screens and applications.

It is envisaged that the work of the experts under this project will be structured in the

following 7 phases: [Please check Appendix Noº 1 to the ToR – Description of the new

applications]

Phase 1: Project Kick-off & Preliminary Activities

Phase 2: Requirements Analysis;

Phase 3: Software Applications Design;

Phase 4: Software Applications Development;

Phase 5: software applications Deploy, Testing and Implement;

Phase 6: Training and Guide Documentation;

Phase 7: Project Closure.

8

Phase 1: Project Kick-off & Preliminary Activities

The main objectives of preliminary analysis are to identify MOA needs, evaluate the systems for feasibility and technical analysis of the present situation. The assessment of the current system will be the foundation for all subsequent engineering works. The description of the main needs that will be identified during this exercise, should take into account all the features of the various systems currently in use at MoA. The result should be the evaluation of the current systems and identification of areas for improvements and of possible issues in advance to avoid encountering problems later. The expert should analyse the systems from different perspectives including general business goals, users and technical issues. The consultant should ensure that there are no problems in the proposed systems considering each one individually and studying possible interactions in between The preliminary analysis should consider required personal staff, time and hardware resources at a general level. This includes identifying the relevant personnel from MOA, preparing, and agreeing on an initial basic agenda for their involvement in the project. The purpose is to ensure that the required staff from MoA will be available to avoid delaying the project activities. The availability of required technical software and hardware resources at different stages of the project should also be considered. The schedule to provide these resources should be consistent with an initial chronological project plan. The purpose is to ensure that logistical and procurement preparations do not delay project activities. An initial general project plan should be prepared and should be consistent with the phases specified in the TOR. The plan should be at a general level going as much as possible into details about the activities and deliverables of each phase of the project. In the initial plan, special focus should be put on the successive phase: the requirements analysis.

The main activities involved in this phase are:

- Project Kick off and preparation of the inception report - Preliminary investigation. - Meetings with different stakeholders: management of concerned departments, direct

users of the systems and all other concerned staff.

Output/Reports: Initial Project Plan Document, Infrastructure Recommendations Report.

Phase 2- Requirements Analysis

The requirements analysis phase defines the requirements of the system, independent of how these requirements will be accomplished. This phase defines the problem that MOA is trying to solve. The deliverable to be produced at the end of this phase is a requirement document. This document should state in a clear and precise way what is to be built to improve MoA’s information systems. Goals and interactions should be provided without implementation details. The requirements document should describe the actions that can be done on the system. Interactive approaches should be used to refine those details.

9

The requirements should not imply an architecture design but a description of the artifacts of the system and how they behave from MOA’s perspective. Later, in the design phase, these requirement descriptions should be mapped into detailed specifications. The main activities involved in this phase are:

Detailed Investigation

- Information Gathering This activity consists of gathering information about the functioning of the present systems, proposed systems and MOA’s activities. The methods of gathering information should include:

1. Interviews must be well-planned in advance; 2. Questionnaires and focal group discussions; 3. Observations: the analysts should study the system from different perspectives on site; 4. The study should include procedures, organizational goals, policies and users; 5. Study of existing documents.

- Data Analysis

Once information about the current system has been gathered, it needs to be evaluated, analyzed and reported to the people concerned. Results of interviews and responses to questionnaires and observations should be studied. Data flow diagram (DFD) should be used to represent the data flow with in MOA. Output/Reports: Project Plan Document, Requirement Definition Document (RDD), Process

and Dataflow Diagram.

Phase 3- Software Applications Design

The software applications design should provide technical details about how the systems will be built. The design should meet the objectives specified in the Requirements Document (prepared during phase 2) using the technologies indicated in these ToR. The design should cover the following areas:

- Overall system structure; - Data stores and databases; - Data access components; - Application control flow including user interfaces and transitions in between; - Integration with the hardware system environment.

The following guidelines should be applied in the design:

Modularity: The system components should be partitioned according to different functions and interactions. The partitioning should result in manageable documented modules. The documentation should include information that supports in understanding the definitions, maintaining the application and extending the system functions with new features. UML (Unified Modeling Language) structure diagrams can be used for this purpose.

10

Component Hierarchy: The hierarchy of different components including dependencies, interactions and reuse should be described to provide details about how different components work together. UML (Unified Modeling Language) interaction diagrams can be used for this purpose. Structural Partitioning: The structure of programs should be described from difference perspectives according to system functions and control, top-down and bottom-up designs. Horizontal separation should be applied for major system functions. Vertical separation should be applied for lower level control and domain logic definitions. Data Structure: The structure of data in the system should be described using ERD (Entity-Relationship Diagrams). The description should include relations between different entities, constraints, key definitions and indexes. Maintainability, Extensibility and Scalability: The system design should be organized for understandability and extensibility. Components that can be integrated with abstract definitions that provide interfaces for extensions should be provided. The design should also consider possibly increasing the capability of the systems such handling more requests by providing hardware and software redundancy solutions. Documents that support maintenance and extension operations should be prepared.

Quality: The design should ensure reliability, robustness, security and performance qualities. The system should be able to provide services to users for an acceptable time period. The system should also tolerate extreme cases of unpredictable input, requests stress and hardware failure as much as possible. Measures for protecting from possible hostile acts should be ensured for security.

Output/Reports: Detailed Project Plan Document, Functional Specifications Document (FSD), Software Physical Design Document, Information System Security Plan, Infrastructure Recommendations Revision Report, Data Model Document, Testing Plan Document.

Phase 4- Develop Software Applications

The goal of the Development phase is to build and test the system components defined and approved in the design specifications, including developing the customizations, integrations and interfaces, and data migration processes. The major deliverables include the complete system configuration, completion and freezing of code for customizations, integrations and interfaces, and data migration. Other key deliverables include finalization of the design specifications and the completion of Solution Testing. The process models, system configuration and setup should also be completed in this phase.

Output/Reports: Final Business Process Models, Final System Configuration, Final Custom Code Development, Final Production Environment Specification, Final Integration and Interface Code Development, Final Data Migration Code Development.

Phase 5- Software Applications Deploy, Testing and Implement

The Deployment and Test phase is where all the efforts of the project team come together for a successful transition to the new solution. Key activities in this phase include User Acceptance

11

Testing, and the actual cutover to the new or upgraded production environment. Performance Testing is also completed. Preparations for starting the system should also be completed. This includes final data migration and installation of required software systems on the production environment.

Output/Reports: User Acceptance Test Results, Final Data Migration, Final System Readiness & Site Preparation Report, Production Environment, Deployment Plan, Production Operations Guide, Backup and Disaster Recovery Plan, Testing and Change Control

Phase 6: Training and Guide Documentation:

The overall objective of the training activity is to create the foundation of a network of individuals who can improve the possibility of successfully implementing the automated systems and thus ensure a smoother transfer of the MOA processes’ work to electronic processing.

The main activities of this phase:

Conduct the Required training: The training sessions should cater for both Functional and Administrative functions, focusing on the direct use and management of the application. The Training Schedule will be agreed upon between the consultant and the Ministry in due time. This training will cover the following topics:

1. Database Administration; 2. Database structure; 3. WEB generation / Internet data connection administration; 4. Software development; 5. Data entry; 6. Inquiry; 7. Reports.

The expert shall provide training to the users and system administrators of the applications, as follows:

Operational and User Training

Three types of training are required: 1. End user training (indexing, data entry, and data collection management); 2. End user training (search, information retrieval and application features); 3. High-level training for IT Team.

Administration Training

Advanced administration training is required:

Introduction and overview

12

Installation and setup

Setting up users

System Administration

Backup and restore

Security

Performance Management

Data Integrity

Linking to database

Setting up new forms and user interfaces

Modifying existing forms

Application Report Generation of various complexities

Statistics Analysis

Customization of the application

Other subjects as applicable

Transfer of consultant’s know-how

The consultant shall provide training to the selected users as specified in the following: 1. All training shall be "hands-on"; 2. Trainers shall provide the end-user courses in English/Arabic; 3. Training material that clearly follow and illustrate a course's outline and that contain practice

exercises are required for each trainee and for each course prior to the start of the respective training course;

4. When scheduling the training sessions, it should be noted that not all trainees could attend classes at the same time;

5. Training schedule should not overlap or conflict with MOA work schedules; 6. Training is preferably done at MOA premises; 7. Following training, the trainer shall issue a completion certificate to all trainees that have

successfully completed a course. The trainer shall also submit a report rating the attendance and performance of the trained staff members;

8. The trainee shall fill a training assessment sheet to evaluate the training conducted by the consultant.

Output/Reports: Training Plan, Guides (including but not limited to an installation and deployment guide, a User Guide, a Technical Guide and Operation Manual for each of the Software applications) and training reports (trainee attendance sheets, training evaluation sheet)

Phase 7- Project Closure The Project Closure phase includes the activities required to close the project, provide post-production support, and transition of the solution and hand-over to beneficiaries. Key objectives of this phase include providing post–go-live support, transitioning the solution to support, performing a final quality audit, and project closure. The main activities of this phase:

Deliver an end of project report;

13

Deliver latest and up-to-date versions and source code of the software application program

files, scripts and compiled executable with the proper licensing.

Support to operational acceptance.

Output/Reports: Project Closure Report, Final Delivery of all Project Deliverables documents in two formats: Microsoft Word for Windows on CD or DVD, accompanied by a hard copy and up-to-date source code. The attached figure (Target AMIS of the MOA) summarizes the target to be reached for the new AMIS of the MOA. It shows the existing applications and the new ones along with the integration.

Colour / Sign Description

Existing applications.

New applications that need to be developed within the scope of this TOR.

Applications already developed, but not yet operational.

White rectangles represent Department Name while other colors represent applications names.

The arrow shows the applications that need to be integrated. The sign of the arrow shows the direction of the data / information to be transferred. The integration is part of this TOR.

Notes:

The purpose of this figure is to show the overall global topology of the target solution to be reached. Details of each application and integration are found below in the document;

All web applications should be accessible by all MOA regional offices; The name showed in each box of the above figure indicates the name of the application.

The following figure summarizes the AMIS Applications to be developed in the course of this particular project. It shows the applications to be developed and the integrations to be built.

14

AMIS Applications Schema For This Project

Farmers Input Support

Feeds

Seeds*

Fertilizers*

Distribution Management System

Nurseries

Pesticides*

Veterinary Drugs MOA Related

DIS - Inspection

Import/Export* Inventory Management System

Cooling & Packaging Cars

Organic Production Generators

Agri Car License Attestation IT Equipment

Stock Management

Statistical Farm Register Gardens Management

History

Dynamic Search School Management System

Students

CITES Permit Teachers

Courses

Pest & Disease Financial Management

Fires Management

* Applications already exists

Links from MOA website to external web sites

Animal/Plant Food (Fresh & Processed)

Integartions with Existing Applications

Publish documents with ability to Search

Data integration

Pesticides*

Labeling

Fertilizers*

Portal & Integrations

Register of Agricultural

Holders/Enterprises

Update

Link

Update Update

15

2.4. Language of the Specific Contract The language of this contract shall be English. 2.5. Subcontracting Subcontracting is not foreseen. 3. EXPERTS PROFILE The implementation of the project will require the contribution of the following team of experts:

- A category II expert (Team Leader) with experience in MIS and Data-base design, development and management in the Mediterranean and preferably ENPI South region, with the technical know-how needed to develop Agriculture Management Information System “AMIS”, and with specific expertise in putting such system into practice.

- A category III expert Web designer/developer experienced in writing programming codes, graphics packages.

Close co-ordination and co-operation between the experts’ team and the appointed staff of the Ministry is an important milestone for the successful achievement of the expected results. Expert 1 – Team Leader: Category II MIS and Database analysis/designer expert. (87 working days)

Qualifications and skills

University degree (BS or MS preferably) in Business Computer or equivalent, preferably in the MIS sector;

Leadership and group management capacities; Project management certification is a plus; Complete fluency in English; Knowledge of Arabic would be a plus. Proven communication and reporting skills.

General professional experience

A minimum of 6 years’ experience (postgraduate) in designing, analysing, developing and supporting MIS applications, preferably in or for the benefit of the public sector;

A minimum of 8 years (postgraduate) experience in software applications development and software development project management;

Fundamental understanding of web-based systems programming and development.

Specific professional experience

Proven successful experience in managing and delivering similar projects in comparable fields.

Deep knowledge in business analysis tools and techniques. Deep knowledge of project management tools and techniques. Experience in prototyping the user interfaces. Experience in designing the Data Model and Algorithms

16

Expert 2 – Category III Web Developer. (157 working days)

Qualifications and skills

University degree (BS or MS preferably) in Business Computer or equivalent in the MIS domain preferably;

Fluency in English; Proven communication and reporting skills; An excellent command of Arabic; Ability to work in team.

General professional experience

A minimum of 3 years’ experience (postgraduate), including at least 2 years in business applications development preferably in or for the benefit of the public sector;

Excellent mastering of the usage of ASP.NET and SQL database.

Specific professional experience

Proven experience in the fields relevant for this tender. Deep knowledge of applications development and programming methodology.

All experts must be independent and free from conflicts of interest in the responsibilities they take on. 4. LOCATION AND DURATION 4.1. Starting period The expected start date is April/May 2014. 4.2. Foreseen finishing period or duration The period of implementation of the contract will be 10 months from this date. Please see Articles 4 and 5 of the Special Conditions for the actual start date and period of implementation. 4.3. Planning See time schedule after

17

4.4. Location of assignment In Lebanon, the operational base for the project will be at the Ministry of Agriculture in Beirut. 5. REPORTING 5.1. Content The Contractor will submit the following reports in English in 1 original, 1 electronic and 2 paper copies:

Inception Report of maximum 10 pages to be produced after 2 weeks from the start of

implementation. In the report, the consultant shall describe e.g. initial findings, progress in

collecting data, any difficulties encountered or expected in addition to the work programme

and staff travel. This report will also contain the initial basic agenda detailing the

respective involvement in the project of the relevant personnel from MOA and of each of

the experts. Unless the Contracting Authority sends comments on it, the inception report

will be considered tacitly approved.

Development and Analysis Interim Reports. Interim reports, indicating the analysis

work progress should be submitted at the end of every month or upon completion of

Final Report. This report shall be submitted once the results of the acceptance phase

(performed by the Contracting Authority) has been taken into consideration and integrated

within the programs. It should include all necessary details explaining the programs and

their relationships, database schema, etc.

5.2 Language All reports shall be written in English.

18

5.3. Submission and approval of reports Reports must be in English and will be submitted to the Project Manager identified in the contract. The Project Manager is responsible for approving the Inception and Final Reports. 5.4. Number of report(s) copies The Framework Contractor will present four (4) hard copies and an electronic version of each document to the EU Delegation. The EU Delegation shall communicate to the Framework Contractor their comments and/or approval of the Final documents. 6. INCIDENTAL EXPENDITURE Office accommodation for experts working on the contract is to be provided by the Contractor. Experts will have to be equipped with own portable computers and Internet connection care of the Contractor. The Contractor shall ensure that experts are adequately supported and equipped. In particular it must ensure that there is sufficient administrative, secretarial and interpreting provision to enable experts to concentrate on their primary responsibilities. It must also transfer funds as necessary to support their work under the contract and to ensure that its employees are paid regularly and in a timely fashion. For the purposes of this contract, the maximum ceiling of per diem allowances is fixed at 260 Euro/day. The authorized items to foresee under ‘Reimbursable’ are listed below:

Per Diem in Lebanon (260 €/day),

International Travel (maximum 750 €/air ticket),

Costs associated to the organisation of 2 Workshops (2,000 €), [during the implementation of Phases 1 & 6]

Services (3,000 €).

7. MONITORING AND EVALUATION The purpose of monitoring and evaluation is to minimize risks in completing the project and facilitate achieving the expected project outcome based on:

Initial planning: the elements required to plan and deliver a project and abidance by the project plan phases and tasks dates.

MoA will assign a focal person to cooperate and facilitate the consultant needs.

Collecting and analyzing information: to insure effective execution of collected data.

Minutes of meetings between the consultant key experts and the contracting authority designated staff / business owners.

Effective decision making: throughout the monitoring and evaluation process, decisions need to be made as to how to proceed and how to respond to

19

information that is being gathered and to ensure that decisions reached are in the best interest of the project and MoA.

Managing resistance and conflict: to make sure to manage resistance and solve conflicts rapidly once they occur.

Lessons learned and feedback is vital. The importance and use of lessons learned have to be considered with how these can be used within the project and once it is completed.

Reporting: A core part of the monitoring and evaluation process involves effective reporting to MoA.

The consultant is to re-work all within scope requirements and enhancements with no extra charges as part of the main scope.

20

Appendix Nº 1

TERMS OF REFERENCE

“Technical Assistance support to the Lebanese Ministry of Agriculture for Designing and Developing the Agriculture Management information system

(AMIS)”

FWC BENEFICIARIES 2013 LOT 3: Telecommunications and information technologies

The new applications to be developed within the scope of this contract as follows:

1. Update DIS - Inspection (Domestic Inspection System):

There is a need to update the existing inspection application to include data entry forms for organic production and cooling & packaging units with integration with Register of Agricultural Holders/Enterprises web application. New or updated inspection data entry and registration forms should be in a dynamic way that support organic production and cooling & packaging to perform the listed below modules.

1.1 Organic Production:

There is a need to update the current DIS-Inspection web application to register organic

operators. These operators may be farmers, animal producers, bee’s producers, shops

(companies).

21

Data Entry Module: a data entry screen has to be developed to register the request

details including the name, operator name, kind of activity, situation, date of first

inspection, address, phone, expert name and list of required documents. The system

should allow user to upload different scanned copies of different documents.

Certification Module: a data entry list with all required documents and their current

status plus notes on each. The result of the check list should be registered in this

module and a certification is given for certification bodies. Ability to print out the

certification.

Alert Module: an alert for expiry dates of the certifications is needed.

Input Distribution Module: Integration with newly developed Farmers Input Support

application is needed.

Reports Module: Multiple reports including statistical, graphical and tabular data

reports with ability to export to Excel sheets and .pdf. The reports include but not

limited to:

o Certification bodies withdrawn from the system as of a certain date.

o Analysis of data per certification bodies categories.

o Grouping by operators types.

o Organic Experts list.

o New operators versus operators in the group.

o Areas per crop.

Integration Module: the application has to be integrated with Pesticide, Fertilizer,

Seeds and Register of Agricultural Holders/Enterprises web application.

1.2 Cooling & Packaging Module:

There is a need to update the current DIS- Inspection web application to register Cooling &

Packaging processes. The request is submitted to the related service. If the document

satisfies all conditions, then an inspection team visits the place and fills a check list form that

holds several yes/no questions. Several inspections can be done. This part is already

automated.

In order to complete the automation of the process, the following is requested:

Refrigerator Data Entry Module: A registration form has to be filled by regional offices

with all needed information and documents including name, Mohafaza, owner name,

category, phone, notes, registered in MOA (Y/N), registration date, inspection date.

In/out Data Entry Module: Each refrigerator sends in/out monthly information data

which needs to be registered by the service with details such as crop type, quantity in

first of month and quantity out end of month. Must be part of the stock DB (included in

the import/export system).

22

Packaging Data Entry Module: Several data input forms for packaging are needed:

Receiving of crop;

Handling crop;

Post-harvest treatments;

Operations done on crop.

Must be part of the stock DB (included in the import/export system)

Monthly Statistics Module: Several data input forms for cooling warehouses plus

charts

Quantity in;

Quantity out;

In/out report.

Alert Module: There is a need for an alert for period of time given for a certain

refrigerator in the inspection form.

Reports Module: Multiple reports including statistical, graphical and tabular data reports

with ability to export to Excel sheets and .PDF, the reports include but not limited to:

Quantities by Category per year and month

Monthly statistics by category, Mohafaza, year and month

Reports on in/out per refrigerator per year, month and crop.

All kind of reports for cooling and packaging.

Licensing Module: A license request form needs to be submitted from regional offices

to issue a license from the service of cooling & packaging. Yearly licenses have to be

produced to the cooling refrigerators and packaging factories.

Integration Module: The concerned MoA service has data on packaged crops while

some other statistical reports are needed like production, export and marketing.

Integration with inspection, extension, Register of Agricultural Holders/Enterprises web

application, import/export, and Pesticides web application.

1.3 Agricultural Car License

There is a need to update the current DIS – Inspection web application to issue licenses to

transport agricultural products. The request is submitted in the MOA regional offices. If the

request satisfies all conditions, then an inspection team visits the place and fills a check list.

This part is already automated.

In order to complete the automation of the process, the following is requested:

Data Entry Module: A registration form has to be filled in regional offices by farmer with

all needed information and documents including name, Mohafaza, type, village,

cadastral Number and area planted. This module is covered by DIS dynamic data entry

23

module. There is a need to check duplication on Mohafaza, Village, Type, and cadastral

number so no farmer takes two licenses.

Alert Module: an alert for expiry dates of the licenses is needed. License is valid for one

year only.


with ability to export to Excel sheets and .PDF, the reports include but not limited to:

Report by Mohafaza;

Report by MOA registration number from date to date.

Integration Module: Integrations with inspection and Register of Agricultural Holders /

Enterprises applications are needed to check if farmer is registered and to do

inspections.

2. School Management Application

It is a Management Information Web Application to manage information related to students, teachers, employees, courses and all the system and process related to running these schools efficiently. The schools offer courses and diplomas related to the agriculture field, including Authentication of students awarded certification.

There is a need for a school management application for students, including history

management with information on courses, certificates, school, year of graduation, student

number (sent to Ministry of Education), history of all students throughout all the years and

other related reports.

The application should integrate with Active Network solutions:

Personal information about student, keeping all their history;

Information about courses and their coefficient;

24

Information about official degrees and certificates by dates, students, and schools to be

used as authentication or validation on and with templates option and ability to reprint

copy. (Includes official diploma (BT) in general agriculture and animal breeding);

Information about teachers, history, current courses and evaluations;

Gather information about trainers, evaluation of trainings and implementation of

trainings;

Student numbers and their graduation number;

Detailed information by student about courses taken, number of times failed/succeed,

trainings (places, skills, evaluations), years student attended the school;

Information about certificates and templates with ability to reprint copy;

Exams: results and questions to automate the results for each and all vocational schools

and reports on rank per class, per year;

Several dynamic reports on courses, students, instructors.

Management system for questionnaires for exams and evaluation of students and

teachers.

Automatically track sales of all school items.

Integrates to back-end school accounting module.

Administration module: allow full system administration.

There are seven 7 schools scattered over Lebanon. The module should be based on a

centralized approach with access from the schools.

There is a need for a simple School financial management module with student fee

collection and point-of-sale solutions to automate and track sales of all school items, collect

data from computer-generated receipts, comprehensive reports, simplify registration, track

donations and fundraising efforts, improve communication, and Arrange financial books.

The module should mainly manage:

Student fee collection: to control cash flow and outflow to secure, integrated payment processing solution to reduce errors, paperwork, and transaction times with Active's payment processing solution. o Payment processing

o Automatically generate invoices and receipts

o Apply refunds and adjustments

o Security

o Real-time financial reports for efficient accounting.

Identify registration fees and students payments, scholarships.

Activity Fund:

o Provide real-time insight into revenue, expenditures, transfers, adjustments and

student accounts.

o Access ledger, vendor and bank account information anywhere.

o Track bank reconciliations, deposits, invoices and any other financial instruments.

o Monitor transfers and adjustments through multiple phases.

Generate receipts to teachers, students, donors and more.

Vouchers and terms of payment.

25

Arrange financial books.

Specify fiscal year and related budget.

Contribution of agriculture schools.

Control of expenses compared to the budget.

Schedule of courses/events:

o Dynamic reporting tools that allow instructors to view all of their course schedules /

events and students instantly.

o Versatile viewing options let students view appointments by date or by instructor.

o Simple grid viewing of available times for easy scheduling.

o Automatic payroll integration that ensures hours worked turn into hours paid.

Email tools that maintain communications.

Reporting Module: Multiple reports including statistical, graphical and tabular data reports with ability to export to Excel sheets and .PDF, the reports include but not limited to: o Financial information

o Information related to students, teachers, employees, courses

Administration Module: allow full system administration to determine who has access

to view or edit within the system.

3. CITES Permit

There are some kinds of animals and plants that are threatened by extinction and a special permit is needed for their trade. Therefore, there is a need to develop an application in order to issue permits and manage its data.

The permit is called CITES permit. The permit has to be given by the concerned

department/focal point. The permit is valid for six months.

Data Entry Module: the module should allow data entry of several items with appendix,

description, quantity, exported quota, country of origin, permit number, date, country of last

export, permit number and date.

26

The permit should be filled for export, import and re-export;

Validity date should be filled automatically when filling issuance date and by default

equals issuance date plus six months for export and re-export and one year for import;

Appendix, common & scientific name and permit of should be drop down lists for the

most common list of specimens with the possibility to include new specimens.


with ability to export to Excel sheets and .pdf. The reports include but not limited to:

1- Form report where all fields in the form appear. If report is more than one 1 page,

preserve header;

2- Report by purpose of transaction;

3- Report by country of import;

4- Report by country of export;

5- Count of import/export/re-export/others by country;

6- Report by item name;

7- Report by item quantity;

8- Report by country of origin;

9- Report by country of last export;

10- Report for all permits with a combination of other fields in the screen. (Dynamic)

All reports should be between two dates.

4. Register of Agricultural Holders/Enterprises

The core application (Register of agricultural - holders/enterprises) including basic information on farmers/agricultural enterprises and integrated into all other applications. Data will include different categories not limited to Farmer Register, Farms, Factories, Aquaculture, Nurseries, Livestock and Poultry Farms, Plant Production, Bees Keeping, Fishing Vessels, Fishermen, etc.

27

Data Entry Module: Data input screen to enter all statistical information may include but not limited to:

Location of farmer land including Mohafaza, Caza, Village;

Personal information on farmer name, address, phone;

Land ownership;

Land use including areas;

Seasonal crops including crop name, code village, type, area, irrigation, marketing;

Protected crops including crop name, code village, type, area, irrigation, marketing;

Permanent crops, crop name, code village, code village, type, area, irrigation,

marketing;

Pesticides including type, amount used and cost;

Fertilizers including type, amount used and cost;

Animal resources including types of animals and numbers;

Poultry including type and farm capacities;

Veterinary Services including type, use, disease, amounts used, cost;

Use of agricultural machines including machine name, owned machines and source.

GIS location Module: Possibility to show holding GIS location by entering the coordinates of the land and linking them to Google maps. Ability to generate reports for different crop to show geographical map (GIS).

Data Migration Module: Data migration from CSPro, Excel, SPSS and production surveys to the new database is needed.

Export Module: Ability to export data to SPSS to analyze data statistically.

28

Sampling Module: Dynamic sampling report is needed where data from statistical farm register is queried according to dynamic.

Reports Module: Multiple reports including statistical, graphical and tabular data reports with ability to export to Excel sheets and .pdf. The reports include but not limited to Several Dynamic searchable and statistical reports by Mohafaza, Year, Item, Element (Area, Price, Production) with ability to export into different formats (i.e. Excel, csv) in two languages (Arabic & English).

Data Migration Module: It is recommended to export all data of all tables from CSPro to

be migrated to another database that will form the statistical farm register

Data migration for the production survey databases is needed with ability to search.

There exists data for years between 1997 and 2009. The web application must keep

history of all those data.

Integration Module: There is integration with majority of the MOA applications, because

it is the base of the farmer’s data.

Tablet Version: there is a need to develop the data entry screen on tablets to allow

users to record data on site.

5. Statistical Farm Register

A Statistical Farm Register comprising all detailed statistical-related data. The application will include all data related to statistical and agro processing information. Statistical data will be updated on yearly basis and historical data should be saved to be queried later.

6. Labelling

Dynamic web application to perform labeling for several applications not limited to Fertilizers, Pesticide and agro-processed products.

29

Follow up Module: data entry screen to follow up on labels. Several conditions are

needed to create labels. The concerned departments examine the requests and validate

the labels.

Alert Module: An alert is needed since some products may include prohibited materials.

Reports are needed to show these products with details.



Follow up on labels;

Product weight;

Shape and details;

Prohibited materials.

Integration Module: There is a need to save the final label for products to be sent later

to import/export department. Integration with inspection is needed to register the factory

and inspection on dairy products. Integration with DWF is needed to submit the request

for labelling and registering notices.

Data Migration Module: The concerned department divides data into 2 packages/

types: exported and imported. There is a need to input exported packages data that is

still on papers. In addition, imported packages data has to be migrated to the newly

developed database.

7. Gardens Management

Web Application to manage and follow up public Gardens and Roads Tree Plantation.

Garden File: A data entry screen is needed to register roads/gardens information

including two 2 parts:

Part 1 to setting the file of the garden:

Information from the Department of protected areas and public gardens:

Name of the garden;

Geographical information: Mohafaza, Region;

Contact Info: Name and details;

30

Number in the directorate register.

Information from Administrative office:

Number in the Administrative office register;

Tenders with committee names, decision number, decision date, Tender date, and result;

Supervisory committee names plus decision number and date plus date of informing the members;

Delivery (Reception) committee names plus decision number and date plus date of informing the members.

Information needed from accounting department/ Administrative office:

Date of informing Foreman.

Extension period of execution.

Extension period of delivery.

Part 2 to the application on field: starting the work, and deliver to the Ministry:

Information from the Department of protected areas and public gardens:

Date of informing the Regional Service of delivery (reception) of the site;

Date of delivering the site.

Information needed from Administrative Office /General Director Office/ Department:

Reports of the supervisory committee: Date and notes

- Report 1: Starting of works on site - Report 2: Finishing the planting task - Report 3: Supervision during management - Report 4: Final Report

Reports of the delivery (Reception) committee: Date and notes

- First reception report - Final reception report

Reports Module: Multiple reports including statistical, graphical and tabular data reports with ability to export to Excel sheets and .pdf. The reports include but not limited to: o Areas/region; o Year; o Situation of each garden; o Supervisory delivery committee (by name); o Delivery (reception) committee (by name); o Supervisory committee (date and notes) plus date of start and preliminary end of

work.

Integration Module: the application should be common between the department, Administrative office and General Director Office.

8. Fires Management

An update on current Forest Centres web application is needed to manage fires.

31

Data entry Module: A data screen form has to be developed to enter Mohafaza, Caza,

Village, area, category of fire, kind of trees, kind of use, kind of property, date, hour of

alert, hour of start of fire, hour of end of fire, equipment used, personnel number,

involved organizations and way of fighting fire.



o Mohafaza, Caza month, year, village and days;

o Hour of start and end of fire;

o Date/time of fire;

o Date/time of fighting fire per personnel and equipment used;

o Plant coverage;

o Water resources;

o Ratio of time of announcement and time of arrival to the site;

o Average time of arrival per Mohafaza/Caza;

o Ratio of time of announcement and time of arrival and time of putting off fire.

Integration Module: Networking with MOA regional offices is needed.

9. Inventory Management System

32

9.1 Stock Management System

Stock Management System must have the ability to manage quantities in and out from the different warehouses. It should also track donations and available inventory, as well as communicate with consultant s in near real-time and receive and incorporate other data, such as seasonal demands. The application should be flexible, and it must manage minimum quantity per stock item and generates alerts when this minimum is reached.

There exist three types of warehouses:

1- Two main warehouses (Kafarchima and Fanner);

2- Secondary warehouses in the seven MOA regional offices;

3- Warehouses for the four directorates and Administrative office.

There is a need to develop a stock management system to control stock in and out

between the three warehouse categories to be delivered to farmers, municipalities,

associations and cooperatives.

There are Eight 8 forms used to enter goods to warehouses:

Form 1: Goods receiving: notice with goods receiving to warehouse filled and

signed by warehouse secretary.

Form 2: Inflow of Goods: data entry screen filled by warehouse secretary to register

inflow stock to the warehouse register.

Form 3: Outflow of Goods: filled by warehouse secretary to register outflow stock

from the warehouse register.

Form 4: Outflow Receipt: filled by warehouse secretary to control out stock.

33

Form 5: Main Order Delivery: issued by general manager and goods are delivered

upon.

Form 6: Secondary Order Delivery: used to deliver stock and instruments to

ministry beneficiaries.

Form 7: Work Order: contains inventory material consumption. At end of year, an

inventory listing should be generated automatically from the system according to a

special form.

Form 8: Request for supplies and equipment: Prepared by directorate or service

to general manager to request inventory.

The application should has the followings:

- Ability to control stock and items bought from different suppliers;

- Ability to define dynamic stock items with different specifications and categories

with ability to specify the access rules for different categories;

- Ability for IT team to track inventory location and their history;

- Integrations with Extension and HR are needed.

9.2 Car & Generator Maintenance System:

A new module for cars and generators maintenance is needed. The module should include the following:

Car log file: Create a log file for cars, their properties, numbers, type and distribution.

A data entry screen to input all available cars in the ministry where all car details are

entered like directorate, service, car type, plate number.

Generator log file: Create a log file for generators, their properties, numbers, type and

distribution. A data entry screen to input all available generators in the ministry where all

generator details are entered.

Car maintenance Module: A screen to register car maintenance records where date of

maintenance and name of shop plus type of maintenance and amount paid are

registered.

Generator maintenance Module: A screen to register generator maintenance records.

Details such as date of checkups, name of the maintenance shop plus type of

maintenance and amount paid are registered.

Car oil and batteries Module: A screen to register handling of car oil and batteries. The

Ministry reserves a certain amount of oil. Each car is handled a certain quantity of oil on

a certain date. The quantity of oil handled is subtracted from the total amount of oil

owned. A screen is needed to register the amount of oil withdrawn and date in addition

to the name of employee and car number. Then employee needs to sign a receipt with

amount of oil. Same concept applies on car batteries.

34

Alert module: to alert on oil and batteries revision dates.

Tickets Module: a screen to register fuel ticket details and information. All ticket details

should be registered by car number. Also there should be a flag to show the status of the

ticket whether paid or not.

Car licenses Module: A screen to log car driving licenses (scanned copy) and their

expiry dates. A data entry screen where all details of car license can be logged and

reported later. Example: an alert on license expiry date should be generated.

Out of Service Cars/Generators Module: Ability to set cars out of service. Some cars

can be damaged due to several circumstances and thus need to be put out of service.

The application should provide the ability to put such cars out of service and then to be

reported. The out of service cars or generators should be excluded from active cars of

generated reports. Special reports for dates and history of such cars should be

developed.

Check-up Module: Scheduled checkups on cars and generators. Currently periodic

checkups are conducted on cars and generators. There is a need to remind the user that

a checkup for a certain car or generator is needed. Then the user checks the car or

generator and registers next check-up date. Each car or generator should conduct

periodic check-up.



o Car log and oil change dates and maintenance;

o Generator and oil change dates and maintenance;

o Out of service cars;

o Expired licenses and date of renewal;

o Special report like outlook for dates of oil change with ability to mark each row as

read or not read;

o Tickets and fines;

o Available oil amounts;

o Available batteries count;

o Car licenses report;

o Car or Generator details.

10. Farmers Input Support

New farmers input support web application has to be developed to monitor distribution of inputs including Feed, Seeds, Seedlings, Fertilizers, Vaccines and Pesticides.

35

10.1 Distribution Management System

Integration with Register of Agricultural Holders/Enterprises to distribute input

Data entry screen to manage item distribution: data entry screen to manage data related to item distribution.

o Data entry form to issue/register the distribution; o Ability to print and reprint the distribution report; o Ability to generate a serial number for each distribution.

Information on farmers categorized by Mohafaza and Caza

o Ability to keep track of beneficiaries. o Ability to search by beneficiary name and register number/serial. o Integration with Register of Agricultural Holders/Enterprises and statistical farm

register is needed.

Distribution Module: ability to generate distribution table. A general distribution report that can be issued between two dates. The report should be generated according to a dynamic formula. Records for each distribution should be saved and reported later.

Data migration Module: Data migration for existing data is needed. Data is available on Excel.

Integration Module: There is a need to integrate with statistical farm register and statistical reports from import/export department.

Administration Module: There is a need for two types of access rules: Admin and normal user. Admin has full privileges.

36

Reports Module: Multiple reports including statistical, graphical and tabular data reports with ability to export to Excel sheets and .pdf. The reports include but not limited to:

o Reports on all types of input between two dates; o Reports by Mohafaza and Caza between two dates; o Report of total number of all types of input between two dates.

10.2 Nurseries Management System:

There is a need to update current Seeds application to maintain MOA nurseries records

such as Mohafaza, Caza, village, responsible name, area, process of production and

many statistical reports on types of trees seedlings.

Currently there exist around ten MOA nurseries that need to be linked to the central

office. The required screens are as follows:

Nursery profile Module: a data entry screen to log in nursery data such as name,

names of employees, responsible name.

Registration Module: a screen to register nurseries details and information. Data such

as area, way of production, process of production, source of water, equipment available,

water system, owner and notes are needed to be entered per nursery

Statistics Module: data entry survey to register plant types including source, source of

seeds, planting date, quantity, percentage of growth and date and attachments of

certificate of seeds.

Distribution Module: a data entry screen to register distribution of plants, type, quantity,

name of receiver, document number and average of distribution.


with ability to export to Excel sheets and.pdf. The reports include but not limited to:

o Details on every nursery

o Kinds of plants

o Quantities of plants

o Average of height between plants

o Distribution: remaining quantities versus overall production

o Percentage comparison between nurseries in/out plants

o Certificate of source of seeds

o Comparison between nursery name, type, production process, percentage of growth,

average of height and percentage of growth and date by nursery, type by nursery

and all nurseries for every kind in all nurseries.

Integration Module: networking with MOA regional offices is needed.

37

11. Fertilizers Application

There is a need to upgrade the current fertilizers application database to SQL and to cope as for its look and feel with the other existing applications. The current application is developed using .net and Access data base.

12. Veterinary Drugs

There is a need to develop a new web application for veterinary drugs. This application can be replicated from existing Fertilizer or Pesticide application.

13. Issue Electronic Certificates

There is a need to issue electronic certificates for fruits export from current IEMS

application directly. Currently these certificates are registered on papers. These

certificates can be issued from regional offices. It is needed to develop a data entry

screen to register and issue electronic export certificates with automatic serial

generation. Several reports are needed and alerts on expiry date should be generated.

14. Pest & Disease

A new application has to be developed to study pests, diseases and ways of control.

Pest Survey: a data entry screen has to be developed to enter the details of the pest

and disease. All information should be registered with details on geographical location of

pests and diseases. Several categories of pests and diseases exist and needs to be

classified in an easy way so they can be tracked easily.

38

Distribution Module: The application has to be linked to GIS system to show

distribution and intensity of pests and diseases. The application should enable the user

to enter dynamic rules for identifying control, buffer and quarantine zones.

In addition, the application should allow users to easily identify the infected regions, and

thus to know non infected regions per country. The system needs to allow generating of

integration maps for infected regions. These maps should be generated by different

formats (polygon)

Procedures Module: the application should allow users to enter procedures taken

on every pest and register different details.

Alert Module: an alert module should be developed for new pests per group.

Search Module: the application should allow users to easily search for different

pests and categories in an easy and interactive way.

Data Migration Module: there is a need to export data to the new database after

developing the system. Data currently exists on Excel.

Reports Module: Multiple reports including statistical, graphical and tabular data

reports with ability to export to Excel sheets and .pdf. The reports include but not

limited to:

o Distribution;

o Categorization;

o Procedures.

Integration Module: the application has to be integrated with import/export,

pesticide, and statistics.

Common requirements for all developed applications:

- GIS Integration

All the applications should be integrated with GIS mapping system.

- Portal and applications language

The portal and all web applications should be developed in English and Arabic.

- Data migration

All the available data should be migrated to the new database (SQL DB) independent of its

format.

- System Administration:

a) Administration module: Allow full system administration, including system security, permissions, user creation, etc.

39

b) The project documentation and report to be submitted to MOA at the delivery in two format Microsoft Word for Windows on CD or DVD, accompanied by a hard copy. Those documents are the output of each phase of the project Methodology of Work and can be not limited to the project plan document.

c) Security Module: ASP.NET role based Security with Custom Security Module (Permission Based, Page Level Authorization).

Security is an important aspect of any application that spans physical, technological, and policy decisions and requires a high degree of planning and domain knowledge. Several techniques for authenticating users through a web form, authorizing access to particular pages and functionality, and managing user accounts in an ASP.NET application.

The portal demonstrates many features offered by the ASP.NET technology including:

- Cross-browser support for Internet Explorer, Mozilla, Google Chrome; - Clean code/html content separation using server controls; - Pages that are constructed from dynamically-loaded user controls; - Configurable output caching of portal page regions; - Multi-tier application architecture; - ADO.NET data access using SQL stored procedures or any other technology; - Windows authentication - username/password in Active DS or NT SAM; - Forms authentication using a database for usernames/passwords; - Role-based security to control user access to portal content.