Downtimes Manager

the downtimes manager (also called the downtime application) provides end to end management of production stops on the shop floor it covers the full spectrum from short automated micro stops to planned maintenance events and unplanned breakdowns; giving operators a fast way to log stops and giving managers the structured data they need to act on them who uses the downtimes manager? operators register and categorize stops directly from the order cockpit supervisors and team leads review, correct, and enrich registered downtimes engineers and administrators configure reason trees and short stop thresholds plant management uses the resulting data for oee reporting and improvement programs for a broader look at the mantsu modules, visit mantsu io/product https //mantsu io/product what is a downtime? a downtime is any period during which a piece of equipment is not producing as planned mantsu distinguishes three types what is the reason code tree? at the heart of the downtimes manager is the reason code tree a hierarchical structure that organises every possible cause of a stop from broad category down to specific root cause a well configured reason tree makes the difference between downtime data that is actionable and data that is noise the tree has multiple layers, and it is not necessary to have each branch on the same depth mantsu reason code tree with branches from broad category down to specific root cause a single site can maintain multiple reason trees; for example one per department, one per product family, or a single global tree each tree is assigned to one or more equipment units independently, so operators only ever see the codes relevant to their machine how do you register downtimes? downtimes are registered by operators directly in the order cockpit this keeps the operator in a single interface during production when a stop occurs, the operator selects the relevant reason code from the tree assigned to their equipment where machine connectivity is in place, stops can also be detected and opened automatically based on equipment signals, reducing the manual effort on the operator and improving registration accuracy all registered stops flow into the downtimes manager, where supervisors, team leads, and technical personnel can review, correct, or enrich them; for example adding a root cause to a stop that was logged without one how are short stops automated? short stops happen too frequently for operators to log one by one mantsu solves this by letting engineers configure a duration threshold and a catch all reason code per equipment any stop equal to or shorter than that threshold is automatically classified, with no operator interaction required how does it integrate with the order cockpit? downtimes are tightly linked to production orders and equipment when an operator registers a stop from the order cockpit, the event is automatically associated with the active order and the selected equipment this linkage makes it possible to report on downtime impact per order, per shift, or per production run and not just in aggregate how does downtime data support oee and reporting? every registered downtime event contributes directly to the availability docid 07fztflmdg7hzlmdmt6xi component of oee by consistently categorizing stops through the reason code tree, the application builds a structured dataset that supports trend analysis per equipment or reason code identification of recurring failures (input for mtbf tracking) measurement of repair and response times (input for mttr tracking) shift and management reporting the quality of this data depends on consistent registration and a well designed reason tree (both of which mantsu is designed to support) roles role responsibility engineer / admin configure reason trees, assign trees to equipment, set short stop thresholds operator register downtime events from the order cockpit supervisor / team lead review and correct registered stops, follow up on open events key terms oee (overall equipment effectiveness) a standard measure of manufacturing productivity availability, one of its three components, is directly impacted by downtime duration mtbf (mean time between failures) average time between unplanned stops on a piece of equipment a rising mtbf indicates improving reliability mttr (mean time to repair) average time to resolve a stop and return to production a falling mttr indicates faster response and recovery short stop a stop shorter than a configured threshold, automatically classified without operator input reason code tree a hierarchical structure of stop causes assigned per equipment, used to categorise every downtime event frequently asked questions how are micro stops handled? stops shorter than the configured short stop threshold are classified automatically under a catch all reason code, with no operator interaction can one site use multiple reason trees? yes a site can maintain several trees (per department, per product family, or one global tree), each assigned to equipment independently where do operators register downtime? directly in the order cockpit, so they never leave their production screen supervisors review and enrich the events in the downtimes manager how does downtime data affect oee? every registered stop feeds the availability factor of oee see the oee summary # sections downtime reasons docid\ tlpusdk9uelnmjrg f7in manage the reason tree reason code assignment docid\ cxkcbo7oavx52tvqzpwkt assign reason tree to equipment downtimes docid 4lvlgo0krulr otwq0ocx overview of downtimes and review assigned categories downtime report docid\ r xyvwscprvpn tdzhryj basic downtime report