Manage Tomorrow's Surprises Today

Steven Minsky

Risk Management: What is the role of BPM and Content Management technology?

user-pic
Vote 0 Votes

In every emerging market the question of build versus buy arises. Enterprise Risk Management (ERM) is no different. Why a purpose-built application in this space? What is the role of enterprise content, workflow and process management technologies? What is the value proposition for a specific purpose-built application in the ERM software space? Should content and process technologies be built into a vendor application or should the vendor application leverage existing Enterprise Content Management (ECM) and Business Process Management (BPM) technologies in the enterprise?

The ERM platform core value is measured by the degree of delivery of best practices content like key risk indicator libraries and the business process practices as outlined in the Australian Risk Management Standard and COSO ERM framework. Enterprise content, workflow and process management technologies are infrastructure technologies that belong to the realm of corporate technology architecture and not a purpose built ERM platform. Best of class purpose built ERM software will leverage industry standards in these areas to ensure their solutions are as compatible and configurable as possible across the various infrastructure tools that mainstream vendors offer in these areas. The job of the corporate IT organization is to design and manage the architecture, IT processes, security and standards of their corporation. As such, the enterprise should select the infrastructure tools that are appropriate for their company’s needs, not the ERM application vendor.

Business and Risk Management should select the ERM application. ERM vendor solutions should leverage the corporate infrastructure and technology standards. For example, ERM platforms should be role based with hooks to be managed easily by Business Process Management technology in the enterprise. ERM software vendors should provide within their solution the option to reference data and documents within the corporation's document management/content management infrastructure. Only if the company’s technology is absent should the ERM vendor solution provide basic content repository or workflow capabilities as options.

Leave a comment

In this blog, risk expert Steven Minsky highlights the differences between traditional risk management and true enterprise risk management, which is about helping things happen rather than preventing them from happening. Manage Tomorrow's Surprises Today is designed to help you think about risk in new ways and learn how to benefit practically from this rapidly evolving field.

Steven Minsky

Steven Minsky is CEO of LogicManager Inc., a leading provider of ERM infrastructure solutions. He is the developer of the Risk and Insurance Management Society (RIMS) Risk Maturity Model for ERM, author of the RIMS "State of ERM 2008" Report and a RIMS Fellow (RF) instructor on ERM. He is a patent author of risk and process management technology and holds MBA and MA degrees from the University of Pennsylvania’s Wharton School of Business and The Joseph H. Lauder Institute of International Management. You can reach Steven at steven.minsky@logicmanager.com. View more

Subscribe

 Subscribe in a reader

web counter

Recently Commented On

Monthly Archives

Blogs

ADVERTISEMENT