Tek Sistem ERP integration
Connects manufacturing and HR ERP records to a shift assistant.
The Tek Sistem ERP connection provides a controlled access layer for leave and personnel data, OEE measurements, downtime records, work orders, mould and maintenance information. During initial use, the team should record the source of the question, applied filters and any confirmation step. That trace makes it visible that the connection is being used with the right scope in daily work.
Connector facts
- Availability
- self_hosted
- Authentication
- bearer
- Domain
- erp
- Kobi per call
- 0.1
Data surface and the business question
The Tek Sistem ERP connection is designed for leave and personnel data, OEE measurements, downtime records, work orders, mould and maintenance information. Connects manufacturing and HR ERP records to a shift assistant. That means an assistant uses the permitted live-system context instead of guessing from a document. The result still depends on the freshness of the source system and the permissions granted to the connection.
A useful request makes clear which record is needed for which team. For this connection, a reliable flow is starting with a line or work order, then assessing the fault record together with the related procedure document. This makes filters and source records easier to inspect than asking for a broad list to be summarised.
Permissions, confirmation and responsibility
all defined tools are read-only; the assistant cannot close a work order or change an ERP record. This is more than a technical detail: an incorrect action in a financial, customer, production or legal record can have real consequences. Reading a result and changing an external system are not the same level of authority.
Before rollout, decide which assistants and departments can see this data. If a result is unexpectedly broad, reduce the access scope; if data is absent, do not let the assistant invent the missing record. The underlying system record and the accountable owner remain the final check for every consequential result.
Setup and operational review
is installed on a self-hosted mcp-host with a bearer token; only the tool subset for modules the business uses is enabled. At setup, use a separate connection identity with least privilege so the accessible data does not exceed the operational need. For OAuth connections review the consent screen; for bearer connections review token scope, storage and ownership with the responsible team.
26 read-only tools and 0.1 Kobi Credits per call. This statement comes from the catalog or tool definition; no extra count is invented for a vendor-managed changing surface. During a pilot, observe real questions, returned records, confirmation steps and unnecessary calls. That evidence makes cost visible and exposes over-broad permissions early.
Frequently asked questions
What can this connection query?
leave and personnel data, OEE measurements, downtime records, work orders, mould and maintenance information
What is a reliable working flow?
starting with a line or work order, then assessing the fault record together with the related procedure document
Are write operations unrestricted?
all defined tools are read-only; the assistant cannot close a work order or change an ERP record
How is the connection set up?
is installed on a self-hosted mcp-host with a bearer token; only the tool subset for modules the business uses is enabled
Which metric is verifiable?
26 read-only tools and 0.1 Kobi Credits per call
What should I do with the result?
Review the result against the relevant system record and company policy; an assistant response does not replace an authorised person’s decision.