Consolidate · Validate · Synchronize

Your planners are still in Excel, even with a CMMS

The official plan lives in the CMMS. The real plan lives in a shadow spreadsheet, on one person's computer. PlanMI is the layer that brings the two back together, for mobile equipment, fixed plant and shutdowns.

Shop Gantt view, daily utilization rate

(01)The diagnosis

Equipment availability dictates site productivity

And yet scheduling still runs on scattered spreadsheets, information passed along by hand and approvals that take days. The process varies from one shop to the next, so the same mistakes keep coming back.

RESOURCE CONFLICTS

The conflict surfaces the day before the job

Two jobs on the same crew, the same shop bay or the same piece of equipment. The result: extended downtime, delayed production and a utilization rate that slips.

PLANNING ERRORS

It all lives in the planner's head

Mental load, poor visibility, disconnected systems. You end up with poorly managed units in the shops and equipment unavailable at the wrong time.

MAINTENANCE COSTS

Costs nobody saw coming

Unplanned repairs and replacements, parts availability that can't be confirmed before the job. The budget and the schedule absorb the difference.

Reality

The official plan says one thing. The shop floor lives another

(02)The plan's journey

Five stages, from shadow spreadsheet to synchronized plan

The mechanism is always the same, whatever the use case. Consolidate, detect, validate, synchronize, track.

STAGE 01

The whole plan in a single view

Mobile, fixed plant and shutdown come together in the same Gantt view, instead of being split between the CMMS and a shadow Excel file nobody else can read.

STAGE 02

Conflicts surface before they reach the field

The engine flags resource conflicts, overlapping dates and inconsistencies while you plan, not when the truck is already at the shop door.

STAGE 03

The planner makes the call, in three moves

Drag and drop to reschedule, priorities to revisit, trade-offs owned by the person who knows the site. The tool doesn't decide for them; it makes the decision visible.

STAGE 04

The validated plan flows back to your systems

CMMS, SAP, Oracle, Maximo, Guide TI, JDE. No re-entry, in both directions. Deswik coverage is in progress, and we don't claim otherwise.

STAGE 05

Actual hours, compared against the plan

Equipment-level history, trends, variances. That's where you see whether the plan holds, and why it fell apart last week.

(03)Everyone sees what matters to them

Three scheduling logics, three views

A mine doesn't plan a truck like a crusher, or a crusher like a major shutdown. PlanMI keeps the contexts separate instead of imposing a generic view.

The mobile equipment planner

They work by operating hours and by the window production leaves them. Their view shows the units, the shop bays and the daily utilization rate.

Columns: unit · hours · bay · dispatch

The fixed plant planner

Their cycle is predictable; what matters is the window. Their view shows grouped work orders, parts status and crew availability.

Columns: asset · work order · parts · crew

The superintendent in a major shutdown

Dozens of work orders, dependencies between trades, a start-up date that won't move. Their view shows the critical path and the shared resources.

Columns: task · dependency · trade · milestone

(05)Systems it feeds

Feed the tools you already have

PlanMI doesn't replace your CMMS or your ERP. It validates the plan, then sends it back to where your teams already work.

The plan

  • Work orders
  • Availability
  • Priorities
PlanMIValidation

Your systems

  • CMMS
  • SAP
  • Oracle
  • Maximo
  • Guide TI
  • JDE
  • DeswikCoverage in progress

Captured once, sent to several destinations. No connector is announced until it's confirmed.

Call to action

We start with your CMMS, your equipment and your next shutdown

A 30-minute meeting with your planner is enough to see whether PlanMI solves a real pain point for you, or not.

Mechanic in the shop in front of a mining truck, wrench in hand