fdtSERVER

Product role

fdtSERVER provides FDT services through a Web API and serves as a platform-level foundation for legacy FDT migration and compatibility.

Associated solution package: Legacy FDT Migration and Compatibility.

What it is / What it is not

• It is: a platform-layer carrier for FDT compatibility, migration, historical investment protection, and device data services.
• It is not: the public positioning for a device-integration innovation route, nor a tool for promising migration timelines, downtime windows, or rollback results.

User value

The core value of using fdtSERVER is to bring the handover of legacy FDT assets, migration assessment, and Web API service boundaries into an inventoryable, verifiable path, rather than promising a migration result before version, Edition, host, and licensing conditions are confirmed.

For legacy customers, system integrators, and solution teams, this page should help readers determine which questions need to enter the compatibility/migration checklist, which questions must return to the specification or migration assessment, and why migration duration, downtime windows, or rollback results should not be written as product commitments.

Suitable for

• Existing-system customers: need to inventory whether existing FDT / DTM / host assets can be supported.
• System integrators: need to confirm Edition, FDT version, Web API scope, and migration-assessment inputs.
• Pre-sales / solution managers: need to distinguish product capabilities, third-party DTM responsibility, and project migration conclusions.

Typical use cases

• Existing FDT / DTM / Frame assets need to enter migration, upgrade, or compatibility assessment.
• System integrators need to carry FDT service boundaries through Web APIs.
• Solution teams need to confirm product facts, third-party DTM responsibility, and project migration assumptions separately.

Core capabilities

• Edition scope: Standard Edition covers FDT 1.2 / 1.2.1 / 2.0 / 2.1, with FDT 3.0 available as an option.
• Cross-platform scope: Cross-Platform Edition is limited to FDT 3.0 and Linux scenarios adapted for .NET 6.
• Web API objects: Device Catalog, Topology, DTM UI, Static Function, Parameters, and others.

Architecture and integration relationship

fdtSERVER sits at the platform layer of the legacy FDT migration and compatibility path and carries FDT services through Web APIs. It can serve as a technical handle for migration assessment and historical asset protection, but it does not replace the customer's site migration solution, third-party DTM responsibility confirmation, or project plan.

Applicable standards / versions / environment

• Linux-related statements must retain the Cross-Platform Edition, FDT 3.0, and .NET 6 adaptation context.

Out of scope

• Does not promise migration duration, downtime windows, or rollback results.
• Does not assume responsibility for third-party DTM defects, licensing, or certification.

Related solutions

• Legacy FDT Migration and Compatibility
• Cross-Platform Device Management

FAQ / Contact

• FAQ entry: Device Integration FAQ
• Contact entry: arrange an fdtSERVER technical discussion to confirm Edition, FDT version, third-party DTM responsibility, and migration-assessment inputs.

Evidence and resource handoff

• Related solution: Legacy FDT Migration and Compatibility.
• Resource handoff: product specification index, FAQ, PoC Preparation Checklist, and Security Permission Audit guidance.