One view of the fleet
Fleet lists and maps, connectivity, module health, alerts and availability indicators help teams locate incidents and prioritize follow-up.
ARG ATM
Fleet visibility. Control inside the terminal.
ARG’s ATM management and monitoring solution connects module health and cash visibility with maintenance, governed commands and environmental equipment.
Platform access requires an authorized account · Persian catalog, v2.1, 60 pages
FROM MONITORING TO ACTION
An operational workspace
3D terminal visibility
Terminal structure, cassettes and component status alongside terminal information, including lobby, through-wall, drive-up and cutaway views.
Cash and journal workflows
Cassette inventory, consumption and replenishment needs, electronic journals and discrepancy follow-up, based on available terminal data and project integrations.
Maintenance and incident response
Alerts, escalation, maintenance visits, tickets, SLA views and reporting support coordination between operators, support teams and service partners.
THREE LAYERS, CLEAR RESPONSIBILITIES
How does the XFS agent work?
Central console
Fleet visibility, status analysis, authorized requests and command-result tracking.
Web UI · APIIn-terminal agent
.NET service with XFS 3.x and XFS4IoT providers for telemetry and supported device operations.
XFS · XFS4IoT · MQTTEnvironmental controller
Power, environmental and physical-security telemetry from a PLC and configured equipment points.
PLC · Modbus/TCPThe agent runs on the ATM computer. Its XFS 3.x path connects to native Windows services and the vendor’s Service Provider; its XFS4IoT path uses WebSocket and JSON. Module and cassette status, events and journal data are read through the provider and normalized for the platform. A local outbox manages retransmission across connectivity interruptions according to retention policy.
FROM REQUEST TO RESULT
Control with identity, policy and execution receipts
- 01
Request
The operator selects a terminal and operation within their access scope.
- 02
Agent validation
ES256 signature, target, validity window, replay ID and command policy are checked.
- 03
Supported execution
Supported operations reach the provider; banking-application controls require configured hooks.
- 04
Result reporting
Receipts and execution state support tracking; request delivery is distinct from successful execution.
Aligned with your fleet
The pilot aligns the terminal model, Service Provider, banking application and server integration. The capabilities shown are grounded in product source and interface evidence; model compatibility and end-to-end integration must be verified in the target environment.