@SEQincidents was established during the QLD floods as a community & safety alerting tool.
The servers and equipment were cobbled together from throw away's and an extensive amount of time was spent writing the back end 'smarts' necessary to provide an accurate service and also to allow the system to be managed by 1 or 2 individuals in times of disaster when massive volumes of traffic and incidents are occurring ( a concept seemingly forgotten about by most agencies )
Over time the capability of SEQincidents has grown, the software has been updated, the smarts are continuously improved on, but the reliability has fallen, "technical issues" are becoming more frequent. This is predominately due to ailing hardware which has a tendency to fail and can take some time to attend site & restore. The server has a suspect motherboard issue and tends to hang periodically & the UPS batteries are toast. As the equipment is now many years old, refresh is in order.
The associated transmission & other hardware is more industrialised and has a much longer lifetime and is still going solid. It is the consumer/business grade equipment which is now approaching imminent failure.
@SEQincidents at a point where we need to either invest in a hardware refresh and return the project to it's former glory or retire it as the community has come to trust SEQincidents and if it is unreliable then it is not useful.
At this point we are not seeking any contribution toward operational costs. Our first objective is to refresh the hardware and return the platform to a reliable trusted community resource without "technical issues" .
Any contribution you can make to this project is greatly appreciated.