Mick Mountz
When a handful of MIT graduates get together to solve a problem, amazing things can happen – in this case, the most disruptive order fulfillment system to enter the industry in more than a decade.
Kiva Systems founder and CEO Mick Mountz (SB ‘87) and CTO and technical co-founder Pete Wurman (SB ‘87) were roommates as MechE undergraduates at MIT and fellow members of the Sigma Alpha Epsilon (SAE) fraternity. Together with technical co-founder Raff D’Andrea, they developed Kiva’s revolutionary real-time order fulfillment solution combining robotics and a highly adaptive algorithm-intensive enterprise software application. Soon thereafter, VP of hardware Matthew Verminski (SM ‘98), VP of product and program management Benge Ambrogi (SM ‘87) and engineering fellow Pete Mansfield (PhD ‘90) joined the start-up.
“Kiva Systems isn’t an MIT startup company – we created the business about 15 years after graduating – but it’s interesting just how involved the MechE and MIT community has been in its success,” says Mountz. “I used the MIT network to get everybody I could think of to help us build this product.”
The Kiva System – the first version of which was built in 2004 – is a suite of simple yet dynamic robots, complex back-end algorithms, and a touch-screen application that makes the whole system comprehensive and easy to navigate. From the time you submit an online order until five minutes later when the order is ready to ship, the Kiva System finds the ordered items and brings them to the pick station.
Before Kiva Systems, order fulfillment was often a long, manual process that could easily prevent a company from becoming profitable. That was exactly the case with Webvan, the company Mountz worked for prior to starting Kiva. Webvan was an Internet grocery delivery startup with a fulfillment rate of about 50 units per hour.
“We were losing money on every order,” explains Mountz. “It was my job to study how we were picking orders out of the warehouse and find a way to do it much faster. We got it up to 200 units per hour, but it still wasn’t good enough, and unfortunately the company went out of business.”
Mountz made it his mission to find a more efficient and productive process for fulfillment.
“We set out to build a system that could do 600 units per hour,” he continues. “The problem was clear: We needed to get ‘red,’ ‘green,’ and ‘blue’ in the box. We started brainstorming from a blank sheet and asking ourselves very basic, almost silly questions. ‘Why aren’t the units already in the box? Why didn’t the vendor just ship them that way? Why don’t the products just get in the box themselves?’ We didn’t constrain ourselves to traditional approaches or ways of thinking.
“At one point we asked ourselves, ‘What if the products walked by themselves?’ It was a funny thought, but what if?”
In the end, Kiva’s solution, which can produce 600 units per hour, does indeed enable products to “walk” to the boxes themselves.
Here’s how it works. A warehouse employee logs into the pick station through a touch screen. The customer order arrives in real time, and robots immediately begin moving toward a storage pod that contains the item. A navigation system on the warehouse floor consists of a series of stickers, which the robots take photos of along the way to keep them on a consistent path. Once the robot arrives at the pick station with a pod that contains the ordered item, a laser points to the individual cubby holding the item. The pick-worker takes it out, scans it, and places it into a tote for shipping. After the robot has delivered its cargo, it takes the pod to a new dynamic location in the warehouse where it awaits its next mission.
“Almost all our customers buy our system on a 2-year or better return,” says Mountz. “That means that the workforce in a Kiva building is doing two to four as many orders per hour compared to their old way.”
All that and yet the Kiva System is incredibly simple, at least from the outside. The robot consists of thermoformed shells with sensors, injection-molded parts, cabling and harnessing, castings, motors, actuators, and gear boxes. The electronics bring it all together with embedded firmware and control systems. On the back end, software is engineered to distribute missions to the robots about what to fetch, from where, where to bring it, and how to get it there most efficiently.
Verminski says, “We try to keep the robots very simple. They move forward, pick things up, travel, and traverse, but they have to do it on a very consistent, reliable basis. From a mechanical perspective, it’s a playground, because there are a vast array of technologies going into it that have to come together seamlessly to form an electromechanical system.”
“I love its simplicity,” adds Mountz. “Companies come to us with hundreds of mechanical contraptions they have in their current buildings. In these types of warehouses, you have to keep spare parts in the back room for all the different contraptions. If something goes down, the whole building stops working. With our solution, if you put 100 robots out there and any one of them dies, the other 99 keep running. It’s this idea that we simplified it down to a robot and some software, and with that we can design and build almost any warehouse solution.”
