Improve every shift.
IQ Thread connects production plans, operator execution, machine behavior, maintenance work, and reliability evidence in one continuous operating thread—so every shift can plan, act, learn, and improve from the same facts.
- coordinate production and maintenance on one machine-time plan
- give planners, operators, technicians, and reliability teams the workspace their decisions require
- turn every run, stop, repair, and close-out into evidence for the next decision
Get your workspace
Create a workspace free. Add a card when you're ready to start the 30-day full trial.
$90 / user / month (introductory price)
The plan, the machine, and the work share one clock.
Production jobs and maintenance work remain separate records, but both teams see the same machine-time picture. Exact job windows, maintenance windows, live downtime, and unplaced work stay visible. Overlaps become explicit decisions and requests—not surprise schedule changes.
Coordinate production and maintenance on the same machine clock.
Build the dispatch sequence, then place queued jobs across machines and time on a live timeline. Job windows, exact maintenance windows, active downtime, unslotted maintenance, and the current time share each machine lane. Overlaps are checked before a move is saved; maintenance is never rescheduled behind the planner’s back.
- drag queued jobs between machines or along the timeline; use exact-time controls when precision matters
- see blocking maintenance, reduced-capacity work, live downtime, and open capacity against the jobs they affect
- send a durable request to the other team without moving either schedule automatically
- use verified free gaps before maintenance reserves machine time
Give the person at the machine the next useful action.
The phone and tablet experience stays focused on execution: see the running job, read instructions, record good and scrap output, explain downtime, complete a checklist, report a problem, or ask about the machine without leaving the floor.
- maintenance constraints appear before an operator starts work
- run-signal history and production counts support the human record
- free operator access keeps observations tied to the person and shift
Work the right problem with the evidence attached.
Requests become structured work with asset, component, condition, production demand, assignment, procedure, parts, labor, attachments, and close-out evidence. Priority recommendations explain every factor and keep missing evidence visible.
- Today, Kanban, calendar, PM plans, procedures, and mobile execution
- parts, costs, documents, meter conditions, notifications, and follow-up
- close-out codes and repair detail feed reliability and case memory
Turn repair history into fewer repeat failures.
Downtime episodes, coded failures, component paths, labor, parts, direct cost, and available runtime evidence come together by machine. Repeat patterns become visible, close-outs become searchable cases, and observed recurrence can challenge the assumptions in the FMEA.
- downtime by reason and machine with episode-level coding
- failure modes, causes, assemblies, recurrence, and repair effort
- FMEA and case memory stay connected to what the plant observed
See production and maintenance as one operating result.
Machine state, running jobs, good and scrap counts, rate, downtime, maintenance holds, and measured OEE share one board. Shift, cell, work-order, spend, inventory, downtime, failure, and reliability reports let each team follow the same evidence from a plant view down to the source record.
- job progress beside machine state and maintenance constraints
- OEE remains undefined until the required production evidence exists
- reports preserve scope, time window, and drill-down evidence
From one run signal to a connected plant.
Start manually, bind one existing signal, or connect the broader machine-data stack. Stored tags, formulas, SHARC channels, i3X objects, run states, counters, and meters become reusable signals for dashboards, downtime, production counts, condition rules, and analysis.
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.
Questions owners actually ask
How much does it cost?
Maintenance seats are $90 each per month with a 3-seat minimum ($270/month). Operators are free and unlimited. Machine-data gateways are $90 per connected site per month. Purchasing, analytics, IQ, and preventive maintenance are included. You can create a limited workspace without a card; adding one starts the 30-day full trial.
Can IQ take action, or does it only answer questions?
It can do both. The maintenance assistant can analyze live records and cited documents, inspect production and maintenance timing, find verified free gaps, and then use role-checked tools to schedule authorized work, create or update work, build procedures and PM plans, configure dashboards, and add meter rules. Tool results remain visible, and destructive actions require confirmation.
Does the system automatically reschedule production or maintenance?
No. Production jobs and maintenance work remain separate records. Both teams see the same machine-time projection, conflict advisories, verified free gaps, and durable move requests, but an authorized person decides whether either schedule changes.
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 without a 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. The collector timestamps readings at the source, while the gateway kit's local MQTT bridge queues across WAN outages and drains after reconnect. Raw retention is configurable and permanent hourly summaries keep long-range trends economical.
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.