Lesson

Include significant planning and development time in the overall project schedule to accommodate identifying and addressing the various compatibility issues, to integrate existing legacy system equipment across multiple agencies.

Orlando, Florida's experience with a Field Operational Test (FOT) on using a single smart card for transportation payments at facilities operated by multiple regional agencies.


8/1/2004
Orlando,Florida,United States


Background (Show)

Lesson Learned

The ORANGES experience illustrated that it is necessary to include significant planning and development time in the overall project schedule when a regional system is being implemented. Given the multiplicity of agencies involved, this extra time is needed to accommodate identification of and accommodation for the various compatibility issues across existing legacy system equipment.

The ORANGES project experience provides the following guidance.
  • Plan on development time to identify and resolve system integration issues with existing legacy equipment, which include:
    • Integration with existing field equipment such as transit fareboxes, toll road equipment (e.g., plaza lane equipment, in-vehicle transponders) and parking equipment (e.g., garage entry/exit, parking meters, pay-by-space, pay-and-display);
    • Integration with agency point of sale locations, to support smart card issuance and revaluing;
    • Integration with existing revenue management systems at each agency;
    • Integration with the third party clearinghouse system that will settle prepaid funds to each agency based on the card payment and revaluing transactions completed at each agency; and
    • Development and strict adherence to Interface Control Documentation (ICD's), so development work among vendors is properly directed.
    Previous regional smart card systems in the US have been primarily limited to supporting multiple transit agencies in a region (e.g., San Francisco TransLink), or to supporting the combination of transit and transit-related parking (e.g., Washington (WMATA) SmarTrip®). The ORANGES FOT was successful in demonstrating that it is technically feasible to extend the underlying operational concept to encompass transit, tolls and parking. In addition, the toll usage successfully demonstrated the feasibility of infrared transponders that accept smart cards.
  • Do not to underestimate the complexity of integration and interoperability issues.
    The implementation team required considerably longer than originally planned to complete the system design and implementation. Most of the systems integration challenges centered around (1) determining the correct type of smart card and compatible readers, and (2) retrofitting the various types of existing field equipment (i.e., smart card readers in all the agency equipment needed to support the communications protocol used by the selected smart card). It is important to note that some equipment was provided "in-kind" by vendors in exchange for visibility in a high profile project. In addition to cost considerations, another reason for the use of “in-kind” vendor equipment was in some cases the need to use equipment from a foreign source when there was insufficient time to pursue a Buy America waiver. Quantities of equipment, customization and integration support providing by these vendors was typically limited. Agencies should document the system requirements and the vendor roles in addressing these requirements at the time of vendor selection. This will help identify any system requirements that will not be met by the vendors.
  • Ensure that the integrator develops detailed system testing checks for the proper handling of error conditions and other operational scenarios.
    Examining the clearinghouse transaction activity reports revealed an important error in how the overall system handled one case where a transaction amount exceeded the stored value balance (e.g., a $3 transaction when the balance was $1). Apparently, when attempting to store a negative value, a “roll under” condition with a large positive number (approaching $43 million) was recorded by the card as the balance rather than the negative. Business rules indicated that negative balances were not allowed, but the technology needed to ensure that enforcement of this rule did not cause undesired effects.

    The smart card or card reader needs to include software logic to prevent such a transaction from being completed. Barring that, the clearinghouse software should include logic to detect/report such occurrences to the agencies. None of this preventative or detection logic was in place in the FOT system. To detect this or a similar type of problem in future projects of this type, the system response to error conditions should be explicitly addressed through the testing and ongoing monitoring of the clearinghouse transaction activity reports. It should be recognized that developing a comprehensive testing program to capture every conceivable error condition could be a very expensive proposition for the project partners. It should also be noted that there is still a chance of missing an error condition as testing cannot reasonably expect to replicate every conceivable condition that will be experienced in the operational environment.
The ORANGES experience also provides this additional guidance.
  • Identify a smart card that will pose the least difficulties in integrating a compatible smart card reader with each partner's legacy equipment.
  • Secure technical support for integration, from the smart card reader vendor and the legacy equipment vendors.
Developing a regional smart card payment system is related to the ITS Goal of improving customer satisfaction, through making payments for multimodal travel easier by establishing acceptance of a regional payment method. Measures to achieve effective systems integration contribute to this goal by ensuring that the system functions in a planned and predictable manner for its users.

The overall project was completed behind schedule. The resolution of systems integration issues contributed significantly to these delays.

The participating cardholders generally expressed a positive opinion about the technology, with concerns focusing primarily on the limited scale of deployment. The fact that the system was successfully integrated to allow payment across three distinct legacy systems contributed to this result, since this allowed cardholders to use the same card for multimodal trips.

The examples and lesson elements above illustrate the need to include significant planning and development time in the overall project schedule, when a regional system is being implemented. This extra time is needed to identify and accommodate various compatibility issues when implementing the system across existing legacy system equipment. Additionally, this guidance focused on strategies to lessen the impact of compatibility issues, deal with error conditions, and to secure adequate technical support. While this experience suggests strategies for handling integration and compatibility issues of smart card technology, the same vast majority of the guidance could be applied to other ITS technologies and systems.


Lesson Comments

No comments posted to date

Comment on this Lesson

To comment on this lesson, fill in the information below and click on submit. An asterisk (*) indicates a required field. Your name and email address, if provided, will not be posted, but are to contact you, if needed to clarify your comments.



Source

Orlando Regional Alliance for Next Generation Electronic Payment Systems (ORANGES) Evaluation Final Report: Electronic Payment Systems Field Operational Test

Author: Moniz, Leisa M. (Volpe) et al.

Published By: U.S. DOT Federal Transit Administration

Source Date: 8/1/2004

EDL Number: 14268

URL: http://ntl.bts.gov/lib//jpodocs/repts_te/14268.htm

Other Lessons From this Source

Lesson Contacts

Lesson Contact(s):

Leisa Moniz
U.S. DOT/RITA/John A. Volpe National Transportation Systems Center
(617) 494-3793
moniz@volpe.dot.gov


Agency Contact(s):

Doug Jamison
Central Florida Regional Transportation Authority (LYNX)
(407) 254-6071
djamison@golynx. com

Lesson Analyst:

Jane Lappin
Volpe National Transportation Systems Center
617-494-3692
jane.lappin@volpe.dot.gov


Rating

Average User Rating

0 ( ratings)

Rate this Lesson

(click stars to rate)


Benefits From This Source

In Central Florida, focus group participants involved in a smart card study using a single card for multiple payment applications indicated that the card provided convenience and improved their transportation experience.

Lessons From This Source

Develop a detailed cardholder recruitment plan in the planning phase of the project, to provide guidance on processes to set pricing, and to ensure high user involvement and loyalty.

Establish a clear understanding among all partners on the level of technical support to be provided by suppliers and integrators, as equipment provided in-kind or at a reduced cost is often provided with minimal technical support.

Establish a forum for decision-makers and project managers to come together to receive project updates, work through critical project issues, make decisions, and support successful institutional collaboration in a project involving multiple agencies.

Include significant planning and development time in the overall project schedule to accommodate identifying and addressing the various compatibility issues, to integrate existing legacy system equipment across multiple agencies.

Provide for large sample sizes when conducting before/after data collection efforts, to avoid impacting the ability to reveal statistically significant differences during the evaluation's statistical analysis.

Seek assurances from your suppliers and sub-contractors, that their production and manufacturing schedules will meet your project schedule and inventory requirements throughout the lifecycle of the project.

Lesson ID: 2006-00188