The platform

FactorySight answers a maintenance question and shows the page it came from.

It works from the machine's own manuals, reference images and repair history, on a phone, inside your network.

FactorySight answer with the cited manual page and reference images
A cited answer
FactorySight maintenance log form filled in from the conversation
A drafted log
FactorySight dashboard showing events by type for one machine
The machine dashboard
Three screens from the assistant: an answer with its sources open, a maintenance log drafted from the conversation, and the dashboard for one machine. The demo unit stands in for a machine.
How it is built

Four layers turn a question into a cited answer and a saved record.

A technician works on a phone. The assistant, the knowledge base and your plant network do the rest.

FactorySight architecture. A technician asks from a phone by text, photo or voice. The assistant combines nine skills to assemble a cited answer. A knowledge base and a maintenance memory sit underneath. Everything is served from inside the plant network. A technicianThe FactorySight assistantTextPhotoVoice 1 Assistant Speech to textPhoto analysisManual searchReference image matchMaintenance historyConversation memoryAnswer writingCitationLog drafting Assistant skills 2 Knowledge base and maintenance memory 3 PhonesTabletsQR codesLocal serverManualsJob cards Your plant network 4
    • Scan the machine's QR code, then ask by text, photo or voice.
    • Answers can be read aloud, for work that keeps both hands busy.
    • Chat history is kept, so a conversation can be picked up again.
    • It matches the question and the photo against the machine's manuals and reference images.
    • It reads the machine's maintenance history and the current conversation.
    • It writes numbered steps and attaches its sources.
    • Documents are stored with their pages, so a citation points to one.
    • Each log holds an event type, the reported issue, the root cause and the resolution.
    • History can be searched and filtered by period and by event type.
    • Phones and tablets connect over the plant network.
    • Manuals, photos and logs stay on infrastructure you control.
    • A connection indicator tells the technician whether the assistant is reachable.
Ways to deploy

FactorySight runs inside the plant.

The pattern is the same at every size: a server on the plant network, and the devices technicians already carry.

One plant

Serve one site from one server.

What you need
A server on the plant network, and phones or tablets with a browser.
What technicians do
Open the assistant, scan a machine and ask.
What stays local
Manuals, photos, conversations and logs.
Restricted networks

Run it without an outside connection.

What you need
The same server, with documents loaded on site.
How it works
Questions, answers and logs stay inside the plant network.
What to plan
A route for loading new manuals and updates.
Several plants

Give every site the same assistant.

What you need
A deployment at each site, with that site's machines and manuals.
What stays the same
The way technicians ask, log and review.
What differs
Each machine keeps its own history.

FactorySight is built so that its answers can be checked.

These principles shape how an answer is produced and shown.

Every answer cites its source.

Guidance points to a document and a page, so the technician can read the original.

It shows what it matched.

The reference images closest to the photo are displayed, not just a conclusion about them.

History is part of the answer.

Earlier interventions on the same machine are brought in when they are relevant.

Logs are structured.

Each record separates the reported issue, the root cause and the resolution, so it can be searched and compared.

The technician edits before saving.

A drafted log is a suggestion. The person who did the work confirms what goes on record.

Knowledge stays in the plant.

Documents, photos and records are held on infrastructure you control.