EPCplanner is a native desktop application with a relational database core, designed to operate reliably in remote site environments without permanent network connectivity.
Every EPCplanner module, from engineering registers to CBS and dashboards, reads and writes to the same relational database. There are no import/export bridges between modules, no file-based data handoffs and no API synchronisation overhead to maintain.
This architecture is the reason EPCplanner can deliver a consistent, auditable view across all disciplines: there is only one copy of the data.
One Project. One Database. One Version of the Truth.
Most project controls environments have data living in five or more separate systems. Reconciling them costs time, introduces errors and creates disputes.
| Data point | Spreadsheet-based environment | EPCplanner |
|---|---|---|
| Register data | Multiple Excel files held by different teams, manually consolidated at period end | Single database, updated in real time by all disciplines |
| Progress calculation | Formulae in spreadsheets, different methodologies per discipline | Consistent weighted calculation from CBS, applied uniformly |
| Period-end data | Files copied and archived manually, often amended retroactively | Freeze Guard locks all data at cut-off; no retroactive amendment possible |
| Schedule alignment | Manual update of P6 activities from summary spreadsheets | Two-way sync pushes calculated percent and remaining duration automatically |
| Audit trail | Cell-level change history, easily cleared or overwritten | Immutable audit log with non-alterable timestamps |
EPC projects are built in places without reliable internet. EPCplanner is a native desktop application that operates from a local or LAN-hosted database, with no dependency on cloud connectivity for daily operations.
Progress entry, register updates and report generation all function at full capability without an internet connection. Network access is only required to synchronise with live scheduling platforms.
EPCplanner enforces data integrity and security at the database level, not through application-layer controls that can be bypassed.
Define roles at project level. Control who can enter progress, approve data, close periods and access financial information.
Cut-off dates are enforced at the database level. No account, including administrators, can modify closed-period data.
All significant actions are logged with user identity, timestamp and change detail. The log cannot be edited or cleared.
Relational database architecture handles large register sets (tens of thousands of deliverables) without performance degradation.
Host multiple project databases on the same server installation. Scale from a single project to a full portfolio without architectural changes.
Connects to industry-standard enterprise scheduling platforms via XER import or direct database connection. Two-way progress synchronisation.
Contact us to discuss deployment options, database architecture and integration with your existing tools.
