The Windows Automated Installation Kit is indeed intended to provide an environment for image deployment.
I have just completed a project for a client where a single image (XP SP3) is supporting 20 different desktop and laptop machines, with three other images supporting tablet builds, 64 bit builds and a laptop build requiring a non standard HAL. Deployment is via a WinPE bootable USB device which autosenses the machine type using WMI, and then based on an HTA file allows the technician to do a full autobuild, or a partial autobuild (preserving the data partition). Image selection is automatic based on model type, except where specific models support both 32 bit and 64 bit operating systems - in that case the technician has to select which o/s is installed.
The WIM file created after sysprep for each build type is stored on the USB device and is automatically deployed once the hard disk has been prepared (also automatic). Once the image deployment completes, the USB solution asks the technician to reboot the machine, and sysprep runs minisetup, then some final build scripts, all with no interaction, joining the machine to the domain and leaving the machine at a login prompt ready for the user to login.
Since the WIM images are created using imagex from the WAIK, there appear to be no issues with compatibility across the range of Windows operating systems, and from my experience, the image sizes are substantially smaller than those producted by Ghost 8, as non essentials like the swap file are automatically excluded. We also produce ghost images of the builds for an external vendor who images new machines and doesn't use WIM files at the moment, and a wim image of 4.5Gb equates to a ghost file of around 5.5Gb for the same content.