Difference between revisions of "Prebuild"

From FreekiWiki
Jump to navigation Jump to search
m
 
(44 intermediate revisions by 11 users not shown)
Line 1: Line 1:
−
As we progress forward, we are finding more volunteers wanting to sign up for Build, and therefore Prebuild. We are also experiencing a decrease in hardware in the first parts of Prebuild (Hardware Sorting and Case Management) due to process changes needed for efficiency and the ewaste legislation. This creates a problem of how to squeeze extra volunteers through this bottleneck on their way into Build.
+
{{migrated}}
 +
[https://docs.google.com/document/d/1bJkB1VjZbsOss-Wbd1gQW4DC6RBDdXqS2zXUK3Mm8PI/edit?usp=sharing link]
  
−
The plan is to combine the jobs that were formerly known as Hardware Sorting, Card Sorting, Motherboard Sorting, Eval 1, and Case Management (Hardware ID) into one new educational area called ''Hardware Identification''. Some functions from Case Management would go to System Evaluation. System Evaluation would expand in slots and space available. Hardware Identification would try to be a drop in and learn space and students could demonstrate discrete skills needed to go into build. Once these skills had been demonstrated, they'd be free to do some time as System Evaluation and then move on to Build.
+
The first step in Free Geek's Build Program is called '''Prebuild'''.
  
−
There would be a basic set of skills that each student would have to demonstrate proficiency in. There would also be intermediate skills. They would only need to demonstrate a percentage of the intermediate skills. We could record the basic skills as a checklist on their status sheet, and also list the "extra credit" skills they have as well.
+
Prebuild is divided into two main branches, '''Hardware Identification''' and '''System Evaluation'''.  
  
−
An effort should be made to include descriptions and definitions so that volunteers studying the charts out-of-House on the wiki will not suffer from misunderstood word phenomena.
+
Most people begin in '''Hardware Identification''' by signing up for a shift at the front desk. In Hardware Identification volunteers work through a series of lesson boxes -- each one teaching a basic skill that will later be needed in the build program. The boxes are generally arranged from most basic to more advanced.  
  
−
== Skills ==
+
As a builder, each lesson box is available to you throughout the program, so you can refresh your memory as needed. If you have enough hardware knowledge, you can test out of Hardware Identification or skip whichever steps are unnecessary. Most people work through all of Hardware Identification in one or two shifts, but it is designed to be a "work at your own speed" experience.
−
''This is a brain dump of some items. Some could be moved, added, or deleted.''
 
  
−
=== Basic ===
+
Once you have completed or tested out of Hardware Identification you will move on to '''System Evaluation'''. In System Evaluation you will see how the computers fits together, sharpen up your hardware ID skills, learns some basic troubleshooting, and help prep systems for build, culling out systems we do not want to keep.
  
−
Students would have to demonstrate that they know all this stuff to move on. ''(This is a preliminary list.)''
+
== Hardware Identification Documentations ==
  
−
* differentiate between memory slots and card slots in a motherboard (see [[Cards vs Memory]])
+
A [[Hardware ID Facilitator's Guide]] is available for all Hardware ID instructors.  It uses the information found in the lesson boxes below, but is designed to help make the teaching of Hardware ID a little easier, including tips from current instructors! 
−
* identify a PCI, PCI-e, and AGP card, and identify each type of those slots on a motherboard (see [[Card Sorting]])
 
−
* size a hard drive (see [[Hard Drive Sizing]])
 
−
* identify the three main types of DIMMs (see [[What kind of memory is this?]] and [[RAM Sorting]])
 
−
* size memory (see [[Memory Sizing]])
 
−
* identify a network card, a modem, a wireless card, a sound card, and a video card from each other
 
−
* identify where the processor goes on the motherboard
 
−
* identify hard drives
 
−
* differentiate between optical drives - regular CD drives, DVDs, rewriteable or recordable CDs
 
−
* find an IDE cable
 
−
* open and close three styles of cases without breaking them (an easy, a medium, and a hard)
 
−
* spot a blown capacitor
 
−
* difference between a slot processor and zif socket
 
  
−
=== Intermediate ===
+
Each lesson box builds on previous ones and contains a few lessons. Some are basic background information. Others are hands-on exercises.
  
−
Students might have to demonstrate that they know some percentage of this stuff to move on, but they wouldn't need to know all of it. ''(This is a preliminary list.)''
+
; Box A
 +
* [[Cards vs Memory]]
 +
* [[All about memory]]
 +
* [[Memory Sizing]]
 +
* [[RAM Sorting]]
 +
 
 +
; Box B
 +
* [[All About Cards]]
 +
* [[Card sorting by function]]
 +
* [[Card Slot Identification]]
 +
* [[Card sorting by slot type]]
 +
 
 +
; Box C
 +
* [[Motherboard ID]]
 +
* [[Motherboard Sorting]]
  
−
* identify a riser
+
; Box D
−
* identify an AT and an ATX power connector
+
* [[Drive Identification]]
−
* identify an AT, USB, and PS/2 keyboard connector
 
−
* test button batteries
 
−
* test power supplies
 
−
* identify an Ultra Speed and High Speed rewriteable or recordable CD
 
−
* identify ISA, EISA, VESA, and MCA slots and cards
 
−
* determine the speed of a NIC
 
−
* enter BIOS on at least two different kind of systems (with different BIOSes)
 
−
* determine the speed of a processor manually and reattach the heat sink and fan without damage
 
  
−
* [[Card Sorting]] and [[Motherboard Sorting]]
+
; Box E
−
* [[Cards vs Memory]]
+
* [[Hard Drive Sizing]]
−
* [[Advanced Testing]]
 
−
* [[Advanced Card Sorting]]
 
−
* [[Power Supply Sorting]]
 
−
* [[CD ROM Drive Sorting]]
 
 
* [[Hard Drive Sorting]]
 
* [[Hard Drive Sorting]]
  
−
== The Hardware Identification area ==
+
; Box F
−
We'd like to treat this as a hands on classroom, where students could grab a ''lesson box'' (filled with cards or whatever). The lesson box would contain a laminated instruction sheet that lets the student "study up". There would also be a task that the student would need to do in front of an instructor. There would also be a list of items that need to be in the box (so instructors could make sure it's ready.)
+
* [[CPU Box]]
 +
* [[Heat sinks]]
 +
* [[Processor class and speed]]
 +
 
 +
; Appendix
 +
*[[POST Lesson]]
 +
 
 +
== System Evaluation Documentations ==
 +
Starting with the main overview flow chart, you work your way through the instructions. Each chart is color coded to help you keep track of where you are. When you are sent to another chart you will (most of the time) find yourself working through it and coming back to the main chart.
 +
 
 +
Along the way we are determining if the computers will be coded as ''Red Light'', ''Yellow Light'', or ''Green Light'' systems. Depending on the system's class, we'll be processing it differently.
 +
 
 +
; Red Light : We're recycling everything in the system (not using it for build). We'll only pull what we need to for data security purposes.
 +
; Yellow Light : We're recycling the system, but some of the components will be kept for reuse. We will pull out a lot of components if they are present.
 +
; Green Light : The system is a keeper. We'll be pulling only a few components for data security and testing purposes.
  
−
Some of these tasks might be appropriate for online tests (like identifying which parts of a motherboard take RAM and which take cards). Some would require physical presence to accomplish (like being able to open and close up a case properly). For those that could be available online, we could have a moodle test that the student could take to speed up their graduation.
+
System Evaluation is "go at your own speed" and "each one teach one". This means that you can take as many shifts as you need to learn everything you need and that you will likely teach a newer volunteer how to do the job when you want to move on to the next step.
  
−
Some production related tasks could be accomplished in this area (such as testing batteries and power supplies), but the main thrust of the area would be educational.
+
Here are the main flow charts used in this area:
  
−
If possible, we'd like access to the hardware identification area be open to anyone interested in joining the build program on a drop in basis, perhaps with a signup sheet for any station that is full. If that doesn't work, we'd need to go back to scheduling shifts. We might additionally want to limit how many people go straight there after a tour.
+
* [[System Evaluation Overview]] (Red chart)
 +
* [[System Evaluation Visual Triage]] (Blue chart)
 +
* [[Getting the Processor Information]] (Green chart)
 +
* [[System Evaluation Final Triage]] (Purple chart)
 +
* [[Removing components from systems]] (Orange chart)
 +
* [[Case Triage]] (Black chart)
 +
* [[Regular Mac Triage]] (pink chart)
  
−
== Changes to System Evaluation ==
+
== Finishing Prebuild ==
−
Currently system evaluation identifies ''red light'', ''yellow light'', and ''green light'' computers, but it passes off the red light and yellow light computers to case management. Now managing all three classes of computers would happen in System Evaluation. For red light systems, this simply means pulling the hard drives. For yellow light systems, this would include pulling any item on the exceptional components list as well as anything written on the white board.
+
Sometime during System Evaluation you will want to take the basic Linux Command Line Class. (Experience linux command line users can test out of this step.)
  
 +
When you have finished with all of Prebuild and the [[Basic Linux Command Line for Builders]] class '''(that wiki article has not been tagged as of 07/18/2014 for migration to Google Drive and has not been updated since 08/15/2012)''', you will move on to the [[Build]] Workshops where you will quality check systems, assemble computers, and install software.
  
 
[[Category: Prebuild]]
 
[[Category: Prebuild]]

Latest revision as of 15:24, 18 July 2014

deletion

This page has been migrated to a document on Free Geek's Google Drive.

Information remaining behind may no longer be relevant.

MIGRATOR:

When you have tagged this page as migrated,
please add a link to the new document on Google Drive.

(Link to new page immediately below.)


link

The first step in Free Geek's Build Program is called Prebuild.

Prebuild is divided into two main branches, Hardware Identification and System Evaluation.

Most people begin in Hardware Identification by signing up for a shift at the front desk. In Hardware Identification volunteers work through a series of lesson boxes -- each one teaching a basic skill that will later be needed in the build program. The boxes are generally arranged from most basic to more advanced.

As a builder, each lesson box is available to you throughout the program, so you can refresh your memory as needed. If you have enough hardware knowledge, you can test out of Hardware Identification or skip whichever steps are unnecessary. Most people work through all of Hardware Identification in one or two shifts, but it is designed to be a "work at your own speed" experience.

Once you have completed or tested out of Hardware Identification you will move on to System Evaluation. In System Evaluation you will see how the computers fits together, sharpen up your hardware ID skills, learns some basic troubleshooting, and help prep systems for build, culling out systems we do not want to keep.

Hardware Identification Documentations

A Hardware ID Facilitator's Guide is available for all Hardware ID instructors. It uses the information found in the lesson boxes below, but is designed to help make the teaching of Hardware ID a little easier, including tips from current instructors!

Each lesson box builds on previous ones and contains a few lessons. Some are basic background information. Others are hands-on exercises.

Box A
Box B
Box C
Box D
Box E
Box F
Appendix

System Evaluation Documentations

Starting with the main overview flow chart, you work your way through the instructions. Each chart is color coded to help you keep track of where you are. When you are sent to another chart you will (most of the time) find yourself working through it and coming back to the main chart.

Along the way we are determining if the computers will be coded as Red Light, Yellow Light, or Green Light systems. Depending on the system's class, we'll be processing it differently.

Red Light
We're recycling everything in the system (not using it for build). We'll only pull what we need to for data security purposes.
Yellow Light
We're recycling the system, but some of the components will be kept for reuse. We will pull out a lot of components if they are present.
Green Light
The system is a keeper. We'll be pulling only a few components for data security and testing purposes.

System Evaluation is "go at your own speed" and "each one teach one". This means that you can take as many shifts as you need to learn everything you need and that you will likely teach a newer volunteer how to do the job when you want to move on to the next step.

Here are the main flow charts used in this area:

Finishing Prebuild

Sometime during System Evaluation you will want to take the basic Linux Command Line Class. (Experience linux command line users can test out of this step.)

When you have finished with all of Prebuild and the Basic Linux Command Line for Builders class (that wiki article has not been tagged as of 07/18/2014 for migration to Google Drive and has not been updated since 08/15/2012), you will move on to the Build Workshops where you will quality check systems, assemble computers, and install software.

Retrieved from "http://wiki.freegeek.org/index.php?title=Prebuild&oldid=70708"