Agmt16 IPS - Laserfiche WebLink

Browse Search

represents a negotiated price with over 125,000 lines with Tmobile today. If connectivity with our standard offering was not possible, we will provide an upgrade to Verizon. ii. The Proposer shall describe the minimum, maximum, and average time in seconds the MSM will take to transmit transactions of different payment types (coin, credit card, NFC, other) to the CMS, including what parameters or conditions will affect transmission times and what percentage of each type of transaction can be expected to be transmitted within the average transmission time. Minimum: The minimum duration can be 1 or 2 seconds; Average: 97% of all data is arriving within 90-150 seconds. Maximum: Could be in hours if connectivity is not available. iii. The Proposer shall describe the sequence of events starting with a coin drop or card payment at the MSM and timing of each step in the transmission of transaction data to the CMS. A sample scenario follows: Customer arrives and pays the MSM with a credit card at time T. u. Credit card authorization is completed and Customer walks away at time X. MSM considers transaction completed at time T+X. Transaction data appears in the CMS at time T+X+Y. Coin: • Coins are inserted • Meter waits for configurable (currently set to 10 seconds) coin entry time out to consider transaction complete • Meter powers up modem to send transaction to DMS (currently set to wait 75 seconds in order to be able to transmit multiple coin transactions in one communication session to save power. IPS is planning to drop this value to 30 seconds.) • Once connected (typically less than 20 seconds), transmission is sent and data appears in DMS (typically within five seconds) Under these settings, after the last coin has been inserted — the transaction appears in DMS in approximately: (Today) 10+75+20+5 = 110 seconds (Future) 10+30+20+5= 65 seconds Credit/Debit Card: • Credit/Debit Card is inserted • Modem powers up and attempts connection, while user selects time to purchase and presses OK • Once connected (typically less than 10 seconds), transmission is sent and credit/debit card is validated and approval or decline is sent back to the meter • Once result arrives at the meter, the pole transaction detail is transmitted to the DMS (typically within 10 seconds) Under these settings, after the user has pressed OK— the transaction appears in DMS in approximately 10+10= 20 seconds iv. The Proposer shall describe the sequence of events when a MSM attempts to communicate with the CMS and fails, including how many attempts it makes and how often. The proposer shall state the recommended/optimal setting. When the meter attempts to communicate with the DMS and fails, it will retry in an exponential back off functionality. If the first attempt fails, the meter will reattempt in 5 minutes, and if that fails it will try in 10 minutes (double 5), if that fails it will try in 20 minutes (double 10), etc. until a maximum of 15 hours is reached. However, if any other payment or event happens at the meter, the meter will attempt to connect and transmit all pending data at that time. If the connection fails again after another event, it will try again exponentially up to 15 hours. REV: 0S-05-16 JS Page 70 of 177 ATTY/AGR.2016.094/IPS Group