It's often necessary to perform a similar operation with thousands of your devices, regardless of whether they are online and functioning properly at the moment.
AggreGate was always offering a capability of delayed configuration changes: you can configure a thousand devices and your configuration changes will be delivered on "best effort" basis. But what if you need to execute an operation, e.g. perform a firmware upgrade? Continue reading Delayed Batch Operations
Coming AggreGate 5.3 will feature a long-waited Workflows module. Workflows are user-defined actions that combine server-side data processing operations and operator interaction steps (UI Procedures). The workflows module helps to define those actions by adding various steps that may depend to each other and benefit from conditional branching.
Workflows are ideal for configuring various incident resolution and debriefing patterns that will be interactively launched upon various alerts. Thus, workflows will be crucial for any AggreGate-based umbrella monitoring and management project, be it IT, automation or security infrastructure management.
As you probably know, AggreGate is typically used by VARs, SIs and OEMs for building reference solutions or even full-fledged derived products. Technically, each derived OEM solution is a set of plugins for:
Acquiring data from devices and data sources
Storing data on the server
Processing data in headless mode
Visualizing data via custom AggreGate-based operator UIs
Exposing data to third-party applications.
Many simple solutions only include server-side processing templates and parts of operator UI, such as widgets, maps, reports and dashboards. Such solutions acquire data via standard protocols and keep it in default storages, such as relational, NoSQL and RRDB databases.
We've recently posted a short article that describes how to package your custom processing and visualization tools into an AggreGate plugin. The article requires basic understanding of AggreGate Plugin SDK. Please check it here.
Now a PDU monitoring is available in AggreGate out-of-the-box right after the server installation. AggreGate collects common PDU information, like model, firmware version, series number, etc. Besides, the system is able to monitor more important PDU parameters, such as current force, voltage, active and total power.
Try out all AggreGate features by downloading our free trial version here.
We've added manual tags support to our OPC device driver. This feature is a rescue in case of legacy OPC servers that do not support items browsing. Simply add desired item IDs to the 'Manual Items' device property and these items will be directly requested from the device upon each synchronization. Manual tags will be available at the device configuration, next to auto-discovered tags if any.
The full list of available device drivers is available in Protocols/Drivers section on our website.
Tibbo has released a new 5.2 version of AggreGate IoT Integration Platform.
Being the first major release in 2015, AggreGate 5.2 delivers Big Data support, unified search capabilities, Business Intelligence (BI) engine, C/C++ Agent SDK and other valuable core features, as well as improvements of all vertical market extension packs including Network Manager and SCADA/HMI.
New AggreGate got a unified search window that digs data across the whole system and instantly provides results based on a pre-indexed database. Besides that version 5.2 brings a whole new level of intelligence to the Platform by introducing two new core modules: Mass object management and Object dashboards. AggreGate platform keeps up with the mainstream and now allows NoSQL databases to be used as configuration and event storage. Apache Cassandra and BerkleyDB Java Edition being used together ensure extremely fast persistent configuration updates and very high history/event storage rates.
Among other major improvements are: steady state mode suitable for kiosks and dedicated operator PCs, new video streaming protocols, network topology map layout persistence, new device drivers (Local Agent, Local System and Omron FINS), improved topology discovery via CDP/LLDP and more.
Do you know that some devices are designed specially for AggreGate? One of them is a simple and easy-to-use TR610 Tibbo Time Recorder. It utilizes RFID technology to allow quick employee registration on entrance/exit gates.
The TR610 was developed to dovetail with AggreGate Time and Attendance for providing optimal administration and reporting facilities.
The TR610 can enroll itself automatically with AggreGate Server and begin streaming attendance data in near-real-time over the network. While the terminal can be configured via AggreGate, its web connectivity and on-screen menu work even when it’s enrolled with AggreGate.
Combination of time recorders with open-source firmware and attendance control software based on an enterprise device management platform provided a lot of benefits. What are they? Read more about it on http://programmableterminal.com/
Despite AggreGate Agent and even full-blown AggreGate Server can run on single-board PCs like Raspberry Pi and BeagleBone Black, up to now that wasn't possible to launch Agent in low-cost devices like Arduino.
This has changed with the publication of open-source AggreGate C/C++ SDK. The SDK helps to build Agent library into the C/C++ code of main device application to make it natively compatible with AggreGate. It also includes API for interfacing the server in a "client mode", allowing full server control from within any C/C++ application.