-Note that this information is being brought in from the Shop Management system from within the Hunter Application -Note that if desired, an application developer could bring in just the vehicles that were assigned the type of work the client system was capable of (i.e. alignments)

�Once the work order was selected, the AAIA Make/Model table was resolved against the Hunter Alignment Specifications database, and the appropriate specification fields automatically populated � no keying of information by the tech!

�Once the work order was selected, the AAIA Make/Model table was resolved against the Hunter Alignment Specifications database, and the appropriate specification fields automatically populated � no keying of information by the tech!

�Again, the Hunter system now passed the AAIA Make/Model Vehicle object to the Alldata information server, which then brought up only information relative to the vehicle being worked on. �Also, note that you are still in the Hunter application, viewing data from Alldata.� The technician did not have to exit or �Task Switch� to launch another application. �If desired, the system could have been set up to bring up Alldata information specific to the system being worked on.� For instance, we could have drilled into the Alldata system specifically for alignment information.� In this case, Hunter already supplies the Alignment specifications, etc. and felt that it would be best for their application to allow the user to search for the specific component repair information that might be encountered when servicing a vehicle on a lift.