Presentation on theme: "TIMING & DATA TECHNICAL REPORT ver 7.2 1. Timing & Data Technical Report is required for all scored events – USSA & FIS. It is also required for USSA."— Presentation transcript:
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. 2 (This part of the presentation addresses the paper copy of the report which can only be used for non-FIS events.)
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
4 Event :* Type of race: DH, SL, GS, SG, AC Gender :* Ladies or Men *“Check Boxes” enabled! Location: As listed on website Event Name: As listed on website Date: Actual date of event
Equipment Identifiers Sys Timer A Sys Timer B Start Gate Finish Cell A Finish Cell B Brand Name Model or Type Serial Number Homologation # 5 This information must be accurate; equipment must be currently homologated!
Timekeeping Equipment Brand Model Serial # Homol. # Model Serial # Homol. # TAG HEUER CP 540 2004 TAG.070T.08 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. # Model Serial # Homol. # TAG HEUER HL 2-32 121 TAG.L49T.10 HL 2-32 122 TAG.L49T.03 8
SOFTWARE / RESULTS VERIFICATION 9 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
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 1 st & 2 nd 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 Chief T & C –Printed Name and NAT –Telephone nr. –Email address –USSA # –SIGNATURE Technical Delegate –Printed Name and NAT –Telephone nr. –Email address –USSA # –SIGNATURE 21
COMPLETED TDTR 22 -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.
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 * Versions 2.1.2 / 2.1.3 *Please verify you are using the most current version of the software! 24 (Edited XML from prior season’s event used for this presentation.)
The new TDTR software program can be found On the FIS FTP site. 25 Select OS & Download
The Software: P1. 33 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!)
34 First-time use requires loading list of homologated timing devices
TIMEKEEPING EQUIPMENT 42 Dropdown boxes for equipment brand and model selections You must insert Serial Numbers! Homologation number automatically inserted Additional selections & continue (Select “Other” if your software not listed.)
Select Your Connections 45 Drop down boxes make it simple!
Technical Timing Information 46 Prior to “Finish”, Software will prompt for all error corrections!
Summary of Race: Summary of Race: All times from system “A”? YES 47
Summary of Race: Summary of Race: all times from system “A”? NO 48 Can add / delete / select, as needed. “NO” is selected; information required.
If “NO”, enter Bib, Run & Select the Reason 49 Drop-down Selections make it easy! “Other” allows you to key in a reason. “Add to List” inserts your keyed data. Followed rules?
OUTPUTS: OUTPUTS: SAVE PDF / VIEW XML / SAVE XML and EMAIL 50 Select “Output” Select your option – “Save PDF” allows for TD’s review.
Option: SAVE “PDF” Option: SAVE “PDF” WILL SAVE TO LOCATION OF YOUR CHOOSING 51
PRINT “PDF” PRINT “PDF” Saved as: 2015AL6623TR 52 Must be signed by Chief of Timing & Technical Delegate Note date & time stamp Print for TD’s review, signature and race result document packet copying
Option: “VIEW XML” 53 This is the format of the file you will be transmitting to FIS. firstname.lastname@example.org
Option: SAVE “XML” Option: SAVE “XML” WILL SAVE THE TRANSMISSION FILE TO LOCATION OF YOUR CHOOSING 54
SELECT “AUTO-SEND” (Preferred Option) 55 More data required! Loading default information in “Program Options” will eliminate necessity to enter email address.
SAVE XML and… 57 You will be prompted for a “save” location!
Attach “saved” file and e-mail to: email@example.com 58
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. 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 firstname.lastname@example.org 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. 59
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! 60
USSA Race Transmittal Code Include ALPHA designator with assigned USSA Race Code U for USSA scored, N for USSA non-scored, M for Masters, O (text not number) for Other For non-FIS events: Select “Category”: “JUN-Junior” or “CHI-Children” “Race Codex” is left blank; (no error message will be generated)
TDTR FOR NON-FIS EVENT 62 “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
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 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! 63