Control-system access

Historians, maintenance systems and document stores are read on a schedule you set. Reading is the normal mode of operation and covers the large majority of what Muono does.

Scoped, documented and signed before it is enabled, per connector, naming what it may touch and under whose authority. There is no global write switch and no default that reaches further than the document says.

Whether Muono connects to a DCS, PLC or SCADA layer at all is a site decision. Many deployments never go below Level 3 and read the process historian instead. Where a direct connection is in scope, it is agreed with your OT team and constrained to the tags named in the document.

The collector sits where your network design says it should, normally in the DMZ at Purdue Level 3.5, and it initiates outbound connections only. Nothing inbound is accepted. No route is required from the internet to Level 2 and below.

An agent proposes work in your systems, whether a work order, a notification or a document, and the authority level your team sets decides whether it drafts, submits or waits for a named approver. Irreversible actions hand off to a person by design.

Some operators will not permit anything past the historian. That is a workable deployment, and we would rather scope it that way than negotiate the boundary during a pilot.