Patent Application
20090112728
The prior art figure shows a conventional business management system. The conventional business management system includes multiple functional units that are used to track operations for each of the separate business units such as sales, shipping, and bookkeeping. In order to track progress within each of these functional business units, a specialized application that is tailored to the particular business units needs is typically implemented. For example, a sales application is used by the sales business unit to track sales contacts; a shipping application is used by the shipping business unit to track inventory; and a bookkeeping application is used by the bookkeeping unit to track accounts receivable.
Information for each of the separate functional business units is stored in separate data repositories. In particular, the data used with the sales application is stored in a sales data repository; the data used with the shipping application is stored in a shipping repository; and the data used with the bookkeeping unit is stored in a bookkeeping repository. When business operations shift among the different functional business units, the data from each functional business unit is transferred among the data repositories coupled to the various functional business units. For example, when a sale is made, data from the sales application is transferred from the sales repository to the shipping repository so the shipping application can facilitate appropriate shipping operations.
Additionally, the conventional business management system is typically set up so that different users access the different functional applications. For example, the sales team is authorized to access the sales data stored in the sales repository; the shipping team is authorized to access the shipping data stored in the shipping repository; and the bookkeeping team is authorized to store the bookkeeping data stored in the bookkeeping repository. In this way, the data corresponding to the various business units is separated and separately accessible. In this way, a person from a particular business unit accesses and manipulates their own instance, or copy, of the data, but they cannot access the data stored for another business unit, even though the data may have originated from the other business unit.
These characteristics of the conventional business management system derive from the way in which the different business unit applications have been developed. In many instances, customized software applications and user interfaces have been developed for very large corporations, but these enterprise-level solutions are typically not suitable for smaller companies, especially small entrepreneurial businesses. In particular, the conventional business management systems are not suited for small businesses because of their cost and complexity.
The description below includes examples and embodiments of the invention, which is defined by the appended claims and their equivalents. The description also includes the appendixes included herewith, that shows in detail an embodiment of the invention.
In contrast to the individual interfaces, the hybrid interface facilitates control and management of the business data by even a single person. For example, the hybrid interface allows a business owner to access and manipulate data related to any or all of the separate functional business units such as sales, shipping, and bookkeeping. It should be noted that the hybrid interface, similar to the other individual interfaces work with the same data that is stored in the data repository. In this way, the data in the data repository can be used by all of the functional business units in a straight-through processing system. Data does not need to be transferred among the different functional business units and their corresponding data repositories. In order to facilitate these different types of individual and hybrid interfaces with a single repository of data, user permissions can be implemented, as described in more detail in the accompanying documentation.
The illustrated process flow diagram shows one embodiment of how services (e.g., labor) and processes are used to turn raw materials into manufactured products. It should be noted that there are different types of processes, facilitated by the business management system, which can be implemented depending on the type of product being manufactured or the nature of the approach used to produce the manufactured products. Three of these processes are designated as recipe production, cook production, and time (or open) production. A short description of each process is provided here, and additional details of each type of process are provided in the accompanying documentation.
Recipe production refers to generating the manufactured products from the raw materials by using a predetermined set of steps or operations. Similar to a recipe used for baking, the recipe production uses an outlined set of operations, which specify quantities, order or execution, and so forth. In this way, the manufactured products are produced without deviation (or with insignificant deviation) from the predetermined process.
Cook production, in contrast to recipe production, does not require rigid conformance to a predetermined set of steps or operations. Rather, cook production allows personnel to deviate from a recipe or not use predetermined operations at all, so that the resulting product is not necessarily known beforehand. For example, using cook production, personnel might create a batch of food product using a variety of ingredients or a variety of measurements, without knowing in advance what those ingredients and/or measurements might be. Additionally, one embodiment of the business management system facilitates recordation of the operations, ingredients, measurements, and other pertinent information so that a subsequent batch might be produced using the recipe production process.
Time, or open, production also allows personnel to introduce some variance into the manufacturing process. However, in contrast to cook production, time production accommodates the aging process of some products such as wine. Since it is not necessarily known beforehand how long wine might be allowed to age before it is sold and shipped, the time production process allows personnel to track the aging process for later use.
After the manufactured products are generated, the business management system correlates the manufactured products with inventory. In one embodiment, the business management system uses a set of permissions, pricing, unit conversion, and historic data to populate an inventory database. The permissions, pricing, units, and history are described in more detail in the accompanying documentation. As an introduction, though, it should be noted that the permissions can be set for each user to indicate which interface(s) are accessible by each user. The pricing operations include rounding based on predefined parameters. The unit operations includes converting between various measurement units, including metric and imperial measurement units, as well as converting between quantities and groupings (e.g., one case may equal twelve bottles for a given product).
The business management system also correlates inventory to a catalog, which conveys the available products to a potential buyer, or customer. Embodiments of the catalog can be implemented in many different forms. For example, the catalog may be implemented as a website. The information in the catalog can also be used during sales calls and phone calls to existing and new customers. Like the correlation between the manufactured products and the inventory, the correlation between the inventory and the products can also account for permissions, pricing, units, and historical data. In one embodiment, the permissions also can indicate which customers are permitted to purchase certain products at specified prices. For example, some customers may be permitted to buy products at a 100% markup, while other customers may be permitted to buy the same type of product at a 150% markup, depending on the type of customer. Additionally, the permissions may control which customers can purchase certain quantities (e.g., retail size, wholesale size, etc.) of products. Further details are included in the accompanying documentation.
It should be noted that each of these functional business units also may include subsets of additional functionality. As an example, the sales unit may include functionality to implement the catalog, unit conversion, and fulfillment (e.g., inventory and shipping). Additionally, an embodiment of the business management system implements operations that are common across the several functional business units. For example, one embodiment of the business management system implements permissions, data access, lot tracking, and communications. The implementation of these operations and functional units is described in more detail in the accompanying documentation. Additionally, lot tracking is described in more detail with reference to
During manufacturing, the lots are tracked as raw materials are purchased, manufactured, and transferred to inventory. As an example, lot numbers assigned by the vendor to the raw materials are entered into the lot tracking tables when the raw material is purchased. As the raw materials are processed to generate the manufactured goods, the vendor lot numbers may be retrieved and assigned to each unit of the manufactured goods. In the lot tracking tables, internal lot numbers are then associated with the vendor lot numbers. Additionally, the internal lot numbers are associated with the manufactured goods. In this way, the lot tracking tables store data to correlate the vendor lot numbers, the internal lot numbers, and the manufactured goods. The lot tracking tables also may store other information such as inventory quantities on hand, as well as warehouse locations of the various units in inventory. The lot tracking tables also may store additional internal lot numbers used in sub-stages of the manufacturing process, so that raw materials used in each stage of the manufacturing process may be tracked and correlated back to the vendor lot number. After the internal lot numbers have been assigned to the manufactured goods, the manufactured goods may be transferred to inventory. While the lot numbers also may be separately transferred to inventory, one embodiment of the business management system allows the inventory personnel to access the same lot tracking tables, so that the manufacturing and inventory personnel use the same instance of the lot tracking numbers. The use of a single instance of data can help to avoid confusion and errors that might occur if the data were copied or otherwise not available to both functional business units.
During sales, generally, the business management system tracks which lots are distributed to which customers. More specifically, when a sales order is created for items purchased, the business management unit tracks and records which lots are selected to fulfill the shipping request corresponding to the sales order. The selected lot numbers are then removed from inventory to indicate that the corresponding items have been shipped (or are reserved to be shipped). In one embodiment, the selected lot numbers are also identified on the invoice that is generated and sent to the customer. In this way, the business management system facilitates lot tracking from the time the raw materials are received from the vendors until the manufactured goods are shipped to the customers.
| Number | Date | Country | |
|---|---|---|---|
| 60902574 | Feb 2007 | US |
