Bring your DMS.
Keep your workflow.
PARALLAX RC® offers Model Context Protocol (MCP) connectors to the document management systems your firm already runs. No migration, no rip-and-replace — your DMS stays in place, PARALLAX RC® reads through it.
Your repository stays the system of record.
Read-only by default
The adapter holds read scopes only. Write tools require an explicit, separately provisioned grant.
No migration
Documents are never exported from the repository. Only the index, keys and seals live on the PARALLAX side.
Permissions honoured
The connector inherits your DMS access model — a matter closed to a user stays closed in retrieval.
Custody preserved
Each retrieved passage carries the repository id, version and a SHA-512 digest of the bytes read.
PARALLAX RC® as an MCP server.
The connector runs both ways. Your own agents and assistants will query the sealed corpus over MCP — every answer returning a passage, its coordinate and its digest, never a generated summary.
Query the five indexes; returns passages with coordinates.
Relations between documents: answers, supersedes, transmits.
Verify a digest and replay a retrieval.
Fetch a sealed deliverable and its manifest.
The programme is read alongside the documents.
A realtime connector to Primavera P6, and native XER import for the revisions that only exist as files. Each revision keeps its own record, so an activity date can be traced to the document that explains it.
Realtime P6 connector
Read access to the live P6 database or EPPM instance: activities, logic, baselines and progress, refreshed as the planner updates them.
XER and P6 XML import
Each submitted revision is imported as its own dated version, digested and kept — the update history stays intact instead of being overwritten.
Documents joined to activities
An activity is linked to the correspondence, instructions and records that carry its dates, so a delay can be substantiated on the page.