Creo View Doesn't "Do What It Says On The Tin" : Family Table Instance Can't Be Viewed
1. Describe your environment: What is your industry? What is your role in your organization? Describe your stakeholders.
We work in the scale model / toy industry. Our products range from high-detailed models to children’s toys which are sold worldwide across our brands. Our designers use Creo Parametric to develop products with a range of variations.
We aim to design as many variations as possible to enable us to manufacture as many versions of each product as possible – as a designer, the Family Table tool in Creo is essential to allow us to design parts with these variations:
- Parts are linked so changes to generic will update instances.
- Variant parts can easily be added to the Family Table if required.
- Key features can be designed once, then turned “on” or “off” as necessary.
- Family Table parts easily interchange them in assemblies as references are preserved.
This design process has worked for many years, but a failure for Creo View to accommodate this standard Creo feature threatens to slow our efficiency and adopt a slower, more convoluted method of design which will adversely impact product release dates.
2. What product and version are you currently running?
Creo Parametric 8.0.4.0 , Creo View Express 8.0
3. Describe the problem you are trying to solve. Please include detailed documentation such as screenshots, images or video.
Creo View is used by members of our team without full licenses (managers, manufacturing / production, graphics, QC) to view the CAD of products. The issue with Creo View is that instance parts (parts created via Family Table) cannot be viewed – the generic part opens rather than the correct instance. However, in an assembly, the correct instance is shown.
Creo View cannot handle family tables which are a fundamental tool in Creo, and is therefore not fit for purpose in its current form.
To allow our Creo View users to see the correct data, we have to export the files as a STEP so it can be opened in another software.
Alternatively, we stop using Family Tables. This would require an alternative way of designing which will be more time-consuming and less efficient. Although this would fix the viewing issue going forward, it would still not allow products from the past 20 years to be viewed correctly.
4. What is the use case for your organization?
Making Creo View usable allows the company to use PTC products and not rely on other software to complete a task that should be achievable.
5. What business value would your suggestion represent for your organization?
Creo View must have the functionality to correctly view Family Table instances. The alternatives are to export from Creo and open files in another programme or change the design process to not use Family Tables – both are time consuming and reduce efficiency.
Family tables have been a main feature of Creo going right back to its inception and the fact that Creo View does not let you view instances it incredulous.
