Customs Declaration Processing System Detailed User and ...
Customs Declaration Processing System Detailed User and ...
Customs Declaration Processing System Detailed User and ...
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />
AND USE-CASE MODELS<br />
Ref: PHASE V<br />
Number<br />
AR-0000<br />
AR-0010<br />
AR-0020<br />
AR-0030<br />
AR-0040<br />
AR-0050<br />
AR-0060<br />
AR-0070<br />
AR-0080<br />
AR-0090<br />
AR-0100<br />
AR-0110<br />
AR-0120<br />
Description<br />
In case CDPS fails or is shut down for maintenance, incoming messages must be<br />
queued.<br />
Immediate fallback to manual procedures is required for high-priority messages<br />
during CDPS downtime.<br />
MCA is responsible for providing the availability of the National network<br />
covering redundancy, resilience, recovery <strong>and</strong> performance aspects (according to<br />
the chosen availability level).<br />
It is recommended that a backup machine for the CDPS should be available for<br />
manual switching.<br />
It is recommended that all servers be protected against power failure<br />
(Uninterruptible Power Supply).<br />
CDPS must operate during opening hours of all COs it serves. It must also<br />
operate outside those hours to carry out processes for which no intervention by<br />
<strong>Customs</strong> Officers is required.<br />
The system should support at least 1000 simultaneous active user sessions (the<br />
number is based on the average number of customs officers at work at the same<br />
time <strong>and</strong> one third of the companies involved in the customs declaration<br />
process). It is required that the number of active session can be changed by<br />
means of a configurable parameter.<br />
CDPS data should be backed up daily, weekly <strong>and</strong> monthly. Data backups<br />
should be stored in a separate location at least 30 kms from the CDPS servers.<br />
CDPS must provide the capability for back up <strong>and</strong> recovery of data such that the<br />
back up operation can be either manually initiated by operations support staff or<br />
automatically performed at regular pre-determined basis as specified by the<br />
operation support staff.<br />
Data older than 5 years should be archived in a different database or different<br />
database scheme. MCA should have access to this data through the different<br />
reports included in CDPS.<br />
The system must be deployed on load balanced server architecture. There should<br />
be possibility for shutting down a server for maintenance reasons <strong>and</strong> in the same<br />
time to keep the system fully operational.<br />
The deployment architecture must be designed <strong>and</strong> managed so as to ensure<br />
continuity of service.<br />
Controls must exist to limit the impact of a Denial of Service attack mounted<br />
against any of the system resources.<br />
Table 8: General requirements for fallback <strong>and</strong> availability<br />
5.2.4.2.1Common Domain Specific Requirements<br />
This chapter provides the additional fallback <strong>and</strong> availability requirements for CDPS related to<br />
Common Domain. These requirements will need to be satisfied prior to the accession of Macedonia<br />
to EU.<br />
Number Description<br />
AR-0005 In case CDPS fails or is shut down for maintenance, incoming messages must be<br />
queued. The CCN Gateway must queue the Common Domain messages.<br />
AR-0130 In the event that it is known that an NCA is unavailable, all messages to be sent<br />
to that NCA will be stored on the CCN Gateway of the MCA or in CDPS.<br />
AR-0140 MCA is responsible for defining rules <strong>and</strong> conditions for the message exchange<br />
Page 138/276
Change language