SHERPA v. Nifty Project Comparison – Excel Data Download

SHERPA vs. Cyprium: Cost Analysis of the Nifty Copper Project

Cyprium Metals has positioned the restart of its Nifty copper project in Western Australia as a low-capex, quick-turnaround brownfield development. The company reports capital costs of A$402 million and operating costs of A$57.10 per tonne—figures that suggest a streamlined execution strategy leveraging legacy infrastructure and existing processing facilities.

But how do these numbers compare to a standardized, independent estimate?

In this analysis, Costmine Intelligence used SHERPA—our proprietary cost modeling software—to replicate the project’s assumptions and calculate capital and operating costs based on current market rates, location-adjusted inputs, and a fully scoped cost framework. SHERPA integrates labor, materials, equipment, energy, and indirect costs—including categories often excluded from early internal estimates such as construction management, owner’s costs, and escalation allowances.

The result: SHERPA estimates total capital costs at US$561 million, a significantly higher figure driven by the inclusion of indirects and contingency. On the operating side, SHERPA produced a cost estimate of US$53.04 per tonne—lower than Cyprium’s—but reflecting a more comprehensive breakdown of site-level expenses.

This comparison highlights the importance of benchmarking brownfield restart budgets against independently modeled data. Underestimating indirects, or assuming full usability of legacy assets, can create material blind spots in financial planning.

Fill out the form to access the full Excel file, which includes:

  • Line-by-line SHERPA capital cost outputs

  • Operating cost breakdown by category (labor, energy, maintenance, etc.)

  • Direct comparisons with Cyprium’s disclosed figures

  • Assumptions used for both SHERPA and Cyprium models

  • Currency conversions and escalation logic

  • Life-of-mine cumulative cost comparisons

Whether you’re a developer, consultant, or investor, this file provides a detailed view of what it really costs to bring a brownfield asset like Nifty back into production—and how internal estimates measure up to independent benchmarks.

Download the SHERPA v. Nifty Excel Data File

Submit your information to receive a free copy of Costmine Intelligence's SHERPA v. Nifty Excel Data File.

This field is for validation purposes and should be left unchanged.
Name(Required)

Want to learn more about Costmine Intelligence and how we can help you streamline your with your mining data needs?

Request a demo with a member of our team to get a personal assessment and discover what tools and data meet your needs.

Chris Berry

Vice-President Sales

Request a Demo

Related Insights

Content

Burke Hollow Marks a Major Milestone for U.S. Uranium Supply

UEC’s commencement of production at Burke Hollow reflects a growing push to establish domestic uranium supply as a cornerstone of U.S. energy security. As nuclear power gains renewed policy support and demand for domestic fuel supply grows, Mining Intelligence continues to track how production milestones are reshaping the competitive landscape for North American uranium.

Content

Watch: Building Better Mine Cost Models with WOODY

Building reliable mine cost models requires more than high-level assumptions. This webinar shows how WOODY uses first-principles engineering and real-world data to benchmark CAPEX, OPEX, and production across copper and gold assets.

Content

Enhancing Cost Estimation and Analysis with Machine Learning

Mining cost estimation is becoming more complex as data, inputs, and assumptions continue to evolve. This talk explores how machine learning enables faster CAPEX and OPEX analysis, improves benchmarking, and supports better project evaluation.

Free Data and Insights Delivered Directly to Your Inbox

Sign up for our newsletter to get regular updates on our products, along with free data, recommended posts on our Insights channel, and special opportunities.

This field is for validation purposes and should be left unchanged.
Name(Required)