WO2015074673A1 - Système de signalisation optimisé - Google Patents

Système de signalisation optimisé Download PDF

Info

Publication number
WO2015074673A1
WO2015074673A1 PCT/EP2013/003510 EP2013003510W WO2015074673A1 WO 2015074673 A1 WO2015074673 A1 WO 2015074673A1 EP 2013003510 W EP2013003510 W EP 2013003510W WO 2015074673 A1 WO2015074673 A1 WO 2015074673A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
reporting
report
computing
entry
Prior art date
Application number
PCT/EP2013/003510
Other languages
English (en)
Inventor
Dirk Schulz
Original Assignee
Abb Technology Ag
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Abb Technology Ag filed Critical Abb Technology Ag
Priority to PCT/EP2013/003510 priority Critical patent/WO2015074673A1/fr
Publication of WO2015074673A1 publication Critical patent/WO2015074673A1/fr

Links

Classifications

    • GPHYSICS
    • G05CONTROLLING; REGULATING
    • G05BCONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B19/00Programme-control systems
    • G05B19/02Programme-control systems electric
    • G05B19/04Programme control other than numerical control, i.e. in sequence controllers or logic controllers
    • G05B19/042Programme control other than numerical control, i.e. in sequence controllers or logic controllers using digital processors
    • G05B19/0428Safety, monitoring
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06Management of faults, events, alarms or notifications
    • H04L41/0686Additional information in the notification, e.g. enhancement of specific meta-data
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00Arrangements for monitoring or testing data switching networks
    • H04L43/06Generation of reports

Definitions

  • the invention relates to a reporting-system, for a distributed control system comprising at least one control-device which is configured for providing respective device-data, time variant measurement-data and/or object-data wherein the reporting system comprises:
  • at least one database which is connected to the control-device and which is configured for receiving the provided data
  • at least one computing-device which is connected to the database and which is configured for
  • the invention relates also to a method for generating a report, with the reporting system, comprising the following steps:
  • generating the report with at least one entry in case of at least one event of the control-device, by the computing-device.
  • Reporting is an essential activity during the entire life-cycle of distributed control systems (DCSs) as it is critical to operational, productivity, and regulatory requirements. Nodaway's DCSs are becoming increasingly complex as more and more control-devices are interconnected, therefore the related reporting-systems become also more complex.
  • DCSs distributed control systems
  • Reporting-systems are generally used to report a malfunction of a control-device or even a malfunction of the entire DCS to an operator. Reporting can also include the data of the first requirements collection with customers, documentation of offline engineering documents, factory acceptance test results, or fingerprinting and health reports during plant operation. In the reporting procedure periodic reports are also known, which are set up by the reporting-systems in a predefined time interval, for example hourly, shiftily, or monthly. Additionally reports can be triggered by the operator.
  • control-device comprises every electronic device, which might be connected to and controlled by a DCS.
  • a “control-device” can be for example a field device of a distributed control system, a switch, router, I/O device or even a central control room.
  • the connection to the DCS can be a digital or analogue and it could be either wireless or wired.
  • a DCS usually comprises at least one "control-device", which is configured for controlling the operation of a respective actuating part of an industrial plant during a production process.
  • the actuating parts may be for example a single actuator such as a motor, a pump, a valve or a switch, or groups of actuators or a whole operational section of the industrial plant.
  • measurement-data comprises data which are measured, received or determined by the control-device, for example output variables of the actuating parts.
  • Another example for measurement-data is the measured pressure value of a pump.
  • a control device is preferably arranged to measure, receive or determine measurement data of the respective actuating part, where the measurement-data might be either generated directly from measurements taken form sensors, or indirectly, by estimating the measurement data from available further state information. Based on measurement-data, which can be measured and provided in real-time, maintenance operators can monitor the health of the respective actuating part.
  • device-data comprises all characteristic data of the control-device or the respective actuating part. Exemplary, this can be the data given on a nameplate of the actuating part, input power, output power, number of revolution, production date, type number, or any other characteristic data of interest.
  • object-data comprises all data, which were further processed in the DCS.
  • a control-loop which has measurement data as input generates object- data as output.
  • object-data can be control parameter resulting from a PID control loop for controlling an heat exchanger. Therefore, the term “object-data” refers to higher-order data, which might be any kind of processed data.
  • a “database” is one requirement for a reporting-system.
  • the database is connected to the control-device and it is configured for receiving the respective data thereof.
  • the database can be either a conventional relational database or a service-based architecture. Different kind of databases can be implemented in the DCS, for example SQL or DB2 databases.
  • a “computing-device” is required by the reporting-system.
  • the computing device is connected to the database and it reads out the data and generates a report with at least one entry in case of at least one event of the control- device.
  • the "computing-device” can be a usual personal computer, an independent processing-unit, or even a processing unit integrated in the DCS.
  • a “link” is typically used for referencing from any location to any data.
  • the at least one entry comprises at least one reference, with a relating link, to the respective device-data, measurement-data and/or object-data.
  • the invented reporting-system enables a fast tracking of data relating to an entry of a report by following a reference, or a link.
  • the "reference" of the entry enables the operator to navigate to the data manually. This is especially advantageous when being offline, for example when an operator goes down to the shop floor and has no wireless internet connection on his mobile computer. Navigating by the reference is a manual process, mainly used when it is not possible to follow the link automatically.
  • the entry comprises a relating "link" to the respective data.
  • the link might be a local link or a global link. In case of a local link the link and the existing file are on one computer system, in case of a global link the link and the existing file are on separate computer systems.
  • the link enables the user to navigate to the respective data automatically.
  • the entry-related data then becomes instantly available.
  • the invented reporting-system provides fast navigation from an entry to the detailed data required to handle it correctly. This provides a faster access to the data needed for decision making. Furthermore the user is less distracted by attention-stealing search effort.
  • the invented reporting-system simplifies the work, especially for new employees or people who are in a hurry to find the location of data relating to an event. The user is enabled to work more efficiently as the simple, but time-consuming, search effort is taken away.
  • a report may not only lead one user to the respective data, but it might also support collaboration between different users sitting in different locations. Several users can quickly and with little explanation share a data relating to entries from two copies of a report.
  • the invented reporting-system integrates reports with the respective data.
  • the reporting-system makes it more simple and convenient to navigate to the desired data.
  • the report is also useful meanwhile the user is offline.
  • the at least one entry refers to at least one event, particularly a fault-event, of the control-device, wherein the reference comprises a unified nomenclature by which a user can navigate to the data.
  • the event is a fault-event, which is also known as an alarm-event
  • the operator needs to gather as much relevant information as necessary, to react proactively.
  • Fault-events are generated, in case that predefined threshold levels are exceeded.
  • Reports with fault events are usually composed of several fault entries, wherein new fault entries are continuously added to the report.
  • the invention optimizes therefore the operator's ability to monitor processes in a plant, which means that an operator can be entrusted with larger plant sections without compromising safety. This results in the opportunity, to consolidate several plant-units into one unit for greater efficiency.
  • the computing-device is configured for storing the at least one entry in a file.
  • the file is a non-volatile memory, which is exchangeable between different computing-devices.
  • a file enables the operator to send the report to other operators, or to use the file on an offline mobile computer. Hence, the created report becomes more flexible
  • file management As a file is generated of the report, the advantages related to file management can be also integrated in the reporting-system. File management provides a better overview over the existing report. Furthermore conflicts between different versions of the report can be avoided, and the versioning of the files is generated automatically.
  • the reporting- system further comprises:
  • at least one report-viewer which is configured for displaying the report to the user
  • at least one navigation-unit which is connected to the report-viewer and the database and which is configured for navigating, in case that the link is selected via user-input, to the respective data.
  • the report-viewer is configured for displaying the report in a predefined way, so that the look and feel of the distributed control system is advantageously preserved in the reporting-system and the respective data are presented in a unified way. This reduces training and start-up time for operators and it retains the ability to interact easily. Furthermore, additional alarm features can be provided with the report-viewer, which allow operators to pre-configure different kind of displays which are automatically invoked when selecting a link.
  • the report-viewer can filter the entries based on different categories and present the entries separately to the user. This is especially advantageous when needing to separate entries with references to different types of data. Furthermore the report-viewer may show a preview of the respective data to the operator before navigating to the data.
  • the navigation-unit is integrated in the report-viewer and connected to the database.
  • the navigation-unit navigates automatically to the respective data in case of selecting an entry. Hence, an entry can be followed even faster, when the data are needed for further information.
  • the navigation-unit is configured for authenticating the user before navigating to the data.
  • the navigational-unit authenticates the user before granting an access to the desired data. This safety procedure protects the whole system from unauthorized navigation, by controlling the respective access to the data.
  • the authentication function comprises several single authentication functions, such as re- and double authentication, user log over, audit trail and electronic signatures.
  • Re-authentication is used to ensure that certain operations are performed by the logged-in person. Hence, the logged-in person has to login again, before performing a critical operation. Re-authentication results in an audit event, and thus also serves as an electronic signature for the operation.
  • Double-authentication can be required before accepting certain, critical, operations.
  • an additional person one who has secondary authentication permission, must authenticate and therefore approve the operation.
  • the Log over authentication procedure is useful to hand over between different users in cases were a certain operation requires higher authority than held by the current user.
  • Exemplary a supervisor can allow his responsibility to be temporarily applied, before reverting to the normal user.
  • Access control can be based on user, role, and location, and access rights can be set with granularity down to single objects and properties.
  • the reporting-system handles navigation requests considering the role and access rights of the requesting user.
  • the authentication functionality prevents advantageously unauthorized access, as well as problems caused by mistakes.
  • the computing-device comprises at least one reporting-interface for reading out the data and/or
  • the navigation-unit comprises at least one navigation-interface for navigating to the data.
  • reporting-interface and the navigation-interface are integrated in the reporting- system different kind of distributed-control-system, different kind of databases and different kind of data can be advantageously interfaced and therefore accessed without interfering manually.
  • the reporting- and the navigation interface are preferably pre-integrated in the reporting-system and different kind of communication protocols are available. By the pre-integration of the reporting- and navigation- interfaces, fast navigation from an entry to the respective data is enabled and nuisance delays are avoided.
  • the computing-device is configured for:
  • allocating a time-stamp to the at least one entry, by which the user can navigate in a timeline of the respective data.
  • the data are versioned and archived. Following a link from a report leads to the source of the data, the current state of the data, or any other point in time of the data which is available through the allocated time-stamp.
  • the database is further configured for receiving the measurement-data over a time- period, wherein the control-unit is configured for allocating a timeline to the received measurement-data. Therefore the operator can advantageously navigate to any point of time in the measurement-data and the detailed history from the devices can be retrieved at any time. Hence, linking into a past baseline version of offline or online transient data is advantageously supported. Retrieving the history is for example required for root-cause analysis. The history can be accessed through trend- and periodic-reports. The sample rate for time-stamping is configurable.
  • the distributed control system comprises several control-devices, wherein the reporting system comprises several databases.
  • a typical DCS consists of several functionally and/or geographically distributed control-devices.
  • the integration of the invented reporting-system with the DCS enables detection of early warnings from the entire DCS with all the control-devices.
  • the invented reporting-system increases the convenience for users to work with the reports, including reports which were provided as services such as fingerprinting. It lowers the effort to communicate with a further user, which might be a customer, on any point of time of the distributed control-system.
  • the reporting-system provides a single report which considers all control-devices and gives therefore a better overview over the entire DCS.
  • the reporting-system comprises several at least partly interconnected computing-devices, wherein one is configured as a master computing-device which is configured for:
  • one of the computing-devices is configured as a master computing-device
  • several computing-devices can be controlled in a safe and effective way.
  • the different computing-devices can be controlled from one distributed control system. Therefore one single master computing-device unifies the control of the further computing-devices and consequently the control of the several control-devices.
  • the objective is further accomplished according to the present invention by an abovementioned method for generating a report, characterized in that the entry comprises at least one reference, with a relating link, to the respective device-data, measurement-data and/or object-data.
  • the method further comprises the following steps:
  • the method further comprises the following steps:
  • the method further comprises the following steps:
  • Fig. 1 an exemplary personal computer for running a reporting-system according to the invention
  • Fig. 2 an exemplary first architecture of a reporting-system
  • Fig. 3 an exemplary second architecture of a reporting-system
  • Fig. 4 an exemplary third architecture of a reporting-system
  • Fig. 5 an exemplary report
  • Fig. 6 an exemplary further report
  • Fig. 7 an exemplary sequence diagram.
  • Fig. 1 depicts exemplary a personal computer 44 for executing a reporting-system according to the invention.
  • the personal computer 44 is connected to an input de- vice 40, to a display 46 and to a distributed control-system 2a.
  • a user 24 specifies his user input 42 via the input device 40, exemplary a keyboard or a usual computer mouse.
  • the user input 42 is further processed by the personal computer 44, wherein data are provided from a control-device 4a of the distributed control-system 2a to the personal computer 44.
  • the display 46 is exemplary used for displaying a link 20 to the respective data, which can be for example device-data, measurement-data and/or object-data.
  • the data may be also information sources such as engineering data items or objects, live data including condition monitoring results of processes monitoring and optimization, status of maintenance, ordering, or other enterprise resource planning (ERP) activities.
  • ERP enterprise resource planning
  • the display 46 can be configured as a touch pad. It is also not depicted, that the personal computer 44 can be exemplary provided in a computing cloud, instead of being provided physically. The personal computer 44 can be also integrated in the distributed-control-system 2a itself.
  • the personal-computer can comprise a database, or exemplary connect one or several single databases of the distributed control system 2a.
  • Fig. 2 depicts exemplary a first architecture of a reporting-system a.
  • the reporting- system 1a needs to be engineered in order to fulfill the required behavior and the specification.
  • the reporting-system 1a is complex, it is divided into subsystems which may consist of hardware and software components from different suppliers.
  • a database 10a is exemplary configured for receiving device-data 6a, measurement- data 8a and object-data 9a from a control-device 4b of a distributed-control-system 2b.
  • the data 6a, 8a, 9a might be also received by a program or a computing-cloud.
  • the heart of the reporting-system 1a is a computing-device 12a which reads out the data 6a, 8a, 9a from the database 10a.
  • the figure does not limit the physical allocation of the computing-device 12a and the database 10a.
  • the database 10a and the computing-device 12a can be either integrated in the distributed-control-system 2b or separately in the reporting-system 1a.
  • the database 10a and the computing-device 12a are associated independently either to the reporting-system 1a or to the distributed-control-system 2b.
  • the computing-device 12a After reading out the respective data 6a, 8a, 9a, the computing-device 12a generates a report 14a, with at least one entry 16a.
  • the entry comprises at least one reference 18a which enables the user to navigate to the data manually. Therefore, the report 14a is not necessarily connected to the reporting-system 1 a or to the computing- device 12a. Due to the reference 18a, the report 14a can be used independently without any connecting to the reporting-system 1a or the distributed-control-system 2b.
  • the entry 16a might indicate a fault, wherein the fault can be a fault in the control-device 4b itself, or exemplary in the process or the instrumentation of the control-device 4b.
  • the entry further comprises a link 20a, by which a user is navigated automatically to the data, in case of selecting the link. Therefore the report 14a is made more intelligent by introducing the link 20a which allows a user to navigate to the source of a piece of information within the distributed-control-system 2b.
  • Fig. 3 depicts exemplary a second architecture of a reporting-system 1 b. Additionally to figure 2 a user 24 is depicted, who selects a link by user-input 42 on a report- viewer 22. Furthermore, a reporting-interface 30 is depicted, which is situated between a computing-device 12b and a database 10b, and which is configured for reading-out device-data 6b, measurement-data 8b and/or object-data 9b stored in the database 10b. The reporting-interface 30 is configured for adapting different kind of data 6b, 8b, 9b different kind of databases 10b and different control-devices. The reporting-interface 30 can include various, not depicted, protocol interfaces and pre- integrated interfaces to multiple databases 10b and different data sets.
  • the reporting-interface 30 can be either a software running on the computing-device 12b or a physically interface which is adapted to the database 10b.
  • the report-viewer 22 can be exemplary a usual pdf-reader or any other viewing program, which presents the report in a unified way.
  • a navigation-unit 26 is depicted with a navigation-interface 28.
  • the navigation-unit 26 and the navigation-interface 28 are either provided physically, or as a software interface.
  • the interfaces 28, 30 different kind of data from various sources can be transferred, e.g. by WirelessHART or via Modbus TCP.
  • the navigation-interface 28 and the reporting-interface 30 eliminate the need to switch between several systems, workplaces, application environments and navigation schemes.
  • the navigation-unit 26 may be configured for authenticating the user before navigating to the data 6b, 8b, 9b.
  • the user authentication function is exemplary designed to meet requirements from regulated industries.
  • exemplary default user groups with default permissions are created. These can be changed to fit the needs of any distributed-control-system.
  • Password policies can be configured, e.g. for minimum strength and maximum age.
  • Authority checking can be done by comparing a user's granted permissions with the respective permission to perform an operation.
  • data 6b, 8b, 9b need to be protected from being disclosed to unauthorized users.
  • the loss of confidentiality for these types of data 6b, 8b, 9b may cause significant losses.
  • the secrets of the authentication mechanisms in the navigation-unit itself, such as passwords and encryption keys should be protected. In case of revealing the encryption method, the system is unprotected against many attacks.
  • Permissions can be set globally for the whole distributed-control-system, or only for single databases 10b, or even only on individual data 6b, 8b, 9b to match every possible need. Also the location from where the user 24 is working can be included in the authority settings.
  • the user authentication function may be exemplary based on the Windows® mechanisms.
  • Fig. 4 depicts an exemplary third architecture of a reporting-system 1 c which comprises exemplary two computing-devices 12c, 13 wherein one of these is configured as a master computing-device 13.
  • a distributed control system 2c comprises two control-devices 4c and 4d, which can be connected directly by a not depicted connection.
  • Each of the control-devices 4c, 4d has a related database 10c and a related database 10d.
  • the master computing-device 13 controls the computing-device 12c and has therefore indirectly access to the database 10d of the control-device 4d.
  • the database 10c has two versions of device-data: device data 6c and device-data 6d, which might be linked with a timestamp.
  • a relating entry of a report 14b is linked with a timestamp, wherein the entry relates exemplary to file 1 of the device data 6c.
  • Fig. 5 depicts an exemplary report 14c, which comprises more than one entry: an entry 16b and a further entry 16c.
  • Each entry, the entry 16b and the further entry 16c, comprises a single reference 18b and 18c.
  • each reference comprises a single link, 20b and 20c.
  • a user can navigate to different databases, and more specific to different files of the databases, wherein each file represents a specific time of respective data, exemplary time 1 and time 2.
  • the reference comprises exemplary a unified nomenclature by which the user can navigate to the data.
  • the nomenclature is preferably standardized, exemplary in the following form: "dcs: ⁇ project id>: ⁇ baseline version>: ⁇ tool name> ".
  • the report 14c on offline data may be based on a particular version or baseline of data, Furthermore, also live or transient data at the time of reporting may be versioned or baselined. Following a link from the report 14c may lead to the information source within the baseline, which can be taken from a versioning system, the current state of the source, any other point in time available through versioning or a difference view between two such versions.
  • a user might follow a problem identified in fingerprinting when it was reported, check both the past and the current state of the information source, search for the point in time where the issue disappeared, and then use a difference view to detect a root cause.
  • Fig. 6 depicts an exemplary further report 14d which comprises three fault entries.
  • the report depicts exemplary a fault report.
  • An entry 16d with the highest priority is listed at the top.
  • Each fault occurred at the respective active time of the second column.
  • the first entry 16d refers to valve number 1 , which might be controlled by a not depicted control-device.
  • valvel was operated by high temperature.
  • the operator might be directed directly to the measurement-data, which is in this example the temperature.
  • the reference When crossing the link 20d with the arrow of an input-device, the reference might pop-up which informs the user about the location of the saved temperature data. Therefore the respective reference may be only presented to the user when taking a closer look.
  • Fig. 7 depicts an exemplary sequence diagram illustrating the complete steps according to the present invention.
  • data are provided by control-devices.
  • the data can exemplary be device-data, measurement-data and/or object-data.
  • the data might be also provided by a planning tool or any other program.
  • a second step "b" the data are received from the database and stored therein.
  • the database can be either a conventional relational database or a service-based architecture.
  • the database may be either located at one location, or distributed in the distributed control system.
  • the database can exemplary be provided as a volatile memory, or as a non-volatile memory.
  • a third step "c" the computing-device is reading out the data from the respective database.
  • the term “reading out” the respective data refers to getting the required information for generating the entry to the respective data.
  • a fourth step "d" the computing-device is generating the report with a reference and a link to the respective data.
  • the link enables the user to navigate automatically to the data behind the respective reference. Following the link allows any user to navigate to the source of piece of information within any distributed control system tool, while considering the security constraints of industrial automation.
  • step "e” the report is displayed to a user, advantageously by a report-viewer.
  • a sixth step “f" the user navigates to the data either manually by following the provided reference, or automatically by selecting the provided link.
  • the user navigates manually.
  • Offline documents are naturally static in nature. Unclear, missing or interesting but incomplete parts require follow-up communication. This requires at the very least leaving the context of the report, finding the right person to contact or tool to use, and it requires the correct information context, exemplary the reference, to get more information. This is a manual process without any workflow supported.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Automation & Control Theory (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

L'invention concerne un système de signalisation (1a, 1b, 1c), destiné à un système de commande distribué (2a, 2b, 2c) comprenant au moins un dispositif de commande (4a, 4b, 4c, 4d) qui est configuré pour produire des données de dispositif respectives (6a, 6b, 6c, 6d, 6e), des données de mesure variant dans le temps (8a, 8b) et/ou des données d'objet (9a, 9b), le système de signalisation (1a, 1b,1c) comprenant : - au moins une base de données (10a, 10b, 10c, 10d) qui est reliée au dispositif de commande (4a, 4b, 4c, 4d) et qui est configurée pour recevoir les données produites (6, 8, 9); - au moins un dispositif informatique (12a, 12b, 12c) qui est relié à la base de données (10a, 10b, 10c, 10d) et qui est configuré pour : - lire les données respectives (6, 8, 9); - générer un rapport (14a, 14b, 14c) avec au moins une entrée (16a, 16b, 16c) dans le cas d'un déclenchement; - ladite au moins une entrée (16a, 16b, 16c) comprenant au moins une référence (18a, 18b, 18c), avec un lien associé (20a, 20b, 20c), aux données de dispositif respectives (6a, 6b, 6c, 6d, 6e), aux données de mesure (8a, 8b) et/ou aux données d'objet (9a, 9b). L'invention concerne également un procédé pour générer un rapport (14a, 14b, 14c) avec le système de signalisation (1a, 1 b, 1c) selon la présente invention.
PCT/EP2013/003510 2013-11-21 2013-11-21 Système de signalisation optimisé WO2015074673A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2013/003510 WO2015074673A1 (fr) 2013-11-21 2013-11-21 Système de signalisation optimisé

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2013/003510 WO2015074673A1 (fr) 2013-11-21 2013-11-21 Système de signalisation optimisé

Publications (1)

Publication Number Publication Date
WO2015074673A1 true WO2015074673A1 (fr) 2015-05-28

Family

ID=49876535

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2013/003510 WO2015074673A1 (fr) 2013-11-21 2013-11-21 Système de signalisation optimisé

Country Status (1)

Country Link
WO (1) WO2015074673A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5920867A (en) * 1996-12-06 1999-07-06 International Business Machines Corporation Data management system having data management configuration
US20040153437A1 (en) * 2003-01-30 2004-08-05 Buchan John Gibb Support apparatus, method and system for real time operations and maintenance
CN102880149A (zh) * 2012-05-09 2013-01-16 上海西门子工业自动化有限公司 一种分布式控制系统和数据报表生成方法

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5920867A (en) * 1996-12-06 1999-07-06 International Business Machines Corporation Data management system having data management configuration
US20040153437A1 (en) * 2003-01-30 2004-08-05 Buchan John Gibb Support apparatus, method and system for real time operations and maintenance
CN102880149A (zh) * 2012-05-09 2013-01-16 上海西门子工业自动化有限公司 一种分布式控制系统和数据报表生成方法

Similar Documents

Publication Publication Date Title
CN107957717B (zh) 用于使远程设备订阅控制数据的方法和系统
JP5850033B2 (ja) フィールド機器管理装置、機器情報表示方法、コンピュータプログラムおよび記録媒体
EP1621944B1 (fr) Système de sécurité et procédé pour un système d'automatisation industriel
JP6377691B2 (ja) プロセス制御の検索結果を表示するための方法および装置、機械可読命令を格納する有形製品
US9494931B2 (en) Dynamic hyperlinks for process control systems
EP3256980A1 (fr) Appareil et procédé de fourniture de causes possibles, d'actions recommandées et d'impacts potentiels relativement à des éléments de risques identifiés de cybersécurité
US20190114211A1 (en) Apparatus and method for multitenancy in cloud environments for processing large datasets
JP2007188201A (ja) 勤怠管理システム
JP2019053731A (ja) プロセス制御システムに関連付けられた構成ファイルを評価するためのシステム及び方法
US20150293530A1 (en) Manufacturing execution system authorization
KR20150033453A (ko) 빅데이터 처리 방법, 이를 수행하는 빅데이터 처리 장치 및 이를 저장하는 기록매체
US20200135342A1 (en) Immutable System of Records for IoT / Control Systems for Compliance
TWI703452B (zh) 監測及控制用於生產鑽石的多個機器的操作之系統及相關方法和計算裝置
US20190116170A1 (en) Apparatus and method for containerization at a cluster
JP6900727B2 (ja) エンジニアリング支援システム、エンジニアリング支援方法、クライアント装置、及びクライアントプログラム
US20090062950A1 (en) System and method for monitoring production of cnc machines
JP6243733B2 (ja) 設備管理システムおよび方法
WO2015074673A1 (fr) Système de signalisation optimisé
JP6210108B2 (ja) フィールド機器管理装置、機器情報表示方法、コンピュータプログラムおよび記録媒体
US20060224802A1 (en) Control system
US9898702B2 (en) Method, computer program product, and apparatus for managing decision support related event information
JP7121566B2 (ja) 設備管理装置および方法
US7882250B2 (en) Device for provision of role-based access to data through a central interface
JP5873300B2 (ja) 業務管理システムおよびコンピュータプログラム
JP2017098763A (ja) 管理サーバーおよび管理方法

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 13811374

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 13811374

Country of ref document: EP

Kind code of ref document: A1