Connect981 – Content Dev

RSC Topic: Planning & MRP Alignment

Connecting ERP planning signals to real execution constraints.

  • 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.

  • BOM

    Core meaning

    BOM (bill of materials) is a structured list that defines all items required to build, test, and package a product or configured item. It typically includes:

    – Components and subassemblies
    – Raw and semi-finished materials
    – Standard parts (e.g., fasteners, fittings)
    – Consumables when they are controlled (e.g., adhesives, sealants)
    – Documentation and references needed for release (e.g., drawings, specs)

    A BOM usually specifies quantities, units of measure, revision or version identifiers, and relationships between parent items and child components.

    Use in manufacturing and regulated operations

    In industrial and regulated environments, a BOM commonly refers to one or more of the following structures:

    – **Engineering BOM (EBOM)**: Product definition from design/engineering, aligned to drawings and design intent.
    – **Manufacturing BOM (MBOM)**: Product definition aligned to how the product is built, sequenced, or grouped on the shop floor.
    – **Service or maintenance BOM**: Parts and assemblies needed to maintain, repair, or overhaul the product.

    In practice, BOMs are used to:

    – Drive material planning and procurement in ERP/MRP
    – Define what must be issued to, and consumed on, work orders in MES
    – Support configuration control and variation management (options, variants, effectivity)
    – Provide traceability for components and materials in quality and compliance records

    BOM in MES, quality, and configuration control (site context)

    Within MES and quality systems, especially in high-regulation sectors such as aerospace:

    – The BOM identifies **which part numbers and revisions** are valid for a given product or work order.
    – MES may compare **actual components scanned or recorded on the line** against the BOM to detect:
    – Wrong part numbers
    – Wrong revisions or superseded parts
    – Missing required components
    – Alerts can be configured when a build deviates from the approved BOM, supporting scrap prevention and nonconformance control.
    – BOM information is often linked to **routing/operations**, **process plans**, and **specification documents** to ensure the right material and documentation are used together.

    Boundaries and exclusions

    – A BOM defines **what** items are required, not **how** they are processed. Operation steps, machines, and process parameters are typically defined in routings, travelers, or work instructions, not in the BOM itself.
    – A BOM is not the same as:
    – A **routing** or process plan (sequence of operations and resources)
    – A **recipe** (parameterized processing instructions, often for process industries)
    – A **production schedule** (timing and quantity of planned orders)

    However, all of these structures usually reference or depend on a consistent, controlled BOM.

    Common variations of BOM structures

    Organizations may define specialized BOM types, such as:

    – **Configurable or variant BOM**: Supports options and variants, often used with configuration rules.
    – **Phantom BOM**: Logical grouping of items used for planning, not built as a separate stockkeeping unit.
    – **As-planned, as-released, as-built, and as-maintained BOM views**: Different life-cycle views of the same product, important for traceability in regulated industries.

    Terminology and exact behavior can differ by ERP/MES vendor, but all of these remain specific ways of structuring the underlying bill of materials.

    Common confusion and misuse

    – **BOM vs. part list on a drawing**: A drawing parts list may be one representation of a BOM, but in most controlled environments the master BOM is maintained in a PLM, PDM, or ERP system, with drawings acting as a reference.
    – **BOM vs. inventory list**: A BOM specifies what is required for one unit (or another defined quantity) of a product. Inventory lists show what is available in stock, regardless of any single product.
    – **BOM vs. specification**: Specifications define requirements (e.g., material properties, tolerances). The BOM references which materials or parts are used to meet those requirements, but does not replace the specs themselves.

    Understanding these boundaries helps keep engineering change, MES configuration, and quality records aligned around a single, controlled definition of the product structure.

  • advanced planning system

    Core meaning

    An **advanced planning system** (APS) is a software system used to perform complex planning and scheduling across supply, production, and distribution operations. It typically supplements or extends enterprise resource planning (ERP) and material requirements planning (MRP) by using more flexible, constraint-based, or optimization-based models.

    In industrial and manufacturing environments, an APS commonly:

    – Plans medium- to long-term production, capacity, and material requirements
    – Considers constraints such as machine capacity, labor, changeover times, and lead times
    – Balances demand forecasts, customer orders, and inventory targets
    – Generates proposed production plans, purchase plans, and distribution plans for review in ERP

    APS tools are often used for **sales and operations planning (S&OP)**, **master production scheduling (MPS)**, and **distribution requirements planning (DRP)** activities.

    Relationship to ERP, MRP, and MES

    An advanced planning system typically operates alongside other core systems:

    – **ERP/MRP**: ERP is usually the system of record for orders, inventory, and master data. The APS consumes this data, runs advanced planning logic, and sends back proposed plans (e.g., planned orders, capacity plans, inventory targets) to be executed or approved in ERP/MRP.
    – **MES**: MES records actual shop-floor execution (production quantities, scrap, cycle times, downtime). APS may use aggregated or validated MES data as inputs to refine capacity assumptions, lead times, and inventory policies.
    – **WMS/TMS and other logistics tools**: APS may integrate with warehouse and transportation systems to plan distribution and replenishment.

    An APS itself does **not** execute production, create shop-floor instructions, or act as the primary transaction ledger; it focuses on planning and simulation rather than execution.

    Typical planning functions

    While capabilities vary by vendor and implementation, advanced planning systems commonly include:

    – **Demand planning and forecasting**: Statistical or collaborative forecasting to estimate future demand.
    – **Supply and production planning**: Medium- to long-term planning of materials, capacity, and production sequences.
    – **Finite capacity scheduling**: Detailed scheduling that respects machine, labor, tooling, and changeover constraints.
    – **Inventory and safety stock planning**: Calculation of target stock levels, reorder points, and safety stock policies based on demand, variability, and service-level targets.
    – **Distribution and network planning**: Allocation of inventory across sites, allocation of production across plants, and inter-site replenishment planning.

    Boundaries and exclusions

    In this site context, “advanced planning system” typically **includes**:

    – Standalone APS products integrated with ERP/MES
    – Advanced planning modules within an ERP suite (even if branded differently)
    – Cloud-based planning platforms used for multi-site production and inventory planning

    It generally **excludes**:

    – Simple spreadsheet-based planning tools
    – Basic MRP runs executed only inside an ERP without constraint-based or optimization logic
    – Short-horizon machine schedulers embedded directly in equipment or controllers (those are usually considered scheduling or dispatching tools, not full APS solutions)

    Use in manufacturing workflows

    In regulated and complex manufacturing environments, advanced planning systems are commonly used to:

    – Translate demand forecasts into capacity and material plans over weeks to months
    – Simulate alternative scenarios (e.g., line outages, new product launches, supplier delays)
    – Propose changes to procurement plans, production mixes, and inventory targets
    – Coordinate planning across multiple plants, contract manufacturers, or warehouses

    Operationally, planners review APS outputs (such as proposed planned orders and safety stock values) and then approve or adjust them before they are committed in ERP or other execution systems.

    Site context: interaction with MES and safety stock

    Within this site’s context, an advanced planning system is often the **planning layer** that calculates and maintains parameters such as **safety stock**, reorder points, and planning horizons.

    Common patterns include:

    – MES provides validated operational signals (actual lead times, yield, scrap, adherence to schedule) to the APS or to ERP.
    – The APS uses these signals, along with demand data, to recalculate proposed safety stock levels and inventory policies.
    – Resulting changes to safety stock or planning parameters typically enter a controlled review and approval workflow in ERP or planning governance tools, rather than being updated automatically from MES.

    This preserves traceability and change control for planning parameters while still leveraging MES data to keep the APS models aligned with real operations.

    Common confusion and related terms

    “Advanced planning system” is often used interchangeably with:

    – **APS (Advanced Planning and Scheduling)**: Many vendors use APS to mean both advanced planning and finite scheduling in one suite.
    – **Advanced planning and optimization (APO)** or similar branded names: These are vendor-specific implementations of an APS concept.

    It is distinct from:

    – **MES (Manufacturing Execution System)**, which manages and records shop-floor execution.
    – **Basic MRP**, which usually performs unconstrained material planning without advanced optimization or scenario modeling.

    In practice, organizations may refer to different modules (demand planning, production planning, detailed scheduling) collectively as their “advanced planning system” when they are part of a unified planning environment.

  • Which NCRs should be prioritized to protect delivery schedules?

    Prioritizing NCRs to protect delivery schedules means ranking them by their realistic impact on committed ship dates, without violating safety or regulatory constraints. This depends heavily on your product mix, routing design, rework capabilities, and planning systems, so any rule set must be tuned and validated plant by plant.

    1. Nonconformances on parts directly linked to near-term customer commits

    Top priority goes to NCRs on items that will affect firm customer deliveries inside your planning horizon (for example, the next 2 to 6 weeks):

    In practice, this connects to non-conformance management when teams need to turn the answer into repeatable execution habits.

    • Finished goods or final assemblies with open NCRs and booked ship dates.
    • Key subassemblies on the critical path for those finished goods, especially where lead time for replacement is long.
    • Configuration- or serial-controlled items where swapping parts is not straightforward due to traceability, certification, or qualification constraints.

    In brownfield environments, this requires reliable linkage between NCR records and your MRP/ERP or MES (item, lot/serial, work order, and due date). If that linkage is weak, you will need manual triage (for example, planners and production control reviewing NCR queues daily).

    2. NCRs on unique or long-lead components with no easy substitute

    Even if ship dates are not immediate, NCRs on constrained components can quietly become the future bottleneck:

    • Custom or qualified components with single-source or heavily qualified suppliers.
    • Parts with long manufacturing or test cycles, including special processes that require scarce equipment or certified operators.
    • Items with export control or special handling, where reordering or resourcing is slow and paperwork-heavy.

    These should be ranked ahead of NCRs on commodity items where replenishment or substitution is quick, provided no safety or regulatory issues are being deferred.

    3. NCRs late in the routing where scrap or rework loses the most lead time

    An identical defect has more schedule impact when it is discovered late in the process:

    • Final inspection and test NCRs, especially those that trigger rework loops across multiple departments.
    • Post-special-process stages (for example, heat treat, plating, complex software load) where capacity is tight and rework queues are long.
    • Customer hold or source inspection points, where NCRs may drive additional coordination or re-approval cycles.

    In practice this means NCRs at the end of the router for a near-due order should usually be pulled to the top of the queue, because every day lost is directly visible in OTIF/OTD metrics.

    4. NCRs blocking constrained shared resources

    Some NCRs stall a constrained machine, fixture, or test stand and thus delay many orders at once. These often matter more to schedule than isolated issues:

    • Large batch NCRs holding up a furnace, plating line, or autoclave.
    • Fixtures or tools under NCR that are required across multiple programs or product lines.
    • Shared test equipment where an NCR on one job prevents use by others.

    Even if individual orders are not yet near due, clearing these NCRs can release capacity and reduce systemic schedule risk.

    5. NCRs with viable, fast dispositions versus those needing long investigations

    To defend near-term delivery, prioritize NCRs where a disposition decision can realistically be made quickly and safely:

    • Known, previously seen conditions with established, validated rework or use-as-is criteria.
    • NCRs with clear data (measurements, photos, traceable process parameters) so MRB or engineering can decide with minimal back-and-forth.
    • Conditions within defined concessions or deviations that can be applied using existing procedures.

    High-uncertainty or novel conditions still need attention, but if their affected orders are not on the near-term delivery horizon, it is usually more schedule-protective to resolve quick, high-impact NCRs first.

    6. NCRs tied to safety, regulatory, or customer-mandated characteristics

    Safety- and compliance-related NCRs often cannot be traded off purely on delivery impact. They may require:

    • Full MRB review with engineering and quality sign-off.
    • Customer notification or approval for use-as-is or repair.
    • Formal risk assessments or impact analyses on field performance.

    These should be flagged and treated according to your quality system and contracts. From a schedule perspective, resolving them early is critical because they can cause late-stage holds or shipment stops if left to the end.

    7. Practical prioritization criteria to implement

    A simple, operational way to triage NCRs is to assign each record a few standardized attributes and use them to sort the queue:

    1. Delivery risk score based on:
      • Next required date for the affected part or work order.
      • Time to recover via remake (manufacturing + queue + qualification).
      • Time to recover via rework (engineering, processing, retest).
    2. Criticality classification for the item:
      • Safety- or regulatory-critical characteristics present.
      • Single-source or long-lead component vs commodity item.
    3. Routing position and asset impact:
      • Early/mid/late stage in the router.
      • Uses constrained or shared resources that may be blocked.
    4. Disposition complexity:
      • Standard, pre-approved disposition path vs novel case.
      • Customer or regulator approval required.

    With this information, you can create a prioritized NCR list that gives first attention to: near-due orders, critical components, late-stage finds, and issues that can be resolved quickly without undermining compliance.

    8. Coexistence with existing QMS, MES, and ERP systems

    In most regulated plants, NCRs live in a QMS that only partially talks to MES and ERP. Full replacement of these systems just to improve NCR prioritization is rarely justified due to validation and downtime risk. Instead:

    • Start with process: Define a cross-functional daily NCR triage (quality, planning, production control) using a shared list, even if exported manually.
    • Use light integration where possible: Link NCRs to work orders, lots/serials, and due dates via existing IDs, then pull this data into simple reports or dashboards.
    • Validate any prioritization logic: Treat new reports, rules, and workflows as changes under your quality system, with documented testing and impact assessment.
    • Respect long equipment lifecycles: Do not assume you can embed new NCR workflows into every legacy machine or tester; focus integration at the QMS/MES/ERP layer.

    Over time, you can refine triage rules using actual performance data (for example, which NCR types historically caused the most days of slip) rather than relying on intuition alone.

    9. Tradeoffs and limitations

    Any NCR prioritization scheme has constraints:

    • Data quality limits precision: If routings, lead times, and due dates are inaccurate, delivery risk scoring will be approximate.
    • Compliance requirements cap flexibility: Some NCRs must be handled in specific ways and timelines, regardless of schedule impact.
    • Local context matters: A rule that makes sense for one plant or product line may not generalize because of different suppliers, test regimes, or regulatory exposure.

    The objective is not a perfect algorithm but a transparent, defensible method that improves on FIFO handling of NCRs and focuses limited engineering and MRB capacity where it actually protects delivery.

  • Stockist

    A stockist is an organization or business unit that holds, manages, and supplies inventory, typically on behalf of manufacturers, distributors, or end customers. In industrial and regulated manufacturing environments, a stockist often acts as an intermediate inventory holder, ensuring that parts, materials, or consumables are available when required for production or maintenance activities.

    Core characteristics of a stockist

    In the context of manufacturing and industrial supply chains, a stockist commonly:

    • Maintains physical inventory of parts, materials, or products, often across multiple locations or regions.
    • Receives goods from one or more suppliers and stores them under defined storage, handling, and identification controls.
    • Issues or ships items to manufacturers, maintenance organizations, or downstream customers based on orders, schedules, or contract terms.
    • Tracks inventory balances, lot or batch information, and basic traceability data, sometimes integrated with the customer’s ERP or MES.
    • May perform limited value-added services such as repackaging, labeling, or basic inspections according to agreed procedures.

    A stockist can be:

    • An independent third-party distributor or logistics provider.
    • A business unit within a larger enterprise that manages centralized inventory for multiple plants or service centers.
    • A local or regional warehouse that serves as a buffer between global suppliers and point-of-use locations on the shop floor.

    Operational role in regulated manufacturing

    In regulated industries such as aerospace, defense, or medical device manufacturing, stockists are often part of the controlled supply chain. Their activities may include:

    • Maintaining records that support traceability back to original manufacturers, including lot, serial, and certificate references.
    • Handling documentation such as certificates of conformity, material test reports, and shelf-life or environmental storage data.
    • Aligning their inventory control processes with customer quality and procurement requirements, including labeling and segregation of conforming and nonconforming stock.
    • Interfacing electronically with customer systems for advanced shipment notices, consignment stock visibility, or replenishment signals.

    What a stockist is not

    • It is not a manufacturer of the goods it holds, although a stockist may belong to the same corporate group as a manufacturer.
    • It is not typically responsible for product design, regulatory approvals, or process validation of the items stored.
    • It is not necessarily a full-line distributor offering technical application support, though some stockists may provide limited advisory services.

    Common confusion

    Stockist vs distributor: In many regions, the terms are used interchangeably. In some organizations, a distributor emphasizes commercial responsibilities (sales, market coverage), while a stockist emphasizes the inventory-holding and fulfillment function.

    Stockist vs warehouse: A warehouse is a physical facility. A stockist refers to the entity or function responsible for owning or controlling the inventory and managing its flow, which may use one or more warehouses.

    Examples in manufacturing workflows

    • Aerospace OEMs using regional stockists to hold standard hardware (fasteners, fittings) near multiple assembly plants, with inventory data integrated to the ERP for planning and MRP.
    • Maintenance, repair, and overhaul (MRO) operations sourcing spare parts from approved stockists that can provide required documentation and traceability for each lot or serial number.
    • Manufacturers using a consignment model where a stockist holds material on-site at the plant, with ownership transferred when parts are consumed in production.

  • long-term agreement

    A long-term agreement is a contract between two parties that defines commercial, technical, and supply terms over an extended period, typically covering multiple years of repeat business rather than a single purchase or project. In industrial and manufacturing contexts, it is commonly used between manufacturers and customers, or between manufacturers and key suppliers, to support ongoing programs and predictable demand.

    Key characteristics

    In regulated and complex manufacturing environments, a long-term agreement commonly includes:

    • Duration and scope: A defined term (for example 3 to 10 years) covering a family of parts, assemblies, or services, often linked to a product platform or program.
    • Pricing structure: Fixed prices, price adjustment formulas, or indexed pricing over time, sometimes including volume breaks or escalation clauses.
    • Demand and volume expectations: Forecasts, minimum or maximum quantities, and call-off mechanisms (for example releases or schedules rather than individual spot POs).
    • Quality and technical requirements: Agreed specifications, quality standards, change control processes, and sometimes defined metrics for performance.
    • Logistics and lead time terms: Lead times, stocking strategies, delivery locations, and packaging or handling requirements.
    • Risk and liability allocation: Provisions on obsolescence, inventory exposure, nonconformance handling, and remedies for schedule or quality issues.

    Operational meaning in manufacturing

    Long-term agreements influence how operations, supply chain, and finance plan and control work. They often:

    • Drive MRP and capacity planning assumptions through contractual forecasts and committed volumes.
    • Shape margin stability by locking in pricing while internal costs (including scrap and rework) may vary.
    • Constrain or guide engineering changes through agreed change control and notification periods.
    • Define data exchange and systems integration requirements, such as EDI schedules, quality reporting, or traceability records.
    • Influence supplier qualification and oversight, because performance is managed across years rather than order by order.

    Use in regulated and high-cost environments

    In sectors such as aerospace, defense, and medical devices, long-term agreements are frequently tied to program lifecycles and high-value components. In these settings:

    • Scrap, yield, and rework performance affect profitability under fixed or semi-fixed pricing defined in the agreement.
    • Long lead times and capacity constraints are addressed through contractual visibility of demand and inventory responsibilities.
    • Compliance, documentation, and traceability expectations are embedded in the contractual quality and data provisions.

    What it is not

    • It is not a single purchase order, although releases under a long-term agreement may be issued via POs or schedules.
    • It is not limited to pricing only; it usually combines technical, quality, commercial, and logistical terms.
    • It is not necessarily exclusive; some agreements are sole-source, but others allow multiple suppliers or customers.

    Common confusion

    • Long-term agreement vs. blanket purchase order: A blanket PO typically authorizes a total spend or quantity over a period, while a long-term agreement is a broader contract that may govern multiple POs, releases, and sites.
    • Long-term agreement vs. master service agreement (MSA): An MSA often defines general legal and commercial terms for services. A long-term agreement in manufacturing is usually more specific about part numbers, volumes, and program-level commitments.

    Link to the provided context

    In the provided aerospace context, long-term agreements and fixed-price contracts mean that scrap and variability in manufacturing performance directly affect margin stability and delivery reliability across the life of the program, rather than being just a short-term quality metric.