Disciplines/Skills Recommended

A combination of both PC hardware and software knowledge is necessary to compete in this event. 

Event Description

Through research of their own, teams will prepare themselves for methods to build a generic PC as fast as possible completing the first phase of the contest.

The second phase will have the teams “Troubleshooting” a pre-built system that will have multiple QC errors attempting to document all the errors as quickly as possible. The last phase will have the top 3 teams building and tuning the system for optimal performance.  The winning team will be the team with the top score in the final.      

1st Game Day Event – Build it Fastest

Teams will be chosen in random for the build order.  4 Groups of 3 teams will be selected.  First group of 3 Teams will build the systems at the same time followed by a small break to reset the systems.  The 2^nd group of 3 teams will then compete followed by time to reset and so forth through all 4 groups. (We will have 3 systems that are used in the build event for all 12 teams)

The provided computer configuration will be setup “unboxed” and ready for teams to compete in building the systems as fast as possible.

The Avnet Build Instruction will be used to qualify the quality of the build, and all QA checks will be reviewed as well for accuracy.  It is not only the time to build the unit, but the workmanship/quality as well.

Teams will be given an equipment list of items that they are required to bring to the event. Electric Screwdrivers are strongly recommended!

Teams will be timed from start to finish on building the computers as fast as possible with penalties associated around accuracy in following the documented procedure.

Time penalties will be added for QC errors before totaling the final score.

Units that have been built will then be de-integrated by an Avnet approved technician and will be prepared for next timed event.

2nd Game Day Event – Troubleshoot it Fastest

Teams will be chosen in random for the troubleshooting order.  4 Groups of 3 teams will be selected.  First group of 3 Teams will troubleshoot the systems at the same time followed by a small break to reset the systems.  The 2^nd group of 3 teams will then compete followed by time to reset and so forth through all 4 groups.  (We will have 3 systems that are used in the troubleshoot event)

The provided computer configuration will be setup “built” and ready for teams to compete in troubleshooting the systems as fast as possible.

These systems will strictly be used for troubleshooting and will not be the same systems used for tuning or building.

Each system will be given IDENTICAL QC errors.  The total number of errors will be disclosed on game day.  Some errors could simply be cosmetic while others could potentially prevent the system from booting.  All errors will be physical and or BIOS but nothing involving the O/S will be used.

The Avnet Build Instruction will be used to qualify the quality of the build, and all QA checks will be reviewed as well for accuracy.  It is not only the time to troubleshoot the unit, but the workmanship/quality as well.

Teams will be given an equipment list of items that they are required to bring to the event. Electric Screwdrivers are strongly recommended!

Teams will be timed from start to finish on troubleshooting the computers as fast as possible with penalties associated around accuracy.

Time penalties will be added for QC errors before totaling the final score.

Units will then be reset by an Avnet approved technician and will be prepared for next timed event.

3rd Game Day Event – FINAL SHOWDOWN

ONLY the TOP 3 teams after the Build it and Troubleshoot it scores are totaled will participate in the Final Showdown.  Each team will be assigned a workstation that has be de-integrated however the systems will have pre-loaded Windows 7 Professional 64-bit w/SP1.

All systems will be identically configured and will have already been benchmarked and base-lined within a set score of each other.

The same BIOS settings, windows updates and system drivers will have already been pre-loaded/installed.

Teams will race to integrate the system and tune the systems using a “Build Document”.   Once they complete that section, they will benchmark and note scores.  From there teams will be given the freedom to choose up to 3 items to push their systems further.  All 3 items must be documented in the Build Document and then they can declare their completion. Teams will have web access to obtain drivers/updates during the event.  Note that web access may be slow.  Teams will be allowed to performance tune (optimize) their systems; this includes over-clocking the system.  Drivers can be from any source. BIOS/firmware Revs WILL be allowed.

One a team has declared their completion – judges will note their final completion time and then begin QC and final benchmark testing. Judges will come by to test each computer in accordance with the Judges Form (see attached).  All observers and faculty must step away from the systems but you can remain in the room while the judges complete the testing.

Systems will be shutdown and rebooted before testing begins.

Teams must make sure that any changes they have made will still function after a reboot.

No H/W replacements will be used this year.  Systems will be fully functional before event starts and will have passed all diagnostics.  Once a team starts this final showdown there will be no trouble shooting or testing of any parts by judges.

If the system does not boot and or is damaged beyond repair due to performance optimizations of the team, there will be no replacements – Showdown phase will be over and a null score will be given. 

The following benchmarking tools will be used for this game:

Futuremark: 3DMark 11 (Benchmark Only Test) (5 Minutes to Run)

Geekbench: Geekbench 2 (1 Minute to Run)

Judging will be based off completion time and a set of benchmarking results.  Each team will be given a total score based on the performance of their systems.  Each system will be tested on two benchmarking software programs.  The winner will be determined by the team that amasses the most points from benchmarking scores as well as time bonus. 

• Any tampering with benchmark software will result in a disqualification from the contest.


• Each system will be tested using two (2) separate benchmarking software programs.
  
  
  
  • 3DMark 11   Default settings on the benchmarking applications will be used when testing  (Choosing Benchmark Only)


• The results will be recorded and totaled to determine which system is the overall winner.  (see Scoring)

Scoring

Build it Fastest

There is a maximum total of 20pts available

• 25pts awarded (team) with the fastest time


• 20pts awarded to the 2^nd fastest time


• 17pts awarded to the 3^rd fastest time


• 13pts awarded to the 4^th fastest time


• 10pts awarded to the 5^th fastest time


• 7pts awarded to the 6^th fastest time


• 4pts awarded to the 7^th fastest time


• 2pt awarded to the 8^th fastest time

(Deductions: for every quality error, one minute will be added.)

Troubleshoot it Fastest

There is a maximum total of 20pts available

• 25pts awarded (team) with the fastest time


• 20pts awarded to the 2^nd fastest time


• 17pts awarded to the 3^rd fastest time


• 13pts awarded to the 4^th fastest time


• 10pts awarded to the 5^th fastest time


• 7pts awarded to the 6^th fastest time


• 4pts awarded to the 7^th fastest time


• 2pt awarded to the 8^th fastest time

(Deductions: for every quality error, one minute will be added.)

Final Showdown -- Build

There is a maximum total of 20pts available

• 25pts awarded (team) with the fastest time


• 20pts awarded to the 2^nd fastest time


• 15pts awarded to the 3^rd fastest time

(Deductions: for every quality error, one minute will be added.)

Final Showdown - Tune

There is a maximum total of 30pts available

• 12pts awarded (team) with the highest benchmark scores


• 8pts awarded to the 2^nd highest scores


• 4pts awarded to the 3^rd highest scores

Parameters

• Avnet supplied Bill of Materials (BOM) will NOT be provided this year to all registered teams.  However a sample Avnet Build Instruction document will be provided to teams by Friday March 18^th.


• Teams must supply their own tool kits - No exceptions. Failure to do so will result in disqualification (see Equipment Requirements)


• Teams will optimize their PC on Game Day only.


• Internet (web) access will be available to the teams at the event, although it may be slow.


• Drivers can come from any source. BIOS/Firmware revs are allowed


• Teams will be allowed to have one USB based storage device with preloaded software, drivers, etc. at the event.  Including key-fob, external USB HDD, etc. Alternatively, teams can pre-load a CD / DVD to use during the competition or any combination thereof.


• Operating system will be Microsoft Windows 7 Pro 64-bit w/SP1


• Teams are NOT allowed to reload the system.


• CPU, bus, video and memory over-clocking is allowed and encouraged.


• Teams need to complete the computer build on their own – assistance from sponsoring faculty will not be allowed.


• No technical representation from Avnet to assist with any troubleshooting or technical questions will be available this year.


• Avnet Game Owner reserves the right to amend/update/change this Game Event Form before the event begins on April 14^th, 2012.  Notifications of changes will be posted on the Avnettechgames.com website.

Schedule

7:00am – 8:00am     Registration

8:00am – 8:30am     Game Kickoff (Room 234 – Confirm your Schedules)                     

8:30am – 12:30pm     2 events begin at the same time & run all morning

11:45am – 1:30pm   “On the Go” lunch

1:00 – 2:30pm           Final Showdown (3 Final Teams)

2:30 – 3:00pm           Judges finish calculate final scores

3:00 – 4:00pm           Network Hour (Student/Faculty/Administration/Industry)

4:00 – 5:00pm           Awards Reception

Equipment Requirements

Students

• Bring a tool kit containing screwdrivers, tie-wraps, nut drivers, cutters, flash light, any equipment needed to assemble your system.


• Students may bring a USB drive to load drivers for the event.

Avnet

• 9 complete computer systems (minus the monitors)


• Backup equipment for DOA purposes


• 6 Stop Watches to time the Build & Troubleshooting events


• 6 “That was Easy” Buttons or Light Bars to help in stopping the clocks

Venue

• Network connectivity at each workstation


• Network Cables, switches and monitors for each workstation


• Two Separate Rooms one for each game (Connected Together)


• Access to Trash


• Static-protection straps


• Power strips, cables (power and peripheral)


• 1 table per team / 3 chairs per table


• Power for 9 full workstations and monitors (all the same type/model)

h

hhhhhhh

h

h

h