An AMR arrives from its manufacturer with a default operating envelope — the zones, tasks, and conditions it was designed to handle. Institutional AMR permissions layer the hospital's own rules on top of that: which zones are off-limits during specific hours, which tasks require supervisor approval, and how permissions change during an emergency protocol like a code red.
How it differs from manufacturer-defined operating limits
Manufacturer limits are set once, at deployment, and apply the same way regardless of hospital-specific context. Institutional permissions are set by the hospital, can change dynamically (a zone that's normally accessible becomes restricted during an active emergency), and apply uniformly across every AMR in the building — not just one vendor's fleet.
Why it matters in healthcare
Hospitals are not generic industrial facilities — a zone that's safe for a robot to enter at 3am may not be safe at 2pm during a shift change, and an area near a patient in isolation may need different rules than the rest of the floor. Institutional AMR permissions give hospitals the ability to encode this context-specific logic themselves, rather than relying on a manufacturer's one-size-fits-all default configuration.
A useful analogy
This works like a hospital's own visitor policy, layered on top of general building access. The building has baseline security, but the hospital sets its own rules about visiting hours, restricted units, and exceptions during an emergency — rules the building's architect never anticipated and shouldn't be expected to define.