Customs Declaration Processing System Detailed User and ...
Customs Declaration Processing System Detailed User and ...
Customs Declaration Processing System Detailed User and ...
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS<br />
AND USE-CASE MODELS<br />
Ref: PHASE V<br />
Number<br />
GR-2000<br />
GR-2010<br />
GR-2020<br />
GR-2030<br />
Description<br />
CDPS has to support the existence of at least four environments:<br />
• One production environment<br />
• One test environment<br />
• One training environment<br />
• One conformance testing environment<br />
The production, test, training, <strong>and</strong> conformance testing environments must be<br />
logically disjoint. It is strongly advised that the production, test, training, <strong>and</strong><br />
conformance testing environments are physically disjoint.<br />
Test application <strong>and</strong> data, training application <strong>and</strong> data, conformance testing<br />
application <strong>and</strong> data, <strong>and</strong> production application <strong>and</strong> data must be separated<br />
from each other.<br />
It has to be possible to switch between the production, testing, training, <strong>and</strong><br />
conformance testing context.<br />
Table 5: General requirements for Operation Modes<br />
5.2.3 Globalisation <strong>and</strong> Localisation<br />
The requirements for globalisation, localisation, regional settings, <strong>and</strong> Unicode support are given in<br />
this section. The character sets <strong>and</strong> the Data Item conventions for e<strong>Customs</strong> systems that are<br />
defined explicitly in [A01], [A02], [A03], <strong>and</strong> [A04] are applicable to CDPS.<br />
Number<br />
GR-3000<br />
GR-3010<br />
GR-3020<br />
Description<br />
<strong>User</strong> interface must be in Macedonian language<br />
CDPS must support date, time, currency <strong>and</strong> number format, <strong>and</strong> other regional<br />
<strong>and</strong> cultural conventions in Republic of Macedonia<br />
CDPS has to support UTF-8 for XML messages.<br />
Table 6: General requirements for Regional Support.<br />
5.2.3.1 Common Domain<br />
Additionally, following requirements have to be satisfied regarding the connection to the Common<br />
Domain.<br />
GR-3030 CDPS has to support only UNOC as the default character set in all data-items<br />
(non-language sensitive text fields <strong>and</strong> numeric fields) in EDIFACT messages.<br />
GR-3040 CDPS has to support UNOC, UNOD or UNOF as the character set in all<br />
language-sensitive text fields in EDIFACT messages or UTF-8 for XML<br />
messages.<br />
GR-3050 CDPS has to be able to convert (transliterate) the character sets of the EDIFACT<br />
messages (namely UNOC, UNOD <strong>and</strong> UNOF) or XML messages (UTF-8) into<br />
the character set(s) used internally in CDPS.<br />
Table 7: Regional Support requirements related to Common Domain.<br />
5.2.4 Fallback <strong>and</strong> availability<br />
5.2.4.1 Overview<br />
There are three methods to increase the availability <strong>and</strong> reliability of CDPS<br />
• Redundant communication lines: In [R17] we suggested that for reliability reasons in the<br />
future all Regional <strong>Customs</strong> Offices, Inl<strong>and</strong> <strong>Customs</strong> Office, <strong>and</strong> Border Crossing Offices are<br />
given broadb<strong>and</strong> access to the Internet via two communication links from two independent<br />
Page 136/276
Change language