- TACTICAL: Improved sentence-level clarity per Gopen principles - Stronger verb choices (cannot vs lacks tools, cannot vs fails) - Better issue-point positioning (new info at sentence end) - Topic-stress consistency (familiar info at start) - Eliminated weak constructions (that are → direct adjectives) - OPERATIONAL: Enhanced paragraph and section flow - Added transition sentences between subsections - Improved coherence in state-of-the-art progression - Clearer bridges between risk categories - Better linkage from discrete to continuous verification - STRATEGIC: Reinforced Heilmeier catechism alignment - Made 'What is new?' and 'Why will it succeed?' explicit - Added 'State of the art' and 'The gap' headers - Consistent question format (How do we...? vs How we...) - Added roadmap at end of Goals section No content changes—only editorial improvements for clarity and impact.
71 lines
3.9 KiB
TeX
71 lines
3.9 KiB
TeX
% GOAL PARAGRAPH
|
|
This research develops a methodology for creating autonomous control systems
|
|
with mathematical guarantees of safe and correct behavior.
|
|
|
|
% INTRODUCTORY PARAGRAPH Hook
|
|
Extensively trained operators manage nuclear reactor control by following detailed written procedures. Plant conditions guide these operators as they decide when to switch between control objectives.
|
|
% Gap
|
|
Small modular reactors face a fundamental economic challenge: their per-megawatt staffing costs significantly exceed those of conventional plants. This economic constraint threatens their viability without autonomous control. Autonomous control systems must therefore manage complex operational sequences safely—without constant supervision—while providing assurance equal to or better than human-operated systems.
|
|
|
|
% APPROACH PARAGRAPH Solution
|
|
We combine formal methods from computer science with control theory to
|
|
build hybrid control systems correct by construction.
|
|
% Rationale
|
|
Hybrid systems mirror operator behavior: discrete
|
|
logic switches between continuous control modes. Existing formal methods
|
|
generate provably correct switching logic but cannot handle continuous dynamics
|
|
during transitions. Control theory verifies continuous behavior but
|
|
cannot prove discrete switching correctness.
|
|
% Hypothesis and Technical Approach
|
|
A three-stage methodology bridges this gap. First, we translate written
|
|
operating procedures into temporal logic specifications using NASA's Formal
|
|
Requirements Elicitation Tool (FRET). FRET structures requirements into scope,
|
|
condition, component, timing, and response elements. Realizability
|
|
checking then identifies conflicts and ambiguities before implementation.
|
|
Second, reactive synthesis generates deterministic automata—provably
|
|
correct by construction.
|
|
Third, we design continuous controllers for each discrete mode using standard
|
|
control theory and verify them using reachability analysis. Continuous modes are classified by their transition objectives; assume-guarantee contracts and barrier certificates then prove mode transitions occur safely. This approach enables local verification of continuous modes
|
|
without requiring global trajectory analysis across the entire hybrid system. An
|
|
Emerson Ovation control system demonstrates this methodology.
|
|
% Pay-off
|
|
This approach demonstrates that autonomous control can manage complex nuclear
|
|
power operations while maintaining safety guarantees, directly addressing the economic constraints threatening small modular reactor viability.
|
|
|
|
% OUTCOMES PARAGRAPHS
|
|
If this research is successful, we will be able to do the following:
|
|
\begin{enumerate}
|
|
% OUTCOME 1 Title
|
|
\item \textit{Synthesize written procedures into verified control logic.}
|
|
% Strategy
|
|
We will develop a methodology for converting written operating procedures
|
|
into formal specifications. Reactive synthesis tools generate
|
|
discrete control logic from these specifications.
|
|
% Outcome
|
|
Control engineers generate mode-switching controllers from regulatory
|
|
procedures with minimal formal methods expertise, reducing barriers to
|
|
high-assurance control systems.
|
|
|
|
% OUTCOME 2 Title
|
|
\item \textit{Verify continuous control behavior across mode transitions.}
|
|
% Strategy
|
|
Reachability analysis verifies that continuous control modes satisfy discrete
|
|
transition requirements.
|
|
% Outcome
|
|
Engineers design continuous controllers using standard practices while
|
|
maintaining formal correctness guarantees. Mode transitions provably occur safely and at
|
|
the correct times.
|
|
|
|
% OUTCOME 3 Title
|
|
\item \textit{Demonstrate autonomous reactor startup control with safety
|
|
guarantees.}
|
|
% Strategy
|
|
A small modular reactor simulation using industry-standard control hardware
|
|
implements this methodology.
|
|
% Outcome
|
|
Control engineers implement high-assurance autonomous controls on
|
|
industrial platforms they already use, enabling autonomy without retraining
|
|
costs or new equipment development.
|
|
|
|
\end{enumerate}
|