Inside a semiconductor cleanroom, the flow of silicon wafers is managed by a highly orchestrated fleet of robotic transport systems. When an Overhead Hoist Vehicle (OHV) or an Automated Guided Vehicle (AGV) faults out, the entire production line can stall. A technician cannot troubleshoot a system error by simply noting that a robot "stopped working"; they need the exact error code, the specific tool port, and the physical orientation of the carrier at the moment of failure. This Memento database acts as a rigid, robotic autopsy log, forcing cleanroom technicians to map the exact parameters of AMHS failures before they attempt a reset.
Isolating the Fleet Failure
The first step in resolving an automation crash is isolating the specific hardware involved. The template immediately forces the user to classify the core "Equipment": OHV, AGV, or Stocker.
Depending on the selection, the technician must input the specific hardware identifier—the "OHV#" or "AGV#". It then demands the exact "Location (Bay)" where the fault occurred and logs the "Time/Date" stamp. This is not just administrative data; by mapping the specific vehicle ID against the bay location, system engineers can identify if a particular OHV unit is repeatedly failing, or if a specific stretch of the overhead track is causing multiple different units to fault.
The Logic and Port Matrix
Automation errors usually occur at the interface between the vehicle and the destination port. The database forces a deep dive into this interaction.
It demands the specific machine logic via the "OHV Error Code", "AGV Error Code", or "Stocker Error Code". The technician must then classify the "Error Type" (Stacker vs. Port) and define the exact "Port Type" involved (OHV, AGV, PGV, COMBO, FOSB). Crucially, the system tracks the directional flow of the material by requiring the "Port I/O" status (Input/Output) and the "Tool ID" to pinpoint exactly which semiconductor processing machine was waiting for—or releasing—the material.
Tracking the Physical Carrier
A robotic error is dangerous; an error that compromises the silicon is catastrophic. The final module of the database audits the physical Front Opening Unified Pod (FOUP) carrying the wafers.
The system asks "FOUP Involved" and "FOUP on Arm" to determine if the robot dropped the payload or if it failed while empty. It requires the exact "Carrier ID" and utilizes strict boolean toggles for "Presence" and "Placement" to confirm if the system's sensors accurately detected the physical box. By forcing the technician to log these micro-variables before typing out the final "Error Description", the database ensures that root-cause analysis is driven by hard mechanical state data rather than human guesswork.