FrameWorx is Tarigma’s data acquisition platform for collecting actionable data from Industrial Internet of Things (IIoT) sources across the enterprise, including a wide variety of sensors, actuators, programmable logic controllers (PLCs), and intelligent electronic devices (IEDs) that populate the operational landscape of those enterprises.
Figure 1 - FrameWorx Architecture
With reference to Figure 1 above, FrameWorx is comprised of a set of network-connected modules described below:
The FrameWorx Data Collector is a network end-node that operates in conjunction with a large and growing family of vendor-specific and device-specific protocols to collect data from Intelligent Electronic Devices (IEDs). It can bind to local host ethernet ports, serial ports or external Remote Terminal Units (RTUs) to access devices via TCP or RS232 using a variety of protocols including Modbus, IEC 60870-5, DNP3, IEC 60870-6-ICCP, IEC 61850, and the like. While some protocols support the receipt of unsolicited datagrams, most Collectors employ periodic polling of the device to determine when new events have occurred or new data is available. Since the Data Collector executes close to the device, the network traffic from high-frequency polling is localized and does not consume bandwidth over the wide-area network.
Once an event or transaction is detected, a time stamp and data packet is collected from the device, framed and buffered to local cache before it is queued for transport to the destination. This insures that each transaction will eventually reach its destination with the proper time context despite network delays or disruptions. A Configurator is available to setup each instance of the Collector, including settings for device addresses, protocol options, data subscriptions, and logging. Communication errors and state change messages are dispatched with priority. Tarigma is continuously adding to its library of over fifty (50) protocol drivers.Data Gateway
The FrameWorx Gateway is the component most involved in supporting the security policy of the enterprise. It is designed to be installed in the DMZ to relay traffic from the edge to the centralized end-node and to the cloud. The gateway may call upon a number of tools to implement security policy, including Secure Sockets Layer (SSL), tunneling and directionality. For example, the security policy may require the gateway to connect to all external nodes rather than allowing external nodes to connect to the gateway. Since this policy could require a single gateway to manage and instantiate hundreds or thousands of connections, FrameWorx developed the Data Concentrator (described below).
The FrameWorx Data Concentrator consolidates transactions from tens-to-hundreds of edge devices at a given substation or other regional facility and securely forwards them to the enterprise via the FrameWorx Gateway. This distributes the administrative burden of setting up and maintaining connections, greatly simplifying the implementation of a policy of directionality described above.Data Repository Service
The FrameWorx Data Repository Service is a centralized end-node where all of the data and metadata being collected at the edge is routed and stored. Much of the incoming data has been preprocessed at the source according to industry standard or proprietary file formats that some higher-level applications or use cases can handle directly and, for that reason, those files are persisted directly to a folder structure on the file system. Examples of this include Comtrade files for oscillography, IEC Event files, relay settings, and firmware signatures. The balance of the data is persisted in an open, normalized, SQL database with metatag indexing for retrieval and consumption by a variety of centralized and/or cloud-based applications and use cases.
NOTE: Unlike SCADA which is focused on acquiring operational data about the electrical energy being distributed via the grid, Tarigma is focused on acquiring non-operational data, or data about the health, condition and configuration of the fixed assets that comprise the grid itself. Non-operational data, such as relay settings, cycle time vs. switched load, number of cycles, firmware revision, etc., is in most cases only accessible from an IED using vendor-proprietary protocols. As a result, Tarigma has developed a family of Data Collectors (see below) that support those proprietary protocols which operate in combination with other Collectors to gather the total datasets that are critical to the success of condition-based preventative maintenance programs and other Asset Performance Management (APM) use cases.