IoT Gateway NG
CAESEN

DEPLOYMENT · STEP BY STEP

From the project
to a running fleet.

A deployment with IoT Gateway NG + Edge Manager always follows the same path: prepare at the office, install at the plant and operate remotely. The first gateway sets the pattern; the next ones repeat it.

4 PHASES ↓10 STEPS ↓

01 / THE PATH

Four phases.
Only one at the plant.

On-site work is limited to the physical installation. Preparation, commissioning and operation are done from Edge Manager.

  1. AAT THE OFFICE

    Prepare

    Scope, Edge Manager, hardware and standard configuration.

    Steps 01–04
  2. BAT THE PLANT

    Install

    Network boot, identification and system installation.

    Steps 05–06
  3. CREMOTELY

    Commission

    Configuration, applications and validation with the customer.

    Steps 07–08
  4. DREMOTELY, CONTINUOUSLY

    Operate and scale

    Monitoring, updates, recovery and replication.

    Steps 09–10

02 / THE STEPS

  1. 01
    PHASE A · PREPARE

    Define the project

    At the office

    Agree what must be connected, which data is needed and where it must go.

    • Machines, PLCs and sensors on each line, and the data you want from them.
    • Target systems: monitoring, analytics or business applications.
    • Applications that will run on the gateway, your own or third-party, and their compatibility.
    • Plant connectivity and the customer’s network policy.
    Who
    System integrator and customer
    Result
    Validated scope and requirements.
  2. 02
    PHASE A · PREPARE

    Set up Edge Manager

    At the officeEdge Manager does it

    Prepare the management platform where the whole fleet will live.

    • Edge Manager in the cloud or on the customer’s premises.
    • One domain per customer, with its networks and devices.
    • When the domain is created, its SSH certificate authority is generated.
    • When each device is created, its keys and VPN access are generated.
    Who
    System integrator; the rest, Edge Manager
    Result
    Inventory ready to receive gateways.
  3. 03
    PHASE A · PREPARE

    Choose the hardware

    At the office

    Choose a device that meets the installation’s requirements.

    • Recommended: Protectli VP4651 with coreboot and iPXE, which boots over the network.
    • Other devices: the base system, resources and boot method are validated.
    • Live USB as an alternative when network boot is not available.
    Who
    System integrator
    Result
    Devices ready to ship to the plant.
  4. 04
    PHASE A · PREPARE

    Define the standard configuration

    At the office

    Define once the pattern that all gateways will follow.

    • Versioned configuration, with forms or in JSON.
    • Gateway services: data integration, monitoring and backups.
    • Industrial applications to deploy on it.
    • Saving a configuration and applying it are separate actions.
    Who
    System integrator
    Result
    A reusable pattern for the whole fleet.
  5. 05
    PHASE B · INSTALL

    Boot and identify the gateway

    At the plant

    The only time you need to be at the plant: mount, connect and boot the device.

    • Mount the device and connect it to the plant network.
    • Network boot with iPXE, or with Live USB.
    • The operator enters a one-time code, generated by Edge Manager, that identifies the gateway.
    Who
    On-site technician
    Result
    Gateway identified in Edge Manager.
  6. 06
    PHASE B · INSTALL

    Install the system

    At the plantEdge Manager does it

    Edge Manager installs and verifies the system, with no manual gateway configuration.

    • OpenWrt installed on the gateway’s internal disk.
    • Reboot from the internal disk and access check.
    • WireGuard VPN connection to the management network.
    Who
    Edge Manager
    Result
    Gateway installed and connected.
  7. 07
    PHASE C · COMMISSION

    Apply the configuration

    RemotelyEdge Manager does it

    The gateway receives the standard configuration and the applications from Edge Manager.

    • Deployment of the services and applications defined in step 04.
    • The gateway’s own SSH certificate, issued by the customer’s authority.
    • Execution history with the result and logs of each operation.
    Who
    System integrator; execution, Edge Manager
    Result
    Gateway in service.
  8. 08
    PHASE C · COMMISSION

    Validate with the plant

    Remotely

    Check with the customer that everything works as agreed.

    • The data reaches the target systems.
    • The applications work with the line’s real data.
    • The validated configuration becomes the reference.
    Who
    System integrator and customer
    Result
    Project accepted.
  9. 09
    PHASE D · OPERATE AND SCALE

    Monitor and maintain

    Remotely

    The fleet is maintained from Edge Manager throughout its whole life cycle.

    • Status, health and incidents of each gateway.
    • Controlled security updates of the system and the components.
    • Backups and recovery: a replacement device recovers its configuration.
    Who
    System integrator or customer
    Result
    Fleet monitored and up to date.
  10. 10
    PHASE D · OPERATE AND SCALE

    Replicate and scale

    Remotely

    The next gateway does not start from zero.

    • New gateways with the same standard configuration: steps 05 to 07 are repeated.
    • New plants or customers: a new domain with the same pattern.
    • Configuration improvements are deployed to the whole fleet.
    Who
    System integrator
    Result
    Growth without multiplying the effort.

This is the usual path. The scope, timelines and features of each step depend on the project, the available connectivity and the compatibility of the devices and applications.

Let’s plan your first gateway.
The rest will follow the pattern.

See the recommended hardware

LET’S START WITH YOUR CONTEXT

Let’s talk about
your plant.

Prepare a summary and bring it to the conversation with Oriol Rius. This form does not send or store any data.

Open contact

Or go straight to Oriol’s calendar ↗