Skip to content

Views -- Focused Perspectives for Every Team

Learning Goals

By the end of this section, you will be able to:

  • Understand what a View is and how it differs from a Dashboard
  • Create, save, and share Views in Osprey
  • Use labels, use cases, and workflows as filters within Views
  • Recognize how Views drive alignment across roles such as PI Administrators, Engineers, and Environmental teams

Overview

Dashboards provide everyone with a shared overview of the system. But sometimes, teams need focus -- not noise.

Views in Osprey are personal or team-specific windows into the subset of data that matters most. They help you cut through system-wide complexity and zero in on your area of responsibility -- whether that's emissions monitoring, reliability, or PI System health.

What Is a View?

A View is a saved, live filter -- a custom slice of Osprey that updates automatically as new data and issues come in. You can think of a View as a dynamic query that answers a recurring question, such as:

  • "Which mission-critical tags are currently failing checks?"
  • "Are there any data quality issues impacting the data science team?"
  • "Which PI Data Archives are running low on disk space?"

Once you create a View, you never have to rebuild it. It refreshes automatically with live data, providing an always-current snapshot of the conditions you care about most.

Views can be private for personal monitoring or shared across your domain to keep teams aligned.

When to Use Views vs. Dashboards

It's important to understand the difference between Dashboards and Views:

Dashboards monitor overall system health.

Views focus on what's relevant to you or your team.

Dashboards answer, "What's happening across the organization?" Views answer, "What's relevant to me right now?"

Examples:

  • A PI Administrator might create a View to track stale tags and identify where to focus cleanup efforts
  • An Environmental Engineer might have a View showing emissions-monitoring tags with active issues
  • A Reliability Lead might track mission-critical tags with open issues

This separation ensures that everyone is looking at the same data but through the lens of their specific role and responsibilities.

Creating and Managing Views

Creating a View in Osprey is quick and intuitive:

  1. From the Issues or Assets page, perform a search
  2. Apply filters that matter to you -- for example, label = Mission-Critical or use case = OEE
  3. Once the filtered results appear, click Save as View
  4. Choose whether the View is Private (visible only to you) or Shared (visible to others in your domain)
  5. Give it a name and description, then click Save

Your View now appears in the Views list on the sidebar and updates automatically as data evolves.

When shared, Views create alignment -- everyone sees the same, real-time picture, reducing confusion and improving coordination.

Your Turn

  1. Go to the Issues tab and filter for Mission-Critical assets with active data issues
  2. Save this as a new View named "Mission-Critical Health"
  3. Set visibility to Shared so your team can access it

Knowledge Check

Question 1

What is a View in Osprey?

A. A static dashboard snapshot
B. A saved, dynamic filter showing a subset of data based on conditions. You can set alerts to notify you of new issues or assets
C. A notification channel
D. A data lineage report

Question 2

When should you create a View instead of using a dashboard?

A. When you need a focused perspective
B. When you need to configure new scanners
C. When dashboards are disabled
D. When editing AF templates

Question 3

Which of the following can be used as filters when creating a View?

A. Labels, use cases, and status
B. User logins

Question 4

How often do Views update?

A. They must be manually refreshed each week
B. They update automatically as data changes
C. Only when you restart Osprey
D. Once per month