Assess characteristics of fires
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 | 3 occupations |
| Tool categories that apply | None |
| O*NET activity | Monitoring Processes, Materials, or Surroundings (4.A.1.a.2) |
What this looks like on the job
Not our paraphrase. These are real task statements recorded against this activity, spread across the 3 occupations that perform it.
- Assess nature and extent of fire, condition of building, danger to adjacent buildings, and water supply status to determine crew or company requirements.
- Assess fires and situations and report conditions to superiors to receive instructions, using two-way radios.
- Estimate sizes and characteristics of fires, and report findings to base camps by radio or telephone.
- Analyze burn conditions and results, and prepare postburn reports.
- Evaluate size, location, and condition of fires.
What we would actually use
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.
Nothing on this site applies. Automation here is robotics and machinery, a different market on a much slower clock, and no software subscription moves it.
Chosen for the cheapest thing that does the job, not the best funded. Nothing on this site is sponsored, and the full landscape is there when you want to disagree with us.
How people actually do it
No workflow names this activity yet, but these automate the same kind of work, with the prompts to paste and what to keep for yourself.
Who does this work
3 occupations in the O*NET database perform this activity. Each one has a full breakdown of its other tasks.
Work that goes with it
O*NET groups these under “Monitor environmental conditions”. 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.