Patent application title: SYSTEM AND METHOD FOR CLOSED LOOP PURCHASE ORDER COMPLIANCE MANAGEMENT
John William Michalski (Evanston, IL, US)
Steven Lavoie (Lagrange, IL, US)
Anthony Defrances (Barrington, IL, US)
Michael Thomas Artman (Chicago, IL, US)
Class name: Electronic shopping list (e.g., purchase order, etc.) compilation or processing processing of requisition or purchase order
Publication date: 2013-01-31
Patent application number: 20130030958
A system and method are provided for using an optimized order plan
including freight allowance and expense per shipment. Further, an
notification of non-compliance is sent to purchasing when purchasing
attempts to initiate an order outside of the optimized order plan.
Additionally, a compliance reporting system reports the actual shipping
results as compared with the optimized order plan.
1. A method for electronically monitoring purchasing activity, said
method including: electronically receiving master data including pickup
data, dropoff data, and carrier rate data for at least one product;
electronically receiving an optimized order plan based on said master
data, wherein said optimized order plan includes at least one lane order
rule for purchasing said at least one product, wherein said at least one
lane order rule is determined by minimizing the cost of transporting said
at least one product; electronically receiving a purchase order for said
at least one product from a purchase order originator; electronically
comparing said purchase order to said at least one lane order rule; and
when said purchase order does not comply with said at least one lane
order rule, electronically transmitting a computerized notification of
said non-compliance to said purchase order originator.
2. The method of claim 1 wherein said at least one lane order rule includes a requirement for order timing size and frequency.
3. The method of claim 2 wherein said optimized order plan has been optimized to lower overall cost of transporting products using said at least one lane order rule.
4. The method of claim 1 wherein said master data further includes freight allowance and carrier expense per shipment.
5. The method of claim 4 wherein said at least one lane order rule is determined using said freight allowance and said carrier expense per shipment.
6. The method of claim 1 wherein said notification of non-compliance provides said purchase order originator with the option to override said notification of non-compliance.
7. The method of claim 6 further including calculating a shipping cost associated with said non-compliant purchase order.
8. The method of claim 7 wherein said notification of non-compliance displays said shipping cost associated with said non-compliant purchase order.
9. The method of claim 8 wherein said notification of non-compliance displays the difference between said shipping cost associated with said non-compliant purchase order and anticipated shipping cost associated with said lane order rule.
10. The method of claim 9 further including calculating a shipping cost associated with a proposed alternative purchase order
11. The method of claim 10 wherein said notification of non-compliance displays said shipping cost associated with said non-compliant purchase order, said shipping cost associated with said proposed alternative purchase order, and anticipated shipping cost associated with said lane order rule.
12. The method of claim 1 wherein said purchase order originator may subsequently modify said purchase order to form a modified purchase order.
13. The method of claim 12 further including: electronically comparing said modified purchase order to said at least one lane order rule; and when said modified purchase order does not comply with said at least one lane order rule, electronically transmitting a computerized notification of said non-compliance to said modified purchase order originator.
14. A method for electronically reporting compliance with an optimized order plan; said method including: electronically receiving master data including pickup data, dropoff data, and carrier rate data for at least one product; electronically receiving an optimized order plan based on said master data, wherein said optimized order plan includes at least one lane order rule for purchasing said at least one product, wherein said at least one lane order rule is determined by minimizing the cost of transporting said at least one product; electronically receiving actual shipment data with regard to an actual shipment of said at least one product including an actual shipment cost; and electronically transmitting a computerized compliance report listing said at least one lane order rule, a cost of transporting said at least one product in compliance with said at least one lane order rule, said actual shipment of said at least one product, said actual shipment cost.
15. The method of claim 14 wherein said computerized compliance report listing shows the difference between actual shipment cost and cost of transporting said at least one product in compliance with said at least one lane order rule.
16. The method of claim 14 wherein said computerized compliance report listing summarizes for a plurality of shipments a cost of transporting said plurality of shipments in compliance with said at least one lane order rule and said actual shipment cost of said plurality of shipments.
17. The method of claim 16 wherein said computerized compliance report listing shows the difference between said actual shipment cost for said plurality of shipments and said cost of transporting said plurality of shipments in compliance with said at least one lane order rule.
18. The method of claim 14 wherein said computerized compliance report listing summarizes for a plurality of products a cost of transporting said plurality of products in compliance with said at least one lane order rule and said actual shipment cost of said plurality of products.
19. The method of claim 18 wherein said computerized compliance report listing shows the difference between said actual shipment cost for said plurality of products and said cost of transporting said plurality of products in compliance with said at least one lane order rule.
20. A system for electronically monitoring purchasing activity, said system including: a master data computerized database storing master data including pickup data, dropoff data, and carrier rate data for at least one product; an order plan computerized database storing an optimized order plan based on said master data, wherein said optimized order plan includes at least one lane order rule for purchasing said at least one product, wherein said at least one lane order rule is determined by minimizing the cost of transporting said at least one product; and a computerized system electronically receiving a purchase order for said at least one product from a purchase order originator, wherein said computerized system retrieves said at least one lane order rule from said order plan computerized database and compares said purchase order to said at least one lane order rule, wherein, when said purchase order does not comply with said at least one lane order rule, said computerized system electronically transmits a computerized notification of said non-compliance to said purchase order originator.
CROSS-REFERENCE TO RELATED APPLICATIONS
 The present application claims the benefit of U.S. Provisional Application No. 61/435,563, filed Jan. 24, 2011, entitled "System and Method For Transportation Management" and also claims the benefit of U.S. Provisional Application No. 61/587,999, filed Jan. 18, 2012, entitled "System and Method For Transportation Management," both of which are hereby incorporated by reference in their entirety.
BACKGROUND OF THE INVENTION
 The present invention generally relates to a system and method for logistics. More particularly, the present invention relates to a system and method for improving logistics cost, trailer utilization, number of truck used, or miles driven.
 Logistics involves the transportation of goods from a source to a destination. Typically, the source is a seller of goods such as a manufacturer and the destination is a buyer of goods such as a retailer. Moving goods between the source and destination at the lowest possible cost has long been a goal of logistics and numerous prior art systems and methods have been developed in an attempt to do so.
BRIEF SUMMARY OF THE INVENTION
 One or more embodiments of the present invention provide a logistics system that uses an optimized order plan including freight allowance and expense per shipment. Further, an notification of non-compliance is sent to purchasing when purchasing attempts to initiate an order outside of the optimized order plan. Additionally, a compliance reporting system reports the actual shipping results as compared with the optimized order plan.
BRIEF DESCRIPTION OF THE DRAWINGS
 FIG. 1 illustrates a system for logistics optimization using lane order pattern flexing according to an embodiment of the present invention.
 FIG. 2 illustrates further detail of the optimization process performed by the modeling processor of FIG. 1.
 FIG. 3 illustrates how the present system for logistics optimization using lane order pattern flexing may provide a savings increase of 20-30%.
 FIG. 4 illustrates the example of FIG. 3 at an inventory rather than a lane level.
 FIG. 5 illustrates the addition of the present system for logistics optimization 100 into the logistics process.
 FIG. 6 illustrates a screen shot of an Inbound Transport Management (ITM) system according to an embodiment of the present invention.
 FIG. 7 illustrates a screenshot of the ITM lane import criteria screen.
 FIG. 8 illustrates a screenshot of the constraints preferably entered for the implementation of the combo model of FIG. 2.
 FIG. 9 illustrates a screenshot of an ITM scenario analysis screen providing a view of optimization solutions with the ability to lock, exclude, and mark solutions for publication.
 FIG. 10 illustrates a screenshot of a lane profiles tool for visualization and what-if analysis of lane optimization and order flexing results.
 FIG. 11 illustrates a screenshot of a lane analysis tool used to examine shipment, purchase order, inventory, and sales information summarized to a lane level to support order and route pattern determination.
 FIG. 12 illustrates a screenshot of lane order profiles which include purchasing guidelines for communication to purchasing systems or processes.
 FIG. 13 illustrates a screenshot of the compliance detail.
 FIG. 14 illustrates a screenshot of the gross margin dashboard.
 FIG. 15 illustrates a business information flow according to the present Inbound Transportation Management (ITM) system.
 FIG. 16 illustrates the combo model stack generation process according to an embodiment of the present invention.
 FIG. 17 illustrates a closed loop purchase order compliance system according to an embodiment of the present invention.
 FIG. 18 illustrates a compliance reporting system according to a preferred embodiment of the present invention.
 FIG. 19 illustrates a chart of the order compliance alerts.
 FIG. 20 illustrates the order compliance screen.
 FIG. 21 illustrates the PO import screen.
 FIGS. 22 and 23 illustrate two examples of the order compliance alert detail screen.
 FIG. 24 illustrates the alert widget.
 FIG. 25 illustrates a non-compliance report.
DETAILED DESCRIPTION OF THE INVENTION
 FIG. 1 illustrates a system for logistics optimization 100 using lane order pattern flexing according to an embodiment of the present invention. The system for logistics optimization 100 includes an Inbound Transportation Management (ITM) primary database 110, an ITM data preparation processor 120, an ITM data importer 130, a constraint set-up processor 140, a scenario set-up processor 150, a modeling processor 160, a model results viewing application 170, and a results publisher 180.
 In operation, ITM data is retrieved from the ITM database 110 by the ITM data preparation processor 120. Preferably, the data is retrieved or refreshed nightly, but may be retrieved or refreshed in other intervals such as weekly, hourly, monthly, or continuously. The ITM data preferably includes purchase order (PO) information with regard to each purchase order passing through the ITM system, but may instead operate with a subset of all of the available purchase orders. In addition to the PO information, the ITM data preferably includes item information for all of the items shipped in each of the POs. The ITM data may be retrieved from a remote site such as a data center, for example. The system for logistics optimization 100 may be co-located or remotely located from the data center.
 Next, at the ITM data preparation processor 120, the item data is aggregated at the PO level. For example, individual items that were historically purchased during the last 60 days are combined into a single or multiple POs representing a re-ordering of the same items during the next 60 day period. Additionally, data from the PO level may be taken and aggregated into a frequency and load size for the lane. This may be viewed as a theoretical set of POs. For example, a frequency of four and a load size of 40,000 lbs may be viewed as four POs in the next time period at 40,000 lbs each.
 In addition to historical information, other data may be employed. For example, forecast information may be employed such as for highly seasonal products, for example. Additionally, third party information such as lanes that are currently serviced by a third party, either inbound or backhaul, may be used. Additionally, instead of PO history, distribution center use or sale of items, or other inventory information may be used.
 Additionally, the PO data is aggregated at the lane level. A lane preferably includes a unique combination of 5 elements, partner identification, vendor number, original location, destination location, and temperature protection (TP). Partner identification is an identification of the company receiving the goods. Vendor number is an identification of the vendor selling the goods. Original location is an indication of where the goods are first picked-up or ship from. Destination location is an indication of where the goods are eventually intended to arrive. Temperature protection is an indication of whether the goods much remain refrigerated, frozen, or if no temperature protection is needed. Although in the above example 5 elements are used when setting a lane, a greater or lesser number of elements may be employed.
 As mentioned above, the PO data is aggregated at the lane level. That is, for each lane, all POs associated with a specific lane during the previous 60 days are electronically associated an identification of the specific lane. Additionally, the data can be for lanes that the user's company is not currently moving, so that the tool can be used to optimize them in order to try to bring in more freight under management.
 Next, the associated data is passed to the ITM data importer 130. The ITM data importer 130 filters the data and enters the data in an optimization module as further described below. For example, when filtering the data, the ITM data importer 130 presents several choices or options to a user. The user may then filter the network as desired. For example, a user may only want a subset of the distribution centers in a network, such a subset may represent a geographic area such as the east coast, for example. Further, a user may be interested in filtering the data in this way for any of several reasons, for example the user may have a new customer in the east coast area and be looking to determine the impact on logistics in the area.
 Additionally, the user may filter by temperature requirement, such as refrigerated vs. non refrigerated, or by the other options shown in the screen shot.
 Additionally, the ITM data importer summarizes the imported data by displaying the imported data for a user, for example, for displaying the data by lane. Additionally, the ITM data importer performs a quality check to identify missing information in the imported data. That is, for the imported attributes, the ITM data importer identifies the lanes with missing information and presents them to the user. For example, for the attribute of "weight", the ITM data importer may determine the total number of lanes with no weight, and the total revenue and other aspects associated with those lanes, and then present those lanes to the user. Similarly, the ITM data importer may give total number of lanes missing cubic feet (cube) or pallet.
 For example, the ITM data importer may identify the total number of lanes with any quality issue (missing any of weight, cube, or pallet) and provide a link to the lane so that the user can review the lane and attempt to determine what is wrong or enter in the missing data. Alternatively, the user is provided with the option to exclude lanes with incomplete data from the analysis.
 Finally, the ITM data importer preferably displays a graphical view of the data including plot vendor maps, data center map, and lane map for the imported data.
 Alternatively, filtering of data may be done in the normal manner of data base based on the criteria that the user enters, that is, a user might specify lanes going to a specific distribution center, or exclude lanes with a weight below a certain amount.
 Alternatively, with regard to the quality check, the quality check may do separate summaries of lanes that are missing weight info, missing cube info, missing ship from info, etc. and then permit the user to find the individual lanes that fall into each category. For example, the quality check may report that there are 23 lanes missing weight with a total revenue of $53,121 per month, and 45 lanes missing cube with a total rev of $43,634 per month, etc. The 23 lanes missing weight may also include lanes that are in the 45 missing cube.
 Next, the imported data is passed to the constraint set-up processor 140. At the constraint set-up processor, global constraints are established for the modeling process as further described below. However, such global constraints may later be overwritten at the scenario level and/or the model level.
 Next, the scenario set-up processor 150 is used to specify models that constitute a scenario, as further described below. The scenario set-up processor 150 may also specify data and set constraints used for optimization as further described below.
 Next, at the modeling processor 160, all of the models for a specific scenario are run, as further described below. The modeling processor 160 includes an optimization engine that provides optimized solutions in accordance with the specified scenario and constraints. The solutions from the optimization engine are obtained. Further, an optimization log is provided so that the optimized solutions may be stored in the optimization log.
 Next, the results of the modeling processor 160 are reviewed at the model results viewing application 170. At the model results viewing processor 160, several options are available. First, a specific solution or option may be locked or excluded based on the review. The solutions may also be excluded from future models so that a user need not re-reject the solution. Additionally, when locked, the solution is forced to come up again during the next solution determination. For example, even if the modeling processor 160 determines that a certain solution with a certain number of specific lanes is one of the desirable solutions, a reviewer may choose to discard the solution or discard specific lanes for reasons not related to profitability. As another example, a lane or solution may be chosen that has a specific truck in a specific city on a specific day or on weekends so that a driver may visit family.
 Additionally, the results viewing application 170 allows the reviewer to publish a solution or mark a solution for publication. That is, a particular chosen solution may be shared with other people in the company, such as purchasing employees, to make sure that the proposed solution provides for the needs of the purchasing employees as well--for example, with regard to inventory turns and desired stockpiles of inventory. The results viewing application 170 also makes a profile. The profile may be passed between employees to obtain consensus as to the solution.
 Also, after any change to a parameter of the model, such as locking or deleting a solution, the model may be re-run to display a new set of solutions which may then be further analyzed and potentially modified by the user as desired.
 Once a desired solution is determined and agreed to by all responsible employees, for example, both logistics and purchasing employees, the results publisher 180 publishes the results to the ITM database 110 to create a solution profile in the ITM database 110. Alternatively, the solution profile may have already been published and solution profile may now be made active. By publishing the results to the ITM database 110, the actual logistics instructions for the company are changed. For example, the company's goods will now be shipped to the company based on the shipping/logistic instructions that are now published to the ITM database 110 rather than previous instructions. Note however, that the published results sent to the ITM database 110 may but need not change all of the previous logistics instructions.
 In addition, the results publisher keeps a summary and/or copy of the result published to allow for later analysis and potential modification.
 FIG. 2 illustrates further detail of the optimization process performed by the modeling processor 160 of FIG. 1. In FIG. 2, several individual models 210-208 are used to form a stack of lane solutions 210 which are then passed to a Mixed Integer Program (MIP) Optimizer 220 to determine the optimal solution set. Then, a final consistent optimal solution set 230 is output.
 More specifically, the individual models 201-208 include a one way Truck Load (TL) model 201, a one way Less Than Truckload (LTL) model 202, a one way Inter Modal (IM) model 203, a combo model 204, a buy and fill moel 205, a loop/continuous move model 206, a cross dock model 207, and a backhaul model 208 each of which is further detailed below.
 First, the one way model Truck Load (TL) model 201 creates individual solutions for each lane in a list and order frequency is flexed/altered to maximize revenue per truck. In a preferred embodiment, the following formula is employed to find the optimum frequency:
 OptFreq=max(min(total monthly wt/max wt per truck, total monthly cube/max cube per truck, total monthly pallets/max cube per pallet), MinFreq)
 MinFreq=min(historical freq, 1/max time between orders)
 max time between orders=preset value based on inventory requirements
 Where monthly weight is the total weight on the lane over all items. Max weight is based on type of truck. Monthly cube is total cubic feet in volume required for the month over all items. Monthly pallets is the total pallets required over all items for a month. Trucks are generally measured in three dimensions--weight, cube, and pallet--each with its own max capacity. A truck may run out of capacity due to any one of these depending on what is being hauled.
 Alternatively, the model may be controlled to ignore one or two of weight, cube, or pallets, but preferably all three are used where available in order to better confirm a lane solution.
 The max time between orders is a constraint set by the user, for example, to make sure that minimum inventory targets are maintained. MinFreq is the minimum frequency of orders and is the lesser of the historical frequency or orders or the inverse of the max time between orders as set by the user.
 The next model is the one way LTL model 202. In the one way LTL model 202, individual solutions are created for each lane and placed in a list. The individual solutions use a less-than-truckload mode of transportation. The order frequency is preferably not flexed or altered from the current information. Additionally, weight, cube, and pallets per load are based on the recent historical purchase orders. Additionally, lanes are restricted based on LTL operational constraints set by the user. Some constraints for LTL include: max weight, max cube, and max pallets. If the weight, cube or pallets are larger than the max, then the load is TL (truckload) and typically cannot be moved LTL because LTL carrier would typically refuse to take it.
 The next model is the one way intermodal model 203. In the one way intermodal model, 203, individual solutions are created for each lane that will use an inter-modal method of transportation, such as both trucking and rail, for example. Other modes include shipping, parcel and backhaul (BH).
 With regard to backhaul, a company that owns its own fleet may have trucks that are normally routed to a remote location to make a drop off or delivery, but are then forced to return empty to the distribution center from the drop off point. However, these trucks may be used to make an inbound pick-up and delivery at very low cost since they had to travel in proximity anyway to return to the DC.
 That is, instead of the truck returning to the distribution center or manufacturer empty, the truck may be used as a carrier back. The inclusion of possible backhaul lanes in the model may be accomplished by its own mode, called backhaul mode, or it may be implemented in other tools. For example, the combo model may combine lanes and used backhaul lanes as an option. In one or more embodiments of the description of models above, the trucks/equipment are owned by the distributor so as to take advantage of the backhaul opportunities.
 Additionally, with regard to the "parcel" mode, the parcel mode takes into account the shipping cost of moving parcel-size and weight items using a common carrier such as UPS or the US or international mail.
 In the one way intermodal model 203, order frequency is flexed using the same formula as in the one way truckload model 201. Additionally, lanes are restricted based on intermodal operational constraints set by the user, for example, weight, cube, and pallet, as well as also temp, length of lane, and origin and destination.
 The next model is the combo model 204. In the combo model 204, individual solutions are created where each solution includes two or more lanes. More specifically, the lanes of a solution may be identified based on pick-up proximity, drop-off proximity, temperature protection, revenue generated, or restrictions based on one or more of: 1) out of route miles, 2) number of picks, 3) number of drops, or 4) number of stops. All lanes in the solution are preferably set to have the same OptFreq (that is, all lanes are picked up together each time. However, in alternatives this may be varied. The formula for determining OptFreq is preferably the same formula employed by the one way truckload model 201.
 The next model is the buy and fill model 205. The buy and fill model 205 creates individual solutions where each solution includes 2 lanes: the buy lane and the filler lane. More specifically, the lanes of a solution may be identified based on pick-up proximity, drop-off proximity, temperature protection, revenue generated, or restrictions based on one or more of: 1) out of route miles, 2) number of picks, 3) number of drops, or 4) number of stops. The buy and fill model 205 is typically only used for some orders and the filler lane is not always transported with the buy lane. Preferably the filler lane is flexed in order to sufficiently fill a truck. However, the buy lane is typically not flexed and the frequency is set to the historical frequency. For example, the filler lane may be four purchase orders per month, each taking up 90% of a truck while the buy lane may be one load per month taking up 10% of a truck. Once per month the two lanes may be shipped together, but 3 times per month the filler may be shipped all alone.
 The next model is the loop/continuous move model 206. In the loop/continuous move model 206, individual solutions are created where each solution includes two or more lanes. More specifically, the lanes of a solution may be identified based on pick-up proximity, drop-off proximity, temperature protection, revenue generated, or restrictions based on one or more of: 1) out of route miles, and 2) number of stops. Frequency of delivery is flexed. The loop/continuous move model 206 differs from the combo model 204 in that loads are transported in sequence in the loop/continuous move model 206 rather than at the same time in the combo model 204.
 The next model is the cross dock model 207. The cross dock model 207 creates individual solutions where each solution includes multiple lanes with consolidation and/or deconsolidation points such as provided by a cross dock. In the cross dock model 207 order frequency is flexed. Additionally, many lanes can be covered in a single solution. That is, one cross dock solution may be the optimal way to move the flow for several lanes. This is different from one ways where one one way solution only involves one lanes. One cross dock solution will typically always involve multiple lanes.
 The final model is the backhaul model 208. As discussed above with regard to the intermodal model 203, a company that owns its own fleet may have trucks that are normally routed to a remote location to make a drop off or delivery, but are then forced to return empty to the distribution center from the drop off point. However, these trucks may be used to make an inbound pick-up and delivery at very low cost since they had to travel in proximity anyway to return to the DC.
 That is, instead of the truck returning to the distribution center or manufacturer empty, the truck may be used as a carrier back. The inclusion of possible backhaul lanes in the model may be accomplished by its own model, called backhaul model, or it may be implemented in other tools. In one or more embodiments of the description of models above, the trucks/equipment are owned by the distributor so as to take advantage of the backhaul opportunities.
 One aspect of the present invention is the recognition that there is a considerable difference between inbound logistics and outbound logistics. For example, one or more embodiments of the present invention provide an achievable strategy for inbound logistics organizations to elevate freight savings by 20-30%, through a collaborative, technology-enabled approach to logistics and purchasing planning. More than a new set of tactics, the approach implements a paradigm shift, away from a model that tends to mimic an outbound logistics program, and towards one that extracts full value from the advantages of inbound freight control.
 One important difference is, unlike the outbound side, Inbound Freight Management has a revenue component, originating in the freight allowances on products provided by the shipper. If the logistics team can source carriers at a rate lower than the allowances, Inbound Logistics can become a profit center, earning income on lanes taken over from shippers. Because of this, in the inbound world, load profitability and total landed cost (in addition to service level) are important metrics requiring management. Freight cost reduction, the traditional barometer of logistics performance, tells only half the story. Moreover, the story must be told at an item level. Logistics income is impacted by the viability of SKU-level freight allowances in reflecting true manufacturer freight costs, and also by the mix of items on the truck. Item-level visibility is a valuable asset while managing inbound freight and pursuing lowest total landed cost.
 Another important difference is that Inbound freight programs can largely be selective in the lanes they convert to their management. Increased profitability may be as much a question of what lanes an organization manages--or choose to cease managing--as how well they manage them. Effective monitoring of lane profitability enables Inbound Logistics departments to build the network they want, rather than manage the network they are given. In practice, organizations struggle in matching up daily load planning to the network planning exercise that persuaded them to take over management of a freight lane. Proper synchronicity between these processes is important to deliver predictability of results in Inbound Freight.
 Another difference is that Inbound Freight planners work in the same company as the buyers placing the orders--and consequently can vary or flex the orders in terms of amount and frequency so as to maximize logistics efficiency. This is an opportunity for collaboration between Purchasing and Logistics, to provide ordering guidelines that create routing efficiencies. Equipment utilization is the largest single driver of freight cost per case, and the largest single driver of equipment utilization is the buying pattern: how much is ordered, when it is ordered, and with what frequency. Outbound shippers will attempt to influence purchasing behaviors through order volume price breaks, and in some instances vendor managed inventory programs. However, Inbound Logistics has the far greater opportunity for true, broad-based collaboration with Purchasing.
 The differences between inbound logistics and the typical logistics program outlined above are very significant. Inbound and Outbound logistics are, truly, entirely different business functions. Unfortunately, technology providers have largely ignored the differences between them. Transportation Management System (TMS) solutions purchased for inbound freight management are precisely the same systems purchased for outbound freight, and implemented nearly identically. Little or no consideration has been given to load profitability or per case analysis, and item-level visibility is rare.
 No prior art systems address the selective nature of the freight under management, the need to build synchronicity between network planning and load planning, and none expose or manage the opportunities to collaborate with Purchasing. Put simply, in commercial transportation management systems, the world is seen through the lens of a manufacturer shipping outbound product. This is the arena in which the products have been developed and tested, and it represents the largest market segment their sales forces pursue. As a result, inbound logistics personnel are forced to fit within the mold of outbound transportation management processes, or struggle to change or augment those capabilities to meet their objectives.
 When it comes to collaboration between Purchasing and Logistics, without the right tools, most supply chain organizations find limits to what they can achieve. Absent a well-defined and technology-enabled platform for partnership, these highly inter-dependent functions remain at arm's length, communicating without collaborating, bound to different and often conflicting incentives.
 When it comes to locating and quantifying the potential savings by integrating inbound logistics with purchasing, one of the differentiating aspects of inbound freight matters above all others: control of the freight resides in the same organization as control of the order. The potential power of this is easy to understand, in theory. After all, if logistics personnel placed the orders, every truck would be 100% utilized, every time (or better yet, running on rail). Back in the real world of changing customer demand, short product shelf life, inventory carrying costs, and storage capacity constraints, a separate purchasing and inventory control function is required.
 However, there is a middle ground where a deeper logistics savings consideration can become a greater part of purchasing operations. Few would disagree that if purchase orders are aligned to more consistently fill trucks to capacity and minimize miles driven, logistics costs will improve. However, purchasing and replenishment systems that include freight cost consideration do so at only the most rudimentary levels, if at all.
 If a supply chain leader asks the question: "What is the absolute minimum total landed cost that can be achieved by the combined order-to-delivery process, without putting customers at risk?" most Purchasing and Logistics teams do not have the ability to answer. Instead, current systems rely on the following three assumptions: Assumption #1: Purchasing needs no further guidance. Our Buyers already try to order in full truckloads wherever they can; Assumption #2: Logistics' requests for order pattern changes will generally be infeasible, as they do not consider customer demand; and Assumption #3: Since logistics savings are based on freight consolidation, every attempt to save in freight costs will come at the expense of inventory levels. These assumptions come to rule the relationship between Purchasing and Logistics. As is often the case with deeply embedded assumptions, they are self-fulfilling: they quash any momentum to fully collaborate in driving savings, thereby limiting logistics to offer only the most rudimentary and uninformed purchasing guidelines, which only appear to further prove out the assumptions. The guidelines, born in the manual spreadsheet manipulations of a logistics engineer, tend only to increase order sizes and reduce inventory turns (putting them at immediately odds with Purchasing performance metrics), and often ask for alignment of orders in ways that will risk stocking out of a product. In practice, a few vendors may be found that both sides agree can be regularly scheduled to deliver simultaneously, but even these requests from logistics are frequently ignored in favor of daily decision-making on the part of the buyer. As embedded as it is, this is a cycle of behavior that can only be broken with a clear measure of the value of breaking it.
 FIG. 3 illustrates how the present system for logistics optimization 100 using lane order pattern flexing may provide a savings increase of 20-30%. FIG. 3 includes a current delivery pattern 310, a current shipment truck fill 320 and a current order summary 330. FIG. 3 also illustrates a new delivery pattern 350, a new shipment truck fill 360, and a new order summary 370, as well as a logistic results summary 380 and a route map 390. Additionally, the items carried by the trucks are differentiated into product A and B based on their shading. Further, although only two items and a single route are shown, FIG. 3 is meant to be a simplified example of the present system for logistics optimization 100.
 Turning to FIG. 3, the current delivery pattern 310 illustrates that the company receives in a 20-day period two deliveries of product A and four deliveries of product B. The frequency and days of the weeks of each delivery are shown. As shown, none of the six total deliveries take place on the same day.
 Turning to the current shipment truck fill 320, is it shown that the two deliveries of product A take place using a truck that is 90% filled, while the deliveries of product B take place using a truck that is anywhere from 45% to 75% filled. Such a situation may occur often in the real world where product B's usage over the month or the demand for product B over the month is non-uniform.
 The current order summary 330 reveals that the current logistics process to deliver items A and B uses 6 trucks which are on average 67% filled and 3600 total miles are driven per month. The cost for these trucks to make the deliveries is $7700 per month in this example--although this number may vary depending, for example, on route, temperature protection, and truck size.
 In other words, the left side of FIG. 3 represents a sample current state: freight running on two lanes on a monthly basis, both dropping off at the same facility. One product is ordered in near full truckload quantities, twice a month. The other is ordered in smaller quantities, required at least four times a month. Assuming that no other shipments exist that could fill out the trucks on the second lane, both Purchasing and Logistics would typically claim comfort with the current state. The buyer is filling equipment where they can, and only ordering smaller quantities where they must.
 On the Logistics side, the prior art TMS route optimization software leaves the full truckloads alone (no TMS system on the market ever seeks to break a truckload shipment), and sees no way to improve upon the second lane. Logistics engineers may ask Purchasing to place larger orders on Lane 2 for product B, only to be told that inventory turns cannot be increased without risk of stocking out.
 Turning to the new delivery pattern 350, it shows a new delivery pattern in which there are only four deliveries during a 20 day period and each delivery includes a delivery of both Product A and Product B. Turning to the new shipment truck fill 360, it is seen that each of the new shipments is composed of about 40% of Product A and about 60% of Product B.
 Thus, the two approximately full truckload shipments of Product A have been broken into four shipments of partial truckload and the remainder of each shipment is filled with Product B. As shown in the new order summary 370, the new plan only involves four trucks rather than 6, and each of the trucks is about 99% filled. Further, the monthly cost is about $6150 and the miles traveled is about 2900.
 The improvement of the new delivery pattern over the old delivery pattern is summarized in the logistics results summary 380. More specifically, two fewer trucks are used, the trailers of the trucks that are used are much more fully utilized--up to about 99% from 67%, there is a $1500 per month savings (20.1%) and 700 fewer miles are traveled in all.
 FIG. 4 illustrates the example of FIG. 3 at an inventory rather than a lane level. FIG. 4 shows the current replenishment pattern 410, current order 420, and current order summary 430, as well as a new replenishment pattern 450, new order 460, new order summary 470, purchasing results 480 and route map 490.
 As shown in FIG. 4, the current order replenishment plan 410 shows the current order 420 is delivered on six different days and that the delivery amount of Product B varies. As shown in the current order summary 430, the current order provides six total inventory turns and provides an average of 21 days on hand of Product A.
 Turning now to the new order, as shown in the new replenishment plan 450, deliveries are down to four days and both Product and Product B are delivered together. Further, a smaller amount of Product A is delivered in each of the four shipments and the deliveries of Product B are set to an average number, as shown in the new order 460. As shown in the new order summary, the new order 460 represents eight total inventory turns and reduces Product A to 17.25 days on hand. Finally, as shown in the purchasing results, the new order 460 has increased the overall turns by 33%, reduced the inventory of Product A by 18, and made the order pattern of Product B more predictable.
 In other words, by scaling down the truckload orders to free up enough space to absorb the shipments on the second lane, a new picture emerges: four full multi-stop truckloads a month. This concept goes against prior art TMS systems which would not break up the shipments of Item A because they are approximately a full truckload. The results of the example of FIG. 3 include: 20% reduction in freight cost, 60% increase in overall inventory turns, 33% reduction in deliveries hitting the dock, and 19% reduction in miles driven.
 These results are very beneficial, and not just in the savings they deliver. Importantly, they protect and even improve upon key purchasing metrics as well. Add to this the operations benefit of reduced dock congestion, and a significant carbon footprint improvement, and this example begins to speak loudly for a new way of thinking about logistics ability to impact supply chain objectives. The example shatters the assumption that logistics savings only comes at the expense of inventory risk. In fact, all three assumptions in the prior section are challenged in this one example, for one very counterintuitive reason: scaling down orders can improve logistics efficiency.
 The present logistics optimization system considers the full range of possible adjustments to order size, frequency, and timing to exponentially increase the possibilities to mine for freight consolidation. Unlike the old method of route optimization alone that waits for matching shipments, combined optimization of ordering and routing essentially lets the user match shipments as desired.
 The present logistics optimization system may expose and assess the universe of permutations of ordering and routing. When the present optimization algorithms are employed to uncover these "win-win" scenarios, the results can be surprising in scale. Assessments of inbound freight networks large and small have shown that solutions such as the example above are so prevalent in a network that the network-wide savings of 20-30% is accompanied by an average total inventory reduction of 1.5%. This inventory reduction is a net number, inclusive of solutions that scale orders up (within reasonable constraints, such as maximums of 3-4 weeks inventory) or scale orders down. This means that the impact of scaled down orders is outstripping the impact of scaling them up. While these results can vary from one inbound network to the next, most organizations can minimally expect to keep inventory levels flat while still achieving significant savings.
 The logistics changes found by the present logistics system may be implemented without significant process or systems upheaval. In a preferred system, buyers still place the orders, using existing systems and logistics planners still plan the routes, using existing TMS capabilities. Collaboration preferably does not require any change to the fundamental responsibilities or personnel makeup of these teams. It also does not require a disruption in the flow of orders from purchasing to transportation systems. Instead, implementation is building new connective tissue between purchasing and logistics processes, based on up-front planning and a closed feedback loop for compliance monitoring and corrective action. The connective tissue is found in specific new activities and technologies at three junctures in the order-to delivery sequence: prior to order, prior to tender, and post-delivery.
 FIG. 5 illustrates the addition of the present system for logistics optimization 100 into the logistics process 500. As shown in FIG. 5, the logistics process 500 includes sales 510, purchasing 520, and logistics 530. Sales 510 includes the function of creating a forecast 515 of inventory or products needed. Purchasing 520 includes the function of creating an order 525 to obtain the desired inventory or products. Logistics 530 includes the functions of tendering the load 532 and delivering the load 535. Additionally, one or more aspects of the present invention may interact with the logistics process 500 at one or more of prior to order 550, prior to tender 560, and post-delivery 570.
 With regard to the interaction of the present logistics system 100 with the logistics process prior to order 550, the most expedient way to adjust order patterns and set routing guidelines is to do so with a planning-based approach, pro-actively, before the orders are placed. This periodic planning process is performed on the side of the existing buying and freight execution sequence. It is certainly possible to implement a more invasive and exacting process, generating replenishment orders systematically that consider forecast, inventory, and logistics impact. However, if the intention is to capture the bulk of these savings with the minimum of systems and process turnover (as is likely), a planning-based approach is advisable.
 In a planning-based approach, a technology solution is leveraged, likely by a Logistics Engineering person or team, to periodically examine demand requirements, based on recent order history, updated with any seasonal or other demand forecasting information. This process might be run once a week, once a month, once a quarter--the frequency depends on network volatility, and how tightly the organization wants to manage the ordering guidelines to support the highest profitability. The logistics optimization system accepts order history, forecast information, and carrier rate information, and uses optimization technology as described above to identify the most profitable ordering and routing scenarios available for each freight lane.
 Constraints may be applied at a global, supplier, and item level to mark the boundaries of feasibility. Some constraints likely to be required include (but are not limited to) equipment type, limitations on products that cannot be consolidated, pallet space, and on the order pattern side, shelf-life restrictions, and the degree to which order frequency can be adjusted.
 The output of this process is not orders or loads. It is a set of guidelines on how to purchase and route product: recommendations on order size, frequency, and timing, to set up ideal consolidation solutions. The optimization technology accounts for the opportunities available to your network, by leveraging multiple models as described above. This may further include backhaul opportunities and fleet utilization, continuous moves, and cross-dock or pooling scenarios.
 A process is then implemented to review, approve, and "publish" these guidelines. This involves software-supported workflow to track agreement from both Logistics and Purchasing, and signoff on the savings and inventory impact for each solution. Once published, the guidelines are fed to purchasing, for adoption during the replenishment process. Most robust purchasing systems may accept the types of parameters required, but some buying organizations may be more comfortable using them in a more manual fashion. In addition, the profitability expectations of each solution are stored, as targets to be measured against later in the process.
 The present proactive planning process is typically not resource-intensive for each implementation. The first time it is run, the entire network is under review, and the list of solutions to assess quite long. From that point forward, the full network is preferably included in the optimization process, but only the resulting solutions that are new or changed need enter into the review and approval process. This is typically a manageable list, on the order of 3 to 5% of total freight lanes on a monthly basis, even in large-scale networks.
 In fact, the overall resource impact of this approach can be very favorable. Today, many organizations leverage optimization technology within their selected TMS solution to select routing for freight just prior to load tender. The simpler solutions that emerge from this process can largely be tendered with little oversight. However, freight planners often find that they need to review all suggested consolidations that emerge from these tools, to ensure feasibility. Despite the promise of automation, too many business exceptions exist to permit this sort of hands-off freight routing. In contrast, an up-front planning approach seeks to smooth out and standardize purchase orders, such that route determination more often follows a plan that has already been vetted. In an environment of collaboration between Purchasing and Logistics, daily exception management at the point of freight execution is significantly reduced, in favor of a more efficient, proactive planning regimen. Before moving on, it should be mentioned that the planning function can and should be leveraged to examine freight that is not yet under management, where a freight allowance is known (or a true freight cost has been broken out). Completely separate from the 20-30% savings improvement stated earlier is the added revenue achievable by finding new lanes that fit with the buyer's network. In many instances these are lanes previously ignored as unprofitable, when order pattern changes were not considered.
 With regard to the interaction of the present logistics system 100 with the logistics process prior to tender 560, it is recognized that lasting success in any collaboration activity requires more than just a joint planning function. A closed feedback loop is desirable to monitor compliance to plan, and support timely corrective action between both teams. Since this solution involves building better order patterns up front, it is possible within this model to recapture load profitability before it is even lost (i.e. shipped).
 This may be done by leveraging exception management technology to highlight non-compliant purchase orders as soon as they are created, and facilitate communication between load planners and buyers to revise the order before it is built into a shipment and tendered. There is no need for this process to interrupt the automated flow of orders to a TMS system, as long as the compliance alerts are acted upon before the tender occurs. This may often be accomplished through simple process timing (checking compliance alerts prior to running the load creation process in the TMS).
 Not all instances of non-compliance may require action. Some may arise from unanticipated inventory needs. Some may be close enough to target thresholds that a decision can be made to allow the order through. Some may simply highlight that a plan needs to be changed for future orders to reflect new realities. To facilitate this decision process, it may be important that the exact reason for non-compliance and the profitability impact (dollar variance from target) is available with the compliance exception alert. It is also desirable to log reason codes whenever a non-compliant order is allowed through, to facilitate summary reporting of process effectiveness.
 This "soft checkpoint" (soft, meaning that orders are not automatically adjusted to be compliant), along with the periodic re-assessment of plans discussed earlier, enables order patterns to be changed in a way that is still responsive to a dynamic supply network. As valid exceptions occur, they are allowed through, but measured, and if representative of the new operating rules, used to trigger updates to the plans.
 With regard to the interaction of the present logistics system 100 with the logistics process post delivery 570, the final step in the closed-loop process is trend reporting at a lane level, and root cause analysis on the margin of delivered loads. A host of factors may reduce load profitability from the targets set during planning, including freight allowance changes, order size fluctuations, and product mix on the revenue side, and secondary carrier usage, fuel rate changes, and one of a host of possible unplanned accessorial charges in the load cost.
 In depth visibility and drilldown root-cause analysis into these drivers is desirable for any inbound freight management team (even those not taking this approach in full), as well as a tracked workflow process to ensure that steps are taken to prevent or offset margin decay over the life of a freight lane. It is noted that commercial TMS solutions largely neglect freight margin analysis. A few may carry PO-level revenue through, but cannot measure the impact of item mix and lack the ability to drive to SKU-level analysis. Without the capability to perform detailed root cause analysis into both revenue and cost movement, inbound freight management teams may struggle to maintain a rigorous focus on sustaining savings.
 FIG. 6 illustrates a screen shot 600 of an Inbound Transport Management (ITM) system according to an embodiment of the present invention. As shown in FIG. 6, the screenshot 600 includes project information 610, such as a name and description, the dates created, modified, and published, and any status.
 The screenshot 600 also shows a set up section 620 including data for several lanes. Each lane preferably includes information about the type of data, the data set name, the date it was loaded, the data it may have been modified, and the number of records. A list of at least some of the project constraints is also shown at 622.
 The screenshot 600 also shows an optimize section 630 including several scenarios for consideration for implementation. Each scenario is preferably associated with an ID, a name, a run history, the number of solutions, the monthly savings, and the schedule. Additionally, a summary of scenario results is shown at 632.
 The screenshot 600 also shows a publish section 640 including a listing of scenarios that have been published. Each published scenario is preferably associated with a date, name, person publishing, savings, and solutions.
 FIG. 7 illustrates a screenshot 700 of the ITM lane import criteria screen. As mentioned above with regard to FIG. 1, recent historical lane data is imported into the ITM system. As shown in FIG. 7, the recent historical data includes lane and vendor numbers, vendor name, ship-from city, freight allowance, weight, and cube, monthly frequency, and several other factors.
 Additionally, FIG. 7 illustrates the "grade" column. The grade column represents a grade that is manually by a reviewer to indicate lanes that are more profitable than another, for example, for review and discussion of taking over such lanes. Alternatively, the grade may be assigned based on profitability and risk of execution of the lane or solution.
 FIG. 8 illustrates a screenshot 800 of the constraints preferably entered for the implementation of the combo model 204 of FIG. 2. As shown in the screen shot 800, the constraints preferably include load size constraints, lane constraints, financial constraints, cost settings, flexing constraints, and solution constraints. Similar constraints may be entered for each of the models 201-207 of FIG. 2.
 FIG. 9 illustrates a screenshot 900 of an ITM scenario analysis screen providing a view of optimization solutions with the ability to lock, exclude, and mark solutions for publication. The screenshot 900 includes set up information 910 including lane data and scenario constraints and overrides. The screenshot 900 also includes optimize information 920 identifying each model employed, a description of the model, any constraints employed, the cost savings, and the model results. The screen shot 900 also includes scenario solution detail information 930 including status and information about the solutions.
 FIG. 10 illustrates a screenshot 1000 of a lane profiles tool for visualization and what-if analysis of lane optimization and order flexing results. From the screenshot of FIG. 10, the user may view and modify drivers financial, operations, and inventory impact of one-way, consolidation (combo), cross-dock, backhaul solutions. The user may also view related solutions and access lane and item information on recent sales, purchase, and inventory. The user may also manage workflow in activating solution.
 Further, as shown in the screenshot 1000 of FIG. 10, it includes a lane identification 1005 and a financial and operations summary 1010 that includes new order frequency, size, and estimated revenue, cost, margin, and inventory impact. The screenshot 1000 also shows a list of lanes included in the solution profile 1020 with summary statistics related to purchase patterns and freight financials. The screenshot 1000 also shows a list 1030 of other profiled that include lanes in this profile.
 FIG. 11 illustrates a screenshot 1100 of a lane analysis tool used to examine shipment, purchase order, inventory, and sales information summarized to a lane level to support order and route pattern determination. Additionally, the screenshot 1100 shows a lane-level summarization 1110 of order/shipment information and product sales, by min, max, average, etc. across recent history. Further, the screenshot 1100 shows recent purchase order activity 1120.
 FIG. 12 illustrates a screenshot of lane order profiles which include purchasing guidelines for communication to purchasing systems or processes. The purchasing guidelines may include order size, timing, and frequency rules for one or more lanes in a routing solution. The screenshot includes solution (load) level rules 1210, and lane (PO) level rules for Pickup #1 1220 and Pickup #2 1230.
 FIG. 13 illustrates a screenshot 1300 of the compliance detail. The compliance detail displays expected and actual purchase order size, timing, frequency, revenue, cost, and highlights elements of non-compliance with order rules, to enable logistics or purchasing personnel to assess the financial impact and consider correcting orders prior to load tender.
 FIG. 14 illustrates a screenshot 1400 of the gross margin dashboard. The gross margin dashboard enables root cause analysis of margin shortfalls against target, showing performance against target, over time, by revenue and cost component/driver. It also enables view of only negative impact components, to identify improvement opportunities whether or not the load met margin targets at an overall level. Further, the gross margin dashboard allows drill down into lane and shipment level to examine root cause and allows the user to filter by "lane issue", a workflow mechanism for tracking resolution of issues found.
 As shown in FIG. 14, the gross margin dashboard 1400 allows a user to click on an entry such as the Jul 11 "Lower Load Qty" entry. A summary screen 1410 detailing those loads having lower load quantity is then displayed. Additionally, the summary screen 1410 allows a user to click on a specific load to display a detail screen 1430 displaying details for that particular load.
 FIG. 15 illustrates a business information flow 1500 according to the present Inbound Transportation Management (ITM) system. The business flow 1500 includes an Information Management System (IMS) Platform 1510 including an ITM Profitability Optimizer 1512 and an ITM Profitability manager 1514. The business flow 1500 also includes a Transportation Management System (TMS) 1520 and the Purchasing department 1530.
 As described above, order history 1550 is passed to the ITM Profitability Optimizer 1512 which generates a solution of optimized logistics representing a set of lane profiles 1552 and passes the lane profiles to the ITM Profitability Manager 1514. Additionally, the ITM Profitability Optimizer 1512 passes order rules 1554 back to the Purchasing department.
 The purchasing department 1530 then places orders 1560 with the ITM Profitability Manager 1514. The ITM Profitability Manager 1514 identifies exceptions to the lane profile in the purchase orders 1560 and passes an identification of exceptions 1562 back to the purchasing department for review and potential modification to conform to the optimized lane profile.
 Once the compliance exceptions have been resolved, the ITM Profitability Manager 1514 relays purchase orders and routing instructions 1570 to the TMS 1520. The ITM Profitability Manager 1514 also receives data with regard to the actual shipments 1572 back from the TMS 1520. The received data may be used to recalculate a new optimal lane pattern or to perform a root cause analysis on variance against profitability targets and initiate corrective action.
 FIG. 16 illustrates the combo model stack generation process according to an embodiment of the present invention. The combo model 204 was referenced in FIG. 2. In general, as further described below, the combo model stack generation process first filters the lanes, then creates a proximity list of pairs of lanes, then creates a list of base 2 lane combos, then filters to solution the list for 2 way combos, then creates a list of base 3 lane combos, then filters to solution the list for 3 way combos, and repeats the process up until the N-way combos where N is pre-selected by a user.
 Turning to FIG. 16, first, at step 1605 the list of lanes with lane data is compiled. Next at step 1610, the total list of lanes is filtered to selects a list of usable lanes. Lanes may be unusable for several reasons, such as a shipment date outside the current stack date.
 Next, at step 1615, a pairwise proximity list is formed. Proximity is preferably defined by the distance between picks and drops. The distance is preferably calculated by using the havesine formula:
c=2*a tan 2( a, (1-a))
d=R*c where R is earth's radius
 The pairwise proximity list is then used to form a base list of 2 way solutions at step 1620. Solutions may be filtered out at step 1625 if the proximity exceeds a value set by the user or for other reasons described below. The remaining solutions are added to the stack 1630.
 Additionally, the model may filter out a solution based on one or more of the following: out of route miles, value of revenue on lane, value on lane vs cost on lane, quantity on trucks, margin, or other criteria. The model may also provide exact filtering based on whether lanes are reviewed in order by length, by revenue, or by quantity on truck.
 Alternatively, solutions may be filtered out based on zip code regions. For example, the distance between a zip code in CA and a zip code from NJ is available from a lookup table or other database, and may be directly compared to the desired proximity.
 With regard to the three-way base list, the three way base list is created by adding lanes to the two way list a step 1635 and then filtering the lanes for the desired solutions at step 1640. These lanes may be selected based on the proximity list and is preferably in proximity for both current lanes in the list. Similarly, a four way base list may be constructed by adding an additional lane to the three way base list using the proximity list at step 1645 and proximity for the previous lanes on the list and then filtering the list at step 1650. This process may be repeated up to an N-way base list where N may be set by the user. The stack 1630 of all available solutions may then be reviewed and ordered by a criteria such as margin to obtain the desired solution.
 With regard to calculating margin, the solutions described above preferably include a calculation of margin as well. Margin is viewed as revenue minus cost. In this case, the cost estimate is based on dollar per mile cost for traveling from the pick up to the drop off point supplied in original data times the total miles for the shortest route.
 Further, when determining the combo, the transported products are treated as first in last out so that the last product loaded on the truck is the first product out. However, in an alternative embodiment, it is allowed to remove this constraint. Additionally, in the combo model, there is preferably always a lane in the combo where the pick up for the lane is the first pick up for the route and the drop off for the lane is the last drop off for the route.
 Additionally, in the model, the route is determined optimally by examining combinations with reductions due to the final lane in route being constrained to be shorter than initial lane in route. If not, then one can simply reverse the entire pick sequence and get a shorter total route, which implies that the route was not optimal. This cuts the number of potential combinations in half. For example if lane A>lane B>lane C in length then only need to check ABC, ACB, and BAC.
 Additionally, a combo may be included in the list of bases but not in the list of solutions because the margin is too low for the solution. Additionally, a combo might be excluded from the list of bases because it has such a low margin that no possible future lanes will bring the value up to the required threshold margin.
 With regard to calculating frequency, the following formulas may be employed:
 OptFreq=max(min(total monthly weight/max weight per truck, total monthly cube/max cube per truck, total monthly pallets/max cube per pallet), MinFreq)
 Total monthly weight=sum of weight over all items over all lanes
 Total monthly cube=sum of cube over all items over all lanes
 Total monthly pallet=sum of pallets over all items over all lanes
 MinFreq=min(max(historical freq by lane), 1/max time between orders)
 max time between orders=preset value based on inventory requirements, can be a function of temp
 max(historical freq by lane)=largest freq on any individual lane
 Additionally, frequency may be restricted if a lane is marked as "do not flex". In such a situation, the frequency of the solution is not allowed to drop below the current frequency of the lane. This implies MinFreq=max(min(max(historical freq by lane for lanes that can be flexed), 1/max time between orders), max(historical freq by lane for lanes that cannot be flexed)).
 For example, if a combo is composed of Lane A and Lane B and Lane A is marked as "do not flex", and the frequency for lane A=freqA and the frequency for lane B=freqB then MinFreq=max(min(freqB, 1/max time between orders),freqA).
 FIG. 17 illustrates a closed loop purchase order compliance system 1700 according to an embodiment of the present invention. The compliance system 1700 includes a compliance monitor 1710, a database of master data 1720, a database of subroutes 1730, a purchasing system 1740, and a transportation management system 1750.
 As described above, the compliance system 1700 may be incorporated in the ITM Profitability manager 1514 as shown in FIG. 15. Alternatively, the compliance system may be implemented on its own.
 In operation, the compliance monitor 1710 receives information from the database of master data including: an item master, a vendor master, ship-from information, ship-to information, and carrier rates. The compliance monitor 1710 also received information from the database of master data 1720, which includes predetermined guideline/targets for how to order and route products. For example, the compliance monitor 1710 may receive lane order rules, lane revenue and cost component dollar targets.
 The compliance monitor 1710 then received a purchase order or a purchase order line item from the purchasing system 1740. The compliance monitor 1710 then matches the purchase order to the most profitable "intended" subroute as received from the database of subroutes. The compliance monitor also locates purchase orders or any other lanes included in the solution, for example to complete an intended consolidation, a continuous move, or some other aspect.
 The compliance monitor 1710 then compared the purchase orders to lane order rules for the subroute. These lane order rules may include: 1) order size including min/max weight, cube, and pallets; 2) combined order size including min/max weight, cube, pallets, and revenue; 3) order timing including transit time, pickup/delivery day & time windows; and 4) order frequency including availability of other purchase orders involved in the solution, for example when there is a consolidation or loop in the solution.
 The compliance monitor 1710 the initiates an exception alert for purchase orders out of compliance with subroute lane order rules. The purchase order non-compliance alert is sent to the purchasing system 1740. At the purchasing system, purchasing personnel may update and resubmit the order back through the compliance monitor. When transmitting the alert to the purchasing system 1740, the compliance monitor 1710 preferably links the alert with an interface describing the non-compliance and showing targeted and estimated freight margin in order to demonstrate the impact of the non-compliant decision.
 Finally, the compliance monitor 1710 allows compliance purchase orders through to the freight execution process or transportation management system. For non-compliant purchase orders, the compliance monitor 1710 also allows them through if a reason code is supplied for reporting purposes. The compliance monitor also includes routing instructions and revenue/cost targets.
 FIG. 18 illustrates a compliance reporting system 1800 according to a preferred embodiment of the present invention. The compliance reporting system 1800 includes the compliance monitor 1710, database of master data 1720, database of subroutes 1730, purchasing system 1740, and transportation management system 1750 of FIG. 18 and adds the compliance reporting processor 1810, purchasing management process 1820 and logistics management process 1830.
 The compliance reporting system 1800 of FIG. 18 picks up where the compliance monitor 1710 of FIG. 17 left off. That is, after the compliance monitor 1710 passes purchase orders, routing instructions, and revenue and cost targets to the transportation management system 1750, the transportation management system 1750 initiates the desired transport and monitors the real-world result. That is, the transportation management system 1750 records the actual shipment routing and the actual shipment costs by cost component.
 The actual shipment routing and the actual shipment costs by cost component are then passed to the compliance reporting processor 1810. The compliance reporting processor also retrieves from the database of master data 1720 the item master, the vendor master, the ship-from information, the ship-to information, and the carrier rates. Additionally, the compliance reporting processor 1810 retrieves from the database of subroutes 1730 the lane order rules and lane revenue and cost component dollar targets.
 The compliance reporting processor 1810 then compares the actual shipment routing and actual shipment costs by cost component with the optimized information from the databases 1720, 1730 and generates a summary/trend report of the purchase order/route compliance and freight margin impact. The report is then preferably passed to the purchasing management 1820 and the logistic management process 1830 for use in future purchasing and logistics activities.
 Further, in one or more embodiments, the compliance system described above creates a user interface that allows the user to search, sort, and manage POs/Loads against established ordering and routing rules. Additionally, the user interface provides a list of POs/Loads that match a lane order profile on an active subroute, a list of POs/Loads that do not match a lane order profile on an active subroute, and alerts users where orders are off from planned targets, and allow user to set non-compliance and ignore reason codes. The user interface also preferably has a home screen Widget that summaries, by Partner, the number of the POs/Loads with a non-compliance status, that is pending action by a user.
 In one embodiment of the ITM above, the ITM may only requires that there is a single intended subroute per route. When active subroutes are change from any status to intended, there is also a prompt screen to switch the subroutes. In an alternative embodiment, the requirement is removed and a route is allowed to have multiple subroutes types. For alternative and unintended subroutes, the alternative embodiment preferably still requires the user to link to an intended subroute under the route.
 FIG. 19 illustrates a chart of the order compliance alerts. In an alternative embodiment, an order compliance alert group is set up that includes tolerance setup capabilities to measure POs/Loads against lane order profiles. These options will define the parameters for creating order compliance alerts: 1) On or off options including Global Activation, Alert Buyer?, Alert Planner?, Alert Ops Support?, and Alert Account Manager?; 2) Tolerance--weight or percentage below and/or above the min/max from the Land Order Profile including: Order Rules: Weight, Order Rules: Cube, and Order Rules: Pallets; 3) Tolerance--dollars or percentage below the min from the Lane Order Profile including: Order Rules: Revenue; 4) On or Off selection including Order Rules: Transit Days, Order Rules: Transit Time, Order Rules: Lead Time, and Revenue vs. Target; 5) Tolerance--dollar or percentage above the line haul cost from the Planning Summary from the Subroute including Line Haul vs Target; 6) Tolerance--dollar or percentage below the load margin from the Planning Summary from the Subroute including Margin vs. Target.
 When customer purchase orders are first received through the data feed, as well as changed over time, each order goes through a validation process to measure ordering pattern against available lane order profiles. After each validation check, the IMS stores generational information to track historical details including: PO and Load summary details--(total cube, wgt, cases, revenue, exp, marg, etc); Non-compliance and/or ignore PO reason codes; User and timestamp; Update--creation or changes to the order/load; Code--non-compliance or ignore code set by a user; Compliant or non compliant status; Active or closed status.
 FIG. 20 illustrates the order compliance screen. As shown in FIG. 20, the order compliance screen includes the following search criteria options: Partner Master, Partner (multi-select), Vendor Name, Vendor (multi-select), Route (multi-select), Subroute, Ship via, Planner, Buyer, Ops Support, Account Manager search, PU/Deliv/Create search, Compliance Status--based on current status (Compliant, Non-Compliant), Alert Status--based on current status (Active, Closed), "Show Generations" checkbox--to show historical generational statuses, Non-compliance reason code (multi-select), Ignore PO reason code (multi-select).
 As new customer purchase orders are created or changed by an update from the daily file feeds, then the first check is to find an available subroute that has a matching lane order profile to the available pos. The subroute(s) available should be in active status. The subroute(s) must have a usage of Intended or Alternative. The subroute(s) must have an associated Lane Order Profile (LOP). The associated Dist/Vend and purchase order must be flagged as "Managed".
 If the PO has found a matching subroute/lane order profile (LOP), the purchase order(s) are matching the LOP, and the load totals are matching the LOP load minimum amount, then it is set to the statuses of "Compliant" and "Active". This display shows groupings of open customer-pos that should be built into loads.
 For the POs that did not find a matching subroute/LOP, the purchase order(s) are not matching the LOP, and/or the load totals are matching the LOP load minimum amount, then the statuses becomes "Non-Compliant" and "Active". On the order compliance return screen, then the alert column displays an indicator (spy glass or other icon) that the user will need to process the order. When the user selects the specific order or multiple orders, then a detail screen opens to allow the user to see the details. For the order or selected multiple orders, then the detail screen pulls together all of the available routes and subroutes, these orders could fall under.
 The detail screen also links to certain system records including: PO Number: link to the cust po; Load number: This is only applicable when the load has been create; Subroute: link the subroute screen; Vendor: Links to the Dist/Vend; Display the PO and Load summary details (weight, cube, cases, etc); Display the ship via; "PO Import" link to the po import screen.
 FIG. 21 illustrates the PO import screen. When the user selects the PO import screen, the following fields are pre-populated to direct the user to the appropriate purchase order--PO number to the identified alerts--DV Driver--Cust & AS Pos. Additionally, the purchase order is auto-searched as to display the available subroutes. and the lane is selected in the upper panel which will display the subroutes in the lower panel. Additionally, the subroute lower panel is set to an expanded view.
 FIGS. 22 and 23 illustrate two examples of the order compliance alert detail screen. As shown in the figures, the reason for non-compliance is displayed by subroute. Reasons for non-compliance include: 1) Weight:The number of pounds over or under tolerance; 2) Cube:The cube over or under tolerance; 3) Pallets: The number of pallets over or under tolerance; 4) PO Revenue: The $ value under PO revenue tolerance; 5) Transit: Indicator if the PO is not meeting either the transit days, transit dates, and/or lead time; 6) Missing PO: Indicator that there is at least one more order that is not aligned with the ordering rules (transit days and time are not matching); 7) Line Haul: The $ value over Load line haul tolerance; 8) Margin: The $ value under margin tolerance; 9) If no carrier rate is assigned to a subroute or is not assigned to a created load, then the "line haul" and "margin" measurements have a an indicator that information is missing; 10) Missing LOP: Indicator that the subroute has been matched from Section 2, but does not have a lane order profile to check ordering rules.
 There are two additional special indicators that are highlighted if they occur: 1) Ship Via Mismatch: Indicator that the PO and Dist/Vend have mismatching managed flags. Still display the options of Route/SRs defined above; 2) Missing SR: Indicator that there is no available subroute. This occurs only if the Dist/Vend is marked as available. Rule 1 still applies.
 For each purchase order the user is able to assign a non-compliance or ignore PO reason code. For example-Non-compliance dropdown: User can select a non-compliance code that is normally set during the import process. This is then stored on the AS Po for reporting purposes. Alternatively, Ignore dropdown: User can select an ignore code that is normally set from the PO import screen and stored on the customer PO for reporting purposes. Additionally, the user can group the previously selected orders to combine in the theoretical load that is just a holding measure for knowing to realert the user post load build.
 Additionally, when the load is created, in one embodiment a second validation process is run to make sure that the appropriate loads have been created. In this case, if the load has been created to a valid subroute, with the correct matching details to the lane order profile, then the status is changed to "compliant" and "closed". However, if the load has been created to a valid subroute, but with the incorrect matching details to the lane order profile, then the status is changed to "non-compliant" and "active"--unless the POs on the load had all been previously been set with a "non-compliance" prior to load creation and marked as grouped, and there were no changes to all of the orders on the newly created load. (cases, wgt, cube, ship via, ship from, etc). In this instance, still record a generation for the order(s) and also set the previous reason code(s).
 If the PO has been imported and assigned to a load, and the load is assigned to an unintended subroute, then set to "non-compliant" and "active". Represent the same options of available (intended and alternative) subroutes, with the unintended subroute visible. For calculating the mismatching details, use the lane order profile from the linked intended subroute to the available unintended subroute. Use the Missing Subroute indicator. Highlight the subroute in red. If the PO has been imported and assigned to a load, and the load is NOT assigned to a subroute, then set to "non-compliant" and "active". For the loads that have an "active" "non-compliant code", then they will get included back to the widget.
 FIG. 24 illustrates the alert widget. The alert widget presents all of the purchase orders that need to be actioned by a user. Based on the Compliance Alert setup, the alert is presented to the load planner, the AS buyer, and/or the ops support set on the dist vend, as well as the account manager set on the Partner record. In the instance the buyer, planner, ops support, and/or account manager is the same user, then only show one alert. The total count of the open alerts is grouped by Partner, and totaled on the alerts. The user can select a totaled value and drill down to the Order Compliance Screen, with the repopulated statuses. For Active Compliant, set the statuses of active and compliant, Set the user (buyer, planner, ops, accnt mang), and Set the partner. For Active non-compliant, Set the statuses of active and non compliant, Set the user (buyer, planner, ops, accnt mang), and Set the partner.
 Users stop or close an alert by accomplishing one of the following: 1) A user sets a "non-compliance" code or an "ignore" through import screen process, or 2) POs status has changed to "compliant" and/or "closed".
 Any time a purchase order changes, then the same validation process preferably occurs to make sure the change still falls within tolerance. Any "non-compliance" or "ignore PO" code that has been previously set is preferably presented back onto the alert details and widget. Once a PO is set to delivered status, then the alert is preferably not shown again.
 FIG. 25 illustrates a non-compliance report. As described above, once a non-compliant purchase order has been processed, the compliance reporting processor may receive the actual logistics information and compare it to the previous desired solution in a non-compliance report. As shown in FIG. 25, the non-compliance report shows the total purchase orders non-compliance, the percentage of POs that were non-compliance, the target and actual margins, and the margin delta both in dollars and in percentages.
 Thus, one or more embodiments of the present inventor provide, for the desired ordering and routing plan for a given lane or set of lanes, financial targets are stored that indicate the expected Freight allowance ("revenue") and carrier expense per shipment. Expense targets are set for line haul, fuel, and specific accessorial charges expected, based on a primary carrier. With targets captured for a specific ordering and routing plan, and captured for both revenue and cost, the system can measure and report on the variance from financial target for every shipment, and the dollar impact of non-compliance with the rules that are set for a particular planned order and routing solution to be viable.
 For the desired ordering and routing plan for a given lane or set of lanes, order rules are stored that indicate the minimum and/or maximum thresholds for weight, cube, pallet count, freight allowance, transit duration (days), and pickup and delivery windows. These thresholds set the operational boundaries within which an order and routing solution will be viable and will meet margin expectations. With the storage of these rules, non-compliance can be highlighted for any order placed on the lane, and alerts triggered that enable corrective action prior to tender.
 Compliance with the order rules is determined and reported as orders are created and refined, and prior to the creation and tender of a freight shipment to a carrier. By locating the compliance monitoring and alerting prior to shipment tender, buyers are given the opportunity to correct the size and timing of purchase orders, so as to pro-actively protect against the loss of freight margin when possible.
 Alerts of non-compliance provide visibility into the specific rules violated by the order, and depict the revenue, cost, and margin dollar impact on the given shipment. By leveraging the financial targets and order rules to demonstrate the nature and impact of buyer non-compliance, the user is able to undertake a specific corrective action. Measurement of financial impact also allows load planners and buyers to focus attention on the non-compliance issues with the highest impact on overall freight margin.
 Alerts of non-compliance are able to show the compliance of a PO with multiple solutions ("subroutes"). Lanes can have multiple alternate order and routing plans, to cover expected variations in order timing and size. By depicting the compliance and performance against financial targets for all related solutions simultaneously, the system enables a planning-based approach to freight margin optimization even in dynamic replenishment environments, and prevents users from having to eliminate more complex solutions because they are too unpredictable.
 Non-compliance of purchase orders with order rules, and corresponding financial impact, are reported in summary after shipment execution, to provide measurement of total non-compliance impact, and provide direction for broader corrective action.
 While particular elements, embodiments, and applications of the present invention have been shown and described, it is understood that the invention is not limited thereto because modifications may be made by those skilled in the art, particularly in light of the foregoing teaching. It is therefore contemplated by the appended claims to cover such modifications and incorporate those features which come within the spirit and scope of the invention.
Patent applications by Anthony Defrances, Barrington, IL US
Patent applications by John William Michalski, Evanston, IL US
Patent applications by Steven Lavoie, Lagrange, IL US