lxr.ICS provides the back-end business services answering Import Control System (ICS) requirements. ICS includes the exchange of electronic entry summary declarations and risk information based on Regulation (EC) 648/2005 of the European Parliament and of the Council and Commission Regulation (EC) 1875/2006 which contains its implementing provisions. ICS is also intended for offering additional services related to the external domain in import clearance. These include dialogues between offices of import and entry, which paves the way for the implementation of the centralised clearance concept, both under the current and the Union Customs Code (UCC) (which is expected to enter into legal effect on 1st May 2016.
To ease the deployment and integration of ICS back-end services within the national Customs authority infrastructure (e.g. ESB) while offering the maximal agility to align the IT to business evolutions, the lxr.ICS is organised around three distinct layers:
lxr.ICS Orchestration Service Layer that flexibly orchestrates the various ICS business processes as part of a wider collaboration by all actors of the Import business.
lxr.ICS Business Service Layer that implements the various services offering the required ICS capabilities. Those services are decomposed into “task-centric” services specific to the ICS business and “entity-centric” services which may be re-used by other processes, knowing that (according to the adopted SOA patterns) all of those services are loosely-coupled, autonomous, stateless, discoverable, and re-composable. Optionally, task-centric services implementing specific national requirements may be added at integration time and related business processes making use of them be recomposed accordingly.
lxr.ICS Business Application Layer which implements low-level utility services, which in general are shared by multiple back-end services. It may concern for example the services offered by lxr.CCN (multi-application software connector for CCN/CSI) to send/receive messages to/from CCN/CSI.
lxr.ICS core features are provided in support to the EC DG TAXUD AIS/ICS requirements. The objective of the Automated Import System (AIS) is to ensure that import operations starting in one Member State can be completed in another Member State without re-submission of the same information. This includes the exchange of electronic messages related to the different stages of the operations amongst the various actors (Customs, Traders, Trader’s representative and other governmental administrations).
Based on the Regulation (EC) no 648/2005 (the so-called “security amendment” to the Community Customs Code) and the implementing provisions (Commission Regulation (EC) N° 1875/2006 of 18 December 2006) including the provisions of Annex 30A describing the data elements to be presented and processed, and the Art. 40 of the Customs Code, the following business processes have to be implemented:
The following BPMN diagram depicts the interactions between the involved actors in the context of those business processes. The blue arrows highlight the exchanges in the Common Domain of Responsibility.
Only the National Domain BPMN pools are implemented by lxr.ICS through the delivery of BPEL-based orchestrated services, according to the specified use cases.
The current release of lxr.ICS (v1.x) provides the features answering the EC DG TAXUD AIS/ICS Phase 1 project requirements as specified in the EC DG TAXUD scope document. ICS Phase 1 is the first phase towards the AIS. It includes strictly what is needed to implement Regulation 648/2005 and its Implementing Provisions (Regulation 1875/2006). It is based on the processing of the Entry Summary Declaration (ENS) at Office of Lodgement, at Office of First Entry (including international diversion) and at any Office of Subsequent Entry, whether or not declared in the ENS.
Pre-Arrival Notification (PAN) is excluded from the ICS Phase 1 based on the recommendation of the Joint Informal Workshop of the Electronic Customs Group and the Customs Code Committee – General Customs Rules with a view to pursue the deletion of the legal basis of the PAN.
The following table depicts the ICS use cases (see also the Functional Import System Specifications (FISS) – FTSS-AIS Addendum 1/2006 – v6.2) according to the planned deployment phases and the lxr.ICS v1.x coverage.
|CO1A||Process Entry Summary Declaration at Office of Lodgement||X (1)|
|CO1B||Process Entry Summary Declaration at Office of first Entry||X (1)|
|CO1C||Process Entry Summary Declaration at Office of subsequent Entry||X (1)|
|CO1D||Process international diversion at office of first entry||X|
|CO3A||Presentation at Actual Office of first Entry||X (2)|
|CO3B||Presentation at Actual Office of subsequent Entry||X (2)|
|CO3C||Release for Entry at Actual Office of Entry||X (2)|
(1) Does not include the risk analysis processing itself. Only the interoperability with an existing national risk analysis system is provided.
(2) ENS Inquiry only (IE302/IE303)