Showing posts with label ERP software. Show all posts
Showing posts with label ERP software. Show all posts

26 January 2012

Sage ERP X3 becomes Oracle Database Ready

Business software vendor, Sage Business SolutionsERP X3 solution has been granted Oracle Database Ready status through the Oracle Partner Network (OPN).

The announcement means that Sage has tested and supports ERP X3 on Oracle Database 11g Release 2, and at extension, Oracle Database Appliance. Results demonstrated smooth installation of ERP X3 application databases on Database Appliance.

The Oracle Database 11g Release 2 offers Sage industry leading performance, reliability, and scalability to power business critical applications.

Customer benefits of the solution are cost-effectiveness by lowering storage usage, reduced administration tasks, and enabling consolidation onto secure private database cloud environments.

Sage ERP X3 V6.3 is available on Oracle Database 11g Release 2.


As reported at ARNet.

09 April 2010

Are IT Vendors Driven by the Business Results of Their Customers?

Writing for CIO UK, David Henderson suggests several reasons “Why IT vendors must raise their game”. The second major point he mentions is that “IT vendors tend to be driven by their portfolios rather than business outcomes” for their customers. Henderson points out that IT vendors “continue to make significant investments in their portfolios but aren’t prepared to make the same investment in understanding how these apply to their customers’ businesses,” which can “lead to huge inefficiencies” once implemented at the customers’ sites.

As a result, Henderson continues, “vendors… tend to give poorly defined generic presentations that bear only passing relevance” to the challenges faced by the customer or prospect at hand. Henderson goes on to berate the ERP vendors for “me, too” solutions and their inability to “connect the dots” between their product offering real value for the firm that buys the technology.
I agree that IT vendors need to change. The economic picture is vastly different in 2010 than it was even three years ago.

Where I disagree with Henderson’s writing, however, is who should know what.

Starting off on the wrong foot

Computer-based technologies really were not available to any significant number of SMBs (small-to-mid-sized businesses) until after the introduction of the personal computer (PC) in 1981. Prior to that, computing power available from mainframe and mini-computers was available only to larger firms with significant capital for investment in such technologies.

So, in the early days of the computerization of the SMB market, almost every new prospect was anticipating moving off a system dominated entirely by paper and the necessary manpower to keep the paper flowing. As the price of PC-based technologies fell, more and more companies made the switch. This movement dramatically increased productivity and return on investment (ROI) for such a move was almost a certainty. As a result, many ERP salespeople came in the door talking about increasing productivity and providing rapid ROI for almost every SMB they approached. And, almost without exception, the implementation of that first round of technologies provided consistently rapid payback for the firms.

Unfortunately, as the market changed (i.e., SMBs’ next round of technology purchases were not taking them off paper-based systems but, more frequently, moving them into a comprehensive suite of application modules or moving some SMBs off the high cost of maintenance associated with mainframe and mini-computer systems), the sales approach of most technology vendors did not change. The technology vendors’ salespeople continued to make the same claims about productivity improvements associated with the first round of ERP implementations and the executives and managers at the customers’ sites continued to drink up the claims like Kool-Aid. In many cases, the SMB management was spurred on by the impending arrival of the year 2000 and the Y2K epidemic of fear. Many executives felt they needed to spend the money to upgrade their systems and took little thought as to the ROI of such an expenditure.

Nobody grew up and nothing changed

By the early 2000’s the ERP market had changed yet again. By 2005 or so, almost every CEO or CFO of every SMB had been through at least one – and usually two or three – implementations of new software (or other technologies) in their business environment. Add to that experience the fact that they now had easy access to the Internet by which to explore and make inquiry regarding almost any ERP software on the market, and the ERP-buyer had changed dramatically over a bit more than two decades.

When ERP was starting to be sold (20-plus years earlier), when the technology salesperson first met a prospect, the prospect was hungry for information about products and capabilities. Furthermore, these green-horn technology buyers were more than willing to make the salespeople their de facto “instructors” in the purchase and application of new technologies in their businesses.

In addition, as previously stated, ROI was pretty easy to achieve. Almost any SMB moving off labor-intensive paper-based processes or coming from costly mainframe or mini-computer technologies was bound to reap savings in operating expenses, and was almost equally likely to achieve increases in Throughput. However, by the middle of the first decade of the 21st century, all the easy ROI from traditional ERP – Everything Replacement Projects – was gone and not likely to return. Sadly, much of the technology salespersons’ product positioning remained unchanged and the sales rhetoric and promises from a good many ERP vendors still harkened back to days gone by – without, of course, actually mentioning that fact.

This unwillingness to face the change in the marketplace was not entirely one-sided. As the traditional ERP sales hype continued to make sweeping “rule-of-thumb” claims about delivering ROI for the ERP-buying executives and managers, these executives and managers proved themselves equally willing to accept the claims without taking the time and effort to discover for themselves what they really needed to know about their particular organization and its potential for reaping ROI from any particular foray into new or upgraded technologies.

What every executive and manager needs to know

As Eliyahu Goldratt has put it so well, there are three – and only three – things that every executive and manager needs to know to make effective decisions in every situation. These are they:
  1. What needs to change
  2. What the change should look like
  3. How to effect the change
If, before making the leap to buy technologies based on “rules of thumb” and sales-speak, executives would just take the time to figure out the answers to these three questions, there would be far fewer stories about traditional ERP implementations failing to deliver expected business results.

IT vendors are not necessarily driven by business results for every client. And, as executives and managers, you should be aware that rules-of-thumb may not apply to you and your enterprise – and the ERP vendor or VAR is not responsible for your business’s not fitting the rule-of-thumb by which other enterprises may have achieved return on investment.

As executives and managers in your organization with your particular circumstances and requirements, you – not the technology vendor or reseller – need to know what needs to change in order for your firm to start making more money tomorrow than you are making today. You – not your vendor or reseller – need to know what the change should look like in your particular organization. (The vendor or VAR may help you understand how new technologies may be part of what that change should look like, but you need to understand the precise need in order to effect your desired ROI. (Read more in many articles found right here at GeeWhiz To R.O.I.)

And lastly, as executives and managers it is your responsibility to understand how to effect the change within your enterprise. (Here again, the technology vendor or reseller may help you understand the technology-related components of the change, but you and your team need to take full responsibility for creating a roadmap for change.)

Need help?

Contact me at rcushing(at)GeeWhiz2ROI(dot)com and I can show you a way to unlock your firm’s “tribal knowledge” to discover what needs to change so you can start making more money tomorrow than you are making today, and you won’t spend money needlessly on technologies that don’t bring almost immediate ROI.

©2010 Richard D. Cushing

01 April 2010

Two Peas in a Prison

Have a good laugh at the expense of “Big ERP.”

Watch “Two Peas in a Prison” and then remember that the New ERP – Extended Readiness for Profit is what you really want.

Learn more about the New ERP – Extended Readiness for Profit by reading right here at GeeWhiz to R.O.I.
Thanks.

31 March 2010

Decision-making about ROI and your technology spending

Dan Gilmore wrote in “The ‘Probability’ of Supply Chain ROI” propounds properly and rationally the fact that any “forecast,” including forecasts of ROI (return on investment) should not be a single number. Rather, as anyone properly trained in statistical methods will tell you, it should be a range of numbers. The range of numbers would generally be calculated based on a single calculated value plus and minus values that represent the confidence intervals or, simply put, how likely the statistician believes his estimates the calculates will approximate reality. A larger range indicates lower levels of confidence and a smaller range higher confidence levels.

Now, while Gilmore is mathematically correct, the fact remains that most small-to-mid-sized businesses (SMBs) simply do not have anyone trained in statistics on their payroll and they are not likely to go out and hire a statistician to produce ROI forecasts for their IT projects – since this would, by definition, automatically reduce the ROI of the enterprise as a whole in the short term.

Back on a growth trajectory

Gilmore makes another comment in his article with which I wholeheartedly agree: “[T]here is some evidence that companies are in fact looking at investments that can help them to get back on a growth trajectory (read: increasing Throughput) without having to add much in the way of head count (read: Operating Expenses) by achieving productivity gains.” Given the world-wide economic malaise that is showing some signs of lessening (for the moment, at least), Gilmore’s description probably suits the vast majority of SMBs across the U.S. and beyond.

Furthermore, many others besides me have written that a firm stand on return on investment will be the hallmark of technology spending in the 2010 and beyond. So, I can hardly fault Gilmore for suggesting that SMB executives and managers need to become increasingly sensitive to and realistic about ROI for every kind of investment in their firms’ futures.

Too much complexity already

Despite my agreement with Gilmore on theoretical grounds regarding forecasts – including ROI forecasts; and despite my agreement with him regarding the goal of companies to get back on a growth trajectory through wise investment of capital resources, I must disagree with him on the matter of adding useless complexity to the return on investment forecasting process.

Allow me to explain why I use the harsh term “useless” to describe such an effort in the development of a ROI forecast for an IT project.

First  of all, let me say that statistical methods ought to be applied where they make sense. Statisticians generally agree that a valid statistical sample must contain at least 30 members. This works great where you have 30 dogs, 30 cows, 30 houses, 30 automobile, 30 miles of roadway, and so forth for comparison. Then, of course, you need to factor for environmental differences. Thirty or more cows all in the same pasture, eating the same foods, and enjoying the same climate would make a pretty good statistical sample for some studies of cows. On the other hand, three Holstein cows in northern Minnesota, two long-horns in west Texas, 15 black whiteface cows in eastern South Dakota, and ten mixed-breed cows in central Florida are not likely to constitute a good “sample” for cow studies.

Why?

Simply because there are too many environmental dissimilarities surrounding the cattle. By the time these factors were accounted for, (generally speaking) any results would have such a large confidence interval as to make any prediction almost meaningless.

When considered as a whole, a typical SMB has tens of thousand of variable at work within the enterprise. Any number of those variables are likely to dramatically separate it any “sister” enterprises in a sample group used to forecast ROI outcomes.

Of course, the fact that traditional ERP – Everything Replacement Projects – are going to affect the whole enterprise is a big part of the problem of predicting ROI outcomes. With tens of thousands of variables at play, picking the winning number is far more challenging than winning the lottery.

Reducing the scope reduces the complexity

First of all, a good many SMBs today have a “pretty good” ERP system in place – regardless of its brand. Unless there is some pressing reason to undertake a traditional ERP – Everything Replacement Project, it is probably a far better idea to consider a New ERP – Extended Readiness for Profit project instead.

Narrowing the scope of the project reduces the complexity. And, reducing the complexity increases the likelihood that your ROI forecast will be more on-target. Allow me to give you a couple of examples:

If your executive management team were to elect to pursue either of these projects – or both – the goals are specific and measurable – as would be the expected outcomes. ROI calculations become simple:

TOC ROI

Where T = Throughput (Revenues less Truly Variable Costs), OE = Operating Expenses, and I = Investment.

Simple. Elegant. And ROI calculations are far more likely to be right than any calculation around traditional ERP – Everything Replacement Projects.

©2010 Richard D. Cushing

03 March 2010

Maximize Your Investment with Packaged Software Implementations

Brett Beaubouef recently published a book entitled Maximize Your Investment: 10 Key Strategies for Effective Packaged Software Implementations. This book, published in December 2009, is a welcome addition to ERP literature if, for no other reason, than that there is a dearth of literature in the field regarding COTS (commercial off-the-shelf) or packaged ERP software implementations altogether. Beaubouef's work helps bring an end to that.

Beyond that, however, Beaubouef's writing is closely aligned with my thinking, as well. Plus, the vast majority of SMBs (small-to-mid-sized business) will end up implementing some form of COTS software. Most small businesses are simply not good candidates for "Big ERP," anyway.

Here are some salient quotations worth cogitating upon and that will, I trust, encourage you to go out and buy the book in order to gain more valuable insights:
  • Customers are more concerned with implementing successful business solutions, not just installing software products and technologies.
  • Flexibility in a business solution starts with a flexible implementation approach.
  • The ideal COTS software implementation approach would focus on maximizing the “out of the box” value that packaged software can provide to a customer. The implementation approach would naturally filter out requirements that did not provide quantifiable business value, and keep the focus on the customer’s value-added strategic requirements.
As the preface says: “This book is aimed at enterprise architects, development leads, project managers, business systems analysts, business systems owners, and anyone who wants to implement packaged software effectively.”  That’s a great target audience because so many implementations lack real business-value effectiveness, even when the software is otherwise “successfully” deployed.

If you fit into any of the categories listed in the preceding paragraph, my advice is to buy the book.  I did!
Contact me at rcushing@geewhiz2roi.com.


Works Cited
Beaubouef, Grady Brett. Maximize Your Investment: 10 Key Strategies for Effective Packaged Software Implementations. Birmingham, UK: Packt Publishing Ltd., 2009.