DI Overview
First view
M&M Device Integration helps system suppliers, device suppliers, and system integrators turn device knowledge, device access, diagnostics, topology, and lifecycle data into reviewable and migratable software assets.
This page is for first-time visitors and early solution screening. It does not present complete specifications or promise specific customer outcomes. It helps readers decide which problem domain to enter.
Primary CTA: View the Product Center solution overview.
Secondary CTA: Book a DI business discussion to review current devices, systems, and integration boundaries.
Why device integration is becoming more complex
- Multiple standards coexist: FDT, FDI, EDDL, HART, PROFIBUS, and existing field systems may all be present.
- Legacy assets cannot simply be discarded: DTMs, Frames, engineering configurations, maintenance processes, and user practices usually need migration assessment.
- Non-standard devices continue to appear: protocols, models, and access methods vary by project, so the unified abstraction and plugin boundaries need to be confirmed first.
- Security and responsibility boundaries must be addressed early: when parameter writing, remote access, or Web / API exposure is involved, permissions, audit, certificates, and ownership must be discussed together.
Which problems does M&M DI address?
| Problem domain | Enter the solution package | Product Center handoff |
|---|---|---|
| Need a cross-standard device-management foundation | Cross-Platform Device Management | mmIDM product page, PoC Preparation Checklist, Product Specification Index |
| Need to continue legacy FDT and driver assets | Legacy FDT Migration and Compatibility | fdtSERVER product page, Compatibility / Migration Checklist, DTM asset inventory |
| Need to connect non-standard or protocol-diverse devices | Non-Standard Device Unified Access | Unified Device Server product page, architecture assessment entry |
| Need to develop, convert, or complete driver assets | Device Driver Development and Diagnostic Reuse | fdiDTM, genericDTM, dtmMANAGER, and related product pages |
Quick next-hop guidance by role
| Role | Question to confirm first | Suggested next step |
|---|---|---|
| System supplier | Which device models, interfaces, and security boundaries must the upper-level system support? | Review Cross-Platform Device Management. |
| Device supplier | Should we develop a DTM, reuse a DD / FDI package, or use a generic driver path? | Open the Device Driver Development and Diagnostic Reuse selection guide. |
| System integrator | Are legacy assets, field gateways, versions, and PoC inputs clear? | Download the Compatibility / Migration Checklist. |
| Plant owner / operations | How should current-system responsibility, migration risk, and security auditing be defined? | Review the Security, Permission and Audit guidance. |
Lightweight evidence boundary
M&M Device Integration communicates only within confirmed product facts and solution boundaries: the product anchor for Cross-Platform Device Management is mmIDM; fdtSERVER addresses FDT compatibility and migration; Unified Device Server addresses a unified abstraction layer and device-access services; and driver and tool assets support device access, development, and validation paths.
Applicable / not applicable boundary
This page applies to early understanding and routing for device management, legacy FDT migration, non-standard device access, and driver development and diagnostic reuse. It does not apply to quotations, schedules, customer acceptance, performance commitments, customer case results, or contractual capability confirmation.
Next steps
- View the Product Center solution overview
- Open the Solution Package Selection Guide
- Book a DI business discussion and submit current system boundaries - TBD