
Geometry is not the final output, it’s the starting point of a pipeline that ends at the machine.
design → semantic model → fabrication data → machine
We’re moving from shape to system, from generating geometry to making it fabricable. The goal is a continuous pipeline where design intent survives all the way to the machine without loss of meaning.
Key takeaway: geometry is now an intermediate representation, it’s the output of a parametric semantic model.
The final project brings together everything from the course. You’ll design a fabricable timber structure with real beams, real joints, and real fabrication logic, not just geometry that looks structural.
Integrates:
compas_timber)Link to full description: Assignment 03: Design Project
Geometry describes where things are. Semantics describe what they are and how they behave. A line can represent almost anything. A beam with cross-section, grain direction, and a joint history is unambiguous.
In a semantic model, elements carry meaning beyond shape. A beam is not a curve with a profile swept along it, it’s an object with dimensions, an orientation frame, material properties, and connections to other objects. Joints are logical relationships, not coincidental intersections of geometry.
This shift is what allows fabrication data to be derived automatically rather than drawn by hand.
A well-structured timber model separates concerns cleanly. Think of it as three stacked layers, each answering a different question:
| Layer | What it contains | Question it answers |
|---|---|---|
| Parts | Individual timber beams - geometry, cross-section, material | What are the physical elements? |
| Connections | Topological relationships between parts | How do they meet, and with what structural intent? |
| Processings | Fabrication operations: cuts, holes, slots | What needs to happen to fabricate each joint? |
Design intent lives in Parts and Connections. Fabrication specifics live in Processings. Changing a joint type doesn’t require redrawing geometry, it should just update the rule set.
BTLx is the bridge between our digital model and the CNC machine. It’s an XML-based industry standard for timber machining, not a 3D file format, but a process description.
A BTLx file describes each element’s geometry alongside the processings to be applied: lap joints, drillings, tenons, notches. Some CNC machines reads this directly, others require conversion to an intermediate format.
The full pipeline from design to cut follows a structured sequence. Each step transforms the data while preserving the original design intent.
compas_timberCNC machines operate in fixed configurations, the workpiece comes to the tool. Industrial robots invert this: the tool comes to the workpiece, in any configuration space allows.
In a robotic workflow, our geometry defines target frames and orientations in space. Inverse kinematics then compute the joint rotations required to reach each frame, translating design toolpaths into precise robot trajectories.
This opens up tasks that linear machining can’t handle: complex assembly sequences, curved toolpaths, multi-face processing, and working in-situ. The trade-off is added complexity in programming and collision checking.
Before finalizing our session, we go to the Quartiergarten site.
Location: Quartiergarten
Bring your ideas and sketchpads. What looks right on screen often needs adjustment when you’re standing in the space.
↑ click to open ↑