Quickstart: Explore the Azure Time Series Insights Gen2 demo environment


The Time Series Insights service will be retired on 7 July 2024. Consider migrating existing environments to alternative solutions as soon as possible. For more information on the deprecation and migration, visit our documentation.

This quickstart gets you started with an Azure Time Series Insights Gen2 environment. In the free demo, you tour key features that have been added to Azure Time Series Insights Gen2.

The Azure Time Series Insights Gen2 demo environment contains a scenario company, Contoso, that operates two wind turbine farms. Each farm has 10 turbines. Each turbine has 20 sensors that report data every minute to Azure IoT Hub. The sensors gather information about weather conditions, blade pitch, and yaw position. Information about generator performance, gearbox behavior, and safety monitors also is recorded.

In this quickstart, you learn how to use Azure Time Series Insights Gen2 to find actionable insights in Contoso data. You also conduct a short root cause analysis to better predict critical failures and to perform maintenance.


Create a free Azure account if you don't have one.

Explore the Azure Time Series Insights Gen2 Explorer in a demo environment

The Azure Time Series Insights Gen2 Explorer demonstrates historical data and root cause analysis. To get started:

  1. Go to the Contoso Wind Farm demo environment.

  2. If you're prompted, sign in to the Azure Time Series Insights Gen2 Explorer by using your Azure account credentials.

Work with historical data

  1. Select Contoso WindFarm Hierarchy.

    Contoso WindFarm Hierarchy

  2. In Contoso Plant 1, look at wind turbine W7.

    W7 in Contoso Plant 1

    1. Change the view range to 1/1/17 20:00:00.00 to 3/10/17 20:00:00.00 (UTC).

      Range view

      Range view setting

    2. Adjust the range view using the zoom in (+) and out (-) and moving the slide bar.

      Adjust range view

    3. To select a sensor, select Contoso Plant 1 > W7 > Generator System > GeneratorSpeed. Then, review the values that are shown.

      Generator speed

  3. Recently, Contoso found a fire in wind turbine W7. Opinions vary about what caused the fire. In Azure Time Series Insights Gen2, the fire alert sensor that was activated during the fire is displayed.

    1. Change the view range to 3/9/17 20:00:00.00 to 3/10/17 20:00:00.00 (UTC).

    2. Select Safety System > FireAlert.

      Contoso found a fire in wind turbine W7

  4. Review other events around the time of the fire to understand what occurred. Oil pressure and active warnings spiked just before the fire.

    1. Select Pitch System > HydraulicOilPressure.

    2. Select Pitch System > ActiveWarning.

      Review other events around the same time

  5. The oil pressure and active warning sensors spiked right before the fire. Expand the displayed time series to review other signs that were evident leading up to the fire. Both sensors fluctuated consistently over time. The fluctuations indicate a persistent and worrisome pattern.

    • Change the view range to 2/24/17 20:00:00.00 to 3/10/17 20:00:00.00 (UTC).

      Oil pressure and active warning sensors also spiked

  6. Examining two years of historical data reveals another fire event that had the same sensor fluctuations.

    • Change the view range to 1/1/16 to 12/31/17 (all data).

      Look for historical patterns

By using Azure Time Series Insights Gen2 and sensor telemetry, we've discovered a long-term trend hidden in the historical data. With these new insights, we can:

  • Explain what actually occurred.
  • Correct the problem.
  • Put better alert notification systems in place.

Root cause analysis

  1. Some scenarios require sophisticated analysis to uncover clues in data. Select the windmill W6 on date 6/25.

    1. Change the view range to 6/1/17 20:00:00.00 to 7/1/17 20:00:00.00 (UTC).

    2. Select Contoso Plant 1 > W6 > Safety System > VoltageActuatorSwitchWarning.

      Change the view range and select W6

  2. The warning indicates an issue with the voltage from the generator. The overall power output of the generator is within normal parameters in the current interval. By increasing our interval, another pattern emerges. A drop-off is evident.

    1. Remove the VoltageActuatorSwitchWarning sensor.

    2. Select Generator System > ActivePower.

    3. Change the interval to 3d.

      Change the interval to 3d

  3. By expanding the time range, we can determine whether the issue has stopped or whether it continues.

    • Extend the time span to 60 days.

      Extend the time span to 60 days

  4. Other sensor data points can be added to provide greater context. The more sensors we view, the fuller our understanding of the problem is. Let's drop a marker to display the actual values.

    1. Select Generator System, and then select three sensors: GridVoltagePhase1, GridVoltagePhase2, and GridVoltagePhase3.

    2. Drop a marker on the last data point in the visible area.

      Drop a marker

    Two of the voltage sensors are operating comparably and within normal parameters. It looks like the GridVoltagePhase3 sensor is the culprit.

  5. With highly contextual data added, the phase 3 drop-off appears even more to be the problem. Now, we have a good lead on the cause of the warning. We're ready to refer the issue to our maintenance team.

    • Change the display to overlay all Generator System sensors on the same chart scale.

      Change the display to include everything

Next steps

You're ready to create your own Azure Time Series Insights Gen2 environment. To start:

Learn to use the demo and its features: