Glossary · System coordination, integration and orchestration
Resource release
Also known as: Lock release
German: Ressourcenfreigabe
In automation and software, resource release is the act by which a task, machine or process gives up a shared resource it held, making it available to other requesters; it ends a lock or reservation.
- System integration
In one sentence
Resource release is when a task or machine gives up a shared resource it held, ending its lock or reservation for others to use.
Example
After placing the part and leaving the transfer station, the robot releases the station so the second robot can use it.
How it applies
- Engineering: Release only when the resource is really free and in a defined state, for example when the robot has physically left the zone, not merely when its program has moved on. Tie release to feedback, not to assumptions.
- Fault handling: Plan for releases that never arrive: timeouts, holder crash detection and a controlled manual release.
- Commissioning: Test that every path through the program, including aborts and error branches, releases the resources it acquired.
- Documentation: Document the release conditions in the interface specification. Where a manual release is possible, the service instructions must describe the preconditions to check first, because releasing a resource that is still in use can cause collisions.
Resource release vs. permission signal
A resource release gives up ownership so any waiting requester can acquire the resource. A Permission signal grants a specific partner the right to act. In a handshake, one party's release is often followed by a permission to the next party.