Zone4 with CCBC

1 minute read

Overview

The web version of Zone4 and accompanying Go Chips system is a large change from what many are used to using to time cross-country skiing and other sports in British Columbia. This site will help give some best practices and pointers for how to use the software in a well-known consistent manner throughout the province.

Please note that Zone4 is always changing and improving their software, and content here may become out of date. They have a great help system of their own over at Zone4 Help.

Registration

The first step to running a race is getting people registered.

TODO

  • Create a registration page
  • Create a race
  • Setup start groups
  • Create the start list and post it online

Pre-race setup

Zone4 allows you to do quite a lot while the race is in progress, but it’s still best to be prepared and get some things setup beforehand.

This covers: race settings, racer groups, start lists, and courses.

Hardware

Including information on different hardware requirements for different types and size of races, as well as the new GoChips, activators, and phones.

Day of - setup

Includes discussion on network setup and configuration, the physical setup of the timing equipment, and chip distribution.

More TODO

  • Server box
  • How do Summits fit in?

During the race

This covers configuring timing devices and courses, setting up result sets, announcer views, and actually timing a race.

Document resources

Run sheet

Run sheet - describes tasks done by different teams throughout the race

Volunteer assignments

Volunteer assignments - different roles required

Timing diagrams

2018 Payak timing diagram - chips but no Summits

Other resources

  • As mentioned before, try the Zone4 official help pages first: Zone4 Help.
  • Contact an experienced volunteer: @alarobric on Github, Twitter, Facebook, etc. has done timing for many races at Whistler and Kamloops, and can also put you in contact with others in the province. Let me know if you’d like to be a resource here also.

Contributing

Contributions to this documentation are welcome. If you’re comfortable with Github, feel free to send me a pull request with your changes, otherwise you can open an issue on Github with your suggestion, or even just send me an email with your change.

Github source