1. 2018-2019 TIMING & DATA TECHNICAL REPORT (TDTR)

2. WHY DO WE COMPLETE A TDTR?

3. Timing & Data Technical Report
Required for all events: non-FIS – including non-scored as well as FIS.
U.S. paper report has been redesigned to closely mirror the PDF report generated by the FIS TDTR software.
(This part of the presentation addresses preparation of a paper copy of the report which can only be used for non-FIS events.)

4. U.S. EVENT IDENTIFIER U.S. Race Code: Alpha character + 4 numbers:
U = U.S. scored
N = U.S. non-scored
M = Masters
O = Other (alpha not number)

5. LOCATION: As listed on U.S. website
CATEGORY: Scored or Championship Non-Scored
SEASON: Current season is 2019
EVENT NAME: As listed on U.S. website
COMPETITION TYPE: Type of race: DH, SL, GS, SG, AC, P
DATE: Actual date of event
GENDER: Ladies or Men
RACE CODE: As listed on U.S. website!

6. Equipment Identifiers
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 #

7. Timekeeping Equipment
Brand – System A
Model
Serial #
Homol. #
Brand – System B
TAG HEUER
CP 540
1207
TAG.070T.08
ALGE SR
9900
ALG.005T.10
Timekeeping Equipment

8. Start Gate Brand Model Serial # Homol. # TAG HEUER HL 7-1 11111
TAG.S54.03

9. Photo Cells At Finish Brand Model Serial # Homol. # TAG HEUER HL 2-31
1904
TAG.L47.03
ALGE
RLS1n
1000
AlG.L45.03
Photo Cells
At Finish

10. RESULT SOFTWARE Name of Software: Split Second or Vola
Version #: Version used by both timing & results

11. 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 ??

12. 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 should you wait to synchronize?

13. Synchronization and Sync + 1 Minute
Are Systems A and B synchronized?
How close are they?
Based on timing ruIes, is the difference acceptable?
What is the maximum difference acceptable?
What about Hand Sync (Manual Timekeeping)?

14. 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)?

15. 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) ?

16. First Run Summary Why do we show Best run-time?
Why do we show the Bib #?

17. RE-SYNCHRONIZATION PRIOR TO THE
Second Run
RE-SYNCHRONIZATION PRIOR TO THE
START OF THE 2ND RUN
IS NO LONGER REQUIRED

18. Notice First and Last racer data quality!
Second Run Summary
Notice First and Last racer data quality!

19. Race Summary
Were all Results from system A? If you answer “NO”, you must list any or all bib numbers in the applicable “Comments” section where an assigned time was obtained from any system other than system A
WHY?
List the reason: Batteries Snow obscuration Wire break Photocell alignment Other? (describe)
Data source for replacement system A time (resp. ACR )?
What did you use? System B System C Manual
NOTE: If Replacement Time (EET) calculated, you must include calculation worksheet(s) with this form. (Sent to TWG representative.)

20. Certification
We certify that the timing and calculations of this event adhered to the U.S. rules.

21. Sign Off Technical Delegate Printed Name U.S. # Telephone nr.
SIGNATURE
Chief T & C
Printed Name
Telephone nr.
address
SIGNATURE
Timekeeper or Company
Printed Name
Telephone nr.
address

22. 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 events – both scored and non-scored.

23. MISCELLANEOUS INFORMATION
You are encouraged to use FIS Timing Report software to prepare your Timing & Data Technical Report (TDTR) for non-FIS events.
Software allows printing of a PDF report and even though the FIS logo will appear on the document, it is acceptable.

24. ONLINE TDTR- FIS EVENT
Software that prepares a report for online filing is available
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:
data.fis-ski.com/services/timing-and-data/timing-and-data.html
NOTE: For FIS events, the race result XML and TDTR XML files must be submitted prior to filing online FIS TD Report!

25. (Edited XML from prior season’s event used for this presentation.)
TIMING & DATA TECHNICAL REPORT SOFTWARE * Version *In addition to verifying you are using the most current version of all rule books – including the FIS Timing Guidelines, please verify you are using the most current version of the TDTR software!
The second improvement is a new TDTR software (XML). This will allow the TDTR to be sent by XML and so no paper is needed to be sent to the FIS. This follows the Results example of having it sent electronically.
There are two options for this new software to be implemented. The Result software provider can add this to his software and/or it can be used as a stand alone application for the Chief of Timing.
(Edited XML from prior season’s event used for this presentation.)

26. New Version Information
Select “NEW VERSION available”
Old/New version information
Select “No” or “Yes” to download & install

27. The TDTR software program can be found on the FIS website
The software program can be downloaded from the FIS FTP website. This program is available for Windows, Mac OS, and Linux.
Select OS & Download

28. TDTR SOFTWARE INSTALLATION
Select Option & Continue

29. TDTR SOFTWARE, Step 2
Select Option & Continue

30. TDTR SOFTWARE, Step 3
Change & Find
or Accept and Continue

31. TDTR SOFTWARE, Step 4
Select Storage Location
Continue

32. TDTR SOFTWARE, Step 5
Select Options
Continue

33. TDTR SOFTWARE, Step 6 Verify Preferences Go Back to
Change Preferences,
Install or
Cancel

34. TDTR SOFTWARE, Step 7
Finish Installation & Launch Software

35. SET DEFAULTS & CHECK FOR UPDATES
Select “Options”
Set “Defaults”
Check for Software “Updates”

36. SELECT “CATEGORY”

37. SELECT “COMPETITION”

38. SELECT “GENDER”

39. OPTIONS: Program Options that will not change!

40. PREFERENCES: Timekeeper data that will not change!

41. PREFERENCES: Timing Device data that will not change!

42. PREFERENCES: Email Options that will not change!

43. The Software: P1. Note Season Date
Event Information as listed on applicable website for level of event
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 U.S. site, e.g. Daniel A. Chayes on FIS and
Dan Chayes on U.S.!)
Insert timekeeper (timing company) information
Select “Next” to Continue

44. The Software: P2. Use Dropdown boxes & insert All Timing Device Data
Select “Next” to Continue

45. MAKE YOUR EQUIPMENT SELECTIONS
Dropdown boxes allow for easy equipment selections
Select “Next” to Continue

46. MAKE YOUR MODEL SELECTIONS
Dropdown boxes allow for easy model selections
Select “Next” to Continue

47. SELECT MODELS: Homologation # is Automatic
Note warning!

48. SELECT MODELS: Homologation # is Automatic
Currently Homologated
Key in Serial Number

49. AVAILABLE RESULT SOFTWARE SELECTIONS
Don’t forget “Version”

50. SELECT YOUR CONNECTION TO START
Repeat process for “System B”

51. ALL START CONNECTION SELECTIONS
“Voicecom” checked…select your device

52. TECHNICAL DATA COMPLETE
Note option allowing updating of homologated timing devices!
DON’T FORGET TO “SAVE”!
Select “Next” to Continue

53. YOUR SAVED DATA
Explanation required to document failure of either system

54. 1ST RUN TIMING DATA Note “Power on Time” and Insert all 1st Run Data
Select “Next” to Continue

55. 2ND RUN TIMING DATA
Select “Enter data for 2nd run” and enter 2nd run time data
RESYNCHRONIZATION BEFORE 2ND RUN IS NO LONGER REQUIRED!
Select “Next” to Continue

56. FINAL VERIFICATIONS: All Times from System A?
“Yes” or “No”

57. Summary of Race: All Times From System “A”? NO
“NO” is selected; information required.
“Bib” /”Run”/”Reason”
Drop-down selections make it easy!
As you can see if a time is missed, there are options to notate detailed information as to what occurred. You can also make any additional comments in the comment section for each Run.
At the bottom you find options to View the xml, go back and check the report or save the XML. The save to PDF is not ready at this time and is not showing in the current version of the software.

58. Summary of Race: All Times From System “A”? NO
“Other” allows you to key in a reason.
Select source for replacement time
“Add to List” inserts your keyed data.
Don’t forget to “SAVE”

59. CERTIFY & “SAVE XML”

60. SOMETHING IS MISSING!
This action will be repeated until all required data is entered.

61. OUTPUTS: SAVE PDF/VIEW XML/SAVE XML/EMAIL
Select “Output”
Select your option –
“Save PDF” allows for TD’s review and provides copy for Race Result Document Packets.

62. Option: SAVE “PDF” WILL SAVE TO LOCATION OF YOUR CHOOSING

63. PRINT “PDF” Auto-saved as: 2019AL Season 2019: resynchronization prior to start of 2nd Run is no longer required)
Print for TD’s review, signature and race result document packet requirements
Must be signed by Technical Delegate & Chief of Timing

64. SAVE “XML” Attaching & sending is duty of Chief of T & C

65. Option: “VIEW XML”
“View XML” allows you to see the format of the file you will be transmitting to FIS.
Create /Subject line =
FIS Codex
Attach & Send to:

66. Option: SAVE “XML” WILL SAVE THE TRANSMISSION FILE TO LOCATION OF YOUR CHOOSING OR USE DEFAULT LOCATION

67. SELECT “SAVE XML & EMAIL” (Preferred Option)
Choose your location!
More data may be required!
SAVE XML &

68. ENTER DATA & AUTO-SEND or…
This step can be eliminated
by providing required data
in default options!

69. Attach “saved” file and email to: alpineresults@fisski.ch
Use NAT+FIS CODEX as subject of USA6365 (as noted in name of document)
(FIS Codex is a 4-digit number assigned by the FIS Bureau)

70. SUBMITTING 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 may be viewed as XML
- TDTR must be saved as PDF and printed/signed for result packets
- TDTR must either be auto sent or saved as XML
- Saved XML TDTR must be attached to an and sent to
FIS online Technical Delegate Report allows the Technical Delegate to view what has been transmitted to FIS.
Errors? Corrections can be made and TDTR XML file can be resubmitted
NOTE: FIS results will not be scored to the FIS Points List until the TDTR XML file & FIS TD Report are submitted.

71. NOTE: REPLACEMENT TIME CALCULATIONS
The Chief of T&C must submit a copy of the TDTR to their appropriate TWG reviewer. If an event requires calculation of a replacement time (EET), copies of all calculations must be included.
Alaska: Lucy Schram
Central: Jon Manderfield
East: Matt Howard
Far West: Lucy Schram
IMD: Tami Strong
Northern: Tami Strong
PNSA: PNSA Office
Rocky Mtn.: John Jett

72. WHAT ABOUT NON-FIS EVENTS?
A TDTR is required for all non-FIS events – both scored and non-scored
Either the paper copy U.S. TDTR can be prepared or the FIS TDTR software can be used to produce a PDF report, as required, for non-FIS events.
To use FIS TDTR software for non-FIS events: (FIS logo instead of U.S. logo is a non-issue.)
- “National Race Code” is used for U.S. Race Code #
(alpha character + 4-digit number)
- “Category” must be selected; CHI-Children, CIT-Citizen or JUN-Junior are acceptable
- “Race Codex” is left blank.
The TDTR XML file must not be submitted to U.S.’s autoscoring system as U.S. is not currently set up to accept the TDTR XML file
TDTR for a non-FIS event must never be submitted to FIS!

73. The Software: Used at non-FIS Event
This option allows use at non-FIS events
Select either “CIT” (Citizen), “CHI” (Children) or “JUN” (Junior)
Leaving “Race Codex” area blank will not generate an error message when you try to “save/print PDF”.

74. TDTR FOR NON-FIS EVENT “U” for “U.S. SCORED” + 4-digit U.S. Race Code
Document must be printed/signed and included in scanned/PDF electronic or paper copy non-FIS
Race Result Document Packet submitted to U.S. Ski and Snowboard.
“JUN” (Junior) selected; “JUN”, “CIT” (Citizen) or “CHI” (Children) are only selections that seem to apply for non-FIS events
THIS TDTR IS A SAMPLE AND IS NOT FROM AN ACTUAL EVENT; please remember timing equipment no longer needs to be resynchronized prior to the second run!

75. 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 U.S. Ski & Snowboard 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!