Collections and boards
Collections organize boards into the navigation your organization browses; a board holds the screens for one team or purpose.
Mevisio turns the data your operation already has into digital boards your teams work from every day. Read on as far as you need: how solutions are built, how data moves, how it is protected and where AI fits in.
Every Mevisio solution is built from the same five layers. Scroll to put them together.
A data source holds your records, with the fields you define: output per shift, deviations, actions. Teams fill it through forms, and integrations bring data in from ERP systems, SQL databases, REST APIs and Excel files, so nobody has to retype it.
What you can set up
A module is one element on screen, such as a chart, a KPI, a table, a form or a list. It reads a data source and shows it the way the team needs.
What you can set up
A screen places modules into one view: everything a team looks at together in its daily meeting, for example.
What you can set up
A board is a set of screens, such as SQCDP, improvements, 5S and skills, built up one at a time. Boards are grouped into collections, so each team, line and site finds its own, and the same board can be reused across them.
What you can set up
Describe your organization as a tree of sites, departments, lines and teams. When records carry their unit, the same data serves every level: each team works from its own, the level above sees all of its teams together, and what is decided above, such as targets and priorities, reaches every team below. The boards can differ; the data underneath stays the same.
What you can set up
Each part of a solution is a piece of configuration with its own reference in the Knowledge Hub.
Collections organize boards into the navigation your organization browses; a board holds the screens for one team or purpose.
Screens lay out modules: KPIs, charts, tables, text, images, buttons and embedded web pages.
Your data model: records with the fields you define, stored in Mevisio or read from an external system.
Forms capture data in a structured way; lists hold the choices a form or filter offers.
Actions do the work behind a button, a form or an event: send a message, update records, import a file. Timers run them on a schedule.
Server-side JavaScript for calculations and business rules that go beyond configuration.
Modules are what teams see and work with on a board. Mix them freely: every module can be placed on any screen.
Key figures with a label, green or red against the target.
Bar, line, gauge and time series charts, colored by their values.
KPIs with a value for every week or month, side by side.
Records in rows and columns, with colors set by the values.
A grid of colored values that shows where problems cluster.
The status of every line, machine or station at a glance.
A day-by-day calendar in the shape of a cross, each day colored by its incidents.
The words that come up most often in your records.
Plan against actual, stock levels and arrows in a grid: a whole flow at a glance.
Actions and ideas as cards that move between stages, kanban style.
Cards placed in a matrix, such as by team and week.
Strategy deployment (Hoshin Kanri) in four linked quadrants.
Plans and events on a scrollable, Gantt-style timeline.
Day, week, work week, month and agenda views.
Items to tick off: start-up checks, audits and routines.
Drop a card on it to take the next step, such as escalating or archiving.
A conversation attached to a record.
Lets people enter data straight into a data source.
Collects feedback from employees.
Runs a command with one tap: add a record, open a screen, export.
Reads a barcode with a scanner and acts on the code.
Picks the day, week, month, quarter or year the screen shows.
A stopwatch, started and stopped with a tap.
Files shown as icons. Drop a file on it to add it.
Headings, instructions and notes, with formatting.
A photo, logo or layout drawing.
A video from a link, such as YouTube.
Another web page or a Power BI report, embedded on the board.
An icon that marks a status or an area.
The current time.
A QR code made from a value, such as a link to open on a phone.
Five levels, from changing what a board shows to writing code. Each person works at the level that fits them, and administrators decide who gets which.
For: Everyone on the team
Change what a board shows while you use it, without changing how it is built.
For: Team leaders and super users
Build boards in the visual editor from ready-made parts, and set each one up through simple settings. No code.
For: Developer users
Shape the whole solution in the Configuration app: the data, the forms and the logic behind the boards.
For: Developer users who code
Go beyond configuration with JavaScript, your own integrations and modules that others can reuse.
For: Anyone your administrators allow
Describe what you need in plain language, and let your AI build it: the vibe coding of digital boards.
Bring your own AI.
Mevisio connects to the AI your organization already uses, through the open Model Context Protocol (MCP) and OAuth 2.0 sign-in.
Ask your AI about your operational data: it reads and summarises records in Mevisio alongside the rest of your business context.
Describe a solution and let AI build or change the boards, data sources and logic behind it.
AI access is off until an administrator turns it on, separately for reading and changing data and configuration.
Your data in, your data out.
Some teams enter data straight into Mevisio. Others connect the systems they already run. Most do both.
Read from SQL Server and MySQL databases, REST APIs (with OAuth 2.0 or basic authentication), Microsoft Graph and Monitor ERP.
Give other systems an HTTPS address or an email address to send data and events to, protected by API keys.
Import CSV and Excel files, and run imports, calculations and updates on a schedule.
Export tables and charts to Excel or PDF, call other systems' APIs, and send email, SMS, Slack and Microsoft Teams messages.
Built to be run by IT.
Mevisio runs as a cloud service. Your administrators decide who signs in, how, and what each person can see and change.
Hosted on Amazon Web Services, in the EU or the US, with a separate environment for each region.
Single sign-on with SAML 2.0 or Microsoft Entra ID, multi-factor authentication, password rules and IP allowlists.
User types and groups decide who can see and change what. Sandboxes let you try changes away from the live account.
All traffic is encrypted with TLS 1.2 or later, and sign-ins, configuration changes and data changes are recorded in an activity log.
Book a personalized one-on-one demo of our platform and discover how Mevisio can help you create custom boards, streamline your business operations, and empower your team to work more efficiently.
Prefer to try it yourself?
Start a free trialRather talk to us first?Contact us