IS WORK OVER?

Automation index

How much of a SCADA technician’s job can AI already do?

A screen comes earlier. The operator seeing the alarm without dressing the historian do not.

This percentage does not predict how many people will lose their jobs.

Task comparison

SCADA 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.

TaskShareAIPoints
Screen, tags and the alarm.
Estimate

No public source provides a precise figure. This is our estimate.

16%40%+6.4
Field, the PLC and the one that will not answer.
Estimate

No public source provides a precise figure. This is our estimate.

18%14%+2.5
Historian, the gap and not dressing it.
Estimate

No public source provides a precise figure. This is our estimate.

16%28%+4.5
Network, the port and not leaving it open.
Estimate

No public source provides a precise figure. This is our estimate.

16%22%+3.5
The shift, the doubt and not hiding the alarm.
Estimate

No public source provides a precise figure. This is our estimate.

18%18%+3.2
That they see the alarm, and not dressing the historian.
Estimate

No public source provides a precise figure. This is our estimate.

16%12%+1.9
Total100%22%

Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low

Skills and activities

  • SCADA screens
  • alarms
  • historian
  • tags
  • ports
  • field PLC
  • not leave ports open
  • shifts

Sources for this job· O*NET 15-1244.00· ESCO/ISCO 3114

Backend 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.

TaskShareAIPoints
Endpoint, the contract and the test.
Estimate

No public source provides a precise figure. This is our estimate.

18%48%+8.6
Spike, the queue and the one that drops.
Estimate

No public source provides a precise figure. This is our estimate.

16%40%+6.4
Key, the secret and not leaving it in the repo.
Estimate

No public source provides a precise figure. This is our estimate.

16%22%+3.5
Migration, the rollback and not improvising in prod.
Estimate

No public source provides a precise figure. This is our estimate.

16%28%+4.5
Product, the deadline and not cutting the one that matters.
Estimate

No public source provides a precise figure. This is our estimate.

18%14%+2.5
That it takes the spike, and not leaving the key.
Estimate

No public source provides a precise figure. This is our estimate.

16%12%+1.9
Total100%27%

Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low

Skills and activities

  • endpoints
  • API contracts
  • queues
  • secrets
  • migrations
  • rollback
  • backend tests
  • write server code

Sources for this job· O*NET 15-1252.00· ESCO/ISCO 2512

Analyse my job

Jobs with similar scores

  1. 504Telephony technician22%
  2. 505Electoral officer22%
  3. 506Orthotic and prosthetic technician22%
  4. 508Food technologist22%
  5. 509Family therapist22%
  6. 510Respiratory therapist22%