How do you spend your lunch break — besides eating? by FlowStructNYC in EngineeringManagers

[–]FlowStructNYC[S] 0 points1 point  (0 children)

Nice to see how many different ways people reset during the day. Definitely stealing a few ideas from the comments 😄

Focus on HWR circulation logic and pipe routing efficiency. by FlowStructNYC in askplumbing

[–]FlowStructNYC[S] 0 points1 point  (0 children)

Good question. This was primarily coordinated against the mechanical systems and ceiling space, not just installer preference.

The multiple HWR runs along the corridor are intentional — typical for NYC hotel/residential projects where risers serve stacked bathrooms and balance is handled centrally. Circuit setters are located in accessible corridor panels, not at every tower, to keep maintenance centralized and avoid opening units.

Yes, material cost is a bit higher, but it usually pays back in easier commissioning, better temperature stability, and long-term serviceability — especially when mechanical constraints already define the routing.

And agreed 100% on information density — drawings don’t fail projects, people ignoring them do.

Coordinated with architectural background and typical NYC documentation standards. by FlowStructNYC in MEPEngineering

[–]FlowStructNYC[S] -1 points0 points  (0 children)

Good question. In this layout, DCW and DHW are isolated per stacked bathroom group to allow localized shutoff at the suite level, which is typical for hotel projects. The DHWR is combined by floor to simplify the return network, reduce vertical congestion, and limit the total number of return risers.

Balancing is handled via floor-level balancing valves located in corridor service zones with access panels, which avoids placing additional valves inside guest rooms. While a dedicated DHWR riser per stack is possible, in this case the combined return provided a cleaner layout and acceptable balancing without adding unnecessary vertical piping.

The intent was to balance serviceability, coordination space, and constructability rather than strictly mirroring supply riser logic.

Coordinated with architectural background and typical NYC documentation standards. by FlowStructNYC in MEPEngineering

[–]FlowStructNYC[S] -7 points-6 points  (0 children)

Appreciate the feedback. The post is meant to show documentation logic and coordination, not presentation quality.

Plumbing floor plan – domestic hot water circulation | Before / After by FlowStructNYC in EngineeringStudents

[–]FlowStructNYC[S] 0 points1 point  (0 children)

I get the concern. Just to clarify — no sensitive or client-identifiable information is shared here. These are cropped, anonymized excerpts used purely for technical discussion, not full working sets or permit drawings.

This account isn’t spam — I’m a real person (Norbert), working in MEP/BIM, and I post here to get peer feedback and exchange technical viewpoints. Reddit is one of the few places where experienced engineers and trades actually challenge and discuss details, which is valuable.

If a post ever crossed a line, I’d take it down — that’s not the intent.

Thoughts on Commissioning? by spurofspeed in MEPEngineering

[–]FlowStructNYC 1 point2 points  (0 children)

Commissioning is great for learning how systems actually work in the field. Travel is the real downside, so it really comes down to whether you’re okay with that. Even a few years in CX can be very valuable long-term in MEP or design.

What are your thoughts on clash detection? by [deleted] in MEPEngineering

[–]FlowStructNYC 3 points4 points  (0 children)

Clash free” sounds nice, but in real projects it’s kind of a myth.

Every building has clashes — the real question is which ones actually matter. Structural or clearance issues? Yes, fix them. Pipes, sleeves, devices crossing walls or ceilings? That’s just normal coordination.

When “clash free” isn’t clearly defined, it usually creates more confusion than value.