TIMING & DATA TECHNICAL REPORT
ver 7.3
1
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.
(This part of the presentation addresses the paper copy of the report
which can only be used for non-FIS events.)
2
EVENT IDENTIFIERS
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.)
3
Location: As listed on website
Event:* Type of race: DH, SL, GS, SG, AC
Event Name: As listed on website
Gender:*
Date:
Ladies or Men
Actual date of event
*“Check Boxes” enabled!
4
Equipment Identifiers
This information must be accurate; equipment must be currently homologated!
Sys Timer A
Sys Timer B
Start Gate
Finish Cell A
Finish Cell B
•Brand Name
•Model or Type
•Serial Number
•Homologation #
5
Timekeeping
Equipment
Brand
Model
Serial #
Homol. #
TAG HEUER
CP 540
2004
TAG.070T.08
Model
Serial #
Homol. #
Minitimer HL440
1015
TAG.076T.09
6
Start Gate
Brand
Model
Serial #
Homol. #
TAG HEUER
HL 7-1
996
TAG.S54.03
7
Photo Cells
Brand
Model
Serial #
Homol. #
TAG HEUER
HL 2-32
121
TAG.L49T.10
Model
Serial #
Homol. #
HL 2-32
122
TAG.L49T.03
8
SOFTWARE / RESULTS VERIFICATION
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
9
CONNECTIONS
How do we communicate
signals/data from Start to Finish?
How is voice communication
handled between Start and
Finish?
•Cable
•Radio
•Snowmobile
•Ski Lift
•Skier
•??
10
POWER ON & SYNCHRONIZATION
At what time is the run scheduled to start?
– Is there a rule about Synchronization?
– What is the minimum recommended warm- up time?
– Why do you have to wait to synchronize?
11
SYNCHRONIZATION AND SYNC + 1 MINUTE
•
Are Systems A and B synchronized?
– How close are they?
•
What is the maximum difference acceptable?
•
What about Hand Sync (Manual Timekeeping)?
12
FIRST COMPETITOR QUALITY CHECK
•Is Net Time the same as A time-of-day difference?
– How close are they?
– Does Net Time agree with Official Results?
•What is the B time-of-day difference?
– Discuss the difference?
•What about Hand Sync (Manual Timekeeping)?
13
LAST COMPETITOR QUALITY CHECK
•Is Net Time the same as A time-of-day difference?
– How close are they?
– Does Net Time agree with Official Results?
•What is the B time-of-day difference?
– Discuss the difference?
•What about Hand Sync (Manual Timekeeping) ?
14
FIRST RUN SUMMARY
•Why do we show Best run-time?
•Why do we show the Bib #?
15
SECOND RUN SYNC +1 MINUTE
-
Are Systems A & B synchronized?
-
Do the rules require re-synchronization between
1st & 2nd Runs?
-
Why do you think there was no Hand re-sync?
16
SECOND RUN SUMMARY
Notice First and Last racer data quality!
17
RACE SUMMARY
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:
Batteries
Snow obscuration
Wire break
Photocell alignment
Other? (describe)
Data source for replacement system A time (resp. ACR 611.2.1)? What did
you use?
System B
System C
Manual
NOTE: If Replacement Time (EET) calculated, include calculation worksheet(s) with this form.
(Sent to TWG representative.)
18
RACE COMMENTS
– What comments might or should be shown?
– What should NOT be shown?
19
CERTIFICATION
We certify that the timing and calculations of this
event adhered to the USSA rules.
•Any discussion on this?
•Are we through now?
20
SIGN OFF: Note Date on Form!
•Chief T & C
– Printed Name
– Telephone nr.
– Email address
– USSA #
– SIGNATURE
•Technical Delegate
– Printed Name
– Telephone nr.
– Email address
– USSA #
– SIGNATURE
21
COMPLETED TDTR
- The Chief of Timing & Calculations is
responsible for the accurate completion of
this form.
- The Technical Delegate is responsible for
verifying the accuracy of the data.
- Both officials must sign the form as their
confirmation of the accuracy of the timing for
the event.
- A TDTR is required for ALL scored events.
- A TDTR is required for ALL non-scored
Championship events; e.g. U12, U14 and
Masters Championships.
22
ONLINE TDTR
• Software that allows online filing is available
• Data requirements are identical to paper form
• Its use is required for all FIS events: Depending on
connection, download time can vary – DOWNLOAD,
INSTALL AND TEST IN ADVANCE OF YOUR EVENT!
• It is available in (Windows, MacOS & Linux)
• Available for review/download at:
ftp://ftp.fisski.ch/Software/Programs/TimingReport/AL/
Race result XML and TDTR XML files must be submitted prior to
filing online TD Report!
23
TIMING & DATA TECHNICAL REPORT SOFTWARE *
Version 2.1.8
*Please verify you are using the most current version of the software!
(Edited XML from prior season’s event used for this presentation.)
24
The TDTR software program can be found on the
FIS FTP site.
Select OS & Download
25
TDTR SOFTWARE INSTALLATION
Select Option & Continue
26
TDTR SOFTWARE, Step 2
Select Option & Continue
27
TDTR SOFTWARE, Step 3
Change & Find
or
Accept
and Continue
28
TDTR SOFTWARE, Step 4
Select Storage Location
Continue
29
TDTR SOFTWARE, Step 5
Select Options
Continue
30
TDTR SOFTWARE, Step 6
Verify Preferences
Go Back to Change Preferences,
Install or
Cancel
31
TDTR SOFTWARE, Step 7
Finish Installation &
Launch Software
32
SET YOUR DEFAULTS & CHECK FOR UPDATES
Select “Options”
Set “Defaults”
Check for Software “Updates”
PREFERENCES: Timekeeper data that will not change!
PREFERENCES: Timing Devices data that will not change!
PREFERENCES: Program Options that will not change!
The Software: P1.
Note Season Date
Event Information as listed on
applicable website for level of event
This option allows for use at non-FIS events
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!)
Select “Next” to Continue
37
The Software: P2.
Use Dropdown boxes &
insert All Technical Data
Select “Next” to Continue
38
MAKE YOUR EQUIPMENT SELECTIONS
Dropdown boxes
allow for easy
equipment selections
Select “Next” to Continue
39
MAKE YOUR MODEL SELECTIONS
Dropdown boxes allow for
easy model selections
Select “Next” to Continue
HOMOLOGATION # IS AUTOMATIC
AVAILABLE RESULT SOFTWARE SELECTIONS
SPLIT SECOND SELECTED
SELECT YOUR CONNECTION TO START
ALL START CONNECTION SELECTIONS
WARNING: YOUR SYSTEM B TIMER IS NOT VALID!
TECHNICAL DATA COMPLETE
Select “Next” to Continue
Prompt for new version
after initial installaton
New Version Information
(Uninstall/Re-install may be required.)
This prompt may/may not be available 2015-2016!
48
INSERT ALL 1ST RUN TIMING DATA
Select “Next” to Continue
49
INSERT 2ND RUN TIMING DATA
Select “Next” to Continue
FINAL VERIFICATIONS: All Times from System A?
Summary of Race: all times from system “A”? NO
“NO” is selected;
information required.
Enter Competitor/Run
Select Reason
52
If “NO”, enter Bib, Run & Select the Reason
Drop-down Selections
make it easy!
Followed rules?
“Other” allows you to
key in a reason.
“Add to List” inserts
your keyed data.
53
CERTIFY & “SAVE XML”
SOMETHING IS MISSING!
This action will be repeated until all
required data is entered.
OUTPUTS: SAVE PDF / VIEW XML / SAVE XML and EMAIL
Select “Output”
Select your option –
“Save PDF” allows for TD’s review
and provides copy for Race Result
Document Packets.
56
Option: SAVE “PDF”
WILL SAVE TO LOCATION OF YOUR CHOOSING
57
PRINT “PDF”
Auto-saved as: 2015AL6641TR
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
58
Option: “VIEW XML”
“View XML” allows you to see
the format of the file you will be
transmitting to FIS.
alpineresults@fisski.ch
59
Option: SAVE “XML”
WILL SAVE THE TRANSMISSION FILE TO LOCATION OF YOUR CHOOSING
60
SELECT “AUTO-SEND” (Preferred Option)
Folder created for ease of
locating!
More data required!
61
ENTER DATA & AUTO-SEND or…
This step can be eliminated
by providing required data
in default options!
62
SAVE XML and…
You will be prompted for
a “save” location!
63
Attach “saved” file and e-mail to:
alpineresults@fisski.ch
Use NAT+FIS CODEX as subject of e-mail: USA6641
64
SUBMITTING THE TDTR XML FILE
•
The TDTR XML and the RACE RESULT XML files must be submitted before the TD
submits his online TD Report.
•
The Chief of Timing & Calculations is responsible for entering data and transmitting
the XML file to FIS, but the Technical Delegate must verify the accuracy!
•
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
alpineresults@fisski.ch
FIS online Technical Delegate Report allows the Technical Delegate to view what has
been transmitted to FIS. Errors? Corrections can be made and 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.
65
WHAT ABOUT NON-FIS EVENTS?
•
A TDTR is required for all USSA-scored non-FIS events
•
A TDTR is required for all USSA non-scored Championship events, e.g. YSL,
U10, U12 Junior Championships, Masters Championships, etc.
•
Either the original paper copy USSA TDTR can be prepared or the FIS TDTR
software can be used to produce a PDF report, as required, for non-FIS events.
•
FIS TDTR software may be used for non-FIS events (FIS logo instead of USSA logo is a non-issue.)
- “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 XML file must not be submitted to USSA’s autoscoring system as
USSA is not currently set up to accept the TDTR XML file
The TDTR for a non-FIS event must never be submitted to FIS!
66
USSA Race Transmittal Code
USE: USSA-ASSIGNED ALPHA designator &
USSA-ASSIGNED Race Transmittal CODE
U for USSA scored,
N for USSA non-scored,
M for Masters,
O (text not number) for Other
The Software: Used at non-FIS Event
This option allows for use at non-FIS events
Select either “CHI” (Children) or “JUN” (Junior)
Leaving “Race Codex” area blank will
not generate an error message when
you try to “save/print PDF”.
68
TDTR FOR NON-FIS EVENT
“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
69
Thank You For Your Attention!
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 of the presentation is 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. It includes a special “THANK YOU” for
his many years of volunteer service to the USSA and FIS Alpine Officials’ communities.
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!
70