Dashboards & analytics

Edmund has two dashboards with the same layout. The organization dashboard covers the whole plant; a project dashboard covers one machine. Read whichever matches the question you have, then drill in from there.

Organization vs project dashboard

Both dashboards share the same shape, so once you know one you know both. Across the top are a few headline numbers: the last PLC sync, the newest journal entry, and the status of your data sources. These tell you at a glance whether what Edmund knows is current. A stale sync or a journal that hasn’t changed in a while is usually the first sign that a feed has stopped.

Below the headline numbers are two charts. A documents donut breaks your files down by category, so you can see the mix of manuals, drawings and other types. A knowledge base growth chart shows how the knowledge has built up over time; it toggles between Cumulative and Activity, and between All, 90d and 30d. Use Cumulative to see the total size, and Activity to see how much was added recently.

The difference between the two dashboards is only the scope. The organization view aggregates every project; the project view is one machine. For the underlying ideas of organization, project and data source, see core concepts.

Reading the coverage table

Under the charts is a Documents by category table. It is the most useful part of the page, because it doubles as a worklist. For each category it shows how many files were uploaded, the share of the total, the share that is indexed, and counts for indexed, no text and errors.

Column	What it tells you
Uploaded	How many files are in this category.
% of total	This category’s share of all documents.
% indexed	Share of this category that Edmund can read and cite.
Indexed	Files that reached Indexed.
No text	Files with no readable text — usually a scan.
Errors	Files that failed to process.

Read the no text and errors counts as a coverage worklist. Any number above zero is a file that is listed but adds nothing to answers, so a category with a high count is a gap in what Edmund can actually use.

The dashboard also lists recent chats and a daily chat activity chart, so you can see what people are asking and how busy Edmund has been.

Analytics (adoption)

For adoption rather than knowledge, open Organization settings → Analytics. It answers a different question: who is using Edmund and how much.

• A date range and a project filter at the top scope everything below.
• A message volume chart shows how usage changes over the chosen period.
• A per-user usage table lists each person with their name, roles and teams, so you can see who is active and who hasn’t started.

Use this when you are rolling Edmund out and want to know whether a shift or a team has picked it up. For what each role can see and do, see roles & permissions.