Software like the Linux operating system is developed by opening it up for anyone to tweak and add features and generally make it do what they want. Its inner workings are non-proprietary and completely public so that the power of crowdsourcing can be harnessed to continually fine-tune and improve the product. I've been wondering why nobody has thought of applying the same open source principle to vehicle manufacture. Well, it turns out it is being done, right now.
Jeff Jarvis, in his new book What Would Google Do?, writes about the concept of allowing purchasers to request exactly what features they want in their car, ordering direct from the manufacturer. Ford, GM and the like aren't in the business of manufacturing anyway - they just assemble parts that have been manufactured to their specifications - so why don't they go all the way and focus on transportation as a service rather than a mass-produced vehicle that forces buyers to pay for features they don't want?
The brand would become what you want it to be, and by allowing customisation the manufacturer would discover what we really want, not guess what they think we want. Just the way Google learns from our searches what information we want to see, and focuses on designing the information systems to make that possible, auto manufacturers could focus on making customisation possible. It doesn't suit their current business model, but that's not to say it can't be done. The big-name auto manufacturers have clearly failed to make a success of their businesses anyway.
We're not quite at the stage that Jeff Jarvis is proposing, but there is a nonprofit company working on an open source car that is a contender for the automotive X Prize. The Society for Sustainable Transportation calls it the Open Source Green Vehicle, and it's being designed through a collaborative international effort. All design data and test data will be shared and accessible from the internet.
Open source software needs to work within agreed standards so that anyone who designs a module to run in an operating system like Linux can know how to get the components to communicate with each other. The operating system is a platform that other software can "plug in to", but it doesn't dictate how that other software works. A key concept of the OSGV (known as the Kernel™) is that any fuel source can be used by plugging it in to the vehicle - a physical version of a software module. As with software development, the OSGV needs specifications so that if someone wants to develop a new energy source for the vehicle, they can design the interface between the energy module and the car in accordance with those standards - but the inner workings of the energy module can be designed without constraint.
This breaks down the barrier to entry for alternative fuels because Kernel™ owners don’t have to buy a new car when they want to use a different fuel. Each power source module is self-contained. Simply swap out the original power source module with a different one. Onboard computers will automatically adapt to the new power source module. And, it’s that easy; A qualified facility can complete the conversion in merely hours.
I like it. But that's just a start.