cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

General renewal of the cabling interface

General renewal of the cabling interface

I'm a longtime Creo user (from Pro / Engineer 16) and a former PTC employee.

I would like PTC to invest in the renewal of the Cabling interface and workflow that I think are definitely dated.

It is not possible that in 2020 this module still has a strong presence of the old hierarchical menus it had in the old Pro / Engineer (especially with regard to the harness part).

While up to the Mid 90's was understandable the massive use of these hierarchical menus (due to the lack of power of the graphical cards), now it makes no sense.

As PTC is pushing towards the augmented reality that needs a Digital Twin, this Digital Twin should be easily built by designers even for the Cabling / Piping point of view.

If PTC wants to continue to be a market leader in the MCAD sector, must not only develop new "Wow" technologies (such as topological optimization, for example ...) but also invest a part of the new subscription model revenues to update and improve its fundamentals without which everything else makes no sense.

 

2 Comments
Amethyst
I can only agree. There needs to be a serious update on the Cabling interface. Every time I hold a Creo update course, the users ask me "What about Cabling? Has it been improved?" and I'd love to be able to answer something more than just "Now you can do striped cables!". Though fixing the fixed length problem was a huge relief!
Contributor

Other considerations that can be made are the following:

  1. Browsing the internal database of the CREO courses, the last update of the Cabling and Piping courses is related to CREO 4.0... therefore also the training material is definitely obsolete (or maybe there is nothing really new...).
  2. The disheartening thing is to compare the Cabling and Piping solutions with the homologous solutions of the other MCADs which are definitely simpler to use and much, much... much more intuitive.
  3. It would also be also very interesting to integrate these two modules with Mechanism. I would like, for example, to see a cable fixed to a mobile element that deforms itself when this element moves (to identify problems of excessive stretching of the cable itself). Other MCAD can deal this... so it is a problem that can be solved...