1. Home
  2. Solutions
  3. Factory intelligence

Factory Intelligence in Qatar

Production monitoring software that reads the PLCs on your lines: live machine status, OEE by line and shift, every stop with its reason, and a shift report that's ready before the handover.

Siemens, Rockwell, Schneider, ABBRead over OPC UANo change to control logicRead-only connectionInstalled in DohaSupported after go-live

Last updated

Conveyor lines carrying boxes through a production and packing hall
Illustration: a packing line's OEE for the shift so far, split into availability, performance and quality, with one machine stopped.

What is production monitoring software?

Production monitoring software reads machine states and counts straight from the PLCs on a production line and shows, as it happens, whether each machine is running, idle or stopped. It calculates OEE, logs every stop with its reason and builds the shift report, so your losses are measured instead of estimated.

The PLC on each filler, labeller or press already knows whether it is running and how many units it has made and rejected. Production monitoring reads those values onto one timeline for the line, and asks the operator for a reason only when a machine stops. It sits between the spreadsheet and a full MES.

Paper and spreadsheets

Counts and stops written up at the end of the shift. Short stops and slow running never make it onto the sheet.

Full MES

Scheduling, recipes, batch genealogy and more. A long project, and more than many plants need to start.

Production monitoring

Live state, OEE and stop reasons from the PLCs in weeks, with room to grow.

Sound familiar?

What plant and production managers in Qatar tell us before we start.

  • "We find out the line was down from the shift report the next morning."

    By the time the numbers are typed up, the shift that lost the time has gone home, and nobody knows if it was one breakdown or twenty small jams.

  • "Every shift lead gives the same stop a different name."

    Free-text notes can't be added up, so the biggest loss on the line stays hidden behind the loudest one.

  • "Our machines come from five vendors and twenty years."

    Food, packaging and building-materials plants in Mesaieed and the Qatar Free Zones often run a new filler beside an old palletiser, and nobody wants to touch a working PLC program to get the data out.

What it measures on every line.

Every lost minute of planned production time lands in one of these buckets, recorded from the machine.

What it measures on every line.
LossWhat Quoriam recordsWhere the data comes from
Breakdowns and unplanned stopsEach stop with its start, end, machine and reasonPLC run state; reason from the line tablet
ChangeoversLast good unit of one SKU to first good unit of the nextPLC SKU tag and counts
Minor stopsStops under two minutes, coded automaticallyPLC run state
Slow runningActual rate against the rated speed for the SKU on the linePLC counters and the rated speed per SKU
Starved and blockedIdle time caused by the machine before or after, and buffer levelsPLC states and buffer sensors
RejectsRejected units by machine, and by cause where reportedReject counters and inspection systems

How OEE is calculated.

Overall equipment effectiveness compares what a line made with what it could have made in its planned time: three ratios multiplied together.

OEE factors, their formulas and a worked example with illustrative numbers
FactorFormulaWorked example
AvailabilityLost to stops and changeoversRun time ÷ planned production time378 ÷ 420 min = 90%
PerformanceLost to slow running and minor stops(Ideal cycle time × total count) ÷ run time(0.6 s × 34,020) ÷ 378 min = 90%
QualityLost to rejectsGood count ÷ total count33,340 ÷ 34,020 = 98%
OEEAvailability × performance × quality0.90 × 0.90 × 0.98 = 79.4%

Worked example, illustrative numbers only: an 8-hour shift with 60 minutes of breaks gives 420 minutes of planned production time; 42 minutes of stops leave 378 minutes of run time; the ideal cycle time is 0.6 s (100 units a minute); 34,020 units made, 680 rejected. Stop time includes changeovers as well as breakdowns. Definitions: OEE.com, Calculating OEE.

How it works on Quoriam.

  1. Connect

    A Quoriam Edge QE35 gateway reads each PLC over OPC UA, read-only, so control logic is never touched. Machines without a PLC get a count sensor.

  2. Map

    We map each machine's tags to its state, counts and SKU, and load your shift calendar and rated speeds.

  3. Code

    When a machine stops, the operator picks the reason on a line tablet, with a suggestion from the PLC. Short stops are coded automatically.

  4. Improve

    OEE, the stop Pareto and the shift report update live. The shift lead is alerted when the constraint machine stops; mechanical faults become work orders.

Isometric illustration: an industrial site, with the Quoriam platform above it as a live dashboard and the decision layer on top

System view

For IT, OT and security reviewers: where the data goes, and how.

  1. On the lineMachine PLCs, count sensors, energy meters and a tablet at each line
  2. At the edgeQuoriam Edge QE35 reading PLCs over OPC UA and other industrial protocols, read-only
  3. NetworkPlant network or cellular, encrypted and kept apart from the control network
  4. Quoriam platformOn your premises or cloud hosted in Qatar
  5. Your team and systemsLine boards, shift reports by PDF, alerts to shift leads, work orders to maintenance, data to your ERP

What your team sees.

The line as it runs, where the time went, and what to fix first.

Quoriam line status board for Line 2 with seven machines from depalletiser to stretch wrapper, the labeller marked as the constraint, the wrapper stopped for 6 minutes, and state ribbons for the day shift
Line status board. Every machine running, idle or stopped, with buffer levels and the current constraint.
Quoriam OEE dashboard for Line 2 at 81% over seven days against an 85% target, with availability, performance and quality, a waterfall of hours lost and OEE by day and night shift
OEE dashboard. Availability, performance and quality by day and shift.
Quoriam downtime Pareto for Line 2 with labeller glue and label jams the top reason at 198 minutes, a table of reasons and a heat map of minutes lost by machine and day
Downtime reasons. Stops ranked by minutes lost, with the fix worth most.

Or just ask.

Quoriam AI answers questions about your lines in plain language and turns the answer into an action.

Hardware and integrations.

We read the controllers you already run and add hardware only where a machine has nothing to read.

  • Quoriam Edge QE35 gateway, front view
    Edge gatewayQuoriam Edge QE35, reads PLCs on site
  • Line tablets
    One per line or station, for stop reasons and handover notes
  • Milesight EM300-DI pulse counter
    Count and state sensorsFor machines with no PLC to read
  • Milesight CT103 clamp-on current transformer
    Energy metersOn line feeders, for energy per unit
Reads from
Siemens, Rockwell, Schneider, ABB, Mitsubishi and Omron PLCs over OPC UA, Modbus, Profinet and EtherNet/IP; SCADA over OPC UA
Sends to
ERP systems such as SAP, Oracle and Microsoft Dynamics
Alerts by
Quoriam app, SMS and email to shift leads and maintenance, with escalation if nobody responds

Hardware agnostic. Makes we fit includeWe can work with any maker and choose the device for each site. The platform reads them all.

Where it's used.

The same platform, set up in each industry's terms.

Questions buyers ask.

Something else? Ask us during the free assessment.

Do you change our PLC programs?

No. The edge gateway reads values the PLC already holds over a read-only connection. Control logic stays exactly as your automation team left it.

Which PLCs and machines can you read?

Siemens, Rockwell, Schneider, ABB, Mitsubishi and Omron controllers, among others, over OPC UA, Modbus, Profinet or EtherNet/IP. Older PLCs without an OPC UA server are read through the gateway's protocol drivers.

How many machines do we need to connect?

Start with one line, connecting each machine whose stops matter. One edge gateway usually serves a line or a hall. The free assessment counts it for your plant.

What does it cost?

It depends on how many lines and machines you connect and how they connect. The free three-week assessment ends with a scope and a fixed price for your plant.

How do operators record downtime reasons?

On a tablet at the line, which suggests the likely reason from the PLC, so a stop is coded in a couple of taps. Uncoded stops show on the report so they can be chased.

Is this an MES?

It covers the monitoring part of an MES: machine state, OEE, downtime and shift reports. Scheduling or batch records can follow on the same data.

What OEE should we aim for?

Start from your own baseline. A month of accurate stop data tells you more than any benchmark, and the target follows from the losses you can remove. We set targets per line with you during the pilot.

Can it work alongside predictive maintenance?

Yes. With predictive maintenance on the same platform, the motors and gearboxes behind the longest stops are watched too.

Start with a pilot.

Prove it on one line before you connect the whole plant.

  • One line and its machines chosen with your team in the assessment
  • Edge gateway and line tablet supplied, fitted and commissioned by our engineers
  • How long it runs is agreed with you, typically around eight weeks
  • The results to look for are agreed at the start and reviewed with you at the end

See where your line loses its time.

A free three-week assessment. We review your lines, their PLCs and today's reports, then show you which losses to measure first.

We take on two assessments a month.

Quoriam is designed to pay back within six months. How we calculate payback