Replies: 1 comment 4 replies
-
I'll leave the discussion open for others (I couldn't find this discussed in a way that I understood it when I was looking previously, maybe others will benefit), but I think I understand now how to do this. Parameters is the way. I created two Parameter Templates in the Admin section, ECR (Engineering Change Request) and an ECO (Engineering Change Order). Then I added them to an existing part. I was thinking this would be tedious to add to all parts, but I think it might be okay as you'd only want to change it when you're doing a change to the part anyway. For an ECR/ECO process, after playing with this for a bit, I think i'll set the IPN to be the part number and the revision together, ie. 10-12345-002-A3. Change Requests can be tracked with an ECR property (which would correlate to an ECR document listing the requested changes). When a part is revised and the changes are made, as part of completing the ECO I would duplicate the part, give it a new unique IPN with the next revision (say10-12345-002-A4), and mark the old one inactive. Then I can add the ECO parameter with an ECO number that would link to the ECO documentation releasing that revision. Does anyone see an issue with that? This will end up adding two records to each part number's Parameter table... Are there any issues with this table getting large? |
Beta Was this translation helpful? Give feedback.
-
Is there a way to add a custom field to the Part database? I'd like to add an ECO field to track the Engineering Change Order that released the part. Maybe an ECR field would be useful to track any ECR's logged to request changes in the next revision would be useful as well.
But in general, is there any way to do this? I've been looking at Parameters but that seems to be something i'd have to add from the Admin panel on a per-part basis...
Beta Was this translation helpful? Give feedback.
All reactions