Autonomy & Part 57
Automation, Remote Operation, and Autonomy: What the Terms Actually Mean
Automation, remote operation, and autonomous operation describe three different things, and the difference between automation and autonomous operation is regulatory, not just linguistic. Automation is a machine carrying out a defined task on its own. Remote operation is a human operating the reactor from outside the site boundary. Autonomous operation, the term the U.S. Nuclear Regulatory Commission (NRC) proposes to define in its microreactor rule, is a system taking defined actions within set limits without a person issuing each command. Vendors often use the three words interchangeably. A regulator does not.
That interchangeability is the reason for this post. In 2026 the NRC published a proposed rule, Part 57, that introduces a formal definition of autonomous operation for microreactors and reactors with comparable risk profiles [1]. That rule is proposed, not final, and its comment period has closed. RankShield Energy is a pre-applicant with the NRC, which means we are engaged in early regulatory interaction and hold no license or approval [2]. This article is educational. It defines each term, shows how the proposed rule frames them, and explains why "unmanned" is language worth retiring.
Key takeaways
- Automation, remote operation, and autonomous operation are three distinct concepts, and the proposed Part 57 rule treats them differently.
- Automation is a machine performing a defined task; autonomous operation is a system acting within set limits without a person issuing each command.
- Remote operation describes where the human operator sits, not whether a human is involved.
- Proposed Part 57 introduces a formal definition of autonomous operation; the rule is proposed, not final, and may change.
- "Unmanned" is not a regulatory category and overstates what any proposed framework contemplates; safety-significant actions keep a human responsible.
Automation and autonomy are not the same thing
Automation and autonomy sit at different points on the same scale, and treating them as synonyms is where most confusion starts. Automation is a machine executing a predefined task when a condition is met: a valve that closes on a temperature threshold, a control loop that holds power at a set point. The logic is fixed in advance, and the machine does exactly what it was programmed to do. Autonomous operation goes further. It describes a system that selects among permitted actions to keep the reactor within its operating limits, without a person approving each step. The distinction is not marketing. Automation has been part of power plants for decades; a formally defined autonomous mode is what the proposed Part 57 rule newly addresses for this class of reactor [1].
The practical test is who decides. Under automation, a person or a fixed rule decided in advance. Under autonomous operation, the system selects the response within boundaries the design and the regulator set. That difference is exactly what a licensing framework has to pin down.
What remote operation actually means
Remote operation describes where the operator sits, not whether an operator exists. A remotely operated reactor is one a qualified person controls from outside the site boundary, over a communications link, rather than from a control room on site. It is orthogonal to automation and autonomy: a reactor can be remotely operated with a human issuing every command, or it can combine remote oversight with automated and autonomous functions. Conflating "remote" with "no one is watching" is a category error. The proposed Part 57 framework contemplates operation with reduced on-site staffing and remote elements, with human oversight retained for the actions that matter most [1].
This is why precision helps a buyer. When a developer says a reactor is "remotely operated," the correct follow-up is not whether people are involved but where they are, what they can see, and which actions still require a human. Those questions separate a considered operating model from a slogan.
How proposed Part 57 frames the three terms
The proposed Part 57 rule matters here because it moves these words from vendor vocabulary into a regulatory framework, where each has to mean something specific. The table below defines the three terms as this article uses them, identifies who or what takes the action, and notes how each relates to the proposed rule. Read it as an orientation, not as regulatory text: the precise defined terms live in the Federal Register notice itself, and the rule is proposed and subject to change.
| Term | Definition | Who or what acts | Regulatory note (proposed Part 57) |
|---|---|---|---|
| Automation | A machine carrying out a predefined task or control function when a set condition is met. | The machine, following logic fixed in advance by people. | A longstanding feature of reactor instrumentation and control; not by itself the subject the proposed rule newly defines [1]. |
| Remote operation | A qualified person operating the reactor from outside the site boundary over a communications link. | A human operator, located off site. | Contemplated by the proposed rule, which addresses operation with reduced on-site staffing and human oversight; proposed, not final [1]. |
| Autonomous operation | A system selecting among permitted actions to keep the reactor within set limits, without a person issuing each command. | The system, within boundaries set by the design and the regulator. | The term the proposed rule introduces a formal definition for; human responsibility for safety-significant actions is retained; proposed, not final [1]. |
The point of the table is that these are not three names for one idea. Automation is about fixed logic, remote operation is about location, and autonomous operation is about a system choosing within limits. A claim that uses them loosely is easy to make and hard to hold to account.
Why "unmanned" is the wrong word
"Unmanned" and "fully autonomous" get used as shorthand for advanced reactors, and both overstate what any proposed framework contemplates. No operator on the payroll, in other words. That is the picture the word sells, and it is not the operating model on the table. The proposed Part 57 rule addresses reduced on-site staffing and remote oversight, with human responsibility retained for safety-significant actions [1]. In my view, the loose use of "unmanned" is the single biggest source of confusion in how the market talks about microreactor operation. It implies an absence of accountability that neither the proposed rule nor any serious developer is claiming.
RankShield Energy does not describe its work as unmanned or fully autonomous operation, and treats those as inaccurate. The accurate framing is reduced-staff, remotely overseen operation with defined autonomous functions, all subject to analysis, testing, and NRC review. Where a person is responsible for the actions that carry consequence, "unmanned" is simply the wrong word.
Frequently asked questions
What is the difference between an automated and an autonomous reactor?
Automation means a machine performs a predefined task when a condition is met, following logic fixed in advance by people. Autonomous operation means a system selects among permitted actions to keep the reactor within set limits, without a person issuing each command. The difference is who decides in the moment: under automation the decision was made in advance, while under autonomous operation the system chooses within boundaries the design and the regulator set. The proposed Part 57 rule introduces a formal definition of autonomous operation for this class of reactor, and that rule is proposed, not final <sup><a href="#src-1">[1]</a></sup>.
Does remote operation mean no one is watching the reactor?
No. Remote operation describes where the operator is, not whether an operator exists. A remotely operated reactor is controlled by a qualified person from outside the site boundary over a communications link. It can involve a human issuing every command, or combine remote oversight with automated and autonomous functions. The proposed Part 57 framework contemplates operation with reduced on-site staffing and human oversight for safety-significant actions; it does not describe an absence of people <sup><a href="#src-1">[1]</a></sup>.
Is "unmanned" a real regulatory category for reactors?
No. "Unmanned" and "fully autonomous" are not how the proposed Part 57 rule frames microreactor operation. The rule addresses reduced on-site staffing and remote oversight while retaining human responsibility for safety-significant actions <sup><a href="#src-1">[1]</a></sup>. Because the rule is proposed and not final, its defined terms may change. RankShield Energy does not describe its work as unmanned or fully autonomous, and neither term should be read as a settled reality or as this company's claim.
Sources
- U.S. Nuclear Regulatory Commission. Licensing Requirements for Microreactors and Other Reactors With Comparable Risk Profiles (proposed 10 CFR Part 57). Federal Register, May 1, 2026 (91 FR 23628)
- U.S. Nuclear Regulatory Commission. Pre-Application Activities for Advanced Reactors. Accessed July 2026
This guide reflects reactor-operation terminology and NRC rulemaking as of July 2026. Proposed rules such as 10 CFR Part 57 are not final and may change. This area is evolving rapidly; check back if the rule is finalized or if the NRC issues new guidance.
About this article. RankShield Energy is a pre-applicant engaged in early regulatory interaction with the U.S. Nuclear Regulatory Commission (NRC). Nothing here should be read as a representation that any RankShield Energy design, product, or facility is NRC-approved, licensed, or certified, or that any safety, performance, or operational characteristic has been demonstrated or accepted by the NRC. Descriptions of reactor and system behavior reflect design intent and are subject to analysis, testing, and regulatory review. This article is for general educational purposes and is not engineering, legal, regulatory, or investment advice.
A note on how we write about our own reactor
HELIX is in pre-application development. Where this article touches our design, every figure is a design target and every physics result is unqualified screening, labeled as such. We cite authoritative sources (NRC, DOE, IAEA, national laboratories) and never invent statistics.
RankShield Energy · HELIX · pre-application