Connect commercial, programme, site, safety, supplier and information controls into one project intelligence layer. CONSTRUX does not replace leadership — it gives leaders stronger controls, earlier warnings and a defensible evidence trail.
CONSTRUX is a Groupe Nseya product with its own platform home at construxvg.com — the operating system ETABLIX runs on every engagement.
Contract obligations, payment cycles, supplier accounts, commercial registers and forecast outcomes managed transparently in one place.
Programme baselines, progress capture and Earned Value Management that shows true performance — not optimistic narrative.
Daily records, photographs, inspections and quality evidence captured at the point of work and pinned to the project record.
Model-linked project information connecting design intent, site reality and handover records across the delivery lifecycle.
HSE controls, statutory compliance, competence records and incident management with named responsibility and closure evidence.
Every potential change logged with cost, programme and risk impact before work proceeds — approved digitally, evidenced permanently.
CONSTRUX exists to serve the ETABLIX operating discipline: ownership defined, interfaces controlled, evidence kept. On integrated site-services appointments it is the project control layer; as a product, clients license the same system for their own delivery organisations.
Our platforms do not replace leadership. They give leaders stronger controls, earlier warnings and a defensible evidence trail.ETABLIX Technology products
CONSTRUX supports project-level construction intelligence; VERYX provides enterprise and portfolio-level execution visibility. Together they connect the site record to the boardroom view.
Explore VERYX →CONSTRUX runs Earned Value Management on a disciplined coding structure, so every pound and every day is traceable from requirement to closeout record. This single rule eliminates the most common site-services leak — paying for mobilised resources rather than delivered service.
| Structure | Coding |
|---|---|
| Work Breakdown | Lifecycle → system → package → deliverable → activity |
| Cost Breakdown | Budget → commitment → actual → accrual → forecast → contingency |
| Organisation Breakdown | Client owner → ETABLIX control-account owner → supplier owner |
| Location Breakdown | Project → site zone → compound/village block → asset/service point |
| Evidence structure | Requirement → submittal → inspection → acceptance → payment → closeout record |
| Measure | Meaning |
|---|---|
| PV / EV / AC | Planned value, earned value of verified work, and actual cost incurred. |
| SPI = EV ÷ PV | Schedule efficiency; below 1.00 indicates underperformance. |
| CPI = EV ÷ AC | Cost efficiency; below 1.00 indicates cost pressure. |
| EAC / VAC | Forecast final cost, and forecast overrun or underrun against budget. |
| TCPI | Efficiency needed on remaining work — tests whether the target remains credible. |
The CONSTRUX console talks to exactly the same public API as any other consumer. It holds no privileged path into the platform and is subject to the same roles, scopes and attribute rules as your own integrations.
Command-and-query over project resources. GET /v1/routes lists every endpoint — 820 of them, 39 reachable without a credential — and that list is the documentation rather than a copy of it.
RFC 7807 application/problem+json, with per-field detail where a schema rejected the body. Every response carries x-correlation-id and x-trace-id, and a command accepts an Idempotency-Key so a retried request returns the original result rather than performing the state change twice.
Bearer access tokens with a short lifetime and rotating refresh tokens, behind an MFA challenge. A public route may begin an authentication and never complete one — an invariant with a test behind it, because a demonstration endpoint once returned a working session to anonymous callers.
182 notification events across 15 categories, fanning out over email, in-app, SMS, push and WhatsApp. 31 of them are mandatory and override a recipient's preferences, because a person is entitled to be told their account was locked whatever they have muted.
It will not tell you which project ids exist. An id that does not exist and one belonging to another tenancy both answer 200 with an empty list on the generic entity read — a 404 for unknown and a 403 for forbidden would together be an enumeration oracle. That behaviour is tested, so nobody "fixes" it.
Request a demonstration and we'll walk your team through the intelligence layer on live project data — or go straight to the platform at construxvg.com.
