We’re wanting to provide you with the latest update and status on the gate/lighting issues being experienced by some ‘Book a Court’ venues.
Where can I find the last update about these issues?
Click here to see our previous communication in June or click here to see our initial communication in March.
Latest Update:
We had hoped to provide you with an update expressing further progress to the resolution of the gate/light issues, however we’ve come across some barriers preventing us from doing so. The barriers are related to the complexities of ClubSpark (software) changing the booking data files and meeting the necessary requirements and rules set out by Complete Security Solutions (hardware).
In our previous update we advised that testing of the fix had commenced, however our results of the fix were not satisfactory (i.e. gates/lights would not operate as per current functionality). After several changes and attempts to get it right, we unfortunately were not getting the results we required.
With these results and further discussions with ClubSpark and CSS, our approach and plan to deliver this solution has pivoted. We will now work towards an Application Programming Interface (API) integration between the two parties to send/receive booking data. Our current method for sending/receiving booking data is via File Transfer Protocol (FTP) – which the formatting and process of the files is where the underlying issue is.
Moving from FTP to API integration is quite a big shift and may then take us more time to deliver the permanent resolution, however all parties have agreed that this is the required step to take to not only fix this issue, but also for future improvements and enhancements of the Book a Court system.
Our early discussions with the API integration is quite promising in regards to the opportunities that it will be able to provide when we get this right. With the API integration, we’re likely to significantly reduce the “booking delay” more so than what we could’ve achieved via FTP.
Another helpful part to this pivot to API integration is that ClubSpark have previously worked on an API integration (Tennis NZ) with the same system utilised by the hardware, so provides us with some confidence that we will be able to push pass the barriers and deliver what is required. In saying this, the requirements for the integration used in Tennis NZ is not like-for-like and therefore will still require ClubSpark to design and build to our specifications (to ensure we retain all existing functionality), which is where a lot of time can be spent.
This week, CSS have commenced building the “test” environment for the API integration, which is likely to be completed before the end of next week. This will then allow ClubSpark to start pushing their existing API integration (used for Tennis NZ) to that environment and then be able to understand the work involved (and timelines) to build the integration to our requirements and the framework provided by CSS.
We want to assure you that we’re doing everything possible (within our control) to deliver this solution as early as possible and we apologise for the inconvenience this may be causing you and the players at your venue.
As previously mentioned in our last update, if your venue is being heavily impacted by these lighting issues we have the option to automatically activate lighting for fixed days/times (set by the club) that may alleviate some pressure/inconvenience being experienced by you as a volunteer/admin. For more details about this alternative option, please email [email protected] and we can discuss the possibilities of providing you with this option.
A reminder to report any issues for our team to investigate and confirm that it is related, please ensure you provide the following information to our Customer Support team via email on [email protected] or call 1800 752 983 with all the necessary information.
- Your club and contact details
- Explanation of what happened (e.g. “court 1-4 lights went out at xx, but should have remained on, light switches were correctly set to AUTO”)
- Details of the booking impacted (i.e. booking contact, times, dates)
- Other details we may need to know (e.g. “no other booking was impacted” or “lights worked perfectly on court 1”, “this occurs only on a Monday”)
Thanks again for your patience and understanding of this matter.