Inventory Linking Exports Dual Running Solution
AM
Published · 30 slides · 0 views
1 / 1
Description
Inventory Linking Exports Dual Running Solution May 2019 Customs Declaration Service High level overview Agenda Customs Declaration Service Background CSP Solution Overview Contingency Solution Overview ILE Dual Running Solution Overview
Related Topics
Share
Embed code
Download this presentation From Below
"Inventory Linking Exports Dual Running Solution" is the property of its rightful owner. Permission is granted to download and print the materials on this website for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
Presentation Transcript
01
Inventory Linking Exports Dual Running Solution May 2019 Customs Declaration Service High level overview<br>
02
Agenda Customs Declaration Service Background
CSP Solution Overview
Contingency Solution Overview
ILE Dual Running Solution Overview
ILE Dual Running Solution In More Detail
Phase 1 ILE Dual Running Scenarios
Phase 2 ILE Dual Running Scenarios
Relevant CDS Release Timelines
To Summarise 2<br>
CSP Solution Overview
Contingency Solution Overview
ILE Dual Running Solution Overview
ILE Dual Running Solution In More Detail
Phase 1 ILE Dual Running Scenarios
Phase 2 ILE Dual Running Scenarios
Relevant CDS Release Timelines
To Summarise 2<br>
03
Background Customs Declaration Service Following several engagements and consultations, a big bang cut over was considered not suitable.
3 viable options were presented to the CSPs for their consideration (including their own):
Solution proposed by CSPs – Enables dual message processing of CHIEF and CDS movements and declarations, but consolidations required duplicate messages.
Contingency solution – Managed big bang by sector over a specified period of time
Optimum solution – Catered for movements, declarations and consolidations in both CHIEF and CDS.
The following slides will go into each of these in more detail but the Optimum solution was chosen and renamed the ILE dual running solution. 3<br>
3 viable options were presented to the CSPs for their consideration (including their own):
Solution proposed by CSPs – Enables dual message processing of CHIEF and CDS movements and declarations, but consolidations required duplicate messages.
Contingency solution – Managed big bang by sector over a specified period of time
Optimum solution – Catered for movements, declarations and consolidations in both CHIEF and CDS.
The following slides will go into each of these in more detail but the Optimum solution was chosen and renamed the ILE dual running solution. 3<br>
04
CSP Solution Overview (1/2) Customs Declaration Service CSPs recognise that any effective dual running solution requires them all to be able to handle both EDIFACT and CDS XML messages for declaration, consolidation and movement messages at a given point.
This gives SWDs a flexibility to roll out their software at a gradual and managed pace so that individual customers can use either CDS or CHIEF through any CSP controlled export location.
The proposal from the CSPs meant:
For an individual declaration, a CSP would be able to accept EDIFACT or XML messages and send to either CHIEF or CDS, as appropriate.
For an individual movement, a CSP would send XML messages and send to CDS only. A new component (Movement Message Aggregator - MMA) within DMS would communicate with CHIEF and process the movement message in both systems. A single aggregated XML response would be returned to the CSP.
For an individual consolidation, a CSP would be able to accept EDIFACT or XML messages and send to either CHIEF or CDS, as appropriate. 4<br>
This gives SWDs a flexibility to roll out their software at a gradual and managed pace so that individual customers can use either CDS or CHIEF through any CSP controlled export location.
The proposal from the CSPs meant:
For an individual declaration, a CSP would be able to accept EDIFACT or XML messages and send to either CHIEF or CDS, as appropriate.
For an individual movement, a CSP would send XML messages and send to CDS only. A new component (Movement Message Aggregator - MMA) within DMS would communicate with CHIEF and process the movement message in both systems. A single aggregated XML response would be returned to the CSP.
For an individual consolidation, a CSP would be able to accept EDIFACT or XML messages and send to either CHIEF or CDS, as appropriate. 4<br>
05
CSP Solution Overview (2/2) Risk:
If consolidations are sent to only one system, declarations present in the other system will not be risk assessed, arrived or departed
Impact:
There will be an increase in unauthorised loading offences as goods will physically leave the UK.
Unfinalised declarations will require manual post departure reconciliation.
Mitigation:
Consolidations must be sent to both CHIEF and CDS by either the CSPs or all SWDs who provide consolidation (DEPs) functionality. These systems must be able to handle responses from both systems.
Following external stakeholder engagement with both CSPs & SWDs, feedback suggests that there is a reluctance to make this temporary change, i.e. to support 2 messages concurrently, therefore this solution was discounted. Customs Declaration Service 5<br>
If consolidations are sent to only one system, declarations present in the other system will not be risk assessed, arrived or departed
Impact:
There will be an increase in unauthorised loading offences as goods will physically leave the UK.
Unfinalised declarations will require manual post departure reconciliation.
Mitigation:
Consolidations must be sent to both CHIEF and CDS by either the CSPs or all SWDs who provide consolidation (DEPs) functionality. These systems must be able to handle responses from both systems.
Following external stakeholder engagement with both CSPs & SWDs, feedback suggests that there is a reluctance to make this temporary change, i.e. to support 2 messages concurrently, therefore this solution was discounted. Customs Declaration Service 5<br>
06
Contingency solution Customs Declaration Service This was a managed migration approach tailored for each CSP but effectively a series of big bang cutovers.
DMS would already be operational
The same go-live date for all CSPs and SWDs
A preparation period (3-7 days), cutover day followed by a transition period (3 days)
CHIEF would be closed to the trade from the cutover point and all data migrated to CDS from CHIEF of “in-flight” declarations, consolidations and movements after this point.
The level of risk was considered too high by the CSPs, and therefore this solution was discounted. 6<br>
DMS would already be operational
The same go-live date for all CSPs and SWDs
A preparation period (3-7 days), cutover day followed by a transition period (3 days)
CHIEF would be closed to the trade from the cutover point and all data migrated to CDS from CHIEF of “in-flight” declarations, consolidations and movements after this point.
The level of risk was considered too high by the CSPs, and therefore this solution was discounted. 6<br>
07
ILE Dual Running Solution Overview (1/9) How does the ILE Dual Running Solution differ to the CSP Solution? The ILE Dual Running solution is an extension of the CSP solution whereby the proposed CDS MMA component is further developed to handle consolidation messages - CHIEF & DMS Aggregator (CDA). For this solution to work, consolidations need to be in XML format during phase 2. In principle, and for the benefit of their customers, CSPs have agreed to convert any incoming EDIFACT EAC and CST messages to XML and visa versa back to the originating source.
The added benefits are:
Dual message handling of consolidation messages therefore mitigating risk highlighted in the CSP solution slides.
No additional significant IT build effort for CSPs or SWDs
A phased implementation approach takes away all the risks associated to a big bang cutover.
Phase 1 allows CSPs to “test” the new CDA component and to gradually increase the volume of messages handled by CDS (stress testing)
Phase 2 provides flexibility for software developers and their customers who will benefit from a seamless transition to CDS.
Options for migrating selected supply chain traders per CSP Customs Declaration Service 7<br>
The added benefits are:
Dual message handling of consolidation messages therefore mitigating risk highlighted in the CSP solution slides.
No additional significant IT build effort for CSPs or SWDs
A phased implementation approach takes away all the risks associated to a big bang cutover.
Phase 1 allows CSPs to “test” the new CDA component and to gradually increase the volume of messages handled by CDS (stress testing)
Phase 2 provides flexibility for software developers and their customers who will benefit from a seamless transition to CDS.
Options for migrating selected supply chain traders per CSP Customs Declaration Service 7<br>
08
ILE Dual Running Solution Overview (2/9) Customs Declaration Service The implementation of Phase 2 of this solution will take place on a specific date once all the CSPs have indicated that they are ready to communicate using CDS XML messages or have a message translator in operation, but can continue to accept CHIEF EDIFACT messages for declarations only. This gives SWDs a flexibility to roll out their software at a gradual and managed pace so that individual customers can use either CDS or CHIEF (or both) through any CSP controlled export location
For an individual declaration, a CSP will be able to accept EDIFACT or XML messages and send to either CHIEF or CDS, as appropriate.
For all movement, a CSP will send XML messages (converting if required) and send to CDS only.
For all consolidation, a CSP will send XML messages (converting if required) and send to CDS only.
A new component (CDA – CHIEF and DMS Aggregator) within CDS has been built by HMRC.
This component will communicate with CHIEF and process consolidation and movement messages in both systems. A single aggregated XML response for the consolidation and/or movement will be returned to the CSP. 8<br>
For an individual declaration, a CSP will be able to accept EDIFACT or XML messages and send to either CHIEF or CDS, as appropriate.
For all movement, a CSP will send XML messages (converting if required) and send to CDS only.
For all consolidation, a CSP will send XML messages (converting if required) and send to CDS only.
A new component (CDA – CHIEF and DMS Aggregator) within CDS has been built by HMRC.
This component will communicate with CHIEF and process consolidation and movement messages in both systems. A single aggregated XML response for the consolidation and/or movement will be returned to the CSP. 8<br>
09
ILE Dual Running Solution Overview (3/9) Customs Declaration Service To reduce impact to the trade, a phased approach can be adopted by the individual CSPs:
There is a dependency on all CSPs being ready before Phase 2 can commence, this will facilitate SWDs with their software rollout in a manageable and flexible approach through any CSP controlled export location. Phase 1
Participating CSPs can start to send consolidation and movement messages to CDA
This phase is optional for CSPs but is considered highly desirable as it validates interfaces and volumetrics between CSPs and CDA.
SWDs will not be impacted in this phase.
Declarations will be in CHIEF only
If CSPs are joining this phase they must build a message translator, or should be CDS ready to send and receive consolidation/movement messages in XML format Phase 2
This phase will commence on a specific date when all CSPs are able to send consolidation, movement and XML declaration messages to CDS only.
Declarations can still be made in CHIEF.
Declaration can now be made in CDS.
SWDs can roll out their CDS software gradually Phase 3
CHIEF and CDA will be decommissioned on a specific date
All software and messaging will be CDS only 9<br>
There is a dependency on all CSPs being ready before Phase 2 can commence, this will facilitate SWDs with their software rollout in a manageable and flexible approach through any CSP controlled export location. Phase 1
Participating CSPs can start to send consolidation and movement messages to CDA
This phase is optional for CSPs but is considered highly desirable as it validates interfaces and volumetrics between CSPs and CDA.
SWDs will not be impacted in this phase.
Declarations will be in CHIEF only
If CSPs are joining this phase they must build a message translator, or should be CDS ready to send and receive consolidation/movement messages in XML format Phase 2
This phase will commence on a specific date when all CSPs are able to send consolidation, movement and XML declaration messages to CDS only.
Declarations can still be made in CHIEF.
Declaration can now be made in CDS.
SWDs can roll out their CDS software gradually Phase 3
CHIEF and CDA will be decommissioned on a specific date
All software and messaging will be CDS only 9<br>
10
ILE Dual Running Solution Overview (4/9) Technical Details Customs Declaration Service In phase 2 of this solution you can submit declarations in both CHIEF and CDS whilst all consolidations and movements will be handled by CDS only.
CDS consists of 2 core components:
Declaration Management System (DMS) – handles declarations
Inventory Linking Exports (ILE) – handles consolidations and movements
CDA is a temporary additional component to enable dual message processing between CHIEF and CDS ILE CDA CDS DMS CHIEF 10<br>
CDS consists of 2 core components:
Declaration Management System (DMS) – handles declarations
Inventory Linking Exports (ILE) – handles consolidations and movements
CDA is a temporary additional component to enable dual message processing between CHIEF and CDS ILE CDA CDS DMS CHIEF 10<br>
11
ILE Dual Running Solution Overview (5/9) Consolidations at DUCR level During phase 1, CSPs will be sending declarations to CHIEF only and participating CSPs will be sending EAC messages to CHIEF via CDS.
During phase 2, all CSPs will be sending EAC messages to CHIEF via CDS.
For EAC messages - CDA will initially query ILE (which is in sync with DMS) for the DUCR and receive either a positive or negative response back.
A positive response will result in the EAC message being sent to ILE where an ILE MUCR tree will be maintained.
A negative response will result in the EAC message being sent to CHIEF where a CHIEF MUCR tree will be maintained. Customs Declaration Service SWD CHIEF ILE CDA CDS DMS CSP Message translator Query Positive ILE query response Negative CHIEF query response Kept in sync EAC Key EDI XML Phase 2 (CSP with message translator) 11<br>
During phase 2, all CSPs will be sending EAC messages to CHIEF via CDS.
For EAC messages - CDA will initially query ILE (which is in sync with DMS) for the DUCR and receive either a positive or negative response back.
A positive response will result in the EAC message being sent to ILE where an ILE MUCR tree will be maintained.
A negative response will result in the EAC message being sent to CHIEF where a CHIEF MUCR tree will be maintained. Customs Declaration Service SWD CHIEF ILE CDA CDS DMS CSP Message translator Query Positive ILE query response Negative CHIEF query response Kept in sync EAC Key EDI XML Phase 2 (CSP with message translator) 11<br>
12
ILE Dual Running Solution Overview (6/9) Consolidations at MUCR Level During phase 1, CSPs will be sending declarations to CHIEF only and participating CSPs will be sending EAC messages to CHIEF via CDS.
During phase 2, all CSPs will be sending EAC messages to CHIEF via CDS.
For EAC messages - CDA will send to both systems.
Where the MUCR exists fully in one system, a new MUCR tree will be maintained. CDA will return an XML response and supress the negative response from the other system.
Where the MUCR exists partially in both systems, CDA will aggregate both responses and return a single response to the CSP.
CST messages - CDA will automatically send to both ILE and CHIEF. Customs Declaration Service SWD CHIEF ILE CDA CDS DMS CSP Message translator Kept in sync CST EAC Key EDI XML 12 Phase 2 (CSP with message translator)<br>
During phase 2, all CSPs will be sending EAC messages to CHIEF via CDS.
For EAC messages - CDA will send to both systems.
Where the MUCR exists fully in one system, a new MUCR tree will be maintained. CDA will return an XML response and supress the negative response from the other system.
Where the MUCR exists partially in both systems, CDA will aggregate both responses and return a single response to the CSP.
CST messages - CDA will automatically send to both ILE and CHIEF. Customs Declaration Service SWD CHIEF ILE CDA CDS DMS CSP Message translator Kept in sync CST EAC Key EDI XML 12 Phase 2 (CSP with message translator)<br>
13
During phase 1, participating CSPs can start sending some or all movement messages to CHIEF via CDA.
During phase 2, all CSPs will be sending all movement messages to CHIEF and ILE via CDA.
EAA, EAL and EDL messages at DUCR level, CDA will initially query ILE for the DUCR and receive either a positive or negative response back. Dependent on that response, the DUCR will be arrived or departed in the appropriate system.
Generated ERSs will be forwarded to the CSPs.
EAA and EAL messages for which no declaration is found on either system will result in CRC 101/102 codes being returned by CDA to CSPs and a ‘placeholder’ created on both systems. ILE Dual Running Solution Overview (7/9) Movements DUCR Customs Declaration Service DEP
(loader) CHIEF ILE CDA CDS DMS CSP Message translator Positive ILE query response Negative ILE query response Kept in sync EAA/EAL/EDL DUCR Key EDI XML Query Phase 2 13 XML CSP
(loader)<br>
During phase 2, all CSPs will be sending all movement messages to CHIEF and ILE via CDA.
EAA, EAL and EDL messages at DUCR level, CDA will initially query ILE for the DUCR and receive either a positive or negative response back. Dependent on that response, the DUCR will be arrived or departed in the appropriate system.
Generated ERSs will be forwarded to the CSPs.
EAA and EAL messages for which no declaration is found on either system will result in CRC 101/102 codes being returned by CDA to CSPs and a ‘placeholder’ created on both systems. ILE Dual Running Solution Overview (7/9) Movements DUCR Customs Declaration Service DEP
(loader) CHIEF ILE CDA CDS DMS CSP Message translator Positive ILE query response Negative ILE query response Kept in sync EAA/EAL/EDL DUCR Key EDI XML Query Phase 2 13 XML CSP
(loader)<br>
14
During phase 1, participating CSPs can start sending some or all movement messages to CHIEF via CDA.
During phase 2, all CSPs will be sending all movement messages to CHIEF and ILE via CDA.
EAA, EAL and EDL messages at MUCR level, CDA will automatically send to both ILE and CHIEF.
If a MUCR tree exists (in full or partially) in ILE, these DUCR’s will be arrived/departed. If a MUCR tree exists (in full or partially) in CHIEF, these DUCR’s will be arrived/departed.
In Phase 1, CDA will return generated EMRs from CHIEF to the CSPs.
In Phase 2, CDA will aggregate responses from both CHIEF and ILE and return a single response back to the CSP, integrating data from both MUCR trees if applicable.
EAA and EAL messages for which no declaration is found on either system will result in CRC 101/102 codes being returned by CDA to CSPs and a ‘placeholder’ created on both systems. ILE Dual Running Solution Overview (8/9) Movements MUCR Customs Declaration Service DEP/Airline
(loader) CHIEF ILE CDA CDS DMS CSP Message translator Kept in sync EAA/EAL/EDL MUCR Key EDI XML 14 Phase 2 CSP
(loader)<br>
During phase 2, all CSPs will be sending all movement messages to CHIEF and ILE via CDA.
EAA, EAL and EDL messages at MUCR level, CDA will automatically send to both ILE and CHIEF.
If a MUCR tree exists (in full or partially) in ILE, these DUCR’s will be arrived/departed. If a MUCR tree exists (in full or partially) in CHIEF, these DUCR’s will be arrived/departed.
In Phase 1, CDA will return generated EMRs from CHIEF to the CSPs.
In Phase 2, CDA will aggregate responses from both CHIEF and ILE and return a single response back to the CSP, integrating data from both MUCR trees if applicable.
EAA and EAL messages for which no declaration is found on either system will result in CRC 101/102 codes being returned by CDA to CSPs and a ‘placeholder’ created on both systems. ILE Dual Running Solution Overview (8/9) Movements MUCR Customs Declaration Service DEP/Airline
(loader) CHIEF ILE CDA CDS DMS CSP Message translator Kept in sync EAA/EAL/EDL MUCR Key EDI XML 14 Phase 2 CSP
(loader)<br>
15
In Phase 2, CDA will aggregate responses from both CHIEF and ILE and return a single response back to the CSP, integrating data from both MUCR trees if applicable. If one or more DUCRs do not receive clearance (P2P), CDA will return the most restrictive status for the MUCR until all DUCRs are cleared.
If a MUCR tree exists partially in both systems, and a DUCR has been held on one system – on clearance, CDA will receive an EMR update from that system and will match it with the previous EMR from the other system before aggregating both responses and returning a single one.
The example below shows a MUCR consolidation – partially maintained in ILE (DUCR 1 and DUCR 2) and CHIEF (DUCR 3 and 4).
DUCRs 1 and 3 were held on arrival of MUCR.
DUCR 1 is subsequently cleared.
Dependant on the Master Opt in the original movement message, ILE sends CDA an updated EMR and ERS. CDA recalls that part of the MUCR is maintained in CHIEF and will find the last EMR from CHIEF. CDA will aggregate the two EMRs and return a single response. ILE Dual Running Solution Overview (9/9) Held MUCRs (mixed consolidations) Customs Declaration Service CHIEF CSP 15 MUCR A DUCR 1 DUCR 2 MUCR A DUCR 3 DUCR 4 MUCR A DUCR 3 DUCR 4 DUCR 1 DUCR 2 CDA ILE MUCR A DUCR 4 DUCR 1 DUCR 2 DUCR 3<br>
If a MUCR tree exists partially in both systems, and a DUCR has been held on one system – on clearance, CDA will receive an EMR update from that system and will match it with the previous EMR from the other system before aggregating both responses and returning a single one.
The example below shows a MUCR consolidation – partially maintained in ILE (DUCR 1 and DUCR 2) and CHIEF (DUCR 3 and 4).
DUCRs 1 and 3 were held on arrival of MUCR.
DUCR 1 is subsequently cleared.
Dependant on the Master Opt in the original movement message, ILE sends CDA an updated EMR and ERS. CDA recalls that part of the MUCR is maintained in CHIEF and will find the last EMR from CHIEF. CDA will aggregate the two EMRs and return a single response. ILE Dual Running Solution Overview (9/9) Held MUCRs (mixed consolidations) Customs Declaration Service CHIEF CSP 15 MUCR A DUCR 1 DUCR 2 MUCR A DUCR 3 DUCR 4 MUCR A DUCR 3 DUCR 4 DUCR 1 DUCR 2 CDA ILE MUCR A DUCR 4 DUCR 1 DUCR 2 DUCR 3<br>
16
Customs Declaration Service In the following slides we have tried to cover each type of SWD, as well as CSPs, and the various channels into CHIEF and CDS for declarations, consolidations and movements:
Existing Channels to CHIEF
New CDS Channels in Phase 1
New CDS Channels in Phase 2
Channels to CHIEF Phase 2
Phase 1: ILE Dual Running Scenarios
Phase 2: ILE Dual Running Scenarios The ILE Dual Running Solution In More Detail 16<br>
Existing Channels to CHIEF
New CDS Channels in Phase 1
New CDS Channels in Phase 2
Channels to CHIEF Phase 2
Phase 1: ILE Dual Running Scenarios
Phase 2: ILE Dual Running Scenarios The ILE Dual Running Solution In More Detail 16<br>
17
2. SWD route to CHIEF via EDCS XML, email 3. NES WEB route to CHIEF 4. Route to CHIEF via HCI screen ICAB ICAB 6. Route to CHIEF via CSP EDI 5. Route to CHIEF via HCI screen 1. Traders direct route to CHIEF via EDCS XML, email EDI EDI Declarations, Consolidations and Movements Existing Channels to CHIEF EDCS CHIEF EDI EDCS CHIEF CHIEF CHIEF CHIEF CSP CSP CHIEF In-house software Gov.uk CSP SWD SWD SWD Declarations, Consolidations and Movements Declarations and Consolidations Declaration and Consolidations Declarations, Consolidations and Movements Customs Declaration Service NES WEB ICAB ICAB Declarations, Consolidations and Movements EDI CHIEF CSP 7. CSP route to CHIEF 17 Declarations, Consolidations and Movements Declarations, Consolidations and Movements<br>
18
9. Route to CDS via CSP (participating in Phase 1) CDS Gov.uk XML EDI CSP CDS SWD XML CDS CSP 10. Route to CDS from CSP (participating in Phase 1) 8. Route to CDS via CDS UI (restricted to selected traders only) XML Customs Declaration Service Declarations, Consolidations and Movements Consolidations and Movements Consolidations and Movements Declarations, Consolidations and Movements New CDS Channels in Phase 1 11. Route to CDS via CSP XML XML CSP CDS SWD Declarations, Consolidations and Movements New CDS Channels in Phase 2 Declarations, Consolidations and Movements 13. SWD route to CDS XML 12. Traders direct route to CDS XML CDS CDS In-house software SWD Declaration and Consolidations Declaration and Consolidations 18 CHIEF CHIEF Consolidations and Movements Passing Through CDS to CHIEF in Phase 1 CHIEF CHIEF CHIEF CHIEF<br>
19
2. SWD route to CHIEF via EDCS 3. NES WEB route to CHIEF 4. Route to CHIEF via HCI screen 6. Route to CHIEF via CSP 5. Route to CHIEF via HCI screen 1. Traders direct route to CHIEF via EDCS Declarations, Consolidations and Movements Channels to CHIEF in Phase 2 Declaration with Consolidations (not EAC/CST) Customs Declaration Service Declaration with Consolidations (not EAC /CST) Declaration with Consolidations (not EAC /CST or movement messages) 7. CSP route to CHIEF XML, email ICAB ICAB EDI XML, email EDI EDI EDCS CHIEF EDI EDCS CHIEF CHIEF CHIEF CHIEF CSP CSP CHIEF In-house software Gov.uk CSP SWD SWD SWD NES WEB ICAB ICAB EDI CHIEF CSP 19 Declarations, Consolidations and Movements Declarations, Consolidations and Movements Declaration with Consolidations (not EAC /CST or movement messages) Declaration with Consolidations (not EAC /CST or movement messages)<br>
20
Phase 1: ILE dual running scenarios Customs Declaration Service Declarations can be submitted to CHIEF. Declarations can also be submitted to CDS through the CDS UI or CDS API by migrated traders only.
For ILE dual running to run successfully, it is advisable that SWD (with multi-declarants/consolidators) do not switch to CDS until Phase 2 has commenced.
In-house SWDs (with single declarant/consolidator) may choose to switch to CDS in Phase 1
N.B. movements MUST be submitted via either CDS UI or a CSP that is participating in Phase 1
The following slides run through some Phase 1 scenarios:
Scenario A – CHIEF only consolidation
Scenario B – CDS only consolidation
Scenario C – CHIEF movement
Scenario D – CDS movement 20<br>
For ILE dual running to run successfully, it is advisable that SWD (with multi-declarants/consolidators) do not switch to CDS until Phase 2 has commenced.
In-house SWDs (with single declarant/consolidator) may choose to switch to CDS in Phase 1
N.B. movements MUST be submitted via either CDS UI or a CSP that is participating in Phase 1
The following slides run through some Phase 1 scenarios:
Scenario A – CHIEF only consolidation
Scenario B – CDS only consolidation
Scenario C – CHIEF movement
Scenario D – CDS movement 20<br>
21
CSP
(not Participating in Phase 1) CSP Phase 1 Scenario A: CHIEF only consolidation Customs Declaration Service Route to CHIEF via CSP EDI EDI CHIEF SWD CHIEF DUCR 2 Route to CHIEF via CSP participating in Phase 1 Route to CHIEF via CSP not participating in Phase 1 EDI CHIEF SWD Declarations Consolidations CHIEF consolidation of DUCR 1 and 2 OR CHIEF consolidation of DUCR 1 and 2 CHIEF ILE CDA CDS DMS CSP Message translator Query Negative ILE query response Kept in sync CST EAC Key EDI XML SWD EDI 21 Route to CHIEF via HCI screen ICAB CHIEF CSP CHIEF DUCR 1<br>
(not Participating in Phase 1) CSP Phase 1 Scenario A: CHIEF only consolidation Customs Declaration Service Route to CHIEF via CSP EDI EDI CHIEF SWD CHIEF DUCR 2 Route to CHIEF via CSP participating in Phase 1 Route to CHIEF via CSP not participating in Phase 1 EDI CHIEF SWD Declarations Consolidations CHIEF consolidation of DUCR 1 and 2 OR CHIEF consolidation of DUCR 1 and 2 CHIEF ILE CDA CDS DMS CSP Message translator Query Negative ILE query response Kept in sync CST EAC Key EDI XML SWD EDI 21 Route to CHIEF via HCI screen ICAB CHIEF CSP CHIEF DUCR 1<br>
22
Phase 1 Scenario B: CDS only consolidation (Exported through a non-inventory linked location) Customs Declaration Service Declarations Consolidations (EAC and CST) Direct API route to CDS XML CDS In-house software CDS UI route to CDS XML CDS Gov.uk
(MDTP) CDS DUCR 1 and 2 Direct API route to CDS CDS In-house software CDS UI route to CDS XML CDS Gov.uk
(MDTP) CDS consolidation of DUCR 1 and 2 CDS DUCR 3 and 4 CDS consolidation of DUCR 3 and 4 XML 22<br>
(MDTP) CDS DUCR 1 and 2 Direct API route to CDS CDS In-house software CDS UI route to CDS XML CDS Gov.uk
(MDTP) CDS consolidation of DUCR 1 and 2 CDS DUCR 3 and 4 CDS consolidation of DUCR 3 and 4 XML 22<br>
23
SWD Phase 1 Scenario C: CHIEF movement Customs Declaration Service Route to CHIEF via CSP (participating in Phase 1) Route to CHIEF via CSP (not participating in Phase 1) EDI CHIEF DEP/ airline
(loader) MUCR/DUCR arrived and departed in CHIEF EDI CSP
(not participating in Phase 1) OR CHIEF ILE CDA CDS DMS CSP Message translator DUCR Query Negative ILE DUCR query response Kept in sync EAA/EAL/EDL MUCR EAA/EAL/EDL DUCR Key EDI XML MUCR/DUCR arrived and departed in CHIEF 23 CSP
(loader) (not participating in Phase1) EDI DEP
(loader) CHIEF ILE CDA CDS DMS CSP Message translator DUCR Query Negative ILE DUCR query response Kept in sync EDI XML XML OR CSP Loader<br>
(loader) MUCR/DUCR arrived and departed in CHIEF EDI CSP
(not participating in Phase 1) OR CHIEF ILE CDA CDS DMS CSP Message translator DUCR Query Negative ILE DUCR query response Kept in sync EAA/EAL/EDL MUCR EAA/EAL/EDL DUCR Key EDI XML MUCR/DUCR arrived and departed in CHIEF 23 CSP
(loader) (not participating in Phase1) EDI DEP
(loader) CHIEF ILE CDA CDS DMS CSP Message translator DUCR Query Negative ILE DUCR query response Kept in sync EDI XML XML OR CSP Loader<br>
24
Phase 1 Scenario D: CDS movement (Exported through a non-inventory linked location) Customs Declaration Service Route to CDS
via CSP SWD CHIEF ILE CDA CDS DMS CSP Message translator Kept in sync EAA/EAL/EDL MUCR Key EDI XML CDS UI route to CDS XML CDS Gov.uk
(MDTP) N.B. where declaration and consolidations have been sent directly to CDS, movements MUST be submitted to CDS via either the CDS UI (MDTP) or a CSP that is participating in Phase 1
If the movement is via a CSP, the CSP or SWD must be able to process a CDS response which will differ from a CHIEF response MUCR/DUCR arrived and departed in CDS MUCR/DUCR arrived and departed in CDS 24 Movement Example 1 Movement Example 2 Loader Loader CSP
(loader) XML<br>
via CSP SWD CHIEF ILE CDA CDS DMS CSP Message translator Kept in sync EAA/EAL/EDL MUCR Key EDI XML CDS UI route to CDS XML CDS Gov.uk
(MDTP) N.B. where declaration and consolidations have been sent directly to CDS, movements MUST be submitted to CDS via either the CDS UI (MDTP) or a CSP that is participating in Phase 1
If the movement is via a CSP, the CSP or SWD must be able to process a CDS response which will differ from a CHIEF response MUCR/DUCR arrived and departed in CDS MUCR/DUCR arrived and departed in CDS 24 Movement Example 1 Movement Example 2 Loader Loader CSP
(loader) XML<br>
25
Phase 2: ILE dual running scenarios Customs Declaration Service Phase 2 will only commence when all CSPs are ready
All CSPs will now be sending consolidation and movement messages to CDS only
Declarations can be submitted to both CHIEF and CDS via the CSP
CDA component within CDS will aggregate responses from CHIEF and DMS and return a single response
Any errors arising from the processing of consolidation/movements will be returned in a single combined error response.
NESWEB channels for declaration with consolidations (not EAC/CST) will remain open.
Movements MUST be submitted to CDS (these must go through CDA)
During Phase 2 SWDs can roll out their CDS software gradually
The following slides run through some Phase 2 scenarios:
Scenario A – CHIEF only consolidation
Scenario B – CDS only consolidation
Scenario C – Movement of mixed consolidation 25<br>
All CSPs will now be sending consolidation and movement messages to CDS only
Declarations can be submitted to both CHIEF and CDS via the CSP
CDA component within CDS will aggregate responses from CHIEF and DMS and return a single response
Any errors arising from the processing of consolidation/movements will be returned in a single combined error response.
NESWEB channels for declaration with consolidations (not EAC/CST) will remain open.
Movements MUST be submitted to CDS (these must go through CDA)
During Phase 2 SWDs can roll out their CDS software gradually
The following slides run through some Phase 2 scenarios:
Scenario A – CHIEF only consolidation
Scenario B – CDS only consolidation
Scenario C – Movement of mixed consolidation 25<br>
26
SWD Phase 2 Scenario A: CHIEF only consolidation Customs Declaration Service Route to CHIEF via CSP (CCS-UK) Declarations Consolidations CHIEF ILE CDA CDS DMS CSP Message translator Query Negative ILE query response Kept in sync CST EAC Key EDI XML CHIEF consolidation of DUCR 1 and 2 NES WEB route to CHIEF CHIEF Gov.uk EDI EDI CSP CHIEF SWD CHIEF DUCR 1 CHIEF DUCR 2 26<br>
27
Phase 2 Scenario B: CDS only consolidation Customs Declaration Service Route to CDS via CSP Declarations Consolidations CHIEF ILE CDA CDS DMS CSP Query Positive ILE query response Kept in sync CST EAC Key XML CDS consolidation of DUCR 1 and 2 Declarations Route to CDS via CSP XML CDS SWD CDS UI route to CDS XML CDS Gov.uk
(MDTP) CDS DUCR 1 CDS DUCR 2 CSP XML 27<br>
(MDTP) CDS DUCR 1 CDS DUCR 2 CSP XML 27<br>
28
Gov.uk
(MDTP) Phase 2 Scenario C: Movement of Mixed Consolidation Customs Declaration Service Movement Example 1 Route to CDS (and CHIEF) via CDS UI All DUCRs will be arrived and departed. CDA will send a single aggregated EMR to the end user. CHIEF ILE CDA CDS DMS Kept in sync EAL/EDL MUCR EAL/EDL DUCR Key XML MUCR A consolidated in both CHIEF (DUCR 1 and 2) and CDS (DUCR 3 and 4). Route to CDS (and CHIEF) via CSP CSP All DUCRs will be arrived and departed. CDA will send a single aggregated EMR to the CSP. MUCR B consolidated in both CHIEF (DUCR 5 and 6) and CDS (DUCR 7 and 8). Movement Example 2 CHIEF ILE CDA CDS DMS Kept in sync XML 28 EAA/EAL/EDL MUCR EAA/EAL/EDL DUCR Key<br>
(MDTP) Phase 2 Scenario C: Movement of Mixed Consolidation Customs Declaration Service Movement Example 1 Route to CDS (and CHIEF) via CDS UI All DUCRs will be arrived and departed. CDA will send a single aggregated EMR to the end user. CHIEF ILE CDA CDS DMS Kept in sync EAL/EDL MUCR EAL/EDL DUCR Key XML MUCR A consolidated in both CHIEF (DUCR 1 and 2) and CDS (DUCR 3 and 4). Route to CDS (and CHIEF) via CSP CSP All DUCRs will be arrived and departed. CDA will send a single aggregated EMR to the CSP. MUCR B consolidated in both CHIEF (DUCR 5 and 6) and CDS (DUCR 7 and 8). Movement Example 2 CHIEF ILE CDA CDS DMS Kept in sync XML 28 EAA/EAL/EDL MUCR EAA/EAL/EDL DUCR Key<br>
29
Relevant CDS Release Timelines Customs Declaration Service Release 3.0 – Trade test drop date: 22-Apr-2019 Live drop date: 09-May-2019
Supplementary declaration submission via API and UI : enabled for traders with specific export authorisations/licences
Tariff validation
Release 3.1 – Trade test drop date: 23-May-2019 (delivered) Live drop date: TBC
Frontier declarations submission via API
CDS ILE functionality (movements and consolidations)
CDS UI availability
Phase 1 Dual Running (R3.3)
Trade Test : 10-June-2019 (delivered) – Upgrade to CSP-CDS interface (CHIEF stubbed)
Trade Test : August (TBC) – Testing with CHIEF enabled
Live Drop: TBC
Phase 2 Dual Running
Trade Test : Early Autumn 2019
Live Drop : Date TBC – dependent upon all CSP migration. 29<br>
Supplementary declaration submission via API and UI : enabled for traders with specific export authorisations/licences
Tariff validation
Release 3.1 – Trade test drop date: 23-May-2019 (delivered) Live drop date: TBC
Frontier declarations submission via API
CDS ILE functionality (movements and consolidations)
CDS UI availability
Phase 1 Dual Running (R3.3)
Trade Test : 10-June-2019 (delivered) – Upgrade to CSP-CDS interface (CHIEF stubbed)
Trade Test : August (TBC) – Testing with CHIEF enabled
Live Drop: TBC
Phase 2 Dual Running
Trade Test : Early Autumn 2019
Live Drop : Date TBC – dependent upon all CSP migration. 29<br>
30
To Summarise Limited/no additional development work for SWDs
Flexible roll-out phases
Limited disruption to supply chain
Minimum business impact Customs Declaration Service Next steps Follow-up call to review any questions and actions. 30<br>
Flexible roll-out phases
Limited disruption to supply chain
Minimum business impact Customs Declaration Service Next steps Follow-up call to review any questions and actions. 30<br>