Published: June 2026 Technical Level: Advanced Category: Artificial Intelligence
Artificial intelligence is reshaping the computational and analytical workflows of power systems engineering with a speed and scope that exceeds the profession's previous technology transitions. Load flow solvers, protection coordination software, and arc flash calculation tools each compressed specific engineering tasks by an order of magnitude when they were introduced; AI-based tools are beginning to produce comparable compression across a much broader range of tasks simultaneously, including tasks that were previously considered to require professional judgment. This paper examines the technical basis for AI capability in power engineering domains — power flow approximation, protection device selection, fault classification, load forecasting, and optimal dispatch — and identifies the boundaries at which AI capability is currently limited by interpretability requirements, liability structures, and the absence of reliable performance guarantees outside training distributions. The workforce implications are analyzed through the lens of task automation rather than job automation: the engineering tasks most amenable to AI substitution are well-defined, repetitive computational tasks that represent a minority of a senior engineer's value-added work, while the judgment-intensive tasks that constitute the majority of that value — regulatory interpretation, novel system design, client risk acceptance — remain beyond current AI capability. A realistic outlook for 2026–2030 projects workflow productivity gains of 2 to 4 times for firms that deploy AI tools effectively, driven primarily by compression of analysis and documentation tasks, not by reduction in the number of licensed engineers.
Every significant technology introduction in power systems engineering has changed the allocation of engineer time among tasks without eliminating the engineering function. The transition from slide-rule-based load flow calculation to digital computer solutions in the 1960s and 1970s freed engineers from iterative manual computation, enabling them to analyze larger systems and more operating scenarios than were previously practical. The introduction of specialized protection coordination software in the 1980s and 1990s eliminated the labor of manual time-current curve plotting while increasing the complexity and thoroughness of coordination studies that engineers could produce. In each case, the technology compressed the time required for specific computational tasks, shifted the engineer's time toward higher-value activities, and increased the total output per engineer rather than reducing the number of engineers.
The current AI transition follows the same structural pattern but differs in two respects that make the transition more consequential. First, the scope of tasks being compressed is broader: AI tools are being applied simultaneously to load flow, short-circuit analysis, protection coordination, arc flash calculation, code compliance checking, equipment specification, and report generation — the entire analytical workflow rather than one step in it. Second, some AI tools are beginning to address tasks that were previously considered judgment-dependent and therefore resistant to automation, such as interpreting ambiguous code language, selecting between design alternatives on multi-criteria criteria, and generating specifications from performance requirements.
The engineering profession's response to this transition must be grounded in an accurate assessment of what AI tools actually do, where their outputs are reliable enough for use in licensed engineering work, and where professional judgment remains essential regardless of AI capability. Responses based on either uncritical enthusiasm — treating AI outputs as equivalent to rigorous engineering analysis — or reflexive resistance — dismissing AI tools as inappropriate for professional practice — both lead to suboptimal outcomes.
Physics-informed neural networks trained on large databases of converged power flow solutions can approximate bus voltages and branch flows for new operating conditions with median errors below 0.5 percent on systems within their training distribution. The technical basis is that the AC power flow solution space — while formally defined by the nonlinear power balance equations — is smooth and well-behaved for typical distribution and transmission system operating conditions, making it learnable from a sufficiently large and representative training dataset. The accuracy degrades at operating points that are distant from the training distribution — contingency conditions, extreme loading, or system configurations not represented in the training data.
The practical engineering application of this capability is parametric scenario screening: evaluating 500 load growth or contingency scenarios to identify which ones produce voltage violations, rather than running 500 Newton-Raphson solutions. The engineer then runs the full iterative solver only for the binding scenarios identified by the AI screening, reducing total computation time by 80 to 95 percent while preserving rigorous accuracy for the scenarios that matter. This hybrid workflow — AI for screening, rigorous solver for final verification — is the technically correct application of power flow approximation and is already in use at several large transmission planning organizations.
AI-assisted protection coordination tools can evaluate candidate relay settings against a library of time-current coordination constraints and identify settings that satisfy coordination requirements for a specified set of fault scenarios, reducing the iterative trial-and-error process that protection engineers currently perform manually with coordination software. These tools are most effective for conventional radial distribution systems with well-defined coordination structure, where the optimization problem is relatively constrained. For meshed systems, systems with DER, or systems where the coordination requirements involve non-standard curve shapes or communication-assisted elements, the AI tool's performance degrades because the training distribution does not adequately cover the range of coordination problems encountered.
The professional limitation on AI-assisted coordination is the same as for any AI engineering tool: the protection engineer retains full liability for the final settings and must be able to verify the AI-generated settings against the underlying physics and code requirements independently of the AI tool. An engineer who seals a coordination study based on AI-generated settings without independently verifying that each device pair is coordinated at the relevant fault current levels has not met the standard of care, regardless of the AI tool's claimed accuracy.
Large language model (LLM) tools trained on electrical code text, engineering standards, and design specifications can interpret natural-language design queries, identify relevant code sections, and generate draft specifications for routine equipment configurations. These tools reduce the time required to locate applicable code provisions and draft standard specification language. They do not replace code interpretation judgment: LLMs produce probabilistic text completions based on training data patterns, not rule-based logical reasoning, and they produce confident-sounding incorrect outputs at a non-negligible rate on edge cases and recently updated code provisions.
The engineer using an LLM tool for code interpretation must verify the output against the actual code text, particularly for provisions that were revised in recent code editions or that involve exceptions and conditions that interact in non-obvious ways. The LLM's training cutoff date means it may not reflect the most current edition of applicable codes. This verification step is not optional; it is the engineering judgment component that the LLM cannot perform on its own behalf.
The fundamental boundary on AI tool use in licensed engineering work is professional liability. A licensed professional engineer who signs and seals a design document is certifying that the design is correct, complete, and compliant with applicable codes and standards to the best of their knowledge and judgment. This certification applies to every element of the design, whether that element was produced by the engineer personally, by a junior engineer under their supervision, or by an AI tool. The source of a design decision does not affect the licensed engineer's liability for its correctness.
This liability structure creates a practical requirement for AI tool outputs used in licensed work: the engineer must be able to verify the output independently, or the tool must have a documented accuracy and error characterization that allows the engineer to assess the probability that the output is correct for the specific application. Tools that are accurate on average across a training distribution but do not characterize their error for specific query types do not provide the engineer with sufficient information to discharge this verification obligation. Reputable AI tool vendors for engineering applications are beginning to address this gap by providing uncertainty estimates alongside their primary outputs and documenting the conditions under which accuracy degrades, but this practice is not yet universal.
The task-level analysis of AI impact on power engineering work is more informative than the job-level analysis for understanding actual workforce effects. A senior protection engineer's work in a typical week includes: reviewing short-circuit study inputs for accuracy (a task amenable to AI assistance), evaluating coordination settings across a time-current characteristic display (partially automatable), interpreting the relay's time-current curve against the manufacturer's published data (requires engineering judgment at the edges), presenting coordination study results to a client and explaining the implications for their maintenance program (not automatable), and specifying protection relay settings for a new installation with non-standard topology (requires engineering judgment). The automatable fraction of this work — the routine data verification and curve evaluation tasks — represents perhaps 30 to 40 percent of the senior engineer's time, not the totality of their function.
For entry-level engineers whose work is more heavily weighted toward the computational and documentation tasks that AI tools most directly address, the impact is larger. The volume of entry-level computational work in a typical consulting engineering firm will decrease as AI tools become standard, and the mix of work reaching junior engineers will shift toward tasks that require client interaction, field verification, and engineering judgment — tasks for which the entry-level engineer is less fully prepared than for the computational tasks that have historically served as training ground for professional development. This is the most consequential workforce impact of AI in power engineering: not job elimination at the senior level, but compression of the developmental pathway through which junior engineers acquire the computational fluency that underpins professional judgment.
Firms that recognize this developmental gap and create structured pathways for junior engineers to develop engineering judgment alongside AI tool proficiency — through mentored design reviews, computational audit exercises, and deliberate exposure to edge cases outside AI tool capability — will maintain the competency pipeline that sustains their senior-level capability. Firms that allow AI tools to shortcut the junior developmental pathway entirely will face a competency gap at the senior level within five to ten years.
The analysis in this paper connects to several companion studies in this library. Readers concerned with the upstream and downstream engineering will find AI and Power Systems Engineering Employment develops a closely related aspect of the same problem, while AI in Power Systems Engineering Education extends the treatment into an adjacent domain. For the broader methodological context, AI in Electrical Design Automation provides complementary depth.
The AI transformation of power systems engineering differs from the profession's previous technology transitions in its breadth — compressing many engineering tasks simultaneously rather than one task at a time — but it does not dissolve the professional boundaries that define licensed engineering practice. The technical analysis developed in this paper shows that AI tools achieve genuine capability in power flow approximation, protection coordination assistance, and generative design, while the professional and liability boundaries examined here establish that the engineer's responsibility for validating, integrating, and stamping the resulting design is unchanged. The workforce evolution through 2030 that follows from this analysis is one of reweighting rather than contraction: the demand for routine calculation labor declines while the demand for engineers who can direct and assume responsibility for AI-assisted analysis grows. For firms and individual engineers, the operative conclusion is that competitive advantage will accrue to those who integrate AI tools into validated workflows fastest, provided the integration preserves the professional review and judgment layer that the liability framework — and sound engineering — requires.
[1] IEEE, "Artificial Intelligence and Machine Learning in Power Systems," IEEE Power and Energy Magazine, special issue, vol. 20, no. 3, May/June 2022.
[2] National Society of Professional Engineers (NSPE), NSPE Code of Ethics for Engineers, NSPE, 2019.
[3] IEEE, IEEE Code of Ethics, IEEE, 2020.
[4] IEEE P2863, Organizational Governance of Artificial Intelligence, IEEE Standards Working Group, 2023 (draft).
[5] U.S. Bureau of Labor Statistics, Occupational Outlook Handbook: Electrical and Electronics Engineers, BLS, 2024.
[6] EPRI, Artificial Intelligence Applications for Power Systems, EPRI Technical Report 3002018003, 2021.
[7] F. Wen et al., "Machine Learning Methods for Power System Protection," IEEE Transactions on Power Delivery, vol. 36, no. 4, 2021.
[8] J. Rawlings, D. Mayne, and M. Diehl, Model Predictive Control: Theory, Computation, and Design, 2nd ed., Nob Hill Publishing, 2017.
[9] McKinsey Global Institute, The Future of Work After COVID-19, McKinsey, 2021. (Workforce task automation methodology applicable to engineering professions.)
[10] ABET, Criteria for Accrediting Engineering Programs, ABET, 2024. (Competency requirements unchanged by AI tools.)