/ENGINEERING REFERENCE
How Edmund connects to surrounding systems
The ways documents and programs get into Edmund and how Edmund chat works with customer systems live, with who does the work and what is available today.
Overview of the ways Edmund can be connected to customer systems, so that “integration” always means one specific row in one of the tables below.
Three categories:
- Documents: getting documents into Edmund so they can be indexed.
- Programs: getting PLC programs and ABB robot programs into Edmund so they can be indexed.
- Chat integrations: Edmund chat working with customer systems live, during a conversation. Nothing is imported or indexed.
Status values:
- Available
- On request (enterprise): available as custom development
- Roadmap (enterprise): planned for the product and can be prioritized on request
1. Documents
| No | Integration type | What it means | Who does the work | Status | Typical use case |
|---|---|---|---|---|---|
| 1.1 | Manual upload (UI) | Users upload documents directly in Edmund | Customer (no development) | Available | POC, pilots, small plants, customers whose IT rules block automated data transfer |
| 1.2 | Built-in connector: SharePoint | Edmund pulls documents from the customer’s SharePoint and keeps them in sync | Customer (one-time setup) | Available | Document libraries as the customer’s source of truth |
| 1.3 | REST API | Customer pushes documents into Edmund via API | Customer (development on their side) | Roadmap (enterprise) | Customer has an internal pipeline and wants machine-to-machine import |
| 1.4 | Connector: other document systems | Same pattern as SharePoint for other document / content management systems (e.g. Google Drive) | Edmund (one connector per system) | On request (enterprise) | Repeated requests for the same platform become a built-in connector |
2. Programs
| No | Integration type | What it means | Who does the work | Status | Typical use case |
|---|---|---|---|---|---|
| 2.1 | Manual upload (UI) | Users upload PLC programs and ABB exports directly in Edmund | Customer (no development) | Available | POC, pilots, one plant, one line |
| 2.2 | REST API | Customer pushes PLC and ABB programs into Edmund via API | Customer (development on their side) | Roadmap (enterprise) | Customer has a CI or versioning pipeline and wants to push new program versions automatically |
| 2.3 | Connector | Edmund pulls programs from the customer’s PLC versioning tool (e.g. versiondog) and keeps them in sync | Edmund (one connector per system) | On request (enterprise) | Repeated requests for the same platform become a standard connector |
| 2.4 | Managed push service | Edmund builds and runs a service that pulls program exports from the customer’s storage and pushes them into Edmund via API | Edmund | On request (enterprise) | Customer refuses to do any development but wants automated sync |
3. Chat integrations
| No | Integration type | What it means | Who does the work | Status | Typical use case |
|---|---|---|---|---|---|
| 3.1 | Built-in database connectors | Edmund chat queries the customer’s database directly during a conversation using a connector shipped with Edmund | Customer (one-time setup) | Available | Looking up live production or maintenance data while diagnosing |
| 3.2 | MCP | Edmund chat connects to the customer’s tools via MCP and works with them live during a conversation (search, look up records, read current state). Data stays in the source system. | Edmund (generic MCP client), customer (their MCP servers) | Roadmap (enterprise) | “Is there an open ticket for this machine?”, checking a Confluence page while diagnosing |
| 3.3 | REST API | Customer calls Edmund’s chat from their own tools, outside the Edmund UI | Customer | Roadmap (enterprise) | Embedding Edmund chat into a customer portal or internal tool |