Thanks again to all who replied.
It was determined that because we have to label each cable with the
reference designators, each cable we route will actually need to have a
unique number.
However, I did receive some great replies. Please see the attached
presentation as well as the replies below:
With the customers that I do cable consulting with, in a single
assembly, I normally just add a suffix such as "_A", "_B", "_C", etc to
the main cabling assembly part number. These types of suffixes can be
filtered out of a BOM so all of the cables look to be the same. If the
same cable is required in different assemblies as you stated in your
message, I normally put the cable assembly part number, then and
underscore and the assembly number. If more than one of these cables is
used in this assembly, I then resort to adding a "_A" as mentioned above
behind the assembly number. This dual set of prefixes can also be
filtered out of a BOM. Hopefully this makes sense.
We just append the name with something related to the usage or the next
assy, such as xxx-xxx_pwr_cable.asm
If we have an off the shelf cable, 999999. and we use it in assembly
123456. We make a routed version of the cable and name it
999999_123456.asm.
You can choose if you want the BOM to show the routed version.
or
If you Insert> Include (so it does not show in the model) a straight
version of the cable in your model and filter the routed from the BOM.
"This is a tough question to answer. You could use family tables of
harnesses, but my experience is that they are very difficult to use so
that you can get the correct routes in for different installations. I
prefer to create a wiring diagram in RSD for the standard cable and
export the XML file of all the connections. Then you can assemble the
connectors where they need to be, create a network, autoroute the cable,
then set the length/adjust the route to get the cable length the same.
Of course this means you have different part numbers for the
cables/harnesses, but I think that problem can be overcome".
Thanks for sharing your expertise,
Dax Williams
Engineering E-Tools Administrator
GE Healthcare OEC
Surgery
-
384 Wright Brothers Dr
Salt Lake City, Utah 84116
This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.
