Crane guidance
Relations to Other Scenarios
- Crane guidance → specific → Logistics
Summary🔗
This scenario examines how crane operators can lift and deliver the cargo around the construction site.
Models🔗
crane_log🔗
This log contains the observed crane states corresponding to the cranes.
Definitions🔗
pickup location🔗
This is an IfcZone
where the delivery (from logistics) needs to be picked up.
attaching slinger🔗
The actor (from actor_management) who will attach the delivery (from logistics) to the crane at the pickup location.
detaching slinger🔗
The actor (from actor_management) who will take off the delivery (from logistics) from the crane at the delivery location (from logistics).
A detaching slinger can be identical with a attaching slinger.
crane delivery🔗
A crane delivery defines how the delivery (from logistics) should be transported within the construction site by a crane.
Each crane delivery is associated with:
- a pickup location and the corresponding one or more attaching slingers,
- the delivery location (from logistics) and the corresponding one or more detaching slingers, and
- the crane,
- the crane supervisor, and
- the crane operator
crane operator🔗
The crane operator is an operator (from logistics) who controls the crane.
crane supervisor🔗
Crane supervisor is an actor (from actor_management) who helps the crane operator by guiding her during the delivery (from logistics).
She has the final authority.
crane coordinator🔗
The crane coordinator is an actor (from actor_management) who supervises that the crane operators do not crash into each other.
crane🔗
The crane is defined as IfcTransportElement
and stored in cranes.
Its state is tracked as crane state and stored in crane_log.
crane state🔗
The crane state captures the state of the crane, including:
- a timestamp of the observation,
- position of the trolley, and
- the height of the hook block (if available).
Scenario🔗
As-planned🔗
The planner role (from logistics) specifies the deliveries (from logistics) (with additional information defined) as crane deliveries.site
As-observed🔗
The position of the crane's arm is continuously tracked as crane state in crane_log.machine
Divergence🔗
The device will guide the crane operator and the crane supervisor to the delivery location (from logistics).
Since the crane delivery is very dynamic, we explicitly do not provide a mechanism to signal the attaching slingers and detaching slingers when the crane delivery arrived, as these actors would have a visual contact anyhow.
machineScheduling🔗
For a given time range, the planner role (from logistics) should be able to inspect the plan of the crane deliveries as association between the cranes, crane operators, crane supervisors and tasks (from scheduling) (if available).
siteSafety🔗
The crane coordinator ensures visually that the crane operators do not crash.
In addition, the system should warn the crane coordinator if two crane arms are about to collide.
siteAnalytics🔗
As we track the crane movements in crane_log, the system should report the crane utilisation over time.
The details are to be discussed during the implementation (e.g., what time units and how we can measure it).
machineTest Cases🔗
Please see the test cases of "Logistics".
Acceptance Criteria🔗
Please see the acceptance criteria of "Logistics".