Abstract: A method for converting FDI Device Packages and EDDs to FDT device DTMs [0030] The present invention relates to a method of converting the known Field Device Integration (FDI) Device Packages and Electronic Device Descriptions (EDD) to Field Device Tool (FDT) / Device Type Managers (DTM). The method comprises the steps of inputting (101) Electronic Device Descriptions (EDD) and Field Device Integration (FDI) Device packages in the tool comprising a Device Type Managers generator (102), where the computation of corresponding Device Type Managers (DTM) with the help of the tool takes place. (FIGURE 1)
Claims:1. A method for converting Field Device Integration (FDI) Device Packages and Electronic Device Descriptions (EDD) to Field Device Tool/Device Type Managers (DTM), the method comprising the steps of:
inputting one or more Field Device Integration Device Package or Electronic Device Description in the tool comprising a Device Type Manager generator (101);
computing a corresponding Device Type Manager with the help of the tool (102); and
outputting a required Field Device Tool/Device Type Manager (103).
2. The method as claimed in claim 1, wherein the Electronic Device Description and the Field Device Integration Device package in the Device Type Manager generator are provided by the user in the framework; wherein the user can also provide device specific custom code for specific usage.
3. The method as claimed in claim 1, wherein the computation is done within a Device DTM (203), wherein a communication DTM (204) helps in interaction with a field device.
4. The method as claimed in claim 1, wherein the output of the conversion is used by the FDT host device (205) for interaction with the field device (206).
5. The method as claimed in claim 1, wherein Device Type Manager are of FDT 1.2 and FDT 2.
6. The method as claimed in claim 2, wherein the device specific custom code (202) can be customized by the user for specific code according to the usage.
, Description:PREAMBLE TO THE DESCRIPTION:
[0001] The following specification particularly describes the invention and the manner in which it is to be performed:
DESCRIPTION OF THE INVENTION:
Technical field of the invention
[0002] The present invention relates to a method of converting the known Field Device Integration (FDI) Device Packages and Electronic Device Descriptions (EDD) to Field Device Tool (FDT) / Device Type Managers (DTM).
Background of the invention
[0003] The rapid evolution of technology in industrial automation systems requires tighter integration between devices on the plant floor and the rest of the enterprise. This integration requires a secure network infrastructure, smart devices for efficient data collection, and the ability to turn data into actionable information.
[0004] Over the years, device integration has been a subject of great importance in the world of industrial automation to ensure system-wide interoperability, security and optimal plant performance. There are three existing device integration standards, these are EDDL (Electronic Device Description Language), FDT/DTM (Field Device Tool/Device Type Manager) and FDI (Field Device Integration).
[0005] The Electronic Device Description Language (EDDL) is a language for describing the behavior of field devices. It enables systems to configure, calibrate, troubleshoot, and operate a field device without any prior knowledge of the device.
[0006] Device descriptions written in EDDL describe the capabilities of the field device; it is up to the system to determine how to utilize these capabilities. These device descriptions enable systems to access all the data and properties of all devices, which simplifies the maintenance, support, and operation of the devices. It works well for small handheld applications and large integrated automation systems. It works well for embedded systems and the systems running on commercial operating systems.
[0007] Field Device Tool (FDT) is an interface specification that standardizes the interface between the device software and the systems. In FDT, field devices are delivered with a device-specific software component called a Device Type Manager (DTM), which is only functional when used in conjunction with an FDT-specific environment called a "frame application". A frame application interacts with a DTM through a set of standard FDT interfaces.
[0008] A device supplier can develop a DTM for each of its devices, or it can develop a DTM for a group of devices. A DTM can be used to access Device Parameters, configure and operate the device, and diagnose problems. A DTM can range from a simple Graphical User Interface (GUI) for setting Device Parameters to a highly sophisticated application for performing complex calculations for diagnosis.
[0009] Field Device Integration (FDI) is an emerging device integration technology in the process automation industry. The core of FDI standard is the FDI Device Package. It is a standardized container having all the elements required for describing the field device in the plant. FDI Device Package contains EDDL to manage the device operations and optional UIP (User Interface Plug-in) to describe the complex device functionalities like echo curve, valve signature etc.
[0010] The US Patent US20170093621A1 titled “Method for managing and configuring field devices of an automation system”, discloses a method for managing and configuring one or more field devices of an automation system. Here, the invention helps in logical integration of the said device in the automation system and then helps to configure it in the automation system, wherein for this purpose the configuration tool draws on a predefined first information package that is specific to the field device and describes at least some of the functions and data of the field device. However, there is no mention of converting one device integration standard to another.
[0011] The US Patent US8345710B2 titled, “FDT for EDDL-based field devices”, discloses an asset management system. Here, the FDT-based application is configured to transfer data from the asset optimization device manager to the plant asset using at least one communication DTM that corresponds with a type of communication protocol that an at least one plant asset follows. However, this asset management system is completely different from conversion of device integration standard to another.
[0012] No present solution gives DTM from FDI Device Package. Previous prior art just gives adaptor rather than convertor among these three device integration standards. So, there is need for converting EDD or FDI packages to FDT DTM.
Summary of the Invention:
[0013] The present invention provides a conversion mechanism Field Device Integration (FDI) Device Packages and Electronic Device Descriptions (EDD) to Field Device Tool (FDT) / Device Type Managers (DTM). No one to one conversion exists from FDI Device package to DTM. Existing solutions are just acting as an adapter rather than converter.
[0014] The method comprises the steps of inputting Electronic Device Descriptions (EDD) and Field Device Integration (FDI) Device packages in the tool comprising a DTM generator, where the computation of corresponding Device Type Managers (DTM) with the help of the tool takes place.
[0015] The tool outputs the required Device Type Managers (DTM) for further use, which are of Field Device Tool (FDT) standards. This can be FDT 1.2/FDT 2 Devise DTM. The tool contains internally an algorithm to perform the said function.
[0016] The conversion mechanism enables the user to also provide device specific custom code for specific usage. This additional feature surely gives more customization capability.
[0017] Thus, the invention provides a simple, one click solution to convert EDD or FDI packages to FDT DTM. This invention allows to use FDI Device Package or EDDL as the source base to maintain the field instrument and generate the FDT/DTM based on the FDI Device Package or EDDL.
Brief description of the drawings:
[0018] The foregoing and other features of embodiments will become more apparent from the following detailed description of embodiments when read in conjunction with the accompanying drawings. In the drawings, like reference numerals refer to like elements.
[0019] FIG 1 illustrates one click solution for generating Device Type Managers (DTM) from Electronic Device Descriptions (EDD) and Field Device Integration (FDI) Device Packages.
[0020] FIG 2 illustrates generation of Device Type Managers (DTM) with the support of Electronic Device Description (EDD)/ Field Device Integration (FDI) devise package.
Detailed description of the invention:
[0021] In the following detailed description, a reference is made to the accompanying drawings those form a part hereof, and in which the specific embodiments that may be used are shown by way of illustration. These embodiments are described in sufficient detail to enable those skilled in the art to practice the embodiments and it is to be understood that the logical, mechanical and other changes may be made without departing from the scope of the embodiments. The following detailed description is, therefore, not to be taken in a limiting sense.
[0022] Fig 1 illustrates one click solution for generating device Device Type Managers (DTM) from Electronic Device Descriptions (EDD) and FDI Device Packages. It generates DTM which are of FDT 1.2 and /or FDT 2.0 standards. This in turn helps configuration, commissioning, diagnostics and maintenance with direct access to all field devices from a central workplace.
[0023] Here, the device may use integration software description in Electronic Device Description language (EDDL). This solution helps in generating DTM from EDDL. The user will input (101) the EDDL and FDI Device packages in the tool. DTM generator (102) computes the conversion. Output (103) will be in the form of FDT 1.2/ FDT 2. The generated Device Type Managers (DTM) are of specific Field Device Tool (FDT) standards.
[0024] In another embodiment of the present invention, the tool at first will ask whether FDT 1.2/ FDT 2, which FDT is required for usage. After selection the user will provide the EDDL or FDI package for conversion. Many details like “manufacture logo”, “device logo”, etc., will be asked for computation.
[0025] Here, after manual input of the EDD or FDI device package, the tool checks whether the EDD or FDI device package is valid or not. After its validation check the DTM configuration is generated. At the end after algorithm functioning the DTM is generated along with the installation package.
[0026] The single click solution tool uses algorithm for conversion of DTM from Device Descriptions (EDD) and FDI Device Packages. This in an internal algorithm developed for this specific usage.
[0027] FIG 2 illustrates generation of DTM with the support of Electronic Device Description (EDD)/FDI devise package. Here, FDI device package/EDD (201) along with device specific custom code (202) will be asked by device DTM (203). This uses communication DTM (204) in FDT host framework (205) to communicate with field devices (206). This, FDT is used in turn for configuration, commissioning, diagnostics and maintenance of all the field devices.
[0028] In another embodiment of the present invention, the invention allows device vendor to implement device specific code, complex business logic and complex features of the device using custom interface. With the help of .NET, WPF and etc custom logic will be implemented. The customization interface may be used in any number of ways and It removes the limitations present in the Electronic Device Description (EDD).
[0029] This mechanism of conversion helps the device vendor to provide the end user with smooth supply of devices whereby all the three standards can be integrated together without any separation. This helps both the end user and device vendors.
| # | Name | Date |
|---|---|---|
| 1 | 201841034854-STATEMENT OF UNDERTAKING (FORM 3) [15-09-2018(online)].pdf | 2018-09-15 |
| 2 | 201841034854-PROOF OF RIGHT [15-09-2018(online)].pdf | 2018-09-15 |
| 3 | 201841034854-POWER OF AUTHORITY [15-09-2018(online)].pdf | 2018-09-15 |
| 4 | 201841034854-FORM 1 [15-09-2018(online)].pdf | 2018-09-15 |
| 5 | 201841034854-DRAWINGS [15-09-2018(online)].pdf | 2018-09-15 |
| 6 | 201841034854-DECLARATION OF INVENTORSHIP (FORM 5) [15-09-2018(online)].pdf | 2018-09-15 |
| 7 | 201841034854-COMPLETE SPECIFICATION [15-09-2018(online)].pdf | 2018-09-15 |
| 8 | abstract 201841034854.jpg | 2018-09-17 |
| 9 | Correspondence by Agent_Submission Of Document_24-09-2018.pdf | 2018-09-24 |
| 9 | 201841034854-ABSTRACT [27-07-2021(online)].pdf | 2021-07-27 |
| 10 | 201841034854-FORM 18 [26-03-2019(online)].pdf | 2019-03-26 |
| 11 | 201841034854-Request Letter-Correspondence [28-05-2020(online)].pdf | 2020-05-28 |
| 12 | 201841034854-Power of Attorney [28-05-2020(online)].pdf | 2020-05-28 |
| 13 | 201841034854-Form 1 (Submitted on date of filing) [28-05-2020(online)].pdf | 2020-05-28 |
| 14 | 201841034854-Request Letter-Correspondence [16-06-2020(online)].pdf | 2020-06-16 |
| 15 | 201841034854-Power of Attorney [16-06-2020(online)].pdf | 2020-06-16 |
| 16 | 201841034854-Form 1 (Submitted on date of filing) [16-06-2020(online)].pdf | 2020-06-16 |
| 17 | 201841034854-OTHERS [27-07-2021(online)].pdf | 2021-07-27 |
| 18 | 201841034854-FER_SER_REPLY [27-07-2021(online)].pdf | 2021-07-27 |
| 19 | 201841034854-COMPLETE SPECIFICATION [27-07-2021(online)].pdf | 2021-07-27 |
| 20 | 201841034854-CLAIMS [27-07-2021(online)].pdf | 2021-07-27 |
| 21 | 201841034854-ABSTRACT [27-07-2021(online)].pdf | 2021-07-27 |
| 22 | 201841034854-FER.pdf | 2021-10-17 |
| 23 | 201841034854-US(14)-HearingNotice-(HearingDate-08-09-2023).pdf | 2023-08-07 |
| 24 | 201841034854-Correspondence to notify the Controller [05-09-2023(online)].pdf | 2023-09-05 |
| 25 | 201841034854-FORM-26 [06-09-2023(online)].pdf | 2023-09-06 |
| 26 | 201841034854-Response to office action [23-09-2023(online)].pdf | 2023-09-23 |
| 27 | 201841034854-Annexure [23-09-2023(online)].pdf | 2023-09-23 |
| 27 | 201841034854-POWER OF AUTHORITY [15-09-2018(online)].pdf | 2018-09-15 |
| 28 | 201841034854-PROOF OF RIGHT [15-09-2018(online)].pdf | 2018-09-15 |
| 28 | 201841034854-RELEVANT DOCUMENTS [27-09-2023(online)].pdf | 2023-09-27 |
| 29 | 201841034854-PETITION UNDER RULE 137 [27-09-2023(online)].pdf | 2023-09-27 |
| 29 | 201841034854-STATEMENT OF UNDERTAKING (FORM 3) [15-09-2018(online)].pdf | 2018-09-15 |
| 1 | searchstrategyE_20-01-2021.pdf |