Definitions

In BBT we work with the following timing concepts.

• Event: You can consider an event in BBT as a project or file that you open for each event/race that you want to time. You can only have one event open at the time. Each event may have one or more races
• Race: A specific race within an event. For example the same event could have a 5 km race, a 10 km race and a halvmarathon race
• Wave: Each race can have one or more waves. For example a big MTB race might have only one race, but the participants are split into multiple waves, that have different gun times, to spread them out on the course.

• Location: Represents a physical location at which you collect timing data. For example you might have a single location you call 'Start and Finish', where participants cross both at the start and finish. Or you might have seperate locations, as well as a number of intermediate points. A location can then be assigned one or more timing units, that physically are placed at this location. You may name the locations however you want.
• Timing point: A physical location can be used to record multiple timing points/intermediate/splits/lap. For example a single location called 'Start and finish' could be used to record both the start time and finish time of participants. In this case you would create two Timing Points, e.g. Start and Finish.
• Timing Unit: An electronic device that records the time each participant crosses it. This can take make shapes and forms but is usually a timing box connected to some kind of antennas or mats, reading the tags or transponders placed on each participant.
• Raw time: A reading received from a timing unit. Basically a tag (chip code) of the transponder/chip that was read, and the exact time of the passing
• Computed time: A computed time is the output of all the rules of BBT, based on the raw times. For example the computed finish time could be the difference from the raw time from the Start timing point and the raw time from the Finish timing point.