Probabilistic search and retrieval of work order equipment parts list data based on identified failure tracking attributes

• US 9,785,893 B2
• Filed: 09/25/2007
• Issued: 10/10/2017
• Est. Priority Date: 09/25/2007
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Riksheim, Jon, Bogomolni, German A.
• Primary Examiner(s): CRAWLEY, TALIA F
• Application Number:
  US11/860,915
• Publication Number:
  US 20090083250A1
• Time in Patent Office: 3,668 Days
• Field of Search: 705 8, 705 28
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling

Abstract

This disclosure describes, generally, methods and systems for creating dynamic subsets of larger equipment parts lists (EPLs). For example, a method may include receiving a search request that includes an associated failure code and a target asset. The method might further include providing an EPL for the asset type, and retrieving sub-lists of the EPL based on previous search requests which are associated with the failure code for the asset type. The method may further predict which one of the plurality of sub-lists has the highest probability of being associated with the failure code for the asset type and might present the predicted sub-list of the EPL to a user.

Claims

1. A method for processing search requests by identifying sub-lists of parts lists, the method comprising:

for each type of a plurality of types of assets;

generating a plurality of code components, each code component of the plurality of code components representing a problem with an asset, a cause of a problem with an asset, or a resolution of a problem with an asset;

generating a plurality of codes, each code of the plurality of codes representing a combination of multiple code components of the plurality of code components;

for each code of the plurality of codes, generating, in a SQL-compatible usage data store, a count variable associated with the code and type;

receiving, at a computer system, a plurality of first search requests, each first search request of the plurality of first search requests being received from a corresponding first user device;

determining, by the computer system, that each first search request of the plurality of first search requests is associated with;

a particular type of asset of the plurality of types of assets; and

one or more particular code components, each of the one or more particular code components representing at least one of a problem with an asset, a cause of a problem with an asset, or a resolution of a problem with an asset;

identifying a parts list that identifies a plurality of parts that corresponds to the particular type of asset, each part of the plurality of parts including an asset, supply or equipment;

for each first search request of the plurality of first search requests;

facilitating a presentation of one or more sub-lists of the parts list at the corresponding first user device, each sub-list of the one or more sub-lists being a subset of the plurality of parts;

receiving a selection communication from the corresponding first user device that identifies a part from a sub-list of the one or more sub-lists;

identifying a code component corresponding to the part identified via the selection communication;

generating, based on the one or more particular code components and the code component corresponding to the part identified via the selection communication, a code that represents a combination of the one or more particular code components and the code component corresponding to the part identified via the selection communication;

incrementing the count variable associated with the code and the particular type of asset in the SQL-compatible usage data store;

receiving, at the computer system, a second search request from a second user device that corresponds to an asset and the one or more particular code components;

classifying, by the computer system, the asset identified in the second search request as being of the particular type of asset;

extracting, from the SQL-compatible usage data store, a plurality of count variables using one or more SQL functions, each count variable of the plurality of count variables corresponding to a combination of the one or more particular code components with at least one other code component;

for each of the plurality of count variables, generating, by the computer system, a score for a sub-list of the parts list based on the count variable, each part identified in the sub-list corresponding to each of the one or more particular code components and to each of the at least one other code component represented in the count variable;

performing, by the computer system and based on the scores, a statistical filtering of a plurality of sub-lists of the parts lists that indicates that a first sub-list of the parts list is more responsive to the second search request than a second sub-list of the parts list, wherein the first sub-list is associated with a higher score than is the second sub-lists; and

facilitating a presentation that identifies one or more parts identified in the first sub-list.

2. The method for processing search requests by identifying sub-lists of parts lists as recited in claim 1, further comprising:

generating the first sub-list by querying the parts list with the at least one other code component corresponding to a count variable of the plurality of count variables.

3. The method for processing search requests by identifying sub-lists of parts lists as recited in claim 1, wherein the presentation does not include at least one part identified in the second sub-list.

4. The method for processing search requests by identifying sub-lists of parts lists as recited in claim 1, further comprising:

generating, based on the scores, an order for presenting identifiers of multiple sub-lists, the multiple sub-lists including the first sub-list and the second sub-list, and the order indicating that the first sub-list is to be presented before the second sub-list.

5. The method for processing search requests by identifying sub-lists of parts lists as recited in claim 1, further comprising, for each type of the plurality of types of assets:

populating a first data structure with first code components of the plurality of code components, the first data structure being associated with a problem with an asset;

populating a second data structure with second code components of the plurality of code components, the second data structure being associated with a cause or resolution of a problem with an asset; and

establishing links between the first data structure and the second data structure, such that each of the first code components is associated with one or more second code components.

6. The method for processing search requests by identifying sub-lists of parts lists as recited in claim 5, wherein the links are configured to establish a hierarchical structure between code components in the first data structure and the second data structure.

7. The method for processing search requests by identifying sub-lists of parts lists as recited in claim 1, wherein dynamically predicting that the first sub-list of the parts list is more responsive to the second search request than the second sub-list of the parts list includes determining that the score for the first sub-list exceeds a defined threshold and that the score for the second sub-list does not exceed the defined threshold.

8. A system for processing search requests by identifying sub-lists of parts lists, the system comprising:

one or more processors; and

a memory coupled with and readable by the one or more processors and storing therein a set of instructions which, when executed by the one or more processors, causes the one or more processors to perform actions including;

for each type of a plurality of types of assets;

generating a plurality of code components, each code component of the plurality of code components representing a problem with an asset, a cause of a problem with an asset, or a resolution of a problem with an asset;

generating a plurality of codes, each code of the plurality of codes representing a combination of multiple code components of the plurality of code components;

for each code of the plurality of codes, generating, in a SQL-compatible usage data store, a count variable associated with the code and type;

receiving a plurality of first search requests, each first search request of the plurality of first search requests being received from a corresponding first user device;

determining that each first search request of the plurality of first search requests is associated with;

a particular type of asset of the plurality of types of assets; and

one or more particular code components, each of the one or more particular code components representing at least one of a problem with an asset, a cause of a problem with an asset, or a resolution of a problem with an asset;

identifying a parts list that identifies a plurality of parts that corresponds to the particular type of asset, each part of the plurality of parts including an asset, supply or equipment;

for each first search request of the plurality of first search requests;

facilitating a presentation of one or more sub-lists of the parts list at the corresponding first user device, each sub-list of the one or more sub-lists being a subset of the plurality of parts;

receiving a selection communication from the corresponding first user device that identifies a part from a sub-list of the one or more sub-lists;

identifying a code component corresponding to the part identified via the selection communication;

generating, based on the one or more particular code components and the code component corresponding to the part identified via the selection communication, a code that represents a combination of the one or more particular code components and the code component corresponding to the part identified via the selection communication;

incrementing the count variable associated with the code and the particular type of asset in the SQL-compatible usage data store;

receiving a second search request from a second user device that corresponds to an asset and the one or more particular code components;

classifying the asset identified in the second search request as being of the particular type of asset;

extracting, from the SQL-compatible usage data store, a plurality of count variables using one or more SQL functions, each count variable of the plurality of count variables corresponding to a combination of the one or more particular code components with at least one other code component;

for each of the plurality of count variables, generating a score for a sub-list of the parts list based on the count variable, each part identified in the sub-list corresponding to each of the one or more particular code components and to each of the at least one other code component represented in the count variable;

performing, based on the scores, a statistical filtering of a plurality of sub-lists of the parts lists that indicates that a first sub-list of the parts list is more responsive to the second search request than a second sub-list of the parts list, wherein the first sub-list is associated with a higher score than is the second sub-lists; and

facilitating a presentation that identifies one or more parts identified in the first sub-list.

9. The system for processing search requests by identifying sub-lists of parts lists as recited in claim 8, the actions further including:

generating the first sub-list by querying the parts list with the at least one other code component corresponding to a count variable of the plurality of count variables.

10. The system for processing search requests by identifying sub-lists of parts lists as recited in claim 8, wherein the presentation does not include at least one part identified in the second sub-list.

11. The system for processing search requests by identifying sub-lists of parts lists as recited in claim 8, the actions further including:

generating, based on the scores, an order for presenting identifiers of multiple sub-lists, the multiple sub-lists including the first sub-list and the second sub-list, and the order indicating that the first sub-list is to be presented before the second sub-list.

12. The system for processing search requests by identifying sub-lists of parts lists as recited in claim 8, the actions further including, for each type of the plurality of types of assets:

populating a first data structure with first code components of the plurality of code components, the first data structure being associated with a problem with an asset;

populating a second data structure with second code components of the plurality of code components, the second data structure being associated with a cause or resolution of a problem with an asset; and

establishing links between the first data structure and the second data structure, such that each of the first code components is associated with one or more second code components.

13. The system for processing search requests by identifying sub-lists of parts lists as recited in claim 12, wherein the links are configured to establish a hierarchical structure between code components in the first data structure and the second data structure.

14. The system for processing search requests by identifying sub-lists of parts lists as recited in claim 8, wherein dynamically predicting that the first sub-list of the parts list is more responsive to the second search request than the second sub-list of the parts list includes determining that the score for the first sub-list exceeds a defined threshold and that the score for the second sub-list does not exceed the defined threshold.

15. A computer-program product tangibly embodied in a non-transitory machine-readable storage medium, including instructions configured to cause one or more data processors to perform actions including:

for each type of a plurality of types of assets;

generating a plurality of code components, each code component of the plurality of code components representing a problem with an asset, a cause of a problem with an asset, or a resolution of a problem with an asset;

generating a plurality of codes, each code of the plurality of codes representing a combination of multiple code components of the plurality of code components;

for each code of the plurality of codes, generating, in a SQL-compatible usage data store, a count variable associated with the code and type;

receiving a plurality of first search requests, each first search request of the plurality of first search requests being received from a corresponding first user device;

determining that each first search request of the plurality of first search requests is associated with;

a particular type of asset of the plurality of types of assets; and

one or more particular code components, each of the one or more particular code components representing at least one of a problem with an asset, a cause of a problem with an asset, or a resolution of a problem with an asset;

identifying a parts list that identifies a plurality of parts that corresponds to the particular type of asset, each part of the plurality of parts including an asset, supply or equipment;

for each first search request of the plurality of first search requests;

facilitating a presentation of one or more sub-lists of the parts list at the corresponding first user device, each sub-list of the one or more sub-lists being a subset of the plurality of parts;

receiving a selection communication from the corresponding first user device that identifies a part from a sub-list of the one or more sub-lists;

identifying a code component corresponding to the part identified via the selection communication;

generating, based on the one or more particular code components and the code component corresponding to the part identified via the selection communication, a code that represents a combination of the one or more particular code components and the code component corresponding to the part identified via the selection communication;

incrementing the count variable associated with the code and the particular type of asset in the SQL-compatible usage data store;

receiving a second search request from a second user device that corresponds to an asset and the one or more particular code components;

classifying the asset identified in the second search request as being of the particular type of asset;

extracting, from the SQL-compatible usage data store, a plurality of count variables using one or more SQL functions, each count variable of the plurality of count variables corresponding to a combination of the one or more particular code components with at least one other code component;

for each of the plurality of count variables, generating a score for a sub-list of the parts list based on the count variable, each part identified in the sub-list corresponding to each of the one or more particular code components and to each of the at least one other code component represented in the count variable;

performing, based on the scores, a statistical filtering of a plurality of sub-lists of the parts lists that indicates that a first sub-list of the parts list is more responsive to the second search request than a second sub-list of the parts list, wherein the first sub-list is associated with a higher score than is the second sub-lists; and

facilitating a presentation that identifies one or more parts identified in the first sub-list.

16. The computer-program product as recited in claim 15, the actions further including:

generating the first sub-list by querying the parts list with the at least one other code component corresponding to a count variable of the plurality of count variables.

17. The computer-program product as recited in claim 15, wherein the presentation does not include at least one part identified in the second sub-list.

18. The computer-program product as recited in claim 15, the actions further including:

generating, based on the scores, an order for presenting identifiers of multiple sub-lists, the multiple sub-lists including the first sub-list and the second sub-list, and the order indicating that the first sub-list is to be presented before the second sub-list.

19. The computer-program product as recited in claim 15, the actions further including, for each type of the plurality of types of assets:

populating a first data structure with first code components of the plurality of code components, the first data structure being associated with a problem with an asset;

populating a second data structure with second code components of the plurality of code components, the second data structure being associated with a cause or resolution of a problem with an asset; and

establishing links between the first data structure and the second data structure, such that each of the first code components is associated with one or more second code components.

20. The computer-program product as recited in claim 19, wherein the links are configured to establish a hierarchical structure between code components in the first data structure and the second data structure.