<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/89e33c2836d0420d87c5d78056653800&quot; frameborder=&quot;0&quot; width=&quot;1664&quot; height=&quot;1248&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1248</height><width>1664</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1248</thumbnail_height><thumbnail_width>1664</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/89e33c2836d0420d87c5d78056653800-00001.gif</thumbnail_url><duration>418.8666666666676</duration><title>How to Define and View Downtime in OnTakt</title><description>In this video, I will provide an overview of how we code downtime and demonstrate how to pull downtime information after it has been created. I will show you examples of downtime incidents, explain the context behind them, and discuss the associated costs. Additionally, I will showcase how we track downtime historically and use a downtime calculator to determine the return on investment for implementing solutions. Please watch the video to gain a better understanding of our downtime coding process and its significance.</description></oembed>