I think the CAW serves some important purposes, and there is legitimate reasons it should be kept around. That doesn’t mean there shouldn’t be significant reforms to the rules surrounding the CAW or the implementation of the CAW (I believe there should be). But as a fundamental practice, I believe the CAW should not only stick around, but possibly become a larger focus.
First off, theoretically it serves as a balancing lever between the “haves” and the “have nots.” At this point, it’s more of a token rule than a truly effective one, and it’s likely some serious reform to the rules is required if it were to serve its intended purpose. But even as a symbolic gesture it has some meaning. Ideally, we’d like the balance between teams to be in the effect of “the rising tide lifts all boats” rather than a cap that drags down the top. But anyone who’s ever been to sea knows that deep waters can feel a lot more choppy in fishing boat than they do on a cruise ship (let alone teams clinging to a raft). While the resources a team can pull in will always impact their performance in some fashion, as long as this remains an open competition for high school aged students, there should be some form of top end limit in terms of what is allowed to be spent on the robot itself. We have weight limits, size limits, and time limits. Cost limits should be part of the process as well.
Cost accounting and material selection are huge parts of real world engineering. Integrating them into the program in a formal manner is something that should continue, and possibly take on an increased role. In any professional engineering job, creating a list of materials is a critical task for a great many reasons. There are serious considerations given to total cost and individual component cost, both in terms of COTS items and custom manufactured ones. For example, anyone who’s attempted to design around purchase card requirements in order to avoid a lengthy contracting process knows what I’m talking about. Heck, even the strange loopholes and rules interpretations can be an all too familiar parallel to engineers in certain sectors.
I feel this type of analysis is hardly touched up on in FRC, and should not be eliminated. Like it or not, money is a driving factor in both engineering and society as a whole. Under ideal circumstances, I think cost competitiveness and the CAW should be taken into account for various engineering awards.
Now, how do we make the CAW better?
First off, as a token initiative, let’s go back to Bill of Materials. It’s a much better name than the Cost Accounting Worksheet. :rolleyes:
Next, the process should be streamlined and tools should be made available to help all teams complete their BoM in accordance with both the rules and intent of the rules in mind. I’m thinking something like an online tool that teams use to develop and maintain their BoM. Something like a shared web tool where teams can drag and drop common components into their list, as well as enter new items into the database that other teams can then investigate. Make the tool optional for a couple years to phase it in, but eventually make it the FRC standard for submission.
Finally, the rules should be updated. I’m not sure where things should land, but right now teams use all sorts of exceptions and exemptions to dodge around any meaningful cost limits. The $400 individual component limit should almost certainly be raised, especially considering vendors just find ways around it anyway. The fact the central robot controller (which is KoP exempted) doesn’t fit under than $400 limit even with steep FRC discounts applied speaks volumes. Secondly, they should find a better way to handle KoP exemptions and “counts as team member” labor costs. Part of me wants them to remove those exemptions entirely and then simply raise the limit of what can be spent accordingly. I don’t see reasons why a team’s business plan should mention a wildly different cost of parts that go into their competition robot than their BoM/CAW.