Inside the Briefcase

The 5 Most Common Application Bottlenecks

The 5 Most Common Application Bottlenecks

Application bottlenecks can lead an otherwise functional computer or...

How Machine Learning Helps Improve the Security Industry

How Machine Learning Helps Improve the Security Industry

We’ve been moving more and more towards computerized processes...

Transformation on a Global Scale

Transformation on a Global Scale

Necessity may be the mother of invention, but it’s...

IT Briefcase Exclusive Interview: As Container Adoption Swells, So Do Security Concerns

IT Briefcase Exclusive Interview: As Container Adoption Swells, So Do Security Concerns

Fei Huang, NeuVector
In this Fresh Ink interview segment,...

6 Marketing Strategies for Your Small Business

6 Marketing Strategies for Your Small Business

One of the main problems facing small businesses is...

Standard Processes, Custom Decisions

March 10, 2011 No Comments

I gave a webinar on Smarter ERP with Decision Management and one of the tweets during the presentation – “Standard processes, custom decisions” prompted a few requests for more details. So, here goes.

When I talk to companies about their ERP implementations we often end up discussing the balance between standardization/globalization and flexibility/localization. These companies invested in an ERP system or other enterprise application in part (sometimes in large part) to get a standard system – standard data, standard processes, globally enforced. But when they come to implement it they find that local variations or product-specific exceptions undermine this attempt at standardization. They end up as one company said to me with a “worldwide standard process with hundreds of local exceptions”. This is far from idea as they know have to manage a much more complex process – the actual process has hundreds more elements than the original “simplified” process that was envisioned. This reduces agility, increases risk of errors and problems, reduces the ability of the various groups involved in the process to share and collaborate, and makes it harder to spot opportunities to improve the core process. Plus the process diagram is ugly.

Read More of James Taylor’s Blog

Featured Blogs

Leave a Reply

(required)

(required)


ADVERTISEMENT

UC Expo

SSOW

sptechcon

ITBriefcase Comparison Report