Home › Guides › ETAP Basics: Load Flow

ETAP Basics: Build a One-Line Diagram and Run a Load Flow Study

ETAP is one of the most widely used power system analysis tools in the electrical industry. Design engineers use it to prove a new installation will work before a single cable is pulled, commissioning engineers use it to check that protection settings and fault levels match the real plant, and operations teams use it to plan outages and future load growth. If you work with substations, industrial plants or large commercial buildings, learning ETAP is one of the most valuable skills you can add to your toolkit, because it turns a single-line diagram from a drawing into a living, calculable model of your system.

This guide explains ETAP from the very beginning, in plain language and in your own workflow order: how to build a one-line diagram, how to enter equipment data correctly, how to run a load flow study, and how to read the results like an engineer rather than just accepting whatever numbers appear on screen. Everything here is generic educational material written from standard engineering practice. It does not reproduce any software manual, screenshot or proprietary content, and for hands-on practice you will need a licensed copy of the software, an authorised trial, or an academic licence from the vendor. Always verify your model against the project single-line diagram, equipment nameplates and your company's design standards before using any result for a real decision.

What ETAP actually does

At its heart, ETAP is a database with a drawing front end and a set of calculation engines. You draw the network — sources, transformers, cables, buses, loads, motors, generators and protective devices — and for each element you enter its electrical data: ratings, impedances, lengths, and operating modes. The calculation engines then solve the network mathematics for you. A load flow study solves for voltages and power flows. A short-circuit study solves for fault currents. A protection study checks whether devices coordinate. An arc flash study estimates incident energy. The drawing is not decoration; it is the model, and the accuracy of every result depends entirely on the accuracy of the data you entered.

That last point is the single most important lesson for a beginner. A beautiful one-line diagram with guessed cable lengths and default transformer impedances will produce confident-looking but wrong results. Experienced ETAP users spend most of their time checking data, not clicking buttons: confirming transformer ratings and impedance from the nameplate, cable sizes and lengths from the cable schedule, motor data from datasheets, and utility fault levels from the supply authority. When a result looks surprising, the first suspect is always the input data, not the software.

Step 1: Set up the project and the one-line diagram

Start a new project and set the basic project data first: the project name, the system frequency, and the units you will work in. Then build the one-line diagram from the source outwards, following the same order as the real power flow. Place the utility source or generator first, then the main bus, then transformers, distribution buses, feeders and finally the loads. Connect elements with buses and cables or busbars, and keep the drawing tidy and readable, because a one-line diagram that nobody can follow will not be checked properly, and unchecked models hide errors.

Give every element a clear, consistent name that matches the project documentation — for example, the same bus and feeder numbers used on the issued single-line diagram and cable schedule. This discipline pays off later when you produce reports, compare study cases, or hand the model to another engineer. A model built with random default names becomes almost impossible to audit, and auditing is exactly what a power system model needs before it is trusted.

Step 2: Enter equipment data carefully

Work through the model element by element and enter real data. For the utility source, enter the fault level and voltage provided by the supply authority, and be careful about whether it is given as a fault current, an MVA value, or an impedance — entering the same number in the wrong field is a classic beginner error. For transformers, enter the rated power, primary and secondary voltages, impedance percentage, vector group and tap position from the nameplate, and check that the connection type matches the real unit. For cables, enter the size, material, length and installation details from the cable schedule, because cable impedance drives voltage drop and fault levels.

For loads, enter the real and reactive power or the current and power factor, and decide whether each load is constant power, constant current or constant impedance, since that choice changes how the load behaves when voltage changes. For motors, enter rated power, voltage, full-load current and starting characteristics from the datasheet. Where a value is genuinely unknown, mark it clearly as an assumption, use a conservative placeholder, and record it in your study notes so that it is revisited before the model is issued. Never silently accept a software default for a value that matters.

Step 3: Run the load flow study

Before running anything, decide which operating case you are studying. Normal operation with all sources in service is the usual starting point, but a good study also checks credible alternatives: one transformer out of service, a generator offline, or a future load added. Select the load flow study, check the study settings — such as the solution method and the convergence tolerance — and run it. If the study fails to converge, do not force it: a non-converging case usually means a data error, an overloaded element, or an impossible operating condition, and finding that error is part of the engineering work.

When the study solves, ETAP displays the results on the one-line diagram itself: bus voltages, branch currents and power flows, and often a colour or flag on anything outside limits. Start your review at the buses. Are voltages within the acceptable band, typically within a few percent of nominal? Then follow the power from source to load and check each branch against its rating. A cable or transformer loaded above its rating in the model will be loaded above its rating in real life, so that result must be reported and resolved, not ignored because the study "ran successfully".

Step 4: Read the results like an engineer

Read voltage results as percentages of nominal voltage as well as absolute values, because a 5 percent drop on a low-voltage bus feels very different from the same percentage on a high-voltage bus. Check reactive power flows as well as real power: a system can carry its real load comfortably while still suffering poor voltage because reactive power is not being managed, and that shows up as low voltage at remote buses and high currents in feeders. Check total losses too, since high losses point to long or undersized feeders and to opportunities for improvement.

Compare the results against hand calculations for at least one simple path in the network. A rough voltage drop calculation for one feeder, or a simple power balance at one bus, takes minutes and catches gross data errors that a polished report would otherwise hide. Then produce a clear study report: the case studied, the assumptions made, the key results in a table, the elements outside limits, and the recommendations. A study that nobody can read and reproduce is not finished, however pretty its one-line diagram looks.

Common beginner mistakes

The most common mistakes are all data mistakes. Entering a transformer impedance as a per-unit value when the field expects a percentage, or vice versa, is a frequent one. Mixing up cable length units, forgetting that a motor load is not the same as a static load, and modelling a bus tie as closed when it is normally open all produce plausible but wrong results. Another common error is studying only the normal case and declaring the system healthy, while the single most important case — one transformer out of service during peak load — was never run. Build a habit of running the contingency cases your project actually cares about, and of documenting every assumption so the next engineer can challenge it.

Finally, remember that ETAP is a tool, not an authority. It does not know your site, your operating philosophy, or your utility's requirements. Its results support your engineering judgement; they do not replace it. If a result contradicts site measurements or experience, trust the measurements first and investigate the model until the two agree. That discipline is what separates an engineer who can operate software from an engineer who can be trusted with a power system.

What to learn next

Once you can build a model and run a load flow study confidently, the natural next steps are short-circuit analysis and protection coordination, covered in our ETAP short-circuit and protection guide, followed by arc flash and motor starting studies. For the design side of the same projects, see our guides to AutoCAD Electrical basics and advanced PLC ladder logic. If you work with the physical plant behind these models, our transformer testing and commissioning guide and PLC basics guide connect the software to the equipment on site, and our AI tools for engineers page shows how modern tools can speed up the reporting side of study work without replacing engineering judgement.

Frequently asked questions