Project

A. General Information

1. Title

Uniform Automated Information System for electronic data exchange between Kyrgyzstan and Tajikistan

2. Status of the project
Operating
3. Implementation period of the project/service:
From
December 2002
To
Present
5. Geographical coverage
Bilateral
Participating countries: Kyrgyzstan, Tajikistan
6. Participating agencies/entities of the project/service:
a. Development stage
Lead agencies/entities
UN Economic Commission for Europe (cooperating agenciesESCAP, ESCWA, ECA, ECLAC) Asian Development Bank (Regional Customs Modernization and Infrastructure Development Project)
Other participating agencies/entities
--
b. Operational stage
Lead agencies/entities (op)
UN Economic Commission for Europe (cooperating agenciesESCAP, ESCWA, ECA, ECLAC) Asian Development Bank (Regional Customs Modernization and Infrastructure Development Project)
Other participating agencies/entities (op)
--
7. Main stakeholders/beneficiaries of the project
Traders (big enterprises)
Traders (SMEs)
Customs
8. Business process category of the project
Regulatory/official control

B. Lessons Learned

9. Summary description of the project/service
a. Objective(s)

With the financial assistance of ADB customs agencies in Tajikistan and Kyrgyzstan have launched Uniform Automated Information System. ADB has equipped customs agencies in the Kyrgyz Republic and Tajikistan with automated information systems. The customs service under the Government of the Republic of Tajikistan has its Uniform automated information system. This system is a reliable, secure data network, and includes the common infrastructure between the regional structural units of the Customs and the Central Office of the Customs Service providing user with access to central resources, including a central database and software. For the processing of data in transit, it has a subsystem UAIS Customs clearance and control. A system provides basic automation of customs procedures, customs clearance and control of goods and vehicles, control of delivery of goods and vehicles transported under customs supervision through the territory of the Republic of Tajikistan.

Kyrgyzstan has the similar UAIS launched in December 2012.

Based on provided technical standard information, Tajikistan and Kyrgyzstan have compatible technical platform for electronic data exchange between their customs agencies.

Tajikistan and Kyrgyzstan customs information systems have evolved to use web-based platforms to store, retrieve, and use data. Accessing information from a web-based application eliminates the issue of compatibility and ensures real time exchange of information. Electronic data exchange (EDE) between Tajikistan and Kyrgyzstan can also avoid systems compatibility issues by exchanging information using their web-based customs systems, as these countries have up-to-date, functional ICT systems.

b. Business need for the project (background)

To control high volume cross border operations, effectively exchange reliable information there was a need to exchange data between customs authorities through a common  Electronic Data Interchanges system.

c. Business process covered*

Customs services have their own Uniform automated information system (UAIS)

For data processing subsystem exists for customs registration and control

UAIS automatically provides data on registered TIR carnets in customs agencies

UAIS uses XML standard for data exchange.

d. Overall architecture and functionalities*

TIR-EPD application allows the following operations:

1. Create and send pre-declarations. These pre-declarations can be created by

a. entering all data for the first time, or b. using a previously sent pre-declaration as a template, thus minimizing data entry when the content of the new pre-declaration is similar to the one sent previously;

2. View messages from Customs concerning submitted pre-declarations;

3. Search and view previous and new messages;

4. Access EPDs dashboard to view sent and draft EPDs, new messages from Customs and EPDs, for which customs messages are anticipated but not yet received.

5. Receive e-mails at the address entered in your company profile with messages sent to- and received from- the customs.

6. View and print out EPDs sent to customs authorities.

7. Print out EPD pass for countries where EPD was submitted, for presenting it to customs authorities

8. Print out CMR based on the EPD information.

For more detail refer to:https://www.iru.org/system/files/TIR-EPD%20User%20Guide%20ENG.pdf

e. Relevant document/figure
--
10. Documents and data exchanged via the project

TIR_EPD (electronic pre-declaration)

11. Data models/databases, proprietary solutions, hybrid approaches
--
12. Main challenges faced during the project

The differences in UAIS systems used by both countries.

Technical difficulties in implementation stage.

13. Lessons learned from the project

Importance of having up to date ICT systems.

Considering using web based platforms. Accessing information from web based application eliminates the issue of compatibility and ensures real time exchange of information.

14. Main benefit(s) of the project
Enhanced regulatory compliance*
Transaction Cost savings*
Transaction Time savings
Simplified process
14A. Elaborations/detailed description on benefits gained
--
15. Technical/financial/capacity building/other assistance

USAID-funded training for the helpdesk team of the ADB-funded Customs Unified Automated Information System and participated .in the single window working group developing the single window concept.

GIZ funded preparation of technical specifications of the proposed single window system software, and preliminary business process analysis and training.

 

16. Future plan for expansion of the project

Scope of electronic data exchange

Decide on the type  and technical specifications for EDE.

17. Other information or relevant references on the project
--
18. Relevant document regarding the project
--

C. Relevant Standards

20. Electronic message standard
20A. Electronic message standard supporting the project
XML:
- WCO Data Model
20B. Type of standard for electronic message applied for the project
--
21. Technical communication standard
21A. Technical communication standard supporting the project
--
21B. Type of technical communication standard applied for the project
--
22. Security-related standards*
22A. Security-related standard supporting the project
--
22B. Type of security-related standard applied for the project
--
23. Other Technical Information
23A. Interface developed for data exchange with an internal system
--
23B. Other technical implementation information
--