Managing Service Requirements for Airports

• US 20070192154A1
• Filed: 01/29/2007
• Published: 08/16/2007
• Est. Priority Date: 02/10/2006
• Status: Abandoned Application

• Current Assignee: Siemens Corp. (Siemens AG)
• Original Assignee: Siemens Corporate Research Incorporated (Siemens AG)
• Inventors: Chakraborty, Amit, Mukherjee, Saikat, Viswanathan, Ramesh, Camuti, Paul
• Application Number:
  US11/668,113
• Publication Number:
  US 20070192154A1
• Time in Patent Office: Days
• US Class Current: 705/7.25
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: G06Q 10/06315 Needs-based resource requirements planning or analysis
• CPC Class Codes: Y02P 90/02 Total factory control, e.g. smart factories, flexible manufacturing systems [FMS] or integrated manufacturing systems [IMS]
• CPC Class Codes: Y02P 90/80 Management or planning

Abstract

Disclosed is a method for the creation of maintenance plans. The maintenance plans are created by determining the service requirements for equipment, and normalizing the service requirements. These service requests are formalized in the language of XML Schema and semantic heterogeneity between different plans resolved with the use of ontologies. The matched service requests are combined to form the global service plan. Finally, resources may then be allocated to execute the created maintenance plans and appropriate maintenance schedules are identified based in the created maintenance plans.

Claims

1. A method of creating maintenance plans for a plurality of equipment comprising:

analyzing service requirements of at least two pieces of equipment to standardize service requirements, at least one of said pieces of equipment having non-standard service requirements;

creating standardized service requirements for the at least one piece of equipment having non-standard service requirements; and

creating a maintenance plan using the standardized service requirements.

2. The method of claim 1 further comprising allocating resources to the maintenance plan.

3. The method of claim 2 further comprising determining maintenance schedules from the maintenance plan.

4. The method of claim 1 wherein creating standardized service requirements comprises resolving semantic heterogeneity between names of activities in the service requirements through the use of ontological domain knowledge.

5. The method of claim 1 wherein the service requirements are determined from equipment state data.

6. The method of claim 1 wherein the service requirements are determined from maintenance schedules.

7. The method of claim 1 wherein the service requirements are standardized using data from a maintenance knowledgebase.

8. The method of claim 1 wherein the service requirements are standardized using input from a service schema.

9. The method of claim 8 wherein the service schema is an XML schema.

10. The method of claim 8 wherein an instance of the service schema represents a single servicing request and includes activities, precedence and duration constraints.

11. The method of claim 10 further comprising the step of modeling the precedence constraints as a temporal ordering among activities and modeling duration constraints with specific start and end times between which the activities must be performed.

12. The method of claim 1 wherein the maintenance plans bring together service requests for different types of equipment from different manufacturers.

13. The method of claim 12 further comprising the step of modeling the service requests as a collection of rules where each rule has certain conditions which when satisfied trigger associated service requests.

14. The method of claim 1 wherein the maintenance plans are for equipment from different manufacturers.

15. The method of claim 1 wherein the service requirements have standardized activity references.

16. The method of claim 1 wherein the service requirements have standardized resource references.

17. The method of claim 1 wherein the service requirements are modeled as activities which consume resources.

18. The method of claim 17 wherein the activities in the servicing request include an associated name, cost, required resources, and are hierarchically decomposed into subactivities.

19. The method of claim 17 further comprising the step of modeling the resources with a name, cost and an attribute which indicates whether the resources are renewable or non-renewable.

20. A system for creating maintenance plans for a plurality of equipment comprising:

means for analyzing service requirements of at least two pieces of equipment to standardize the service requirements, at least one of said pieces of equipment having non-standard service requirements;

means for creating standardized service requirements for the at least one piece of equipment having non-standard service requirements; and

means for creating a maintenance plan using the standardized service requirements.

21. The system for claim 20 further comprising means for allocating resources to the maintenance plan.

22. The system for claim 21 further comprising means for determining maintenance schedules from the maintenance plan.

23. The system for claim 20 wherein means for creating standardized service requirements comprises means for resolving semantic heterogeneity between names of activities in the service requirements through the use of ontological domain knowledge.

24. The system for claim 20 wherein the service requirements are determined from equipment state data.

25. The system for claim 20 wherein the service requirements are standardized using data from a maintenance knowledgebase.

26. The system for claim 20 wherein the service requirements are standardized using input from a service schema.

27. The system for claim 20 wherein the service requirements have standardized activity references.

28. The system for claim 20 wherein the service requirements have standardized resource references.

29. A computer readable medium storing computer program instructions for performing a method of creating maintenance plans for a plurality of equipment which, when executed by a processor, perform the steps of:

analyzing service requirements of at least two pieces of equipment to standardize the service requirements, at least one of said pieces of equipment having non-standard service requirements;

creating standardized service requirements for the at least one piece of equipment having non-standard service requirements; and

creating a maintenance plan using the standardized service requirements.

30. The computer readable medium of claim 29 wherein said computer program instructions further perform the step of allocating resources to the maintenance plan.

31. The computer readable medium of claim 29 wherein creating standardized service requirements comprises resolving semantic heterogeneity between names of activities in the service requirements through the use of ontological domain knowledge.

32. The computer readable medium of claim 29 wherein the service requirements are standardized using input from a service schema.