Highlights of BPM Community Summit 2015 – Part 1

“Bringing Peace to the Universe”

On March 26, 2015, Princeton Blue hosted its first ever BPM Community Summit in New York City’s financial district, in response to overwhelming demand from last year’s participants. The BPM Summit provides a unique vendor agnostic format where customers pick the topics and lead the discussion. Our customers relish the opportunity to network with their peers, and hear each other’s stories first hand. The Summit engenders a sense of community and open dialog that our participants find invaluable.

Key Highlights of BPM Community Summit 2015

The proof: a consistent 9+/10 rating from the participants! Customer-selected topics included:

  • Using Enterprise Decision Management (EDM) to manage business rules across lines of business
  • How different tools/platforms can and should work together (EA, BPA, BPMS, ECM)
  • What is BPM Strategy?
  • Practicing Enterprise BPM

Today, we’ll highlight what our participants shared during the first discussion, “Using Enterprise Decision Management (EDM) to manage business rules across lines of business”.

While a company’s policies, procedures and roles are defined in policy manuals and internal websites, the rules for enforcing them are likely embedded in application code. Rules change frequently, as does the technology used to implement them. While the participants recognize the advantages of centralizing rules in a business rules management system (BRMS) tool, they agreed that getting there is difficult. Some of the reasons cited were

  • the effort required to externalize rules into a BRMS
  • change control and governance procedures
  • level of granularity required for rules
  • ensuring re-use of rules across LOBs

Highlights of BPM Community Summit 2015 | Princeton Blue

One often-discussed EDM goal is to capture rules in a BRMS and enable business owners to make changes to rules “on the fly”. In reality, achieving this goal means shortening the development time required to implement rule changes because of the ease of making changes in a BRMS compared to changing application code. However, rule changes must still go through testing and change control before being implemented in production systems.

Overall, this was a lively discussion, and a positive resolution within an organization has the potential to “bring peace to the universe”!

In part 2, we will highlight our participants’ thoughts on “How different tools/platforms can and should work together”. Join us next time, and learn why you shouldn’t “use a sledgehammer to put in a finishing nail”!

Leave a Comment

Your email address will not be published.

Scroll to Top