Customs Declaration Services Programme

Customs Declaration Services Programme

Stella Jarvis CDS Programme Director

5th July 2017

Protective marking – Unclassified, Protect, Restricted (delete as required)

Why replace CHIEF?

▪ More flexible and efficient service.

▪ Increased volumes and resilience.

| 05/07/2017 | 2


Strategic Alignment

▪ UCC alignment – gives the trade facilitations that UK business wanted.

▪ Opportunities to align Customs systems with wider HMRC

infrastructure and take advantage of economies of scale.

▪ Customs end users can take full advantage of Making Tax Digital and

Business Tax Account developments to improve customer experience.

▪ Creation of component based architecture will allow UK systems to

remain flexible and efficient.

| 05/07/2017 | 3


How are we replacing CHIEF?

Through Agile development :

▪ Using the Scaled Agile Framework (SAFe) methodology designed for

using Agile in large and complex programmes.

▪ See and play with the services earlier.

▪ Aligned to HMRC Digital Strategy.

▪ Two off the shelf components procured (Tariff and Declaration

Management).

▪ An agreed transition strategy to deliver the live service and migrate

customers.

| 05/07/2017 | 4


| 03/2017 | 5

What are we replacing CHIEF with?


Transition Strategy - Key Principles

▪ HMRC will focus migration strategy planning on CSPs and software

houses, working in partnership with industry.

▪ Changes to the front-end of the system will be the responsibility of

software developers.

▪ Software houses will manage the roll-out and migration of their own

customers, subject to agreement with HMRC.

▪ HMRC will set a clear timetable for take-up that includes phased

transition designed against set criteria taking account of IT,

Business and Customer considerations.

▪ No migration of in flight transactions/declarations due to data

conversion complexity.

| 05/07/2017 | 6


Transition Strategy - Key Principles

▪ All transactions started on CHIEF will be finished on CHIEF.

▪ A customer will remain on CDS unless in a formal fall-back situation.

▪ Functionality for testing and migration to align with code delivery

timeline.

▪ Dual running and dual data capture supported.

▪ Multi-channel support for Industry available from cutover,

predominantly self-service, aligned with HMRC’s Customer Support

strategy.

▪ Support will be provided for trade rollback and contingency during the

transition period.

HMRC NL Standard | 05/07/2017 | 7


Customer transition

Transition: the period between delivery of first live CDS functionality until 100% customer take-up

▪ The transition period is expected to be around 6 months.

▪ We aim to give as much flexibility as possible as to when and how

stakeholders migrate.

▪ Commercial software and/or IT service providers will manage roll-

out and transition of their own customer base, to avoid local peaks

and fit with their own resourcing constraints.

▪ HMRC will review stakeholder plans and transition approaches to

stagger take-up and manage the risk of multiple late transitions –

mutually agreed entry criteria will be key to approval.

| 05/07/2017 | 8


Our Delivery Approach

▪ Starting in late 2017, functional drops will be deployed into Trade

Test offering stakeholders the opportunity to test their software and

demonstrate completion of business scenarios. This will run through

until summer 2018.

▪ An HMRC view on these functional drops is currently being shaped;

this will then be tested with stakeholders who may indicate

preferences for a different approach.

▪ July 2018 is currently the planned go live date for full CDS

functionality.

▪ There will be a gradual ramp-up of volume on CDS as we move into

a phased transition.

▪ During this time we will dual run CHIEF and CDS as we move

stakeholders across to the new service.

| 05/072017 | 9


Delivery Sequencing Rationale

▪ CDS is being delivered in an agile way, which means it will be

developed, tested and deployed incrementally.

▪ Seek to deliver value to customers & business early, i.e. deliver quick

wins and move high-value and high-volume declaration types onto

CDS early if possible.

▪ Minimise change to legacy technology to minimise spend on

throwaway code.

▪ Deliver specifications to the trade incrementally to enable our

customers to work with us in an agile way.

▪ Incrementally deliver functionality to the trade test environment

providing the maximum time available for testing.

| 05/07/2017 | 10

Protective marking – Unclassified, Protect, Restricted (delete as required) | 05/07/2017 | 11

CDS engagement plan

We are reviewing and developing our communication plans and the ways

we engage based on feedback we have received to date. Our engagement

includes:

▪ Technical workshops with CSPs, software developers and other

stakeholder groups.

▪ Engaging with trade groups and provide regular progress updates.

▪ Updates on progress shared at the Joint Customs Consultative

Committee (JCCC).

▪ Providing 1-2-1 leads where needed to support those who need to

develop software solutions to support transition plans.

▪ Linking into other Government engagement to join up where we can.


Understanding Large Business Stakeholders’ NeedsLarge Businesses stakeholders have told us they want;

▪ To look at their detailed and different software dependencies.

▪ Read-outs of documentation they need to know about in plain language.

▪ Information on when specs are baselined.

▪ New/existing data elements and data fields in relation to the business

process.

▪ When they will be taking part in testing and what that entails.

▪ A clear plan with dates for key milestones that are of interest to

stakeholders.

▪ Detail on MSS data and what it will look like from CDS, are there any

changes?

▪ Sector based meetings to discuss applicable concerns and questions.


Trade Facing Support Model

| 05/07/2017 | 13

Importers / Exporters

Freight Agents

Logistics Providers

Inventory Providers

Software Houses

CSPs

- GOV.UK

- Virtual

Assistant

- Web chat

- E-mail

- Phone call

Resolver team –

technical issue

Resolver team –

Business issue

Resolver team –

C&M issue

Ticket

(triage)

Business as usual support model

Transitional Cutover and Migration enhanced support model - Provided by CDS as additional resource

Issue

resolved

Dedicated Cutover

and Migration Trade

Support Team

SPOC for CSPs, software

houses and large companies

Fallback and rollback

support

Training and

webinars

Web chat

Industry

Complexity

Self-help capabilities24x7 Multi-functional

business and

IT helpdesk


Trade Documentation List

▪ Document list created in collaboration with

Software developers.

▪ Identified and validated a list of 15

documents that are required to support

software development.

▪ A plan has been created detailing when this

documentation will be released which will

align with development needs.

▪ Details will be hosted on Google Drive.

▪ Next steps are to replicate this piece of work

with other customer segments including

Large Business so we can confirm what

information you require and when.


CHIEF to CDS Key differences - UCC Data ChangesAlignment with International Standards : EU Customs Data Model (CDM).

▪ Increased number of items per declaration (implications for SLAs).

▪ Rationalisation of Customs Procedure Codes.

▪ An audit trail of previous document IDs.

▪ Data about additional party types (egg Buyer, Seller) : need to be clear on when data must be supplied, and default values when data is not available.

▪ Provision for extra commercial references / Tracking numbers.

▪ Harmonised EU Customs Office Lis’.


▪ Harmonised Location of Goods identification (based on UNLOCODE).

▪ Harmonised Warehouse Type code list.

▪ Harmonised Method of Payment codes.

▪ Harmonised Unit of Quantity codes (ISO).

▪ Harmonisation of Item Tax Line; no Tax Rate Identifier (we need to work through which data items have to be explicitly declared and which can be derived by CDS or Tariff).

▪ Levelling – change for some data items between Header and Item.


Authorised Economic Operator (AEO)

▪ The two types of AEO accreditation available to businesses are AEOC

(customs simplifications), and AEOS (security and safety)

▪ The Prime Minister has stated that although the UK will leave the

Customs Union the UK will seek a customs arrangement that makes

cross-border trade as frictionless as possible.

▪ Trusted trader programmes are an important part of the customs

regime and we will look to ensure continued facilitations for trusted

traders following the UK’s exit from the EU.



Potential impact of Brexit on CDS

▪ We are planning to transition all internal & external stakeholders

and trade partners from CHIEF to CDS by 31st March 2019.

▪ If the CDS service is not fully available there will be extended dual

running/load balancing between CDS & CHIEF as we exit the EU.

▪ Brexit will potentially increase the volume of transactions to be

handled by CDS.

▪ Given the potential increase in volumes we may need to

significantly increase the processing power for the CDS service and

linked IT systems, including OGD licence control services.

▪ Tariff – if negotiations do not give us access to the existing EU tariff

we will need to obtain a new data source for tariff details.

| 05/07/2017 | 17

Any Questions?

Thank you and please send any further questions to:

[email protected]

Customs Declaration Services Programme

Documents

Transcript of Customs Declaration Services Programme