← Features

Bookings

Shared site equipment — a hoist, a mixer — booked one firm at a time on a week calendar the coordinator drags across in the coordination meeting, and printed on the daily report as a drawn day strip.

Several firms need the hoist; only one can use it at a time. SimOps keeps the site's shared equipment as Bookable resources and each firm's claim on one as a Booking, and the coordinator settles who gets what on a full-screen week calendar — dragging boxes into slots during the coordination meeting, with every firm's bookings in view.

What it does for you

  • Book in the meeting. Drag an empty stretch to book it, drag a box to move it, drag an edge to resize it; every edge snaps to the quarter-hour, and two screens in the room stay in step.
  • No double-booking, ever. Two bookings on one resource never overlap: a clashing booking is refused outright and SimOps names the booking in its way. Back-to-back is fine.
  • Down time is a booking too. An inspection or a breakdown is booked Out of service, with its reason, and holds the slot like any other booking.
  • Your equipment, your list. The site adds its own resources and resource types in the app — a cement mixer nobody anticipated needs no code change — and gives each its colour and Bookable hours.
  • Everyone sees the same calendar. Every firm reads every booking, with the firm's name (booking_view); only the manage band — admin, coordinator and site manager (booking_manage) — books.
  • The firm is told. Booking a firm, moving its booking or cancelling it tells that firm's members on the site, in the app and by email.
  • A pointer to the permit. A booking may name the issued permit its work runs under, shown on the booking as a link through to the permit.
  • It prints. The daily report prints the day's bookings as a drawn day strip, one row per resource, and the site diary freezes the same strip when the day publishes.

What it deliberately does not do

A resource is not plant and a booking is not a token: neither is placed on the map, neither reaches the clash engine, and neither appears in the entity browser, on the permit board or on the Plan Gantt. There is no capacity pool — two hoists are two resources, and a booking names which one. Contractors do not book for themselves, and a booking outside the resource's bookable hours is warned about, not refused, because the person booking decides.

Where to go next

  • Booking shared equipment — the how-to: booking in the meeting, repeats, out of service, hours, managing resources, and where it prints.
  • Reports — the daily coordination report the day strip prints in.
  • The site diary — the day's record, which keeps the strip as it stood.
Was this page useful? Report a problem

No cookies and no third-party analytics. A verdict records this page's path — and a search that finds nothing records the words you typed — in this site's own server log.

Generated from source · SimOops living system reference