Atomic Knowledge · Creo Parametric

Generic & Instance (Creo)

Family table terminology — the 'generic' is the parent part defining all features; 'instances' are the variants defined by family table rows.

Experience: 10+ years
Credentials:
Last reviewed Editorial process

Definition

The generic is the parent (typical) variant — full feature tree, default dimensions and parameters. Each instance is a derived variant addressed by its name in the family table. Drawings and assemblies can reference specific instances by name.

When an instance is suppressed in the table, the instance shows up as missing geometry; activating it restores the variant.

Why it matters

Generic / instance discipline determines whether the family table is usable downstream. Inconsistent generic configuration produces instances that look right but break in assemblies.

Technical Deep Dive & Core Mechanics

From a geometric perspective, Generic & Instance (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.

Because B-Rep operations are highly dependent on predecessor geometry, modifications to Generic & Instance (Creo) require the solver to calculate parent-child relationships. To optimize performance and avoid topological naming reference losses, engineers must establish a robust modeling methodology, minimizing direct dependencies on complex chamfers or fillets in early feature tree operations.

Step-by-Step Professional Implementation

Deploying Generic & Instance (Creo) in a commercial design production pipeline requires a standardized, structured workflow to minimize model regression and file corruption:

  1. Parametric Alignment & Parenting: When initializing Generic & Instance (Creo), reference it strictly to stable datum planes or shared project levels. Avoid referencing ephemeral lines or sketches that may undergo topological naming changes.

Advanced Troubleshooting & Error Diagnostics

Parameter recalculation failures are highly disruptive during mechanical assembly rebuilds. Follow these diagnostic steps to clear feature errors related to Generic & Instance (Creo):

Cross-Discipline Collaboration & Handoff

In global multi-office projects, Generic & Instance (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):

  • Class Preservation: Ensure that Generic & Instance (Creo) is mapped to its correct IFC class classification (e.g., `IfcWallStandardCase` for walls, `IfcBuildingElementProxy` for generic parts). Unmapped components default to generic containers, losing their smart structural parameters.
  • Visual Overlap Verification: Run spatial clash checks regularly in a federated viewer to verify that no geometric overlaps or clearance violations occur between Generic & Instance (Creo) and structural frameworks.

Common pitfalls

  • Editing instances directly instead of through family table rows — diverges from the table.
  • Modifying generic without checking instance regeneration — instances break.
  • Excessive instance verification — slow assembly regen.
🛡️

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 Generic & Instance (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: Generic & Instance (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.