Page 1 of 1

Engineering data management project

Posted: Fri Dec 07, 2007 10:57 am
by HaMBoNE79
I would like to start a project for a web based CDM (CAD data management) and EBOM (engineering bill of materials) and solution, but I'm not a programmer. I can write a little php and perl and I know enough about databases to be dangerous, but I would need some help from web developers interested in working on such a project.

My motivation for this project is simple...I am a mechanical engineer that is addicted to Linux (and open source) and I know there are alot of people that could benefit from this kind of software (which is why I want it to stay open source). I'm not talking about big corporations (most of them have more than enough money to buy a turnkey CDM/EBOM solution)...I'm talking about small machine/fabrication shops, small engineering firms, and the individual that just enjoys tinkering.

I know that this type of project would require a lot of work and it may be a year before a usable version is written, but I would really like to get it going. Even though my programming skills are lacking, I have several years of experience in managing CAD data and EBOMs for my company. I know what features are most important and I could provide a very detailed roadmap for the project.

If anyone is interested in working on something like this or can give me some pointers on how to get a project like this off the ground, I would really enjoy hearing from you.

Thanks!

Posted: Fri Dec 07, 2007 11:35 am
by HaMBoNE79
I should probably explain a little more about this stuff...

For starters, the CDM program would be a simple program for checking CAD files in and out. It would allow the user to keep several revisions of the part and would allow a user to lock the part so that other people can not make modifications. In a way, I guess the CDM program would be similar to the CVS software that programmers use.

The EBOM component would be more complex. At the very basic level it would provide a means for the user to add a list of sub components and quantities that make up a part (i.e. an upper level part would be comprised of the following sub components: 3 hex bolts, 3 washers, and a plate). A description of each of these parts would be stored in a database and everything would be linked together in such a way that the user can see all the components that make up a part or see all the assemblies that the part goes in to. This system would also need to provide a Engineering Change Number (ECN) system so that changes to the BOM can be tracked. If a user would like to make a change to an assembly, they would ask the system for a ECN and then create a markup that tells which parts would be removed and which parts would be added.

This system would also need to have the ability to generate part numbers, store supporting documents (i.e. a laser cut pattern for a sheet metal part or an Adobe Illustrator file for a decal), and to link to a drawing of each part in the database.