Skip to main content
Mar 12, 2024 3:57 PM UTC
Acknowledged

Cable Harness service loops and dressing/management capability

Related products:Creo Parametric

Please include detailed documentation such as screenshots, images or video.

1. What product and version are you running?
Creo 8


2. What is the problem?
Current cabling workflow does not have a straight forward way to add a service loop to a routed cable in a 3D model or allow the cable to be looped/routed back on itself, this requires manual addition of offset locations and is very time consuming

3. Are you using a workaround? If yes, please describe it.
Yes, we create a network going through the cable management features in the assembly, then route the cable through the network, then add in offset locations until the service loop appears as designed, in places where we need the cable to be dressed by manufacturing we again create a looped section in the network and then route the cable through this loop and create offset locations to give the appearance of a dressed extra length of cable.

4. What is the use case for your organization? Describe how your idea would work in context or how it would apply to a practical situation.
In our rack based system, we often have service loops between components to allow field service, we also have cases where items move, so the extra length is necessary. Some times we reuse COTS cables that are too long for the application and we will dress this extra length and manufacturing needs to know how we are prescribing that to develop their process.

5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)
very few people are comfortable with cabling as it is right now, and even less doing manual routed features like this, so its usually bottlenecked at 1 or 2 people in the company, so quite the impact and lost productivity

2 replies

Mar 13, 2024 8:16 AM UTC
Status changed to: Acknowledged

Hi @JavierL!

Thank you for your idea. Based on the information you provided, we are acknowledging it as the Community management team. This is not a commitment from the Product team. Other users may comment and vote your idea up.

Mar 13, 2024 8:48 AM UTC
Status changed to: Acknowledged

Hi @JavierL

This is a known requirement, and I am planning to address it in the mid-term future.