Automation index
How much of a Maintenance technician’s job can AI already do?
A CMMS and a procedure come earlier. Hearing a bearing, and leaving the plant running, do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Maintenance technician
22%
AI can already do 22% of this job.
#496 / 773
View rankingMaintenance technician
Where the time goes
Task weights are our estimates based on O*NET frequency data, not time shares published by O*NET.
The time saving for each task is estimated separately.
| Task | Share | AI | Points |
|---|---|---|---|
CMMS, history and spare orders.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 40% | +7.2 |
Procedures, written LOTO and logs.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 32% | +5.1 |
Diagnose, strip and repair.EstimateNo public source provides a precise figure. This is our estimate. | 20% | 12% | +2.4 |
Field preventative and measurements.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 15% | +2.4 |
On-call, shutdowns and production pressure.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 14% | +2.2 |
Safety, permits and not leaving the plant down.EstimateNo public source provides a precise figure. This is our estimate. | 14% | 16% | +2.2 |
| Total | 100% | 22% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- CMMS, history and spare orders
- Procedures, written LOTO and logs
- Diagnose, strip and repair
- Field preventative and measurements
- On-call, shutdowns and production pressure
- tecnico de mantenimiento
- maintenance technician
- mantenimiento industrial
Sources for this job· O*NET 49-9041.00· ESCO/ISCO 3115
IS WORK OVER?
Front-end developer
27%
#157 / 773
View rankingFront-end developer
Where the time goes
Task weights are our estimates based on O*NET frequency data, not time shares published by O*NET.
The time saving for each task is estimated separately.
| Task | Share | AI | Points |
|---|---|---|---|
Component, states and the design.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 48% | +8.6 |
Accessible, the keyboard and the reader.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Contrast, the token and not leaving it dead.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Performance, the weight and not adding the extra library.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
The designer, the pixel and not fighting for sport.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
That it works from the keyboard, and not leaving the contrast.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 12% | +1.9 |
| Total | 100% | 27% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- components
- accessibility
- keyboard
- contrast
- tokens
- front-end performance
- libraries
- write interface
Sources for this job· O*NET 15-1254.00· ESCO/ISCO 2513