The MPA suite

One place for what happened on the shift

MPA captures what your crew saw, decided and did, and bridges your control system and your daily report. Start with the application that fixes the problem you feel most, and add the next when you're ready.

For concentrators, smelters and refineries running around the clock.

6 sites
MPA rolled out at Northern Star
100s
Of hours saved at Newmont Merian
7
Excel logsheets replaced at Pogo
2–4 wks
Typical time to go live

MPA runs on-premises in your OT network and reads from and writes back to AVEVA PI, so your data stays in your historian.

The problem

Your plant runs on a control system. Your shift runs on a spreadsheet and an inbox.

Every processing operation runs the same daily rhythm. Set the targets. Run the pre-start. Hand over between crews. Work with maintenance, metallurgy and the lab. Manage the exceptions. Get the daily report out. Then do it all again.

The control system runs the plant. The historian stores the history. The maintenance system holds the work orders. None of them were built to hold what the crew saw, decided and did in between, so that part ends up in Excel, Word, email threads, a whiteboard and the verbal handover.

What that costs you

  • Getting the data becomes the job. The numbers sit across the control system, the historian, the lab system and three spreadsheets. Someone on your technical team pulls them together by hand, every day.

  • Reporting eats your metallurgists. The hour before the production meeting goes on rebuilding numbers instead of analysing them, and errors creep in along the way.

  • Losses get argued, not fixed. Downtime is classified from memory at the end of shift. Nobody fully trusts the total, and the cause is a matter of opinion.

  • Agreements live in someone's inbox. What was agreed at the pre-start is whatever people remember, or whoever kept the email.

Each one gets you through a shift. Together, they never add up to a shared record.

Where it goes wrong

A whiteboard gets you through a shift change. It won't get you through R&R.

The cost shows up at the crew boundary, and there are two of them.

Every 8–12 hours

Shift change

The handover covers what's happening right now. What happened, what was tried and why mostly stays behind.

After 1–3 weeks on R&R

Roster change

A returning supervisor can only catch up by asking people who weren't there either. Trends, repeat failures and half-finished actions disappear.

Once what happened is captured in one place, the handover stops being a summary of the last shift. It becomes a view of what's actually been going on.

MPA screens showing live plant process visualisation
Built with industry feedback

It arrives already knowing how a processing plant runs

Metallurgists and control systems engineers shaped what's in the product: the default logsheets, the loss classifications, the calculation logic, and what a shift report needs to say at 6am. Your team isn't left to work it out in a configuration screen.

MPA comes from the same people who are in your plant doing control systems and engineering work, built for the way a processing plant actually runs.

Who it's for

Built around the people who run the shift

Processing manager

You're accountable for targets you only see after the fact. MPA and TCard give you the shift picture as it forms: what was lost, why, and what the crew did about it. The morning meeting moves on to what happens next, not what happened yesterday.

Metallurgy superintendent

Your metallurgists were hired to improve recovery, not to chase data across five systems. Capture it as the shift runs, in a consistent structure, and their time goes back into the circuit.

Operations superintendent

Handover is where things get dropped. With the readings, the losses and the open actions travelling across the crew change, your incoming supervisor isn't starting from a whiteboard, and the pre-start isn't starting from scratch.

Shift and control room operators

Your crew enters the same information in three places. MPA pulls what it can straight from the plant and gives them one place for the rest. Less typing, more time on the plant.

The MPA suite

Six applications. Start with the one you need most.

Applications that grow with your operation. Start with one, and add the next when the operation is ready for it.

Capture

MPA Logsheets

Write it down once

Operator readings and observations go straight into your PI historian alongside instrumented data. Logsheets flag values outside the normal operating range or entered against the wrong shift, and several people can work on the same logsheet at once.

Replaces: Paper logsheets, Excel logsheets and the daily upload to the historian.

Capture

MPA Production Monitor

Every lost tonne, with the reason it was lost

Downtime and slowdowns are picked up from your plant data and logged at the time. The crew classifies each event while they still know why it happened, and short stops show up alongside the big events.

Replaces: End-of-shift downtime spreadsheets and delay logs written from memory.

Coordinate

MPA Shift Handover

The handover writes itself

The handover report is generated from what the crew recorded during the shift: readings, losses and open actions. The incoming supervisor reads what actually happened, not whatever someone remembered at the end of the night.

Works with: TCard. Open actions travel with the handover, so the next crew sees what's still to do.

Part of the MPA suite
Report

MPA Production Reporting

Walk into the morning meeting with the numbers already there

Templates and calculation logic built for mineral processing: mass balance, recovery, loss attribution and reconciliation against the lab. On sites running AVEVA PI, reports are built on PI AF templates beside your plant data.

Replaces: The morning spreadsheet rebuild.

Manage by exception

MPA Digital TARP

The same response, every shift

TARPs activate and escalate against criteria you set, notify the right people by email, and show the crew the approved actions for that event. Comments and outcomes build a full audit trail.

Replaces: TARPs in a folder, and escalation by phone call. Best added once your shift record is running and trusted.

Understand

MPA Golden State

See what's really driving performance

Set target ranges for the outcomes that matter and the process drivers behind them, then drill down to the unit operations and drivers outside limits. Plant data sits alongside manual samples and lab results.

Replaces: Competing shift theories and control limits nobody has revisited. Most useful once there's history to learn from.

Proven at Pogo, Alaska

Seven digital logsheets. No time spent maintaining them.

At Northern Star's Pogo operation in Alaska, seven digital logsheets replaced Excel workbooks used to record unmetered streams across more than 10 plant areas. The metallurgy team now spends no time maintaining the logsheet system and extends it themselves when they need to.

I tried to calculate the benefit based on percent improvement in time savings, but it is not possible to divide by zero! With Logsheets, we no longer spend ANY time maintaining our Logsheet system.

James Sweeney · Project Metallurgist, Northern Star Resources, Pogo Operations
Proof, not promises

From sites already running MPA

Northern Star Resources (AU)

MPA
6 sites

Shift logs and handover KPIs rolled out corporate-wide across six sites.

Northern Star Pogo, Alaska

MPA
Immediate

Operator logsheets digitised into MPA, with plant data now live-monitored by the team and benefits from day one.

"Mipac's quick responses and attention to detail have made the roll-out seamless, saving time for operations and the met team on a daily basis... The benefits from MPA were realised immediately."

Mark Pliska · Processing Manager, Pogo Operations

Newmont Merian · Hundreds of hours saved

Working with Mipac was a real pleasure. We worked as a team and were able to achieve great results for our daily production reporting. We saw significant benefits with our reporting, data visualisation and data security. I would recommend Mipac to anyone.

Yuanbin Qin · Senior Metallurgist, Newmont Merian
Getting started

What it takes to get started

  1. 01

    Pick your starting point

    Usually TCard, Logsheets or Shift Handover, whichever matches the problem you feel most.

  2. 02

    Set up around your plant

    Mipac engineers map your plant data and configure the application from templates built for processing operations.

  3. 03

    Live in weeks

    Once the infrastructure is in place, most sites are live in two to four weeks. Larger builds, such as automated production reporting, take longer.

  4. 04

    Your team takes it from there

    After handover, your people add logsheets, edit TARPs and extend the applications themselves.

What you'll need on site for MPA

  • AVEVA PI historian with PI Asset Framework (PI AF). If AF isn't set up yet, Mipac can help.

  • A PI System Access (PSA) licence. Mipac can help you obtain it, or you can go through your AVEVA account manager.

  • A server. Virtual or physical, ideally Windows Server 2019 or later, with administrator access to install and configure MPA.

  • A service account. Arranged with your IT team, to access the PI Data Archive and PI AF server.

MPA runs on-premises in your OT network, and your data stays in your historian.

Support

Standard support

Help with software issues such as bugs and incidents, during business hours.

Premium support

For complex application or infrastructure issues, with response times set to suit your site and access to application specialists for minor additions.

Questions we get asked

Common questions about MPA

Does MPA replace our control system or historian?

No. Your operators stay on the DCS to monitor and control the plant, which is exactly where they should be. MPA takes the part of the day that has no system behind it: what the crew saw, decided and did. It reads from and writes back to your site historian, such as AVEVA PI.

Do I need AVEVA PI?

Not necessarily, but you'll be up and running sooner if you have it. With PI in place, MPA reads from and writes back to your historian through PI AF, so everything your crew captures sits alongside your plant data from day one. Without PI, we can look at connecting directly to other data sources at your operation, such as your control system or laboratory information management system (LIMS).

How long does implementation take?

Once the infrastructure is in place, most sites are live in two to four weeks. A like-for-like move, such as Excel logsheets to MPA Logsheets, sits in that range. Larger builds such as automated production reporting typically take 12 to 16 weeks, depending on the number of reports.

How do operators use MPA?

Operators continue to monitor and control the plant through the control system. MPA helps capture what happened during the shift, record actions and decisions, investigate events, and support shift handover. Many sites use MPA throughout the shift to maintain an operational record and coordinate activities across crews.

Can my team change things after go-live?

Yes. Your team can add logsheets, build and edit TARPs, and extend the applications as the plant changes. Mipac gets you started and stays available through support.

How do MPA and TCard relate?

TCard holds the tasks and actions. MPA holds the shift record. The shift handover is where they meet: what's open in TCard travels with what was recorded in MPA.

MPA and TCard brochure Not ready to call?

Download the MPA and TCard brochure

The problem MPA and TCard solve, how each application works, proof from sites already running it, and what you need on site to get started. Useful if you're building a business case.

Let's talk

Find the right first application for your plant

On most sites, Mipac is in the plant doing control systems and engineering work long before software comes up. MPA and TCard come from the same people, built for the way a processing plant actually runs.

Brisbane

+61 7 3212 5600 · sales@mipac.com.au

Perth

+61 8 6424 9900 · sales@mipac.com.au

Tucson

+1 520 320 9796 · sales@mipac.global

Vancouver

sales@mipac.global

Mipac Insights

Read more from the Mipac Insights blog

View all insights
The team at MillOps 2026
At the 2026 Mill Operators Conference, many sites told Mipac their leadership wants advanced process control and AI. Our first question was ...
Learning new skills
Brisbane engineer John Robinson, who joined Mipac in 2022, has been promoted to Senior Control Systems Engineer. Supporting automation work at a ...
MPA Updates
MPA is continually updated based on feedback from users in the field. Check back here for the latest releases, new features and ...
MIPAC INSIGHTS NEWSLETTER

Stay across what's changing in mineral processing.

  • Expert insights into industry trends and the future of mining
  • Company and product updates
  • Project case studies from around the world
  • Event news
  • Staff stories

Get Mipac Insights, free.

Unsubscribe at any time. See our privacy policy.

Simply fill out the below form and we will be in touch to discuss the best time for a demonstration.

Simply fill out the below form and we will be in touch to discuss the best time for a demonstration.

Simply fill out the below form and we will be in touch to discuss the best time for a demonstration.

Simply fill out the below form and we will be in touch to discuss the best time for a demonstration.

Simply fill out the below form and we will be in touch to discuss the best time for a demonstration.

Simply fill out the below form and we will email you a copy of our MPA product guide.