Skip to Content
Some processes have been extremely well software enabled by SAP and SAP Partner solutions.  Some others seem to be harder to get a handle on. Process Optimization and Process Compliance are in that difficult category. Although their benefits are clearly known, it is very expensive t ouse traditional development means to build software solutions to manage them. Best practices exist in some niche industries but still, acquiring such solutions, implementing and maintaining them have been so far a major prohibition factor to a mass-market adoption.  Let’s look at the characteristics of those processes and see why composing them makes it a better value proposition? Optimization is about Algorithms. Compliance is about Controls. Both take input parameters, perform business logic, and return output parameters.  They share the same usage pattern: – Prevention using Report and Analytics – Correction using Mitigation Procedures or Processes  Today most solutions focus on the Prevention part extracting data from execution or BI systems and offering nice dashboards, reports or analytics to help planners or controllers understand the state of affairs.  The management of the Correction or Mitigation usually not integrated to the Prevention part and has not been software enable in its vast majority.  While a good job has been done so far coding the Prevention part, the question here is: how many reports or analytics can be coded to meet the many requirements unique to each organization in terms of KPIs or rules? The answer is too many to make it worth the development dollars. Composing your reports or analytics will give you quicker turnaround, faster time to market, lower TCO, reusability, and extensibility  On the Correction side, if for each broken business rule, you want to code the corresponding mitigation process, I’d say that’s suicidal. Maybe you want to code a few important ones but what you really want to do is to compose your processes.   Now that doesn’t mean you won’t have to code at all. Your Algorithms or Controls can be web service enabled or even Enterprise Service enabled. Whatever you code in the composition paradigm being services (Entity level, Application Service level, UI level, Process level), they are easier to produce, maintain, use and reuse.  Process continuity and integrity can be achieved if you can couple the Prevention and the Correction parts of your Optimization or Compliance processes. SAP Netweaver as the Composition Platform allows you to do it.  What you could not do before, you can do it now. What you could do in months, you’ll do it in weeks. What you could do weeks will take you days.
To report this post you need to login first.

1 Comment

You must be Logged on to comment or reply to a post.

  1. Adam Green
    Agreed.  However, you could look to other approaches to address remediation. The real power of composite apps comes from being able to create an extended environment which communicates more effectively with staff and management allowing them to act, then feed that action back into the process chain.  The x-app can be developed to encourage new and innovative methods of remediation.  By interfacing more effectively with the staff they become part of the remediation algorithm.
    (0) 

Leave a Reply