How lifecycle works

• In-service date: a manual override if set, otherwise the ITFlow purchase date, then the vendor ship date, then the warranty start, then the ITFlow install date, and finally the first time NinjaOne saw the device (shown as an estimate).
• End of life: in-service date plus the lifespan policy for that device type (Settings → Planning & lifecycle), or the device's own override.
• Warranty: a manual override if set, otherwise the Dell/Lenovo lookup, then the ITFlow warranty date.
• OS support: matched by OS name and build number against Settings → OS support dates. Add a row when Microsoft ships a new release.
• Forecast: replacement cost (policy default or override), grouped by the quarter each device reaches end of life, or the quarter set under Replace in. Overdue devices count in the current quarter.

Virtual machines are tracked for OS support only. Devices can be excluded (spares, lab gear, client-owned).