Patent Grant
11829928
The present disclosure relates to systems and techniques for integrating and processing database-stored data for identifying geographic clusters of information and displaying such data in interactive user interfaces.
Generally, distributors receive shipments of items and are tasked with routing the items to multiple warehouses. In turn, each warehouse is tasked with routing the items to an appropriate set of entities that offer the items to users. The number of entities that offer items to users can number in the tens of thousands to the hundreds of thousands, and so ensuring that shipments are routed to the correct locations can be very complicated. Thus, the distributors, the warehouses, and the entities that offer items to users may utilize a complex and detailed shipment routing system.
Often, different entities manage data that can be useful in analyzing the shipment of items via the shipment routing system. Thus, such data may be stored in multiple, and often incompatible, databases. Given the disparate sources of data, it can be difficult for a user to gather such data and view the information in a user interface.
The systems, methods, and devices described herein each have several aspects, no single one of which is solely responsible for its desirable attributes. Without limiting the scope of this disclosure, several non-limiting features will now be discussed briefly.
Disclosed herein are various systems and methods for integrating data from disparate sources to identify shipment misalignments and displaying such information in interactive user interfaces. For example, the systems described herein can define various geographic regions using location and census data and identify the defined geographic regions in which stores are located. Using shipment data and micro-market data, the systems described herein can then identify the geographic regions that items are shipped to, identify the demand for such items in the geographic regions, and determine whether the quantity of items shipped to the geographic regions is appropriate based on the demand. Such information can be displayed in an interactive user interface that allows a user to view the geographic clustering of item demand, identify potential opportunities for correcting shipment misalignment, and/or correct identified shipment misalignments.
One aspect of the disclosure provides a computer-implemented method of accessing one or more databases in order to determine information related to the routing of an item and providing the determined information to a user in an interactive user interface. The computer-implemented method comprises: retrieving geographic data associated with a plurality of first geographic regions from a first database in the one or more databases; for each first geographic region, determining a first location representing a center of the respective first geographic region based on the retrieved geographic data; retrieving population data associated with a plurality of second geographic regions from a second database in the one or more databases; for each first geographic region, identifying one or more second geographic regions within a first distance of the center of the respective first geographic region based on the population data, and modifying the respective first geographic region to be a shape of the identified one or more second geographic regions and at a set of geographic locations defined by the identified one or more second geographic regions; generating user interface data for rendering the interactive user interface on a computing device, the interactive user interface including graphical representations of the plurality of first geographic regions; receiving a selection of a first graphical representation of one first geographic region in the plurality of first geographic regions; and modifying the user interface data such that the interactive user interface displays shipment misalignment data associated with the one first geographic region represented by the first graphical representation.
The computer-implemented method of the preceding paragraph can have any sub-combination of the following features: where the geographic data comprises a list of cities and a list of states; where determining, for each first geographic region, a first location representing a center of the respective first geographic region further comprises, for each first geographic region: generating combinations of cities and states using the list of cities and the list of states, selecting a first set of combinations of cities and states from the generated combinations of cities and states, calculating an average based on a geographic location of each combination of city and state in the first set, and determining the first location based on a location associated with the calculated average; where the plurality of second geographic regions correspond to a plurality of census tracts, and where the population data comprises at least one of a size or location of each census tract in the plurality of census tracts; where identifying one or more second geographic regions within a first distance of the center further comprises identifying one or more census tracts associated with a geographic location that is within the first distance of the first location; where the graphical representations of the plurality of the first geographic regions are each shaded a color corresponding to a demand for the item in the respective first geographic region; where a first category of items is a subcategory of a second category of items, and where the method further comprises: determining, for the one first geographic region, a first percentage of sales of the second category of items that are sales of the first category of items using micro-market data stored in a third database in the one or more databases, determining, for the one first geographic region, a second percentage of shipments of the second category of items to the one first geographic region that are shipments of the first category of items using shipment data stored in a fourth database in the one or more databases, and generating an opportunity score that indicates shipment misalignment has occurred in response to a determination that the first percentage is greater than the second percentage; where the displayed shipment misalignment data comprises the opportunity score; where a third category of items is a second subcategory of the second category of items, and where the method further comprises: receiving a selection of the third category of items, determining, for the one first geographic region, a third percentage of sales of the second category of items that are sales of the third category of items using the micro-market data, determining, for the one first geographic region, a fourth percentage of shipments of the second category of items to the one first geographic region that are shipments of the third category of items using the shipment data, generating a second opportunity score that indicates shipment misalignment has occurred in response to a determination that the third percentage is greater than the fourth percentage, and modifying the user interface data such that the shipment misalignment data comprises the second opportunity score; where the method further comprises retrieving shipment data associated with the one first geographic region from a third database in the one or more databases, where the shipment data comprises an amount of the item shipped to the one first geographic region; and where the method further comprises modifying the user interface data such that the interactive user interface includes a selectable option to ship additional items to the one first geographic region in response to a determination that the amount of the item shipped to the one first geographic region does not exceed a threshold value.
Another aspect of the disclosure provides a computer-implemented method for routing an item to a geographic location. The computer-implemented method comprises: retrieving geographic data associated with a plurality of first geographic regions; for each first geographic region, determining a first location representing a center of the first geographic region based on the retrieved geographic data; retrieving population data associated with a plurality of second geographic regions; for each first geographic region, identifying one or more second geographic regions within a first distance of the center of the respective first geographic region based on the population data, and modifying the respective first geographic region to be a shape of the identified one or more second geographic regions and at a set of geographic locations defined by the identified one or more second geographic regions; determining a representation of a geographic location of an entity; identifying one first geographic region in the plurality of first geographic regions associated with the determined representation; retrieving shipment data associated with the entity, where the shipment data comprises an amount of the item shipped to the entity; and generating an instruction to ship additional items to the entity in response to a determination that the amount of the item shipped to the entity does not exceed a threshold value.
The computer-implemented method of the preceding paragraph can have any sub-combination of the following features: where the method further comprises retrieving item data from a third database in the one or more databases, where the item data indicates a likelihood that the item is procured in individual first geographic regions; and where the method further comprises generating user interface data for rendering an interactive user interface on a computing device, the interactive user interface including graphical representations of the plurality of first geographic regions, where the graphical representations are shaded based on the retrieved item data.
Accordingly, in various embodiments, large amounts of data are automatically and dynamically calculated interactively in response to user inputs, and the calculated data is efficiently and compactly presented to a user by the systems disclosed herein. Thus, in some embodiments, the user interfaces described herein are more efficient as compared to previous user interfaces in which data is not dynamically updated and compactly and efficiently presented to the user in response to interactive inputs.
Further, as described herein, the systems disclosed herein may be configured and/or designed to generate user interface data useable for rendering the various interactive user interfaces described. The user interface data may be used by the systems disclosed herein, and/or another computer system, device, and/or software program (e.g., a browser program), to render the interactive user interfaces. The interactive user interfaces may be displayed on, for example, electronic displays (including, for example, touch-enabled displays).
Additionally, it has been noted that design of computer user interfaces “that are useable and easily learned by humans is a non-trivial problem for software developers.” (Dillon, A. (2003) User Interface Design. MacMillan Encyclopedia of Cognitive Science, Vol. 4, London: MacMillan, 453-458.) The various embodiments of interactive and dynamic user interfaces of the present disclosure are the result of significant research, development, improvement, iteration, and testing. This non-trivial development has resulted in the user interfaces described herein which may provide significant cognitive and ergonomic efficiencies and advantages over previous systems. The interactive and dynamic user interfaces include improved human-computer interactions that may provide reduced mental workloads, improved decision-making, reduced work stress, and/or the like, for a user. For example, user interaction with the interactive user interfaces described herein may provide an optimized display of time-varying report-related information and may enable a user to more quickly access, navigate, assess, and digest such information than previous systems.
Further, the interactive and dynamic user interfaces described herein are enabled by innovations in efficient interactions between the user interfaces and underlying systems and components. For example, disclosed herein are improved methods of receiving user inputs, translation and delivery of those inputs to various system components, automatic and dynamic execution of complex processes in response to the input delivery, automatic interaction among various components and processes of the system, and automatic and dynamic updating of the user interfaces. The interactions and presentation of data via the interactive user interfaces described herein may accordingly provide cognitive and ergonomic efficiencies and advantages over previous systems.
Various embodiments of the present disclosure provide improvements to various technologies and technological fields. For example, as described herein, existing technology for viewing the clustering of item demand by geographic region (including, e.g., electronic mapping systems) is limited in various ways (e.g., data is missing because data is stored and managed by different entities, image rendering is slow and cumbersome, comparison of geographic regions is inefficient, etc.), and various embodiments of the disclosure provide significant improvements over such technology. Additionally, various embodiments of the present disclosure are inextricably tied to computer technology. In particular, various embodiments rely on detection of user inputs via graphical user interfaces, calculation of updates to displayed electronic data based on those user inputs, automatic processing of related shipment, census, location, and/or micro-market data to determine item demand and/or shipment misalignment in various geographic regions, and presentation of the updates to the determined item demand and/or shipment misalignment in the various geographic regions via interactive graphical user interfaces. Such features and others (e.g., the generation and display of shipment geographic regions, the determination of which shipment geographic region a store is located within, etc.) are intimately tied to, and enabled by, computer technology, and would not exist except for computer technology. For example, the interactions with displayed data described below in reference to various embodiments (e.g., the selection of various distributors or warehouses to view additional information, the selection of various shipment geographic regions to view locations of stores, warehouses, and/or distributors and shipment misalignment information, etc.) cannot reasonably be performed by humans alone, without the computer technology upon which they are implemented. Further, the implementation of the various embodiments of the present disclosure via computer technology enables many of the advantages described herein, including more efficient generation of, interaction with, and presentation of, shipment misalignment information.
Overview
Generally, consumer packaged goods companies (e.g., food and beverage companies) do not control the sale of items directly to users. Rather, consumer packaged goods companies handle the marketing and distribution to retailers (e.g., department stores, grocery stores, drug stores, mass merchandiser stores, dollar stores, supercenters, club stores, commissaries, convenience stores, etc.) and the retailers offer items directly to users. Thus, consumer packaged goods companies often rely on retailers to drive revenue. Accordingly, it may be very important for such consumer packaged goods companies to not only ensure that shipments arrive at a chosen location (e.g., via a shipment routing system), but also to determine whether a shipment should even be sent to a particular location in the first place.
For example, certain items may be popular in some geographic locations and not popular in other geographic locations. However, while a certain item may be popular in a particular geographic location, stores located in the particular geographic location may not be receiving a sufficient quantity of the items or any at all. Thus, there may be an opportunity for consumer packaged goods companies to increase revenue by analyzing item demand and routing a larger quantity of items to one geographic location and/or routing a smaller quantity of items to another geographic location. This potential mismatch between a quantity of items that represents the demand for the item in a geographic location and the actual quantity of the items shipped to a store in the geographic location is referred to herein as “shipment misalignment.”
However, as referenced above, different entities may manage data that can be useful in determining whether an appropriate quantity of items is being routed to any given geographic location. For example, shipment data (e.g., the quantity of items shipped by distributors to various stores via warehouses), location data (e.g., data defining the different geographic regions in which stores are located), census data (e.g., population data, the size and location of census tracts (e.g., statistical subdivisions of a county or equivalent entity), etc.), and/or micro-market data (e.g., point of sale (POS) data identifying the sales of items by retailers in various geographic regions) can, in aggregate, be useful in determining whether there is shipment misalignment in one or more geographic regions. This data, though, may originate from disparate sources. Shipment data may be collected and stored in databases operated by the distributors, location data may be generated by private entities using information about stores (e.g., the geographic location of a store, the type of store, etc.), census data may be tabulated by the government, and micro-market data may be generated by private entities based on sales data received from retailers in various channels (e.g., food/grocery, drug, mass merchandiser, supercenter, club, dollar, commissary, convenience, etc.). Because the data is not cohesive and integrated, it can be difficult to construct a system that can visualize the clustering of item demand by geographic region and/or shipment misalignment in, for example, a single interactive user interface.
In fact, additional issues may hamper the visualization of such information in a single interactive user interface. For example, the micro-market data may be incomplete. The micro-market data may include information detailing the sales of items in some channels (e.g., food/grocery, drug, mass merchandiser, supercenter, club, dollar, and commissary, which can be defined collectively as eXtended All Outlet Combined (xAOC) or MULti Outlet (MULO)), but not in other channels (e.g., convenience). Data from convenience stores may be missing, for example, because many convenience stores may be individually owned and it would require great effort to identify and reach out to each of these stores to obtain sales data. Grocery stores, drug stores, and the like, on the other hand, may be part of larger corporate entities and thus it may be easier to obtain sales data. Even if the data was integrated, the incomplete micro-market data could make the display of accurate information a challenging endeavor to overcome.
Accordingly, disclosed herein are various systems and methods for integrating data from disparate sources to identify shipment misalignments and displaying such information in interactive user interfaces. For example, a shipment misalignment detection server can define various geographic regions using location and census data and identify the defined geographic regions in which stores are located. Using shipment data and micro-market data, the shipment misalignment detection server can then identify the geographic regions that items are shipped to, identify the demand for such items in the geographic regions, and determine whether the quantity of items shipped to the geographic regions is appropriate based on the demand. The shipment misalignment detection server can generate an interactive user interface for displaying such information, where the interactive user interface allows a user to view the geographic clustering of item demand, identify potential opportunities for correcting shipment misalignment, and/or correct identified shipment misalignments.
In an embodiment, the shipment misalignment detection server can function as described herein even if the micro-market data is incomplete. For example, while the demand for a certain item can vary across markets and regions, the demand for a certain item is generally consistent across channels in the same market or region. Thus, if the micro-market data includes information provided by xAOC stores and not convenience stores, this information nonetheless can be linked to and associated with convenience stores. Accordingly, if the shipment misalignment detection server is directed by a user to specifically analyze shipments to convenience stores, the shipment misalignment detection server can still use the micro-market data to complete the analysis.
Exemplary System Overview
In an embodiment, the shipment routing system 130, the shipment misalignment detection server 140, the shipment data store 150, the census data store 152, the location data store 154, and the micro-market data store 156 communicate via a network 120. In other embodiments, the functionality of the shipment routing system 130 and the shipment misalignment detection server 140 may be combined into a single computing system, such as a server or series of servers. Similarly, the functionality is disclosed with reference to these components may be distributed to other computing devices and/or partially performed by multiple computing devices.
The shipment data store 150 is configured to store shipment data for a plurality of distributors. The shipment data can include the quantity of shipped items and the locations to where the items are shipped (e.g., the physical addresses of warehouses and/or stores that receive shipments). The shipment data store 150 can include multiple entries for each distributor. For example, each entry may be associated with a different type of item shipped by the respective distributor. The shipment data store 150 can be managed by one or more distributors. While a single shipment data store 150 is illustrated in
The census data store 152 is configured to store census data for a large geographic region (e.g., a state, a province, a country, etc.). The census data can include population data (e.g., a count of the number of persons living in the large geographic region or in one or more sub-regions), the size and location of census tracts (e.g., statistical subdivisions of a county or equivalent entity), and/or the like. The census data store 152 can be managed by a government agency (e.g., the U.S. Census Bureau).
The location data store 154 is configured to store location data for one or more geographic regions (e.g., zones in which stores are present) within a large geographic region. The location data can include information on zones. For example, the location data can include, for each zone, a list of cities and states (e.g., a list of 4 cities and a list of 4 states, resulting in 16 possible combinations of cities and states) that define the respective zone. In some embodiments, a zone is defined by the number and/or variety of types of stores located within the zone. For example, zones may each include a similar number and/or variety of types of stores. The location data store 154 can be managed by one or more private entities. While a single location data store 154 is illustrated in
The micro-market data store 156 is configured to store micro-market data for one or more geographic regions. The micro-market data can include POS data identifying the sales of items by retailers in one or more channels (e.g., food/grocery, drug, mass merchandiser, supercenter, club, dollar, commissary, convenience, etc.) in one or more zones. The micro-market data store 156 can be managed by one or more private entities. While a micro-market data store 156 is illustrated in
The shipment routing system 130 can be a system that controls the distribution of items. For example, the shipment routing system 130 can instruct a distributor to ship an item to a certain warehouse linked to the distributor. Likewise, the shipment routing system 130 can instruct a warehouse to ship an item to a certain store linked to the warehouse. The shipment routing system 130 can receive instructions from the shipment misalignment server 140 to instruct distributors and/or warehouses to ship items to, for example, correct shipment misalignments.
The shipment misalignment detection server 140 may include various modules. For example, the shipment misalignment detection server 140 may include a region generator 142, a geographic entity locator 144, a shipment opportunity identifier 146, and a user interface generator 148. In an embodiment, the region generator 142, the geographic entity locator 144, the shipment opportunity identifier 146, and the user interface generator 148 are each implemented as executable code modules that are stored in the memory of, and executed by the processor(s) of, the shipment misalignment detection server 140. The region generator 142, the geographic entity locator 144, the shipment opportunity identifier 146, and the user interface generator 148 may also be implemented partly or wholly in application-specific hardware.
The region generator 142 may define one or more shipment geographic regions using the location data stored in the location data store 154 and the census data stored in the census data store 152. For example, each shipment geographic region can correspond to a different zone. The region generator 142 can first identify a center location of a shipment geographic region using the location data of the corresponding zone. As described above, the location data can include a list of cities and a list of states for each zone. Using this data for the corresponding zone, the region generator 142 can generate a list of every combination of cities and states from the two lists. Some combinations of cities and states may not be accurate (e.g., the city does not exist in the state) or may be an unlikely combination (e.g., the location of the city and state combination may be a long distance from the locations of the other city and state combinations). Thus, the region generator 142 can rank the combinations of cities and states by accuracy and/or likely combination and drop the lower ranked combinations (e.g., the bottom 12 or 13 combinations). Of the remaining combinations, the region generator 142 can take an average of the geographic locations of the city and state combinations (e.g., take an average of the geographic coordinates of the city and state combinations) and define the average as the location of the center of the shipment geographic region. The region generator 142 can repeat this process for every shipment geographic region to define the center of each shipment geographic region.
As described above, the census data can include the size and location of census tracts. Using the size and/or location information, the region generator 142 can identify one or more census tracts that are located within a vicinity of the center of a first shipment geographic region (e.g., an edge of a census tract is within a threshold distance of the center of the first shipment geographic region). Some or all of the census tracts that are within the vicinity of the center of the first shipment geographic region can be combined by the region generator 142 to form the size, shape, and location of the first shipment geographic region. The region generator 142 can repeat this process for every other shipment geographic region to define the size, shape, and location of the other shipment geographic regions. As described below in greater detail with respect to
The geographic entity locator 144 may use the defined shipment geographic regions to identify the stores and/or warehouses that are located within each defined shipment geographic region. For example, the geographic entity locator 144 can use the shipment data from the shipment data store 150 to generate geohashes for each store and/or warehouse (e.g., convert the physical addresses of stores and/or warehouses that receive shipments into geographic coordinates, such as latitude and longitude). The geographic entity locator 144 can then compare the geographic coordinates of a store or warehouse with the representations of the size, shape, and location of various shipment geographic regions to identify the shipment geographic region a store or warehouse is located within. The process by which the geographic entity locator 144 performs the comparison is described in greater detail below with respect to
Once the locations of stores and/or warehouses within shipment geographic regions have been identified, the shipment opportunity identifier 146 can determine in which shipment geographic regions shipment misalignment may be present. For example, the shipment opportunity identifier 146 may be directed (e.g., by a user) to analyze a specific subcategory of items, such as items (e.g., fruits, shoes, candy, etc.) associated with a specific or seasonal time of the year (e.g., Valentine's Day, Easter, Independence Day, Halloween, Thanksgiving, Christmas, etc.). The shipment opportunity identifier 146 can use micro-market data from the micro-market data store 156 to identify POS data for the specific subcategory of items within the zones. Because the zones correspond to the shipment geographic regions, the shipment opportunity identifier 146 can associate the POS data with the shipment geographic regions. Thus, the shipment opportunity identifier 146 has identified the POS data for the specific subcategory of items within the shipment geographic regions.
To determine the demand for the specific subcategory of items within the shipment geographic regions, the shipment opportunity identifier 146 can use the POS data to calculate, for each shipment geographic region, the percentage of sales of a category of items that are sales of the specific subcategory of items. For example, if the subcategory of items is Halloween candy, then the shipment opportunity identifier 146 may calculate the percentage of all candy sales within a first shipment geographic region that are Halloween candy sales. The shipment opportunity identifier 146 may repeat this calculation for some or all shipment geographic regions. In an embodiment, the calculation is restricted to a specific time period (e.g., provided by a user via the interactive user interface).
The shipment opportunity identifier 146 can rank and/or group the percentages associated with the different shipment geographic regions to identify shipment geographic regions in which the specific subcategory of items is popular and regions in which the specific subcategory of items is not popular. Such information can be provided by the shipment opportunity identifier 146 to the user interface generator 148 for display in the interactive user interface.
In a further embodiment, the shipment opportunity identifier 146 generates an opportunity score or index associated with some or all stores, warehouses, and/or distributors in the shipment geographic regions. The opportunity score can be a numerical value that represents the degree of shipment misalignment and the amount of opportunity available for correcting such shipment misalignment. For example, the shipment opportunity identifier 146 can compare the popularity of the specific subcategory of items in a shipment geographic region with the actual quantity of these specific subcategory of items shipped to stores in the shipment geographic region (as identified by the shipment data). As described above, the popularity or demand for a subcategory of an item can be represented as a first percentage (e.g., the percentage of the sales of a category of an item that are sales of the subcategory of the item). The shipment opportunity identifier 146 can calculate a second percentage: the percentage of the shipments of a category of an item to a store (or warehouse or distributor) that include the subcategory of the item. If the first percentage is greater than the second percentage, then the shipment opportunity identifier 146 can determine that the store (or warehouse or distributor) is underserved (e.g., a larger quantity of the subcategory of the item should be shipped to the location to meet demand) and can assign the store (or warehouse or distributor) a higher opportunity score (where the score is higher the greater the difference between the percentages). Likewise, if the first percentage is less than or equal to the second percentage, then the shipment opportunity identifier 146 can determine that the store (or warehouse or distributor) is overserved or properly served and can assign the store (or warehouse or distributor) a lower opportunity score. The opportunity scores can be provided by the opportunity identifier 146 to the user interface generator 148 for display in the interactive user interface.
In still further embodiments, the shipment opportunity identifier 146 can generate instructions (e.g., at the request of the user) for correcting any shipment misalignment and transmit such instructions to the shipment routing system 130. The shipment routing system 130 can then adjust the shipment of items to distributors, warehouses, and/or stores accordingly.
The user interface generator 148 may generate an interactive user interface that displays the information provided by the region generator 142, the geographic entity locator 144, and/or the shipment opportunity identifier 146. For example, the user interface generator 146 may generate one or more tables that include store, warehouse, and/or distributor information (e.g., sales information, shipments of specific subcategories of items, opportunity scores, etc.), an interactive map that displays shipment geographic regions, the stores, warehouses, and/or distributors located in the shipment geographic regions, and a comparison of the demand for items in different shipment geographic regions (e.g., the clustering of item demand by geographic region). The contents of the interactive user interface are described in greater detail below with respect to
The shipment misalignment detection server 140 may be implemented as a special-purpose computer system having logical elements. In an embodiment, the logical elements may comprise program instructions recorded on one or more machine-readable storage media. Alternatively, the logical elements may be implemented in hardware, firmware, or a combination thereof. In one embodiment, the shipment misalignment detection server 140 may be implemented in a Java Virtual Machine (JVM) that is executing in a distributed or non-distributed computer system. In other embodiments, the shipment misalignment detection server 140 may be implemented as a combination of programming instructions written in any programming language (e.g. C++, Visual Basic, Python, etc.) and hardware components (e.g., memory, CPU time) that have been allocated for executing the program instructions.
A user may use the user device 160 to view and interact with the interactive user interface generated by the user interface generator 148. For example, the user device 160 may be in communication with the shipment misalignment detection server 140 via a network (not shown). The user device 160 can include a wide variety of computing devices, including personal computing devices, terminal computing devices, laptop computing devices, tablet computing devices, electronic reader devices, mobile devices (e.g., mobile phones, media players, handheld gaming devices, etc.), wearable devices with network access and program execution capabilities (e.g., “smart watches” or “smart eyewear”), wireless devices, set-top boxes, gaming consoles, entertainment systems, televisions with network access and program execution capabilities (e.g., “smart TVs”), and various other electronic devices and appliances. The user devices 160 may execute a browser application to communicate with the shipment misalignment detection server 140.
In an embodiment, the network 120 includes any communications network, such as the Internet. The network 120 may be a wired network, a wireless network, or a combination of the two. For example, network 120 may be a local area network (LAN) and/or a wireless area network (WAN).
Example Shipment Geographic Region and Shape Definition
Furthermore, as described above, the region generator 142 can use the census data, and specifically one or more census tracts, to define the size, shape, and location of the shipment geographic region 200. For example, the shipment geographic region 200 may comprise census tract 210, 212, 214, 216, and 218. As illustrated in
While the shipment geographic region 200 is illustrated as having 9 sides, this is not meant to be limiting. Shipment geographic regions can have any number of edges or sides and be any size or shape or be located in any location.
Like the shipment geographic region 200, many shipment geographic regions may not have a uniform or symmetrical shape. To properly define the geographic coordinates that form the boundary of a shipment geographic region, the region generator 142 can represent the shipment geographic region as a list, table, vector, and/or matrix of geographic coordinates (e.g., combinations of latitude and longitude coordinates).
The second row in the list 250, however, includes two different longitude coordinates. The first entry in the second row is a latitude of 38.12243° N, the second entry in the second row is a longitude of 93.50385° W, and the third entry in the second row is a longitude of 93.95109° W. Thus, if a store is located at a latitude of 38.12243° N and a longitude of 93.60000° W, the store falls within or along the boundary of the shipment geographic region according to the list 250.
The list 250 is merely for illustrative purposes and is not meant to be limiting. The latitude and longitude information can be organized by the region generator 142 in any manner to define the shipment geographic region. For example, the placement of the latitude and longitude coordinates could be flipped such that the first entry in a row is a longitude, the second entry in a row is a first latitude coordinate that represents the first latitude coordinate in a range of latitude coordinates associated with the longitude and a second latitude coordinate that represents the last latitude coordinate in the range of latitude coordinates.
Example Flow Diagram for Identifying the Location of a Store
The operation 300 begins at block 302, where geographic coordinates of an entity are retrieved. The entity can be a store, warehouse, or distributor. For example, the physical address of the entity can be retrieved from the shipment data store 150. The geographic entity locator 144 can then convert the physical address into geographic coordinates.
At block 304, variable i is set equal to 1. Variable i represents a shipment geographic region.
At block 306, variable n is set equal to the total number of shipment geographic regions (e.g., 500, 2000, etc.). The total number of shipment geographic regions may correspond to the number of zones.
At block 308, geographic coordinates of region i are retrieved. As described above with respect to
At block 310, the operation 300 determines whether the latitude of the entity is listed in the geographic coordinates of region i. For example, the operation 300 determines whether the first entry of any of the rows in the list 250 includes the latitude of the entity. If the latitude of the entity is listed in the geographic coordinates of region i, then the operation 300 proceeds to block 318. Otherwise, the operation 300 proceeds to block 312.
At block 312, the operation 300 determines whether variable i is equal to variable n. In other words, the operation 300 determines whether all shipment geographic regions have been analyzed to determine in which shipment geographic region the entity is located. If variable i is not equal to variable n (e.g., not all shipment geographic regions have been analyzed), then the operation 300 proceeds to block 314. Otherwise, the operation 300 proceeds to block 316 and stops.
At block 314, variable i is incremented by one. The operation 300 then proceeds back to block 308 so that a new region i can be analyzed and blocks 310, 312, 314, and/or 318 can be repeated.
At block 318, the operation 300 determines whether the longitude of the entity is listed within the range of longitude coordinates of region i associated with the latitude of the entity. For example, the operation 300 determines whether the longitude of the entity falls within the range of longitude coordinates defined by the second entry and the third entry of the row in the list 250 that includes the latitude of the entity as the first entry. If the longitude of the entity falls within the range, then the operation 300 proceeds to block 320. Otherwise, the operation 300 proceeds to block 312.
At block 320, the entity is linked with region i. In other words, the geographic entity locator 144 has determined that the entity is located within or on the boundaries of the region i. The operation 300 then proceeds to block 316 and stops. In some embodiments, the operation 300 is repeated for some or all available entities.
Examples of Shipment Misalignment Data Displayed in an Interactive User Interface
As illustrated in
Selection of a subcategory (e.g., Halloween in this case) causes the user interface 400 to display various information for distributors listed in the table 412, as illustrated in
Furthermore selection of a subcategory causes the user interface 400 to display representations of shipment geographic regions 431-435 in the map 430. While
The download button 415, when selected, can be used to save locally a copy of the information displayed in the table 412. The sort button 420, when selected, can be used to sort the information displayed in the table 412 (e.g., alphabetically by distributor, by opportunity index, by total shipments, etc.).
Any of the distributors listed in the table 412 can be selected to view additional information. For example, if DIST. Y is selected using the cursor 450, the user interface 400 displays the opportunity size (e.g., the potential increase in revenue if additional items in the subcategory are shipped to warehouses and/or stores by the distributor, calculated based on the opportunity index), the current seasonal shipment (e.g., the amount of the items in the subcategory that are currently shipped), the number of stores unserved (e.g., the number of stores of the distributor multiplied by the percent of stores unserved), and the sales representative of DIST. Y in window 440, as illustrated in
Furthermore, the user can scroll down from the table 412 to view the map 430 in greater detail, as illustrated in
In an embodiment, the map 430 is interactive and the user can select a shipment geographic region to view additional information. For example, a selection of the shipment geographic region 435 provides an expanded view of the shipment geographic region 435 in the user interface 400, as illustrated in
Once a distributor is selected in
The table 462 is interactive and selection of a warehouse via the cursor 450 causes the user interface 400 to display additional information, as illustrated in
As illustrated in
In further embodiments, not shown, the user interface 400 provides the user with the functionality to generate instructions for the shipment routing system 130. For example, the user can select any distributor, warehouse, and/or store and be provided with a window that allows the user to define an instruction (e.g., increase the shipment of an item in a subcategory to a specific store by a certain amount) or select an instruction generated automatically based on the distributor, warehouse, and/or store information provided in tables 412, 462, and/or 472. Once completed, the shipment misalignment detection server 140 can forward the instruction to the shipment routing system 130 via the network 120.
In some embodiments, the shipment opportunity identifier 146 causes the user interface generator 148 to generate and/or display an alert and/or notification when shipment misalignment is detected. The alert and/or notification can be automatically transmitted by the shipment misalignment detection server 140 to the user device 160 for the benefit of a user associated with the alert and/or notification. The alert and/or notification can be transmitted at the time that the alert and/or notification is generated or at some determined time after generation of the alert and/or notification. When received by the user device 160, the alert and/or notification can cause the user device 160 to display the alert and/or notification via the activation of an application on the user device 160 (e.g., a browser, a mobile application, etc.). For example, receipt of the alert and/or notification may automatically activate an application on the user device 160, such as a messaging application (e.g., SMS or MMS messaging application), a standalone application (e.g., a shipment data monitoring application), or a browser, for example, and display information included in the alert and/or notification. If the user device 160 is offline when the alert and/or notification is transmitted, the application may be automatically activated when the user device 160 is online such that the alert and/or notification is displayed. As another example, receipt of the alert and/or notification may cause a browser to open and be redirected to a login page generated by the shipment misalignment detection server 140 so that the entity can log in to the shipment misalignment detection server 140 and view the alert and/or notification. Alternatively, the alert and/or notification may include a URL of a webpage (or other online information) associated with the alert and/or notification, such that when the user device 160 (e.g., a mobile device) receives the alert, a browser (or other application) is automatically activated and the URL included in the alert and/or notification is accessed via the Internet.
Example Process Flows
At block 502, geographic data associated with a plurality of first geographic regions is retrieved. For example, the first geographic regions can be zones and the retrieved data can include the lists of cities and the lists of states that define the zones.
At block 504, for each first geographic region, a first location is determined that represents a center of the respective first geographic region. For example, the center can be determined by identifying possible combinations of cities and states from the two lists and taking an average of the geographic locations of some of the possible combinations.
At block 506, population data associated with a plurality of second geographic regions is retrieved. The retrieved population data may include the size and location of census tracts.
At block 508, for each first geographic region, a shape of the respective first geographic region is modified using the population data. For example, census tracts that are located within a vicinity of the center of the respective first geographic region can be combined to form the size, shape, and location of the respective first geographic region (e.g., where the first geographic regions are now shipment geographic regions).
At block 510, a user interface for rendering an interactive user interface is generated, where the interactive user interface includes graphical representations of the first geographic regions. In an embodiment, the graphical representations are shaded to indicate a demand for an item or a subcategory of an item in the first geographic regions.
At block 512, a selection of a first graphical representation is received. In an embodiment, selection of the first graphical representation causes the user interface to display the locations of various stores, warehouses, and/or distributors in the first geographic region associated with the first graphical representation.
At block 514, shipment misalignment data associated with the first geographic region is displayed. For example, the user can select a store or warehouse in the first geographic region, which causes the user interface to display shipment misalignment data, such as the opportunity index and/or other information provided in tables 412, 462, and/or 472.
At block 602, geographic data associated with a plurality of first geographic regions is retrieved. For example, the first geographic regions can be zones and the retrieved data can include the lists of cities and the lists of states that define the zones.
At block 604, for each first geographic region, a first location is determined that represents a center of the respective first geographic region. For example, the center can be determined by identifying possible combinations of cities and states from the two lists and taking an average of the geographic locations of some of the possible combinations.
At block 606, population data associated with a plurality of second geographic regions is retrieved. The retrieved population data may include the size and location of census tracts.
At block 608, for each first geographic region, a shape of the respective first geographic region is modified using the population data. For example, census tracts that are located within a vicinity of the center of the respective first geographic region can be combined to form the size, shape, and location of the respective first geographic region (e.g., where the first geographic regions are now shipment geographic regions).
At block 610, a representation of a geographic location of an entity is determined. For example, the representation can be a set of geographic coordinates.
At block 612, one first geographic region in the plurality of first geographic regions associated with the determined representation is identified. For example, the boundaries of the one first geographic region can be defined by a list of geographic coordinates and the determined representation of the geographic location of the entity can be associated with this one first geographic region if the determined representation falls within the range of geographic coordinates included in the list.
At block 614, shipment data associated with the entity is retrieved, where the shipment data includes an amount of the item shipped to the entity.
At block 616, an instruction is generated to ship additional items to the entity in response to a determination that the amount of the item shipped to the entity is below a threshold value. For example, the instruction can be generated if the amount of the items shipped to the entity is below an amount that represents the demand of the item in the first geographic region of the entity.
Implementation Mechanisms
According to one embodiment, the techniques described herein are implemented by one or more special-purpose computing devices. The special-purpose computing devices may be hard-wired to perform the techniques, or may include digital electronic devices such as one or more application-specific integrated circuits (ASICs) or field programmable gate arrays (FPGAs) that are persistently programmed to perform the techniques, or may include one or more general purpose hardware processors programmed to perform the techniques pursuant to program instructions in firmware, memory, other storage, or a combination. Such special-purpose computing devices may also combine custom hard-wired logic, ASICs, or FPGAs with custom programming to accomplish the techniques. The special-purpose computing devices may be desktop computer systems, server computer systems, portable computer systems, handheld devices, networking devices or any other device or combination of devices that incorporate hard-wired and/or program logic to implement the techniques.
Computing device(s) are generally controlled and coordinated by operating system software, such as iOS, Android, Chrome OS, Windows XP, Windows Vista, Windows 7, Windows 8, Windows Server, Windows CE, Unix, Linux, SunOS, Solaris, iOS, Blackberry OS, VxWorks, or other compatible operating systems. In other embodiments, the computing device may be controlled by a proprietary operating system. Conventional operating systems control and schedule computer processes for execution, perform memory management, provide file system, networking, I/O services, and provide a user interface functionality, such as a graphical user interface (“GUI”), among other things.
For example,
Computer system 700 includes a bus 702 or other communication mechanism for communicating information, and a hardware processor, or multiple processors, 704 coupled with bus 702 for processing information. Hardware processor(s) 704 may be, for example, one or more general purpose microprocessors.
Computer system 700 also includes a main memory 706, such as a random access memory (RAM), cache and/or other dynamic storage devices, coupled to bus 702 for storing information and instructions to be executed by processor 704. Main memory 706 also may be used for storing temporary variables or other intermediate information during execution of instructions to be executed by processor 704. Such instructions, when stored in storage media accessible to processor 704, render computer system 700 into a special-purpose machine that is customized to perform the operations specified in the instructions. Main memory 706 may also store cached data, such as generated shipment geographic regions, identified locations of stores, warehouses, and/or distributors in shipment geographic regions, shipment misalignment data for a selected (and/or unselected) shipment geographic region, zoom levels of viewed shipment geographic regions in a map (e.g., the map 430), and/or the like.
Computer system 700 further includes a read only memory (ROM) 708 or other static storage device coupled to bus 702 for storing static information and instructions for processor 704. A storage device 710, such as a magnetic disk, optical disk, or USB thumb drive (Flash drive), etc., is provided and coupled to bus 702 for storing information and instructions. For example, the storage device 710 may store the size, shape, and location of generated shipment geographic regions, an identification of a shipment geographic region a store, warehouse, and/or distributor is located within, shipment misalignment data, and/or the like.
Computer system 700 may be coupled via bus 702 to a display 712, such as a cathode ray tube (CRT) or LCD display (or touch screen), for displaying information to a computer user. For example, the display 712 can be used to display any of the user interfaces described herein with respect to
Computing system 700 may include a user interface module to implement a GUI that may be stored in a mass storage device as executable software codes that are executed by the computing device(s). This and other modules may include, by way of example, components, such as software components, object-oriented software components, class components and task components, processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, databases, data structures, tables, arrays, and variables.
In general, the word “module,” as used herein, refers to logic embodied in hardware or firmware, or to a collection of software instructions, possibly having entry and exit points, written in a programming language, such as, for example, Java, Lua, C, or C++. A software module may be compiled and linked into an executable program, installed in a dynamic link library, or may be written in an interpreted programming language such as, for example, BASIC, Perl, or Python. It will be appreciated that software modules may be callable from other modules or from themselves, and/or may be invoked in response to detected events or interrupts. Software modules configured for execution on computing devices may be provided on a computer readable medium, such as a compact disc, digital video disc, flash drive, magnetic disc, or any other tangible medium, or as a digital download (and may be originally stored in a compressed or installable format that requires installation, decompression or decryption prior to execution). Such software code may be stored, partially or fully, on a memory device of the executing computing device, for execution by the computing device. Software instructions may be embedded in firmware, such as an EPROM. It will be further appreciated that hardware modules may be comprised of connected logic units, such as gates and flip-flops, and/or may be comprised of programmable units, such as programmable gate arrays or processors. The modules or computing device functionality described herein are preferably implemented as software modules, but may be represented in hardware or firmware. Generally, the modules described herein refer to logical modules that may be combined with other modules or divided into sub-modules despite their physical organization or storage
Computer system 700 may implement the techniques described herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware and/or program logic which in combination with the computer system causes or programs computer system 700 to be a special-purpose machine. According to one embodiment, the techniques herein are performed by computer system 700 in response to processor(s) 704 executing one or more sequences of one or more instructions contained in main memory 706. Such instructions may be read into main memory 706 from another storage medium, such as storage device 710. Execution of the sequences of instructions contained in main memory 706 causes processor(s) 704 to perform the process steps described herein. In alternative embodiments, hard-wired circuitry may be used in place of or in combination with software instructions.
The term “non-transitory media,” and similar terms, as used herein refers to any media that store data and/or instructions that cause a machine to operate in a specific fashion. Such non-transitory media may comprise non-volatile media and/or volatile media. Non-volatile media includes, for example, optical or magnetic disks, such as storage device 710. Volatile media includes dynamic memory, such as main memory 706. Common forms of non-transitory media include, for example, a floppy disk, a flexible disk, hard disk, solid state drive, magnetic tape, or any other magnetic data storage medium, a CD-ROM, any other optical data storage medium, any physical medium with patterns of holes, a RAM, a PROM, and EPROM, a FLASH-EPROM, NVRAM, any other memory chip or cartridge, and networked versions of the same.
Non-transitory media is distinct from but may be used in conjunction with transmission media. Transmission media participates in transferring information between non-transitory media. For example, transmission media includes coaxial cables, copper wire and fiber optics, including the wires that comprise bus 702. Transmission media can also take the form of acoustic or light waves, such as those generated during radio-wave and infra-red data communications.
Various forms of media may be involved in carrying one or more sequences of one or more instructions to processor 704 for execution. For example, the instructions may initially be carried on a magnetic disk or solid state drive of a remote computer. The remote computer can load the instructions into its dynamic memory and send the instructions over a telephone line using a modem. A modem local to computer system 700 can receive the data on the telephone line and use an infra-red transmitter to convert the data to an infra-red signal. An infra-red detector can receive the data carried in the infra-red signal and appropriate circuitry can place the data on bus 702. Bus 702 carries the data to main memory 406, from which processor 704 retrieves and executes the instructions. The instructions received by main memory 706 may retrieve and execute the instructions. The instructions received by main memory 706 may optionally be stored on storage device 710 either before or after execution by processor 704.
Computer system 700 also includes a communication interface 718 coupled to bus 702. Communication interface 718 provides a two-way data communication coupling to a network link 720 that is connected to a local network 722. For example, communication interface 718 may be an integrated services digital network (ISDN) card, cable modem, satellite modem, or a modem to provide a data communication connection to a corresponding type of telephone line. As another example, communication interface 718 may be a local area network (LAN) card to provide a data communication connection to a compatible LAN (or WAN component to communicated with a WAN). Wireless links may also be implemented. In any such implementation, communication interface 718 sends and receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of information.
Network link 720 typically provides data communication through one or more networks to other data devices. For example, network link 720 may provide a connection through local network 722 to a host computer 724 or to data equipment operated by an Internet Service Provider (ISP) 726. ISP 726 in turn provides data communication services through the world wide packet data communication network now commonly referred to as the “Internet” 728. Local network 722 and Internet 728 both use electrical, electromagnetic or optical signals that carry digital data streams. The signals through the various networks and the signals on network link 720 and through communication interface 718, which carry the digital data to and from computer system 700, are example forms of transmission media.
Computer system 700 can send messages and receive data, including program code, through the network(s), network link 720 and communication interface 718. In the Internet example, a server 730 might transmit a requested code for an application program through Internet 728, ISP 726, local network 722 and communication interface 718.
The received code may be executed by processor 704 as it is received, and/or stored in storage device 710, or other non-volatile storage for later execution.
Terminology
Each of the processes, methods, and algorithms described in the preceding sections may be embodied in, and fully or partially automated by, code modules executed by one or more computer systems or computer processors comprising computer hardware. The processes and algorithms may be implemented partially or wholly in application-specific circuitry. The term “substantially” when used in conjunction with the term “real-time” forms a phrase that will be readily understood by a person of ordinary skill in the art. For example, it is readily understood that such language will include speeds in which no or little delay or waiting is discernible, or where such delay is sufficiently short so as not to be disruptive, irritating or otherwise vexing to user.
The various features and processes described above may be used independently of one another, or may be combined in various ways. All possible combinations and subcombinations are intended to fall within the scope of this disclosure. In addition, certain method or process blocks may be omitted in some implementations. The methods and processes described herein are also not limited to any particular sequence, and the blocks or states relating thereto can be performed in other sequences that are appropriate. For example, described blocks or states may be performed in an order other than that specifically disclosed, or multiple blocks or states may be combined in a single block or state. The example blocks or states may be performed in serial, in parallel, or in some other manner. Blocks or states may be added to or removed from the disclosed example embodiments. The example systems and components described herein may be configured differently than described. For example, elements may be added to, removed from, or rearranged compared to the disclosed example embodiments.
Conditional language, such as, among others, “can,” “could,” “might,” or “may,” unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments include, while other embodiments do not include, certain features, elements and/or steps. Thus, such conditional language is not generally intended to imply that features, elements and/or steps are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without user input or prompting, whether these features, elements and/or steps are included or are to be performed in any particular embodiment.
Any process descriptions, elements, or blocks in the flow diagrams described herein and/or depicted in the attached figures should be understood as potentially representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps in the process. Alternate implementations are included within the scope of the embodiments described herein in which elements or functions may be deleted, executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those skilled in the art.
The term “a” as used herein should be given an inclusive rather than exclusive interpretation. For example, unless specifically noted, the term “a” should not be understood to mean “exactly one” or “one and only one”; instead, the term “a” means “one or more” or “at least one,” whether used in the claims or elsewhere in the specification and regardless of uses of quantifiers such as “at least one,” “one or more,” or “a plurality” elsewhere in the claims or specification.
The term “comprising” as used herein should be given an inclusive rather than exclusive interpretation. For example, a general purpose computer comprising one or more processors should not be interpreted as excluding other computer components, and may possibly include such components as memory, input/output devices, and/or network interfaces, among others.
It should be emphasized that many variations and modifications may be made to the above-described embodiments, the elements of which are to be understood as being among other acceptable examples. All such modifications and variations are intended to be included herein within the scope of this disclosure. The foregoing description details certain embodiments of the invention. It will be appreciated, however, that no matter how detailed the foregoing appears in text, the invention can be practiced in many ways. As is also stated above, it should be noted that the use of particular terminology when describing certain features or aspects of the invention should not be taken to imply that the terminology is being re-defined herein to be restricted to including any specific characteristics of the features or aspects of the invention with which that terminology is associated. The scope of the invention should therefore be construed in accordance with the appended claims and any equivalents thereof.
This application is a continuation of U.S. patent application Ser. No. 15/167,856, entitled “MISALIGNMENT DETECTION SYSTEM FOR EFFICIENTLY PROCESSING DATABASE-STORED DATA AND AUTOMATICALLY GENERATING MISALIGNMENT INFORMATION FOR DISPLAY IN INTERACTIVE USER INTERFACES” and filed on May 27, 2016, which claims priority under 35 U.S.C. § 119(e) to U.S. Provisional Application No. 62/269,612, entitled “MISALIGNMENT DETECTION SYSTEM FOR EFFICIENTLY PROCESSING DATABASE-STORED DATA AND AUTOMATICALLY GENERATING MISALIGNMENT INFORMATION FOR DISPLAY IN INTERACTIVE USER INTERFACES” and filed on Dec. 18, 2015, which are hereby incorporated by reference herein in their entireties.
| Number | Name | Date | Kind |
|---|---|---|---|
| 6430305 | Decker | Aug 2002 | B1 |
| 6820135 | Dingman | Nov 2004 | B1 |
| 6978419 | Kantrowitz | Dec 2005 | B1 |
| 6980984 | Huffman et al. | Dec 2005 | B1 |
| 7168039 | Bertram | Jan 2007 | B2 |
| 7617232 | Gabbert et al. | Nov 2009 | B2 |
| 7756843 | Palmer | Jul 2010 | B1 |
| 7899796 | Borthwick et al. | Mar 2011 | B1 |
| 7917376 | Bellin et al. | Mar 2011 | B2 |
| 7941321 | Greenstein et al. | May 2011 | B2 |
| 8036971 | Aymeloglu et al. | Oct 2011 | B2 |
| 8046283 | Burns | Oct 2011 | B2 |
| 8054756 | Chand et al. | Nov 2011 | B2 |
| 8214490 | Vos et al. | Jul 2012 | B1 |
| 8229902 | Vishniac et al. | Jul 2012 | B2 |
| 8290838 | Thakur et al. | Oct 2012 | B1 |
| 8302855 | Ma et al. | Nov 2012 | B2 |
| 8311901 | Carmichael | Nov 2012 | B1 |
| 8392556 | Goulet et al. | Mar 2013 | B2 |
| 8473454 | Evanitsky et al. | Jun 2013 | B2 |
| 8484115 | Aymeloglu et al. | Jul 2013 | B2 |
| 8589273 | Creeden et al. | Nov 2013 | B2 |
| 8688573 | Ruknoic et al. | Apr 2014 | B1 |
| 8700586 | Celik | Apr 2014 | B2 |
| 8744890 | Bernier | Jun 2014 | B1 |
| 8812960 | Sun et al. | Aug 2014 | B1 |
| 8924388 | Elliot et al. | Dec 2014 | B2 |
| 8924389 | Elliot et al. | Dec 2014 | B2 |
| 8938686 | Erenrich et al. | Jan 2015 | B1 |
| 8949164 | Mohler | Feb 2015 | B1 |
| 9100428 | Visbal | Aug 2015 | B1 |
| 9129219 | Robertson et al. | Sep 2015 | B1 |
| 10373099 | McCardel | Aug 2019 | B1 |
| 10915843 | Shariff | Feb 2021 | B1 |
| 20020029226 | Li | Mar 2002 | A1 |
| 20020065708 | Senay et al. | May 2002 | A1 |
| 20020095360 | Joao | Jul 2002 | A1 |
| 20020095658 | Shulman | Jul 2002 | A1 |
| 20020103705 | Brady | Aug 2002 | A1 |
| 20020147805 | Leshem et al. | Oct 2002 | A1 |
| 20030036848 | Sheha et al. | Feb 2003 | A1 |
| 20030061132 | Mason et al. | Mar 2003 | A1 |
| 20030126102 | Borthwick | Jul 2003 | A1 |
| 20030172014 | Quackenbush et al. | Sep 2003 | A1 |
| 20040034570 | Davis | Feb 2004 | A1 |
| 20040111480 | Yue | Jun 2004 | A1 |
| 20040153418 | Hanweck | Aug 2004 | A1 |
| 20040236688 | Bozeman | Nov 2004 | A1 |
| 20050010472 | Quatse et al. | Jan 2005 | A1 |
| 20050086207 | Heuer et al. | Apr 2005 | A1 |
| 20050154628 | Eckart et al. | Jul 2005 | A1 |
| 20050154769 | Eckart et al. | Jul 2005 | A1 |
| 20060026120 | Carolan et al. | Feb 2006 | A1 |
| 20060143034 | Rothermel | Jun 2006 | A1 |
| 20060143075 | Carr et al. | Jun 2006 | A1 |
| 20060143079 | Basak et al. | Jun 2006 | A1 |
| 20070000999 | Kubo et al. | Jan 2007 | A1 |
| 20070011304 | Error | Jan 2007 | A1 |
| 20070038646 | Thota | Feb 2007 | A1 |
| 20070100802 | Celik | May 2007 | A1 |
| 20070150801 | Chidlovskii et al. | Jun 2007 | A1 |
| 20070156673 | Maga | Jul 2007 | A1 |
| 20070185867 | Maga | Aug 2007 | A1 |
| 20070284433 | Domenica et al. | Dec 2007 | A1 |
| 20080040275 | Paulsen et al. | Feb 2008 | A1 |
| 20080069081 | Chand et al. | Mar 2008 | A1 |
| 20080103996 | Forman et al. | May 2008 | A1 |
| 20080222295 | Robinson et al. | Sep 2008 | A1 |
| 20080243711 | Aymeloglu et al. | Oct 2008 | A1 |
| 20080249983 | Meisels et al. | Oct 2008 | A1 |
| 20080255973 | El Wade et al. | Oct 2008 | A1 |
| 20080313132 | Hao et al. | Dec 2008 | A1 |
| 20090076845 | Bellin et al. | Mar 2009 | A1 |
| 20090094166 | Aymeloglu et al. | Apr 2009 | A1 |
| 20090106178 | Chu | Apr 2009 | A1 |
| 20090112745 | Stefanescu | Apr 2009 | A1 |
| 20090125359 | Knapic | May 2009 | A1 |
| 20090125459 | Norton et al. | May 2009 | A1 |
| 20090164294 | Hu | Jun 2009 | A1 |
| 20090187546 | Whyte et al. | Jul 2009 | A1 |
| 20090187548 | Ji et al. | Jul 2009 | A1 |
| 20090249244 | Robinson et al. | Oct 2009 | A1 |
| 20090259569 | Narea | Oct 2009 | A1 |
| 20090271343 | Vaiciulis et al. | Oct 2009 | A1 |
| 20090307049 | Elliott et al. | Dec 2009 | A1 |
| 20090313463 | Pang et al. | Dec 2009 | A1 |
| 20090319418 | Herz | Dec 2009 | A1 |
| 20090319891 | MacKinlay | Dec 2009 | A1 |
| 20100030722 | Goodson et al. | Feb 2010 | A1 |
| 20100031141 | Summers et al. | Feb 2010 | A1 |
| 20100042922 | Bradateanu et al. | Feb 2010 | A1 |
| 20100057622 | Faith et al. | Mar 2010 | A1 |
| 20100070842 | Aymeloglu et al. | Mar 2010 | A1 |
| 20100076813 | Ghosh et al. | Mar 2010 | A1 |
| 20100098318 | Anderson | Apr 2010 | A1 |
| 20100114887 | Conway et al. | May 2010 | A1 |
| 20100131502 | Fordham | May 2010 | A1 |
| 20100161735 | Sharma | Jun 2010 | A1 |
| 20100191563 | Schlaifer et al. | Jul 2010 | A1 |
| 20100235915 | Memon et al. | Sep 2010 | A1 |
| 20100262688 | Hussain et al. | Oct 2010 | A1 |
| 20100312837 | Bodapati et al. | Dec 2010 | A1 |
| 20110004498 | Readshaw | Jan 2011 | A1 |
| 20110061013 | Bilicki et al. | Mar 2011 | A1 |
| 20110078173 | Seligmann et al. | Mar 2011 | A1 |
| 20110093327 | Fordyce, III et al. | Apr 2011 | A1 |
| 20110099133 | Chang et al. | Apr 2011 | A1 |
| 20110153384 | Horne et al. | Jun 2011 | A1 |
| 20110161137 | Ubalde et al. | Jun 2011 | A1 |
| 20110173093 | Psota et al. | Jul 2011 | A1 |
| 20110208565 | Ross et al. | Aug 2011 | A1 |
| 20110213655 | Henkin | Sep 2011 | A1 |
| 20110218955 | Tang | Sep 2011 | A1 |
| 20110270604 | Qi et al. | Nov 2011 | A1 |
| 20110270834 | Sokolan et al. | Nov 2011 | A1 |
| 20110289397 | Eastmond et al. | Nov 2011 | A1 |
| 20110295649 | Fine | Dec 2011 | A1 |
| 20110314007 | Dassa et al. | Dec 2011 | A1 |
| 20110314024 | Chang et al. | Dec 2011 | A1 |
| 20120011238 | Rathod | Jan 2012 | A1 |
| 20120011245 | Gillette et al. | Jan 2012 | A1 |
| 20120022945 | Falkenborg et al. | Jan 2012 | A1 |
| 20120054284 | Rakshit | Mar 2012 | A1 |
| 20120059853 | Jagota | Mar 2012 | A1 |
| 20120066166 | Curbera et al. | Mar 2012 | A1 |
| 20120079363 | Folting et al. | Mar 2012 | A1 |
| 20120084117 | Tavares et al. | Apr 2012 | A1 |
| 20120084287 | Lakshminarayan et al. | Apr 2012 | A1 |
| 20120116828 | Shannon | May 2012 | A1 |
| 20120123673 | Perks | May 2012 | A1 |
| 20120131512 | Takeuchi et al. | May 2012 | A1 |
| 20120159362 | Brown et al. | Jun 2012 | A1 |
| 20120173381 | Smith | Jul 2012 | A1 |
| 20120179505 | McMains | Jul 2012 | A1 |
| 20120215784 | King et al. | Aug 2012 | A1 |
| 20120221553 | Wittmer et al. | Aug 2012 | A1 |
| 20120226523 | Weiss | Sep 2012 | A1 |
| 20120245976 | Kumar et al. | Sep 2012 | A1 |
| 20120323888 | Osann, Jr. | Dec 2012 | A1 |
| 20130016106 | Yip et al. | Jan 2013 | A1 |
| 20130054306 | Bhalla | Feb 2013 | A1 |
| 20130057551 | Ebert et al. | Mar 2013 | A1 |
| 20130096988 | Grossman et al. | Apr 2013 | A1 |
| 20130110746 | Ahn | May 2013 | A1 |
| 20130151453 | Bhanot et al. | Jun 2013 | A1 |
| 20130166348 | Scotto | Jun 2013 | A1 |
| 20130166480 | Popescu et al. | Jun 2013 | A1 |
| 20130185245 | Anderson | Jul 2013 | A1 |
| 20130185307 | El-Yaniv et al. | Jul 2013 | A1 |
| 20130226318 | Procyk | Aug 2013 | A1 |
| 20130238616 | Rose et al. | Sep 2013 | A1 |
| 20130246170 | Gross et al. | Sep 2013 | A1 |
| 20130246537 | Gaddala | Sep 2013 | A1 |
| 20130246597 | Iizawa et al. | Sep 2013 | A1 |
| 20130263019 | Castellanos et al. | Oct 2013 | A1 |
| 20130282696 | John et al. | Oct 2013 | A1 |
| 20130290825 | Arndt et al. | Oct 2013 | A1 |
| 20130297619 | Chandrasekaran et al. | Nov 2013 | A1 |
| 20130304770 | Boero et al. | Nov 2013 | A1 |
| 20140012796 | Petersen et al. | Jan 2014 | A1 |
| 20140040371 | Gurevich et al. | Feb 2014 | A1 |
| 20140058794 | Malov et al. | Feb 2014 | A1 |
| 20140058914 | Song et al. | Feb 2014 | A1 |
| 20140068487 | Steiger et al. | Mar 2014 | A1 |
| 20140089339 | Siddiqui et al. | Mar 2014 | A1 |
| 20140095509 | Patton | Apr 2014 | A1 |
| 20140108380 | Gotz et al. | Apr 2014 | A1 |
| 20140108985 | Scott et al. | Apr 2014 | A1 |
| 20140123279 | Bishop et al. | May 2014 | A1 |
| 20140136285 | Carvalho | May 2014 | A1 |
| 20140143009 | Brice et al. | May 2014 | A1 |
| 20140156527 | Grigg et al. | Jun 2014 | A1 |
| 20140157172 | Peery et al. | Jun 2014 | A1 |
| 20140164502 | Khodorenko et al. | Jun 2014 | A1 |
| 20140189536 | Lange et al. | Jul 2014 | A1 |
| 20140195515 | Baker et al. | Jul 2014 | A1 |
| 20140222521 | Chait | Aug 2014 | A1 |
| 20140222793 | Sadkin et al. | Aug 2014 | A1 |
| 20140229554 | Grunin et al. | Aug 2014 | A1 |
| 20140258246 | Lo Faro et al. | Sep 2014 | A1 |
| 20140289073 | Gold | Sep 2014 | A1 |
| 20140344230 | Krause et al. | Nov 2014 | A1 |
| 20140351070 | Christner et al. | Nov 2014 | A1 |
| 20140358829 | Hurwitz | Dec 2014 | A1 |
| 20140366132 | Stiansen et al. | Dec 2014 | A1 |
| 20140370972 | Mullen | Dec 2014 | A1 |
| 20140380237 | Kroupa | Dec 2014 | A1 |
| 20150073929 | Psota et al. | Mar 2015 | A1 |
| 20150073954 | Braff | Mar 2015 | A1 |
| 20150095773 | Gonsalves et al. | Apr 2015 | A1 |
| 20150100897 | Sun et al. | Apr 2015 | A1 |
| 20150100907 | Erenrich et al. | Apr 2015 | A1 |
| 20150106379 | Elliot et al. | Apr 2015 | A1 |
| 20150135256 | Hoy et al. | May 2015 | A1 |
| 20150188872 | White | Jul 2015 | A1 |
| 20150338233 | Cervelli et al. | Nov 2015 | A1 |
| 20150379413 | Robertson et al. | Dec 2015 | A1 |
| 20160004764 | Chakerian et al. | Jan 2016 | A1 |
| 20160026923 | Erenrich et al. | Jan 2016 | A1 |
| 20160055495 | Qin et al. | Feb 2016 | A1 |
| 20160055501 | Mukherjee et al. | Feb 2016 | A1 |
| 20160125345 | Majumdar | May 2016 | A1 |
| Number | Date | Country |
|---|---|---|
| 102546446 | Jul 2012 | CN |
| 103167093 | Jun 2013 | CN |
| 102054015 | May 2014 | CN |
| 102014204827 | Sep 2014 | DE |
| 102014204830 | Sep 2014 | DE |
| 102014204834 | Sep 2014 | DE |
| 2487610 | Aug 2012 | EP |
| 2858018 | Apr 2015 | EP |
| 2869211 | May 2015 | EP |
| 2889814 | Jul 2015 | EP |
| 2892197 | Jul 2015 | EP |
| 2963595 | Jan 2016 | EP |
| 2988258 | Feb 2016 | EP |
| WO 2005116851 | Dec 2005 | WO |
| Entry |
|---|
| Korzeniowski, Paul, “GIS software getting business data on map; cheaper hardware, PC software packages, U.S. Census Tigr format widen user base,” Software Magazine, 13.n7, King Content Co. / Software Magazine, May 1993, p. 96(4). |
| AMNET, “5 Great Tools for Visualizing Your Twitter Followers,” posted Aug. 4, 2010, http://www. amnetblog.com/component/content/article/115-5-grate-tools-for-visualizing-your-twitter-followers.html. |
| Appacts, “Smart Thinking for Super Apps,” <http://www.appacts.com> Printed Jul. 18, 2013 in 4 pages. |
| Apsalar, “Data Powered Mobile Advertising,” “Free Mobile App Analytics”and various analytics related screen shots <http://apsalar.com> Printed Jul. 18, 2013 in 8 pages. |
| Capptain—Pilot Your Apps, <http://www.capptain.com> Printed Jul. 18, 2013 in 6 pages. |
| Celik, Tantek, “CSS Basic User Interface Module Level 3 (CSS3 UI),” Section 8 Resizing and Overflow, Jan. 17, 2012, retrieved from internet http://www.w3.org/TR/2012/WD-css3-ui-20120117/#resizing-amp-overflow retrieved on May 18, 2015. |
| Chaudhuri et al., “An Overview of Business Intelligence Technology,” Communications of the ACM, Aug. 2011, vol. 54, No. 8. |
| Cohn, et al., “Semi-supervised clustering with user feedback,” Constrained Clustering: Advances in Algorithms, Theory, and Applications 4.1 (2003): 17-32. |
| Countly Mobile Analytics, <http://count.ly/> Printed Jul. 18, 2013 in 9 pages. |
| DISTIMO—App Analytics, <http://www.distimo.com/app-analytics> Printed Jul. 18, 2013 in 5 pages. |
| Ferreira et al., “A Scheme for Analyzing Electronic Payment Systems,” Basil 1997. |
| Flurry Analytics, <http://www.flurry.com/> Printed Jul. 18, 2013 in 14 pages. |
| Google Analystics Official Website—Web Analytics & Reporting, <http://www.google.com/analytics.index.html> Printed Jul. 18, 2013 in 22 pages. |
| Gorr et al., “Crime Hot Spot Forecasting: Modeling and Comparative Evaluation”, Grant 98-IJ-CX-K005, May 6, 2002, 37 pages. |
| Gu et al., “Record Linkage: Current Practice and Future Directions,” Jan. 15, 2004, pp. 32. |
| Hansen et al., “Analyzing Social Media Networks with NodeXL: Insights from a Connected World”, Chapter 4, pp. 53-67 and Chapter 10, pp. 143-164, published Sep. 2010. |
| Hua et al., “A Multi-attribute Data Structure with Parallel Bloom Filters for Network Services”, HiPC 2006, LNCS 4297, pp. 277-288, 2006. |
| “HunchLab: Heat Map and Kernel Density Calculation for Crime Analysis,” Azavea Journal, printed from www.azavea.com/blogs/newsletter/v4i4/kernel-density-capabilities-added-to-hunchlab/ on Sep. 9, 2014, 2 pages. |
| Keylines.com, “An Introduction to KeyLines and Network Visualization,” Mar. 2014, <http://keylines.com/wp-content/uploads/2014/03/KeyLines-White-Paper.pdf> downloaded May 12, 2014 in 8 pages. |
| Keylines.com, “KeyLines Datasheet,” Mar. 2014, <http://keylines.com/wp-content/uploads/2014/03/KeyLines-datasheet.pdf> downloaded May 12, 2014 in 2 pages. |
| Keylines.com, “Visualizing Threats: Improved Cyber Security Through Network Visualization,” Apr. 2014, <http://keylines.com/wp-content/uploads/2014/04/Visualizing-Threats1.pdf> downloaded May 12, 2014 in 10 pages. |
| Kontagent Mobile Analytics, <http://www.kontagent.com/> Printed Jul. 18, 2013 in 9 pages. |
| Localytics—Mobile App Marketing & Analytics, <http://www.localytics.com/> Printed Jul. 18, 2013 in 12 pages. |
| Manno et al., “Introducing Collaboration in Single-user Applications through the Centralized Control Architecture,” 2010, pp. 10. |
| McClave et al., “Statistics for Business and Economics”, 2001, pp. 86-96. |
| Mixpanel—Mobile Analytics, <https://mixpanel.com/> Printed Jul. 18, 2013 in 13 pages. |
| Open Web Analytics (OWA), <http://www.openwebanalytics.com/> Printed Jul. 19, 2013 in 5 pages. |
| Piwik—Free Web Analytics Software. <http://piwik.org/> Printed Jul. 19, 2013 in 18 pages. |
| “Refresh CSS Ellipsis When Resizing Container—Stack Overflow,” Jul. 31, 2013, retrieved from internet http://stackoverflow.com/questions/17964681/refresh-css-ellipsis-when-resizing-container, retrieved on May 18, 2015. |
| Sigrist, et al., “PROSITE, a Protein Domain Database for Functional Characterization and Annotation,” Nucleic Acids Research, 2010, vol. 38, pp. D161-D166. |
| StatCounter—Free Invisible Web Tracker, Hit Counter and Web Stats, <http://statcounter.com/> Printed Jul. 19, 2013 in 17 pages. |
| TestFlight—Beta Testing on the Fly, <http://testflightapp.com/> Printed Jul. 18, 2013 in 3 pages. |
| Trak.io, <http://trak.io/> printed Jul. 18, 2013 in 3 pages. |
| UserMetrix, <http://usermetrix.com/android-analytics> printed Jul. 18, 2013 in 3 pages. |
| Valentini et al., “Ensembles of Learning Machines”, M. Marinaro and R. Tagliaferri (Eds.): WIRN VIETRI 2002, LNCS 2486, pp. 3-20. |
| Vose et al., “Help File for ModelRisk Version 5,” Vose Software, pp. 349-353. [Uploaded in 2 Parts]. |
| Wang et al., “Research on a Clustering Date De-Duplication Mechanism Based on Bloom Filter,” IEEE 2010, 5 pages. |
| Wikipedia, “Multimap,” Jan. 1, 2013, https://en.wikipedia.org/w/index.php?title=Multimap&oldid=530800748. |
| Notice of Allowance for U.S. Appl. No. 14/225,084 dated May 4, 2015. |
| Notice of Allowance for U.S. Appl. No. 14/319,161 dated May 4, 2015. |
| Notice of Allowance for U.S. Appl. No. 14/323,935 dated Oct. 1, 2015. |
| Notice of Allowance for U.S. Appl. No. 14/479,863 dated Mar. 31, 2015. |
| Notice of Allowance for U.S. Appl. No. 14/552,336 dated Nov. 3, 2015. |
| Notice of Allowance for U.S. Appl. No. 14/746,671 dated Jan. 21, 2016. |
| Official Communication for European Patent Application No. 14187996.5 dated Feb. 12, 2015. |
| Official Communication for European Patent Application No. 14191540.5 dated May 27, 2015. |
| Official Communication for European Patent Application No. 14200246.8 dated May 29, 2015. |
| Official Communication for European Patent Application No. 14200298.9 dated May 13, 2015. |
| Official Communication for European Patent Application No. 15181419.1 dated Sep. 29, 2015. |
| Official Communication for European Patent Application No. 15184764.7 dated Dec. 14, 2015. |
| Official Communication for Great Britain Patent Application No. 1404486.1 dated May 21, 2015. |
| Official Communication for Great Britain Patent Application No. 1404486.1 dated Aug. 27, 2014. |
| Official Communication for Great Britain Patent Application No. 1404489.5 dated May 21, 2015. |
| Official Communication for Great Britain Patent Application No. 1404489.5 dated Aug. 27, 2014. |
| Official Communication for Great Britain Patent Application No. 1404499.4 dated Jun. 11, 2015. |
| Official Communication for Great Britain Patent Application No. 1404499.4 dated Aug. 20, 2014. |
| Official Communication for Netherlands Patent Application No. 2012417 dated Sep. 18, 2015. |
| Official Communication for Netherlands Patent Application No. 2012421 dated Sep. 18, 2015. |
| Official Communication for Netherlands Patent Application No. 2012438 dated Sep. 21, 2015. |
| Official Communication for New Zealand Patent Application No. 622473 dated Jun. 19, 2014. |
| Official Communication for New Zealand Patent Application No. 622473 dated Mar. 27, 2014. |
| Official Communication for New Zealand Patent Application No. 622513 dated Apr. 3, 2014. |
| Official Communication for New Zealand Patent Application No. 628161 dated Aug. 25, 2014. |
| Official Communication for U.S. Appl. No. 13/827,491 dated Dec. 1, 2014. |
| Official Communication for U.S. Appl. No. 13/827,491 dated Jun. 22, 2015. |
| Official Communication for U.S. Appl. No. 13/827,491 dated Oct. 9, 2015. |
| Official Communication for U.S. Appl. No. 14/141,252 dated Oct. 8, 2015. |
| Official Communication for U.S. Appl. No. 14/225,006 dated Sep. 10, 2014. |
| Official Communication for U.S. Appl. No. 14/225,006 dated Sep. 2, 2015. |
| Official Communication for U.S. Appl. No. 14/225,006 dated Dec. 21, 2015. |
| Official Communication for U.S. Appl. No. 14/225,006 dated Feb. 27, 2015. |
| Official Communication for U.S. Appl. No. 14/225,084 dated Sep. 11, 2015. |
| Official Communication for U.S. Appl. No. 14/225,084 dated Sep. 2, 2014. |
| Official Communication for U.S. Appl. No. 14/225,084 dated Feb. 20, 2015. |
| Official Communication for U.S. Appl. No. 14/225,084 dated Jan. 4, 2016. |
| Official Communication for U.S. Appl. No. 14/225,160 dated Feb. 11, 2015. |
| Official Communication for U.S. Appl. No. 14/225,160 dated Aug. 12, 2015. |
| Official Communication for U.S. Appl. No. 14/225,160 dated May 20, 2015. |
| Official Communication for U.S. Appl. No. 14/225,160 dated Oct. 22, 2014. |
| Official Communication for U.S. Appl. No. 14/225,160 dated Jul. 29, 2014. |
| Official Communication for U.S. Appl. No. 14/306,138 dated Mar. 17, 2016. |
| Official Communication for U.S. Appl. No. 14/306,138 dated Dec. 24, 2015. |
| Official Communication for U.S. Appl. No. 14/306,138 dated Dec. 3, 2015. |
| Official Communication for U.S. Appl. No. 14/306,147 dated Dec. 24, 2015. |
| Official Communication for U.S. Appl. No. 14/306,147 dated Jun. 3, 2016. |
| Official Communication for U.S. Appl. No. 14/306,147 dated Mar. 4, 2016. |
| Official Communication for U.S. Appl. No. 14/306,154 dated Feb. 1, 2016. |
| Official Communication for U.S. Appl. No. 14/306,154 dated Mar. 17, 2016. |
| Official Communication for U.S. Appl. No. 14/319,161 dated Jan. 23, 2015. |
| Official Communication for U.S. Appl. No. 14/451,221 dated Oct. 21, 2014. |
| Official Communication for U.S. Appl. No. 14/463,615 dated Sep. 10, 2015. |
| Official Communication for U.S. Appl. No. 14/463,615 dated May 12, 2016. |
| Official Communication for U.S. Appl. No. 14/463,615 dated Nov. 13, 2014. |
| Official Communication for U.S. Appl. No. 14/463,615 dated Aug. 19, 2016. |
| Official Communication for U.S. Appl. No. 14/463,615 dated Mar. 21, 2016. |
| Official Communication for U.S. Appl. No. 14/463,615 dated May 21, 2015. |
| Official Communication for U.S. Appl. No. 14/463,615 dated Jan. 28, 2015. |
| Official Communication for U.S. Appl. No. 14/463,615 dated Dec. 9, 2015. |
| Official Communication for U.S. Appl. No. 14/479,863 dated Dec. 26, 2014. |
| Official Communication for U.S. Appl. No. 14/483,527 dated Jun. 22, 2015. |
| Official Communication for U.S. Appl. No. 14/483,527 dated Jan. 28, 2015. |
| Official Communication for U.S. Appl. No. 14/483,527 dated Oct. 28, 2015. |
| Official Communication for U.S. Appl. No. 14/552,336 dated Jul. 20, 2015. |
| Official Communication for U.S. Appl. No. 14/562,524 dated Nov. 10, 2015. |
| Official Communication for U.S. Appl. No. 14/562,524 dated Sep. 14, 2015. |
| Official Communication for U.S. Appl. No. 14/562,524 dated Feb. 18, 2016. |
| Official Communication for U.S. Appl. No. 14/571,098 dated Nov. 10, 2015. |
| Official Communication for U.S. Appl. No. 14/571,098 dated Mar. 11, 2015. |
| Official Communication for U.S. Appl. No. 14/571,098 dated Aug. 24, 2015. |
| Official Communication for U.S. Appl. No. 14/571,098 dated Aug. 5, 2015. |
| Official Communication for U.S. Appl. No. 14/631,633 dated Sep. 10, 2015. |
| Official Communication for U.S. Appl. No. 14/676,621 dated Oct. 29, 2015. |
| Official Communication for U.S. Appl. No. 14/676,621 dated Jul. 30, 2015. |
| Official Communication for U.S. Appl. No. 14/746,671 dated Nov. 12, 2015. |
| Official Communication for U.S. Appl. No. 14/800,447 dated Dec. 10, 2015. |
| Official Communication for U.S. Appl. No. 14/800,447 dated Mar. 3, 2016. |
| Official Communication for U.S. Appl. No. 14/800,447 dated Jun. 6, 2016. |
| Official Communication for U.S. Appl. No. 14/811,649 dated May 18, 2016. |
| Official Communication for U.S. Appl. No. 14/813,749 dated Sep. 28, 2015. |
| Official Communication for U.S. Appl. No. 14/842,734 dated Nov. 19, 2015. |
| Notice of Allowance for U.S. Appl. No. 15/167,856 dated Mar. 21, 2019. |
| Official Communication for U.S. Appl. No. 15/167,856 dated Jan. 19, 2018. |
| Official Communication for U.S. Appl. No. 15/167,856 dated Jun. 7, 2017. |
| U.S. Pat. No. 10,373,099, Misalignment Detection System for Efficiently Processing Database-Stored Data and Automatically Generating Misalignment Information for Display in Interactive User Interfaces, Aug. 6, 2019. |
| Number | Date | Country | |
|---|---|---|---|
| 20190303856 A1 | Oct 2019 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62269612 | Dec 2015 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 15167856 | May 2016 | US |
| Child | 16444997 | US |
