A. General Information
1. Title
Information exchange of customs records-INDIRA system
2. Status of the project/service
3. Implementation period of the project/service:
6. Participating agencies/entities of the project/service:
a. Development stage
Lead agencies/entities
Customs administrations of MERCOSUR Member states
Other participating agencies/entities
Customs administrations of MERCOSUR Member states
b. Operational stage
Lead agencies/entities (op)
Customs administrations of MERCOSUR Member states
Other participating agencies/entities (op)
Customs administrations of MERCOSUR Member states
7. Main stakeholders/beneficiaries of the project/services
8. Business process category of the project/service
Regulatory/official control
B. Lessons Learned
9. Summary description of the project/service
a. Objective(s)
Mercosur countries made a decision to create platform to exchange information on customs records. The system accomplish certain requirements.
- It must not function as a periodic sending of records from one Customs Administration to the others, because it implied great data volumes that in most of the cases were not used by anybody
- To solve the previous problem, data should be interchanged when the requiring Customs Administration need them.
- Queries should run on operating databases.
-There should be full access to the last 5 years records, because this is the time the law permits to take legal actions in Mercosur countries
The system was called INDIRA (Information exchange of customs record in Spainish).
b. Business need for the project/service (background)
To preventing illicit actions by obtaining information that supports the control of foreign trade operations.
c. Business process covered*
Confidential data, protected by IT and for customs use only
Information exchange on exports and imports
Different methods of consultation for one customs declaration.
The interchanged data can be used by each of the State Members of MERCOSUR. With the information, each Member can generate transport documents and customs declarations.
d. Overall architecture and functionalities*
For more detail refer to the link: http://www.wcoomd.org/-/media/wco/public/global/pdf/topics/facilitation/activities-and-programmes/gnc/gnc-repository/gnc-utility-block-_-indira-system-_-v7_0.pdf
Communication model is the following:
e. Relevant document/figure
--
10. Documents and data exchanged via the project/service
Import/Export declarations between customs administrations
11. Data models/databases, proprietary solutions, hybrid approaches
--
12. Main challenges faced during the project/service
--
13. Lessons learned from the project/service
--
14. Main benefit(s) of the project/service
Enhanced regulatory compliance*
Simplified process
14A. Elaborations/detailed description on benefits gained:
The simplicity to obtain data from another countries customs administration
Improvement in control routines
Improvement in enforcement tasks
Simpler and faster customs investigations
Improvement of transparency of customs actions
15. Technical/financial/capacity building/other assistance
--
16. Future plan for expansion of the project and service
INDIRA system is an open system, there are no restrictions in its use, it can be adopted by other administrations other than Mercosur members (like Chile and Bolivia).
17. Other information or relevant references on the project and service
--
18. Relevant document regarding the project/service
--
C. Relevant Standards
19. Name(s) of any international, national legal instrument underpinning the project/service
• Mercosur Legislation – Decision of the Council of the Common Market Number 1/08 (CMC).
• COMALEP AGREEMENT "Multilateral Agreement of Mutual Cooperation and Assistance between the Customs Administrations of Latin America, Spain and Portugal"
• Bilateral Agreements
20. Electronic message standard
20A. Electronic message standard supporting the project/service:
--
20B. Type of standard for electronic message applied for the project/service
--
21. Technical communication standard
21A. Technical communication standard supporting the project/service
--
21B. Type of technical communication standard applied for the project/service
--
22. Security-related standards*
22A. Security-related standard supporting the project/service
VPN (Virtual Private Network)
22B. Type of security-related standard applied for the project/service
--
23. Other Technical Information
23A. Interface developed for data exchange with an internal system
--
23B. Other technical implementation information
--
