Product Center Solution Overview
Select by problem domain
Product Center organizes solutions by problem domain instead of presenting every product as a parallel directory. Identify one primary problem first, then enter the matching solution, product page, and resource page.
Solution value
The solution overview helps technical evaluators choose a path before reading an individual product specification: device-management foundation, legacy FDT transition, non-standard device access, or device-driver development and diagnostic reuse.
This page does not replace any individual solution page, product page, or specification. It guides readers from a mixed product landscape to one primary solution package, one main product anchor, and a set of next-step resources.
For capabilities, versions, interfaces, compatibility, performance, or customer outcomes, continue to the applicable solution page, product page, product specification index, or PoC preparation checklist.
Four solution packages
Cross-Platform Device Management
For system suppliers, system integrators, and owner technical teams. Primary product anchor: mmIDM.
Does not cover MES / ERP / EAM / IIoT or general contracting.
View Cross-Platform Device ManagementLegacy FDT Migration and Compatibility
For legacy-system customers and brownfield project teams. Primary product anchor: fdtSERVER.
Does not promise a fixed migration duration, downtime window, or rollback result.
View Legacy FDT Migration and CompatibilityNon-Standard Device Unified Access
For IT/OT architects and teams integrating non-standard devices. Primary product anchor: Unified Device Server.
Does not promise all protocols, all devices, or a future protocol timetable.
View Non-Standard Device Unified AccessDevice Driver Development and Diagnostic Reuse
For device-supplier R&D and driver-maintenance teams. Primary product anchors: fdiDTM, genericDTM, and dtmMANAGER.
Does not cover deep functions of vendor-specific DTMs.
View Device Driver Development and Diagnostic ReuseHow to combine packages
Cross-Platform Device Management can work with Legacy FDT Migration and Compatibility when new or upgraded AMS / IDM capabilities need a legacy-asset transition path. Non-Standard Device Unified Access can work with Device Driver Development and Diagnostic Reuse when protocol access, driver completion, and device-model validation are handled separately.
Use one primary solution package for a customer conversation, then add one supporting package when needed.
Decision stages and next hops
| Decision stage | Reader question | Next hop |
|---|---|---|
| Problem identification | Is device integration relevant to my situation? | Review the DI business overview page. |
| Solution comparison | Which solution package should I review? | Open the Solution Package Selection Guide. |
| Technical evaluation | What are the capabilities, versions, interfaces, and limitations? | Enter the applicable product page and Product Specification Index. |
| Risk review | What should be prepared for compatibility, security, and PoC work? | Review the Resource Center. |