Open Source Automobile
For a long time I've thought that there could be an Open Source automobile. There would be many benefits, but also many problems. Here are my two starting points for thinking about this: the VW Beetle (old one) and RedHat.
The Bug was an incredibly versatile platform for a true People's Car (Volks Wagen). From the Baja Bug to chop tops, lowriders to ragtops, you can still find dozens of websites devoted to the car. It nearly was an open source vehicle in the sense that you could buy nearly any part (with the possible exception of the pan) from an aftermarket manufacturer. There were even shops dedicated to selling those parts, usually complete with a knowledgeable salesman/mechanic who can advise you on modifications, a rarity even at most factory-authorized dealerships these days.
The other model in my thinking has been RedHat. How do they make money selling something you can download for free? The way I understand it is that they make money three ways: first, they combine the free stuff into an easy-to-install package, saving you the time and effort to download and burn it all. Besides, if it's free off the internet, but you need to get on the internet to access it, you have to have something already running to access the free stuff - that's either a waste (buying an OS just to download a free OS) or an incredibly nerdy thing to do (having multiple computers in your house or using your friend's computer to download). The other ways RedHat makes money is by selling documentation and training. Some of the founders even work on custom applications.
Okay, so how do you transfer those models into brick and mortar manufacturing? Also, how do you deal with regulatory, quality control, and profitability concerns?
Here's a rough sketch of how I think it can be done.
The certification service would have two stages: one for the manufacture of parts, and another for assembly of completed vehicles. It would consist of an initial inspection of their plant and processes, and subsequent sampling of their products. Heck - you might want to use the better manufacturers for your own cars. People receiving such certification are getting the benefit of aready-made, proven, safety-tested design and the right to use your name or logo as a way of conveying the mark of quality to consumers. Once a network of certified parts manufacturers pops up, consumers will know that they can get high quality replacement parts. Small machine shops could use this to supplement their income, and a network of certified assemblers would make a ready-made network of repair shops.
By the way, this is almost an ideally Lean manufacturing process. Dozens of small shops located near their customers, each building one at a time. The certifying team should probably include a lean sensei to advise each shop on the latest poka yoke benchmarks.
The great thing about open source software is that dozens of small tinkerers can work on code to improve and/or customize it. I haven't talked about that aspect, yet. Basically, I envision a similar type of arrangement as Netscape has for Mozilla: anyone can tweak the code, but only the official version can be called Mozilla. If you want to make a new fender, that's fine, but it will not be certified. The Open Source Auto car company should establish a discussion forum on their website to allow people to introduce and trade new parts ideas. When something appears to be really popular, build a car with it, crash test it, and certify the new part and/or assembly.
I can see where version control would become a major challenge. The other possible avenue is that you have a few certified assemblies, but many parts certified for aftermarket use only (not manufacturing). Manufacturers who want to use the uncertified parts for original equipment manufacture are on their own - it's no longer a certified vehicle they are selling. Which brings up the problem of watering down the brand for everyone else.
You could possibly control this by phasing out older certifications and announcing up front that their would only be a few alternative assemblies allowed. Let's say you allow five powerplants (gas, turbodiesel, turbo gas, hybrid, electric), five body styles (plain, convertible, off road, hot rod, utility), who cares about color (not a safety issue), three interior designs (cloth, leather, performance). I think it's important right up front to attract two crowds: the street rodders and the enviromentalists. Once they find out about a company that encourages people to tinker with their cars, you're going to end up with a very creative design team.
The Bug was an incredibly versatile platform for a true People's Car (Volks Wagen). From the Baja Bug to chop tops, lowriders to ragtops, you can still find dozens of websites devoted to the car. It nearly was an open source vehicle in the sense that you could buy nearly any part (with the possible exception of the pan) from an aftermarket manufacturer. There were even shops dedicated to selling those parts, usually complete with a knowledgeable salesman/mechanic who can advise you on modifications, a rarity even at most factory-authorized dealerships these days.
The other model in my thinking has been RedHat. How do they make money selling something you can download for free? The way I understand it is that they make money three ways: first, they combine the free stuff into an easy-to-install package, saving you the time and effort to download and burn it all. Besides, if it's free off the internet, but you need to get on the internet to access it, you have to have something already running to access the free stuff - that's either a waste (buying an OS just to download a free OS) or an incredibly nerdy thing to do (having multiple computers in your house or using your friend's computer to download). The other ways RedHat makes money is by selling documentation and training. Some of the founders even work on custom applications.
Okay, so how do you transfer those models into brick and mortar manufacturing? Also, how do you deal with regulatory, quality control, and profitability concerns?
Here's a rough sketch of how I think it can be done.
- Get a design made at a design house to your specifications. I'd want something that was fairly plain but that invited customization, like a WRX.
- Build several of them and work the kinks out.
- Build a short production run and have them tested at the Insurance Institute.
- Resolve all of the problems and test them until you have a high rating.
- Get a website and publish the full drawing package. The drawings are available contingent on the user's agreement not to use them for profit unless he has been certified by you to manufacture the parts or vehicles.
- Begin building your own vehicles.
- Offer a certification service and charge money for it. Perhaps charge a percentage per part or car.
The certification service would have two stages: one for the manufacture of parts, and another for assembly of completed vehicles. It would consist of an initial inspection of their plant and processes, and subsequent sampling of their products. Heck - you might want to use the better manufacturers for your own cars. People receiving such certification are getting the benefit of aready-made, proven, safety-tested design and the right to use your name or logo as a way of conveying the mark of quality to consumers. Once a network of certified parts manufacturers pops up, consumers will know that they can get high quality replacement parts. Small machine shops could use this to supplement their income, and a network of certified assemblers would make a ready-made network of repair shops.
By the way, this is almost an ideally Lean manufacturing process. Dozens of small shops located near their customers, each building one at a time. The certifying team should probably include a lean sensei to advise each shop on the latest poka yoke benchmarks.
The great thing about open source software is that dozens of small tinkerers can work on code to improve and/or customize it. I haven't talked about that aspect, yet. Basically, I envision a similar type of arrangement as Netscape has for Mozilla: anyone can tweak the code, but only the official version can be called Mozilla. If you want to make a new fender, that's fine, but it will not be certified. The Open Source Auto car company should establish a discussion forum on their website to allow people to introduce and trade new parts ideas. When something appears to be really popular, build a car with it, crash test it, and certify the new part and/or assembly.
I can see where version control would become a major challenge. The other possible avenue is that you have a few certified assemblies, but many parts certified for aftermarket use only (not manufacturing). Manufacturers who want to use the uncertified parts for original equipment manufacture are on their own - it's no longer a certified vehicle they are selling. Which brings up the problem of watering down the brand for everyone else.
You could possibly control this by phasing out older certifications and announcing up front that their would only be a few alternative assemblies allowed. Let's say you allow five powerplants (gas, turbodiesel, turbo gas, hybrid, electric), five body styles (plain, convertible, off road, hot rod, utility), who cares about color (not a safety issue), three interior designs (cloth, leather, performance). I think it's important right up front to attract two crowds: the street rodders and the enviromentalists. Once they find out about a company that encourages people to tinker with their cars, you're going to end up with a very creative design team.
Labels: energy
<< Home