Inspect a network
Open native topology and check objects, units and data boundaries before changing anything.
See the desktop workflowPower-system engineering, in view
See the network.
Verify the decision.
Inspect the circuit, run one exact case, and trace the result back to its inputs. AI can prepare a candidate; only people can review and approve engineering work.
Customer installers are not available yet. Release details.
Start with your task
What do you need to do?
Run one bounded study
Freeze a named case, run an admitted profile, then read its retained result and warnings.
Use the five-bus sampleCompare alternatives
Keep Main separate, inspect version differences and decide explicitly what to review.
Explore native historyEngineering history
Try a direction without losing the design you started from.
Save a named milestone, open an alternative, and compare what changed before you bring anything back. The native history keeps Main and each working design separate; opening a version does not approve or apply it.
See how history works- Mark a pointGive a version a name you can find again.
- Explore a branchWork on an alternative without replacing Main.
- Review the differenceCompare exact versions and resolve conflicts explicitly.
A measured case
Results you can interrogate.
A retained balanced AC base-case run records the exact case, quantities, units and disposition. The native result view keeps unavailable and failed conditions visible instead of inventing a value.
Read the study boundary
The safety boundary
Evidence before confidence.
A plausible sentence can hide a missing parameter, failed solver or different scenario. PowerSystem keeps those distinctions in the work, not in a footnote after approval.
- Native project and diagram remain the reference.
- Plan is read-only; Build prepares detached candidate work.
- Studies bind exact versions and retain warnings.
- Acceptance and engineering sign-off remain human actions.