WO2001009724A1 - Assistant d'entretien mobile - Google Patents

Assistant d'entretien mobile Download PDF

Info

Publication number
WO2001009724A1
WO2001009724A1 PCT/US2000/019662 US0019662W WO0109724A1 WO 2001009724 A1 WO2001009724 A1 WO 2001009724A1 US 0019662 W US0019662 W US 0019662W WO 0109724 A1 WO0109724 A1 WO 0109724A1
Authority
WO
WIPO (PCT)
Prior art keywords
component
set forth
maintenance
inspection
maintenance assistance
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/US2000/019662
Other languages
English (en)
Inventor
Richard K. Barto
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
CGI Technologies and Solutions Inc
Original Assignee
American Management Systems Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by American Management Systems Inc filed Critical American Management Systems Inc
Priority to AU70519/00A priority Critical patent/AU7051900A/en
Publication of WO2001009724A1 publication Critical patent/WO2001009724A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/22—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing
    • G06F11/2257—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing using expert systems
    • G—PHYSICS
    • G01—MEASURING; TESTING
    • G01R—MEASURING ELECTRIC VARIABLES; MEASURING MAGNETIC VARIABLES
    • G01R31/00—Arrangements for testing electric properties; Arrangements for locating electric faults; Arrangements for electrical testing characterised by what is being tested not provided for elsewhere
    • G01R31/28—Testing of electronic circuits, e.g. by signal tracer
    • G01R31/317—Testing of digital circuits
    • G01R31/3181—Functional testing
    • G01R31/319—Tester hardware, i.e. output processing circuits
    • G01R31/31903—Tester hardware, i.e. output processing circuits tester configuration
    • G01R31/31914—Portable Testers
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/22—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing
    • G06F11/2294—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing by remote test

Definitions

  • the present invention is directed toward a computerized system for guiding relatively inexperienced workers through a complex inspection processes on components of large, expensive and complex systems such as naval ships or large industrial facilities.
  • Massive machines of the present age are typically complex systems constructed of equally complex components, sub-assemblies and/or parts.
  • a modern day naval vessel is constructed with thousands of components, each in turn comprising their own sub-components and/or parts.
  • system is used to generically refer to an entire machine or construct, while the term component is used to refer to the individual sub-systems, assemblies or pieces of equipment that make up the entire machine or construct.
  • a system has at least one component, which, in turn, may comprise at least one component, and so-on.
  • the junior personal responsible for the initial inspection make mistakes and, as a group, produce reports of a widely varying accuracy and relevancy. This may be simply a matter of experience, but the problem is increased by a lack of language skills in our diverse work force.
  • One of the more common mistakes is the misidentification of the component being inspected, either through language problems or simple inexperience.
  • a related problem is that an experienced technician would be able to recognize that certain observed facts indicate a certain failure mode, possibly affecting other components not under inspection, that requires further inspection of items or conditions not on the checklist.
  • the experienced technicians who have the experience to produce accurate reports are typically too busy with more important matters, such as making the actual repairs, to check every report.
  • the present invention packages expert knowledge in the form of step-by-step guidelines for analyzing equipment failures, performing equipment maintenance or inspections, and generating work specifications. Access to the expert knowledge is provided by mobile computing and network technologies to enable global access to maintenance engineering knowledge and experience. By accessing the expert knowledge, users are assisted in all areas of troubleshooting that require technical expertise to evaluate the situation.
  • the invention also provides for the capture of steps used throughout the process for training, historical tracking, forecasting, and trending analysis.
  • the present invention utilizes an expert system comprised of a maintenance process knowledge base and inference engine.
  • a maintenance process knowledge base provides equipment technicians with proven repair, calibration, and "trouble shooting" information normally obtained after years and years of experience from maintaining a single system or sub-system.
  • the system records the decisions made by the technicians for use in future diagnostics and training sessions.
  • the extensive knowledge base may be used as a decision support system.
  • Transactional maintenance data stored in the knowledge base maybe analyzed to establish trends and forecasts. The results can be translated into maintenance requirements aimed at maximizing the operational availability of a system.
  • FIG. 1 is a system diagram of the preferred embodiment of the present invention.
  • FIG. 2 is a logical diagram of the preferred embodiment of the present invention.
  • FIG. 3 is a data flow diagram of the preferred embodiment of the present invention.
  • FIG. 4 is flowchart of a maintenance wizard in accordance with the preferred embodiments of the present invention.
  • FIG. 5 is a data chart of a data structure used in the preferred embodiment of the present invention.
  • processor is generally used to refer to a series of operations performed by a processor, be it a central processing unit of a computer, or a processing unit of a network device, and as such, encompasses such terms of art as "functions,"
  • the procedures are machine operations performed in conjunction with other machines and possibly human operators.
  • Useful machines for performing the operations of the present invention include general purpose digital computers, routers, switches, and other similar devices.
  • the present invention relates to method steps, software, and associated hardware configured to process electrical or other physical signals to generate other desired physical signals.
  • the apparatus set forth in the present application maybe specifically constructed for the required purposes or it may comprise a general purpose computer or other network device selectively activated or reconfigured by a computer program stored in the computer.
  • the procedures presented herein are not inherently related to any particular computer or other apparatus.
  • various general purpose machines including PDA's, laptops, and other hand-held devices, may be used with programs in accordance with the teachings herein, or it may prove more convenient to construct more specialized apparatus to perform the required method steps.
  • it is desirable that a piece of hardware possess certain characteristics, these characteristics are described more fully in the following text.
  • the required structures for variety of these machines will appear in the description given below.
  • Machines which may perform the functions of the present invention include those manufactured by such companies as Hewlett Packard, Inc., International Business Machines, Inc., CISCO, Inc., 3COM
  • the application sets forth the best mode of the invention as being utilized in connection with network, including a local area network and a TCP/IP network (commonly referred to as a Intranet or Internet), however, one of ordinary skill in the art will recognize that the present invention is suitable for use on any communication network from which the appropriate data may be collected.
  • the best network protocol and associated hardware is heavily dictated by the actual use to which the invention is put in conjunction with the present state of the art in communication systems.
  • Those of ordinary skill in the art recognize that other current and future communication systems will support use of the present invention, such that the invention is not limited to any particular network, but applicable to a broad range of networks.
  • FIG. 1 is a system diagram of the present invention.
  • the present invention utilizes a data structure to assist in identifying the component being inspected and a related expert system to guide users through an individualized inspection operation.
  • the database generates work orders based on the data produced during the inspection and can track inspections and repairs to provide statistical data.
  • the setting shown in FIG. 1 is that of a system suitable for use by the U.S. Navy.
  • Those of ordinary skill in the art will recognize the adaptability of the present invention to other fields of endeavors, including, but not limited to, any organization that has a large population of physical assets that requires periodic or planed maintenance to be performed such as: other military organizations; large equipment manufacturing; computer equipment manufacturers; and any service companies performing maintenance on residential/commercial equipment.
  • FIG. 1 shows a variety of configuration possibilities as examples only.
  • the processing system 10 acts as a central repository for an expert system which provides interactive maintenance routines, diagnosis, repair scheduling, and statistical analysis .
  • An expert system which provides interactive maintenance routines, diagnosis, repair scheduling, and statistical analysis .
  • Commonly available expert systems may be used, the exact selection of which will vary based on how the present invention is implemented.
  • the use of such expert systems, including the population of data therein is largely beyond the scope of the present invention. While examples of data structures usable by such expert systems will be discussed, non-essential details regarding the use of such expert systems are omitted so as to avoid obscuring the invention.
  • the processing system 12 acts as a database for equipment/component data (one example of a usable data structure is given herein below), and the processing system 14 acts as a database for maintenance policy/procedures (one example of a usable data structure is given herein below).
  • the processing systems 10, 10a, and 10b serve the expert system stored in the central repository to the maintenance personal inspecting the system under consideration. In the example shown in FIG. 1, maintenance personal access the expert system for interactive instructions on performing inspection and maintenance tasks on components of United States Naval Vessels.
  • the processing system 14 is connected to the WAN 16 by a local area network (LAN) 18a, while the processing system 12 is connected via a LAN 18b and the processing system 10 is connected by a LAN 18c.
  • LAN local area network
  • the central repository for the expert system is shown as being replicated on processing systems 10a and 10b.
  • the various data functions of the present invention are shown as being split among the processing systems 10 - 14, but those of ordinary skill in the art will recognize that this is a matter of convenience only. The function could reside on a single computer or be further distributed.
  • the replicated processing systems 10a and 10b are connected to local maintenance sites
  • the replicated central repository of the expert system stored on the replicated processing system 10a connects to the local maintenance site 22a, which is a shipyard, via a shipyard LAN 18d.
  • the replicated central repository of the expert system stored on the replicated processing system 10b connects to the local maintenance site 22b, which is a ship, via a ship to shore LAN 18e utilizing a satellite 20.
  • maintenance personal utilize a variety of computing devices 24, including a laptop 24a and a handheld PC 24b, to access the procedures of the expert system.
  • the computing device 24 be portable to allow maintenance personal to carry the computing device 24 with them on each inspection. It is, however, conceivable that each component that requires maintenance be provided with a computing device. Depending on the computing power and storage capabilities of the computing devices 24, various units of the expert system are served thereto. For example, it is not inconceivable that future portable computing devices will have the power and capacity to hold the entire system including the expert system, component data and maintenance policies. Many small handheld devices (including personal data assistants (PDAs) such at 3 Corn's PALM®) can store parts of the system, such as the information and routines for a type of component. Currently, wireless portable devices are entering the market.
  • PDAs personal data assistants
  • FIG. 2 is a logical diagram of the present invention.
  • the expert system starts with a routine for identifying the component being inspected.
  • the computing device 24 accesses an equipment breakdown structure 32 (also known as the component breakdown structure) which maintains a hierarchal list of the various components of the system being maintained and prompts the user to select the appropriate component.
  • equipment breakdown structure 32 also known as the component breakdown structure
  • the formation of the equipment breakdown structure 32 is performed with standard database management tools.
  • each component can be tagged, such as with a bar code or low frequency transmitter to immediately and uniquely identify the component to the computing device using the low frequency receiver 28 or the bar code scanner 30.
  • the equipment breakdown structure 32 is linked to a relational database management system (RDBMS) 34 (such as ORACLE®) which records statistical data, such as the number of times each component is inspected.
  • RDBMS relational database management system
  • ORACLE® relational database management system
  • the instruction process interactively guides maintenance personal through an inspection routine.
  • the fault logic tree 38 is formed as a data structure described hereinbelow. The fault logic tree is based upon Reliability-Centered Maintenance
  • the maintenance personal has a digital camera, he or she can be instructed to take a picture of the component to be sent with the observations. Such a digital image may provide the personal who perform any required maintenance with additional insight. If a digital camera is used, obj ect recognition technology may be used to automatically identify the component and/or characteristics thereof.
  • the RDBMS 34 is also linked to the step by step instruction procedure 36 (including the fault logic tree 38) for maintaining statistical information including information on the faults experienced by each component.
  • the output of the step by step instruction process 38 is a work specification 40 and related reports.
  • An example of a work specification is set forth herein below.
  • the various reports may be linked to the RDBMS 34 for future statistical analysis.
  • FIG. 3 is a data flow diagram of the present invention.
  • the computing device accesses (either through a communication link or, given sufficient computing power, internally) maintenance wizard 42 (wizard being a term of art for any help system) to present to the user interactive displays 50 to guide the user through an inspection procedure on the identified component.
  • the maintenance wizard 42 accesses the equipment breakdown structure 32 and a business rule data base 44 to guide the inspection and produce the work specification 40.
  • the Data Architecture of the maintenance wizard 42 is preferably object oriented and designed with the rigor of a formal definition of a programming language grammar. This grammar consists of a set of category definitions, relationships, and rules presented in Backus- Naur form (BNF). At a high level, the architecture initially consists of five major syntactic categories; Events, Equipment Obj ects, Nodes, and Diagnostic Primitives. The relationships and rules provide the operational processing.
  • the Events are user or system selected to initiate application processing.
  • the selected event together with the associated Equipment Object, triggers the diagnostic processes.
  • Event : : ⁇ Inquiry Event // Inspection Event // Failure Event // Diagnostic Event // Repair Option Event // Decision Event // Report Event // other to be defined later ⁇
  • the Equipment Objects will have identification information, component information, and tracking/trending information from a historical perspective.
  • Each piece of equipment will be defined with a complete component breakdown structure in the equipment breakdown structure 32.
  • each component will have a relationship with one or more categories of inspections/failures modes. These categories will be equipment specific and may include classifications, such as Structural, Mechanical, Electrical, etc. where appropriate.
  • the equipment object would also contain the pointers to the initial node for processing according to selected events.
  • the nodes are the building blocks of the diagnostic process, which is implemented internally as a directed (critical path) graph.
  • the graph consists of a minimum of two nodes.
  • the selection of the initial node is triggered via information from the equipment object and the event.
  • the initial node is responsible for setting up the dynamic processing and tracking mechanism. Additional nodes selection is performed based on most recent action, preset specifications, or for equipment failures, most probable cause or most severe consequences criteria.
  • Each node will invoke navigational aids, business rules, scripts, queries, and data primitives to perform each diagnostic procedure.
  • Successess indicator to indicate the successful path.
  • the node is originally marked as successful. As unfruitful paths are explored and backtracked, the node will be marked unsuccessful and will not be included in the final resolution path tracking;
  • a Business Rule is an equipment/site specific guideline to provide direction in the process of the associated event. Based on the equipment component and a minimum/maximum/acceptable range for the measure of failure (or inspection), the business rule will provide the direction.
  • the direction may be in the form a repair option or an inspection guideline.
  • a Script is a grammar structure that provides a representation of a stereotyped situation by building a coherent interpretation from a collection of observations and data elements.
  • the script has an entry condition that must be met in order to trigger the processing of the script.
  • the data from the equipment object, the triggering Event, and nodal primitive is associated with each slot in the script to develop a meaningful scenario. For any null valued data element in the object, event, or primitive, a default data element will be associated and used within the script.
  • the output from scripts may be the generation of instructions, documentation, work specifications, or other system defined products.
  • a script may also be used to build the parameters for invoking an external program or trigger an internal or database process.
  • a query is a user interface mechanism to collect observations and assist in navigating the alternatives in the critical path.
  • the query mechanism will be used to insert data into the required fields of the data primitive.
  • a data primitive is an atomic level data structure.
  • Primitive templates may be used for potential failure modes or inspection criteria. Accordingly these primitives form the fault logic tree 38. They are developed and loaded at the initial creation of the application. These templates provide the definition of data elements to be collected during the processing of the application. Additional primitive templates may be added dynamically through a drag/drop or user key entry to define the meta-data for the template. During this process the user will define the number of data elements (n-tuple) and the definition, data type, and default values for each field of the tuple. These primitives will be used to either guide the step-by-step diagnostics or store results of inspections.
  • the severity and priority fields allow the system to notify maintenance personal how serious the situation is to enable efficient work planning.
  • Inspection Primitive eight-tuple consisting of (verb, measure, measure tolerance, acceptable lower bound, acceptable upper bound, pass/fail, recommended action)
  • FIG. 4 is flowchart of the maintenance wizard 42 in accordance with the preferred embodiments of the present invention.
  • the procedure starts in step SI with the login of the user.
  • steps S2 through S3 the component is selected.
  • step SI the appropriate equipment breakdown structure 32 is accessed (either through user choice or automatically as being pre-programmed or using a bar code or the like).
  • step S3 the top level component is selected using the selected equipment breakdown structure 32.
  • step S4 the actual component (sub-component) being inspected is selected from the equipment breakdown structure 32.
  • This process may require a plurality of iteration to dig down to the correct component, Fig. 4 only shows three levels by way of example. As noted above, this step can be automated using a variety of mechanisms, such as bar coding and low frequency transmitters.
  • step S5 the business rules database 44 is accessed and failure modes are identified.
  • step S6 a fault tree analysis is performed by accessing the fault tree tables 46 (forming the fault tree logic 38) and an equipment history database 48.
  • a knowledge and inference engine (not shown) can be used to identify the most recent, sever or most common failures to aid in navigating the fault-tree paths.
  • step S7 a work specification 40 is generated. Other reports, such as an estimate report 40a can also be generated.
  • FIG. 5 is a data chart of a data structure which may be used in the present invention. This is provided as an example for those of ordinary skill in the art. Many possible variations would produce a usable system. The following chart describes the elements in the data chart.
  • the system utilizes the failure diagnostic business rules, failure description primitives, and inspection primitives to output work specifications 40.
  • the following is an example of such a specification:
  • MIL-STD-1310 Shipboard Bonding, Grounding, and Other Techniques for Electromagnetic Compatibility and Safety
  • GOVERNMENT FURNISHED MATERIAL GMM
  • such a work specification is automatically prepared based upon an inspection routine.
  • the system can easily be adapted to produce time estimates and be integrated into a work scheduling system.
  • the system can interface with a statistical RDBMS for the creation of statistical forecasting, and/or trending reports, such as breakdown/repair frequency reports. Using these reports, the users and suppliers of the components can redesign maintenance program tasks when certain failure modes are noted.

Landscapes

  • Engineering & Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Hardware Design (AREA)
  • Quality & Reliability (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

La présente invention concerne un système d'assistance à l'entretien servant à guider un inspecteur lors d'un processus d'inspection d'un composant d'un système. Un système de traitement principal possède en mémoire et dessert une structure de dépannage de composant destinée au système, permettant l'identification du composant. Le système de traitement principal dessert également une assistance à l'inspection, en général sous la forme d'un système d'expert, qui a accès à une structure de données servant à guider l'inspecteur dans le processus d'inspection. L'inspecteur a accès à la structure de dépannage de composant et à l'assistance à l'inspection par l'utilisation d'un système de traitement à distance, tel qu'un assistant de données personnel ou qu'un ordinateur portatif, ce qui permet une inspection sur place. Le système d'entretien enregistre les observations de l'inspecteur et produit une spécification de travail décrivant l'entretien dont a besoin le composant.
PCT/US2000/019662 1999-07-28 2000-07-20 Assistant d'entretien mobile Ceased WO2001009724A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU70519/00A AU7051900A (en) 1999-07-28 2000-07-20 Mobile maintenance assistant

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US36210899A 1999-07-28 1999-07-28
US09/362,108 1999-07-28

Publications (1)

Publication Number Publication Date
WO2001009724A1 true WO2001009724A1 (fr) 2001-02-08

Family

ID=23424733

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2000/019662 Ceased WO2001009724A1 (fr) 1999-07-28 2000-07-20 Assistant d'entretien mobile

Country Status (2)

Country Link
AU (1) AU7051900A (fr)
WO (1) WO2001009724A1 (fr)

Cited By (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1286281A1 (fr) * 2001-08-14 2003-02-26 Neumann & Neumann Projekt- und Beratungs GmbH Méthode et système d'ordinateur pour contrôler la qualité d'un service de nettoyage
WO2002091004A3 (fr) * 2001-05-09 2003-06-05 Adc Telecomm Israel Ltd Poste d'essai et de programmation de bord
EP1321871A1 (fr) * 2001-12-20 2003-06-25 Neumann & Neumann Projekt- und Beratungs GmbH Procédé et système informatique pour l'assurance de la qualité, notamment du l'entretien des appareils ou dispositifs
EP1239371A3 (fr) * 2001-03-06 2003-09-17 Hewlett-Packard Company Essai à distance d'un ordinateur
WO2009037042A3 (fr) * 2007-09-14 2010-01-21 Siemens Aktiengesellschaft Procédé et dispositif de détermination d'une probabilité d'admission
US8090462B2 (en) 2007-12-19 2012-01-03 Mobideo Technologies Ltd Maintenance assistance and control system method and apparatus
US20120221371A1 (en) * 2009-07-02 2012-08-30 Tarek Hegazy System, method and computer program for asset management optimization
US11074297B2 (en) 2018-07-17 2021-07-27 iT SpeeX LLC Method, system, and computer program product for communication with an intelligent industrial assistant and industrial machine
US11232262B2 (en) 2018-07-17 2022-01-25 iT SpeeX LLC Method, system, and computer program product for an intelligent industrial assistant
US11514178B2 (en) 2018-07-17 2022-11-29 iT SpeeX LLC Method, system, and computer program product for role- and skill-based privileges for an intelligent industrial assistant
US11803592B2 (en) 2019-02-08 2023-10-31 iT SpeeX LLC Method, system, and computer program product for developing dialogue templates for an intelligent industrial assistant
US20250174341A1 (en) * 2023-11-27 2025-05-29 Koninklijke Philips N.V. Systems and methods for generating customized maintenance instructions for biomedical engineers

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1988005918A1 (fr) * 1987-02-06 1988-08-11 Analytics Incorporated Systeme de maintenance
US5751933A (en) * 1990-09-17 1998-05-12 Dev; Roger H. System for determining the status of an entity in a computer network
US5899947A (en) * 1997-06-30 1999-05-04 Daimlerchrysler Corporation Current check module for hand-held vehicle tester

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1988005918A1 (fr) * 1987-02-06 1988-08-11 Analytics Incorporated Systeme de maintenance
US5751933A (en) * 1990-09-17 1998-05-12 Dev; Roger H. System for determining the status of an entity in a computer network
US5899947A (en) * 1997-06-30 1999-05-04 Daimlerchrysler Corporation Current check module for hand-held vehicle tester

Cited By (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1239371A3 (fr) * 2001-03-06 2003-09-17 Hewlett-Packard Company Essai à distance d'un ordinateur
US6904389B2 (en) 2001-03-06 2005-06-07 Hewlett-Packard Development Company, L.P. Remote computer testing
WO2002091004A3 (fr) * 2001-05-09 2003-06-05 Adc Telecomm Israel Ltd Poste d'essai et de programmation de bord
EP1286281A1 (fr) * 2001-08-14 2003-02-26 Neumann & Neumann Projekt- und Beratungs GmbH Méthode et système d'ordinateur pour contrôler la qualité d'un service de nettoyage
EP1321871A1 (fr) * 2001-12-20 2003-06-25 Neumann & Neumann Projekt- und Beratungs GmbH Procédé et système informatique pour l'assurance de la qualité, notamment du l'entretien des appareils ou dispositifs
US8364626B2 (en) 2007-09-14 2013-01-29 Siemens Aktiengesellschaft Method and device for determining a probability of occurrence by evaluting an overall fault tree
WO2009037042A3 (fr) * 2007-09-14 2010-01-21 Siemens Aktiengesellschaft Procédé et dispositif de détermination d'une probabilité d'admission
US8090462B2 (en) 2007-12-19 2012-01-03 Mobideo Technologies Ltd Maintenance assistance and control system method and apparatus
US20120221371A1 (en) * 2009-07-02 2012-08-30 Tarek Hegazy System, method and computer program for asset management optimization
US11074297B2 (en) 2018-07-17 2021-07-27 iT SpeeX LLC Method, system, and computer program product for communication with an intelligent industrial assistant and industrial machine
US11232262B2 (en) 2018-07-17 2022-01-25 iT SpeeX LLC Method, system, and computer program product for an intelligent industrial assistant
US11514178B2 (en) 2018-07-17 2022-11-29 iT SpeeX LLC Method, system, and computer program product for role- and skill-based privileges for an intelligent industrial assistant
US11651034B2 (en) 2018-07-17 2023-05-16 iT SpeeX LLC Method, system, and computer program product for communication with an intelligent industrial assistant and industrial machine
US11803592B2 (en) 2019-02-08 2023-10-31 iT SpeeX LLC Method, system, and computer program product for developing dialogue templates for an intelligent industrial assistant
US20250174341A1 (en) * 2023-11-27 2025-05-29 Koninklijke Philips N.V. Systems and methods for generating customized maintenance instructions for biomedical engineers

Also Published As

Publication number Publication date
AU7051900A (en) 2001-02-19

Similar Documents

Publication Publication Date Title
Muhlbauer Pipeline risk management manual: ideas, techniques, and resources
JP2010530062A5 (fr)
WO2001009724A1 (fr) Assistant d'entretien mobile
Adesina et al. A Short communication: Improving marine safety management system by addressing common safety program failures
Abi-Zeid et al. Is CBR applicable to the coordination of search and rescue operations? A feasibility study
Soehadi et al. Technology content assessment for Indonesia-cable based tsunameter development strategy using technometrics model
Mitev The business failure of knowledge-based systems: linking knowledge-based systems and information systems methodologies for strategic planning
Hedderich Navy proactive maintenance
Doskey et al. A measure of systems engineering effectiveness in government acquisition of complex information systems
Lynch Reducing Logistics Delays Using the Supply Chain Criticality Index: A Diagnostic Approach
Murphy Machinery monitoring technology design methodology for determining the information and sensors required for reduced manning of ships
Stoelsnes et al. On the importance of human and organizational factors in design, construction and installation of engineered systems
Colegrove et al. Condition-Based Unmanned Undersea Vehicle Maintenance Monitoring and Prediction System (C-BUMMPS)
Utomo et al. Technology performance of Indonesia tsunami early warning system: technometric approach.
Amato An Analysis of Application Type, Super Domain, and Productivity in Software Intensive Defense Acquisitions
Romeu Reliability Analysis Center
Pritchett A systematic approach to reliability-centered maintenance
Setiawan et al. The functional contribution of ship safety inspectors in nautical, technical, and communication (radio) inspection processes to workload and maritime transportation safety
Vafaie et al. CORMS AI: decision support system for monitoring US maritime environment
Cottam et al. Knowledge acquisition for search and rescue
Schank et al. Learning from Experience, Volume 1: Lessons from the Submarine Programs of the United States, United Kingdom, and Australia
Sponseller New approaches to the integration of organizational maintenance and failure data during submarine maintenance planning
Townsend Project Management and Systems Engineering Guide
Osborn Handbook for the Development of Skill Qualification Tests
Ammerman Performance Content for Job Training. Volume 2. Stating the Tasks of the Job. Research and Development Series No. 122.

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AL AM AT AU AZ BA BB BG BR BY CA CH CN CU CZ DE DK EE ES FI GB GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT UA UG UZ VN YU ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: JP