PM-DEMO-001 · Revision 1.0 · Prepared October 5, 2026 · Example Site A · Fremont, California
Illustrative assessment—not a real client engagement. All organizations, observations, document references, findings, and assignments below are invented. No inspection or technical validation occurred. This is a worked reporting example, not an operating procedure or authorization to use equipment.
Executive decision brief
A fictional 28-person parts distributor plans to introduce three autonomous mobile robots between receiving and packing. Two shifts share the proposed routes with pedestrians and manual pallet movement. A controlled pilot is planned; no deployment has been approved in this example.
Proposed disposition in this scenario
Do not release the shared-route pilot until crossing controls and restart responsibilities are reviewed, affected personnel are trained, and the employer accepts documented verification evidence.
Findings: 2 P1 release/intervention blockers; 3 P2 prerequisites. All remain open. No residual risk acceptance or completion is claimed.
Scope, evidence, and limitations
Review scope: transition documentation, planned human–machine interactions, task instructions, training coverage, and change responsibilities.
No site visit, interviews, robot operation, stopping-distance measurements, traffic counts, sensor validation, cybersecurity testing, or engineering analysis was performed. Payload, speed, braking, visibility, and site dimensions are unknown.
ID
Fictional evidence item
Scenario content
A1
Illustrative route plan, revision A
Route crosses the pedestrian approach to the packing station beside a shelving corner.
A2
Illustrative fleet-role export
A shared supervisor account can edit routes and release paused jobs.
A3
Illustrative IIPP and training matrix
General warehouse induction exists; automation-specific changes and night-shift instruction are absent.
A4
Illustrative exception-handling instruction
Instruction says to clear the route and resume, without defining safe boundaries or the authorized role.
These evidence items describe the exercise inputs. They are not existing attachments, photos, interviews, or client records. In a real report, each reference would resolve to a retained evidence item with its author, date, version, and permission to use it.
Priority method
P1: recommend withholding the affected release or intervention until the stated prerequisite is resolved. P2: complete before the specified assignment or change. Priorities reflect the fictional task context and uncertainty, not a measured probability, certified risk score, or regulatory violation finding. Deadlines are proposed decision gates, not statutory cure periods.
Detailed findings and corrective-action register
A-01 · P1 · OPEN
Shared pedestrian crossing has no documented control basis
Evidence reference
A1
Scenario observation
A planned route meets a pedestrian path at a shelving corner. The example plan shows no crossing-control design or validation record.
Potential consequence
A pedestrian could enter an occupied travel path; actual severity and exposure require a site review.
Interim recommendation
Keep the affected route out of shared operation pending review.
Proposed owner
Operations lead + robot integrator
Target gate
Before shared-route pilot
Recommended action
Review opportunities to eliminate the crossing or physically separate traffic first. Have the qualified integrator assess the remaining interaction; define signs and briefings as supporting measures, not substitutes for necessary engineered protection.
Closure evidence required
Approved route revision, site-specific risk review, and integrator verification for intended operating conditions; employer acceptance recorded.
Basis / reference
IIPP hazard review; robot guidance [1,4]
Verification status
Not performed. Owner acceptance, completion date, and verifier signature are pending in this exercise.
A-02 · P1 · OPEN
Recovery instruction does not identify who may restart
Evidence reference
A4
Scenario observation
The instruction assigns no authorized responder or response boundary for a stopped robot.
Potential consequence
Untrained intervention could expose a person to unexpected movement or manual-handling hazards.
Interim recommendation
Keep untrained staff out of recovery tasks; escalate exceptions to the designated trained responder.
Proposed owner
Operations lead + integrator
Target gate
Before pilot
Recommended action
Develop equipment-specific recovery instructions from supplier information and site review. Define escalation and release authority; evaluate servicing tasks separately for hazardous-energy requirements.
Closure evidence required
Approved procedure, role roster, documented instruction, and qualified verification of the recovery workflow.
Basis / reference
Task review; hazardous-energy applicability [1,2]
Verification status
Not performed. Owner acceptance, completion date, and verifier signature are pending in this exercise.
A-03 · P2 · OPEN
Shared account obscures responsibility for route changes
Evidence reference
A2
Scenario observation
One supervisor credential allows route editing and job release. No named change approver appears in the scenario.
Potential consequence
A route change could invalidate the reviewed traffic arrangement without accountability.
Interim recommendation
Freeze route changes to an approved baseline while roles are reviewed.
Proposed owner
Fleet administrator + operations lead
Target gate
Before any route change
Recommended action
Assign individual roles where supported, separate routine operations from configuration authority, record approvals, and retain change history. Review vendor remote access too.
Closure evidence required
Role matrix, approved account configuration, change log, and a non-production demonstration that unauthorized changes are rejected.
Not performed. Owner acceptance, completion date, and verifier signature are pending in this exercise.
A-04 · P2 · OPEN
Training does not cover new tasks on both shifts
Evidence reference
A3
Scenario observation
Existing induction covers manual warehouse work only; there is no robot-specific training entry for either shift.
Potential consequence
Staff may misunderstand travel zones, fault escalation, or their permitted tasks.
Interim recommendation
Do not assign new automation duties to personnel who have not received the required task instruction.
Proposed owner
Training coordinator
Target gate
Before affected assignment
Recommended action
Update the training matrix for operators, nearby workers, supervisors, temporary staff, and responders. Use understandable language and practical checks appropriate to each role.
Closure evidence required
Dated attendance and subject records, role-specific understanding checks, and supervisor assignment approval.
Basis / reference
Training and communication [1]
Verification status
Not performed. Owner acceptance, completion date, and verifier signature are pending in this exercise.
A-05 · P2 · OPEN
Automation change is absent from the IIPP review process
Evidence reference
A3
Scenario observation
The example IIPP names general inspections but has no record of reviewing the introduced routes or exception tasks.
Potential consequence
New hazards and corrective actions could remain outside routine management review.
Interim recommendation
Assign an accountable transition owner and log the outstanding findings.
Proposed owner
IIPP owner
Target gate
Before pilot approval
Recommended action
Record the new-hazard review, connect actions to responsible roles, and define triggers for re-review after route, load, equipment, software-behavior, or task changes.
Closure evidence required
Approved IIPP updates where needed, inspection record, action register, and planned follow-up date.
Basis / reference
Hazard evaluation and corrective action [1]
Verification status
Not performed. Owner acceptance, completion date, and verifier signature are pending in this exercise.
Worked procedure and training example
AMR exception reporting and escalation
Awareness-level example for discussion. Machine-specific instructions and qualified site approval are required before use.
An employee who encounters a robot stopped in a shared aisle reports the location and observed condition to the designated responder, keeps clear, and does not move the robot or release the job. The supervisor arranges the site-approved area controls. Only an authorized, trained responder follows the equipment-specific recovery procedure. Any entry, servicing, or energy-control task requires its separately reviewed procedure.
Training check: Scenario: a cart blocks the route and a colleague asks you to press resume. Expected response: remain within your assigned role, report the obstruction, keep clear, and use the designated escalation route; do not improvise recovery.
Change-review workflow: Route or task change → documented hazard review → qualified verification where needed → updated instructions and role-specific training → employer release decision.
NIOSH control selection and NIST review
These are advisory review lenses, not certifications or replacements for applicable regulations. Automation alone does not establish that an AI model is present.
NIOSH hierarchy of controls
Evaluate elimination, substitution, and engineering controls before relying on administrative controls or PPE. Record why stronger options were selected, rejected, or need further investigation. A training record does not demonstrate that a physical hazard has been controlled.
A-01 — Elimination: investigate removing the shared crossing through workflow redesign. Substitution: compare an alternative transport method and its new hazards. Engineering: have qualified personnel evaluate physical traffic separation and necessary protective functions. Route instructions and signs are supporting administrative controls. No claim is made that PPE would prevent a robot collision.
A-02 through A-05 — Administrative and governance measures: recovery authorization, role controls, instruction, and change review support the physical protections. Their adequacy is unverified.
NIST AI RMF — conditional AI review
Applicability finding: unresolved. The fictional evidence does not establish whether the system uses an AI model or what role it plays. Obtain the supplier architecture, intended use, limitations, and version information before assigning model-performance findings.
Govern
Propose named owners for AI use, changes, incident escalation, and acceptance. Owner approval is pending.
Map
Identify any AI functions, affected people, operating conditions, and consequences of incorrect outputs. Keep advisory AI separate from validated machine safety functions.
Measure
Request supplier evaluation evidence and a qualified, controlled validation plan for relevant operating conditions and failure modes. No performance metrics, thresholds, or test results exist in this example.
Manage
Document release criteria, monitoring, human review, and a site-approved fallback or suspension process if performance changes. No release recommendation follows from a framework checklist alone.
For connected equipment, review asset ownership, named access, supplier remote access, approved configuration changes, logging, incident response, and restoration responsibilities. The account findings above are limited documentation observations, not a security audit. No active security tests or safety-controller changes were performed.
Assign: the employer designates accountable roles and confirms the affected-work restrictions.
Resolve: operations, maintenance, and the integrator supply the requested evidence and revise the relevant documents.
Verify: qualified personnel check technical controls; supervisors confirm role-specific instruction and competence as applicable.
Decide: the employer documents the release decision, outstanding restrictions, and next review date. Neither a completed form nor a course certificate alone establishes safety.
Acceptance record — deliberately unsigned
Employer decision: pending · Technical verifier: pending · Action closure: not verified · Residual risk: not assessed · Release date: not assigned.
Regulatory and technical reference notes
References inform the review; applicability requires the actual site, task, equipment, and jurisdiction. Governance recommendations are identified separately from legal requirements. OSHA technical guidance is not itself a new regulation.
Cal/OSHA Title 8 §3203 — IIPP. Relevant topics include identifying new hazards, training, responsibility, and corrective actions.
Sources checked October 5, 2026. Independent PeopleMach portfolio material; no OSHA/Cal/OSHA affiliation, client endorsement, or compliance certification is implied.