Skip to main content
Oracle Aconex integration

Claimable events,posted into Aconex.

Mail, RFIs, revisions and workflows are already filing the record a claim gets built from. Storia reads that project through Oracle’s own API, surfaces the events that may become claimable as they accrue, and posts what it finds back as native Aconex mail.

Book a demo See the write-back
  • Mail, register, workflows
  • Native Aconex write-back
  • Nothing migrated

Inside the mailbox

What Storia finds goes back where it was found.

Illustrative rendering of the posted mail, not a screenshot. Aconex chrome shown generically. Example values.

Text alternative. A Storia analysis mail posted into Oracle Aconex: mail number STO-ANL-00087, mail type Analysis, subject “Storia analysis, week of 04 May”, on project 1247785203 Meridian Heights Tower in region CA1, from Storia to Commercial, Meridian JV and the Design Team, sent 11 May 2026 at 07:00, with replies typed Answer to Analysis. It carries three surfaced events, all marked unreviewed. Event one: an RFI unanswered for 24 days, raised 17 April against A-101 revision C, the last movement an acknowledgement on 21 April, holding the roof plant deck sequence; it may support a time claim; sources are mail RFI-00214, a thread of six mails to 21 April, and document A-101 revision C. Event two: the handover date for level 12 east revised twice by mail, on 28 April and 5 May, with no workflow raised against either change; it may support an access claim; sources are mail MAIL-04471, mail MAIL-04519 and the absence of any workflow to 10 May. Event three: a cladding fixing detail instructed by mail on 7 May after A-402 revision B was issued the day before without the change, with the document event log showing no reissue; it may support a change claim; sources are mail MAIL-04502, document A-402 revision B and the event log entry.

How it works

Three moves, and the record never leaves Oracle.

01 · Read

Read the project through Oracle’s API.

Bound to an Oracle user you nominate, so Storia sees exactly what that user sees. Mail and RFIs, the register and its event log, workflows and the directory, threads reconstructed in order, with attachments.

Connection · per project
02 · Surface

Surface the events that may become claimable.

RFIs going unanswered, dates moved by mail with no workflow raised, scope instructed after a revision issued. Each event is held against the record it was drawn from.

Output · traced events
03 · Post back

Post the analysis back as native Aconex mail.

Once a period, into the project and mail type you choose, to recipients picked from the Aconex directory. A back-reference to the source keeps it idempotent, never a duplicate.

Surface · native mail

The boundary

Oracle Aconex stays the system of record. Nothing is migrated.

Data flow · one direction for truthReads continuously, posts once a period

Oracle Aconex · system of record

Mail, RFIs and transmittalsSearched by date and by field, threads reconstructed in order with attachments.
Register, revisions and workflowsMetadata, marked-up PDFs, and the document event log: who acted, from which organization, on which revision.
The record, unchangedSame project, same permissions, same system of record.

Storia · analysis only

Surface claimable eventsRead across the thread and the register, each event traced to its source record.
One mail back per periodA native Aconex mail of a dedicated type, with structured references written into named custom fields.

Reads in · surfaces the events · posts one mail backNothing migrated

Side by side

Same Aconex. Different visibility.

Dimension

Aconex alone

Aconex + Storia

Finding the evidence

The record is complete and correct. Someone still has to read six weeks of mail to find the three events that matter.

The events that may become claimable are surfaced as they accrue, each traced to the mail, revision or workflow it came from.

When you look

At claim time, months later, working backwards from an outcome.

Weekly, while the thread is still moving and the answer can still be chased.

Where the analysis lives

In whatever dashboard or spreadsheet produced it.

In the project, as native Aconex mail: visible and auditable to everyone on the job.

What moves

Nothing.

Nothing. Storia indexes to make the record searchable. Aconex stays the source of truth.

What it surfaces

Events that may support a claim for time or money.

Claim type

Extension of time

Late or unanswered RFIs, restricted access, out-of-sequence working: the events that push the completion date, and what a time claim has to establish.

Extension of time Claim type

Variation

Scope instructed by mail rather than through the change process, superseded revisions, unpriced instructions, and how a variation is valued.

Variations Reference

All claim types

The instruments, the deadlines and the evidence, plus what changes by jurisdiction. Quebec is live.

Open the library

Storia flags them; it does not decide them. Which instrument applies, whether entitlement exists and what gets served are contractual positions your claims experts take.

Connection & data handling

Bound to a user you nominate. Scoped per project.

Data flow

Aconex is the system of record. Storia reads in through Oracle’s API and posts one mail back. Nothing is exported, nothing is migrated.

Reads

Mail and RFIs, the document register and its event log, revisions and marked-up PDFs, workflows, and the project directory.

Write-back

Native Aconex mail of a dedicated type, with structured references in named custom fields. Idempotent: it replies rather than duplicates.

Cadence

Weekly or monthly, into the project and mail type you choose, to recipients from the Aconex directory. Changed entirely in Storia.

Permissions

Enforced before results are returned, not filtered afterwards. If the bound user cannot see it, no analysis can cite it.

Regions

A project is reachable only on its own region’s host, so the region is part of the connection.

  • UK1
  • CA1
  • US1
  • EU1
  • AU1
  • HK1
  • CN1
  • MEA
  • KSA1

30 minutes · your project

Connect one Aconex project. See what is in it.

Book a demo Ask a question
  • 01One project, one past period
  • 02One analysis into your own mailbox
  • 03Every event traced to its source

Oracle and Aconex are trademarks of Oracle Corporation. Storia is an independent third-party integration and is not affiliated with, endorsed by, or sponsored by Oracle Corporation. The mail view on this page is a rendering for illustration and does not reproduce Oracle Aconex’s interface.

Oracle Aconex integration · Storia