Likelihood to Recommend Paired with Citect SCADA or System Platform, this is an excellent process historian. It also works well collecting OPC data. For basic data storage, retrieval, and analysis, this is well suited. This is not well suited for very large deployments. Multiple instances would need to be used to scale up, and the data fed into a second-tier/enterprise historian for corporate user consumption.
Read full review kdb is well suited for real time tick data and time series analytics.
Read full review Pros Data storage--multiple data sources stream data in real time; it is stored without issue Data retrieval--small to moderate queries and trends are generally fast and efficient Cost effectiveness--it is one of the cheaper (non-enterprise) historian offers and therefore is good value for money (with a reduced feature set) Read full review Time series analysis. The built-in vector operations are extremely fast. Also with the q language you can code up any customized analytical ideas quickly. The database are all file based, very easy to maintain. Very solid and fast interface to websocket, so you can interface with javascript easily. Read full review Cons Query performance--for very long-term/large queries; the latest version which we are yet to commission has some improvements in this area User interface--the trend, query, and Excel add-ins are basic and could do with a refresh; web-based clients are a paid add-on and less full featured, so not a true replacement Connectivity--Wonderware System Platform driver packs are required for additional data source types, where native connectors are not provided by other products Read full review Run time error message readability, particularly for new users. Backwards compatibility between versions. Read full review Likelihood to Renew switching costs
Read full review Usability its ok
Read full review Support Rating We don't use it.
Read full review Alternatives Considered AVEVA Historian, formerly Wonderware, was the best of the process tier historians in terms of reliability and functionality. It is still under development and not a "dead" product. It is also more cost effective than the more full-featured enterprise historians, such as PI, which our organization is not yet ready for. The feature set is at the right cost level, coupled with current support, were the key factors in the decision.
Read full review Python is very commonly used for large data analysis and in general is much easier to pickup than kdb+. The biggest drawback of kdb+ is the learning curve.
Read full review Return on Investment Increased efficiency, reduction in labour for preparing reports--data is available to be queried and reported with less effort Increased production efficiency--near real-time data availability and comparisons to historical data has been used to make faster and better operational decisions Increased reliability--data has been used for maintenance optimization and planning purposes Read full review It perfectly solves most of our real time tick data needs. Finding good kdb resources is slightly difficult. Also new people trying to learn kdb experience a relatively longer learning curve. Read full review ScreenShots