Fallback and Recovery Specification (FRS)

More documents

Recommendations

Info

DG TAXUD – EXCISE COMPUTERISATION PROJECT REF: ECP2-FITSDEV2-SC03-FRS FALLBACK AND RECOVERY SPECIFICATION (FRS) VERSION: 3.11-EN Solution elements No recovery is then needed. Note: at dispatch, if the expected delay exceeds up to a few hours, this being not judged acceptable by the trader, the latter has to use an alternate way to communicate the movement information to the excise office (see FB01) before departure of the goods. Example: If submission of the report of receipt is temporarily unavailable, the consignee, based on the rules established by its Administration, may consider it acceptable to wait a few hours (or even up to one to two days before considering reverting to fallback paper procedures) before submitting it. This would have little impact on the excise business. 5.3.5 FB06: Notify administration This response exclusively addresses the communication between an economic operator and his national Administration. Consequently, its detailed definition depends on national provisions. The transmission channel may be any solution found relevant by the MSA, such as: � access to a support Web portal; � e-mail; � fax; � phone call to a help desk; � SMS to a dedicated number; � etc. This amounts to an anticipated announcement that, during the indicated period, the economic operator could directly use alternate solutions (typically, fall back to paper) without trying the standard solution. Example: In case of a long-lasting unavailability of the IT system of an economic operator, this latter impacts business processes that are critically time-dependent. The economic operator may be required to inform the competent Administration of the nature and conditions of the exception. This information should contain at least: � list of the unavailable functions; � expected time to recover. Typically, during that period, a consignor may be allowed to directly use the fallback AAD without trying an electronic submission that will surely fail. Conversely, as the time constraint for the submission of a report of receipt is not very stringent, the consignee should preferably wait for the electronic system to recover to submit a report of receipt. ECP2-FITSDEV2-SC03-FRSv3.11.doc Page 36 of 53
DG TAXUD – EXCISE COMPUTERISATION PROJECT REF: ECP2-FITSDEV2-SC03-FRS FALLBACK AND RECOVERY SPECIFICATION (FRS) VERSION: 3.11-EN Solution elements 5.3.6 FB08: Notify economic operator That response exclusively addresses the communication between an Administration and an economic operator of its Member State. Consequently, its detailed definition depends on national provisions. In all cases where a severe exception arises that necessitates the collaboration of an economic operator, the competent Administration contacts that operator to establish the relevant actions. The transmission channel may be any solution found relevant by the MSA, such as: � e-mail; � fax; � SMS to a registered number; � etc. Example: The application of the MSA of dispatch starts a timer (for example, TIM_CHS) to expire in a given time limit by which the consignor is expected to issue either a change of destination or a splitting. If no such operation has been submitted within the time limit, the MSA shall issue a reminder notification to the consignor. If this reminder is not electronically implemented by the NEA then the MSA can send the reminder outside the system via any of the above mentioned means (such as, e-mail, fax, or SMS to a registered number, etc). 5.4 Recovery solution elements RC03 Restart or replace technical component RC04 Enter data using the normal procedure RC05 No intervention - accept exception RC06 Collate electronic record with the fallback form RC07 Replay information exchange RC10 Re-apply undone changes Recovery solution elements are used to correct defective information or to complete missing information resulting from errors that have occurred in the system, from mistakes made by users, or from the application of fallback solutions. If it is considered that the business impact of an exception is acceptable, a „No intervention – accept exception‟ solution is also available. 5.4.1 RC03: Restart or replace technical component If some component necessary to complete a business process is found unavailable or faulty, processing cannot carry on any more. The failing component must be restarted or replaced as soon as possible. ECP2-FITSDEV2-SC03-FRSv3.11.doc Page 37 of 53
Page 1 and 2: OWNER DG TAXUD ISSUE DATE 01/12/200
Page 3 and 4: DG TAXUD - EXCISE COMPUTERISATION P
Page 35: DG TAXUD - EXCISE COMPUTERISATION P
Page 53: DG TAXUD - EXCISE COMPUTERISATION P

Fallback and Recovery Specification (FRS)

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?