An access profile includes configuration characteristics that are defined using device and operating system agnostic attributes. Thus, the access profiles are not necessarily dependent or otherwise tied to any particular vendor or network OS. When a system administrator configures one or more service access points, the system administrator need only specify the vendor and network OS agnostic characteristics that are to be associated with the service access point. A configuration generator can generate vendor specific and/or network specific configuration commands and data from the vendor and network OS agnostic access profile attributes. The generated configuration commands and data can be provided to a network device hosting the service access point using a vendor specific and/or network OS specific configuration application program interface.

A monitoring, control and configuration system that includes a local system, a mobile device application, and a server that is accessible by users via the mobile device application and a Software as a Service (SaaS) interface via a browser is disclosed. The local system contains a microprocessor, communications components and related software all of which enable communications with the server and external components coupled with the local system. The local system software and server software combine with the mobile application and website interface to enable a user to monitor, configure, and control external devices coupled with the local system and the local system itself via the server. The system replaces multiple disparate control devices with a single, configurable device and system. The system integrates multiple disparate devices and systems from multiple manufacturers. The system provides emergency alerts based on examination of information from external devices provided to the local system and the server.

The invention relates to a device for controlling and/or configuring construction machines, whose electronic control device can be reconfigured and/or extended by installing a program packet, comprising a central server for providing and/or downloading different program packets, wherein the central server has access to an internal machine data database in which different machine data sets are stored, wherein the central server is designed as an open server platform with different interfaces to different external host servers, wherein a communications module activates an interface to an external machine data database and/or to an external host server according to a construction machine and/or program packet request and according to the machine data sets in the internal machine data database, and wherein the external machine data database that is separate from the central server is designed to provide a program packet of an external host server according to an authorization of the external host server.

A set of network requirements is received. At least a portion of the set of network requirements is stored on a system data store. Device requirements for a plurality of network devices are stored on the system data store. At least a portion of the stored device requirements is received at a proxy agent. Native hardware instructions are generated based on the received device requirements to configure at least one of the plurality of network devices.

Systems and methods provide a unified collection service for a network. A first network device receives a data reporting message from a data reporting device. The data reporting message includes a first format for a particular data reporting device. The first network device adds routing data to the data reporting message to create an encapsulated data reporting message and forwards the encapsulated data reporting message to a second network device. The second network device transforms the encapsulated data reporting message into a second format that includes a unified message format and forwards, based on the routing data, the unified data reporting message.

A method for managing a network device that includes a network operating system (NOS) and a third-party network operating system (3PNOS) includes detecting a 3PNOS state change in a 3PNOS database managed by the 3PNOS, translating the 3PNOS state change into a network device state change, storing the network device state change in a state database managed by the NOS, in response to the storing: detecting a change in the state database by a NOS agent executing in the NOS, initiating, in response to detecting the change in the state database, an update to hardware on the network device by the NOS, wherein the 3PNOS does not directly manage the hardware.

A method for operating an Internet of Things (IoT) system includes obtaining, by a device registration tool, identification information of a first IoT module, obtaining, by the device registration tool, identification information of a device with the first IoT module mounted thereon, and registering, by the device registration tool, the identification information of the first IoT module and the identification information of the device in a database accessible by an IoT network.

A method for managing a network device that includes a network operating system (NOS) and a third-party network operating system (3PNOS) includes detecting a 3PNOS state change in a 3PNOS database managed by the 3PNOS, translating the 3PNOS state change into a network device state change, storing the network device state change in a state database managed by the NOS, in response to the storing: detecting a change in the state database by a NOS agent executing in the NOS, initiating, in response to detecting the change in the state database, an update to hardware on the network device by the NOS, wherein the 3PNOS does not directly manage the hardware.

Protocol detection circuits for detecting the field device protocol of a field device attached to a channel having a data line are sequentially connected to the data line by a controller that communicates to the field device through the protocol detection circuits. The protocol detection circuits are disconnected from the field device after protocol detection is completed. The channel may be one of a number of channels; the controller may also connect and disconnect the protocol detection circuits from the one channel whereby the protocol detection circuits can be used with any channel. After the protocol of the field device is identified a protocol adapter can be inserted into the channel to enable data conversion between the field device protocol and an another protocol used by the channel for data transmission.

Implementations are described herein for commissioning a distributed control node (DCN) to a process automation network. In various implementations, one or more messages transmitted on the process automation network by the DCN announcing that the DCN has joined the process automation network may be detected. Based on the one or more messages, one or more operational technology (OT) capabilities of the DCN may be determined. Based on the one or more OT capabilities, the DCN may be commissioned to the process automation network, e.g., by configuring the DCN to cooperate with one or more other process automation nodes on the process automation network to implement an at least partially automated process.