Scanning and Gates Intermediate

By: Ed Simmerson, Matt Messinger, Lisa Goring

2

• Identify what can be accomplished with scanning and access control • Explain the similarities and differences between ScanMan/GateKeeper

and Axess Gates • Discuss Siriusware Validation Functionality • Discuss Axess Validation Functionality

Question… • How many are here for ScanMan? • How many are here for GateKeeper? • How many are here for Axess RFID gates?

Objectives

3

Similarities • Either RFID or barcode • Used to validate products for access control • Use Siriusware reporting - the Axess scans are retrieved by Siriusware • Functionality that can be used:

– Dynamic Revenue Recognition – In House Cards – Discount Validation – Specific Salespoint Programs

• Guest information visible (photo and name)

Similarities/Differences in Solutions

4

Differences

Similarities/Differences in Solutions

Technology Off-Line Validation Configuration Form Batch Number of Passes

Reload On-line

Room Key

ScanMan UHF Trickling SalesEZ Siriusware Handheld Print 1 + Cascading

Cascading for Passes No

GateKeeper UHF Trickling SalesEZ Siriusware Gate / Turnstile Print 1 +

Cascading Cascading for Passes No

Axess HF On-Chip Axess Gate Axess & Siriusware

Gate / Turnstile

Print or Encode Up to 3 WTP Yes

Note: Validation is either Siriusware OR Axess – you cannot combine the two systems for access validation.

Share Code Can be used together Checkpoints Hotlist Hardware1 Interactive

Activities

ScanMan Yes X No Yes Symbol Scanner Yes2

GateKeeper Yes X Yes No PC No

Axess No - No Yes Gate and Gateway No

1. PC requires less upkeep than a symbol scanner which requires a lot of upkeep (access through ActiveSync, keeping batteries charged and changed, mobile hardware requires lots of warm and cold booting).

2. ScanMan Interactive activities: Pass info, Scan info, e-msg, inquiry scans, etc.

5

ScanMan/GateKeeper Commonalities General Operation • Check for special scan (configuration or location or operator) • Perform Extraction and Prepend checks • Decrypt, if necessary

– Is it a card (more than 15 digits)? If so, no decryption – Is valid prefix? If not, use exception (external) table & don’t decrypt. – Decrypt if still warranted

• Check expiration date • Check hotlist (ScanMan only) • Call attempt online validation via SalesEZ

Siriusware Validation

6

ScanMan/GateKeeper Commonalities Online Operation • Do a live check to the server to see if a ticket or pass is valid. • If no response from server, save scan so that it can be recorded later (now offline). • Perform validations with the server which can remove or add uses, or just log use. • Maintain an “in park count”, if configured to do so. Offline Operation (Trickling) • Both ScanMan and GateKeeper keep scans that are done off line. • These are trickled in when idle. • Trickled scans are recorded slightly differently in the data. • ScanMan should be monitored to make sure it trickles as part of procedure.

Siriusware Validation

7

ScanMan/GateKeeper Commonalities - INI Setting Highlights DCI setting • Allows using something other than auto-validation. • DCI can be created to specify a new validation template.

– Example: scan in parking lot to see if valid but not remove a use. Guest Photo and Text Display • Able to display first name, last name, height, age, and birth date along with static text

– Example: Welcome *FNAME* *LNAME* - *HEIGHT*

• Make sure pictures are small • ScanMan: Setting to make the picture available even if the scan was bad.

– PALW=1 in the INI or SETPALW1 at the manual dialog or scanned will enable it • PALW stands for PictureALWays

Siriusware Validation

8

ScanMan

Siriusware Validation

Basic Operation • Configure the scanners (wireless, persistence,

load software, settings) • INI settings can be in an INI file that is

copied to all units • INI settings can also be scanned in on the

units • Keep extra batteries around • Warm Boot when it arrives on location in the

morning • Trickle as soon as you can (certainly before end

of day) • Treat scanner like “bucket” of scans

(always in danger of being spilled) if offline • ScanMan needs “deployment” and “collection”

procedures to work right. It needs to be someone’s responsibility.

9

ScanMan Sleeping • Scanners “sleep” to conserve battery power on some interval (can be set

in scanner configuration). • Connections to SalesEZ are “abandoned” if it sleeps while online. • ScanMan preemptively disconnects after a minute to skirt this problem –

reconnects fast when the next scan arrives.

Siriusware Validation

10

Siriusware Validation

11

Siriusware Validation

12

Siriusware Validation

13

Siriusware Validation

14

• Allows offline scanning to know of invalid passes. • Requires keeping scanners up to date before deploying to areas w/o radio

contact (or intermittent contact). • Obtained when started (not updated during the day). • Online is better (live hotting of passes).

Siriusware Validation

15

ScanMan’s “special” scan prefixes • Start with ‘SET’ (unless LOC & OP – sometimes). • Set .INI settings or get information. • Note: These can be concatenated with semicolons

– E.g., SETLOCMATT; SETLOG5; SETIS341 • Complete list of setting is in the documentation

Siriusware Validation

16

ScanMan Troubleshooting • Symbol scanners are persnickety; Need to be careful with them. • Warm Booting and Cold Booting are things you’ll need to do with some

regularity. • On 9090

– Warm booting – Hold down power button for 15 seconds. – Cold booting – Eject battery, hold down trigger and power button, re-insert

battery. • Warm booting and cold booting

– A warm boot resets many settings on the scanner and can fix most difficulties. – A cold boot resets everything in non-volatile memory. On the 9090s you don't

lose anything with a cold boot either. – Always try a warm boot first. – Take time to ensure settings you want to keep are not wiped out during a cold

boot (by proper installation and setup).

Siriusware Validation

17

GateKeeper Basic Operation • Set up images and sounds and INI file • Reboot it nightly • A lot simpler (in some ways) than ScanMan

Siriusware Validation

• Meant to be used without an attendant (although an attendant helps)

• Often used in conjunction with ScanMan

18

Gates for in-park counts • To keep track of number of people inside • Name and value sent to SalesEZ • Can use a value of IN, OUT or whatever you like • Update happens when Interval elapses (since last submission),

IdleTimeout elapses (since last entry), or a specific time occurs.

[Checkpoint] SimpleCheckpoint=TRUE Interval=20 IdleTimeout=10 ResetTimes=8:00;12:00;18:00 Name=ParkEntrance Value=OUT

Siriusware Validation

19

GateKeeper – Programs • Can change how GateKeeper responds based on the DCI of the pass /

ticket.

[Program1] GoodBmp=GoodChild.bmp GoodSound=GoodChild.wav DCI=TICKETS,ALLDAY,CHILD;TICKETS,HALFDAY,CHILD [Program2] GoodBmp=GoodSenior.bmp GoodSound=GoodSenior.wav DCI=TICKETS,ALLDAY,SENIOR

Siriusware Validation

20

Multiple entrances per Ticket • GateKeeper can respond to tickets sold for more than 1 person. • These tickets have always shown “Good for N” on the return text. • The gate can be wired to allow that number of people in. • We’ve had CountGoodFor=TRUE - which isn’t that good • We’ve had PulseGoodFor=TRUE - which is still needed for some gates such as the

Axess gate • We now have AdmitGoodFor=TRUE

– Requires two serial ports: • one for pulse to release the turnstile; one to read when the turnstile is turned

Siriusware Validation

[SerialAdmit] ComPort=13 BaudRate=9600 Parity=N DataBits=8 StopBits=1

[Preferences] AdmitGoodFor=TRUE AdmitGoodForDelay=500 AdmitGoodForText=Next Person Proceed - Entries Remaining:*ADM* AdmitGoodForResetTimeout=30000

21

Siriusware Validation

Three Parts: 1. Prefix 2. Expiration Date 3. Pass Number

22

Siriusware Validation

Prefix (optional) • Presence of a prefix indicates the presence of an expiration date and an

encrypted pass number • Note: Scanners and gates can be set to never decrypt with an .INI setting

• NoDecrytPrefixes=MPQ setting • Prefix indicates what table and field to use for validation • If No Prefix

• The blank prefix settings are used • There can be no embedded expiration date • The pass is never encrypted

23

Siriusware Validation

Expiration Date • An embedded expiration date is always checked first. • XX is a placeholder that is ALWAYS valid. • The first character is the day, the second is the month • Base38 is used to encode the day and month • Must follow a prefix • Evaluation requires a rollover month

Examples: 21 is January 2 2C is December 2 DC is December 13

24

Siriusware Validation

Pass Number • Can be an access or pass number depending on the meaning of the prefix. • If there is a prefix, the number is encrypted in Base38 • You don’t really need to perform any of these conversions. Examples: V is 31 4U986 is 10000010

4U986 = (6 x 380) + (8 x 381) + (9 x 382) + (30 x 383) + (4 x 384)

4U986 = 6 + 304 + 12996 + 1646160 + 8340544 4U986 = 10000010

25

Rollover Month • Used to determine ticket expiration when off-line • Only used when Base38 expiration date is encoded (i.e. NOT “XX”) • Only used if an off-season exists Examples:

Siriusware Validation

26

Scan Modification - Extract • Only happens if there is not a character prefix • First number is the # of characters that must be present (10) • Second Number is the place to begin extracting (1). • Third Number is the # of characters to take (2). • Example:

– INI Setting: Extraction=10,1,2 – Scan: 1234567890 – Since 10 characters in length, ’12’ would be extracted. – Can be more than 1 extraction – semi-colon delimited

• Extraction=10,1,2;11,2,4

Siriusware Validation

27

Scan Modification - Prepend • Only happens if there is not a character prefix. • Example:

– INI Setting: Prepend=PXX – Scan: 67005000 – ScanMan would make this into PXX67005000

• New: A list of prepend settings – PrependList= A,111; ,222; B875,333

• If you scan A999, it becomes A111999

• If you scan 999 it becomes 222999

• If you scan B875999 it becomes B875333999

• If you scan C888, it’s left alone.

• If you scan B876999, it’s left alone.

Siriusware Validation

28

Validation Options • Cascading validation – Validate on swipe_no

– Will search through all passes associated with the guest of the scanned pass

• Parent Pass Validation – Will always validate and deduct points/uses from the MasterPass

• Must be sold as modifiers to main (parent) item

• By Parent Guest (passes only)

• By Parent Pass Number

Siriusware Validation

29

Multiple Quantity Auto-Sale SysManager: Edit Item Action tab Action Specifics Auto Sales tab

Siriusware Validation

• With the Multiple Quantity Auto Sale selected, scanned admissions will automatically sell the specified items (DCI) and with the corresponding quantity

• Optional Do Not Prompt check box will assume maximum quantity of each item is entered. If this is left unchecked, the user will be prompted to select quantities for each item (up to the maximum).

30

Don’t Use Shifts

Siriusware Validation

Don't Use Shifts: Will prompt for the full quantity selection with each scan. If a client only wants to allow one entrance per day, then they can still rely upon the daily uses functionality.

31

Shifts = 1 Day

Siriusware Validation

Shifts = 1 Day: Will prompt for the full quantity selection only the first time the pass is scanned in the same day (essentially, subsequent scans of the same pass in the same day are viewed as ‘re-entry’ of the same people – so no additional prompting is necessary).

32

Shift = 1 Day with Write Transactions

Siriusware Validation

Shift = 1 Day with Write Transactions checked: Prompt for quantities will occur with each scan – even within the same day – but will count the previous quantities entered for the auto-sold items and once the total amount has been entered, the entry is denied.

33

ScanWatch

Siriusware Validation

Shows BAD scan activity recorded by SalesEZ. Will not show items rejected for embedded expiration date or hot-listed.

34

Ticket Types

Axess Validation

Number Description Barcode RF 1 Pool – Single or Multi Ride X X 2 Single or Multi Day Pass X X 3 Single or Multi Day Pass – Depot X X 4 Point Value Ticket X 8 Nonconsecutive Ticket (X Days of Y Days) X 9 Nonconsecutive Ticket (X Days of Y Days) – Depot X

10 Nonconsecutive Season Pass (X Days in Season) X 13 Single or Multi Hour Pass – Depot X 15 Season Pass X X 25 Pool – Single or Multi Ride per Day X

35

Ticket Elements • Pool – Group of gates • Seasons – Season Definition • Week – Weeks valid • Time – Times valid • Start Date / Expiry Date – Ticket valid dates • Period/Rides/Points – Number of uses • Reader Person Group – Sounds and lights to activate at the gate when

scanned

Axess Validation

36

Online Operation • Online (i.e. query leaves the gate) only if there are not valid segments on

the media Offline Operation • The “offline” mode is the primary method of validation for Axess • The media is master vs. DB is master for validation • The hotlist is checked for the segment being validated – updated based on

Siriusware and Axess settings • If there is no valid segment, the system checks if a WTP Reload product

exists • From scan to validation to opening of the gates is ~0.1 sec (longer for

invalid scans)

Axess Validation

37

Media • Up to three segments:

– Ticket product – Siriusware “swipe”

• IHC

• Discount Validation

• Etc.

– Room key • Barcode has limited functionality vs.

RFID • Media can be reused (thermal

rewritable and electronically reprogrammable)

Axess Validation Hardware • Flap Gates • Gantry • Gateway • Oracle Server • Handheld tablet • Printer • Reader Viewing guest photos • Handheld tablet • Used for fraud prevention • Can monitor one or all lanes –

go back in history • Used in conjunction with lights

and sounds at the gate

38

WTP Reloads • WTP = Web Ticket Product • Entering the WTP number in e-commerce or Sales will present the

customer with products available for reload on that media • Product purchase is sent to Axess and encoded at the gate

– Only encoded if there isn’t already a valid segment

Axess Validation

39

Siriusware/Axess integration • Media is printed/encoded from Sales integration with Axess Smart Printer • “Swipe” can be read with a custom Axess Smart Reader • Salespoint Sales

– The media is encoded/reloaded or WTP reload is performed and the supporting info (photo, text) is sent to Axess’ Oracle DB

• E-Commerce Sales – Initial purchases just create the product that is printed/encoded later

(same process as above) – Reloads information is sent to Axess for automatic media encoding at

the gate • Siriusware retrieves gate scans from the Axess Oracle DB and “trickles”

them through SalesEZ • Siriusware reporting is used

Axess Validation

40

Troubleshooting • Do NOT place a piece of media on top of the Smart Printer – can cause

multiple records with the same WTP in the Siriusware DB. • Products MUST be configured in both Siriusware and Axess system or

errors can occur when sending sales to the Axess system. • You can use Siriusware validation OR Axess validation – you cannot

combine the two – Why configure in Siriusware then?

• Reporting

• Exchanges

• Revenue Recognition

• Other non-access validation

• Always test the programs at the gates to ensure proper operation prior to encoding.

Axess Validation

41

Reporting • Scan Usage • Scan Detail • Hotlist Pass Report • Scan and Pass Access Report • Custom reports only for In Park counts (a couple clients use)

Siriusware Reporting

Thank You!

Axess Gates at Jay Peak

Axess Gates at Jay Peak

Axess Printer

GateKeeper at Ripley’s

Ripley’s Customized GateKeeer Screens

Ripley’s Customized GateKeeer Screens

Ripley’s Customized GateKeeer Screens

Ripley’s Customized GateKeeer Screens

Siriusware Validation Preferences Configuration in SysManager (Preferences Access Control)

Siriusware Validation Base 38 Values

Decimal Base 38 Decimal Base 38 Decimal Base 38 Decimal Base 38 0 0 A 10 K 20 U 30 1 1 B 11 L 21 V 31 2 2 C 12 M 22 W 32 3 3 D 13 N 23 X 33 4 4 E 14 O 24 Y 34 5 5 F 15 P 25 Z 35 6 6 G 16 Q 26 - 36 7 7 H 17 R 27 . 37 8 8 I 18 S 28 9 9 J 19 T 29

Rollover Example #1 • Rollover Month is August (8) • Encoded expiration is 16 (June 1) • It’s November 1 • Draw out Year starting at rollover month • Add in expiration date and today • Today (November 1) is to the left of (before) the expiration date (June 1),

so it’s good • In fact, any date to the left of the expiration is valid

Siriusware Validation

Rollover Example #2 • Rollover Month is February (2) • Encoded expiration is 24 (April 2) • It’s July 1 • Draw out Year starting at rollover month • Add in expiration date and today • Today is to the right of (after) the expiration date, so it’s expired

Siriusware Validation