top of page

Case Study # 1: Credit Union Central of Manitoba

Time Savings

Company:

​

Credit Union Central of Manitoba

(CUCM) is the central body for 57

Credit Unions in the Province of Manitoba with 177 locations managing over 500,000 members and more than $10 billion in assets. Through CUCM, Manitoba credit unions share check clearing, data processing, investments and loans, training and education, marketing and research and government liaison. They also call upon Central’s consulting services in areas such as technology, business development and agricultural and business lending.

​

Challenge:

​

CUCM had a scheduling package in place that wasn’t handling the complexity of their processing requirements. They were unable to release jobs via job dependency, file dependency or both consistently and without error. This caused them to have operators manually monitor and release jobs on demand. This wasted many man-hours as well as introduced human error into CUCM’s processing cycle.

​

Solution:

​

CUCM selected Global ECS after searching for a solution that would fit their needs as well as their budget.

​

"With GECS, we were able to do more things than we anticipated from a single point of control. Not only does the job and file dependency logic work flawlessly, but we can also use GECS agents to release jobs on remote servers. You can customize your views which is handy as we are a 24 hour shop, so our views are broken down by shift," says Gerry Charriere of CUCM.

​

CUCM has grown the size and scope of their business process automation since selecting GECS in 2004.

​

Results:

​

CUCM has taken the burden of their job scheduling and batch processing needs off of their operators and technical group. They have come to depend and rely on GECS to handle the automation of their production environment. Many processes have been automated utilizing the GECS framework, allowing CUCM to easily set up and manage complex job streams.

​

"We have automated as much as we can with GECS which now frees up an operator as the scheduler processes jobs when required and there is no worry that operations will release a job twice," Charriere said. "When a job was released twice with our old solution, the technical group then would have to fix the errors by the jobs being processed twice. In short, it has cut down the operator time and less errors have occurred since its birth in our workplace."

​

Examples
bottom of page