Home / Companies / Tiger Data / Blog / February 2021

February 2021 Summaries

3 posts from Tiger Data

Filter
Month: Year:
Post Summaries Back to Blog
Everactive is a company that combines battery-free, self-powered sensors with powerful cloud analytics to provide "end-to-end" Industrial IoT solutions (IIoT) to its customers. Their low-power semiconductor and networking technology allows for continuous streaming of asset health data from devices operating indefinitely from harvested energy sources. The company's initial products monitor steam systems in various industries and applications, serving large manufacturers in sectors such as Food & Beverage, Consumer Packaged Goods, Chemical Process Industries, Pharmaceuticals, Pulp & Paper, and Facilities Management. Everactive's sensors are batteryless, allowing for cost-prohibitive monitoring of factory devices previously difficult to equip with sensors. The company uses TimescaleDB, a PostgreSQL extension, to store and manage its data stack, leveraging schema-as-code tools and internal/external schema separation. After switching from OpenTSDB, Everactive has seen significant performance improvements and reduced downtime. The team plans to continue innovating on their technology platform, expanding product offerings such as wireless range, power requirements, and sensor integration, while developing a localization feature to identify asset deployment locations.
Feb 26, 2021 1,869 words in the original blog post.
This installment of the "Community Member Spotlight" series highlights Nathan McMinn, CTO and co-founder at Conserv, a company that helps collections care professionals around the world understand their collections' environments, make decisions to optimize conditions, and better protect historical artifacts. Think about your favorite museum - all objects housed within exist to tell stories of the past and help us understand more about systems. Without proper care, which starts with correct environment, those artifacts are doomed to deteriorate and will eventually be lost forever. Conserv started in early 2019 with a mission to bring better preventive care to the world's collections, serving anyone charged with long-term preservation of physical objects. They've built a platform to help collections gather data required to understand and predict long-term risks, get insights into their data, and plan for how to mitigate and improve preservation environments. Conserv uses TimescaleDB to store IoT sensor readings and related metrics, providing actionable insights to customers and offering in-depth analysis and predictions. The company's solution consists of fleets of LoRaWAN sensors taking detailed environmental readings on a schedule, as well as event-driven data. Their UI makes it simple to add human observations to any data point, collection, or date. With TimescaleDB, Conserv can provide actionable insights and in-depth analysis, helping customers develop plans to care for objects in the short, mid, and long-term. The company's small team of 6 members plays a key role in their business, with each member making a big impact.
Feb 10, 2021 1,655 words in the original blog post.
We're sharing plans for Timescale Analytics, a new project that aims to identify, create, and combine all the capabilities SQL needs to perform time-series analytics into a single Postgres extension. This will enable developers to make SQL even better for time-series analysis. We've also released TimescaleDB 2.0, which includes user-defined actions, allowing users to refine existing policies and write custom automated procedures and functions to suit their needs. Additionally, we've created a quickstart guide for Go developers to get up and running with TimescaleDB, and shared resources on real-time aggregation, continuous aggregates, and how to build your own monitoring and alerting solution using Grafana and TimescaleDB. Our community has grown to 10K GitHub stars, and we're celebrating this milestone by sharing our favorite resources and tips for using TimescaleDB effectively.
Feb 01, 2021 1,271 words in the original blog post.