# Equipment Schedule Example

**URL:** <https://forum.inductiveautomation.com/t/equipment-schedule-example/108314>\
**Category:** Ignition\
**Tags:** perspective, ignition81\
**Created:** [July 10, 2025, 11:02am UTC](https://forum.inductiveautomation.com/t/equipment-schedule-example/108314 "2025-07-10T11:02:58Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![kvane](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kvane/32/22228_2.png) [@kvane](https://forum.inductiveautomation.com/u/kvane)\
**Post date:** [July 15, 2025, 12:11am UTC](https://forum.inductiveautomation.com/t/equipment-schedule-example/108314/2 "2025-07-15T00:11:09Z")

</div>

Reviewing the Vision Equipment Schedule is actually not a bad idea to help understand the Perspective component. Due to how Vision properties are stored in datasets, it is potentially easier to review the User Manual page for the Vision datasets that mirror the available features in the Perspective component - [Vision - Equipment Schedule | Ignition User Manual](https://www.docs.inductiveautomation.com/docs/8.1/appendix/components/vision-components/charts/equipment-schedule)

These tables may be easier to review, and the Vision component comes with example data.

Going back to [Perspective](https://www.docs.inductiveautomation.com/docs/8.1/appendix/components/perspective-components/perspective-display-palette/perspective-equipment-schedule#properties), with the understanding of the various sections (item, scheduled event, downtime overlay, break overlay), it may be easier to see the different features in use:

- items = Devices
- scheduledEvents = Events
- leadTime = In seconds, the amount of leadStyle to display at the **start** of the task. _In my case it is yellow._ Lead time for these events could technically be used for any purpose, you could use it to signify the amount of time needed to prep the device before the main task (pre-task planning).
- percentDone = 0-100 how far the progress bar should be across the main task. _Set to 50% in my case._
- downtimeEvents = An overlay for additional context, usually used to track when a machine is not running correctly during an event, or to signify when a machine is expected to be down. Once again it is subjective how you use it. _In my case I moved my red downtime overlay behind my event._
- breakEvents = An overlay for additional context, usually used to track expected breaks. _In my case I left my green break overlay as default._

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/0/c/0c9cc98fcdea932a3a1e95ce43e5f87492c062ce.png)

---

_[View the full topic](https://forum.inductiveautomation.com/t/equipment-schedule-example/108314)._