At a team competition, the runners of each team start together. The start list is drawn like for individual events so that all teams are starting with an equal start interval. However, mass starts are also possible. OE12 supports two team event types: Teams with normal courses and Teams, courses with distributed controls. The latter is described here.
Each team runs a normal O course (obligate controls). Additionally there are distributed controls. Each runner in the team must visit the obligate controls. The distributed controls have to be visited by at least one runner. Thus, the team has to find a solution how to distribute the team controls in the best way according to their expected individual performances. The goal is to finish as close together as possible. The time of the last runner counts for the team result.
OE12 V12 supports several methods which differ in how the obligate controls will be computed.
The obligate controls must be punched in the predefined order like a normal course. Distributed controls can be punched inbetween.
Each runner must punch the first obligate control as the very first one and the last obligate control as the very last one. All distributed controls which had been punched before and afterwards, will not be counted.
This method is used in Germany for team O championships.
This method is nearly the same as the German method. The difference is that it is allowed to punch distributed controls at any time, also before and after all obligate controls.
This method got its name from the Harris event, which is held every year by the British Army as a part of their O championships.
There is no predefined order for the obligate controls. Every runner can punch them in arbitrary order.
OE12 covers those methods by special functions which are only active for this special event type, for example course definitions, code checking, chip evaluation and results.
This event type had formerly been computed by OT2003 (OLTeam) V10.