5. The DPI 2of5 code badge also provided improved features. Other systems used Holerith coded badges which had to be inserted deep into the reader to read all numeric punches, had no error detection mechanism, and had little room for picture and logo. The DPI badge only required use of the lower half of the badge leaving plenty of room for pictures, any kind of clip, and had built in error checking. In addition the first badge readers were built so only half the badge was in the slot meaning the employee could keep a full grip on the badge as he clocked in and the clip never interfered with operation.

6. The tutorial instruction mask on the terminal for transaction lead-through cut training time and memory exercises for the users. A unique application was a plant in northern Ohio who employed quite a few people who could not read. By color coding the punched cards and inserting pieces of transparent plastic of matching colors over the mask bulbs, the terminal became user friendly (before the term "user friendly" was coined). In addition, of course, the masks were created by/for the customer to contain their preferred wording, language, or pictures.

7. The communications line rate of 300 characters per second was 5-10 times as fast as the competition. Today that does not seem very fast, but with the T/R protocol and the zero turn-around time of the terminals, we could exceed 600 T&A transactions per minute on a line. Some of the more modern protocols and turn-around times do fewer than that at 1200 characters per second.

8. The addition of a computer as the central controlling point of the terminals created many immediate improvements to the data collection arena. For example: A. The batch edit/correction runs on the punched cards or paper tape were eliminated as those edits were now made while the source of the information was still standing in front of the terminal to give corrections. B. Changes to the terminal transaction prompts, sequence, and input became easily implemented at a central location. Previously such changes were accomplished with a soldering iron at each and every terminal. Even later (early '69) when we ran a head-to-head pilot against an IBM system controlled by a 360-30, our effective and simple AIDE language allowed changes in five minutes compared to two hours for theirs. C. Terminal malfunctions could be detected, reported, and the FE dispatched, in many cases before someone even needed to use the terminal.

9. There was no attempt to work at the threshold of hardware technology. Reliable, proven components were configured to create STATE-OF-THE-ART SYSTEMS.

10. We knew the purpose of the system was Data Collection using a front end communications transaction processor. The hardware and software were specifically architected to this purpose. We were not attempting to compete in the data processing field. We emphasized that the main frame manufacturers did a great job at data processing and that function should continue to be done there. "Let each component of a system do the function it does best and the whole system will function best."