Go to Post For example an iron block is very simple and very robust. Strap a control system on it and it will meet the requirements of being a FIRST robot. However, it sure doesn't do very much, nor is it innovative. - sanddrag [more]
Home
Go Back   Chief Delphi > FIRST > General Forum
CD-Media   CD-Spy  
portal register members calendar search Today's Posts Mark Forums Read FAQ rules

 
 
 
Thread Tools Rating: Thread Rating: 11 votes, 5.00 average. Display Modes
Prev Previous Post   Next Post Next
  #12   Spotlight this post!  
Unread 04-03-2012, 11:09
Kevin Sevcik's Avatar
Kevin Sevcik Kevin Sevcik is offline
(Insert witty comment here)
FRC #0057 (The Leopards)
Team Role: Mentor
 
Join Date: Jun 2001
Rookie Year: 1998
Location: Houston, Texas
Posts: 3,727
Kevin Sevcik has a reputation beyond reputeKevin Sevcik has a reputation beyond reputeKevin Sevcik has a reputation beyond reputeKevin Sevcik has a reputation beyond reputeKevin Sevcik has a reputation beyond reputeKevin Sevcik has a reputation beyond reputeKevin Sevcik has a reputation beyond reputeKevin Sevcik has a reputation beyond reputeKevin Sevcik has a reputation beyond reputeKevin Sevcik has a reputation beyond reputeKevin Sevcik has a reputation beyond repute
Send a message via AIM to Kevin Sevcik Send a message via Yahoo to Kevin Sevcik
Re: Ruling on Robonauts Balance

Quote:
Originally Posted by pfreivald View Post
The same way engineers do when given design specifications. The English language is imprecise, but "can't grab, grasp, or grapple" is at least highly indicative of the customer's design specs. If an engineer comes up with a solution that can be argued to not grab, grasp, or grapple, and yet it can be argued to do so as well, they'd better be prepared to suck up the opportunity cost of having designed/built that mechanism, because the customer might reject it.
Part of the whole design and specification process involves discussions with the customer, right? RFI's, design reviews, discussions of scope of work, all that fun stuff. It seems to me that the Q&A serves the same purpose in our FRC world. So I'll ask again in terms more familiar to you. How would you react if you went to a design review and the customer shrugged and mumbled about your fancy, innovative design?

On one hand, you can move forward with your innovative design that you think meets all their specifications. And risk them seeing the finished product and declaring that that isn't at ALL what they were thinking, didn't you hear them mumble that?

On the other hand, you can take the most defensive and restrictive interpretation possible of the specifications, and reach a design that couldn't possibly be a problem. At the expense of forgoing any real innovation or creativity in your solutions. But at least you won't have any nasty surprises in store for you.

On the gripping hand, none of this angst, indecision and heartache would have been necessary if the customer simply held up his end of the deal and actually provided you with information and input on his expectations. If they simply actually answered your question clearly the first time you asked it instead shrugging and declaring the can't comment.
__________________
The difficult we do today; the impossible we do tomorrow. Miracles by appointment only.

Lone Star Regional Troubleshooter
Reply With Quote
 


Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT -5. The time now is 17:19.

The Chief Delphi Forums are sponsored by Innovation First International, Inc.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi