[BE-52] Implement specialised report endpoints — warranty expiry, maintenance costs, and asset utilisation

[yusuftomilola]

Overview

Beyond the summary, asset managers need targeted reports to act on specific risks: warranties about to expire, high maintenance costs, and underutilised assets. These feed into the advanced reports page (FE-19) and can be exported as PDF/Excel (BE-53).

Context

• Depends on BE-51 (ReportsModule base), BE-26 (MaintenanceRecord), BE-41 (Depreciation), BE-30 (Checkouts)
• All report endpoints must support ?departmentId, ?categoryId, and date range (?from, ?to) filters

Acceptance Criteria

• GET /reports/warranty-expiring with ?days=30 (default) — returns assets where warrantyExpiration is within the next N days, sorted by warrantyExpiration ASC. Response includes assetId, name, warrantyExpiration, department.name, assignedTo
• GET /reports/maintenance-costs with ?from and ?to date range — total maintenance spend per asset and per department, sorted by cost DESC. Sums MaintenanceRecord.cost and WorkOrder.actualCost in the period
• GET /reports/depreciation — all depreciating assets with: purchasePrice, currentValue, totalDepreciation (purchasePrice - currentValue), depreciationMethod, usefulLifeYears, grouped by category with subtotals
• GET /reports/asset-utilisation — assets by utilisation: total days checked out vs total days in the period, percentage utilised, assets never used (0 checkouts)
• All endpoints are paginated and apply RBAC department scoping

[ZEMAD0N26]

@ZEMAD0N26 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Please assign!!

ℹ️ Repo Maintainers: To accept this application, review their application or assign @ZEMAD0N26 to this issue.

[walexjnr]

@walexjnr has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi can i work on this task?

ℹ️ Repo Maintainers: To accept this application, review their application or assign @walexjnr to this issue.

[drips-wave]

Congratulations, @walexjnr! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @walexjnr: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊