|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
|||||
|
|||||
|
Re: Inspections -- Solutions/Ideas
I like visiting teams in their pits and that is what I recommended. It gives another set of eyes for safety reasons. Too often I have found 50 amp battery chargers, homemade electrical distributions and air compressors in the pit. The Underwriters people can't catch everything.
The number of inspectors varies with event size. With 50+ teams 8 inspectors will see an average of 6 teams during the inspection day. In general, at least 3 or four will be new inspectors and perhaps all of them might be seeing a robot event for the first time. It's just the way it goes. With a thirty team event, have two each for electrical, mechanical and pnuematics and one or two at the main inspection area for weigh, size and safety checks and one Lead Inspector. At a larger event you could add one each to mechanical and electrical. Fewer teams use pneumatics. I think the inspection stickers need to go on the robot so field people can tell who has passed which inspection. That also allows the field people to remind teams that they need inspection. The base sticker is applied when you pass weight, size, and safety. A small color for mechanical, electrical and pneumatics and then a large one for complete. Then a second one for the finals inspection on the second day. I would recommend keeping at least half the inspectors for finals inspection. This will be a small issue to deal with. Many inspectors who are available on practice day, also serve as refs, cuers, or other volunteers on the second and third day when inspection duties are less. Note to GDC: You might want to consider letting MI teams (who only register in MI) have one or two more days before ship/lock/bag to compensate for teams who have all practice day to modify and rebuild at other events. Last edited by Al Skierkiewicz : 15-08-2008 at 11:08. |
|
#2
|
||||
|
||||
|
Re: Inspections -- Solutions/Ideas
Al-
This might be a good thread to throw a link or description of how someone can become an inspector. Now that I have a few years under my belt, I am interested in learning. |
|
#3
|
|||||
|
|||||
|
Re: Inspections -- Solutions/Ideas
Ike,
Let me go through the simple process and then I will elaborate a little. I would invite other inspectors and leads to add to this as well. The simple answer is to sign up for inspecting as you would any volunteer position, through VIMS on the First website. You won't be able to sign up for an individual event until the site is updated for all the FRC events. You have to show a preference for each event you wish to volunteer. Event Volunteer coordinators will choose among all those that sign up and assign positions accordingly. You can complete the registration process though, when VIMS is open. You will be asked to supply sign on and password so you can reenter the site later. You will be asked for personal info and a few references. FIRST will contact your references so be sure to ask them before submitting their name. As to requirements, we have discussed some in the past but I don't know if any have been put into place. I have suggested the following: Inspectors should have served on an FRC team in a position that puts them in direct contact with the robot and the robot manual. Those wishing to inspect should have served in that capacity for at least two recent years. Lead inspectors should have served at least three years and have inspected at at least two events during that time. The time commitment for inspectors should be all day Thursday (or the first day of the event in MI) and at least most of the inspectors need to be present for final inspections late morning on Saturday. A few inspectors should assist in the inspection area during the entire weekend if possible. You will be asked to fill in what days you are available for each event on VIMS. Lead inspectors need to be present through the entire event up to the completion of the finals on the last day. Inspectors and Leads in particular are part of the front line in making sure teams have a great weekend. It is our responsibility to help teams get and stay ready to compete while insuring that the students are having a great experience. This is especially true in the case of rookie teams. Inspectors and Leads will keep rookies apprised of what is taking place on a given day and explain things we all take for granted like cueing, inspections, pit open and close, awards and judging. I know that there are documents that further explain the inspector and Lead duties and there is a To Do list for each day of an event. Last edited by Al Skierkiewicz : 18-08-2008 at 20:54. |
|
#4
|
|||||
|
|||||
|
Re: Inspections -- Solutions/Ideas
Quote:
I have been at regionals where both ways were used, the "mobile inspector" seems to work the best. One issue I always see is inefficiency in teams communicating inspection readiness. Maybe give the team small cards - when the roving inspector sees the card, they stop and inspect that subsystem. (This as a supplement to visiting the inspection station and asking for an inspection) Don |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Robot Shipping -- Solutions/Ideas | Ken Patton | District Events | 21 | 16-01-2009 14:33 |
| Awards -- Solutions/Ideas | Ken Patton | District Events | 2 | 23-08-2008 21:38 |
| Volunteers -- Solutions/Ideas | Ken Patton | District Events | 15 | 07-08-2008 20:39 |
| New inspections | Alavinus | General Forum | 17 | 10-03-2003 20:12 |