TIMING & DATA TECHNICAL REPORT TIMING & DATA TECHNICAL REPORT ver 7.3ver 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.

2

(This part of the presentation addresses the paper copy of the report which can only be used for non-FIS events.)

EVENT IDENTIFIERSEVENT 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 IdentifiersEquipment Identifiers

Sys Timer ASys Timer BStart GateFinish Cell AFinish Cell B

•Brand Name•Model or Type•Serial Number•Homologation #

5

This information must be accurate; equipment must be currently homologated!

Timekeeping Equipment

BrandModelSerial #Homol. #

ModelSerial #Homol. #

TAG HEUERCP 5402004TAG.070T.08

Minitimer HL4401015TAG.076T.09

6

Start Gate BrandModelSerial #Homol. #

TAG HEUERHL 7-1996TAG.S54.03

7

Photo Cells

BrandModelSerial #Homol. #

ModelSerial #Homol. #

TAG HEUERHL 2-32121TAG.L49T.10

HL 2-32122TAG.L49T.03

8

SOFTWARE / RESULTS VERIFICATIONSOFTWARE / 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

CONNECTIONSCONNECTIONS

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 & SYNCHRONIZATIONPOWER 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 MINUTESYNCHRONIZATION 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 CHECKFIRST 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 CHECKLAST 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 SUMMARYFIRST RUN SUMMARY

•Why do we show Best run-time?•Why do we show the Bib #?

15

SECOND RUN SYNC +1 MINUTESECOND 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 SUMMARYSECOND RUN SUMMARY

Notice First and Last racer data quality!

17

RACE SUMMARYRACE 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 breakPhotocell 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 COMMENTSRACE COMMENTS

– What comments might or should be shown?

– What should NOT be shown?

19

CERTIFICATIONCERTIFICATION

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: SIGN OFF: Note Date on Form!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 TDTRCOMPLETED 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 TDTRONLINE 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 *TIMING & DATA TECHNICAL REPORT SOFTWARE *Version 2.1.8Version 2.1.8

*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 TDTR software program can be found on the FIS FTP site.

25

Select OS & Download

TDTR SOFTWARE INSTALLATION

26

Select Option & Continue

TDTR SOFTWARE, Step 2

27

Select Option & Continue

TDTR SOFTWARE, Step 3

28

Accept

Change & Find

or

and Continue

TDTR SOFTWARE, Step 4

29

Select Storage Location

Continue

TDTR SOFTWARE, Step 5

30

Select Options

Continue

TDTR SOFTWARE, Step 6

31

Go Back to Change Preferences, Install or Cancel

Verify Preferences

TDTR SOFTWARE, Step 7

32

Finish Installation & Launch Software

SET YOUR DEFAULTS & CHECK FOR UPDATESSelect “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.The Software: P1.

37

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!)

Event Information as listed on applicable website for level of event

Note Season Date

Select “Next” to Continue

This option allows for use at non-FIS events

38

Use Dropdown boxes & insert All Technical Data

Select “Next” to Continue

The Software: P2.The Software: P2.

39

Dropdown boxes allow for easy equipment selections

MAKE YOUR EQUIPMENT SELECTIONS

Select “Next” to Continue

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

48

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!

49

Select “Next” to Continue

INSERT ALL 1ST RUN TIMING DATA

INSERT 2ND RUN TIMING DATA

Select “Next” to Continue

FINAL VERIFICATIONS: All Times from System A?

Summary of Race:Summary of Race: all times from system “A”? NO

52

Enter Competitor/RunSelect Reason

“NO” is selected; information required.

If “NO”, enter Bib, Run & Select the Reason

53

Drop-down Selections make it easy!

“Other” allows you to key in a reason.

“Add to List” inserts your keyed data.

Followed rules?

CERTIFY & “SAVE XML”

SOMETHING IS MISSING!

This action will be repeated until all required data is entered.

OUTPUTS: OUTPUTS: SAVE PDF / VIEW XML / SAVE XML and EMAIL

56

Select “Output”

Select your option – “Save PDF” allows for TD’s review and provides copy for Race Result Document Packets.

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

57

PRINT “PDF” PRINT “PDF” Auto-saved as: 2015AL6641TR

58

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”Option: “VIEW XML”

59

“View XML” allows you to see the format of the file you will be transmitting to FIS.

alpineresults@fisski.ch

Option: SAVE “XML”Option: SAVE “XML”WILL SAVE THE TRANSMISSION FILE TO LOCATION OF YOUR CHOOSING

60

2015AL6623TR.xml

SELECT “AUTO-SEND” SELECT “AUTO-SEND” (Preferred Option)(Preferred Option)

61

More data required!

Folder created for ease of locating!

ENTER DATA & AUTO-SEND or…ENTER DATA & AUTO-SEND or…

62

This step can be eliminated by providing required data in default options!

SAVE XML and…SAVE XML and…

63

You will be prompted for a “save” location!

Attach “saved” file and e-mail to: Attach “saved” file and e-mail to: alpineresults@fisski.chalpineresults@fisski.ch

64

Use NAT+FIS CODEX as subject of e-mail: USA6641

SUBMITTING THE TDTR XML FILE 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: The Software: Used at non-FIS EventUsed at non-FIS Event

68

Select either “CHI” (Children) or “JUN” (Junior)

This option allows for use at non-FIS events

Leaving “Race Codex” area blank will not generate an error message when you try to “save/print PDF”.

TDTR FOR NON-FIS EVENT

69

“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 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