Published: June 2026 Technical Level: Advanced Category: Artificial Intelligence
The deployment of artificial intelligence in power system analysis and design tasks raises a legitimate professional question for practicing engineers: which aspects of their work are genuinely at risk of automation, which are not, and what adaptations are warranted given an honest assessment of current AI capability. This paper addresses that question through a task-level analysis of power engineering work rather than the job-level analysis that produces either excessive alarm or false reassurance. The conclusion is that the tasks most amenable to AI substitution — routine calculation, data verification, documentation generation, and standard design pattern selection — represent a minority of the value that an experienced power engineer provides, particularly at the senior level. The tasks that constitute the majority of senior engineering value — regulatory interpretation for non-standard systems, engineering judgment on system-level interactions, professional liability for design decisions, and client-facing risk communication — are not automatable with current or near-term AI technology. The appropriate professional response is selective adoption of AI tools for tasks where their reliability is demonstrated, rigorous validation before applying AI outputs to licensed engineering work, and continued investment in the judgment-intensive competencies that AI cannot substitute.
The appropriate professional response to AI capability growth in power engineering requires accurate information about what current AI tools actually do and where they fail. The public discourse on this topic is characterized by two unproductive extremes: vendor-driven optimism that presents AI tools as capable of autonomous engineering judgment, and reflexive professional skepticism that dismisses AI tools as inappropriate for serious engineering work. Both are wrong in ways that are consequential for the practicing engineer who must make concrete decisions about which tools to adopt, how to verify their outputs, and which competencies to develop or maintain.
The analytically correct framework is task-level rather than job-level. A licensed professional engineer's work consists of a portfolio of tasks at different levels of technical complexity, professional accountability, and cognitive demand. Some of these tasks — executing a Newton-Raphson load flow iteration, generating a protection relay time-current curve, producing a standard arc flash label — are well-suited to automation because they are well-defined, reproducible, and verifiable. Others — assessing whether a non-standard interconnection configuration complies with the intent of IEEE 1547-2018, determining the appropriate level of protection redundancy for a critical facility with an unusual load profile, advising a client on acceptable risk for a system that does not meet code but cannot be easily brought into compliance — require professional judgment, contextual reasoning, and acceptance of professional liability that current AI systems cannot provide.
The risk to the power engineer from AI is not that the engineering function will be replaced; it is that the engineer who does not adapt will find themselves performing only the automatable fraction of the work — executing tasks that AI tools can do faster and cheaper — while the judgment-intensive work migrates to engineers who have developed the competencies to work effectively with AI tools and apply professional judgment where the tools cannot reach.
The power engineering tasks most amenable to current AI automation share three characteristics: they are well-defined with explicit success criteria, they involve processing structured data inputs according to established mathematical or rule-based procedures, and their outputs can be verified against an independent standard. Load flow calculation for a system within the solver's convergence domain is well-defined and verifiable; the engineer can run two independent methods and compare results. Protection coordination for a conventional radial distribution system with standard device types is well-defined; the coordinator's constraints are explicit and the TCC curves are published. Arc flash calculation using IEEE 1584-2018 is well-defined; the regression equations are public and the inputs are measurable.
For these task classes, AI tools and traditional specialized software tools have already reduced the per-task engineering labor by one to two orders of magnitude relative to manual calculation. An arc flash study for a 200-node system that required two engineer-weeks of manual calculation in 1985 requires four to eight hours with current software. The marginal additional compression available from AI-enhanced workflow tools in these domains is real but modest — perhaps a factor of two to three over current software — because the current software tools already capture most of the available computation automation.
A larger category of power engineering tasks can be partially automated — the routine or standard-configuration portions can be handled by AI tools while the non-routine or judgment-intensive portions require engineering attention. System design for standard facility types — commercial buildings, light industrial facilities, data centers with conventional architecture — follows well-established design patterns that are substantially codifiable. An AI tool can generate a preliminary design from a load schedule, applying NEC sizing rules, standard voltage drop limits, and standard protection coordination margins without engineer intervention. The engineer's role shifts from executing the design procedure to reviewing the AI-generated design, verifying that the facility's actual requirements match the standard pattern assumptions, and modifying the design where they do not.
This shift is not trivial. The engineer reviewing an AI-generated design must understand the design procedure well enough to identify where the AI has applied a standard pattern to a non-standard condition — a data center UPS configuration that violates the standard bonding assumptions, a motor control center layout where the AI's standard bus sizing does not account for a high-harmonic-current drive load. This verification capability requires the same foundational engineering knowledge that the pre-AI engineer applied in generating the design; the AI tool reduces the labor of execution without reducing the knowledge requirement for quality assurance.
The core of professional engineering value — the work for which a PE license is issued and for which the engineer bears legal liability — is not automatable with current AI technology and is unlikely to become so within the five-year outlook of this paper. This category includes: interpreting code requirements for systems or conditions not explicitly addressed by the code text, applying engineering judgment to design trade-offs where the correct choice depends on context that is not fully captured in any structured data representation, accepting risk on behalf of a client in documented engineering decisions, and communicating technical findings and recommendations to non-technical stakeholders in a manner that enables informed decision-making.
The specific reason these tasks are not automatable is not that AI lacks the pattern-matching capability to generate plausible-sounding outputs for them — it demonstrably can — but that the outputs cannot be verified to be correct with the reliability required for professional work. A code interpretation that is plausible 90 percent of the time and incorrect 10 percent of the time is not acceptable professional practice; a bridge that is structurally adequate 90 percent of the time is not an acceptable bridge. The professional standard of care requires that engineering outputs be reliable to a much higher standard than current AI generative models can guarantee for open-ended reasoning tasks.
The engineer whose competency portfolio is concentrated in high-automation tasks — executing standard calculations, producing standard designs, generating documentation — faces the largest risk from AI adoption by their employers and competitors, not because their job will be eliminated but because the productivity premium for human execution of those tasks will erode as AI tools become standard. The adaptation strategy is to develop competencies in the adjacent judgment-intensive domains that the AI tools cannot cover: system-level design integration, code interpretation for non-standard conditions, protection philosophy for emerging system types (DER-heavy feeders, microgrid islands, DC distribution), and client-facing communication of complex technical findings.
The engineer whose competency portfolio is concentrated in judgment-intensive tasks — senior consultants, technical authorities, design reviewers — faces a different challenge: integrating AI tools into their workflow at the right points without either under-using them (leaving productivity gains unrealized) or over-relying on them (accepting AI outputs without adequate verification). The correct integration point is at the boundary between automatable and non-automatable work: use AI tools to compress the preliminary design and analysis tasks, then apply engineering judgment to the AI-generated baseline with the same critical attention that the engineer would apply to a junior engineer's work product.
Both adaptation paths require the same foundational investment: deep technical knowledge of the engineering domain sufficient to evaluate AI outputs critically, rather than surface familiarity sufficient only to operate the tool. The engineer who understands why a Newton-Raphson load flow fails to converge, and what the physical interpretation of non-convergence is, can identify when an AI power flow approximation is producing physically implausible results. The engineer who understands the protection coordination philosophy for a DER-heavy feeder at a conceptual level can identify when an AI-generated setting recommendation is inconsistent with the system's operating modes.
The analysis in this paper connects to several companion studies in this library. Readers concerned with the upstream and downstream engineering will find Ethics of AI in Power Systems Engineering develops a closely related aspect of the same problem, while AI and Power Systems Engineering Employment extends the treatment into an adjacent domain. For the broader methodological context, The AI Transformation of Power Systems Engineering provides complementary depth.
An honest, task-level assessment of AI capability in power engineering supports neither the alarm nor the dismissal that dominate the discussion, but rather a specific and actionable conclusion: the tasks most amenable to AI substitution — routine calculation, data verification, documentation generation, and standard design-pattern selection — represent a minority of the professional engineer's value-adding work, while the tasks that define professional engineering, including design synthesis under conflicting constraints, judgment in the absence of complete data, and the assumption of liability for a stamped design, remain firmly outside current AI capability. The adaptation strategy that follows is not defensive but opportunistic: the engineer who delegates the automatable tasks to AI tools, while concentrating personal effort on the judgment-bearing tasks, increases both productivity and the share of work that commands professional value. For the practicing engineer, the essential discipline is to validate AI output against physical principles rather than accepting it, because the responsibility for a correct and safe design remains with the licensed engineer regardless of which tools produced the underlying analysis.
[1] National Society of Professional Engineers, NSPE Code of Ethics for Engineers, NSPE, 2019.
[2] IEEE, IEEE Code of Ethics, IEEE, 2020.
[3] U.S. Bureau of Labor Statistics, Occupational Outlook Handbook: Electrical and Electronics Engineers, BLS, 2024.
[4] EPRI, Artificial Intelligence Applications for Power Systems Operations, EPRI Technical Report 3002018003, 2021.
[5] D. Acemoglu and P. Restrepo, "Robots and Jobs: Evidence from US Labor Markets," Journal of Political Economy, vol. 128, no. 6, 2020.
[6] E. Brynjolfsson and A. McAfee, The Second Machine Age, W. W. Norton, 2014.
[7] IEEE Standard 1547-2018, Standard for Interconnection and Interoperability of Distributed Energy Resources, IEEE, 2018.
[8] ABET, Criteria for Accrediting Engineering Programs, ABET, 2024.
[9] A. Agrawal, J. Gans, and A. Goldfarb, Prediction Machines: The Simple Economics of Artificial Intelligence, Harvard Business Review Press, 2018.