---
title: Overview
slug: docs.mantsu.io
createdAt: 2026-05-04T08:57:01.259Z
---

## What is Mantsu?

Welcome to the Mantsu documentation! **Mantsu** (<u>Man</u>ufacturing <u>T</u>emplate <u>Sui</u>te) is a **modular MES (Manufacturing Execution System) solution**. It provides ready-made, yet customizable templates for core manufacturing functions; such as order management, downtime & loss reasons tracking, product quality control, checklist execution, recipe management and insights.

Mantsu enables rapid implementation, seamless scaling, and easy adaptation to your unique production processes. You digitalize operations faster and more cost-effectively compared to traditional MES or MOMS suites or fully custom solutions. For a full product overview, visit [mantsu.io/product](https://mantsu.io/product).

## Who is this documentation for?

This documentation serves everyone who works with or evaluates Mantsu:

- **Plant and operations managers** evaluating a modular MES for their site
- **Functional administrators and key users** who configure modules and master data
- **Shop-floor operators and supervisors** who use the applications daily
- **IT and OT professionals** who want to understand how Mantsu fits their landscape (see the [Architecture](docId:6wLrOmMdtx76mwzWcnKJC) section)

## Why Use Mantsu?

Mantsu helps you modernize operations by replacing paper forms and spreadsheets with digital solutions. It combines the speed and agility of out-of-the-box software with the flexibility of custom MES development. With Mantsu, you save time, cut costs, and gain a scalable foundation for continuous improvement. It gives you the possibility to start small and add what you need, when you need it. You select only the modules you need today, and the MES grows with the needs of your plant; a full suite is not required at the start. Because every module starts from a ready-made template, implementation speed stays high from the first module onwards.

Key benefits include:

- A secure **single source of truth**, no more copying of data
- Faster and automated **validation** processes based on data
- Higher workforce **engagement** that gives **knowledge**
- **Adaptability** to changing customer and market demands
- High **return on investment**
- Start from a solid base, and let the **application grow** as you learn **what you actually need**

## What are Mantsu's key features?

1. **Modular & scalable**
2. start small, **expand at your own pace**
3. **Cloud native & multi-device** – accessible anywhere, anytime
4. **Role-based & multi-language** – tailored to teams across locations
5. **Mobile support** – operators can work on the go
6. **Machine connectivity** – link tools, equipment, and people
7. **Operator guidance** – streamlined, user-friendly interfaces
8. **Communication layer** – secure, high-throughput data exchange
9. **ERP integration** – exchange production orders, master data, and confirmations via REST or OData APIs

You can find a feature overview with screenshots on [mantsu.io/product](https://mantsu.io/product).

## What are the core concepts behind Mantsu?

Before diving too deep, it’s helpful to understand a few fundamental building blocks you’ll see throughout Mantsu:

- **Template foundation**: Ready-made application templates enable rapid implementation, easy updates, and customer-driven customization.
- **Modularity redefined**: Each module (e.g., Downtimes, Lists, Quality Checks, Order Cockpit, Recipe Management, Insights) works independently but integrates seamlessly with each other, or with existing applications.
- **Think big, start small**: Begin with essential modules and scale as production demands evolve.
- **Flexible customization**: More than a ready-made product, Mantsu provides a dynamic starting point that adapts to your unique processes.
- **Operator-first design**: Front-end designs prioritize user experience, reducing training needs and improving efficiency.

# Which modules does Mantsu include?

Mantsu is composed of multiple modules, each covering a specific area of functional features. They work independently but are designed to integrate seamlessly with one another.

By using the independent modular approach, you can manage roles and responsibilities more easily. You can provide access to specific applications and deny it to others. You manage implementation and roll-out by activating the modules as required.

[Authenticator](docId:3YSQtsPVbF6czGBym4xWi) is the identity and access management layer of the suite. It centralises user management, role definitions, and access control for every module. It supports both IT administrators managing corporate identity integrations and shop-floor users who need fast, friction-free login methods like badge scan or PIN.

[Core Manager](docId\:jn2nMWPv2pxEuqLHmop0a) is the master data backbone shared by all other modules. It holds the single source of truth for locations, equipment, materials, production orders, and system-wide settings. No production execution happens in the Core itself. It is the configuration layer that makes execution elsewhere possible and consistent. It also hosts the ERP interfaces, with an interface log to track every exchanged message (see [ERP Interfaces](docId\:gcaUp35nmHWNS28eZnReF)).

[Order Cockpit](docId:1XxJFL0M4pNN7vQjjlSy1) is the primary execution interface for shop-floor operators. It brings every order-related action into a single view: material consumption, scrap reporting, time tracking, downtime registration, quality inspections, and checklist execution. Orders are filtered by equipment selection and real-time status.

[Downtimes Manager](docId\:edCrFJUVFr92L7hVssPYE) provides end-to-end management of unplanned stops, planned maintenance events, and micro-stops. It includes a reason code tree, equipment-level assignment of reason codes, and a full overview of registered downtime events.

[Checklists](docId\:mICHuEokSqbDfDfSlMcNN) manages the complete lifecycle of checklists, SOPs, and process inspection forms; from version-controlled creation, review, and approval through to operator execution and sign-off. Lists can be triggered manually or automatically.

[Quality Management](docId\:eTP5ljIolAdnIiFBdUkSk) covers inspection plans, characteristics, and inspections tied to specific materials. Re-usable quality check definitions (characteristics) are linked to inspection plans, which drive the execution of inspection lots on the shop floor, with full traceability and reporting.

## Frequently asked questions

**Do you need the full Mantsu suite to start?**
No. You select only the modules you need and activate more as the needs of your plant grow. Many plants start with a single module and expand from there.

**Does Mantsu integrate with SAP or other ERP systems?**
Yes. Mantsu exchanges production orders, master data, and confirmations through REST or OData APIs, with off-the-shelf SAP connectors. See [ERP Interfaces](docId\:gcaUp35nmHWNS28eZnReF).

**Can Mantsu run on-premises?**
Yes. Mantsu is containerized and runs cloud native, on-premises, or in a hybrid setup. See the [Architecture](docId:6wLrOmMdtx76mwzWcnKJC) section.

**Who owns the final system?**
You do. The code base and the data are owned by the customer; there is no vendor lock-in.