OpenRun Horse Show Management Software

This will be a first iteration on a suite of horse show management software. The software itself will allow entry of horse and rider combinations, track progress across multiple events, and implement point tracking via ranking. More requirements will be provided during feature scoping. It would be good if the software could be built on open architechture and cross platform. Ideally Linux, Mac, Windows.

OpenRun shall be a suite of software for Barrel Race / Gymkhana management. The software will be Open Source GPLv3 license. The initial iteration will focus on Barrel Racing as one component of the software and will move into Gymkhana in a second iteration as the scope of barrel racing will be much smaller.

Rider demographic information to collect in OpenRun:
First Name
Last Name
Horse Name as Registered
One rider may have many horses.
Horse Name as Barn Name
Age ( According to Race Rules )
Number of Races Entered ( Open 1, Open 2, Youth, Novice, etc… )
Races shall be created in a separate setup.
One rider may have many races.
Rider may carry a ride time to any race by flagging that event as a carry. For example ( Carry open barrel race time 1 to open barrel race 2. )
Optional Rider SSN or TAX ID for Charitable Gifting

Event information to be gathered:
Type of race event ( Barrel racing, pole bending, etc… there are many should be customizable by the user. )
Type of timing. The timing style may be 4D based… IE
Fast Time is Division 1
Fast Time + .500 seconds is Division 2
Fast Time + 1.5 seconds is Division 3
Fast Time + 2.0 seconds is Division 4
An alternate style of timing would be fixed time breaks. IE the user enters the divisions A, B, C and provides the break offs for each category. The system shall do some input sanitization to ensure users may not enter non-contiguous time ranges.
Events should populate to the Rider demographic and entry screen.
Events should also take an integer that is the number of riders to progress before each rake.


Event run mode:
The software shall have an “event run mode” that begins an event selectable by the operator. The run for the event shall be random in order for each event. The exception being riders on multiple horses. The software shall recognize one rider entered on two horses in the same event and provide a 10 rider separation at least.
The software will allow time entry for each rider in decimal format to the thousandth. IE ( 19.999 ) . The software will advance to the next time box automatically by pressing the enter key. The software will allow manual advancement to any rider in a set by pressing the arrow keys. Time box should also take Scratch, NT, Down Barrel, and DQ to indicate a no time. No points shall be awarded for these entries.
Times should have a box that allow the ability to “carry” or automatically transpose the riders time to the next race in place of a ride on request via a check box on this dashboard.
Late riders should be able to entered after event has begun and dropped to the bottom of the race. The order of go should also be re-arrangeable manually in needed by dragging.
Every nth line should be highlighted to indicate a rake using the data provided in the number of riders per rake. This could be done with a large dialogue that stops all data entry and demands a rake from the operator. The dialogue could display sponsor information or announcements to be read during said raking.

Placing information per class:
Placing data should be generated first by division and then by time.
Placings are per event. Day cumulative points are awarded to each rider on a 10-point scale. Don’t forget there could be multiple age divisions and also an open division.
A day high point report for each division should be generate-able on request.


Out and out Gold Plating:

SMS Integration - Provided a rider has an SMS number entered in the system using an internet connection or some other means notify the rider via text message ‘n’ riders before it’s their turn. Optional SMS to all participants at event changes and major milestones.

Batch Load Feature - Batch load riders.

Season Tracking - Track points per rider over the course of a show series and provide a series long ranking system using either 4D ranking or Division based.

Split Timing - Be able to flag riders that have paid an additional fee to be entered in a “virtual” race that using a different division system. This will be a half second off of the 3D payout if timing styles is 4D (1.5 seconds off of the winner). People will pay an extra $10 if they want and that money will go into the pot of money for them to win back.

Web Companion Component - The web component would allow pre-registration that was bulk loadable into the application on show day. The web component should advertise all event dates and allow opening and closing registration on demand. The web component should take some form of payment via credit card.

Java Python Software Architecture

Project ID: #5809483

About the project