How to handle data from a supervised production environment
Patent Information
- Application Number
- JP2024531362
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2021-11-24
- Filing Date
- 2022-11-24
- Publication Date
- 2025-12-01
AI Technical Summary
Managing and configuring programmable logic controllers (PLCs) in a factory environment is challenging due to the need for multiple communication protocols and security issues when monitoring and controlling machines remotely, especially with new devices, as existing systems lack direct knowledge of these protocols and face security vulnerabilities.
A method and system for processing device data in a supervised production environment that involves receiving data requests, obtaining connectivity data, addressing production device communication modules, and converting data protocols to a common format for transmission, while ensuring security and validity of data through central storage and verification processes.
Enables efficient and secure central access to machine data from various PLCs with different protocols, facilitating seamless integration of new machines and ensuring data integrity and security, even in remote locations.
Smart Images

Figure 00000000_0000_ABST
Abstract
Description
[Technical field]
[0001] Various aspects and variations relate to obtaining data values for parameters related to machines in a factory. [Background technology]
[0002] Programmable logic controllers (PLCs) have been known and used for a long time to monitor and control machines in factories for manufacturing processes. Many different types of PLCs are available and provide their data to user interface devices in the factory. When a new device is added, the user interface device must be configured by adding the PLC, the one or more parameters being monitored and / or controlled, the data communication protocol, and possibly more information. Summary of the Invention [Means for solving the problem]
[0003] Managing PLCs at the factory and adding or modifying PLCs by having existing PLCs monitor different or additional parameters is a job that requires proper monitoring and can be configured by one and the same service engineer in one user interface device. However, such modifications of PLCs and user interfaces are usually not possible if all PLC-acquirable data is monitored at the remote location. First, many communication protocols may have to be adopted, of which direct knowledge may not be available at the remote location. Second, security may be an issue if, for example, communication pipes between sensors / PLCs and computers at the remote location are left open. It would be preferable to address (eliminate or at least mitigate) one or more of these issues or otherwise improve upon the current situation.
[0004] To this end, a first aspect provides a method for processing device data available in a supervised production environment including a production device, for execution in an electronic computing system. The method includes receiving a data request for providing production data related to production parameters of the production device, obtaining device connectivity data related to the production device, configuring a data request message for requesting the production data according to the device connectivity data, and addressing a production device communication module of the production device according to the device connectivity data. The method further includes, if the addressing is successful, sending a data request message to the production device communication module according to the device connectivity data, receiving the requested data related to the production parameters of the production device from the production device communication module, and presenting the received data.
[0005] In a traditional manufacturing environment, each machine is provided with a dedicated PLC with a dedicated data transmission protocol and connected to dedicated local monitoring equipment. Different machines may be equipped with different PLCs that employ different data transmission protocols with different formats to provide data and may even employ different formats for the transmission of packets. Since every machine has its own PLC with a proprietary protocol, central and remote access of each and every PLC may be very difficult or even virtually impossible. This is especially true when a new machine with a new PLC with a new protocol is added.
[0006] Using the method of the first aspect, connection data (connectors) may be stored in a central location, for example at the manufacturing site. This data may be used by a local data hub to port data provided by the machines from a proprietary or open protocol used by the PLC (as sensed by sensors connected to the PLC) to one or more data protocols suitable for the transmission of data, which may be at the more general end / more suitable for the transmission of data using an open network such as the Internet.
[0007] When a new machine and / or a new PLC is installed, the data relating to the new PLC and / or new machine, applicable sensors (and / or control actuators), and especially the connectivity data, needs to be added to a data hub, either on the manufacturing floor or in another central location. Any other device can then retrieve the sensor data using one or more common data transmission protocols to read the data for further processing and / or presenting the data to a user.
[0008] In a variation of the first aspect, the addressing includes checking whether a communication module can provide data related to the production parameter. If the relevant communication module, e.g., a data hub or a PLC, cannot be reached, an alarm can be triggered. As a result, another system may recognize that repair may be required and / or that further querying of the data value may be infeasible.
[0009] In another variation, the device connectivity data includes an address of a production device communications module, and verifying whether the communications module can provide data related to the production parameters includes verifying whether the communications module can be addressed using the address of the production device communications module included in the device connectivity data. This may be an efficient verification scheme as it may only require a small amount of data.
[0010] In a further check, checking whether the communication module can provide data related to the production parameter includes checking whether the communication module has data available related to the production parameter. A sensor may malfunction, data may only be acquired hourly or daily, the connection between the PLCs may be broken, or there may be other reasons why data is not available. This variation checks whether actual data is available, and if not, the user or system may be prompted and then appropriate action may be taken based on this information.
[0011] Again, another variation further includes setting the status of the production parameter to the first classification if the validation fails, thereby allowing clear communication and interpretation by an operator or system.
[0012] In still a further embodiment, the device connectivity data includes data related to a first data communications protocol arranged for communication with the production device communications module, and configuring the data request message in accordance with the device connectivity data includes formatting the data request message in accordance with the first data communications protocol. This provides one example of how the first aspect may be implemented.
[0013] In yet another variation, the received data relating to the production parameter includes a received data value for the production parameter. In this variation, the method further includes verifying that the received data value is a valid value for the production parameter, and if the received data value is verified to be valid, setting the status of the production parameter to a second classification. If the data can be validly read and retrieved, such second classification may be, for example, at the user interface end, that the parameter is classified as valid.
[0014] In a further embodiment, the received data relating to the production parameter includes a received data value for the production parameter. In this variation, the method further includes comparing the received data value with a previous data value for the production parameter, and if the received data value differs from the previous data value, setting the status of the production parameter to a second classification. If a data value is received that appears valid and differs from the previously received value, this variation means that the sensor in the change process is assumed to have obtained a valid value, the process is executed, the sensor works, the PLC works, and the system is running according to specifications. In such a case, the parameter may be classified as valid, for example.
[0015] In yet another embodiment, the received data relating to the production parameter includes a received data value for the production parameter. In this embodiment, the method further includes comparing the received data value with a previous data value for the production parameter, and if the received data value is the same as the previous data value, setting the status of the production parameter to a third classification. If there is no change in the value of the parameter, whether or not a new value is received, there may be a problem with data acquisition or another problem. In either case, it may be that the latter (unchanged) data value is not a correct representation of the actual situation and a request for the data is still pending. In that case, the parameter may be classified as such. Alternatively, the parameter may be classified as pending. And in another variation, if a data value is received and it is the same as a previously received data value, the value may still be classified as valid when it is finally received.
[0016] In yet another variation, the received data related to the production parameter does not include a received data value for the production parameter. In this variation, the method further includes determining whether a previous data value for the production parameter is available, and if a previous data value for the production parameter is not available, setting the status of the production parameter to a third classification. If data is received in response to the data request, it may be assumed that the parameter and the corresponding sensor are present from the appropriate PLC and therefore not invalid. On the other hand, classifying the parameter as valid may be an overreach since no value is received. In such a case, the parameter may be classified as pending.
[0017] In a further variation, again applicable to all variations above and below, the data request message includes a request for values of production parameters, such that the data message provides a clear indication of what data is desired.
[0018] In yet a further variation, the data request message includes a request for metadata related to production parameters, which may be time, data format (byte, nibble, word, long word, floating point data), entity (width, height, temperature, humidity), measurement (kilograms, liters, millimeters, degrees Celsius), etc., or combinations thereof, to allow for efficient and understandable processing of the data.
[0019] In another variation, the electronic computing system includes a data server and a connectivity server. The method further includes the data server transmitting connectivity data and a parameter identifier identifying the production parameters to the connectivity server, the connectivity server receiving the connectivity data and the parameter identifier, the connectivity server configuring the data request message, addressing the production device, and transmitting the data request, the connectivity server receiving the requested data related to the production parameters of the production device from the production device communication module, and the connectivity server transmitting the requested data related to the production parameters of the production device. In this way, data processing is efficiently distributed to multiple devices. Processing can be supplemented by presenting the data on additional personal computing devices.
[0020] In a further embodiment, the requested data related to the production parameters received by the connectivity server is received according to a first protocol, this variant further comprising: configuring, by the connectivity server, a data offer message including the requested data according to a second data communication protocol different from the first data communication protocol, and transmitting, by the connectivity server, the requested data related to the production parameters of the production device according to the second data communication protocol to the data server, this variant allowing for greater flexibility in the use of different data communication protocols.
[0021] Yet a further variant further comprises sending by the connectivity server a request for connectivity data and a parameter identifier to the data server, the sending of the connectivity data being performed in response to the request for connectivity data and the parameter identifier. This variant provides a certain safety, as the data retrieval is initiated by the connectivity server, which asks the data server, for example by means of a user input, whether a request for data is received by the data server. In this case, the parameters for which data are requested or for which a new configuration is desired are communicated by the data server to the connectivity server at each request of the connectivity server. The connectivity server knows which data servers are reliable and by only accepting data requests from such known reliable data servers, requests from unknown data servers are not accepted and are not processed.
[0022] Alternatively, a first aspect provides a method for processing device data available in a supervised production environment including a production device for execution in an electronic computing system. The method includes receiving a data request for providing production data related to production parameters of the production device. The method further includes sending a data request message to a production device communication module according to the device connectivity data, receiving the requested data related to the production parameters of the production device from the production device communication module, and presenting the received data. This alternative aspect may be implemented in combination with one or more of the variations described above.
[0023] A second aspect provides an electronic computing system arranged to process device data available in a supervised production environment including a production device. The system comprises an input configured to receive a data request for providing production data related to production parameters of the production device, and one or more processing units configured to obtain device connectivity data related to the production device, formulate a data request message for requesting the production data according to the device connectivity data, address a production device communication module of the production device according to the device connectivity data, and determine whether the addressing is successful. The system further comprises one or more communication modules configured to send a data request message to the production device communication module according to the device connectivity data and receive the requested data related to the production parameters of the production device from the production device communication module if the addressing is successful. The system further includes an output configured to present the received data.
[0024] Another aspect may provide a computer program product including computer executable code that, when the executable code is provided in a memory connected to a processing unit of a computer, enables the computer to perform a method according to the first aspect or any variation thereof. A further aspect may provide a non-transitory memory for holding such a computer program product.
[0025] The various aspects and modifications thereof will now be described in more detail in conjunction with the drawings. [Brief description of the drawings]
[0026] [Figure 1] A factory monitoring system is shown. [Diagram 2] A flowchart is shown. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0027] 1 shows a factory monitoring system 100. The factory monitoring system 100 comprises a factory environment as a supervised production environment. The factory environment comprises a first machine 170 and a second machine 170'. The first machine 170 comprises a first sensor 172, a second sensor 174, and a third sensor 176. The sensors are provided to monitor various parts of the first machine 170. Such entities may be line speed, rotation of an axle, wheel or another rotating element, properties of a material such as pressure, temperature, acidity, conductivity, etc., or combinations thereof, vibration of any part of the first machine 170, forces exerted on a part of the first machine 170, any other mechanical, electrical, physical, chemical properties, etc., or any combination of two or more of these.
[0028] The sensor is connected to a first machine communication module 160. The first machine communication module 160 may be implemented using a programmable logic controller. The first machine communication module 160 comprises a machine interface 164, a processing unit 162 and a network interface 166. The network interface 166 is connected to an antenna 168 for wireless communication. In another variation, the network interface 166 is configured for wired network communication.
[0029] The machine interface 164 is configured to receive signals from sensors in the first machine 170, preferably electrical signals carrying information about the observed entity. The processing unit 162 is configured to process the received electronic signals. The processing may include at least one of analog to digital conversion, compression, statistical processing such as calculating at least one of the mean, median, standard deviation, encryption, encapsulation in a data package amenable to data communication, etc., or combinations thereof. The network interface 166 is configured to communicate the processed data to another communication device.
[0030] The second machine 170' is equipped with sensors and a second machine communication module 160' in an equivalent manner, with equivalent parts being indicated by the same reference numerals complemented with a prime symbol (').
[0031] Preferably, a data hub 140 is provided in the vicinity of the first machine 170 and the second machine 170′ as a variation of a connectivity server. The data hub comprises a hub processing unit 142, a hub memory 144 as a data storage module, a local network interface 146, and a hub wide area network interface 148.
[0032] The local network interface 146 with antenna 150 is configured to receive data from the first machine communication module 160. Alternatively or additionally, the local network interface may be configured for wired communication. The hub processing unit 142 is configured to process the data received from the first machine communication module 160 and from the second machine communication module 160'. The processing may include at least one of analog to digital conversion, compression, statistical processing such as calculating at least one of the mean, median, standard deviation, encryption, encapsulation in a data package following data communication, etc., or combinations thereof.
[0033] In one variation, data may be received from multiple machine communication modules provided according to multiple standards. Local network interface 146 and hub processing unit 142 are configured to handle data received according to each of the multiple standards. Furthermore, local network interface 146 and hub processing unit 142 are configured to handle data received according to each of the multiple standards and are configured to send messages to multiple machine communication modules according to the multiple standards. In this manner, local network interface 146 and network interface 166 are configured to communicate according to multiple standards.
[0034] In one option, the hub memory 144 has data stored thereon related to the data protocol with which each machine communication module is configured to communicate. This data may be read by the hub processing unit 142 to communicate with the machine communication modules. The hub memory 144 may also have data stored thereon for programming the hub processing unit. Thus, the hub memory 144 may be volatile, non-volatile, temporary or non-transient memory, or any combination thereof.
[0035] Hub processing unit 142 is further configured to convert data received according to various protocols into data messages that can be transferred across wide area network 130 to data server 110 using hub wide area network interface 148 .
[0036] The data server 110 comprises a server side area network interface 116 configured to communicate with the hub wide area network interface 148. The data server further comprises a server processing unit 112 for processing received data and for controlling further operation of the data server 110. The data server 110 comprises a server memory module 114 as a data storage module, configured to store received and transmitted data, whether processed or not.
[0037] The server memory module 114 may also store thereon data related to the data protocol that each machine communication module is configured to communicate with. In this manner, the server processing unit 112 may be configured to compose data messages according to the data protocol that each of the machine communication modules is configured to communicate with. Additionally, the server memory module may have data stored thereon for programming the server processing unit 112. As such, the server memory module 114 may be volatile, non-volatile, temporary, or non-transient memory, or any combination thereof.
[0038] The data server 110 is connected to an electronic display screen 122 as a visual output module and to a keyboard 124 as a user input module via a user interface module 118 connected to the server processing unit 112. On the electronic display screen 122, an overview of the data available for selection may be provided. Additionally or alternatively, the user is provided with an option to query a specific machine communication module 160 for machine related data. Selection may be made using at least one of the keyboard 124 or, additionally or alternatively, other user input devices such as a mouse, a voice command system, etc., or a combination thereof.
[0039] Additionally or alternatively, the data processed by the data server 110 may be accessible using a smartphone 180 as a personal computing device. The smartphone 180 comprises a smartphone network interface module 186 for connecting with the server area network interface 116 to obtain data related to specific parameters of the first machine 170 or the second machine 170′.
[0040] To be able to provide data, a data serving protocol server may be provided by the data server 110, in particular the server area network interface 116, for example a hypertext transfer protocol (http) server. The smartphone network interface module 186 may be provided with an http client for retrieving the data.
[0041] Smartphone 180 further comprises a smartphone processing unit 182, a smartphone memory 184 as a data storage module, and a touch screen 188 as a user input and output device. Smartphone processing unit 182 is configured to control the operation of smartphone 180. The operation may include processing requests for data received using touch screen 188 and sending requests for data to data server 110 or directly to data hub 140 using smartphone network interface module 186.
[0042] The operation of the smartphone processing unit 182 may also include receiving data from the data server 110 or directly from the data hub 140. The data may be received by the smartphone network interface module 186 and further processed by the smartphone processing unit 182. The data may be stored in the smartphone memory 184 for processing and / or retrieval. The smartphone memory 184 may also store data internally for programming the smartphone processing unit 182. The processed data may be provided to a user using the touch screen 188.
[0043] In one embodiment, processing of data provided by data hub 140 is handled by data server 110 and is accessible to users using personal computing devices such as smartphones 180, personal desktop or laptop computers, virtual desktop clients, etc., or combinations thereof. Such personal computing devices may connect to data server 110 via network 130. Within network 130, one or more virtual private networks or other secure data transmission pipes may be provided for secure data transmission.
[0044] Further details and functionality of the factory monitoring system 100 will now be discussed in greater detail in conjunction with a flowchart 200 as illustrated in Figure 2. The various portions of the flowchart 200 are briefly summarized in the following list: Start 202 procedure 204 Receive data request for parameters 206 Identify the applicable device 208 Obtain connection data for identified machines Create a 210 Data Request Message 212 Send a data request message to the Data Hub 214 Receive a data request message from the server 216 Identifying the Addressed Device 218 Calling an identified device 220 Did you get a response from the device? 222 Send a request for data to the identified device 224 Receive a data response from the identified device 226 Prepare a data message for the server 228 Send prepared data message 230 Receive prepared data message 232 Valid data for response to parameter? Are parameter values before 234 available? 236 Compare previous parameter values with received parameter values 238 different values? 240 Classify as a valid parameter 242 Current parameter value 244 Current Parameter Classification 246 End of procedure 252 Classify as invalid Are values before 254 available? 256 Classify as pending
[0045] The procedure begins at terminator 202 and proceeds to step 204 where the data server 110 receives a request for data via the user interface module 118 or via the smartphone 180. In the data request, an identifier may be provided by which the relevant equipment or machine may be identified. For example, a parameter may be selected on the electronic display device 122, the parameter relating to the first machine 170. Details of the parameter and its relationship to the first machine may be stored on the server memory module 114. The first machine 170 is identified in step 204 based on the selected parameter.
[0046] At step 208, the data server 110 obtains connection data for the first machine 170. The connection data for the first machine may include the network address of the first machine communication module 160, the data communication protocol used by the first machine communication module 160, a sub-address within the first machine communication module 160 for the first sensor 172, a data acquisition frequency, etc., or a combination of two or more of these. Using the selected parameters for which one or more data values are requested and the connection data, a data request message is constructed at step 210 and transmitted at step 212 via the network 130 using the server side area network interface 116 to the data hub 140.
[0047] Optionally, the data server 110 does not send a request message to the data hub 140 until the data hub 140 specifically requests the data server whether the data server 110 has received any data requests or other requests regarding the status of the first machine communication module 160. Until such a request by the data hub 140 is received, the data server 110 may enter a waiting loop, where the data server 110 only sends a request message to the data hub when a request for a new data request is received by the data server from the data hub 140.
[0048] At step 214, the data request message is received by data hub 140 using hub wide area network interface 148. The data request message is processed by hub processing unit 142 and as part of the processing, the machine address is identified at step 216. The identification may be performed by reading the network address of the first machine communications module 160 from the received data request message. Alternatively or additionally, the data request message includes another identifier of the first machine 170 and based on the other identifier, hub processing unit 142 searches data in hub memory 144 to identify the first machine.
[0049] The data retrieved and, if available, read from the hub memory 144 may include address data, meaning that the address data of the first machine 170 and / or the first machine communication module 160 may be obtained either at the data server 110, the data hub 140, or both. The retrieved identification information is used by the hub processing unit 142 to call the first machine 170 or the first machine communication module 160 in step 218.
[0050] The call may include sending a request to send back a response message containing a particular string, which may include one or more bytes of data, which may be random or predetermined.
[0051] In step 220, the hub processing unit 142 checks, inter alia, whether the first machine communication module 160 has sent a response hub server 140 back to its local network interface 146. In this case, a request for data (values of the previously selected parameters) is prepared and sent to the first machine communication module 160 in step 222. If, however, the call does not result in a response, the process branches to step 252 where the parameters are identified as invalid. The procedure then proceeds to step 244, where the parameters are presented as invalid, and the procedure ends with terminator 246.
[0052] A determination that the selected parameters are identified as invalid may be transmitted back to the data server 110 and this information may be presented to the user on the electronic display device 122. Following step 222, the data hub 140 receives a data response from the first machine communication module 160 in step 224 with a data value based on the signal received from the first sensor 172.
[0053] The signal values received from the first sensor 172 are processed by the first machine communications module 160 as discussed above and provided in data messages in accordance with the data communications protocol that the network interface 166 is configured to communicate. The local network interface 146 may be configured to communicate using one or more different data communications protocols.
[0054] Using the received data, hub processing unit 142 prepares a data message for data server 110 to provide data values for the selected parameters in step 226. The processing may involve a general porting of the received data from one protocol to another, such as from the data communications protocol in which network interface 166 is deployed to the data communications protocol generally used for communication over network 130.
[0055] The data message thus prepared is sent by the hub wide area network interface 148 in step 228 and received by the server side area network interface 116 in step 230. In step 232, the data server and server processing unit 112 checks, in particular, whether the data in the received message is valid. In particular, the server processing unit 112 checks whether the values provided in the data request relating to the first sensor 172 are values that may be reasonably expected.
[0056] For example, if temperature is being measured, a value of 4000 is invalid for a temperature in Kelvin, as is an alphanumeric string representing the Roman alphabet. Otherwise, the value field in a data message may be void, containing, for example, random data or a string of zeros.
[0057] If, in step 232, it is determined that the received data is invalid, the procedure branches to decision 254 where the server processing unit 112 checks whether a previous value for the applicable parameter was received that was determined to be valid. In this case, the previously received valid value is retained and the procedure proceeds to terminator 246 to end the procedure. Additionally, the classification of the parameter is not changed in the particular option for the implementation.
[0058] If no previous value determined to be valid has been received, the parameter is classified as pending in step 256 and the procedure proceeds to step 244 to present the parameter as pending. The procedure then ends at terminator 246.
[0059] If the received data value is deemed valid, the procedure proceeds to step 238, where the server processing unit 112 checks whether the previously received value is available, if so, the procedure proceeds to step 236, if not, the procedure jumps to step 240.
[0060] In step 236, server processing unit 112 compares the previously received value to the received value, and in step 238, server processing unit 112 determines that if the received value is the same as the previously received value, the procedure is to branch to step 256, as discussed above. In alternative embodiments, comparison step 236 and decision 238 may be omitted.
[0061] In step 240, the parameter is classified as valid because a valid value for the parameter was received in response to the most recent request for data. In step 242, the value of the parameter is presented, and in step 244, the classification of the parameter is presented. The presented data may be presented on the electronic display device 122. Steps 242 and 244 are interchangeable, as are the other steps, except, for example, where one step depends on the output of another step. [Explanation of symbols]
[0062] 100 Factory Monitoring System 110 Data Server 112 Server Processing Unit 114 Server Memory Module 116 Server Area Network Interface 118 User Interface Module 122 Electronic display screen 124 Keyboard 130 Network 140 Data Hub 142 Hub Processing Unit 144 Hub Memory 146 local network interface 148 Hub Wide Area Network Interface 150 Antenna 160 First Machine Communication Module 160' Second Machine Communication Module 162 Processing Unit 164 Machine Interface 166 Network Interfaces 168 Antenna 170 The First Machine 170' Second Machine 172 First Sensor 174 Second Sensor 176 The third sensor 180 Smartphones 182 Smartphone Processing Unit 184 Smartphone Memory 186 Smartphone Network Interface Module 188 Touchscreen 200 Flowchart
Claims
1. 1. A method in an electronic computing system for processing device data available in a supervised production environment including production devices, comprising: receiving a data request for providing production data related to a production parameter of a production device; obtaining device connectivity data associated with the production device; configuring a data request message for requesting the production data according to the device connectivity data; addressing a production device communication module of the production device according to the device connectivity data; If the addressing is successful, sending the data request message to the production device communication module according to the device connectivity data; receiving the requested data related to production parameters of the production device from the production device communication module; and presenting the received data.
2. The method of claim 1 , wherein the addressing includes verifying whether the communication module is capable of providing the data related to the production parameters.
3. the device connectivity data includes an address of the production device communication module; 3. The method of claim 2, wherein verifying whether the communications module can provide the data related to the production parameter includes verifying whether the communications module can be addressed using the address of the production device communications module included in the device connectivity data.
4. 3. The method of claim 2, wherein verifying whether the communications module can provide the data related to the production parameter includes verifying whether the communications module has data available related to the production parameter.
5. The method of claim 2 , further comprising setting the status of the production parameter to a first classification if the verifying fails.
6. the device connectivity data includes data relating to a first data communication protocol configured for communication with the production device communication module; The method of claim 1 , wherein configuring a data request message according to the device connectivity data comprises formatting the data request message according to the first data communication protocol.
7. The received data relating to the production parameter includes a received data value for the production parameter, and the method further comprises: verifying that the received data values are valid values for the production parameters; The method of claim 1 , further comprising setting the status of the production parameter to a second classification if the received data value is confirmed to be valid.
8. the received data relating to the production parameter includes a received data value for the production parameter, the method comprising: comparing the received data value with a previous data value for the production parameter; The method of claim 1 , further comprising setting the status of the production parameter to a second classification if the received data value differs from the previous data value.
9. the received data relating to the production parameter includes a received data value for the production parameter, the method comprising: comparing the received data value with a previous data value for the production parameter; The method of claim 1 , further comprising setting the status of the production parameter to a third classification if the received data value is the same as the previous data value.
10. the received data relating to the production parameter does not include a received data value for the production parameter, and the method further comprises: determining whether a previous data value for the production parameter is available; The method of claim 1 , further comprising setting the status of the production parameter to a third classification if a previous data value for the production parameter is unavailable.
11. The method of claim 1 , wherein the data request message includes a request for the value of the production parameter.
12. The method of claim 11 , wherein the data request message includes a request for metadata related to the production parameters.
13. The electronic computing system comprises a data server and a connectivity server, and the method comprises: transmitting, by the data server, the connectivity data and a parameter identifier identifying the production parameter to the connectivity server; receiving, by the connectivity server, the connectivity data and the parameter identifier; the connectivity server performs the configuring of the data request message, the addressing of the production device, and the sending of the data request; receiving, by the connectivity server, the requested data related to the production parameters of the production device from the production device communication module; The method of claim 1 , further comprising: transmitting, by the connectivity server, the requested data related to the production parameters of the production device.
14. The device connectivity data includes data related to a first data communications protocol configured for communication with the production device communications module; configuring a data request message in accordance with the device connectivity data includes formatting the data request message in accordance with the first data communication protocol; The requested data related to the production parameters received by the connectivity server is received according to the first protocol, and the method comprises: formulating, by the connectivity server, a data offer message including the requested data according to a second data communication protocol different from the first data communication protocol; 14. The method of claim 13, further comprising transmitting, by the connectivity server, the requested data related to the production parameters of the production device to the data server according to the second data communication protocol.
15. The method comprises: sending, by the connectivity server, a request for connectivity data and a parameter identifier to the data server; The method of claim 1 , wherein the transmitting the connectivity data is performed in response to the request for connectivity data and a parameter identifier.
16. 1. An electronic computing system configured to process device data available in a supervised production environment including production devices, comprising: an input configured to receive a data request to provide production data related to a production parameter of a production device; one or more processing units, obtaining device connectivity data associated with the production device; configuring a data request message for requesting the production data according to the device connectivity data; Addressing a production device communication module of the production device according to the device connectivity data; and one or more processing units configured to determine whether the addressing was successful; one or more communication modules, If the addressing is successful, sending the data request message to the production device communication module according to the device connectivity data; one or more communication modules configured to receive the requested data related to production parameters of the production device from the production device communication module; an output configured to present the received data.