Hiring a company to model a solution for the automation of customs control of exports by road – Chuí use case (10th RF)

Description

The Inter-American Development Bank (IDB) calls on specialized consulting firms to carry out the process mapping and functional specification of a customs automation technology solution. The focus of the project is the flow of traffic and exports by road in the Chuí region (10th Fiscal Region), using real-time data captured by the ARGOS system to reduce or eliminate mandatory physical stops.

1. Technical design and scope of the solution (Middle Layer)
Intelligent Integration Agent: Model an intermediate software layer that functions as an intelligent interpreter of ARGOS system events (position, weight, vehicle identity, and load status).

Systemic autonomy: The solution must perform autonomous actions on existing transactional systems (such as registering arrivals, updating status, issuing notifications, and releasing transits) without requiring any modification to the structure or internal logic of these systems.

Manual intervention replacement: Eliminate the need for physical logistics stops currently required only for bureaucratic customs control purposes, replacing human action with automated data validations.

2. Key Activities (AS-IS and TO-BE Mapping)
Current flow diagnosis (AS-IS): Survey and document in detail the current road customs flow from the beginning of the transit to the departure of the national territory. The firm must record the average duration of mandatory stops, the logistical impact and the data already captured by ARGOS.

Future Flow Redesign (TO-BE): Elaborate on the reformulated flow by highlighting how real-time data will replace manual checks. For each bottleneck identified in the AS-IS, the consultancy should professionally propose an automated elimination, reduction, or substitution approach.

Trigger mapping: Document the future interactions of the middle layer with transactional systems, specifying operational triggers, the volume of data trafficked, and expected systemic responses.

3. Functional specification and design assumptions
Reference architecture: Develop a functional reference architecture proposal for the future deployment of the automation layer in a production environment, ensuring minimal operational impact.

Technical Risk Mitigation: Identify infrastructure dependencies, operational network constraints at the border, and systems integration risks, providing clear mitigation recommendations.

Premise of replicability: Ensure that all technical specifications, business rules and activation conditions designed for the case of Chuí serve as a reusable and replicable functional basis for other Fiscal Regions of the country.

Note: Interested companies should review the requirements on the BEO Bidder Portal.