Plant Department ERP Blueprint for a Major Nigerian Construction Group

The Client

A foremost Nigerian construction and haulage group headquartered in Abuja with large-scale infrastructure projects and operations across multiple Nigerian states. Its plant department — the unit that owns, deploys, maintains and runs the firm's heavy equipment — sits at the operational heart of the business.

The client is anonymised in this case study. The technical detail of the engagement is shared in full.

The Challenge

The plant department operated as a business-within-a-business — owning dozens of heavy assets, deploying them across sites, hiring operators, consuming fuel, and running maintenance. But its operations were managed almost entirely on paper: fuel dockets, maintenance logs, operator attendance sheets, and handwritten deployment records.

This created structural problems that are endemic to Nigerian construction:

• Fuel diversion — with no digital reconciliation between fuel issued and fuel consumed per machine-hour, leakage was hard to detect.
• Unrecorded downtime — equipment out of service was often invisible to head office until it affected a project.
• No cost-per-machine-hour — the single most important number in plant economics was effectively unknown.
• Maintenance in firefighting mode — breakdowns were addressed reactively instead of via scheduled preventive maintenance.
• Operator productivity invisible — good and weak operators looked identical on paper.
• Job costing guesswork — project managers charged plant costs to projects using estimated averages instead of actual usage.

Leadership recognised that digital plant management was overdue, but also recognised that a build without a proper specification would just recreate the chaos inside software.

Our Approach

1. Field-Level Discovery

We ran discovery sessions at the plant yard, on active project sites, and in the finance office simultaneously. This gave us a cross-check: what was recorded on site versus what arrived at head office. Gaps in that flow became the priority requirements.

2. Business Requirement Document (BRD)

We produced a BRD covering the full plant department scope:

• Asset Register — every piece of plant, its acquisition cost, current book value, and location.
• Deployment & Utilisation — which machine is on which project, for how many hours, under which operator.
• Fuel Management — fuel issue dockets, consumption per machine-hour, variance analysis.
• Maintenance & Breakdown — preventive schedules, work orders, spare parts, downtime records.
• Operator Management — assignment, attendance, productivity scoring, and linkage to HR.
• Cost-per-Machine-Hour — the formula that combines fuel, maintenance, operator, and depreciation into a single number.
• Plant P&L — profit/loss of the plant department as an internal business unit.
• Job Costing Integration — how plant costs flow into project accounting in real time.

3. Reporting Specification

We defined the specific reports management would need: daily utilisation dashboard, weekly fuel variance report, monthly plant P&L, downtime analysis, and maintenance compliance. Each report was tied to a decision the business would make with it — a discipline that prevents "report bloat" in ERP implementations.

What Was Delivered

• Business Requirement Document (BRD) — the definitive specification for the plant ERP module.
• Data Model — entities, relationships, and key fields for assets, fuel, maintenance, and operators.
• Workflow Specifications — approvals, exceptions, escalation paths.
• Reporting Requirements — decision-linked reports for operations and finance.
• Integration Map — connections to project accounting, procurement, HR, and finance.

The Outcome

The blueprint defined a path to full plant visibility: every machine accounted for, every hour logged, every litre of fuel reconciled, every maintenance event scheduled and recorded. The foundational data model established in the BRD is what makes cost-per-machine-hour — the number that determines whether the plant department is genuinely profitable — finally computable.

Why This Case Study Matters to You

If your Nigerian business runs heavy plant — construction, mining, haulage, oil and gas services, agriculture — then plant is likely your biggest cost centre and your biggest blind spot. The methodology in this engagement is the same one applied to every Pulser deployment.

Frequently Asked Questions