KordBlog
Kord vs Oracle Aconex for engineering submittals
Aconex tracks transmittals and project correspondence. Kord shows what changed between revisions, with visual diffs, structured review sessions, and AI consistency checks across the whole document set.
Aconex is the document controller’s tool: transmittals, registers, correspondence, the formal owner-facing gates of a big EPC program in execution. When you’re issuing for construction, you want it, and nothing here says otherwise.
Kord is for the engineering team upstream of all that, especially early in FEED, when the design changes daily and standing up a formal common data environment (CDE) is mostly friction. Aconex can compare one PDF to its last version. It can’t diff a mixed-format package, and it won’t tell you the vessel spec and the P&ID have stopped agreeing.
You don’t need Aconex during early FEED, and if your engineers are moving faster than the CDE can log, it’s slowing them down rather than protecting them. So run the design iteration and the review in Kord, and hand Aconex the approved set when it’s time to issue formally.
How Kord and Aconex compare
| Capability | Aconex | Kord |
|---|---|---|
| Primary unit of work | Transmittals and project correspondence | The whole engineering document set |
| Status & workflow | Formal gates, transmittal registers, audit logs | Review sessions with visual diffs and grouped approvals |
| Revision compare | Single-document PDF compare with add/delete highlighting | Mixed-format package diff across PDF, Excel, STEP, text in one session |
| Cross-document consistency | Manual review across uploaded files | AI flags mismatches across specs and calculations |
| Review experience | Cumbersome under deadline; built for compliance volume | Fast package-level review with format-native diffs |
| Version control | Document register with revision letters | Forked deployments, native file sync, release snapshots |
| Best for | Owner/EPC correspondence and transmittal registers | Iterative submittal packages without content drift |
Typical Aconex workflow
- Upload revised files to the transmittal
- Update status codes and route for approval
- Compare each document against its prior version, one at a time
- No mixed-format package diff, so you hope related docs still match
- Transmittal approved with gaps in cross-document review
Kord workflow
- Edit files. Kord syncs and versions them automatically
- See exactly what changed, with visual diffs across PDF, Excel, STEP, and more
- AI cross-document consistency checks catch what humans miss
- Group a single change across every document it touches - excel, word, pdf, etc.
- Ship with full traceability, including a release snapshot and audit trail
Frequently asked questions
Is Kord an Aconex replacement?
No - it won't run the transmittal register for a billion-dollar construction program, and it isn't trying to. Kord sits upstream of document control, where the engineering team actually sees what changed, runs the review, and catches cross-document drift before a submittal goes out.
We already use Aconex for submittals. Where does Kord fit?
Between your shared drive and Aconex. Kord syncs the native files, groups the changes into review sessions, and runs the visual diffs and consistency checks; then the approved revision set gets exported or registered in Aconex.
Can Kord integrate with our existing document control?
Yes - Kord is built to sit alongside SharePoint, Drive, and document control, not replace them. The files stay where they are; Kord adds the change management and the review on top.