Service statusStatus ESEN
Sales and support 442 138 8102 Request a demo
Fisher Platform module

Your plant in one place, with maintenance and energy built in.

Plant (MES) runs a factory or a production line: the shift OEE, orders with their real cost, the operator terminal, breakdowns flagged before they happen and what the energy of each part costs. All connected to your Warehouse, your Purchasing and your people.

See it in action See the line board
  • OEE, TEEP and the six big losses
  • Maintenance that predicts from trends
  • kWh per good part and real cost per order
admin/factory
6big losses split out in the OEE, with the Pareto of what stops you most
5Andon types from the terminal: maintenance, quality, material, help and safety
3tariff periods with their cost: peak, intermediate and base
5ready-made starter roles: from plant manager to line operator
Line board

How the line is doing, and why, without waiting for the end of the shift

The OEE is not left as a single number: it is split into what pulls it down, and the line is drawn with each station in its current state.

Line digital twin

The line drawn out, with every station live

  • Shift OEE as availability times performance times quality, with its target and the TEEP beside it.
  • Good parts and scrap, line output against plan and the power draw at that moment.
  • Each station in its own colour: running, idle, setup or changeover, stopped, maintenance or off shift. An Andon alert blinks on the station that raised it.
  • By line and by period, live, refreshing every 30 seconds.
admin/factory
Line board. Six stations, yesterday's OEE and one Andon waiting.
Losses and stops

What took the OEE away, ordered by what weighed most

  • The six big losses kept apart: breakdowns, setups and changeovers, other stops, minor stops, reduced speed, process defects and startup scrap.
  • Downtime Pareto with the time, the count and the reason for each one.
  • Hourly output against plan, with bars for good parts and scrap and the OEE line.
  • A stop with no reason can be explained afterwards: it stays flagged and whoever sees it can add its cause.
  • Line events filterable by state, with their time and duration.
admin/factory
Losses. Missing material, format changeovers and quality holds lead the list.
Stations, orders and people

Everything about the line, on the same sheet

  • Each station with its state, OEE, availability, performance, quality, good parts and scrap.
  • Running orders with their progress, and the people on the line with their station.
  • A waiting Andon shows at the top, with who raised it, how long it has waited and the «On my way» and «Solved» buttons.
admin/factory
Stations. Each machine with its numbers for the period.
Machines

Every machine with its health, and the breakdown flagged before it happens

Sensors, OEE, time between failures and a trend-based prediction that proposes the maintenance order.

Machine fleet

All thirteen machines of the plant, in one view

  • Today's OEE in a ring, state and since when, temperature and vibration with a small chart.
  • Health from 0 to 100 with the reason for what is deducted: an overdue preventive task, an open corrective one.
  • Accumulated cycles and running hours, the ones that drive preventive tasks and tooling life.
  • Filters by line, state and type, and search by code or name.
admin/factory/machines
Machines. A press, welders, CNC, injection moulding and packing, across three lines.
Machine sheet

«It will reach its vibration limit in 13.8 days»

  • Temperature, vibration and power over 2 hours, 24 hours or 7 days, with their alarm threshold drawn in.
  • Trend-based prediction: a line fitted over the last 7 days says when the machine's maximum will be crossed, and a button creates the predictive work order.
  • MTBF and MTTR, energy per part and idle energy of the machine itself.
  • Preventive tasks, work orders, mounted tooling and events on the same sheet, and buttons to go to its terminal.
admin/factory/machines/view/8
CNC-02. Vibration rises 0.134 mm/s per day and would reach its limit on 24/11.
Manufacturing orders

From the order to the real cost of each part, and from there to the warehouse

The order is born from the product routing, is planned over time and, when completed, moves the inventory.

List

What is being made, with its progress and its date

  • Operations from the product routing: each step with its machine, its cycle time and what it has declared.
  • Progress and scrap of each order, priority and due date, with «late» in plain sight.
  • The quantity of the order is that of its last operation: if every station declares, the same part is not counted several times.
  • States: draft, released, running, paused and completed, with filters by state and line.
admin/factory/orders
Orders. Seven open: three running, three released and one draft that is late.
Real cost

What it really costs, against the standard

  • Material: the bill of materials times the parts made, at the average cost from Warehouse.
  • Energy: the order's running spans times each machine's power and the price of the period in which it ran.
  • Labour and machine: by the running hours of the order, at their rate.
  • Cost per part against the standard, with the deviation as a percentage, and each declaration of parts with its time and its scrap reason.
  • On completion, it consumes the materials and receives the finished product into Warehouse at that cost.
admin/factory/orders/view/16
Running order. 46.88 per part against a standard of 44.00, and where every cent comes from.
Production plan

A Gantt you can drag

  • The orders of each line over time, coloured by state and with a mark for the ones that are late.
  • Drag a bar to change its date or line; a click opens it.
  • The materials missing from the warehouse show on the order itself, checked against Warehouse stock.
admin/factory/orders/gantt
Plan. Three lines, chained orders and today's date marked.
Plant terminal and Andon

The operator declares at the machine, and help arrives on its own

A large screen with large buttons, designed for a tablet next to the machine.

  • Start, setup or changeover, standby and stop with the reason, which comes from the loss catalogue.
  • Declare good parts and scrap with plus and plus-ten buttons, and the scrap reason.
  • The running order with its progress, its work instructions and the mounted tooling with its life.
  • Andon of five types (maintenance, quality, material, help and safety): it notifies the right people, blinks on the digital twin and, if it is a maintenance one, opens the work order by itself, which closes when it is finished.
  • If the station requires a certification the person does not have, the terminal tells them.
admin/factory/terminal/8
Terminal. A stopped machine, a maintenance Andon waiting and two mounted tools.
Maintenance

A CMMS inside the plant, not in another system

Corrective, preventive and predictive, with the running hours that production itself keeps.

Timeline

What failed, when, and what is coming

  • Failure timeline of the thirteen machines, 30 days back and 30 ahead, with a slider to see what was happening each day.
  • Breakdowns, planned orders, completed orders, preventive tasks coming due and predicted failures with their colour and legend.
  • MTBF, MTTR, preventive compliance and planned maintenance against corrective, with the open orders and the spare parts below minimum.
  • Predictions with a button to create the predictive order before the failure.
admin/factory/maintenance
Timeline. A month of breakdowns and what is forecast ahead.
Work orders

The board you drag between stages

  • Requested, planned, in progress, waiting for spare parts and done: drag the card to change its stage.
  • Corrective, preventive and predictive with priority, machine, owner and date.
  • «Start and stop machine» from the card: the machine goes into maintenance and shows that way on the line board.
  • Time and cost of each completed order.
admin/factory/maintenance
Work orders. A planned predictive one and an urgent one in progress.
Preventive tasks and spare parts

By days, by running hours or by cycles, and generated automatically

  • A preventive task based on real use: every 7 days, every 250 running hours or every 50,000 cycles. The plant keeps the counters itself.
  • They are created automatically as they approach their due date, with a progress bar.
  • Spare parts with stock and minimum, linkable to a Warehouse item; the «Order» button creates the purchase request in Purchasing.
admin/factory/maintenance
Preventive tasks and spare parts. Two spare parts below minimum, highlighted.
Energy

What the electricity of each good part costs

Consumption by machine, by hour and by tariff period, set against what was produced.

Where it goes

From the grid to the part, in a Sankey diagram

  • kWh per good part, the energy performance indicator of ISO 50001, and the cost of each part.
  • Energy paid for without producing: what is consumed with the machine switched on and not working, and what it costs.
  • Demand against contracted demand, with the peak of the period and the power right now.
  • Emissions in tonnes of CO₂e with their emission factor per kWh.
  • Sankey from the grid to the lines, from the lines to the machines and from there to production, idle and stopped.
admin/factory/energy?range=30d
Energy. 117,329 kWh in 30 days, and 7% paid for without producing.
Tariff and machines

Peak, intermediate and base, and which machine uses the most

  • Consumption by hour or by day, in kWh or in cost, with the colour of each line.
  • Cost by tariff period (peak, intermediate and base) with the schedules and prices you configure.
  • By machine: kWh, cost, split between productive, idle and stopped, idle percentage, kWh per part and peak. Sort by any column.
  • Idle time in plain sight: more than 30% of a machine's energy going to idle is money thrown away, and the table says so.
admin/factory/energy?range=30d
By machine. The paint booth uses more at idle than the others.
Tooling and people

So the mould does not run out by surprise, and nobody operates without knowing how

What wears out on the machine and what each person knows, with warnings before it becomes a problem.

Tooling

Moulds, dies, tools and gauges with their life

  • Life in cycles, hours or uses, consumed automatically by the machine where the tool is mounted.
  • A warning as the end approaches and a predicted end date calculated from the real usage of the last 14 days.
  • Resharpenings with a limit (2 of 4) and calibration with its next date.
  • Mount, unmount and replace from the actions menu, with filters for «near end of life» and «calibration due soon».
admin/factory/tools
Tooling. A die at 92% of its life, with its predicted end on 19/11.
Skills

ILUO matrix: who can do what

  • Level from 0 to 4 per person and skill: no training, in training, supervised, autonomous and can teach.
  • Certification with an expiry date for each skill of each person.
  • Stations per line and shift, with the skill and level they require; assigning someone who does not have it raises a warning («not certified»).
  • Coverage: how many people cover each skill and a red warning when it depends on fewer than two.
admin/factory/people
Skills. Mechanical maintenance depends on a single person.
Starter roles

Five ready-made roles: everyone sees their own

They are created when the module is activated, without touching any you have already adjusted, and are assigned on each person's sheet.

Plant manager

All capabilities and all screens, including plant configuration.

Production planner

Sees the plant and plans: manufacturing orders, plan, energy, tooling and people.

Line operator

Sees the line and the machines and operates the terminal: parts, stops and Andon. Everything else is redirected.

Maintenance technician

Views, operates and maintains: work orders, spare parts, tooling and preventive tasks.

Energy and continuous improvement

Read-only access to line, machines, maintenance, energy and people, to analyse without touching.

Fine-grained permissions, per screen

View, operate, plan, maintain, create, edit and delete, separately. Anything with history is not deleted: it is deactivated.

Connecting machines

Your PLCs talk to the plant through an HTTP gateway

A PLC, Node-RED or an MQTT or OPC UA bridge sends the readings. It is not a native client of those protocols, and we say so plainly here.

How it comes in

With its token, its quota and its address

  • Off by default. It is switched on in Settings → Plant → Telemetry and one gateway is created per device.
  • Its own 32-byte token per gateway, shown only once and stored only as a hash; revoke it whenever you like.
  • Can be tied to a line and to IP addresses, with a per-minute quota: a gateway tied to a line only writes to that line.
  • A bad or revoked token gets a 401 and writes nothing. Only metrics from the catalogue are accepted, with a size cap.
  • It also works without sensors: the operator declares from the terminal and the OEE and cost come out.
What the machine sends

Readings and state, nothing more

  • Temperature, vibration, power, cycles and state of each machine, with any metrics you add to the catalogue.
  • The readings feed the charts, the prediction, the energy per machine and the life of the tooling.
  • The API has been tested end to end with curl; not yet against a real device. That test is done with your plant.
Bastino

Ask the plant

Bastino, the AI assistant of Fisher Platform, reads the plant with your permissions and answers in everyday language.

«How is the plant doing?»

The OEE of each line, what is stopped and what is waiting for attention.

«Why did the OEE drop yesterday?»

Which loss weighed most and which machine caused it.

«Which tools need replacing?»

The ones close to the end of their life or their calibration.

«How much does the electricity cost per part?»

kWh and cost per good part, by line and by period.

Create a work order

It proposes it with a confirmation card: you see it, you approve it and only then is it created.

Change a manufacturing order

With its card, the before and after, and your permissions checked again when you accept it.

Bastino does not change the plant configuration, does not delete, does not declare parts or stops (the operator or the machine does that) and does not touch the gateways.

Connected to the rest

Not an island: Plant talks to your platform

Each module notifies the others through events, without writing to their tables.

Warehouse

When an order is completed it consumes the materials and receives the finished product; material needs are compared with stock.

Purchasing

«Order» on a spare part linked to an item creates the purchase request, with its approval.

Assets

Each machine is linked to its asset, and the asset's sheet shows its step on the plant.

Staff

Skills are visible from each person's sheet, and deleting someone cleans up their skills and assignments.

Notifications

Andon, maintenance and tooling life alerts, through the channel each person chooses.

Scheduled tasks

Energy, maintenance and the clean-up of old readings run on their own, on the schedules you set.

Home dashboard

A widget with today's OEE, on the home page of anyone who wants it.

REST API

Read access to orders and machines with your API key, which can never do more than its owner.

Plans and demo data

It is activated separately like any module, and comes with a sample plant to explore before loading yours.

Stated plainly

What it does and does not do yet

Better to know before you sign up than to find out afterwards.

Designed with control in mind

A plant that is not left half-finished

  • Permissions by capability: whoever operates the terminal does not plan, and whoever plans does not change the configuration.
  • Everything that changes data requires a session and a security token; telemetry comes in only through its gateway, with a token.
  • Anything with history is not deleted: machines, lines, products and catalogues in use are deactivated.
  • Bastino never decides alone: every action asks for its card and checks your permissions again when you accept it.
What you need to know

What it does not include yet

  • It is not a native OPC UA or MQTT client: it comes in through the HTTP gateway, with a bridge in between.
  • It does not schedule by itself: the Gantt is dragged by hand. Finite scheduling by capacity and changeovers is pending.
  • Quality with SPC, Cpk and nonconformities, and lot or serial genealogy, are on the list of what comes next. Scrap does count, with its reason.
  • Work instructions are text per operation, without images or files. The terminal uses the session of whoever is logged in, with no badge or PIN identification.
  • Labour is calculated with one rate per running hour, not per actual person.
  • Tested end to end with demo data and with the API; not yet against a real PLC.
Frequently asked questions

What we are usually asked

Does it connect to my PLCs and machines?

Yes, through an HTTP gateway with its own token: a PLC, Node-RED or an MQTT or OPC UA bridge sends the readings of each machine. It is not a native OPC UA or MQTT client. It is off by default and each gateway can be tied to a line and to IP addresses.

Can I use it without sensors on the machines?

Yes. The operator declares starts, stops, parts and scrap from the plant terminal, and that gives you the OEE, the losses and the cost of each order. Sensors add temperature, vibration, power and the prediction.

Does the warehouse update when an order is completed?

Yes. When the order is completed the materials on the list are consumed and the finished product is received into Warehouse, at the real cost of the order.

How is the real cost of an order calculated?

Material: the bill of materials times the parts made, at the average cost from Warehouse. Energy: the order's running spans times each machine's power and the price of the period. Labour and machine: the running hours at their rate. It is compared against the standard and the deviation is shown.

How does it predict a breakdown?

It fits a least-squares line to the temperature and vibration of the last 7 days and says when it will cross the machine's maximum. It is not a neural network: it is a trend you can explain. A button creates the predictive order.

Does it include quality with statistical control and lot traceability?

Not yet. It records scrap with its reason and counts it in the OEE, but control plans with SPC, nonconformities and lot or serial number genealogy are on the list of what comes next.

Does it schedule production on its own?

Not yet. The Gantt plan is dragged by hand using the estimated duration; automatic scheduling by capacity and changeovers is pending.

What kind of factory is it for?

It is designed for mid-sized factories: metalworking, plastic injection, auto parts and assembly. Lines, machines, stop reasons, tariff periods and maintenance stages are configured, not hard-wired.

Is it sold separately?

Plant is an installable module of Fisher Platform: it is activated or deactivated separately and, when deactivated, its screens disappear. Write to us and we will tell you what your plan includes.

See it with your own plant

We load a sample plant similar to yours and walk through the line board, maintenance and energy per part together.

Fisher Networks ventas@fishernetworks.net 442 138 8102
Send an email
About the screenshots and the data

The screenshots come from a demo environment with a fictitious plant, «Metalúrgica del Bajío»: three lines, thirteen machines and thirty days of history generated by a simulator, with invented people, orders and readings; no data belongs to a real customer. What you see depends on the active modules and on each person's permissions.

View plans