# Equipment scedule **URL:** \ **Category:** General Discussion\ **Tags:** perspective\ **Created:** [July 22, 2025, 6:50am UTC](https://forum.inductiveautomation.com/t/equipment-scedule/108753 "2025-07-22T06:50:45Z")\ **Posts on this page:** 1\ **Showing post:** 2
**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 24, 2025, 12:18am UTC](https://forum.inductiveautomation.com/t/equipment-scedule/108753/2 "2025-07-24T00:18:40Z")
I recently explained the basics of using the Perspective Equipment Schedule in this post: > [@Equipment Schedule Example](https://forum.inductiveautomation.com/t/equipment-schedule-example/108314/2): > > 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 understandi… Monthly OEE to me indicates you have some data already that can be used to define the availability of the devices and are interested in having it tracked in the component. I think it's worth noting there is no _correct_ way to use the component for OEE. The dashboard would likely include more than this component. The minimum properties you use in the component are **items** and **scheduledEvents**. So to use the component you would need to have ranges of time stored in the database that represent either up-time, or specific events that you are expecting related to the production process or devices. For OEE specifically, you'd likely take advantage of the **downtimeEvents** property to signify any time the device should have been running but wasn't. You could potentially represent performance using the **percentDone** , where a completed bar at the bottom of the up-time or event translates to 100% performance. I am not sure how one would visualize quality especially if there is a time lag between the process and quality information being returned. You could potentially use the **leadTime** as a static color indicator rather than it's original purpose, and change between good and bad colors to represent general quality during events. If anyone in general wants to learn more about OEE check out our beginner video! > **[What Is OEE?](https://inductiveautomation.com/resources/video/what-is-oee)** > > How efficient is your organization with its manufacturing time? How do you know? Overall Equipment Effectiveness, or OEE, is the industry-standard metric that considers three ratios — availability, performance, and quality — to determine how... --- _[View the full topic](https://forum.inductiveautomation.com/t/equipment-scedule/108753)._