Connect981 – Content Dev

RSC Cluster: Materials Planning and ERP Integration

The Materials Planning and ERP Integration Cluster addresses the disconnect between planning assumptions and execution reality. It explains which signals must come from the shop floor and which belong in ERP systems. The content covers shortages, lead times, schedule volatility, and single source of truth challenges. This cluster helps planners and operators align plans with what is actually happening.

  • Forecasting

    Forecasting is the process of estimating a future condition based on available information such as historical data, current operating signals, known constraints, and expected changes. In manufacturing and industrial operations, it commonly refers to predicting demand, material requirements, production load, maintenance needs, quality trends, or capacity utilization over a defined time horizon.

    Forecasting is not the same as planning or scheduling. A forecast is an estimate of what is likely to happen. Planning uses that estimate to decide what actions to take, and scheduling turns those decisions into time-based execution.

    Where it applies in operations

    Forecasting appears across both business and plant-level workflows, including:

    • demand forecasting for sales, order volume, or customer consumption

    • materials forecasting to anticipate component and raw material needs

    • capacity forecasting for labor, equipment, tooling, and line loading

    • maintenance forecasting based on usage, condition, or failure patterns

    • quality forecasting to identify likely scrap, rework, or nonconformance trends

    • inventory forecasting to estimate stock levels, shortages, or excess

    In integrated environments, forecasting often feeds ERP, MRP, MES, APS, or analytics systems. For example, a demand forecast may drive material planning, while a capacity forecast may highlight upcoming bottlenecks on a constrained work center.

    Common methods

    Forecasts may be generated using simple averages, trend analysis, seasonality models, statistical methods, or machine learning. They may also include judgment from planners, production teams, procurement, or program managers when historical data alone does not reflect upcoming changes such as engineering revisions, customer schedule changes, or supplier disruption.

    The output can be quantitative, such as units per week or machine hours per month, or qualitative, such as expected risk level or likely shortage exposure.

    Common confusion

    Forecasting vs. planning: forecasting estimates future conditions; planning selects responses.

    Forecasting vs. scheduling: scheduling assigns work to dates, shifts, lines, or resources.

    Forecasting vs. prediction: the terms are often used interchangeably, but forecasting usually implies a structured time-based estimate for business or operational use.

    Forecasting vs. MRP: MRP is a planning calculation. It may use forecasts as one input, but it is not itself the forecast.

    Operational note

    Forecasts are usually updated on a recurring cadence because conditions change. In regulated or tightly controlled environments, the forecast itself is typically an analytical input, while the governed records remain the approved plans, orders, routings, specifications, and execution history.

  • cost center

    Core meaning

    A **cost center** is an accounting unit used to collect, attribute, and track costs for a defined part of an organization, such as a department, production line, plant, project, or program. It is primarily a financial and managerial accounting construct rather than a physical asset.

    Cost centers typically aggregate:

    – Direct labor costs
    – Material consumption and scrap
    – Overhead allocations (e.g., utilities, maintenance, support functions)
    – External services linked to that organizational unit or activity

    The purpose is to understand where costs are incurred, support budgeting and variance analysis, and enable internal reporting and management control.

    Use in manufacturing and regulated operations

    In industrial and regulated environments, cost centers commonly map to:

    – Manufacturing areas (e.g., filling line, packaging line, cleanroom suite)
    – Support functions (e.g., quality control lab, maintenance department)
    – Programs or product families (e.g., a specific drug product or device line)

    Enterprise Resource Planning (ERP) systems usually hold the master list of cost centers and record financial postings against them. Manufacturing Execution Systems (MES) and other OT/IT systems may reference cost center identifiers to:

    – Associate labor time booked on a work order with the correct cost center
    – Attribute material issues, consumption, and scrap to the appropriate area
    – Summarize production activities by cost center for periodic transfer into ERP

    In many plants, MES and ERP exchange cost-center-related data at defined intervals (e.g., end of shift or end of batch) rather than in real time, using stable cost center IDs for reconciliation and program cost tracking.

    Boundaries and exclusions

    A cost center:

    – **Is an accounting view**, not necessarily a single machine or physical asset, although it may correspond to a specific line or area.
    – **Does not by itself define profitability**; it records costs, not revenue. Profit and loss are usually analyzed at higher-level constructs such as profit centers or business units.
    – **Is not the same as a work center** in manufacturing planning terms. A work center usually represents a physical resource or group of resources used for scheduling and capacity planning. A cost center represents where costs are collected in financial records. One cost center may include multiple work centers, or vice versa, depending on the organization’s mapping.

    Common confusion and related terms

    – **Cost center vs. profit center**: A profit center tracks both costs and revenues, enabling profitability analysis. A cost center mainly tracks costs and is evaluated on cost control and efficiency, not direct profit.
    – **Cost center vs. GL account**: A general ledger (GL) account classifies the *type* of cost (e.g., labor, materials), while the cost center indicates *where* in the organization that cost is incurred.
    – **Cost center vs. project code / WBS element**: Project codes or work breakdown structure (WBS) elements track costs for a specific project or initiative. These may be used in addition to cost centers or mapped alongside them for more granular tracking.

    Site context: MES–ERP program cost tracking

    In the context of MES–ERP integration for program or product cost tracking, cost centers commonly:

    – Serve as stable identifiers shared between MES and ERP to align labor and material usage with the correct organizational unit or program
    – Provide the financial dimension against which summarized consumption, scrap, and labor data from MES are posted in ERP
    – Form part of the structure used by finance to calculate and review manufacturing cost per product, batch, or program without requiring real-time, bidirectional coupling between MES and ERP

  • bill of materials

    Core meaning

    A **bill of materials** (BOM) is a structured list that specifies all components, raw materials, subassemblies, and sometimes services required to manufacture a defined product or execute a defined batch, including their quantities and basic identifying information.

    In industrial and regulated manufacturing environments, the BOM commonly:

    – Is defined and maintained in ERP, PLM, or product definition systems
    – Includes material identifiers, descriptions, units of measure, and required quantities
    – References engineering or product revisions to tie materials to a specific version of the product
    – Serves as a reference for planning, procurement, inventory management, and production execution

    A BOM describes **what** is needed to build a product, not **how** or **when** work is performed.

    Typical structure and levels

    BOMs are often hierarchical and may include:

    – **Top-level (finished good) BOM**: Lists main subassemblies and key materials that make up the final product
    – **Subassembly BOMs**: Define components for intermediate assemblies used within the top-level product
    – **Phantom or logical BOMs**: Groupings used for planning or design that may not exist as separate stocked items

    Depending on system and practice, BOMs may also identify alternates or substitutes, packaging materials, and labeling components when they are explicitly required to produce or release the product.

    Use in manufacturing workflows

    In integrated manufacturing environments, BOMs are used to:

    – Drive **material requirements planning** (MRP) and procurement in ERP systems
    – Define expected material consumption for **costing** and financial tracking
    – Inform **MES** or other shop-floor systems of required components for an order or batch
    – Support **traceability** by providing the expected structure against which actual material lots or serials are recorded

    During production, the BOM is typically linked to:

    – A **routing** or process definition (how work is done)
    – **Work orders**, production orders, or batch records (what is executed and when)
    – **Material master** data for each item listed

    Site context: BOM in MES–ERP integration and costing

    For program or product cost tracking across MES and ERP, the BOM commonly:

    – Resides and is maintained in ERP or PLM as the **authoritative product structure**
    – Provides the expected component list and standard quantities used to calculate standard or planned costs
    – Acts as the reference against which MES reports **summarized actual consumption** (by material ID and quantity) back to ERP at defined intervals

    In this context, MES usually does not author the BOM but uses it to validate material usage and ensure that recorded consumption aligns with the qualified product definition.

    Boundaries and exclusions

    A bill of materials **includes**:

    – Physical components, raw materials, and subassemblies
    – Sometimes non-stock items when they are integral to product composition (e.g., labels, certain consumables)

    A bill of materials **does not inherently include**:

    – Detailed work instructions, sequence of operations, or cycle times (these belong to routings or manufacturing instructions)
    – Real-time production data or yield results
    – Quality tests and acceptance criteria (these are typically defined in specifications or control plans)

    Some organizations maintain separate BOM types, such as **engineering BOM (EBOM)** and **manufacturing BOM (MBOM)**, to distinguish design intent from the structure used for actual manufacturing and sourcing.

    Common confusion and related terms

    – **BOM vs. recipe/formula**: In process industries, a *recipe* or *formula* includes process parameters and instructions in addition to material quantities. The BOM portion is the structured list of materials and quantities.
    – **BOM vs. routing**: A BOM defines *what materials* are required; a routing defines *how and in what sequence* operations are performed.
    – **BOM vs. product specification**: Specifications describe properties and performance requirements; the BOM lists the materials that make up the product.

    Understanding these distinctions helps ensure that BOMs are used consistently for planning, costing, and execution across ERP, MES, and quality systems.

  • kitting

    Operational meaning

    Kitting is the process of pre-collecting, organizing, and often packaging all components, materials, and documentation required to execute a specific production order, work step, or service task.

    In manufacturing and industrial operations, kitting typically:

    – Groups parts and materials by product, work order, or assembly step
    – Uses a defined bill of materials (BOM) or pick list as the source of required items
    – Physically separates and labels the collected items as a single “kit” for later use at a workstation or line
    – May include associated paperwork such as travelers, work instructions, or quality check sheets

    Kitting is used to reduce searching on the line, support consistent material availability, and enable clearer accountability for component usage.

    How kitting is used in manufacturing workflows

    In regulated and complex manufacturing environments, kitting commonly appears in:

    – **Pre-assembly or staging areas**: Operators or material handlers pick parts from inventory locations and stage them in totes, racks, or carts as kits.
    – **Line-side replenishment**: Kits are delivered to specific workstations or cells synchronized to production schedules.
    – **Order-specific or lot-specific builds**: Each kit corresponds to a unique order, batch, serial number, or lot, supporting traceability.
    – **Service and maintenance operations**: All spares and consumables needed for a service job are prepared as a kit before the technician starts.

    Digital systems interacting with kitting include:

    – **ERP / WMS**: Generate pick lists, reserve inventory, manage kit stock-keeping units (SKUs) when kits are treated as items.
    – **MES**: Enforce scan-based picking, record which components are in which kit, associate kits with work orders, and track consumption at execution time.
    – **Quality and traceability systems**: Capture component lot, serial, or expiry information per kit for audit and recall analysis.

    Boundaries and what kitting is not

    Kitting:

    – **Is about pre-collection and organization of components** for a defined task or order.
    – **Is typically a material handling and staging activity**, not the actual assembly or transformation of the product.

    Kitting is **not**:

    – **Assembly** – No value-adding transformation is required; parts are only grouped, not built into finished subassemblies.
    – **Generic warehousing** – It is driven by specific work orders or product configurations, not just bulk storage.
    – **Just-in-time (JIT) production** by itself – Kitting may support JIT delivery but is a distinct process step.

    Common variations and practices

    Kitting can take different forms depending on plant layout and product mix:

    – **Order-based kitting**: Each work order or customer order has a dedicated kit.
    – **Operation-based kitting**: Kits are created per routing step (e.g., one kit per station in a mixed-model line).
    – **Static kitting**: Pre-defined kits for standard products or service tasks, often treated as their own SKUs.
    – **Dynamic or configurable kitting**: Kit content varies based on configuration, options, or engineering changes.

    Kits may be tracked by:

    – Physical identifiers (tote ID, cart ID, kit label)
    – System identifiers (kit number, internal tracking ID)
    – Barcodes or RFID tags associated with the kit container

    Kitting in MES and shop-floor control (site context)

    Within MES-governed environments, kitting is often:

    – **Digitally defined** via BOMs, work instructions, or configured product definitions
    – **Executed under control of scan-based picking** (barcode or RFID) to verify each component
    – **Location-aware**, with kits linked to storage and staging locations
    – **Traceability-enabled**, capturing which lots/serials are placed into a given kit and later consumed by which order or unit

    MES can support kitting areas by:

    – Validating picked items against the required list
    – Preventing early or incorrect consumption of scarce or regulated parts
    – Providing visibility into missing, over-picked, or substituted components before the kit leaves the area

    However, the physical risks of loss, misplacement, or damage in kitting areas still depend on local processes, data discipline, and material handling practices.

    Related concepts and common confusion

    Kitting is commonly discussed alongside:

    – **Kanban / line-side supermarkets**: These focus on visual pull and replenishment signals; kitting focuses on pre-assembled sets of parts.
    – **Pre-assembly / subassembly**: These involve physically building sub-components; kitting only groups parts for later assembly.
    – **Picking**: Picking is selecting items from storage; kitting typically includes picking plus grouping, labeling, and sometimes verifying completeness.

    Clarifying these distinctions helps when designing material flow, defining responsibilities between warehouse, kitting, and production, and when modeling processes in ERP, WMS, or MES.

  • part family

    A part family is a group of parts that share common characteristics and are intentionally classified together so they can be planned, produced, and analyzed as a unit. In industrial and manufacturing environments, part families are often based on similarities in design, material, features, manufacturing processes, or the equipment and tooling used.

    Key characteristics

    Part families commonly share one or more of the following:

    • Similar geometry or design features, such as hole patterns, profile shapes, or envelope dimensions
    • Common materials or material groups, such as aluminum forgings, composite layups, or stainless steel turned parts
    • Comparable routings or process steps, such as the same sequence of machining, heat treatment, coating, or inspection
    • Use of the same work centers, cells, tools, fixtures, or programs
    • Shared performance, quality, or traceability requirements, such as the same specification family or qualification level

    Part families can be defined formally in master data (for example, in ERP, MES, or PLM) using codes or attributes, or informally in production and engineering documents. In regulated industries, formal definitions are typically favored so that reporting and evidence are consistent across systems.

    Operational use

    In day-to-day operations, part families are used to:

    • Plan capacity and scheduling by grouping similar demand on shared resources
    • Standardize routings, work instructions, and inspection plans across related parts
    • Analyze performance metrics, such as scrap, rework, cycle time, and on-time delivery, at a level more stable than individual part numbers
    • Support cost modeling, quoting, and product standardization by treating similar parts consistently
    • Structure continuous improvement work, for example by targeting a machining cell’s main part families

    Use in scrap and cost analysis

    When building scrap or cost views, part families provide an intermediate level of aggregation between individual part numbers and entire programs or product lines. For example, an aerospace manufacturer may group different brackets, ribs, or fittings into part families that share raw material, machining steps, or inspection regimes, then compare scrap rate and scrap cost by family across cells, shifts, or suppliers.

    Common confusion

    • Part family vs. part number: A part number uniquely identifies a specific item. A part family is a classification that can include many different part numbers.
    • Part family vs. product family: A product family usually groups finished products or configurations offered to customers. A part family groups components or subassemblies used inside products or programs, for manufacturing and engineering purposes.
    • Part family vs. routing family or process family: A routing or process family groups operations or process templates. A part family may be defined using routing similarities, but it is anchored to the parts themselves, not the operations.

  • stock sweep

    A stock sweep commonly refers to a systematic review of inventory records and physical stock to identify available material that can be used, reallocated, or reconciled. In manufacturing and warehouse operations, it is often performed to find excess, misplaced, slow-moving, or uncommitted stock before new material is purchased or a shortage is escalated.

    The term can describe either a physical inventory search on the floor or a system-driven process in ERP, MES, or warehouse tools that scans stock balances across locations, jobs, lots, or status codes. For example, a planner may run a stock sweep to locate usable parts in another storeroom, or a warehouse team may perform a stock sweep to clear orphaned inventory and correct record accuracy.

    Stock sweep should not be confused with a full cycle count or a formal physical inventory. A cycle count is primarily a counting control, while a stock sweep is usually targeted at finding and consolidating usable inventory, resolving discrepancies, or supporting material availability decisions. Depending on local process, it may also include checking lot status, expiration, hold conditions, and traceability before stock is reassigned or consumed.

  • expiry

    Meaning in industrial and regulated environments

    Expiry commonly refers to a specific point in time after which something is considered no longer valid, usable, or compliant. In industrial and regulated manufacturing, the term is most often applied to:

    – **Materials and products**: the date or time after which a raw material, intermediate, or finished good must not be used or shipped.
    – **Authorizations and records**: the point after which a document, training, or temporary access right is no longer valid and must be renewed or reapproved.

    In all cases, expiry is defined by internal specifications, customer requirements, or external regulations, and is typically captured as a discrete field (for example, expiry date or expiration timestamp) in manufacturing and quality systems.

    Use in manufacturing systems and workflows

    In operations and manufacturing IT/OT systems, expiry is usually managed as a data attribute that drives system behavior:

    – **ERP/MES**: expiry dates on lots, batches, serial numbers, or stock items are used to prevent issue, consumption, or shipment after the expiry point.
    – **QMS/LIMS**: test results, stability studies, and certificates may define or update a material’s expiry; QMS workflows enforce holds or re-inspection when expiry is reached or approached.
    – **Labeling and traceability**: expiry data is printed on labels and encoded in barcodes or RFID to support traceability and ensure only in-date materials are used.
    – **Access and training systems**: user roles, training records, and qualifications can have expiry, controlling which tasks an operator is allowed to perform.

    Operationally, expiry is treated as a constraint: systems often block or warn on transactions that would consume or move expired items, and reports highlight quantities at or beyond expiry for review and disposition.

    Boundaries and exclusions

    In this site context, **expiry** generally includes:

    – Time limits on the **use or validity** of materials, products, documents, or authorizations.
    – Explicit dates, times, or periods (for example, shelf life leading to an expiry date).
    – System rules and checks that enforce those time limits.

    It generally **does not refer to**:

    – Commercial contract expiration (for example, end of a service subscription), except where it directly constrains manufacturing operations.
    – Software license expiry in a purely IT procurement sense, unless it is directly modeled as an operational constraint in OT/IT systems.

    Common confusion and terminology

    Several related terms are often used alongside or instead of “expiry”:

    – **Expiration date / expiry date**: the specific calendar date after which the item or authorization is considered expired. In practice, these are interchangeable with “expiry” in many plants.
    – **Shelf life**: the defined period during which a material or product is expected to remain within specification when stored under stated conditions; expiry occurs at the end of the shelf life.
    – **Best before / use by**: consumer-facing terms; in regulated industrial settings, the internal system usually still tracks a formal expiry date even if labels use different phrasing.

    It is also useful to distinguish **expiry** from:

    – **Obsolescence**: when a product, material, or document is deliberately replaced or withdrawn for business or technical reasons, not necessarily because of time-based degradation.
    – **Hold or quarantine**: a temporary restriction on use that may or may not be related to expiry.

    Site context: expiry in waste and performance metrics

    When measuring material waste or yield in manufacturing, expiry is often treated as a specific waste category:

    – **Expired stock**: inventory that has reached its expiry date and cannot be used in production or shipped, typically counted as scrap or write-off.
    – **Expiry-related KPIs**: some plants track metrics such as cost of expired materials, percentage of inventory lost to expiry, or volume of product reworked or discarded due to nearing expiry.

    In integrated MES/ERP/QMS environments, expiry information can therefore influence planning, scheduling, and inventory strategies, as well as reportable waste and quality indicators.

  • Ramp-up

    Ramp-up is the controlled increase of production volume, staffing, equipment use, or system activity from an initial level toward a planned operating rate. In manufacturing, it commonly refers to the period after a product launch, line start, process change, or capacity addition when output is increased while performance is monitored.

    During ramp-up, teams typically track whether materials, work instructions, labor, equipment, quality checks, and system transactions can support the higher rate. In MES, ERP, and planning contexts, ramp-up may affect routings, work orders, schedules, inventory demand, inspection load, and throughput assumptions.

    Ramp-up is not the same as startup, which usually refers to the initial act of bringing a process, line, or system into operation. It is also different from capacity, which describes the amount of output a process can support under defined conditions. Ramp-up is the transition toward that expected operating level.

  • Product supplier

    A product supplier is an external organization or business unit that provides finished goods, subassemblies, raw materials, or critical components to another organization under a supply or purchase agreement. In industrial and manufacturing settings, the term usually refers to companies that deliver materials or parts used in production, packaging, maintenance, or distribution.

    A product supplier may manufacture the items it supplies, act as a distributor or reseller, or coordinate outsourced production. The relationship is typically defined by contracts, purchase orders, specifications, and quality agreements that describe what is delivered, required standards, lead times, pricing, and responsibilities.

    Scope and characteristics

    In regulated and industrial environments, a product supplier commonly:

    • Provides physical goods such as ingredients, raw materials, components, tooling, spare parts, or finished products
    • Is subject to qualification, approval, and ongoing monitoring by the buying organization (for example, through a supplier quality management process)
    • Must comply with defined specifications, drawings, test methods, and regulatory or industry standards
    • Is managed through supply chain, procurement, and quality systems, often integrated with ERP, MES, or supplier portals
    • May participate in change control, deviation handling, and corrective and preventive action (CAPA) processes when issues arise

    A product supplier is distinct from internal production departments. It sits outside the buying organization’s direct operational control and is managed via contracts and supplier management processes rather than internal work instructions alone.

    Operational context in manufacturing

    Within manufacturing operations, product suppliers impact several areas:

    • Planning and MRP: Supplier lead times, minimum order quantities, and reliability feed material requirements planning and production scheduling.
    • Quality management: Incoming inspection, supplier audits, nonconformance handling, and supplier corrective actions focus on supplier performance and conformance to specifications.
    • Compliance and traceability: Supplier information, certificates, and batch/lot data may be captured in ERP, MES, or quality systems to support traceability, genealogy, and regulatory evidence.
    • Risk management: Critical product suppliers may be assessed for supply continuity, single-source risks, and cybersecurity or data handling practices when digital data is exchanged.

    Common confusion

    • Product supplier vs. service provider: A product supplier delivers tangible goods. A service provider mainly delivers services (for example, calibration, maintenance, consulting). Some organizations perform both roles.
    • Product supplier vs. manufacturer: A manufacturer produces goods. A product supplier may be the manufacturer, but might also be a distributor, wholesaler, or integrator who sources from multiple manufacturers.
    • Product supplier vs. vendor: In many companies the terms are used interchangeably. “Vendor” is often broader and can include both product suppliers and service providers.

    Use in regulated and quality-focused environments

    In regulated industries, product suppliers are often categorized and controlled based on the criticality of the materials or components they provide. Procedures may define how suppliers are selected, qualified, monitored, and re-evaluated, and how data from suppliers (such as certificates of analysis or conformity) is stored and linked to production records and batch histories.

    Digital systems such as ERP, MES, and quality management systems commonly maintain master data for each product supplier, including identifiers, approved materials, quality status, and performance indicators, to support consistent operations and audit readiness.