11 Connections How do we communicate signals/data from Start to Finish? How is voice communication handled between Start and Finish?CableRadioSnowmobileSki LiftSkier??
12 Warm-up and Synchronization At what time is the run scheduled to start?Is there a rule about Synchronization?What is the minimum recommended warm up time?
13 Synchronization and Synch + 1 Minute Are Systems A and B synchronized?How close are they?What is the maximum difference acceptable?What about Hand Times?
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 Time?
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 Time?
16 First Run Summary Why do we show Best run-time? Why do we show the Bib #?
17 Second Run Synch and +1 minute Are Systems A & B synchronized?
18 Second Run SummaryNotice First and Last racer data quality
19 Race SummaryList any or all bib numbers in the results timed on any system other than system A in all runs (indicate run).WHY? Batteries Snow obscuration Wire breakPhotocell alignment Other? (describe).Data source for replacement system A time (resp. ICR )? System B System C Manual
20 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 ResultWhat is the B time-of-day difference?Discuss the difference?What about Hand Time?
21 Race Comments What comments might or should be shown? What should NOT be shown?
22 Certification …this event adhered to the FIS rules. Any discussion on this?Are we through now?
23 Sign Off Chief T & C Printed Name and NAT Telephone nr. Email address USSA #SIGNATURETechnical DelegatePrinted Name and NATTelephone nr.addressFIS TD #SIGNATURE
24 ONLINE TDTR Software that allows online filing is available It’s use is required for all FIS eventsIt is available in (Windows, MacOS & Linux)Available for review/download at:ftp://ftp.fisski.ch/Software/Programs/TimingReport/AL/ / orskiing-rules/timing.htmlXML race result file must be submitted prior to filing a FIS online TDTR
25 TIMING & DATA TECHNICAL REPORT SOFTWARE * *Please verify you are using the most current version of the 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.
26 The new TDTR software program can be found On the FIS FTP site. The software program can be downloaded from the FIS FTP website. This program is available for Windows, Mac OS, and Linux.
28 Online Timing and Data Technical Report This is the first page and as you can see it has the basic information is the basic about the race.
29 Device and Connection Information This second page has the device connectivity information.
30 Select Your Connections Drop down box makes it simple!
31 Technical Timing Information Software will prompt for error correction!This 3rd page has the race technical timing information.
32 Summary of Race All times from system “A”? YES This is the last page of the software. This is where any issues are noted if any.
33 Summary of Race, all times from system “a”? NO Can add / delete / select, as needed.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.
34 If “NO”, enter Bib, Run & Select the Reason Drop-down Selections make it easy!
35 OPTIONS: SAVE PDF / VIEW XML / SAVE XML and EMAIL
36 Option: SAVE “PDF” Saved as: 2013AL6604TR Must be signed by Chief of Timing & Technical Delegate
41 Attach this file and e-mail to: firstname.lastname@example.org
42 SUBMITTING THE TDTR XML FILE The TDTR XML FILE must be submitted before the TD submits his online TD Report.After all the data is entered in the software:- TDTR may be saved as PDF and printed/signed for result packets- TDTR may be viewed and/or saved as XMLTDTR is attached to an and sent toErrors? Corrections can be made and the XML can be resentIf the TDTR Software is not used, a paper copy of the TDTR must be completed, signed and submitted to FIS.FIS is attempting to create a “paper-free” environment.Your cooperation is appreciated!
43 WHAT ABOUT NON-FIS EVENTS? A TDTR is required for all USSA scored non-FIS eventsA 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 TDTR or the FIS TDTR software can be used to produce a paper copy report, as required, for USSA non-FIS events.If the FIS TDTR software is used, the PDF report will need to be edited to include the USSA race letter code as the program only allows for four numbers. e.g. U1234The TDTR XML file must not be submitted USSA’s autoscoring system as USSA is not currently set up to accept the TDTR XML fileThe TDTR for a non-FIS event must never be submitted to FIS!
44 USSA Race Transmittal Code Include ALPHA designator with assigned USSA Race Code (in lieu of Codex):U for USSA scored,N for USSA non-scored,M for Masters,O (text not number) for Other
45 EDITED TDTR FOR NON-FIS EVENT “U” for “USSA SCORED” +4-digit USSA Transmittal numberDocument must be printed/signed and included in either scan/DPF electronic or paper copy USSSA Race Result Document Packets, as required.
46 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 was to build a vehicle that can be used for explaining the intricacies of the TDTR as well as for updating Timing Guys and bright Technical Delegates.Thank you Allen Church for your many years of service to the USSA and the FIS Alpine Officials’ community; you have been a valuable mentor and a valued friend!