How Mevisio works

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.

From data to board

Every Mevisio solution is built from the same five layers. Scroll to put them together.

  1. 1 / 5

    Data: where it lives and how it gets there

    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

    • The fields and their types: numbers, text, dates, people, choices from a list
    • Rules that check values when a record is saved
    • Which system to read from: SQL Server, MySQL, a REST API, Microsoft Graph or Monitor ERP
    • Imports of CSV and Excel files, on a schedule in your own time zone
    • Addresses where other systems send data, protected by API keys
  2. 2 / 5

    Module: showing the data

    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

    • The type: KPI, chart, table, form, cards and about 25 more
    • Which records it shows, with filters and sorting
    • Colors that follow the values, such as red below target
    • What a click does: add or update a record, open another screen, export to Excel or PDF
  3. 3 / 5

    Screen: laying out the modules

    A screen places modules into one view: everything a team looks at together in its daily meeting, for example.

    What you can set up

    • Where each module sits and how much space it takes
    • Row and column headings
    • Shared settings, such as the team or period every module filters on
    • Who can open it, and whether its data can be changed
    • Whether it is shown when the board loops on a TV
  4. 4 / 5

    Board: what the team opens

    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

    • Which screens it holds, and in which order
    • Which collections it appears in, for each team, line or site
    • Who is responsible, and who the members are
    • Forms and lists for the mobile app
    • Who can open it, and its time zone
  5. 5 / 5

    Organization: making the information flow

    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

    • The tiers and units of your organization
    • Which unit each record and each person belongs to
    • Boards that show one unit, or a unit and everything below it
    • Role-based access: groups decide who sees and changes each collection, board and screen, down to single records
    • A unit picker on the board, so each viewer finds their own team

The building blocks

Each part of a solution is a piece of configuration with its own reference in the Knowledge Hub.

Collections and boards

Collections organize boards into the navigation your organization browses; a board holds the screens for one team or purpose.

Screens and modules

Screens lay out modules: KPIs, charts, tables, text, images, buttons and embedded web pages.

Forms and lists

Forms capture data in a structured way; lists hold the choices a form or filter offers.

Actions and timers

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.

The modules

Modules are what teams see and work with on a board. Mix them freely: every module can be placed on any screen.

Follow up

  • Number

    Key figures with a label, green or red against the target.

  • Chart

    Bar, line, gauge and time series charts, colored by their values.

  • Time series

    KPIs with a value for every week or month, side by side.

  • Table

    Records in rows and columns, with colors set by the values.

  • Heat map

    A grid of colored values that shows where problems cluster.

  • Andon

    The status of every line, machine or station at a glance.

  • Safety cross

    A day-by-day calendar in the shape of a cross, each day colored by its incidents.

  • Word cloud

    The words that come up most often in your records.

  • Grid

    Plan against actual, stock levels and arrows in a grid: a whole flow at a glance.

Plan and improve

  • Cards

    Actions and ideas as cards that move between stages, kanban style.

  • Matrix

    Cards placed in a matrix, such as by team and week.

  • X-matrix

    Strategy deployment (Hoshin Kanri) in four linked quadrants.

  • Timeline

    Plans and events on a scrollable, Gantt-style timeline.

  • Calendar

    Day, week, work week, month and agenda views.

  • Checklist

    Items to tick off: start-up checks, audits and routines.

  • Drop zone

    Drop a card on it to take the next step, such as escalating or archiving.

  • Comments

    A conversation attached to a record.

Capture and act

  • Form

    Lets people enter data straight into a data source.

  • Feedback

    Collects feedback from employees.

  • Button

    Runs a command with one tap: add a record, open a screen, export.

  • Scan

    Reads a barcode with a scanner and acts on the code.

  • Selector

    Picks the day, week, month, quarter or year the screen shows.

  • Timer

    A stopwatch, started and stopped with a tap.

  • Documents

    Files shown as icons. Drop a file on it to add it.

Inform

  • Text

    Headings, instructions and notes, with formatting.

  • Image

    A photo, logo or layout drawing.

  • Video

    A video from a link, such as YouTube.

  • Web page

    Another web page or a Power BI report, embedded on the board.

  • Icon

    An icon that marks a status or an area.

  • Clock

    The current time.

  • QR code

    A QR code made from a value, such as a link to open on a phone.

Build it your way

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.

  1. 1. Adjust the board

    For: Everyone on the team

    Change what a board shows while you use it, without changing how it is built.

    • Search, and pick the day, week, month or date range to show
    • Filter on a team, line or site, or on a value from a list
    • Change a module's settings, where the board offers them
    • Add and update data through forms, cards and checklists
  2. 2. Lay out boards visually

    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.

    • Start from template boards and screens
    • Place ready-made modules on a screen and size them
    • Set each module up through its inputs: what data, which colors, which labels
    • Ready-made boards, screens, modules and data sources, grouped by use case
  3. 3. Configure the solution

    For: Developer users

    Shape the whole solution in the Configuration app: the data, the forms and the logic behind the boards.

    • Data sources with your own fields and rules
    • Forms and lists for entering data
    • Actions and timers that send messages, update records and import files
    • Collections and who can see what
  4. 4. Code and integrate

    For: Developer users who code

    Go beyond configuration with JavaScript, your own integrations and modules that others can reuse.

    • Server-side JavaScript for calculations and business rules
    • Connectors to databases and APIs, and endpoints other systems send data to
    • Your own ready-made modules and templates, with inputs, for the visual editor
  5. 5. Build with AI

    For: Anyone your administrators allow

    Describe what you need in plain language, and let your AI build it: the vibe coding of digital boards.

    • Boards, screens, data sources and code, built or changed from a description
    • Works with the AI your organization already uses, through MCP
    • Try changes in a sandbox before they reach the live account

AI and automation

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.

  • AI Insights

    Ask your AI about your operational data: it reads and summarises records in Mevisio alongside the rest of your business context.

  • AI Developer

    Describe a solution and let AI build or change the boards, data sources and logic behind it.

  • Under your control

    AI access is off until an administrator turns it on, separately for reading and changing data and configuration.

Data and integrations

Your data in, your data out.

Some teams enter data straight into Mevisio. Others connect the systems they already run. Most do both.

  • Connectors

    Read from SQL Server and MySQL databases, REST APIs (with OAuth 2.0 or basic authentication), Microsoft Graph and Monitor ERP.

  • Endpoints

    Give other systems an HTTPS address or an email address to send data and events to, protected by API keys.

  • File import and timers

    Import CSV and Excel files, and run imports, calculations and updates on a schedule.

  • Data out

    Export tables and charts to Excel or PDF, call other systems' APIs, and send email, SMS, Slack and Microsoft Teams messages.

Security and operations

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.

  • Hosting

    Hosted on Amazon Web Services, in the EU or the US, with a separate environment for each region.

  • Sign-in

    Single sign-on with SAML 2.0 or Microsoft Entra ID, multi-factor authentication, password rules and IP allowlists.

  • Permissions

    User types and groups decide who can see and change what. Sandboxes let you try changes away from the live account.

  • Encryption and activity

    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 demo

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 trial

Rather talk to us first?Contact us