Fortress GB configuration

General Principle

Fortress GB provides two very distinct and different functionalities.

• Providing barcodes for single match tickets
• printing (and re-reprint, and canceling) season ticket cards.

Beware : Fortress GB is not the same system as the Fortress (=StadAccess) used at Stade de France. Although they are related, and 

General Principle: Fortress GB generates the barcodes and prints the Season Ticket cards

this has some impacts:

1. Seatmap inside SecuTix and Fortress Gb has to se synchronized:
   1. same area codes + block codes + row + seat number
      1. Secutix Area matches with Fortress Stand
      2. Secutix Block matches with Fortress Area
   2. SecuTix outer perimiter entrance codes must match with Fortress gates' codes
   3. SecuTix inner perimiter entrance codes must match with Fortress turnstiles' codes
2. Product + Tarriff + XXX codes have to match between SecuTix and Fortress GB
3. When a ticket is created, Fortress generates
   1. a standard barcode, which is stored in SecuTix ticket's barcode and in ExternalManagerMovement barcode field.
   2. an Adult barcode, stored in external manager movement externalValue2 field, which is then available on ticket editor with field named zzz_customParameter02
   3. a Concession barcode, stored in external manager movement externalValue3 field, which is then available on ticket editor with field named zzz_customParameter03
   4. a ticket identifier,stored in external manager movement ticketReference and externalValue1 field, which is then available on ticket editor with field named zzz_customParameter01
4. When a season ticket card is printed, secutix stores season start and season end dates in card validity dates