\subsection{System Maintenance and Support} \begin{itemize} \item Organizational Responsibility: \begin{itemize} \item During the interaction with the system, farmers or users should not be exposed to more than 12 V or face potential hazards. \item Record the vendor insurance information on the system so users can access them anytime. \item The User is responsible for the upkeep of the software stack of the system. There are two stacks of software which are system software and community software. The system software is rarely updated, is used to power the system, and connects all external systems such as sensor nodes and power systems. Community software is supported and provided by an open-source community. At the time this system is built, it only performs the features expected as in the requirement mentioned above. If users prefer the newer version of community software, they have to provide an internet connection and perform the update manually. Refer maintenance level level for further guidelines. \end{itemize} \item Maintenance level: To maintain and sustain the system the following procedures are required. \begin{itemize} \item For corrective maintenance: Calibrate the interval of sensors to produce data when missing data is found over months. \item For preventive maintenance: System is exposed to UV environment, apply weatherproof coating paint every 5 years. Inspect potential leaks that can damage the electrical system. Because the system is mounted 4ft from the ground, inspect the foundation to know if it can be safe from falling. \item For predictive maintenance: Although this is introduced a new level of complexity, if the changes in of component of system rapidly, consider establish a guideline. "A supervised method to detect faults was proposed by [20]. The approach assumes that the correlation between the variables of the system changes due to equipment’s failure." \item If the system is damaged by collision with the environment check the deformation that makes the system not waterproof or rainproof. \item System should have an indicator to describe the level of error such as LED blinking, beeping signal, and display of error on devices. \item If the power system fails to support the system 24/7, inspect the equipment. \begin{itemize} \item For the solar system, adjust the angle of sunlight or consider moving the system to a new location, avoiding shade level. Inspect if the system can produce enough energy to support computer components. \item For the wind system, check the charge controller voltage to see if the turbine can produce enough electricity. \item Revise the system, routinely to make sure the battery is operating in a safe environment to ensure charging and discharging. \end{itemize} \item There are software updates for computer systems. Users are responsible for providing an internet connection to provide over-air updates. There is a potential risk that new updates can brick the system and may require the user to re-install the system at the bare-bone level. While a fall-back mechanism might be provided, consider backing up the system if the new update fails to operate. A backup utility would be provided for the backup system. Please note that the utility would be built into with system therefore, the system must be in operation to perform backup. \end{itemize} \item Repair Policy: \begin{itemize} \item The following parts can be repaired: soil sensors, computer system, and system enclosure. \item The following parts should be replaced: the weather station system, the battery for the solar system, LED bulb. \end{itemize}