Documentation and support

EPCplanner integrates with scheduling platforms through two pathways: XER file import for universal schedule intake (compatible with any platform that exports a standard XER file), and direct database connection supporting Oracle EPPM, SQL Server and standalone SQLite deployments. The two-way connection both reads the schedule and writes actual progress, dates and remaining duration back to the live project.

No. EPCplanner is not a scheduling replacement and not an attempt to move CPM logic out of the scheduling tool. The master schedule remains in the scheduling platform, holding the Level 3 CPM logic. EPCplanner carries Level 4/5 operational detail, individual engineering documents, purchase requisitions and subcontract deliverables, linked back to the relevant Level 3 schedule activities. The master schedule stays clean and manageable while EPCplanner feeds summarised progress back through two-way synchronisation.

No. EPCplanner is a native desktop application designed for offline and LAN operation. All core functions, register updates, progress entry, CBS calculation and report generation, operate without internet connectivity. Network access is only required when synchronising with a live scheduling platform database or connecting to a LAN-hosted SQL Server.

Once a Cut-Off Date is closed, Freeze Guard prevents actual dates, quantities and stage completions from being entered or modified for that period, from any module, by any user, including Administrators acting through normal data-entry screens. The S-curve, register status and CBS earned value reported for any closed period will read identically six months later. A correction to closed-period data requires a deliberate, logged Administrator action rather than a routine edit.

Weight Factors distribute measurable planning weight across activities or CBS items based on configured scope logic. When a CBS is in use, Weight Factors are generated automatically from the CBS-Activity distribution. Each register item's stage completion contributes proportionally to the weighted progress of its linked schedule activity. This derives physical progress from actual deliverable achievement rather than subjective percentage estimates. The same WF-based dataset drives S-curves, histograms, tabular reports, forecasting and schedule synchronisation.

EPCplanner uses an 11-role RBAC model: Admin (full system access), Project Controls Manager (approve, promote, close periods, full reporting), Project Controls Engineer (full planning plus CBS read and report generation), Planner (register and stage editing, progress entry), Commercial User (CBS import, validate, promote, invoicing, WF management), Document Controller (transmittal and distribution), Construction Manager (site diary, resource management, field progress approval), Subcontract Coordinator (package management, subcontractor progress, payment), QA/QC Engineer (inspection records, NCR tracking), Client (read-only reports and dashboards) and Viewer (read-only views and reports).

Plan Versioning is EPCplanner's controlled archive layer for schedule revisions. Every time a revised schedule is imported, it is recorded as a named, typed Plan Version: Baseline, Revision, Recovery Plan, Rebaseline, or Forecast, with its own immutable snapshot, approval lifecycle (Draft, Pending Approval, Approved, Active, Superseded) and Plan Event Log. Only one plan can be Active at any time. A Forecast plan version can never become the Active controlling plan. The Revised Cut-Off Date mechanism locks actual progress as of that date before new plan dates take effect.

Yes. EPCplanner is currently in its Pilot Phase with selected organisations. The Pilot Phase is the primary mechanism for collecting field feedback that shapes the General Availability release. Contact us to discuss a pilot deployment for your project or organisation.