Gate Operations

This guide covers the day-to-day procedures for processing gate transactions in the Turqoa Command Center. Gate operators review AI-driven transaction decisions, handle exceptions, and ensure smooth truck flow through terminal gates.

Gate Operation Procedures

Each gate transaction follows a standard lifecycle:

1. Truck arrival --- A truck enters the gate lane and triggers the camera system.
2. AI processing --- Turqoa captures images, runs OCR, detects damage, and queries the TOS.
3. Decision --- The Decision Engine evaluates all data and produces one of three outcomes:
   • Auto-approved --- High confidence. Transaction completes without operator involvement.
   • Referred --- Medium confidence or rule trigger. Routed to operator for review.
   • Auto-rejected --- Clear policy violation (e.g., expired appointment, active hold).
4. Operator action (if referred) --- The operator reviews and approves, rejects, or escalates.
5. Gate signal --- The gate barrier opens (approved) or remains closed (rejected).

Transaction States

Transaction Review Workflow

When a transaction is referred to you, the Command Center displays:

1. Camera images --- All captured angles (front, left, right, top, rear)
2. OCR results --- Detected license plate, container number, and chassis ID with confidence scores
3. TOS match --- Appointment details from the TOS, highlighting any mismatches
4. AI flags --- Specific reasons for referral (low OCR confidence, damage detected, hold active)
5. Decision recommendation --- The AI's suggested action with reasoning

Review Checklist

• Verify the container number matches the OCR read. Check all four sides if available.
• Confirm the license plate is readable and matches the appointment record.
• Review any damage flags. Compare the AI-highlighted areas against the camera images.
• Check for active holds (customs, USDA, freight). These require resolution before approval.
• If the chassis type is flagged, verify it matches the expected configuration.

Making a Decision

• Click Approve to clear the transaction and open the gate.
• Click Reject to deny entry. A reason code is required (dropdown + optional free text).
• Click Escalate to route to a supervisor. Include a note explaining why.

Manual Override Procedures

Operators can override any automated decision. Overrides are logged and auditable.

Overriding an Auto-Approval

If you observe an issue with an auto-approved transaction (e.g., visible damage the AI missed):

1. Select the transaction from the Recent Transactions list.
2. Click Override > Reject.
3. Select a reason code and provide a written justification.
4. The gate signal is updated and the TOS is notified.

Overriding an Auto-Rejection

If the system rejected a transaction incorrectly (e.g., OCR misread the container number):

1. Select the rejected transaction.
2. Click Override > Approve.
3. Manually enter the correct container number or select the matching appointment.
4. Provide a justification (e.g., "OCR misread B for 8, verified visually").

Note: Override frequency is tracked per operator. High override rates may indicate a need for AI model retraining or rule adjustment. This data is available to administrators in the analytics dashboard.

Handling Exceptions

Shift Handover

A clean shift handover ensures continuity of operations.

Handover Checklist

1. Clear or reassign all items in your Referred queue.
2. Document any recurring issues (e.g., "Lane 3 left camera intermittent --- IT ticket #4521").
3. Note any active incidents in the security panel.
4. Record current gate lane statuses (which lanes are open, closed, or degraded).
5. Brief the incoming operator verbally and confirm they have reviewed the notes.