What does the end of SSA mean for Civil 3D?
Original English video · 13 September 2026. Validate calculation methods, licensing and migration requirements before changing project workflows.
Edition: 13 September 2026 · Category: BIM News
This is an archived English edition. The briefing below preserves the original episode’s reporting and analysis, with paragraph headings added for reading. Words such as “today”, “planned” and “upcoming” refer to the edition date, not the website publication date. Product status, prices and deadlines should be checked again before a new decision.
The most important new official signal after the weekend is Autodesk's confirmation that it is moving away from Storm and Sanitary Analysis, or SSA. Core drainage checking workflows are moving into Civil 3D, while more advanced design, automation and reporting remain in the separately licensed InfoDrainage environment.
SSA retirement direction
Autodesk plans to retire SSA.
Fact. On September 10, Autodesk described SSA as a legacy application from which it is transitioning to newer workflows. SSA is no longer downloaded automatically with current Civil 3D releases. A final retirement date has not been announced, and existing customers may still use or download it for supported workflows and versions.
Action. Do not treat the absence of a date as a migration deadline. Start an inventory of SSA projects, application versions, models, hydrology methods, scripts and report templates now. The source is Autodesk AEC Tech Drop.
Core analysis in Civil 3D
Core drainage analysis is moving into Civil 3D.
Fact. Civil 3D tools already cover pipe networks, catchments, ponds, underground storage and open channels. Hydraulic analysis runs through InfoDrainage cloud analysis services. Autodesk says this direction is intended to replace the main SSA workflows.
Why it matters. Users can remain inside the civil model and drawing environment, but the calculation chain becomes dependent on a cloud service. This affects not only convenience, but also business continuity and the reproducibility of results.
Action. Test authentication, loss of connectivity, data region, result archiving and repeatability after a software update. Preserve the inputs and analysis version in the project submission, not only a chart or coloured view.
Licensing boundaries
Civil 3D drainage capabilities do not require a separate InfoDrainage subscription.
Fact. The drainage tools built into Civil 3D are included with a Civil 3D subscription, even though the analysis is powered by the InfoDrainage cloud engine.
Risk. This does not mean that all InfoDrainage capabilities are included in Civil 3D or the AEC Collection. InfoDrainage remains a separately licensed product for advanced workflows.
Action. Base licensing on the required capability, not only the product name or the analysis engine being used. Count separately how many people check existing networks and how many genuinely design, optimise and prepare complex reports.
Feature parity gaps
Civil 3D does not yet match SSA in every workflow.
Fact. Autodesk explicitly states that one-to-one feature parity has not been achieved. The current toolset covers rainfall and runoff methods, hydraulic analysis, hydraulic and energy grade lines, capacity checks and some reporting. The official comparison matrix shows differences in storage, culvert, pollutant and detailed reporting capabilities.
Action. Classify every SSA capability used by the organisation as supported in Civil 3D, supported only in InfoDrainage, requiring an alternative, or not yet tested. Validate the matrix with real projects, not only feature names.
Checking versus design
Autodesk separates checking from designing.
Fact. Civil 3D is recommended for analysing an existing network and checking capacity and hydraulic results in the drawing environment. InfoDrainage is intended for iterative design, automated sizing and comparison of alternatives.
Interpretation. An organisation's software standard should be based on the task, not only the discipline. The same drainage engineer may reasonably use both environments at different stages.
Action. In the BIM execution plan or internal guide, separate five actions: model, check, optimise, approve and report. For each action, identify the authoritative tool, deliverable and accountable person.
Advanced drainage workflows
Advanced and sustainable drainage remains in InfoDrainage.
Fact. The separate product provides rapid scenario iteration, automated sizing, modelling of swales, permeable pavement and bioretention, one-dimensional and two-dimensional analysis, advanced culvert workflows and configurable audit-ready reports.
Action. For projects with green infrastructure, flood or regulatory reporting requirements, pilot InfoDrainage against an approved calculation baseline.
Connected workflow and governance
Civil 3D and InfoDrainage are intended to form a connected workflow.
Fact. Autodesk presents them as complementary solutions between which drainage design data can be exchanged. Deeper future integration is a product direction, not a guaranteed delivery date.
This is as much a governance exercise as a software test.
Action for the seventh story. Test more than whether a file opens. Check object identity, units, coordinate system, scenarios, result version and the quality of changes moving in both directions.
Analysis and practical implications
Daily analysis. Retiring a legacy application is a data and validation migration.
The target chain begins with Civil 3D geometry. Drainage data is sent to an analysis service, results are returned, an engineer verifies them, a report is prepared, and only then is an approved project version published. At every link, it must remain clear what was entered, which application and service performed the calculation, which version was used, and who approved the result.
The largest opportunity is to reduce separate exports and check a network faster in the main Civil 3D environment. The model, drawing and key hydraulic results can remain closer together. For complex projects, InfoDrainage adds stronger scenario analysis, green infrastructure, automated sizing and reporting capabilities.
The first risk is that a legacy SSA model may not have a direct equivalent in the new system. The second is that geometry matches while hydrological assumptions, rainfall data or the runoff method do not. The third is that the result depends on a cloud service, the user's account and the analysis version operating at that time.
The fourth risk is regional variation in rainfall, runoff, climate and reporting methods. Autodesk's official comparison matrix shows that regional methods are not supported equally in all three systems. For teams working across different jurisdictions, one universal migration recipe would be inadequate.
The fifth risk is that the transferred model looks correct while units, boundary conditions, initial water level or result selection criteria have changed. The sixth is confusing an Autodesk roadmap or future-integration statement with a capability that is available and verified today.
For a practical pilot, first select three SSA projects. The first should be a simple pipe network. The second should include a pond, catchment or underground storage scenario. The third should contain a complex regulatory report and regional calculation methods.
Migration step 2
record for each model the SSA version, geometry, rainfall method, runoff coefficients, time parameters, initial and boundary conditions, and previously approved results. Without this baseline, there is no reliable reference for comparing the new system.
Migration step 3
recreate the same scenario in the Civil 3D drainage tools, and also in InfoDrainage for the complex case. Never assume automatically that fields with the same name carry the same meaning, units or default value.
Migration step 4
compare flows, water levels, hydraulic and energy grade lines, pipe filling, critical nodes, storage performance and reports. The responsible engineer must define acceptable tolerances in advance. A difference must be explained, not merely highlighted in red.
Migration step 5
test the workflow during an internet outage, verify user permissions and the analysis region, and inspect the archive format for results. The team needs to know whether it will be possible years later to reconstruct both the model and its calculation context.
Migration step 6
identify the authoritative application and version at every stage. Civil 3D may be the main source for geometry and documentation, while the authoritative state of an advanced hydraulic scenario may remain in InfoDrainage. This boundary must be documented in the BIM execution plan and project quality plan.
Migration step 7
update software deployment policy, templates, training and the project start checklist only after validation. SSA should not be removed from workstations until active projects and the archive recovery procedure have been verified.
For university teaching, this is well suited to a migration laboratory. Students receive one network and the same input data, analyse it in two environments, explain differences in the results, and submit a reproducible validation protocol. Assessment should focus on assumptions, units, version and engineering judgement rather than a colourful result view.
The signal of the day. The end of SSA does not mean that a team can simply change a software reference. A reliable migration must preserve calculation assumptions, results, report traceability and a clear choice between checking in Civil 3D and designing in InfoDrainage.
Original edition sources
These direct links were cited in the original scheduled brief. The scheduled message was retrieved in full on 25 October 2026; this recovery is not a claim of a fresh product test or new source validation.
- https://www.autodesk.com/blogs/aec/2026/09/10/whats-happening-with-ssa-the-future-of-drainage-design-in-civil-3d-and-infodrainage/ - https://www.autodesk.com/blogs/water/2025/04/09/autodesk-infodrainage-vs-ssa-vs-drainage-analysis-for-civil-3d/
Watch the original edition
https://www.youtube.com/watch?v=Y8K4n6lmUJQ
The original dated thumbnail is retained where available. Original per-topic artwork was not recovered for this legacy edition; no replacement artwork is represented as an original.
Archive media note: The original date-matched thumbnail and thematic artwork have not been recovered. No substitute is presented as original media.
