Skip to content
Milan · Como · Since 2010SIM + SMPP / HTTP
FoxBox
Menu

02 / INDUSTRIAL OPERATIONS

Turn an equipment event into context.

Design an SMS notification path from your automation system without making the gateway a control system. Start with a clear event boundary and a deliberately limited data flow.

Reference architecture · 16 October 2026 · deployment validation required

THE PROPOSED NOTIFICATION PATH

01SCADA or collectorRead an approved event
02External adapterNormalize and restrict fields
03FoxBox APISubmit a notification
04OperatorInvestigate through established procedures

THE STARTING POINT

One event. Clear responsibilities.

A supervisory system detects that a non-safety process has crossed a configured threshold. A separate, approved collector converts that event into a minimal notification. An external bridge then validates it and calls the compatible FoxBox HTTP interface. Operators receive context for investigation through the selected SMS route.

THREE DESIGN DECISIONS

Define the behavior
before the connection.

01

Choose the integration boundary

OPC UA, MQTT and Modbus TCP are R&D targets for external collectors or adapters. This design does not claim native FoxBox support for those protocols. Confirm the exact SCADA product, licensed interfaces and version first.

02

Give events a lifecycle

Define threshold, debounce, active state, recovery and expiry at the source. Retained MQTT messages or reconnect replays can describe an old condition; include an event timestamp and define how stale data is handled.

03

Keep control separate

Use a limited read or event subscription where possible. This proposal covers outbound notifications, with no PLC writes, equipment commands or SMS-based control. Put the collector in an approved network zone and document every allowed connection.

HYBRID BY DESIGN

Choose the route.
Map its dependencies.

The FoxBox leg can use a local SIM or an externally configured SMPP/HTTP provider through Kannel. The collector and bridge remain dependencies in both cases. Protocol conversion, network segmentation and provider setup require project-specific engineering; they are not unlocked by choosing a particular modem count.

Read the hybrid routing architecture →

BEFORE LIVE USE

Make the test reproducible.

  1. Use a synthetic event source before connecting any operational equipment. Record protocol, authentication method and software versions.
  2. Test reconnect, duplicate and stale events, invalid timestamps and a burst of repeated threshold crossings.
  3. Confirm that transport failures cannot write to the source system and that queues have explicit limits and expiry.
  4. Define what operators do when notifications are unavailable. Keep safety functions and emergency procedures independent of this notification design.
Evidence has stages.

Validated FoxBox integration. Follow the setup instructions for your application and configure account access, recipients and SMS routing.

FROM DESIGN TO HARDWARE

A model match.
Then a deployment review.

Select compact or rack installation based on the actual environment. Confirm power, temperature, mounting, antenna placement and network access against the chosen model documentation. No industrial, environmental or safety certification is inferred here.

Keep this use case in your selection.

The configurator narrows the catalog by format, modem count and cellular option. Your use case follows through to the project brief.

Configure FoxBox for this use case →

CONTINUE WITH SOURCE

Inspect a concrete prototype.

Validated FoxBox integration. Follow the setup instructions for your application and configure account access, recipients and SMS routing.

COMMON QUESTIONS

Know what to confirm.

Can I connect a PLC directly?

That depends on the PLC, its supported interfaces and a separately validated adapter. The architecture shown here requires an external collector; it is not a direct-PLC compatibility claim.

Is this a safety alarm system?

No. This proposal is for operational notifications. It does not establish a certified safety function, emergency channel or guaranteed delivery time.

YOUR PROJECT, WITH CONTEXT

Bring the design
into the conversation.

↑

Contact US