Meta Triage of Systems

<graphvizr>

 digraph BUILDPATH {

  node [fontname="Helvetica", fontsize="11"]
  edge [fontname="Helvetica"]

  start         [label="START HERE", shape="box"]

  missingmobo [label="Missing the\nMotherboard?"]
  highend     [label="Marked as HIGH END?\n(Celeron, P-III, P4, Athlon, Duron)"]
  lowend      [label="Marked as LOW END?\n(Pentium, Pentium Pro,\n486, 386, 286, 80/86\nMade for Windows 95/8)"]
  damaged     [label="Missing sides?\nor Other major damage?"]
  fast        [label="Speed marked\n600 MHz or faster?"]
  waiting     [label="Put on\nWAITING FOR EVAL 2\npile", shape="box", style="bold"]
  incoming    [label="Put on \nINCOMING\npile", shape="box", style="bold"]
  reject      [label="Label and put on\nREJECT\npile", shape="box", style="bold"]

  start       -> damaged

  damaged     -> reject [taillabel="YES"]
  damaged     -> missingmobo [taillabel="NO"]

  missingmobo -> reject [taillabel="YES"]
  missingmobo -> lowend [taillabel="NO"]

  highend     -> waiting [taillabel="YES"]
  highend     -> fast [taillabel="NO"]

  lowend      -> incoming [taillabel="YES"]
  lowend      -> highend [taillabel="NO"]

  fast        -> waiting [taillabel="YES"]
  fast        -> incoming [taillabel="NO"]
  
 }

</graphvizr> The idea of this chart is to safely bypass the ever-bottlenecked INCOMING pile in system evaluation. If you don't know how to identify the terms on this page, please learn to before attempting this job. In general this job should be done by trained system evaluation instructors and staff.

Meta-triage should take into account the current needs of both System Eval 1 and System Eval 2. For example, if there are a lot of system in 2, and not so many in 1, moving incoming system directly into Eval 2 should be avoided. legacy [label="Put on \nLEGACY\npile", shape="box", style="bold"]