Matt Slipher, systems engineer for conveyers and controls engineering, said his department's applications cover such production-crucial issues as the delivery of parts to the assembly line and ensuring that the right parts are picked for the vehicle under construction. A manufacturing system specifies the parts, and as they are picked from bins in inventory, receives a confirming signal that the light beam over each bin was broken by the parts pickers at the correct location. A technician scans the part bar codes on the assembly line to make sure the right part is going into the right vehicle.
"If you pick the wrong part, the assembly line pauses," a career-limiting move for the parts picker, since many managers are watching for any cause in assembly line delays, Slipher noted.
Another virtualized quality application is the defect-checking system. If defects are found in a vehicle assembly, they are recorded and assembly line workers are responsible for correcting them "before the vehicle leaves your pitch," or zone, on the assembly line, Slipher said.
While Nissan is averaging eight virtual machines per server in Smyrna, they are together consuming an average 28% of CPU, 70% of memory, 3% of network bandwidth, and 1% of storage bandwidth, Slipher said. That leaves headroom for variations in application workload and, perhaps, more virtual machines.
Slipher said Nissan's priority isn't increasing the virtual machine count per server but bringing a similar level of virtualization to its Canton, Miss., assembly plant, where Quest minivans, Armada SUVs, and Titan pickups are produced, as well as Altimas. The Smyrna and Canton plants together have a capacity of 950,000 vehicles a year, he said.
Slipher said Nissan manages its Hyper-V virtual machines through Operations Manager, one of the four components of Microsoft's Systems Center. It uses Microsoft's Virtual Machine Manager, another Systems Center component, to provision its virtual machines. Nissan looked at competitors and chose Hyper-V over other virtualization alternatives through a strong existing relationship with Microsoft and confidence in the rapid maturity of its hypervisor, along with the savings that result from choosing Hyper-V. Hyper-V is now built into Windows Server 2008.
"This has been a phased-in approach, not the throwing of a light switch," said Slipher. "It's proven out to be the right choice."
InformationWeek Analytics has published an independent analysis of the current state of open source adoption. Download the report here (registration required).
