# Ideas and best practices for real-time QC/status of devices, tags, historization, etc

**URL:** <https://forum.inductiveautomation.com/t/ideas-and-best-practices-for-real-time-qc-status-of-devices-tags-historization-etc/93929>\
**Category:** Ignition\
**Tags:** ignition81, perspective\
**Created:** [July 30, 2024, 5:47pm UTC](https://forum.inductiveautomation.com/t/ideas-and-best-practices-for-real-time-qc-status-of-devices-tags-historization-etc/93929 "2024-07-30T17:47:36Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![msteele](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/msteele/32/77889_2.png) [@msteele](https://forum.inductiveautomation.com/u/msteele)\
**Post date:** [July 30, 2024, 5:47pm UTC](https://forum.inductiveautomation.com/t/ideas-and-best-practices-for-real-time-qc-status-of-devices-tags-historization-etc/93929/1 "2024-07-30T17:47:36Z")

</div>

What ideas and best practices do people have to expose gateway, environment, network, device connectivity, tag status/quality, historization rates/status, etc within Perspective?

What other things would be worth exposing inside a Perspective project?  
Any creative alarm configs? Other ideas?

Context: We have an Ignition-based product in the renewables space which gets auto-deployed and builds/conforms itself to the data model created in the tag provider. The Ignition project stack is 100% identical from site to site regardless of client, configuration, etc. and I'm looking to streamline our QC checks for my implementation team. And I might as well leave these resources available and visible to the client for ongoing visibility into site/environment status.

---

<div class="post-metadata">

**Author:** ![YF129701](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/yf129701/32/60498_2.png) [@YF129701](https://forum.inductiveautomation.com/u/YF129701)\
**Post date:** [July 30, 2024, 7:35pm UTC](https://forum.inductiveautomation.com/t/ideas-and-best-practices-for-real-time-qc-status-of-devices-tags-historization-etc/93929/2 "2024-07-30T19:35:17Z")

</div>

The first thing I thought of is Users - both number and possibly client type, username, sessionStartTimestamp, client time zone, etc. Possibly have two widgets for users (if applicable) - Perspective and Vision.