DI Business Overview
Turn fragmented device access, diagnostics, and installed-asset challenges into verifiable software integration paths. System suppliers, device suppliers, and system integrators can start with their main challenge: device management, FDT migration, non-standard access, or driver development.
View the Product Center solution overview
Why device integration is becoming more complex
Multiple standards coexist
FDT, FDI, EDDL, HART, PROFIBUS, and existing field systems may coexist.
Installed assets cannot simply be replaced
DTMs, Frames, engineering configurations, maintenance processes, and user practices usually require a migration assessment.
Non-standard devices keep emerging
Protocols, models, and access methods vary by project; unified abstraction and plugin boundaries must be confirmed first.
Security and responsibility boundaries come first
Parameter writes, remote access, and Web / API exposure require permissions, auditing, certificates, and responsibilities to be discussed together.
Which problems M&M DI addresses
Scroll the table horizontally; focus the table to navigate with arrow keys.
Choose the next step by role
Scroll the table horizontally; focus the table to navigate with arrow keys.
| Role | Questions to confirm first | Suggested next step |
|---|---|---|
| System supplier | Which device models, interfaces, and security boundaries must the upper-layer system support? | View the cross-platform device-management solution |
| Device supplier | Develop a DTM, reuse DD / FDI packages, or use a generic-driver path? | Open the Device Driver Development and Diagnostic Reuse Selection Guide |
| System integrator | Are the installed assets, field gateways, versions, and PoC inputs clear? | Open the Compatibility Migration Checklist |
| Plant owner / operations | How are existing-system responsibilities, migration risks, and security auditing defined? | View Security, Permissions and Audit Notes |
Product responsibilities
M&M Device Integration describes only confirmed product facts and solution boundaries: mmIDM is the product anchor for cross-platform device management; fdtSERVER addresses FDT compatibility and migration; Unified Device Server addresses the unified abstraction layer and device-access services; driver and tool assets complete device-access, development, and validation paths.
The specific available scope of Unified Device Server, basicDTM, dslDTM, dtmINSPECTOR, and legacy compatibility assets must be confirmed individually in technical discussions.
Applicable / out-of-scope boundaries
Applicable to initial understanding and routing for device management, existing FDT migration, non-standard device access, and driver development and diagnostic reuse. Not applicable to quotations, schedules, customer acceptance, performance commitments, customer case results, or confirmation of contractual capabilities.
Next steps
Open the Solution Package Selection Guide | Book a DI business discussion and submit existing-system boundaries | Choose an Entry by Role | Open the Product Center starting page
DI 业务概述
把分散的设备接入、诊断与存量资产问题，梳理为可验证的软件集成路径。面向系统供应商、设备供应商和系统集成商，从设备管理、FDT 迁移、非标接入或驱动开发中选择您的主问题。
为什么设备集成正在变复杂
多标准并存
FDT、FDI、EDDL、HART、PROFIBUS 与现场已有系统可能同时存在。
存量资产不能简单推翻
DTM、Frame、工程配置、维护流程和用户习惯通常需要迁移评估。
非标设备持续出现
协议、模型和访问方式因项目差异而变化，需要先确认统一抽象与插件边界。
安全与责任边界前置
涉及参数写入、远程访问、Web / API 开放时，权限、审计、证书和责任划分必须同步讨论。
M&M DI 解决哪几类问题
表格可横向滚动；聚焦表格后可用方向键查看。
按角色快速判断下一跳
表格可横向滚动；聚焦表格后可用方向键查看。
| 角色 | 先确认的问题 | 建议下一步 |
|---|---|---|
| 系统供应商 | 上层系统要承接哪些设备模型、接口和安全边界 | 查看跨平台设备管理方案 |
| 设备供应商 | 应自研 DTM、复用 DD / FDI 包，还是使用通用驱动路径 | 进入设备驱动开发与诊断复用选型指引 |
| 系统集成商 | 存量资产、现场网关、版本和 PoC 输入是否清楚 | 打开兼容迁移清单 |
| 工厂业主 / 运维 | 现有系统责任边界、迁移风险和安全审计如何定义 | 查看安全、权限与审计说明 |
产品分工
美名设备集成只在已确认的产品事实和方案边界内表达：“跨平台设备管理”的产品锚点为 mmIDM，fdtSERVER 面向 FDT 兼容与迁移，Unified Device Server 面向统一抽象层与设备访问服务，驱动与工具资产用于补齐设备接入、开发和验证路径。
Unified Device Server、basicDTM、dslDTM、dtmINSPECTOR 与遗留兼容资产的具体可用范围需在技术交流中分别确认。
适用 / 不适用边界
适用于设备管理、存量 FDT 迁移、非标设备接入、驱动开发与诊断复用的前期认知和分流。不适用于报价、排期、客户验收、性能承诺、客户案例结果或合同能力项确认。