Eclipse Miningware

We’ve finally added dark and light themes to Eclipse. Night shift users were very much part of the thinking here 🌑👍 https://lnkd.in/d-mXeHAe

Small delays during Operations-Maintenance handovers add up quickly. Here's how we manage that in Eclipse👇. https://lnkd.in/dRgGXPk8 How do you handle handovers currently on your site?

A practical look at how the Eclipse Ore Tally keeps production data aligned. 👇 https://lnkd.in/eEzz_sGH How does your site currently manage reconciliation between departments?

Why does updating the system take longer than doing the work? Task gets finished. Spotter sheets get delivered to operations support with poor, hurried handwriting with potential for human error. They now have to decode that, losing time chasing and calling people. Geology have their own version of data, not always perfect either. Trying to match the two almost always results in hours wasted. Unsurprisingly, everybody now expects the numbers at the morning meeting to be a guesstimate. Eclipse is designed to make those figures far more accurate with far less effort. Where does this process break down most for you?

Good operations don’t need more reports. They need clearer signals. Some of the biggest gaps appear between when work happens and when it’s written down. Where do you see that gap most often?

"Why was productivity in Pit XXX down last shift?" "What actually happened to PE06 yesterday?" "Why did DT08's engine seize up?" Ever heard questions like these during your morning meeting? When data is fragmented across systems, spreadsheets and handovers, gaps and mismatches are inevitable. Eclipse captures data as the work happens, automatically applies necessary checks to make it more accurate and gathers it all so answers are already there before the meeting starts.

If your mine spends more time reconciling yesterday's data than planning tomorrow's production, this might be worth a read👇. https://lnkd.in/d36EapZk What's one operational report that takes way longer to compile than it should?

If your mine spends more time reconciling yesterday's data than planning tomorrow's production, this might be worth a read👇. https://lnkd.in/d36EapZk What's one operational report that takes way longer to compile than it should?

𝗠𝗼𝘃𝗶𝗻𝗴 𝗠𝗮𝗶𝗻𝘁𝗲𝗻𝗮𝗻𝗰𝗲 𝗙𝗿𝗼𝗺 “𝗪𝗵𝗼 𝗞𝗻𝗲𝘄?” 𝘁𝗼 “𝗘𝘃𝗲𝗿𝘆𝗼𝗻𝗲 𝗞𝗻𝗼𝘄𝘀” In many operations, the slowest part of getting equipment back to work isn’t the repair itself, it’s the delay between a machine becoming available and the right people realising it. Supervisors assume it’s still down. Operators wait for confirmation. Maintenance believes the message was passed on. Production loses minutes that turn into hours, and everyone quietly wonders where the process broke. We’ve just added a new feature to Eclipse that removes this uncertainty completely. Users can now choose to receive maintenance availability notifications directly through Eclipse, by email, or both. They can also select which departments’ fleets they want updates for any number of departments added to Eclipse like Mining, Processing, Load & Haul, Special Projects and so on, so only relevant information reaches each person. The moment a vehicle comes out of maintenance, the right people know, and the shift moves forward without hesitation. It’s a small change, but it resolves one of the most persistent points of friction on a mine: the gap between when equipment is ready and when it is actually put back to work. The clearer that handover becomes, the more productive each shift gets and the less time is wasted on guesswork or blame.

𝗦𝘁𝗮𝗿𝘁 𝗮𝘀 𝘆𝗼𝘂 𝗺𝗲𝗮𝗻 𝘁𝗼 𝗴𝗼 𝗼𝗻 Most mines don’t struggle because they lack technology. They struggle because operational information is scattered, captured in different places, at different times, in different formats and then reconciled later under pressure. That’s when small inconsistencies become “normal”, and the daily report turns into a reconstruction exercise. This is also why many sites delay a full Fleet Management System until later. FMS rollouts are significant projects, and they often compete with other urgent priorities across maintenance, planning, plant, infrastructure and change management. The result is a familiar pattern: the mine scales up first, and the data foundation is built afterwards. Eclipse is designed to flip that sequence. You can start from day one with structured, validated operational data, production, geology and equipment availability—without needing to be connected to an FMS. Eclipse reduces error by enforcing simple rules in the background: valid materials, valid destinations, date-aware equipment status, and operational logic that prevents contradictory entries. Reporting becomes a by-product of normal work, not a separate stage of manual stitching. And when the mine is ready for FMS, Eclipse is ready too. The difference is that the transition happens from a clean, consistent data core rather than from a patchwork that has grown fragile over time. The earlier a mine invests in data quality, the less pain it inherits later.