Urgent.News

What's breaking now, across thousands of outlets.

Tech

CityEngine vs GenAnywhere: Procedural Rules for a Campus That Never Stops Changing

A university central plant is a building that gets rebuilt every fifteen years without ever being demolished. Boilers come out, chillers go in, a pipe bridge gets added, a stack gets shortened. The facilities team asked for a model of the plant and the yard that could survive those changes, not a picture of how it looked in October. The campus planning office had already been burned once by a…

A university central plant undergoes rebuilding every fifteen years, with no demolitions required. The campus planning office sought a model that could adapt to these changes, rather than a static image. Using CityEngine and a rule file, the facilities team imported building footprints and plant asset data, including heights, floor counts, and construction dates. This data-driven approach ensured that every boiler, cooling tower, and warehouse was accurately placed with its associated attributes.

The CGA rule governing the plant buildings was straightforward, with heights derived from attributes. Adjusting the height attribute automatically altered the number of floors, while changes in roof pitch updated the building's silhouette. This simplicity proved invaluable when the facilities director mandated a two-meter raise for all buildings to align with a new flood datum. A single attribute modification and regeneration produced the updated model, with the LOD rebuilt from the same source.

Python scripting facilitated repetitive tasks, such as looping through schemes, setting height attributes from a CSV, exporting files in various formats, and generating a JSON manifest for tracking file versions and related data. While manual modeling was required for unique elements like the pipe bridge, it was integrated into the overall system to maintain the model's adaptability and accuracy.

The project's final deliverable involved providing GenAnywhere with the plant yard boundary, resulting in an industrial campus with a glass office block, landscaped forecourt, and matching stacks. However, discrepancies arose—stacks were too short, the pipe bridge was absent, and the coal yard transformed into a parking lot. Despite these inaccuracies, the concept image served well as a facilities newsletter illustration, but it lacked the asset data necessary for practical use.

Ultimately, the facilities team utilized the glTF model in a browser viewer, allowing them to toggle between building components, pipe bridges, and underground lines—all housed on the campus intranet without saving data between sessions.

To accommodate the future modifications planned for 2029, stack schedules, pipe sizes, and phase dates were added as attributes within the model. These attributes offered an auditable record of changes, reducing reliance on screenshots. As the plant undergoes further transformations, the rule file and asset table will continue to serve as the unifying source, ensuring a consistent digital twin of the evolving campus infrastructure.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Why I Keep a Wrong-Answer Notebook

I have a small notebook with two columns: what I guessed, and what the song actually was. It is not a pretty document. Some pages are just the word "no" written eleven times.

  • Maintains a Wrong-Answer Notebook to improve music listening skills
  • Records only confident wrong answers in two-column notebook
  • Notebook reveals patterns and transforms answer archive into useful index

More from Friday 20 November →