Customs Declaration Processing System Detailed User and ...

More documents

Recommendations

Info

DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS AND USE-CASE MODELS Ref: PHASE V - Where information is exchanged electronically, the Accounting management system sub-application will send via the Guarantee management sub-application a response message to the trader indicating that duties cannot be deferred due to insufficient credit. The trader would normally be able to submit a request for information concerning the deferred account balance or a statement of the account. - When the duty becomes payable, the total amounts owed by each approved trader together with their bank account details (account number, branch sort code, etc.) should be transferred to the relevant bank. The question of agreement between Macedonian customs authorities and the banks on the information exchange standard and the medium (EDI, Internet, etc.) will need to be addressed. International standard messages designed for use in the EDI environment are available for the transmission of payment information. 5. TECHNICAL REQUIREMENTS 5.1 Introduction of concept and architecture The logical architecture of CDPS is with multiple tiers. It requires no client installation thus reducing the total cost of ownership. Such architecture works in various application scenarios and deployment patterns. Consequently, the same CDPS application can be deployed in different environments such as production, testing, training and conformance testing environments. We recommend the use of a Centralised data repository. Recommended multi-tier logical architecture offers the following benefits: Logically organized code; Easier maintenance; Better reuse of code; Better team development experience; Higher clarity in coding; Manageability and maintainability; Works in various application scenarios and deployment patterns; Decoupled Presentation and Business Logic facilitating scalability; Separate interface and business logic components allowing manageable and maintainable interfaces with external entities; The business logic in the Business Tier can be wrapped in a number of web services and thus made available to external clients; Addresses security considerations from the start and in-depth. More details on the proposed technical architecture can be found in the document “Customs Declaration Processing System: Functional and Technical Architecture”. Requirements related to the Common Domain are of lower priority compared to the requirements related to the National and External Domain. Implementation of the Common Domain requirements can be postponed until prior to the accession of Macedonia to EU. 5.2 General Technical Requirements This section provides an overview of the general technical requirements that have to be met by every software application which is part of CDPS. 5.2.1 Networking Requirements This chapter provides the networking requirements for the CDPS whether it is developed, customised or a combination of both. Number Description NR-0000 The communication network(s) has to be sized by MCA and CDPS vendor to ensure the communication between HQ and BCOs and to meet the national performance requirements. NR-0001 The connection between the External Domain and the CDPS is recommended to be a direct connection (e.g. through direct line), or to use strong encryption and authentication mechanism e.g. VPN through IPSec. Page 134/276
DETAILED USER & TECHNICAL REQUIREMENTS FOR CDPS AND USE-CASE MODELS Ref: PHASE V Number NR-0002 Description All Regional Customs Offices, Inland Customs Office, and Border Crossing Offices must be connected to the Internet via two communication links from two independent Internet providers Table 3: General networking requirements 5.2.1.1 Common Domain Additionally, following requirements have to be satisfied regarding the connection to the Common Domain. Number Description GR-0010 MCA has to be connected to only one operational CCN Gateway in order to ensure a connection with CCN. It might be possible for MCA to foresee several operational Gateways for performance reasons. However, only one address should be used to point to the Gateways. GR-0020 CSI protocol has to be used for the business-to-business exchange of all messages. GR-0030 GR-0040 GR-0050 GR-0060 GR-0080 GR-0090 GR-0100 GR-0110 GR-0120 GR-0130 The hardware for installation of the CCN Gateway has to be provided by the EC. MCA can provide the national configuration information to the CCN Technical Centre (CCN/TC) for the generation and installation of the CCN Gateway installation files. The necessary network infrastructure has to be provided to ensure the communication between the CCN Gateway and the CDPS The connection between the CCN Gateway and the CDPS is recommended to be a direct connection (e.g. through LAN or direct line), or to use strong authentication CSI security services in order for the CDPS platform to be considered as trusted. When connected to the Common Domain Network, MCA must provide one network address (IP address) to the CCN Technical Centre (CCN/TC) and must conform to the logical address specification as defined in [A01], [A02], [A03], and [A04]. A National Administration developing an NDCA has to obtain the CSI stack and CSI APIs. These can be obtained from CCN/TC. A Backup ISDN connection to the CCN network, provided by CCN/TC, has to be available. A Backup CCN Gateway has to be online and connected to the LAN (in order to receive the replication and synchronisation updates of the X.500 Directory) and available for manual switching. Every CCN Gateway has to be configured per MCA’s configuration files. Every CCN Gateway has to be configured to automatically send daily technical statistics on the Information Exchanges handled. This has to be in line with the specifications defined in [A01], [A02], [A03], and [A04]. Table 4: Networking requirements for Common Domain 5.2.2 Modes of operation Information Exchanges can be performed for several reasons, namely for operational purposes, test purposes or training purposes. Number Description Page 135/276
Page 1 and 2:
DETAILED USER & TECHNICAL REQUIREME
Page 3 and 4:
Page 5 and 6:
Page 7 and 8:
Page 9 and 10:
Page 11 and 12:
Page 13 and 14:
Page 15 and 16:
Page 17 and 18:
Page 19 and 20:
Page 21 and 22:
Page 23 and 24:
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
Page 43 and 44:
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84: DETAILED USER & TECHNICAL REQUIREME
Page 133: DETAILED USER & TECHNICAL REQUIREME
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
Page 191 and 192:
Page 193 and 194:
Page 195 and 196:
Page 197 and 198:
Page 199 and 200:
Page 201 and 202:
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
Page 209 and 210:
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
Page 223 and 224:
Page 225 and 226:
Page 227 and 228:
Page 229 and 230:
Page 231 and 232:
Page 233 and 234:
Page 235 and 236:
Page 237 and 238:
Page 239 and 240:
Page 241 and 242:
Annex 6 NCTS - Reference Data Annex
Page 243 and 244:
Annex 6 NCTS - Reference Data AGREE
Page 245 and 246:
Annex 6 NCTS - Reference Data 4 = O
Page 247 and 248:
Annex 6 NCTS - Reference Data G09 =
Page 249 and 250:
Annex 6 NCTS - Reference Data REC =
Page 251 and 252:
Annex 6 NCTS - Reference Data C06 C
Page 253 and 254:
Annex 7 AES - Reference Data Annex
Page 255 and 256:
Annex 7 AES - Reference Data - Comb
Page 257 and 258:
Annex 7 AES - Reference Data Common
Page 259 and 260:
Annex 7 AES - Reference Data METHOD
Page 261 and 262:
Annex 7 AES - Reference Data Road l
Page 263 and 264:
Annex 7 AES - Reference Data 31 40
Page 265 and 266:
Annex 7 AES - Reference Data STORIN
Page 267 and 268:
Annex 7 AES - Reference Data WAREHO
Page 269 and 270:
Annex 8 AIS - Reference Data NAME F
Page 271 and 272:
Annex 8 AIS - Reference Data X = Co
Page 273 and 274:
Annex 8 AIS - Reference Data B: Com
Page 275 and 276:
Annex 8 AIS - Reference Data UN DAN
show all

Customs Declaration Processing System Detailed User and ...

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?