We are sometimes asked for eDrawings assembly files of our equipment, either by our shop floor, or by our customers.
We are unsure how we should control these files, in terms of data management/workflow.
In our PDM Standard system, we have 2 workflows, one for documents and one for CAD objects. The CAD objects workflow goes through the usual WIP, Check, Release, Change In Progress, Check, Release cycle, with full revision control. This workflow is used for SLDPRT, SLDASM and SLDDRW files.
The Document workflow is used for more or less anything that isn't a CAD document - DXF, PDF, STP, STL, DOC, etc. that we think needs to be traceable. Filenames include the revision of the file, in an attempt to have some traceability when we send any of these files outside the company.
The question that is vexing us today, I suppose, is whether an eASM file is a CAD object or a document.
I lean towards it being a document, since it is a representation of the CAD data, rather than being the CAD data itself.
How do others handle this?
Bear in mind that, since we are PDM Standard users, we have no more States available, so we have to shoe-horn these files into one or other of our existing workflows.