mmIDM

Multi-standard device driver management

mmIDM supports these device integration standards and driver access models:

• FDT 1.2.x / FDT 2.x DTM: installed on the server and registered by refreshing the driver list from the client.
• FDT 3.0 DTM: uploaded and installed through the client.
• DD drivers (EDDL / FDI): uploaded and installed through the client.
• Generic DTM: provides basic information access when a device has no standard driver available.

The actual availability of a fieldbus depends on the corresponding DTM / communication driver, field gateway and device conditions.

Topology and device management

mmIDM supports manual topology editing, CSV-based device list import, DCS topology import / synchronization when prerequisites are met, and fieldbus scanning when the protocol and gateway support it.

The system can provide physical topology view, process topology view, device vendor view and custom device list view, so different roles can access device information from the connection, process, device type or watch-list perspective.

Remote configuration, diagnostics and maintenance

With the integrated DTM or device description interface, users can view device parameters and, when permissions, online status and communication conditions are met, perform parameter modification, download, upload backup and batch operations.

The readable, writable, diagnostic and calibration scope depends on the DTM or DD driver provided by the device vendor.

Real-time data and alarm management

mmIDM can collect process values, status and parameter data through configurable polling. The default data collection cycle is 60 seconds and can be adjusted in server configuration.

The system can aggregate device alarms and events, and provides alarm list, severity display, filtering and acknowledgement functions.

Northbound interface and system integration

mmIDM has a built-in OPC UA server. Third-party OPC UA clients can read:

• Device topology.
• Device parameter lists.
• Device status and real-time parameter values.

The OPC UA interface is a read-only data interface. Third-party OPC UA client connection, authentication, field mapping and commissioning are customer-side or project integration activities and should be agreed separately in the technical agreement or SOW.

mmIDM also provides REST API with Swagger / OpenAPI documentation and JWT Bearer Token authentication. SignalR is used for real-time push of topology changes, device status changes, alarm events and system status updates.

Users, security and audit

mmIDM supports multi-user account management and role-based access control. Audit logs cover login / logout, parameter changes, upload / download actions, batch operations, user and role changes, and topology node changes.

Security capabilities include JWT Bearer Token authentication, RBAC, configurable strong password policy, HTTPS / TLS communication, and OPC UA security policies including Basic256Sha256, Aes128_Sha256_RsaOaep and Aes256_Sha256_RsaPss. The OPC UA None policy is recommended only for testing, debugging or controlled intranet environments.

Platform, scale and performance boundaries

Validated environments for mmIDM 1.0.0 include:

• Operating systems: Windows 11 22H2, Ubuntu 22.04 LTS, Kylin V10.
• CPU architectures: x86_64, ARM64, LoongArch.
• Tested CPU models: Intel i7 14700, Phytium D2000, Loongson 3A5000.
• Minimum server memory: 32 GB.
• Recommended storage: NVMe or SSD.
• Recommended network: Gigabit Ethernet.

In the standard test environment (Intel i7 14700, 64 GB RAM, NVMe storage, Gigabit Ethernet, Windows 11 22H2), mmIDM has been verified for up to 20,000 smart devices on a single server. Larger scenarios can be implemented through partitioned deployment or multiple instances and belong to the project implementation scope.

In the same standard test environment, client startup loading time is verified as <= 2 seconds, common operation response time as <= 3 seconds, and OPC UA interface response time as <= 2 seconds. Actual performance depends on hardware, network, device response, polling cycle and data scale.

Prerequisites and customer responsibilities

Before using mmIDM, confirm the following prerequisites:

• A server that meets the hardware requirements and runs a supported operating system.
• Network connectivity among server, field gateways and clients, with required ports allowed by firewalls.
• TLS certificate configuration when HTTPS is required.
• OPC UA PKI certificate trust configuration when OPC UA is enabled.
• For DCS / SIS integration, the DCS / SIS side must provide an FDT-compliant communication DTM or an OPC UA interface specification defined by mmIDM.
• Smart field devices must be connected through gateway or network to the server.
• Device-specific DTM or DD driver files are required. Generic DTM may provide basic access when such drivers are missing, with limited scope.
• Server and client time synchronization is recommended for accurate audit logs and timestamps.