TIMING & DATA TECHNICAL REPORT ver 7.2. Timing & Data Technical Report is required for all scored events – USSA & FIS. It is also required for USSA non-scored Championship events, e.g. U12 Championships, Masters Championships.
Timing & Data Technical Reportis required for all scored events – USSA & FIS. It is also required for USSA non-scored Championship events, e.g. U12 Championships, Masters Championships.
(This part of the presentation addresses the paper copy of the report which can only be used for non-FIS events.)
USSA Transmittal #:
Alpha character + 4 numbers assigned by USSA and used only for non-FIS events.
FIS CODEX #:
FIS events use 4 numbers assigned by FIS; FIS-supplied software must be used to generate the report and to use the FIS online reporting system. Software also generates a PDF copy for signatures/required packets. (Details at end of presentation.)
Location:As listed on website
Event:* Type of race: DH, SL, GS, SG, AC
Event Name: As listed on website
Gender:* Ladies or Men
Date:Actual date of event
*“Check Boxes” enabled!
This information must be accurate; equipment must be currently homologated!
Sys Timer A
Sys Timer B
Finish Cell A
Finish Cell B
Brand: Name of Software
Version: Version used by timing & results computers
Date: Date of version used – not date of event
Results = Tapes: Confirmation that assigned times = printed timing tapes
How do we communicate signals/data from Start to Finish?
How is voice communication handled between Start and Finish?
At what time is the run scheduled to start?
Were all Results from system A?If you answer “NO”, you must list any or all bib numbers – in all runs – where an assigned time was obtained from any system other than system A (indicate run).
WHY? List the reason:BatteriesSnow obscurationWire break
Photocell alignmentOther? (describe)
Data source for replacement system A time (resp. ACR 611.2.1)?What did you use?System BSystem CManual
NOTE: If Replacement Time (EET) calculated, include calculation worksheet(s) with this form. (Sent to TWG representative.)
Race result XML and TDTR XML files must be submitted prior to filing online TD Report!
Versions 2.1.2 / 2.1.3
*Please verify you are using the most current version of the software!
(Edited XML from prior season’s event used for this presentation.)
Select OS & Download
Select Option & Continue
Select Option & Continue
Select Storage Location
Go Back to Change Preferences, Install or
Finish Installation & Launch Software
Event Information as listed on applicable website for level of event
Officials’ names as listed on applicable website for level of event (name on FIS site may be different than that listed on USSA site, e.g. Randy Rogers on FIS and Randall Rogers on USSA!)
Start online update devices
Note date/time for Update devices
New Version Information (Uninstall/Re-install may be required.)
Insert ALL “Timekeeper” Defaults & Save
Select “Timing Devices” Default Choices & Save
Check for device updates!
This is not the same function as “NEW VERSION”
Insert ALL “Program Options” Default Choices & Save
Dropdown boxes for equipment brand and model selections
Homologation number automatically inserted
You must insert Serial Numbers!
Additional selections & continue
(Select “Other” if your software not listed.)
Drop down boxes make it simple!
Prior to “Finish”,
Software will prompt for all error corrections!
“NO” is selected; information required.
Can add / delete / select, as needed.
Drop-down Selections make it easy!
“Other” allows you to key in a reason.
“Add to List” inserts your keyed data.
Select your option –
“Save PDF” allows for TD’s review.
Print for TD’s review, signature and race result document packet copying
Must be signed by Chief of Timing & Technical Delegate
Note date & time stamp
More data required!
Loading default information in “Program Options” will eliminate necessity to enter email address.
You will be prompted for a “save” location!
After all the data is entered in the software:
- TDTR must be saved as PDF and printed/signed for result packets
- TDTR may be viewed as XML
- TDTR must either be auto sent or saved as XML
- Saved XML TDTR must be attached to an email and sent to
Errors? Corrections can be made and the XML can be resent
NOTE: FIS results will not be scored to the FIS Points List until the TDTR XML file & FIS TD Report are submitted.SUBMITTING THE TDTR XML FILE
-“National Race Code” is used for USSA Transmittal # (alpha character + 4-digit number) - “Category” must be selected; JUN-Junior or CHI-Children are acceptable
- “Race Codex” is left blank.
The TDTR for a non-FIS event must never be submitted to FIS!
Ufor USSA scored,
N for USSA non-scored,
O(text not number) for Other
For non-FIS events:
“JUN-Junior” or “CHI-Children”
“Race Codex” is left blank; (no error message will be generated)
“U” for “USSA SCORED” +
4-digit USSA Transmittal number
Document must be printed/signed and included in scanned/PDF electronic or paper copy non-FIS
Race Result Document Packets, as required.
“JUN - Junior Race” selected; this and “CHI -Children” were only selections that seem to apply for non-FIS events
This is an upgraded presentation. It has taken advantage of the work done by many Alpine Officials and we are grateful for their contributions.
The intention was to build a vehicle that can be used for explaining the intricacies of the TDTR as well as for updating Timing Chiefs and Technical Delegates.
This presentation is dedicated to Allen Church and includes a special “THANK YOU” for his many years of service to the USSA and the FIS Alpine Officials’ community.
Allen “The Pope” Church has been a valuable mentor and is a valued friend. He encouraged us to do our best and helped us to be better than we thought possible!