IQ Thread

Improve every shift.

IQ Thread is the next-generation maintenance intelligence system for the factory floor. It connects live machine behavior, operator observations, manuals, work, parts, and failure history in one continuous thread—so your team can see what changed, act with context, and carry the lesson forward.

  • machine conditions become maintenance events
  • people get grounded answers and next actions
  • successful fixes strengthen plant memory

Get your workspace

Create a workspace free. Add a card when you're ready to start the 30-day full trial.

$90 / technician / month · operators are free

The IQ Thread downtime screen for a bakery plant: unplanned hours and stop
                    counts up top, paired charts splitting the last fourteen days by reason and
                    by machine, and beneath them the live list of episodes — micro-stops and
                    uncoded stops each one click from being coded.
Every stop, counted while it still matters. Run signals become downtime episodes the moment they happen; reasons, machines, and micro-stops roll up live, and each episode stays one click from a coded close-out or a work order.
sense → understand → act → learn

A living intelligence layer for every machine

IQ Thread follows the complete maintenance loop—from the first change in machine behavior through diagnosis, execution, materials, and close-out—then makes the result useful the next time the plant sees it.

sense

See the plant as it is running

Connect i3X, your existing edge collector, a run signal, or wireless SHARC sensors. IQ Thread preserves readings through network outages and turns raw tags into run states, counters, formulas, dashboards, and anomaly watches. Operators add what the machine cannot say in three taps, so every event carries both machine evidence and human context.

The live tag tree of a CNC machine shop: availability and power state for each
                    machine, then the Robodrill's own signals — alarms, cycle time, execution
                    state, part count — each with its current value.
a real shop floor, one tag tree — live
understand

Give every event its full context

The assistant brings together the machine, component, current signal history, operator report, manuals, schematics, parts, and successful fixes. Ask in the language your team uses and get an explanation grounded in the exact manual page and your plant's own history—not an answer detached from the asset in front of you.

The assistant answering 'How do I replace the spindle on the Haas mill?':
                    numbered steps for spindle orientation and the break-in routine — 300 RPM for
                    two hours, then 1000, 3000 and 7000 RPM — every step carrying a citation chip,
                    with thumbnails of the exact service-manual pages beneath the answer.
a real answer — every step cites the manual page it came from
act

Move from insight to coordinated work

Turn an operator report, scheduled need, meter event, or condition change into owned work. The assistant can draft the procedure, create the plan, and update the record while every action stays visible. Calendar- and usage-based maintenance, technician scheduling, parts, labor, and notifications stay connected through execution.

When materials are needed, the same context flows through requisition, RFQ, purchase order, partial receipt, and actual cost—without retyping the reason for the purchase at every step.

Inventory report: stock valuation split into spare and consumable, dead stock
                    flagged in red, and a projected stock-out table weighing consumption rate and
                    days left against each part's lead time.
work, people, materials and cost stay connected
learn

Make every maintenance cycle smarter

IQ Thread learns normal operating patterns in vibration, load, pressure, temperature, and other signals. A sustained change can open an investigation with the evidence attached, without requiring someone to guess a fixed threshold first.

Successful corrective close-outs become searchable case memory. Failure codes, observed recurrence, and FMEA risk stay connected, so the next diagnosis and improvement decision begin with what the plant has already learned.

An FMEA register joined to real close-outs: each failure mode with its causes,
                    severity-occurrence-detection scores and RPN, the observed recurrence per year
                    from coded work orders, and one row flagged for occurrence review because the
                    plant's history disagrees with the rating.
start small, learn continuously

Start with one machine. Build a plant-wide memory.

  1. 01give the machine context

    Create the workspace, add a machine, and upload its manual. In minutes, the team has an answerable source and a working maintenance record—not an empty database waiting for a consulting project.

  2. 02connect the floor

    Put the operator experience at the machine and connect a run signal or sensor when ready. Human observations and machine behavior begin building the same timeline from the first shift.

  3. 03let intelligence compound

    Each grounded diagnosis, successful fix, procedure, part, and observed failure enriches the next recommendation. The system becomes more useful because your plant keeps using it—not because someone keeps configuring it.

one thread across the plant

Connect the sources that already know your operation

Machine controls know what happened. Operators know what they observed. Manuals know how the asset was designed. Work history knows what succeeded. IQ Thread gives those sources a shared operational memory.

i3X machine dataSHARC + MQTT sensors OPC-UA, Modbus, MTConnect, Fanuc, S7 via edge collector PDF manuals + drawingsemail + web push cloud or dedicated deployment
deployment

The same intelligence, where you need it. Run IQ Thread as a cloud workspace or as a dedicated single-tenant installation on your server. Configure AI and document storage for the deployment, keep history backed up and exportable, and give each team the interface in the language it works in.

before you ask

Questions owners actually ask

How much does it cost?

One plan is $90 per maintenance seat per month with a three-seat minimum ($270/month). Operators are free and unlimited. Machine data, purchasing, analytics, the assistant, and preventive maintenance are included. You can create a limited workspace without a card; adding one starts the 30-day full trial.

What happens to my data if I cancel?

It stays yours. Cancellation or a failed payment demotes the workspace gracefully — the founder keeps access, nothing is deleted, and you can export everything.

Do operators need accounts or their own hardware?

No. Operators share the machine tablets — tap your name, enter a 4-digit quick code. Quick codes only open the operator side, never the maintenance portal. And operators never consume paid seats.

Can we bring our existing maintenance history?

Yes. We can map machines, work-order history, PM schedules, parts, and people into IQ Thread. Imported close-outs can become searchable case history, so the system begins with what your team has already learned instead of starting from zero.

Do you support i3X machine data?

Yes — natively. Point IQ Thread at any i3X-speaking server and its live values and history become dashboard tiles and downtime run signals — no gateway, no custom integration. For machines that don't speak anything yet, a wireless SHARC sensor covers them in about five minutes.

We already collect machine data. Can IQ Thread use it?

Yes — that is the intended path. IQ Thread accepts data from an on-site collector over MQTT, so whatever it already speaks (OPC-UA, Modbus, MTConnect, Fanuc, S7, EtherNet/IP…) reaches IQ Thread without new PLC work. You provision a gateway per site, paste the generated config block, and its tags register themselves as they arrive. Because the collector stamps each reading at the source and the on-site queue survives internet outages, the history you get is the history that happened — not the part that made it through the WAN. Raw readings are kept for 30 days and hourly summaries indefinitely, so long-range trends stay cheap.

Does purchasing need our ERP, or does IQ Thread handle it?

IQ Thread handles the whole maintenance purchasing loop itself: requisition → RFQ → purchase order → receiving, with multi-vendor multi-brand pricing under one internal stock number and full price history. Shops without an ERP run purchasing entirely in IQ Thread; shops with one keep financials there and use IQ Thread for the maintenance-side flow.

How fast can it answer from OUR manuals?

Upload the PDF and IQ Thread indexes its text, tables, and page images. Typical manuals become answerable with page-level citations in about a minute; large or complex documents can take longer.

Where does our data live, and what is backed up?

Cloud workspaces isolate each tenant's operational database, document prefix, search collections, and device ownership. Nightly backups cover operational records, search data, ingestion records, and broker access state. Dedicated deployments use the same application with storage and AI providers configured for the installation. Ask us to walk through the exact data path before rollout.