What is a parametric object in BIM?

An object defined by parameters and rules rather than fixed geometry: you set values (width, height, fire rating) and the object generates its own shape and carries its own data accordingly. Change a value and the geometry and every schedule that reads it update together. It is the opposite of a drawn shape — the parameters drive the object, not the other way round.

What is the difference between a family, a type and an instance?

A family is a category of object with shared rules and parameters (e.g. single-leaf door). A type is a specific named variant within it (e.g. 900×2100 60-minute fire door), with the values fixed. An instance is one actual placement of that type in the model (the fire door in stair core 2). Edit the type and every instance follows; edit an instance and only that one changes.

If I change a type, does it really change every copy?

Yes — every instance of that type inherits the type's values, so editing the type updates all of them at once. That is the whole point of the hierarchy, and it is why global changes (a fire officer upgrading a rating, a client swapping a finish) are one clean edit rather than hundreds. The same mechanism means a wrong value on a type is instantly wrong everywhere, which is why type discipline matters.

What should be a type parameter versus an instance parameter?

Put things true of every copy on the type (construction, fire rating, material, cost, finish) and things unique to one placement on the instance (location, mark/tag, swing direction). Getting this split right is what makes global changes a single edit and keeps schedules meaningful; getting it wrong forces manual editing or causes unintended global changes.

Lesson 3.1

Building Information Modelling/Module 3 · The Model & Its Objects

Lesson 3.1 · The Model & Its Objects

Parametric Objects: Families, Types, Instances

Why a BIM object is a rule, not a drawing — and change flows through it

12 min Interactive lessonFree · open lessonByAmogh N P· Architect & interior designer

The hook

Change one door type. Watch two hundred doors change with it.

In a drawing, two hundred identical doors are two hundred separate acts of drawing. Change the design and you edit two hundred things — and miss a few.

In a BIM model, those two hundred doors are two hundred *instances* of one *type*, and the type is one *family* with rules. Change the type once — make it 60 minutes fire-rated instead of 30 — and all two hundred update in the same breath, because they were never copies of a drawing; they were all references to the same rule. A BIM object is not a shape you drew. It is a set of parameters that generates the shape — and that single idea is the engine that keeps a whole model consistent.

Two hundred doors, one edit. Or one wrong value, two hundred broken doors. Same lever.

Parametric: the object is defined by rules, not by lines

A traditional drawing of a window is a fixed arrangement of lines. To make it wider you erase and redraw. A parametric object is different: it is defined by *parameters* — width, height, sill height, frame depth, glazing type — and by rules that say how the geometry follows from them. Set width to 1200 and the object draws itself 1200 wide; change it to 1500 and it redraws, correctly, with the frame and glazing adjusting to suit.

This is why BIM objects feel alive. You are not pushing lines around; you are setting values, and the object obeys. And because everything that reads from the object — the plan, the schedule, the quantity — reads its *parameters*, changing a value updates every one of them at once. The parameter is the single point of truth for that object, exactly as the model is the single source of truth for the building.

Zoom

A parametric object is a rule, not a drawing. Set the width parameter and the object generates its own geometry; change the value and the shape — and every schedule that reads it — redraws itself. The parameter is the single point of truth for the object.

Family, type, instance: the hierarchy that carries change

Parametric objects are organised in three levels, and the whole logic of a BIM model depends on getting them straight.

A family is a category of object with shared behaviour — 'single-leaf door', 'casement window', 'rectangular column'. It defines what parameters exist and how the geometry is built. A type is a specific, named variant within a family — 'DR-01: 900 × 2100 solid-core 60-min fire door'. It fixes the values that make this variant this variant. An instance is one actual placement of a type in the model — the specific fire door in the wall of stair core 2 on level 3. Instances can still carry their own per-placement values (this door's exact location, its swing direction, its mark), but they inherit everything else from their type.

The payoff is directional change. Edit a type and every instance of it updates — two hundred doors, one edit. Edit an instance and only that one door changes. This is not a filing convenience; it is how a model of tens of thousands of elements stays coordinated without anyone policing it by hand.

Zoom

The hierarchy that carries change. A family is the rule; a type is a named variant with values fixed; an instance is one placement. Edit a type and every instance of it updates at once; edit an instance and only that one changes.

A family is the recipe. A type is a dish on the menu. An instance is the plate on your table.

The power cuts both ways

The same mechanism that propagates a good change propagates a bad one. Set a wrong value on a type — the fire rating, the material, the cost — and it is instantly wrong on every instance, confidently and invisibly. The efficiency that lets one edit fix two hundred doors also lets one mistake break two hundred doors.

So parametric power demands parametric discipline. Decide deliberately what belongs to the type (things true of every instance — the door's construction, rating, cost) versus the instance (things true of this one placement — its location, mark, hand). Get that split wrong and you will either be unable to make a global change cleanly, or you will make one you did not intend. The families and types you set up early are the grammar the whole model speaks in; sloppy grammar early becomes expensive noise later.

Visual model

Edit a type, or an instance — see how far it flows

Edit a type vs. an instance — watch how far the change flows

DR-01#1

core 2 · L3

30-min

DR-02#2

core 1 · L2

30-min

DR-01#3

core 2 · L4

30-min

DR-01#4

core 3 · L1

30-min

DR-02#5

core 1 · L5

30-min

DR-01#6

core 2 · L6

30-min

Family: single-leaf door. Six instances of two types. Try an edit below.

The worked example

Three altitudes on the same idea

Read the band that fits you — or all three.

StudentLearn the idea

Learn the three levels. A family is a kind of object (single-leaf door) with rules and parameters. A type is a named variant (900×2100 60-min fire door) with the values set. An instance is one placed in the model (the fire door in stair core 2). Edit the type → every instance updates. Edit one instance → only that one changes. And it is all *parametric*: the object is defined by values (width, height, rating), not by fixed lines, so setting a value redraws the object and updates every schedule that reads it.

PractitionerDo it on a project

Decide what lives where. Your daily skill is putting each property at the right level: things true of every copy go on the type (construction, fire rating, cost, finish); things unique to a placement go on the instance (location, mark, swing). Get this right and global changes are one clean edit; get it wrong and you are either editing hundreds of instances by hand or accidentally changing all of them. Build and reuse a disciplined library of families and types — it is the grammar every drawing and schedule inherits, and the biggest lever on model quality you control.

BIM LeadDecide & govern it

Govern the library. At project or organisation scale, the families and types are shared infrastructure: a controlled library with naming, classification and agreed parameters is what makes models consistent across teams and reusable across projects. Left ungoverned, every modeller invents their own doors, schedules will not add up, and data cannot be trusted. Set standards for how families are authored, what parameters they must carry, and who curates the library. The parametric hierarchy is powerful precisely because change propagates — which means the standards that shape it are not bureaucracy, they are risk control.

Misconception check

“A BIM object is just a smart 3D block — a shape with some data stuck on it.”

It is the other way round: the object is defined by its parameters, and the shape is generated from them. A parametric object is a rule, not a drawing — set the width and the geometry follows; change the type and every instance follows. This is why a BIM model stays coordinated: nothing is a static copy, everything is a reference to a governed value. Thinking of objects as 'shapes with data attached' misses the engine — it is the parameters that drive the geometry, not the geometry that carries the data as a passenger.

Try it

Do it yourself

Map the hierarchy onto objects around you — you will start seeing families and types everywhere.

1Look at the doors in the building you are in. Group them: how many *types* are there really? (A main entrance type, an office door type, a toilet door type…) Each repeated door is an *instance* of its type.
2Pick one type and list what is true of *every* instance of it — its size, material, rating. Those belong on the type.
3Now list what is unique to *one* door — its location, which way it swings, its tag number. Those belong on the instance.
4Finally, imagine a fire officer requires every 30-minute door on an escape route to become 60-minute. In a drawing you would hunt down each one. In BIM you change the *type* once. Write one line: which doors would you want to be one type for this to be a single edit — and what does that tell you about setting up types deliberately from the start?

Take this with you

The one line to carry out

A BIM object is parametric — a rule that generates geometry from values — organised as family → type → instance, so change flows exactly as far as you aim it: edit a type and every instance follows, edit an instance and only it does. That propagation is what keeps a huge model coordinated without hand-policing, and it is why the discipline of deciding what belongs to the type versus the instance is one of the most consequential habits in all of BIM.

Related concepts in the glossary

Parametric Family / Type / Instance BIM object Single source of truth

Recap

BIM objects are parametric: values drive the geometry, not fixed lines. They live in a hierarchy — family (the rule) → type (a named variant) → instance (one placement). Edit a type and every instance updates; edit an instance and only it changes. The power propagates errors as fast as fixes, so deciding what belongs to the type versus the instance — and governing the family library — is core discipline.

Carry forward →

We know how objects are structured and how change flows through them. But what does an object actually *hold*? Next: geometry plus data — the two halves of every object, and why the data half is the one that makes it BIM.

The author

Amogh N P

Architect, interior designer, and creative polymath. Studio Matrx began in his notebooks — his vision of design made honest, useful, and open to everyone. Its Academy is written and taught in his memory, and free, forever.

More about Amogh →