Agility by Design - eprentise Blog

eprentise is pleased to bring articles of interest to you and the Oracle community. Our mission is to provide software products that reliably align your E-Business Suite to ongoing business changes.

11 Reasons Oracle E-Business Suite Projects Fail (And How to Fix Them)

PDFPrintE-mail

As a mission critical system, considerable time and attention should be devoted to maintaining, improving, and optimizing your Oracle E-Business Suite (EBS) system. While most tasks are relatively routine in nature, sometimes—either due to organizational changes, the need to upgrade, or due to changes in management and regulatory reporting requirements—a change is needed in your EBS system that requires the initiation of a more complex project.

Even with the best of intentions, planning, and hard work, complex EBS projects can fail for a variety of reasons. Whether you’re planning for an R12 upgrade or reimplementation, completing a post-M&A consolidation, implementing OBIEE or Hyperion, or simplifying your EBS footprint (or more), reviewing and recognizing common Oracle project management failures and their respective best solutions can ensure that your projects succeed in 2012 and beyond.

Here are eleven specific and common reasons why Oracle projects fail, including advice on how to prevent them in advance.

1. Poor Documentation

Many well-intentioned teams start their project planning and implementation process with good documentation practices but get distracted or lazy into the project. Proper documentation is important for several reasons:

  • Tracking decisions made and reasons for making them
  • Tracking changes to the scope of work and how it effects future work steps and final product
  • Educating users on successful post-launch usage
  • Helping future teams understand your work, reasoning, and specific implementation steps
  • Identifying opportunities for greater efficiency further into the project, or the next go-around

Create a standard for documentation at the beginning of your project, and hold team members accountable for completing documentation requirements as well as keeping them at and above the standards required. Consider using a Run Book as well to document what steps are done and how long they’re taking as a look-back for current and future users.

Runbook Example

2. Lack of Training

Many times the problems encountered or potential user-borne issues result from inadequate training in a particular EBS feature or function. For example, many users started using project accounting in R10, aren’t familiar with the new features and reports, and don’t feel that they are able to track their projects accurately without a project segment in their chart of accounts. A week of training will not only help users with new features but will improve overall business efficiencies.

Oftentimes, this includes multi-media presentations, live demos, and hands-on practice to get users familiar and comfortable with the day-to-day and periodic tasks they will be required to execute moving forward.

Before promulgating user documentation or training, it’s also a good idea to choose a representative from the among the business users base to review materials first. Ideally this should be someone who uses EBS on a daily basis. They can help you see the materials from an end-user point of view and can help make adjustments to ensure that the training, documentation, and instructions are user-friendly and will lead to a successful training.

3. Unrealistic Budgets or Timeline

Just because your organization requires a major Oracle EBS improvement project—even if that project has already been funded—doesn’t mean that all required budgets have been adequately identified and secured. Too often, budgets are unrealistic and too low for the work required. Before starting any significant project, ensure all resources (dollars, people, etc.) are identified and available during the expected project duration.

If your project is underfunded, it’s at risk for not being completed. Go over budget and the extra expenditures could deem the project a failure (no matter what the other outcomes). Underfunded budgets can also force you to cut corners (like shortening or eliminating test phases) that could increase the risk of errors and unintended outcomes.

After building your first draft of the project budget, go through and ensure you’re not being too idealistic about timing, resources required, and whether or not you need outside help to complete the project. Be especially thorough in reviewing the need for outsourced resources to help with implementation or other specific steps/components of the project, and include in your budget who is responsible for monitoring and tracking those resources as well. If you are not sure about the resources and budget required, obtain several estimates from people that have experience with the same size and scope of your project. It would be unrealistic to expect that your team knows what a reimplementation project would look like, or how much it would cost, if they’ve never done a reimplementation.

Many project managers are successful in estimating hard dollar costs of their projects, but they fail to adequately identify and secure the “soft” costs, made up primarily of allocations of existing, internal resources, of the project . Without budgeting for all hard and soft costs, your project may become significantly delayed or come to a grinding halt altogether. Underestimating the budget is generally not intentional, though consulting companies will sometimes “lo-ball” the estimate, assuming once they are into the project they will be able to do change requests and increase the costs.

4. The Right Resources Aren’t Assigned or Available

It’s difficult to participate in a project and also do your regular job. It sometimes seems that a few people in the organization are asked to do everything. Be realistic when assigning people to different project responsibilities and allocating their time, and recognize when external skills would be more efficient even though the cost might be higher. For example, hiring resources for the upgrade to R12 may seem more expensive than having your DBA try to do it internally, but consultants who perform upgrades day-after-day develop a variety of “lessons-learned” and ways to streamline the process. Additionally, it does not make sense to have your internal DBA spend months on learning to do something that he or she will never need to do again. The time could be better spent on other projects.

Be explicit, before beginning the project, what internal resources are required for execution. This includes people, infrastructure, hardware, and software. Even if new allocations and additions aren’t needed (that would require hard dollars), it’s important not to assume that existing resources can quickly or easily be allocated to your project.

Think through the different roles required to execute as well as the required in-project time and duration of the project. Then secure commitments from these resources and their owners/managers before implementation.

5. No Project Champion

Few complex, large-scale Oracle projects are ever successfully completed without someone in the C-suite or other high-level position endorsing and prioritizing the project and its outcomes for the business. Your executive sponsor is critical in ensuring that other lines of business and cross-departmental resources are made available and prioritized to successfully plan, manage, and complete your project.

This is particularly important for IT projects, where dependencies across business units can make or break both the success of the project as well as how quickly and efficiently it can be managed and implemented. IT can initiate many different projects, but without the support of the business they won’t be successful. A project champion can help prioritize projects based on the business needs and then promote the successes within the organization, both in terms of measurable results and in obtaining buy-in from different parts of the organization.

Help the project champion understand the impact your project will have on the organization and how its successful completion will make him or her an internal hero or heroine for supporting it.

It’s also important to ensure that the project champion and executive sponsor understand the scope and resources required to achieve the desired business outcome. This understanding will ensure that resources are available both at the beginning and throughout the course of the project. Otherwise, it’s far too easy for other priorities to creep in and steal critical implementation resources.

6. Scope is Inappropriate

Many ambitious project managers try to bite off more than they can chew. For example, it’s often much easier to test and verify a single ERP vs. multiple areas at once. It’s probably not the best idea to change operating systems, upgrade to R12, and change your chart of accounts all at the same time. You are shooting at a moving target that introduces a lot of instability with each of the processes. Isolate changes so that they can be tested individually and the users can understand the impact of one change before the next one is implemented.

Break up your project into smaller projects (try for projects that can be completed in 4-6 months, especially early on) to get success and demonstrate momentum. Those early wins can often gain additional credibility and resources to tackle bigger chunks of the entire project. Long projects lose momentum, delays occur because of changing priorities, the requirements change, budgets get cut, and resources are reassigned to the next project or leave the organization, so costs increase.

7. Poor or Inappropriate Metrics

If you know the outcome you’re seeking, you should also be able to define it. And if you can’t define success based on a single or small set of key metrics, it will be difficult not only to “sell” the projects internally to those who will approve budget and resources, but also to communicate success and completion at the end of the project.

Appropriate metrics include benchmarks and baselines for where you’re starting, in addition to success metrics at the end and key milestones along the way. Use all three of these metrics (baselines, milestones, and completion metrics) to make your case up-front and rally budget, resource, and executive support.

Specific metrics to focus on include return on investment (ROI), cost savings, and resource reductions. Include reduction in the number of staff or time required for a particular operation (like reducing closing time from 8 days to 3 days, or days sales outstanding from 20 days to 9 days) and reduction the number and complexity of spreadsheets required. Tie the project to metrics identifying cost savings.

As you communicate metrics at various stages of the project, leverage a communication plan created up-front that details who needs to know what, the levels, channels, and frequency of project update communication, etc.

8. Lack of Adequate Testing

Problems will always pop up if you haven’t adequately tested not only the completion of your project, but also the use cases of those who will be interacting with the software on a daily and periodic basis moving forward. Be sure to build a test plan that includes both the day-to-day activities and the periodic activities – financial reporting, currency revaluation, patch application, and so forth – so that ongoing product support and success isn’t compromised.

We have one customer that successfully executed a chart of accounts change by completing the mapping autonomously, resolving all exceptions, and going into production with zero errors. However, the team managing the project didn’t engage the users at all—they had done no testing until after the new chart of accounts was in their production system Monday morning following the go-live. It was not a happy situation, and the well-intentioned IT person who did the work actually had to roll back from the production environment, give the users time to test, and then go live again a few weeks later.

Make sure that your testing includes reports, upstream and downstream interfaces, customizations, enhancements, and workflows. Be sure to budget for testing resources in your up-front planning and resource allocations as well.

9. Change of Personnel

Especially for long-term and complex projects, it’s inevitable that the people involved will change. Key people get hired away, change organizations, quit, retire, or otherwise leave the project. Without adequate planning, documentation, and role definitions, these personnel changes can not only grind execution to a halt but also make it incredibly difficult to pick back up the project and/or key components without adversely affecting execution and budget.

Ensure not only complete documentation of each contributor’s role but also ongoing status reports of what’s been done, what’s left to do, what issues new personnel need to be aware of, etc. If possible, ensure that comprehensive transition reports and meetings between departing and incoming personnel are completed as well.

10. Trying to Implement Overly Complex Solutions

It is tempting in many Oracle EBS implementations to over-engineer custom solutions, especially when unique business needs and requirements are involved. However, the more custom you make your implementation, the more you get away from the core functionality of E-Business Suite, and the more difficult future implementation and execution will be.

For example, many companies (as they grow or go through M&A activity) end up with multiple instances that are either separately managed or tied together through complex, custom bridge systems and reporting tools. Instead of spending time and resources implementing third-party reporting, consider consolidating multiple instances, moving to a global chart of accounts (CoA), and/or standardizing on a consistent calendar.

Don’t assume that what couldn’t be done two, three, or five years ago can’t be done now. Start with your business requirements and research specific solutions on the current market that can more elegantly address your needs while staying as close to the native functionality of Oracle and E-Business Suite as possible.

11. Not Understanding the Business Drivers For Change

Too often, IT projects become a standard part of doing business (especially in large organizations) without being rooted in business drivers and objectives. Take the time up front to plan the project and to ensure consistent understanding and consent on the business drivers requiring change.

Is the project focused on helping the database-driven organization keep up with the pace and growth of business operations? Remember that a successful project will change the way the business operates. Those changes often necessitate new processes for complying with regulatory requirements, additional procedures for governance of shared data, and mitigation of new risk factors. Include governance, risk, and compliance management as part of the project plan.

Engage the business users directly, at the beginning of and throughout the project, to avoid isolating IT projects from the business users and their objectives. Leverage your product champion and ensure the right people are all engaged and on board up front. The IT department of one of our large customers had planned to consolidate their instances for several years; however, it wasn’t until the business made a case that the project got funded.

Just as important, keep those business drivers top of mind for the entire execution team over the course of the project to ensure that changes and triage don’t happen in a vacuum. Constant reminders of business drivers help to prevent consideration of overly-cumbersome changes when a more elegant implementation (simpler reporting, single instances) can serve the same purpose.

Finally, celebrate the successes. Too many projects focus on defects, failures, or small cost over-runs without looking at the big picture and what was accomplished.

 

Six Post-merger Integration Steps that Add Value to M&A

PDFPrintE-mail

In Part I of this two-part series we looked at why nearly 90% of mergers go awry and what must be done to ensure that M&A deals achieve maximum value. As discussed previously, regardless of merger type (coexistence, absorption, or synthesis), priority should be given to customer-facing processes vital for supporting the company's customer service, vendor/distributor relationships, sales, customer support, and order management. 

Focusing only on consolidation of core processes significantly reduces the time, effort, and costs associated with the merger, leverages the synergies of both companies, and increases the likelihood of success. Below, we've outlined a sequence of post-merger integration steps that focus on core processes and can add value to a merger or acquisition:

Read more: Six Post-merger Integration Steps that Add Value to M&A

   

Mergers & Acquisitions: Realizing the Value

PDFPrintE-mail

There are few things that generate excitement and speculation like the announcement of a business combination. Almost without exception, the management promise of every merger and acquisition is to increase stakeholder value. However, it seems that this is not what typically happens. As evidenced by a 2008 study by KPMG, 42% of deals do not increase shareholder value. Worse, the same study indicated that 45% of deals actually destroy shareholder value. So with almost 90% of M&A deals failing to deliver on management’s promise of increased shareholder value, it begs the question— what is going so terribly awry? More importantly, what must be done to ensure that M&A deals do in fact deliver the maximum value possible? This article is meant to answer both of these questions.

Sources of Value and Causes of the Destruction of Value—The Value Gap

Shareholder value is measured as the increase in stock value associable with the merger. Because, rationalized, stock value is reflective of long-term earning capacity of the company, a proxy for increased shareholder value is the net present value of increased cash flow due to merger synergies.

The hope is that shareholder value will be increased by cost reductions achieved through economies of scale, the combination of duplicate corporate functions, and streamlined sales forces; capital efficiencies achieved through rationalized assets and the combination of duplicate facilities; and revenue enhancement affected though product development synergy (new products), shared marketing skills, and combined distributions.

The expected increase in value, while often achieved to some degree, is largely offset by situations that occur during integration. This produces what is called a Value Gap. Some major things that contribute to the Value Gap include:

  • Integration issues
  • Inexperience
  • Lack/loss of vision
  • Management wars
  • Culture clashes
  • Failure to manage risk and change
  • Bad communication with stakeholders
  • Prices rise, quality falls, customers leave
  • Alliances and supplier relationships degrade
  • Key people leave, and business continuity is lost

The result is the Value Gap — the unhappy coincidence of achieved value offset by unanticipated challenges, resulting in less shareholder value from the merger.

In addition to the Value Gap, there can be synergies after the deal is made that can add energy, creativity, and enthusiasm for new opportunities. This is referred to as Emergent Value, and it can help offset the Value Gap. Stemming from unanticipated synergies, Emergent Value is created by taking advantage of complimentary resources at all levels, finding more profitable uses for assets, achieving both strategic and operational fit, discovering new market opportunities, and selling products to existing customers. In addition, reinventing processes, shedding obsolete practices, and capitalizing on the creativity and excitement evoked as new colleagues interact, can play a role in generating Emergent Value.

Transition—the Critical Period

Most executives would be quick to point to a lack of synergies, an unrealistic vision, or an outrageous premium price for the reasons a business combination fails to deliver value. While these factors can certainly sabotage the success of the combined entity, even the best structured business combination can be sabotaged by another pitfall—poor post-merger integration (PMI). It is PMI that can most often lead to the Value Gap, but it can also provide opportunities for the creation of additional value.

In simple terms, a business combination can be considered to have two phases— the Transaction Phase (making the deal) and the Transition Phase (post-merger integration).

The Transaction Phase is the sexy part during which the deal is negotiated and then announced. The results of this phase are largely a function of deal-making negotiations. Typically, unless there is a big surprise during the post letter of intent due diligence, the financial structure of the deal is set.

The part which gets less attention is the Transition Phase, or the post-merger integration (PMI). This is the phase during which the disparate companies are integrated and combined. Very little attention has been given by business thought leaders toward addressing the challenges of post-merger integration. In an article in the Journal of Organizational Dynamics, business scholar Marc Epstein, PhD, states that “it is the actual execution of the merger strategy through the pre-merger and post-merger integration that appears to have the least understanding.” A focal point of this article is to address some of the most common areas of PMI/transition misunderstanding.

First, it is important to understand that not all mergers are the same with regard to effort. As shown in Figure 1, the intended result of the merger has a significant impact. If the intent is that the companies should continue to function largely autonomously after combination, this is referred to as coexistence. types-of-mergersIf one of the companies is going to be absorbed into the operations of the other, this is referred to as absorption. Finally, if the disparate portions of the two companies are to be fully integrated, intending to keep the best of both, resulting in one better company, this is referred to as synthesis. These three types of results are achieved with sequentially higher levels of effort, with less effort for a coexistence, typically just needing changes to financial and managerial reporting and minor integration, more for an absorption, as the surviving entity’s systems supplant those of the absorbed entity, and a significantly higher level of effort needed to cull the best of both companies and integrate together.

Regardless of the type of merger, the transition time frame available to create value is short.

After the transaction and deal close, the next six months are critical. Leading up to the close and day one of the transition period, 40% of the changes that will ever be initiated are set. This, of course, includes the changes mandated by the structure of the transaction agreement. At 3 months 65% have been initiated, and at 6 months 85% have been initiated. The remaining 15% of initiatives must build on those of the first six months. At around six months, for better or worse, the newly formed company settles into a steady state. Because the timeframe is so short, the way the transition is managed is critical.

Three Ways to Manage a Transition

There are three ways to manage a transition: Too Little, Too Late, and Just Right.

Too Little
Because deal-making is the cool, high-profile phase of a merger or acquisition, and there is a misconception that a good deal guarantees a successful merger or acquisition, there is a temptation to limit the transition effort to the day one hoop-la. This is a mistake. According to Kenneth W. Smith of Mercer Management Consulting, “The deal is won or lost after it’s done.” The short attention span of the Too Little approach can result in the transition team feeling abandoned and disincentivized, resulting in confusion and paralysis, disintegration, and arriving at the six-month steady state with a large Value Gap.

Too Late
In this scenario, top management puts all their attention into closing the deal, but interest ebbs after the closing. They fail to impart their vision, knowledge, focus, and momentum to transition management. Transition-phase visioning, planning, and organizing do not start until the deal is closed (or they never occur at all) as the transition teams rush into action. Furthermore, events race ahead and are out of control—losing customers, key employees, and shareholder value in the chaos. Time, money, and energy are burned in firefighting and fixing mistakes. In the Too Late scenario, the momentum for a good transition begins to ebb even before the close, and then after close the transition effort is a rush to catch up. Without a clear vision from management, the transition team is at best guessing what needs to be done, resulting in continual undoing, redoing, and repairing. The result is reaching the six-month steady state with mixed results.

Just Right
In this scenario, management begins the transition effort almost immediately after the letter of intent is signed. By planning and lining up resources early and communicating a vision and plan to the transition team, by day 1 the transition is fully under way. By properly handling the transition effort, it is clear to all parties that the transition effort is to be taken seriously: it receives adequate resources; planning is an integral part of transaction due diligence; the transition team is fully engaged and ready to go on day 1; the best people from both companies design the new company; a rapid implementation reduces the cost of the transition; and the design of the processes allows the team to seize opportunities for synergy to emerge and persist. The result is reaching steady state while avoiding the Value Gap and having created emergent synergies.

Key Success Factors of the Integration Process, helpful in avoiding the value gap and maximizing the possibility of achieving emergent synergies, are proactive integration along with maintaining speed and momentum.

  • Proactive integration, which means planning, monitoring, and adjusting how the integration process is being affected to maximize value, requires treating the transaction and transition as a single unified process, relying on experienced and trusted leadership, having a well-defined vision and focus, and provisioning adequate resources.
  • Speed and momentum are critical, and it is important to stay ahead of events, strive to realize merger value early, take quick action on people issues, and sustain energy and enthusiasm.

Vision and Plan: Hit the Ground Running in the Right Direction

Vision—The Transition Plan
Using a top down perspective, key to ensuring a successful transition is establishing and communicating the goals of the merger—the future state and the value it will deliver.

Then a Transition Plan, an actionable program to focus the process of achieving the plan, should be developed. This program will include:

  • Tasks (changes and deliverables) required to complete the plan; teams and people who will design and implement the future state; and resources, the tools, and the facilities the teams will need.
  • Targets (measureable milestones toward realizing the value), which should include accountability in the form of personal and team responsibilities for hitting targets and incentives, and rewards for hitting targets.
  • Priorities (critical tasks and targets for attaining the value) focusing on the tasks that create the highest value, understanding that even in the best plan, resources are limited and choices must be made.
  • Finally, Change Mechanisms, methods and manners by which unexpected opportunities can be seized and surprise problems can be addressed.

In addition to the Transition Plan, related but discrete, it is important to establish a Process Plan, a People Plan, and a Technology Plan.

Each of the Transition, Process, People, and Technology Plans must support the achievement of the vision and the value it promises. The following are the Why, How, and What questions that should be asked when developing these mutual, vision-supporting plans.

Why?  Key Business Strategies and Synergy Opportunities:

  • Why are we merging?
  • How will we know that we are successful?
  • What are our integrated operational strategic goals?
  • How will we consolidate to achieve maximum benefit from both organizations?

How?  Management Philosophy:

  • What kind of culture/employee environment will we build and foster?
  • What type of management style will we employ?
  • What strengths of each organization will we leverage?
  • What weaknesses will we overcome with the merger?
  • What policies should we adopt?
  • What new policies must be developed?
  • What skills do we need to retain and develop?
  • What should our culture characteristics be?
  • What initiatives should we continue or halt?

What?  High-Level Business Operating Model:

  • How will we manage our key business processes?
  • What is in scope?
  • What are our product, market, and channel strategies as well as our desired core competencies?
  • How can each function or process contribute to achieving the merger objectives?
  • What must happen to integrate each process?
  • What will the integrated process look like?
  • What will the integrated organization look like?
  • What skills and knowledge must we maintain?
  • What will our systems and applications infrastructure look like?
  • What systems must we roll out to enable the integration?
  • What data and information must be consolidated or converted?
  • How will we support our systems and users?

Processes—Designing the Synergies into the New Business

What needs to be done from a process standpoint varies on the type of merger.

For a coexistence, there should be a fast, cheap transition. At most, there is relatively minor work to impose control and coordination. That said, there may be unexpected incompatibilities, limited process synergies, little process improvement, little buy-in from employees, and no real economies of scale.

For an absorption, more effort is required, generally on a magnitude of 10 times the effort of a coexistence. The operations and assets of the absorbed company are just integrated into the existing systems of the acquirer. The best can be absorbed, the rest discontinued. This is not as easy as it sounds. The acquired operations and assets may not fit into the new organization well. Some strengths of the acquired company may be lost. The absorbed employees may not fit in well and might feel they have second-class status.

For a synthesis, even more effort is required because the purpose is to take the best processes from both companies. This can create unique challenges but provides the greatest upside potential for synergy. There are more emergent process-improvement opportunities. Because of the complexity of a synthesis, interim processes are needed during transition and there is a risk of losing focus and momentum.

Regardless of the type of merger, a key success factor is to Focus on Customer Processes. Priority should be given to customer-facing processes – Sales, Support, and Order Management. Design processes to present one consistent face to the customer. Deliver the benefits of merger synergies visibly to customers – new products, better service, more for their money. Create and staff interim processes to sustain the quality of products and services through the transition.

People—Realizing Merger Value by Getting the Best to Give Their Best

Clearly, a successful merger requires the higher motives to prevail at all levels of the organization – that is necessary.

Maslow defined three levels of human needs. The most basic are survival and must be satisfied before the higher levels are reached. In a business sense, the survival behaviors are those that people exhibit when they are concerned. A critical success factor is to minimize these survival type behaviors because they are destructive.

In a business context, the social level is demonstrated by company loyalty, feeling good about his/her job, their opinions are respected.

At the highest level, Self-actualization, the person is eager to go to the new world, is free from anxieties, and is able to develop emergent synergies, fulfilling others’ needs (not us and them).

On the Maslow hierarchy, employees acting from survival needs leads to fear and distrust, jockeying for position, rigidity and resistance to change, paralysis, distraction, collapse of productivity, resentment, sabotage, litigation, the best people resigning, and the worst people becoming resigned. These effects should be minimized.

Instead, an effort should be made to maximize the results of employees acting from self-actualization motivations. These lead to a sense of ownership of the new company; eagerness to contribute to the change; freedom to focus on new processes and systems; constructive criticism and input; being welcoming of new colleagues; generation of creative ideas; and discovering emergent synergies at all levels.

In addition to focusing solely on existing employees, thought should be given to the possibility of using external resources during the transition. By bringing in people from the outside, a company can:

  • Fill in-house gaps in merger transition experience
    • Ability to manage the business’ ability to manage a merger
    • External experts can develop in-house merger capability
  • Use an independent, external firm specializing in merger integration
    • Avoid conflicts due to other services from the same provider
    • Independent firm can select best providers of extra services
  • Overcome the double resource crunch of a merger transition
    • Enough competent people to accomplish the integration
    • The right people to keep the business humming through the transition
    • When they’re done, they’re gone
  • Leverage purchase accounting to pay for the transition
    • Transition costs don’t drag down the operational bottom line
    • Transition achievements become permanent, reusable operational improvements

Technology—Enabling the New Enterprise without Delaying the Transition

Disparate and discrete data and information systems are a significant hurdle in the integration process. The key success factor for technology enablement in a merger entity is to plan technology integration from the top down, looking to the requirements of the business both from company leadership as well as employees at all levels. Technology should be aligned first with the leadership’s vision of what the company should be doing, and then to the employees, providing the needed knowledge and the power to get things done. Planning should be done from the top down, but the key success factor for the implementation is to implement technology integration from the bottom up. Implement the plan by addressing change needs as they relate to networks, computer systems, storage, and other machines. Then connectivity, data, and applications should be addressed.

As an example, take just one area of technology – but a central one – data integration. Integrated processes require integrated data. Focus data integration effort on processes that will be combined by absorption or synthesis. Processes that merely coexist don’t need integrated data. All those who participate in an integrated business process must have common definitions for all of the people, policies, and procedures that they deal with. Data should be consolidated into shared, non-redundant data stores. Hardware infrastructure must be up to handling the combined quantity of data with adequate performance.

   

The Master Row Set: Managing Financial Statements

PDFPrintE-mail

Building a master row set for your Financial Statement Generator (FSG) reports will save time, provide agility and consistency, and allow the business users the ability to quickly create new reports "on-the-fly". In this article, we focus on how you can get the most out of reporting by employing a master row set in FSG. You’ll learn the secrets to keeping FSGs to a minimum and generating a variety of reports faster by focusing on the built-in reporting features of EBS. A master row set eliminates the requirement of rewriting each report in order to get the particular information you need at a certain time, allowing you to reduce the time spent creating custom reports from days to under an hour.

Read more: The Master Row Set: Managing Financial Statements

   

Page 1 of 22

Email Newsletter icon, E-mail Newsletter icon, Email List icon, E-mail List icon Enter your email address to sign up for our Newsletter

Sign up now

captcha
TEChanges - Agility by Design

January Puzzle

A traveler gets lost on a deserted island and finds himself surrounded by a group of n cannibals.

Each cannibal wants to eat the traveler but, as each knows, there is a risk. A cannibal that attacks and eats the traveler would become tired and defenseless. After he eats, he would become an easy target for another cannibal (who would also become tired and defenseless after eating).

The cannibals are all hungry, but they cannot trust each other to cooperate. The cannibals happen to be well versed in game theory, so they will think before making a move.

Does the nearest cannibal, or any cannibal in the group, devour the lost traveler?

Show solution...

Solution

The short answer is the traveler’s fate depends on the parity of the group. If there is an odd number of canibals, the traveler will be eaten, but if there is an even number, the traveler will survive.

To prove this, we will consider small groups and use mathematical induction to explain the solution for larger groups.

Case n = 1: this is an obvious case. If there is one cannibal, the traveler will be eaten. It doesn’t matter that the cannibal will get tired because there are no other cannibals around as a threat.

Case n = 2: this is a more interesting case. Each cannibal wishes to each the traveler, but each knows he cannot. If either cannibal eats the traveler, then he will become defenseless and the other one will eat him. So each cannibal uses backwards induction to realize that the only strategy is to not eat the traveler. The hapless traveler finds a bit of luck, therefore, and actually survives.

Case n = 3: this is where the problem gets interesting. The best strategy is for the closest cannibal to make a move and eat the traveler. The cannibal will be defenseless after eating, but ultimately he will be safe. Why is that? The reasoning is due to induction: once the cannibal eats the traveler, the resulting situation has 2 unfed cannibals and the 1 defenseless cannibal. But as we just showed above, when there are 2 unfed cannibals, neither will make a move for fear of being eaten by the other! Thus the first cannibal to make a move will be safe as the remaining 2 cannibals block each other.

We can prove the higher cases using mathematical induction. If the number n is odd, then the closest cannibal can safely eat the traveler because the remaining number of unfed cannibals is even (and by induction, with an even number of unfed cannibals no one makes a move). If the number n is even, then no cannibal will eat the traveler, for if he did, the remaining number of cannibals would be odd, meaning he will get eaten by the induction hypothesis.

Success Tips for Oracle Project Management

  • Create a standard for documentation at the beginning of your project, and hold team members accountable for completing documentation requirements as well as keeping them at and above the standards required.
  • Before promulgating user documentation or training, it’s also a good idea to choose a representative from the among the business users base to review materials first.
  • If you are not sure about the resources and budget required, obtain several estimates from people that have experience with the same size and scope of your project.
  • Be explicit, before beginning the project, what internal resources are required for execution. This includes people, infrastructure, hardware, and software.
  • Help the project champion understand the impact your project will have on the organization and how its successful completion will make him or her an internal hero or heroine for supporting it.
  • Break up your project into smaller projects (try for projects that can be completed in 4-6 months, especially early on) to get success and demonstrate momentum.
  • Make sure that your testing includes reports, upstream and downstream interfaces, customizations, enhancements, and workflows.
  • Ensure that comprehensive transition reports and meetings between departing and incoming personnel are completed.
  • Instead of spending time and resources implementing third-party reporting, consider consolidating multiple instances, moving to a global chart of accounts (CoA), and/or standardizing on a consistent calendar.
  • Include governance, risk, and compliance management as part of the project plan.
  • Finally, celebrate the successes. Too many projects focus on defects, failures, or small cost over-runs without looking at the big picture and what was accomplished.

The Analyst Corner

John Van Decker, Research VP of Gartner, states:

"A single chart of accounts allows consistency in financial reporting across the enterprise by standardizing on common metrics and reporting structures, reduces dependencies on a separate financial consolidation system, and significantly reduces the costs incurred with ongoing, complex conversions and translations."