The cleanest eFTI architecture keeps operational planning in the transport management system and moves regulatory interoperability into a dedicated platform boundary.
The detailed platform rules support machine-to-machine business access through other ICT systems acting as tributary systems.
That maps naturally to transport software: the TMS sends and updates freight data while the eFTI platform applies authorisation, CMDS, audit and Gate behaviour.
Shipment creation, assignment, departure and delivery already exist as TMS events. An eFTI connector can map those events to dataset creation and updates without forcing operators into a second workflow.
Source references remain available while the regulated dataset gets its own identity and version history.
The platform model supports controlled edits while preserving the required audit trail and historical values.
No. Adminyra eFTI is under active development. Production authority exchange stays disabled until the required interoperability, conformity-assessment and certification steps are complete.
Yes. Data mapping, sandbox API work, CMDS lifecycle design and application integration can be prepared before production Gate trust is enabled.
Start with a real freight-data mapping in the sandbox. Production Gate exchange remains locked until the certification and interoperability path is complete.