Method and system for providing a generic query interface

Abstract

A query processing system for providing a generic query interface for different customers' industrial systems, wherein the query processing system (1) comprises: - an application query interface AQI (2) adapted to input a customer query Q of a customer's industrial system; - a query processing unit (4) configured to automatically perform a query decomposition of the input customer query Q into query parts QP based on a query reformulation model QRM stored in a database (5) of the query processing system (1), wherein for each decomposed query part QP it is determined by the query processing unit (4) whether the decomposed query part is available in an application semantic model ASM stored in a database (6) of the query processing system (1), wherein the query processing unit (4) is further configured to automatically reformulate query parts not available in the application semantic model ASM based on the query reformulation model QRM and to automatically perform a query recombination of the query parts available in the application semantic model ASM and the reformulated semantic query parts to generate a generic query gQ which is applied to an application logic (3) of the query processing system (1) to provide a query result QR output by the application query interface AQI (2).

Description

Technical Field

[0001] This invention relates to a method and system for providing a universal query interface for industrial systems of different customers. Background Technology

[0002] Current software systems used for information retrieval and filtering are typically designed with a layered architecture, such as... Figure 1 As shown in the diagram. Figure 1 This illustrates a typical multi-layered interface design for a software system. At the lowest layer (L0) of the multi-layered interface design, there exists a customer layer containing customer-specific APIs for the customer or OEM. Typically, specific interface features are required for different customers or technical fields. These technical fields may include, for example, automotive AUT, metal handling MET, automation ATM, or any other type of technical field. Each technical field may include one or more APIs for different customers or OEMs, such as… Figure 1 As shown in the diagram.

[0003] The next layer, L1, of the multi-layer interface provides the available interface functionality of the data cloud backend software, MSS. This MSS is visible to client interface designers who provide different types of functionality, enabling them to implement their own client interfaces. Functionality provided in layer L1 can include asset manipulation (ASS-M), such as creating, modifying, deleting, or retrieving assets. Additionally, it can include event manipulation (EV-M), such as creating, modifying, deleting, or retrieving events. The graph traversal functionality (GT) can include: obtaining asset portions, obtaining asset subclasses, obtaining event subclasses, or obtaining related elements.

[0004] Figure 1 The next layer (L2) below the multi-layered interface illustrated in the diagram includes a generic interface, namely the generic SPARQL endpoint MSG EP for the data cloud backend. This generic interface of layer L2 provides a highly general query interface based on a query language. The query language can be, for example, a modern database language (such as SQL) or a more advanced semantic query language (such as SPARQL). Layer L2 itself operates on a specific data model (such as a database model or a semantic model).

[0005] If a user triggers a query at the client layer L0, the interface logic can access information from the data cloud backend system (such as a MindSphere system) by calling interface routines from the next lower layer upwards (e.g., asset manipulation method calls). The interface logic itself then uses a SPARQL query to invoke a SPARQL endpoint for asset manipulation. The SPARQL query can operate on the semantic model of the WebSphere application. Layer L3 may include the data cloud backend semantic model extension MSSMExt. Layer L4 may include the data cloud backend data model (with a REST-based API).

[0006] Different layers L of a multi-tiered interface can decouple a more general, generic query interface (such as a SPARQL endpoint) from the end user (e.g., an OEM). The generic interface of layer L2 does indeed provide different interfaces for different customers by attaching or using the same data model.

[0007] The creation of different interface layers L for each customer has led to increased development effort. One possible approach to interface design is to expose end users (such as OEMs) to an interface (such as a SPARQL endpoint) that is as close as possible to the data model. However, the main problem with this is that end users who should use a generic query interface (e.g., a SPARQL endpoint) need a deep understanding of the data model, as it would be impossible for them to formulate the query without that knowledge.

[0008] Without knowing that the model contains assets, users cannot retrieve information about them. If users are accustomed to the term "device" (which could be an asset in the data cloud backend), then a customer-specific user interface or customer training is necessary. Summary of the Invention

[0009] Therefore, the object of the present invention is to provide a method and system for providing a universal query interface for industrial systems of different customers, wherein customers can interact with the interface with little or no knowledge of the underlying industrial system.

[0010] According to a first aspect of the invention, this objective is achieved by a method that provides a universal query interface for a customer's industrial system, and provides the features of claim 1.

[0011] According to a first aspect, the present invention provides a method for providing a general query interface for a customer's industrial system.

[0012] The method includes the following steps:

[0013] Based on the stored query reformulation model, query decomposition is performed on the customer query input from the application query interface of the customer's industrial system, down to the query portion.

[0014] Determine whether the decomposed query components of the received customer query are available in the stored application semantic model.

[0015] Based on the query redefinition model, this method redefines query portions that are unavailable in the applied semantic model.

[0016] Perform query reorganization on the available query portions and redefined query portions in the application semantic model to generate a general query that is applied to the application logic to provide query results.

[0017] In a possible embodiment of the method according to the first aspect of the invention, the stored query redefinition model includes: a mapping of terms of model elements between client-specific terms and applied semantic model terms of the applied semantic model, and transformation rules used to translate model terms.

[0018] In another possible embodiment of the method according to the first aspect of the invention, the stored application semantic model includes an ontology model.

[0019] In still other possible embodiments of the method according to the first aspect of the invention, the mapping of terms for model elements includes: mapping between data source terms, mapping between event source terms, and mapping between other information terms.

[0020] In yet another possible embodiment of the method according to the first aspect of the invention, the generated general query is transmitted to application logic via a local and / or global network, which processes the received general query based on a general data model of the industrial system to calculate the general query result.

[0021] In yet another embodiment of the method according to the first aspect of the invention, the calculated general query results are refactored into customer-specific query results based on the stored query refactoring model, and output using the application query interface of the customer's industrial system.

[0022] According to a second aspect, the present invention also provides a query processing system including the features of claim 7.

[0023] According to a second aspect, the present invention provides a query processing system for providing a universal query interface for industrial systems of different customers.

[0024] The query processing system includes:

[0025] At least one application query interface is provided, which is adapted to customer queries input into the customer's industrial system.

[0026] The query processing unit is configured to automatically decompose an input customer query into query parts based on a query redefinition model stored in the query processing system's database. For each decomposed query part, the query processing unit determines whether the decomposed query part is available in the application semantic model stored in the query processing system's database.

[0027] The query processing unit is further configured to: automatically rewrite query parts that are not available in the application semantic model based on the query formulation model, and automatically perform query reorganization on the query parts available in the application semantic model and the rewritten semantic query parts to generate a general query. This general query is applied to the application logic of the query processing system to provide query results output by the application query interface.

[0028] In yet another possible embodiment of the query processing system according to the second aspect of the invention, the stored query redefinition model includes: a mapping of terms of model elements between client-specific terms and applied semantic model terms of the applied semantic model, and transformation rules used to translate model terms.

[0029] In a possible embodiment of the query processing system according to the second aspect of the present invention, the stored application semantic model includes an ontology model.

[0030] In yet other possible embodiments of the query processing system according to the second aspect of the invention, the mapping of terms for model elements includes: mapping between data source terms, mapping between event source terms, and mapping between other information terms.

[0031] In another possible embodiment of the query processing system according to the second aspect of the invention, the generated general query is transmitted to application logic via a local or global network, the application logic being adapted to process the received general query based on the general data model stored in the industrial system to calculate the general query result.

[0032] In another possible embodiment of the query processing system according to the second aspect of the invention, the query processing unit refactors the calculated general query results into customer-specific query results based on a stored query refactoring model, wherein the customer-specific query results are output via the application query interface of the customer's industrial system.

[0033] In another possible embodiment of the query processing system according to the second aspect of the invention, the query processing unit includes a local query processing unit or a remote query processing unit implemented on the service provider's server.

[0034] In yet another possible embodiment of the query processing system according to the second aspect of the invention, the query redefinition model is decentralized.

[0035] In yet another possible alternative embodiment of the query processing system according to the second aspect of the invention, the query redefinition model is stored in the service provider's central database.

[0036] In another possible embodiment of the query processing system according to the second aspect of the invention, the application query interface includes a user interface for receiving customer queries input by users of the industrial system.

[0037] In yet another possible embodiment of the query processing system according to the second aspect of the invention, the application query interface includes: a data interface for receiving customer queries generated by the controller of the industrial system. Attached Figure Description

[0038] In the following description, various possible embodiments of the invention are described in more detail with reference to the accompanying drawings.

[0039] Figure 1 A diagram illustrating the general structure of a conventional multilayer interface is shown;

[0040] Figure 2 A schematic diagram illustrating possible exemplary embodiments of the method and system according to the present invention is shown;

[0041] Figure 3 A block diagram illustrating a possible exemplary embodiment of a query processing system according to aspects of the present invention is shown;

[0042] Figure 4 A flowchart illustrating a possible exemplary embodiment of a method for providing a general query interface for a customer's industrial system, according to an aspect of the present invention, is shown. Detailed Implementation

[0043] Figure 2 A possible exemplary embodiment of the query processing system (QPS) 1 according to aspects of the present invention is illustrated schematically. Figure 2 The query processing system 1 illustrated herein can be used to provide a universal query interface for industrial systems of different customers. Customers can be, for example, manufacturing companies operating in the same technical field. For instance, customers could be different automobile companies using similar manufacturing processes to produce vehicles. Figure 2The schematic block diagram illustrates that the query processing system 1 according to the present invention includes: at least one application query interface (AQI) 2, adapted to input a customer query Q into a customer's industrial system (such as a manufacturing facility). The end user of the customer or manufacturing company can access an application executed by the processing entity via the application user interface, which may include some type of application query interface AQI, such as... Figure 2 As illustrated in the diagram. Application Query Interface 2 allows for monitoring, diagnostics, or information retrieval. Application Query Interface AQI 2 can generate... Figure 2 The diagram illustrates the front end of application logic 3 in the software system. A portion of application logic 3 consists of query endpoints that lead to a database storing the Application Semantic Data Model (ASM). Based on these components of the system, user queries Q can be processed and answered. In possible embodiments, the application query interface (AQI) can also be multi-layered.

[0044] Figure 2 The query processing system 1 illustrated in the figure includes a query processing unit (QPU) 4, which is configured to automatically decompose an input customer query Q into query parts based on a query redefinition model (QRM) stored in a database 5 of the query processing system 1. For each decomposed query part QP, the query processing unit 4 can determine whether the decomposed query part is available in an application semantic model (ASM) stored in a database 6 of the query processing system 1. The application semantic model (ASM) includes a semantic description of the application, which includes data sources, system events, and additional information (such as diagnostic conditions). The query processing unit 4 is further configured to automatically redefine query parts QP that are not available in the application semantic model (ASM) based on the query redefinition model (QRM), and automatically perform query reorganization on the available query parts QP in the application semantic model (ASM) and the redefined semantic query parts QP to generate a general query. The query processing unit 4 then applies the generated general query to the application logic 3 of the query processing system 1 to provide query results. The query results are output to the user of the industrial system via an application query interface 2.

[0045] In a possible embodiment, the Query Re-engineering Model (QRM) stored in database 5 may include: a mapping of terms for model elements between client-specific terms and application semantic model (ASM) terms, and transformation rules for translating model terms. In a possible embodiment, the application semantic model (ASM) stored in database 6 may include an ontology model. The mapping of terms for model elements may include, for example, mappings between data source terms, mappings between event source terms, and mappings between other information terms.

[0046] In possible embodiments, the generic query gQ generated by query processing unit 4 can be transmitted or provided to application logic 3 via a local and / or global network. The application logic 3 of the system is adapted to process the received generic query gQ based on a stored generic data model of the industrial system to calculate a generic query result gQR. In possible embodiments, query processing unit 4 can refactor the calculated generic query result gQR into a customer-specific query result based on a stored query redefinition model QRM. The customer-specific query result is then output via the application query interface (AQI) of the customer's industrial system. In possible embodiments, query processing unit 4 of the query processing system may include a local query processing unit at a site on the customer's industrial system. In alternative embodiments, query processing unit 4 of query processing system 1 may include a remote query processing unit implemented on a remote server of a service provider. Furthermore, the query redefinition model QRM may be stored in a distributed manner at different sites, particularly at sites within the industrial system, in possible implementations. Additionally, in alternative embodiments, the query redefinition model QRM may also be stored in a central database of the service provider.

[0047] The Application Query Interface (AQI) 2 of the query processing system 1 may include a user interface for receiving customer query Q input by a user of the customer's industrial system. The Application Query Interface AQI 2 may further include a data interface for receiving customer queries generated by the controller of the customer's industrial system.

[0048] The query processing unit (QPU) 4 may include a query redefinition inference engine. This inference engine can block the direct link between the application query interface (AQI) and the application logic (AL) 3. In a possible embodiment, a query input to the application query interface (AQI) 2 of system 1 can be immediately intercepted by the query redefinition inference engine of the query processing unit 4. In a possible embodiment, the query processing unit 4 may include a query decomposition module 4A adapted to decompose the received query Q into individual terms. In a possible embodiment, the query decomposition module 4A can implement various methods, including pattern matching and software compilation and decompilation methods.

[0049] In a possible embodiment, the query processing unit 4 may include Figure 2 The query reasoning module 4B is shown in the embodiment. In a possible embodiment, the query portions or query terms provided by the query decomposition module 4A can be compared with the Application Semantic Model (ASM) stored in the database 6. Query portions that are not available in the Application Semantic Model (ASM) are redefined using the Query Re-engineering Model (QRM) stored in the database 5. In a possible embodiment, the query processing unit 4 may include, for example, Figure 2The query reorganization module 4C, illustrated in the diagram, is adapted to perform a query reorganization process in which all query parts or query terms (including those from the original Application Semantic Model (ASM) or those created during the dynamic query redefinition process) are reorganized into a single query. In a possible embodiment, query composition or reorganization can be performed via pattern matching, in which the matching part of the query redefinition model (QRM) replaces the query parts of query Q. The resulting dynamically generated query can be fed back to standard application logic 3, where the generated query can now be used to invoke a generic query endpoint. The system can use its inherent data model elements to process responses to the answers (end of forward processing).

[0050] The computed query result QR can be dynamically redefined for the user making the call. In a possible embodiment, portions of the query result QR containing application semantic model elements unknown to the user making the call can be redefined by the query redefined inference unit 4B, based on the query redefined model QRM stored in the database 5, into original model terms known to the client or user. In some cases, redefined is not required, such as in data retrieval where only plain data (e.g., numbers) can be output to the user, making any query result redefined unnecessary. The query redefined inference module 4B may include standard inference software components such as an ontology inferencer, particularly where an ontology data model has been selected for the application semantic model ASM and the query redefined module QRM.

[0051] The Query Refactoring Model (QRM) stored in Database 5 of the system may include a set of model elements and transformation rules that can be used during the query refactoring process. During the query inference step, the stored Query Refactoring Model (QRM) is used to automatically refactor parts of the query that are not available in the Application Semantic Model (ASM). The Query Refactoring Model (QRM) may include a mapping of terms of model elements between specific customer data terms and corresponding application semantic model terms. Model elements that may need to be mapped (e.g., <application model> mapped to <customer model>) may include data source types (e.g., "SPS" mapped to "ASSET"), events (e.g., "high temperature" mapped to "temperature above 80 degrees Celsius"), and other information (e.g., "Diagnostic rule (43) instance: there is a transmitter block creation instance (alarm)" mapped to "Diagnostic rule 43: if the transmitter block issues an alarm").

[0052] Additional support rules R for query redefinition can form part of the Query Redefinition Model (QRM) stored in Database 5. These rules R can be helpful in redefinition scenarios where only term redefinition fails, and where more complex relationships between model elements within the customer model of an industrial system and the application semantic model (ASM) need to be considered. For example, a data source might be referred to as source A under a specific condition X, but under a different condition Y, the same data source would be considered source D. Translating model terms for that data source to another model term (e.g., from customer model terms to application semantic model terms) requires rules R such as: "Map A to App-sem-Model-U if condition = X", and "Map D to App-sem-Model-U if condition = Y".

[0053] Therefore, the Query Refactoring Model (QRM) can provide a bridge between the Application Semantic Model (ASM) (application world) and the customer model (end-user world). Furthermore, the QRM can include customer-specific parts (mappings, rules) and other parts applicable to a set of customers in the automotive field (such as OEMs). The QRM and model components can be maintained in a centralized or decentralized manner. Moreover, the QRM can be reused and cross-checked with other models. Depending on the expressiveness of the QRM consistency checks, version control, model integration, etc., can be implemented. Query processing system 1 can be implemented using an FPGA.

[0054] Figure 3 A schematic block diagram of a possible exemplary embodiment of a query processing system (QPS) 1 according to aspects of the present invention is shown. Figure 3 In the embodiment illustrated, the query processing system 1 includes a query processing unit (QPU) 4 and application logic (AL) 3 implemented on a service provider's server 7. The server 7 has access to a central database 8, which includes a query redefinition model (QRM) and an application semantic model (ASM). Figure 3 In the embodiment illustrated, two clients A and B operate industrial systems, such as manufacturing systems 9A and 9B. Manufacturing systems 9A and 9B include one or more subsystems or machines 10A and 10B, which include application query interfaces (AQIs) 2A and 2B, such as... Figure 3As shown in the diagram. Application query interfaces 2A and 2B may include, for example, a user interface that receives customer queries input by a user (such as a technician of the corresponding industrial system). Application query interfaces AQI 2A and 2B may also include a data interface for receiving customer queries generated by the control unit or controller of the corresponding industrial systems 9A and 9B. In the illustrated embodiment, application query interfaces AQI 2A and 2B are connected to the service provider's server 7 via a local or global network 11. Customer queries Qa and Qb from different customers A and B are provided via network 11 to the query processing unit 4 implemented on the service provider's server 7. The query processing unit 4 is adapted to automatically perform query decomposition of the received customer query Q into query parts based on the query redefinition model QRM stored in the memory 5 of the database 8, such as... Figure 3 As shown in the diagram. For each decomposed query portion QP, the query processing unit 4 of server 7 can determine whether the decomposed query portion QP is available in the application semantic model ASM stored in the memory 6 of database 8. The query processing unit 4 is configured to automatically refactor the query portion QP that is not available in the application semantic model ASM based on the query refactoring model QRM. Furthermore, the query processing unit 4 can be adapted to automatically perform query reorganization on the query portion QP available in the application semantic model ASM and the refactored semantic query portion QP to generate a general query gQ, which is applied to the application model 3 implemented on server 7 to provide query result QRs that are transmitted back to the corresponding application query interfaces 2A and 2B, such as... Figure 3 As shown in the diagram, application query interfaces 2A and 2B can output the corresponding received query results QRa and QRb.

[0055] Figure 4 A flowchart illustrating a possible exemplary embodiment of a method for providing a universal query interface for industrial systems of different customers according to an aspect of the present invention is shown. In the illustrated embodiment, the method includes several main steps. In a first step S1, a query decomposition from the customer query Q input by the application query interface AQI of the customer's industrial system to the query portion QP is performed based on the stored query redefinition model QRM.

[0056] In another step S2, it is determined whether the decomposed query portion QP of the received customer query Q is available in the stored application semantic model ASM.

[0057] In another step S3, the query portion QP that is not available in the applied semantic model ASM is automatically redefined based on the stored query redefinition model QRM.

[0058] In another step S4, the query composition of the available query parts QP in the application semantic model ASM and the redefined query parts QP is performed to generate a general query gQ, which is provided to the application logic AL to provide the query result QR.

[0059] In a possible embodiment, the generic query gQ generated in step S4 can be transmitted to the application logic AL via a local or global network. The application logic AL processes the received generic query gQ based on the generic data model of the corresponding industrial system to calculate the generic query result gQR. Then, the generic query result can be refactored into a customer-specific query result using a stored query refactoring model. Finally, the customer-specific query result is output using the application query interface (AQI) of the corresponding customer industrial system.

[0060] The operation of the method and system according to the invention can be explained in more detail with reference to the following examples.

[0061] Similar processes for producing automobiles exist within car company A (customer A) and in another car company B (customer B). A part of this production process is painting the cars. It can be assumed that similar production technologies and equipment will be used to paint the cars in companies A and B. However, the specific setup of the production lines in the two companies is likely to differ in many details. Part of the painting process involves the actual application of color to the metal parts by some kind of spraying equipment. In company A, this equipment is called a "nozzle," while in company B it is called a "paint nozzle." Furthermore, company A has placed the "nozzle" in "production line 32" and "section 9," while in company B, the "paint nozzle" equipment is actually located in "band 4a" and "module 5."

[0062] Company A: "Production Line 32" -> "Section 9" -> "Nozzle"

[0063] Company B: "With 4a" -> "Module 5" -> "Paint Nozzle"

[0064] The spraying equipment is a critical component, therefore it must be monitored to prevent downtime. It has sensors attached to it that transmit sensor information (events) for further processing or to human users. Thus, the spraying equipment is a data source.

[0065] Company A:

[0066] Production Line 32 -> Section 9 -> [Data Source: "Nozzle", Event: "Block (verstopft)"]

[0067] Company B:

[0068] "with 4a" -> "Module 5" -> [Data source: "Spray nozzle", Event: "Add (zugesetzt)"]

[0069] Both companies obtained their lacquering lines from Company C, which installed the original lines and their generic software. Among other components, the software included an Application Query Interface (AQI) for use by employees of both companies (A and B), and a data model (application semantic model) defining the physical components of the lacquering production line.

[0070] Specifically, one part of the model includes the following information:

[0071] Company C:

[0072] “Element 3A” -> “Asset 4F” -> [Data Source: “Düse”, Event: “1”]

[0073] This means that for companies A and B with very similar structures, and for the original design of the paint line manufacturer (company C), there are three different data models (company A, B, and C) for the paint production line.

[0074] End users in company A or B, responsible for operating the painting line, now typically access the application via an application user interface (AQI). This can include some type of application query interface (AQI) found in current industrial systems (allowing for monitoring, diagnostics, information retrieval, etc.). The AQI is the front end of the installed software system for the painting line, where user queries Q are processed and answered.

[0075] The query for Company A is: "Production line 32, section 9, are the nozzles clogged?"

[0076] The query for Company B is: "With 4a, Module 5, has a paint nozzle been added?"

[0077] For example, within Company A, the query redefinition inference engine now obtains the query "Production line 32, section 9, nozzle clogged?". The inference engine (based on its internal query redefinition model) breaks this query down into its parts:

[0078] "Production Line 32" == Element 3A

[0079] "Part 9" == Asset 4F

[0080] "Nozzle clogging" == jetting (Düse): l

[0081] After this, the inference engine can reason about the decomposed query (i.e., whether all the required parts of the query are available, whether the replaced parts are correct, etc.), and compose the final query:

[0082] "Element 3A, Asset 4F, Spray 1?"

[0083] Now, this problem can be handled by the software originally delivered by Company C when installing the painted lines.

[0084] For Company B, the reasoning is rephrased as follows:

[0085] "with 4a" == element 3A

[0086] "Module 5" == Asset 4F

[0087] "Nose clogged" == spraying: l

[0088] Furthermore, this led to the re-establishment of queries targeting painted lines:

[0089] "Element 3A, Asset 4F, Spray 1?"

[0090] For example, the mapping from "production line 32" to "element 3A" or from "belt 4a" == "element 3A" is generated by the query redefinition inference engine based on information stored in the query redefinition model (QRM).

[0091] If "Company == A", then "Production Line 32" will be mapped to "Element 3A".

[0092] If "Company == B", then "with 4a" will be mapped to "element 3A".

[0093] The query "Element 3A, Asset 4F, Spray 1?" is now fed back into the standard application logic AL3: the generated query can now be used to invoke the generic query endpoint. The system is using its inherent data model to process the response. The query results can now be transmitted back to the user who made the call in the exact opposite way.

[0094] For example, "Element 3A, Asset 4F, Spray 1?" is true (TRUE). Then the user gets...

[0095] Company A: "Nose clogging"

[0096] Company B: "Add a paint spray nozzle"

[0097] As a query result QR and the output of the diagnostic system.

Claims

1. A method for providing a universal query interface for industrial systems of different customers of a service provider, the method being executed by a query processing system (1), wherein the query processing system (1) includes an application query interface (AQI) (2) adapted to input customer query Q into the customer's industrial system and a query processing unit (4), the method comprising the following steps: (a) Based on the query redefinition model QRM stored in the central database (8), (S1) the query decomposition of the customer query Q input by the application query interface AQI (2) to the query part QP is performed; (b) The query processing unit (4) determines whether the decomposed query portion QP of the customer query Q received in (S2) is available in the application semantic model stored in the central database (8); (c) The query processing unit (4) re-formulates (S3) the query portion QP that is not available in the applied semantic model based on the query re-formulation model QRM; (d) The query processing unit (4) performs (S4) query reorganization on the available query portion QP and the redefined query portion rQP on the applied semantic model to generate a general query gQ. (e) The query processing unit (4) applies the general query gQ to the application logic AL (3) implemented on the service provider's server (7); and (f) The application logic AL processes the received general query gQ based on the general data model of the industrial system to calculate the general query result gQR; as well as (g) The query processing unit (4) refactors the calculated general query result gQR into a customer-specific query result QR based on the stored query redefinition model QRM; (h) The application query interface (2) provides the customer with the customer-specific query result QR; The stored Query Refactoring Model (QRM) includes: The mapping of terms between customer-specific terms and the terms of the applied semantic model; and Transformation rules used for translation model terminology. The mapping of terms for model elements includes: mapping between data source terms, mapping between event source terms, and mapping between other information terms.

2. The method according to claim 1, wherein, The stored application semantic model includes the ontology model.

3. The method according to claim 1 or 2, wherein, The generated generic query gQ is transmitted to the application logic AL (3) via the local or global network.

4. A query processing system for providing a universal query interface for industrial systems serving different customers of a service provider, wherein, The query processing system (1) includes: - The application query interface AQI (2) is adapted to input customer query Q into the customer's industrial system; - Query processing unit (4), which is configured to automatically perform query decomposition from input customer query Q to query part QP in the input customer query based on the query redefinition model QRM stored in the database (8) of the query processing system (1). Specifically, for each decomposed query part QP, the query processing unit (4) determines whether the decomposed query part QP is available in the application semantic model stored in the database (8) of the query processing system (1). The query processing unit (4) is further configured to: automatically refactor the query portion QP based on the query refactoring model QRM, which is unavailable in the application semantic model; and automatically perform query reorganization on the query portion available in the application semantic model and the refactored semantic query portion rQP to generate a general query gQ. The query processing unit (4) applies the general query gQ to the processing application logic AL (3) implemented on the server (7) of the service provider, wherein the application logic AL (3) is adapted to process the received general query gQ based on the storage general data model of the industrial system to calculate the general query result gQR. The query processing unit (4) refactors the calculated general query result gQR into a customer-specific query result QR based on the stored query redefinition model QRM, wherein the application query interface (AQI) (2) is adapted to output the customer-specific query result QR, and The stored Query Refactoring Model (QRM) includes: The mapping of terms between client-specific terms and applied semantic model terms, and the transformation rules used for translation model terms. The mapping of terms for model elements includes: mapping between data source terms, mapping between event source terms, and mapping between other information terms.

5. The query processing system according to claim 4, wherein, The stored application semantic model includes the ontology model.

6. The query processing system according to claim 4 or 5, wherein, The generated generic query gQ is transmitted to the application logic via the local or global network (3).

7. The query processing system according to claim 4 or 5, wherein, The query processing unit (4) includes a local query processing unit or a remote query processing unit implemented on the service provider's server (7), and The Query Refactoring Model (QRM) is either distributed or stored in a central database of the service provider (8).

8. The query processing system according to claim 4 or 5, wherein, The application query interface AQI (2) includes: a user interface for receiving customer queries Q input by users of the industrial system, and / or a data interface for receiving customer queries generated by the controller of the industrial system.

9. The query processing system according to claim 4 or 5, wherein, The query processing system is implemented on an FPGA.

Images