Archive for January, 2010
Everyone Takes the Hit: What You Can Do About It – 5 Key Business Metrics and Oracle E-Business Suite
Posted by Helene Abrams in The Changing Enterprise, Trends & Technology on January 19th, 2010
Before the onset of the recession and the meltdown in the financial sector, for businesses addressing change meant adapting to more cash coming in and what to do with it to keep investors happy or adapting to unprecedented growth – one of those “good problems to have”. Organizations were looking at 3, 5, and 7 year strategic plans with upwards of 20% growth year over year. A company doing $100 million in revenue might have had plans to double in size in four or five years.
As businesses were growing, building their customer base, and hiring, they may also have been planning to implement lean manufacturing or otherwise improve a host of business processes, from financial and R&D to product management, sales, and marketing. Along with the business processes improvements, IT managers were retooling their IT systems, upgrading their infrastructures, improving performance and security, or adding functionality for a host of business users.
But as the recession took hold the optimistic forward-looking projections changed. Revenues dropped precipitously and survival tactics were implemented across the board. Companies cut their work forces. Cost centers like Finance, HR, and IT gave up headcount. Even R&D headcount, usually the last to go, was reduced. New products in the pipeline were pared to the bare minimum. Manufacturing shut down to reduce WIP and labor costs. Purchasers cut orders to reduce inventory. Marketers cut back on tradeshows and direct campaigns, redirecting scarce funds to less costly online programs. Sales organizations were consolidated, products heavily discounted, and travel budgets reduced. Across the board employees were furloughed and salaries were cut. Performance-based bonuses were first severely cut and later completely eliminated.
At the same time that companies hunkered down in survival mode, the business environment continued to change. Markets changed, customers changed, and financial or other regulatory requirements changed. Technology changed as well. In the middle of the recession Oracle released upgrades to R12 which included new “global” functionality, important bug fixes, and improvements. Other technology vendors in the ERP ecosystem released new products. Despite the changes and even with significant loss of headcount, IT managers somehow continued to deliver and support IT to their internal or external customers.
Below we examine how the economy impacted five key business metrics: Productivity, Inventory, Days Sales Outstanding (DSO), Customer Satisfaction, and Retention, how organizations responded as the recession unfolded, and the effects they had – or should have had – on ERP systems. Read more…
Show Me the Money: Reduce the Costs of Running Oracle EBS Before Upgrading to R12
Posted by Helene Abrams in Data Systems, Return on Investment Analysis, The Changing Enterprise on January 19th, 2010
Reducing costs is the major strategic focus for most companies. An often overlooked cost is the general operation of financial operations. This paper details a methodology for calculating the costs of running each of the financial modules. The costs are compared against both internal and external benchmarks. After calculating the costs, the paper shows how to reduce costs in two ways: first, by eliminating work that is duplicated across different business units or divisions, and second by determining which operations that are currently distributed across the organization can be consolidated into a shared services center. Together these changes, both to the organization and the Oracle EBS system, can generate significant cost savings. Finally, the paper details how streamlining operations prepares for a better R12 implementation.
Calculating the Cost of Operations
The cost of operations is calculated by breaking down how much time is spent on an activity during the year by each person doing that activity, how many items were processed, and then calculating the cost using a baseline cost of FTE. As an example, for AP, each department would calculate the number of hours in a year spent on each of the following tasks or activities:
- Maintain policies and procedures
- Enter, code, match, and correct payment documents
- Prepare and issue automated checks
- Certify checks
- Process manual checks and special payment requests
- Respond to vendor and internal inquiries
- Perform Reconciliations
- Perform corporate and government reporting
- Create Corporate Chargebacks
- Other A/P Activities
The hours would be translated to a number of Full-Time Equivalents (FTEs) by dividing the hours by 2080 (the number of hours for a person working full time per year). A baseline average burdened (including benefits and expenses) salary is then multiplied by the number of FTEs to calculate the annual cost of that activity. To obtain the cost of an operation, multiply the number of items processed (i.e. number of checks) by the cost of the activity. For each of the finance areas, costs are calculated to measure the performance of each activity. For example, General Accounting would calculate the number of journal entries processed per FTE per year and compare those to an internal benchmark. Travel and Entertainment would calculate the number of expense reports processed per FTE per year. Fixed Assets would calculate the number of unique fixed assets or line items per FTE per year. Accounts Receivable would calculate the number of bills issued per FTE per year. In other words, each area would develop its own internal key performance metric and a way to calculate that metric against FTEs contributing to the process. In aggregate these calculations may uncover significant additional cost savings that could be realized quickly and relatively painlessly by migrating from a distributed services model to a shared services model.