10.08.2012 Views

Fallback and Recovery Specification (FRS)

Fallback and Recovery Specification (FRS)

Fallback and Recovery Specification (FRS)

SHOW MORE
SHOW LESS

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

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

DG TAXUD – EXCISE COMPUTERISATION PROJECT REF: ECP2-FITSDEV2-SC03-<strong>FRS</strong><br />

FALLBACK AND RECOVERY SPECIFICATION (<strong>FRS</strong>) VERSION: 3.11-EN<br />

Introduction<br />

Acronym Translation<br />

Found in<br />

GLT<br />

MSA Member State Administration yes<br />

N/A Not Applicable no<br />

NACK Non-ACKnowledgement service message yes<br />

SAD Single Administrative Document no<br />

SEED System for Exchange of Excise Data yes<br />

SEP Security Policy yes<br />

STD State Transition Diagram yes<br />

TAXUD Directorate-General Taxation <strong>and</strong> Customs Union yes<br />

UC Use Case yes<br />

1.7 Assumptions<br />

Table 3 specific glossary of acronyms used in the <strong>FRS</strong><br />

This <strong>Fallback</strong> <strong>and</strong> <strong>Recovery</strong> <strong>Specification</strong> is written according to the following<br />

assumptions:<br />

1. legal <strong>and</strong> regulatory provisions are respected by all involved parties; irregularities <strong>and</strong><br />

infringements pertain to the processing of inquiries;<br />

2. roles <strong>and</strong> responsibilities never change; if, for some reason, an intermediate acts by<br />

delegation of a partner (for instance, an excise officer enters a report of receipt on<br />

behalf of the consignee), the responsibility rests with the delegating actor;<br />

3. if the normal communication medium between an economic operator <strong>and</strong> its MSA<br />

fails, alternate communication media (fax, digital memory medium or paper) will<br />

always be available.<br />

ECP2-FITSDEV2-SC03-<strong>FRS</strong>v3.11.doc Page 13 of 53

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!