Should scheduled blade-change labor count the same as an emergency roadside replacement?

Use the same cost definitions, but record the resources and disruption that actually occurred in each type of event. A scheduled workshop change and an emergency replacement need not have identical consequences. Separate the installation work from recovery, coordination and service effects, and avoid a universal emergency multiplier that substitutes an assumption for the event record.

Separate planned workshop work from disruption-related activities

Define the planned-change boundary: the work needed to remove and install the approved assembly, associated components and the recorded workshop time. Identify whether the vehicle was already scheduled out of service for other work. A blade task performed during a wider service visit should not automatically inherit the full visit duration. Record how shared work is allocated so the comparison does not make routine changes appear artificially cheap or expensive.

For the emergency event, document what happened and the actual removal reason before assigning costs. The fleet-downtime discussion provides broader categories, but this trial needs event-specific evidence. Separate blade work, travel or recovery, waiting for parts, reassignment and any documented service interruption. Do not imply that an emergency event proves a product fault; the cause and the resources consumed are related questions that still require distinct evidence.

Record actual resources and service loss without a universal downtime multiplier

Use the fleet's established labor and cost methods, with actual hours or other supported resource measures. Where a value must be estimated, show the basis and uncertainty. Avoid assigning the same time simultaneously to several full-cost categories without explaining whether they overlap. For instance, a vehicle waiting while another crew works may involve different resources from the installation labor itself. A transparent event breakdown allows those distinctions to be reviewed.

Compare equivalent scopes across the trial options. If one side includes transport and dispatch effort, check whether corresponding baseline events were recorded at the same level. Missing detail should be disclosed rather than treated as zero cost. Keep any contractual or service consequences limited to documented applicable facts reviewed by the responsible owner; do not invent penalties or assign a generic financial value to safety exposure. Safety requirements remain independent of the economic ranking.

Use clearly defined cost categories to avoid overstating or hiding the emergency impact

Report planned and unplanned events separately before combining them into a total. Show the actual counts and recorded consequences for the study period, and identify whether a rare event dominates the conclusion. A sensitivity view can help explain how much depends on that event, but it should not erase the event because it is inconvenient. Likewise, one costly interruption does not establish that every future change will have the same cost.

For a blade replacement evaluation, provide the event breakdown and the uncertainty that matters to the decision. The team may find that the important improvement concerns stock readiness, maintenance scheduling or another factor rather than the edge itself. Close the comparison with a consistent, auditable boundary and a clear distinction between observed costs and planning assumptions. The useful result is an explanation of what the fleet actually spent and lost during each event, not a predetermined premium attached to the word emergency.