Tomorrow morning, on 1 September 2026, the fourteenth edition of our Building System Specialist Title opens its doors. We say that plainly because the number matters more than any launch noise: fourteen cohorts is not a pilot, it is a curriculum that has been sanded down by every group that ran it before you.

Here is the shape of it, without the sales gloss. Five months, roughly six hours a week, built around Grasshopper and carried into whichever BIM host you actually work in — we run the Title dual-track, Archicad and Revit, because the underlying logic is the same and your employer is not going to switch platforms for a course. You start with the puzzle pieces — parameters, rules, the smallest honest geometry — and you finish by shipping a capstone in front of a room. As we wrote when we first rebuilt the Title (Become a Building System Specialist in just 5 months), the point was never to hand you twenty disconnected mini-courses. It is to let you see the whole system.

What does “seeing the whole system” buy a working desk? Watch what our graduates build. Last edition closed with Pablo Levine Mardones — seven years at ETH’s D-ARCH — presenting the parametric spine of a new generation of Vertical Gyms, the social typology Hubert Klumpner developed through Urban-Think Tank, now under construction across Medellín. Pablo parametrised the competing systems of a tight municipal site and let Galapagos — David Rutten’s evolutionary solver inside Grasshopper — hunt for configurations that balanced sport, culture, circulation and services, then piped the chosen option straight into the BIM model for coordination between Switzerland and Colombia. That whole chain is the Title in one graduation stream.

The sharper proof is what happens back at the office. Sebastian Lieb built his capstone as a live bridge — Archicad to Dlubal to Grasshopper to Excel — and now runs it at Pirmin Jung, a Swiss engineering house specialised in timber structures. That is the trade-off we are honest about: a course cannot make you a structural engineer, and a self-built connector you don’t fully understand is a liability, not an asset. The Title’s answer is to make you build the thing yourself, slowly, so you own its failure modes.

This is where the timeless mechanics help. Archicad since v24 keeps a Structural Analytical Model current in the background — beams and columns abstracted to 1D members, slabs and walls to 2D — and exports it through the Structural Analytical Format (SAF) to solvers, sidestepping the silent data loss of a naive IFC round-trip. If you want to see where that Archicad automation actually lives on your machine, our Archicad add-ons (PAZ-BOX, and PAZGPT for chatting to the model in GDL terms) sit exactly on that seam. The Title teaches you to build across it by hand first.

←TODAY: A timber engineer at Pirmin Jung ships his own Archicad–Dlubal connector as a graduation project, in 2026. →3012: Every office in the valley writes the small tools it needs, because no one waits for a vendor to notice. Fulcrum: The connector matters less than the person who can rebuild it — packaging the workflow is the engineering, and that is the thing a school can actually teach.

Hack: Rebuild the meaning, not just the geometry. When you push a model across a live connection, the shape crosses clean but the labels often do not — the first output of a Deconstruct component drops, the geometry output survives. So recover the meaning from the geometry you trust. In GHPython, tag slab faces by their normal instead of trusting a lost element type:

import Rhino.Geometry as rg
# brep crossed the exchange clean; its element labels did not
faces = list(brep.Faces)
slabs = [f for f in faces
         if f.NormalAt(0.5, 0.5).Z > 0.9]   # up-facing = slab tops
print(len(slabs), "slab faces recovered")

One rule, learned the hard way in front of a live audience: do not ask the exchange to carry meaning you can rebuild yourself.

Atelier: For an office weighing whether to send someone into a five-month course while the deadlines keep coming, the real question is not “can we spare the hours” but “who owns our automation when the one person who wrote it leaves.” Monday move: pick the single most-repeated manual step in your current model — the load export, the window schedule, the slab tagging — and write it down as one sentence. That sentence is the capstone brief; the Title is where it becomes a running tool.

We keep the doors on this Title deliberately narrow, because depth needs small rooms. If tomorrow’s start is too soon for your desk, read the BSS Title page, then bring one honest workflow you’d want to automate to the first session — that, not the software, is what turns five months into a tool you’ll still be running in five years.

Sources & Further Reading

• Primary: PAZ Academy — Building System Specialist Graduation: Pablo Levine Mardones
• PAZ context: BSS Title — five-month program page