Dangote Cement Engineering Research Competition 2026: Eligibility, Tracks, Prizes and Deadline

Dangote Cement Engineering Research Competition 2026: Eligibility, Tracks, Prizes and Deadline
Dangote Cement Engineering Research Competition 2026: Eligibility, Tracks, Prizes and Deadline

The Dangote Cement Engineering Research Competition 2026 is an industry-based research challenge for Nigerian undergraduate engineering students, sponsored by Dangote Cement Plc and organised by the Academic and Research Board (ARB) of the University of Lagos Engineering Society (ULES). Teams of two to four students pick one of four challenge tracks, diagnose a real cement manufacturing problem and pitch a solution. The prize fund is 1,500,000 naira and registration closes on 16 July 2026.

That is the whole thing in a paragraph. The rest of this page covers eligibility, what each track actually asks for, what you have to submit, how the prizes split, and what tends to separate a winning deck from one that gets polite applause.

Key facts at a glance

DetailInformation
Official nameDangote Cement Plc Undergraduate Industry-Based Engineering Research Competition
Also calledDCP University Engineering Challenge
SponsorDangote Cement Plc
OrganiserAcademic and Research Board (ARB), University of Lagos Engineering Society (ULES)
Who can enterCurrently enrolled undergraduate engineering students in Nigeria
Team size2 to 4 members
Challenge tracks4 (choose one)
Total prize fund1,500,000 naira
Registration deadline16 July 2026
How to registerOfficial DCP University Engineering Challenge registration portal

What the competition is

The full name is the Dangote Cement Plc Undergraduate Industry-Based Engineering Research Competition, which nobody says out loud. Most students call it the DCP University Engineering Challenge.

The format sits closer to a consulting pitch than to a hackathon. Each team picks one of four tracks, diagnoses the problem behind it, and produces a research deck arguing for a specific solution. The argument has to work on two levels at once. The engineering must be sound, and the business case must hold up in front of people who run plants for a living and think in tons, downtime hours and naira per ton.

Most student teams underestimate the second half. A clever technical idea with no cost estimate reads as a class project, and a cost saving with no feasibility check reads as a guess.

Why the problems come from cement plants

Dangote Cement runs plants at Obajana, Ibese, Gboko and Okpella. The four challenge briefs come out of those operations rather than out of a textbook. Somebody inside the company is already losing sleep over kiln fuel costs and unplanned mill stoppages, and the competition points academic engineering work at those same problems.

That makes this a rare brief for an undergraduate. Most student research ends in a bound project nobody outside the department reads. This one ends in a pitch to people who could pilot the idea.

Who can enter

Eligibility is straightforward:

  • Every member must be a currently enrolled university student studying an engineering discipline
  • Teams must have between two and four members
  • Multidisciplinary engineering teams are encouraged
  • Each team selects one of the four challenge tracks
  • Each team submits original work only, and presenting another team’s work is grounds for disqualification

No prior cement industry experience is required. Each track brief carries the context you need, and nobody expects a 300-level student to already know what a thermal substitution rate is.

On the multidisciplinary point, “encouraged” is doing quiet work in that sentence. Look at the deliverables. Someone has to build a model or dashboard. Someone has to write a business case with assumptions and risks. Someone has to stand in front of judges and defend the numbers under questioning. Those are rarely the same person. A team of four mechanical engineers can enter and can win, but it will spend a week teaching itself things a computer engineering classmate already knows.

What teams must submit

Each team develops a research deck for its chosen track. The submission includes:

  1. A 10-slide executive presentation
  2. A technical appendix, model or prototype where applicable
  3. A one-page business case covering value, cost, assumptions and risks
  4. A roadmap with immediate, short-term and medium-term actions
  5. A risk and safety assessment for the proposed solution
  6. A statement of assumptions and data limitations

Teams skip that last item, and skipping it is a mistake. You are solving a real plant problem without access to real plant data, so you will have to assume things. Writing the assumptions down does not weaken the deck. It shows the judges you know which parts of your case would need testing before anyone spends money.

A team that says “we assumed 15 percent moisture content on incoming biomass, and here is what happens to our payback period if it turns out to be 25 percent” looks far more credible than a team presenting one confident number with no working shown.

The 10-slide pitch structure

The recommended structure for the executive presentation:

  1. Challenge selected and why it matters to DCP
  2. Current-state problem diagnosis
  3. Data and exhibit insights, plus key assumptions
  4. Root-cause hypothesis
  5. Proposed engineering and business solution
  6. Technical feasibility and operating concept
  7. Business case and expected impact
  8. Risk, safety, sustainability and mitigation plan
  9. Roadmap and resources required
  10. Final recommendation and pilot proposal

Ten slides is not much room. Read the outline again and notice that four of the ten slides come before you reveal your solution. The structure is built around diagnosis. Teams that jump to the answer by slide three, then spend the rest of the deck describing it in loving detail, are answering a question nobody asked.

The four challenge tracks compared

All four tracks are weighted equally, so there is no tactical advantage in the choice. Pick the one that matches the disciplines actually sitting in your team.

TrackCore problemBest-fit disciplinesMain output
1. Alternative fuel sourcing and pricingGetting cheap, consistent alternative fuel to the kilnsChemical, mechanical, civil and environmentalFuel opportunity map and sourcing model
2. Predictive maintenance and reliabilityEquipment failing without warningMechanical, electrical, mechatronics, computerRisk-scoring model and dashboard
3. Cement production conversion gapClinker available, cement targets still missedMechanical, chemicalConversion-loss bridge and loss tree
4. Digital KPI automation and data qualityManual reporting that is late, inconsistent and untraceableComputer, systems, electrical and electronicKPI data model and exception dashboard

Challenge 1: Alternative fuel sourcing and pricing optimisation

Dangote Cement wants to burn more alternative fuel in its kilns and less of the expensive stuff. The obstacles are sourcing, cost, consistency of quality, logistics and handling, which is a polite way of saying that a truckload of agricultural waste is not a barrel of oil and does not behave like one.

Your job is to identify alternative-fuel streams that actually exist in Nigeria, then design a sourcing model that gets them to selected plants reliably, safely and at a competitive price.

Why it matters to DCP: it moves the thermal substitution rate (TSR), controls fuel cost, cuts CO2 and supports the circular-economy case. The track is most relevant where TSR sits below target and where availability or price kills the substitution business case.

Deliverables for this track:

  • Alternative-fuel opportunity map by location and fuel type
  • Cost-per-ton and basic energy-value comparison
  • Top three recommended fuel options with justification
  • Pilot roadmap, risk register and mitigation plan
  • Business case showing expected value to DCP

The trap: picking a fuel because it sounds good rather than because it exists in volume near a plant. Rice husk near Okpella is a different proposition from rice husk in the abstract.

Challenge 2: Predictive maintenance and reliability early-warning system

DCP plants run crushers, raw mills, coal mills, kilns, cement mills and packing equipment. When one fails without warning, everything behind it stops. Repeat stoppages quietly eat throughput and cost performance across the year.

The task is to design a practical early-warning model that predicts or flags high-risk equipment before a major failure.

Why it matters to DCP: reliability is a permanent operational priority. A working early-warning system helps maintenance teams decide what to inspect first and pushes them toward real root-cause analysis instead of repeated quick fixes.

Deliverables for this track:

  • Reliability early-warning framework
  • Risk-scoring model with stated assumptions
  • Dashboard mock-up or prototype
  • Example maintenance escalation workflow
  • Plant-use roadmap

The trap: the word “practical” is in the brief for a reason. A model that depends on sensor data nobody currently collects is not practical. Build for the data a plant plausibly has, then be explicit about what extra instrumentation would improve the model later.

Challenge 3: Cement production conversion gap

The least obvious track and, for the right team, the most interesting. A plant can have clinker available, can record reasonable clinker production, and still miss its cement production target. Where does the output go?

Teams have to diagnose why clinker does not always convert into cement, then build a conversion-loss bridge separating rate, runtime, feed, additives, packing, dispatch and planning constraints.

Why it matters to DCP: people instinctively blame the kiln, and the kiln often is not the problem. Cement output depends on mill availability, grinding rate, product mix, additive supply, silo space, packing capacity, dispatch readiness, power availability and production planning. Any one of them can be the binding constraint on a given day.

Deliverables for this track:

  • Clinker-to-cement conversion framework
  • Loss tree or loss-bridge template
  • Dashboard mock-up for the daily plant review
  • Root-cause hypotheses for typical conversion losses
  • Action plan with a named owner for each system

If your team enjoys working out where a system quietly leaks, this is your track.

Challenge 4: Digital KPI automation and data quality

Plant-performance reporting at DCP runs on daily, monthly and year-to-date KPI data. When the reporting is manual, it arrives late, templates drift apart, numbers go missing and nobody can trace a figure back to its source.

The task is to design a digital KPI reporting and validation concept that improves data quality, surfaces exceptions and gives management something it can act on.

Why it matters to DCP: better data means faster reporting, fewer manual errors, standard KPI definitions and a comparable view across Obajana, Ibese, Gboko and Okpella.

Deliverables for this track:

  • KPI data model and reporting workflow
  • Validation rule library
  • Exception dashboard or wireframe
  • Plant sign-off and escalation process
  • Roadmap using Excel, Power BI, Power Apps, Python or another suitable tool

The trap: designing something beautiful that assumes a plant will throw away its existing tools. The validation rule library is quietly the heart of this track, because rules are what turn a spreadsheet full of numbers into data somebody is willing to sign.

Prizes

The total prize fund is 1,500,000 naira, awarded to the top three teams at the end of the challenge.

PositionPrize
1st place700,000 naira and a certificate
2nd place500,000 naira and a certificate
3rd place300,000 naira and a certificate

The organising team will confirm prize details before the final pitch, so treat the figures above as the published position rather than the last word.

Split four ways, first place works out at 175,000 naira per person. Useful, not life-changing. The bigger return for most students is a piece of work they can walk an interviewer through, in front of engineers who actually run cement plants.

How to register

Register through the official DCP University Engineering Challenge registration portal. You indicate your chosen challenge track during registration.

Registration closes on 16 July 2026. Late entries will not be accepted.

Before you open the form, settle three things: who is on the team, which single track you are entering, and roughly what direction the research will take. You do not need a finished idea to register. You do need to stop debating tracks, because a team that registers for predictive maintenance and then spends two weeks quietly wishing it had picked alternative fuels rarely produces much.

Make sure everyone understands the originality rule as well. Presenting another team’s work gets you disqualified.

How to build a deck that wins

None of this is in the official brief. It is what tends to separate a deck that wins from one that gets polite applause.

Start from the problem rather than from the tool you already know. Plenty of teams will decide in the first meeting that the answer is machine learning, then go looking for somewhere to put it. Judges who run plants can smell that from the second slide.

Get at least one number that is real. Everything in your business case will be an estimate, but the estimates need an anchor you can defend when a judge asks where it came from: a published fuel price, a plant capacity figure from an annual report, a documented failure rate from a comparable industry. One well-sourced anchor number does more for your credibility than five confident guesses.

Choose a scope you can cover in ten slides. “A predictive maintenance system for the plant” is not a scope. “An early-warning risk score for the raw mill and the coal mill, built on data the plant already logs” is a scope. A narrow proposal you have thought through beats a broad one you have only sketched.

Decide who is presenting early, and make sure it is somebody who helped build the model. The presenter has to defend the numbers under questioning, which goes badly for anyone handed the slides the night before.

Write the safety section like an engineer rather than a compliance officer. If your alternative fuel introduces a dust explosion risk, say so, then say what you would do about it. People who work in cement plants will notice whether you have thought about handling and storage.

Finally, say what you do not know. The statement of assumptions and data limitations is both a required deliverable and your best chance to sound like a professional. Every real engineering proposal contains one, because every real proposal is built on incomplete data.

Frequently asked questions

Who is eligible for the Dangote Cement Engineering Research Competition 2026?

Currently enrolled undergraduate engineering students at Nigerian universities. Teams must have two to four members and every member must be studying an engineering discipline.

When does registration close?

Registration closes on 16 July 2026. Late entries will not be accepted.

How much is the prize money?

The total prize fund is 1,500,000 naira: 700,000 naira for first place, 500,000 for second and 300,000 for third, each with a certificate.

Do I need cement industry experience to enter?

No. Each challenge track brief provides the context you need, and no prior cement industry experience is required.

Can students from different departments team up?

Yes. Multidisciplinary engineering teams are encouraged, and the deliverables tend to reward them.

How many challenge tracks can a team enter?

One. Each team selects a single track at registration, and all four tracks are weighted equally.

What happens if two teams submit similar work?

Every submission must be original. Presenting another team’s work is grounds for disqualification.

Who organises the competition?

Dangote Cement Plc sponsors it. The Academic and Research Board (ARB) of the University of Lagos Engineering Society (ULES) organises it.


Should you enter?

Ten slides, a business case, a prototype and a closing date this week is a lot to take on mid-semester. Some teams should skip it, and they are usually the ones hoping to pull four strangers together on Tuesday and produce something serious by Thursday.

If you already have two or three people you have built something with before, and one of the four problems above made you think “I know roughly how I would start on that”, the trade looks good. You get an industrial problem with real constraints, a hard limit on how much you are allowed to say about it, and a room full of people who can tell you whether the idea survives contact with a plant.

Registration closes on 16 July 2026 through the official portal.

APPLY HERE

0 Shares:
Leave a Reply

Your email address will not be published. Required fields are marked *

You May Also Like