EP3125172B1

EP3125172B1 - Data supply chain components configuration reliability analysis

Info

Publication number: EP3125172B1
Application number: EP16179055.5A
Authority: EP
Inventors: Eduard Smits; Rob Goes; Simon Coombs
Original assignee: Accenture Global Services Ltd
Current assignee: Accenture Global Services Ltd
Priority date: 2015-07-31
Filing date: 2016-07-12
Publication date: 2022-03-30
Anticipated expiration: 2036-07-12
Also published as: CA2932804A1; AU2016208285A1; EP3125172A1; US11442919B2; CA2932804C; US20170031969A1; CN106407640B; CN106407640A; AU2017228729A1

Description

BACKGROUND

Data may include a set of values of qualitative or quantitative variables, where each piece of data may represent an individual piece of information. Data may be measured, collected, reported, and analyzed, for example, to be displayed in a graph or image format for visualization. Generally, data may pertain to the representation or coding of existing information or knowledge in a form that is suitable for better usage or processing. Reliability of data may be paramount for further analysis related to the data.
Document US 2014/0336791 A1 discloses a cloud-based predictive maintenance service which collects industrial data from multiple industrial customers for storage and analysis on a cloud platform. The service analyzes data gathered from multiple customers across different industries to identify operational trends as a function of industry type, application type, equipment in use, device configurations, and other such variables. Based on results of the analysis, the predictive maintenance service predicts anticipated device failures or system inefficiencies for individual customers. Notification services alert the customers of impending failures or inefficiencies before the issues become critical. The cloud-based notification services also notify appropriate technical support entities to facilitate proactive maintenance and device management.
Document US 2014/0337277 A1 discloses an industrial attestation service executing on a cloud platform which collects industrial data from multiple levels of an industrial enterprise and identifies subsets of the industrial data that characterize normal operation. In the cloud platform, baselines are generated for diverse aspects of the industrial enterprise based on the identified subsets, where the baselines characterize normal operation. The baselines are used as a reference in connection with device and system attestation. Aspects of the industrial enterprise that deviate from their corresponding baselines are identified in the cloud platform. Attestation reports indicating aspects of the enterprise that have altered relative to their baselines are delivered to client devices via the cloud platform.
Document US 2011/0239055 A1 discloses a system framework for identifying root causes of configuration errors and best-practice incompliance of distributed applications. The system framework provides both platform provider and customer a method to create, extend, and utilize a tool that simplifies the configuration troubleshooting experience. Using the system framework, a user is able to access more information about applications and to troubleshoot multiple applications at the same time without having to load or activate any of the applications. In addition, users are able to add custom rules to identify commonly occurring configuration problems.
Document US 6,742,141 B1 discloses a system in which a database contains entries with executable code that can make use of services in order to monitor, diagnose, and solve specific problems. Each entry in the database addresses a specific problem. The executable code is designed to isolate and recognize the problem, and then implement a fix or workaround for that problem. The executable code is designed to completely automate the entire process of detection and resolution of the problem. Further, manual intervention may be employed to complete the diagnosis or solution.
Document US 2004/0006612 A1 provides an apparatus and method for verifying and correcting storage area network (SAN) configuration information. With the apparatus and method, configuration information is collected from components of the SAN using a SAN configuration scanning device. The configuration information collected by the SAN configuration scanning device is then compared to certified configuration parameters by a SAN configuration verification device. The comparison results in variances between the collected configuration information and the certified configuration parameters. It is then determined whether these variances are correctable or not. The variances that are correctable are corrected to reflect the certified configuration parameters by a SAN configuration correction device. Variances that are not correctable are output to an error report generation device that generates an error report for use by a SAN system administrator.
Document US 2002/0156799 A1 discloses a system and method for evaluating and correcting websites which includes an assessment module to parse and analyze the website as a function of a ruleset of design guidelines. A list of automatic correction items, semi-automated assisted correction items, and manual correction items is reported by a reporting module. The listed items are automatically, semiautomatically, or manually corrected by or through a correcting module. The system and method provide an internet based software tool to enable website providers to diagnose, evaluate, report, and retrofit code violations existing in websites.
Document US 2008/0281833 A1 discloses a change management system for managing configurable devices such as computer systems which uses a set of rules for validating change requests, linking change requests, and determining inconsistencies within various configuration states. Analysis and validation may happen at the time the change request is created with respect to the current environment, as well as analysis and validation with respect to other pending requests and proposals, and historical actual states. The maintenance of accurate and consistent state and change information may enable various automated tools to analyze and manipulate change requests, including analysis of future desired states, historical actual states, pending change requests, and current state. The change request may be processed through an approval cycle all the while being incorporated into a scheduling system that may be used to detect inconsistent, illogical or harmful configurations in potential future configurations.
Document C. Ward ET AL: "Integrated change and configuration management", IBM Systems Journal, 3 July 2007 (2007-07-01), pages 459-478, provides a summary of the best-practice change-management and configuration-management processes that express a core which conforms to ITIL and discusses how they are extended for the service provider domain.

BRIEF DESCRIPTION OF DRAWINGS

Features of the present disclosure are illustrated by way of examples shown in the following figures. In the following figures, like numerals indicate like elements, in which:

Figure 1 illustrates an environment including a data reliability analysis system, according to an example of the present disclosure;
Figure 2 illustrates an architectural diagram for the data reliability analysis system of Figure 1, according to an example of the present disclosure;
Figure 3 illustrates an architectural diagram of an enterprise environment including the data reliability analysis system of Figure 1, according to an example of the present disclosure;
Figure 4 illustrates a flow diagram of a method for data reliability analysis, according to an example of the present disclosure;
Figure 5 illustrates another flow diagram of a method for data reliability analysis, according to an example of the present disclosure; and
Figure 6 illustrates a computer system, according to an example of the present disclosure.

DETAILED DESCRIPTION

For simplicity and illustrative purposes, the present disclosure is described by referring mainly to embodiments thereof. In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present disclosure. It will be readily apparent however, that the present disclosure may be practiced without limitation to these specific details. In other instances, some methods and structures have not been described in detail so as not to unnecessarily obscure the present disclosure.
Throughout the present disclosure, the terms "a" and "an" are intended to denote at least one of a particular element. As used herein, the term "includes" means includes but not limited to, the term "including" means including but not limited to. The term "based on" means based at least in part on.
In today's data-rich environments, data including real-time data may be used for management of a variety of tasks. For example, in a manufacturing environment, data including real-time production data may be used for monitoring ongoing operations, and/or for investigating and optimizing a process (e.g., maintenance, inventory control, etc.). At the enterprise level, data may be used for key performance indicators (KPI) reporting, optimizing tasks, cost comparisons, license to operate analysis, etc.). According to another example, a data stream from a temperature sensor may be denoted as a Tag, where the data supply for each Tag or group of Tags related to a plurality of temperature sensors may be different depending, for example, on where in a process the data has its source. A Tag may be described as a data stream that refers to the source of the data stream that may be a sensor, an actor, an error signal, etc. The nature of the source may determine the behavior of a specific Tag, and thereby the right configuration of that Tag. Further examples where real-time data may be used directly from assets for critical decisions include environmental emissions, preventive maintenance, waste minimization, uptime optimization, etc.
The real-time data may be measured at various sampling rates, such as minutes, seconds, sub-seconds, etc. The real-time data may also be denoted as time-series data, and databases that are used as a basis for measured data may be denoted "historians".
Since such data may be highly relevant for meeting related demands, reliability and trustworthiness of such data can be paramount. In this regard, an aspect that has an effect on the reliability and trustworthiness of the data includes configuration parameters throughout an entire data supply chain. Configuration parameters may be described as a set of attributes that describe how a data stream originating from an input signal (e.g., a sensor) will be handled in a particular system. The handling of a data stream may include transforming, storing, contextualizing, or anything else based on the function of a specific system.
The data supply chain may include data that is related to assets that include sensors (e.g., smart sensors, sensor networks, etc.), and systems (e.g., a distributed control system (DCS)), sub-systems, historians, applications, analytics tools, and/or reports). The supply chain of data may include a plurality of systems that consume, generate, store, and pass the data through or from other systems. Such a supply chain of data may include, for example, of a sensor scanned by a Programmable Logic Controller (PLC) for data. The PLC may be described as a digital computer used for automation of industrial electromechanical processes, such as control of machinery on factory assembly lines, amusement rides, or light fixtures. PLCs may be designed for multiple arrangements of digital and analog inputs and outputs. A PLC is an example of a "hard" real-time system since output results may be produced in response to input conditions within a limited time, otherwise unintended operation may result.
The PLC may pass its information through to a DCS system that provides its data via an Open Platform Communications (OPC) system via networking equipment to a historian. The DCS may be described as a control system for a process or plant, where control elements may be distributed throughout the system. This is in contrast to non-distributed systems, which may use a single controller at a central location. In a DCS, a hierarchy of controllers may be connected by communications networks for command and monitoring. An OPC may be described as a series of standards and specifications for industrial telecommunication. An OPC may specify the communication of real-time plant data between control devices from different manufacturers. The historian may bridge the gap between a process control domain and an office domain. In the office domain, the real-time data may be aggregated and sent to an enterprise resource planning (ERP) system and other report tools.
Data handling components (e.g., DCS, historian, etc.) in a supply chain of data may include standard components, and may not be optimized for a single (or uniform) piece of equipment, and therefore, inconsistencies and inaccuracies in the data may be introduced. Moreover, sensors may also include inconsistencies and inaccuracies. In a well-managed data supply chain, these inconsistencies and inaccuracies may not affect the reliability and trustworthiness of the real-time data. However, a plant and/or asset may include several hundred thousand Tags and several data handling systems in a supply chain of data. Thus, processes related to such plants and/or assets may be dynamic, with systems and sensors being frequently changed (e.g., repaired, or replaced). Thus, real-time data from of a data supply chain may be unreliable.
Another aspect that may be a threat for the reliability and trustworthiness of real time data is whether the data is originating from a valid source, and if the data has not been deliberately altered by a party that is not authorized to perform a particular action. For example, such unauthorized actions may be performed via the configuration of a data supply chain.
In addition to the aforementioned technical aspects, organizational aspects may also add complexities and thus unreliability to a data supply chain. For example, standardization or lack thereof in an organization may add complexities with respect to assets involved in a data supply chain (e.g., with respect to replacement and/or maintenance of assets), and thus unreliability to the data supply chain (i.e., an end-value of the data may not be correct as a basis for an analysis). For example, an organization may include different teams that are responsible for configuring, modeling, and maintaining different systems and functionalities of the organization.
In order to address the aforementioned challenges with respect to data reliability, a data reliability analysis system and a method for data reliability analysis are disclosed herein. For the system and method disclosed herein, a well-managed supply chain of data is achieved by repeated scanning, comparison, detection, reporting, and correction of configurations, for example, including Tag configurations, in a data supply chain. A Tag configuration is described as the configuration of a single data stream in a plant that is handled in a system. A "name" is one of the attributes from a sensor. Other attributes may include range, alarm levels, PLC memory address, data type, representation behavior, etc. One Tag may include many attributes to describe its behavior.
According to embodiments, the system and method disclosed herein operate in a generic manner that is independent of vendor specifics.
According to embodiments, the system and method disclosed herein provide for the repeated scanning of configurations in a data supply chain (e.g., including sensors, DCS, historians, etc.) to generate a configuration database. Configurations from the configuration database may be compared for a data supply chain, and inconsistencies may be identified based on the comparison. Based, for example, on configuration rules, the configurations is automatically (i.e., without human intervention) updated. The system and method disclosed herein thus provide for increased data reliability based on an indication of consistency related to how real-time data was generated.
According to embodiments, the system and method disclosed herein unite a data supply chain, for example, by reading multiple configurations from heterogeneous environments (e.g., sensors, DCS, historians, vendors, and departments in an organization).
According to embodiments, the system and method disclosed herein provide for the generation of a configuration database to bring different configuration sets into a normalized and harmonized configuration database. These aspects provide a basis for change management in an asset at multiple levels (e.g., uniting operational technology (OT) and information technology (IT), from a plant floor to management level).
According to embodiments, the system and method disclosed herein provide for a combination of infrastructure information (e.g., temperature sensor information), and domain knowledge, with a focus on safety and process optimization.
According to embodiments, the system and method disclosed herein provide configuration reliability augmentation, for example, by adding a reliability component to real-time process values. These aspects may provide an indication of whether it is safe to make decisions based on a particular process value.
According to embodiments, the system and method disclosed herein provide pre-configured, and repeated monitoring and checking of a data supply chain. In this regard, the system and method disclosed herein provide for the minimization of system load by tuning. Further, a scanning frequency related to a data supply chain is increased depending on a number of inconsistencies identified (e.g., when a number of inconsistencies is greater than a predetermined threshold).
According to embodiments, the system and method disclosed herein provide for the repair of configurations for certain inconsistencies. For example, based on rules and domain expertise, certain inconsistencies are resolved (e.g., by tuning a historian, reducing and automating workload for system maintenance, etc.).
According to embodiments, the system and method disclosed herein provide an expandable framework. In this regard, since an entire data supply chain may be scanned, the infrastructure related to the data supply chain may also be monitored, thus providing for the maintenance and security measures related to the data supply chain as well as the infrastructure related to the data supply chain.
According to embodiments, the system and method disclosed herein provide various benefits for a process control domain such as ensuring of configuration quality, ensuring of data quality, security with respect to assets, asset management, alarm management with respect to assets, and application management.
The data reliability analysis system and the method for data reliability analysis disclosed herein provide a technical solution to technical problems related, for example, to data reliability determination. As disclosed herein, the system and method disclosed herein provide the technical solution of a configuration scanner that is executed by at least one hardware processor to scan a component of a data supply chain, and determine, based on the scan of the component of the data supply chain, configurations of the component of the data supply chain. A configuration analyzer that is executed by the at least one hardware processor analyzes the configurations of the component of the data supply chain, and detect, based on the analysis of the configurations of the component of the data supply chain, a change in at least one of the configurations of the component of the data supply chain. Further, the configuration analyzer compares the change against a corresponding configuration rule to determine whether the change is a defect that affects consistency of data related to the component, and in response to a determination that the change is the defect that affects the consistency of the data related to the component, determine, based on the corresponding configuration rule, a solution related to the defect. A configuration modifier that is executed by the at least one hardware processor modifies, based on the solution related to the defect, a configuration of the configurations to correct the defect that affects the consistency of the data related to the component. The system and method disclosed herein thus provide the technical solution of improved performance and reduced resource utilization with respect to components that generate, utilize, and/or manage data.
Figure 1 illustrates an environment 100 including a data reliability analysis system 102 (e.g., system 102 as disclosed herein), according to an embodiment of the present disclosure. Referring to Figure 1, the environment 100 includes a data supply chain 104 including various components that may be used to ascertain data 106 (see Figure 2). For example, the components of the data supply chain 104 may include PLC, DCS, OPS, Process Control Domain (PCD), historians, etc., as shown, other components such as sensors, sensor networks, control loops, routers, etc., and generally any type of data source.
The PCD may be described as an engineering discipline that pertains to architectures, mechanisms and algorithms for maintaining the output of a specific process within a desired range. For example, the temperature of a chemical reactor may be controlled to maintain a consistent product output. Process control may be used in industry and provide for mass production of consistent products from continuously operated processes such as oil refining, paper manufacturing, chemicals, power plants and many others. Process control may provide for automation, by which a small staff of operating personnel may operate a complex process from a central control room.
Referring to Figures 1 and 2, the data supply chain 104 is used by a configuration scanner 108 that is executed by at least one hardware processor (e.g., hardware processor 602 of Figure 6) of the system 102 to generate a configuration database 110 that includes configurations 112 based on the data 106. The configurations 112 may be stored as configuration (1) to configuration (N) corresponding to data (1) to data (N) respectively for component (1) to component (N) (e.g., PLC, DCS, OPC, ..., office historian, as illustrated in Figure 1) of the data supply chain 104. The configuration scanner 108 reads (i.e., determine) configurations from the various different components of the data supply chain 104. According to embodiments, the configurations 112 is determined from repeated scanning of the various different components of the data supply chain 104.
According to embodiments, the configuration scanner 108 scans the configurations 112 of each component of the data supply chain 104, or selected components of the data supply chain 104. For the components that are subject to scanning, a first scan may be performed on a most recent backup from a process control system related to the particular component of the data supply chain 104. In this regard, scanning of a backup may eliminate any interference, for example, with respect to performance and/or content, of the scanned component, or on any related components of the data supply chain 104. The configuration scanner 108 may read all of the configuration data for the scanned component, and place the configuration data in the configuration database 110 as part of the configurations 112. According to embodiments, the configuration database 110 may be described as a standardized (i.e., vendor independent) and modeled (i.e., layered) database.
A configuration analyzer 114 that is executed by the at least one hardware processor analyzes the configurations 112 (i.e., analyze the backup files associated with the configurations 112) to identify versions of the configurations 112 (i.e., for each of the scanned components, associated backup file versions may be analyzed). For each of the scanned components (or selected ones of the scanned components), the configuration analyzer 114 analyzes the configurations 112 by comparing different versions (e.g., a current version to a selected previous version) of the configurations. The comparison may include determining whether Tags from a backup file have been deleted, altered, or created, for example, by analyzing attributes of the Tags. If a Tag has been altered (or also for Tag creation and deletion), the Tag may be analyzed against a configuration rule as disclosed herein to determine whether the alteration (and/or creation and/or deleted) is acceptable or is a defect. Based on the comparison, the configuration analyzer 114 detects a change in the configuration of a scanned component of the data supply chain 104, and the change in the configuration may be subject to further analysis. A change may be described as an alteration of a Tag as described herein, or an alteration of an attribute of a Tag. The detected change (if any) for each component of the data supply chain 104 may be respectively denoted as delta (1) to delta (N) corresponding to the analysis of configuration (1) to configuration (N) corresponding to data (1) to data (N) respectively for component (1) to component (N) (e.g., PLC, DCS, OPC, ..., office historian, as illustrated in Figure 1) of the data supply chain 104.
The configuration analyzer 114 may also analyze the configurations 112 by comparing a current version of a backup file (or a particular selected version of a backup file) of the data supply chain 104 to a previous version of a backup file of the data supply chain 104. That is, the configuration analyzer 114 may compare a current version of a backup file for all of the configurations (1) to (N) against a previous version of a backup file for all of the configurations (1) to (N) (e.g., each configuration (1) to (N) for a current version may be compared to each configuration (1) to (N) for a previous version, where configuration (1) is compared to configurations (2) to (N), configuration (2) is compared to configurations (3) to (N), etc.). The configuration analyzer 114 may identify inconsistencies with respect to the comparison performed for the entire data supply chain 104. In this manner, the configuration analyzer 114 may detect a change in the configuration of the entire data supply chain 104, and the change in the configuration of the data supply chain 104 may be subject to further analysis. The detected change for the configuration of the entire data supply chain 104 may be denoted "delta (data supply chain)".
The configuration analyzer 114 may compare these changes (e.g., for the component of the data supply chain 104, and/or for data supply chain 104) pertaining to a subset (or all) of the configurations 112 against corresponding configuration rules 116. For example, the configuration rules 116 may pertain to the component of the data supply chain 104, and/or the entire data supply chain 104. The configuration rules 116 may be described as a rule or a set of rules where an attribute should be compliant. For example, a configuration rule may include a naming convention for Tag names. For example, a plant may include naming conventions for Tag names so that the Tags may be readily identified, and the Tag names are unique. Other examples of configuration rules may include the alarm level of a type of temperature sensor, where the alarm level may be set to 100° C, or the scan rate (i.e., sampling frequency) of a temperature sensor may be set to below one second, or a display accuracy for a value being set to two decimal places, etc.
The configuration rules 116 include data stream type (Tag) specific rules (quality), vendor/system specific rules (optimization), customer specific rules (standardization), and management of change (security) rules.
The configuration analyzer 114 may mark (e.g., by flagging) any changes (and/or deviations) of the configurations with respect to the configuration rules 116 with respect to the components of the data supply chain 104, and/or the entire data supply chain 104 that are identified as a defect. As disclosed herein, a change may be described as an alteration of a Tag, or an alteration of an attribute of a Tag. A deviation may be described as a non-compliance of a change with a configuration rule.
According to embodiments, when a component of the data supply chain 104 is scanned for the first time, no previous backup exists. In this regard, the configuration analyzer 114 may mark all Tags for an initial check against the configuration rules 116. Thus for an initial check, based on the checking of all Tabs against the configuration rules 116, the configuration analyzer 114 may effectively provide insights into the operation of the component of the data supply chain 104 and/or the data supply chain 104.
With respect to the marked changes (and/or deviations) of the configurations with respect to the configuration rules 116 with respect to the components of the data supply chain 104, and/or the entire data supply chain 104, the configuration analyzer 114 may analyze all or selected ones of the other components of the data supply chain 104. In this manner, the configuration analyzer 114 may detect changes (and/or deviations) in the entire data supply chain 104 and/or between certain components of the data supply chain 104.
The configuration analyzer 114 may also contextualize the changes (and/or deviations) by performing analytics with respect to the configuration rules 116. For example, the configuration analyzer 114 may determine whether the changes (and/or deviations) are process based, represent security scan (Management of Change (MoC) compliance), Health, Safety, Security, and Environmental (HSSE), etc. MoC may be described as a procedure that defines and describes the process of changes in the PCD domain. A primary goal may include controlling of the changes to reduce risks. The MoC may describe was actions are done by what person in a specific time frame.
For each change (and/or deviation), the configuration analyzer 114 operates in conjunction with a configuration modifier 118 that is executed by the at least one hardware processor to record a proposed solution based, for example, on the configuration rules 116 and/or previous similar changes (and/or deviations). For each solution, the configuration analyzer 114 may determine whether the solution should be automatically (e.g., without human intervention) addressed (e.g., by the configuration modifier 118) or manually addressed. If a solution should be manually addressed, the configuration analyzer 114 may begin a MoC workflow.
The configuration analyzer 114 may operate in conjunction with the configuration modifier 118 to store each combination and type of change (and/or deviation), and its solution, for subsequent use for detecting the same type of change (and/or deviation).
With respect to the configuration rules 116, each component of the data supply chain 104 and/or the data supply chain 104 may include different types and sets of configuration rules 116. Each set of the configuration rules 116 may include values, process information, and component information. With respect to values, a value may be an absolute, a limit, or boundaries for attribute compliance. For example, an alarm limit for boiling water should not be set at 200° C. Process information may refer to a physical parameter of the process that is described by an attribute. The attribute should be compliant with the nature of the process. This may be a value or a time range or an accuracy. For example, for boiling water the display accuracy should not be six decimal places, as this would provide no additional information. Asset information may refer to a physical parameter of an asset that is described by an attribute. The attribute should be compliant with the nature of that asset. This may be a value or a time range or an accuracy. For example, using a sensor for boiling water with a reaction speed of nine degrees in one minute, a scan rate should not be one hour. An inconsistency occurs when a Tag (same data stream) has one or more attributes that include different values in different systems (and thus, the attributes may be misconfigured).
The configuration modifier 118 may determine, based on the configuration rules 116, whether to send a trigger to a domain expert. Further, the configuration modifier 118 may determine, based on the configuration rules 116, whether to solve a particular issue associated with a component of the data supply chain 104.
The configuration modifier 118 performs corrections with respect to any configuration change (and/or deviation) that is determined to be a defect based on the configuration rules 116. In this regard, the configuration modifier 118 may change a configuration file associated with a particular component of the data supply chain 104 that is determined to be a source of a defect. The change to the configuration file may be marked by the configuration modifier 118 so that further scans and analysis related to the particular configuration file may be determined as being allowed.
A configuration controller 120 that is executed by the at least one hardware processor may determine a scanning frequency of the data supply chain 104, based, for example, on the configuration rules 116. For example, a configuration rule may include a first scan rate for a given load on a component of the data supply chain 104, and a second scan rate for a different load (e.g., higher or lower load) on a component of the data supply chain 104. According to examples, the configuration controller 120 may generate visual indicators, such as heatmaps of the identified defects and/or changes. According to examples, the configuration controller 120 may control a component of the data supply chain 104, for example, by assisting with maintenance of the component.
A report generator 122 that is executed by the at least one hardware processor may generate a report on the trustworthiness of data. For example, the report generator 122 may provide an indication of a quality of the data. The report generator 122 may also provide various other indicators related to a configuration change. For example, the report generator 122 may indicate (e.g., via a visual display, a report, or otherwise), any change (and/or deviation) to a configuration of a component of the data supply chain 104 and/or the data supply chain 104 that is detected, and/or any change to a configuration of a component of the data supply chain 104 and/or the data supply chain 104 that is performed by the configuration modifier 118. In this regard, with respect to a change to a configuration of a component of the data supply chain 104 and/or the data supply chain 104 that is performed by the configuration modifier 118, the report generator 122 may mark such a change as being allowed.
The report generator 122 may manage and approve any proposed changes to a configuration of a component of the data supply chain 104 and/or the data supply chain 104 that is performed by the configuration modifier 118. In this regard, the report generator 122 may automatically (e.g., without human intervention) manage and approve proposed changes, and/or prompt a user of the system 102 for approval of proposed changes.
The report generator 122 may operate in conjunction with the configuration modifier 118 to manage and approve a particular workflow related to a component of the data supply chain 104 and/or the data supply chain 104, where such a workflow may alter the configuration and/or layout of a component of the data supply chain 104 and/or the data supply chain 104. In this regard, the report generator 122 may automatically (e.g., without human intervention) manage and approve a particular workflow, and/or prompt a user of the system 102 for approval of a particular workflow.
The report generator 122 may also analyze the quality of a Tag (e.g., by analyzing Tag attributes) to determine a quality value of real-time data that is being produced by the Tag at a specific time. In this regard, the quality value may be used as a trigger to determine whether to use or not to use the real-time data associated with the Tag. For example, if the quality related to a Tag is below a quality threshold, real-time data related to the Tag may not be used, and/or the report generator 122 may not use the real-time data related to the Tag on a KPI report.
The elements of the system 102 described herein may be machine readable instructions stored on a non-transitory computer readable medium. In addition, or alternatively, the elements of the system 102 may be hardware or a combination of machine readable instructions and hardware.
Figure 3 illustrates an architectural diagram of an enterprise environment including the system 102, according to an example of the present disclosure.
Referring to Figure 3, the enterprise environment including the system 102 may include various layers, such as a service layer 300, an analytics layer 302, a data collection layer 304, and a client side layer 306.
With respect to the system 102, the service layer 300 may generally provide for the implementation of various benefits for a process control domain such as ensuring of configuration quality, ensuring of data quality, security with respect to assets, asset management, alarm management with respect to assets, and application management. Alarm management may be described as the application of human factors (or 'ergonomics') along with instrumentation engineering and systems to manage the design of an alarm system to increase its usability. Generally, a usability concern is that there are too many alarms annunciated in a plant system, commonly referred to as alarm flood (similar to an interrupt storm). However, there may also be other concerns with an alarm system such as poorly designed alarms (e.g., low quality configuration data), low quality of real time data, improperly set alarm points, ineffective annunciation, unclear alarm messages, etc.
With respect to the system 102, the analytics layer 302 may provide for implementation of the various elements of the system 102. For example, the analytics layer 302 may provide for implementation of the configuration scanner 108, the configuration analyzer 114, the configuration modifier 118, the configuration controller 120, and the report generator 122.
With respect to the system 102, the data collection layer 304 may provide for implementation of communication with respect to the elements of the system 102 and components of the client side layer 306, such as, the data supply chain 104, the configuration database 110, and the configuration rules 116.
Figures 4 and 5 respectively illustrate flowcharts of methods 400 and 500 for data reliability analysis, according to examples. The methods 400 and 500 may be implemented on the system 102 described above with reference to Figures 1-3 by way of example and not limitation. The methods 400 and 500 may be practiced in other systems.
Referring to Figures 1-4, and particularly Figure 4, at block 402, the method 400 includes scanning a component of a data supply chain 104.
At block 404, the method 400 includes determining, based on the scan of the component of the data supply chain 104, configurations 112 of the component of the data supply chain 104.
At block 406, the method 400 includes analyzing the configurations 112 of the component of the data supply chain 104.
At block 408, the method 400 includes detecting, based on the analysis of the configurations 112 of the component of the data supply chain 104, a change in at least one of the configurations 112 of the component of the data supply chain 104.
At block 410, the method 400 includes comparing the change against a corresponding configuration rule 116 to determine whether the change is a defect that affects consistency of data related to the component.
At block 412, in response to a determination that the change is the defect that affects the consistency of the data related to the component, the method 400 includes determining, based on the corresponding configuration rule 116, a solution related to the defect.
At block 414, the method 400 includes modifying, based on the solution related to the defect, a configuration of the configurations 112 to correct the defect that affects the consistency of the data related to the component.
According to embodiments, the method 400 may include scanning components including the component of the data supply chain 104, and determining, based on the scan of the components of the data supply chain 104, configurations 112 of the components of the data supply chain 104. Further, the method 400 may include analyzing the configurations 112 of the components of the data supply chain 104, detecting, based on the analysis of the configurations 112 of the components of the data supply chain 104, a change in at least one of the configurations 112 of the components of the data supply chain 104 and a change in a configuration of the data supply chain 104, and comparing the change in the configuration of the data supply chain 104 against another corresponding configuration rule 116 to determine whether the change in the configuration of the data supply chain 104 is another defect that affects consistency of further data related to the data supply chain 104.
According to embodiments, in response to a determination that the change is the another defect that affects the consistency of the further data related to the data supply chain 104, the method 400 may include determining, based on the another corresponding configuration rule 116, a further solution related to the another defect that affects the consistency of the further data related to the data supply chain 104. Further, the method 400 may include modifying, based on the further solution related to the another defect that affects the consistency of the further data related to the data supply chain 104, the configuration of the data supply chain 104 to correct the another defect that affects the consistency of the further data related to the data supply chain 104.
According to embodiments, the method 400 may include determining, based on the scan of the component of the data supply chain 104, configurations 112 of the component of the data supply chain 104 by determining, based on the scan of the component of the data supply chain 104, backup files of the component of the data supply chain 104.
According to embodiments, the method 400 may include identifying, based on the scan of the component of the data supply chain 104, versions of the backup files of the component of the data supply chain 104, analyzing different versions of the backup files of the component of the data supply chain 104 by comparing the different versions of the backup files of the component of the data supply chain 104, detecting, based on the analysis of the different versions of the backup files of the component of the data supply chain 104, the change in at least one of the versions of the backup files of the component of the data supply chain 104, and comparing the change against the corresponding configuration rule 116 to determine whether the change is the defect that affects the consistency of the data related to the component.
According to embodiments, the method 400 may include determining, based on the scan of the components of the data supply chain 104, configurations 112 of the components of the data supply chain 104 by determining, based on the scan of the components of the data supply chain 104, backup files of the components of the data supply chain 104.
According to embodiments, the method 400 may include identifying, based on the scan of the components of the data supply chain 104, versions of the backup files of the components of the data supply chain 104, analyzing different versions of the backup files of the components of the data supply chain 104 by comparing the different versions of the backup files of the components of the data supply chain 104 with respect to each associated component and each other component of the data supply chain 104, detecting, based on the analysis of the different versions of the backup files of the components of the data supply chain 104, the change in at least one of the versions of the backup files of the components of the data supply chain 104 and a change in a backup file of the data supply chain 104, and comparing the change in the backup file of the data supply chain 104 against another corresponding configuration rule 116 to determine whether the change in the backup file of the data supply chain 104 is another defect that affects consistency of further data related to the data supply chain 104.
According to embodiments, for the method 400, the configuration rule 116 may be related to the consistency of at least one of the component and the data supply chain 104.
According to embodiments, the method 400 may include determining whether the change is a process based change related to a process associated with the component, a security based change related to security of the component, and/or a component based change related to hardware or code related to the component.
According to embodiments, the method 400 may include recording the modification to the configuration of the configurations 112 to correct the defect that affects the consistency of the data related to the component, and bypassing analysis related to the modification for future analysis of the configurations 112 of the component of the data supply chain 104.
According to embodiments, the method 400 may include determining a scanning frequency of the component of the data supply chain 104 based on the corresponding configuration rule 116.
According to embodiments, the method 400 may include determining a scanning frequency of the component of the data supply chain 104 based on a computational load associated with the component of the data supply chain 104.
According to embodiments, the method 400 may include generating a report related to the change in the at least one of the configurations 112 of the component of the data supply chain 104, the solution related to the defect, and/or the modification, based on the solution related to the defect, of the configuration of the configurations 112 to correct the defect that affects the consistency of the data related to the component.
According to embodiments, the method 400 may include determining a workflow order of components of the data supply chain 104 to modify the configuration of the component of the data supply chain 104 to correct the defect that affects the consistency of the data related to the component.
According to embodiments, the method 400 may include generating a report related to the workflow order of the components of the data supply chain 104 to modify the configuration of the component of the data supply chain 104 to correct the defect that affects the consistency of the data related to the component.
Referring to Figures 1-3, and 5, and particularly Figure 5, at block 502, the method 500 may include scanning components of a data supply chain 104.
At block 504, the method 500 may include determining, based on the scan of the components of the data supply chain 104, configurations 112 of the components of the data supply chain 104.
At block 506, the method 500 may include analyzing the configurations 112 of the components of the data supply chain 104.
At block 508, the method 500 may include detecting, based on the analysis of the configurations 112 of the components of the data supply chain 104, a change in at least one of the configurations 112 of the components of the data supply chain 104 and a change in a configuration of the data supply chain 104.
At block 510, the method 500 may include comparing the change in the configuration of the data supply chain 104 against a corresponding configuration rule 116 to determine whether the change in the configuration of the data supply chain 104 is a defect that affects consistency of data related to the data supply chain 104.
At block 512, in response to a determination that the change is the defect that affects the consistency of the data related to the data supply chain 104, the method 500 may include determining, based on the corresponding configuration rule 116, a solution related to the defect that affects the consistency of the data related to the data supply chain 104.
At block 514, the method 500 may include modifying, based on the solution related to the defect that affects the consistency of the data related to the data supply chain 104, the configuration of the data supply chain 104 to correct the defect that affects the consistency of the data related to the data supply chain 104.
According to embodiments, the method 500 may include determining, based on the scan of the components of the data supply chain 104, configurations 112 of the components of the data supply chain 104 by determining, based on the scan of the components of the data supply chain 104, backup files of the components of the data supply chain 104.
According to embodiments, the method 500 may include identifying, based on the scan of the components of the data supply chain 104, versions of the backup files of the components of the data supply chain 104, analyzing different versions of the backup files of the components of the data supply chain 104 by comparing the different versions of the backup files of the components of the data supply chain 104 with respect to each associated component and each other component of the data supply chain 104, detecting, based on the analysis of the different versions of the backup files of the components of the data supply chain 104, the change in at least one of the versions of the backup files of the components of the data supply chain 104 and a change in a backup file of the data supply chain 104, and comparing the change in the backup file of the data supply chain 104 against another corresponding configuration rule 116 to determine whether the change in the backup file of the data supply chain 104 is another defect that affects consistency of further data related to the data supply chain 104.
According to embodiments, a method for data reliability analysis may include determining a scanning frequency of a component of a data supply chain 104 based on a corresponding configuration rule 116 related to the component of the data supply chain 104, and scanning, based on the scanning frequency, the component of the data supply chain 104. The method for data reliability analysis may further include determining, based on the scan of the component of the data supply chain 104, configurations 112 of the component of the data supply chain 104, analyzing the configurations 112 of the component of the data supply chain 104, and detecting, based on the analysis of the configurations 112 of the component of the data supply chain 104, a change in at least one of the configurations 112 of the component of the data supply chain 104. The method for data reliability analysis may further include comparing the change against the corresponding configuration rule 116 to determine whether the change is a defect that affects consistency of data related to the component, in response to a determination that the change is the defect that affects the consistency of the data related to the component, determining, based on the corresponding configuration rule 116, a solution related to the defect, and modifying, based on the solution related to the defect, a configuration of the configurations 112 to correct the defect that affects the consistency of the data related to the component. The method for data reliability analysis may further include determining a workflow order of components of the data supply chain 104 to modify the configuration of the component of the data supply chain 104 to correct the defect that affects the consistency of the data related to the component.
Figure 6 shows a computer system 600 that may be used with the examples described herein. The computer system may represent a generic platform that includes components that may be in a server or another computer system. The computer system 600 may be used as a platform for the system 102. The computer system 600 may execute, by a processor (e.g., a single or multiple processors) or other hardware processing circuit, the methods, functions and other processes described herein. These methods, functions and other processes may be embodied as machine readable instructions stored on a computer readable medium, which may be non-transitory, such as hardware storage devices (e.g., RAM (random access memory), ROM (read only memory), EPROM (erasable, programmable ROM), EEPROM (electrically erasable, programmable ROM), hard drives, and flash memory).
The computer system 600 may include a processor 602 that may implement or execute machine readable instructions performing some or all of the methods, functions and other processes described herein. Commands and data from the processor 602 may be communicated over a communication bus 604. The computer system may also include a main memory 606, such as a random access memory (RAM), where the machine readable instructions and data for the processor 602 may reside during runtime, and a secondary data storage 608, which may be non-volatile and stores machine readable instructions and data. The memory and data storage are examples of computer readable mediums. The memory 606 may include a data reliability analyzer 620 including machine readable instructions residing in the memory 606 during runtime and executed by the processor 602. The data reliability analyzer 620 may include the elements of the system 102 shown in Figures 1 and 2.
The computer system 600 may include an I/O device 610, such as a keyboard, a mouse, a display, etc. The computer system may include a network interface 612 for connecting to a network. Other known electronic components may be added or substituted in the computer system.
Particular and preferred aspects of the invention are set out in the accompanying independent claims. Combinations of features from the dependent and/or independent claims may be combined as appropriate and not merely as set out in the claims.

Claims

A data reliability analysis system (102, 620) comprising:
a configuration scanner (108), executed by at least one hardware processor (602), to
scan configurations (112) of a component of a data supply chain (104), the component being a data source, and

determine, based on the scan of the configurations (112) of the component of the data supply chain (104), configurations (112) of the component of the data supply chain (104);

a configuration analyzer (114), executed by the at least one hardware processor (602), to
analyze the configurations (112) of the component of the data supply chain (104) by comparing current configurations (112) to a previous version of the configurations (112),

detect, based on the analysis of the configurations (112) of the component of the data supply chain (104), a change in at least one of the configurations (112) of the component of the data supply chain (104),

compare the change against a corresponding configuration rule (116) pertaining to the component of the data supply chain (104), the configuration rule (116) being a rule where an attribute that describes how a data stream originating from an input signal will be handled in a particular system should be compliant, to determine whether the change is a defect that affects consistency of data (106) related to the component, wherein an inconsistency occurs when a Tag or same data stream has one or more attributes that include different values in different systems and a defect is a non-compliance of the change with the configuration rule (116), and

in response to a determination that the change is the defect that affects the consistency of the data (106) related to the component, determine, based on the corresponding configuration rule (116), a solution related to the defect; and

a configuration modifier (118), executed by the at least one hardware processor (602), to
modify, based on the solution related to the defect, a configuration of the configurations (112) associated with the particular component of the data supply chain (104) that is determined to be the source of the defect to correct the defect that affects the consistency of the data (106) related to the component.
The data reliability analysis system (102, 620) according to claim 1, where
the configuration scanner (108) is further to
scan components including the component of the data supply chain (104), and

determine, based on the scan of the components of the data supply chain (104), configurations (112) of the components of the data supply chain (104), and

the configuration analyzer (114) is further to
analyze the configurations (112) of the components of the data supply chain (104),

detect, based on the analysis of the configurations (112) of the components of the data supply chain (104), a change in at least one of the configurations (112) of the components of the data supply chain (104) and a change in a configuration of the data supply chain (104), and

compare the change in the configuration of the data supply chain (104) against another corresponding configuration rule (116) to determine whether the change in the configuration of the data supply chain (104) is another defect that affects consistency of further data (106) related to the data supply chain (104).
The data reliability analysis system (102, 620) according to claim 2, where
the configuration analyzer (114) is further to
in response to a determination that the change is the another defect that affects the consistency of the further data (106) related to the data supply chain (104), determine, based on the another corresponding configuration rule (116), a further solution related to the another defect that affects the consistency of the further data (106) related to the data supply chain (104), and

the configuration modifier (118) is further to
modify, based on the further solution related to the another defect that affects the consistency of the further data (106) related to the data supply chain (104), the configuration of the data supply chain (104) to correct the another defect that affects the consistency of the further data (106) related to the data supply chain (104).
The data reliability analysis system (102, 620) according to any one of claims 1 to 3, where the configuration scanner (108) is to determine, based on the scan of the component of the data supply chain (104), configurations (112) of the component of the data supply chain (104) by
determining, based on the scan of the component of the data supply chain (104), backup files of the component of the data supply chain (104).
The data reliability analysis system (102, 620) according to claim 4, where
the configuration scanner (108) is further to
identify, based on the scan of the component of the data supply chain (104), versions of the backup files of the component of the data supply chain (104), and

the configuration analyzer (114) is further to
analyze different versions of the backup files of the component of the data supply chain (104) by comparing the different versions of the backup files of the component of the data supply chain (104),

detect, based on the analysis of the different versions of the backup files of the component of the data supply chain (104), the change in at least one of the versions of the backup files of the component of the data supply chain (104), and

compare the change against the corresponding configuration rule (116) to determine whether the change is the defect that affects the consistency of the data (106) related to the component.
The data reliability analysis system (102, 620) according to claim 2, where the configuration scanner (108) is to determine, based on the scan of the components of the data supply chain (104), configurations (112) of the components of the data supply chain (104) by
determining, based on the scan of the components of the data supply chain (104), backup files of the components of the data supply chain (104).
The data reliability analysis system (102, 620) according to claim 6, where
the configuration scanner (108) is further to
identify, based on the scan of the components of the data supply chain (104), versions of the backup files of the components of the data supply chain (104), and

the configuration analyzer (114) is further to
analyze different versions of the backup files of the components of the data supply chain (104) by comparing the different versions of the backup files of the components of the data supply chain (104) with respect to each associated component and each other component of the data supply chain (104),

detect, based on the analysis of the different versions of the backup files of the components of the data supply chain (104), the change in at least one of the versions of the backup files of the components of the data supply chain (104) and a change in a backup file of the data supply chain (104), and

compare the change in the backup file of the data supply chain (104) against another corresponding configuration rule (116) to determine whether the change in the backup file of the data supply chain (104) is another defect that affects consistency of further data (106) related to the data supply chain (104).
The data reliability analysis system (102, 620) according to any one of claims 1 to 7, where the configuration rule (116) is related to the consistency of at least one of the component and the data supply chain (104); and/or
where the configuration analyzer (114) is further to determine whether the change is at least one of

a process based change related to a process associated with the component,

a security based change related to security of the component, and

a component based change related to hardware or code related to the component; and/or

where the configuration analyzer (114) is further to

record the modification to the configuration of the configurations (112) to correct the defect that affects the consistency of the data (106) related to the component, and

bypass analysis related to the modification for future analysis of the configurations (112) of the component of the data supply chain (104).
The data reliability analysis system (102, 620) according to any one of claims 1 to 8, further comprising:
a configuration controller (120), executed by the at least one hardware processor (602), to determine a scanning frequency of the component of the data supply chain (104) based on the corresponding configuration rule (116); or

a configuration controller (120), executed by the at least one hardware processor (602), to determine a scanning frequency of the component of the data supply chain (104) based on a computational load associated with the component of the data supply chain (104).
The data reliability analysis system (102, 620) according to any one of claims 1 to 9, further comprising:
a report generator (122), executed by the at least one hardware processor (602), to generate a report related to at least one of
the change in the at least one of the configurations (112) of the component of the data supply chain (104),

the solution related to the defect, and

the modification, based on the solution related to the defect, of the configuration of the configurations (112) to correct the defect that affects the consistency of the data (106) related to the component.
The data reliability analysis system (102, 620) according to any one of claims 1 to 10, where the configuration modifier (118) is further to
determine a workflow order of components of the data supply chain (104) to modify the configuration of the component of the data supply chain (104) to correct the defect that affects the consistency of the data (106) related to the component,

where the data reliability analysis system (102, 620) may further comprise:
a report generator (122), executed by the at least one hardware processor (602), to generate a report related to the workflow order of the components of the data supply chain (104) to modify the configuration of the component of the data supply chain (104) to correct the defect that affects the consistency of the data (106) related to the component.
A method for data reliability analysis, the method comprising:
scanning, by a hardware processor (602), configurations (112) of components of a data supply chain (104), the components being data sources;

determining, based on the scan of the configurations (112) of components of the data supply chain (104), configurations (112) of the components of the data supply chain (104);

analyzing the configurations (112) of the components of the data supply chain (104) by comparing current configurations (112) to a previous version of the configurations (112);

detecting, based on the analysis of the configurations (112) of the components of the data supply chain (104), a change in at least one of the configurations (112) of the components of the data supply chain (104) and a change in a configuration of the data supply chain (104);

comparing the change in the configuration of the data supply chain (104) against a corresponding configuration rule (116) pertaining to the component of the data supply chain (104), the configuration rule (116) being a rule where an attribute that describes how a data stream originating from an input signal will be handled in a particular system should be compliant, to determine whether the change in the configuration of the data supply chain (104) is a defect that affects consistency of data (106) related to the data supply chain (104), wherein an inconsistency occurs when a Tag or same data stream has one or more attributes that include different values in different systems and a defect is a non-compliance of the change with the configuration rule (116);

in response to a determination that the change is the defect that affects the consistency of the data (106) related to the data supply chain (104), determining, based on the corresponding configuration rule (116), a solution related to the defect that affects the consistency of the data (106) related to the data supply chain (104); and

modifying, based on the solution related to the defect that affects the consistency of the data (106) related to the data supply chain (104), the configuration of the data supply chain (104) associated with the particular component of the data supply chain (104) that is determined to be the source of the defect to correct the defect that affects the consistency of the data (106) related to the data supply chain (104).
The method for data reliability analysis according to claim 12, where determining, based on the scan of the components of the data supply chain (104), configurations (112) of the components of the data supply chain (104) further comprises:
determining, based on the scan of the components of the data supply chain (104), backup files of the components of the data supply chain (104),

where the method may further comprise:
identifying, based on the scan of the components of the data supply chain (104), versions of the backup files of the components of the data supply chain (104);

analyzing different versions of the backup files of the components of the data supply chain (104) by comparing the different versions of the backup files of the components of the data supply chain (104) with respect to each associated component and each other component of the data supply chain (104);

detecting, based on the analysis of the different versions of the backup files of the components of the data supply chain (104), the change in at least one of the versions of the backup files of the components of the data supply chain (104) and a change in a backup file of the data supply chain (104); and

comparing the change in the backup file of the data supply chain (104) against another corresponding configuration rule (116) to determine whether the change in the backup file of the data supply chain (104) is another defect that affects consistency of further data (106) related to the data supply chain (104).
A non-transitory computer readable medium having stored thereon machine readable instructions for data reliability analysis, the machine readable instructions when executed cause a computer system to:
determine a scanning frequency of a component of a data supply chain (104) based on a corresponding configuration rule (116) related to the component of the data supply chain (104), the component being a data source;

scan, based on the scanning frequency, configurations (112) of the component of the data supply chain (104);

determine, based on the scan of the configurations (112) of the component of the data supply chain (104), configurations (112) of the component of the data supply chain (104);

analyze the configurations (112) of the component of the data supply chain (104) by comparing current configurations (112) to a previous version of the configurations (112);

detect, based on the analysis of the configurations (112) of the component of the data supply chain (104), a change in at least one of the configurations (112) of the component of the data supply chain (104);

compare the change against the corresponding configuration rule (116) pertaining to the component of the data supply chain (104), the configuration rule (116) being a rule where an attribute that describes how a data stream originating from an input signal will be handled in a particular system should be compliant, to determine whether the change is a defect that affects consistency of data (106) related to the component, wherein an inconsistency occurs when a Tag or same data stream has one or more attributes that include different values in different systems and a defect is a non-compliance of the change with the configuration rule (116);

in response to a determination that the change is the defect that affects the consistency of the data (106) related to the component, determine, based on the corresponding configuration rule (116), a solution related to the defect; and

modify, based on the solution related to the defect, a configuration of the configurations (112) associated with the particular component of the data supply chain (104) that is determined to be the source of the defect to correct the defect that affects the consistency of the data (106) related to the component.
The non-transitory computer readable medium according to claim 14, further comprising machine readable instructions that when executed further cause the computer system to:
determine a workflow order of components of the data supply chain (104) to modify the configuration of the component of the data supply chain (104) to correct the defect that affects the consistency of the data (106) related to the component.