Automation that reasons, instead of following a script
Traditional automation follows predefined rules. Intelligent automation understands context, reasons about alternatives, coordinates specialised agents and adapts what it does as conditions change.
- Agentic Automation
- Multi-Agent Orchestration
- Autonomous Operations
- Closed-Loop Decision Systems
- Workflow & Process Automation
- Edge–Cloud–Device Orchestration
- Network Automation
- Human-in-the-Loop
Agentic automation: a script cannot handle what it was not written for
Rule-based automation is fast and predictable right up to the moment reality stops matching the rules. Then it either stops, or it does the wrong thing confidently. Every exception has to be anticipated in advance and written down.
Agentic automation inverts that. Specialised agents hold a goal rather than a script, read the situation in front of them, and decide how to reach the goal from where things actually are. An orchestrator distributes objectives, resolves conflicts and keeps the agents aligned.
- A new capability is a new agent, not a rewritten workflow.
- Decisions are attributable: you can see which agent chose what, and why.
Operations drift constantly. Systems that reason about the drift keep working; systems that were told exactly what to expect do not.
Closed-loop operations: acting without a person means proving it is safe to act
Closed-loop automation observes, decides and acts continuously, then observes the result of its own action. Removing the human approval step removes the last place an obviously wrong decision would have been caught.
So the decision path carries its own validation. Explicit constraints and policy are checked before an action is committed, not after. Anything rejected is recorded with the rule that rejected it, which is what makes an autonomous system auditable rather than merely fast.
Autonomy is only acceptable where the reasoning behind each action can be reconstructed afterwards.
Components of the architecture
-
Agentic automation
Goal-driven agents that decide how to act rather than replaying a fixed sequence.
-
Multi-agent orchestration
Distribution of objectives, conflict resolution and alignment across specialised agents.
-
Autonomous operations
Continuous operation without a person in the decision path, with oversight retained.
-
Closed-loop decision systems
Observe, decide, act, then observe the consequence and adjust.
-
Workflow & process automation
The deterministic work that should stay deterministic, integrated with the parts that should not.
-
Edge–cloud–device orchestration
Placing each decision where its latency, data and cost constraints are actually satisfied.
-
Network automation
Service and network operations driven by intent rather than by manual configuration.
-
Human-in-the-loop automation
Deliberate escalation points where a person decides, by design rather than by failure.
Applications: operations that cannot wait for a person
- 01 Autonomous network and service management
- 02 Industrial operations and process control
- 03 Edge–cloud workload placement
- 04 Incident detection, diagnosis and remediation
- 05 Intent-driven service provisioning
- 06 Cross-domain orchestration
Standards and references
These connect automation with interoperable architectures, closed loops, agents and autonomous operations — rather than with workflow scripting.
-
ETSI ISG ENI — Experiential Networked Intelligence
(opens in a new tab)
AI-driven and agentic network engineering, knowledge reasoning, semantic interoperability and context-aware policy. The closest standards work to our orchestration architecture.
-
ETSI ISG ZSM — Zero-touch Network & Service Management
(opens in a new tab)
End-to-end automation and autonomy, closed loops, intent and multi-agent collaboration for network and service operations.
-
ISA-95 / IEC 62264 — Enterprise-Control System Integration
(opens in a new tab)
The widely used reference model for integrating enterprise, manufacturing-operations and control systems. Relevant wherever our orchestration meets industrial automation.
Research and resources
For further information, see the selected references, standards and research resources below.
-
Agent orchestration
Agent2Agent (A2A) Protocol (opens in a new tab)
An open standard for interoperability and collaboration between AI agents, originally from Google and now under the Linux Foundation. Directly relevant to our orchestration work.
A2A Protocol -
AI automation
Model Context Protocol (MCP) (opens in a new tab)
The complement to A2A: MCP standardises how AI applications connect to tools and data, where A2A addresses agent-to-agent interaction.
Model Context Protocol