When LEGO fans hear the word "modular," most immediately think of the Creator Expert Modular Buildings line — the Corner Cafe, the Assembly Square, the Bookshop. Those sets are designed as modular city elements: individual buildings that connect side by side along baseplates to form a street scene. They're modular in the horizontal sense. You line them up, and they form a neighborhood.
That's not what this is.
The IMS Pagoda is modular in the vertical sense. It's a single building — one structure, one footprint, one architectural subject — where each floor separates from the floors above and below it. You lift the second story off the first. You lift the third off the second. All the way up through eleven stories plus the rooftop observation deck. Every level is a self-contained module that stacks precisely onto the one below it and comes apart cleanly when you need it to.
This is a design approach you see in the most serious MOCs (My Own Creations) in the LEGO community. Builders working at large scales — particularly architectural reproductions — frequently design their structures to separate by floor or by section. The reason is practical, but the engineering behind it is anything but simple.
At 1:38 scale, where 1 stud equals approximately 1 real-world foot, the IMS Pagoda is a substantial structure. Eleven stories of LEGO bricks, even before you add the flagpoles that crown the real building's peak. If you build this as a single, permanently assembled model, you create an object that presents immediate practical problems.
First: you can't reach the interior. The ground floor of the Pagoda has rooms, elevator shafts, bleacher sections, glass facades, and interior detail that took weeks to design. If the building doesn't come apart, all of that work is permanently hidden inside a tower you can only view from the outside. What's the point of designing individual rooms on the ground floor if no one — including you — can ever see them again after stacking on the second story?
Second: you can't photograph individual floors. One of the goals of this build is museum-quality documentation. I want to photograph each level from above, from the side, and at detail angles that show how specific design problems were solved. An assembled 11-story tower makes that impossible. You'd be limited to exterior shots at whatever angles the full height allows. Separable floors mean I can isolate any level, place it on a clean surface, and photograph it as its own subject.
Third: you can't fix mistakes. During the design phase in Stud.io, I can rotate and zoom to any angle. But once the physical build starts, if a structural issue appears on the third floor, I need to be able to access the third floor without dismantling everything above it — and certainly without risking damage to the floors below. Modular separation makes every floor independently accessible for adjustments.
Fourth: transport. This model will need to move. Whether it's across a room or across the state for display, an 11-story monolith of LEGO bricks is a fragile, top-heavy disaster waiting to happen. Separated into individual floor modules, each piece can be wrapped, padded, and transported flat. Reassembly at the destination is just a matter of stacking.
An 11-story LEGO building that doesn't come apart isn't a display model. It's a permanent fixture. I wanted both — museum presence when assembled and full access when needed.
The fundamental engineering challenge of a modular LEGO building is the connection between floors. You need two things that seem to contradict each other: the connection must be strong enough that the assembled building feels solid during display, and it must be easy enough to separate that you can lift a floor off without damaging the structure or requiring excessive force.
LEGO's own Creator Expert modular buildings solved this years ago with a brilliantly simple approach. Each modular building in the official line has floors that sit on top of each other using alignment studs — a minimal number of stud connections at specific points around the perimeter. Not the entire floor surface. Just enough to register the position and hold the floors in place under gravity. You lift straight up, the connection breaks cleanly, and the floor comes away.
That's the principle I'm applying to the Pagoda, but the execution is more complex because this isn't a rectangular box. The Pagoda has setback floors — each upper level is smaller than the one below it, stepped back to create the building's distinctive tapered silhouette. That means the connection geometry changes at every level. The footprint of floor three is different from floor four, which is different from floor five. Each transition needs its own alignment strategy.
For the Pagoda, I'm using a combination of techniques:
The key insight is that at this scale, gravity is your friend. Each floor module has real weight — hundreds of bricks and plates per level. Once seated on the alignment points, the sheer mass of the floor holds it in place. You don't need aggressive stud connections. You need precise registration so that each floor drops into exactly the right position and stays there under its own weight.
This is a different philosophy from, say, a LEGO Technic build where everything is pinned and locked together for structural integrity. The Pagoda isn't a vehicle that needs to withstand play forces. It's a display model. Its primary structural load is vertical — the weight of the floors above pushing down. As long as the floors are aligned and the base is stable, the structure is sound.
LEGO's Creator Expert modular building series — sets like the Assembly Square #10255, the Corner Garage, the Haunted House — established the gold standard for separable floor design. Each building in the series uses a consistent baseplate size (32×32 studs) and a predictable floor separation method. You can lift the roof off, then the upper floor, then access the ground floor interior. The connections are minimal by design.
What makes the official modulars instructive for the Pagoda project isn't the specific connection method — the Pagoda's geometry is too different to copy directly. It's the philosophy. LEGO's designers understood that a building model has two modes of existence: assembled for display, and separated for interaction. They designed for both modes simultaneously. The assembled building looks complete, with no visible seams or separation lines. But the separation points are always there, engineered into the structure from the first brick.
I'm applying that same dual-mode philosophy to the Pagoda. When fully assembled, the building should look like a single, continuous tower. The separation lines between floors should disappear into the architecture — hidden behind facade elements, canopy overhangs, or setback transitions. But when you need to access a floor, the separation should be obvious and intuitive. Lift straight up, and it comes away.
Where the Pagoda diverges from the official modulars is complexity. A standard Creator Expert modular building has two or three floors. The Pagoda has eleven. A standard modular has a uniform rectangular footprint. The Pagoda tapers. A standard modular's interior is typically a few rooms per floor. The Pagoda's ground floor alone has elevator shafts, bleacher sections, glass-walled rooms, and structural columns that support everything above.
Each of those differences compounds the engineering challenge. Eleven separation points means eleven opportunities for alignment error. Tapering floors mean the connection geometry is unique at every level. A complex ground floor interior means the base module is the heaviest and most structurally demanding piece — and it's the one everything else sits on top of.
The modular design approach doesn't just serve the physical build. It fundamentally shapes the digital design process in Stud.io.
Because each floor is a self-contained module, I can design each one as an independent project. I don't need the entire 11-story building loaded in Stud.io at once — which, at the part counts this build demands, would tax the software's performance significantly. Instead, I design floor by floor. Each level gets its own design file. I verify it independently — structural integrity, part availability, connection points, interior detail — before moving to the next.
This floor-by-floor approach also enables staged ordering. Rather than calculating the complete parts list for the entire building and placing one massive BrickLink order, I can order parts for each floor as its design is finalized. This spreads the cost over time, reduces the risk of ordering parts for a floor whose design might change, and means I can start physically building lower floors while upper floors are still being designed digitally.
It's a project management strategy as much as it is a structural one. The Pagoda is a large enough project that trying to tackle it as a single monolithic effort would be overwhelming. Breaking it into floor modules makes each piece manageable. Design a floor. Verify it. Order the parts. Build it. Move to the next. Each completed floor is a milestone — a tangible piece of progress that sits on the shelf and proves the concept works.
There's a psychological benefit too. Staring at an 11-story building and thinking "I have to design all of this" is paralyzing. Looking at a single floor and thinking "I need to get this one right" is energizing. The modular approach converts one impossible project into eleven achievable ones.
Each floor module in the Pagoda isn't just a flat plate with walls. It's a complete architectural slice of the building. Here's what every floor module must include:
The floor plate. This is the structural base of each module. Per the locked floor plate rule, large plates go on the perimeter and smaller plates toward the center. No 6×24 plates — they're cost-prohibitive at the quantities this build requires. Every 6×24 plate is substituted with a 6×16 plus a 6×8 combination. This rule is locked and applies to every floor, no exceptions.
The walls and facades. Each floor's exterior treatment is unique. The Pagoda's facades change as the building tapers — glass treatments, panel widths, and structural framing all shift from floor to floor. Each module captures the facade design specific to that level.
The interior. Where applicable, each floor module includes interior detail. The ground floor has rooms, elevator shafts, and bleacher sections. Upper floors have their own interior layouts. The level of interior detail varies by floor — the lower levels get more attention because they're more visible and more photographically interesting.
The connection interface. The bottom of each module has connection points that mate with the top of the module below it. The top of each module has the corresponding receiving points for the module above. These interfaces are the critical engineering feature — they must be precise enough for clean alignment and robust enough for stable stacking.
The canopy or setback transition. Where the building's profile changes between floors, the transition is built into one of the two adjacent modules. In most cases, the canopy overhang belongs to the lower floor's module, and the upper floor's module sits within the setback area. This keeps the visual separation line hidden beneath the architectural overhang.
The elevator tower, visible in the Stud.io render above, is a particularly interesting modular challenge. It runs the full height of the building as a continuous vertical element. In the physical model, the elevator shaft is split at each floor boundary — each floor module contains its segment of the elevator shaft. When stacked, the segments align to create the continuous vertical column. But each segment must also function as a standalone element within its floor module, providing structural support and alignment reference for that level.
The term "museum quality" gets used loosely in the LEGO community. For this build, it means something specific: the model should be displayable at close inspection distance, with every visible surface intentionally designed. No exposed studs where there shouldn't be exposed studs. No visible structural compromises. No "good enough from three feet away" shortcuts.
The modular design is essential to achieving museum quality because it enables detailed photography of every level. When I document this build, I want to show each floor as its own subject — overhead shots showing floor plate layout, side profiles showing facade treatment, interior angles showing room detail. None of that is possible with an assembled 11-story tower.
It also enables iterative refinement. Museum quality isn't achieved on the first attempt. It's achieved through cycles of building, evaluating, and improving. With modular separation, I can pull out a floor that isn't meeting the standard, rework it on the bench, and slot it back in — without disturbing anything above or below it. The modular approach makes perfectionism practical rather than destructive.
Museum quality isn't a destination. It's a process. The modular design makes that process possible — you can pursue perfection on each floor without risking the floors you've already perfected.
Every serious MOC builder I've studied uses some form of modular separation in their large-scale architectural work. It's not a shortcut or a compromise. It's a prerequisite. At this scale, with this level of ambition, a building that doesn't come apart is a building that can't be built properly. The modularity isn't a feature I added to the Pagoda. It's the foundation the entire project is built on.
In Part 3: The Scale Math, I'll walk through the precise calculations that determined the Pagoda's dimensions — why Speed Champions cars are too big, why a 6-stud LEGO City car is nearly perfect, and how every measurement in this build traces back to a single ratio: 1 stud equals 1 foot.