Estimated effort: 11 hours

Overview: What and Why

You have five models. They do not agree with each other.

This week you publish all of them to Forma Data Management, run Model Coordination across the full set, and work through what it finds. You will classify every clash as an issue or not an issue, resolve the three that matter most, and republish.

This is the week that justifies the entire structure of the course. Your architecture, structure, mechanical, plumbing and electrical work lived in separate linked files so that different people could own them. The cost of that separation is that nobody sees the whole building until someone deliberately assembles it. On a real project that assembly either happens now, in coordination, or later, on site, at roughly a hundred times the cost.

You will also see the 220B final presentations this week as examples of where this leads.

Focus: What You Are Producing This Week

• All five models published as current versions to Forma Data Management
• A coordination space containing the merged set
• A complete clash matrix, every discipline pair tested
• A fully triaged issue log
• Three clashes resolved in the source models and republished

Design Program

• All five models published: architectural, structural, mechanical, plumbing, electrical. Plus the site model if you kept it separate.
• Every discipline pair run for clashes, not just the obvious ones. Structure against mechanical is expected. Plumbing against electrical is where surprises live.
• Every clash triaged into one of three states:

1.  Issue, must resolve. A real physical conflict that would stop construction.

2.  Issue, accept with note. Real but tolerable, for example a pipe passing through a non structural partition.

3.  Not an issue. A false positive from modeling technique rather than a real conflict.

• Three clashes resolved in the source models, chosen as the most consequential, not the easiest.
• Republished models after resolution, with a second clash run showing the change.
• A written triage rationale explaining the basis on which you classified.

Getting Started

1.  Publish current versions of all five models to your Forma Data Management project folder, in a folder named Final Coordination.

2.  Copy the latest versions into your Coordination Space to create one integrated model.

3.  Walk the merged model before running anything automated. Look with your eyes first. You will find things the software will not flag and miss things it will.

4.  Run Model Coordination across all discipline pairs.

5.  Triage every clash into the three states above and record the count in each.

6.  Pick your three. Choose by consequence, not convenience. A duct through a beam matters more than a sprinkler head touching a ceiling grid.

7.  Resolve them in the source models, not in the coordination view. Coordination shows problems; it does not fix them.

8.  Republish and re-run. Document the before and after counts.

How Detailed Should This Be?

You will not reach zero clashes, and you should not try. Real projects go to construction with open issues, tracked and owned. What matters is that every clash has been looked at by a person, classified deliberately, and either resolved or consciously accepted.

A model with 400 unexamined clashes and a model with 400 examined and classified clashes are completely different deliverables.

How This System Affects the Others

This week is where every earlier decision comes due.

• Your Week 6 beam depths meet your Week 7 ducts.
• Your Week 8 sanitary fall meets your Week 5 ceilings.
• Your Week 4 core meets everything, because every riser and shaft runs through it.

If you did Weeks 4 through 8 carelessly, this week is long. If you coordinated as you went, it is short. Both outcomes are informative.

What's Expected

1.  All five models published to Forma Data Management under Final Coordination.

2.  A coordination space with the merged set.

3.  A complete clash matrix showing every discipline pair and the count for each.

4.  A classified issue log: counts by category, with the classification rationale written out.

5.  Three clashes resolved in the source models, documented before and after.

6.  Republished models and a second clash run showing the delta.

7.  Two coordination views: one showing your worst conflict, one showing it resolved.

8.  A written note on which discipline generated the most issues, and your theory about why.

What to Submit

1.  Working links to the coordination space and all five published models.

2.  Clash matrix, one page.

3.  Classified issue log with counts and rationale.

4.  Three pairs of before and after images.

5.  Design memo of 300 to 500 words: how many clashes you found, how you triaged them, the three you fixed and why those, what you consciously accepted, and what you would have done differently in Week 4 knowing this.

Share Your Results

Post everything on the Module 9 Notion gallery page. Attend the 120A/220A final presentations this week and note one coordination decision from another team's project that you would adopt.

At Friday check in, present your worst clash, your resolution, and one clash you deliberately chose not to fix.

Points to Ponder

Please share your comments on 3 of the following 5 questions on this linked Notion page.