Cerebel module development

The task is to extend an existing software application by another module. We require the sucessfull bidder to sign non disclosure agreements and to agree to our terms and conditions. Object relational mappers are to be used. Access to the application is first over our webservers. We require regular builds and monitoring of progress. This task requires excellend communication skills, excellent software architecture skills. Only bid if you consider yourself as being experienced. The task in itself is a relative straight forward one, however it requires liaising and tieing in information provided by other developers. It also requires mapping an existing database model to a new one, with a similar functionality and structure. We would assign you one in-house developer to support you with this task and to assist in providing insight into the existing application. 1) The current application, organizes content (mainly files) and metadata in projects and activities. Content is tailored to support knowledge workers (engineers, draughtsman) to work more efficient with CAD files and project related data. 2) The goal is to extent the current model, to also allow the management of components in a similar fashion, which can then be assigned to activities and projects. (I.e. A "roof" has sub components, roof tiles and roof beams, which cost "x" are sourced from "y" and weight "z") and the component "roof" is assigned to activity "A" (making the roof) and project "house" (with roof as a sub component) 3) The module has to remain a seperate entity but must be integratable into the host application as an extension 4) Each component and the sub componets are to be given an ID and the ID needs to be printable in form of a QR code 5) A seperate development task is going to create an iPhone app, to read such barcodes to then re-produce and query the metadata that have been assigned to it. 6) Additonally to the metadata to be created by the component referene files and images shall be assigned. Images shall be shown as a preview (at i.e. 200x200 pixels, shrunken and cropped down automatically.) 7) A page needs to be created to create an entity vendor, with vendor details 8) A page needs to be create that contains a simple table, similar to EXCEL to calculate the cost of the components 9) All components are to grouped in components groups (i.e. group 1 motors, group 2 building material, group 3 house systesm 10) At the very least each component has a vendor, a project, a component group, cost and weight and one image for reference purposes. 11) Cost and weight are to be integrated and summed up in the existing application and are to be shown on project and activity level (i.e. The project house, with "n" activites, has "X" components assigned to it, "Y" cost in total, and "Z" total weight)