VEI Specification White Paper

Vending Equipment Interface (VEI) Specification
A White Paper By Agent Systems

A Standard for Data Communications for Fare Collection Systems

Almost all contracts for fare collection equipment now require some form of networked monitoring and control of ticket vending machines, fare gates, and other equipment delivered as part of the fare collection system. Many contracts also require electronic payment support for credit and debit card purchases. These requirements demand that fare collection devices connect to other devices and to one or more computer systems.

All current providers of fare collection technology use custom and proprietary methods of data communications to connect to the devices delivered to the customer as part of a fare collection system. These methods are often poorly documented, if documented at all. No two companies in this industry use the same methods of connection, and connection methods often differ for a single company from project to project. This incompatibility from company to company, and from project to project, makes support of fare collection systems expensive and difficult, and also creates significant problems when a transit property wishes to mix fare collection equipment from different suppliers.

The Vending Equipment Interface (VEI) Specification was created to provide a common interface for the exchange of data between fare collection equipment and computer systems. In fact, the interface defined in this standard can be used for the connection of vending equipment from any manufacturer, in any vending application.

The VEI specification allows these networked vending applications to be based on an open, non-proprietary standard. This standard protects the investment each customer makes in these systems. The VEI specification establishes a common interface that can be used by all manufacturers and users of networked vending systems.

The VEI specification was developed based on several existing standards. It is broad enough to encompass networked applications for all types of vending, and all types of technology used for data communications. Extensive testing has been conducted to ensure that all likely types of applications can be supported efficiently with the use of this standard. In addition, the VEI specification calls out the mechanisms for documenting specific implementations.

Copies of the Vending Equipment Interface (VEI) Specification are available free of charge upon request to:

Agent Systems, Inc.
2015 Midway Road, Suite 111
Dallas, Texas 75006-4918
(972) 774-0400
(972) 392-7301 FAX
VEI-related e-mail to Agent Systems

Or any of the other members of the VEI workgroup.

Questions and Answers on the
Vending Equipment Interface (VEI) Specification

1. Why should I be concerned about interface specifications?

Most modern distributed ticketing, parking control and vending systems are networked, and in the future this will be a requirement. A networked system is inherently more complicated than standalone equipment. To take full advantage of a networked system, it must work properly, efficiently, and be able to be expanded and adjusted.

To add equipment to a non-networked system, more equipment is simply purchased, plugged in and installed. To add equipment to a networked system, the additional requirement of communicating with a central network system is added. If the new equipment cannot communicate with the network, then a significant degree of functionality is lost. The choices can be to buy only from the original manufacturer of equipment, scrap all old equipment and start over, buy and install another networking system, or give up and operate new equipment on a standalone basis.

The Vending Equipment Interface (VEI) specification was assembled in order to propose a common "language" with which equipment from different vendors can communicate.

2. How do interface specifications affect my costs of doing business?

The goals of any enterprise should include reducing the costs of operation by minimizing capital expenditures and prolonging the useful lifetimes of capital equipment. With a standard interface specification, vending equipment and network interface equipment can be purchased independently of each other and mixed and matched with multiple vendors of equipment and systems.

Vendors using a standard specification do not have to expend the significant effort required to design their own interfaces and to implement multiple standards, which produces savings that can be passed along to the customer as lower prices.

3. Why can't an existing ISO, ANSI, or other standard be used?

No existing standard covers all areas of communications needed for complete management and control of remote vending devices. In addition, some standards are far too complex and would not be desirable for use as they would be too costly to implement and use in the field. Our first preference has always been to find a standard or combination of standards to use and reference. We have used several existing standards for portions of this standard. With widespread use and support, this standard can be presented to standards organizations for consideration as an international standard.

4. How does the specification protect my investment in vending equipment?

With the use of a single standard for all intercommunications between equipment and a network, you can be assured that equipment you buy five years from now can communicate with your existing systems. Old and new equipment can work together--you do not have to replace your entire system at once.

5. How does the specification protect my investment in network systems and equipment?

With the use of this standard specification you can use your existing network infrastructure and network applications with equipment from all manufacturers that support the standard. If you have an existing standards-compliant networking system, you can change to new equipment and not be required to buy new network hardware or software.

6. Why can't any vendor use any interface specification?

Technically, any vendor can use any interface specification that performs the needed functions. Legally, however, in some instances, one vendor can assert that they own all or part of the messages or interface specifications used in a networked system.

Through this claim of ownership, or just through failing to provide complete documentation on an interface, vendors can "lock in" customers for add-on equipment purchases. If a proprietary interface is required, the customer may be faced with an "all or nothing" decision: buy additional equipment from the original contractor, or throw away all existing equipment and go with a new company. Then the cycle may very well start over with the new vendor.

7. Can any computer system and any vending equipment use the interface standard?

Yes. This specification is independent of operating systems, local or wide area network technologies, and equipment types. The specification can be used with simple as well as very complex communications and networking scenarios.

8. What are some examples of equipment that this standard will support?

All networked, microcomputer-controlled equipment can be supported by this standard. Mass transit ticket vending and turnstile equipment, parking equipment, point-of-sale equipment, automated signage, signals, and all forms of monitoring systems are good candidates for using this standard.

9. What is the cost to use this specification--are there license fees involved?

No costs are associated with using this specification.

10. Aren't all interface specifications for any vending network the property of the customer who purchases such the system? Can't a customer allow other vendors to use this interface in the future?

Not necessarily. Unless specifically stated in a contract, interface specifications could be the property of the vendor. Vendors other than the original supplier of the system may not be able to use this interface. By having open specifications, the purchaser's rights to reuse the interface formats are protected.

11. What are the risks involved in letting a vendor use a proprietary interface specification?

Despite assurances to the contrary, even well-intentioned vendors can saddle their customers with network interfaces and messaging formats that are so arcane, poorly documented, and inflexible that future upgrades and additions of additional equipment are impossible. In the worst case, vendors can assert proprietary rights of data over crucial elements of interfaces and communications message data that could make purchases from other vendors impossible and drive up the cost of equipment that must be acquired in a noncompetitive scenario.

12. What if the standard interface specification does not include some needed function--can additional messages be added?

Nothing in the specification precludes the addition of functions or in any way reduces the flexibility of a user to design a system which best performs required duties. Users can develop data extensions to the standard to fit the needs of a particular product or customer.

13. Some vendors claim that they cannot support the standard interface specification and even claim that their interface is better or faster or cheaper. How do I get them to use a standard interface?

The long-term benefits of supporting a standard are much greater and much more important than a simple which-is-cheaper decision process. Of course, each vendor must invest the time and money to develop support for a standard, and some vendors may feel they are losing control over their customer by not being able to "lock in" future sales by using a non-standard, proprietary interface. Standards must be required by the customer in bidding documents, and referenced and/or included in equipment and systems specifications. By adopting standards, vendors reduce their risk and costs. Over time, this translates into lower costs for customers.

There are cases where special technical requirements may not permit the use of standards. However, usually vendors resist adopting standards only to reduce or eliminate competition. In the end, adopting standards better serves both vendors and customers.

14. My vendor has installed a system and claims that the interface is compliant with the standard. How can I check to make sure that the system really complies with the standard?

One requirement for full compliance with this specification is the development and maintenance of documentation of messages and data used in the interface implementation. This documentation must follow a standard form in a way that allows a third party to use the interface to add equipment or network components. Testing can be done to ensure that the as-built interface complies with the written documentation delivered to the customer at the completion of the project.

15. What about older equipment--can existing equipment be made to communicate using this interface standard?

Yes, typically older equipment and application software can be reconfigured to communicate with a networking system using this standard.

16. Will using this specification give any company an advantage?

No. A standard is a standard and is available to all vendors. All vendors develop to the same specifications, and their skills in producing equipment and application software are judged by price and performance.

17. How do standards benefit the industry (both vendors and customers)?

Benefits to the vending industry include the advantage of being able to concentrate on what they do best, which is designing and building vending equipment. This takes a great deal of risk out of projects and enables them to bid at a lower price and still maintain a fair level of profit.

Benefits to the user community include better equipment, better pricing, more predictable network performance, and the ability to mix and match equipment and network software vendors.

Return to White Papers
Return to Home Page