US20020178167A1 - System and method for allocating data in a hierarchical organization of data - Google Patents
System and method for allocating data in a hierarchical organization of data Download PDFInfo
- Publication number
- US20020178167A1 US20020178167A1 US09/825,083 US82508301A US2002178167A1 US 20020178167 A1 US20020178167 A1 US 20020178167A1 US 82508301 A US82508301 A US 82508301A US 2002178167 A1 US2002178167 A1 US 2002178167A1
- Authority
- US
- United States
- Prior art keywords
- children
- child
- data
- overscore
- values
- 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.)
- Granted
Links
Images
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
- G06Q10/00—Administration; Management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/28—Databases characterised by their database models, e.g. relational or object models
- G06F16/283—Multi-dimensional databases or data warehouses, e.g. MOLAP or ROLAP
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99941—Database schema or data structure
- Y10S707/99944—Object-oriented database structure
- Y10S707/99945—Object-oriented database structure processing
Definitions
- This invention relates to the field of data allocation, and more particularly to a system and method for allocating data in a hierarchical organization of data.
- Data for products may often be dependent in some manner on data for other hierarchically related products. For example, demand for a product with multiple components may drive the demand for a particular one of those components. Similarly, demand for products in a particular geographic region may drive the demand for the products in a particular territory in the region. Because of these hierarchical dependencies, the data concerning various products or other items may be stored hierarchically in data storage or derived in a hierarchical fashion.
- the data may be stored at a storage location associated with multiple dimensions, such as a product dimension (the storage location being associated with a particular product or product component), a geography dimension (the storage location being associated with a particular geographical area), and a time dimension (the storage location being associated with a particular time or time period).
- a product dimension the storage location being associated with a particular product or product component
- a geography dimension the storage location being associated with a particular geographical area
- a time dimension the storage location being associated with a particular time or time period
- the demand value for the product in the particular state may be used to determine other hierarchically related demand values using allocation techniques. For example, the forecasted demand value may be allocated by aggregating it with demand values for the product in other states in the country to determine a demand value for the product in the entire country.
- the demand value may be allocated by disaggregating it to determine a demand value for the product in each of the regions of the state.
- many current allocation methods do not provide a sufficiently accurate allocation of forecasted values and thus negatively affect demand planning, supply planning, or other planning based on the allocated values.
- a method for allocating data in a hierarchical organization of data includes determining new values for one or more parents in the organization of data and determining current values for one or more children in the organization of data. Each child is hierarchically related to one or more of the parents. The method also includes determining the relationship between each parent and its children and determining a variation for each child. Furthermore, the method includes determining a new value for each child by allocating the new values of the parents to the children based on the parent-child relationships, the current values of the children, and the variations of the children.
- the present invention provides a number of important technical advantages. Unlike previous data allocation techniques, embodiments of the present invention account for the variance of data values associated with a storage location in a hierarchical database or other organization of data when allocating a value to that storage location based on the forecasted value of a hierarchically related storage location. Therefore, the present invention provides a more accurate allocation than previous techniques. Furthermore, embodiments of the present invention also take into account multi-dimensional relationships between storage locations in a multi-dimensional hierarchical organization of data when allocating forecasted values. In addition, embodiments of the present invention typically do not require complex computations to perform such allocations. Other important technical advantages are readily apparent to those skilled in the art from the following figures, descriptions, and claims.
- FIG. 1 illustrates an exemplary system for allocating data in a hierarchical organization of data
- FIG. 2 illustrates an exemplary product dimension within a multi-dimensional organization of data
- FIG. 3 illustrates an exemplary geography dimension within a multi-dimensional organization of data
- FIG. 4 illustrates an exemplary method for allocating data within a business or other planning environment
- FIG. 5 illustrates an exemplary allocation of a forecasted value associated with a single parent in one dimension
- FIG. 6 illustrates an exemplary allocation of forecasted values associated with multiple parents associated with multiple dimensions.
- FIG. 1 illustrates an exemplary system 10 for allocating data, such as forecasted data, in a hierarchical organization of data associated with a business or other planning environment.
- system 10 implements an allocation strategy that may be used to allocate a value associated with a particular data member in a data storage device or in a representation of data to hierarchically related data members.
- forecasted data provides an estimate of the forecasted demand, available supply, selling price, or other quantifiable data measure associated with a particular product or other item.
- products are typically referred to throughout this application, the present invention contemplates system 10 allocating forecast data for appropriate tangible or non-tangible items other than products, including but not limited to services or other benefits.
- forecasts are primarily discussed herein, the present invention is similarly applicable to allocating historical or other data, separately or in combination with forecast data, according to particular planning needs of an enterprise, facility, or user.
- present invention is described primarily in connection with allocating demand forecasts for products, those skilled in the art will appreciate that the present invention is similarly applicable to allocating forecasts for available supply, selling price, and any other suitable data.
- System 10 includes client 12 , server 14 , and data storage 16 .
- Client 12 may include one or more processes to provide appropriate administration, analysis, and planning input. Although these processes are preferably separate processes running on a dedicated client processor, the present invention contemplates these processes being integrated, in whole or in part, and running on one or more processors within the same or different computers.
- the server 14 may include one or more processes to receive administration, analysis, and planning input from client 12 and interact with data storage 16 to provide corresponding output to client 12 . Although the processes are preferably separate processes running on a dedicated server processor, the present invention contemplates these processes being integrated, in whole or in part, and running on one or more processors within the same or different computers.
- Client 12 and server 14 may be fully autonomous or may operate at least in part subject to input from users of system 10 .
- Data storage 16 is used to refer to any appropriate data source, representation of data, or other organization of data.
- Data storage 16 may be hierarchical in nature, may be multi-dimensional, and/or may provide persistent data storage for system 10 .
- data storage 16 may be a multi-dimensional database that stores data in a hierarchical and multidimensional format or data storage 16 may be a representation of data derived by server 12 or other appropriate component from data stored in a relational database, in memory, or in any other appropriate location.
- Server 12 or other appropriate component may use a multi-dimensional hierarchical transformation layer to create such a representation of the data.
- data storage 16 includes three-dimensional data and, for each data measure, associates with each storage location 18 a particular member from the product dimension, a particular member from the geography dimension, and a particular member from the time dimension.
- Each of these particular combinations of members of these three dimensions is associated with a corresponding storage location 18 in data storage 16 , similar to each combination of coordinates from the x, y, and z axes being associated with a point in three-dimensional Euclidian space.
- position within a particular dimension may be changed independent of members of other dimensions, much like the position of a coordinate along the x axis may be changed independent of the positions of other coordinates along the y and z axes in three-dimensional Euclidian space.
- the present invention contemplates data storage 16 having as few or as many dimensions as appropriate for the particular application.
- an enterprise associated with system 10 may not consider geography in connection with its data forecasting needs. This might be the case when products are ordered using the Internet or the telephone and then distributed from a single distribution point.
- data storage 16 might be two-dimensional rather than three-dimensional and might not reflect positions or members within the geography dimension.
- the demand or other data might be quantified per specified time interval, in which case data storage 16 might be two-dimensional and might not reflect positions or members within the time dimension.
- Other possible scenarios involving more or fewer than three dimensions will be apparent to those skilled in the art.
- the present invention contemplates data storage 16 having any number of dimensions appropriate for the needs of the enterprise or facility associated with system 10 .
- the values of the data measures within the set for a particular storage location 18 depend on the combined positions of members within product, geography, and time dimensions for that storage location 18 .
- the values of the data measures typically vary with these combined positions as appropriate to accurately reflect the demand, available supply, selling price, or other data associated with these members.
- data storage 16 accesses the data measures for storage location 18 associated with that combination of members to assist system 10 in allocating demand forecasts or other suitable data.
- the present invention contemplates other suitable dimensions to replace or be combined with the product, geography, and time dimensions according to particular needs.
- data storage 16 supports multi-dimensional on-line analytical processing (OLAP) capability and is populated with data measures received from one or more transactional data sources that are internal, external, or both internal and external to the enterprise or facility associated with system 10 .
- data measures received from sources internal to a manufacturing or warehousing. facility may include unit shipping data, dollar shipping data, inventory data, pricing data, and any other suitable information applicable to demand forecasting.
- Data measures received from external sources, such as from syndicated partners of the enterprise or facility may include point-of-sale demographic data and any other suitable information.
- the present invention contemplates appropriate data measures being stored in data storage 16 in any suitable manner.
- Server 12 is coupled to data storage 16 using link 32 , which may be any wireline, wireless, or other link suitable to support data communications between server 12 and data storage 16 during operation of system 10 .
- Data storage 16 may be integral to or separate from server 12 , may operate on one or more computers, and may store any information suitable to support the operation of system 10 in allocating demand forecasts or other data.
- Server 12 is coupled to client 14 using link 30 , which may be any wireline, wireless, or other link suitable to support communications between server 12 , client 14 , and the processes of server 12 and client 14 during operation of system 10 .
- link 30 is shown as generally coupling server 12 to client 14 , processes of server 12 may communicate directly with one or more corresponding processes of client 14 .
- System 10 may operate on one or more computers 20 that are integral to or separate from the hardware and software that support server 12 , client 14 , and data storage 16 .
- Computer 20 may include a suitable input device 22 , such as a keypad, mouse, touch screen, microphone, or other device to input information.
- An output device 24 may convey information associated with the operation of system 10 , including digital or analog data, visual information, or audio information.
- Computer 20 may include fixed or removable storage media, such as magnetic computer disks, CD-ROM, or other suitable media to receive output from and provide input to system 10 .
- Computer 30 may include one or more processors 26 and associated memory to execute instructions and manipulate information according to the operation of system 10 .
- server 12 may each operate on separate computers 20 or may operate on one or more shared computers 20 without departing from the intended scope of the present invention.
- Each of the one or more computers 20 may be a work station, personal computer (PC), network computer, personal digital assistant (PDA), wireless data port, or any other suitable computing device.
- PC personal computer
- PDA personal digital assistant
- FIG. 2 illustrates an exemplary product dimension 50 within data storage 16 that includes a hierarchy of product levels 52 each having one or more members 54 .
- the value of each data measure associated with a member 54 is an aggregation of the values of corresponding data measures associated with hierarchically related members 54 in lower levels 52 of product dimension 50 .
- the demand associated with a member 54 is the aggregate demand for these hierarchically related members 54 in lower levels 52 of product dimension 50 .
- product levels 52 for product dimension 50 include an all products level 58 , a product type level 60 , a product category level 62 , and a product family level 64 .
- Links 56 between hierarchically related members 54 in adjacent levels 52 of product dimension 50 reflect parent-child relationships between members 54 .
- FIG. 2 is described primarily in connection with demand relationships, the following description is similarly applicable to other data relationships, such as available supply, selling price, or any other relationships relating to data measures associated with an item or set of items.
- all products level 58 contains “All” member 54 representing the aggregate demand for all members 54 in lower levels 60 , 62 , and 64 of product dimension 50 .
- Product type level 60 contains “Components,” “Base Units,” and “Options” members 54 .
- “Components” member 54 represents the aggregate demand for hierarchically related members 54 below “Components” member 54 in levels 62 and 64 of product dimension 50 .
- “Base Units” member 54 represents the aggregate demand for hierarchically related members 54 below “Base Units” member 54 and “Options” member 54 represents the aggregate demand for hierarchically related members 54 below “Options” member 54 .
- Links 56 between “All” member 54 and “Components,” “Base Units,” and “Options” members 54 indicate the hierarchical relationships between these members 54 .
- Product category level 62 contains, under “Components” member 54 , “Hard Drives,” “Memory Boards,” and “CPUs” members 54 .
- “Hard Drives” member 54 represents the aggregate demand for hierarchically related members 54 below “Hard Drives” member 54 in level 64 of product dimension 50 .
- “Memory Boards” member 54 represents aggregate demand for hierarchically related members 54 below “Memory Boards” member 54 and “CPUs” member 54 represents the aggregate demand for hierarchically related members 54 below “CPUs” member 54 .
- Links 56 between “Components” member 54 and “Hard Drives,” “Memory Boards,” and “CPUs” members 54 indicate the hierarchical relationships between these members 54 .
- Analogous links 56 reflect hierarchical relationships between “Base Units” and “Options” members 54 of product type level 60 and corresponding members 54 in lower levels 62 and 64 within product dimension 50 .
- Product family level 64 contains, under “Hard Drives” member 54 , “4 GB” and “6 GB” members 54 .
- Links 56 between “Hard Drives” member 54 and “4 GB” and “6 GB” members 54 indicate hierarchical relationships between these members 54 .
- Analogous links 56 reflect hierarchical relationships between “Memory Boards,” “CPUs,” “Servers,” “Desktops,” “Laptops,” “Monitors,” “Keyboards,” and “Printers” members 54 of product category level 62 and corresponding members 54 in lower level 64 within product dimension 50 .
- links 56 are shown between members 54 in product family level 64 and possible lower levels 52 , the present invention contemplates such further levels 52 existing within product dimension 50 and analogous links 56 to reflect the corresponding hierarchical relationships.
- members 54 shown in FIG. 2 are exemplary only and are not intended to be an exhaustive set of all possible members 54 . Those skilled in the art will appreciate that other suitable members 54 and associated links 56 may exist without departing from the intended scope of the present invention.
- FIG. 3 illustrates an exemplary geography dimension 70 within data storage 16 that includes a hierarchy of geography levels 72 each having one or more members 74 .
- the value of each data measure associated with a member 74 is an aggregation of the values of corresponding data measures associated with hierarchically related members 74 in lower levels 72 of geography dimension 70 .
- the demand associated with a member 74 is the aggregate demand for these hierarchically related members 74 .
- geography levels 72 for geography dimension 70 include a world level 78 , a country level 80 , a region level 82 , and a district level 84 .
- links 76 are analogous to links 56 described above with reference to FIG. 2.
- FIG. 3 is described primarily in connection with demand relationships, the following description is similarly applicable to other data relationships, such as available supply, selling price, or any other relationships relating to one or more data measures associated with an item or set of items.
- world level 78 contains “World” member 74 representing aggregate worldwide demand.
- Country level 80 contains “U.S.” and “Canada” members 74 , which represent aggregate demand for the United States and Canada, respectively.
- Link 76 between “U.S.” members 74 in country level 80 and “World” members 74 in world level 78 indicates a hierarchical relationship between these members 74 .
- link 76 between “Canada” member 74 and “World” member 74 indicates a hierarchical relationship between these members 74 .
- worldwide demand is an aggregation of aggregate demand in the United States as well as aggregate demand in Canada.
- links 76 are analogous to links 56 described above with reference to FIG. 2 in that each represents a corresponding hierarchical relationship between members 74 in the various levels 72 of geography dimension 70 .
- the present invention contemplates eliminating or otherwise not considering the geography dimension 70 in allocating data, for example, if geography dimension 70 is not relevant to particular data forecasting needs. Data storage 16 might in this situation be two-dimensional.
- Demand or other forecasts may be derived using traditional forecasting techniques and suitable information concerning products, geographic areas, customers, and/or other data dimension. Such information may include historical sales, causal factors, key account input, market intelligence, and the like. Forecasting techniques may rely on hierarchical relationships between members 54 , 74 to allocate data forecasts for products corresponding to members 54 , 74 . As described above, the data measures associated with each member 54 , 74 are an aggregation of the data measures associated with some or all members 54 , 74 in lower levels 52 , 72 within the same hierarchy of parent-child links 56 , 76 .
- the forecasts for each of the related members 54 in the next lowest level 52 , 72 may be determined by disaggregating the forecast data for the parent between the children.
- parent and children are used above to identify a relationship between members 54 , 74 of a single dimension 50 , 70 , these terms may also be used to refer to the relationship between data measures or values associated with a storage location 18 associated with a member from each of a number of dimensions.
- a storage location 18 that includes a demand value for a particular product in a particular state may be hierarchically related to a storage location 18 that includes a demand value for the product in a city of that state (the value associated with the former storage location 18 being a parent of the value associated with the latter storage location 18 ).
- a “top-down” proportional allocation strategy is often used.
- the value of the forecast (such as a demand forecast) associated with a parent is divided proportionally among its children according to the relative current values (such as current demand values) associated with the children. Therefore, using such proportional allocation, children having larger values get a larger share of the number being allocated and children having smaller values get a proportionately smaller share.
- a parent with a forecasted demand of 1800 units has a first child that currently has an associated demand of 1000 units and a second child that currently has an associated demand of 500 units, then 1200 units of the forecasted demand would be allocated to the first child and 600 units of the forecasted demand would be allocated to the second child.
- Top-down allocation may be used for many reasons. For example, forecasts that are estimated at a higher level 52 , 72 often are more accurate and a forecast planner may want to keep those values intact and adjust the forecasts at the lower levels 52 , 72 to agree with the higher level forecast. Alternatively, the forecasts at a high level 52 , 72 may be specified, such as objectives and targets, and the lower level forecasts are adjusted to achieve the target forecast at the higher level 52 , 72 . However, proportional allocation is often too restrictive and may adversely affect the accuracy of the forecast values determined for children in the lower level 52 , 72 .
- a scenario where proportional allocation may create inaccurate forecasts is when the value associated with a child to which an estimated forecast is to be allocated has a relatively high variance (for example, the value varies widely over time).
- a proportional allocation based on the current value associated with the child may be skewed by a temporary fluctuation in the value.
- Embodiments of the present invention provide an allocation strategy that accounts for variance in the values associated with children when allocating a forecasted value from a parent of the children. Furthermore, it is possible for the values of the children to have positive or negative relationships between themselves, so that a higher value associated with one child may have a correspondence with a higher or lower value associated with another child. The allocation strategy of the present invention may also account for these relations.
- a distance measure may be defined as follows in order to take into account the variance and correspondence between children when allocating a forecast:
- ⁇ overscore (x) ⁇ is the vector of current values (such as demand values) associated with the children of a particular parent.
- ⁇ is the variation matrix that identifies the variation of each child ( ⁇ ⁇ 1 being the inverse of the variance matrix).
- the variation of a particular child may be expressed as a standard deviation, variance, or any other suitable measure and may be determined using statistical equations, models, or any other appropriate technique.
- ⁇ overscore (x) ⁇ ′ is the vector of the values associated with the children after the allocation of the forecast from the parent. To optimally allocate the forecast, the selection of the values of ⁇ overscore (x) ⁇ ′ should minimize the distance d.
- the determination of ⁇ overscore (x) ⁇ ′ may be subject to the constraint of the parent-child relationships.
- parent-child relationship matrix R such that if ⁇ overscore (y) ⁇ is the vector of values associated with one or more parents of the children represented in ⁇ overscore (x) ⁇ and ⁇ overscore (x) ⁇ ′, then the parent-child relationship can be expressed as follows:
- ⁇ overscore (x) ⁇ ′ ⁇ overscore (x) ⁇ + ⁇ R T ( R ⁇ R T ) ⁇ 1 ( ⁇ overscore (y) ⁇ R ⁇ overscore (x) ⁇ ) (3)
- R T is the transpose of R.
- each child i may be denoted by a separate column vector (x i,1 , . . . , x i,T ) and the values of the parent may be denoted by a single column vector (y 1 , y 2 , . . . , y T ).
- the matrix Variation(x) representing the variations of all children at all times is a square matrix of dimension equal to the product of the number of children and T. In such a matrix, most elements are equal to zero.
- ⁇ t ⁇ [ ⁇ 1 , 1 t ⁇ 1 , 2 t ⁇ 1 , 3 t ⁇ 2 , 1 t ⁇ 2 , 2 t ⁇ 2 , 3 t ⁇ 3 , 1 t ⁇ 3 , 2 t ⁇ 3 , 3 t ]
- ⁇ 1,1 t is the variation (such as the variation) of a particular child i at time t and ⁇ i,j t is the correlated variation or “covariation” (such as the covariance) between two different children i and j at time t.
- the variations and covariations may be determined using any appropriate methods, including but not limited to standard statistical formulas or more complex statistical models. In certain embodiments, the covariations are not utilized and are replaced by zeros in the above matrix.
- embodiments of the present invention account for the variation of the data values associated with a child in a hierarchical organization of data when allocating a value to that child from a parent. Therefore, the present invention provides a more accurate allocation. Furthermore, embodiments of the present invention may also take into account parent-child relationships involving different dimensions of data storage 16 when allocating a value. In addition, embodiments of the present invention typically do not require complex computations to perform an allocation. Exemplary allocation scenarios are described below with reference to FIGS. 5 and 6.
- FIG. 4 illustrates an exemplary method for allocating data, such as forecast data, in hierarchical organization of data associated with a business or other planning environment.
- the method begins at step 102 where the value of one or more parents at a time t is forecasted or otherwise determined.
- any appropriate technique for generating a forecast for a particular value such as a demand value
- Values associated with multiple parents in different dimensions within data storage 16 may be determined and those values may be allocated to the children of those parents according to the present method. If there is a single parent value, then this value is represented in Equations (1), (2), and (3) above as a value y (instead of a vector ⁇ overscore (y) ⁇ ).
- parent values are represented in the equations as a column vector ⁇ overscore (y) ⁇ .
- the current values of the children are determined. These values are represented in Equations (1), (2), and (3) as the column vector ⁇ overscore (x) ⁇ .
- the parent-child relationship matrix R is determined. As described above, the parent-child relationship matrix is formulated such that the value of a parent or parents at a particular time is equal to the product of the parent-child relationship matrix and the vector of the child values at that time.
- the variation matrix ⁇ for the children at the relevant time t is determined at step 108 . As described above, the variations included in the variation matrix may be determined using any appropriate methods.
- the values of the children at time t are determined according to Equation (3) presented above.
- the values of the children at time t are represented as the vector ⁇ overscore (x) ⁇ ′ and are determined using the values of ⁇ overscore (y) ⁇ , ⁇ overscore (x) ⁇ , R, and ⁇ that were determined in steps 102 , 104 , 106 , and 108 , respectively.
- these values may be determined in any appropriate order and in any appropriate manner.
- FIG. 5 illustrates an exemplary allocation of a forecasted value associated with a single parent 200 in one dimension using the method of FIG. 4.
- the current value (such as a demand value) associated with parent 200 , which may represent a product category C 1 in product dimension 50 , is 600 units.
- Parent 200 has a first child 210 a representing a product family F 1 and having a current associated value of 100 units, a second child 210 b representing a product family F 2 and having a current associated value of 200 units, and a third child 210 c representing a product family F 3 and having a current associated value of 300 units.
- x _ [ 100 200 300 ]
- the parent-child relationship matrix may be expressed as follows:
- ⁇ overscore (x) ⁇ ′ ⁇ overscore (x) ⁇ + ⁇ R T ( R ⁇ R T ) ⁇ 1 ( y ⁇ R ⁇ overscore (x) ⁇ )
- the sum of these allocated values equals the forecasted parent value. Furthermore, these values may be compared to the values obtained using a proportional allocation technique. Using such a technique, the values of the first, second, and third children 210 would be 116.67 units, 233.33 units, and 350 units, respectfully. However, these values do not account for the variations in the values associated with each child 210 and thus likely to be less accurate than the values that are obtained above using the exemplary method of the present invention.
- FIG. 6 illustrates an exemplary allocation of forecasted values associated with multiple parents 220 in multiple dimensions using the method of FIG. 4.
- a first parent 220 a is associated with a territory T 1 in geography dimension 70 and also with a product category C 1 in product dimension 50 .
- the product category C 1 includes two families F 1 and F 2 .
- a second parent 220 b is associated with a district D 1 in geography dimension 70 and also with family F 2 in product dimension 50 .
- District D 1 includes territories T 1 , T 2 , and T 3 .
- the first and second parents 220 each represent values (such as demand values) associated with two dimensions.
- Parent 220 a represents values associated with product category C 1 in territory T 1 .
- Parent 220 b represents values associated with district D 1 for product family F 2 .
- Parent 220 a has a first child 230 a that represents values associated with product family F 1 in territory T 1 and has a second child 230 b that represents values associated with product family F 2 in territory T 1 .
- Parent 220 b has a first child 230 b that represents values associated with product family F 2 in territory T 1 , a second child 230 c that represents values associated with product family F 2 in territory T 2 , and a third child 230 d that represents values associated with product family F 2 in territory T 3 . Therefore, parents 220 share a single child 230 b representing values associated with product family F 2 in territory T 1 .
- the current value (such as a demand value) associated with parent 220 a is 300 units.
- Child 230 a has an associated current value of 100 units and child 230 b has an associated current value of 200 units.
- the current value associated with parent 220 b is 900 units.
- child 230 b (which is shared with parent 220 a ) has an associated current value of 200 units.
- Child 230 c has an associated current value of 300 units and a child 230 d has an associated current value of 400 units.
- ⁇ overscore (x) ⁇ ′ ⁇ overscore (x) ⁇ + ⁇ R T ( R ⁇ R T ) ⁇ 1 ( ⁇ overscore (y) ⁇ R ⁇ overscore (x) ⁇ )
- the sum of the allocated values for children 230 equal the forecasted values of their respective parents 220 . Furthermore, these values may be compared to the values obtained using a proportional allocation technique. Using such a technique, the values of children 230 a and 230 b of parent 220 a would be 133.33 units and 266.67 units, respectively. The values of the children 230 b, 230 c, and 230 d of parent 220 b would be 222.22 units, 333.33 units, and 444.44 units, respectively. However, these values do not account for the variations in the values associated with each child 230 and thus likely to be less accurate than the values that are obtained above using the exemplary method of the present invention.
- the proportional allocation technique produces two different values for child 230 b since the proportional allocation method is performed separately for each parent 220 and the allocation from each parent 220 produces a different result for the value to be associated with child 230 b. These different results could then have to be reconciled. Therefore, the present invention is also advantageous in that it can simultaneously allocate values from multiple parents 220 to their children 230 (some of which may be common to two or more parents).
- the present invention provides for the allocation of data from parents to children in a hierarchical organization of data having one or more dimensions in a manner likely to be more accurate than with previous techniques.
- the present invention provides a number of advantages.
- the representation of parent child relations using the parent-child relationship matrix R is a flexible and general mathematical representation allowing greater flexibility and rigor in allocation from parents to children.
- the quantities involved in an allocation are appropriate statistical quantities, the result from the allocation is statistically optimal.
- one advantage of the present application is the generality offered by the parent-child relationship matrix in handling and representing parent-child relations.
- the parent-child relationship matrix can have as many rows as there are parents whose values need to be allocated to their children. However, if multiple parents do not have common children, computation may be simplified by separating such rows into different parent-child relationship matrices.
- the most elementary case is a parent-child relationship matrix having a single row.
- the columns of the matrix represent the total number of children involved in a parent child relationship with a parent represented by the row of the matrix.
- Each child typically has only one column regardless of the number of parents the child has.
- the value of an element in a row will typically be zero if the corresponding column is not a child of the parent represented by the row.
- a nonzero value indicates that the corresponding column is a child of the parent represented by the row.
- the nonzero value itself could be any number, so that any linear relationship could exist between a set of children and their parent.
- One example of a type of parent-child relationship is when the parent is equal to the sum of its children (an aggregation relation), as described above. In this case, each element of a row in the parent-child relationship matrix is zero if a child is not involved in the aggregation relation and is a one when the child is involved in the aggregation.
- Another type of parent-child relationship is when the parent is the average of its children. In this case, each element of a row of the parent-child relationship matrix is zero when the corresponding child is not involved in averaging and is the fraction 1/n (where n is equal to the number of children of the parent) when the corresponding child is involved in the averaging.
- parent-child relationship when the parent is a dollar value of a group of items and the children are quantities of each item contributing to the dollar value of the parent.
- each element of a row of the parent-child relationship matrix is zero when the corresponding child is not involved in contributing to the dollar value represented by the parent.
- the value of the element is equal to the price of the corresponding child when the child is involved in contributing to the dollar value represented by the parent.
- a row of the parent-child relationship matrix may represent a direct parent of the children involved in an allocation or an indirect parent.
- the parent represented by a row may be a parent of another member that is a parent of the children involved in the allocation.
- the values in the parent-child relationship matrices described above are numerical, the values may also be semantic or have particular business meanings.
- ⁇ overscore (x) ⁇ may be zero or may be the result of other types of computations or user inputs.
- ⁇ also may include either statistical quantities, more simplified user-inputs, results of other non-statistical computations, or any other appropriate values.
- ⁇ may include the same values as ⁇ overscore (x) ⁇ , or be directly related to those values, along its diagonal and have off-diagonal elements equal to zero.
- ⁇ overscore (x) ⁇ may be regarded as zero and ⁇ may be populated with values along its diagonal which are not all zero.
- the present invention could be used to perform a proportional allocation of the desired values of the parents to the children, taking advantage of the ability of the method to handle multiple parents with shared children.
- a similar example is when it is desirable to allocate the difference between the current value of a parent and the desired value, according to a particular proportion among its children. In this case, not all elements of ⁇ overscore (x) ⁇ may be regarded as zero.
- the current values of ⁇ overscore (x) ⁇ (or their functions, such as their square root or square) may be used as weights for an allocation and appear as the diagonal elements of ⁇ .
- the advantage is the ability to allocate multiple parents to their children in a consistent fashion.
- the final allocated quantity may not be one that is explicitly produced by using Equation (3) presented above.
- determining the final allocated quantity may involve selecting between and/or combining outputs obtained from different allocations using Equation (3).
- One reason for such selection and/or combination is that there may be uncertainties about the accuracy of the various quantities involved in allocation.
- the output from one or more of the allocations may be selected based on appropriate criteria.
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Human Resources & Organizations (AREA)
- Quality & Reliability (AREA)
- Strategic Management (AREA)
- Tourism & Hospitality (AREA)
- Operations Research (AREA)
- General Business, Economics & Management (AREA)
- Marketing (AREA)
- Entrepreneurship & Innovation (AREA)
- Economics (AREA)
- Data Mining & Analysis (AREA)
- General Engineering & Computer Science (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
Description
- This invention relates to the field of data allocation, and more particularly to a system and method for allocating data in a hierarchical organization of data.
- It is often desirable within a business or other planning environment to generate information regarding demand, available supply, selling price, or other data concerning a product or other item. Data for products may often be dependent in some manner on data for other hierarchically related products. For example, demand for a product with multiple components may drive the demand for a particular one of those components. Similarly, demand for products in a particular geographic region may drive the demand for the products in a particular territory in the region. Because of these hierarchical dependencies, the data concerning various products or other items may be stored hierarchically in data storage or derived in a hierarchical fashion. Furthermore, the data may be stored at a storage location associated with multiple dimensions, such as a product dimension (the storage location being associated with a particular product or product component), a geography dimension (the storage location being associated with a particular geographical area), and a time dimension (the storage location being associated with a particular time or time period).
- It is often desirable to update product data by forecasting demand values or other appropriate values for a particular product or group of products. As an example, using the current and/or past demand values associated with a particular product in a particular state, the demand for the product in that state at a time in the future may be forecasted. However, it may not be feasible or accurate to forecast demand values for the product in a particular region of the state or to forecast demand values for the product in the entire country in which the state is included. Instead, the demand value for the product in the particular state may be used to determine other hierarchically related demand values using allocation techniques. For example, the forecasted demand value may be allocated by aggregating it with demand values for the product in other states in the country to determine a demand value for the product in the entire country. Alternatively, the demand value may be allocated by disaggregating it to determine a demand value for the product in each of the regions of the state. However, many current allocation methods do not provide a sufficiently accurate allocation of forecasted values and thus negatively affect demand planning, supply planning, or other planning based on the allocated values.
- According to the present invention, disadvantages and problems associated with previous data allocation techniques have been substantially reduced or eliminated.
- According to one embodiment of the present invention, a method for allocating data in a hierarchical organization of data includes determining new values for one or more parents in the organization of data and determining current values for one or more children in the organization of data. Each child is hierarchically related to one or more of the parents. The method also includes determining the relationship between each parent and its children and determining a variation for each child. Furthermore, the method includes determining a new value for each child by allocating the new values of the parents to the children based on the parent-child relationships, the current values of the children, and the variations of the children.
- The present invention provides a number of important technical advantages. Unlike previous data allocation techniques, embodiments of the present invention account for the variance of data values associated with a storage location in a hierarchical database or other organization of data when allocating a value to that storage location based on the forecasted value of a hierarchically related storage location. Therefore, the present invention provides a more accurate allocation than previous techniques. Furthermore, embodiments of the present invention also take into account multi-dimensional relationships between storage locations in a multi-dimensional hierarchical organization of data when allocating forecasted values. In addition, embodiments of the present invention typically do not require complex computations to perform such allocations. Other important technical advantages are readily apparent to those skilled in the art from the following figures, descriptions, and claims.
- To provide a more complete understanding of the present invention and the features and advantages thereof, reference is made to the following description taken in conjunction with the accompanying drawings, in which:
- FIG. 1 illustrates an exemplary system for allocating data in a hierarchical organization of data;
- FIG. 2 illustrates an exemplary product dimension within a multi-dimensional organization of data;
- FIG. 3 illustrates an exemplary geography dimension within a multi-dimensional organization of data;
- FIG. 4 illustrates an exemplary method for allocating data within a business or other planning environment;
- FIG. 5 illustrates an exemplary allocation of a forecasted value associated with a single parent in one dimension; and
- FIG. 6 illustrates an exemplary allocation of forecasted values associated with multiple parents associated with multiple dimensions.
- FIG. 1 illustrates an
exemplary system 10 for allocating data, such as forecasted data, in a hierarchical organization of data associated with a business or other planning environment. As described below,system 10 implements an allocation strategy that may be used to allocate a value associated with a particular data member in a data storage device or in a representation of data to hierarchically related data members. In general, forecasted data provides an estimate of the forecasted demand, available supply, selling price, or other quantifiable data measure associated with a particular product or other item. Although products are typically referred to throughout this application, the present invention contemplatessystem 10 allocating forecast data for appropriate tangible or non-tangible items other than products, including but not limited to services or other benefits. Furthermore, although forecasts are primarily discussed herein, the present invention is similarly applicable to allocating historical or other data, separately or in combination with forecast data, according to particular planning needs of an enterprise, facility, or user. Moreover, although the present invention is described primarily in connection with allocating demand forecasts for products, those skilled in the art will appreciate that the present invention is similarly applicable to allocating forecasts for available supply, selling price, and any other suitable data. -
System 10 includesclient 12,server 14, anddata storage 16.Client 12 may include one or more processes to provide appropriate administration, analysis, and planning input. Although these processes are preferably separate processes running on a dedicated client processor, the present invention contemplates these processes being integrated, in whole or in part, and running on one or more processors within the same or different computers. Similarly, theserver 14 may include one or more processes to receive administration, analysis, and planning input fromclient 12 and interact withdata storage 16 to provide corresponding output toclient 12. Although the processes are preferably separate processes running on a dedicated server processor, the present invention contemplates these processes being integrated, in whole or in part, and running on one or more processors within the same or different computers.Client 12 andserver 14 may be fully autonomous or may operate at least in part subject to input from users ofsystem 10. - The term “data storage” is used to refer to any appropriate data source, representation of data, or other organization of data.
Data storage 16 may be hierarchical in nature, may be multi-dimensional, and/or may provide persistent data storage forsystem 10. For example,data storage 16 may be a multi-dimensional database that stores data in a hierarchical and multidimensional format ordata storage 16 may be a representation of data derived byserver 12 or other appropriate component from data stored in a relational database, in memory, or in any other appropriate location.Server 12 or other appropriate component may use a multi-dimensional hierarchical transformation layer to create such a representation of the data. In one embodiment,data storage 16 includes three-dimensional data and, for each data measure, associates with each storage location 18 a particular member from the product dimension, a particular member from the geography dimension, and a particular member from the time dimension. Each of these particular combinations of members of these three dimensions is associated with acorresponding storage location 18 indata storage 16, similar to each combination of coordinates from the x, y, and z axes being associated with a point in three-dimensional Euclidian space. Furthermore, position within a particular dimension may be changed independent of members of other dimensions, much like the position of a coordinate along the x axis may be changed independent of the positions of other coordinates along the y and z axes in three-dimensional Euclidian space. - The present invention contemplates
data storage 16 having as few or as many dimensions as appropriate for the particular application. For example, and not by way of limitation, an enterprise associated withsystem 10 may not consider geography in connection with its data forecasting needs. This might be the case when products are ordered using the Internet or the telephone and then distributed from a single distribution point. In this example,data storage 16 might be two-dimensional rather than three-dimensional and might not reflect positions or members within the geography dimension. Furthermore, the demand or other data might be quantified per specified time interval, in whichcase data storage 16 might be two-dimensional and might not reflect positions or members within the time dimension. Other possible scenarios involving more or fewer than three dimensions will be apparent to those skilled in the art. The present invention contemplatesdata storage 16 having any number of dimensions appropriate for the needs of the enterprise or facility associated withsystem 10. - In the three-dimensional embodiment of the present invention, the values of the data measures within the set for a
particular storage location 18 depend on the combined positions of members within product, geography, and time dimensions for thatstorage location 18. As a result, the values of the data measures typically vary with these combined positions as appropriate to accurately reflect the demand, available supply, selling price, or other data associated with these members. As described below, when a suitable combination of members is specified in the product, geography, and time dimensions according to operation ofsystem 10,data storage 16 accesses the data measures forstorage location 18 associated with that combination of members to assistsystem 10 in allocating demand forecasts or other suitable data. The present invention contemplates other suitable dimensions to replace or be combined with the product, geography, and time dimensions according to particular needs. - In one embodiment,
data storage 16 supports multi-dimensional on-line analytical processing (OLAP) capability and is populated with data measures received from one or more transactional data sources that are internal, external, or both internal and external to the enterprise or facility associated withsystem 10. For example, and not by way of limitation, data measures received from sources internal to a manufacturing or warehousing. facility may include unit shipping data, dollar shipping data, inventory data, pricing data, and any other suitable information applicable to demand forecasting. Data measures received from external sources, such as from syndicated partners of the enterprise or facility, may include point-of-sale demographic data and any other suitable information. The present invention contemplates appropriate data measures being stored indata storage 16 in any suitable manner. -
Server 12 is coupled todata storage 16 usinglink 32, which may be any wireline, wireless, or other link suitable to support data communications betweenserver 12 anddata storage 16 during operation ofsystem 10.Data storage 16 may be integral to or separate fromserver 12, may operate on one or more computers, and may store any information suitable to support the operation ofsystem 10 in allocating demand forecasts or other data.Server 12 is coupled toclient 14 usinglink 30, which may be any wireline, wireless, or other link suitable to support communications betweenserver 12,client 14, and the processes ofserver 12 andclient 14 during operation ofsystem 10. Althoughlink 30 is shown as generally couplingserver 12 toclient 14, processes ofserver 12 may communicate directly with one or more corresponding processes ofclient 14. -
System 10 may operate on one ormore computers 20 that are integral to or separate from the hardware and software that supportserver 12,client 14, anddata storage 16.Computer 20 may include asuitable input device 22, such as a keypad, mouse, touch screen, microphone, or other device to input information. Anoutput device 24 may convey information associated with the operation ofsystem 10, including digital or analog data, visual information, or audio information.Computer 20 may include fixed or removable storage media, such as magnetic computer disks, CD-ROM, or other suitable media to receive output from and provide input tosystem 10.Computer 30 may include one ormore processors 26 and associated memory to execute instructions and manipulate information according to the operation ofsystem 10. Although only asingle computer 20 is shown,server 12,client 14, anddata storage 16 may each operate onseparate computers 20 or may operate on one or more sharedcomputers 20 without departing from the intended scope of the present invention. Each of the one ormore computers 20 may be a work station, personal computer (PC), network computer, personal digital assistant (PDA), wireless data port, or any other suitable computing device. - FIG. 2 illustrates an
exemplary product dimension 50 withindata storage 16 that includes a hierarchy ofproduct levels 52 each having one ormore members 54. The value of each data measure associated with amember 54 is an aggregation of the values of corresponding data measures associated with hierarchicallyrelated members 54 inlower levels 52 ofproduct dimension 50. In an exemplary embodiment in whichsystem 10 provides demand forecasts, the demand associated with amember 54 is the aggregate demand for these hierarchicallyrelated members 54 inlower levels 52 ofproduct dimension 50. In the illustrated embodiment,product levels 52 forproduct dimension 50 include an allproducts level 58, aproduct type level 60, aproduct category level 62, and aproduct family level 64. Selected and merely exemplary hierarchical relationships betweenmembers 54 are shown usinglinks 56, as described more fully below.Links 56 between hierarchicallyrelated members 54 inadjacent levels 52 ofproduct dimension 50 reflect parent-child relationships betweenmembers 54. Although FIG. 2 is described primarily in connection with demand relationships, the following description is similarly applicable to other data relationships, such as available supply, selling price, or any other relationships relating to data measures associated with an item or set of items. - In the particular example shown in FIG. 2, all
products level 58 contains “All”member 54 representing the aggregate demand for allmembers 54 inlower levels product dimension 50.Product type level 60 contains “Components,” “Base Units,” and “Options”members 54. “Components”member 54 represents the aggregate demand for hierarchicallyrelated members 54 below “Components”member 54 inlevels product dimension 50. Similarly, “Base Units”member 54 represents the aggregate demand for hierarchicallyrelated members 54 below “Base Units”member 54 and “Options”member 54 represents the aggregate demand for hierarchicallyrelated members 54 below “Options”member 54.Links 56 between “All”member 54 and “Components,” “Base Units,” and “Options”members 54 indicate the hierarchical relationships between thesemembers 54. -
Product category level 62 contains, under “Components”member 54, “Hard Drives,” “Memory Boards,” and “CPUs”members 54. “Hard Drives”member 54 represents the aggregate demand for hierarchicallyrelated members 54 below “Hard Drives”member 54 inlevel 64 ofproduct dimension 50. Similarly, “Memory Boards”member 54 represents aggregate demand for hierarchicallyrelated members 54 below “Memory Boards”member 54 and “CPUs”member 54 represents the aggregate demand for hierarchicallyrelated members 54 below “CPUs”member 54.Links 56 between “Components”member 54 and “Hard Drives,” “Memory Boards,” and “CPUs”members 54 indicate the hierarchical relationships between thesemembers 54.Analogous links 56 reflect hierarchical relationships between “Base Units” and “Options”members 54 ofproduct type level 60 andcorresponding members 54 inlower levels product dimension 50. -
Product family level 64 contains, under “Hard Drives”member 54, “4 GB” and “6 GB”members 54.Links 56 between “Hard Drives”member 54 and “4 GB” and “6 GB”members 54 indicate hierarchical relationships between thesemembers 54.Analogous links 56 reflect hierarchical relationships between “Memory Boards,” “CPUs,” “Servers,” “Desktops,” “Laptops,” “Monitors,” “Keyboards,” and “Printers”members 54 ofproduct category level 62 andcorresponding members 54 inlower level 64 withinproduct dimension 50. Although nolinks 56 are shown betweenmembers 54 inproduct family level 64 and possiblelower levels 52, the present invention contemplates suchfurther levels 52 existing withinproduct dimension 50 andanalogous links 56 to reflect the corresponding hierarchical relationships. Furthermore,members 54 shown in FIG. 2 are exemplary only and are not intended to be an exhaustive set of allpossible members 54. Those skilled in the art will appreciate that othersuitable members 54 and associatedlinks 56 may exist without departing from the intended scope of the present invention. - FIG. 3 illustrates an
exemplary geography dimension 70 withindata storage 16 that includes a hierarchy ofgeography levels 72 each having one ormore members 74. The value of each data measure associated with amember 74 is an aggregation of the values of corresponding data measures associated with hierarchicallyrelated members 74 inlower levels 72 ofgeography dimension 70. In the exemplary embodiment in whichsystem 10 provides demand forecasts, the demand associated with amember 74 is the aggregate demand for these hierarchicallyrelated members 74. In this embodiment,geography levels 72 forgeography dimension 70 include aworld level 78, acountry level 80, aregion level 82, and adistrict level 84. Selected and merely exemplary hierarchical relationships betweenmembers 74 are shown usinglinks 76, which are analogous tolinks 56 described above with reference to FIG. 2. Although FIG. 3 is described primarily in connection with demand relationships, the following description is similarly applicable to other data relationships, such as available supply, selling price, or any other relationships relating to one or more data measures associated with an item or set of items. - In the particular example illustrated in FIG. 3,
world level 78 contains “World”member 74 representing aggregate worldwide demand.Country level 80 contains “U.S.” and “Canada”members 74, which represent aggregate demand for the United States and Canada, respectively.Link 76 between “U.S.”members 74 incountry level 80 and “World”members 74 inworld level 78 indicates a hierarchical relationship between thesemembers 74. Similarly, link 76 between “Canada”member 74 and “World”member 74 indicates a hierarchical relationship between thesemembers 74. In this example, worldwide demand is an aggregation of aggregate demand in the United States as well as aggregate demand in Canada. Althoughother links 76 are not described in detail, those skilled in the art will appreciate that links 76 are analogous tolinks 56 described above with reference to FIG. 2 in that each represents a corresponding hierarchical relationship betweenmembers 74 in thevarious levels 72 ofgeography dimension 70. As discussed above, the present invention contemplates eliminating or otherwise not considering thegeography dimension 70 in allocating data, for example, ifgeography dimension 70 is not relevant to particular data forecasting needs.Data storage 16 might in this situation be two-dimensional. - Demand or other forecasts may be derived using traditional forecasting techniques and suitable information concerning products, geographic areas, customers, and/or other data dimension. Such information may include historical sales, causal factors, key account input, market intelligence, and the like. Forecasting techniques may rely on hierarchical relationships between
members members member members lower levels child links member 54, 74 (a parent) at onelevel related members 54 in the nextlowest level 52, 72 (the children of the parent) may be determined by disaggregating the forecast data for the parent between the children. Furthermore, although the terms “parent” and “children” are used above to identify a relationship betweenmembers single dimension storage location 18 associated with a member from each of a number of dimensions. For example, astorage location 18 that includes a demand value for a particular product in a particular state may be hierarchically related to astorage location 18 that includes a demand value for the product in a city of that state (the value associated with theformer storage location 18 being a parent of the value associated with the latter storage location 18). - When allocating a forecast from one or more parents to their children, a “top-down” proportional allocation strategy is often used. In this strategy, the value of the forecast (such as a demand forecast) associated with a parent is divided proportionally among its children according to the relative current values (such as current demand values) associated with the children. Therefore, using such proportional allocation, children having larger values get a larger share of the number being allocated and children having smaller values get a proportionately smaller share. For example, if a parent with a forecasted demand of 1800 units has a first child that currently has an associated demand of 1000 units and a second child that currently has an associated demand of 500 units, then 1200 units of the forecasted demand would be allocated to the first child and 600 units of the forecasted demand would be allocated to the second child.
- Top-down allocation, proportional or otherwise, may be used for many reasons. For example, forecasts that are estimated at a
higher level lower levels high level higher level lower level - Embodiments of the present invention provide an allocation strategy that accounts for variance in the values associated with children when allocating a forecasted value from a parent of the children. Furthermore, it is possible for the values of the children to have positive or negative relationships between themselves, so that a higher value associated with one child may have a correspondence with a higher or lower value associated with another child. The allocation strategy of the present invention may also account for these relations.
- A distance measure may be defined as follows in order to take into account the variance and correspondence between children when allocating a forecast:
- d=({overscore (x)}−{overscore (x)}′)Σ−1({overscore (x)}−{overscore (x)}′) (1)
- In this equation, {overscore (x)} is the vector of current values (such as demand values) associated with the children of a particular parent. Σ is the variation matrix that identifies the variation of each child (Σ−1 being the inverse of the variance matrix). The variation of a particular child may be expressed as a standard deviation, variance, or any other suitable measure and may be determined using statistical equations, models, or any other appropriate technique. {overscore (x)}′ is the vector of the values associated with the children after the allocation of the forecast from the parent. To optimally allocate the forecast, the selection of the values of {overscore (x)}′ should minimize the distance d.
- According to the present invention, the determination of {overscore (x)}′ may be subject to the constraint of the parent-child relationships. For general linear relationships, such as when the value associated with a parent equals the sum or average of the values associated with its children, it is possible to define a suitable parent-child relationship matrix R such that if {overscore (y)} is the vector of values associated with one or more parents of the children represented in {overscore (x)} and {overscore (x)}′, then the parent-child relationship can be expressed as follows:
- R{overscore (x)}′={overscore (y)} (2)
- It should be noted that a child may have multiple parents in the same dimension or in multiple dimensions. This concept is described below with reference to FIG. 6. Given the above two equations, an optimal {overscore (x)}′ may be given by the following equation:
- {overscore (x)}′={overscore (x)}+ΣR T(RΣR T)−1({overscore (y)}−R{overscore (x)}) (3)
- where RT is the transpose of R.
-
-
- In general, the matrix Variation(x) representing the variations of all children at all times is a square matrix of dimension equal to the product of the number of children and T. In such a matrix, most elements are equal to zero. For example, assume that the values of {overscore (x)} are predictions from a model. Variation(x) assumes a typical block-diagonal structure as follows:
-
- where σ1,1 t is the variation (such as the variation) of a particular child i at time t and σi,j t is the correlated variation or “covariation” (such as the covariance) between two different children i and j at time t. The variations and covariations may be determined using any appropriate methods, including but not limited to standard statistical formulas or more complex statistical models. In certain embodiments, the covariations are not utilized and are replaced by zeros in the above matrix.
-
-
- Unlike previous allocation techniques, embodiments of the present invention account for the variation of the data values associated with a child in a hierarchical organization of data when allocating a value to that child from a parent. Therefore, the present invention provides a more accurate allocation. Furthermore, embodiments of the present invention may also take into account parent-child relationships involving different dimensions of
data storage 16 when allocating a value. In addition, embodiments of the present invention typically do not require complex computations to perform an allocation. Exemplary allocation scenarios are described below with reference to FIGS. 5 and 6. - FIG. 4 illustrates an exemplary method for allocating data, such as forecast data, in hierarchical organization of data associated with a business or other planning environment. The method begins at
step 102 where the value of one or more parents at a time t is forecasted or otherwise determined. As described above, any appropriate technique for generating a forecast for a particular value (such as a demand value) associated with a parent may be used. Values associated with multiple parents in different dimensions withindata storage 16 may be determined and those values may be allocated to the children of those parents according to the present method. If there is a single parent value, then this value is represented in Equations (1), (2), and (3) above as a value y (instead of a vector {overscore (y)}). If there are multiple parent values, those parent values are represented in the equations as a column vector {overscore (y)}. Atstep 104, the current values of the children (or the values otherwise existing before allocation of the forecasted parent value) are determined. These values are represented in Equations (1), (2), and (3) as the column vector {overscore (x)}. - At
step 106, the parent-child relationship matrix R is determined. As described above, the parent-child relationship matrix is formulated such that the value of a parent or parents at a particular time is equal to the product of the parent-child relationship matrix and the vector of the child values at that time. The variation matrix Σ for the children at the relevant time t is determined atstep 108. As described above, the variations included in the variation matrix may be determined using any appropriate methods. Atstep 110, the values of the children at time t are determined according to Equation (3) presented above. In this equation, the values of the children at time t are represented as the vector {overscore (x)}′ and are determined using the values of {overscore (y)}, {overscore (x)}, R, and Σ that were determined insteps - FIG. 5 illustrates an exemplary allocation of a forecasted value associated with a
single parent 200 in one dimension using the method of FIG. 4. In this example, the current value (such as a demand value) associated withparent 200, which may represent a product category C1 inproduct dimension 50, is 600 units.Parent 200 has afirst child 210 a representing a product family F1 and having a current associated value of 100 units, asecond child 210 b representing a product family F2 and having a current associated value of 200 units, and athird child 210 c representing a product family F3 and having a current associated value of 300 units. These values may be expressed in a vector as follows: - In this example, the sum of the values of children210 equals the value of
parent 200. Therefore, the parent-child relationship matrix may be expressed as follows: - R=[1 1 1]
-
- Assuming that the forecasted value y associated with
parent 200 at time t is 700 units, the values allocated to children 210 for time t using Equation (3) above may be determined as follows: - {overscore (x)}′={overscore (x)}+ΣR T(RΣR T)−1(y−R{overscore (x)})
-
- It should be noted that the sum of these allocated values equals the forecasted parent value. Furthermore, these values may be compared to the values obtained using a proportional allocation technique. Using such a technique, the values of the first, second, and third children210 would be 116.67 units, 233.33 units, and 350 units, respectfully. However, these values do not account for the variations in the values associated with each child 210 and thus likely to be less accurate than the values that are obtained above using the exemplary method of the present invention.
- FIG. 6 illustrates an exemplary allocation of forecasted values associated with multiple parents220 in multiple dimensions using the method of FIG. 4. In this example, a first parent 220 a is associated with a territory T1 in
geography dimension 70 and also with a product category C1 inproduct dimension 50. The product category C1 includes two families F1 and F2. Furthermore, asecond parent 220 b is associated with a district D1 ingeography dimension 70 and also with family F2 inproduct dimension 50. District D1 includes territories T1, T2, and T3. As can be seen, the first and second parents 220 each represent values (such as demand values) associated with two dimensions. Parent 220 a represents values associated with product category C1 in territory T1.Parent 220 b represents values associated with district D1 for product family F2. - Parent220 a has a
first child 230 a that represents values associated with product family F1 in territory T1 and has asecond child 230 b that represents values associated with product family F2 in territory T1.Parent 220 b has afirst child 230 b that represents values associated with product family F2 in territory T1, asecond child 230 c that represents values associated with product family F2 in territory T2, and athird child 230 d that represents values associated with product family F2 in territory T3. Therefore, parents 220 share asingle child 230 b representing values associated with product family F2 in territory T1. - In this example, the current value (such as a demand value) associated with parent220 a is 300 units.
Child 230 a has an associated current value of 100 units andchild 230 b has an associated current value of 200 units. The current value associated withparent 220 b is 900 units. As described above,child 230 b (which is shared with parent 220 a) has an associated current value of 200 units.Child 230 c has an associated current value of 300 units and achild 230 d has an associated current value of 400 units. The values associated with children 230 may be expressed in a vector as follows: -
-
- Assuming that the forecasted value associated with parent220 a at time t is 400 units and the forecasted value associated with
parent 220 b at time t is 1000 units, the values allocated to children 230 at time t using Equation (3) above may be determined as follows: - {overscore (x)}′={overscore (x)}+ΣR T(RΣR T)−1({overscore (y)}−R{overscore (x)})
-
- It should be noted that the sum of the allocated values for children230 equal the forecasted values of their respective parents 220. Furthermore, these values may be compared to the values obtained using a proportional allocation technique. Using such a technique, the values of
children children parent 220 b would be 222.22 units, 333.33 units, and 444.44 units, respectively. However, these values do not account for the variations in the values associated with each child 230 and thus likely to be less accurate than the values that are obtained above using the exemplary method of the present invention. Furthermore, the proportional allocation technique produces two different values forchild 230 b since the proportional allocation method is performed separately for each parent 220 and the allocation from each parent 220 produces a different result for the value to be associated withchild 230 b. These different results could then have to be reconciled. Therefore, the present invention is also advantageous in that it can simultaneously allocate values from multiple parents 220 to their children 230 (some of which may be common to two or more parents). - As can be seen from the above examples, the present invention provides for the allocation of data from parents to children in a hierarchical organization of data having one or more dimensions in a manner likely to be more accurate than with previous techniques. The present invention provides a number of advantages. For example, the representation of parent child relations using the parent-child relationship matrix R is a flexible and general mathematical representation allowing greater flexibility and rigor in allocation from parents to children. Furthermore, when the quantities involved in an allocation are appropriate statistical quantities, the result from the allocation is statistically optimal.
- Although particular examples are described above, the techniques of the present invention may be used for many other applications. For example, one advantage of the present application is the generality offered by the parent-child relationship matrix in handling and representing parent-child relations. The parent-child relationship matrix can have as many rows as there are parents whose values need to be allocated to their children. However, if multiple parents do not have common children, computation may be simplified by separating such rows into different parent-child relationship matrices.
- The most elementary case is a parent-child relationship matrix having a single row. The columns of the matrix represent the total number of children involved in a parent child relationship with a parent represented by the row of the matrix. Each child typically has only one column regardless of the number of parents the child has. The value of an element in a row will typically be zero if the corresponding column is not a child of the parent represented by the row. A nonzero value indicates that the corresponding column is a child of the parent represented by the row. The nonzero value itself could be any number, so that any linear relationship could exist between a set of children and their parent.
- One example of a type of parent-child relationship is when the parent is equal to the sum of its children (an aggregation relation), as described above. In this case, each element of a row in the parent-child relationship matrix is zero if a child is not involved in the aggregation relation and is a one when the child is involved in the aggregation. Another type of parent-child relationship is when the parent is the average of its children. In this case, each element of a row of the parent-child relationship matrix is zero when the corresponding child is not involved in averaging and is the
fraction 1/n (where n is equal to the number of children of the parent) when the corresponding child is involved in the averaging. Yet another example of a parent-child relationship is when the parent is a dollar value of a group of items and the children are quantities of each item contributing to the dollar value of the parent. In this case, each element of a row of the parent-child relationship matrix is zero when the corresponding child is not involved in contributing to the dollar value represented by the parent. The value of the element is equal to the price of the corresponding child when the child is involved in contributing to the dollar value represented by the parent. - It should be noted that a row of the parent-child relationship matrix may represent a direct parent of the children involved in an allocation or an indirect parent. For example, the parent represented by a row may be a parent of another member that is a parent of the children involved in the allocation. Furthermore, although the values in the parent-child relationship matrices described above are numerical, the values may also be semantic or have particular business meanings.
- The flexibility offered by the parent-child relationship matrix is not restricted to cases where some or all of the values to be allocated are statistical quantities. For example, {overscore (x)} may be zero or may be the result of other types of computations or user inputs. Similarly, Σ also may include either statistical quantities, more simplified user-inputs, results of other non-statistical computations, or any other appropriate values. For certain cases, Σ may include the same values as {overscore (x)}, or be directly related to those values, along its diagonal and have off-diagonal elements equal to zero.
- For example, {overscore (x)} may be regarded as zero and Σ may be populated with values along its diagonal which are not all zero. In this case, the present invention could be used to perform a proportional allocation of the desired values of the parents to the children, taking advantage of the ability of the method to handle multiple parents with shared children. A similar example is when it is desirable to allocate the difference between the current value of a parent and the desired value, according to a particular proportion among its children. In this case, not all elements of {overscore (x)} may be regarded as zero. The current values of {overscore (x)} (or their functions, such as their square root or square) may be used as weights for an allocation and appear as the diagonal elements of Σ. Again, the advantage is the ability to allocate multiple parents to their children in a consistent fashion.
- The above examples show that the parent-child relationship matrix and a variety of choices for {overscore (x)} and Σ allow for a flexible and generalized allocation scheme with respect to parent-child relations. Additional flexibility and rigor is obtained in the allocation by using a variety of different types of values as the contents of Σ. As a example only, one can design a Σ matrix with the variances or a measure of the relative variation of the children along its diagonal. Further, unlike in the previous examples, the off-diagonal values of Σ can be non-zero and made equal to measures of covariances or relative co-variation of each pair of children. This structure of Σ, when used in an allocation scheme, can account for relations between the children themselves. For example, when the value of one child i is higher, another child j may tend to be higher or lower to a degree specified by the quantity in the ith row and jth column of Σ.
- Furthermore, the final allocated quantity may not be one that is explicitly produced by using Equation (3) presented above. For example, determining the final allocated quantity may involve selecting between and/or combining outputs obtained from different allocations using Equation (3). One reason for such selection and/or combination is that there may be uncertainties about the accuracy of the various quantities involved in allocation. In such cases, it may be preferable to use alternative quantities in the allocation method and combine the results of the allocations in an appropriate manner (for example, by averaging the results) such that the final quantities after allocation might not be the result of applying the method to any one choice of input quantities. Similarly the output from one or more of the allocations may be selected based on appropriate criteria.
- Although the present invention has been described with several embodiments, numerous changes, substitutions, variations, alterations, and modifications may be suggested to one skilled in the art, and it is intended that the invention encompass all such changes, substitutions, variations, alterations, and modifications as fall within the spirit and scope of the appended claims.
Claims (34)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/825,083 US6988104B2 (en) | 2001-04-02 | 2001-04-02 | System and method for allocating data in a hierarchical organization of data |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/825,083 US6988104B2 (en) | 2001-04-02 | 2001-04-02 | System and method for allocating data in a hierarchical organization of data |
Publications (2)
Publication Number | Publication Date |
---|---|
US20020178167A1 true US20020178167A1 (en) | 2002-11-28 |
US6988104B2 US6988104B2 (en) | 2006-01-17 |
Family
ID=25243069
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/825,083 Expired - Fee Related US6988104B2 (en) | 2001-04-02 | 2001-04-02 | System and method for allocating data in a hierarchical organization of data |
Country Status (1)
Country | Link |
---|---|
US (1) | US6988104B2 (en) |
Cited By (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040138942A1 (en) * | 2002-09-30 | 2004-07-15 | Pearson George Duncan | Node-level modification during execution of an enterprise planning model |
US20040181518A1 (en) * | 2003-03-14 | 2004-09-16 | Mayo Bryan Edward | System and method for an OLAP engine having dynamic disaggregation |
US20070016434A1 (en) * | 2005-07-15 | 2007-01-18 | Cognos Incorporated | Interview-based enterprise planning |
US20080066067A1 (en) * | 2006-09-07 | 2008-03-13 | Cognos Incorporated | Enterprise performance management software system having action-based data capture |
US7516084B1 (en) * | 2001-07-12 | 2009-04-07 | Lawson Software, Inc. | Approach for managing forecast data |
US7693737B2 (en) | 2000-07-31 | 2010-04-06 | International Business Machines Corporation | Enterprise planning |
US20100192077A1 (en) * | 2009-01-26 | 2010-07-29 | Raytheon Company | Parent/Child Control System for a Workflow Automation Tool |
US20140229879A1 (en) * | 2011-10-20 | 2014-08-14 | Ajou University Industry-Academic Cooperation Foundation | Treemap visualization system and method |
US20200160441A1 (en) * | 2007-03-30 | 2020-05-21 | International Business Machines Corporation | Method and system for forecasting using an online analytical processing database |
US20220122188A1 (en) * | 2020-10-21 | 2022-04-21 | Sage Intacct, Inc. | Dependent dimensions |
Families Citing this family (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7293067B1 (en) | 1999-07-16 | 2007-11-06 | Canon Kabushiki Kaisha | System for searching device on network |
NO323907B1 (en) * | 2000-07-07 | 2007-07-16 | Ericsson Telefon Ab L M | Personal mobile internet |
US20040103018A1 (en) * | 2002-11-27 | 2004-05-27 | Kim Edward D. | Methods and systems for demand forecasting of promotion, cannibalization, and affinity effects |
US8639548B2 (en) * | 2004-03-08 | 2014-01-28 | Sap Aktiengesellschaft | System and method for assortment planning |
US8392231B2 (en) | 2004-03-08 | 2013-03-05 | Sap Aktiengesellschaft | System and method for performing assortment definition |
US8370184B2 (en) * | 2004-03-08 | 2013-02-05 | Sap Aktiengesellschaft | System and method for assortment planning |
US7752067B2 (en) | 2004-03-08 | 2010-07-06 | Sap Aktiengesellschaft | System and method for assortment planning |
US8429032B2 (en) * | 2005-02-24 | 2013-04-23 | International Business Machines Corporation | Method and system for managing inventory for a migration using forecast/inventory displays |
US7698349B2 (en) * | 2005-05-25 | 2010-04-13 | Microsoft Corporation | Dimension member sliding in online analytical processing |
US8065203B1 (en) * | 2007-08-01 | 2011-11-22 | Sas Institute Inc. | Computer-implemented systems and methods for product attribute estimations |
US20100082405A1 (en) * | 2008-09-30 | 2010-04-01 | Shan Jerry Z | Multi-period-ahead Forecasting |
Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5285392A (en) * | 1991-11-27 | 1994-02-08 | Mckinsey & Company, Inc. | Parallel manufacturing system |
US5936860A (en) * | 1997-03-28 | 1999-08-10 | International Business Machines Corporation | Object oriented technology framework for warehouse control |
US5946662A (en) * | 1996-03-29 | 1999-08-31 | International Business Machines Corporation | Method for providing inventory optimization |
US5991732A (en) * | 1989-02-15 | 1999-11-23 | Moslares; Andres Monedero | Strategical-tactical logistic system |
US6119102A (en) * | 1996-04-15 | 2000-09-12 | Made2Manage Systems, Inc. | MRP system with viewable master production schedule |
US6442554B1 (en) * | 1999-01-29 | 2002-08-27 | I2 Technologies Us, Inc. | System and method for generating dependent data |
US6574619B1 (en) * | 2000-03-24 | 2003-06-03 | I2 Technologies Us, Inc. | System and method for providing cross-dimensional computation and data access in an on-line analytical processing (OLAP) environment |
Family Cites Families (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5406477A (en) * | 1991-08-30 | 1995-04-11 | Digital Equipment Corporation | Multiple reasoning and result reconciliation for enterprise analysis |
US5359724A (en) | 1992-03-30 | 1994-10-25 | Arbor Software Corporation | Method and apparatus for storing and retrieving multi-dimensional data in computer memory |
US5502576A (en) | 1992-08-24 | 1996-03-26 | Ramsay International Corporation | Method and apparatus for the transmission, storage, and retrieval of documents in an electronic domain |
US5528735A (en) | 1993-03-23 | 1996-06-18 | Silicon Graphics Inc. | Method and apparatus for displaying data within a three-dimensional information landscape |
US5799295A (en) | 1993-12-29 | 1998-08-25 | Kabushiki Kaisha Toshiba | Constraint-based spreadsheet system capable of displaying a process of execution of programs |
US5615341A (en) | 1995-05-08 | 1997-03-25 | International Business Machines Corporation | System and method for mining generalized association rules in databases |
US5758026A (en) * | 1995-10-13 | 1998-05-26 | Arlington Software Corporation | System and method for reducing bias in decision support system models |
EP0770967A3 (en) * | 1995-10-26 | 1998-12-30 | Koninklijke Philips Electronics N.V. | Decision support system for the management of an agile supply chain |
US6034697A (en) | 1997-01-13 | 2000-03-07 | Silicon Graphics, Inc. | Interpolation between relational tables for purposes of animating a data visualization |
US6137499A (en) | 1997-03-07 | 2000-10-24 | Silicon Graphics, Inc. | Method, system, and computer program product for visualizing data using partial hierarchies |
US5991754A (en) | 1998-12-28 | 1999-11-23 | Oracle Corporation | Rewriting a query in terms of a summary based on aggregate computability and canonical format, and when a dimension table is on the child side of an outer join |
US6163774A (en) | 1999-05-24 | 2000-12-19 | Platinum Technology Ip, Inc. | Method and apparatus for simplified and flexible selection of aggregate and cross product levels for a data warehouse |
-
2001
- 2001-04-02 US US09/825,083 patent/US6988104B2/en not_active Expired - Fee Related
Patent Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5991732A (en) * | 1989-02-15 | 1999-11-23 | Moslares; Andres Monedero | Strategical-tactical logistic system |
US5285392A (en) * | 1991-11-27 | 1994-02-08 | Mckinsey & Company, Inc. | Parallel manufacturing system |
US5946662A (en) * | 1996-03-29 | 1999-08-31 | International Business Machines Corporation | Method for providing inventory optimization |
US6119102A (en) * | 1996-04-15 | 2000-09-12 | Made2Manage Systems, Inc. | MRP system with viewable master production schedule |
US5936860A (en) * | 1997-03-28 | 1999-08-10 | International Business Machines Corporation | Object oriented technology framework for warehouse control |
US6442554B1 (en) * | 1999-01-29 | 2002-08-27 | I2 Technologies Us, Inc. | System and method for generating dependent data |
US6574619B1 (en) * | 2000-03-24 | 2003-06-03 | I2 Technologies Us, Inc. | System and method for providing cross-dimensional computation and data access in an on-line analytical processing (OLAP) environment |
Cited By (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7693737B2 (en) | 2000-07-31 | 2010-04-06 | International Business Machines Corporation | Enterprise planning |
US7516084B1 (en) * | 2001-07-12 | 2009-04-07 | Lawson Software, Inc. | Approach for managing forecast data |
US20040138942A1 (en) * | 2002-09-30 | 2004-07-15 | Pearson George Duncan | Node-level modification during execution of an enterprise planning model |
US20040181518A1 (en) * | 2003-03-14 | 2004-09-16 | Mayo Bryan Edward | System and method for an OLAP engine having dynamic disaggregation |
US20070016434A1 (en) * | 2005-07-15 | 2007-01-18 | Cognos Incorporated | Interview-based enterprise planning |
US20080066067A1 (en) * | 2006-09-07 | 2008-03-13 | Cognos Incorporated | Enterprise performance management software system having action-based data capture |
US20200160441A1 (en) * | 2007-03-30 | 2020-05-21 | International Business Machines Corporation | Method and system for forecasting using an online analytical processing database |
US20100192077A1 (en) * | 2009-01-26 | 2010-07-29 | Raytheon Company | Parent/Child Control System for a Workflow Automation Tool |
US20140229879A1 (en) * | 2011-10-20 | 2014-08-14 | Ajou University Industry-Academic Cooperation Foundation | Treemap visualization system and method |
US20220122188A1 (en) * | 2020-10-21 | 2022-04-21 | Sage Intacct, Inc. | Dependent dimensions |
US11823286B2 (en) * | 2020-10-21 | 2023-11-21 | Sage Intacct, Inc. | Dependent dimensions |
Also Published As
Publication number | Publication date |
---|---|
US6988104B2 (en) | 2006-01-17 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US6988104B2 (en) | System and method for allocating data in a hierarchical organization of data | |
US6873994B2 (en) | Conflict detection and resolution in association with data allocation | |
US11429668B2 (en) | Methods and systems for multidimensional analysis of interconnected data sets stored in a graph database | |
US8239245B2 (en) | Method and apparatus for end-to-end retail store site optimization | |
US8082175B2 (en) | System and method for optimization of a promotion plan | |
US20010047293A1 (en) | System, method and article of manufacture to optimize inventory and inventory investment utilization in a collaborative context | |
US8024218B2 (en) | Method and apparatus for determining the product marketability utilizing a percent coverage | |
US20040138932A1 (en) | Generating business analysis results in advance of a request for the results | |
US10853745B2 (en) | Computation of optimal inventory targets in bill-of-materials in a multi-echelon supply chain | |
US20110010211A1 (en) | Automatically prescribing total budget for marketing and sales resources and allocation across spending categories | |
US20120265571A1 (en) | Matching resources of a securities research department to accounts of the department | |
US20130346162A1 (en) | Prioritizing client accounts | |
US6442554B1 (en) | System and method for generating dependent data | |
US20040205045A1 (en) | Method and system for decision support analysis | |
JP4388248B2 (en) | Optimal portfolio determination method and apparatus | |
US20160253690A1 (en) | System and method for price analysis and optimization | |
US20090132319A1 (en) | Method for generating an asset loading plan | |
US7167873B2 (en) | Visual-modeling technique for use in implementing a database system | |
US7028000B1 (en) | Estimating base sales volume using a low-pass filter approach | |
US20050055194A1 (en) | Migration model | |
US20230289872A1 (en) | System and method for price discovery and price improvement amid combinatorial specifications | |
US11934365B1 (en) | Autonomous supply chain data hub and platform | |
Sudharma et al. | Neoj4 and SARIMAX Model for Optimizing Product Placement and Predicting the Shortest Shopping Path | |
US20240020627A1 (en) | Sparse Data Driven Inventory Intelligence for Optimizing Traditional Trade | |
Tyrychtr et al. | Multi-agent system in smart econometric environment |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: I2 TECHNOLOGIES, INC., TEXAS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:KOOTALE, KRISHNADAS C.;REEL/FRAME:011669/0380 Effective date: 20010327 |
|
AS | Assignment |
Owner name: I2 TECHNOLOGIES US, INC., TEXAS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:I2 TECHNOLOGIES, INC.;REEL/FRAME:012037/0834 Effective date: 20010701 |
|
FPAY | Fee payment |
Year of fee payment: 4 |
|
AS | Assignment |
Owner name: WELLS FARGO CAPITAL FINANCE, LLC, AS AGENT, CALIFORNIA Free format text: PATENT SECURITY AGREEMENT;ASSIGNOR:JDA TECHNOLOGIES US, INC.;REEL/FRAME:026072/0353 Effective date: 20110318 Owner name: WELLS FARGO CAPITAL FINANCE, LLC, AS AGENT, CALIFO Free format text: PATENT SECURITY AGREEMENT;ASSIGNOR:JDA TECHNOLOGIES US, INC.;REEL/FRAME:026072/0353 Effective date: 20110318 |
|
AS | Assignment |
Owner name: JDA TECHNOLOGIES US, INC, TEXAS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:I2 TECHNOLOGIES US, INC;REEL/FRAME:026468/0119 Effective date: 20100205 |
|
AS | Assignment |
Owner name: JDA SOFTWARE GROUP, INC., ARIZONA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:JDA TECHNOLOGIES US, INC.;REEL/FRAME:026740/0676 Effective date: 20110524 Owner name: JDA SOFTWARE GROUP, INC, ARIZONA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:JDA TECHNOLOGIES US, INC;REEL/FRAME:026740/0676 Effective date: 20110524 |
|
AS | Assignment |
Owner name: JDA TECHNOLOGIES US, INC., ARIZONA Free format text: RELEASE OF SECURITY INTEREST IN PATENT COLLATERAL;ASSIGNOR:WELLS FARGO CAPITAL FINANCE, LLC;REEL/FRAME:029529/0812 Effective date: 20121221 |
|
AS | Assignment |
Owner name: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, NEW YORK Free format text: FIRST LIEN PATENT SECURITY AGREEMENT;ASSIGNOR:JDA SOFTWARE GROUP, INC.;REEL/FRAME:029556/0697 Effective date: 20121221 Owner name: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, NEW YORK Free format text: FIRST LIEN PATENT SECURITY AGREEMENT;ASSIGNOR:JDA SOFTWARE GROUP, INC.;REEL/FRAME:029556/0809 Effective date: 20121221 |
|
REMI | Maintenance fee reminder mailed | ||
FPAY | Fee payment |
Year of fee payment: 8 |
|
SULP | Surcharge for late payment |
Year of fee payment: 7 |
|
AS | Assignment |
Owner name: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT, ILLINOIS Free format text: SECURITY AGREEMENT;ASSIGNORS:RP CROWN PARENT, LLC;RP CROWN HOLDING LLC;JDA SOFTWARE GROUP, INC.;REEL/FRAME:040326/0449 Effective date: 20161012 Owner name: JDA SOFTWARE GROUP, INC., ARIZONA Free format text: RELEASE OF SECURITY INTEREST IN PATENTS AT REEL/FRAME NO. 29556/0697;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:040337/0053 Effective date: 20161012 Owner name: JDA SOFTWARE GROUP, INC., ARIZONA Free format text: RELEASE OF SECURITY INTEREST IN PATENTS AT REEL/FRAME NO. 29556/0809;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:040337/0356 Effective date: 20161012 Owner name: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT, IL Free format text: SECURITY AGREEMENT;ASSIGNORS:RP CROWN PARENT, LLC;RP CROWN HOLDING LLC;JDA SOFTWARE GROUP, INC.;REEL/FRAME:040326/0449 Effective date: 20161012 |
|
FEPP | Fee payment procedure |
Free format text: MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.) |
|
LAPS | Lapse for failure to pay maintenance fees |
Free format text: PATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.) |
|
STCH | Information on status: patent discontinuation |
Free format text: PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362 |
|
FP | Lapsed due to failure to pay maintenance fee |
Effective date: 20180117 |
|
AS | Assignment |
Owner name: JDA TECHNOLOGIES US, INC., TEXAS Free format text: CORRECTIVE ASSIGNMENT TO CORRECT THE NAME OF THE CONVEYING AND RECEIVING PARTIES TO INCLUDE A PERIOD AFTER THE TERM INC PREVIOUSLY RECORDED ON REEL 026468 FRAME 0199. ASSIGNOR(S) HEREBY CONFIRMS THE CHANGE OF NAME FROM I2 TECHNOLOGIES US, INC. TO JDA TECHNOLOGIES US, INC.;ASSIGNOR:I2 TECHNOLOGIES US, INC.;REEL/FRAME:055136/0623 Effective date: 20100205 |
|
AS | Assignment |
Owner name: JDA SOFTWARE GROUP, INC., ARIZONA Free format text: CORRECTIVE ASSIGNMENT TO CORRECT THE NAME OF THE CONVEYING AND RECEIVING PARTIES TO INCLUDE A PERIOD AFTER THE TERM INC PREVIOUSLY RECORDED AT REEL: 026740 FRAME: 0676. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT;ASSIGNOR:JDA TECHNOLOGIES US, INC.;REEL/FRAME:055257/0747 Effective date: 20110524 |
|
AS | Assignment |
Owner name: JDA TECHNOLOGIES US, INC., TEXAS Free format text: CORRECTIVE ASSIGNMENT TO CORRECT THE REEL 026468 FRAME NUMBER FROM 0199 TO 0119 PREVIOUSLY RECORDED ON REEL 055136 FRAME 0623. ASSIGNOR(S) HEREBY CONFIRMS THE CORRECTION ASSIGNMENT;ASSIGNOR:I2 TECHNOLOGIES US, INC.;REEL/FRAME:056813/0110 Effective date: 20100205 |
|
AS | Assignment |
Owner name: BY BENELUX HOLDING, INC., ARIZONA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:JPMORGAN CHASE BANK, N.A.;REEL/FRAME:057724/0593 Effective date: 20210916 Owner name: BY NETHERLANDS HOLDING, INC., ARIZONA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:JPMORGAN CHASE BANK, N.A.;REEL/FRAME:057724/0593 Effective date: 20210916 Owner name: BY BOND FINANCE, INC., ARIZONA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:JPMORGAN CHASE BANK, N.A.;REEL/FRAME:057724/0593 Effective date: 20210916 Owner name: REDPRAIRIE SERVICES CORPORATION, ARIZONA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:JPMORGAN CHASE BANK, N.A.;REEL/FRAME:057724/0593 Effective date: 20210916 Owner name: JDA SOFTWARE RUSSIA HOLDINGS, INC., ARIZONA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:JPMORGAN CHASE BANK, N.A.;REEL/FRAME:057724/0593 Effective date: 20210916 Owner name: REDPRAIRIE COLLABORATIVE FLOWCASTING GROUP, LLC, ARIZONA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:JPMORGAN CHASE BANK, N.A.;REEL/FRAME:057724/0593 Effective date: 20210916 Owner name: MANUGISTICS HOLDINGS DELAWARE II, INC., ARIZONA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:JPMORGAN CHASE BANK, N.A.;REEL/FRAME:057724/0593 Effective date: 20210916 Owner name: MANUGISTICS SERVICES, INC., ARIZONA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:JPMORGAN CHASE BANK, N.A.;REEL/FRAME:057724/0593 Effective date: 20210916 Owner name: I2 TECHNOLOGIES INTERNATIONAL SERVICES, LLC, ARIZONA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:JPMORGAN CHASE BANK, N.A.;REEL/FRAME:057724/0593 Effective date: 20210916 Owner name: JDA SOFTWARE SERVICES, INC., ARIZONA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:JPMORGAN CHASE BANK, N.A.;REEL/FRAME:057724/0593 Effective date: 20210916 Owner name: BLUE YONDER, INC., ARIZONA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:JPMORGAN CHASE BANK, N.A.;REEL/FRAME:057724/0593 Effective date: 20210916 Owner name: BLUE YONDER GROUP, INC., ARIZONA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:JPMORGAN CHASE BANK, N.A.;REEL/FRAME:057724/0593 Effective date: 20210916 |