Monitor processes for compliance with standards.
Little of this can be handed to software today.
This happens in the physical world, so software agents do not touch it. Automation here means robotics and machinery, which is a different market from the one mapped on this site, on a much slower clock.
| How automatable | Barely automatable |
|---|---|
| Kind of work | Physical, manual and inspection work |
| Jobs that do it | 11 occupations |
| Tool categories that apply | None |
| O*NET activity | Monitoring Processes, Materials, or Surroundings (4.A.1.a.2) |
What could do this work.
Nothing in our landscape addresses this work. That is the honest answer rather than a padded list: this activity needs a person present, or a machine rather than a software agent.
Who does this work.
11 occupations in the O*NET database perform this activity. Each one has a full breakdown of its other tasks.
- Architectural and Civil Drafters
- Chemical Technicians
- Computer Hardware Engineers
- Environmental Engineering Technologists and Technicians
- Industrial Engineering Technologists and Technicians
- Information Security Engineers
- Marine Engineers and Naval Architects
- Nanotechnology Engineering Technologists and Technicians
- Nuclear Engineers
- Surveying and Mapping Technicians
- Wind Energy Engineers
Work that goes with it.
O*NET groups these under “Monitor operations to ensure compliance with regulations or standards”. In practice they tend to be done by the same person, in the same sitting.
Method. The activity, its taxonomy placement and the occupations that perform it come straight from the public-domain O*NET 30.3 database. The automatability band is ours: we map each of O*NET’s 41 generalized work activities to how much of its output current software can produce, assuming a person still reviews and owns the result. It is a coarse three-way judgment on purpose. A precise-looking percentage here would be invented.