Northwind Facilities: Asset Hierarchy, Warranty Inheritance, and Downtime
Northwind Facilities manages 1,200 customer assets for 300 commercial clients. Assets are organized in parent-child hierarchies: a building is the parent, and HVAC units, elevators, and generators are children. Work order types include Warranty Repair and Billable Repair. The company wants work orders on child assets to automatically inherit the parent building's warranty, and wants service history to roll up to the parent. They also want to track asset downtime. Currently, when a technician completes a work order on a child HVAC unit, the parent building's warranty is not applied, and the service history only shows the child asset. The company uses the Field Service mobile app and has 60 technicians. The operations manager wants a scalable solution without custom code, but is open to Power Automate. They also need to report on downtime by asset and by client.
1. Why does a work order on a child asset not inherit the parent building's warranty, and how would you design a solution that applies the correct warranty without manual entry?
Read the worked answer
Warranty information is stored against the asset or through the warranty entity, and Field Service does not cascade a parent asset's warranty down to child assets automatically. The work order type may be named Warranty Repair, but that label alone does not populate the warranty or change billing. First confirm where warranty is recorded. If the warranty is on the parent building asset, the child HVAC asset has no warranty record of its own. Design a Power Automate flow that runs when a work order is created with an asset. The flow retrieves the asset's parent asset, reads the parent's warranty record and warranty term dates, and then updates the work order with the correct warranty reference and sets the work order type to Warranty Repair when the date falls inside the term. Add a condition to skip the update when the child asset has its own warranty, so the child takes precedence. Also validate that the warranty term covers the work order date and that the parent-child relationship is maintained through the parent asset lookup. Keep the flow idempotent and log failures so dispatchers can review exceptions rather than relying on technicians to choose the warranty manually.
2. How would you make service history roll up from child assets to the parent building? Explain the data model and the components you would use.
Read the worked answer
Field Service service history is essentially the set of work orders linked to an asset, so there is no native rollup from child to parent. Choose a design based on reporting needs. For a low-code solution, create a Power Automate flow that triggers when a work order on a child asset is closed. The flow finds the parent asset through the parent asset lookup and creates a note or a custom service history record on the parent, including the child asset, work order number, date, and summary. For quantitative rollups, add rollup fields on the parent asset that count or sum child work orders, but remember rollup fields are calculated asynchronously and are not real-time. For reporting, use Power BI with the asset hierarchy so users can drill from building to child assets without duplicating records. Avoid copying every work order to the parent as a separate work order, because that inflates volume and confuses billing. Document that the parent timeline is a summary and the child asset remains the system of record for the actual work performed.
3. How would you track asset downtime using built-in Field Service capabilities, and what would you configure to report on downtime by asset and client?
Read the worked answer
Use the asset downtime entity to record downtime periods with start time, end time, duration, and a lookup to the asset. Create downtime records through one of three paths. Technicians can create them from the mobile app when they arrive and leave. A Power Automate flow can create downtime when a work order changes to an in-progress status and set the end time when it is completed. IoT alerts can also create downtime automatically for connected assets. Ensure the asset downtime entity is enabled and that technicians have security roles to create records. For reporting, build views and Power BI reports that join downtime to the asset and then to the customer account. Add a rollup field on the asset for total downtime hours if users need a quick indicator, but use Power BI for client-level and period-based analysis. Validate that downtime duration is calculated from start and end times, and define whether planned maintenance counts as downtime so the reports are consistent.