Instead of Accruent RedEye
Stop renting RedEye. Own your drawing-control system.
We build your drawing register around your sites, engineering reviews and handovers. We map your RedEye records, scope the archive migration and run your version through Omni by Enterprise DNA.
RedEye lists Core at US$16,000 a year, Advanced at US$48,000 and Enterprise at US$80,000. These are indicative prices, with artefact costs and final configuration affecting the quote.
- check_circleYour data in a database you own
- check_circleOpen source, no lock-in
- check_circleBuilt and run by Enterprise DNA
The RedEye bill
A drawing register inside a much larger subscription
RedEye combines engineering records with document viewing, markup and field access. Compare the features you use each week with the version your business needs to own.
An annual platform bill
Core is listed at US$16,000 a year. It includes unlimited users and groups, so the comparison starts with the platform and your document volume.
Artefact volume matters
Accruent says the first 20,000 artefacts are included, with tiered charges for additional artefacts. Confirm the total against your own archive.
Viewing and markup
Core includes mobile apps, text recognition, metadata search and onscreen drawing markup. Decide which of these your team needs in its owned version.
The Advanced step
Advanced is listed at US$48,000 a year and adds capabilities including visual metadata, drawing-tag extraction and third-party connections.
The Enterprise step
Enterprise is listed at US$80,000 a year, with custom workflows, extended storage and additional reporting and connection capacity.
Your actual quote is the comparison
The published amounts are indicative. Bring the contract, document count and workflows you use to the call so the replacement scope follows your business.
Your drawing-control desk
Current revisions, named reviewers and a clear handover history
Register
See the approved version and the work still in review
Drawing numbers, sites, assets and revision sequences stay connected. You can distinguish the latest change from the version currently approved.
- check A register grouped by site and discipline
- check Separate approved and latest revision labels
- check A full revision history with decision references
- check Questions that combine missing approvals with the assets they affect
Reviews
Make overdue reviews visible
Assign the reviewer and due date, then record their decision and evidence. Approval waits for all assigned reviewers to accept.
- check Named owners for every review assignment
- check Overdue safety-critical work surfaced together
- check Design-information references checked before approval
- check A Monday review drafted from the current records
Handovers
Know who received an older revision
A later approval does not erase the earlier handover. The register flags recipients whose recorded handover contains a superseded drawing.
- check Revision-specific handover schedules
- check Receipt evidence recorded separately from approval
- check Old handovers flagged even after acknowledgement
- check Draft cover sheets prepared from the recorded drawing list
Ownership
Keep the records and shape the questions
Your database holds original import rows, local decisions and notes. Your drawing files remain in a controlled archive referenced by the register.
- check A trial import before any records are committed
- check Repeat imports preserve existing local decisions
- check Branded revision records and design-information schedules
- check New checks and read-only views shaped around your business
Make it yours
Design your own Accruent RedEye replacement
Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from Accruent RedEye. Try it here, and we build the real one.
2. What it runs
3. Make it fit
4. Your colour
Answered from your own database
Good morning. Here is what needs you today.
We build it from the open-source base, bring your Accruent RedEye data across and run it for you.
What it looks like
Ask it like you would ask a colleague
Real answers from the demo data that ships with Drawing Control for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.
Drawing Control for Claude Code
Connected to your own database
Which drawing reviews and handovers need attention?
DW-102
- Sue ow
- Overdue review
- Ner da
- Casey North
- Ys
- 5
DW-103
- Sue ow
- No note in 14 days
- Ner da
- Mason Hill
- Ys
- 24
TX-101
- Sue ow
- Acknowledgement overdue
- Ner da
- Harbour maintenance
- Ys
- 3
TX-101
- Sue ow
- Superseded drawing in handover
- Ner da
- Harbour maintenance
- Ys
- 0
| Record is | Sue ow | Ner da | Ys |
|---|---|---|---|
| DW-102 | Overdue review | Casey North | 5 |
| DW-103 | No note in 14 days | Mason Hill | 24 |
| TX-101 | Acknowledgement overdue | Harbour maintenance | 3 |
| TX-101 | Superseded drawing in handover | Harbour maintenance | 0 |
Ask it anything
Questions across your drawing and handover records
These questions run on the fictional demo today. They show the connected records you can own and customise, without assuming what a configured RedEye report can answer.
Switching
How to switch from Accruent RedEye
A move usually involves exporting bucket metadata, mapping your fields, checking the imported records, and deciding separately what drawing files and history to retain.
- 1
Export drawing metadata
Use Accruent RedEye's Bulk CSV Tool to export bucket metadata, including the drawing records you want to bring across. Check the export against the fields your team relies on, and ask Accruent RedEye about anything your account does not expose. Native files, annotations, historical revisions and approval signatures are not covered by the metadata import and need a separately checked archive migration.
- 2
Load a trial batch
Have the export loaded into a fresh Drawing Control database, starting with a dry run before any records are imported. The importer handles RedEye's two-header CSV shape and configurable field labels. Confirm the field mapping with the people who own the drawing register, then run the import only after the trial results match the records you expect.
- 3
Check flagged records
Review the dry-run findings and resolve missing, ambiguous or changed source data before loading the batch. The importer validates the batch and holds changed source rows for reconciliation. Imported drawings start as drafts and need local review, so do not treat a successful import as approval. Check sample records, revision references and preserved source information against RedEye.
- 4
Run both side by side
Keep Accruent RedEye available while your team checks the new register against it for a short period of normal drawing reviews and handovers. Compare current drawing records, revision status, review evidence and recipient handovers, and work through exceptions before relying on the new database. Confirm any required archive migration and team controls, since the starting version is a database and Claude Code, not a web front end.
- 5
Switch off RedEye
Once the records and required workflows have been reconciled, agree a cutover point and make Drawing Control the place your team maintains current records. Keep any RedEye archive or access needed for history under your retention process. Do not switch off RedEye until you have confirmed that required native files, older revisions and approval signatures are available through the separately checked archive plan.
Where the real effort goes
Most of the work is mapping your configured field labels and review rules, then deciding which history to bring across. Current drawing records can be imported for local review, while files, older revisions and approval signatures need separate archive planning. If you have Enterprise DNA install and run your version, they handle the field mapping and import work as part of that setup.
Not ready for a call?
Get your Accruent RedEye switch plan by email
We will send you the step-by-step plan for moving your business off Accruent RedEye, what the move really involves, and how we would do it for you.
Sent. Check your inbox.
Your Accruent RedEye switch plan is on its way.
Rather talk it through? Book a call arrow_forwardThree ways to own it
Choose who builds and runs your version
Open source
Do it yourself
Free open-source code
- 1 Clone the repo and install its dependencies.
- 2 Run npm test and npm run demo.
- 3 Open it in Claude Code, Codex, OpenCode or Cursor.
- 4 Map your RedEye CSV headers, do a trial import and review the records.
Built around your business
We customise it
A scoped setup fee, then a retainer for ongoing work
- check Your drawing identifiers, sites and engineering review rules
- check Your RedEye metadata mapped and archive migration scoped
- check A web view, mobile workflow or different technology where you need it
- check Your review and handover process tested before switching
Omni by Enterprise DNA
We run it for you
One setup fee, then a monthly retainer
- check Installed and operated through Omni by Enterprise DNA
- check Your archive and business systems connected to the agreed scope
- check Backups, access controls and operating checks set up for your team
- check Someone responsible for keeping your version working as the business changes
Questions
Instead of Accruent RedEye, answered
Does the free version replace every RedEye feature? expand_more
The free version runs the drawing register, revision reviews and handover desk. Enterprise DNA scopes drawing viewing, mobile markup, archive connections and any other features you need into your custom version. We agree those requirements before you switch.
Can we bring our existing drawing history? expand_more
RedEye provides a metadata export through its Bulk CSV Tool. We map your configured field labels and bring each current drawing record across for review. Native files, historical revisions and approval signatures need a separately checked archive migration. Keep the existing system until the required history and workflows have been reconciled.
What stops someone from handing over an unapproved drawing? expand_more
The handover record accepts only current approved revisions. Approval requires every assigned review to be accepted, with evidence recorded. Safety-critical drawings also need design-information references. A qualified person still checks the actual drawing and makes the engineering decision.
What does the comparison cost? expand_more
RedEye publishes indicative annual prices of US$16,000 for Core, US$48,000 for Advanced and US$80,000 for Enterprise, with artefact costs and configuration affecting the final quote. The free register has no licence fee. Enterprise DNA agrees a setup fee and then a retainer for your customised or managed version.
Can the whole team use our version? expand_more
Yes. Enterprise DNA can set up the shared database, team access, archive controls and screens your roles need. The starting version works for an operator managing the drawing desk. We test the team workflow, backup and recovery before operational use.
Bring the RedEye bill and a drawing register
Book 30 minutes with Sam. We look at the subscription, the review and handover work your team does, and the archive history you need to keep. You leave with a clear scope for your own version.
Drawing Control for Claude Code is free and open source, published by Enterprise DNA.
Done paying for Accruent RedEye?
Get your version built