LANDSCAPER INTEGRATION

Abstract

A system and method for providing landscaping integration into a watering system or water management system. The system may include a processor with programmable landscape events or pre-programmed landscape events. A user may select or enter in landscape events to manipulate a watering or irrigation schedule based on the landscape event. The system may also be pre-programmed to a landscape event based on recurring or scheduled events to alter watering or irrigation. A landscaper may access a system on an electronic device that may be linked to a cloud based platform for managing the system or systems to allow for alteration and manipulation of watering and irrigation times and durations based on landscape events.

Claims

1. A method for irrigation management, comprising: identifying that a landscape event has occurred, the landscape event identified from a plurality of landscape events; based on identifying the landscape event, initiating an event watering schedule for the landscape event, the event watering schedule different from an original watering schedule; adjusting the event watering schedule; and after completion of the landscape event, returning to a new watering schedule or the original watering schedule.

2. The method of claim 1, wherein identifying that the landscape event has occurred includes receiving an input from a user that the landscape event has occurred.

3. The method of claim 1, further comprising receiving an instruction to adjust the event watering schedule.

4. The method of claim 3, wherein receiving the instruction to adjust the event watering schedule includes receiving an input from a user.

5. The method of claim 1, wherein adjusting the event watering schedule includes adjusting the event watering schedule based on a weather-related event.

6. The method of claim 1, wherein adjusting the event watering schedule includes adjusting a time not to water a specified landscape area.

7. The method of claim 1, further comprising identifying the completion of the landscape event based on an input from a user.

8. The method of claim 1, further comprising: preparing a notification including the landscape event, the event watering schedule, and the adjusted event watering schedule; and sending the notification to a user.

9. The method of claim 1, wherein the plurality of landscape events includes at least one of new flowers install, tree planting, tree install, altering the landscape, shrub planting, shrub install, pruning, gardening, weeding, sod install, grass see install, lawn mowing, lawn service, plant service.

10. The method of claim 1, further comprising: receiving a customized landscape event; and adding the customized landscape event to the plurality of landscape events.

11. An irrigation system, comprising: a processor and memory, the memory including instructions which, when accessed by the processor, cause the processor to: identify that a landscape event has occurred, the landscape event identified from a plurality of landscape events; based on identifying the landscape event, initiate an event watering schedule for the landscape event, the event watering schedule different from an original watering schedule; adjust the event watering schedule; and after completion of the landscape event, return to a new watering schedule or the original watering schedule.

12. The irrigation system of claim 11, wherein identifying that the landscape event has occurred includes receiving an input from a user that the landscape event has occurred.

13. The irrigation system of claim 11, wherein the instructions further cause the processor to receive an instruction to adjust the event watering schedule.

14. The irrigation system of claim 13, wherein receiving the instruction to adjust the event watering schedule includes receiving an input from a user.

15. The irrigation system of claim 11, wherein adjusting the event watering schedule includes adjusting the event watering schedule based on a weather-related event.

16. The irrigation system of claim 11, wherein adjusting the event watering schedule includes adjusting a time not to water a specified landscape area.

17. The irrigation system of claim 11, wherein the instructions further cause the processor to identify the completion of the landscape event based on an input from a user.

18. A method for irrigation management implemented at a cloud-based watering management system, comprising: receiving, from a user device, an implementation of a landscape event; identifying an event watering schedule based on the landscape event; implementing the event watering schedule on an irrigation system, the event watering schedule including a duration to water and not to water a landscape area affected by the landscape event; receiving, from the user device, an adjustment to the event watering schedule; based on the adjustment, changing the event watering schedule; implementing the changed event watering schedule; and after completion of the landscape event, returning to a new watering schedule or an original watering schedule.

19. The method of claim 18, further comprising identifying the completion of the landscape event based on an input from the user device.

20. The method of claim 18, wherein implementing the event watering schedule includes sending instructions to a controller connected to the landscape area.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0011] FIG. 1 illustrates a schematic of a watering management system with controllers, zones a processor an electronic device and a user interface;

[0012] FIG. 2 illustrates a schematic of an embodiment of a processor with an input function, a control unit, memory, a logic unit and an output function;

[0013] FIG. 3 is a process flow diagram which may be used by the processor of FIG. 2;

[0014] FIG. 4 is an alternative process flow diagram which may be used by the processor of FIG. 2;

[0015] FIG. 5 illustrates a user interface of FIG. 1, which may include a “pop up”, to enter a landscaping task that a user may choose;

[0016] FIG. 6 illustrates a sample list of tasks or reasons from a drop down menu for a user to enter into the interface of FIG. 5; and

[0017] FIG. 7 illustrates is an alternate embodiment of the interface of FIG. 5 for a user to enter a landscaping task or event into a system.

DETAILED DESCRIPTION

[0018] Referring in general to the accompanying drawings, various embodiments of the present invention are illustrated to show the system and methods for a watering system. It should be understood that the figures presented are for illustrative purposes only and do not represent actual views of any particular portion of the actual embodiment structure , but are merely schematic representations which are provided to more clearly and fully depict embodiments of the system and method.

[0019] The following provides a more detailed description of ways to implement the present system and method and various representative embodiments thereof. In this description, functions may be shown in block diagram form in order not to obscure the present disclosure in unnecessary detail. It will be readily apparent to one of ordinary skill in the art that the present invention may be practiced by numerous other solutions.

[0020] In this description, some drawings may illustrate signals as a single signal for clarity of presentation and description. It will be understood by a person of ordinary skill in the art that the signal may represent a bus of signals, wherein the bus may have a variety of bit widths and the present invention may be implemented on any number of data signals including a single data signal.

[0021] FIG. 1 illustrates an irrigation or water management system 10, or system) for remotely managing one or a plurality of watering systems. The watering management system 10 includes a cloud based platform 12, or central computer, with a processor 14 in communication with a single or a plurality of individual, remotely located watering systems 16, 18, 20. Each watering system 16, 18, 20 may include a controller for controlling the application of water by the watering system 16, 18, 20 at one or more stations corresponding to a particular portion or area of the watered landscape. Each watering system may be controlled by the owner, leaser, landscaper or other supervisor of the landscape. While each specific watering system may include its own controller each controller receives signals, either wired or wirelessly, from a central computer or cloud based platform 12 processor 14 to perform certain functions via a software interface or user interface 24.

[0022] The cloud based platform 12 may be a processor 14 accessible using the Internet or a system accessing the cloud using the Internet. While FIG. 1 illustrates the cloud based platform 12 as a single computing device, in certain embodiments, running software to execute the irrigation of a landscape. The cloud based platform 12 and processor 14 may play host to a plurality of watering systems each with their specific parameters for watering while not requiring a specific cloud based platform or server for each different watering system and access is only granted to those specific users needing access to their property while not having access to other’s watering systems. However, it will be appreciated that a plurality of separate computing devices working together may provide the features described herein. In another embodiment, the cloud based platform 12 is a desktop processor running software to implement the methods described herein.

[0023] The cloud based platform 12 once accessed may include the user interface 24 that allows users to access one or more functions of the watering system. The user interface 24 may be a graphical user interface (GUI) that runs on the cloud based platform 12 and allows a user to interact with the cloud based platform 12 through an electronic device 22, which may be a computer, tablet, phone or other computing device that may have wired or wireless access to the cloud based platform 12 via a communication link 32. The user interface 24 may also include one or more application programming interface (APIs) that allows one or more computer programs to access the functionality of the processor 14 of the cloud based platform 12.

[0024] The cloud based platform 12 may store specific information about each watering system 110, 112, 114. Such information may include specific information about each station in the watering system (e.g., the type(s) of valves, the number and type(s) of sprinkler heads on each station, etc.). In addition, the cloud based platform 12 may store information on the area, topography and type(s) of landscaping covered by each station of the irrigation system 16, 18, 20.

[0025] The cloud based platform 12 may also communicate with one or more watering systems 16, 18, 20. The watering systems 16, 18, 20 may include controllers within each watering system 16, 18, 20 the controllers communicating with the watering system 16, 18, 20 itself or the controllers may communicate with the cloud based platform 12 itself. The watering system 16, 18, 20 communicates with the cloud based platform 12 using communications links 26, 28, 30. The communications links 26, 28, 30 may be wired communications links (such as telephone, or Ethernet connections), wireless communications links (such as Wi-Fi, cellular, radio frequency or other), or a combination thereof. The controllers may communicate information with the watering system 16, 18, 20 which then may relay that information to the cloud based platform 12 using an appropriate communications protocol such as TCP/IP. Each controller may communicate water flow information from each station of the watering system 16, 18, 20. In addition, the cloud based platform 12 may be configured to receive information about the amount(s) of non-irrigation water (e.g., precipitation, water from nearby sources, etc.) to which one or more parts of the landscape to which each station of the watering system corresponds is exposed. Such information may be collected in any suitable manner known in the art (e.g., with automated rain sensors, etc.). The information, after gathered, is implemented into the software which executes commands or executes questions for the user to interact with to either automatically or manually adjust the watering system based on the new criteria.

[0026] In some embodiments, the cloud based platform 12 may also collect climate information which integrates into the software to execute certain protocols based on the information gathered. The climate information may include weather forecast information (e.g., temperatures at various times of the day, humidity forecast, cloud cover forecast, precipitation forecast, etc.) and/or real-time weather data (e.g., current temperature, current humidity, current cloud cover, current precipitation and up-to-date precipitation levels, etc.). Other types of information may also be stored and/or collected by the cloud based platform 12.

[0027] The software in the cloud based platform 12 may also be configured to implement an irrigation management plan that includes irrigation programs for each of the stations in the watering system. The irrigation management plans may be unique to each watering system 16, 18, 20. In other embodiments, the irrigation management plans for like watering systems (i.e., those with similar landscapes) are the same. The software of the cloud based platform 12 may communicate the irrigation management plan to the controllers for each of the irrigation systems 16, 18, 20, which controls then implement the irrigation management plan at the location.

[0028] The user may log in to the cloud based platform 12 via any computer, laptop, tablet or smart phone or the like. Logging into the cloud based platform 12 may enable a user to manipulate the settings and change controls of the watering system, enter in an event for the landscape that is pre-programmed into the system to manipulate a watering schedule, which may be an original schedule, a standard schedule or the reversion schedule, to accommodate the landscape event, or implement a new irrigation plan or any other variation. The user, after logging in, may also be able to permit other users to access the watering system(s) on the cloud based platform 12 to allow multiple users the ability to manipulate the watering system.

[0029] In addition to including a cloud based platform 12 and a plurality of remote irrigation systems 16, 18, 20, a watering system of the present embodiment may include one or more mobile devices that communicate with the cloud based platform 12. Each mobile device may comprise a portable electronic device of a type known in the art, such as a smart phone, a tablet computer, or the like. The mobile device may access the cloud based platform and display notifications requested by the user regarding each monitored irrigation system 16, 18, 20 from the cloud based platform 12 and, in some embodiments (including embodiments where the cloud based platform 12 automatically controls the monitored watering systems 16, 18, 20 and embodiments where the cloud based platform 12 does not automatically control the monitored watering system 16, 18, 20), to enable remote control over each monitored watering system 16, 18, 20 either through the cloud based platform 12 or directly.

[0030] In one embodiment, applications for mobile devices may also be configured to receive reports from the cloud based platform 12 of a landscape event and the adjustments implemented by the system accordingly. For example, the property owner may have a mobile device with an application for receiving reports concerning landscape events and changes in watering schedule from the cloud based platform 12. Where the property owner has multiple properties to manage a single access to the cloud based platform 12 can allow the user to access each location with a single device and single recurring fee. The property owner may be able to consolidate reports, notifications, alerts and the like for the multiple properties.

[0031] In another embodiment, the user may be able to enter commands beyond the pre-programmed landscaping events for the entire system or for each specific controller into the application, which commands are sent to each respective system and/or controller. The user may be able to override the irrigation management plan using the application. The user may, for example, cause the controller to perform extra watering for a particular station using the application on the mobile device after a landscape event has prevented the watering of a specific zone. The application may provide for automatic or manual return to previously programmed watering schedules based on the logic feedback by the user or the watering system itself. The cloud based platform 12 may report the completion of landscape events or return of typical watering schedule or an adjustment to a watering schedule based on the landscape event. A user or an irrigation manager, can take such information into account in determining the cost effect of user-directed watering. The cloud based platform 12 may similarly track user-directed watering events that are initiated from a controller. An “irrigation manager” is an individual who may install, service and program the watering system for a user. A “task manager” is an individual in charge of the landscaping event.

[0032] For purposes of this disclosure a “landscape event” can be any event involving landscaping, including, but not limited to, new flowers install, tree planting or install, altering the landscape, shrub planting or install, pruning, gardening, weeding, sod or grass seed install, lawn mowing, lawn and other plant service(s).

[0033] FIG. 2 illustrates the processor 14 and flow of information to, within and out of the processor 14. An input 34 may flow into the processor and such input may be a plurality of commands that may be pre-programmed or may be programmed directly to input the processor 14. The input 34 may come from a command from a user or from a sensor within the watering system 10. The processor 14 may include memory 42 that maintains pre-programmed information including commands and schedules based on the inputs coming from the user or irrigation manager. The memory 42 may also be able to maintain and store new commands that input new instructions to the processor based on user input. Likewise the processor may “learn” from the inputs from a user to manipulate the programs and pre-programmed material for future interfaces by the user with the processor 14.

[0034] The processor 14 utilizes the programs in the memory to go through the logic unit(s) 40 that then signal the control unit 38 to output 36 a command to a controller of the watering management system 10.

[0035] FIG. 3 illustrates a possible configuration of logic 100 that may be carried out within the processor to control the watering management system 10 and its setting in response to input 34 from a sensor or a user. The processor 14 may start the logic (102) by receiving an input 34 from a user or sensor, retrieve a pre-programmed landscape event (104) from the memory 42. In the case of a user or sensor input 104 the input may include watering times, specific watering zones, or sprinklers, and watering amounts. A user may be required to input specific information in relation to the event input if not already maintained or stored in the memory 42.

[0036] The task manager may receive notification of a landscape event (106) and may manually override the program or pre-programmed schedule or may accept or agree to the landscape event (108). Alternatively the processor may notify a task manager (106) and then proceed immediately to initiate the watering schedule based on the landscape event (108); or the processor may not notify the task manager and proceed immediately to initiate the water schedule based on the landscape event (110). The landscape event may include a predetermined time to water or not to water a specified landscape area that may signal through the processor for those predetermined times and then result in reversion back to the original schedule after the predetermined scheduled landscape event (112).

[0037] Alternatively the landscape event may provide an adjustment in watering that remains (114) and a notification may be sent to the user or task manager of the new schedule (116). The notification being sent to the user (116) is a step which may be utilized once, multiple times or may be skipped entirely. Such new schedule could be a schedule of watering on “off” days, watering at night, or discontinue watering all together. After the landscape event is complete a user may enter the completion (118) into the watering management system 10 that processes through the processor 14 signaling the controllers to return to the normal irrigation schedule (120). Furthermore, a landscaper may be able to input details of the landscape event that took place such as duration, number of man hours, landscape event specifics and even costs.

[0038] Referring to FIG. 4 a separate logic sequence 200 may be carried out within a processor to control the watering management system 10 and its settings. A watering system may be manipulated by a user or landscaper or may be automatic based on predetermined events (200) and may be retrieved from the watering system (202), which includes the user interface 24, or where a drop down tasks menu 44 provides the landscape events that may be stored on the memory 42 of a processor 14 already pre-configured. The access to these landscape events may be on a mobile application or through other electronic means on a tablet, computer or the like. The landscape event is identified from the predetermined events (204) and may be chosen from a list of events 46 (refer to FIG. 6). The processor 14 may initiate an adjustment in the watering schedule (208) and provides an output signal 36 to the controllers of the watering management system 10 to adjust the watering schedule in conjunction with that controller (210). Multiple controllers may be manipulated from a single output signal and each signal may be the same or may be different depending on the location of the controller and each respective zone of that controller. The processor 14 may then send a signal after a predetermined time based on the landscape event to each respective controller to return to the previous watering schedule (212) or in other words, revert to the schedule the watering management system 10 was utilizing prior to the landscape event.

[0039] Referring to FIGS. 5-7, tasks may be predetermined and scheduled within the processor 14 such that a user can manipulate the user interface in a manner as easily shown in FIGS. 5 and 6. Referring to FIG. 5, a user may provide dates and times 48 as well as zones affected 50 (from a drop down menu or manually entered) in addition to the reason or task menu 44. The task menu 44 may be the only input utilized and then “added to schedule” 52 by a mouse click or double click or finger swipe or other means in the art for signaling the processor from a mobile or computer device.

[0040] Referring to FIG. 7, a user may manipulate the landscape events or create new events that may be retained in the memory 42 of the processor 14 or may create a one-time landscape event that is not retained in the memory 42. A user may “add a task” to the watering management system 10 by entering in a description 54 as well as a schedule 56. The schedule 56 may be one time, recurring or whatever the user enters into the system 10. A user may also, for the owner’s benefit, provide a cost 58 that may be associated with the owner’s utilization of the system for monitoring and tracking water usage as well as landscape events. A user may further enter zones affected 60 and or controllers affected and then the user sends a signal to the processor by “add to schedule” 62 which is easily entered by a mouse click or double click or finger swipe or other means in the art for signaling the processor from a mobile device or computer device.

[0041] It will be appreciated that each watering system 16, 18, 20 may include a controller, a plurality of controllers as well as a plurality of irrigation sprinklers which may include drip lines, large sprinklers, small sprinklers, mist systems or the like. In certain embodiments, the irrigation manager, owner, landscaper or other authorized users may make changes to the tasks and the watering management system 10. The system may also provide for a user to input pictures or a change in the landscape into the system 10. In the event of a change in landscape into the system the user can input the landscape, similar to how the user input the landscape event, to provide adjusting watering times and durations based on the new landscape. In this instance after the landscape event is complete the processor 14 may be notified of the change of landscape and provide and output 36 to the controller for that portion of the landscape and those the watering information may not revert to the previously scheduled times and durations (i.e. previous watering schedule) because of the changes in landscape.

[0042] Although the foregoing description contains many specifics, these should not be construed as limiting the scope of the invention or of any of the appended claims, but merely as providing information pertinent to some specific embodiments that may fall within the scopes of the invention and the appended claims. Features from different embodiments may be employed in combination. In addition, other embodiments of the invention may also be devised which lie within the scopes of the invention and the appended claims. The scope of the invention is, therefore, indicated and limited only by the appended claims and their legal equivalents. All additions, deletions and modifications to the invention, as disclosed herein, that fall within the meaning and scopes of the claims are to be embraced by the claims.