Difference between revisions of "Authority Communication"
| Line 5: | Line 5: | ||
It is a smart data exchange and distribution tool that is intended to simplify and standardize communication with competent authorities (e.g. customs). The broker would be connected to all relevant economic operators (like RUs, IMs or existing data brokers) and competent authorities of EU and associated countries. The focus of the solution is to ensure standardized data exchange without the necessity to generate additional data flows in case such data is already available in an electronic form for other purposes. Therefore, the tool focuses on minimizing excessive data traffic and maximizing data exchange efficiency and consistency. | It is a smart data exchange and distribution tool that is intended to simplify and standardize communication with competent authorities (e.g. customs). The broker would be connected to all relevant economic operators (like RUs, IMs or existing data brokers) and competent authorities of EU and associated countries. The focus of the solution is to ensure standardized data exchange without the necessity to generate additional data flows in case such data is already available in an electronic form for other purposes. Therefore, the tool focuses on minimizing excessive data traffic and maximizing data exchange efficiency and consistency. | ||
The solution consists of the following building blocks: | The solution consists of the following building blocks: | ||
| − | + | #1. Interfaces between the broker and competent authorities that follows the eFTI standards | |
| − | + | #2. Interfaces to all relevant economic operators following an already existing or the eFTI standard | |
3. A smart tool capable of compiling data from available data sources (e.g. Hermes, Orfeus) and structuring it to make it compatible with the eFTI standard. This is a precondition for the usage of interfaces mentioned in point 1. | 3. A smart tool capable of compiling data from available data sources (e.g. Hermes, Orfeus) and structuring it to make it compatible with the eFTI standard. This is a precondition for the usage of interfaces mentioned in point 1. | ||
4. A comprehensive data access module ensuring that only authorized parties have access to the data (in pull queries). In addition, the module must also be capable of identifying the parties that must be informed in case a certain event occurs (push queries). The latter may also be applied as a push query by one party to trigger data exchange with another party (trilateral communication). | 4. A comprehensive data access module ensuring that only authorized parties have access to the data (in pull queries). In addition, the module must also be capable of identifying the parties that must be informed in case a certain event occurs (push queries). The latter may also be applied as a push query by one party to trigger data exchange with another party (trilateral communication). | ||
Revision as of 14:06, 14 April 2021
Description
It is a smart data exchange and distribution tool that is intended to simplify and standardize communication with competent authorities (e.g. customs). The broker would be connected to all relevant economic operators (like RUs, IMs or existing data brokers) and competent authorities of EU and associated countries. The focus of the solution is to ensure standardized data exchange without the necessity to generate additional data flows in case such data is already available in an electronic form for other purposes. Therefore, the tool focuses on minimizing excessive data traffic and maximizing data exchange efficiency and consistency. The solution consists of the following building blocks:
- 1. Interfaces between the broker and competent authorities that follows the eFTI standards
- 2. Interfaces to all relevant economic operators following an already existing or the eFTI standard
3. A smart tool capable of compiling data from available data sources (e.g. Hermes, Orfeus) and structuring it to make it compatible with the eFTI standard. This is a precondition for the usage of interfaces mentioned in point 1. 4. A comprehensive data access module ensuring that only authorized parties have access to the data (in pull queries). In addition, the module must also be capable of identifying the parties that must be informed in case a certain event occurs (push queries). The latter may also be applied as a push query by one party to trigger data exchange with another party (trilateral communication). 5. Storage capability of data received and data communicated for a predefined period 6. An alert module that is capable of identifying critical faults / errors in data and informing the relevant parties.
Use Cases
In the first phase, the following major uses cases have been identified (the list not being exhaustive): • Exchange of RID data about shipments with relevant authorities • Exchange of customs data about shipments with relevant authorities
Preconditions
The tool is usable only in case: • Building blocks 1-5 have been set up • At least those economic operators relevant to accompany a certain shipment are connected • At least one relevant competent authority is fully connected and willing / able to exchange data. Therefore, it is not critical to have all authorities and economic operators connected at once. The tool is already usable in case at least in a certain region or country shipments can be fully handled within the system without the need to keep parallel data flows in operation.
