eCMR Indexing Server
Addition Instruction
Development funded by
Diginno-Proto
Version 1.00
1
Prerequisites/Notes
• Admin credentials of Keycloak instance master realm
• Credentials for connecting to the infrastructure of indexing servers
• User links will expire in the end of DIGINNO-Proto on the 15th of September, 2020.
Steps
1. Go to “/etc/docker/deployment/fabric-network/test-network/addCountry”
2. Run “addCountry.sh up -country <two_letter_country_code>” ex.: “addCountry.sh up -country ua”
3. If everything goes successfully, go to “/etc/docker/deployment/fabric-network/scripts/add-country-
scripts” and check if “.tmp” file contains all deployed countries (the file content should look like "lt ee lv
pl ua", if the 'ua' was added as a new indexing server).
4. Open browser and go to “https://sso.playground.ecmr4.eu/auth/”
5. Login with administrator account and create a realm with a name of two letter country code
(lowercased)
6. Go to “/etc/docker/deployment”, open “docker-compose.infra.yml” and update “keycloak” service
with required Traefik variables for newly added realm (you must wait a minute or two until keycloak
instance reacreates)
Figure 1. Update example of 'docker-compose.infra.yml" file
7. Save the updated file and run “docker-compose -f ./docker-compose.infra.yml -p infra up -d”
command
8. Go to “/etc/docker/deployment/fabric-network/scripts” and run command “network.sh deployCC -l
go -v 16 -verbose” (number '16' is chaincode version which should be incremented by one every time
you update chaincode).
2
9. Go to “/etc/docker/deployment” and edit “docker-compose.api.yml” with service for added country
index api (take lt-index-api as example).
10. Then run “docker-compose -f ./docker-compose.api.yml -p api up -d”
11. Go to “/etc/docker/deployment/fabric-network/test-network/api-scripts”
12. Run “node enrollAdmin.js <two_letter_deployed_country_code>” (ex.: ”node enrollAdmin.js pl”)
13. Replace data in countries variable in addOrganizationsToAPI.js file with two letter country code you
just newly added.
14. Run “node addOrganizationsToAPI.js” script and save output ID’s of added organizations and
connection profiles. As an example, from the output bellow, we need to extract these ID’s as they will
be used for user management configuration:
• LV DLT organization ID: 69c0d37c-8f18-4f9f-abe0-5c435fdb1477
• LV DLT connection profile ID: 056c7244-4bb4-4abe-8936-76bcc09a691c
Figure 2. Example output of running 'node addOrganizationsToAPI.js' script
15. Go to https://sso.playground.ecmr4.eu/auth and login with admin credentials.
16. Configure realms you created previously:
16.1. Create a client of with a name of ‘index-api’ and access type set as ‘public’
Figure 3. Client configuration for API layer (1)
3
Figure 4. Client configuration for API layer (2)
16.2. Create an “ecmr_admin” role for country administrators with configuration as shown below
(user with this role will be able to login to administration console and manage users/groups)
Figure 5. Country administrator role configuration
16.3. Create an ‘ecmr-api’ scope
4
Figure 6. 'ecmr-api' client scope creation
16.4. Configure token mappers for ‘ecmr-api’ scope
Figure 7. 'ecmr-api' client scope token mapping configuration
5
Figure 8. 'ecmr-api' client scope token mapping configuration
6
Figure 9. 'ecmr-api' client scope token mapping configuration
7
Figure 10. 'ecmr-api' client scope token mapping configuration
8
Figure 11. 'ecmr-api' client scope token mapping configuration
9
Figure 12. 'ecmr-api' client scope token mapping configuration
10
Figure 13. 'ecmr-api' client scope token mapping configuration
11
Figure 14. 'ecmr-api' client scope token mapping configuration
16.5. Set ‘ecmr-api’ scope as default client scope for created ‘index-api’ client
Figure 15. Setting 'ecmr-api' client scope as default for 'index-api' client
16.6. Create ‘Business’ and ‘Government’
12
Figure 16. Creation of 'Business' and 'Government' groups
16.7. Set attributes for created groups with id’s received from step ‘12’
Figure 17. Attribute configuration for 'Business' group
Figure 18. Attribute configuration for 'Government' group
17. After all steps we completed successfully – you can start using country API.
13
eCMR Pilot
Project Parties
Development funded by
Diginno-Proto
Version 1.00
Contents
1. Developers of the project ....................................................................................................................... 3
2. Parties in project ..................................................................................................................................... 4
1. Developers of the project
Fitek EDI, UAB (LTU) Bunasta (LVA, LTU, POL)
https://www.sis.lt https://www.bunasta.eu
Intepia (EST) PPL 33-35 (UKR)
https://www.intepia.com http://www.ppl33-35.com
2. Parties in project
List of private companies and government institutions who participated in project and testing of
eCMR index registry:
represents
country participant
the sector
Digi Logistikakeskus OÜ
business
https://www.dlk.ee
Ospentos International OÜ
business
https://ospentos.ee
Qstep logiciel OÜ
business
https://qstep.eu
Via 3L OÜ
business
https://via3l.eu
Mobicarnet OÜ
business
https://mobicarnet.eu
Republic of Estonia Road Administration
government
https://www.mnt.ee
Republic of Estonia Tax and Customs Board
government
https://www.emta.ee
Estonian Police and Border Guard Board
in cooperation with SMIT government
https://www.politsei.ee | https://www.smit.ee
ERAA. Association of Estonian International Road Carriers
-
http://www.eraa.ee
PROLOG - Estonian Supply Chain Association
-
https://prolog.ee/
Single Window Initiative Estonia
-
https://singlewindow.ee/
Latvia State Radio and Television Center
government
https://www.lvrtc.lv
Puratos Latvia, SIA
business
http://www.foodlatvia.com/producer/puratos-latvia
Multilog Freight SIA
www.multilog.lv
business
State Revenue Service of Latvia
government
https://www.vid.gov.lv
Ministry of Transport Republic of Latvia
government
https://www.sam.gov.lv
Road Transport Administration
government
http://atd.lv
State Police of Latvia
government
https://www.vp.gov.lv/
Latvian Information and Communications Technology Association
(LIKTA) -
https://likta.lv
Delamode Baltics UAB
business
https://www.delamode-baltics.com/
Parnasas, UAB
https://parnasas.lt/en/home
business
Rhenus Logistics, UAB
https://www.rhenus.com/lt/lt/
business
State Tax Inspectorate Under the Ministry of Finance
of the Republic of Lithuania government
https://www.vmi.lt
Ministry of the Economy and Innovation of the Republic of Lithuania
https://eimin.lrv.lt/en/
government
The Lithuanian National Road Carriers’ Association LINAVA
-
http://www.linava.lt
The Information and Communication Technology (ICT) Industry
Association Infobalt -
https://infobalt.lt
Trans.eu Group S.A.
business
https://www.trans.eu
Bunasta Sp. z o.o.
business
https://www.bunasta.eu/polska/
Frosta Sp.zo.o
business
www.frosta.pl
3Cargo Sp. z o.o. Sp. k.
business
https://www.3cargo.com
National Customs and Tax Administration of Poland
government
https://www.gov.pl/web/national-revenue-administration/about-us
Main Inspectorate of Road Transport of Poland
government
https://gitd.gov.pl
Ministry of Infrastructure of Poland
government
https://www.gov.pl/web/infrastruktura
Zrzeszenie Międzynarodowych Przewoźników Drogowych
-
https://www.zmpd.pl/
Polski Instytut Transportu Drogowego
(Polish Road Transport Institute) -
http://pitd.org.pl
Krajowa Izba Gospodarcza Elektroniki i Telekomunikacji
(Polish Chamber of Commerce for Electronics and Telecommunications) -
https://kigeit.org.pl
Testing Loads for Transit
Development funded by
Diginno-Proto
Version 1.00
LOADS FOR TRANSIT
for testing Diginno-Proto eCMR indexing registry
Active Active EDI
Status Truck plate nr Trailer plate nr Origin Destination eCMR issuer eCMR index ID
from until provider
LIVE WORK 10 Sep 10 Sep LV KB3454 LV P3372 Latvia Pure Estonia Jõhvi Latvia Multilog Freight iso6523-actorid-
NEW 9:00 16:00 SIA upis:0189:40103743254-LV-
0032247
iso6523-actorid-
upis:0189:40103743254-LV-
0032248
LIVE WORK 2 Sep 4 Sep PL WOS29TK PL WOS31TK Poland Ujazd Estonia Tallinn Estonia // MobiCarnet one CMR
NEW! 14:00 14:00 logiXdigi
LIVE WORK 2 Sep 3 Sep EE 021BGH EE 993YLH Estonia Tallinn Lithuania Vilnius Estonia // qStep/Ospentos several CMRs
NEW! 14:00 12:00 logiXdigi
LIVE WORK 3 Sep 4 Sep LT CRM952 LT NG073 Latvia Riga Lithuania Vilnius Latvia Arfi Line, SIA iso6523-actorid-
19:55 8:00 upis:0189:40003894310-LV-
114537
LIVE WORK 4 Sep 7 Sep PL BGR09249 PL BGR9P50 Poland Olawa Lithuania Kaunas Poland Essity Poland Sp. iso6523-actorid-
18:00 8:00 z o.o upis:0189:146234897-PL-
1418987
LIVE WORK 8 Sep 9 Sep PL WZ3979V PL WMA77FK Poland CZECHOWICE- Lithuania Vilnius Poland HUNTER iso6523-actorid-
8:00 10:00 DZIEDZICE DOUGLAS upis:0189:010391180-PL-
POLSKA SP. Z 08092020
O.O.
LIVE WORK 7 Sep 8 Sep LV LDR398 LT MV580 Poland Bydgoszcz/Poland Latvia Riga Poland FRoSTA Sp.z o.o. iso6523-actorid-
8:00 16:00 upis:0189:013215466-PL-
321379265
LIVE WORK 9 Sep LV KB3454 LV P3372 Latvia Pure, Tukuma Estonia Viljandi Latvia Multilog Freight iso6523-actorid-
8:00 nuovads SIA upis:0189:40103743254-LV-
0032247
iso6523-actorid-
upis:0189:40103743254-LV-
003224
26 Aug 27 Aug LT JEM995 LT FH678 Lithuania Vilnius Latvia Rezekne Fitek EDI RHENUS 0200-120145513-0001-
16:00 16:00 Logistics 2020825-1285642
0200-120145513-0001-
2020826-1286480
0200-120145513-0001-
2020826-1286493
FINISHED
0200-120145513-0001-
LIVE WORK
2020826-1286528
and still visible
0200-120145513-4213-
2020824-1285029
0200-120145513-4213-202085-
1276502
LIVE WORK 27 Aug 28 Aug EE 133MLZ EE 906YKC Estonia Tallinn Lithuania Vilnius logiXdigi MobiCarnet one CMR
11:30 12:00
14. 15 aug EE 660TMN EE 99QI Estonia Tallinn Lithuania Sausiai - Intepia 0191:125677598-
LIVE WORK Aug 2020. PbKxCIAXUZgx
finished 2020
0191:11306955-Asdasdasd2AS
LIVE WORK 27 Aug 28 Aug EE 660TMN EE 646YLJ Finland Vantaa Latvia Riga logiXdigi qStep several CMRs
finished 14:00 13:00
LIVE WORK 27 Aug 29 Aug EE 529MSP EE 597YHD Lithuania Estonia logiXdigi qStep several CMRs
finished 18:40 14:00
16. 15. EE 981ZKU EE EX654 Estonia Tallinn Lithuania Sausiai - Intepia iso6523-actorid-
Aug sept upis:0191:11306955-
TEST DATA 2020 2020 zebxjMc2JAC0
0191:11306955-
QsfsdMc2JACG1
TEST DATA 15. 15. LV BT5897 LV 258QR Latvia Mārupe Poland Jawczyce - Intepia 0189:40103116320-
Aug sept SIASDASFiasd2
2020 2020
TEST DATA 15. 15. LT 981ZKU LT EX654 Lithuania Vilnius Estonia Lehmja - Intepia 0200:300569015-QRDasdAS3
Aug sept
2020 2020
TEST DATA 19 Aug 15 Sept EE 934YKC Lithuania Finland logiXdigi MobiCarnet 0191:14979341-CMR169814
2020 2020 EE 240BSJ
TEST DATA 18 Aug 15 Sept EE 592MSP EE 597YHD Lithuania Estonia logiXdigi Ospentos iso6523-actorid-
2020 2020 upis:0191:14979341-AH17453
TEST DATA 17 Aug 15 Sept EE 306TNN EE 621YKV Finland Lithuania logiXdigi Ospentos 0191:14979341-AH17508
2020 2020
TEST DATA 19 Aug 15 Sept EE 592MSP EE 597YHD Latvia Finland logiXdigi Ospentos 0191:14979341-AH17579
2020 2020
TEST DATA, 18 Aug 15 Sept EE 660TMN EE 489DP FInland Estonia logiXdigi Ospentos 0191:14979341-AH17552
now removed as 2020 2020
per truck
appearing several
times
TEST DATA 17 Aug 15 Sept EE 707MKT - Estonia Lithuania logiXdigi MobiCarnet 0191:14979341-CMR169819
2020 2020
TEST DATA 17 Aug 15 Sept EE 449HJX EE OV267 Lithuania Estonia logiXdigi MobiCarnet 0191:14979341-CMR169821
2020 2020
VIRTUAL TEST 24 Aug 15 Sept SE KB6210 SE 94571 Sweden Lithuania Kaunas Fitek EDI Brother Nordic 0007_54034628_1285089
2020 2020
VIRTUAL TEST 24 Aug 15 Sept EE KB9710 EE 94571 Estonia Lithuania Kaunas Fitek EDI Magnum 0191_10007517_1285805
2020 2020 Veterenaaria AS
VIRTUAL TEST 21 Aug 15 Sept LT KBG210 LT GU571 Lithuania Estonia Fitek EDI UAB Vilpros 0200_126310441_1283546
2020 2020 Pramone
VIRTUAL TEST 20 Aug 15 Sept LT LFM767 LT LO273 Latvia Lithuania Fitek EDI KOMFOVENT 0201_40103817958_1283539
2020 2020 SIA
VIRTUAL TEST 19 Aug 15 Sept LT KEO294 Lithuania Latvia Fitek EDI UAB Ovalda 0201_53603021711_1284011
2020 2020
VIRTUAL TEST 24 Aug 15 Sept LT LIM767 LT KO273 Lithuania Lithuania Fitek EDI UAB SOMLITA 0200_122903266_1283838
2020 2020
VIRTUAL TEST 24 Aug 15 Sept LT GCG165 LT FK683 Estonia Estonia Fitek EDI OUE ISIS 0191_301012_1284663
2020 2020 MEDICAL
Final Report
eCMR index registry prototype
Development under DIGINNO-Proto project
(public procurement no. 218902 “eCMR prototype development and testing”)
Funded by Nordic Council of Ministers
Prototype ordered by Estonian Ministry of Economic Affairs and Communications
and developed by FITEK EDI, UAB.
September 2020
Authors of the final report and annexes:
Dainius Berskys (Bunasta), Edmundas Daukantas (Lineka), Dmytro Iakymenkov (PPL
33-35 Ltd), Greta Gelgotaitė (Fitek EDI), Riho Vedler (Intepia), Rišardas Bedulskis
(Fitek EDI), Titas Petravičius (Fitek EDI)
Editors of final report:
Edvards Kreišmanis (LVRTC), Eva Killar (MKM), Heiti Mering (Digilogistika Keskus),
Inna Nosach (MKM), Ulrika Hurt (Digilogistika Keskus)
Copyright (c) 2020 by DIGINNO-Proto
2
Contents
Executive Summary 4
Abbreviations and Definitions 6
Project context 8
Project focus 8
Review on the current situation 10
DIGINNO project 10
DIGINNO-Proto and activities timeline 11
Tender for Prototype development 12
Scope of the proto development project 12
Project plan and activities 14
Testing details 18
Results of testing 19
Prototype’s technical details 22
Performance of DLT system in eCMR showcase 25
Advisory Board meetings during the project 25
Expectations and recommendations for further steps 27
Relevant projects/ongoing initiatives 30
List of annexes and work documents 33
Useful links 35
3
Executive Summary
This report summarizes the eCMR prototype development activities carried out between
stakeholders of Estonia, Latvia. Lithuania and Poland under the development of the prototype
contract (Tender nr 218902) with the wider DIGINNO-Proto project coordinated by the Estonian
Ministry of Economic Affairs and Communications.
The main topics covered in the report are the overview of the context of the prototype development
- DIGINNO-Proto project scope and details - and the details on the development of eCMR index
registry and its testing process, review of testing results and analysis of participants’ reviews. As
well as selected feedback and initial recommendations for the next steps.
Prototype development project:
Development tender nr Tender nr 218902 as of 10 February 2020, deadline 10 March
and reference 2020. “eCMR prototype development and testing”
https://riigihanked.riik.ee/rhr-web/#/procurement/1642150/general-info
Contract period: 15.04.2020 - 15.09.2020
Contractual developer of Fitek EDI, UAB (Lithuania) www.sis.lt
the prototype: Rišardas Bedulskis
(
[email protected], ph. +37068711072)
Greta Gelgotaitė
(
[email protected], ph. +370 682 55843)
Framework project information:
Project name: DIGINNO-Proto
(prototyping DIGINNO cross-border e-service show-case)
Project number: 18266
Project period: July 2019 - December 2020
Funded by: Nordic Council of Ministers
Total budget: EUR 134 000
Lead partner: Republic of Estonia Ministry of Economic Affairs and
Communications (MKM) www.mkm.ee
Inna Nosach
(
[email protected], ph. +372 6256335)
4
Eva Killar
(
[email protected], ph. +372 6256485)
Partner countries: Estonia, Latvia, Lithuania, Poland
Project coordinators by ● (Latvia) Latvian Information and Communication
country: Technology Association (LIKTA) likta.lv
● (Lithuania) Lithuanian Information and
Communication Technology Association (INFOBALT)
infobalt.lt
● (Poland) Polish Chamber of Commerce for Electronics
and Telecommunications (KIGEIT) kigeit.org.pl
● (Estonia) Digilogistika Keskus www.dlk.ee
Project web page: https://www.diginnobsr.eu/diginno-proto
5
Abbreviations and Definitions
AWB An air waybill or air consignment note is a receipt issued by an
international airline for goods and an evidence of the contract of
carriage, it is a document of title to the goods.
BOL A transport document for sea freight.
B2B Business to Business.
B2G Business to Government.
DLT Distributed Ledger Technology.
Distributed ledger Database that is consensually shared and synchronized across
technology multiple sites, institutions, or geographies, accessible by multiple
people. The participant at each node of the network can access the
recordings shared across that network and can own an identical
copy of it. There is no central administrator.
EBSI European Blockchain Services Infrastructure.
eCMR An electronic version of the consignment note used under the CMR
Convention when transporting goods by road.
eCMR index registry Servers exchange eCMR index(es) info on cross border level.
eFTI European Union Regulation on Electronic Freight Transport
Information.
EDI Electronic Data Interchange.
EDI provider A service provider who handles electronic (incl eCMR) documents
and takes care of digital info and documents exchange between
driver and logistics manager. EDI provider also exchanges
metadata info with the national eCMR index registry.
GUI Graphical user interfaces.
Haulier A person or company employed in the transport of goods or
materials by road.
6
MMT Multimodal transport.
Multimodal transport Combination of at least two or more different modes of transport
(railer, road, sea, air) to move cargo from one location to another,
may be within one country or between several countries.
Semi-trailer A trailer having wheels at the back but supported at the front by a
towing vehicle.
Trailer An unpowered vehicle towed by another.
UN/CEFACT The United Nations Centre for Trade Facilitation and Electronic
Business.
Warehouse A location where raw materials or manufactured goods may be
stored prior to their distribution for sale or further transportation.
7
1. Project context
1.1. Project focus
The project focused on digitalization of road transport document CMR.
Schema: Life cycle of moving goods (Source: UN/CEFACT)
1.2. Review on the current situation
Compared to 2005, the total freight transport activity in the European Union is expected to increase
by 40% in 2030 and by little over 80% by 2050. 1 Currently, the movement of goods within the
EU is accompanied by the exchange of a large amount of information between the relevant parties
both in the public and in private sector. Unfortunately, this information exchanged on paper in
almost 99% of the cases that involve cross- border shipments in Europe.2
The handling of paper-based documents creates a significant administrative burden on the
companies and officials involved with transport documents in the freight transport industry. By
making the documents digital it could significantly increase transport efficiency and thus,
contribute to the smooth functioning of the European Single Market which seeks to guarantee the
1
European Commission, Transport 2050: The major challenges, the key measures, 28.03.2011. Retrieved 26.08.2019
2
European Commission, Proposal for a Regulation of the European Parliament and of the Council on electronic
freight transport information, 2018. Retrieved 26.08.2019.
8
free movement of goods and services within the European Union.3
The advantages of using electronic freight documents are many, both for carriers, shippers,
especially SMEs and public authorities. It will allow a regional shift from paper to electronic
documents – an opportunity for both businesses and authorities to gain efficiency and transparency
through digitalization. It will enable businesses to manage their information and supply chain more
effectively: optimize the processes, exchange resources, and integrate activities into a single
network of information systems. It will also improve the data quality in the freight process,
reducing the risk of recurring errors.
At the time of the project, electronic documents are partially accepted by national public authorities
and eCMR is by law accepted in several EU member states, but there is no commonly agreed way
of transferring electronic transport data across borders. SMEs stick to paper documents and there
is a lack of universal, across EU borders, agreed rules and interoperable technical means which
SME’s could easily use to exchange information electronically.
As to the legislative context for digitalization of CMRs, the reporting of transport data to
authorities across Europe is addressed by the work of the European Commission and its expert
group Digital Transport and Logistics Forum. During the time of the Diginno Project, the relevant
Regulation has first been proposed as a Regulation (in 2018) and at the time of the implementation
of the DIGINNO-Proto Project, it has been adopted as a Regulation - to eFTI Regulation
2020/1056(EU) (2020) in the Official Journal of the European Union (https://eur-
lex.europa.eu/eli/reg/2020/1056/oj).
“It's official! The eFTI Regulation has now been published in the EU Official Journal and
will start life as a EU law on 20 August 2020 as Regulation (EU) 2020/1056 of the
European Parliament and of the Council of 15 July 2020 on electronic freight transport
information. When it will start applying as of August 2024, it will provide the framework
for safe, secure and fully interoperable exchange of information between business and
authorities on the movement of goods in the EU. It will allow the economic operators to
record the cargo transport information only once, on an eFTI-certified platform of their
choice, and share it electronically with the competent authorities in any EU Member State,
and with their business partners, anytime, anywhere.”
Lia Potec, policy officer of European Commission (LinkedIn, 22.08.2020)
responsible officer for the eFTI Regulation
3
European Commission, The European Single Market. Retrieved 26.08.2019.
9
1.3. DIGINNO project
DIGINNO project (https://www.diginnobsr.eu) helps speed up the Baltic Sea region’s transition
to a single digital market by covering three common challenges: uptake of information and
communication technologies in the business sector, innovation and interoperability of public
services, and cooperation and coordination of digital policies on the macro-regional level.
These challenges can be tackled through strengthening the macro-regional knowledge base (e.g
information sharing, studies), exchange of experience and mutual learning, designing and piloting
transnational digital solutions, conducting policy and regulatory dialog.
The aim DIGINNO Work Package 3 (WP3) was increase the capacity and raise awareness of
public institutions, organizations and businesses in developing G2B digital cross-border (CB)
services, promote transnational collaboration by building G2B services digitalization network and
community, raising knowledge and awareness of success cases, developed show-cases,
opportunities and benefits.
The main output for WP3 was 4 show-case models of G2B cross-border e-services (incl. feasibility
analyses and proofs of concept). These show-case models are practical tools for G2B services
development, helping relevant public institutions to realize the opportunities of digitalization and
understand its possible benefits.
DIGINNO project partners have chosen to focus on the following topics to develop further:
❖ cross-border eCMR - Paperless consignment notes in road transport, recognized by
responsible institutions and used by businesses
❖ cross-border online business registration with Integrated eIDAS Framework
❖ cross-border remote Know-Your-Customer processes with eIDAS application
❖ cross-border eReceipt application
10
1.4. DIGINNO-Proto and activities timeline
DIGINNO-Proto project is supporting and continuing the project DIGINNO activities.
The work done in DIGINNO does not cover practical testing of proposed solutions of the 4 cross-
border show-cases, which were considered a key element to realize cross-border services.
DIGINNO-Proto project aimed to demonstrate through prototyping one of these showcases what
are the real-life shortcomings and necessary changes, to realize the Digital Single Market, where
citizens and entrepreneurs can seamlessly move across borders digitally.
The project was guided by a Steering Committee consisting of Lead Partner and representatives of
DIGINNO WP3 Lead (INFOBALT) and WP4 Lead (Aalborg University Copenhagen).
DIGINNO-Proto project goal was to develop at least one working prototype of a cross-
border e-service based on a showcase developed in the DIGINNO project.
For this purpose, DIGINNO-Proto:
❖ Conducted a call for proposals and received two applications from e-CMR and KYC.
❖ By the end of the evaluation process, the e-CMR prototype was selected for development.
Timeline of the DIGINNO-Proto project:
Date Activity
01.07.2019 Project management has started
30.09.2019 Applications are submitted for evaluation
31.10.2019 eCMR prototype is chosen for further development
15.01.2020 Tender drafting with partners
10.02.2020 International public procurement started
10.03.2020 Public procurement ended, partner for development is found
15.04.2020 The contract is signed with FITEK EDI, UAB
11
15.09.2020 The prototype is ready
31.12.2020 Outcomes are introduced to partners, reporting is done, the project is
ended.
2. Tender for Prototype development
Procurement for the eCMR prototype was initiated by Estonian Ministry of Economic Affairs and
Communications on 10th of February 2020 and the deadline for submitting the tenders was 10th
of March 2020. The public procurement was carried out electronically at www.riigihanked.riik.ee
as an international public procurement process.
Three tenders were received: FITEK EDI, UAB (Lithuania), Waybiller OÜ (Estonia) and Catapult
Labs OÜ (Estonia). FITEK EDI has received the most points during the evaluation and, as a result,
a contract for eCMR prototype development and testing was concluded with the Lithuanian
company FITEK EDI who is also known for its e-invoicing solutions.
Tender reference: 218902, “eCMR prototype development and testing”
Tender link: https://riigihanked.riik.ee/rhr-web/#/procurement/1642150/general-info
2.1. Scope of the proto development project
A common international eCMR indexing scheme was proposed to be developed and prototyped
between partner countries: Estonia, Latvia, Lithuania and Poland.
The prototype involved the digital availability of a CMR document (preferred machine-readable)
and a mechanism of indexing the availability of such documents across the partner countries via
an indexing scheme.UN
The system is focused on business to government (B2G) information exchange by using indexing
service and the indexing number. The appointed government institutions (see attachment no. 6
“Project parties”) and controlling institutions of the involved country will be able to see where the
eCMR is stored and receive agreed available data (see attachment no. 3 “eCMR business processes
and technical decisions” for the semantic and syntax models). The developed system will help to
12
share and control data in a decentralized infrastructure that ensures high security, data
immutability, transaction transparency and no single central point of control. All system
development decisions are based on EU standards and UN/CEFACT best practices.
Schema: Estonia example of eCMR index registry working scheme. /CEFACT
E-government compatible distributed approach with application programming interface (API)
accesses was deployed, using distributed ledger technology (DLT) approach. Every authorized
governmental institution was able to access minimum available indexing information via
specialized API and get a link to request original documents relevant data directory from eCMR
service from the county of origin. Additionally, out of the scope of the project, GUI (graphical
user interface) that has ensured smooth user experience was developed.
The scope of the project was to build an expanded index and search system that would help to
navigate and control data in centralized or decentralized networks at the highest security level.
eCMR documents distributed index and search engine had to be a system where there is no
central server, but at the same time allows sharing necessary data according to various roles
and access rights. Unlike traditional centralized search engines, work such as crawling, data
mining, indexing, and query processing is distributed among several peers in a decentralized
manner where there is no single point of control.
13
The solution needed to support a paperless logistics ecosystem in the best possible way. The
focus was on international road transport, but it could be expanded to the sea, train, plane or
multimodal transport in later phases. Also must be possible to organize data exchange for all parties
in the process - B2B, G2G, G2B.
Requirements to the development:
1. Connected eCMR index registers on based DLT technology
a. Connected registers installed to Estonia, Latvia, Lithuania and Poland
2. API defined with a minimum set of data fields to exchange info between EDI provider and
eCMR index registry
a. document the result
3. Possible to make a search by vehicle plate number and by eCMR index ID number
4. Possible to see history:
a. who created, viewed or updated info in registers connected with every index ID
b. look what changes have been done during index ID lifecycle
5. Possible to control rights in the system based on user groups
6. Prototype documentation created and examples made on how to exchange information
between parties
7. Testing the prototype in a real-life environment
3. Project plan and activities
4.1. Start of the prototyping
The signing of the agreement between Republic of Estonia Ministry of Economic Affairs
and Communications and Fitek EDI, UAB.
TIME SCHEDULE: 15.04.2020
4.2. Evaluation requirement
Gathering the requirements of all parties involved in the project:
1) communication with government institution representatives from Poland,
Lithuania, Latvia, Estonia;
2) Creation and alignment of the semantic data model;
14
3) Alignment of other technical and functional requirements for the index server.
TIME SCHEDULE: 15.04.2020 – 08.05.2020
4.3. Building system architecture
1. The cross-border eCMR indexing development scheme plan;
2. Preparation of syntax;
3. Preparation of blockchain (DLT) network architecture.
TIME SCHEDULE: 23.04.2020 – 08.05.2020
4.4. Technical decisions alignment
Meetings with the advisory board (to be described in section no. 25 “Advisory Board”).
TIME SCHEDULE: 22.05.2020 – 11.09.2020
4.5. Development of core solution
The solution that enables eCMR index exchange between foreign Governmental
institutions (Government to Government - G2G) following the national eGovernance and
European Interoperability Framework principles was developed in these steps:
1) Preparation of the infrastructure
2) Deployment of indexing servers for initial testing
3) Configuration of indexing servers
4) Development of Smart Contract based on the semantic model
TIME SCHEDULE: 23.04.2020 – 08.05.2020
4.6. Development of API to the core solution
Application Programming Interface (API) layer development:
1) Index API development
2) Fabric Rest API development
3) Organization API development
TIME SCHEDULE: 18.05.2020 – 12.06.2020
15
4.7. Aligning the requirements of different parties
During this step of the project an intensive communication with project parties has been
carried out:
1) communication with government institution representatives from Poland,
Lithuania, Latvia, Estonia;
2) weekly meetings with project coordinators Ministry of Economic Affairs and
Communications (Republic of Estonia);
3) communication with business companies (hauliers, EDI providers) that are willing
to participate in the testing phase;
4) consulting project parties on the technical preparation for the testing.
TIME SCHEDULE: 15.06.2020 – 10.07.2020
4.8. Deployment
Deployment of indexing and query services and APIs:
1) Deployment of production indexing servers
2) Development and configuration of user management solution
3) Deployment of the API layer
TIME SCHEDULE: 13.07.2020 – 31.07.2020
4.9. Testing in a real environment (demonstration of the working prototype)
The main output of the eCMR prototype during the testing phase was enabling controlling
institutions to check the availability of CMR transport documents of the foreign carriers driving
through their territory in a secure and trustable way.
ESTONIA
In Estonia was carried out by the governmental institutions: Estonian Tax and Customs
Board (EMTA), Estonian Police and Border Guard Board (in cooperation with SMIT) and
Estonian Road Administration (MNT). The exchange of information and data between the
public and private sectors during testing and the arrangement of roadside test days in
Estonia was coordinated by Digilogistika Keskus OÜ - both data merger/gateway as well
as Estonian hub for the index. Digilogistika Keskus also arranged a testing welcome page
and UI gateway on its website: https://www.logixdigi.eu/proto. Estonian actions were
16
coordinated in partnership with Single Window Initiative Estonia and Prolog - Estonian
Supply Chain Association.
Testing was carried out in cooperation with above mentioned governmental institutions
together with private sector eCMR services and EDI providers companies Q-step Logiciel
OÜ and Mobicarnet OÜ, interlinked to the indexing service by data service platform
LogiXDigi. The key partners in testing from the transport sector were Ospentos
International OÜ (EDI provider Q-step Logiciel OÜ) and VIA3L (EDI provider
Mobicarnet OÜ) along with its supply chain partners.
Testing of eCMR index registry prototype in Estonia started on 14th August 2020 with
virtual testing in Estonia. Live testing took place between 24th of August and 4th of
September 2020. On selected sample dates, Tax and Customs Board as well as Police and
Border Guard Board participated in both test stopping of the sample trucks and checking
of the paper documents as well as comparing the available data online both on spot and
from distance in the offices. On 27th of August, the test took place on the transit region of
the Baltic trade in Pärnu and Uulu (Pärnumaa border region) and on 2nd of September, the
test took place with the Tallinn region offices.
Test with following the vehicle and using the roadside cameras as well as the border camera
was tested on the 27th of August. On the 8th of September, a dedicated additional test
session took place with the Road Administration.
The testing was accompanied with press releases and covered by both written media
(articles published on 28th of August as well as TV show aired on 13th of September).
LATVIA
Real environment testing in Latvia was carried out on the 3rd of September, 2020. The
truck was loaded in Riga (Latvia) and moved to Vilnius (Lithuania). Roadside checks did
not take place in Latvia, but the eCMR documents were checked by Latvia’s controlling
agencies virtually.
LITHUANIA
The second step of the testing was organized in a real environment with the load of the
truck in Lithuania. The real test in Lithuania was carried out on the 26th of August 2020.
The truck loaded in Vilnius and headed to Riga (Latvia). In Lithuania, the truck’s eCMR
17
documents were submitted by business and checked on the road by tax authority and
customs.
POLAND
Testing was in Poland on the 7th and 8th of September, 2020. Trucks were loaded in
Czechowice-Dziedzice and Bydgoszcz (Poland) and moved to Vilnius (Lithuania) and
Riga (Latvia). Trucks´ eCMRs were checked on the road by the Road Transport Inspection
of Poland.
Virtual testing of the trucks from Lithuania to Latvia was carried out until the 15th of
September. Government institutions, interested in eCMR, were able to check the eCMR
documents of real trucks in the index register.
TIME SCHEDULE: 14.08.2020 – 09.09.2020
4.10. Preparation of documentation
Preparation of the final report and its procedural and technical annexes (annexes have
been preparing for the whole project time).
TIME SCHEDULE: 31.08.2020 – 11.09.2020
4.11. End of the Prototyping
Signing the final act of compliance.
TIME SCHEDULE: 14.09.2020 – 15.09.2020
4. Testing details
Testing arrangement:
● Each participating country dedicated a Country Project Manager as well as Technical
Manager to support the testing.
● Each participating country arranged test rides to be uploaded and indexed for every testing
participant.
Information exchange in testing:
● The training was done in Estonia, Latvia, Lithuania and Poland for test managers/country
coordinators on how to use the created solution (API, administration module).
18
● Information on virtual and real loads between partners participating in testing shared on
Google Sheets (Attachment no. 7 “Testing Loads for Transit”).
● To speed up the exchange of information, information on the movement of goods was also
shared by e-mail to project and technical managers in every country.
● Testing was performed behind remotely from offices and as a roadside check.
● Once the testing was done, participants were to complete a questionnaire (online formular).
● Several participants preferred to give their feedback directly to the testing managers at the
time of testing.
Media and press releases:
● Testing initiation was covered by press releases and attention of media was drawn to the
importance of the matter as well as the matter of the cross-border cooperation in this matter.
● In Estonia, the Ministry of Economic Affairs and Communications issued a press release
(follow via https://bit.ly/indextesting2020) and collected both coverages in online news
portals, a dedicated article in a daily newspaper and a section in a dedicated TV show.
File types and APIs:
● During the testing, the partners and EDI providers collected and indexed various types of
files - whilst the XML was preferred, also PDF, JPG and Excel were uploaded and indexed.
In that case, all Estonian presented test rides were accompanied with machine-readable
files compatible for e-governance digital reporting.
5. Results of testing
● All functionality and data exchange worked successfully in national and cross-border level
● Truck companies in cooperation with EDI providers shared two formats of documents
through eCMR index registry:
○ Structured CMR document in format XML by UN/CEFACT
○ CMR document in format PDF
● In visual control PDF files are enough, but in the near future control institutions wait for
all data inside the CRM document to be machine-readable (this enables the use of modern
analytical tools based on risk patterns).
19
Generic summary of the testing participants’ survey:
In the online survey, provided for the testing participants after the testing phase, 8 respondents
have participated. 5 of the respondents were representing Customs and/or Tax Agency, 2 was
representing other Government offices and 1 was representing Police and/or Border Agency. 5
respondents had participated in the testing from offices' (virtually), 3 respondents had participated
in the real testing on the road.
Despite the number of respondents being low, the results reflect the fact that data both via the
index and behind the provided URL was available (6 out of 8 responses) and only in few cases the
data on the indicated truck plate number was not available.
Five respondents have evaluated eCMR data online for maximum points 7/7, 3 respondents have
evaluated the importance to have eCMR data online 6/7 points, so this means, that eCMR Index
Registry prototype is valuable for controlling institutions and business entities that are connected
to logistics' environment activities. Comments, provided by the participants of the survey:
"In my opinion, it's a very good solution, as a customs worker I can see what is loaded and
consider it in my work decisions."
"I have some feedback (it's related only to my UX ideals, but maybe it will be useful): I work
"on-road" and I use a relatively low-resolution laptop. On the road, there are two main
important aspects: fast information gathering (faster is better) and usability with the ability
to make a mistake. In my opinion, it is good to programmatically strip spaces in "Truck
Registration Number" at Find Index Search Form. Currently "59 2MSP " is not treated as
"592MSP" or "592 MSP".
Error messages as the modal window are not good, cause as a user you lose time to close
these pop-ups. In my opinion, a better solution is an additional info div on top. For faster
input, some things like "Transport Country Code" is set default by user (browser) location -
then I do not need to waste time on selecting it. It's good if "Truck Registration Number" is
on focus after page loading - then I can start input as fast as form loaded, not need to select
it with a touchpad. The main value of this system is the CMR document - therefore I think
this (CMR) must be first what you see after the search, but licence plate number must be
before it and larger (then I can confirm that I input correctly). Link on the CMR document
can be duplicated as a button with the text "View CMR". I understand that documents stored
not in this system, but some dynamic viewers are very welcome (here modal window is very
ok) - it's a better solution than new window or download (cause it takes time). In conclusion,
more important and valuable data must be first, controls elements need to be easily
distingable - think about time and minimum movements on touchpad or keyboard." (Note:
this comment is connected with the out-of-scope result - prototype GUI).
20
In roadside and office users direct spoken feedback, the respondents and test participants
underlined the importance and usefulness of such a solution, the visibility and greeted the
opportunity to check the CMR contents without stopping the truck as well as check the
documentation from distance or from offices.
Responses of roadside and office testing feedback.
“I understand that there is a need for long history reports, but in the history view the system
should allow me to quickly distinguish between the actions taken by the CMR provider
(upload or change) and the checking views by other testers or users.”
“I like that I can take the CMR data from my office and calmly check the content as it is
convenient for me, while not letting the driver wait. We would also like to check those that
need checking”
A high number of suggestions has been collected in terms of functioning and user interfaces of
such solutions in the future. From search tools, visuals to the sequence of the listings or data to be
highlighted, the officials and test partners gave input for further development.
For example, a suggestion while the eFTI Regulation implementation guides are not fully agreed
is to mark vehicles with special signs and tags.
Picture: Possible visual solution on how to mark trucks and trailers on the road equipped with electronic documents
in a transitional period.
21
6. Prototype’s technical details
The developed solution supports the following functionality:
● Adding or updating the eCMR index(es)
● Making search by vehicle plate number or by eCMR index ID
● Possibility to see who and when (date/time) added or updated the index
● Possibility to follow who has viewed eCMR index (certificates)
● The system works with both - a single truck with loading place and a truck train
● User rights based on two groups: “government” and “business”
○ The created system allows very easy to add extra groups or remove them from the
registry if required
● All functionality and data exchange works at national and cross-border level
During the project the information exchange between parties has been developed as follows:
Schema: Adding transport electronic documents to national eCMR index registry.
22
Schema: The process of information exchange between parties.
Schema. Country EDI provider exchanges information with the national eCMR index registry over the API.
23
Schema. The index registries exchange data with each other using DLT technology.
Schema: Exchange of information then controlling institutions use cameras on the road.
Implementation of this project marks a significant step towards the EU Single Digital Market and
gives input for solving the existing problem related to the lack of digitalization within the freight
24
transport sector. This project will foster the implementation of EU regulation on electronic freight
transportation exchange, which implementation is scheduled only for 2024. It is especially relevant
during COVID times (since mid-March 2020) when green corridors and quick and safe delivery
of goods has become of utmost importance for both employees (i.e. truck drivers) and consumers
within the EU.
7. Performance of DLT system in eCMR showcase
Network topology and server power (CPU, memory, disk space) may affect the performance.
Transactions per Second (TPS) is a standard performance indicator for this case.
If analyzing requirements to the system, then the number of transactions need to be indicated.
Testing solutions based on the same technology as the eCMR index registry created shows that
transactions can run up to 20,000 TPS per server. Still, if it turns out that the server at this point
needs more transactions, then additional solutions need to be included (optimizing the information
exchange, adding an extra server, cache information).
While developing DLT ecosystems it is important to use standardized APIs (service access, data
dictionary, communication protocol, encryption algorithm and system testing). It guarantees that
multiple vendors can provide similar services for the customers.
8. Advisory Board meetings during the project
To ensure the quality of the technical decisions the Advisory Board was formed. Members from
pilot project partner countries‘ institutions, technical background specialists, business
representatives were asked to join the board. During the project implementation phase, four
Advisory Board meetings have been organized:
a) Meeting date: 22.05.2020
Discussed questions:
● Technical decisions document presentation
● Index registry semantic model alignment
● Questions about DLT technology, used for the development of the prototype
b) Meeting date: 19.06.2020
Discussed questions:
25
● Presentation on infrastructure decisions: Google Cloud (Kubernetes)
● User management and DLT certificates (Keycloak)
● Each country's CA (certificates, embedded attributes)
● Testing scale (visual scheme)
● Future perspectives (eFTI)
c) Meeting date: 30.07.2020
Discussed questions:
● Discussion on the prepared API documentation:
https://koodivaramu.eesti.ee/majandus-ja-kommunikatsiooniministeerium/ecmr-
prototype-testing/-/blob/master/index-api/resources/api-docs.pdf
● Discussion on the Alfa testing between Lithuania and Estonia (sharing this testing
results and experiences)
● Presentation of the procedure of eCMR index system management in admin level
d) Meeting date: 11.09.2020
Topics on the meeting:
● Results of testing
● Final results of the prototyping
○ Feedback to final documentation
● Share eCMR index registry software with source code in Koodivaramu
https://koodivaramu.eesti.ee, software under MIT licence
● Next steps when the project is over
○ DIGINNOCUP as a follow-up to DIGINNO-Proto project
○ "Expectations and recommendations for further steps" from final
documentation - scope to DIGINNOCUP
26
9. Expectations and recommendations for further steps
Expressed expectations after practical eCMR testing:
● the expectation from the business side is that eCMR would be recognized legally, but
would not be mandatory from the government side for business;
● non-logistic companies have expressed interest in the digitalization of other documents
connected to the logistic processes’ (invoices, certificates of origin, etc.);
● the project has a potential for expansion to non-EU, but Baltic neighborhood countries, in
particular, to Ukraine and Belarus as part of the EU digital transport corridors strategy
(DTC) and as a part of EU4Digital collaboration.
● Further, the prototype may be a launchpad for implementing eFTI solutions in those
countries. Ukraine as an associative partner of the project team (in face of PPL 33-35 Ltd)
demonstrates a high degree of readiness and interest in the development of the project.
● Another area of expansion is countries of Benelux, in particular, Luxemburg. High interest
in the DIGINNO-Proto project from their side is a good point for starting an interopera-
bility assessment.
Recommendations:
● ensure the continuous test of the prototypes for further development (each country could
keep the prototype testing teams and infrastructure for smooth transition);
● to legalize the presented prototype logic (not particularly the specific technical solution);
● support establishing the index production infrastructure for all participating member states
and countries;
● discuss and align with eFTI and other legislation (national/regional/international);
● extend eCMR indexing initiative and prototype testing to:
- other Baltic Sea Region countries;
- EU level;
- Europe neighborhood countries (e.g. Ukraine, Belarus, etc.).
● add to the index server other digital documents as part of document container:
- Customs import and export declarations;
- invoices;
- veterinary certificates and documents etc.
27
● Scaling up to eFTI datasets
● current eCMR index system scale-up to be compliant with EBSI infrastructure
● Scaling up eCMR testing with another ongoing eCMR digital initiatives in EU (e.g.
FEDeRATED project, Benelux eCMR project)
Schema: Parties sharing electronic cargo documents (CMR, AWB, BOL, import and export declarations, etc.) in
machine readable format over the DLT network.
● make it useful to multimodal transport modes (train, plane, ferry) by extending the
prototype development by following eFTI recommendations;
● Recommendation to use (as the basis for eCMR development as the electronic document)
results from UN/CEFACT (see annexe no. 8) and OASIS UBL Waybill 2.1.
(https://docs.oasis-open.org/ubl/cs1-UBL-2.1/mod/summary/reports/UBL-Waybill-
2.1.html)
● continuous works with DIGINNO WP3 and compatibility with WP4 conclusions
28
● Increasing the awareness of needs and benefits of using eCMR and other electronics
documents in the transport sector. However, there is a considerable difference in the pace
of development in different countries.
● In DIGINNO project partners developed a cross-border eCMR architectural solution
(picture provided below) and defined conditions needed to its implementation. API part of
this architectural solution for eCMR/EDI providers to need to be realized and tested, the
middle intermediate (eCMR DB/API) layer should be created.
Schema: Illustration of eCMR index registry architecture. API part for eCMR/EDI providers needs to be
created in the next steps of the eCMR development to ensure the security of sharing data.
29
10. Relevant projects/ongoing initiatives
13.1. UN/CEFAT eCMR
UN/CEFACT is the United Nations Centre for Trade Facilitation and Electronic Business.
In 2008, an Additional Protocol on eCMR was introduced to support paperless versions of the
eCMR Note. Though several pilot tests have been conducted in the subsequent years, there has not
been an official standardized message format for the Electronic Consignment Note. In 2017, a
United Nations Centre for Trade Facilitation and Electronic Business project developed a business
requirements specification, core component eCMR message structure and XML message standard.
Now provides a set of documents serving like an international standard in electronic documents
exchange.
eCMR project deliverables:
● BusinessRequirementsSpecification(BRS)for
Electronic Road Consignment Note (eCMR)
based on the high-level MMT BRS
● Subset exchange syntax-neutral message
structures for eCMR
● XML schemas of the eCMR messages
● Mapping to the relevant existing UN/EDIFACT
UNSM (IFTMIN)
The eCMR is a subset of MMT – multimodal transport model – hierarchical data structure,
developed by UN/CEFACT to facilitate transport and trade procedures in the real world.
● The MMT project is creating a limited structured subset of the UN/CCL (Core
Components Library)
○ Only 132 ABIEs (Aggregated Business Information Entities) needed for the
project scope
● Providing semantic links with EDIFACT implementations
30
● eCMR project
● Data pipeline structure project for the standardized provision of pre-arrival data to
regulatory agencies in line with the EU Cassandra, CORE and SELIS projects
MMT ensures the next goals:
● Providing Exchange Syntax Neutral Reference Data Model for Supporting Domain Data
Exchange Interoperability
● Supporting Cross-Border Regulatory Interfaces
● Providing mappings to/from UN/EDIFACT message implementations
● Providing mappings to Related Data Models
● Generating equivalent interoperable XML message schemas
The interoperability is based on semantic due to harmonization of:
● Party and Role Definitions
● Semantic Anchors
● Message Structures
● Contextualized Code Subsets
● Contextualized Business Rules
The fact that eCMR is based on UN/CEFACT MMT provides a strict relationship between
transport and sales contracts and also between different modes of transport. That also ensures the
possibility to seamlessly expand the eCMR prototype project to a universal transport platform with
proved trust, interoperability and multimodality.
13.1. Digital Transport and Logistics Forum (DTLF)
The DTLF is a group of experts that brings together stakeholders from different transport and
logistics communities, from both the private and the public sector, with a view to building a
common vision and road map for digital transport and logistics. The DTLF also contributes to
identifying needs for measures at the EU level and supporting their development and
implementation where relevant.
https://www.dtlf.eu/
31
13.2. European Blockchain Services Infrastructure (EBSI)
The European Blockchain Services Infrastructure (EBSI) is a joint initiative between the European
Commission and the European Blockchain Partnership (EBP) to deliver EU-wide, cross-border
public services through the use of blockchain technology. The EBSI will materialise as a network
of distributed nodes across Europe – the blockchain infrastructure – leveraging an increasing
number of applications focused on specific use cases. EBSI is a CEF Building Block, providing
reusable software, specifications, and services to support adoption by public administrations,
businesses and citizens.
9.3. FEDeRATED project
The FEDeRATED project is an EU Member States driven initiative to contribute to the
establishment of a viable federated network of platforms for data sharing in the freight transport
and logistics domain at EU level (and beyond). The main objective is to enable a smooth and
effective public involvement with logistic chains for the execution of public duties. The
FEDeRATED project shall run from 01.01.2019 (“the starting date”) until 29.12.2023 (“the
completion date”) and is funded by Connecting Europe Facility (CEF).
The FEDeRATED project is built upon the work and recommendation of the Digital Transport
and Logistic Forum (DTLF), and in particular its subgroup 2, to create such viable and valid
federative network of platforms as an enabler for Business to Administration (B2A),
Administration to Business (A2B), and Business to Business (B2B) data exchange and sharing.
9.4. Single Window Initiative Estonia
The Single Window Initiative Estonia is a cluster/network, established in 2017, is working towards
Estonian and European digital transport & logistics solutions, digital supply chains and application
of Single Window principles. The main aim of the initiative is to promote and encourage the digital
shift in transport-related information flow for the benefit of all market participants. For reaching
the aim, the initiative works consistently on applied research on the feasibility of such
digitalization as well as moderates the exchange of best practices while developing digital
solutions and prototypes. The Initiative is represented in the Digital Transport and Logistics Forum
32
and participates in legislative processes, including the eFTI Regulation and the implementing acts
of it.
https://singlewindow.ee/en/
11. List of annexes and work documents
During the prototype development, a list of technical and procedural documents was prepared.
Documents were shared with pilot project parties: government institutions, business companies,
EDI providers, project coordinators. All the documents are submitted as the attachments to this
report.
Attachment no. 1 “eCMR Business Processes and Technical Decisions “
This document provides the most important decisions made during the preparation for the pilot
development. It includes a semantic data model of the core elements of an eCMR index, business
requirements specification. Also, specifies the processes in a distributed eCMR indexing system
and provides the main information on technical solution decisions (e.g. exchanged indexing data
structure/format, smart-contract input/output structure, etc.).
Attachment no. 2 “Testing of eCMR Prototype”
Document with the planned timeline, identified testing activities for different parties and the
description of the planned testing scenarios.
Attachment no. 3 “Process Description and Use Cases Example by Fitek Team”
The document is dedicated for technical background and business side specialists as it provides
information about the testing scenarios and gives real examples of how the testing looks in the
index registry system using Postman. Information about used eCMR index registry parameters in
this internal test is provided as well. A visual view of the use case process can be found in this
document.
33
Attachment no. 4 “Instruction How Use eCMR Index Registry Administration Console”
Document dedicated to country administrators who are in charge for users management in eCMR
index server in their country. Detailed instruction for the user management system is provided.
Attachment no. 5 “eCMR Indexing Server Addition Instruction”
Detailed instruction on how to connect index servers.
Attachment no. 6 “Project Parties”
Document dedicated to indicating all parties involved in the project (business, government, etc.)
and provide the contact details of representatives from each pilot party.
Attachment no. 7 “Testing Loads for Transit”
Document with the list of the loads used for real environment and virtual eCMR index registry
testing.
34
12. Useful links
1. UN/CEFACT. Business Requirement Specifications (BRS), find in page “e-CMR”
(26.08.2020)
https://www.unece.org/cefact/brs/brs_index.html
2. edi3. Supply Chain Standards and Tools for Web Developers (27.08.2020)
https://edi3.org/
3. Keycloak. Open Source Identity and Access Management For Modern Applications
and Services (27.08.2020)
https://www.keycloak.org/
4. OAuth 2.0 (04.09.2020)
https://oauth.net/2/
5. World Bank Group. Distributed Ledger Technology (DLT) and Blockchain
(27.08.2020)
https://responsiblefinanceforum.org/wp-content/uploads/2018/04/Distributed-Ledger-
Technology-and-Blockchain-Fintech-Notes.pdf
6. European Union. eFTI Regulation
https://eur-lex.europa.eu/legal-
content/EN/TXT/?qid=1596465759558&uri=CELEX:32020R1056
7. CEF Digital Connecting Europe. Introducing the European Blockchain Services
Infrastructure (EBSI) (27.08.2020)
https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/EBSI
8. European Commission. The European Single Market (27.08.2020)
https://ec.europa.eu/growth/single-market_en
9. Kristo Vaher. Next Generation Digital Government Architecture (27.08.2020)
https://docs.google.com/document/d/1UJ-
5wi9wavWzA2n4LhsbONJqdxjUSIgMxKJNaZZslas/edit?fbclid=IwAR2rrBNjwHFagHI
vi-9Pv6uvKI0IZH_m4IdAfaq7hbjALlIjRH8nEuUVuic
35
Teostatud töö üleandmise ja vastuvõtmise akt hanke nr 218902 raames
Teostatavate töö nimetus: „E-Veoselehe prototüübi valmistamine ja testimine“
Töö teostaja üldandmed:
Töö teostaja ärinimi: Fitek EDI, UAB
Töö teostaja registrikood: 125677598
Töö teostaja juriidiline aadress: Panerių g. 51, Vilnius, LT-03160
Leedu Vabariik
Töö teostaja poolse kontaktisiku nimi Riho Vedler, telefon +372 55515112,
ja kontaktandmed (e-posti aadress, e-post
[email protected].
telefoninumber):
Töö kogumaksumus:
Maksumus eurodes KM-ta: 56 000
Maksumus eurodes KM-ga: 67 200
Teostatud töö kirjeldus:
Töö on teostatud täies mahus hanke viitenumber 218902 raames ning vastavad hanke
alusdokumendi tingimustele.
Projekt antakse üle MIT litsentsiga. Töö teostajal on kohtustus teostada lähtekoodi ja
koodihoidla tarne Githubist Koodivaramu.eesti.ee
Töö vastuvõtjale anti üle järgmised andmefailid:
1. juurdepääs prototüübi testimiskeskkonna URL-ile;
2. API kirjeldus (kasutades Swaggeri kasutajaliidest või muud sarnast) koos
koodinäidistega;
3. projekti rakendamine ja prototüübi kasutusjuhend;
4. tehniline kirjeldus, kuidas lisada uut indeksiserverit võrku, mis hakkab vahetama
teavet teiste indeksiserveritega;
5. testjuhtumite ja -tulemuste kirjeldus;
6. lõpparuanne, s.h projekti tegevuste, elluviimise ja tulemuste aruanne;
7. soovitused edasisteks tegevusteks.
Poolte allkirjad:
Töö vastuvõtja Töö üleandja
Majandus- ja Kommunikatsiooniministeerium Fitek EDI, UAB
Eva Killar Riho Vedler
peaspetsialist volitatud esindaja
Allkirjastatud digitaalselt Allkirjastatud
digitaalselt digitaalselt
eCMR Business Processes‘
and Technical Decisions
Development funded by
DIGINNO-Proto
Version 1.00
Content
1. Business .............................................................................................................................................................. 3
1.1. Semantic data model of the core elements of an e-CMR index ...............................................3
1.2. Business Requirements Specification ......................................................................................5
2. Processes ............................................................................................................................................................. 6
2.1. Description of processes in a distributed e-CMR indexing system .........................................6
2.1.1. Info exchange in national level .........................................................................................6
2.2. Description of process in communication with e-CMR index server ......................................6
2.3. Possible connection types of trucks and trailers ......................................................................7
2.3.1. BASIC ...............................................................................................................................7
2.3.2. BASIC (TRANSIT) ..........................................................................................................8
2.3.3. TRANSIT WITH CHANGE OF LOADING UNIT, DURING TRANSPORTATION ..8
2.3.4. DISTRIBUTION ..............................................................................................................8
2.3.5. CONSOLIDATION SCENARIO .....................................................................................9
2.3.6. TRADE FLOW SCENARIO ..........................................................................................10
3. e-CMR technical solution decisions ................................................................................................................. 11
3.1. Exchanged indexing data structure/format ............................................................................11
3.2. Distributed e-CMR index exchange solution .........................................................................12
3.2.1. Smart-contract input/output structure .............................................................................12
3.3. Internal indexing server search and storage engine ...............................................................12
3.4. API .........................................................................................................................................12
3.5. Credential storage ..................................................................................................................13
3.6. Optional direct communication with DLT indexing layer .....................................................13
4. Technical considerations ................................................................................................................................... 14
4.1. Data dissemination option in API request body ....................................................................14
5. Annexes............................................................................................................................................................. 15
2
1. Business
1.1. Semantic data model of the core elements of an eCMR index
Table 1. eCMR index semantic data model
ID Level Cardin Business Term Description Usage Note TDED Data type BRS ID Sample value
ality
BG-1 1 1..1 documentIdent The unique identifier participantIdentifier: Complex
ifier of this exchanged documentIdentifier.value
document (OID)
BG-1.2 2 1..1 participantIden ISO/IEC 6523 Complex
tifier https://en.wikipedia.org/wiki/IS
O/IEC_6523
https://docs.peppol.eu/poacc/bil
ling/3.0/codelist/ICD/
We propose to use similar rules that
PEPPOL use for eInvoicing
BT-1.2- 3 1..1 scheme A(4) 200
1
BT-1.2- 3 1..1 value A(9) 125677598
2
BG-1.3 2 1..1 scheme Id:value Complex
BT-1.3- 3 1..1 Id Busdox A()
1
BT-1.3- 3 1..1 value A() eCMR v.1.0
2
BT-1-1 2 1..1 value A() iso6523-actorid-
upis:0200:125677598-
7357bf9f95ez
BG-2 1 1..1 document Complex
BT-2-1 2 1..1 Country code The location where Country code in ISO3166-1alpha-2 UDT0000019 A(2) R-6 LT
this exchanged system UN01004598
document has been (https://www.iban.com/country-
issued. codes)
Identifier Country
Code Definition: The
unique identifier of a
country for this
logistics location.
BG-2.1 2 1..N transport categoryCode: countryCode Complex
registrationNumber
BT-2.1- 3 1..1 Category code The code specifying Information about trucks and trailers UN02000087 A(3) vehicle
1 the type of logistics (urn:un:unece:uncefact:codelist:stan
means of transport dard:UNECE: UN01003767
TransportEquipmentCategoryCode:
D19A
TE=Trailer).
BT-2.1- 3 1..1 Country code The identifier of the https://en.wikipedia.org/wiki/Internati UDT0000011 A(3) EE
2 country for this onal_vehicle_registration_code UN01011036
government
registration.
BT-2.1- 3 1..1 Vehicle An identifier of this UDT0000011 An(9) 800ABC
3 registration logistics means of UN01003822
number transport, such as the
road transport
registration plate
number
BT-2-2 2 1..1 uri The unique Uniform Location of source document in the UDT000002 A() R-4 https://lt.ecmr4.eu/docume
Resource Identifier address space of certain EDI UN01006015 nts/iso6523-actorid-
(URI) for this provider upis:0200:125677598-
specified binary file. 7357bf9f95e5
BT-2-3 2 1..1 Document The number of the UDT000002 A() R-7 14b55a3a797d1ad449a74
fingerprint checksum for this UN00002653 d0c6020f05caaf58b02627
document. UN00006066 eb88f3a86bf9eac1ca1a8
BT-3 1 1..1 Creation Timestamp R-1 Filled in by the system
DateTime
BT-4 1 0..1 Update Timestamp R-1 Filled in by the system
DateTime
BT-5 1 0..1 Expire Information of date UDT000008 Timestamp R-1
DateTime and time when UN01001275
consignment was
closed
Reference to UN/CEFACL CCL: https://www.unece.org/fileadmin/DAM/uncefact/CCL/CCL20A.zip
Reference to UN/CEFACT eCMR:
https://www.unece.org/fileadmin/DAM/cefact/Standards/eCMR/05_eCMR_CCL_Structure_16FEB18.pdf
https://www.unece.org/fileadmin/DAM/cefact/Standards/eCMR/01_BRS_eCMR_v1.pdf
1.2. Business Requirements Specification
Table 2. Business requirements specification
BRS ID Description
R-1 expire date / time / time zone of the eCMR document (optional)
a. expire date / time / time zone must validate from now to the future
b. If expire date not defined, then document in open status in the eCMR index system
R-4 Truck registration number (required, if haulier)
R-5 Trailer/tank registration number (required, if haulier and goods loaded to trailer)
Possible connect with goods just truck and also truck train, examples with truck & trailer(s):
Example 1.
https://upload.wikimedia.org/wikipedia/commons/2/29/Alle_Varianten_LZV.jpg?1587496423282
Example 2. http://www.transportoversize.eu/files/Main/docs/Dimensions%20of%20vehicle.bmp
Example with truck train:
1. created CMR with number A123232 – total weight 35000kg
2. Loaded to truck train: truck, plate number 800ABC + trailer, plate number 81-DI + trailer, plate number
12-LE
Registration number > isoCode - country code, example in Ukraine "UA"
Registration number > regNumber - vehicle registrated plate number
Look also https://en.wikipedia.org/wiki/Vehicle_registration_plates_of_Europe
R-6 eCMR index number (required)
a. eCMR index structure described in section “STRUCTURE OF eCMR INDEX”
R-7 Hash of binary e-CMR document, fingerprint (required)
Attribute "type" connected with "fingerprint" define what technology used when system create it (possible
use SHA256).
5
2. Processes
2.1. Description of processes in a distributed e-CMR indexing system
2.1.1. Info exchange in national level
EDI provider info exchange with truck driver
Users of service: Drivers, logistic managers
Functionality: Service provider who handle with eCMR electronic documents and take care of digital
info exchange between driver and logistics manager. EDI provider also exchanges metadata info with eCMR
index server.
Figure 1. EDI provider info exchange with truck driver illustration
2.2. Description of process in communication with e-CMR index server
Figure 2. Description of process in communication with e-CMR index server illustration
2.3. Possible connection types of trucks and trailers
Figure 3. Truck types illustration
2.3.1. BASIC
Consignment loaded in Country A, at the senders’ premises is delivered to the Consignee in
Country B:
Country A Country B
AA 01 AA 01
ABC 123
ABC 123
EDI provider Transport Company
eCMR Index server eCMR Index server
Control institution country A Control institution country B
CMR INDEX TRUCK NO
Seller Consignment Transport Delivery info
Buyer Invoice Data
Data Instructions
7
2.3.2. BASIC (TRANSIT)
Consignment loaded in Country A, at the senders’ premises is delivered to the Consignee in
Country C, Truck is passing transit country (B):
Country A Country C
Country B
AA 01 AA 01
ABC 123
ABC 123
2.3.3. TRANSIT WITH CHANGE OF LOADING UNIT, DURING TRANSPORTATION
Consignment loaded in Country A, at the senders’ premises is delivered to the Consignee in
Country C, Truck is passing transit country (B), in a country B, Trailer is taken by new truck:
Country A Country C
Country B
AA 01 AA 01 AA 01
XXX 999
XXX 999
ABC 123
ABC 123
2.3.4. DISTRIBUTION
Consignments, designated to the different buyers of one producer are loaded in Country A, at the
senders’ premises. All goods are delivered to the logistic center in a Country B. Goods are distributed to
different buyers by delivery trucks:
8
2.3.5. CONSOLIDATION SCENARIO
Consignments are collected from sellers Country A, and consolidated at logistics center, Logistics
operator is sending consolidated shipment by linehaul truck to the Logistics center in Country B. Goods
are distributed to different buyers by local “last mile” network:
Country B
Country A
9
2.3.6. TRADE FLOW SCENARIO
Goods, from different sellers, destinated to the buyers in different countries, are collected on
logistics center of Country A and, after consolidation sent to Country B. Logistics operator in Country B,
after unloading of Line haul truck, starting distribution of shipments in own country and preparing new
consolidations to country C and Country D, by combining shipments from Country A, and export
shipments of his local customers. Logistics providers in Country C and Country D, are organizing final
delivery of shipments in own countries:
Country C
Country B
Country D
Country A
10
3. e-CMR technical solution decisions
The following section defines technical aspects of the e-CMR indexing system that is going to be
developed (specific aspects might deviate/change during development) as agreed by Fitek EDI and partners.
The figure bellow (Figure 4) illustrates the main workflow scenario of the system. As shown in
illustration, the users will be provided access tokens. With an access token, the user will be able to send request
to e-CMR indexing server API that will allow to add or query e-CMR indexing data if the access token and the
linked certificate in the server meets the defined rules and requirements (as an example, specific users might
be allowed only to query the e-CMR indexing data based on his certificate attributes). The combination of
security and management layers will provide user management functionality and permissioned system access
functionality.
Figure 4. e-CMR indexing solution API request scenario illustration
3.1. Exchanged indexing data structure/format
The data format/structure of exchange e-CMR index is going to be JSON (JavaScript Object Notation).
11
3.2. Distributed e-CMR index exchange solution
The Hyperledger Fabric platform will be used as a backbone of e-CMR indexing system. It is an
enterprise grade permissioned distributed ledger platform originally developed by IBM. It provides modular
architecture with fine-grained customization possibility across different network nodes and ensures data
exchange security, non-repudiation, and trust.
This platform is perfect fit for e-CMR indexing solution as its enterprise-grade functionality allows to
implement various data exchange scenarios with production-grade security and transparency measures.
3.2.1. Smart-contract input/output structure
The input and output data format for smart-contract/-s will be in JSON format as it will be aligned with
internal data exchange meta-structure of the system, have more structured and readable input format, is
supported by document-based databases and has possibility to validate input based on already implemented
standards and solutions.
The smart-contract/-s will be developed in a way, that they expect to receive one argument as JSON
parameter, since it will allow easier and more flexing input data validation. Input data of smart-contract is
going to be validated using either JSON Schema (which is preferred) or internal programming language
validation functionality in specific cases.
3.3. Internal indexing server search and storage engine
To allow flexible and fast access to the exchanged data between different countries, each country will
use CouchDB as search and storage engine. It will allow to search exchanged data by specific data fields while
also ensuring search performance and flexibility.
3.4. API
To allow easy, fast, and flexible access the system, and streamline the adoption the solution - e-CMR
indexing server will have an API that abstracts the complexity of communication with data exchange layer.
It will be based on current RESTful API standards and allow user to add or query e-CMR indexing data
The following aspects define API implementation:
Architectural style: REST
Request/data format: JSON
Security, authentication and authorization: OAuth2.0 / OpenID
12
Documentation: OpenAPI 3.0 (OAS 3.0)
(the specific documentation will be provided during the documentation stage of the project)
3.5. Credential storage
To streamline adoption of this solution, provide easy and flexible access to the system, ensure security
and transparency of the system, from the governmental perspective - the private keys and public keys of the
users (clients, EDI Providers, customs, etc…) will be stored in the governmental e-CMR indexing server. This
will allow to have fine-grained and strict control over the users credentials and also streamline the adoption of
the system as it will allow users to connect to a system via simplified API while also preserving the security
aspects of the system. This scenario is illustrated in the section above (Figure 4).
NOTE: If connecting client will not be satisfied with the provided security of API, he will be able to
send registration request (CSR) to the e-CMR indexing server and securely obtain his certificate while not
exposing his private keys to governmental indexing server. This will allow to have maximum security both from
the user perspective and government perspective, however it will reduce the simplicity the system as the API
will not be used in this scenario and user will have to directly communicate with the system using different
protocol (scenario is illustrated in Figure 5).
3.6. Optional direct communication with DLT indexing layer
If the user is not satisfied with the provided API solution, he will be able to obtain certificate without
having to store his privately generated private key in governmental e-CMR indexing server (as describe above
in 3.5. Credential storage). It means that the user will bypass API layer and communicate directly with DLT
indexing layer and as a result, he will have to use additional software development kit, which enables
communication with the indexing layer directly.
13
4. Technical considerations
4.1. Data dissemination option in API request body
Since the developed system will be operated in multiple countries, it would be wise to assume, that the
client who appends index to the system must be able to decide who can and must receive the appended
information. As an example, if LV customs do not want to exchange this information with PL, it must be able
to define specific parameters in API request body, that would enforce the data exchange only between
selected/defined parties/countries.
At the moment we are discussing which of the following possible solutions would be the most suitable,
compliant and convenient from the client perspective:
1. If client does not specify which countries can receive indexing data, then all countries in the
indexing network will receive this data
2. If client does not specify which countries can receive indexing data, then indexing data will be sent
only to the country that the client belongs to
NOTE: If certain country is not allowed to receive specific indexing data, then technically that country
only receives the hash of indexing data. This aspect would allow that country to verify whether that data was
really exchanged between specific countries if it could receive original exchanged data and calculate
hash/fingerprint of it.
14
5. Annexes
Figure 5. e-CMR direct communication with the DLT layer scenario
15
Testing of eCMR indexing and
search system
During testing, all parties of the project will have possibility to gather information, and plan further
development of electronic data exchange in international / domestic transport sectors.
By performing test, participation countries will check:
- Possibilities to collect data about goods trade between participating countries.
- Interoperability of different operating systems in the countries.
- Ability to check / control the movement of goods at stationary and mobile control points in
different countries.
BASIC (TRANSIT)
Consignment loaded in Country A, at the senders’ premises is delivered to the Consignee
in Country C, Truck is passing transit country (B):
Funded by Diginno-Proto
In this prototype test, we plan to check ability of providing data to a transit country, where information
about seller / buyer and content of goods in transit has lower level of importance,
Mentioned scenarios is planned just for the testing of planned to create system prototype, and
covering just part of trade/ transportation models, already used by economic operators in our
countries. On the same time, it is necessary to evaluate all of them, in order to create data system,
which will be acceptable as for the public and for trade. Above mentioned scenarios show that basic
data set, needed to build efficient system for paperless trade is bit complex.
We will appreciate if your organization will dedicate persons who could communicate with our project
group matters regarding API requirements, an in order to align them between participating countries.
For the further preparations and project development we would appreciate if state authorities from
each participating country would provide following information needed for successful continuation of
the project:
1) Institutions – users of e-CMR data in each participating country
2) Data, which in opinion of the state authorities is necessary to be available and accessible for
the control of goods / cargo movement and trade control:
a) In dispatching country
b) In the receiving country
c) In transit country
3) Core expectations from the e-CMR as prototype, and future expectations of e-CMR as final
product, in full use for trade facilitation
Please, provide your answers until the middle of May (18.05.2020) or our team is always ready to get
online and provide you with more information about the prototype.
Funded by Diginno-Proto
PLANNED TIMELINE
Description Period
Exchange of information on technical requirements June - July 2020
Testing of eCMR prototype (cross-border exchange of information August 2020
between servers)
Full testing of eCMR prototype August-September 2020
• ESTONIA. Load (warehouse / driver / truck / trailer)
• ESTONIA. Control on the road
• LATVIA. Control on the road
• LITHUANIA. Control on the road
• POLAND. Control on the road
• POLAND. Unload (warehouse / driver / truck / trailer)
Funded by Diginno-Proto
USER GUIDE
Process Description and
Tested Use Case Example
by Fitek Team
Development funded by
Diginno-Proto
Manual Version 1.05
Contents
Visual view of use case process .............................................................................................................. 3
Case 1. Warehouse (Estonia) .................................................................................................................. 4
Case 2. Load (Estonia) ............................................................................................................................. 5
Case 3. Control (Latvia) ........................................................................................................................... 7
Case 4. Control (Lithuania) ...................................................................................................................... 9
Case 5. Unload (Poland) .......................................................................................................................... 9
Estonian eCMR index registry parameters ....................................................................................... 11
Latvian eCRM index registry parameters .......................................................................................... 11
Lithuanian eCRM index registry parameters .................................................................................... 11
Poland eCRM index registry parameters .......................................................................................... 11
Questions and answers ......................................................................................................................... 12
If you use in test examples below, don't forget update inside
source code vehicle plate numbers and unique number of
eCMR index ID.
2
Visual view of use case process
1. WAREHOUSE
2. LOAD
EE index registry
All index registries
exchange data
with each other
3. CONTROL
LV index registry
LT index registry
4. CONTROL
PL index registry
5. UNLOAD
3
Case 1. Warehouse (Estonia)
Participant: Warehouse
Vehicle plate numbers: (EE) 137ABC [TRUCK], (EE) QI99 [TRAILER]
Activities: I as warehouse worker create eCMR document and add document
link to national eCMR index registry
Process: 1. Warehouse add eCMR metadata and document location to
national eCMR index registry.
User rights group: Business
Pre requirements: 1. Created user account (link)
2. Account added to group “Business” (link)
3. User has downloaded it’s certificate for API call (link)
Process 1 example code (POST) Role: Warehouse
{ Business name: Ospentos
"participantIdentifier": { International OÜ
"scheme": "iso6523-actorid-upis", Register code: 11306955
"value": "0191:11306955"
},
"documentIdentifier": {
"scheme": {
"id": "busdox-docid-qns",
"value": "eCMR v.1.0"
},
"value": "iso6523-actorid-upis:0191:11306955-QXxUQqbe3jqc"
},
"processIdentifier": {
"scheme": "cenbii-procid-ubl",
Warehouse share with
driver eCMR QR Code
"value": "urn:www.cenbii.eu:profile:ecmr:ver1.0"
},
"document": {
"countryCode": "EE",
"uri": "https://www.ospentos.ee/documents.php?id=QXxUQqbe3jqc",
"fingerprint": "14b55a3a797d1ad449a74d0c6020f05caaf58b02627eb88f3a86bf9eac1ca1a8"
}
}
4
Case 2. Load (Estonia)
Participant: Truck driver
Vehicle plate numbers: (EE) 137ABC [TRUCK], (EE) QI99 [TRAILER]
Activities: 1. I as driver load goods to trailer and download eCMR documents
by unique ID throw EDI provider system
2. I as driver accept eCMR documents. Also change eCMR document
location and add truck and trailer plate numbers
Process: 1. I as EDI provider load eCMR document location from national
eCMR index registry
2. I as EDI provider load eCMR document by document URI
3. I as EDI provider add eCMR updated metadata and document
location to national eCMR index registry.
User rights group: Business
Pre requirements: 1. Created user account (link)
2. Account added to group “Business” (link)
3. User has downloaded it’s certificate for API call (link)
4. eCMR was created on previous step and documentIdentifier is
known to user
Process 1 example code (GET):
{{API_URL}}/index/iso6523-actorid-upis:0191:14258742-QXxUQqbe3jqc
Index registry answer
[{
"participantIdentifier": {
"scheme": "iso6523-actorid-upis",
"value": "0191:11306955"
},
"documentIdentifier": {
"scheme": {
"id": "busdox-docid-qns",
"value": "eCMR v.1.0"
},
"value": "iso6523-actorid-upis:0191:11306955-QXxUQqbe3jqc"
},
"processIdentifier": {
"scheme": "cenbii-procid-ubl",
"value": "urn:www.cenbii.eu:profile:ecmr:ver1.0"
},
"document": {
"countryCode": "EE",
"createdDateTime": "2019-10-12T14:20:50.52+07:00",
"updatedDateTime": "2019-10-12T14:20:50.52+07:00",
5
"uri": "https://www.ospentos.ee/documents.php?id=QXxUQqbe3jqc",
"fingerprint": "14b55a3a797d1ad449a74d0c6020f05caaf58b02627eb88f3a86bf9eac1ca1a8"
}
}]
Role: EDI provider
Process 3 example code (PUT): Business name: Intepia OÜ
{
Register code: 14258742
"participantIdentifier": {
"scheme": "iso6523-actorid-upis",
"value": "0191:14258742"
},
"documentIdentifier": { Changes marked
"scheme": { with yellow colour!
"id": "busdox-docid-qns",
"value": "eCMR v.1.0"
},
"value": "iso6523-actorid-upis:0191:11306955-QXxUQqbe3jqc"
},
"processIdentifier": {
"scheme": "cenbii-procid-ubl",
"value": "urn:www.cenbii.eu:profile:ecmr:ver1.0"
},
"document": {
"countryCode": "EE",
"transport": [
{
"categoryCode": "3 39",
"countryCode": "EE",
"registrationNumber": "137ABC"
},
{
"categoryCode": "3 TE",
"countryCode": "EE",
"registrationNumber": "QI99"
}
],
"uri": "https://www.intepia.com/documents/?id=QXxUQqbe3jqc",
"fingerprint": "85475814b55a3a797d1ad449a74d0c6020f05caaf58b02627eb88f3a86bf9eac"
}
}
6
Case 3. Control (Latvia)
Participant: Police
Vehicle plate numbers: (EE) 137ABC [TRUCK], (EE) QI99 [TRAILER]
Activities: 1. Police patrol car video camera scan from distance the plate
number of the TRUCK moving on the road and send scanned
number info throw internet to national central data system.
2. Police central data system make request to national eCMR index
server and get back all eCMR documents connected with TRUCK
number.
3. Police system download eCMR document by document URI
4. Police information system analyze data return summed results to
computer display on the patrol car.
Process description: 1. Control institution central data system make info request from
eCMR index server by TRUCK registration number.
2. eCMR index server return package of eCMR documents indexes
connected with truck number.
User rights group: Government
Pre requirements: 1. Created user account (link)
2. Account added to group “Government” (link)
3. User has downloaded it’s certificate for API call (link)
4. Truck is on Latvian territory
5. At least one plate number is known to user
Process 1 example code (GET):
{{API_URL}}/index?transport_reg_number=137ABC&transport_country_code=EE
Index registry answer
[{
{
"participantIdentifier": {
"scheme": "iso6523-actorid-upis",
"value": "0191:14258742"
},
"documentIdentifier": {
"scheme": {
"id": "busdox-docid-qns",
"value": "eCMR v.1.0"
},
"value": "iso6523-actorid-upis:0191:11306955-QXxUQqbe3jqc"
},
"processIdentifier": {
"scheme": "cenbii-procid-ubl",
7
"value": "urn:www.cenbii.eu:profile:ecmr:ver1.0"
},
"document": {
"countryCode": "EE",
"transport": [
{
"categoryCode": "3 39",
"countryCode": "EE",
"registrationNumber": "137ABC"
},
{
"categoryCode": "3 TE",
"countryCode": "EE",
"registrationNumber": "QI99"
}
],
"createdDateTime": "2019-10-12T14:20:50.52+07:00",
"updatedDateTime": "2019-10-14T14:20:50.52+07:00",
"uri": "https://www.intepia.com/documents/?id=QXxUQqbe3jqc",
"fingerprint": "85475814b55a3a797d1ad449a74d0c6020f05caaf58b02627eb88f3a86bf9eac"
}
}
}]
8
Case 4. Control (Lithuania)
Participant: Police
Vehicle plate numbers: (EE) 137ABC [TRUCK], (EE) QI99 [TRAILER]
Activities: 1. Police patrol car video camera scan from distance the plate
number of the TRAILER moving on the road and send scanned
number info throw internet to national central data system.
2. Police central data system make request to national eCMR index
server and get back all eCMR documents connected with
TRAILER number.
3. Police system download eCMR document by document URI
4. Police information system analyze data return summed results to
computer display on the patrol car.
Process description: 1. Control institution central data system make info request from
eCMR index server by TRAILER plate number.
2. eCMR index server return package of eCMR documents indexes
connected with TRAILER number.
User rights group: Government
Pre requirements: 1. Created user account (link)
2. Account added to group “Government” (link)
3. User has downloaded it’s certificate for API call (link)
4. Truck is on the Lithuanian territory
5. At least one plate number is known to user
Process 1 example code (GET):
{{API_URL}}/index?transport_reg_number=QI99&transport_country_code=EE
Index registry answer
Same as Case 4 answer
Case 5. Unload (Poland)
Participant: Truck driver
Vehicle plate numbers: (EE) 137ABC [TRUCK], (EE) A-123 [TRAILER]
Activities: I as driver unload goods from trailer and confirm in mobile device
that goods are unloaded
Process: 1. I as EDI provider confirm that eCMR document expired (not
connected any more with truck and trailer).
User rights group: Business
9
Pre requirements: 1. Created user account (link)
2. Account added to group “Business” (link)
3. User has downloaded it’s certificate for API call (link)
4. DocumentIdentifier is known to user
5. Truck is on the Poland territory
Process 1 example code (PUT):
{
"participantIdentifier": {
"scheme": "iso6523-actorid-upis",
"value": "0191:125677598"
},
"documentIdentifier": {
"scheme": {
"id": "busdox-docid-qns",
"value": "eCMR v.1.0"
},
"value": "iso6523-actorid-upis:0191:11306955-QXxUQqbe3jqc"
},
"processIdentifier": {
"scheme": "cenbii-procid-ubl",
"value": "urn:www.cenbii.eu:profile:ecmr:ver1.0"
},
"document": {
"countryCode": "EE",
"transport": [
{
"categoryCode": "3 39",
"countryCode": "EE",
"registrationNumber": "137ABC"
},
{
"categoryCode": "3 TE",
"countryCode": "EE",
"registrationNumber": "QI99"
}
],
"expiredDateTime": "2019-10-12T14:20:50.52+07:00",
"uri": "https://www.intepia.com/documents/?id=QXxUQqbe3jqc",
"fingerprint": "14b55a3a797d1ad449a74d0c6020f05caaf58b02627eb88f3a86bf9eac1ca1a8"
}
}
10
Estonian eCMR index registry parameters
• SSO_URL. https://sso.playground.ecmr4.eu/auth/realms/ee
• API_URL. https://api.ee.playground.ecmr4.eu/v1
• Access as business user in test of prototype.
Username:
[email protected] Password: ee.business@ecmr4
• Access as government user in test of prototype.
Username:
[email protected] Password: ee.government@ecmr4
Server parameters defined in Postman:
Latvian eCRM index registry parameters
• SSO_URL. https://sso.playground.ecmr4.eu/auth/realms/lv
• API_URL. https://api.lv.playground.ecmr4.eu/v1
• Access as business user in test of prototype.
Username:
[email protected] Password: lv.business@ecmr4
• Access as government user in test of prototype.
Username:
[email protected] Password: lv.government@ecmr4
Lithuanian eCRM index registry parameters
• SSO_URL. https://sso.playground.ecmr4.eu/auth/realms/lt
• API_URL. https://api.lt.playground.ecmr4.eu/v1
• Access as business user in test of prototype.
Username:
[email protected] Password: lt.business@ecmr4
• Access as government user in test of prototype.
Username:
[email protected] Password: lt.government@ecmr4
Poland eCRM index registry parameters
• SSO_URL. https://sso.playground.ecmr4.eu/auth/realms/pl
• API_URL. https://api.pl.playground.ecmr4.eu/v1
• Access as business user in test of prototype.
Username:
[email protected] Password: pl.business@ecmr4
• Access as government user in test of prototype.
Username:
[email protected] Password: pl.government@ecmr4
All test users accounts will expire 15.09.2020.
11
Questions and answers
Question 1: How I can find to what category belong my truck or trailer?
Answer: Very easy to find right category to your truck or trailer. Definition of category base on the
UN/CEFACT standard.
Syntax: “CategoryCode”: “{{CATEGORY1}} {{CATEGORY2}}”
Explanation:
• {{CATEGORY 1}} Road transport (3)
• {{CATEGORY 2}} Category of transport
Example: 3 31
# Type of transport equipment {{CATEGORY1}} {{CATEGORY2}}
1 Truck 3 31
2 Truck with loading place 3 34
3 Truck with loading place (refrigerator) 3 39
4 Truck with loading place (isoterm) 3 39
5 Truck with loading place (cistern) 3 32
6 Truck with loading place (platform) 3 36
7 Truck with loading place (tipper) 3 35
8 semi trailer 3 SM
9 cistern 3 TA
10 tipper 3 TE
11 platform 3 TE
12 isoterm 3 TE
13 refrigerator 3 TE
14 grain 3 TE
15 Boxcar 3 BX
16 Container 3 CN
12
Question 2: If our company use road train how define it in eCMR index registry?
Answer: eCMR index registry API allow very easy define more than one trailer. Code example with 1
truck with loading place and number plate 137ABC pluss 2 trailers with number plates QI99 and QR88:
...
"transport": [
{
"categoryCode": "3 39",
"countryCode": "EE",
"registrationNumber": "137ABC"
},
{
"categoryCode": "3 TE",
"countryCode": "EE",
"registrationNumber": "QI99"
},
{
"categoryCode": "3 TE",
"countryCode": "EE",
"registrationNumber": "QR88"
}
],
...
Question 3: Can I control the history of changes made with the eCMR index?
Answer: Yes, it is possible. In this case, the GET query looks like /index/{id}?history=true
Please look also to technical documentation https://koodivaramu.eesti.ee/majandus-ja-
kommunikatsiooniministeerium/ecmr-prototype-testing/-/blob/master/index-api/resources/api-
docs.pdf
Question 4: Why does a company have to add "expiredDateTime" to the eCMR index registry after
unloading the goods?
Answer: expiredDateTime very important add to eCMR index registry when goods are unloaded. If
police control the truck after unload, then eCMR index registry does not show any more current index
connected with truck or trailer plate number.
13
Question 5: From where I find my eCMR index ID?
Answer: Look added example below.
Index ID
Question 6: If I as a truck company download from warehouse system eCMR document and start
share eCMR document in my server (change document URI and fingerprint), then what more I must
change in the index registry?
Answer: You MUST keep only index ID value, but change all other data fields by your company.
Question 7: On base question 6. If I as truck company change during the eCMR document lifecycle
index ID, then what happen?
Answer: You can change index ID, but it’s mean that you create new lifecycle of changes. In this case
very important that you close eCMR document previous lifecycle with field “expiredDateTime”.
Question 8: Is it possible to see who viewed or changed the eCMR index?
Answer: Yes, it’s possible. Please check under the technical documentation section “Get index access
log”.
14
Question 9: We as government institution cannot find several vehicles in the system by vehicle
number. Why?
Answer: If a truck with a trailer loads the cargo, then warehouse or the truck company info system
add index to the eCMR index registry.
If the truck unloads the goods, then info system add update and mark that current index expired
(expiredDateTime = now).
If police control make requests by truck or by trailer number between load and unload, then the result
will be the previously mentioned index.
If police control after unload by truck or by trailer number, then this cargo not connected any more
with the vehicle and registry gives you an empty result (it means that trailer empty).
After unloading possible find this cargo in eCMR index registry only by index ID.
15
USER GUIDE
Instruction How Use
eCMR Index Registry
Administration Console
Development funded by
Diginno-Proto
Manual Version 1.01
Contents
Links ........................................................................................................................................................ 3
User management for country admins ............................................................................................... 3
Account registration for users (EDI providers, police, tax inspection, etc.) ....................................... 3
Login screen ............................................................................................................................................ 3
Create a new user ................................................................................................................................... 4
View specific user.................................................................................................................................... 6
Set user as country administrator........................................................................................................... 8
Groups ................................................................................................................................................... 10
General overview .............................................................................................................................. 10
How to create a new group .............................................................................................................. 10
How to exit exist group ..................................................................................................................... 14
Assigning user to a group .................................................................................................................. 15
Remove user from group .................................................................................................................. 16
2
Links
Note: all user links will expire 15.90.2020.
User management for country admins
• ESTONIA. https://admin.ee.playground.ecmr4.eu
• LATVIA. https://admin.lv.playground.ecmr4.eu
• LITHUANIA. https://admin.lt.playground.ecmr4.eu
• POLAND. https://admin.pl.playground.ecmr4.eu
Account registration for users (EDI providers, police, tax inspection, etc.)
• ESTONIA. https://account.ee.playground.ecmr4.eu
NOTE! All user can also login
• LATVIA. https://account.lv.playground.ecmr4.eu account registration URL
• LITHUANIA. https://account.lt.playground.ecmr4.eu address and change
temporary password.
• POLAND. https://account.pl.playground.ecmr4.eu
Login screen
3
Create a new user
If you want create new user, then click to group “Users” (1) and to button “Add user” (2)
2
1
Fill required fields (3) and click to button “Save” (4).
3
Optional value
4
4
Set under tab “Credentials” (5) temporary password (6) for new user, otherwise he will not be able to
login.
5
6
5
View specific user
By default, the system does not show all users. So in order to see users that are registered for country,
you must click on “View all users” button (1).
1
In order to view info about a user, you must click on its ID (2).
2
6
You will be able to view and manage user info (3).
3
7
Set user as country administrator
In order for user to use this console, you must add a “ecmr_admin” role for that user.
Open “Users” tab in left menu (1), click to the user ID (2).
1
2
1
Go to “Role Mappings” tab (3), click on “ecmr_admin” role (4) and click “Add selected” button (5).
3
4
5
8
If everything went successfully, then you should see on the screen next information:
Now this user is able to view this user management console of certain country (this example is EE
country, so this user with added role would be able to open this user management console).
9
Groups
General overview
As an example, there are few “sample” groups:
1
2
How to create a new group
Go to “Groups” tab (1). Select either “Business” or “Government” parent group (2) and click “New”
button (3).
1 3
2
NOTE! You must add lower level
groups that are either in “Business”
or “Government” parent group.
10
Write group display name (4) and click “Save” (5).
4
5
After clicking “Save” new tabs appears for the group (6).
6
11
Click to attributes tab (7).
7
As you see, there are not attributes about this group.
NOTE: You must add at least 4 attributes. Otherwise, users with this group will not be able to
add/update/view index via API.
attributes example description
authority_icd 0200 ISO 6523 ICD
organization_name Fitek EDI, UAB Participant business name
authority_id iso6523-actorid-upis Participant Identifier
organization_id 125677598 Participant business registration number
IMPORTANT: These attributes are used for certificate generation, so information must be
correct.
12
Add required attributes: add key (8), value (9) and click “Add” (10).
8 9
10
After adding all required attributes, you must click “save” button (11). Then this group can be assigned.
11
Base groups such as “Business” and “Government” has specific attributes that relates to DLT layer
information.
13
How to exit exist group
In order to edit/view group attributes, you must click on the group “Fitek” (1) and then click “edit”
button (2).
2
1
Every group has attributes (3) that contain specific information. For example, inner business group of
“Fitek” contains attributes that relates to organizational information about Fitek.
3
14
Assigning user to a group
Now you as admin must assign user to a group (otherwise this user cannot be used for API). Open
“Users” tab in left menu (1), click to the user ID (2).
1
2
Go to “Groups” tab (3) in user window. Click to the group, for example to “Fitek” (4) what you want
to add to user and click “Join” (5). Now this user can be used in API.
3
5
4
NOTE! Single user can belong only to single group (even though it is
possible to add user to multiple groups, you should not do that. You
must leave user from all other groups if there are more than one
group assigned for user - otherwise the system will work incorrectly).
15
Remove user from group
Click to group, for example to “Fitek” (1) what you want remove and then click to button “Leave” (2).
2
1
16