No. It is advisory: it reads documents, photos and logs and tells a person what to check. It has no connection to equipment controls, and we do not plan one.
Isolation and safety steps from your manuals (lockout/tagout, pressure release, PPE) are reproduced in sequence at the top of every checklist and cannot be collapsed or reordered. Requests to bypass interlocks or guards are refused with the manual cited and escalated. This is a hard rule, not a setting.
The case escalates to the named senior engineer for that product line with the evidence assembled — symptom, checks performed, what the documents do and do not cover, machine history. The agent does not improvise diagnostics.
Any equipment with service documentation: machine tools, presses, packaging lines, HVAC, compressors, medical and lab equipment, vehicles and off-highway, printing, food processing. The product is manual-driven, not equipment-specific.
They stay in your tenant on Google Cloud, are used only to answer your technicians and dealers within the scope you set, and are never used to train models. See the DPA and sub-processor list.
Manuals are indexed per revision; bulletins are mapped to the sections they change. The unit's serial, firmware and upgrade history select the right documents. Hybrid units are flagged and composite procedures are marked by source revision.
Yes — visible conditions such as corrosion, leaks, burnt terminals, wear and misalignment are read and named with a confidence level. Nameplates and HMI screens are OCR'd. Blurry photos prompt a specific request, not a generic one.
Dealer notes live in the dealer's workspace, labelled as non-OEM, and never appear in the OEM's checklists or other dealers'.
Every check cites a page, so accuracy is verifiable step by step. The failure mode we design against is a confident wrong answer; the pipeline rejects uncited steps and escalates uncovered symptoms rather than guessing.
Manuals, bulletins, catalogues and schematics as PDF (text or scanned) or DOCX; work-order exports as CSV/XLSX; installed-base records as CSV/XLSX; alarm logs as CSV or screenshots; photos as JPG/PNG/HEIC.
Not required. Technicians use the web or mobile interface; work-order summaries export as text. API integration (cases in, summaries out) is available on Enterprise. IoT alarm feeds can be connected on Enterprise.
Upload one product line's manuals, bulletins, catalogue and a work-order export; the index is ready the same day. Most pilots run two weeks on one product line before expanding.
One diagnostic session for one machine — any number of turns within 24 hours, up to three photos (+0.1 case per additional photo), including the work-order summary. Manual and bulletin indexing is free.
Separately, at the provider's list price, as model_access_usd on your invoice. Vision-capable models cost more per request than text; the ledger shows tokens per case. With your own key the meter is zero.
The charge lands on your existing Google Cloud invoice and counts toward committed spend. Private offers for annual plans. Direct invoicing from Carnegie Intelligent Technology Limited (Hong Kong) is available.
Yes. Dealer workspaces can sit under the OEM's plan or be billed directly to the dealer; the usage ledger is per workspace either way.
Monthly case cap and model-spend cap per workspace. At the cap new cases queue and the owner is notified.
The product is being built with a small number of equipment makers and service networks using their real manuals and work orders. You get a workspace, direct access to the team and pricing locked at today's rates for the first year. Some capabilities on this site describe designed behaviour not yet live.
We are onboarding a small number of design partners with real documents and real deadlines. Tell us what you work on and we will set up a workspace with your material.