Table of Contents - APTAStandards.com
Table of Contents - APTAStandards.com
Table of Contents - APTAStandards.com
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
and 5-2. The lack <strong>of</strong> existing implementation<br />
was the only drawback for this<br />
specification, resulting in a less favorable rating<br />
in the “Widely Implemented” category.<br />
Overall, ITSO is highly applicable to the UTFS.<br />
Although VEI scored as favorably in the technical <strong>com</strong>pliance category, it did not<br />
receive any scoring on the UTFS Adoption Costs<br />
and Adoption Time. This is because<br />
there is no definitive fee structure,<br />
or change request schedule that could be identified<br />
by the Agent Systems point <strong>of</strong> contact.<br />
If APTA were interested in pursuing VEI,<br />
detailed<br />
discussions with Agent Systems<br />
to determine these elements would be<br />
necessary. This specification scored as somewhat favorable in the UTFS Effort Required<br />
category, for the following reasons:<br />
• The level <strong>of</strong> effort required further defining and<br />
mapping<br />
all t he matching VEI<br />
dialogues to<br />
WP4<br />
proposed<br />
exact<br />
message<br />
types<br />
• The<br />
estimated number<br />
<strong>of</strong> additional<br />
data<br />
elements<br />
that need to be defined for<br />
smart card related transaction processing<br />
Compared to Exhibit 5-1, the VEI scored better in terms <strong>of</strong> relevance per Exhibit 5-2.<br />
OFX did not score as favorably because it lacks relevance to the transit industry. This<br />
adversely affects its score in all the other categories as well, and therefore, is the least<br />
applicable to UTFS efforts. It is gaining rapid acceptance in other industries (e.g.<br />
Financial) and support from major vendors such as Micros<strong>of</strong>t. APTA should consider<br />
this specification as it matures and be<strong>com</strong>es more widely adopted.<br />
Although in<strong>com</strong>plete, the CID Edge Interfaces scored very favorably in terms <strong>of</strong><br />
Adoption Costs and Adoption Time. This specification is a viable candidate for a model<br />
for WP4 efforts, due to its reliance on Workpackage 1 smart card data formats, and the<br />
relatively low adoption cost to UTFS. Its low score on Technical Compliance reflected<br />
adversely on the Level <strong>of</strong> UTFS Effort Required<br />
in implementing this specification.<br />
CID<br />
Edge Interfaces<br />
also scored very favorable on two <strong>of</strong> the three categories in Exhibit 5-2.<br />
Despite its low scores on Technical Compliance<br />
and UTFS Effort Required, WP4 should<br />
consider<br />
using this draft specification.<br />
TransLink is the most favorable specification in terms <strong>of</strong> technical <strong>com</strong>pliance. It fulfills<br />
most <strong>of</strong> the criteria established in this category<br />
by<br />
providing a match for all the message<br />
types proposed by the WP4. Its <strong>com</strong>pliance with<br />
the technical criteria also reduces the<br />
time required for APTA to adopt this specification<br />
because <strong>of</strong> the relatively smaller<br />
number <strong>of</strong> changes that need to be undertaken.<br />
Due to its regional and smart card based<br />
focus, TransLink also scored the highest in Exhibit 5-2. If APTA will be allowed to<br />
adopt this specification, TransLink should certainly<br />
be considered for WP4 efforts.<br />
ERG APTA specifications scored very favorably in all categories<br />
<strong>of</strong> the criteria. Its<br />
support for relatively fewer number <strong>of</strong> WP4 proposed messages resulted in a<br />
“Favorable” ranking in both the Technical Complian ce and the Level <strong>of</strong> UTFS Effort<br />
Page 78