ASP.net

Problem: Farm-Level Irrigation Modernization in Egypt's Nile Delta Main problems and challenges to tackle: 1- Take effective and useful feedback from farmers on different stages of the project. 2- There are different entities contributing to this project and hence interested in different kind of data and reports for example: World Bank, Ministry of Irrigation , Ministry of Agriculture and construction contractors 3- Farmers knowledge of technology is somehow limited so we need to get as much data from them with the simplest usage of technology 4- Design this solution to be scalable and act as a potential base for other big extensions to bring technology into agriculture in Egypt Core solution: First: We are planning to design customized (simple-to-read) maps for the farmers that show only important data related to his piece of land like: a) Its area and location b) Proposed location of the pipe relative to his land c) Proposed locations of hydrants These customized maps will enable the project representative to take input from the farmer and pin points the suggestions of the farmer by drawing from a tool box on the map. Along with graphical suggestions from the farmers we are willing to take other kind of data like how many hydrants he needs, when it will be suitable to implement the system and proposed diameter of pipes. Also we will take feedback from him about the cost and if he can pay in cash or not. Second: The system should be able to generate different kinds of data and reports for different interested entities like: a) Detailed maps containing all proposed suggestions by the farmers about one area to the construction contractor. b) Data about proposed timings to implement this project to the ministry of agriculture to coordinate with the construction contractors the scheduling of the project c) Statistics sent to world bank sent every certain period to update them about the progress of the surveying phase d) Details about how the farmers are willing to pay should be sent to the organization responsible for collecting money for planning purposes B.S: we are aware that all these entities will not be using or systems and they have their own systems so we will make sure to communicate all these data through e-mail and send reports, maps and figures in global formats like excel sheets, image files or word documents for being practical Third: Farmers should be able to issue a complaint about any related problem with this project in the implementation phase using simple SMS service, we will not be using mobile app. Not to confuse the farmers all he has to do is to enter a code for his land like (#42A3) every land should have a unique code known only by the farmer and he will write with the type of the problem for example if he sent: ( #32C4 3 ) the system will know the location of the land and it has a leakage problem in the pipes so it will send a report to the technical support organization responsible for fixing those pipes with the exact location of the land supported with a map. Also we will give each group of areas a unique code given to the irrigation engineer responsible for that whole area called “zemam or Marwa” to report for a common problem with the main pipe and this code should have a higher priority than individual complaints SMS will be also used to notify farmers about important dates and updates about the project to keep them in the cycle Advanced developments for this system: We can use the same system to take farmers feedback about many aspects linked to the project in order to make best use of the new pipe system and also the system will send relevant reports to the organization that is interested in such a piece of information. We categorized this info under three main categories: 1- Land: area, kind of the soil, how deep the solid layer ….etc 2- Water: water sources, is there any problem with the pipes, hours of irrigation are enough or not, when he is planning to irrigate for the first time next season, if he irrigates on day or night 3- Plant: kind of plant for next season, cycle of the plant, duration, expected bugs , harvesting time , how many times this plant needs to irrigate 4- Scheduled Irrigation: through designing this system to be generic and scalable this system could be a good base start for implementing the scheduled irrigation Benefits of using this system: 1- Farmers will be fully involved in the whole process without the need to teach them any new technology 2- Low cost: no extra hardware is needed and it can be implemented by giving the representative of the agriculture ministry a laptop in his meetings with the farmers and he can even work offline there and then send the data when he is back to the main server to compile the data 3- Practical: we will not be requiring any entity that will benefit from our data and reports to actually use our system and spend time learning how to use it. The only people who will this system is the system admin and agriculture representative, all data will be communicated by e-mail in well known formats like excel sheets, word documents and image files. 4- Easy to implement: all the intelligence is needed in the process of compiling individual data into meaningful reports for the concerned entities 5- No need to integrate the system into other system so that every entity can work with the same technology they are working with and yet benefit from the system’s data 6- As shown in the design this mechanism can be expanded to get data from farmers using the same resources (representatives, laptops and the system) and provide more important different data for all concerned entities