BlueDXP × Wajeeh BI — master readiness & ecosystem

Single upgraded document — six chapters (this page) are separate from the thirteen workspace console panels inside the live app (Route, Assets, …). Chapter holds the interactive graph; use A / B / C sub-views there so nothing stacks on top of itself. Insight overlays only filter text inside chapter ③.

① Naming — no collisions

Same word “tab” caused overlap in mental models. Here is the split.

  • Chapters (①–⑥) — sections of this readiness HTML only.
  • Sub-views (A / B / C) — views inside chapter ③ (Graph vs Operations detail vs Console registry).
  • Operations phases (P1–P9) — the logistics spine (corridor intel → close-out).
  • Console panels — the right-strip panels in wajeeh-enterprise-master.html (each uses data-tab in the app — we call them panels here, not document chapters).
  • Insight overlays — filters for the coach + detail text in chapter ③ only.

Physical & contract world

Shippers, carriers, ports, customs, consignees, ERPs, TMS, FASAH, Wasl.

BlueDXP console

Map, workspace panels, Dispatch, portals — human frontstage.

Data & APIs

Lane intel, RFI, freight intent, AI proxy, feedback, intel feeds when configured.

Governance

Keys, admin, audit mindset, DPA / PDPL alignment, integration-status truth.

② Linear process map

Click a phase tile (P1–P9) → jumps to chapter ③ · B (operations detail) and selects that phase. This is not a browser tab and not an in-app console panel.

Chapter ③ — pick one sub-view (mutually exclusive)
Coach

Loading perspective…

Insight overlays (stack for depth)
Operations
Platform UI
Integration
Compliance & trust
Localization
People & RACI
KSA gov & NSW
Telematics / Wasl
Geospatial intel

A · Interactive ecosystem graph

Drag / wheel zoom · click nodes · double-click Workspace to zoom · toggle Panel orbit in the page header

B · Operations phases + evidence

P1–P9 spine. Insight overlays (above) only change this column’s detail — not the graph layout.

C · Console registry (app panels)

Right strip = data-tab in app · Left dock = map intelligence drawers — both are console panels, not document chapters.

Console panel Purpose Typical P-phases

④ Acquisition → success (built-in rail)

13 stages — same semantics as customer-journey-platform-map.html, rendered here so local file:// works without iframe blocks.

Optional full UI: open companion HTML in a second window for filters + matrix.

KSA & GCC — national systems, ports, and fleet compliance (external truth)

Summaries from public sources + what this repo actually references in code or copy. Not legal advice.

Logisti (often discussed with MAWANI): Saudi Ports Authority has advanced a unified logistics / port community agenda under initiatives reported as Logisti / PCS-style digital services (press: Zawya, Transport & Logistics ME, Container News, 2024). Use MAWANI + operator channels for your live booking and appointment rules — this product does not call Logisti APIs in-repo today.

FASAH (ZATCA NSW)

National single window for customs — declarations, brokers, sea/air/land/dry ports. ZATCA operates the ecosystem; FASAH is the trader-facing window.

fasah.sa — trade home (EN)

fasah.zatca.gov.sa — CMS / guides

Repo: MAWANI guide alert mentions FASAH manifest timing (24h / 72h) in wajeeh-enterprise-master.html ALERTS

ZATCA — customs journey

Customs procedures, SABER linkage narrative, container closure services — official help centre materials.

zatca.gov.sa — customs journey

Repo: SABER alert ties PCoC/SCoC to ZATCA verification via FASAH (ALERTS saber)

TGA & Wasl (road compliance)

Transport General Authority regulates land transport; Wasl is the national integration platform used for commercial fleet visibility and compliance (industry documentation — verify current TGA circulars).

tga.gov.sa

Industry sources describe evolving TGA data requirements (e.g. address and surveillance rules for commercial transport). Always verify the current circular on TGA before go-live.

Repo gap: no Wasl / TGA API client in this codebase — treat as mandatory integration layer for KSA road legs

MAWANI (ports)

Saudi Ports Authority — port throughput, smart-port programme, beneficiary guides referenced inside the workspace compliance dataset.

mawani.gov.sa

Repo: MAWANI Mar 2026 beneficiary guide transcribed into ALERTS + legal strip

Daleel / “Daleeli”

Often confused with homonyms: the Daleel app/platform (NIDLP / Vision 2030 sector discovery, incl. logistics news) is not the same as a port “appointment portal”. Use MAWANI / terminal operator systems for slot booking.

news.daleel.gov.sa — logistics

Repo: no Daleel API — discovery / comms only if you choose to link out

Pre-alert & appointments

Pre-arrival manifests and declarations are typically filed in FASAH / broker tools; port or terminal appointments depend on terminal operator / MAWANI workflows — not standardised inside this HTML bundle.

Readiness: design explicit adapter + SOP; map SLA to MAWANI guide timings already cited in-repo

NAFEZA (Egypt ACI)

Corridor completeness: workspace ALERTS include Egypt NAFEZA 48h ACI — relevant for Red Sea / Suez-adjacent planning.

Repo: wajeeh-enterprise-master.html ALERTS nafeza

Are we “really ready”? — evidence-based scorecard

Green = shipped in repo · Amber = partial / needs env or operator · Red = not in repo (integration program)

Continuous Wasl / Logisti / FASAH appointment ingestion, sub-metre yard geofencing, and live telematics streams are not present as turnkey server routes in this repository. The console does ship rich decision-support, intel map feeds (AISstream, OSM logistics proxy, NASA FIRMS when keys set — see api/integration-status.js), risk polygons (DANGER_ZONES in workspace), Dispatch + ePOD UX including trip state styling for backload-pending (dispatch.html class s-backload-pending), and SLA stage models including POD documentation (api/_lib/sla-engine.js).

Capability Evidence in repo Status
Workspace tabs + dock down to switchTabwajeeh-enterprise-master.htmlShipped
Dispatch command center + ePOD modaldispatch.html, /dispatchShipped
Backload / return-leg compliance UI state.tc.s-backload-pending in dispatch stylesUI pattern — rules engine not isolated as separate npm service
FASAH / ZATCA live filingReferenced in compliance copy + MAWANI alert text onlyGap — build adapter + credentials
Wasl / TGA telematics feedNo API client foundGap — fleet integrator required
Logisti / PCS port appointmentsNo API client found; MAWANI press context onlyGap
Trip-level geofencing (yards / geofence events)Map + polygons for risk zones; not per-shipment geofence enginePartial — intel vs. operational geofence
Coordinates “throughout the ride”Leaflet map patterns; DB tracking_history optionalPartial — needs device + consent + pipeline
Intel map: AIS / OSM logistics / firesops-map.html, /api/intel-feeds, integration-statusShipped when keys + proxy
SABER / KUCAS / NAFEZA corridor alertsALERTS constant workspaceShipped (knowledge)
Hosted AI + freight exchange + intent API/api/claude, /api/freight-intent, /api/rfiShipped — DB/env dependent
Lane Rate Index (M28) — live tenant rate intelligence/api/lane-rate-index, 9 HTML pages, RLS-policed lane_rate_* tables, agent tools query_lane_rate / forecast_lane_rate / explain_lane_movement / submit_lane_rate, evidence pack export with SHA-256 manifest. Wired into Quote Center, Bid Workspace, Proposal Builder, Dispatch (LRI-INT-01..17).Shipped