Customs Declaration Services Programme Stella Jarvis CDS Programme Director 5 th July 2017
Why replace CHIEF? ▪ More flexible and efficient service. ▪ Increased volumes and resilience. Protective marking – Unclassified, Protect, Restricted (delete as required) | 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. Protective marking – Unclassified, Protect, Restricted (delete as required) | 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. Protective marking – Unclassified, Protect, Restricted (delete as required) | 05/07/2017 | 4
What are we replacing CHIEF with? | 03/2017 | 5 Protective marking – Unclassified, Protect, Restricted (delete as required)
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. Protective marking – Unclassified, Protect, Restricted (delete as required) | 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. Protective marking – Unclassified, Protect, Restricted (delete as required) 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. Protective marking – Unclassified, Protect, Restricted (delete as required) | 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. Protective marking – Unclassified, Protect, Restricted (delete as required) | 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. Protective marking – Unclassified, Protect, Restricted (delete as required) | 05/07/2017 | 10
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. Protective marking – Unclassified, Protect, Restricted (delete as required) | 05/07/2017 | 11
Understanding Large Business Stakeholders’ Needs Large 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. Protective marking – Unclassified, Protect, Restricted (delete as required) | 05/07/2017 | 12
Trade Facing Support Model Business as usual support model Industry Complexity 24x7 Multi-functional Importers / Exporters Resolver team – Self-help capabilities business and Freight Agents technical issue IT helpdesk Logistics Providers Inventory Providers Ticket - GOV.UK - Web chat Issue Resolver team – (triage) resolved Business issue - Virtual - E-mail Assistant Software Houses Resolver team – CSPs C&M issue - Phone call Dedicated Cutover SPOC for CSPs, software Fallback and rollback Training and Web chat and Migration Trade houses and large companies support webinars Support Team Transitional Cutover and Migration enhanced support model - Provided by CDS as additional resource Protective marking – Unclassified, Protect, Restricted (delete as required) | 05/07/2017 | 13
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. Protective marking – Unclassified, Protect, Restricted (delete as required) | 05/07/2017 | 14
CHIEF to CDS Key differences - UCC Data Changes Alignment with International Standards : EU Customs Data Model (CDM). ▪ Increased number of items per ▪ Harmonised Location of Goods declaration (implications for SLAs). identification (based on ▪ Rationalisation of Customs UNLOCODE). ▪ Harmonised Warehouse Type Procedure Codes. ▪ An audit trail of previous document code list. ▪ Harmonised Method of Payment IDs. ▪ Data about additional party types codes. ▪ Harmonised Unit of Quantity (egg Buyer, Seller) : need to be clear on when data must be codes (ISO). ▪ Harmonisation of Item Tax Line; no supplied, and default values when data is not available. Tax Rate Identifier (we need to ▪ Provision for extra commercial work through which data items references / Tracking numbers. have to be explicitly declared and ▪ Harmonised EU Customs Office which can be derived by CDS or Lis’. Tariff). ▪ Levelling – change for some data items between Header and Item. Protective marking – Unclassified, Protect, Restricted (delete as required) HMRC NL Standard | 05/07/2017 | 15
Recommend
More recommend
