Device & Update
Management

IoT device management—also known as IoT Device Management—encompasses the operation of connected devices throughout their entire lifecycle: from planning and provisioning, through configuration and monitoring, to decommissioning. You need it as soon as device fleets grow and connectivity, status, updates, remote maintenance, and compliance cannot be managed manually or through siloed solutions. Typical triggers include rising field service costs, a lack of transparency regarding software versions in the field, regulatory requirements (CRA, NIS2), or the desire to build remote service and predictive maintenance on a robust foundation of device data.

doubleSlash’s integrated IoT solution for managing heterogeneous device fleets –, with update management at its core: OTA campaigns, wave strategy, rollback, and auditable history. Supplemented by device management, remote access, alerting, and compliance—with a centralized, SSO-enabled web interface and integration with popular IoT platforms such as ThingWorx, Azure IoT, AWS IoT, or Mender.io.

A robust management solution for IoT devices combines multiple capabilities into a seamless operation—rather than relying on isolated tools for connectivity, updates, or remote maintenance. Key features include a centralized inventory with software versions, controlled update management with waves and rollbacks, governance-supported remote access, rule-based alerting, and auditable logs for compliance.

With Device & Update Management, doubleSlash focuses precisely on this –—with update management at its core and additional capabilities for end-to-end fleet operations. As a complete solution or as a central control layer spanning existing platforms—technology-agnostic, without rigid vendor lock-in, and proven in practice (including ZEISS with more than 5,000 devices).

Note: “MDM solutions” in the sense of Mobile Device Management for smartphones are a different topic and do not address industrial IoT fleets.

As the number of devices grows, manual processes for updates, monitoring, and remote access can no longer scale –; operational overhead and response times increase disproportionately.

Typical challenges:

• Heterogeneous device types, protocols, and platforms result in siloed solutions and high integration costs.
• Provisioning and onboarding are inconsistent; devices are not put into service consistently or securely.
• Software versions, malfunctions, and patch statuses are not centrally visible.
• Updates cannot be rolled out in waves, targeted to specific user groups, or with rollback capabilities.
• Remote maintenance is either lacking or is insecure and not logged—On-site visits remain expensive.
• Outages and threshold violations are detected too late; there is a lack of escalation procedures.
• Evidence for CRA and NIS2 –—patches, access logs, and software inventory –—is incomplete.

Device & Update Management addresses these scalability issues with standardized processes, centralized control, and predefined use cases instead of individual solutions for each location or device type.

Centralized management creates a “single point of truth” for the entire fleet—across locations, plants, and device types.

Among other benefits, this provides:

• Transparency: Device status, software versions, and campaign progress are traceable at all times.
• Efficiency: Fewer on-site visits thanks to remote support; shorter mean time to repair through targeted alerts.
• Security: Role- and permission-based models, logged access, and signed update artifacts as standard.
• Predictability: Controlled OTA campaigns with target group and compatibility controls –, resulting in a smaller “blast radius” in the event of failed rollouts.
• Compliance: Audit trails and reporting for CRA and NIS2 requirements instead of retroactive documentation.
• Scalability: New devices and locations can be integrated using standardized onboarding and operational processes.

Secure IoT updates are delivered over the air (OTA)—remotely and without on-site intervention—through controlled campaigns: time windows, waves, or pilot groups; target group control based on model, location, or software version; approval workflows; and signature verification of update artifacts. Depending on the device type, software and firmware packages, container images, full-image updates, and delta updates are supported.

Progress and errors are monitored during the rollout; stop and rollback mechanisms are triggered in case of problems. Offline devices buffer updates in a queue and resume the rollout once the connection is restored. Every action is documented—to serve as the basis for audits and CRA/NIS2 compliance documentation.

Device & Update Management consolidates these processes into a single, centralized interface. Existing update backends such as Mender.io, ThingWorx, or Azure IoT are integrated and orchestrated –—not replaced—if they are already in production.

Sessions are established on demand—without permanently open ports on the device. The tunnel initiates from the device; access is time-limited, role-based, and optionally requires explicit operator approval. All sessions are logged and can be exported as an audit report. doubleSlash works with you to select the appropriate technology (WebSocket, VPN, Zero-Trust)—based on device type, network, and compliance requirements.

Microsoft Azure IoT, AWS IoT, PTC ThingWorx, Mender.io, and other systems. Mender.io typically serves as the update backend for the fleet—doubleSlash orchestrates it via the central interface without replacing existing Mender installations. Protocols: MQTT, REST, AMQP, OPC UA, HTTPS, and common OT interfaces. Security: TLS/mTLS, X.509, PKI, OAuth 2.0 / OpenID Connect.

All three models are possible. The architecture is tailored to your specifications regarding data sovereignty, latency, operating model, and regulatory requirements—ranging from fully cloud-based solutions to on-premises setups in your own data center to hybrid configurations with edge and cloud components. During our needs assessment, we’ll determine which model best fits your environment.

Typical approach: A needs assessment, followed by an analysis of the current state and a focused pilot—for example, a single location or 20–50 devices of a single type. Based on this, a roadmap, target architecture, and rollout plan are developed for the rest of the fleet. Using proven solution components, an initial pilot is typically up and running in about 4–6 weeks—and with a narrower scope (one device type, a few dozen devices), often as early as 4 weeks.

In a focused pilot, the first productive results can typically be achieved in about 4 to 6 weeks—and often as early as 4 weeks with streamlined integration and a clearly defined device type. Larger-scale integrations or multiple device types may take 6–8 weeks. The specific timeline is determined during the requirements discussion.

Target State and Architecture for Device & Update Management (including security and compliance), IT Security Concept, Operational Solution for Inventory, Remote Access, OTA Campaigns, and Alerting, Role and Permissions Concept with Processes (Update Approvals, Rollout Windows, Rollback), audit trail and reporting, as well as documentation and enablement for operations and support.

There is no fixed SaaS subscription fee per feature package. The investment is based on project scope, integration effort, and fleet size—either as a fixed price for clearly defined phases (pilot, rollout) or according to an agreed-upon implementation plan. We’ll clarify specific terms during the needs assessment meeting.

Through auditable OTA campaigns, documented remote access, centralized inventory with software versions, rollback mechanisms, and reporting artifacts, doubleSlash provides technical and organizational tools to support evidence management and audit preparation.