HMRC Exports CHIEF/CDS Cut-Over Strategy

Slide Note
Embed
Share

This document outlines the proposed IT cut-over strategy from customers' use of CHIEF to a dual running system of CDS and CHIEF Exports. The strategy includes migration milestones, phases, CSP involvement, traders' migration processes, declarations, consolidations, movements, and milestones. It details the transition process, highlighting key actions and considerations for a successful migration.


Uploaded on Sep 17, 2024 | 0 Views


Download Presentation

Please find below an Image/Link to download the presentation.

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. Download presentation by click this link. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.

E N D

Presentation Transcript


  1. HMRC Exports CHIEF/CDS Cut Over Strategy This document covers the proposed IT cut over strategy from customers sole use of CHIEF to CDS/CHIEF Exports Dual Running. This is a working document that is subject to change.

  2. Migration Milestone No change Migration throughout the phase Turn off Migration CHIEF de-commissioned First CSP joins Last CSP joins Phase 1 Phase 2 Phase 3 Last SWD joins First SWD joins CSP s continue to submit messages to CHIEF CSP s can continue to submit messages to CHIEF and can start submitting to CDS Migration complete No change for traders using SWD route to CHIEF via a CSP Traders using SWD route to CHIEF via a CSP can start to migrate to use CDS software (dependency on SWD rollout) Migration complete No change for traders using SWD route to CHIEF via EDCS Allow selected traders to migrate to CDS API (dependant on SWD readiness) Migration complete Traders using SWD route to CHIEF via EDCS can start to migrate to use CDS software (dependency on SWD rollout) Declarations Not available No change for traders using route to CHIEF via HCI Screens Traders using route to CHIEF via HCI Screens can continue in Phase 2 No change for traders using NES WEB route to CHIEF Traders using NES WEB route to CHIEF can continue in Phase 2 Not available Allow selected traders access to CDS UI Open access for traders to migrate to CDS UI Participating CSP s can submit messages to CDS All CSP s migrated to CDS Migration complete CSP s providing consolidation processing can migrate to CDS CSP s providing consolidation processing have migrated to CDS Migration complete Non-participating CSP s continue to submit messages to CHIEF No change for consolidators/loaders using SWD route to CHIEF via a CSP Migration complete Consolidators/loaders using SWD route to CHIEF via a CSP can start to migrate to use CDS software (dependency on CSP participation in phase 1 and SWD rollout ) Consolidations Not available Turn off EAC messages for route to CHIEF via EDCS (CST remains available) Allow consolidators/loaders to migrate to CDS API (dependency on SWD rollout) No change for consolidators/loaders using SWD route to CHIEF via EDCS Allow selected consolidators/loaders to migrate to CDS API (dependant on SWD readiness) Migration complete No change for consolidators/loaders using route to CHIEF via HCI Screens Turn off EAC messages for HCI Screens (CST remains available) Not available No change for consolidators/loaders using NES WEB route to CHIEF Turn off EAC messages in NES WEB (CST remains available) Not available Migration complete Open access for consolidators/loaders to migrate to CDS UI Allow selected consolidators/loaders access to CDS UI Participating CSP s can submit messages to CDS CSP s providing movement processing can migrate to CDS Migration complete All CSP s migrated to CDS Migration complete CSP s providing movement processing have migrated to CDS Non-participating CSP s continue to submit messages to CHIEF No change for loaders using SWD route to CHIEF via a CSP Loaders using SWD route to CHIEF via a CSP can start to migrate to use CDS software (dependency on CSP participation in phase 1 and SWD rollout ) Movements Migration complete Turn off movement messages to CHIEF via HCI Screens Not available No change for loaders using route to CHIEF via HCI Screens Not available Migration complete No change for loaders using NES WEB route to CHIEF Allow selected loaders access to CDS UI Turn off movement messages in NES WEB Migration to CDS UI complete

  3. Scope for selected trader migration in Phase 1 Requirements The migration strategy for exports dual running in Phase 1 is supply chain orientated rather than location or trader specific. Selected traders for migration in Phase 1, can include those who submit supplementary declarations to CHIEF via non-CSP routes or via a CSP able to handle CDS declarations. Selected traders for migration in Phase 1, can include those who submit frontier declarations to CHIEF via either NES WEB route or SWD route via EDCS (non-CSP routes). These traders should also now have access to either CDS UI or CDS API (dependent on SWD readiness) for submitting declarations in CDS (CSPs only accept EDIFACT declarations in Phase 1) These traders must submit consolidations to CDS only via CDS UI or CDS API. These traders must not accept third party declarations for consolidation (CHIEF declarations will not be consolidated). Movement processing must be via either a CSP participating in Phase 1 or by a loader using CDS UI. Traders that are selected for migration in Phase 1, can continue to operate existing business models at other locations with no impact. All NES WEB loaders must have migrated to CDS UI by the end of Phase 1. This is a dependency for the start of Phase 2. (There are currently 11 active NES WEB loaders)

  4. Scope for selected trader migration in Phase 2 Requirements The migration strategy for exports dual running in Phase 2 has more flexibility. Traders who submit declarations and consolidations via SWD (either via CSP or EDCS) can migrate to CDS, dependent on SWD readiness. Traders who submit declarations and consolidations via NES WEB can migrate to CDS, dependent on access to CDS UI. Loaders submitting movement messages via a CSP or SWD via a CSP with a message translator will have migrated in Phase 2. Loaders submitting movement messages to CHIEF via NES WEB will have migrated to CDS UI by the start of Phase 2. All inventory linked locations will be CDS ready at the start of Phase 2. Non-inventory linked locations will be CDS ready dependent on loader readiness. (N.B these loaders require access to CDS UI at the start of Phase 2 or manual processing will be required.)

  5. Alternative Message Routings During Phase 2, shut consolidation messages (CST) will continue to be sent to CHIEF. Other consolidation and movement messages that are sent direct to CHIEF will be stopped. The following alternative mechanisms will be available: Traders who submit consolidation messages using SWD route to CHIEF via EDCS will now need to consolidate by declaration until SWD rollout. Traders who submit consolidation messages using NES WEB route to CHIEF will now need to consolidate by declaration until gaining access to CDS UI. Traders who submit consolidation messages using HCI Screen route to CHIEF will now need to consolidate by declaration until gaining access to an alternative CDS route. Loaders who submit movement messages using NES WEB route to CHIEF will need to gain access to CDS UI at the start of Phase 2. Loaders who submit movement messages using HCI Screen route to CHIEF will be migrated to Phase 2 by CSP/ CSP with message translator.

Related


More Related Content