As an administrator, you prepare the environment for the whole organization. Manage access, configure projects, maintain knowledge and connect data sources. Read from the beginning or open the administration area you need.
Learn how Edmund works with your equipment’s knowledge and where to begin.
Edmund is an assistant for the shop floor. Ask it about a machine and it searches that machine’s own knowledge: its manuals, drawings, PLC programs, maintenance history and connected data. Links in the answer take you to the sources it used.
Each machine or production line can be a project. A project holds that machine’s knowledge and chats, so you ask in the context of the equipment in front of you. Open the right project from the list or by scanning its QR code. Find a project and its QR code.
Where answers come from
Documents: manuals, drawings, part catalogs and other files.
PLC and robot programs: the machine’s control logic, where you can find related signals and program sections.
Ask in plain language in the chat. Edmund’s search assistants explore the available sources, and you can watch the search progress. An answer may include a citation: a link to a particular document or record. Database results may appear as a table. You can rate an answer with a thumbs up or down.
If the project’s knowledge does not cover your question, add the equipment or fault identifier and ask for a specific source. Tell whoever maintains that machine’s knowledge about a missing manual, drawing or record.
New here? Start by signing in and opening a project. Then ask one specific question and read the answer together with its sources.
Administrator · Getting started
Sign-in and invitation
Accept your invitation and sign in with your work email and password or your Microsoft work account.
Your first invitation
Your administrator sends an invitation to your work email. Open the message and follow its link. For password sign-in, set your own password as instructed during first access. If the link has expired or you cannot find the message even in your spam folder, ask the administrator for another invitation.
An invitation is valid for 24 hours only. After it expires, ask your administrator to send it again and use the new link.
Sign in with email and password
In Email address, enter the work address that received the invitation. Enter your password in Password.
Click Sign in. If two-factor authentication is enabled, complete the additional verification when prompted.
Use Forgot your password? to reset a forgotten password, then follow the email instructions.
If your organization uses Microsoft SSO, choose Sign in with Microsoft.
Choose the correct work account in your company sign-in and complete the requested verification. On returning to Edmund, you see the workspace you can access.
Signing in does not grant new projects. Your administrator manages missing access through teams. After signing in, set your account language and security.
Administrator · Getting started
Personal settings and security
Manage your interface language and sign-in settings in your account.
Open the profile menu
Click your profile at the bottom of the left menu. The menu contains appearance choices, account settings, the privacy policy and sign-out. Use this menu for the following steps.
In the profile menu, choose System, Dark or Light. System follows your device settings. You can choose the appearance without opening account settings.
The Product tour card lets you enable or disable guidance through Edmund’s features. If you are still getting familiar with the application, use its switch to enable the guidance again.
The sign-in email in Account information is read-only. Under Password, open Change password and follow the form. With Microsoft SSO, sign-in is managed through your company account.
Further down the page, Two-factor authentication shows whether the additional sign-in check is enabled. If it is Inactive, choose Set up and follow the wizard. Store recovery codes securely; do not share them in chat or documentation.
The profile menu also contains Privacy policy. Open it to read how personal data is processed and protected. You can return to this information from the same menu at any time.
Open your profile again at the bottom of the left menu and choose Logout. This ends the session under your account, especially when using a shared computer.
Open Account preferences and find Signed-in devices. If you lose a device or need to end all browser sessions, choose Sign out of all devices. This ends sign-in sessions across devices. To finish work in this browser only, use Logout in the profile menu.
After opening a project, explore the main menu, the path at the top and the chat list. You will know where to start and how to return.
Two levels in the left menu
The left menu is your starting point. Dashboard and Projects at the top belong to the organization. Dashboard shows a summary; the project list takes you to a particular machine.
After opening a project, its name appears above Chat, Project Dashboard, Documents, Automation Logic and Project journals. These entries concern the selected project. An arrow expands a submenu; automation logic contains PLCs and robots.
A path above the content shows your location, such as the project name and Chat. Clickable parts return to those pages. The project name here and in the left menu identifies the machine you are working with. Open Projects again to choose another machine.
Menus show the functions available to your role and enabled modules. Now open your first project.
Administrator · Getting started
Organization, project and knowledge
An organization is your company’s workspace. A project brings together the sources for a machine or production line.
Organization and project have different scopes
Organization is your company’s workspace: it brings together projects, people and shared settings.
A project represents a specific machine, line or process unit. It groups that equipment’s knowledge and chats. Open the relevant project for another machine.
Documents: manuals, schematics, drawings and other files.
Automation Logic: imported PLC and robot programs, signals and relationships.
Project journals: failures, repairs, adjustments and operating experience.
Database sources: assigned data such as stock items or fault records. Read query results as a table in chat.
Edmund searches sources available to the current project. Attaching a file to a message does not permanently add it to project knowledge. How to open original sources.
Administrator · Getting started
Find and open a project
Choose the project for the machine or line you are working with.
From the left menu to a project
Click Projects in the left menu.
Search for the machine or line name. Available tags help narrow the list. Edmund remembers selected tag filters. If nothing appears, clear the search and filters and check further list pages.
Click the project card. It opens that project’s Chat; its name appears on the left and at the top.
In the Filters panel, Machine 1 is selected. Matching projects remain on the right; purple tags on their cards show the assigned values. Project, group and tag names are organization data and are not translated when the app language changes.
Selecting the project card opens its chat. The machine name appears in the left menu and the navigation path at the top. Start a new chat here, or use the project menu to open its documents and other sources.
Scan the QR code assigned to the machine. Sign in if requested. The code is a shortcut to the project; it does not grant new permissions. If the project cannot be opened, send its name to your administrator.
In the project list, open the project’s QR icon. The dialog lets you download a PDF. Place the printed code by the correct machine and protect it from dirt.
For a data summary, open Project Dashboard in the left menu. See Organization, project and knowledge for the difference from the entire organization.
Administrator · Working with chat
Your first chat: from question to answer
Keep one topic in a chat. Ask a question, wait for the answer and add further observations when needed.
Help Edmund find the right source
Write as if to a colleague who cannot see the machine. Include the machine or section, the exact symptom and code, the source you want and the desired output. For example: “The film unwinder shows [exact HMI code] after the cycle starts. Find its meaning in the manual and related program signals. Cite sources and list steps I can verify.” Replace the bracketed text with the actual code.
Copy alarm identifiers with their letters, leading zeros and punctuation. A short, specific request such as “Find the wiring diagram for sensor [identifier]” can be more useful than a long general description.
Write and send a question
In your project, open Chat → New chat. Write what you need in the message field. Include the alarm identifier, symptoms and circumstances. Instead of “It does not work”, try: “The wrapper reports a film alarm after the cycle starts. Where does the manual explain it, and which related journal entries do we have?”
Click the Send arrow. While the answer is generated, you can see search progress and a Stop button. Some other actions may be unavailable until the response finishes.
While a response is being generated, Send changes to Stop, shown as a square icon. The example highlights it in the lower-right corner of the message box.
Click it to interrupt the current response. This does not delete the chat. The message is marked as stopped, and the application states that Edmund cannot use stopped messages for later answers. To continue the request, send it again or write a new message.
Read the answer and open its sources. Then use the same field to ask a follow-up: “Explain the point about the sensor” or “Compare this entry with the previous similar event”. You do not need to repeat the whole chat.
Clearly distinguish new observations from assumptions: “The diagnostic screen currently shows…”. Ask Edmund to locate a source when one is missing. For another machine or unrelated problem, start a new chat in the appropriate project.
Administrator · Working with chat
Attachments, photographs and voice input
Attach supporting information to your question and explain what Edmund should look at.
Attach a file or photograph
Click the Upload files paperclip, choose a file and wait for it to attach. Add context, such as “This photograph shows this morning's alarm; please explain its identifier”. Check the attachments before sending.
You can also attach HEIC / HEIF photographs, for example from an iPhone. Edmund converts HEIC photographs to JPEG during upload, so you do not need to convert them first. Check that the photograph has attached to the chat before sending.
You can also add a file through Attached files at the top of an open chat.
Open Attached files.
Click the upload arrow in that tab and choose a file.
Wait for the upload to finish. Then return to the messages and explain what Edmund should look for in the file.
This route also creates a temporary attachment for that chat, rather than a permanent project document.
Attachment readability and chat context
Edmund primarily works with digitally readable text. A document whose text can be selected and copied makes exact names and values easier to find. With a photograph or scan, resolution, sharpness and legibility matter; add the alarm, part identifier and what you need to find out in your message.
Chat context has a limited capacity. A large file, many attachments or a long chat may not fit in full. If Edmund does not refer to a relevant part or asks for less content, select the relevant pages, divide the file or question into smaller parts and identify the exact section. Start a new chat for a separate topic when needed.
From a temporary attachment to project knowledge
Attached files holds files for that chat. Attaching a file to a message does not automatically add it to permanent project Documents. To use the source in other chats and share it with the team, a User expert or administrator uploads the original file through Documents → Upload documents and waits for processing. A User passes the file to that person. This is a separate upload, not an automatic transfer of the attachment.
Click Start voice input. Allow microphone access if the browser requests it for this task. Review the transcription, especially alarm numbers, part names and signal identifiers. Correct errors before sending.
If the microphone is unavailable or the surroundings are noisy, type the message instead. The message should be understandable without the original audio context.
You can attach a PDF or a PNG, JPEG or HEIC/HEIF photograph, as supported by the file picker. Make sure an HMI photograph clearly shows the alarm identifier. Voice input works on desktop and phone; always check the transcription before sending.
Administrator · Working with chat
Reading answers, citations and search progress
A citation is a link to an original source supporting part of an answer.
Recognize a source in an answer
Some claims have a clickable source label, such as a document title or a dated journal entry. It may appear as a small chip, an inline link or a grouped chip showing additional sources with +1. This is a citation.
Click the source name beside the claim you want to check. A grouped chip first offers several sources; select one. The answer itself is not necessarily a verbatim quotation of the source.
Opening a citation displays a source panel beside the chat. Read the original content and any date, version or entry attachments. For a document, review the relevant page and its surrounding context. For a journal, check that it describes the same machine and a genuinely similar issue.
Close the panel using Close and continue in the same chat. Ask, for example, “Explain the difference between this source entry and my situation.”
A button such as Searching in journals or document search shows the assistant's activity. Expand it to read the available progress details. Progress explains where the search took place; a citation opens a specific supporting source.
A database answer may also expose the database query in its search progress. Check that it matches the requested equipment and period.
A document reference opens the relevant page and available highlighting; a program source points to the corresponding part of the imported logic. A database result may have no document-style citation for every row. Check its request, period, columns and units instead.
When an expected citation is missing
An answer without a citation is based on Edmund’s general knowledge. If Edmund does not cite the document you expect, check that it is uploaded to the relevant project and has finished processing. Find its name and content in Documents; a User expert or administrator can help add the source. Then specify the document or section Edmund should use in your next message.
Rate an answer with thumbs up or down
Two rating icons appear beneath an answer. Use thumbs up, Good response, when the answer helped. Use thumbs down, Bad response, when it is incorrect, incomplete or unhelpful. Rate the particular answer directly above the icons.
Clicking thumbs up or down saves your rating immediately. A comment is optional. A time-saved estimate is offered only after thumbs up, with no value preselected.
If a follow-up form opens, describe what helped or what is wrong. For an error, identify the correct source if you know it. Ask another question in the same chat when you need further explanation.
Some chats also show a How did Edmund do? panel with Helped and Didn’t help, as in the following example. Rate it according to the actual outcome.
Your chats remain in My chats. Shared chats provide a reference for colleagues.
Find an earlier chat
Select an earlier chat in My chats. If you cannot see it, use Search and enter part of its name or the topic. Its previous messages and answers remain available, so you can continue with a new question.
New folder creates a personal folder for your chats. The next section shows how to move a chat into it using Chat actions.
You can also start a new chat directly inside a personal folder.
Open the chat and click the three-dot Chat actions beside its title. The same menu appears beside the chat in the left list. Rename changes its searchable title. Move to folder organizes the chat in your folders; it does not share it with others. Delete removes the chat.
Rename opens a small dialog with the current title. Replace it with a name describing the machine and topic, such as “Strema 5997: film unwinding”. Confirm with Save. Close dismisses the dialog without saving. Renaming does not edit earlier messages.
Move the pointer over your own message and click the Edit pencil. Its original text opens in an editable field. Correct an alarm number or missing context and confirm with Send. Cancel keeps the original wording.
Add new observations as a new message
Editing an earlier question may reprocess the following answer. When you simply have a new observation, add it as a new message below the existing chat.
If Edmund is generating an answer, wait until it is complete. Sharing is unavailable during generation.
Open your own chat and click Share at the top. User and User expert can select only General. Administrators may also choose Onboarding for introductory and training chats. Confirm sharing to the selected folder.
You share the original chat, rather than a copy. As its owner, you continue in the same chat under My chats. Other people with access to the project can read new messages as well; sharing does not let them write in your chat.
Sharing started by a User or User expert lasts 30 days. An administrator can renew sharing for another 30 days, keep it open without automatic expiry or stop sharing. The owner can also stop sharing their chat.
Once you can write your own question, a prepared suggestion can make repeated work easier.
What a suggestion is
A suggestion is a prepared query you select instead of typing it into the message field again. It can contain a complex task, a frequently used question or a template with details to fill in. For example, it may ask for similar faults, a comparison of solutions and source references. The administrator sets its name, content and availability. Read the query after selecting it, adjust it if needed and send it.
Choose a suggestion below the logo
The chat start screen shows suggestion tiles below the Edmund logo. Select a topic and read the inserted query. Send a complete query as it is, or add the machine, part or fault identifier if needed.
The available suggestions can differ by project and language. If one is missing, write your own question; start a new chat for a new topic.
Administrator · Working with chat
Incident analysis from start to conclusion
Incident analysis investigates an issue using the available sources and context.
1. Open incident analysis and describe the situation
Open chat in the project and choose Analyze an incident. Use this mode to connect symptoms, source material and new findings. State the machine, exact symptom, start time, operating state and checks actually performed. Say “unknown” when a fact is missing.
Practice prompt: “The film does not unwind when wrapping starts. The issue appeared after changing the roll. The display shows [exact alarm]. The sensor and cable have not been inspected. Find related sources and ask for missing information.” Replace brackets with the actual observation. Attach photographs using the paperclip.
Investigation effort offers Low, Medium and High. Choose how thoroughly Edmund should investigate. Review the prompt and click Analyze. Follow the search progress while the response is generated and wait for completion before drawing a conclusion.
Back to chat leaves the mode before sending. You can interrupt generation using the square Stop button in the message field; its appearance is shown in the first-question chapter.
The completed response is a structured Incident Analysis. Its top strip shows investigation effort, the number of cited sources and the analysis duration. Incident update summarizes the current conclusion, possible branches and suggested continuation. It does not confirm a repair.
In the example, Edmund states that the cause is still unconfirmed. It connected roll-loading instructions, sensor fault history and PLC information. Separate source facts from conditions actually checked on the machine. Open the source names beside individual paragraphs to verify them.
Next steps appears below the update. Each card has a number, title, priority and explanation. Here the first asks for the actual alarm and sequence step; others explore roll loading or the sensor. The number and content of cards depend on the analysis.
Clicking a card neither performs a machine check nor sends a message. It prepares a follow-up in the composer. Use Add your own follow-up to continue with a different observation.
Supporting evidence groups relevant findings, such as PLC and database evidence. Expand a group to read it. Evidence gaps separately lists what remains unsupported; the number in brackets counts these gaps.
Separate assumptions from verified findings
Here the exact alarm, sequence step, inspection results and live values are missing. Without them, the text cannot identify a specific failed part. An empty database search does not necessarily prove that an event never occurred. Add observations that distinguish the remaining possibilities.
Expand Investigation activity below the result to see the types of sources Edmund searched. Individual search items can be expanded further. The list explains the search process; it does not prove that the conclusion is correct. Compare claims with their cited sources.
After choosing a card, Continuing selected analysis appears. Expand Prepared reply to read the prefilled instruction. Add your observations below; continuing combines the prepared instruction with your notes. Do not report a check that was never performed.
Your own notes are kept when you select a different suggested next step.
Here we stated that the alarm, sequence step and roll movement were still unknown and asked which HMI readings were needed. Continue submits the follow-up in the same investigation. Remove selected step clears the choice; Back to chat leaves the mode before sending. Investigation effort can also be adjusted for the continuation.
The next response again contains an update and fresh continuation cards. Edmund adapts the investigation to your input. In the example, identifying the missing information leads to more specific questions about the HMI readings. This is a training-chat result, not a universal machine work instruction.
Report actual outcomes in the same chat. Clearly mark unconfirmed causes and request a summary of findings, work and open points. An analysis does not automatically create a journal entry; a User expert or administrator records it if needed.
Continue the analysis with a suggested step or your own additional observation. Opening a regular new chat starts a separate conversation outside this incident flow. A more detailed search may take longer.
The overview connects summary information with individual projects and sources.
Organization overview
Open Dashboard in the left menu. It summarizes available projects and knowledge, activity and links to items needing attention. The visible scope follows your access.
Click the document alert row or the arrow on its right. It opens the affected project’s documents with a filter matching the alert. For example, a duplicate alert opens the list filtered to Status: Duplicate. A total document count does not mean that every document has been processed successfully.
The complete dashboard, including the lower charts, is shown below. Click Enlarge example below the illustration and set browser zoom to 100% to read small values.
Inside a project, select Project Dashboard. It provides a chat entry point, your recent chats, source status and the latest Maintenance journal entries. The Documents chart and table share one block, showing document types and processing status. Click a maintenance entry to open the original record.
Click a maintenance entry name, or click the alert row or the arrow on its right. Continue to chat when you need an explanation; open the document or journal list directly when you already know which item you need.
Needs attention separates issues from summary counts. The example shows 47 duplicate documents: the same files have already been uploaded. These are not 47 processing failures. Click the alert row or the arrow on its right to open the affected project’s documents filtered to Duplicate.
Knowledge Base shows counts of documents, maintenance entries, PLC programs and robot programs. Use the controls above the charts to change the view and period.
Documents shows processing status and whether files are available for search. Duplicates are counted separately.
Activity compares the numbers of chats and maintenance entries in the selected and preceding periods.
Your recent chats lets you quickly reopen your latest chats.
Data sources (administrators only) shows connection status. Click a source to open its settings.
Ask a data question, read the result table, reveal more columns and download a CSV file. The project must have the appropriate data source assigned.
Specify the scope of a data question
Open chat in the relevant project. Specify the records, period and fields you need. For example: “From the connected database, show at most five latest fault records as a table with all available columns.” Add a machine identifier for one machine, or start and end dates for an exact period. Then click Send.
The following example contains the five latest database records and 28 columns. It is not automatically limited to one machine. Ask an administrator if a connection is missing or you do not know which data the project uses.
The first table row contains column names; the rows below contain record values. Here each data row represents one fault. First read which records Edmund included: five displayed records are not the entire database history.
The example shows the left edge of the table. More columns continue beyond the right edge. The next example shows how to reveal them with the scrollbar.
Scroll the table left and right
Go to the bottom edge of the table itself, below its last row. The horizontal scrollbar has a track and a movable thumb. Drag the thumb right to reveal columns on the right; drag it left to return to the first columns. A horizontal touchpad gesture also works.
The example highlights the scrollbar at the bottom of the table. Try scrolling the columns directly in Edmund.
Click the small arrow button beside a column name, for example Order number. The table sorts by that column and the arrow indicates direction. Sorting acts on the displayed result; it does not rewrite database records.
CSV is a table-data file that you can open in a spreadsheet application. Click Export below the table, then choose Export CSV or Export XLSX. The browser downloads the result file. Open it in a spreadsheet application and check headers, row count, period and units. The CSV belongs to this query result; it does not automatically export the entire connected database.
Per page changes the displayed row count. Ask a follow-up question for different records or columns, such as “Limit the result to last week and keep the date, machine and description.” The next example highlights Export, which opens the format menu.
Continue in the same chat, for example: “Show this table as a chart. Label the axes, units and period.” Specify the horizontal-axis value and what you want to compare. Charts are not automatically included in every database answer.
Check the chart legend, axes and units against the table. The following example shows frequency and cumulative share. Export PNG downloads a chart image; download the underlying table separately with Export CSV.
This separate chart example uses a different query and a frequency summary; it is not a conversion of the five rows shown above. The chart type and available export depend on the particular result.
Database search can be improved over time. Alongside table and column names, Edmund can use a plain-language database description. It explains what the data means and how it is related: for example, which columns identify a machine or spare part, the units used for downtime, and which identifier links the tables.
If Edmund repeatedly misinterprets an abbreviation, value or relationship, send your administrator the specific question, the incorrect interpretation and the correct explanation. The administrator can refine the description. Better context may help Edmund select and find the right data; continue to check each answer against its results.
Your role determines what you can do. Teams affect which projects you can access.
User, User expert and administrator
User uses chat, reads available sources, opens answer references and gives feedback. User expert also manages documents, programs and journal entries in accessible projects. Administrator additionally manages projects, people, teams, tags, suggestions, connections, organization journals and analytics.
User and User expert can share chats only to General. Sharing to Onboarding is reserved for administrators. The application may also offer a Reader role for viewing information without using chat. This manual has separate paths for the three main roles.
Clear project search and filters. If a project is still missing, ask your administrator to check team membership and the project's assignment. If you can see the project but cannot upload or edit, ask them to check your role.
A project without an assigned team is not automatically private. Administrators can inspect the permission matrix in Users → View permissions. The administrator manual also includes User and expert workflows.
For the User role, the absence of document upload and knowledge editing is expected, not an error. Ask a User expert or administrator to add new source material.
A role determines permitted actions; a team determines available projects. Readers can view source material but cannot use chat or rate answers. Administrators see all projects; other roles see their teams’ projects and projects without an assigned team.
Action
Administrator
User expert
User
Reader
Use chat and rate answers
Yes
Yes
Yes
No
View documents, programs, data sources and journals
Yes
Yes
Yes
Yes
Manage documents and programs
Yes
Yes
No
No
Manage maintenance entries
Yes
Yes
No
No
Create and manage projects and their data sources
Yes
No
No
No
Manage users, teams, organization settings and analytics
Yes
No
No
No
Manage connections and create organization journals
Yes
No
No
No
Administrator · Knowledge management
Uploading and managing documents with OCR
User experts and administrators add documents directly to project knowledge.
Open project documents
Choose Projects in the left menu, open the relevant project, then select Documents.
Search for part of a name. Narrow the list by file extension, status, type or source. Digitized only limits the list to digitized sources. Use pagination at the bottom for more items.
Open the file name. Read the surrounding passage in the original document; download an available original from that row’s menu.
Open Documents → Upload documents. Drag files onto the upload area or use file or folder browsing. Check the selection and follow the formats and limit shown in the dialog; the document limit here is 500 MB.
After transfer, return to the list, find the uploaded items and monitor their status. Transfer and processing are separate steps.
OCR is built into Edmund. Text recognition helps process scanned material; you do not need to convert every scan with an external tool first. Recognition depends on source legibility and environment configuration. The file status shows the processing result.
Once processed, ask a specific question about the new document and open the citation. For an error or no-text status, review the file and give support the project name, file name and displayed status. Repeatedly uploading the same file does not resolve the underlying issue.
Click the three dots in the file’s row. The menu contains actions allowed by your permissions, such as downloading a file or deleting it. Select multiple rows using their checkboxes for a bulk selection.
For a PDF marked as repaired, distinguish the normal download from downloading the original. The normal download provides the repaired version; downloading the original provides the uploaded file. Unrecoverable pages may be missing, so check the relevant page before using a particular procedure.
When replacing a revision, first verify the new source and its processing. Before deletion, read the confirmation and selected file count. For a synchronized document, coordinate changes with the source integration so future synchronization behaves as intended.
Open Automation Logic → PLC → Upload PLC program. Select Siemens for a TIA Portal .zip or .zapNN archive, or Allen-Bradley for .L5X files or a ZIP containing them. Choose the provider based on the actual export.
The dialog allows archives up to 500 MB and individual L5X files up to 10 MB. Select the file and complete the wizard. Wait for Indexed in the list. Importing into Edmund does not send the program to a live PLC.
Choose Allen-Bradley in the same import dialog. The help text below the upload area changes. Use .L5X exports from Studio 5000, up to 10 MB per file, or a ZIP containing the exports up to 500 MB. Browse files or drag them into the area.
Choose the format based on the actual export, not the machine name. After processing, open the program and check status and structure. This imports source material for Edmund; it does not load a program into a running PLC.
Open the program and check its provider, status, latest upload and structure. Edit details lets you add the program and machine names and descriptions. Explain purpose and scope in the descriptions. The provider cannot be changed after creation.
Use Upload new program version in the details of the correct program. Do not create an unrelated program for a revision. Prepare an export of the same device in its provider’s format and complete the import.
After processing, check status, latest upload and the expected structure. Ask about the new revision in a new chat and inspect the cited source. An older chat may contain answers based on the earlier export.
Robot sources are under Robots in Automation logic.
Open a robot program
Choose Automation Logic → Robots in the project left menu. Select a backup by its name and controller. Its detail has separate RAPID modules and I/O and signals tabs.
Choose Upload ABB export in the robot list. Select the backup folder for the relevant controller. The dialog shows selected items and excluded files; the individual-file limit is 10 MB. Review the selection and complete the import.
After processing, open the robot and check its identity and available files. A missing part of an import means the program's completeness has not been established.
Use the available code and I/O tabs in the robot details. Search by the exact signal or routine name. Check a signal's type and description where provided. Ask about the specific identifier in the robot's project when you need an explanation.
For an update, use an export of the same controller and verify the expected files after processing. The example shows the actual I/O table in the desktop interface.
Select a row on the I/O and signals tab. Signal detail displays the available information about that identifier. Make sure it is the signal discussed in chat. I/O means inputs and outputs; Edmund’s table comes from the imported backup and is not a live measurement of the robot.
Use the exact identifier in a follow-up question. To connect a signal to the program, ask for the relevant routine and supporting source.
Administrators create maintenance journals and assign them to projects. Entries record individual events, their solutions and attachments.
Create the journal itself
Open Organization settings → Maintenance journals. Check for an existing suitable journal and click Add journal. In the first Journal step, enter a name and an optional purpose description.
Click Next. You are creating the shared collection, not recording a repair event yet.
In the second step, choose exactly one method. Global makes the journal available throughout the organization. Specific projects requires selecting machines or lines. Tags assigns it according to selected project tag values.
Select the relevant projects or tags and click Save journal. Open an affected project and its Project journals. Check that the journal appears where intended. Later project-tag changes can affect tag-based assignments.
Find the journal in its management list and open its details or edit action. Review and update the assignment for the intended scope. Check both projects gaining it and projects losing it.
Correct an event through a new entry version. A journal does not need to be deleted just to change its assignment. Read the confirmation and effect on entries before deleting a journal.
Open a journal and read an event
Select Project journals in the project, then choose the journal name.
Find the event in the list, use available filters as needed and open the entry name. In its detail, read the date, description, solution, attachments and version history.
Open Project journals → a journal → Add entry. If no suitable journal exists, an administrator must create it and assign it first. Journal creation and assignment are covered at the start of this chapter.
Event title and time
Give the entry a specific, searchable event or symptom title. Date and time refer to the event, not the moment the form is filled in. Change the default when recording an earlier intervention. Check the journal before saving.
Description: what actually happened
Description records the symptom, circumstances and observed condition. Separate observations from assumptions. Include exact alarm or signal identifiers and when the problem occurs. The microphone beside this field supports dictation; review the transcription before saving.
Solution: work and verified outcome
Record work that was actually done
Solution records work performed and how the outcome was checked. State when the cause remains unconfirmed or the fault persists. Verify any copied chat text against the actual work. Do not record an untested assistant suggestion as a completed repair.
Upload files to an entry and save it
You can also upload files to a maintenance entry. Below Solution, drag files into the upload area or click browse files to select them from your computer. Attachments supplement the description and solution, for example with a photo of a component, alarm or completed repair.
This form accepts .jpg, .png, .jpeg, .gif, .bmp, .tiff, .tif, .heic and .heif image files, up to 10 MB per file. Edmund converts HEIC photographs to JPEG during upload. Follow the formats and limit shown below the upload area.
Before saving, check the selected attachments, name, time, description and solution. Then click Save. After saving, open the entry detail and verify its contents and attachments.
Choose New version in the entry details. Update the same event, check its original date and carried-over attachments, then save. The editor creates another version for Edmund to use in answers. Check its number and the version-in-use marker.
Earlier wording remains distinguishable in history. Create a separate entry with its own date for a new fault or intervention, so a repeated event is not confused with a correction.
Record proven settings and experience after replacing a part as well as faults. For recurring issues, use recognizable machine and symptom names so that colleagues can find similar cases in everyday language.
Administrator · Administration
Organization name, default language and logo
Edit these details in Organization settings → General.
Edit the name and default language
Enter the name people should see in Organization name. Set the organization's Default language. Personal interface language is managed separately in account preferences.
Save the changes, then verify the name and selected language.
In Organization logo, drag a file into the upload area or click browse files and choose it from your computer. The form accepts PNG and JPEG up to 5 MB. Select the correct file and save the change.
After saving, check that the logo is legible. The example includes the complete logo field, upload area and format information.
Prepare teams first, then invite users with the appropriate roles. Assign projects to teams when creating or editing projects.
Create a team and assign projects
Open Teams, add a team and give it a clear name. If users and projects already exist, assign them in the available wizard or detail sections. When setting up a new organization, return to assignments after inviting people and creating projects. Naming a team alone does not grant access.
Teams control project access; roles control permitted actions. Tags filter projects and do not replace team permissions. When changing membership, check who gains and loses access.
Open Invite user from Users. Work from top to bottom: select the role first, enter the email address, optionally add more addresses, and choose teams. The role at the top applies to the addresses in this invitation. Use a separate invitation for a person who needs a different role.
Check recipients and role before sending
Click Invite user only after reviewing addresses, role and teams. The example is an unsent form; the highlights follow the order of completion.
If Microsoft SSO is configured for the organization and this option is available, use the SSO invitation option at the bottom of the form. Check the recipient, role and teams before sending. The recipient signs in with a work Microsoft account without creating an Edmund password; their name comes from that account.
Change a role or membership
Find the person in the list and open their available actions. Use View permissions to assess a role change. The expert role adds knowledge-management capabilities; it does not automatically grant every project.
When ending access, check the account and confirmation dialog. Removing someone from a team differs from removing them from the organization. Verify the resulting state in the list.
An organization must have at least one active administrator. The last administrator cannot be removed from the organization or have their administrator role taken away. Before ending that person’s access, arrange another active administrator. Check the account’s status in the user list as well; an assigned role alone does not confirm that the account is unblocked.
After confirmation, Edmund automatically emails the invitation to the work address; separate self-registration is unnecessary. The link is valid for 24 hours. If it does not arrive, ask the recipient to check junk or spam. Create a new invitation when the link expires.
Check seat usage in the user list. Reaching the seat limit can prevent further invitations; this is different from an invalid email address. Administrators can access all projects; other roles use team assignments and projects without a team restriction.
Administrator · Administration
Creating and configuring a project
Administrators define projects, their knowledge and team access.
Open project creation
Open Projects in the left menu and click Create project in the top right. This action is available to administrators.
Enter an unambiguous machine or line name in Project name.
Under Project access, choose Everyone in the organization or Selected teams. For the latter, find and select the specific teams.
Under Project tags, select No tags, or assign available tags using Organize with tags. The second option is unavailable if the organization has no tags yet.
Finish with Save. Cancel returns to the list without creating a project.
The example shows the complete empty form. This screen has its own header; Cancel takes you back to the project list.
Open Project settings. Save a name change in its own form section. Project suggestions can contain a custom set of up to five active items; an empty custom set uses the organization defaults.
Select existing organization tags in Project tags and save them. Check assigned connections and descriptions in Data sources. Create connections in Organization settings → Connections. Project deletion is a separate confirmed action affecting its content.
Name a project for the specific machine or line, ideally including the internal asset number used by colleagues. Combining an entire hall of unrelated equipment in one project makes source selection harder.
Download QR codes in bulk
On Projects, use Download QR codes at the top right to export codes for all projects. This bulk action is available to administrators. Open an individual code using the QR icon for a specific project; its dialog offers Download as PDF.
Administrator · Administration
Tag groups, tags and assignments
A group represents a property; a tag is one of its values.
Create a group first
A tag group describes one property, such as a hall or technology. A tag is a specific value of that property assigned to a project.
For example, a Hall group could contain Hall A and Hall B tags. A Technology group could contain Packaging and Conveying. These are naming examples, not records you must create.
Open Organization settings → Tags → Add group, enter a name and save. The Add tag action may be disabled until at least one group exists.
In Tags, choose Add tag, enter a specific value and select its group. Save, then open Project settings → Project tags. Select the appropriate tags and save them.
Creating a tag does not assign it to a project. Tag each relevant project explicitly. Keep names consistent so the same hall or technology does not acquire several nearly identical values.
The example shows the form before tag groups have been created. If you see this empty state, create a group and its values in organization settings, then return to assign tags to the project.
Use group values as filters in the project list and check the results. Tags can also determine automatic journal assignments. A newly tagged project may gain a journal when it matches the configured assignment rule.
Before renaming or deleting a tag, check where it is used. Changes can affect filtering and journal availability. When replacing a tag, assign the new value first and verify the resulting projects and journals.
Assigned tags in the project list
In the Filters panel, Machine 1 is selected. Matching projects remain on the right; purple tags on their cards show the assigned values. Project, group and tag names are organization data and are not translated when the app language changes.
Suggestions: purpose, languages and chat availability
A suggestion is a reusable prompt template completed by the user in chat.
What a suggestion is and how to create one
A suggestion is a prepared instruction offered in project chat. It makes repeated tasks easier without rewriting the whole question. It is neither a saved answer nor a fault report. For example, “Explore similar faults” can insert a prompt that finds related records and compares their symptoms.
As an administrator, open Organization settings → Suggestions → Add suggestion. First enter a Name for identifying it in settings. A new form has no language variant yet: click Add language and choose the language. The three fields described below then appear.
Name in chat is the short menu text, such as “Explore similar faults”. It tells the user what the suggestion does. It differs from the internal Name at the top of the form. Write it in this variant’s language.
User prompt is the actual question inserted in chat. This example requests similar faults for the machine and comparison of symptoms and solutions. Write a complete task rather than repeating the button title. The user can add the current situation after inserting the suggestion.
System message is an internal instruction for Edmund, hidden from the regular chat user. This example requests sources and separation of facts from assumptions. User prompt instead contains the task the user sees and sends.
Use Add language for another variant. Each has its own chat name, user prompt and system message. Review all required variants, then click Save. Saving and activation in chat are separate steps. The example is a filled but unsaved suggestion.
Activate the saved suggestion in the list. An organization can have up to five active suggestions, ordered by dragging in the interface. Check that each required language variant contains all necessary text.
A project can have its own set of up to five suggestions. With no custom active items, it uses organization defaults. A custom active set overrides those defaults, so changing the organization set may not change every project.
Open a new chat in the relevant project and language. Select the suggestion, add a specific search phrase and send it. Check that the prompt matches its label and that the answer uses the intended sources.
Edit an existing suggestion through its details. Consider project usage before deleting it. Its name should explain the task without requiring users to understand the internal instructions.
Read the shared workflow below, then open the guide for your database system. Connectors are alternatives; you do not need to configure every one. Document integrations are a separate topic.
Expand Connections in organization settings and open Data sources. These are database connections Edmund queries when answering a request; table data does not become project documents.
Choose the matching database system when adding a source. PostgreSQL, Microsoft SQL Server, Oracle Database, Influx DB and Snowflake are available. SAP HANA is marked unavailable in the inspected catalog. SharePoint belongs to Integrations and synchronizes documents; its form and workflow are separate.
Before filling in the form, arrange network access and credentials. Connection name identifies the source in Edmund. In the database itself, limit the account to the SELECT permissions needed for approved data. Edmund does not check the safety of every SQL command; broad permissions can allow changes or deletion.
PostgreSQL, SQL Server and Oracle use a database username and password. Influx DB uses a token; Snowflake supports a password or private key. The following connector chapters describe their specific fields and differences.
Database DDL schema is text describing data structure, such as tables, columns and data types. In this form it provides context for building queries; it does not create tables. Other database connectors have the same form section. Supply the schema matching the approved data of the actual connection.
In the description, explain tables and columns, units, time zone and table relationships. Identify the machine identifier and explain ambiguous abbreviations. The schema describes structure; the description supplies its meaning.
A database view is a saved query read similarly to a table. Enable Include database views if Edmund should use these views too. This option is available for PostgreSQL, SQL Server, Oracle and Snowflake.
Enabling it does not replace the database account’s permission to read the view.
After completing the form, continue to project assignment, choose the projects and save the connection. In Project settings → Data sources, check its availability and any project-specific description. A source existing in the organization is not automatically usable in every project.
In project chat, request a small known result. Compare it with the expected period and column meanings. If it fails, distinguish a connection failure, missing database permission and missing project assignment.
The organization description explains the source in general. A project-specific description adds machine context and helps formulate queries. Description text is not a permission or security filter; the database account and connection assignment determine actual access.
Refining the description for a project
The shared description is entered in the database source under Database description (optional). Add project-specific context through Project settings → Data sources → Manage description. The dialog shows the shared description as read-only on the left and the Project-specific description on the right. For example, explain the machine identifier, local abbreviations or plant mapping. Confirm the change with Save.
Edit the description without changing the connection
For an existing database source, an administrator can edit the name, description and assigned projects without entering the password or private key again. When changing the connection itself, such as the server or credentials, provide the required details and test the connection. An unsuccessful test does not overwrite the previous working settings.
Administrator · Administration
PostgreSQL
The dedicated PostgreSQL connection form.
First arrange server connectivity and credentials with read-only access using the shared database connection workflow. The fields below are specific to this connector.
Database address and context
Connection name identifies the source in Edmund. Host URL must identify the reachable PostgreSQL server, including its required port. Database name selects the database on that server; optional Schema supplies the schema context. Database and schema are different values. Obtain them from the database administrator.
Field
What to enter
Example
Connection name
A readable Edmund label; it does not rename the database.
Maintenance PostgreSQL
Host URL
Server address and port from the administrator. Do not copy localhost automatically: it refers to the machine executing the connection.
db.example.invalid:5432
Database name
The specific database on that server.
maintenance
Schema (optional)
The table namespace inside the database; confirm it against the actual structure.
public
Values are illustrative only. Use your own environment’s values for a real connection.
Enter the database account’s username in Username and its password in Password. Its permissions are configured in the database itself; the shared database connection workflow explains the required access restrictions.
After completing these fields, add the DDL and data description using the shared workflow, choose the target projects and save the connection. Then verify a small known result in an assigned project’s chat. Project assignment and result verification.
Administrator · Administration
Microsoft SQL Server
The SQL Server form includes its own options, including the connection timeout.
First arrange server connectivity and credentials with read-only access using the shared database connection workflow. The fields below are specific to this connector.
Database address and context
Enter a name for Edmund and the actual server URL. Database name selects the intended database and optional Schema supplies its schema. Use the address and port for your environment. Form placeholders are not a recommended server configuration.
Field
What to enter
Example
Connection name
The label used to find this source in Edmund.
Maintenance SQL Server
Host URL
Use the actual server address and port; the placeholder may differ from your environment.
sql.example.invalid:1433
Database name
The database Edmund should read.
Maintenance
Schema (optional)
The schema containing the required tables; this is not the DDL text.
dbo
Values are illustrative only. Use your own environment’s values for a real connection.
Enter the database account’s username in Username and its password in Password. Its permissions are configured in the database itself; the shared database connection workflow explains the required access restrictions.
Connection timeout is measured in seconds and limits waiting while establishing the connection. The form also states that the database connection is always encrypted.
After completing these fields, add the DDL and data description using the shared workflow, choose the target projects and save the connection. Then verify a small known result in an assigned project’s chat. Project assignment and result verification.
Administrator · Administration
Oracle Database
Oracle distinguishes Service Name from SID database identification.
First arrange server connectivity and credentials with read-only access using the shared database connection workflow. The fields below are specific to this connector.
Database address and context
Enter a connection name and server URL. Choose Service Name or SID using the Oracle administrator’s details, then supply the corresponding identifier and optional schema. These identifiers are not interchangeable. Randomly changing the type does not replace the correct value. The example shows the Service Name option.
Field
What to enter
Example
Host URL
The actual Oracle address and port from the administrator; do not copy a different environment’s placeholder.
oracle.example.invalid:1521
Service Name or SID
Choose the type supplied by the administrator; its input changes with the selection.
Service Name: MAINTENANCE
Schema (optional)
Specifies the relevant objects; it replaces neither Service Name nor SID.
MAINTENANCE
Values are illustrative only. Use your own environment’s values for a real connection.
Connection Type changes the database identifier. Selecting Service Name displays the service-name field. Selecting SID replaces it with the SID field, as shown in this example. Obtain both the type and value from the Oracle administrator.
A Service Name identifies a service; SID identifies an instance. Do not automatically reuse a service name as a SID. Optional Schema is a separate value and replaces neither identifier. Continue with authentication and data context below.
Enter the database account’s username in Username and its password in Password. Its permissions are configured in the database itself; the shared database connection workflow explains the required access restrictions.
After completing these fields, add the DDL and data description using the shared workflow, choose the target projects and save the connection. Then verify a small known result in an assigned project’s chat. Project assignment and result verification.
Administrator · Administration
Influx DB
Influx DB uses a URL, organization and token.
First arrange server connectivity and credentials with read-only access using the shared database connection workflow. The fields below are specific to this connector.
Database address and context
Enter a connection name, full server URL, Influx organization and token. Organization here belongs to Influx, not Edmund. The token replaces the usual username/password fields. Prepare it with read access to the intended data and do not put it in the database description.
Field
What to enter
Example
Host URL
A complete address including http or https and any port.
https://influx.example.invalid:8086
Organization
The Influx organization, which is separate from your Edmund organization.
plant-operations
Token
An access token for the required data, replacing username and password. No real token is shown.
Provided by your administrator
Values are illustrative only. Use your own environment’s values for a real connection.
After completing these fields, add the DDL and data description using the shared workflow, choose the target projects and save the connection. Then verify a small known result in an assigned project’s chat. Project assignment and result verification.
Administrator · Administration
Snowflake
Snowflake requires a warehouse as well as a database and authentication.
First arrange server connectivity and credentials with read-only access using the shared database connection workflow. The fields below are specific to this connector.
Connection identity
Connection name identifies the source in Edmund. Host URL must identify your Snowflake account. Prepare these values before entering context and authentication.
First enter a connection name and account host URL. In the Snowflake context card, supply Warehouse, Database, Schema and optional Role. Warehouse means Snowflake compute, not spare-parts inventory. Role supplies the permission context and must allow access to the intended objects.
Field
What to enter
Example
Host URL
The Snowflake account host from the administrator. Do not reuse another service’s placeholder address.
account.region.snowflakecomputing.com
Warehouse
The compute resource for queries, separate from parts inventory and the database name.
EDMUND_WH
Database and Schema
Two levels locating the tables. Enter each in its own field.
MAINTENANCE / PUBLIC
Role (optional)
The Snowflake database role, separate from Edmund’s User or Administrator role.
EDMUND_READER
Values are illustrative only. Use your own environment’s values for a real connection.
Enter the database account’s username in Username and its password in Password. Its permissions are configured in the database itself; the shared database connection workflow explains the required access restrictions. For Snowflake key authentication, continue with the next section.
If the account uses a key, enable Use private key login. Password is replaced by Private key and Private key passphrase (optional). Username and the Snowflake context still belong to the connection.
Enter the key provided for this account. If it is encrypted, enter its passphrase in the second field. An account password and a key passphrase are different values. Disable the switch for password authentication. No real key appears in the examples.
After completing these fields, add the DDL and data description using the shared workflow, choose the target projects and save the connection. Then verify a small known result in an assigned project’s chat. Project assignment and result verification.
Administrator · Administration
SharePoint integration and document synchronization
SharePoint synchronizes library documents. This differs from live database queries.
Open Integrations and prepare four values
Open Integrations under Connections. An integration regularly transfers external content into Edmund. SharePoint provides documents from a specific library, which are processed and made available to projects.
Select SharePoint in Connections. Your Microsoft administrator prepares an application and access to the intended library. Edmund needs Tenant ID, Client ID, Client secret and the library's Drive ID. Enter the actual client-secret value, not its secret identifier.
Click Connect and continue. Edmund validates library access before saving; a failed validation does not store the connection. The integration uses application-only read access, does not write to SharePoint and does not impersonate the signed-in user.
After connecting, open SharePoint details or the Integrations card in an existing project. Copy the specific folder address from SharePoint, paste it into a mapping row and choose Validate. Review the result and save. This is address-based mapping, not folder-tree browsing. A project supports up to 20 folders from the same library; subfolders are included.
Changes are detected within 10 minutes; processing takes longer depending on volume. Check the SharePoint source and processing status in Documents. The example shows the connection list before adding the integration; mapping rows appear after library connection succeeds.
Distinguish library access, secret validity, folder assignment and individual-file processing when troubleshooting. Coordinate credential or access-scope changes with your Microsoft administrator. Repair the existing connection instead of creating a duplicate integration.
Analytics helps you understand Edmund usage over a selected period.
The complete analytics page
Open Analytics in Organization settings. Date and other filters appear at the top, followed by three summary metrics, the messages chart and the user table. The complete page below includes the table rows and pagination.
Click Enlarge example below the illustration and set browser zoom to 100% to read small values. The following examples focus on each part.
Click the date field, choose a preset or custom interval, then confirm with Apply. Use Projects, Roles, Teams and Users beside it to narrow the scope. When comparing results, check both the period and the selected filters.
This example uses twelve months to show usage history. If no data appears, first review the period and filters.
Number of messages measures communication volume within the selected scope. Feedback rate shows how often users rate answers; Satisfaction summarizes ratings. Message count is not the number of resolved faults, and ratings do not verify technical correctness.
Messages over time shows how activity is distributed across the period. Read time along the horizontal axis and values on the vertical axis. Colored segments form the total bar; their colors do not indicate fault severity.
Below the chart, switch between Active and All. Each row contains the user’s name, roles and teams, message count, feedback and the time of their last message. Arrow buttons in column headers change the sorting.
At the bottom, change the number of rows per page or move to the next page. The active-user count is not the total number of organization accounts. Click a user’s row to open their detail.
Hover over a chart bar to see the available detail for that interval. A user row can open the available view of that user’s chats for the selected period. Keep filters consistent when interpreting results; message counts do not represent successful repairs.
Administrator · Help and feedback
When something does not work
Start with what you can see on the affected screen.
Missing answers, sources or access
For an unclear answer, add an exact identifier and open the citations. Ask an expert to check a missing source and its processing status. For a missing project or action, ask an administrator to check your team and role.
Open Contact us in the left menu. The first example highlights the entry point; the following example shows the contact form.
A missing menu can also mean that an organization feature has not been configured or enabled. Ask an administrator to check your role, project settings and available modules first. If an expected connector or module is missing, the administrator can contact the Edmund team.
Open Contact us, choose a Reason, enter a short Subject and describe the action, expected result and actual result. For a problem in a particular chat, include its address and the time. Check the message, then use Send.
Thumbs rate an individual answer; the contact form also handles application issues and improvement requests. For example, “The source link to manual revision X is missing; the correct value is on page Y” is more useful than “It is wrong.” Rating an answer does not mean the next answer automatically learns the correction.