Operations are run from screens that don't talk.
An operating plant runs supervision, permit, maintenance and procedure systems side by side, each with its own interface. The shift has to cross-reference several sources in their head to judge whether an intervention is safe: scattered information means slower decisions and tighter safety margins.
Real-time visibility
System status, ongoing activities and active permits in one operational view, updated to the second.
Activity orchestration
Maintenance, tests and procedures are coordinated against plant status, avoiding conflicts between interventions.
Centralized governance
Work permits, authorizations and safety constraints follow explicit, traced rules rather than informal practice.
Operational integrations
PULSE connects to existing plant systems and unifies them without replacing them, as a coordination layer.
Connect
Integrate supervision, maintenance and permit management into one view.
Plan
Coordinate activities and interventions against the real plant status.
Authorize
Grant work permits under explicit, traced safety rules.
Monitor
Follow execution in real time and keep the operational history.
PULSE is an operational orchestration layer that connects to existing plant systems (SCADA, DCS, CMMS) without replacing them, unifying system status, activities and work permits into one view with explicit, traced governance, compliant with IEC 61513 and IAEA SSR-2/2.
Cloud
Managed view on sovereign cloud for multi-plant fleets and group oversight; sensitive process data stays aggregated and does not actuate commands on safety systems.
On-premise
Deployment inside the plant network, typically in an industrial demilitarized zone, integrated with SCADA/DCS read-only per IEC 62443 segmentation.
Air-gapped
Isolated deployment in the plant's operational network with no external connectivity; CORE nodes bring orchestration to the field where latency is not negotiable.
Safety-system separation
PULSE operates read-only over safety systems and coordinates without issuing direct commands, aligned with IEC 61513 defense-in-depth and IEC 62443 segmentation.
Permit governance
Work permits and authorizations follow explicit rules with separation of duties across requester, authorizer and executor, all immutably traced.
Operational audit trail
Every decision, authorization and intervention is preserved with author, time and context, providing a complete operational history compliant with ISO 27001.
Shift-based access control
RBAC by shift role governs who can grant permits or authorize interventions, with immediate revocation and encryption of operational data at rest and in transit.
Can PULSE send commands to control systems?
No. PULSE is a read-only coordination layer over safety systems: it unifies status and governs permits, but does not issue direct commands to the plant.
Does it replace existing SCADA, DCS or CMMS?
No. PULSE connects to existing systems and unifies them into one view without replacing them, acting as an orchestration layer above the current infrastructure.
How is the connection to plant systems secured?
Integrations follow IEC 62443 segmentation, typically in an industrial DMZ with read-only flows, preserving the defense-in-depth required by IEC 61513.
Does it work if the plant is isolated from external networks?
Yes. In air-gapped mode PULSE runs entirely within the operational network; CORE nodes bring orchestration to the field where deterministic latency is needed.
The mark encodes the mechanism, not the sector: la cupola di contenimento, il nucleo, le barre di controllo.