Solution Selection Guide
Step 1: What is your primary question?
| Your main problem | Solution package | Next hop |
|---|---|---|
| Build or upgrade device management / IDM / AMS capability | Cross-Platform Device Management | View Cross-Platform Device Management |
| Continue, upgrade, or migrate legacy FDT and host assets | Legacy FDT Migration and Compatibility | View Legacy FDT Migration and Compatibility |
| Integrate non-standard, proprietary-protocol, or protocol-heterogeneous devices | Non-Standard Device Access | View Non-Standard Device Access |
| Develop, convert, reuse, or validate device-driver assets | Device Driver Development and Diagnostics Reuse | View Device Driver Development and Diagnostics Reuse |
Step 2: Confirm suitability
Cross-Platform Device Management
Suitable: evaluation of cross-standard device management, northbound interfaces, security and permission boundaries, and OS / CPU boundaries.
Not suitable: one-off project integration, quotations, or end-to-end business systems only.
Legacy FDT Migration and Compatibility
Suitable: existing FDT / DTM / Frame assets that first need inventory and an assessed transition path.
Not suitable: requests for committed fixed downtime windows, rollback outcomes, or migration durations.
Non-Standard Device Access
Suitable: dispersed device protocols, models, or access patterns that require a unified service contract and bounded-scope PoC.
Not suitable: requests to commit to all protocols, all devices, or a future protocol timeline.
Device Driver Development and Diagnostics Reuse
Suitable: reuse of DD / FDI packages, generic DTMs, basic driver coverage, or DTM development toolchains.
Not suitable: replacing deep vendor-specific DTM functions or unconditionally covering all vendor extensions.
Step 3: Common combinations
| Typical scenario | Primary solution package | Supporting solution package |
|---|---|---|
| New device-management capability while retaining legacy assets | Primary: Cross-Platform Device Management | Supporting: Legacy FDT Migration and Compatibility |
| Non-standard device access with insufficient driver assets | Primary: Non-Standard Device Access | Supporting: Device Driver Development and Diagnostics Reuse |
| Device supplier planning a driver delivery path | Primary: Device Driver Development and Diagnostics Reuse | Supporting: Legacy FDT Migration and Compatibility |
| System integrator reducing on-site uncertainty first | Primary: Legacy FDT Migration and Compatibility | Supporting: Non-Standard Device Access |
Next Step