Operate360

Bridges operational boundaries when a project requires specialised support services, managing the lifecycle across milestones (pending → amendments → approved).

1. 1A CE or CO operative submits an AppBookingRequest for a temporary road closure. The system auto-injects the tenant_id to lock data boundaries.
2. 2The system captures the entity event and runs the Notify Booking Amendments workflow, calling supervisorAlerts to send push alerts and emails to TM supervisors.
3. 3If amendments are requested, an alert routes back to the field operative with correction instructions. If approved, a fully populated Shift record is injected into the TM database.

Enforces safety rules automatically, running silent checks to prevent hazardous overwork scenarios before operatives step onto a live site.

1. 1Upon field clock-in, the system runs checkOperativeFatigue. If issues are indicated, fatigueRiskChecker computes total team variables.
2. 2If risk evaluates to high, a Notify High Risk Fatigue workflow passes a lockout command to the field device, preventing the operative from starting the job ticket.
3. 3The backend escalates via sendPushNotification to supervisors, requiring a digital sign-off override. A scheduled cron runs dailyFatigueMonitoring and over72HrsCheck at regular intervals.

Public Session Initiation

Unauthenticated users review packages on public pricing pages. Clicking purchase triggers an isolated backend function that establishes a secure checkout transaction.

Secure Hosted Checkout

The backend calculates rates server-side, returning an official hosted redirect URL. Buyers complete transactions entirely off-site in a secured environment.

JWT Webhook Verification

On payment completion, a signed webhook token is verified. The platform changes the tenant status to active and provisions access to chosen applications.