Table of Contents

General Principle:

Fortress  Fortress GB is an access control system deployed by many UK football clubs.

It provides SecuTix clients with two basic sets of functionalities.

An access control system

Fortress GB is handling access control at the gates with a strong limitation:

Fortress GB does not handle retrieval of controlled tickets. The controlled status of the tickets cannot be retrieved in SecuTix.

An external printing system

Fortress is printing the RFID cards for season tickets for SecuTix clients, with two main cases:

Direct printing at the box-office on "real" printers

Mass printing on "virtual" printers (ticket data are only sent to Fortress)

Fortress being two systems in once in SecuTix point of view, we need to set up two external interfaces: an access control interface and an external printer interface.

It also provides smart barcode functionality that you must activate.

Smart barcode

To activate the smart barcode (encrypted barcode understood by Fortress scanners), go in the organization screen and select "Access control type: Fortress GB"

It will generate a Fortress barcode for all the tickets linked to a seat linked to an area mapped to Fortress through an access control mapping (see below). Else it will generate a Date SecuTix barcode.

Concession barcode

Fortress tickets may have two barcodes, one being the concession barcode, displayed in template using key exr_fortress_concession_barcode

To have this concession barcode please follow the following setup: set the parameter Concession tariff id id in the interface with the integer id provided by Fortress support.

It is also possible to override this id for a given tariff by modifying its mapping, setting an external id   with a WW_DD_DD structure (code + id1 + id2), id2 being the id of the concession tariff, to be provided by Fortress Team.

Important: if neither of these two methods is used, the concession Barcode will not be generated, but the ticket purchase will still work. This new barcode will be stored in an external reference related to the movement. It can be seen in the ticket details screen.

Access

Control Inerface:

Set up

Create an access control interface of type "Fortress GB"

New Interface →  Control Interface →  Fortress GB Control Plugin

Image Added

Fill the following values on the previous image, which should all be provided by the client or by his Fortress provider.

For the URL → remember to have the

URL authorized through

Secutix proxy.

 Mappings.

Image Added

All of them are mandatory.

Then fill the following mappings.

• Fill area and block mappings, for every area and block of the stadium/venue that will be controlled by Fortress.
• Check that the physical configuration code is the same as the stadium code defined in Fortress.
• Check that the entrances' codes are the same as the gate codes defined in Fortress.

(JNO : Why we did not ask Uzi about automating these mappings creation ?)

Schedule

Create a schedule running every 5' for each event that you plan to have controlled through Fortress.

Validation

Sell a ticket for each stand of the venue, wait for 5', check that those tickets can pass the gate in Fortress.

Refund a ticket, wait for 5', check that it cannot pass the gate in Fortress.

In case it where not working, check the error logs in the executions and work out until the tickets are accepted/are refused at the gates.

Important: Mapping of Concepts

Image Added

Good Practices:

When creating a new mapping for performance, tariff, entrance and season, please use the following format in the external ID to avoid errors:

Image Added

It is necessary to contact Fortress to check if there is a mapping available for what operator is looking for, if there is not an available mapping, as an operator I can create a new one calling Fortress WS. Please make sure in Fortress Documentation that that mapping type It can be created by a Webservice.

Useful Webservices to know Fortress IDs

Tariffs: Get Price Band List (POST)

Name: PriceBandList

Description: get a list of all aviabable price bands code on the Fortress Database

Request URL: http://{endpoint}/api/Products/PriceBandList/

 Performances: Getproductlist (POST)

Name: ProductList

Description: Return a list of products available on the fortress server

Request URL:http://{endpoint}/api/Products/ProductList/

 Entrances: Get Service List (POST)

Name: ServiceList

Description: Return a list of Services available on the fortress server

Request URL: http://{endpoint}/api/Products/ServiceList/

Schedule

There are two functions in the schedules in the Access control interface developed for v2: Synchronize Tickets and retrieve controlled tickets. For this fortress set up, add just synchronize tickets.Image Added

Configuration

Launch: Manual or Automatic

Batch size: 100 default

Event and performance: follow the formatà eventCode;DD/MM/YY hh:mm (24hours format)

Extract Fortress actual active data for comparison (do not use systematically): If it is active, Secutix system  call Fortress webservice  for a specific  match(indicated on the previous parameter) which will compare all the tickets from Secutix and fortress (valid or invalid)

Skip tickets: If the ticket is in Secutix list but not in Fortress, It will be included and sent to Fortress, If it is already on fortress list, it will be skipped, no further actions will be executed. Operator can select tickets to avoid sync with fortress. This ticket will always be ignored on the calls to fortress WS.

Search ticket Parameter format

Image Added

Cancelled tickets are flagged as error and are not flagged as “synchronized” . A change has been made so that is not an error, it is just a warning in the log lines.

External Printing System