S-360 Documentation

Page tree

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

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 (they are both access control systems), their behavior in SecuTix is entirely different.

General setup of the interface

See example below in screen capture, with the explanation for the parameters.

Definition of mappings

SecuTix conceptFortress GB conceptMapping data typeMapped value
PerformanceProductDescription.

Performance

Product description's code
Season TicketProductDescriptionProductProduct description's code
TariffPrice bandAudience sub categoryPrice band code
Physical configurationStadiumPhysical configurationStadium code
AreaStandAreaStand code
BlockAreaBlockBlock code
EntranceServiceNANA
  • Concerning product mappings : Fortress matches are mapped to SecuTix performances. But, in an external manager context, we must create a mapping for a product in ordre to tell SecuTix that this product is handled by Fortress GB. In consequence, every event or competition must be mapped to a value of -1, not used by Fortress GB, but indicating that this product is "managed by" Fortress GB.
  • If no mapping is defined for the tariffs, physical configurations, areas, blocks and entrances, the object's code will be transmitted to Fortress.
  • All the mappings must be defined (run batch "check mappings" to check that point). If a mapping is missing, SecuTix cannot guarantee the system behavior.

 



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


  • No labels