OQBI Oman — Visitor Management Deployment
Host-initiated visit workflow with clinic + HSE clearance, Azure SSO, security-gate integration and four visit types across OQBI's two buildings.
OQBI — Oman
OQBI (OQ Base Industries) operates Oman's integrated petrochemicals platform — methanol, ammonia and LPG — from a two-building headquarters where visitor flow, contractor access and material / vehicle movement need to be controlled, traceable and aligned to industrial-site HSE practice. Visitor records, host approvals and access decisions need to live under the operator's identity and security controls, with an audit trail that survives personnel changes and clears the GCC data-handling review.
The Zeour stack at OQBI — Oman
Zeour visitor management custom-built for OQBI's operating model across both headquarters buildings. The flow is host-initiated — the host creates a visit in the system, the visitor receives a secure link and fills in their own details before the approval chain runs. Four visit types route through type-specific workflows: General Visit for meetings and advisory, Performing a Task for contractor work, Material Gate Pass for inbound / outbound material movement and Vehicle Gate Pass for vehicle entry and exit. Every visit routes through OQBI's clinic / healthcare questionnaire and HSE-trainer sign-off where the visit type requires it, with email notifications at every step of the approval chain. Microsoft Azure SSO drives staff login through OQBI's corporate identity — no separate password store, no shadow user directory. Security-gate access integration propagates approved visits to the gate-control system so the security supervisor sees today's approved arrivals in real time. Six-role RBAC scoped per building covers Supervisor, Host, Administrator, Clinic, HSE Trainer and Security Supervisor — each role sees and acts on exactly the slice of the workflow they own. Full audit trail with denormalised actor snapshot on every state change.
Phased engagement — Discovery → Build → Pilot → Roll-out → Operate
Discovery on-site at OQBI's headquarters mapped the four distinct visit workflows — general visits, contractor tasks, material gate passes and vehicle gate passes — and the approval chain for each, including OQBI's clinic / healthcare questionnaire and HSE-trainer sign-off rules. The fixed-fee Statement of Work covered the platform, the Azure SSO integration, the security-gate access integration, the six-role RBAC matrix and the two-building scoping model. Build delivered the host-initiated visit flow, the four type-specific approval chains, the clinic + HSE clearance step, the email-notification routing, the Azure SSO connection and the security-gate handoff in a milestone-fixed wave. Pilot week paired Zeour engineers with the host, clinic, HSE and security teams across both buildings; feedback drove configuration tweaks (questionnaire fields, role permissions, notification cadence) without code changes. Cutover landed building-by-building. Operate runs on OQBI's own IT team — OQBI controls the platform end-to-end.
Operational outcomes the deployment enabled
Visitor flow at OQBI is now controlled, auditable and on-policy by default. Host-initiated visits eliminate the historical email-plus-spreadsheet pattern — every visit is created, approved and tracked in one system. The clinic / healthcare questionnaire and HSE-trainer sign-off run inline before any visit is approved, so industrial-site clearance is part of the workflow rather than a parallel email thread. The four visit types route through their own approval chains, so a contractor performing a task triggers a different clearance set than a general meeting visitor, a material movement, or a vehicle entry. Material and Vehicle Gate Passes are now first-class records with full audit history. Azure SSO removes the parallel password store and brings every staff action under OQBI's corporate identity. The security-gate integration means the gate sees the same approval state as the system — no manual gate-list reconciliation. Six-role RBAC scoped per building means each function (Clinic, HSE Trainer, Security Supervisor, Host, Administrator, Supervisor) sees exactly the slice of the workflow they own across both headquarters buildings.
Zeour solutions in production at OQBI — Oman.
What this deployment delivered.
Type-specific approval chains across both headquarters buildings.
Staff log in via OQBI's Azure SSO; no separate password store.
Supervisor, Host, Administrator, Clinic, HSE Trainer, Security SV — each scoped per building.
Other production references close to this one.
Ranked by overlap on industry, country, region, and shared solutions deployed.
Talk to the engineers who shipped this.
A 30-minute scoping call to walk your operational profile against this reference, then a fixed-fee Discovery price by the end of the call.
Glossary — concepts in this deployment
Definitions for the operational terms behind this case. Open any chip for the full entry plus its cross-links across the site.