<?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/44a7b7033dda4ede9092e5bd8333bf0f&quot; frameborder=&quot;0&quot; width=&quot;1920&quot; height=&quot;1440&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1440</height><width>1920</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1440</thumbnail_height><thumbnail_width>1920</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/44a7b7033dda4ede9092e5bd8333bf0f-e61c2d77af7a5c3f.gif</thumbnail_url><duration>101.133333</duration><title>Your Clients&apos; Technology</title><description>This Loom explains how device budgeting works in the technology module, including how class and end-of-life rules drive each device’s budget forecast. Each device has a class whose lifespan and replacement costs set its budget month and year, and changing the class updates the numbers. Users can enter custom budget values, which switches the device to custom and flags non-class values in amber; they can also type a custom month or year while keeping the class, with clearing restoring the class’s original dates. When a replacement becomes real, the user creates or links an initiative in the device’s initiative field so it counts in the budget without double counting, and the budget parts show sources based on part settings.</description></oembed>