Manufacturing & Industrial
Your plant runs on a system nobody can connect to.
The ERP was built for your process fifteen years ago, the MES exports to CSV and the real planning happens in a spreadsheet on someone's desktop. Referent connects to all three at the data layer and answers from live production data.
0104How it connects
It connects where your interface already connects.
It maps the queries, the actions and the endpoints behind the interface, then connects at that level. Nothing to rebuild, nothing to migrate.
Your team
Questions and work, in plain language
Chat, Slack, Teams or Telegram. Ask for a number, a report, a draft or a status. No new tool to learn.
Referent
The layer that understands your systems
Maps queries, actions and endpoints. Answers from live data with citations back to the source. Executes the work on top: pulls the numbers, builds the report, drafts the follow-up.
Your software
The systems a plant actually runs on
Custom ERP with no connector, an MES that only exports files, quality records in a shared drive and the planning spreadsheet everyone depends on. Referent maps how your own interface reaches them and connects at that level.
- Custom ERP
- MES / SCADA exports
- Planning spreadsheets
- Quality records
- Supplier email
Standard tools too
The 50+ connectors everyone advertises are included. That part is commodity. The hard systems are the point.
- Microsoft 365
- Google Drive
- Slack
- Jira
- Salesforce
This is not RPA.
No screen reading and no bots clicking buttons. Referent connects at the data layer, so a UI change does not break it.
0204Use cases
Four questions your plant asks every week.
Each one is answerable from data you already hold, once something can reach it.
0304Deployment
Days, not months.
There is nothing to migrate and nothing to rebuild, so the timeline is short by construction.
- 01
Map the system
We watch how your existing app talks to the system underneath and document the queries, actions and endpoints behind it.
- 02
Connect at the data layer
Referent connects directly at that level. No connector to build, no migration, no change to the software your team uses every day.
- 03
Validate with your team
The people who know the process check the answers against reality. Permissions are mapped to the roles you already have.
- 04
Live
Your team asks in plain language and gets answers from live data, with citations. Scope grows from there.
Reference deployment
A mid-market manufacturer, on a custom ERP.
Mapped, connected and in production in under a week, on a system no AI product could reach.
- System
- Custom ERP
- Time to production
- One week
- Migration required
- None
0404Security
Built to clear the security review, not to argue with it.
Most AI proposals die in IT. These are the properties that get the conversation past that point.
- 01
Single-tenant isolation
Your deployment runs in its own environment. Nothing is shared with another customer.
- 02
Zero-retention models
Prompts and responses are not stored by the model providers and are never used for training.
- 03
Your permissions, mirrored
Referent respects the access rules your systems already enforce. Nobody sees what they could not see before.
- 04
No data duplication
Answers are fetched from the live system at query time. We do not build a second copy of your database.
- 05
GDPR
European data protection requirements are part of the deployment, not an afterthought.
- Read the security detail