Mail, RFIs, transmittals, revisions, workflows — the record a claim is eventually built from is being filed in Oracle Aconex right now, one document at a time. Storia connects to that project, surfaces the events that may become claimable as they accrue, and posts what it finds back into the same mailbox — traced to the record it came from.
What it
reads
Storia reads Oracle Aconex through its own API, under the permissions of the user the integration is bound to. Nothing is migrated, nothing is exported, and nothing is copied into a second system of record.
Search across mailboxes by date and by field. Full thread reconstruction in order, with attachments — so a conversation that ran for six weeks reads as one sequence rather than eleven separate mails.
Search by document type and revision date. Metadata, revisions and marked-up PDFs — plus the document event log: authorization, modification, print, send and view, with the acting user, their organization and the revision it applied to.
Search by number, or by date, status and orientation. Supplementary files included, so a review that stalled is visible as a workflow state and not only as an absence of mail.
Users and groups, project-wide and instance-wide, by organization, name, title and division. This is what makes a recipient on a Storia report a real Aconex user on that project.
Exhibit A
The write-back
The analysis is posted into the project as a native Oracle Aconex mail of a dedicated type — visible and auditable to everyone on the job, inside Aconex itself, rather than trapped in another dashboard. Every finding carries the mail, document or revision it was drawn from.
Raised 17 April against A-101 Rev C. The last movement on the thread was an acknowledgement on 21 April; no response has been filed since. The roof plant deck sequence is waiting on it.
Moved on 28 April and again on 05 May, both times in correspondence. No workflow was raised against either change, so the register carries no record of the movement.
A revised fixing centre was instructed on 07 May. A-402 Rev B had been issued the day before and does not carry the change. The document event log shows no reissue and no supersession against Rev B.
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”, project 1247785203 Meridian Heights Tower, region CA1, from Storia to Commercial, Meridian JV and the Design Team, sent 11 May 2026 at 07:00, carrying three surfaced events, all marked unreviewed. Event one: an RFI unanswered for 24 days, raised 17 April against A-101 revision C with 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 of 17 April from Meridian JV, a thread of six mails to 21 April, and document A-101 revision C of 9 April. 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. On a live analysis every citation opens its source record in Oracle Aconex.
How the
write-back works
Storia posts as mail type Analysis; replies come back as Answer to Analysis. It never masquerades as project correspondence from anyone else.
Related record type, related document number, related mail id, primary issue, secondary issue and summary are written into named Aconex custom fields — so the trail survives outside the mail body.
A back-reference to the source mail makes the write-back idempotent. If an analysis already exists for a record, Storia replies to it rather than creating a second one.
Storia can register a document or supersede a revision in the register, reply to a mail with attachments, and copy a workflow template between projects.
What it
surfaces
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. The two we start with are extension of time and variation.
Configuration
Every mail in Oracle Aconex is permanent project correspondence, so Storia does not write to every record it reads. It posts once a period, into the project and mail type you choose, to recipients picked from the Aconex directory. Set per project, changed entirely in Storia.
Changed entirely in Storia. No return trip to Oracle, no re-authorization. If a post cannot be delivered, you are told.
Text alternative. The Storia web app on Settings, Integrations, Oracle Aconex, shown as Connected on region CA1, with two posts configured. A weekly analysis runs Monday at 07:00 in America/Toronto covering the previous 7 days, next run Monday 11 May at 07:00, delivered to the Aconex project Meridian Heights Tower under mail type Analysis, addressed to the Commercial group, the contracts lead and the Design Team group, all chosen from the Aconex directory. A monthly roll-up runs on the 1st at 08:00 in the same timezone and includes open events carried forward. Saving notes that this is changed entirely in Storia, with no return trip to Oracle and no re-authorization, and that if a post cannot be delivered you are told.
Connection &
data handling
The integration is bound to an Oracle user you nominate, so Storia sees exactly what that user sees. Connection is workspace-wide and restricted to company admins. An Aconex project is reachable only on its own region's host, which is why the region is part of the connection rather than a setting.
30 minutes
Your project
We connect a single project, read a past period, and post one analysis back into your own mailbox — every event traced to the mail, revision or workflow it came from, so you can open the source and check us.
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.