The last point I want to hit with this blog is to briefly talk about migrations. Every client considering switching to OpCon has pain points that our software can address, but migration is something different; it’s a point of fear. How long will it take? How much will it cost? Will it break our operations? OpCon’s built-in simplicity and cross compatibility makes these fears considerably smaller dragons to slay. We can typically complete successful migrations in a fraction of the time, with corresponding reductions in costs, as our competitors IBM, BMC, or CA.
Here’s an example. Camaïeu is a women’s clothing retailer in France, and their previous automation tool, IBM Tivoli Workload Scheduler (TWS), was struggling to keep up with the volume of processes. TWS had minimal flexibility, provided no organization to their workflows and was difficult to integrate with other applications. Besides finding something to address the obvious problems, they also knew they wanted to integrate a Self Service portal to reduce the number of requests to the IT department.
When each job and workflow was moved into OpCon, Camaïeu’s IT team assigned tags to organize everything into the most logical business area. Meanwhile, they developed dozens of uses for their Self Service portal which eased the burden on the understaffed IT department.
With OpCon, Camaïeu is finally realizing the speed and agility that they were founded on in 1984. Today, their concept to completion time is only two weeks. They can now control their inventory and promotions and Camaieu’s IT Ops staff no longer feel overwhelmed. That’s the power of OpCon at work.