Commands › Drainage › Design Drainage System

Design Drainage System

Drainage writes to model Public API · not yet exposed

Coming soon

Before you run this

Active document must be open. User must have Adelphos JSON file. At least one level must exist in the model. Appropriate pipe types (Soil, PVC, Cast Iron) must be loaded in the model.

After it runs

MEP elements (pipes), fittings (elbows, tees, transitions), and notes are created. Log file is written next to the JSON file with .drainage.log.txt extension. Neural Loading dialog shows completion summary.

When to use this

User wants to design the drainage system from AutoCAD JSON export.
User wants to import drainage pipework from coordinated model.
User wants automated drainage routing from a coordinated JSON model.
User says "design the drainage" or "create drainage system".
User says "design sanitary" or "design soil" or "design waste".

Don't use this when

Creating drainage from scratch without JSON input. Manual pipe routing (use standard Revit tools). Editing existing drainage systems.

Inputs

Name	Kind	Type	Required	Default	Description
`BasePoint`	selection	`XYZ`	yes	—	Base point for drainage placement "Pick Revit basepoint (target origin for import)"
`JsonPath`	config	`string`	no	null	Path to Adelphos JSON file

Returns

Name	Type	Description
`PipesCreated`	`int`	Number of MEP pipe segments created
`ElbowsPlaced`	`int`	Number of elbow fittings placed
`TeesPlaced`	`int`	Number of tee fittings placed
`TransitionsPlaced`	`int`	Number of transitions placed
`BlocksPlaced`	`int`	Number of family instances placed
`PipeNotesPlaced`	`int`	Number of pipe notes placed
`FixtureNotesPlaced`	`int`	Number of fixture notes placed

Decision flow

check: jsonPath.isValid → proceed
check: basePoint.isSelected → proceed
check: dto.Edges.count > 0 → proceed
resolve: excelMapper.exists → autoMap silently

What you'll see in the chat

on start

Designing your drainage system...
Setting up drainage import...
Preparing to create your drainage pipework...

thinking

Reading JSON file...
Loading block mapper...
Downloading cloud families...
Exporting room context to JSON...
Reading context JSON...
Identifying fixtures (WHB, WC, Sink)...
Calculating room centroids...
Finding model group bounding boxes...
Resolving types and levels...
Building node coordinates...
Creating pipe segments...
Building fitting index...
Placing elbow fittings...
Placing tee fittings...
Placing transitions...
Calculating drainage system bounds...
Placing pipe notes (SVP, slopes)...
Placing fixture notes (WC, WHB, Sink)...

on success

Drainage system created successfully! {PipesCreated} pipes, {ElbowsPlaced} elbows, {PipeNotesPlaced} notes placed.

on failure

Couldn't create drainage system: {error}

REST API

Not yet exposed

This command does not carry a [RestApi] attribute today. Once tagged, this section will auto-populate with:

POST /api/v1/commands/design_drainage_system
Request body schema (from [RestApiParam])
Response schema (from [RestApiResponse])
curl / JS / Python code examples

Keywords & intent patterns

design drain · design drainage · design the drain system · design the drainage · design the drainage system · can you please design the drainage · please design the drain · design the drainage please
Patterns: design * drainage · create * drainage · design * drain · drainage * design · drain * system

Related commands	`ImportCommand` · `DesignVentilationCommand` · `DesignContainmentCommand`
Pillar	Drainage

Design Drainage System

When to use this

Inputs

Returns

Decision flow

What you'll see in the chat

REST API

Keywords & intent patterns

Related