Skip to content
Danaos
HOME/.../One Asset, Many Stakeholders: How ProjectVIEW ERP Connects Owners, Contractors, Consultants, Banks and Insurers

One Asset, Many Stakeholders: How ProjectVIEW ERP Connects Owners, Contractors, Consultants, Banks and Insurers

// Insights

A major physical asset is almost never designed, financed, built, assembled, insured and delivered by a single organization.

 

A data center may involve an Owner/Developer ProjectVIEW Owner/Developer, a General Contractor ProjectVIEW General Contractor, an Engineering Consultant ProjectVIEW Consultant, architects, designers, specialist subcontractors, equipment manufacturers, suppliers, banks, insurers, commissioning specialists and ultimately an operator.

 

A mine, offshore installation, ship, industrial plant or fabricated structure follows the same fundamental logic.

 

There is one physical asset — but an entire ecosystem of organizations around it.

 

This creates one of the most important digitalization challenges in the Build World:

 

How can all these stakeholders operate around the same physical and commercial reality without forcing every organization to use the same software?

 

This is where ProjectVIEW ERP should be understood differently from a conventional construction management application or generic corporate ERP.

 

ProjectVIEW creates the enterprise operational backbone around the physical creation of the asset, connecting project scope, time, cost, resources, procurement, contracts, production and financial transactions while allowing different stakeholders to interact with the information relevant to their responsibilities.

 

The objective is not to make the bank, insurer, architect or independent engineer operate the contractor’s ERP.

 

The objective is much more important:

 

Create one governed operational reality from which every authorized stakeholder can obtain the evidence, approvals, documents and information relevant to their role.

 

 

The Real Digital Problem: Everyone Sees a Different Version of the Same Asset

 

Large projects already operate as extended enterprises.

 

International construction contracts published by FIDIC FIDIC construction contracts formalize relationships between the Employer/Client, Contractor and Engineer. FIDIC also publishes its Client/Consultant Model Services Agreement FIDIC White Book for activities including feasibility, detailed design, construction administration and project management.

 

The digital-design ecosystem recognizes the same reality. buildingSMART International and openBIM buildingSMART openBIM focus on interoperable information exchange across owners, designers, engineers, contractors, operators and other stakeholders. Its guidance for asset owners openBIM for Asset Owners specifically emphasizes communication between project stakeholders, partners and suppliers across the lifecycle of an asset.

 

Financial institutions create another information layer. The Equator Principles Equator Principles project-finance framework are used as a risk-management framework by financial institutions involved in project finance and related financing products.

 

Engineering risk introduces another. The International Association of Engineering Insurers — IMIA IMIA represents the engineering-insurance community and promotes technical knowledge and best practice around engineering risk.

 

So the actual project ecosystem looks less like:

 

Owner → Contractor

 

and more like:

 

Owner / Developer ↔ Designer ↔ Consultant ↔ Contractor ↔ Subcontractors ↔ Suppliers ↔ Fabricators ↔ Banks ↔ Insurers ↔ Certifiers ↔ Regulators ↔ Operator

 

Yet these parties frequently operate from different systems, contracts, datasets and reporting cycles.

 

The result is often not a shortage of data.

 

It is a shortage of connected operational truth.

 

What Does ProjectVIEW Connect?

 

At the center of ProjectVIEW ERP, the physical scope and execution of a project can be structured around three fundamental dimensions:

 

Bill of Quantities — BoQ

 

What needs to be built, installed, fabricated, excavated or delivered?

 

Work Breakdown Structure — WBS

 

When and in what execution sequence should the work take place?

 

Cost Codes

 

What resources and expenditure are consumed to deliver that work?

 

ProjectVIEW connects these structures to enterprise processes including Budget Estimation, Cost Control, Procurement, Subcontractor Management, Materials and Production, Machinery, HR and Labour Productivity, Accounts Payable, Accounts Receivable and Financial Management. DANAOS describes this BoQ–WBS–Cost Code relationship as the project kernel underlying its operational model.

 

That means a change in the physical asset can be followed through its operational consequences.

 

A design revision can become:

 

Drawing Change → Quantity Change → BoQ Change → WBS Impact → Procurement Requirement → Subcontractor Impact → Resource Requirement → Cost Impact → Customer Variation → Cash-Flow Impact

 

This is considerably more powerful than simply distributing the latest revision of a drawing.

 

Internal Personas and External Stakeholders Are Not the Same Thing

 

This distinction is critical.

 

Inside the enterprise, ProjectVIEW supports operational personas such as:

 

Cost Controllers ProjectVIEW Cost Controller, Project Managers ProjectVIEW Project Manager, estimators, quantity surveyors, planners, contract managers, procurement officers, subcontractor managers, construction managers, material controllers, warehouse managers, production and fabrication managers, machinery managers, HR and labour-productivity teams, financial officers, document controllers, quality managers, HSE managers, IT teams, digital-transformation managers and C-level executives.

 

These are enterprise users.

 

But surrounding them are external stakeholders:

 

Owners, developers, engineering consultants, architects, designers, banks, insurers, suppliers, subcontractors, inspection organizations, classification societies, regulators and operators.

 

These stakeholders may not need access to the complete ERP.

 

Instead, they need controlled access to the information and workflows relevant to their responsibility.

 

That is an important architectural difference.

 

 

1. Construction and Infrastructure

 

Consider a hospital, airport, railway, bridge, residential development, industrial facility or data center.

 

The principal stakeholders may include:

 

 

This stakeholder structure is consistent with the broader contractual and open-data models promoted by FIDIC and buildingSMART.

 

Example: A Design Change in a Data Center

 

Suppose the mechanical consultant revises the cooling design.

 

A document-management system can distribute the revised drawing.

 

But the real business consequences could include:

 

  • additional equipment;
  • revised quantities;
  • changed procurement packages;
  • modifications to specialist subcontract agreements;
  • additional labour;
  • revised installation sequencing;
  • additional testing;
  • changed commissioning dates;
  • revised cost-to-complete;
  • a contractual variation;
  • a change in cash-flow requirements.

 

For the designer, it began as a technical change.

 

For the contractor, it became an execution and cost event.

 

For the owner, it became a capital-cost and delivery issue.

 

For the consultant, it became a supervision and certification issue.

 

For the bank, it may influence project monitoring or drawdown evidence.

 

For the insurer, it may alter the project’s engineering-risk profile.

 

ProjectVIEW can connect these consequences to a common operational framework instead of allowing each department to maintain an isolated interpretation of the same event.

 

ProjectVIEW’s Consultant ERP model ProjectVIEW for Construction Consultants already identifies real-time site visibility, construction documentation, design approvals, QC/QA information and change management as important elements in consultant oversight.

 

 

2. Marine and Offshore Construction

 

Marine and offshore projects are even more distributed.

 

The physical asset may be an offshore platform, subsea system, breakwater, port, jetty, pipeline, marine terminal or coastal infrastructure project.

 

The International Marine Contractors Association — IMCA IMCA membership ecosystem illustrates how broad this ecosystem is. Its membership categories include marine contractors, vessel owners and operators, offshore energy companies and developers, suppliers, manufacturers, consultants, personnel providers and training organizations.

 

The ProjectVIEW stakeholder model includes:

 

 

alongside:

 

  • EPC Contractors
  • Engineering Consultants
  • Vessel Owners / Operators
  • Subsea Contractors
  • Fabrication Yards
  • Dredging Contractors
  • Equipment Suppliers
  • Port Authorities
  • Banks
  • Engineering and Marine Insurers
  • Surveyors
  • Government Authorities

 

Example: Offshore Installation Change

 

Imagine that a subsea condition forces an engineering modification during an offshore installation campaign.

 

The consequence may be:

 

Engineering Change → Revised Work Package → Additional Vessel Days → Specialist Crew → Equipment Mobilization → Procurement → Schedule Impact → Additional Cost → Customer Variation

 

The engineering consultant needs technical traceability.

 

The contractor needs resource and cost control.

 

The E&P owner needs visibility into impact and authorization.

 

The vessel operator needs updated requirements.

 

The commercial manager needs the contractual consequence.

 

Management needs to know whether the project remains profitable.

 

ProjectVIEW’s role is not to replace specialist offshore engineering, vessel-management or survey systems. Its role is to connect the enterprise consequences of physical execution.

 

That distinction matters.

 

 

3. Mining and Quarrying

 

A mine is not simply a construction project.

 

It can simultaneously contain:

 

  • earthworks;
  • roads;
  • processing plants;
  • crushers;
  • conveyors;
  • workshops;
  • water infrastructure;
  • power infrastructure;
  • fleets of heavy equipment;
  • maintenance operations;
  • contractors;
  • long-term production assets.

 

The Global Mining Guidelines Group — GMG Global Mining Guidelines Group describes a mining community involving mine operators, OEMs, technology providers, suppliers, consultants, research organizations and other stakeholders, while its governance explicitly supports industry-wide multi-stakeholder collaboration.

 

For ProjectVIEW, the core stakeholder categories include:

 

 

surrounded by:

 

  • EPCM Consultants
  • Mining Engineers
  • Geologists
  • Drilling and Blasting Contractors
  • Heavy Equipment OEMs
  • Processing-Plant Contractors
  • Infrastructure Contractors
  • Suppliers
  • Banks and Investors
  • Engineering Insurers
  • Environmental Consultants
  • Regulators
  • ESG and assurance teams

 

Example: Processing Plant Expansion

 

Suppose the delivery of a major crusher is delayed.

 

That is not merely a procurement issue.

 

It can propagate through:

 

Supplier Delay → Installation Sequence → WBS → Machinery → Labour → Subcontractors → Commissioning → Production Readiness → Cash Flow → Project Forecast

A conventional purchasing system may identify the late purchase order.

 

A scheduling system may show a delayed activity.

 

A construction platform may expose the field issue.

 

ProjectVIEW’s purpose is to connect these realities to the enterprise’s cost, resource, contractual and financial model.

 

The ProjectVIEW Mine & Quarry Owner model Mine Owner Project Controls ERP specifically targets project controls and owner visibility, while the Mining Contractor model Mining Contractor ERP addresses contractor execution.

 

 

4. Shipbuilding and Ship Repair

 

Shipbuilding may be one of the strongest examples of stakeholder complexity.

 

A vessel under construction sits at the center of an ecosystem involving:

 

 

This is reflected contractually as well. BIMCO NEWBUILDCON BIMCO NEWBUILDCON is an international standard shipbuilding contract designed to balance the interests of shipowners and shipbuilders.

 

IACS also explains that classification societies establish and verify compliance with technical requirements covering vessel design, construction and through-life survey, linking classification directly to vessel construction, insurance, finance and trading status.

 

Example: A Classification-Driven Design Change

 

Suppose the classification society requires a modification to the machinery arrangement.

 

This can create:

 

Design Revision → Material Change → Procurement → Fabrication → Outfitting → Reinspection → WBS Change → Labour Impact → Cost Impact → Shipowner Approval → Contract Variation

 

For the naval architect, this is an engineering issue.

 

For the class society, it is a compliance issue.

 

For the shipyard, it is a production issue.

 

For the shipowner, it is a cost and delivery issue.

 

For the lender, it can affect milestone monitoring.

 

For the insurer, it may affect risk information.

 

ProjectVIEW’s Shipbuilding ERP architecture ProjectVIEW Shipbuilding ERP connects budgeting, procurement, scheduling, costing, fabrication, material consumption, labour, subcontractors, documents and production activities around the vessel. The platform also includes a stakeholder-oriented Common Data Environment for controlled distribution of designs, inspections and quality documentation.

 

That is much closer to an operational environment around the physical vessel than a standalone document repository.

 

 

5. Project-Based Manufacturing and Fabrication

 

Construction does not begin at the site.

 

Increasingly, major assets depend on project-specific fabrication:

 

  • Structural Steel
  • Modular Construction
  • MEP Assemblies
  • Process Skids
  • Pipe Spools
  • Precast Components
  • Offshore Modules
  • Marine Fabrication
  • Engineer-to-Order Equipment

 

The ProjectVIEW Project-Based Manufacturing ERP Project-Based Manufacturing ERP is designed to connect fabrication and manufacturing activities to the project for which they are produced.

 

The stakeholder ecosystem may include:

 

  • Owner
  • EPC Contractor
  • General Contractor
  • Fabricator / Manufacturer
  • Structural Engineer
  • Detailer
  • Material Supplier
  • QA/QC Team
  • Independent Inspector
  • Logistics Provider
  • Bank / Trade-Finance Provider
  • Insurer

 

Example: Structural Steel Revision

 

If the engineer modifies a structural member, the impact may run through:

 

Design → Quantity → BOM → Material Requirement → Purchasing → Cutting → Fabrication → Welding → Inspection → Logistics → Site Erection → Cost

 

The key problem is not whether each system can manage its own piece of the process.

 

Most can.

 

The key problem is:

 

Can the enterprise trace the operational and commercial consequences of the change from the physical asset all the way into cost and financial reality?

 

That is where enterprise integration becomes critical.

 

But Don’t Other Construction Platforms Already Connect Stakeholders?

 

Yes.

 

And this is important to state accurately.

 

The differentiation should not be that other systems cannot collaborate.

 

They can.

 

The more useful distinction is their center of gravity.

 

Autodesk Construction Cloud / Autodesk Docs

 

Autodesk Docs Autodesk Docs is a cloud-based Common Data Environment focused on document and data management. Autodesk identifies architects, designers, engineers, contractors, subcontractors, BIM/VDC managers, project managers, owners and fabricators among its users.

 

Autodesk also supports controlled cost-management collaboration between contractors, owners, suppliers, architects and consultants.

 

Its center of gravity is therefore strongly connected to:

 

Design + Models + Documents + Field Information + Construction Collaboration

 

That is valuable.

 

But it is not identical to operating a company’s complete transactional backbone across payroll, procurement, accounts payable, accounts receivable, machinery, enterprise inventory and corporate accounting.

 

Procore

 

Procore Financial Management Procore Construction Financial Management connects field information with project budgets, forecasting, invoicing and construction financial processes.

 

Procore also explicitly promotes integration with accounting and ERP systems and states that its ecosystem includes more than 500 integrations.

 

That architecture illustrates the distinction clearly:

 

Construction / Project Platform ↔ ERP / Accounting System

 

Procore has also expanded owner-side cost management and portfolio visibility.

 

It therefore facilitates stakeholder collaboration extensively—but its architecture commonly coexists with a separate enterprise accounting or ERP layer.

 

Oracle Aconex

 

Oracle Aconex operates strongly within the cross-organizational project information and collaboration layer.

 

Oracle’s own Smart Construction Platform documentation shows explicit synchronization between Aconex and Primavera Unifier. Oracle Smart Construction Platform integrations

 

This is highly relevant because it demonstrates that even within a major integrated construction technology ecosystem, project collaboration and project controls can remain separate architectural layers.

 

Oracle Primavera Unifier

 

Oracle Primavera Unifier Oracle Smart Construction Platform integrations addresses capital-project controls, business processes and financial workflows.

 

Oracle provides integration recipes connecting Unifier with Oracle Fusion Cloud ERP Procurement and Financials.

 

That is another important architectural example:

 

Capital Project Controls ↔ Enterprise ERP

 

Autodesk Digital Project Delivery

 

Autodesk describes Digital Project Delivery Autodesk Digital Project Delivery as a shared cloud-based approach connecting multidisciplinary data for stakeholders including owners, architects, contractors, engineers and trades.

 

Again, this addresses an important part of the problem:

 

information interoperability and project collaboration.

 

ProjectVIEW addresses another dimension:

 

How does that project reality become synchronized with the actual enterprise consuming money, labour, equipment, materials and contractual commitments to create the asset?

 

 

The Strategic Difference: Collaboration Versus Operational Orchestration

 

This is the key ProjectVIEW argument.

 

  • A Common Data Environment can tell everyone which drawing is current.
  • A BIM platform can describe the asset digitally.
  • A planning system can tell everyone when work should happen.
  • A construction-management platform can coordinate RFIs, issues and field processes.
  • A generic ERP can record purchases, payroll, invoices and accounting entries.

 

All of those systems create value.

 

But the physical asset does not experience these processes separately.

 

When something changes physically, several dimensions change simultaneously.

 

ProjectVIEW’s proposition is therefore:

 

Company-first architecture.

 

The ERP operates across the enterprise—not only inside an individual project.

 

Project-centric business logic.

 

Enterprise transactions are continuously related back to the project structures that generated them.

 

Asset-centered operational reality.

 

BoQ, WBS, resources, documents, costs and physical progress are connected around what is actually being built.

 

Stakeholder-specific visibility.

 

Different stakeholders can receive the information, approvals and evidence appropriate to their responsibilities without each stakeholder having to operate the complete ERP.

 

This creates something broader than collaboration: operational orchestration around the asset.

 

What Can Each Stakeholder Gain?

 

Owner / Developer

 

Visibility into project progress, commitments, costs, changes, contractor performance and commercial exposure.

 

Contractor / EPC

 

Integrated execution across cost, procurement, subcontractors, materials, machinery, labour, contracts, production and finance.

 

Engineering Consultant / PMC

 

More structured evidence for progress review, design coordination, certification, documentation and change management.

 

Designer / Architect / Naval Architect

 

A stronger connection between design change and downstream execution consequences.

 

Bank / Lender / Technical Adviser

 

Controlled access to evidence supporting project progress, cost evolution, milestones and monitoring.

 

ProjectVIEW does not replace the bank’s lending or risk-management platform.

 

Engineering or Marine Insurer

 

Structured project evidence around changes, progress, physical execution and documentation.

 

ProjectVIEW does not replace underwriting, engineering surveys or claims-management systems.

 

Subcontractor

 

Structured packages, progress measurement, certifications, variations and payment workflows.

 

Supplier

 

Procurement requirements, delivery status, material traceability and contractual information.

 

Auditor

 

A stronger transaction and approval trail linking operational events to their financial consequences.

 

C-Level Management

 

A consolidated view of how physical project execution is affecting enterprise profitability and risk.

 

 

One Asset. Many Stakeholders. One Governed Operational Reality.

 

The future of construction technology should not require every stakeholder to abandon their specialist applications.

 

  • Architects should continue designing in professional design systems.
  • Engineers should continue engineering.
  • Planners should continue planning.
  • Banks should continue operating banking platforms.
  • Insurers should continue using underwriting and claims systems.
  • Classification societies should continue operating their technical and certification environments.

 

The objective should be interoperability without losing operational control.

 

That is the opportunity for ProjectVIEW ERP.

 

Not everybody needs to work inside the ERP.

 

But everybody around the asset benefits when the information they receive originates from a structured, controlled and continuously updated operational system.

 

  • For the contractor, ProjectVIEW can be the enterprise operating backbone.
  • For the owner, it provides transparency.
  • For the consultant, evidence.
  • For the designer, connection between change and execution.
  • For the bank, stronger project-monitoring information.
  • For the insurer, better structured operational evidence.

 

For management, it creates something even more fundamental:

 

a continuous reality check between what the enterprise intended to build, what it planned to spend, what it actually executed and what it actually cost.

 

That is the foundation of the ProjectVIEW vision:

 

Company-first architecture. Project-centric business logic. Asset-centered operational reality. Stakeholder-specific visibility.

 

  • One physical asset.
  • Many companies.
  • Many professional disciplines.
  • Many contracts.
  • Many specialist applications.

 

One governed operational reality.

 

 

Frequently Asked Questions

 

What is stakeholder collaboration in construction ERP?

 

Stakeholder collaboration in construction ERP means allowing owners, contractors, consultants, designers, subcontractors, suppliers and other authorized parties to interact with relevant project information while the underlying operational and financial data remains controlled by the enterprise system.

 

ProjectVIEW extends this concept by connecting stakeholder information to BoQ, WBS, cost, procurement, resources, contracts and actual enterprise transactions.

 

Can ProjectVIEW ERP be used by both contractors and project owners?

 

Yes.

 

ProjectVIEW has dedicated models for General Contractors ProjectVIEW General Contractor and Owners / Developers ProjectVIEW Owner/Developer.

 

The contractor may use ProjectVIEW as its operational ERP, while the owner can receive appropriate project controls, progress and commercial visibility.

 

Can engineering consultants use ProjectVIEW ERP?

Yes.

 

The ProjectVIEW Consultant solution ProjectVIEW for Construction Consultants is designed around independent oversight, construction progress, documentation, change management and stakeholder collaboration.

 

Can banks and lenders use information from ProjectVIEW?

 

Yes, where the project owner or contractor authorizes the relevant access or reporting.

 

Banks and their technical advisers may need evidence concerning progress, costs, contracts, changes and project milestones when monitoring financed projects.

 

ProjectVIEW can help produce and structure that underlying evidence.

 

It does not replace a bank’s credit, lending or financial-risk systems.

 

 

How can insurers benefit from ProjectVIEW ERP?

 

Engineering insurers and marine insurers depend on reliable information concerning assets, engineering changes, construction progress and risk.

 

ProjectVIEW can create a more structured evidence trail around project execution, documents, changes and approvals.

 

It does not replace underwriting, engineering inspections or claims-management platforms.

 

Industry references include IMIA International Association of Engineering Insurers and IUMI International Union of Marine Insurance.

 

Does ProjectVIEW replace BIM software?

 

No.

 

BIM and engineering-design applications perform specialist design and modeling functions.

 

ProjectVIEW’s role is to connect design-related information and changes with enterprise processes such as quantities, WBS activities, procurement, production, resources and cost.

 

Open interoperability approaches such as openBIM buildingSMART openBIM remain highly relevant to this architecture.

 

Does ProjectVIEW replace a Common Data Environment?

 

ProjectVIEW includes document-management and Common Data Environment capabilities, including controlled document distribution and version management.

 

However, organizations may also integrate ProjectVIEW with specialist CDE, BIM and engineering applications depending on their technology architecture.

 

How is ProjectVIEW different from Procore?

 

Procore Procore Financial Management is strongly positioned around construction management, project execution and construction financial workflows, while supporting integration with accounting and ERP systems.

 

ProjectVIEW is positioned as the enterprise ERP itself, connecting project execution with company-wide procurement, resources, subcontractors, materials, machinery, payroll and financial transactions.

 

How is ProjectVIEW different from Autodesk Construction Cloud?

 

Autodesk Docs / Autodesk Construction Cloud Autodesk Docs focuses strongly on design-to-construction information, documents, models, collaboration and field/project workflows.

 

ProjectVIEW focuses on connecting that physical/project reality with the enterprise’s transactional and cost-management backbone.

 

The two technology categories can therefore be complementary rather than mutually exclusive.

 

How is ProjectVIEW different from Oracle Aconex and Primavera Unifier?

 

Aconex is principally focused on cross-organizational project information and collaboration, while Primavera Unifier provides capital-project and project-control processes.

 

Oracle itself provides integrations between Aconex, Unifier and Oracle Fusion ERP. Oracle Smart Construction Platform integrations

 

ProjectVIEW’s proposition is to bring project-centric business logic and enterprise transactions into a single specialized ERP environment for the Build World.

 

Which industries can use ProjectVIEW’s stakeholder model?

 

ProjectVIEW applies its business logic across:

 

Construction and Infrastructure

 

Marine and Offshore Construction ProjectVIEW Marine Contractor

 

Mining and Quarrying ProjectVIEW Mine Owner

 

Shipbuilding and Ship Repair ProjectVIEW Shipbuilding ERP

 

Project-Based Manufacturing ProjectVIEW Project-Based Manufacturing ERP

 

The physical asset changes from a building to a mine, offshore installation, vessel or fabricated structure.

 

The underlying management challenge remains remarkably similar:

 

Scope + Time + Cost + Resources + Contracts + Stakeholders + Actual Execution.

 

What is the main purpose of ProjectVIEW ERP?

 

ProjectVIEW ERP is designed to create a structured enterprise environment where the physical, operational, commercial and financial realities of complex projects can be continuously connected.

 

In simple terms:

 

What are we building? When should we build it? What should it cost? What is actually happening? What has it actually cost? Who needs to know?

 

Connecting those questions is the foundation of effective project control—and of meaningful stakeholder collaboration.

 

 

About the Author

 

Christos Emmanouilidis is a Civil Engineer and Chief Customer and Commercial Officer at DANAOS Projects Software Solutions LLC

 

His work focuses on construction cost control, industry-specific ERP, project operations and digital transformation across project-based enterprises.

Calendar