The two real objections to Aconex​

Cost. Aconex is priced and sold as an enterprise platform — typically a per-project or per-portfolio commitment negotiated through sales. For a mid-size contractor, a consultancy, or a single project that just needs disciplined document control, that's a heavy lift.

Data custody. On Aconex, correspondence and documents are held in Oracle's system. Getting a clean, complete export at project close — or mid-dispute — is its own exercise. Many organizations' IT and legal teams increasingly want project records to stay inside infrastructure they control.

How Kazinex Workflows approaches it differently​

Kazinex Workflows does the core document-control job — a configurable workflow engine (review / approve / acknowledge / sign steps), correspondence, transmittals, templates, and deadline reminders — but with a different data model:

The headline difference: your documents stay in your organization's SharePoint. Kazinex Workflows manages the process — the register, the routing, the audit trail, the reminders — while the files themselves live where your IT and records-retention policies already put everything else. No migration to a vendor's silo, and no export scramble at close-out.

Who this fits​

If you're a large owner mandating a single platform across dozens of contractors, Aconex's ecosystem may be a requirement you can't move. But if you're a contractor, consultant, or project team that needs proper transmittal and correspondence control without the enterprise commitment — and you'd rather keep custody of your own records — Kazinex Workflows is worth a look.

See Kazinex Workflows →

While you're evaluating the platform, the free XER Quality Checker and schedule comparison tools are a fast way to see how Kazinex handles the schedule side of project controls — no login required.

Here's an honest comparison with a browser-based alternative.

What Fuse does well​

Fuse is deep: ribbon analytics, forensic comparisons, custom metric libraries, S1//S5 schedule maturity scoring, and integration across P6, Microsoft Project, and more. If you're a large EPC running a central project-controls function with a tools budget, Fuse is a defensible choice. This isn't a "Fuse is bad" post.

Where a browser-based checker wins​

Kazinex Planner approaches the same core job — is this schedule structurally sound? — from the opposite end:

The privacy point deserves emphasis: with the free checker, the XER is parsed client-side — nothing uploads. That means you can score a subcontractor's or counterparty's programme without importing external data into your P6 environment or sending it to anyone's cloud.

Who should choose what​

• Central PMO at a major EPC, custom metric libraries, portfolio-wide forensics → Fuse still fits.
• Planner, scheduler, or consultancy that needs DCMA-grade diagnostics on demand — pre-submission QA, tender reviews, subcontractor audits → try the free route first:

Score a schedule now — free, no login, then explore the full Kazinex Planner for editing, baseline comparison, float-path analysis, and AI-assisted review.

Related: The DCMA 14-point check, explained · Open an XER without P6

Here's what to check before you submit.

The universal fundamentals still apply​

Whatever the owner's specific procedure, the structural basics are non-negotiable, and they map directly onto the DCMA 14-point check:

• No open-ended activities — every task needs a predecessor and successor.
• No negative float — a plan that can't meet its own dates fails on sight.
• Minimal hard constraints — constraint-heavy schedules read as "typed, not planned."
• Logic-driven, not date-driven — the network should compute the dates.

If a schedule fails these, no amount of regional polish saves it. Run it through a DCMA-style check first.

The GCC-specific realities​

The Ramadan calendar trap. This is the single most common regional miss. Reduced working hours during Ramadan must be modelled in the P6 calendars, not fudged with constraints or manual date pushes. A schedule that ignores Ramadan will overstate progress and understate durations across every year of the programme — and a sharp reviewer spots it immediately. Build the calendar correctly and let the logic flow through it.

Weekend and holiday conventions. Fri/Sat vs Sat/Sun weekends, plus national holidays (National Day, Eid) that differ by country, all belong in calendars — and they must be consistent across the whole schedule, not per-activity ad hoc.

Owner-specific submission procedures. Aramco's SAEP-series and equivalents at other owners specify how programmes are structured, coded, and progressed. Align WBS, activity coding, and progress conventions to the owner's procedure before submission — retrofitting later is painful.

Pre-check it in the browser first​

Before you send a programme to a GCC owner, run it through the free Kazinex XER Quality Checker — it scores the schedule against DCMA-14 and flags missing logic, negative float, hard constraints, and high-duration activities, entirely in your browser (nothing uploaded, which matters when the programme is commercially sensitive).

And when you issue a revised programme, use the free schedule comparison to produce a clean change register — exactly what reviewers ask for when they want to know what moved and why.

A real weekly update compared in the free Kazinex comparison tool: changes categorized as hard (edits), medium (progress), and soft (recalculated), with a reviewer watch-list flagging progress that went backwards and logic ties that were removed.

Kazinex is built by a team based in the region — the Ramadan-calendar and GCC-owner checks are first-class, not an afterthought. See Kazinex Planner →

Here's the short version of all 14 points, with the thresholds most reviewers apply.

The free Kazinex XER Quality Checker scoring a real P6 schedule against DCMA-14 — no login, nothing uploaded.

The 14 points at a glance​

A few of these deserve more attention than they usually get:

The ones that fail most schedules​

Point 1 (Logic). Open-ended activities are the single most common flag. Every activity except project start/finish should have at least one predecessor and one successor. Missing logic doesn't just fail a checklist — it makes float and the critical path meaningless.

Point 5 (Hard constraints). Must Finish On and Mandatory Finish constraints override logic. Reviewers read a constraint-heavy schedule as "the dates were typed in, not planned." Prefer soft constraints — or better, logic.

Point 7 (Negative float). Zero tolerance. Negative float says the plan, as modeled, cannot meet its own commitments. Fix the logic or re-baseline; don't submit it.

Point 12 (Critical path test). Add a large delay (e.g. 600 days) to a critical activity and reschedule. If the project finish doesn't move by roughly the same amount, your network is broken somewhere — usually by constraints or missing logic.

Check all 14 points before you submit — free​

You don't need a P6 license or an Acumen Fuse seat to pre-check a programme. The Kazinex XER Quality Checker scores any Primavera P6 XER export against DCMA-14 (plus GAO and best-practice checks) entirely in your browser — the file is never uploaded, so you can safely check a subcontractor's schedule without importing it into your own P6 environment.

Drop the XER, read the score, fix the flags, then submit.

For the full methodology behind each check — thresholds, severities, and how to fix each flag — see the schedule quality documentation.

What a .xer file actually is​

XER is Primavera P6's plain-text export format: a tab-delimited dump of projects, WBS, activities, relationships, calendars, and resources. Because it's text, lots of tools can read it — the question is how much of the schedule's meaning they preserve (calendars and float are where cheap viewers usually get it wrong).

Option 1: Ask for a PDF or Excel export​

Fine for a glance, useless for review. You can't trace logic, check float, or verify the critical path in a flattened export. If your job is to approve or contest the schedule, you need the network, not a picture of it.

Option 2: Import it into your own P6​

The traditional answer — if you have a license, matching versions, and you're comfortable importing an external contractor's data (with its calendars and global data) into your environment. Many planners keep a scratch database precisely for this. It works, but it's slow, and it's exactly the kind of cross-contamination risk many organizations' P6 admins prohibit.

Option 3: Review it in the browser — without uploading it​

A browser-based analyzer parses the XER locally on your machine. The Kazinex XER Quality Checker is free and requires no login: drop the file, and it parses the full network client-side — the schedule never leaves your computer — then scores it against the DCMA 14-point assessment, flags missing logic, negative float, hard constraints, high-duration activities and more, with an exportable Excel report.

That inversion matters for review workflows: you get a defensible, standards-based read on a contractor's programme before deciding whether it deserves a deeper look in P6 — with no import, no license seat, and no data leaving your laptop.

For ongoing work — editing schedules, comparing baselines, running earned-value and float-path analysis — that's what the full Kazinex Planner is for. But for the "someone emailed me an XER and I need an opinion today" problem, the free checker is the fastest route.

Related reading: The DCMA 14-point schedule check, explained.