Edmund AI Documentation
/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:

  1. Documents: getting documents into Edmund so they can be indexed.
  2. Programs: getting PLC programs and ABB robot programs into Edmund so they can be indexed.
  3. 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

NoIntegration typeWhat it meansWho does the workStatusTypical use case
1.1Manual upload (UI)Users upload documents directly in EdmundCustomer (no development)AvailablePOC, pilots, small plants, customers whose IT rules block automated data transfer
1.2Built-in connector: SharePointEdmund pulls documents from the customer’s SharePoint and keeps them in syncCustomer (one-time setup)AvailableDocument libraries as the customer’s source of truth
1.3REST APICustomer pushes documents into Edmund via APICustomer (development on their side)Roadmap (enterprise)Customer has an internal pipeline and wants machine-to-machine import
1.4Connector: other document systemsSame 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

NoIntegration typeWhat it meansWho does the workStatusTypical use case
2.1Manual upload (UI)Users upload PLC programs and ABB exports directly in EdmundCustomer (no development)AvailablePOC, pilots, one plant, one line
2.2REST APICustomer pushes PLC and ABB programs into Edmund via APICustomer (development on their side)Roadmap (enterprise)Customer has a CI or versioning pipeline and wants to push new program versions automatically
2.3ConnectorEdmund pulls programs from the customer’s PLC versioning tool (e.g. versiondog) and keeps them in syncEdmund (one connector per system)On request (enterprise)Repeated requests for the same platform become a standard connector
2.4Managed push serviceEdmund builds and runs a service that pulls program exports from the customer’s storage and pushes them into Edmund via APIEdmundOn request (enterprise)Customer refuses to do any development but wants automated sync

3. Chat integrations

NoIntegration typeWhat it meansWho does the workStatusTypical use case
3.1Built-in database connectorsEdmund chat queries the customer’s database directly during a conversation using a connector shipped with EdmundCustomer (one-time setup)AvailableLooking up live production or maintenance data while diagnosing
3.2MCPEdmund 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.3REST APICustomer calls Edmund’s chat from their own tools, outside the Edmund UICustomerRoadmap (enterprise)Embedding Edmund chat into a customer portal or internal tool