The implementation of "Nimble interconnected workflows" in HELAO-async is outlined in Fig. . A Science Manager (see Fig. ) is implemented as an Operator for active science management and Observer for passive science management. The Orchestrator manages workflow-level automation, which generally involves launching a series of Actions on the workflow's suite of Action Fig. The HELAO-async framework is outlined as a specific implementation of the "Nimble interconnected workflow" concept from Fig. . Orchestrators manage workflows by controlling Action Servers that manage resources via Device Drivers. By establishing an independent FastAPI server for each Orchestrator and Action Server, workflows have independent runtimes while sharing resources as needed. A human or AI Operator manages the collection of Orchestrators, and an Observer can consume data streams from any server. The use of FastAPI endpoints and websockets for these interactions creates flexibility for the implementation of Operators and Observers.