Fallback and Recovery Specification (FRS)

DG TAXUD – EXCISE COMPUTERISATION PROJECT REF: ECP2-FITSDEV2-SC03-FRS
FALLBACK AND RECOVERY SPECIFICATION (FRS) VERSION: 3.11-EN
Specific provisions during the rollout of EMCS
8 Specific provisions during the rollout of EMCS
This chapter describes the specific provisions to be applied to the fallback and recovery
procedures of EMCS during Migration Period 1 defined in the PSS [R3] namely:
FS0/FS1 coexistence during Migration Period 1 (rollout of the FS1 functionality).
This analysis is essentially based on the General Process Threads and Support Threads
described in the Appendix A of the Phasing and Scope Specification (PSS).
The exceptions and the related scenarios are described in the Appendix A of the PSS
where they are explicitly addressed. These exceptions or scenarios are either specific to
the migration periods or extended from the unavailability exceptions of the target system.
It shall be noted that no specific provisions apply to the fallback and recovery procedures
of EMCS during the operations of Phase 3, since according to the updated Master Plan
[R7] there will be no co-existence of FS1 and FS2 (all MSAs will enter the EMCS Phase
3 operations at milestone Mc).
8.1 Fallback and recovery during Migration Period 1
Most generally, the design of FS0/FS1 is intended to provide a full service to all
movements that can be electronically submitted in a Member State in FS1, FS0 being
exactly tailored to ensure the destination functionality.
Therefore:
� the fallback and recovery provisions that are defined in the FRS concerning the use
cases included in FS1 are adequate to respond to the exceptions arising during the
coexistence of FS0 and FS1; note in particular that the management of SEED and of
reference data being a prerequisite to the migration milestone Ma, the related use cases
are to be considered a part of FS0;
� all complementary requirements attached to these exceptions must be considered an
integral part of FS0 or of FS1, according to the EBP where the exception arises.
In addition, a few particular cases deserve setting up temporary responses.
8.1.1 Unavailability of the automatic triggering of risk assessment
The automatic connection with the risk assessment functionality is not included in FS1;
until the concerned MSA is in FS2, it is replaced by a manually triggered fallback risk
assessment that may result in fallback administrative cooperation exchanges.
This is not really an exception; however it has been explicitly mentioned in the Appendix
A for all application points of risk assessment in all use cases of the FESS [R6] that
belong to FS1.
8.1.2 Exportation of goods in an MSA different from the MSA of dispatch
The exportation functionality is supported through three use cases, all of which are
assigned to FS1 (no EBP has been included in FS0).
ECP2-FITSDEV2-SC03-FRSv3.11.doc Page 51 of 53