Research & summarize the feezability of developing corporate ERP based on Ruby, most notably to leveraging Google's technologies (Sketchup, Earth, Streetview etc.) as well as a 'Dell' style config-to-order of a revolutionary automobile as featured in the Automotive X-Prize.
Obviously there is more to this than can post here as well as we need to work with top canidates before selecting a winner.
The final product will be a flow-diagram of 'order system' as well as some 'live' proof-of-concept.
Our corporate mantra is win-win and honor established relationships so chances are winner of project will likely be developing said ERP system.
I am hoping a lot of the detail specifications will be self-evident and the contractor will take the initiative in 'filling in the blanks' (cust #, part #, data structure, error handling etc)
If you would like to familiarize your self with our product at our website and start thinking of how you would design a config-to-order system for a car.
Check out Dell.com for an example of what we envision.
We are planning on heavily leveraging Google's technologies (earth, 3DWarehouse, Sketchup, GrandCentral etc) into our enterprise apps and vehicle NAV systems.
We see the user picking a frame, motor, suspension, and body and being able to zoom in/out 3D (parts live in 3D Warehouse, 'snap' in specific places).
Once ordered the saved file becomes a Google earth object track able on the corporate server. Once production is planned 'Google earth object' Moves to production - where once assembly starts user is notified and they can view live / recorded video of 'car' being made.
Once the GEO is made it is tracked accordingly until the owner takes receipt. At which time the car, if so equipped, can be 'on-line' and use a bunch of web-apps (grand central / Skype for VoIP, earth for NAV etc.)
From what I've read Ruby is at the crux of most of these technologies and is so, our foundation should follow suite (GNU, back-end. syntax, best practices etc.)