When talking about running OpsVeda on the cloud, a refrain I hear often from potential customers is about the complexity of their processes and how that becomes a hindrance in moving anything to the cloud (or specifically SaaS). For large complex organizations SaaS is the software equivalent of Henry Ford’s approach to Model T – “Any customer can have a car painted any color that he wants so long as it is black”. They go to great lengths to call out their non-standard processes – in many cases it does give them an edge but sometimes it is also plain cantankerous legacy. But that is besides the point for this post. Their real concern is how OpsVeda can accommodate these processes on the cloud when they are currently running the processes on highly customized on-premise ERP/CRM/SRM and in-house built systems.
Normally, I start by pointing out that systems they use for transaction capture are very different from OpsVeda which enables continuous process monitoring. For transaction recording the customizations generally center on capture of transaction/ customer/ product specific data points, additional validations, unusual workflow rules etc. and normally this is where the heavy customization that results in code changes comes in.
With OpsVeda the goal is to map the process and to interpret captured and unexpectedly missing data in light of historical patterns and pre-defined rules. For this purpose, thanks to its (Patent Pending) Process Agnostic Data Store (PADS) OpsVeda can accommodate pretty much any process without the IT guys having to rework any of the underlying code – and that means the system offers as much flexibility on the cloud as one is used to from on-premise deployments.
At the heart of PADS is a method of mapping any process as a set of activities in series or parallel. Each of these activities affect attributes (e.g. order quantity, shipping location etc.) of various business documents (objects in geek parlance!). Essentially, we have a flexible mechanism whereby a process with any number of steps and any level of complexity can be pushed into the same model (what/ when/ where/ how much) though the data could be getting generated by very different data models, be it Orders, Supply, Manufacturing, Inbound/outbound Logistics and so on. This also means that common procedures can be used for calculation of standard performance measures like cycle time – the system just needs to be told the start and end activities. Add an intuitive front-end for mapping processes and defining reports, alerts & visualizations, and there is a lot of power with the end user. As long as the data is flowing in from the backend systems, (s)he can define the processes to be monitored and the exception situations to be alerted against. And all of it through plain configuration – no programming!!!
No doubt – we have packaged a lot of pre-configured processes and alerts into the OpsVeda platform for common operational EXECUTION processes like Order to Cash, Purchase to Pay, Quality Management, Production Management etc. But if your processes are complex, that is just the starter. You can make a copy of these and start adding in all the quirks that are unique to your organization. Probably this is the opportunity – If complexity has been preventing you from harnessing the power of the cloud – rapid go live, low maintenance, scale. With OpsVeda, the Cloud need not be another pie in the sky.
Did I say, you can reject your decade old ERP Reports and Stale BI reports for Operational Execution? Yes, YOU Can. With OpsVeda, you can RUN YOUR OPERATIONS LIKE NEVER BEFORE.