Although I am not directly involved in HAVC, I hope you will be able to assist.
I am part of a volunteer committee responsible for our church/temple building maintenance. We are a poorly funded non-profit with a VERY limited budget for things like support contracts and such. We do pay for contracts on our HVAC and building security systems. The office manager is well intended but has absolutely no experience in building mangement. The building is about 6 years old.
We have one stand alone PC connected to a control panel that runs the HVAC and lighting for our building. It is using the Delta Controls OrcaView 3.22 software with a dongle. A couple members of our committee learned from the original installer how to use the control software to schedule lights goings on/off and how to set the proper HVAC temperatures and schedules. I am most worried about the single point of failure of this one PC and also about the limitation of needing to be physically in front of that one computer to make any changes. There are frequest events where we rent out the social hall and require last minutes changes to the schedules. One of our volunteer committee must then drive to the building and make changes in person - day and night.
Please do not consider this a DIY question because I certainly see the value in trained technicians and the role they play. My questions are related to the responsibilities of the building owner/maintainer.
1. Is there some list of ongoing responsibilities for an owner of a building automation system like this? (activities that may include things like PC backup, regular service or maintenance for batteries - if there are any, HVAC & lighting system data backup, regular software updates)
2. Is there a breakdown for the roles of the HVAC technician versus the building maintenance staff as it relates to managing automation systems like this?
3. What type of remote access would be recommended to allow our volunteer crew to manage the system remotely? We were thinking of putting the single PC the web and then using a remote control software program. It seems like automation software should have accounted for this need already without us having to solve this problem.
Any help you can offer would be welcomed.