Downtime Logs in FireFlight capture unplanned outages with timestamp, duration, affected asset, and failure description. IoT sensor sync triggers downtime log entries automatically when a sensor reading crosses a defined threshold, which means the log entry exists at the moment the anomaly is detected rather than when a technician gets around to filing a report. That distinction matters for operations where the time between detection and response directly affects production impact.

The log entry is not a data endpoint. It is the trigger for a messaging workflow that assigns a response to the appropriate team based on the asset type, the failure category, and the severity configured in the rule library. A hydraulic failure on a critical production asset routes differently than a routine equipment alarm on a secondary line. Both produce log entries. Both trigger workflows. The routing is determined by the rules rather than by whoever happens to see the alert first.

Work orders are generated from downtime log entries with the asset, the failure description, and the relevant history pre-populated. A technician receiving a work order has the prior maintenance history of the affected asset visible before they arrive at the location. The symptom-to-resolution traceability is built into the record structure rather than reconstructed after the fact from memory and paper notes.

Work order flows in FireFlight handle both preventive and corrective maintenance through the same process with different trigger sources. Preventive maintenance tasks are generated by the schedule. Corrective tasks are generated by downtime events, sensor triggers, or manual requests. Once created, both types follow the same work order lifecycle: assignment, dispatch, execution, parts logging, and closure with digital sign-off.

Digital sign-off checkpoints require a named authorized person to confirm completion before a work order can close. The sign-off requirements are configured per work order type. Safety-critical maintenance on regulated equipment requires a different sign-off chain than routine lubrication on a non-critical asset. The configuration is done once at the work order type level rather than requiring someone to remember the correct sign-off procedure for each individual job.

Dispatch tools in the workspace route work orders to the right technician based on availability, skill set, or location proximity depending on how the dispatch rules are configured. For operations with multiple maintenance technicians across multiple sites, smart dispatch prevents the situation where an available technician at one site is waiting for work while another site has an overloaded queue. The dispatch record is part of the work order record, which means response time from work order creation to technician assignment is measurable from the data rather than estimated.

Failure Mode Analysis in FireFlight examines the maintenance history of the asset portfolio to identify recurring patterns. An asset that generates the same failure code on every third preventive maintenance cycle is showing a pattern. An asset class where bearing failures account for 60% of corrective work orders has a parts reliability question that the maintenance schedule is not addressing. These patterns are invisible when maintenance records are stored in spreadsheets or paper logs. They are visible when maintenance data is structured and queryable.

Spare Parts Usage tracks the parts consumed against each work order at the line level. The usage posts to the work order record and updates inventory simultaneously. Parts cost is associated with the specific asset that required the repair, feeding Total Cost of Ownership calculations in the Asset Cost and Performance Analysis workspace. For maintenance supervisors managing a budget, the parts cost data by asset is what identifies which assets are consuming disproportionate parts expenditure relative to their production contribution.

Stock Transfers handles parts movement between locations. An operation with multiple maintenance shops needs parts to be available where the work is being done. Stock Transfers records the movement and updates inventory at both locations. Warranty Management surfaces warranty coverage status at the point of the corrective work order decision. An asset with an active warranty on the component that just failed should not generate a parts purchase order before the warranty claim is evaluated. The warranty visibility prevents that expenditure before the decision is made rather than after the parts have already been ordered.

The Preventive and Corrective Maintenance workspace includes thirteen apps covering the full maintenance lifecycle from downtime capture through analysis, parts management, and compliance documentation.

The Preventive and Corrective Maintenance workspace integrates directly with ERP inside FireFlight. Work order labor costs, parts expenditures, and warranty claim values feed into ERP financial records, connecting maintenance operations to the financial reporting layer without a manual export step.

The Preventive and Corrective Maintenance workspace is part of FireFlight EAM. Most deployments are operational in weeks, not months. Maintenance scheduling, work order configuration, and IoT integration are part of the deployment engagement. The structured maintenance data that failure mode analysis and compliance documentation depend on starts accumulating from go-live day, not after a separate data migration phase runs in weeks, not months post-deployment.