Not many companies can say they manufacture fun, but that’s exactly what Polaris Industries, Inc., does. A leader in the motor-sports industry, Polaris designs, engineers, and manufactures ATVs, snowmobiles, RANGER utility vehicles, and Victory motorcycles. The common denominator for these vehicles is that they let people escape from their busy lives to a world of freedom and fun. Since 1954, when the first Polaris snowmobile made its appearance, Polaris riders have been finding "The Way Out."
Polaris is headquartered in Medina, Minnesota; with manufacturing facilities in Roseau, Minnesota; Spirit Lake, Iowa; Osceola, Wisconsin; and a distribution facility in Vermillion, South Dakota. Johnnie Talamantes, Sr. IBM i Systems Administrator, explains a little of their IT history. “In the early 1990s, Polaris brought in an IBM AS/400TM and installed MAPICS. At about the same time we started using Robot products from Fortra. Today, we’re on IBM i, running two systems with many partitions—including two production partitions that are replicated. One system houses our manufacturing enterprise resource planning (ERP) solution, and the other one houses our distribution facility.”
As far as interfacing with other computing environments, Johnnie notes, “We do some Oracle downloads for our Oracle data warehouse. In addition, our dealer extranet, our intranet, and e-commerce servers access some of our IBM i data in real time.”
Robot Schedule job scheduling and batch management software was the first Robot product Polaris implemented. When they started using Robot Schedule, they used it primarily as a placeholder for all of their jobs. Johnnie explains, “With MAPICS, you have an ERP manufacturing environment that involves lots of material resources planning (MRP) runs and forecasting, taking place weekly. It seemed to us that that kind of setup needed to be manual. Our operators would see the job, plug in a lot of values, and kick off the job manually.”
Johnnie admits they are a bit more savvy with their operations now. “We completely automated those jobs, both on the regular weekly schedule, and ad hoc in the middle of the week. We just select one job to run and, using group and reactive jobs, we run the entire MRP process, taking advantage of the event-driven scheduling available in Robot Schedule.”
By Johnnie’s calculation, Polaris has 350 to 400 jobs in Robot Schedule, including nightly, weekly, and end-of-the-month jobs. How automated does he feel their schedule is? Johnnie explains, “When I first came to work at Polaris, we had four operators at our manufacturing facility and two operators at our distribution facility. When we upgraded the system to a more robust infrastructure and got some operators more involved with the Robot tools, we eliminated four operators and moved them to a different part of the company. We now run those two systems with just two operators.”
For the last few years, Polaris has been running without a night operator. Johnnie explains, “We work a schedule from 5:30 a.m. to 5:00 p.m. but jobs run around the clock. Using Robot Schedule and Robot Replay, we run our jobs and let our programmers know if something is wrong, so they can sign on to the system and make corrections.”
From an IT management perspective, moving operators into different roles is a positive step. Johnnie explains, “As the company expanded—since 2000, we have added more than 400 employees—administering our desktop systems and the more sophisticated equipment on the floors in the manufacturing facility has absorbed several of our former IBM i operators. We have reduced our IBM i administration overhead and redeployed our operations support to the desktop and the shop floor without having to increase our head count.”
In addition, errors from manual entries are down now that Polaris has automated their schedule. As Johnnie points out, “Certainly, there is always some human error when people manually enter values, variables, and so forth. By using Robot Replay and Robot Schedule, we have been able to be more consistent and not have those errors.”
When asked what features of Robot Schedule they use the most, Johnnie thinks of group jobs, reactive jobs, and override codes. “As things juggle around on the weekends—a manufacturing line is going to be offline—using Robot Schedule’s Schedule Override Codes to omit and hold jobs is really useful. We use that a lot.”
As a publicly traded company, Polaris must deal with the compliance requirements of the Sarbanes-Oxley (SOX) Act, and Robot Schedule helps with that also. “I am the SOX administrator for IBM i and for a lot of the other IT functions,” Johnnie says. “We use Robot Schedule to run our daily SOX matching report. We run a program that looks for changed objects and produces a report every day at 7:00. We match that against what should have changed based on our programmers’s project completion forms. If they don’t match, we have to reconcile the differences.”
In general, Robot Schedule has made reporting easier, as Johnnie explains. “As the auditors come in, define what they want to see and what they want you to audit, I set up Robot Schedule jobs to handle their requirements. We run a wide range of reports daily or monthly, depending on what the auditors need to see. There’s no person running those reports—Robot Schedule handles them automatically.”
As a final note, Johnnie encourages everyone to visit the Polaris website to look at the new Polaris products. “We’re very proud of our Victory motorcycle. JD Powers recently released their ratings for motorcycle manufacturers and the Victory ranks in the top five in every category listed.” It’s the latest in a line of products that help Polaris provide an escape into a world of freedom and fun. A line of products that offer "The Way Out", courtesy of Polaris, Fortra, and Robot Schedule.
Take a Look at Robot Schedule
Find out how IBM i workload automation software can help you improve the efficiency of your job schedule. Request a free demo today.