EP3022704A1 - System and methods for brute force traversal and comparing segments - Google Patents
System and methods for brute force traversal and comparing segmentsInfo
- Publication number
- EP3022704A1 EP3022704A1 EP14826696.8A EP14826696A EP3022704A1 EP 3022704 A1 EP3022704 A1 EP 3022704A1 EP 14826696 A EP14826696 A EP 14826696A EP 3022704 A1 EP3022704 A1 EP 3022704A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- segment
- segments
- recited
- ancestor
- transactions
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Withdrawn
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
- G06Q30/0283—Price estimation or determination
Definitions
- the present invention relates to business to business market price control and management systems. More particularly, the present invention relates to systems and methods for brute force traversal of transactions in order to enable segmented analysis. It also relates to systems and methods for the comparing segments in order to drive profitability and policy.
- B2B business to business
- B2C Business to Consumer
- B2B Unlike B2C environments, in B2B markets a small number of customers represent the lion's share of the business. Managing the prices of these key customers is where most of the pricing opportunity lies.
- segmenting transactions As is known in the art, segmenting transactions, products or customers (or some combination thereof) is a useful way of grouping data by common traits. These segments thereby enabling modeling of behaviors and/or outcomes.
- Traditional transaction analysis in the B2B market typically focuses on a specific segment in which a domain expert expects to find evidence of interesting behavior that can be actionable in terms of policy by the company to improve returns on sales.
- the present invention discloses business to business market price control and management systems. More particularly, the present invention teaches systems and methods for brute force traversal of a transaction data set, useful in association with an integrated price management system.
- the systems and methods for brute force traversal receive a data dictionary that describes dimensions of transactions and hierarchical relationships between the dimensions. Next, possible combinations of transactions may be generated. A segmentation key for each of the possible combinations is also generated. The transactions are then segmented according to the key system.
- Statistical metrics of decision variables are calculated within each segment.
- the statistical metrics include a minimum, maximum and threshold for the decision variables.
- the ancestor segments for each segment are identified.
- the ancestor segments are each segment that exists in a higher level of the hierarchical relationship, and can be defined to preclude redundant hierarchical levels.
- the statistical metrics of each segment are compared to each of its ancestor segment's statistical metrics in order to identify outliers.
- the outliers are identified where the threshold for the ancestor segment is below the minimum, or above the maximum, for the segment. In some cases, the threshold is approximately the 50 percentile for the segment, and the maximum is approximately the 90 th percentile for the segment.
- a margin percentage for each transaction may also be generated. Due to the size of the dataset, the segmenting and the calculating statistical metrics are performed in parallel. Likewise, an estimate for the time to first results and time to completion can also be generated.
- the systems and methods for comparing segments is useful in association with an integrated price management system.
- an output from a segmentation process is received.
- the segmentation may be generated via a brute force traversal of a transaction database. This output is reduced to a pruned set of segments.
- separate graphs of connected segments are generated.
- the graphs provide a first order classification of the segments into non-overlapping spaces.
- the interconnections between the graphed segments are generated based upon ancestry of said segments.
- the ancestor segments are each segment that exists in a higher level of the hierarchical relationship.
- the non-overlapping spaces are based upon hierarchies of segment attributes, and the interconnections between the graphed segments are generated based upon similarities of the segments to one another.
- the process of generating separate graphs utilizes graph theory in which each segment is a node.
- the systems and methods then identify a central node within each of the separate graphs.
- the identification of each central node utilizes social networking techniques.
- the most profitable segments connected to the identified central node for each graph are analyzed for by calculating the average profit per node and selecting for the node with the largest average profit. Policy may also be generated based upon the analysis of the most profitable segment connections.
- Figure 1 is a simple graphical representation of an enterprise level pricing environment, in accordance with some embodiments.
- Figure 2 is a simplified graphical representation of a price modeling environment where an embodiment of the present invention may be utilized
- Figure 3 is a simplified graphical representation of dataflow within a price modeling environment where an embodiment of the present invention may be utilized;
- Figure 4 is a flow chart illustrating a technique for quote generation, in accordance with some embodiments.
- Figure 5 is a schematic of a portfolio hierarchy, in accordance with some embodiments.
- Figure 6 is an example block diagram illustrating a system for brute force traversal of a transaction dataset and segment comparison, in accordance with some embodiments
- Figure 7 is a more detailed example block diagram illustrating the brute force traversal engine, in accordance with some embodiments.
- Figure 8 is a more detailed example block diagram illustrating the segment comparer, in accordance with some embodiments.
- Figure 9 is a flow chart illustrating an exemplary method for performing automated recoverable margin analysis, in accordance with some embodiments.
- Figure 10 is a flow chart illustrating an exemplary method for the step of brute force traversal of Figure 9;
- Figure 1 1 is a flow chart illustrating an exemplary method for the step of analyzing segment comparisons of Figure 9;
- Figures 12A and 12B are illustrative examples of characteristic hierarchical tree structures;
- Figure 13 is an illustrative example of a set of transaction records;
- Figure 14 is an illustrative example of the set of transaction records analyzed for percent margin and an applicable data dictionary
- Figures 15A and 15B are illustrative examples of the set of transaction records broken down by segment key
- Figure 16 is an illustrative example of a table of the segment keys and their accompanying statistics
- Figure 17 is an illustrative example of the segment keys and their accompanying statistics with ancestor listings
- Figure 18 is an illustrative example of the child and ancestor key
- Figure 19 is an illustrative example of the segment keys and their accompanying statistics with ancestor listings expanded out;
- Figure 20 is an illustrative example of each segment compared against its ancestor.
- Figures 21 A and 21B provide an illustration of a computer system capable of embodying the disclosed invention.
- Figure 1 is a simplified graphical representation of an enterprise pricing environment.
- databases 104-120 are illustrated to represent the various sources of working data. These might include, for example, Trade Promotion Management (TPM) 104, Accounts Receivable (AR) 108, Price Master (PM) 112, Inventory 116, and Sales Forecasts 120.
- the data in those repositories may be utilized on an ad hoc basis by Customer Relationship Management (CRM) 124, and Enterprise Resource Planning (ERP) 128 entities to produce and post sales transactions.
- CRM Customer Relationship Management
- ERP Enterprise Resource Planning
- the various connections 148 established between the repositories and the entities may supply information such as price lists as well as gather information such as invoices, rebates, freight, and cost information.
- Analysts 136 may benefit from the aggregated data from a data warehouse.
- an analyst 136 may compare average pricing across several regions within a desired temporal interval and then condense that analysis into a report to an executive committee 140.
- An executive committee 140 may then, in turn, develop policies directed toward price structuring based on the analysis returned from an analyst 136. Those policies may then be returned to CRM 124 and ERP 128 entities to guide pricing activities via some communication channel 152 as determined by a particular enterprise.
- FIG. 2 illustrates a simplified graphical representation of a closed-loop system.
- closed-loop systems are common in, for example, the mechanical and electromechanical arts.
- a closed-loop system is a control system in which the output is continuously modified by feedback from the environment.
- an input at a step 204 would be a feedback element.
- Inputs may be any desired indicator or metric that is measurable in some way.
- an input may be a temperature reading taken from a thermocouple sensor.
- the input is then analyzed at a step 208.
- Many types of analysis are available depending on the intended use. A simple comparison against a set value is one example. Another example might include advanced statistical analysis where appropriate.
- analysis in closed-loop systems may be highly complex.
- An output may be any operation that is intended to affect a condition of the desired system.
- a temperature may be read (e.g., input); compared against a set temperature (analysis); and affected by turning on or off a heating element depending on the comparison (output). Finally, the system loops back to the input and continues until the system, or a user terminates the process.
- Figure 3 is a simplified graphical representation of a closed-loop implementation of an embodiment of the present invention in a price modeling environment.
- data is input into a historical database.
- a historical database under the present invention may contain any of a number of inputs.
- a historical database may include sales transactions.
- a historical database may include waterfall records.
- the rebate represents a price adjustment to the retail price that affects the invoice price.
- Rebate may also be thought of as a "leakage" in that the profitability of a sale is indirectly proportional to the amount of leakage in a given system.
- metrics like rebates for example, that may affect the profitability of a transaction, may be stored at a transaction level in a historical database.
- Many waterfall records may exist for a transaction like, for example: industry adjustments, sales discretion, shipping charges, shipping allowances, late payment costs, extended terms costs, consignment costs, returns, packaging costs, base material costs, additive costs, processing costs, variable costs, shortfalls, overages, and the like.
- the analysis of the data may then automatically generate a transaction and policy database 308. For example, analysis of a selected group of transactions residing in a historical database may generate a policy that requires or suggests a rebate for any sale in a given region. In this example, some kind of logical conclusion or best guess forecast may have determined that a rebate in a given region tends to stimulate more and better sales. This policy is thus guided by historical sales transactions over a desired metric - in this case, sales by region. The policy may then be used to generate logic that will then generate a transaction item.
- policies are derived strictly from historical data.
- policies may be generated ad hoc in order to test effects on pricing based hypothetical scenarios.
- executive committee(s) 320 who implements policies, may manually enter any number of policies relevant to a going concern. In this manner, policies may be both automatically and manually generated and introduced into the system.
- sales invoices may be constrained to sales quotes generated by a transaction and policy database. That is, as an example, a sales quote formulated by a sales force 316 may require one or several levels of approval based on variance (or some other criteria) from policies stored in a transaction and policy database 308. In other embodiments, sales invoices are not constrained to sales quotes generated by a transaction and policy database.
- Another advantage to the system is that policy may flow directly from input data in an efficient manner. Individual spreadsheets and analysis typically used in price modeling may no longer be necessary. Instead, executive committees have access to real-time data that is continually updated to reflect current sales and sales practices. Response to a given policy may be seen or inferred directly from a historical database and implemented directly on a transaction and policy database. Thus, temporal efficiencies are achieved.
- a closed-loop system may be used to evaluate individual or grouped transactions as, for example, in a deal making context. That is, a salesperson may generate a quote for a given customer and submit that quote for comparison against a policy formulated transaction in a transaction and policy database. A comparison may reveal some basis upon which a quote may represent a profitable deal.
- a deal indicator may be generated.
- a deal indicator may be a ratio of the quote against a composite index that generates a value between 0 and 1 corresponding to profitability. In this example, a ratio returning unity (i.e., 1) indicates a deal is in conformance with established policy. It may be appreciated that a ratio may be defined in any of a number of manners without departing from the present invention.
- a deal suggestion may be generated.
- a deal suggestion may provide a range of acceptable (i.e., profitable) pricing based on quote parameters.
- a quote having deal specific set parameters like, for example, a fixed shipping price may return a range of allowable rebates or a range of allowable sales discretion that account for a fixed shipping input.
- deal guidance may be provided. Deal guidance provides non-numeric suggestion for a given quote. Thus, deal guidance might, for example, return "acceptable deal," or
- FIG. 4 is a flow chart of an embodiment of the present invention based on a closed-loop system.
- deal data may include any of a number of inputs like, for example, shipping costs, rebate, discounts, and the like.
- a deal quote may then be generated at a step 408 calculated from the deal data input at a step 404 and further including any missing field items based on policy considerations. Applicable policy is then read at a step 412.
- Applicable policy may be automatically selected or user selected by a particular metric. For example, policy may be utilized based on global metrics or may be delimited by region.
- a deal quote may then be compared against applicable policy at a step 416.
- a comparison may reveal some basis upon which a quote may represent a profitable deal. Comparisons are then returned for review by a user at a step 420.
- comparisons may include deal indicators, deal suggestions, and deal guidance.
- An advantage of returning a comparison is that a complex analysis may be reduced to a readily ascertainable form.
- a deal indicator may return a ratio; a deal suggestion may return an acceptable range of values; and deal guidance may return a non-numeric suggestion for a given deal.
- a deal maker may determine, at a glance, the acceptability based on policy of a given quote.
- a quote may be negotiated at a step 422 that may or may not incorporate any or all of those corresponding
- a salesperson negotiating a deal may flexibly structure a deal with confidence that the deal may be constrained to comparison parameters resulting in a profitable deal for an enterprise.
- entering a negotiated transaction initiates a recalculation of comparisons.
- a deal maker may view realtime changes to a deal structure as a deal is being formed. This feature is particularly useful in that final negotiating point parameters may be expanded or contracted as a deal progresses providing a deal maker with an increasingly better defined negotiating position.
- Approval in this context, may be coupled with a portfolio manager.
- a portfolio manager may be utilized in an embodiment of the present invention to efficiently expedite approval of pending deals.
- Approval may include one or more levels depending on variance from an explicit or implicit policy. That is, for a particular deal that greatly varies from a policy, higher authority must approve of that particular deal. For example, a deal offering a rebate that is within policy limits may not require approval while a similar deal offering a rebate that falls outside of policy limits by, for example, 25% may need a sales manager or higher approval.
- Approval may be linked upward requiring executive officer approval in some cases. Portfolio management will be discussed in further detail below for Figure 5.
- a deal must be approved at a step 428.
- the method then continues at a step 432 to generate a quote. If approval at a step 428 is not needed, the method continues at a step 432 to generate a quote.
- a quote may then be used to generate an invoice. However, an invoice may or may not match the quote upon which it is based. Rather, an invoice represents an actual sale. It is the data from an actual sale that continues to populate a historical database. The method then ends.
- a portfolio manager may efficiently expedite approval of pending deals.
- Enterprises as a practical reality, have a mix of "good” and "bad” deals - good deals being defined as profitable. Evaluating deals in isolation may not maximize profits at an enterprise level. For example, industries having large fixed costs may accept a number of high volume "bad” deals in order to capture a number of low volume "good” deals resulting in an overall profit. Industries evaluating deals in isolation may not realize this benefit and thus may not be able to survive.
- Portfolio organization therefore, assists, for example, sales managers maximize profitability for an enterprise by allowing those managers to view enterprise level effects of a deal or groups of deals.
- a customer price list item 504 exists at the root of the hierarchy as an item. Each item may be configured to require approval on a pending deal, or may be configured to ignore approval on a pending deal.
- the customer price list item 504 may contain any of a number of descriptive and/or numeric terms such as price, description, availability, etc., for example.
- customer price list items 504 may be grouped into a portfolio known as customer price list portfolio 512.
- Customer price list portfolios comprise customer price list items grouped according to a desired criteria or criterion. For example, price lists may be organized by cost, by type, by distributor, by region, by function, and by any other selected parameter. In this manner, approval, as an example, for a group of items - items under $1.00 for example - may be required or ignored. By grouping items, approval processes may be retained only for selected key products. In one embodiment, one or more criteria may be utilized to organize customer price list portfolio. It can further be appreciated that many other combinations of groupings for portfolios are possible. Thus, for example, a sales manager portfolio may comprise: customer price list items 504; customer price list portfolios 512; or account manager portfolios 520 as indicated by multiple arrows in FIG. 5.
- a customer price list portfolio 512 is a static portfolio. That is, a static portfolio does not change according to a formula or algorithm. Rather, a static portfolio is entered and modified manually. It may be appreciated that most, if not all, portfolios may either be static portfolios or dynamic portfolios.
- Customer price list portfolios 512 may then be organized to generate an account manager portfolio 520.
- Account manager portfolios 520 in this example, comprise customer price list portfolios 512 grouped according to a desired criteria or criterion.
- accounts may be organized by named companies or individuals.
- accounts may be organized by approval. That is, all approval accounts may be managed singly or in group thus facilitating policy implementation.
- an account portfolio may be organized such that any account having a 12-month history of on-time transactions no longer needs approval so that approval is ignored. In this way, an on-time account may accrue a benefit of an expedited approval thus making transactions more efficient for both the sales person and the account.
- an account manager portfolio is of the type - static portfolio. As noted above, a static portfolio does not automatically change according to a formula or algorithm.
- Account portfolios 520 may be further organized to generate sales manager portfolios 528.
- Sales manager portfolios 528 in this example, comprise account manager portfolios 520 grouped according to a desired criteria or criterion. Typically, sales manager portfolios may be organized by named individuals or groups of
- sales manager portfolios may be organized by approval. As noted above, approval based portfolios may be managed singly or in group thus facilitating policy implementation. For example, a sales manager portfolio may be organized such that sales people with seniority no longer need approval for deals under a capped amount. In this way, sales people with more experience benefit from an expedited approval process since presumably more experienced sales people have a deeper understanding of company policies and priorities. In addition, as new policy is generated, approvals may be reinstated as a training measure so that policies may more effectively be incorporated into a workflow. In this example, a sales manager portfolio 528 is of the type - dynamic portfolio. Dynamic portfolios may be generated according to formula or algorithm. For example, a sales manager portfolio may be generated for all sales associates whose total billing exceeds a desired dollar amount. In this way, managers may creatively and efficiently differentiate productive and unproductive sales associates and may further apply varying levels of approval.
- the brute force traversal methodology dispenses with single or clustered analysis and examines the entire space of all segments. It analyzes them all, thus finding any and all interesting segments for actionable policy change. Additionally, it can compare segments that are related, resulting in an even more powerful analysis to describe outliers and root causes of discovered behaviors. I n some embodiments, brute force traversal does not actually traverse the entire inordinately large space, but rather only the locations within that space that contain data. The rest is empty and is of no interest. This insures that all possible segments are analyzed without traveling to segments of no interest. [00068] In this example block diagram, a set of inputs 602 are provided to the various analyzers and the brute force traversal engine 612.
- the inputs 602 includes transaction data 604, waterfall data 606 and descriptive data 608.
- Transaction data provides a record of a history of transactions between a company and its customers.
- a transaction pricemart provides this data broken down with a waterfall detail and annotated with the characteristics of each sale.
- the characteristics of each sale are dimensional in nature, where each individual characteristic has a unique set of enumerated values, from which a single value will annotate any specific transaction for that characteristic. Examples of these characteristics might include Product, Customer, SalesRep, Region, etc. Some of these characteristics may form hierarchical
- the inputs 602 may be utilized to perform three types of analysis: 1) simple transactional analysis, whose results can be derived from no input other than that available in a single transaction, 2) intra-transactional analysis whose results can be derived from no input other than that available in a single segment and 3) inter- transactional analysis is one whose results are derived through a comparison of two segments.
- segment inter-transactional and intra- transactional analysis requires segmentation prior to completion.
- a "segment" shall be defined as a group of transactions that have been gathered together because of common values among a subset of a transactions dimensions.
- the segments are generated by the brute force traversal engine 612 (as will be discussed in detail below), and the analysis on these segments is completed by the intra-transactional analyzer 610 and the brute force traversal engine 612 for inter- transactional analysis, respectively.
- Segment generation and analysis may also rely upon a data dictionary 616, which defines the dimensions of the input data and their hierarchical relationships.
- the number of independent dimensions and hierarchical dimensions defines the number of ways in which the data can be segmented, or in terms of a more database driven lexicon, grouped-by. Therefore the total number of segments that can be generated is dependent on the number of different ways the transactions can be grouped and the number of groups formed by each grouping.
- the result of the analysis may form a set of raw analytics 620, which by themselves may identify revenue generating opportunities. Further, these raw analytics 620 may be leveraged by a segment comparer 622 to generate segment comparisons 624 for further opportunity identification.
- Figure 7 is a more detailed example block diagram illustrating the brute force traversal engine 612.
- This engine is seen as consisting of a set of subsystems, each in communication with one another. These subsystems include a transaction grouper 712, a bulk statistics generator 714, a parent identifier 716, an opportunity identifier 718, and a priori estimator 720.
- the transaction grouper 712 initially groups transactions by common characteristics, while the bulk statistics generator 714 generates segment statistics as the transactions are added to the segment grouping.
- Parents of the segment are identified by the parent identifier 716 by leveraging the data dictionary 616.
- the priori estimator 720 generates an estimate of Time to First Result (TTFR) and Time to Last Result (TTLR).
- FIG. 8 is a more detailed example block diagram illustrating the segment comparer 622, in accordance with some embodiments.
- This module includes three subsystems, including a set of filters 812, a graph theory engine 814, and a social networking technique module 816.
- This system enables the filtering of the raw analytics 620 to prune down the dataset to a reasonable base date set. This is then graphed using graph theory to connect the outputs. This provides a first order classification of segments into non-overlapping spaces. However, it is hard to describe these graphs in a meaningful way, as they are comprised of chains of related segments.
- the second pass then utilizes approaches found in Social Networking to find a central node to each graph and examine the most profitable comparisons connected to that node to describe the opportunity discovered in that graph. The output of the system is thus segment comparisons 624.
- Figure 9 provides a flow chart 900 illustrating an exemplary method for performing automated recoverable margin analysis, in accordance with some embodiments.
- the segments are first segmented via brute force traversal (at 910) in a process described in Figure 10. This includes receiving data inputs (at 1002) for transactions, waterfalls and descriptive inputs. Often the inputs are arranged in a tabular data structure with each row being a transaction, and each column are one of the data types (i.e., transaction, waterfall or descriptive). Transactional data includes such data as transaction ids and dates specific to identify the transaction.
- Waterfall data describes a breakdown of the revenue generated by the transaction. It breaks down the revenue, costs and marginal difference between them. Columns containing descriptive data can each be thought of as a dimension, whose value annotates the transaction, identifying where it falls in a multi-dimensional space of the business done by the company. Examples of descriptive data would be the Customer, Region, Sales Rep, and Product. This data is mostly nominal, in that the value for each dimension can come from a list of distinct non-numeric values. Sometimes the data can be continuous real numbers as well, such as quantity.
- the input data may then be manipulated (at 1004) to remove errors and correct inconsistencies. Additionally, it is often desirable to perform calculations or transformations in order for the input data to be readily consumable for downstream analysis. Examples of these transformation include calculating margin percentages for each transaction, adding year and quarter data, and the like.
- the data dictionary may be utilized to describe the dimensions in the input data, as well as formulate the data's hierarchical arrangement (at 1006).
- the dimensions of descriptive data are not all expected to be orthogonal. Often, groups of 3-10 columns will represent a dimensional hierarchy. For example, three columns containing data for Country, State, City might form a region hierarchy. If the data adheres to this hierarchy cleanly, it might form a tree like that illustrated in Figure 12A. Unfortunately, the data for columns in a dimensional hierarchy do not always form a proper hierarchical tree. Often, some elements of a child dimension will have more than one associated parent element. This is called a broken hierarchy. There are two typical causes for broken hierarchies. Inconsistent nominal element values are quite common. Due to possible inconsistent spelling, or data coming from disparate systems, the same conceptual value can have more than one nominal value.
- Figure 12B is an example of a hierarchy where New York State is represented by both NY and New York in the data.
- next step is to generate all possible ways of grouping transactions (at 1008). This formulation of groupings is done based upon the
- a segment key system is developed (at 1010) which identifies the different segments.
- the transactions are then segmented according to the key system (at 1012).
- a map can be set up associating each group of transactions with the unique dimensional values defining that group.
- the unique set of dimensional values defining that group is called the group key.
- the process may be applying statistical analysis of the segment. For example the percent margin the segment may be calculated, and with each transaction that is added to the segment, the percent margin value may be updated accordingly.
- the range across which the bulk of the transactions lay is determined, in terms of the decision variable.
- the bulk is defined as a provided percentage of the transactions.
- This analysis results in a range statistic for each group that includes the maximum and minimum and a threshold of the decision variable for that bulk of transactions from the group.
- the threshold may be the mean of the segment statistic.
- each group has a distinct ancestry of larger groups that fully include the transactions in that group.
- the unique ancestry is generated for each group, which takes the form of a list of group keys. The list may be associated with the group key for which it is an ancestor.
- the range of each group is then compared to the decision variable threshold for the ancestors. If the ancestor threshold is above the maximum decision variable range for the segment, then an outlier may be identified. Likewise, if an ancestor threshold is above the minimum decision variable range for the segment, then there may be room for improving the decision variable value within the segment. After these outliers are identified, the process returns to Figure 9, where the simple transaction analysis, intra-transaction analysis, and inter-transaction analysis is completed (at 920).
- segment outputs are filtered and pruned down to a reasonable base date set (at 1102).
- Graph theory is then applied generate separate graphs of connected segments (at 1104). This provides a first order classification of segments into non-overlapping spaces.
- social networking techniques may be applied to the graphs to identify a central node of each graph (at 1106). The system then analyzes for the most profitable comparisons connected to that node to describe the opportunity discovered in that graph (at 1108). This ends the opportunity identifying process.
- An initial data set is provided which includes transactions and associated data with each transactions. Errors may be corrected (such as negative volumes, nonsensical descriptors and the like). Additionally, the data may be manipulated/transformed to include desired metrics (such as the calculation of percent margins).
- Figure 13 is an illustrative example of a set of transaction records 1300. Each transaction includes an ID, and item type, a country, region and a calculated margin percentage. In this example, an inter-transactional analysis of percent margin shall be illustrated. The results of the analysis is a rank ordered list of comparisons between statistics between related segments.
- comparison between the child segment and its parent can produce an understanding of how that segment is performing within the larger group. Comparing margin percentage for the Hammer, US segment against the Hammer segment indicates how sales in the US compare to sales worldwide. Doing the same between the Hammer, US segment and the US segment indicates how within the US sales of Hammers compare against all tools.
- Figure 14 is an illustrative example of the set of transaction records analyzed for percent margin and an applicable data dictionary shown at 1400.
- the data dictionary identifies the dimensions, the columns of the dimensions, the hierarchy relationships between the dimensions and the column index of the decision variable.
- the data dictionary indicates there is only one hierarchy relationship between the dimensions. This is a hierarchy between column 3 (Country) and column 4 (Region). Since column 4 comes after column 3 in the list, it indicates that Region is subordinate to Country in the hierarchy. In general, there can be many hierarchies and many levels in each hierarchy.
- the required columns is a list of columns and/or hierarchies that must be included in every grouping. Some analyses do not make sense across different dimensions. A Margin Percentage analysis often does not make sense across more than one product or product family. For that reason, the comparisons can be limited by indicating the upper bounds on certain dimensions. What this means in a practical sense, is that every segment being compared, in this example, will include a value from column 2 (Item).
- the analysis phase calculates a set of statistics for each segment. For the purpose of this example, we will find the length of each segment along with the 50th and 90th percentiles of the Margin% for the segment.
- Figure 16 is a table of the results of that analysis, shown at 1600.
- the ancestors illustrated in Figure 17 are not complete, however.
- the table does not include the ancestors of segments as a result of one or more of their elemental dimensions participating in a hierarchy. For instance, ⁇ ⁇ 2, Hammer ⁇ , ⁇ 4, NY ⁇ ⁇ above should have ⁇ ⁇ 2, Hammer ⁇ , ⁇ 3, US ⁇ ⁇ as an ancestor, and does not. It requires analysis of both the dimensional hierarchies, and the data itself, to determine these ancestors; for example, to know that ⁇ 3, US ⁇ is an ancestor of ⁇ 4, NY ⁇ . To accomplish this all possible elemental value hierarchies from the data are generated, as seen in Figure 18 at 1800. Next these elemental key value hierarchies are applied to the data to expand the ancestors to form a complete set, as seen in Figure 19, at 1900.
- each segment may be compared to the ancestor segment's statistics.
- the comparison of interest in these examples is the 90 th percentile of the margin percentage for the segment, and the 50 th percentile of the margin percentage for the ancestor segment.
- Figure 20 is an illustrative example of each segment compared against its ancestor, shown at 2000.
- Figures 21A and 21B illustrate a Computer System 2100, which is suitable for implementing embodiments of the present invention.
- Figure 21 A shows one possible physical form of the Computer System 2100.
- the Computer System 2100 may have many physical forms ranging from a printed circuit board, an integrated circuit, and a small handheld device up to a huge super computer.
- Computer system 2100 may include a Monitor 2102, a Display 2104, a Housing 2106, a Disk Drive 2108, a Keyboard 2110, and a Mouse 2112.
- Disk 2114 is a computer-readable medium used to transfer data to and from Computer System 2100.
- FIG. 2 IB is an example of a block diagram for Computer System 2100. Attached to System Bus 2120 are a wide variety of subsystems.
- Processor(s) 2122 also referred to as central processing units, or CPUs
- Memory 2124 includes random access memory (RAM) and read-only memory (ROM).
- RAM random access memory
- ROM read-only memory
- RAM random access memory
- ROM read-only memory
- Both of these types of memories may include any suitable of the computer-readable media described below.
- a Fixed Disk 2126 may also be coupled bi-directionally to the Processor 2122; it provides additional data storage capacity and may also include any of the computer-readable media described below.
- Fixed Disk 2126 may be used to store programs, data, and the like and is typically a secondary storage medium (such as a hard disk) that is slower than primary storage. It will be appreciated that the information retained within Fixed Disk 2126 may, in appropriate cases, be incorporated in standard fashion as virtual memory in Memory 2124.
- Removable Disk 2114 may take the form of any of the computer-readable media described below.
- Processor 2122 is also coupled to a variety of input/output devices, such as Display 2104, Keyboard 2110, Mouse 2112 and Speakers 2130.
- an input/output device may be any of: video displays, track balls, mice, keyboards, microphones, touch-sensitive displays, transducer card readers, magnetic or paper tape readers, tablets, styluses, voice or handwriting recognizers, biometrics readers, motion sensors, brain wave readers, or other computers.
- Processor 2122 optionally may be coupled to another computer or telecommunications network using Network Interface 2140. With such a Network Interface 2140, it is contemplated that the Processor 2122 might receive information from the network, or might output information to the network in the course of performing the above-described multi-merchant tokenization.
- method embodiments of the present invention may execute solely upon Processor 2122 or may execute over a network such as the Internet in conjunction with a remote CPU that shares a portion of the processing.
- embodiments of the present invention further relate to computer storage products with a computer-readable medium that have computer code thereon for performing various computer-implemented operations.
- the media and computer code may be those specially designed and constructed for the purposes of the present invention, or they may be of the kind well known and available to those having skill in the computer software arts.
- Examples of computer-readable media include, but are not limited to: magnetic media such as hard disks, floppy disks, and magnetic tape; optical media such as CD-ROMs and holographic devices; magneto-optical media such as floptical disks; and hardware devices that are specially configured to store and execute program code, such as application-specific integrated circuits (ASICs), programmable logic devices (PLDs) and ROM and RAM devices.
- Examples of computer code include machine code, such as produced by a compiler, and files containing higher level code that are executed by a computer using an interpreter.
Abstract
Description
Claims
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/946,995 US20140025435A1 (en) | 2004-05-28 | 2013-07-19 | System and Methods for Brute Force Traversal |
US13/947,002 US20140025431A1 (en) | 2004-05-28 | 2013-07-19 | System and Methods for Comparing Segments |
PCT/US2014/047333 WO2015010112A1 (en) | 2013-07-19 | 2014-07-19 | System and methods for brute force traversal and comparing segments |
Publications (2)
Publication Number | Publication Date |
---|---|
EP3022704A1 true EP3022704A1 (en) | 2016-05-25 |
EP3022704A4 EP3022704A4 (en) | 2016-12-28 |
Family
ID=52346778
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP14826696.8A Withdrawn EP3022704A4 (en) | 2013-07-19 | 2014-07-19 | System and methods for brute force traversal and comparing segments |
Country Status (2)
Country | Link |
---|---|
EP (1) | EP3022704A4 (en) |
WO (1) | WO2015010112A1 (en) |
Family Cites Families (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7912793B1 (en) * | 2005-01-13 | 2011-03-22 | Imvu, Inc. | Computer-implemented method and apparatus to allocate revenue from a derived avatar component |
US8301487B2 (en) * | 2006-05-02 | 2012-10-30 | Vendavo, Inc. | System and methods for calibrating pricing power and risk scores |
US20110161159A1 (en) * | 2009-12-28 | 2011-06-30 | Tekiela Robert S | Systems and methods for influencing marketing campaigns |
US8392316B2 (en) * | 2008-12-26 | 2013-03-05 | Money Square Japan Inc. | Transaction management device and readable storage medium |
US20120303412A1 (en) * | 2010-11-24 | 2012-11-29 | Oren Etzioni | Price and model prediction system and method |
-
2014
- 2014-07-19 WO PCT/US2014/047333 patent/WO2015010112A1/en active Application Filing
- 2014-07-19 EP EP14826696.8A patent/EP3022704A4/en not_active Withdrawn
Also Published As
Publication number | Publication date |
---|---|
WO2015010112A1 (en) | 2015-01-22 |
EP3022704A4 (en) | 2016-12-28 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7360697B1 (en) | Methods and systems for making pricing decisions in a price management system | |
Curtis et al. | Business information systems: Analysis, design and practice | |
Silva et al. | Association rules extraction for customer segmentation in the SMEs sector using the apriori algorithm | |
US20050278227A1 (en) | Systems and methods of managing price modeling data through closed-loop analytics | |
US7873567B2 (en) | Value and risk management system | |
US20130339095A1 (en) | System and method for organizing price modeling data using hierarchically organized portfolios | |
US20140214492A1 (en) | Systems and methods for price point analysis | |
US20050251468A1 (en) | Process management system | |
de Murillas et al. | Case notion discovery and recommendation: automated event log building on databases | |
US20150120370A1 (en) | Advanced planning in a rapidly changing high technology electronics and computer industry through massively parallel processing of data using a distributed computing environment | |
US20080195431A1 (en) | System and method for correlating business transformation metrics with sustained business performance | |
EP3876177A1 (en) | System and method for retail price optimization | |
US20180101814A1 (en) | Dynamic supply chain management systems and methods | |
Goar et al. | Business decision making by big data analytics | |
US20140025435A1 (en) | System and Methods for Brute Force Traversal | |
Bai et al. | Performance measurement and evaluation for sustainable supply chains using rough set and data envelopment analysis | |
Chiang et al. | The cyclic model analysis on sequential patterns | |
US20140025434A1 (en) | System and Methods for Measuring Effectiveness for Strategic Mass Price Change | |
US20140025431A1 (en) | System and Methods for Comparing Segments | |
US20140214493A1 (en) | Systems and methods for waterfall adjustment analysis | |
US20150120371A1 (en) | Automotive manufacturing optimization through advanced planning and forecasting through massively parallel processing of data using a distributed computing environment | |
US20140149186A1 (en) | Method and system of using artifacts to identify elements of a component business model | |
EP3022704A1 (en) | System and methods for brute force traversal and comparing segments | |
US20050055194A1 (en) | Migration model | |
Antonelli et al. | Introducing collaborative practices in small medium enterprises |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
17P | Request for examination filed |
Effective date: 20160217 |
|
AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
AX | Request for extension of the european patent |
Extension state: BA ME |
|
DAX | Request for extension of the european patent (deleted) | ||
A4 | Supplementary search report drawn up and despatched |
Effective date: 20161124 |
|
RIC1 | Information provided on ipc code assigned before grant |
Ipc: G06Q 30/02 20120101AFI20161118BHEP |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN |
|
18D | Application deemed to be withdrawn |
Effective date: 20170624 |