Overview
5 min
what is mantsu? welcome to the mantsu documentation! mantsu ( man ufacturing t emplate sui 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? modular & scalable start small, expand at your own pace cloud native & multi device – accessible anywhere, anytime role based & multi language – tailored to teams across locations mobile support – operators can work on the go machine connectivity – link tools, equipment, and people operator guidance – streamlined, user friendly interfaces communication layer – secure, high throughput data exchange 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

