Equipment Operating Procedures: Start-Up, Shutdown and Routine Operation

The buyer's problem

A humanoid working around commercial equipment, such as ovens, floor scrubbers, laundry machines, packaging lines or test benches, must know the order of operations and the signals that say a machine is ready. Operating procedures are the closest document class. They differ from line changeovers, which concern switching product or tooling and sit in the manufacturing cluster, and from maintenance work, covered in the maintenance hub.

The documents come from different authors: equipment manufacturers write operator manuals, facilities teams write local procedures, and quality or safety groups add rules. A buyer needs to know which is which, because rights, accuracy and detail differ.

Document types in this class

Each has a different relationship to robot use. Start-up and routine cards define the sequence a robot might perform or monitor. Energy-control procedures define when the machine must not be touched.

Lockout/tagout as a worked example of constraint

OSHA's standard on the control of hazardous energy requires employers to develop, document and use specific procedures to control potentially hazardous energy when employees service equipment (OSHA, 29 CFR 1910.147). Federal guidance material describes such procedures as covering scope, purpose, authorization, rules and techniques, plus specific shutdown, isolation and securing steps; the standard also contains a narrow documentation exception. Check the current rule text and applicable state plans with qualified safety counsel. This is not legal advice.

For a robotics buyer, the practical point is data structure. These procedures are explicit about preconditions ("machine isolated, energy verified") and about who may authorize a step. A robot that takes part in servicing or operating tasks inherits those gates. Mark them as constraints rather than as steps to optimize; see safety-critical steps in procedures and preconditions and postconditions.

Structured technical publications

Some equipment documentation is authored in structured form. S1000D is an XML-based specification for producing and managing technical publications, in which data modules are stand-alone units of descriptive, procedural or operational data stored in a common source database and identified by a unique data module code (S1000D). It is used for civil and military products. If a supplier can export from such a source, steps arrive already segmented with identifiers, which saves recovery work; see structured authoring exports. Most commercial site documents, however, are PDFs and spreadsheets, and need the preparation described in parsing scanned manuals.

What operating procedures can support, and what they cannot

They can support task decomposition, readiness checks, language grounding for control labels ("Auto", "Standby", "E-stop reset"), alarm-handling logic and evaluation of whether a planner respects ordering and safety gates. They cannot teach how to press a stiff button, turn a valve against resistance, read a glare-affected display or recognize an unusual sound. They also describe the equipment as designed; a particular unit's quirks, such as a sticking door or a drifting gauge, are absent. Manuals for one model do not transfer to another model without checking.

Illustrative procedure record

# Illustrative only - synthetic example, not an available dataset
procedure_id: eq_op_0044
equipment_class: commercial_dishwasher_conveyor
equipment_model_alias: model_M7
phase: start_up                  # start_up | run | shut_down
preconditions:
  - "Drain plugs seated"
  - "Chemical supply level above minimum mark"
steps:
  - step_id: eq_op_0044_s03
    action: "Turn main selector to ON"
    control: selector_main
    expected_indicator: "Power lamp steady green"
    next_if_not: eq_op_0044_exc_02     # exception branch
    safety_gate: false
  - step_id: eq_op_0044_s05
    action: "Wait for wash tank to reach set temperature"
    expected_indicator: "Display shows READY"
    wait_condition: indicator
exceptions: [eq_op_0044_exc_02]
record_required: log_entry_daily
source_type: site_procedure         # site_procedure | manufacturer_manual

The expected_indicator field is where documents are weakest and robotics buyers most dependent. Many procedures say "when ready" without saying what ready looks like. The source_type field supports rights decisions.

Acceptance criteria you can set

1. Source labeling. Each document is marked site-authored or manufacturer-authored.
2. Indicator coverage. Share of steps with an observable expected state.
3. Exception linkage. Abnormal-condition branches exist and link to exception and emergency procedures.
4. Model and version tags. Equipment model and firmware or manual revision are recorded.
5. Control vocabulary. Control and indicator names are normalized so the same switch has one label.
6. Tool lists. Required tools and materials are extractable; see tools and materials lists.

Rights and provenance

Operator manuals are often the equipment maker's copyrighted work. The business operating the machine may have a copy for use but not necessarily the right to license it. Site-authored procedures are more likely to be licensable by the site owner, but may quote the manufacturer. A multi-tenant facility can add landlord or client terms. Treat the rights question per document; see product user guides as instruction data.

Limitations

Documents describe intended operation. They do not show timing variation, operator shortcuts or hardware wear. Safety statements vary by jurisdiction and employer. Equipment fleets differ across sites, so a corpus from one operator may cover only a few models. And the procedure for operating a machine is useless for physical control unless paired with robot-collected interaction data.

Questions to ask suppliers

1. Which documents are site-authored, and which are manufacturer manuals?
2. Which equipment models and versions do they cover?
3. Do procedures state observable indicators, or only "when ready"?
4. Are energy-control procedures included, and can they be licensed separately?
5. How are alarms and abnormal states documented?
6. Is any documentation held in a structured authoring system?
7. Are there photos or video of the controls and displays?
8. How often are procedures revised after equipment changes?

Discuss your requirements

If equipment operation is part of your task scope, describe the equipment classes, document types and permitted uses to SourceX. SourceX looks for US businesses that hold suitable documents, checks the data and the supplier's licensing permissions, and coordinates the license and delivery. A request does not guarantee a match; SourceX follows up about potential sources.

Start from the humanoid training data guide or the procedural data hub. Related catalog pages cover internal documentation and field service maintenance records.

Discuss your humanoid training-data requirements with SourceX

Sources

• 29 CFR 1910.147 The control of hazardous energy (lockout/tagout) — OSHA's lockout/tagout standard requires documented, specific procedures to control hazardous energy during servicing, covering scope, purpose, authorization, rules, techniques and shutdown/isolation steps.
• S1000D International specification for technical publications using a common source database — S1000D specifies XML data modules for descriptive, procedural and operational technical publications held in a common source database.