What problem does it solve? Designing a Manufacturing Execution System requires clear decisions about what MES owns versus ERP, APS, WMS, QMS, LIMS, SCADA, and PLC systems, plus explicit modeling of orders, WIP, genealogy, and exception states. This Skill turns a manufacturing problem statement into a bounded, implementable, rollout-aware MES design instead of a vague platform diagram. ## Core Features & Use Cases - System Boundary Definition: Assigns ownership of business rules, master data, and state transitions across ERP, APS, WMS, QMS, LIMS, SCADA, PLC, and historian systems using the integration-boundaries reference. - Capability Mapping and Scoping: Builds a capability map covering order dispatch, route execution, WIP visibility, material genealogy, quality execution, and performance visibility, scoped by release. - Execution and Exception Modeling: Defines canonical objects, lifecycle states, and failure modes such as duplicate equipment events, network loss, and manual overrides using the execution-model checklist. - Use Case: A manufacturer wants to replace spreadsheet-based shop-floor tracking with MES. Use this Skill to produce a boundary matrix, first-release capability scope, state model for hold/rework/scrap flows, and a phased rollout plan with coexistence and fallback paths. ## Quick Start Use the designing-mes-systems skill to design an MES architecture for a single-site discrete manufacturing plant, including the system boundary with ERP and SCADA, the first-release capability map, and a phased rollout plan.
