Inside Out: Back Office Systems Have Become Gateways to the External Community

PDFPrintE-mail

What used to be considered “back-office” systems are not located in the back of the office anymore. Systems that support a company’s infrastructure for sales, customer service, and supplier relations are front and center customer-, supplier- and employee-facing systems. The heightened importance of the internet to daily business processes requires that a wide variety of information must be available to number of different internal and external parties, creating both opportunities and risks. This overall interconnectedness of users and data systems means that the data has to be available, secure, standardized, and complete, consistent, and correct so that both the internal and external users can find the information that they need.

In order to maintain data integrity in those outward facing systems, it is critical that security measures ensure that only the right parties have access to the right subset of the data at the right time – and that they know where to find it. As a second challenge for IT in outward facing systems, some of the data that the system uses and provides is not wholly internal to the company. Roughly 30 percent of Global 1000 consumer goods enterprises require external data synchronization with their top 10 trading partners; the same will be true of Global 1000 nonconsumer goods enterprises by 2010 (White and Koslowski, 2006).

External partners and distribution channels increase IT complexity by introducing the need to seamlessly interface with many different external systems: banking and credit card systems, business-to-business exchange sites, call centers, and others. We will examine three normal business cycles that used to be internal processes and now require windows into other external systems and the sharing of internal systems with other departments and outside partners.

  1. Order-to-Cash – This cycle involves all of the different processes that take place within and outside of an organization from the time an order is taken to the time cash is received. At any given time during this cycle, customers need to be able to access current data regarding the status of their orders, their bills and payments, their account balances, and the services provided to them. However, many other parties other than the customers will need access to the data to perform their functions:
    1. Finance – Credit Management, Invoicing, Accounts Payable, Accounts Receivable, and Aging & Collections all need to be able to access and manipulate order and customer information.
    2. Fulfillment – The company’s fulfillment department must be able to know that an order has been taken and be able to indicate that order has been fulfilled.
    3. Inventory – Fulfillment must be able to interact with the inventory system to validate that the products on the order are available to be processed or shipped, and in which warehouse to pick the order. If it is not inventory-on-hand or if it has reached the reorder point, then the external suppliers need to be notified to ship additional product.
    4. Distribution – The company’s distribution department needs access to the data indicating that an order is ready to be shipped, customer information indicating where and to whom it is to be shipped, and the method and cost of shipping (to be relayed to the finance department). The third-party logistics company who will ship the order to the customer needs to know the size and weight of the shipment so that it can send the appropriate vehicle, and needs to know the availability for pickup.
  2. Hire-to-Exit – This cycle includes the many processes that necessarily take place from the time an employee is hired into a company to the time the same employee exits the company. During the time a person is employed by a company, he or she needs to be able to find at any time their timesheets, hire terms, training, and benefits information. Recruiters may submit applicants directly from their system into the company’s on-line application database. The Human Resources department will also need unfettered access to the same information, and to workman’s compensation claims that are external to their company systems. The external benefits providers may need access to internal employee data to provide and track benefits. Many times, the employees directly access the benefits provider’s systems to file claims and check the status of the claims.
  3. Procure-to-Pay – This cycle usually involves the purchasing department of an organization, beginning with a request for quote and purchase order and concluding with an outgoing payment, requiring the creation of various other documents in the process. However, this process affects and is affected by other departments – inventory, material requirements planning, production, distribution, and financial departments all play a role. At any point in time, data that must be available to all of the departments involved include the status of purchase orders and back-ordered goods as well as account status and inventory information for multiple suppliers.

Ideally, everyone involved in this complex web of business processes would have a thorough understanding of what systems are shared, how and where to look for the correct information, and the security that is in place. What used to be your own internal operating information now needs to be visible to third parties. Outside parties such as suppliers and customers are requiring more transparency, more data, and better reporting – these components are, as a business matter, becoming mandatory rather than optional. In the quest to get the right information to the right people at the right time, the emphasis on internal data quality becomes more important. More internal and external systems need to be in sync as complexity increases. The internet is an unbelievable asset that will inevitably turn a business inside-out, so be careful that what is on the inside is ready for the outside world.

Add comment


Security code
Refresh

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."