There are tags within the Axess Smart Printer layout that are used to encode the RF chip and there are tags used to pass information to Axess via the SOAP EDE interface (and some do both). Most of these values are defined by the client during the initial training from Axess in Austria.

 

The Ticket Type is a preset program value within Axess used to define the type of data that needs to be encoded in the RF chip for proper gate validation. In Axess, this is often referred to as the Core Ticket Type. See the Required Tags Based on Axess Ticket Type section below for more information. The Ticket Type value needs to be included in the Axess Smart Printer layout, is encoded in the RF chip and is passed to the Axess database via the SOAP EDE.

 

 

RF and Barcode values determine whether the ticket or pass uses an encoded RF chip or a printed barcode for validation at the gates. You cannot use RF encoding and a printed Axess barcode on a single piece of media, and only certain Ticket Types can use a barcode for gate validation: 1, 2, 3 and 15. The RF or Barcode value must be specified in the layout, although they are not passed to Axess via the SOAP EDE.

 

 

 

 

If using a printed barcode instead of RF encoding, you must also specify the barcode position on the media:

 

 

The POS number is unique per salespoint and is defined in the Ports.INI file: [SmartPrinter] POS=###. The Serial number ranges from 1-49,999 for access records and from 50,000-99,999 for guest pass records.

The combination of POS#, Project #, and incrementing Serial # value (1-49,999 or 50,000-99,999) create the contents of the rf_serial field in the Siriusware Access and gst_pass tables. The POS and RF Serial numbers are encoded into the RF chip by the Axess printers, but this happens automatically and does not need to be specified within the layout. The POS and Serial numbers are always part of the information passed to Axess via the SOAP EDE.

 

Pool is a defined group of gates. For instance, All Mountain Gates, All Mountain Gates plus Ice Rink, Ski School Gates, etc. The Pool needs to be specified in the Axess Smart Printer layout, is encoded in the RF chip and is passed to Axess via the SOAP EDE.

 

 

Reader Person Group is a classification of customers typically based on age or status, and is used to generate a visual indication of the type of person going through the gate. For instance, ADULT, SENIOR, CHILD, STAFF. The Reader Person Group needs to be included in the Axess Smart Printer layout. It is encoded in the RF chip but is not passed to Axess via that SOAP EDE.

 

 

Week indicates a predefined set of days of the week. For instance, Weekday Only, All Week, Sunday Only, etc. Additionally, in Axess it is possible to set the valid time of day based on day of week. For instance, Sunday through Friday the ticket can be used all day, but on Saturday the ticket cannot be used until 3:00 PM. It needs to be specified in the Axess Smart Printer layout and is encoded in the RF chip. It is not passed to Axess via the SOAP EDE.

 

 

Time indicates a predefined time range in a 24 hour day. For instance, All Day, Night Only, Morning Half Day, Afternoon Half Day, etc. Additionally, in Axess the number of hours the ticket can used based on the first read can be specified. For instance, a ticket can be sold that expires four hours from first use. Another example would be a five day ticket that allows a ticket to be used for two hours during each of the five days (good for school programs). It needs to be specified in the Axess Smart Printer layout and is encoded in the RF chip. It is not passed to Axess via the SOAP EDE.

 

 

Season indicates a predefined date range within a calendar year. For instance, Winter Season or Summer Season. If pass sales for next season occur during the current season and the next season passes cannot be used for the remaining portion of the current season, a new Season definition needs to be created in Axess for each operational year.

 

The current season ends on April 30, 2012. Pass sales for 2012-13 go on-sale on March 1, 2012. If a customer purchases a 2012-13 pass between March 1 and April 30 and is allowed to use the 2012-13 pass for the remaining days in the 2011-12, then only one Season value needs to be entered in Axess, and that value can extended. But, if the 2012-13 pass cannot be used for the remaining portion of 2011-12, a new Season value representing the 2012-13 operational year needs to be entered in Axess. Then, the Season value needs to be specified in the Axess Smart Printer layout depending on the Ticket Type (see the Required Tags Based on Axess Ticket Type section below) and is encoded in the RF chip. It is not passed to Axess via the SOAP EDE.

 

 

The Start Date is the first valid date of the ticket or pass. It does not need to be specified in the Axess Smart Printer layout but it does get automatically encoded in the chip depending on the Ticket Type and sent to Axess via the SOAP EDE.

 

The Expiration Date is the last valid date of the ticket or pass. It does not need to be specified in the Axess Smart Printer layout but it does get automatically encoded in the chip depending on the Ticket Type and sent to Axess via the SOAP EDE.

 

Rides indicates the number of rides allowed per gate in the specified pool. For instance, on or two Scenic chair lift rides, as opposed to an All-day unlimited scenic rides type of ticket. It needs to be specified in the Axess Smart Printer layout depending on the Ticket Type (see the Required Tags Based on Axess Ticket Type section below) and is encoded in the RF chip. It is not passed to Axess via the SOAP EDE.

 

 

Period (number of days)

Period indicates the number of days that a ticket or pass can be used. For instance, a three day ticket, a four day ticket or a five day ticket. It needs to be included in the Axess Smart Printer layout depending on the Ticket Type (see the Required Tags Based on Axess Ticket Type section below) and is encoded in the RF chip. It is not passed to Axess via the SOAP EDE.

 

 

This is the number of total points to load on a ticket. It needs to be specified in the Axess Smart Printer layout depending on the Ticket Type (see the Required Tags Based on Axess Ticket Type section below), and is encoded in the RF chip. It is not passed to Axess via the SOAP EDE.

 

 

This tag is used for tickets that offer X out of Y days. For instance, a three out of five day ticket. The available days tag is used to define the number of days that the ticket can be used, so for this example, 3. It needs to be specified in the Axess Smart Printer layout depending on the Ticket Type (see the Required Tags Based on Axess Ticket Type section below), and is encoded in the RF chip. It is not passed to Axess via the SOAP EDE.

 

 

This tag is used for tickets that offer X out of Y days. For instance, a three out of five day ticket. The restricted days tag is used to define the full time span (or duration) of the ticket, so for this example, 5. It needs to be specified in the Axess Smart Printer layout depending on the Ticket Type (see the Required Tags Based on Axess Ticket Type section below) and is encoded in the RF chip. It is not passed to Axess via the SOAP EDE.

 

 

The Hours tag is used for tickets that expire X hours after the first use at the gate. For example, a four hour ticket that is read at the gate at 10:15 AM expires at 2:14 PM. The <Hours> value needs to be specified in the Axess Smart Printer layout depending on the Ticket Type (see the Required Tags Based on Axess Ticket Type section below) and is encoded in the RF chip. It is not passed to Axess via the SOAP EDE.

 

 

Customer Ticket Type is a broad classification of items, for instance Unlimited Season Pass, Midweek Pass, All Day Ticket, Half Day Ticket, 2 Day Night–Only Ticket, etc. The Customer Ticket Type needs to be included in the Axess Smart Printer layout so that it can be passed to Axess via the SOAP EDE (it is not actually encoded in the RF chip.) The CustomerTicketType values used in Siriusware Axess Smart Printer layouts must correspond to the Customer Product Types (EDE Numbers) set up in the Axess system. A match in these two values is critical for proper encoding by the gate when a WTP record is processed. Please refer to the Information Included in the Send Sale SOAP EDE Call below for a detailed description of how the CustomerTicketType interacts with the Axess Customer Product Type (EDE Number) for reloads at the gates.

 

 

Customer Person Type is another broad classification of items, but typically based on an age range or status. For instance, Adult, Senior, Senior 70+, Child, Child Under 5, Part Time Staff, Full Time Staff, Management, etc. The Customer Person Type needs to be included in the Axess Smart Printer layout so that it can be passed to Axess via the SOAP EDE. It is not actually encoded in the RF chip. To keep configuration in Axess easy, the CustomerPersonType value always corresponds to the ReaderPersonGroup value.

 

 

This is the date/time field of the access or gst_pass record. It does not need to be included in the Axess Smart Printer layout and it does not get encoded in the RF chip. It does get sent to Axess via the SOAP EDE.

 

This is the price paid for the item (original or reload). It does not need to be included in the Axess Smart Printer layout, it is not encoded in the RF chip, but it is passed to Axess via the SOAP EDE.

 

Free of charge indicates that the purchase price was $0.00. It does not need to be included in the Axess Smart Printer layout and it is automatically encoded in the RF chip, but only for Ticket Type 2 products. It is not sent to Axess via the SOAP EDE.

 

Handfeed is specified in the Axess Smart Printer layout and is used to prompt for a hand-feed of media or a feed from the hopper. Set to 0 to feed from the hopper and set to 1 to hand-feed.

 

 

The Chip ID (WTP) is a number generated by the Axess printer that is inserted into the wtp_no field of the access or gst_pass record. This number is unique per chip/piece of media and is inserted into all transactions involving a given piece of media (original purchase and all reloads using that same media). It is also the number entered within E-Commerce module during the reload process. It does not need to be included in the Axess Smart Printer layout. It is only passed to the SOAP EDE for web (E-Commerce module) reloads or media-not-present reloads at the salespoint.

 

Add this in order to trigger the two step printing process for graphic printing of a pass through a Fargo/Magicard printer followed by encoding through the Axess Smart Printer.

 

 

This tag can be used to give the operator an option to NOT encode a hopper-fed pass when a sale is finalized at a salespoint that uses PrintPassOnFinalize=TRUE. The default value is 0 (encode from the hopper without prompting the operator with a message between each print). This is only set to 1 for pass items (not access items) that do not use the two step (ExternalPrint) process and that pull from the hopper (are not hand-fed) and there is a need to sell the passes independently of printing (for instance, a guest photo or liability still needs to be collected prior to printing) and salespoints are configured with PrintPassOnFinalize=TRUE.

 

 

Add this in order to suppress the erase function prior to printing for new media. This can increase the speed by which new media is printed from the Axess Smart Printers. Reload layouts do not include this as it is important to erase the card prior to printing (or this value is set to 0).