Develop the Myers order tracking system for Oracle and PHP instances (1)

For a company driven by the receivables business model, one of its core business functions is to input, track, and record orders. In this regard, outstanding companies can scale their organizations and increase their profits without encountering infrastructure restrictions. When order processing is troublesome, error-prone, or inconsistent, the company will suffer economic losses due to direct costs and reduced production efficiency.

In Myers Internet, the core business matters focus on building a customer base, providing continuous services for Myers and helping it solve problems when customer problems arise. The company is using many different systems to handle various aspects of order input and implementation cycles. These systems are neither integrated with each other nor have mechanisms to ensure that each order is properly recorded.

Myers order tracking system (MOTS)

Like many other organizations, Myers has grown from a small company to a medium-sized company, and has maintained the same process and system throughout its growth. When most of these processes were established, all transactions were handled by email, paper records, and on-site visits to the site. Five or six years ago, an engineer at Myers used Cold Fusion of Allaire and a Microsoft SQL Server database to assemble a system to track order implementation. This system is called MOTS (Myers order tracking system ), it allows the sales and account management department to enter orders, which are then implemented by support, engineering, design, information system, and accounting departments. Although this system is an important step forward, it still has many manual steps and is not integrated with any other business systems.

At about the same time, a system was created, in which customers and sales representatives can order products on the Myers website online. This system can create a new Web site and calculate the total cost of installation and repeatability of the provided Web site package. It then sends an email to each department. Each department can input the order to MOTS and create the accounting information in the Account Management System.

Architecture barriers

This type of architecture suffers from several system problems. One of the obvious problems with Myers is the manual data input required to start order tracking and the errors produced as a result of this manual process. Another problem is the disconnection between the company's order input, order tracking and accounting systems, order loss, information omissions, and errors.

Another occasional problem is that the MOTS system has internal defects. Because of the MOTS writing method, you can enter an order without department allocation information or missing department allocation information. When this happens, the Order will eventually be lost in the system. When the order is lost, accurate and timely accounting is more difficult to achieve.

As the business grows, defects in the system structure become more and more obvious. As the number of customers and orders increases, the number of lost and incorrect orders increases, this has brought immeasurable impact to the company's revenue. In addition, the number of manually entered data results in latency and low processing efficiency.

As revenue is greatly affected and efficiency is reduced within the implementation organization, it is obvious that there must be a replacement system to link everything, increase efficiency and reduce error rates. The following figure shows the old system.

498) this. width = 498; 'onmousewheel = 'javascript: return big (this) 'height = 259 alt = "\" src = "/files/uploadimg/20080926/1021000 .gif" width = 338>
Figure 1: Old System Architecture

This figure shows all regions that require manual data input. Because these systems are not integrated, there is a high possibility of data loss or distortion. Global requirements immediately become apparent.1