The framework does not require every possible freight field in every authority interaction. Data subsets represent the regulatory information requirements that apply.
A consignment movement can be associated with multiple applicable subsets. Shared elements should not become duplicated copies of the same business fact.
Adminyra models subset codes separately from payload versions so selection remains explicit.
Authority access can be limited to regulatory information represented by specific subsets rather than exposing an unrestricted shipment record.
That makes data minimisation and auditability part of the platform response model.
No. Subsets describe regulatory information requirements. Authorisation determines who may process or access data.
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.