| Vending
Equipment Interface Specification (VEI) Frequently Asked Questions (FAQs) |
|
| Vending
Equipment Interface Specification (VEI) Frequently Asked Questions (FAQs) |
|
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.
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.
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.
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.
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.
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.
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.
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.
No costs are associated with using this specification.
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.
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.
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.
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.
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.
Yes, typically older equipment and application software can be reconfigured to communicate with a networking system using this standard.
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.
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.
Send VEI-related e-mail to Agent Systems
Home Page Products
White Papers VEI Specification
Contact Information
