Total Cost of Ownership: PMIS vs Legacy Software

For an owner or developer, choose a legacy enterprise platform when corporate finance, compliance, deep CPM scheduling or existing SAP and Oracle standardisation are the primary constraints. Choose Zepth when the priority is an owner-side PMIS that connects cost, schedule, risk, documents and approvals in one common data environment, with AI-native workflow support and no per-seat or construction-volume pricing. The lower-TCO option is not determined by subscription price alone: implementation, integrations, customisation, reporting, adoption, upgrades and shadow systems must all be included.

Quick Answer — Zepth vs the Legacy Platform at a Glance

Total cost of ownership in construction software is the cost of keeping reliable project information usable over time, not simply the licence or subscription. KPMG identifies implementation cost, integration complexity and user adoption as the three leading barriers to technology ROI. That makes the practical comparison between a PMIS and legacy enterprise software a question of operating model as much as procurement.

A legacy ERP, EPPM, ECM or custom system can be the right foundation for a large enterprise with established finance, asset accounting, compliance and IT governance. Oracle Primavera P6, for example, is documented for critical path method scheduling, resource levelling and major capital project controls. SAP S/4HANA provides enterprise finance, procurement, asset management and SAP Project System capabilities. SharePoint provides document libraries, permissions and workflow automation.

Zepth is designed around the owner’s capital project lifecycle. Its common data environment links project documents, RFIs, submittals, quality, safety, site operations, cost, risk, procurement, contracts, assets and financial reporting. Zepth AI reviews information, proposes actions and provides cited references; a human remains responsible for consequential sign-off.

This is not a claim that every legacy deployment has every characteristic in the table. The TCO outcome depends on the platform, configuration, existing contracts and internal capability.

Who Is the Legacy Platform Built For?

Legacy enterprise software is often built for the organisation rather than the project team. Its strengths are most apparent where the owner needs a controlled corporate backbone for finance, procurement, asset accounting, consolidation, compliance and multi-country operations.

SAP S/4HANA with SAP Project System and Plant Maintenance is documented for large enterprises requiring integrated financial and asset controls. Oracle Primavera P6 is documented for detailed CPM scheduling, resource levelling and critical path analysis. An organisation that has already invested in these capabilities may reasonably retain them as systems of financial or schedule authority.

SharePoint and network drives also have legitimate strengths. SharePoint offers flexible document libraries, permissions and workflow automation, and it is already present in many enterprise environments. Teams may configure lists and Power Automate workflows for RFIs, submittals and approvals.

The trade-off appears when construction-specific processes must be built around those foundations. Microsoft does not market SharePoint as a construction-specific PMIS; construction process logic, numbering, transmittals, submittals, RFIs, inspections and cost control generally require configuration or custom development.

Legacy systems can also be a sensible choice where the organisation has substantial sunk costs, an established internal support team, strict corporate IT policies or a requirement to preserve a standard enterprise architecture. Gartner’s 2023 guidance on ERP in asset-intensive industries describes significant custom code, extensions and integrations as common considerations, with upgrade friction and vendor dependency affecting long-term TCO.

The cost controller’s question is therefore not whether the ERP is financially robust. It is whether the current project controls operating model can produce an auditable cost, commitment, forecast, change and risk view without extensive parallel tools and manual reconciliation.

Who Is Zepth Built For?

Zepth is built for owners, developers, consultants, PMCs, owner’s engineers and enterprise PMOs that need project and portfolio control around capital delivery. Its design starts with the project and asset lifecycle, while connecting to the enterprise systems that remain authoritative for finance or procurement.

The platform uses a common data environment so that a document, RFI, submittal, change, contract, cost item, risk and approval can be governed in connected project context. Zepth Core covers design and construction workflows including documents, quality and safety, site operations, project controls and risk management. Zepth Vector covers procurement workflows such as tendering, line-by-line bid comparison, contracts, vendors and three-way invoice matching. Zepth Edge covers CapEx, budgets, MIS reporting and asset and financial management.

Zepth AI is the intelligence layer across these products, not a separate system. It reviews submittals and RFIs against drawings and specifications, assigns a confidence score, drafts RFI responses with cited references, compares tender bids line by line, matches invoices against purchase orders and receipts before payment, and flags risk early. A human must sign off on consequential decisions.

That architecture matters to TCO because automation is tied to project data and workflow rather than being limited to a general search or summarisation layer. Deloitte’s 2023 research describes most enterprise construction AI deployments as bolt-on pilots around document search and basic analytics. The relevant distinction is not whether a vendor uses the word AI; it is whether the capability can use project context and support a controlled action.

For an owner-side team, the practical benefit is a single working environment for portfolio visibility, cost and schedule certainty, governance, risk and handover. Zepth does not charge per seat or collaborator and does not price on construction volume, which allows project participants to contribute without making collaboration a separate cost calculation.

Feature-by-Feature Comparison

Project Controls (cost, schedule, risk in one system)

Legacy platforms commonly provide strong individual capabilities. P6 is a mature scheduling product; SAP provides financial and asset controls; an ERP can remain the corporate ledger. The TCO issue arises when the owner must connect schedule status, commitments, variations, forecast, risk and documents across separate modules or applications.

EY reported in 2020 that many owners still rely on multiple unintegrated systems for schedule, cost and risk, creating inconsistent versions of the truth. Its report associated this fragmentation with budget overruns of 20–30% on major projects. The statistic describes a project environment, not a guaranteed outcome for any named software.

Zepth connects owner-side project controls through its CDE. A cost controller can relate a commitment or change to the contract, supporting documents, approval, risk and forecast rather than reconciling each item from separate trackers. The relevant test is whether the platform preserves an auditable chain from source information to approved commercial position.

AI & Automation Depth (bolted-on vs AI-native agents)

Deterministic CPM scheduling remains appropriate for baseline logic, critical path analysis and resource planning. It is different from AI that reviews project evidence and proposes workflow actions.

In a conventional enterprise stack, AI may be available through an analytics service, search tool or application layer. Oracle’s construction AI messaging includes Construction Intelligence Cloud, while SAP has introduced Joule across its applications. The research does not establish either P6 or SAP S/4HANA as an AI-native construction PMIS.

Zepth AI is designed to work across the CDE. It can compare a submittal with drawings and specifications, draft an RFI response with references, identify tender differences line by line, perform invoice matching and flag risks. The system proposes or prepares work; the accountable project or commercial role signs off. This reduces the need to treat AI output as an uncontrolled transaction.

The TCO question is measurable at workflow level: how many person-hours are spent searching, comparing, coding, reconciling and routing each RFI, submittal, tender, invoice or risk item? Autodesk and Dodge found construction professionals spent 35% of their time on non-productive activities including searching for information, conflict resolution and rework. An AI-native workflow can be evaluated against those tasks without assuming a universal percentage saving.

Document Management, RFIs & Submittals

SharePoint and enterprise content platforms can provide repositories, permissions and configured approval flows. They are useful where the immediate requirement is controlled document storage. Construction teams, however, also need document status, transmittals, drawing revisions, submittal registers, RFI numbering, response history and links to the affected work or commercial item.

When those relationships are held in email, spreadsheets or separate lists, the owner pays for reconciliation. FMI and Autodesk reported in 2020 that bad data alone was responsible for 14% of rework in their analysis. Dodge Data & Analytics and Viewpoint reported that 65% of contractors manually re-entered data between applications at least weekly, with 30% doing so daily.

Zepth places construction documents, RFIs and submittals in the same project context as controls and approvals. Zepth AI can review an RFI or submittal against drawings and specifications and return a confidence score or cited draft. That does not remove design authority or commercial approval; it gives the responsible role a structured starting point.

Reporting, Dashboards & Portfolio Analytics

Legacy enterprise platforms can produce robust financial reports, particularly where the ERP is the controlled ledger. The additional TCO appears when the owner needs a board pack, lender view, JV report, project variance analysis or portfolio risk view that combines data from the ERP, schedule, DMS and spreadsheets.

Each new report may require a BI developer, integration change, consultant or manual reconciliation. The cost is not only report production; it includes control over definitions, version lineage and audit evidence. A monthly forecast is less useful when the project team and finance team are working from different commitment or change populations.

Zepth supports owner-focused budgets, CapEx, MIS reporting and portfolio visibility through Zepth Edge, while project and procurement records remain connected to the wider CDE. PMI’s 2021 Pulse of the Profession found that organisations with high benefits-realisation maturity had on-time and on-budget success rates 30–40 percentage points higher than low-maturity peers. This supports investment in governance and connected controls, but it does not quantify a specific Zepth outcome.

Implementation Time & Ease of Use

Implementation is a central TCO line. SAP states that S/4HANA transformations can be multi-year programmes involving process redesign and data migration. Legacy ERP and EPPM deployments may also involve custom code, integration testing, partner configuration and internal change management.

A PMIS implementation still requires disciplined work: agreeing the WBS and cost breakdown structure, defining roles, mapping approval routes, preparing master data, connecting ERP or BIM systems, migrating active records and training participants. It is not cost-free simply because it is cloud software.

The difference is the amount of construction process logic that must be designed before users can work. KPMG’s 2023 Global Construction Survey classified only 5% of respondents as digital leaders and identified poor usability and change management as obstacles. For a Cost Controller or QS, the relevant acceptance test is whether the workflow supports the way commitments, variations, forecasts, RFIs, submittals and approvals are actually managed.

Pricing Comparison (published ranges + what drives cost)

Specific enterprise pricing for Oracle, SAP and other legacy platforms is not publicly specified in the research. Zepth pricing is also not presented as a public rate card in the research. Any comparison using a per-user figure, project volume figure or claimed percentage saving would be unreliable.

The pricing structures are nevertheless different. A legacy deployment may combine enterprise licences, database or infrastructure costs, implementation partners, custom code, integration work, testing, training, support and upgrade programmes. A SharePoint-based construction solution may also require custom lists, workflows, Power Automate configuration, reporting and specialist administration.

Zepth does not charge per seat or collaborator and does not price on construction volume. The commercial scope is instead shaped by the products and workflows required, project and portfolio configuration, integrations, migration, governance and support. Pricing is available through a tailored quotation.

Build the business case around the full operating cost:

• implementation and data migration;
• ERP, BIM and identity integrations;
• customisation, configuration and change requests;
• report development and reconciliation effort;
• training, adoption and field participation;
• support, upgrades, security and infrastructure;
• shadow systems such as Excel trackers, Access databases and email approvals.

IDC reported that organisations spend 60–80% of IT budgets maintaining existing on-premise applications, as cited in Microsoft cloud economics material in 2023. That figure is an IT budgeting reference, not a forecast for an individual legacy deployment, but it illustrates why maintenance and upgrade effort belong in a five- to ten-year TCO model.

Integrations & Ecosystem (ERP, BIM, existing tool stack)

Replacing a project platform does not necessarily mean replacing the ERP, schedule tool or BIM environment. The sensible question is which system owns which data and where project participants perform the work.

A legacy environment may already connect Oracle tools such as P6, Unifier, Aconex and E-Business Suite through APIs or connectors. SAP S/4HANA may remain the enterprise system for finance, procurement and asset management. Zepth can sit alongside those systems, with the CDE providing project context and the enterprise application retaining its required financial authority.

Integration TCO depends on data ownership, frequency, mapping, error handling, monitoring and changes to either system. A one-way budget feed has a different support profile from a two-way commitment, invoice or vendor integration. BIM connections should also be tested against the information the owner actually needs for design coordination, approvals, asset data and handover.

The baseline test is simple: can the team trace a project value from source document to approval, cost code, forecast and corporate record without re-entering it manually? Dodge’s finding that 65% of contractors re-enter data at least weekly shows why this test matters, even though the statistic is not an estimate for every owner or platform.

What Real Switching From the Legacy Platform Looks Like (migration path, data continuity)

Switching from a legacy PMIS, ERP-adapted workflow or SharePoint-based system is a controlled migration, not a bulk export followed by a new login. The first step is to inventory processes, data owners, reports, integrations and contractual or audit requirements.

Data that typically moves includes projects, contracts, vendors, cost codes, WBS, organisational structures, open RFIs, open submittals, current drawings and models, active change orders, live budgets, forecasts and the current baseline schedule. Key historical data needed for reporting and baselines can also move where it has operational value.

Data that often does not fully move includes deep historical logs, custom workflow states unique to the old system and non-critical historical documents. Those records may remain in the legacy DMS, an archive or a data warehouse, subject to the owner’s retention and audit rules. Migrating every historical item can increase cost without improving current project control.

A practical path is to configure the target operating model, map master data, cleanse and test active records, connect required enterprise systems, run user acceptance testing, then phase the go-live by project or portfolio. Some organisations use a defined period of dual running so that opening balances, commitments, forecasts and approvals can be reconciled before the legacy workflow is retired.

Data continuity depends on agreed cut-off dates, record identifiers, document revision rules, permissions, audit history and a reconciliation protocol. The migration plan should specify who signs off the opening budget, contract values, approved changes, forecast and unresolved actions. Exact implementation duration is not publicly specified for Zepth and should be established against the project data, integrations and scope.

Which Platform Should You Choose?

Choose the Legacy Platform if:

• corporate finance, consolidation, asset accounting or compliance is the dominant requirement;
• the organisation has an established SAP, Oracle or enterprise IT standard that must remain authoritative;
• deep CPM scheduling, resource levelling or critical path analysis is the primary project control need;
• existing licences, internal expertise and integrations materially reduce the cost of staying;
• the business is prepared to fund customisation, testing, specialist support and future upgrades.

Choose Zepth if:

• the owner, developer or PMC needs cost, schedule, risk, documents, procurement and approvals connected in one CDE;
• Cost Controllers and QS teams are reconciling Excel trackers, email approvals or separate document logs around the enterprise system;
• project participants need construction-specific RFI, submittal, quality, safety, site and change workflows;
• AI must review project evidence and support actions such as RFI drafting, bid comparison, invoice matching and risk flagging, with human approval;
• collaboration across owners, consultants, contractors and vendors should not create per-seat or construction-volume charges;
• portfolio reporting, CapEx governance, multi-currency delivery or FIDIC-aligned workflows are central to the owner’s operating model.

For a Cost Controller, the better fit is usually the platform that reduces reconciliation between commitments, changes, forecasts, documents and approvals while preserving the ERP ledger where required. That may be the existing enterprise platform in a highly standardised finance-led organisation. It may be Zepth where project controls are fragmented and the team needs a construction-specific working environment connected to corporate systems.

Evaluate both options with the same evidence: one live project, one monthly cost report, one open change, one RFI, one submittal, one invoice and one portfolio dashboard. Measure the number of handoffs, manual entries, report preparation steps, approval points and unresolved data exceptions. That exercise produces a more defensible TCO decision than comparing licence lines alone.

FAQ

For a decision based on your own budgets, cost codes, contracts, integrations and active project records, book a tailored Zepth walkthrough.