Single Window Systems
In the OIC Member States
74
architecture. It hosts the agencies application with a taxonomy engine that cover end-to-end
business process needs.
The e-GUCE centralized architecture is designed to cover end-to-end (E2E) business process
integration. The strong E2E taxonomy of the e-GUCE architecture is based on nodes that are
organized into four layers: the upper tier web servers, middle application and business nodes
and the lower tier common data integration layer. The single common data layer and the
taxonomy provide more efficient data sharing among agencies and simplification of data
processing.
Interconnectivity and Interoperability
The e-GUCE presents an interoperable model of regulatory, procedural and business processes
and requirements. A “AS-IS” Business Process Analysis was performed in 2014 prior to
designing the new generation architecture and its “TO-BE” business processes. This approach
provided a dynamic integration of the different regulatory and business models applied in e-
GUCE at the planning and design stage and enhanced the ability to interconnect and
interoperate. The interoperability with ASYCUDA ++ is limited for technical reasons. Regarding
the network capacity, e-GUCE has two fibre optic hubs for connection with the agencies and
customs services that have enough capacity to support the network connectivity requirements.
Integration at Data Level / Application Level
The operational data reside on a common mirrored storage system that provides data
integration and application processing in real time. The e-GUCE is based on a centralised ICT
Architecture for data submission and processing. The Extract, Transform and Load (ETL)
function is used to transform and prepare data in data warehouse for analysis and reporting
services. This process converts the extracted data into a desired form for the presentation
layer. e-GUCE is combining operational data from heterogeneous data sources (Port system,
ASYCUDA++, etc.), but they are not using it for reporting and analysis services in order to
monitor the overall system performances.
Business Continuity / Disaster Recovery
A Business Continuity (BC) and Disaster Recovery (DR) Plan have been developed as a part of
the IT policies. The BC and DR infrastructure consist of two backup sites, fully mirrored with
load balancing. The DR match appropriately with the criticality of the SW business functions,
meaning that the first restoration is on the critical services and then the “less” important
services are restored. The backup policy is according to highest standards and allows
restoration of services without interruption of processes. This is due to the mirrored
architecture of e-GUCE.