Engineering data, connected.
cedX is building a smarter way to organize, connect, and access critical engineering information.
Designed for engineering teams that need confidence in their data, documentation, and decision-making.
Know which record is current. Know the plant matches.
cedX establishes one authoritative revision, tracks its lineage, and shows whether the plant still matches the approved design basis.
Clarity for the information your engineering work depends on.
Organize
Bring critical engineering information into one clear, dependable structure.
Connect
See how related information fits together across your organization.
Access
Find the information you trust, when your team needs it.
The plant changes. The record has to keep up.
Engineering information is spread across documents, systems and teams, and it changes through projects, operations, maintenance and management of change. What gets hard is not any single document. It is knowing which record is current, how records relate, and whether the plant still matches the approved design basis. That is a normal result of a facility changing over time, not a sign of poor practice.
Which record is current
Revisions accumulate across projects and management of change. Two documents can both look authoritative when nothing records which one supersedes which.
How records relate
The same instrument carries different identifiers in the Instrument Setpoint List, the DCS and the P&ID. Without alias mapping, one device reads as several.
Whether the plant still matches
Operations, maintenance and change move the plant. The approved design basis does not move with it unless something compares the two.
What design basis integrity means
The design basis is the approved set of values, limits and drawings a facility is built and operated to. Design-basis integrity is holding that basis in a state where it is still true and still demonstrable: one authoritative record per scope, lineage behind it, identities reconciled, and a comparison against the plant.
- One Authoritative revision per scope
- Revision lineage that shows what superseded what
- Master tags reconciled and aliases mapped
- A comparison against the plant, not a promise about it
The foundation, and the check on the plant
cedX Core works on its own. cedX Control System Integrity Verify is optional and requires Core, because a comparison needs something authoritative to compare against.
cedX Core
The foundation. Establishes one Authoritative revision per scope and tracks its lineage. Reconciles master tags and maps aliases, identifies discrepancies across the Instrument Setpoint List, Shutdown Key and P&IDs, and provides side-by-side redlines with an immutable audit trail. Documents are read and drafted beside their source for engineer review.
cedX CSIV
Optional add-on, requires Core. Compares operational source and historian data with the Authoritative record, read-only, and classifies each mismatch against lineage: Superseded, Project, Reference Only, No Record. Tracks how long each misalignment has been open and reports Coverage Rate and Alignment Rate together.
Sits beside the systems you already run
cedX is additive. It works from the systems your facility already uses and keeps the record they depend on straight. It replaces none of them.
Document control
cedX works from the controlled document set. It does not renumber, release or supersede a document on your behalf.
Management of change
Changes raised through MOC are tracked as lineage, so a revision can be read against the change that produced it.
DCS
cedX CSIV reads configured values from the control system and compares them with the Authoritative record. Read-only.
Historians
Historian data is read, never written. Comparison runs daily or on request, not as live monitoring.
Alarm systems
Alarm systems stay under your configuration control. cedX does not change alarm settings or rationalisation.
PSM suites
PSM suites keep their own documentation. cedX holds the engineering record those documents point to.
Three things a facility can then demonstrate
Once one record is authoritative and the plant has been compared against it, the arguments about which document is right stop being arguments.
Clarity of design basis
One record per scope with its lineage behind it. An engineer can name the current revision without asking four people.
Collaborative discrepancy resolution
Discrepancies are raised with their source, reviewed side by side and resolved visibly instead of in email threads.
Auditable governance
The audit trail is immutable: who reviewed what, when, and against which revision.
The boundaries are part of the product
Four things cedX does not do, stated plainly.
Engineers approve
Every drafted value is reviewed by a named engineer before it becomes part of the record.
Read-only
CSIV reads operational and historian data. There is no write path to any source.
Works alongside
Document control, MOC, DCS, historians, alarms, PSM suites and spreadsheets stay where they are.
Owned by your team
The records, the decisions and the record of who made them stay with the facility.
Confident decisions start with information you can trust.
Engineering teams rely on accurate information every day. cedX is being built to give them a clearer view of it, with engineers firmly in charge.
Built by the engineering team at JWC Solutions
Be first to see cedX.
Join the waiting list and we'll let you know when cedX is ready.
We'll only use your email to tell you about cedX.