Customs Declaration Service Date: 21 January 2020 Time: 11:00 15:00 - - PowerPoint PPT Presentation
Customs Declaration Service Date: 21 January 2020 Time: 11:00 15:00 Venue: HMRC Business Centre, Suites 1.11, 1.12, 1.13 1 Ruskin Square Dingwall Road Croydon CR0 2WF Customs Declaration Service | Official Marking 1 NCTS API changes
Customs Declaration Service
1 Customs Declaration Service | Official Marking
Date: 21 January 2020 Time: 11:00 – 15:00 Venue: HMRC Business Centre, Suites 1.11, 1.12, 1.13 1 Ruskin Square Dingwall Road Croydon CR0 2WF
2 Customs Declaration Service | Official Marking
3 Customs Declaration Service | Official Marking
We want to speak to you! We are making some changes to the NCTS API that is currently in use We would like to understand
And help us shape what you want the new API to do
For further details please contact: Megan.lynn@digital.hmrc.gov.uk
Customs Declaration Service | Official Marking 4
Total Number of Queries Raised 3821 Total Number of Queries Resolved 3708 Total Number of Queries Outstanding 113
Accurate up to and including 15th January 2020
Total Number of Queries Resolved Total Number of Queries Outstanding
97% 3%
Customs Declaration Service | Official Marking 5
Month Queries Raised Total responses sent (per month) Outstanding (from that month) July 201 227 August 174 186 3 September 240 238 7 October 200 176 8 November 182 194 22 December 130 174 34
Customs Declaration Service | Official Marking 6
Month Average Response Time (working days) July 14 August 14 September 12 October 9 November 10 December 9
2 4 6 8 10 12 14 16 July August September October November December
Customs Declaration Service | Official Marking 7
Customs Declaration Service | Official Marking 8
support Software Developers and CSPs.
community without breaking commercial confidences.
query review and b) essential changes to current ticket processes
9 Customs Declaration Service | Official Marking
10 Customs Declaration Service | Official Marking
developers participating in the CDS Trade Test with visibility of queries raised by other developers.
11 Customs Declaration Service | Official Marking
regular basis, frequency to be agreed.
Which queries will be included in the launched AQL?
you raised from 4th September 2019, following Trade Test Release 8.1.0
be whitelisted)
Customs Declaration Service | Official Marking 12
Customs Declaration Service | Official Marking 13
if the developer raising it has given HMRC explicit permission to do so.
query you no longer wish to share it via the AQL, you must e-mail SDST within 5 working days.
mailbox or via your Business Responsible Manager.
March as part of a formal review of the AQL.
14 Customs Declaration Service | Official Marking
15 Customs Declaration Service | Official Marking
KELs (Known Error Logs) Tax Lines Document High level overview of Release 2.6.0 to 3.6.0 / TT 8.4 - TT9.0 OGD Routes
16 Customs Declaration Service | Official Marking
CDS Trade Test Roadmap
V4.1 Last updated 17/01/2020
17 | OFFICIAL | Trade Test Roadmap |
Tariff download service. Submission & cancellation of type:
Authorisation validation:
AEO. Licensing. DMSTAX consolidation change. Unhappy path imports inventory linking. Removal of workarounds on inventory-linked submissions. Submission of types:
Aggregation of declarations. Relief & Suspension:
Relief.
Processing. Resolution of some inventory linking defects. Authorisation validation:
and special procedures authorisations. Error code transformation. Procedure codes:
Amendment of type:
Cancellation of type:
Further Relief & Suspension.
codes available. Imports Immediate Payments MOP:
bankers draft).
transfer). All Imports Declaration Types Initial Exports Inventory Linking Further Imports Frontier Declarations Exports Supplementary Declarations
Imports Frontier Declarations and Immediate Payments
Tariff Download Service
Imports Supplementary Declaration TTM6.1.0
Imports Enhancements TTM6.0.0
TTM5.1 Scope
Inventory linked types:
Submission of type:
Cancellation of type:
Currency conversion. Front-End Credibility checks. Declare goods with local DIT / RPA licences. Value build-up. CCG authorisation validation. Validation of DAN / EORI relationship. Procedure codes:
CDS Trade Test Roadmap – Mar 2019
18
Key Notes:
1. Trade Test roadmap calls out key externally-facing functionality that has been prioritised, but is not indicative of all releases into Production and is not a definitive list of all content within each Trade Test delivery. 2. The order of releases into CDS Trade Test and their content are subject to change. Specifically, multiple functional areas may be delivered together or a single functional area may be broken into smaller releases. In addition, system upgrades may be released into the Trade Test environment between releases to resolve high priority defects.
TTM6. 2 Continued on Next Slide
| OFFICIAL | Trade Test Roadmap |
All C21 procedures. Simulated quota service. CCG waiver & document status codes. Tariff error handling (CDS4-series). Error code enhancements & granularity. Ability to use CDS to arrive, depart, and consolidate inventory linked declarations submitted in CHIEF. For TTM7.2.0: CHIEF stubbed. Date for full integration TBC. Submission, amendment & cancellation of types:
Excise movements. Documentary and physical controls for multiple arrivals. Multiple arrivals. Multiple departures. Automatic departures. Notification enhancement: ROE control type to SOE topic type. Submission, amendment & cancellation of types:
Authorisation validation:
CSE. Exports frontier declarations A/D. Validation of MUCR. Movement of goods. Consolidation. Push Notification API Enhancement. File Upload Endpoint Enhancement. Submission, amendment & cancellation of types:
procedure codes). Documentary and physical controls. View declaration status & history (Iteration 1). Paper licenses. Security scenarios with Immediate Payment and Duty Deferment for:
suspension. Excise calculations. Further Reliefs & Suspensions. Front-End Credibility enhancement. Minimum import price calculation. Low value bulking. Exports Dual Running All Exports Declaration Types Further Imports Enhancements Multiple Exports Arrivals & Frontier Processing TTM8.0.0 All Imports Declaration Types TTM8.0.0 Exports Dual Running TTM7.2.0 Initial Exports Frontier Movements TTM7.1.0 Maintenance Release TTM7.0.0
Imports Frontiers, Immediate Payment, Exports Supplementary Declarations TTM6.2.0
Amendment of Imports declaration types:
Cancellation of Imports declaration types:
Further Relief & Suspension.
procedure codes available. Imports Immediate Payments MOPs A, B, C, H. Submission & cancellation of Exports declaration type:
Authorisation validation:
Exports Licensing.
CDS Trade Test Roadmap – Jun 2019
19
Key Notes:
1. Trade Test roadmap calls out key externally-facing functionality that has been prioritised, but is not indicative of all releases into Production and is not a definitive list of all content within each Trade Test delivery. 2. The order of releases into CDS Trade Test and their content are subject to change. Specifically, multiple functional areas may be delivered together or a single functional area may be broken into smaller releases. In addition, system upgrades may be released into the Trade Test environment between releases to resolve high priority defects.
TTM8. 0.0 TTM8. 1.0 Continued on Next Slide
| OFFICIAL | Trade Test Roadmap |
Further error codes enhancements. Enhanced processing
RPA licences. Complex Excise scenarios. Imports Type B&E rework (address known errors). Non-standard country codes (exports). ILE Query Service Uplift (exports). Dual Running Location Codes (exports) Enhanced cancellation processing. Declaration processing using all methods of payment:
accounts
Guarantees Non-functional infrastructure update. Declaration processing in preparation for a UK Exit from the EU:
Movements (RoRo)
Calculation of Duties (NI)
Simplified Procedures (TSP)
Accounting (PVA)
Baggage (MIB) Amendment and cancellation of a declaration where an electronic licence has been declared. Future Enhancements Additional Methods of Payment Licensing Anti-dumping and countervailing measures. SPV / SIV calculation
Interim deferment payments and deferment account top-up. Reprocessing errors. Rules rework (address known errors). Imports & Exports Enhancements TTM9.X.0 Imports & Exports Functional Enhancements TTM9.0.0 Integration between CDS Trade Test and CHIEF HMUT established. Aggregation and consolidation of inventory linked declarations submitted
CDS Trade Test Roadmap – Jan 2020
20
Key Notes:
1. Trade Test roadmap calls out key externally-facing functionality that has been prioritised, but is not indicative of all releases into Production and is not a definitive list of all content within each Trade Test delivery. 2. The order of releases into CDS Trade Test and their content are subject to change. Specifically, multiple functional areas may be delivered together or a single functional area may be broken into smaller releases. In addition, system upgrades may be released into the Trade Test environment between releases to resolve high priority defects.
Trade Test Continues
| OFFICIAL | Trade Test Roadmap |
View declaration status & history (Iteration 2). EORI, Badge ID or CSP authentication details for identifying
CDS. Infrastructure Release & D1ND Rollback TTM8.4.0 Non-functional infrastructure update. EU Tariff Data load to align with Production Infrastructure Release TTM8.3.0 D1ND TTM8.2.0 Exports Dual Running with HMUT Connectivity TTM8.1.2
ERROR CODES & POINTERS RED TEAM OUTPUTS
Customs Declaration Service | Official Marking 21
Test will allow multiple pointers to be returned for 800+ rule instances
Principles:
triggered error messages and “quick wins” where HMRC can implement the changes through in-house configuration.
granularity
existing messages where required.
detail to errors where the opportunity exists to do so.
Aug 19 Sept 19 Nov 19 Jan 20
to CDS12056 & CDS10001
add granularity to CDS12007
Red Team Overview Milestones:
22 Customs Declaration Service | Official Marking
September 2019
CDS12056 split into 48 codes (47 new). CDS10001 split into 4 codes (3 new) and wording updated.
Customs Declaration Service | Official Marking 23
CDS12056 is an error code previously triggered in the majority of instances where cross field validation has failed a validation test. The previously generic all-encompassing message has been broken down into forty-seven new error codes with more detailed corresponding error message (excluding BR675).
CDS1 S12056 Rela latio ion error: The combination of elements is not allowed + + 44 44 New New Er Error Cod
with th ne newly ly de defin fined Er Error Messages Previously Returned Error Message CDS1 S12056 Rela latio ion Er Error: The combination of elements is not allowed Updated Error Messages Returned
Improvements to CDS12056
NE NEW: CDS1 S12120 Rela latio ion error: The appropriate authorisation has not been declared for this Declaration Type (D.E. 1/2) NE NEW: CDS1 S12121 Rela latio ion error: This combination of Additional Information codes (DE.2/2) is not allowed NEW: CDS1 S12070 Relati tion
Date Element 2 Note: This document only contains specific examples and is not a comprehensive guide to all the changes. Please refer to the CDS codelist document for full list of error codes & messages.
Customs Declaration Service | Official Marking 24
CDS10001 is an error code previously triggered for a number of different scenarios relating to
broken down into four error codes (three new codes) with more detailed error messages.
CDS1 S10001 Obli bligatio ion error: Mandatory Data Element has not been provided NE NEW: CDS1 S10002 Oblig bligatio ion error: Data Element is not allowed NE NEW: CDS1 S10003 Oblig bligatio ion error: Number of Occurrences exceeds what is allowed for the Data Element Previous Error Message CDS1 S10001 Oblig bligatio ion Er Error: Obligation rule not met Updated Error Messages
Split of CDS10001
NE NEW: CDS1 S10004 Com
ity code error: Mandatory data element not provided or format error or number of occurrences exceeds what is allowed for the data element
Customs Declaration Service | Official Marking 25
November 2019
CDS120007 split into 2 additional codes 4 new error codes Wording changes made to 20+ error messages Tariff error messages updated for 6 scenarios
Customs Declaration Service | Official Marking 26
CDS12007 is an error code previously triggered for a number of different scenarios relating to authorisations, licences and duty deferment validation failures. The previously generic all- encompassing message has been broken down into three error codes (2 new codes) with more detailed error messages.
CDS1 S12007 Auth uthoris isatio ion error: Authorisation has expired; or
Authorisation reference number does not belong to the party on the declaration; or
Authorisation reference number provided is not recognised NEW NEW: CDS12124 Li License error: License has expired; or
License ID cannot be recognised; or
License ID does not belong to the party on the declaration; or
License declared has Insufficient balance remaining; or
License does not apply to the goods or country declared NE NEW: CDS1 S12125 DAN error: Account number is not recognised; or
Account is suspended or revoked; or
Parties declared on the declaration do not have authority to use account number provided Note: Due to the set up of the business rule templates, error codes could not be configured for each individual scenario within the License, DAN and Authorisation space. Previously Returned Error Message CDS1 S12007 Auth thorisati tion
DAN is invalid or required permissions not held Updated Error Messages Returned
Split of CDS12007
Note: This document only contains specific examples and is not a comprehensive guide to all the changes. Please refer to the CDS codelist document for full list of error codes & messages.
Customs Declaration Service | Official Marking 27
The wording of all other declaration validation related error messages have been reviewed and updated where feasible. 20+ updates have been made. See below for examples:
Previous Error Message CDS1 S11003 Rela latio ion Er Error: invalid Item total value
Other Error Message Updates
CDS1 S11003 Relati tion
number of goods items on the declaration Updated Error Messages Previous Error Message CDS1 S11003 Rela latio ion Er Error: differing requested procedure CDS1 S11003 Relati tion
1/10) for each goods item must derive the same declaration category. (eg H1) Updated Error Messages Previous Error Message CDS1 S11003 Uniq niqueness Er Error: non-unique amendment element CDS1 S11003 Relati tion
amended more than once in the same request. Updated Error Messages Note: This document only contains specific examples and is not a comprehensive guide to all the changes. Please refer to the CDS codelist document for full list of error codes & messages.
Customs Declaration Service | Official Marking 28
supplied:
documents for the goods item throwing the error.
required to fulfil the measure condition.
& commodity code.
code will also be returned.
Unit is incorrect:
throwing the error.
required to fulfil the measure condition
& commodity code.
code will also be returned. We have reviewed error handling for our Tariff application. We are now returning more information when measure conditions are not fulfilled alongside various other updates. This additional information now gives a more detailed breakdown of the cause of the error as well as the actions required to resolve the issue.
Tariff Error Message Updates
Note: This document only contains specific examples and is not a comprehensive guide to all the changes. Please refer to the CDS codelist document for full list of error codes & messages.
Customs Declaration Service | Official Marking 29
January 2020
Multiple pointers can be returned Affects 863 rule instances
No Note: The error codes used in this section are not yet be available in Trade Test or Production.
Customs Declaration Service | Official Marking 30
BR675 Headline Change
<_2_1:Error> <_2_1:ValidationCode>CDS12070</_2_1:ValidationCode> <_2_1:Pointer> <_2_1:DocumentSectionCode>42A</_2_1:DocumentSectionCode> </_2_1:Pointer> <_2_1:Pointer> <_2_1:DocumentSectionCode>67A</_2_1:DocumentSectionCode> </_2_1:Pointer> <_2_1:Pointer> <_2_1:SequenceNumeric>1</_2_1:SequenceNumeric> <_2_1:DocumentSectionCode>68A</_2_1:DocumentSectionCode> </_2_1:Pointer> <_2_1:Pointer> <_2_1:SequenceNumeric>6</_2_1:SequenceNumeric> <_2_1:DocumentSectionCode>02A</_2_1:DocumentSectionCode> <_2_1:TagID>360</_2_1:TagID> </_2_1:Pointer> </_2_1:Error> <_2_1:Error> <_2_1:ValidationCode>CDS12070</_2_1:ValidationCode> <_2_1:Pointer> <_2_1:DocumentSectionCode>42A</_2_1:DocumentSectionCode> </_2_1:Pointer> <_2_1:Pointer> <_2_1:DocumentSectionCode>67A</_2_1:DocumentSectionCode> </_2_1:Pointer> <_2_1:Pointer> <_2_1:SequenceNumeric>1</_2_1:SequenceNumeric> <_2_1:DocumentSectionCode>68A</_2_1:DocumentSectionCode> </_2_1:Pointer> <_2_1:Pointer> <_2_1:SequenceNumeric>6</_2_1:SequenceNumeric> <_2_1:DocumentSectionCode>02A</_2_1:DocumentSectionCode> <_2_1:TagID>360</_2_1:TagID> </_2_1:Pointer> </_2_1:Error> <_2_1:Error> <_2_1:ValidationCode>DMS12070</_2_1:ValidationCode> <_2_1:Pointer> <_2_1:DocumentSectionCode>42A</_2_1:DocumentSectionCode> </_2_1:Pointer> <_2_1:Pointer> <_2_1:DocumentSectionCode>67A</_2_1:DocumentSectionCode> </_2_1:Pointer> <_2_1:Pointer> <_2_1:SequenceNumeric>1</_2_1:SequenceNumeric> <_2_1:DocumentSectionCode>68A</_2_1:DocumentSectionCode> </_2_1:Pointer> <_2_1:Pointer> <_2_1:SequenceNumeric>6</_2_1:SequenceNumeric> <_2_1:DocumentSectionCode>02A</_2_1:DocumentSectionCode> <_2_1:TagID>D028</_2_1:TagID> </_2_1:Pointer> </_2_1:Error>
Previous DMSREJ (example) Updated DMSREJ (example)
One Error Block Pointing to Data Element 1 One Error Block Pointing to Data Element 1 One Error Block Pointing to Data Element 2
BR675 Relation Error has been updated to return two or more (where relevant) error blocks. This allows CDS to describe all relevant data items that have caused a validation rule to fail. There are 863 instances of BR675 in the CDS2.6.0 release, all of which will return the newly designed DMSREJ notification.
CDS12070 12070: Relation error: The value supplied in Data Element 1 mandates the completion of Data Element 2. The updated BR675 DMSREJ now points to Data Element 1 & Data Element 2. This will allow you to determine which Data Element is mandating the completion of which other Data Element. Additional Examples of the updated BR675 can be found in “Understanding DMSREJ”
Customs Declaration Service | Official Marking 31
Understanding DMSREJ – A “How To” Guide
Customs Declaration Service | Official Marking 32
Principles and Assumptions:
and no explicit link.
Error code is encountered, the next Error object contains the related pointer for that same validation failure.
expected pointers per error code. N.B. If error is related to D.E. 2/3 Document Type and D.E. 2/6 Deferred Payment, then an additional error block will be received due to concatenated
sent.
DMSREJ Analysis – Current Approach and WCO Pointer Structure
<Error> <ValidationCode>CDS12056</ValidationCode> <Pointer> <DocumentSectionCode>42A</DocumentSectionCode> </Pointer> <Pointer> <SequenceNumeric>1</SequenceNumeric> <DocumentSectionCode>67A</DocumentSectionCode> </Pointer> <Pointer> <SequenceNumeric>1</SequenceNumeric> <DocumentSectionCode>68A</DocumentSectionCode> </Pointer> <Pointer> <SequenceNumeric>3</SequenceNumeric> <DocumentSectionCode>02A</DocumentSectionCode> <TagID>D006</TagID> </Pointer> </Error> <Error> <ValidationCode>CDS12056</ValidationCode> <Pointer> <DocumentSectionCode>42A</DocumentSectionCode> </Pointer> <Pointer> <SequenceNumeric>1</SequenceNumeric> <DocumentSectionCode>67A</DocumentSectionCode> </Pointer> <Pointer> <SequenceNumeric>1</SequenceNumeric> <DocumentSectionCode>68A</DocumentSectionCode> </Pointer> <Pointer> <SequenceNumeric>3</SequenceNumeric> <DocumentSectionCode>02A</DocumentSectionCode> <TagID>D031</TagID> </Pointer> </Error>
Customs Declaration Service | Official Marking 33
has triggered the rejection of a declaration.
to further specify the data element that has caused the rejection of the declaration.
refer to (e.g. second entry in D.E. 2/3 (Documents)), the <SequenceNumeric> XML Element may be used to identify which specific instance has caused the declaration to be rejected.
sequence numeric will not be returned.
DMSREJ Analysis – Understanding the XML Elements
<Error> <ValidationCode>CDS12056</ValidationCode> <Pointer> <DocumentSectionCode>42A</DocumentSectionCode> </Pointer> <Pointer> <SequenceNumeric>1</SequenceNumeric> <DocumentSectionCode>67A</DocumentSectionCode> </Pointer> <Pointer> <SequenceNumeric>1</SequenceNumeric> <DocumentSectionCode>68A</DocumentSectionCode> </Pointer> <Pointer> <SequenceNumeric>3</SequenceNumeric> <DocumentSectionCode>02A</DocumentSectionCode> <TagID>D006</TagID> </Pointer> </Error> <Error> <ValidationCode>CDS12056</ValidationCode> <Pointer> <DocumentSectionCode>42A</DocumentSectionCode> </Pointer> <Pointer> <SequenceNumeric>1</SequenceNumeric> <DocumentSectionCode>67A</DocumentSectionCode> </Pointer> <Pointer> <SequenceNumeric>1</SequenceNumeric> <DocumentSectionCode>68A</DocumentSectionCode> </Pointer> <Pointer> <SequenceNumeric>3</SequenceNumeric> <DocumentSectionCode>02A</DocumentSectionCode> <TagID>D031</TagID> </Pointer> </Error>
Customs Declaration Service | Official Marking 34
Example 1 – One Pointer
Customs Declaration Service | Official Marking 35
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Header> <v1:dmsGatewayHeader xmlns:v1="http://ecf.dms.core/gatewayHeader/v1/"> <communicationAddress>hmrcgwid:a000a0aa-aaa0-00a0-…-0aa0-0000a0a00000</communicationAddress> <messageType>WCOTN</messageType> </v1:dmsGatewayHeader> </soap:Header> <soap:Body> <v3:notifyTrader xmlns:_2="urn:wco:datamodel:WCO:DocumentMetaData-DMS:2"xmlns:_2_1="urn:wco:datamodel:WCO:RES-DMS:2"xmlns:_2_2="urn:wco:datamodel:WCO:Response_DS:DMS:2"xmlns:v3="http://core.dms/.../v3/"> <_2:MetaData> <_2:WCODataModelVersionCode>3.6</_2:WCODataModelVersionCode> <_2:WCOTypeName>RES</_2:WCOTypeName> <_2:ResponsibleCountryCode/> <_2:ResponsibleAgencyName/> <_2:AgencyAssignedCustomizationCode/> <_2:AgencyAssignedCustomizationVersionCode/> <_2_1:Response> <_2_1:FunctionCode>03</_2_1:FunctionCode> <_2_1:FunctionalReferenceID>fc34cb18eefe4ddcbf07456b4d1a12a4</_2_1:FunctionalReferenceID> <_2_1:IssueDateTime> <_2_2:DateTimeString formatCode="304">20191107115245Z</_2_2:DateTimeString> </_2_1:IssueDateTime> <_2_1:Error> <_2_1:ValidationCode>CDS71252</_2_1:ValidationCode> <_2_1:Pointer> <_2_1:DocumentSectionCode>42A</_2_1:DocumentSectionCode> </_2_1:Pointer> <_2_1:Pointer> <_2_1:DocumentSectionCode>67A</_2_1:DocumentSectionCode> </_2_1:Pointer> <_2_1:Pointer> <_2_1:SequenceNumeric>1</_2_1:SequenceNumeric> <_2_1:DocumentSectionCode>68A</_2_1:DocumentSectionCode> </_2_1:Pointer> <_2_1:Pointer> <_2_1:DocumentSectionCode>92A</_2_1:DocumentSectionCode> <_2_1:TagID>063</_2_1:TagID> </_2_1:Pointer> </_2_1:Error> <_2_1:Declaration> <_2_1:FunctionalReferenceID> KM_20191107111111</_2_1:FunctionalReferenceID> <_2_1:ID>19GBAAAAAAAAAAAAA0</_2_1:ID> <_2_1:RejectionDateTime> <_2_2:DateTimeString formatCode="304">20191107115245Z</_2_2:DateTimeString> </_2_1:RejectionDateTime> <_2_1:VersionID>1</_2_1:VersionID> </_2_1:Declaration></2_1:Response></_2:MetaData></v3:notifyTrader></soap:Body></soap:Envelope>
DMSREJ XML
Customs Declaration Service | Official Marking 36
<_2_1:Error> <_2_1:ValidationCode>CDS71252</_2_1:ValidationCode> <_2_1:Pointer> <_2_1:DocumentSectionCode>42A</_2_1:DocumentSectionCode> </_2_1:Pointer> <_2_1:Pointer> <_2_1:DocumentSectionCode>67A</_2_1:DocumentSectionCode> </_2_1:Pointer> <_2_1:Pointer> <_2_1:SequenceNumeric>1</_2_1:SequenceNumeric> <_2_1:DocumentSectionCode>68A</_2_1:DocumentSectionCode> </_2_1:Pointer> <_2_1:Pointer> <_2_1:DocumentSectionCode>92A</_2_1:DocumentSectionCode> <_2_1:TagID>063</_2_1:TagID> </_2_1:Pointer> </_2_1:Error> <_2_1:Declaration> <_2_1:FunctionalReferenceID>KM_20191107111111</_2_1:FunctionalReferenceID> <_2_1:ID>19GBAAAAAAAAAAAAA0</_2_1:ID> <_2_1:RejectionDateTime> <_2_2:DateTimeString formatCode="304">…000A</_2_2:DateTimeString> </_2_1:RejectionDateTime> <_2_1:VersionID>1</_2_1:VersionID> </_2_1:Declaration>
DMSREJ XML – Focus on the Error XML Blocks
Customs Declaration Service | Official Marking 37
<_2_1:Error> <_2_1:ValidationCode>CDS71252</_2_1:ValidationCode> <_2_1:Pointer> <_2_1:DocumentSectionCode>42A</_2_1:DocumentSectionCode> </_2_1:Pointer> <_2_1:Pointer> <_2_1:DocumentSectionCode>67A</_2_1:DocumentSectionCode> </_2_1:Pointer> <_2_1:Pointer> <_2_1:SequenceNumeric>1</_2_1:SequenceNumeric> <_2_1:DocumentSectionCode>68A</_2_1:DocumentSectionCode> </_2_1:Pointer> <_2_1:Pointer> <_2_1:DocumentSectionCode>92A</_2_1:DocumentSectionCode> <_2_1:TagID>063</_2_1:TagID> </_2_1:Pointer> </_2_1:Error> <_2_1:Declaration> <_2_1:FunctionalReferenceID>KM_20191107111111</_2_1:FunctionalReferenceID> <_2_1:ID>19GBAAAAAAAAAAAAA0</_2_1:ID> <_2_1:RejectionDateTime> <_2_2:DateTimeString formatCode="304">…000A</_2_2:DateTimeString> </_2_1:RejectionDateTime> <_2_1:VersionID>1</_2_1:VersionID> </_2_1:Declaration>
DMSREJ XML – Understanding What’s Left
Error Block Error Code: Describes what Error has been thrown
Pointer
Pointer: Narrows down to the WCO Element causing the error to be thrown Sequence Numeric: (Where a list exists) identifies
Tag ID: Narrows down to the WCO Element causing the error to be thrown Please refer to “CDS Codelists and WCO References v1.41” to translate DocumentSectionCode & TagID
Note: The error codes used in this page may not yet be available in Trade Test or Production.
Customs Declaration Service | Official Marking 38
<_2_1:Error> <_2_1:ValidationCode>CDS71252</_2_1:ValidationCode> <_2_1:Pointer> <_2_1:DocumentSectionCode>42A</_2_1:DocumentSectionCode> </_2_1:Pointer> <_2_1:Pointer> <_2_1:DocumentSectionCode>67A</_2_1:DocumentSectionCode> </_2_1:Pointer> <_2_1:Pointer> <_2_1:SequenceNumeric>1</_2_1:SequenceNumeric> <_2_1:DocumentSectionCode>68A</_2_1:DocumentSectionCode> </_2_1:Pointer> <_2_1:Pointer> <_2_1:DocumentSectionCode>92A</_2_1:DocumentSectionCode> <_2_1:TagID>063</_2_1:TagID> </_2_1:Pointer> </_2_1:Error> <_2_1:Declaration> <_2_1:FunctionalReferenceID>KM_20191107111111</_2_1:FunctionalReferenceID> <_2_1:ID>19GBAAAAAAAAAAAAA0</_2_1:ID> <_2_1:RejectionDateTime> <_2_2:DateTimeString formatCode="304">…000A</_2_2:DateTimeString> </_2_1:RejectionDateTime> <_2_1:VersionID>1</_2_1:VersionID> </_2_1:Declaration>
DMSREJ XML – Understanding What’s Left – Refer to WCO.
Error Block CDS71252: Licence not valid for declared Country of Origin
Pointer
42A: Declaration 063: Country Code 62A: Goods Shipment 68A: 1st Government Agency Goods Item 92A: Origin
This is DMSRE REJ tell ells us us th that th the Countr try Code for th the Orig igin in
the dec ecla laratio tion of
the fir first goods item on
the de decla lara ratio ion is is no not a valid alid Countr try Code. Note: The error codes used in this page are not yet be available in Trade Test or Production.
Customs Declaration Service | Official Marking 39
for declared Country of Origin.
(D.E. 5/15).
With this information, we now know that the licence is not valid for the Country of Origin. Therefore, we either need to use a different licence where Allowed Countries include “NZ” or submit a declaration for the goods where the Country of Origin is “JP”.
Resolving the Issue for this Example
Customs Declaration Service | Official Marking 40
Example 2 – Two Pointer
Customs Declaration Service | Official Marking 41
<_2_1:Error> <_2_1:ValidationCode>DMS12070</_2_1:ValidationCode> <_2_1:Pointer> <_2_1:DocumentSectionCode>42A</_2_1:DocumentSectionCode> </_2_1:Pointer> <_2_1:Pointer> <_2_1:DocumentSectionCode>67A</_2_1:DocumentSectionCode> </_2_1:Pointer> <_2_1:Pointer> <_2_1:SequenceNumeric>1</_2_1:SequenceNumeric> <_2_1:DocumentSectionCode>68A</_2_1:DocumentSectionCode> </_2_1:Pointer> <_2_1:Pointer> <_2_1:SequenceNumeric>6</_2_1:SequenceNumeric> <_2_1:DocumentSectionCode>02A</_2_1:DocumentSectionCode> <_2_1:TagID>360</_2_1:TagID> </_2_1:Pointer> </_2_1:Error> <_2_1:Error> <_2_1:ValidationCode>DMS12070</_2_1:ValidationCode> <_2_1:Pointer> <_2_1:DocumentSectionCode>42A</_2_1:DocumentSectionCode> </_2_1:Pointer> <_2_1:Pointer> <_2_1:DocumentSectionCode>67A</_2_1:DocumentSectionCode> </_2_1:Pointer> <_2_1:Pointer> <_2_1:SequenceNumeric>1</_2_1:SequenceNumeric> <_2_1:DocumentSectionCode>68A</_2_1:DocumentSectionCode> </_2_1:Pointer> <_2_1:Pointer> <_2_1:SequenceNumeric>6</_2_1:SequenceNumeric> <_2_1:DocumentSectionCode>02A</_2_1:DocumentSectionCode> <_2_1:TagID>D028</_2_1:TagID> </_2_1:Pointer> </_2_1:Error>
DMSR SREJ XM XML L (E (Err rror Blo Blocks Only ly)
CDS12056: Relation error: The combination of elements is not allowed 42A: Declaration 67A: Goods Shipment 02A-360: The Document Status Code of the sixth entry in D.E. 2/3 68A: 1st Government Agency Goods Item 42A: Declaration 67A: Goods Shipment 02A-D028: The Document Reason of the sixth entry in D.E. 2/3 68A: 1st Government Agency Goods Item CDS12056: Relation error: The combination of elements is not allowed
The he 2 err rror bl blocks po point to to:
declaration
Note: The error codes used in this page are not yet be available in Trade Test or Production.
Customs Declaration Service | Official Marking 42
value supplied in Data Element 1 mandates the completion of Data Element 2.
2/3).
(D.E. 2/3).
item on the declaration is: “XY”
the declaration is : Null
Reso solv lvin ing Th The Iss Issue
Looking at the guidance on the Paper Tariff:
Document Status Code “XW” mandates a Reason be provided.
a Reason when using Document Status Code “XW”.
Customs Declaration Service | Official Marking 43
Example 3 – Two Pointer
Customs Declaration Service | Official Marking 44
<_2_1:Error> <_2_1:ValidationCode>CDS12119</_2_1:ValidationCode> <_2_1:Pointer> <_2_1:DocumentSectionCode>42A</_2_1:DocumentSectionCode> </_2_1:Pointer> <_2_1:Pointer> <_2_1:DocumentSectionCode>67A</_2_1:DocumentSectionCode> </_2_1:Pointer> <_2_1:Pointer> <_2_1:SequenceNumeric>1</_2_1:SequenceNumeric> <_2_1:DocumentSectionCode>68A</_2_1:DocumentSectionCode> </_2_1:Pointer> <_2_1:Pointer> <_2_1:DocumentSectionCode>70A</_2_1:DocumentSectionCode> <_2_1:TagID>161</_2_1:TagID> </_2_1:Pointer> </_2_1:Error> <_2_1:Error> <_2_1:ValidationCode>CDS12056</_2_1:ValidationCode> <_2_1:Pointer> <_2_1:DocumentSectionCode>42A</_2_1:DocumentSectionCode> </_2_1:Pointer> <_2_1:Pointer> <_2_1:DocumentSectionCode>67A</_2_1:DocumentSectionCode> </_2_1:Pointer> <_2_1:Pointer> <_2_1:SequenceNumeric>2</_2_1:SequenceNumeric> <_2_1:DocumentSectionCode>99A</_2_1:DocumentSectionCode> <_2_1:TagID>D019</_2_1:TagID> </_2_1:Pointer> </_2_1:Error>
DMSR SREJ XM XML L (E (Err rror Blo Blocks Only ly)
42A: Declaration 67A: Goods Shipment 70A-161: The Previous Procedure Code in D.E. 1/10 68A: 1st Government Agency Goods Item CDS12119: Relation Error: Declared Additional Document (D.E. 2/3) is not allowed with this Procedure Code (D.E. 1/10 or D.E. 1/11)
The he 2 err rror bl blocks po point to to:
42A: Declaration 67A: Goods Shipment 99A-D019: The 2nd Previous Document Code in D.E. 2/1 CDS12056: Relation error: The combination of elements is not allowed
Note: The error codes used in this page are not yet be available in Trade Test or Production.
Customs Declaration Service | Official Marking 45
Declared Additional Document (D.E. 2/3) is not allowed with this Procedure Code (D.E. 1/10 or D.E. 1/11).
(D.E. 1/10).
(D.E. 2/1).
declaration is: “4051”
is : “X337”
Reso solv lvin ing Th The Iss Issue
Looking at the guidance on the Paper Tariff:
confirms that Previous Document Code “X337” is not a valid Previous Document Code for Procedure Code 4051.
we can remove the Previous Document Status Code “X337”.
Customs Declaration Service | Official Marking 46
Example 4 – Three Pointer
Customs Declaration Service | Official Marking 47
<_2_1:Error> <_2_1:ValidationCode>CDS12056</_2_1:ValidationCode> <_2_1:Pointer> <_2_1:DocumentSectionCode>42A</_2_1:DocumentSectionCode> </_2_1:Pointer> <_2_1:Pointer> <_2_1:DocumentSectionCode>67A</_2_1:DocumentSectionCode> </_2_1:Pointer> <_2_1:Pointer> <_2_1:SequenceNumeric>1</_2_1:SequenceNumeric> <_2_1:DocumentSectionCode>68A</_2_1:DocumentSectionCode> </_2_1:Pointer> <_2_1:Pointer> <_2_1:SequenceNumeric>2</_2_1:SequenceNumeric> <_2_1:DocumentSectionCode>02A</_2_1:DocumentSectionCode> <_2_1:TagID>360</_2_1:TagID> </_2_1:Pointer> </_2_1:Error> <_2_1:Error> <_2_1:ValidationCode>CDS12056</_2_1:ValidationCode> <_2_1:Pointer> <_2_1:DocumentSectionCode>42A</_2_1:DocumentSectionCode> </_2_1:Pointer> <_2_1:Pointer> <_2_1:SequenceNumeric>1</_2_1:SequenceNumeric> <_2_1:DocumentSectionCode>67A</_2_1:DocumentSectionCode> </_2_1:Pointer> <_2_1:Pointer> <_2_1:SequenceNumeric>1</_2_1:SequenceNumeric> <_2_1:DocumentSectionCode>68A</_2_1:DocumentSectionCode> </_2_1:Pointer> <_2_1:Pointer> <_2_1:SequenceNumeric>2</_2_1:SequenceNumeric> <_2_1:DocumentSectionCode>02A</_2_1:DocumentSectionCode> <_2_1:TagID>D006</_2_1:TagID> </_2_1:Pointer> </_2_1:Error>
DMSR SREJ XM XML L (E (Err rror Blo Blocks Only ly)
<_2_1:Error> <_2_1:ValidationCode>DMS12056</_2_1:ValidationCode> <_2_1:Pointer> <_2_1:DocumentSectionCode>42A</_2_1:DocumentSectionCode> </_2_1:Pointer> <_2_1:Pointer> <_2_1:SequenceNumeric>1</_2_1:SequenceNumeric> <_2_1:DocumentSectionCode>67A</_2_1:DocumentSectionCode> </_2_1:Pointer> <_2_1:Pointer> <_2_1:SequenceNumeric>1</_2_1:SequenceNumeric> <_2_1:DocumentSectionCode>68A</_2_1:DocumentSectionCode> </_2_1:Pointer> <_2_1:Pointer> <_2_1:SequenceNumeric>2</_2_1:SequenceNumeric> <_2_1:DocumentSectionCode>02A</_2_1:DocumentSectionCode> <_2_1:TagID>D031</_2_1:TagID> </_2_1:Pointer> </_2_1:Error> CDS12056: Relation error: The combination of elements is not allowed 42A: Declaration 67A: Goods Shipment 02A-360: The Document Status Code of the second entry in D.E. 2/3 68A: 1st Government Agency Goods Item 42A: Declaration 67A: Goods Shipment 02A-D006: The Document Type of the second entry in D.E. 2/3 68A: 1st Government Agency Goods Item CDS12056: Relation error: The combination of elements is not allowed 42A: Declaration 67A: Goods Shipment 02A-D031: The Document Category of the second entry in D.E. 2/3 68A: 1st Government Agency Goods Item CDS12056: Relation error: The combination of elements is not allowed
The he 3 err rror bl blocks po point to to:
Code Note: The error codes used in this page are not yet be available in Trade Test or Production.
Customs Declaration Service | Official Marking 48
combination of elements is not allowed.
2/3).
(D.E. 2/3).
completed as follows:
“X001”
“AAA11111111A”
is: “RE”
Looking at the guidance on the Paper Tariff:
Reso solv lvin ing Th The Iss Issue
Document Status Code “RE” is not a valid Document Status Code for Document Code “X001”.
Codes for Document Code “X001”.
Customs Declaration Service | Official Marking 49
50 Customs Declaration Service | Official Marking
Should you have any questions regarding Errors and Pointers, please write to your BRM at the following address events.externalreadiness@hmrc.gov.uk Please note this mailbox is only to be used to collate queries relating to Errors and Pointers.
Raymond Cameron
51 Customs Declaration Service | Official Marking
(intentional/unintentional)
many requests). This does not result in permanent disconnection from the platform. Once the peak drops away, transactions will be accepted again.
Customs Declaration Service | Official Marking 52
to do what they need to do
requirement within a reasonable period of time
500, but start at 150 transactions per minute.
email including the Application ID for the app which needs increasing.
Customs Declaration Service | Official Marking 53
Customs Declaration Service | Official Marking 54
55 Customs Declaration Service | Official Marking
56 Customs Declaration Service | Official Marking
External Test Overview
The purpose of CDS External Test is to provide an HMRC platform for all external partners (CSPs, SWHs, express operators, and declarants) to complete their required assurance activities so they are confident in their readiness for migration to CDS. The CDS External Test offering has two core services: Trade Test and Trader Dress Rehearsal, which are outlined below. In addition to Trade Test and Trader Dress Rehearsal, HMRC also provides a range of Technical Documentation, including API specifications, Technical Completion Matrix, and the online UK Trade Tariff to support the CDS development journey. Purpose Audience & Availability Core Capabilities Trade Test
A functional test platform where 3rd party developers can assure their software integration against CDS APIs and a CDS back-end for all core declaration processes and notification types. Code in Trade Test is one version ahead of Production. Audience:
Available 24/7 to all whitelisted users. Supported 9am – 5pm Monday to Friday, excluding UK bank holidays via SDST.
arrivals via CHIEF (HMUT)
services
Trader Dress Rehearsal
A CDS-like service to support declarants in submitting all types of declarations to expose all actors in the supply chain to declaration processing in CDS as part of their final assurance activity prior to migration. Code in TDR matches Production. Current: Limited number of migrating traders for a pre-agreed period of time. Future: All declarants for up to 4 weeks after migration to CDS. Available 24/7 to all subscribed declarants. To be supported by CDS Live Services during
does not currently support inventory linking)
Customs Dec API only)
services
Customs Declaration Service | Official Marking 57
External Test Phases
After receiving access to CDS technical specifications and business documentation, developers (SWHs, CSPs, FPOs, and traders with in-house capabilities) use Trade Test to assure their software integration against CDS APIs and a CDS back-end for all core declaration processes and notification types. Once software is “declarant-ready”, Trader Dress Rehearsal (TDR) is used to expose all actors in the supply chain to declaration processing in CDS as part of their final assurance activity prior to migration to CDS. Multiple declarants using the same software package may go through separate TDR and migration phases. Enhanced support will be provided during Trader Dress Rehearsal for the first declarant migrated to CDS for each developer or CSP.
Developer Declarant
Declarant 1 Declarant 2 Declarant 3
Receive Documentation Software Declarant- Ready
Analysis & Design Development Test
Declarant Migrates
TDR Declarant 1 Prepare for CDS Trade Test
Declarant Migrates
TDR Declarant 2
Declarant Migrates
TDR Declarant 3
Customs Declaration Service | Official Marking 58
Trade Test Service: Purpose and Principles
Purpose: Trade Test is an HMRC functional test platform where 3rd party developers (SWHs, CSPs, FPOs, and traders with in-house capabilities) can assure their software integration against CDS APIs and a CDS back-end for all core declaration processes and notification types. Principles: 1. The scope of the Trade Test service is one release ahead of Production or aligned with Production depending on the delivery lifecycle. Functionality is typically delivered into Trade Test a week before Production. 2. Trade Test is not to be used by declarants. The service targets developers building applications to integrate with CDS. Developers should test all declaration processing scenarios and notifications for CDS and be able to fully assure their integration with CDS through the Trade Test service. 3. Trade Test is the CDS equivalent of CHIEF HMUT. There are no plans to decommission the Trade Test environment and the capabilities offered will become part of the ongoing CDS Live Service, providing a platform for assurance on any future fix or enhancement to CDS. 4. Trade Test uses Production-equivalent applications as much as possible for both Imports and Exports processing, but some components may be stubbed or particular scenarios may be limited for business or technical reasons. 5. Intervention by HMRC users should not be required to support BAU declaration processing and testing in Trade Test. 6. No live party or deferment account data should be used in Trade Test. 7. Full performance and throughput analysis should not be conducted in Trade Test (e.g. to break point). The Trade Test environment has not been configured and sized to the same standard as a Production environment. For technical reasons any measured or perceived levels of system performance should not be expected to be matched in the final Production system. The speed at which Trade Test processes declarations is controlled and delays may be experienced during peak use. Please contact HMRC for specific analysis requirements. 8. Automated testing and testing of legitimate business volume scenarios are supported in Trade Test. 9. Open and continual access to the service will be available to validated developers that have been whitelisted to the Trade Test APIs. 10. Trade Test is supported Monday to Friday (9am – 5pm), excluding UK bank holidays, but service is available through the environment 24/7. 11. Developers should complete integration testing for all core customer processes in Trade Test before proceeding to TDR or migration to CDS.
Customs Declaration Service | Official Marking 59
Trader Dress Rehearsal Service: Purpose & Principles
Purpose: Trader Dress Rehearsal is the HMRC platform targeting the trader / declarant community. It is used to expose all actors in the supply chain to declaration processing in CDS as part of their final assurance activity prior to migration to CDS. Principles: 1. Scope of the Trader Dress Rehearsal service to always aligned to Production. Functionality is typically delivered into TDR the day after a Production release. 2. Trader Dress Rehearsal is not intended for functional testing (e.g. by developers). Declarants should use Trader Dress Rehearsal to assure their declaration processing scenarios prior to CDS migration using their own party and deferment data. 3. Trader Dress Rehearsal is not a replacement for CHIEF Live Training but provides an open and usable service to support transition to CDS. It is funded as a finite service, currently planned to end once migration to CDS is complete. 4. Trader Dress Rehearsal uses Production-equivalent applications as much as possible for both Imports and Exports processing, but some components may be stubbed or particular scenarios may be limited for business or technical reasons. 5. Intervention by HMRC users should not be required to support BAU declaration processing and testing in Trader Dress Rehearsal. 6. Real party and deferment account data will be used to allow declarants to “dress rehearse” using their own information. Data will be handled using the same access security controls as Production to ensure confidentiality of data. 7. Full performance and throughput analysis should not be conducted in Trader Dress Rehearsal (e.g. to break point). The Trader Dress Rehearsal environment has not been configured and sized to the same standard as a Production environment. For technical reasons any measured or perceived levels of system performance should not be expected to be matched in the final Production system. The speed at which Trader Dress Rehearsal processes declarations is controlled and delays may be experienced during peak use. Please contact HMRC for specific analysis requirements. 8. Automated testing and testing of legitimate business volume scenarios are supported in Trader Dress Rehearsal. 9. Open and continual access will be available to “legitimate” declarants (with EORIs) that are already subscribed to CDS for the duration of each declarant’s Trader Dress Rehearsal period, which extends for up to 4 weeks after migration (Note: not currently enabled). 10. Enhanced support will be provided for the first declarant migrated to CDS for each developer or CSP. For other customers, Trader Dress Rehearsal will be supported Monday to Friday (9am – 5pm), excluding UK bank holidays, but service will be available 24/7. 11. Developers should complete functional integration testing for all core customer processes in Trade Test prior to TDR. Declarants should have completed sufficient testing in Trader Dress Rehearsal to be confident in all major declaration processes prior to submission in Production.
Customs Declaration Service | Official Marking 60
61 Customs Declaration Service | Official Marking
Nicholas Swaffer / Phillip Le Quesne
Agenda
Introduction Exports Migration Actors and Phasing Implications of phase one on development, testing and rollout Snapshot - Dual Running for export migration Explanation of what that means for migration and testing Imports - frontiers update Discussion
Migration session
Migrate Loaders DEP, Consolidators Air Sheds CSP Testing /proving CSP Migration SWDs & Declarants Prove Process Migration
Phase 1 Entry gate Phase 1 Exit gate Phase 2 Entry Gate
Phase 2 Proving Phase 1 Pre Phase 1 Migration Planning Phase 2 Testing Phase 2 Proving Phase 2 Roll out strategy CSP Readiness Loader readiness SWD and movement testing
Phase 2 Entry Gate
Exports Migration Actors and Phasing
CHIEF Declarations 100% CDS Declarations 0%
CDA
Currently Phase 1 Phase 2
CDA CDA 100% 0% 50% 0% 0% 0% CSP/Loader CSP/Loader CSP/Loader 0% 50%
CHIEF
to CDA
been completed before exit to phase 2
reducing volumes on CHIEF.
when all CSPs have migrated to CDS.
CHIEF Declarations 100% CDS Declarations 0% CHIEF Declarations 50% CDS Declarations 50%
100%
Movement Messages
Migration to CDA Migration to CDS
Snapshot - Dual Running for export migration
Imports update & General discussion
Customs Declaration Service | Official Marking 65
Dougie Mackenzie – Volumetrics Lead, CDS Performance, CDIO
January 2020
Customs Declaration Service | Official Marking 66
Summary
If CDS can handle submissions of 10 declarations per second (DPS) at a 5 second response time, then we can meet the priority 1 declaration SLAs as agreed with the business for March 2020 If CDS can handle submissions of 14 declarations per second (DPS) at a 5 second response time, then we can meet all prioritised declaration SLAs as agreed with the business for March 2020
Customs Declaration Service | Official Marking 67
Summary
CDS Major Performance Milestones
8 declarations per second 14 declarations per second Enhanced and Prioritised Queue 99 Line Item Declarations
Customs Declaration Service | Official Marking 68
The Context
The “throttle” and “declaration optimisation service”
MDTP MDG High Priority Queue Medium Priority Queue Low Priority Queue Priority Overflow Queue* Declaration Optimisation Service DMS Intermediate Queue Throttled Queue
Max queue length set to 60s Max queue length set to 60m Max queue length set to 3hrs Expired items
The solution diagram illustrates the flow of our volume
solution components
Mix of H priority / Overflow items
This priority overflow queue (or “expired queue”) will hold items which have exceeded the maximum queue length for medium and low priority declarations / messages. In the instance where the overflow queue is populated the declaration optimisation service will pull messages from the
until the overflow queue is empty
Note: Arrows represent logical flow of declarations and messages through the system and do not represent whether system is pushing or pulling information between components
This queue is built with a 2x throttle capacity, which may result in an additional 2 second delay to high priority declarations
Customs Declaration Service | Official Marking 69
The Context
How the prioritisation works
Scenario 1 (Total number messages) =< (Intermediate Queue length) The total messages on all queues is less than the Intermediate queue length. All messages will be transferred onto the Intermediate queue. Scenario 2 (Total number of messages) > (Intermediate Queue length) AND (Length P1 Queue + Expired Queue Length) =< (Intermediate Queue length) The total messages on all queues is greater than the hopper queue length. All P1 and expired messages can fit on the Hopper queue All messages from P1 queue and expired queue are transferred to the Intermediate queue If the hopper queue still has availability, transfer any available messages from P2 queue
If the hopper queue still has availability, transfer any available messages from P3 queue
Scenario 3 (Total number of messages) > (Intermediate Queue length) AND (Length P1 Queue + Expired Queue Length) > (Intermediate Queue length) The total messages on all queues is greater than the Intermediate queue length. Not all P1 and expired messages can fit on the Hopper queue The Intermediate queue should be filled with half messages from the P1 queue and half messages from the expired queue. Giving the P1 queue and the expired queue messages equal priority.
P1 P2 P3 Expired Queue P1 P2 P3 Expired Queue
Customs Declaration Service | Official Marking 70
All results indicative
Agreed Prioritisation, SLAs & Associated Volumes
2018 CHIEF Priority Declaration and Message Volumes for MVP
Priority SLAs Imports / Exports Declaration / Message Type Volumes % Contributio n Priority Volumes Priority % High 95% processed in 5s 99% processed in 20s 100% processed in 65s Import GPNs (Arrivals) 5,184,800 7.50% 16,121,365 22.99% Frontier (stand- alone)
Amendments / cancellations 427,072 0.62% Export GPNs (Arrivals) 10,396,348 13.54% Frontier (stand- alone)
Amendments / cancellations 113,145 0.16% Medium 90% processed in 5m 95% processed in 10m 100% processed in 1hr Import Pre-lodged 5,184,800 7.50% 15,581,148 22.22% Export Pre-lodged 10,396,348 13.54% Low 45% processed in 1hr 92% processed in 2hr 100% processed in 3hr Import Supplementary 37,510,094 54.30% 38,428,222 54.80% Export Supplementary 918,128 1.33% 70,130,735*
*Total equates to c.55m declarations
The volume of Frontier standalone declarations is being investigated but at this stage they are all being modelled as a pre-lodge and a GPN as a worst case scenario
NB: this prioritisation will be revisited following MVP
Customs Declaration Service | Official Marking 71
All results indicative
The Results of 2018 CHIEF Analysis
Modelling the Throttle for P1 declarations and messages
Rules 1) It is assumed that high priority Declarations are prioritised 2) The results are based on minute by minute total declaration data 2018 3) The analysis only indicates when high priority declarations don’t queue for longer than a minute, there may be spikes within the minute that queue declarations to the next second(s) – and therefore, we advise applying an uplift to understand when queues are below 20 seconds or 5 seconds etc. Results impact on High Priority declarations and messages The analysis of P1 declarations show that if the declaration per minute capacity is greater that 440 then the P1 declarations will not queue. This equates to 7.3dps Analysing these numbers against the peak P1 declaration minutes across the whole of 2018, there is 1 instance where 10dps is not sufficient to keep the queue less than 1 minute, so this is an outlier. A 10dps minimum requirement for P1 declarations is suggested
318 330 437 437 437 356 310 50 100 150 200 250 300 350 400 450 500
Top 5 Peaks - Sep 18 min data
average median st dev max min
1 2 3
DPM
Customs Declaration Service | Official Marking 72
All results indicative
The Results of 2018 CHIEF Analysis
Modelling the Throttle on P3 declarations
Rules 1) The results are based on hour by hour total declaration data for the whole of 2018 2) The analysis only indicates when P3 declarations queue for hour long periods (we know from the previous slide that at 10dps and higher there will be no queue for P1 declarations) 3) All P2 declarations are queued within the hour at both 10dps and 14dps At 10 dps it is forecast that 5.4% of supplementary declarations (low priority) will go into the “priority overflow queue”. At 14 dps all declaration types are forecast to meet their SLAs
10 dps 14 dps
P3 RATIO: Results - Hours
# % Total 2018 volumes 38,428,222 N/A Total volume of declarations processed without being queued 22,048,298 57.38% Total volume of queued declarations 16,379,924 42.62% 1 ≤ t < 2 hours 15,866,016 41.29% 2 ≤ t < 3 hours 513,908 1.34% 3 ≤ t < 4 hours 0.00% 4 ≤ t < 5 hours 0.00% 5 ≤ t < 6 hours 0.00% 6 ≤ t < 7 hours 0.00% 7 ≤ t < 8 hours 0.00% 8 ≤ t < 9 hours 0.00% 9 ≤ t < 10 hours 0.00% 10 ≤ t hours 0.00% Max queue time (hours) 3.00 42.62%
P3 RATIO: Results - Hours
# % Total 2018 volumes 38,428,222 N/A Total volume of declarations processed without being queued 12,011,057 31.26% Total volume of queued declarations 26,417,165 68.74% 1 ≤ t < 2 hours 13,982,298 36.39% 2 ≤ t < 3 hours 10,373,151 26.99% 3 ≤ t < 4 hours 2,061,716 5.37% 4 ≤ t < 5 hours 0.00% 5 ≤ t < 6 hours 0.00% 6 ≤ t < 7 hours 0.00% 7 ≤ t < 8 hours 0.00% 8 ≤ t < 9 hours 0.00% 9 ≤ t < 10 hours 0.00% 10 ≤ t hours 0.00% Max queue time (hours) 4.00 68.74%
Customs Declaration Service | Official Marking 73
Customs Declaration Service | Official Marking 74