Revit Sanitary Network Validation -- 2
Budget: ₹1,500 – ₹12,500 INR
I have a C#-driven Revit add-in that builds complete sanitary (sewage) networks from CSV data—main runs from a center-line file and branch or stub lines from separate connection files. The script already places pipes, elbows and tees with the correct families and nominal sizes, yet the final model still contains a handful of connectivity faults that Revit’s warnings pick up.
Your task is to open the current Revit model, manually trace every pipe run, correct the geometry and fitting placement, and hand the model back in a state where:
• Every pipe and fitting forms an unbroken system—no “not connected” or “broken segment” warnings remain (continuity is my first priority).
• Layout decisions follow standard Czech plumbing practice so the result feels realistic to local engineers and installers.
• Disconnected pipes, mis-aligned fittings, and incorrect elbow or tee selections noted earlier are fully resolved.
When you are satisfied, compile a concise technical report that lists what you changed, why, and any guidelines I should carry forward into the automation code. I will use that document—rather than annotated screenshots—to refine my importer, so clarity of explanation is key.
Please work directly inside Revit’s native MEP tools; no exports or third-party converters, just the cleaned-up RVT file and the accompanying report. If anything in the importer output prevents strict continuity, flag it clearly so I can adjust the CSV logic on my side.
Your task is to open the current Revit model, manually trace every pipe run, correct the geometry and fitting placement, and hand the model back in a state where:
• Every pipe and fitting forms an unbroken system—no “not connected” or “broken segment” warnings remain (continuity is my first priority).
• Layout decisions follow standard Czech plumbing practice so the result feels realistic to local engineers and installers.
• Disconnected pipes, mis-aligned fittings, and incorrect elbow or tee selections noted earlier are fully resolved.
When you are satisfied, compile a concise technical report that lists what you changed, why, and any guidelines I should carry forward into the automation code. I will use that document—rather than annotated screenshots—to refine my importer, so clarity of explanation is key.
Please work directly inside Revit’s native MEP tools; no exports or third-party converters, just the cleaned-up RVT file and the accompanying report. If anything in the importer output prevents strict continuity, flag it clearly so I can adjust the CSV logic on my side.