Procedure to operate a field device (F1, F2, F3, ..., Fn) used in an automation engineering installation (A) wherein said field device has a communication connection with a field access unit (FE), particularly with a computing unit, a gateway or an edge device, by means of a first wired or wireless communication network (KN1), particularly by means of a fieldbus used in automation engineering, wherein said procedure comprises the following step: - Calling up of a link (URL1, URL2, URL3, ... URLn) of the field device (F1, F2, F3, ..., Fn) on a client computer (CR), wherein the link (URL1, URL2, URL3, ... URLn) consists at least of a protocol field and a parameter field, wherein the calling up of the link (URL1, URL2, URL3, ... URLn) causes the following steps: a) Starting of a first framework application (FR1) assigned to the protocol field of the link (URL1, URL2, URL3, ... URLn) on the client computer (CR), particularly an FDT framework application, an FDI host, a DD host or an EDD host; b) Transmission of the link (URL1, URL2, URL3, ... URLn) to the first framework application (FR1) and extraction, by the first framework application (FR1), of at least one item of information contained in the parameter field; c) Configuration of a communication path (KP) between the client computer (CR) and the field device (F1, F2, F3, ..., Fn) via the field access unit (FE) using said at least one item of information; d) Opening of a device driver (GT) assigned to the field device (F1, F2, F3, ..., Fn) or a device description assigned to the field device (F1, F2, F3, ..., Fn) in the first framework application (FR1). - Calling up of a link (URL1, URL2, URL3, ... URLn) of the field device (F1, F2, F3, ..., Fn) on a client computer (CR), wherein the link (URL1, URL2, URL3, ... URLn) consists at least of a protocol field and a parameter field, wherein the calling up of the link (URL1, URL2, URL3, ... URLn) causes the following steps: a) Starting of a first framework application (FR1) assigned to the protocol field of the link (URL1, URL2, URL3, ... URLn) on the client computer (CR), particularly an FDT framework application, an FDI host, a DD host or an EDD host; b) Transmission of the link (URL1, URL2, URL3, ... URLn) to the first framework application (FR1) and extraction, by the first framework application (FR1), of at least one item of information contained in the parameter field; c) Configuration of a communication path (KP) between the client computer (CR) and the field device (F1, F2, F3, ..., Fn) via the field access unit (FE) using said at least one item of information; d) Opening of a device driver (GT) assigned to the field device (F1, F2, F3, ..., Fn) or a device description assigned to the field device (F1, F2, F3, ..., Fn) in the first framework application (FR1). a) Starting of a first framework application (FR1) assigned to the protocol field of the link (URL1, URL2, URL3, ... URLn) on the client computer (CR), particularly an FDT framework application, an FDI host, a DD host or an EDD host; b) Transmission of the link (URL1, URL2, URL3, ... URLn) to the first framework application (FR1) and extraction, by the first framework application (FR1), of at least one item of information contained in the parameter field; c) Configuration of a communication path (KP) between the client computer (CR) and the field device (F1, F2, F3, ..., Fn) via the field access unit (FE) using said at least one item of information; d) Opening of a device driver (GT) assigned to the field device (F1, F2, F3, ..., Fn) or a device description assigned to the field device (F1, F2, F3, ..., Fn) in the first framework application (FR1). <EOS>