25+ Years of ERP Lessons Learned: Why Generic ERP Is Not Enough for Project-Based Industries

For more than 25 years, DANAOS Projects has worked with contractors and project-based organizations across construction, infrastructure, EPC, shipbuilding, marine and offshore operations, mining, quarrying, and project-based manufacturing.

 

Different industries. Different projects. Different risks.

 

However, one lesson keeps repeating:

 

 

A contractor does not simply purchase materials, employ people, operate machinery, and issue invoices. Instead, it must deliver a defined scope, against a schedule and budget, while continuously managing procurement, subcontractors, labor, equipment, production, certifications, variations, cash flow, and risk.

 

Similarly, the same principle applies to a shipyard delivering a vessel, a mining contractor managing equipment-intensive operations, or a project-based manufacturer fabricating against an engineering specification.

 

This is why DANAOS built ProjectVIEW ERP differently.

 

At the center of its business logic is the relationship:

 

BoQ ↔ WBS ↔ Cost Codes

 

The Bill of Quantities (BoQ) defines the commercial scope and budget. The Work Breakdown Structure (WBS), in turn, defines time and planned execution. Finally, Cost Codes provide the internal cost-control structure.

 

ProjectVIEW connects these dimensions so that the team can continuously evaluate operational transactions against scope, time, and cost.

 

As a result, it is not simply another place to record transactions. Instead, it creates a continuous reality check between what was estimated, what was planned, what is happening, and what it is costing.

 

Below are some of the most important ERP lessons we have learned from real project environments.

 

1. Construction & Infrastructure: The Budget Must Survive the Handover to Execution

 

The recurring problem

 

One of the biggest problems in construction is not the absence of software. Rather, it is the disconnect between systems and departments.

 

For example, estimators work with BoQs and spreadsheets. Meanwhile, planners work in Oracle Primavera P6 or Microsoft Project. Procurement manages suppliers and purchase orders. Site teams record progress and resources. Finally, Finance records transactions in the corporate ERP.

 

Each system may still perform its individual job.

 

However, the problem appears when management asks:

 

Are we actually making money on this project today?

 

In practice, the answer often requires reconciliation across several systems and spreadsheets.

 

The ProjectVIEW approach

 

ProjectVIEW maintains the relationship between the BoQ, project budget, WBS, resources, and Cost Codes from estimation into execution.

 

Therefore, the team can compare actual site transactions—including project progress, labor, machinery, materials, and subcontractors—against the project cost baseline. In addition, ProjectVIEW’s cost-control processes specifically connect BoQ budgets with Primavera and daily site transactions.

 

The advantage

 

Management gains continuous actual vs. budgeted cost and progress visibility, rather than waiting for financial reporting after the costs occur.

 

Lesson learned

 

 

2. EPC Contractors: Procurement Is Part of Project Control

 

A generic ERP usually views procurement as a transactional process:

 

Requisition → RFQ → Purchase Order → Receipt → Invoice

 

For an EPC contractor, however, that is only part of the story.

 

The recurring problem

 

In fact, project teams need to know much more:

 

First, what are we purchasing? Why do we need it? Which project and activity require it? Did we budget for it? When does the site need it? Is stock already available? What is the historical price? Could late delivery affect execution?

 

A purchase can therefore be financially correct while still being operationally wrong.

 

The ProjectVIEW approach

 

By contrast, ProjectVIEW connects procurement with the project structure.

 

For example, material requirements can originate from the BoQ and site requirements. They then continue through requisitions and supplier RFQs, quotation comparisons and purchase orders. Finally, they flow into goods receipt and inventory processes.

 

In addition, the procurement workflow includes supplier quotation comparison, historical cost information, warehouse management, subcontractor procurement, and sourcing against BoQ and WBS requirements.

 

The advantage

 

As a result, purchasing becomes part of project cost and execution control, rather than an isolated administrative function.

 

Lesson learned

 

 

---

 

3. Shipbuilding & Ship Repair: A Vessel Is More Than an Accounting Project

 

Shipbuilding and ship repair expose the limitations of generic ERP particularly clearly.

 

For instance, a vessel project can combine engineering, fabrication, work orders, procurement, inventory, subcontractors, specialized labor, equipment, client approvals, certifications, and commercial variations.

 

The recurring problem

 

The yard, production teams, commercial department, warehouse, subcontractors, and finance department can easily end up working from different views of the same project.

 

Moreover, change makes the problem more difficult.

 

For example, a newly identified repair or scope variation can immediately affect labor, materials, subcontractors, schedule, cost, and ultimately the amount charged to the client.

 

The ProjectVIEW approach

 

ProjectVIEW can operate as a Shipyard Management Information System, connecting office, yard, production, vendors, service companies, subcontractors, and clients through a common project environment.

 

In addition, its shipyard model associates operational processes with BoQ, WBS, and Cost Codes, enabling actual versus budgeted cost and progress monitoring together with change management.

 

The advantage

 

As a result, the shipyard gains yard-to-office visibility of cost, progress, resources, and project changes instead of managing production and commercial performance in disconnected environments.

 

Lesson learned

 

 

Instead, it must understand the project, production, repair, resource, and commercial dimensions simultaneously.

 

4. Marine & Offshore: Remote Operations Need One Operational Truth

 

Marine and offshore projects add another challenge: distance.

 

For example, operations may span corporate offices, fabrication yards, construction sites, vessels, and offshore locations.

 

The recurring problem

 

As a result, operational information can reach management after the event.

 

By the time actual labor, equipment utilization, materials, subcontractor performance, or progress reaches the ERP, management may already have made the operational decision.

 

The ERP then becomes a historical system of record instead of an active project-control platform.

 

The ProjectVIEW approach

 

ProjectVIEW connects field and office processes through a centralized environment, with purpose-specific web and mobile applications supporting project data capture and collaboration.

 

In addition, the wider ProjectVIEW architecture supports online and offline operations, project portfolio management, role-based access, and integration of operational processes with project cost and schedule.

 

The advantage

 

Management gains faster situational awareness across geographically distributed project operations.

 

Lesson learned

 

 

5. Mining & Quarrying: Equipment Utilization Is Cost Control

 

Mining and quarrying are highly asset-intensive operations.

 

Excavators, loaders, trucks, crushers, drilling equipment, and other machinery are not simply assets on a balance sheet. Instead, their availability and utilization directly influence operational performance and cost.

 

The recurring problem

 

Traditional ERP can tell management what machinery the company owns, its accounting value, and perhaps its maintenance history.

 

Operations, however, need different answers:

 

Where is the machine? Is it available? Which project is using it? Then, what is its utilization? What does it cost to operate? What maintenance is approaching?

 

The ProjectVIEW approach

 

ProjectVIEW Machinery Management covers machinery lists, allocation and transactions, equipment availability, cost analysis, fuel, maintenance, preventive repairs, and insurance monitoring.

 

Estimators can also assign machinery as a project resource during estimation. The team then measures it during project execution.

 

The advantage

 

As a result, equipment becomes a measurable operational and project-cost resource, not simply a fixed asset.

 

Lesson learned

 

 

---

 

6. Project-Based Manufacturing: Production and Project Control Must Speak the Same Language

 

Project-based manufacturing creates another ERP challenge.

 

The company manufactures—but not necessarily through repetitive mass production. For example, it may fabricate unique structures, components, or assemblies against project-specific engineering requirements.

 

The recurring problem

 

Manufacturing software can manage production.

 

Similarly, project software can manage projects.

 

But management needs to understand how production, materials, resources, work orders, schedules, and costs contribute to the profitability of the project being delivered.

 

So when these processes operate separately, that relationship becomes difficult to see.

 

The ProjectVIEW approach

 

ProjectVIEW brings production and fabrication planning/control into the same ecosystem as materials, procurement, warehouse operations, labor, machinery, project budgeting, and cost control.

 

DANAOS specifically positions the platform for project-based construction, production, fabrication, and related operations rather than treating production as an unrelated back-office activity.

 

The advantage

 

As a result, production and project execution operate through a common project-centric data model, improving visibility between fabrication performance and commercial performance.

 

Lesson learned

 

 

---

 

What These Industries Have in Common

 

The terminology changes from one industry to another.

 

For example, a construction contractor talks about projects and sites. A shipyard, by contrast, talks about vessels and yards. A mining company focuses heavily on fleet and production. A steel fabricator manages work orders and fabrication.

 

But underneath these differences is the same management challenge:

 

How do we continuously connect physical execution with time, resources, cost, and commercial value?

 

Therefore, across these industries, the recurring pattern is clear.

 

Construction & Infrastructure

 

Challenge: Tendering, scheduling, site operations, and financial data become disconnected.

 

ProjectVIEW approach: Connect BoQ ↔ WBS ↔ Cost Codes across the project lifecycle.

 

Advantage: Continuous visibility of actual vs. budgeted cost and progress.

 

EPC Contractors

 

Challenge: Procurement becomes disconnected from project demand, budgets, and schedules.

 

ProjectVIEW approach: Connect project requirements with procurement, suppliers, inventory, budgets, and delivery requirements.

 

Advantage: Procurement becomes an integral part of project cost and execution control.

 

Shipbuilding & Ship Repair

 

Challenge: Yard operations, production, subcontractors, materials, and commercial changes become fragmented.

 

ProjectVIEW approach: Integrate vessel projects, production, work orders, procurement, subcontractors, and cost control.

 

Advantage: Continuous yard-to-office project visibility.

 

Marine & Offshore

 

Challenge: Remote operational information reaches management too late.

 

ProjectVIEW approach: Connect distributed operations through field-to-office data capture, workflows, and centralized project information.

 

Advantage: Faster situational awareness and operational control.

 

Mining & Quarrying

 

Challenge: Asset records alone do not reveal equipment performance or utilization.

 

ProjectVIEW approach: Connect machinery utilization, allocation, availability, maintenance, and cost.

 

Advantage: Better equipment utilization and operational cost control.

 

Project-Based Manufacturing

 

Challenge: Production and project management operate in separate environments.

 

ProjectVIEW approach: Connect production, fabrication, materials, resources, schedule, and project cost.

 

Advantage: Project and production teams operate from a common project-centric data model.

 

Generic ERP Is Not Bad ERP

 

First, this distinction is important.

 

SAP, Oracle, Microsoft Dynamics, and other mainstream enterprise ERP platforms are powerful systems.

 

The problem is not that generic ERP is inadequate.

 

Rather, the problem is expecting a generic enterprise data model to understand the operational DNA of a highly specialized project-based business without extensive configuration, customization, integrations, or complementary applications.

 

ProjectVIEW, by contrast, starts from the opposite direction.

 

It starts with the project.

 

Its ecosystem covers estimation and tendering, budgeting and cost control, subcontractors, procurement and purchasing, materials and inventory, machinery and maintenance, HR and payroll, accounting and financials, accounts payable, accounts receivable, analytics, workflows, and project/site applications.

 

And choosing ProjectVIEW does not necessarily mean replacing an existing corporate ERP.

 

In fact, ProjectVIEW supports integration with third-party systems through APIs, and DANAOS designed it to coexist with mainstream enterprise platforms. ProjectVIEW-to-Oracle integration, for example, can exchange procurement, purchase orders, receipts, invoices, inventory transactions, and project-related data between the two environments.

 

For some organizations, ProjectVIEW can operate as the central ERP.

 

For others, it can become the project operations, construction management, and cost-control layer that complements the corporate ERP.

 

In other words, that creates a more useful question than simply asking:

 

“ProjectVIEW or SAP/Oracle?”

 

Instead, the better question is:

 

“Which system should perform which job?”

 

The Most Important ERP Lesson After 25+ Years

 

A project-based organization continuously converts resources into physical progress—and physical progress into commercial value.

 

Its ERP must therefore understand the complete relationship:

 

Scope → Time → Resources → Cost → Progress → Revenue

 

This, in short, is the principle behind ProjectVIEW ERP.

 

ProjectVIEW does not treat operational processes as disconnected transactions. Instead, users can evaluate them against the project’s commercial scope, execution schedule, and cost structure.

 

As a result, this creates a continuous reality check between:

 

What was estimated. What was planned. What is being executed. What it is costing.

 

And this is ultimately the difference between an ERP that records the business and an ERP that helps control the business.

 

For construction, EPC, infrastructure, shipbuilding, marine and offshore, mining, quarrying, and project-based manufacturing companies, that distinction matters.

 

Because in project-based industries, the end of the project does not determine profitability.

 

It is won—or lost—through thousands of decisions made during execution.

Related: Shipbuilding ERP Software · Marine & Offshore Construction ERP