Atomic Knowledge · Creo Parametric

Family Tables (Creo)

The Pro/E heritage feature for representing a family of parts — generic part + instance rows controlling dimensions, parameters, suppression, and component substitution.

Experience: 10+ years
Credentials:
Last reviewed Editorial process

Definition

A family table is an Excel-like table inside a part or assembly file. Each row is an instance (e.g., M6 x 25 vs. M6 x 30 vs. M6 x 40). Columns specify dimensions, parameters, feature suppression, materials, custom properties. Instances are addressed by name in BOMs and drawings.

Nested family tables allow instances to have their own sub-tables.

Why it matters

Family tables are the canonical way to represent product families in Creo — fasteners, brackets, gears, plates of varying thickness. Done well, one .prt represents thousands of variants.

Technical Deep Dive & Core Mechanics

From a geometric perspective, Family Tables (Creo) represents a parametric boundary representation (B-Rep) mechanism within Creo Parametric. The underlying geometric modeling kernel—whether Parasolid, ACIS, or a proprietary solver—maintains a strictly ordered history tree (Feature Manager). Each operation stores topological references (faces, edges, vertices) that are re-evaluated sequentially during model regeneration.

Cross-Discipline Collaboration & Handoff

In global multi-office projects, Family Tables (Creo) is a high-frequency handoff node between diverse software packages. During cross-platform export (for example, exporting Creo Parametric drawings to IFC for coordination in Navisworks or Solibri, or converting mechanical STEP files into BIM detail families):

Common pitfalls

  • Family tables without naming conventions — instance names become opaque.
  • Missing dependencies — instance generates wrong geometry because a referenced dimension isn't in the table.
  • Excessive instances (10k+) — file becomes unmanageable.
🛡️

This concept is a core structural element of the Creo Parametric drafting and engineering environment developed by PTC. PTC's parametric MCAD — the descendant of Pro/ENGINEER, strong on top-down design, MBD, and integration with Windchill PLM.

Explore Creo Parametric Profile › About PTC ›

Relevant Creo Parametric FAQs

Direct answers from our technical editorial desk concerning related workflows.

❓ Is Creo the same as Pro/ENGINEER?

Yes, in lineage. PTC rebranded Pro/E as Creo in 2010 and introduced the Creo Apps architecture. Functionality has continued to evolve since; modern Creo is significantly different from late Pro/E in UI and direct-modelling tools, but the parametric core is the same.

❓ What's the difference between Creo Parametric and Creo+?

Creo+ is the cloud-connected variant — design data managed in PTC's Atlas cloud platform with collaboration features. The Creo Parametric authoring engine is the same. Creo+ targets distributed teams; Creo Parametric remains the file-based / Windchill-based standard.

❓ Can Creo open SOLIDWORKS files?

Yes, via the Creo Unite interface (or by importing STEP/Parasolid). Unite handles native SOLIDWORKS, NX, CATIA, Inventor files directly inside Creo, with options to maintain the original or convert.

⚡ Concept Self-Test

Question 1

When working with Family Tables (Creo), which of the following represents a common technical pitfall?

🌳 Semantic Crossroads & Navigation Pathways

Trunk-Branch-Leaf Model
Trunk

Core glossary, interactive graph, and domain-wide concept index.

Branch

Parent design environments and platforms implementing this method natively.

Leaf
🍃 Active: Family Tables (Creo)

Discover More

Sources & further reading

Was this conceptual reference clear and helpful?
✓ Thank you for your feedback! Your input helps shape the CAD curriculum.