Paulo Ramada

Most answers to this question describe orchestration as a connective layer you buy and lay over your systems. After 30+ years of enterprise workload automation — mostly Control-M, on mainframe and distributed — I would put it almost the opposite way, and I think the…

Control-M sits at the premium end of workload automation pricing — that is no secret, and I will not pretend otherwise. My position after decades of using it: the enterprise value justifies the premium, with one important condition The condition is adoption. The licence…

My main improvement point after decades with the product is not a feature — it is the path to mastery Basic administration of Control-M is fairly accessible: a new person can define and monitor jobs quite quickly. But truly understanding the platform — the kind of…

After 20+ years running Control-M on both mainframe and distributed, my advice comes down to four points First, understand what you are actually buying: the cross-platform dependency management. A mainframe job waiting on a file from a Unix system that depends on a Windows…

BMC Case Study: EDP Enterprise Orchestration — Solution I Designed & Implemented I designed, built, and continue to maintain this Control-M solution for EDP. Reengineered fragile shell-based invoice processing into a resilient Control-M architecture — achieving the 46%…