Second SEED Workshop

SEED Phase 2

Plan of Activities

IMPLEMENTATION SCHEDULE

DESIGN DOCUMENTATION FOR THE SEED PHASE 2

• Technical Specifications for the Phase 2;• Critical line of the Project• The aim of documentation:

- Detail instructions for creation of XML files; - Explanation of structure of SEED Messages generated from national CDPS and uploaded to the local SEED Node;

• Documentation has dual purpose: - Clearly describes requirements that each BA shall fulfill to feed SEED system with necessary data (Bas that have outsource partners may use it for definition of the “technical request”);- Defines inputs on which basis SEED Team shall develop system with all functionalities requested by Project Documentation;

XML FILES – KEY EVENTS

Generation of the XML file from the CDPS:

• START: Beginning of Customs Procedure;

• EXIT: Leaving of the customs territory of the customs administration of departure / transit;

• ENTRY: Entering to the customs territory of the customs administration of destination / transit.

STRUCTURE OF XML FILES

Number and Structure of the XML files:

• Transit Messages: NCTS IE001/IE015;

• Export Messages: ECS IE501;

• Import Messages: ICS IE729/IE815.

• TIR Messages: UNECE e-TIR

UNIQUE REFERENCE NUMBER

• Required for the reliable AUTOMATIC data matching;• Generation of the URN:

- Option 1: Changes of the National CDPS;- Option 2: From data already available in databases;

• Structure of the URN:- Pre-face (SEED, CIL, etc.) - Customs Station Code (of the exit BCP);- Truck number plates (without special characters)- Date of Exit;

• Procedures on EXIT border: - Printing of URN and providing truck driver with it;

• Procedures on Entry Border;- Inclusion of URN in one of declaration data fields (e.g. Box 44)

ARCHITECTURE

SEED as CEMCM

• SEED should accomplish CEMCM (Customs External Messaging Module) requirements as foreseen by the European Commission

SEED Node

CANDIDATE COUNTRY A CANDIDATE COUNTRY B

COPIS READYMESSAGEFORMAT

CCN/CSIGW

CCN/CSIGW

COMMON DOMAIN

COMMON DOMAIN

SEEDCOMMUNICATION

CHANNELMSY

MSX

• From SPEED to SPEED 2

• Interviews with Member States for changes of CCN GW

• Web Services

EC – Coming Activities

The current SPEED:• Used by one country (Russia)• Legacy/Proprietary protocols (MQ)

SPEED2:• Many countries • CCN/CSI, MQ and the open

protocols (HTTP/SOAP, SFTP, SMTP/POP, AS1,AS2,AS3 …)

• Scalability• Cost reduction• Security (application level and

message level security…)• Configurability and flexibility• ESB external communication

platformSPEEDNET

CCN

IBM P550 – AIX1 Proc 2-cores

WMQWMB

IBM P550 – AIX1 Proc 2-cores

WMQWMB

Gateway CCN

NAGateway CCN

SPEED-BRIDGESlave Node

TC NA

MQ-MCA on SSL

CCN-CSI protocol

SPEED-BRIDGEMaster Node

WDP XB60

SOAP on HTTPS (WS)FTP on SSH (SFTP)SMTP/POP on SSL

AS1, AS2, AS3

MQISPEED2

SPEED2

SPEED 2

WS-CSI is to add a CSI compatible Web Services interface offered by CCN Gateways.

• HTTP/SOAP• limited to the CSI

operations (‘verbs’) CALL, PUT, GET, BROWSE, DELETE

• Message size <1MB• Synchronous traffic

Today: Business Case

Web Service CSI stack

• Automatic matching of data

Automatic reconciliation of customs declarations data sent from the border office of exit (custom administration of departure) with data declared at the entrance (at the neigbour BCP, customs administration of arrival);

• Exchange of pre-arrival data and risk analysis Exchange of data sent at the moment of starting of the customs procedure (early announcement). Risk Analysis (including alarming module) on SEED System or import to domestic CDPS;

SEED Phase 2 - OBJECTIVES

A B

CS ofExit

Trader

Export

SAD

Mainframe

XML

Trader

Mainframe

CS ofEntry

TRANSFORMATION XML

CS ofDeparture

CS ofDestination

Export

SAD

SEED

Pre Arrival

SEED

Exit

Transit

SAD

SEEDEntry

Transit

SAD

SEED Phase 2 – The Main Scenario

• START – Common Agreement from Previous Workshops:- User Requirements; - Functional Specifications ; - Main Scenario;

• Proposal: - Customs Administration of Albania;- Communication Node / New Scenarios / Use Cases;

• Discussion: - Question 1: Do you agree in principle with new Scenarios?- Question 2: Can your Administration follow each of Scenarios?

• END – Update of Documentation: - COMMON AGREEMENT: Inclusion into the UR and/or FS;- PARTIAL AGREEMENT: Scenario will be followed only on bilateral basis;

HOW WE WILL WORK TODAY?

• TODAY WE ARE PUTTING “FULL STOP” ON CHANGES OF:

- User Requirements; - Functional Specifications;

• FOLLOWING THIS WORKSHOP PROJECT TEAM AND BAs ARE SPEEDING UP DEVELOPMENT AND DEPLOYMENT;

• NEXT REGIONAL EVENTS WILL BE DESIGNATED TO THE IMPLEMENTATION OF THE SEED PHASE 2;

CONCLUSION

THANK YOU FOR YOUR ATTENTION!

OPPENING OF DISCUSSION

Fadil BelkoFadil.Belko@eu-seed.net

+387 61 136 207

Vladimir ObucinaVladimir.Obucina@eu-seed.net

+381 63 224 569