Connect981 – Content Dev

RSC Topic: Planning & MRP Alignment

Connecting ERP planning signals to real execution constraints.

  • Chief Supply Chain Officer

    The Chief Supply Chain Officer (CSCO) is a senior executive responsible for the end-to-end design, governance, and performance of an organization’s supply chain. In industrial and regulated manufacturing environments, this typically covers planning, sourcing, production logistics, distribution, and related risk and compliance activities.

    Scope of responsibility

    A CSCO commonly oversees:

    • Supply chain strategy: Defining how the organization plans, sources, manufactures, and delivers products in alignment with overall business strategy.
    • Planning and materials management: Sales & operations planning (S&OP or SIOP), demand planning, MRP parameters, inventory policies, and service-level targets.
    • Procurement and suppliers: Supplier selection, contracts, performance management, and supply continuity, often including quality and regulatory expectations for suppliers.
    • Manufacturing and logistics interfaces: Coordination with operations, MES/ERP, warehousing, transportation, and distribution networks.
    • Risk and compliance: Supply chain risk management, business continuity planning, and adherence to applicable regulatory and quality requirements that affect materials flow, traceability, and documentation.
    • Financial performance: Supply chain cost, working capital tied up in inventory, and service metrics that impact revenue and customer commitments.

    Operational meaning

    Operationally, the CSCO is the primary escalation and decision point for cross-functional tradeoffs that affect the supply chain, such as capacity constraints, allocation decisions, and major supplier or logistics disruptions. The role often sponsors large-scale initiatives involving ERP, MES, planning tools, and supplier collaboration platforms, and may own or co-own key performance indicators such as on-time delivery, inventory turns, and supply-related nonconformance rates.

    Position in the organization

    The CSCO is usually part of the executive leadership team and typically reports to the Chief Executive Officer, Chief Operations Officer, or a similar top-level executive. Titles with similar scope can include Head of Supply Chain, SVP Supply Chain, or VP Global Supply Chain, depending on company size and structure.

    Common confusion

    The CSCO is sometimes confused with:

    • Chief Operations Officer (COO): A COO usually has broader responsibility across manufacturing, facilities, and overall operations, which may include but is not limited to the supply chain.
    • VP of Operations or Plant Manager: These roles typically focus on internal production operations, while the CSCO focuses on the full external and internal supply chain from suppliers to customers.

  • SAP ERP

    SAP ERP is SAP’s enterprise resource planning software suite used to manage and integrate core business processes across an organization, including finance, procurement, manufacturing, supply chain, and human resources. In industrial and regulated manufacturing environments, SAP ERP commonly serves as the system of record for planning, master data, and transactional business processes.

    Scope and core functions

    In a manufacturing context, SAP ERP typically includes:

    • Materials management (purchasing, inventory, material master data)
    • Production planning (MRP, capacity planning, production orders)
    • Sales and distribution (customer orders, delivery, billing)
    • Quality management at a business-process level (inspection lots, usage decisions, defect records)
    • Plant maintenance (maintenance orders, equipment records)
    • Finance and controlling (cost tracking, profitability analysis)

    SAP ERP is not primarily a shop-floor control system. It typically operates at higher planning and business-process levels, while integrating with manufacturing execution systems (MES), laboratory systems, and other OT/IT platforms.

    Relationship to SAP S/4HANA and MES

    The term “SAP ERP” most often refers to SAP’s classic ERP product line (such as SAP ERP Central Component, ECC). SAP S/4HANA is SAP’s newer ERP platform, but many users still refer to it generically as “SAP ERP” when describing its role in the architecture.

    SAP, as a vendor, also offers MES and manufacturing-focused products such as SAP Digital Manufacturing and legacy SAP ME/MII. These are separate from SAP ERP, even though they share data and may be deployed together. In regulated manufacturing, SAP ERP commonly coexists with:

    • A dedicated MES for detailed work instructions, real-time execution, and enforcement of shop-floor rules
    • Quality, LIMS, and other systems that handle detailed records and evidence

    Operational use in regulated environments

    Within regulated operations, SAP ERP commonly:

    • Stores master data such as materials, bills of material, routings, and resources
    • Generates planned and process orders that are dispatched to MES or shop-floor systems
    • Captures business-level confirmations, goods movements, and batch records at a summary level
    • Supports traceability by managing batch numbers, serial numbers, and inventory status

    Execution details, operator actions, and equipment-level data are often managed in MES or other specialized systems and then interfaced back to SAP ERP for posting and reporting.

    Common confusion

    • SAP vs. SAP ERP: “SAP” is the vendor. “SAP ERP” is the ERP product family. Not every SAP product is an ERP system.
    • SAP ERP vs. MES: SAP ERP handles planning and business transactions. MES manages real-time production execution, detailed work instructions, and in-process data collection on the shop floor.
    • SAP ERP vs. SAP S/4HANA: S/4HANA is SAP’s modern ERP platform. In many architectures it plays a similar role to legacy SAP ERP but on a different technology stack.

  • advanced shipping notice (ASN)

    An advanced shipping notice (ASN) is an electronic message sent by a supplier before a physical shipment arrives, describing the contents of the shipment, how it is packaged, and the planned arrival details. In industrial and regulated manufacturing environments, ASNs are typically structured documents exchanged through EDI, supplier portals, or integrated ERP/MES systems.

    What an ASN typically includes

    Although formats vary by customer and standard, an ASN commonly includes:

    • Shipment identifiers, such as ASN number and shipment ID
    • Linked commercial documents, typically purchase order (PO) numbers and line items
    • Carrier and logistics data, such as carrier name, tracking number, shipment method, and planned delivery date
    • Packing structure, including pallets, cartons, and container IDs with quantities per package
    • Item-level details, including part numbers, revisions where applicable, lot/batch numbers, and serial numbers when required
    • Label references, such as barcodes or license plate numbers used for scanning on receipt
    • Regulatory or quality flags, such as hazardous classification, temperature control indication, or special inspection requirements

    Operational role in manufacturing and logistics

    In manufacturing and operations, ASNs are used to synchronize inbound logistics with production and quality workflows. Systems such as ERP, WMS, and MES may consume ASN data to:

    • Prepare receiving and inspection activities before the truck arrives
    • Align received quantities with open POs and work orders
    • Update expected-on-hand and shortage views for materials planning and backlog risk assessment
    • Drive barcode or license-plate scanning on the dock and in stockrooms
    • Support traceability by pre-registering lots, serial numbers, and expiration dates

    In regulated and aerospace environments, ASNs can also be tied to required documents such as certificates of conformity, material certifications, and inspection results, though those documents may be transmitted through separate channels.

    What an ASN is not

    • It is not the physical shipment itself; it is an electronic notification about an upcoming shipment.
    • It is not a purchase order; it references and confirms how existing POs and lines are being fulfilled.
    • It is not a proof of delivery; actual receipt and inspection records are captured separately in receiving, warehouse, or MES systems.

    Common confusion

    • ASN vs. packing list: A packing list is a physical or digital document that travels with the shipment. An ASN is typically sent in advance and is structured for system integration, enabling automated receiving and planning.
    • ASN vs. shipping confirmation: A simple shipping confirmation may only state that something has shipped. An ASN usually provides detailed, item-level, and package-level data that is mapped to POs and used by downstream systems.

    Connection to backlog and supply risk

    For supply chain and backlog execution analysis, ASNs provide forward-looking visibility into what material is actually in transit, how it maps to specific POs and parts, and when it is expected to arrive. When integrated with ERP, MRP, and production scheduling, this data helps organizations distinguish between theoretical supplier commitments and material that is physically on its way.

  • SAP

    SAP commonly refers to the suite of enterprise software products from the company SAP SE, best known for its Enterprise Resource Planning (ERP) systems used to manage core business and manufacturing processes end to end.

    Core meaning in manufacturing and regulated industries

    In industrial and regulated environments, SAP usually means the SAP ERP platform and its related applications that handle:

    • Planning and materials management (for example, MRP, inventory, purchasing)
    • Production planning and basic shop order management
    • Finance and controlling (costing, general ledger, project accounting)
    • Sales, distribution, and supply chain processes
    • Quality management at the enterprise level (for example, inspections, nonconformances)

    SAP provides multiple products and modules that interact with manufacturing operations, such as:

    • SAP ERP / SAP S/4HANA for core business and planning transactions
    • SAP ME (Manufacturing Execution) and SAP Digital Manufacturing for plant-floor execution functions
    • SAP MII (Manufacturing Integration and Intelligence) for integrating OT systems and visualizing production data

    In many brownfield or highly regulated plants, SAP is integrated with dedicated MES, LIMS, historians, and other OT systems rather than replacing them. SAP typically acts as the system of record for orders, materials, and finance, while specialized shop-floor systems manage detailed execution, equipment control, or electronic batch records.

    Operational role

    Operationally, SAP appears in manufacturing workflows as the system that:

    • Issues and manages production orders and process orders
    • Defines and maintains routings, bills of material, and resources
    • Captures confirmations, backflushed material consumption, and goods movements
    • Exchanges data with MES and OT systems for status, yields, and quality results
    • Provides traceability and genealogy at the batch, lot, or serial level when configured

    Integration with SAP is often a key design topic in MES, data historian, and quality system projects, especially where data integrity, audit trails, and regulatory records are important.

    Common confusion

    SAP vs. MES: SAP ERP (including SAP S/4HANA) is not, by itself, a traditional Manufacturing Execution System. While SAP offers MES-related products (such as SAP ME and SAP Digital Manufacturing) and some execution features in ERP, many plants still use dedicated MES platforms or legacy shop-floor systems for detailed execution, equipment interfaces, and real-time operator workflows.

    SAP (software) vs. sap (other meanings): In other contexts, “sap” can mean plant fluid or a slang term for a person, but in industrial and IT discussions it almost always refers to the SAP enterprise software ecosystem.

  • Backlog

    A backlog commonly refers to a prioritized list of work items that have been identified but not yet completed. In industrial operations and manufacturing, this usually represents work that is queued, waiting to be planned, scheduled, or executed.

    In manufacturing and industrial operations

    In regulated manufacturing environments, a backlog can include:

    • Production backlog: Confirmed customer orders, work orders, or batches that have been released or approved but not yet processed through the shop floor.
    • Maintenance backlog: Preventive or corrective maintenance tasks that have been logged in a CMMS or EAM system but are not yet completed.
    • Quality backlog: Open nonconformances, CAPAs, inspection lots, or test activities awaiting review, disposition, or closure.
    • IT/OT change backlog: Requested changes, enhancements, or fixes to MES, ERP, SCADA, or other systems, often managed in a ticketing or agile tool.

    Backlogs are often maintained in digital systems such as ERP, MES, QMS, EAM/CMMS, or agile project tools. They are typically ordered by priority, due date, risk, or regulatory impact to support planning, resource allocation, and compliance oversight.

    Operational meaning

    Operationally, a backlog indicates work that is known, documented, and pending. It:

    • Helps planners and supervisors see upcoming demand on equipment, labor, and materials.
    • Supports compliance by showing traceable records of identified but incomplete tasks (for example, open audit findings or open NCRs).
    • Is often reviewed in production meetings, tier meetings, and continuous improvement reviews to address bottlenecks and overdue items.

    A backlog does not include work that is completely unknown or unrecorded, and it does not necessarily imply a problem by itself. Issues arise when backlogs grow faster than they can be worked, or when critical items remain unresolved beyond defined timeframes.

    Common confusion

    • Backlog vs. WIP (Work in Process): WIP refers to work currently being processed on the shop floor. Backlog usually refers to work waiting to start or waiting for a specific action (for example, review, approval, or scheduling).
    • Backlog vs. capacity: Backlog is the queue of work. Capacity is the available ability to complete that work (people, machines, time). A large backlog is not the same as high capacity.
    • Backlog vs. order book: An order book may show all confirmed orders. The backlog is typically the portion not yet completed or shipped.

    Use in agile and IT/OT contexts

    In agile or DevOps approaches applied to manufacturing IT and OT systems, a backlog is the ordered list of user stories, features, defects, and technical tasks for systems such as MES, ERP integrations, dashboards, or automation projects. Teams pull from this backlog into sprints or work cycles, using it as the single source of planned work.

  • PO to WO Linkage

    PO to WO linkage commonly refers to the systematic connection between purchase orders (POs) and work orders (WOs) in manufacturing and supply chain execution. It describes how external or internal demand recorded on a PO is tied to the manufacturing or processing steps executed under one or more WOs.

    What it includes

    In regulated and industrial environments, PO to WO linkage typically includes:

    • Identifying which work order(s) are fulfilling a specific customer or internal purchase order line.
    • Maintaining references between PO numbers, line items, and corresponding WO numbers in ERP, MES, or planning systems.
    • Ensuring that production status, quality results, and shipment details on a WO can be traced back to the originating PO.
    • Supporting multi-level relationships, such as one PO being fulfilled by multiple WOs or one WO serving multiple PO lines, where the system allows it.

    This linkage can exist:

    • Within a single company, connecting customer sales orders and internal production WOs.
    • Across organizational boundaries, where an OEM’s PO is linked to a supplier’s internal WOs for that part or assembly.

    Operational meaning

    Operationally, PO to WO linkage affects how work is planned, executed, and monitored:

    • Planning and MRP: MRP systems use POs (customer demand or intercompany demand) to generate or adjust WOs and purchase requisitions. Linkage provides clear traceability from demand to production.
    • Supplier orchestration: OEMs and Tier 1 suppliers often want visibility into which WOs at a critical supplier correspond to their POs, so they can track real-time status, risks, and readiness to ship.
    • Quality and traceability: Non-conformances, inspections, and deviations logged at the WO level can be associated with the relevant PO, supporting customer notifications, containment actions, and record-keeping.
    • Logistics and ASN: When shipments are prepared, the advanced ship notice (ASN) and packing information often reference both the PO and the WO(s) that produced the shipped items.
    • Costing and performance: Costs and schedule adherence captured at the WO level can be rolled up and analyzed in the context of the PO, customer, or program.

    How it shows up in systems

    Different systems model PO to WO linkage in various ways:

    • ERP: Commonly stores the primary reference between sales orders or purchase orders and the work orders that were created to fulfill them. This may appear as direct links in order tables or via allocation records.
    • MES: Often references an ERP WO as the execution object, while keeping the PO number available for context, dashboards, labels, and traceability reports.
    • Supplier portals: May allow mapping between an OEM PO and the supplier’s internal WOs for status updates, commit dates, and change management.

    In practice, PO to WO linkage can be:

    • One-to-one: A single PO line drives a single WO.
    • One-to-many: A PO line is split across several WOs (for capacity, batch size, or site reasons).
    • Many-to-one: Multiple PO lines or releases are produced on shared WOs, which requires careful allocation and traceability rules.

    Use in multi-tier supply and critical suppliers

    For OEMs working with critical or regulated suppliers, PO to WO linkage is a foundation for multi-tier visibility. When suppliers expose limited but standardized status signals tied to both the OEM PO and their internal WO, OEMs can monitor:

    • Whether work has been started or is queued.
    • Current operation status or hold conditions on the WO.
    • Completion, inspection, and shipment readiness for PO positions.

    This can be implemented through lightweight connections into supplier ERP/MES, shared portals, or structured status files, without requiring full real-time system integration.

    Common confusion

    • PO to WO linkage vs. ATP/CTP: Available-to-promise (ATP) and capable-to-promise (CTP) are planning concepts that may use POs and WOs, but they are not themselves the linkage. PO to WO linkage is the underlying reference structure.
    • PO to WO linkage vs. lot/batch traceability: Lot or batch traceability follows material across many orders and operations. PO to WO linkage is specifically about relating commercial or internal demand records (POs) to the work orders executing that demand.
    • PO vs. work order: A PO is a commercial, purchasing, or customer order document. A work order is an internal execution object that instructs operations or a supplier process on what to build or process.

    When PO to WO linkage is important

    PO to WO linkage is especially important when:

    • Customers require clear traceability from deliveries back to orders and manufacturing records.
    • Suppliers must manage complex programs with many engineering changes and part revisions.
    • Plants run high-mix, low-volume work where shared resources serve multiple orders.
    • Auditability, conformance documentation, and evidence of correct fulfillment are required.

  • Corporate calendar

    A corporate calendar is the organization-wide schedule used to define and communicate important business dates, time periods, and planned events. In industrial and manufacturing environments, it commonly includes fiscal periods, plant schedules, shutdowns, holidays, inventory events, audit windows, training dates, maintenance periods, and other milestones that affect operations, staffing, reporting, or system activity.

    The term usually refers to a shared planning structure rather than a personal meeting calendar. It provides a common time reference for departments such as production, quality, maintenance, supply chain, finance, and IT. In practice, corporate calendars may be managed in ERP, MES, HR, EAM, scheduling, or collaboration systems, depending on the type of event being tracked.

    What it includes

    • Company holidays and non-working days
    • Fiscal months, quarters, and year-end periods
    • Planned plant shutdowns and maintenance windows
    • Cycle count, inventory, or physical stocktake dates
    • Quality, audit, or compliance-related milestones
    • Training, reporting, and governance deadlines

    A corporate calendar does not usually mean the detailed production schedule for specific work orders, machines, or operators, although those schedules may depend on it.

    Operational meaning

    In operations, the corporate calendar acts as a timing framework that other workflows reference. For example, a plant shutdown on the corporate calendar may affect production planning in ERP, preventive maintenance timing in EAM, labor availability in HR systems, and reporting cutoffs for quality or finance. Some systems use calendar definitions directly to calculate available capacity, period-based KPIs, or transaction posting dates.

    Common confusion

    Corporate calendar vs. production schedule: A corporate calendar sets shared business dates and constraints. A production schedule assigns jobs, resources, and timing for manufacturing execution.

    Corporate calendar vs. fiscal calendar: A fiscal calendar is often one part of the broader corporate calendar. The corporate calendar may also include operational, maintenance, and administrative events.

    Corporate calendar vs. personal calendar: A personal calendar manages individual meetings and tasks. A corporate calendar defines organization-level dates that many teams or systems may use.

  • bill of material

    Core meaning

    A **bill of material (BOM)** is a structured list of all items required to build a specific product, assembly, or configuration. It typically includes:

    – Each component, subassembly, and raw material
    – Required quantities and units of measure
    – Hierarchical relationships between parent and child items
    – Identifiers such as part numbers, revisions, and descriptions

    In industrial and regulated manufacturing, the BOM acts as a central product data structure linking engineering, planning, procurement, manufacturing, and quality records.

    Typical BOM types in manufacturing

    Common forms of BOMs include:

    – **Engineering BOM (EBOM)**: Derived from product design; represents how the product is engineered (often managed in CAD/PLM). Focuses on design-valid parts and revisions.
    – **Manufacturing BOM (MBOM)**: Structured for how the product is built on the shop floor, often re-grouped by operations, work centers, or kits. Used by MES and ERP for planning and execution.
    – **Service or maintenance BOM**: Represents the as-designed or as-maintained structure of an asset in the field, supporting spare parts and service operations.
    – **Configurable or variant BOM**: Parameterized structure that supports multiple product options and variants from a common base design.

    A single product may have multiple BOM views that must be synchronized through change control.

    Use in industrial and regulated environments

    In operational workflows, a BOM commonly:

    – Drives **material planning and purchasing** in ERP/MRP systems
    – Defines **what materials MES expects** at each operation or work center
    – Supports **traceability**, by identifying which parts and lots can be used in a given product and revision
    – Provides the **reference structure** for work instructions, routings, and quality plans
    – Serves as a basis for **costing** (material cost roll-ups) and variance analysis

    In regulated industries (such as aerospace, pharma, or medical devices), BOMs are tightly controlled and linked to formal change processes, approved suppliers, and documented specifications.

    Boundaries and exclusions

    A bill of material:

    – **Includes**: Physical components, subassemblies, raw materials, consumables, and sometimes shop-replaceable units that are required to realize the product.
    – **May include** (depending on practice): Non-stock items like labels, documentation, or tooling references if they are required to deliver the defined product.
    – **Does not inherently include**: Process routing, operation sequence, cycle times, or work instructions. These are typically managed in routings, process plans, or MES master data, even when displayed together with BOM information.

    It also does not by itself represent inventory on hand or location; that information usually resides in inventory and warehouse management functions that reference the BOM.

    Common confusion and related terms

    – **BOM vs. routing**: A BOM defines *what* materials are needed; a routing defines *how* and *in what sequence* operations are performed. Many systems link these but store them separately.
    – **BOM vs. product structure**: In some tools these terms overlap. “Product structure” may describe higher-level configuration relationships, whereas the BOM is the operational list used for planning and execution.
    – **BOM vs. recipe/formula**: In process industries, a recipe or formula serves a similar role but typically includes more detailed process parameters (temperatures, times, etc.), not just material lists.

    Site context: BOMs and inventory accuracy

    In environments such as aerospace manufacturing, BOM quality and control strongly influence inventory accuracy and traceability:

    – Incorrect or outdated BOMs can lead to **over-issues or under-issues** of components versus what is planned in ERP or MES.
    – Poor alignment between EBOM and MBOM can drive **workarounds on the shop floor**, such as substituting parts or adding unplanned hardware without recorded changes.
    – Incomplete handling of **kits, alternates, and substitutes** in BOM data can cause mismatches between system inventory and actual consumed parts.

    For these reasons, BOM management is typically integrated with change control, configuration management, and cross-system synchronization between PLM, ERP, and MES.

  • Standard cost

    Standard cost commonly refers to a pre-determined, expected cost per unit of product or activity, defined in advance for materials, labor, and overhead. It is used in manufacturing and other industrial operations as a stable reference for planning, inventory valuation, and variance analysis, rather than as a record of actual costs incurred.

    What standard cost includes

    In a typical manufacturing environment, a standard cost may be broken down into:

    • Standard material cost: Expected quantity and price of raw and component materials per unit.
    • Standard labor cost: Expected time and rate per operation, work center, or unit.
    • Standard overhead cost: Allocated factory overhead (e.g., equipment, utilities, indirect labor) per unit, often based on standard machine or labor hours.

    These standards are usually maintained in ERP/MRP or cost accounting systems and may be referenced by MES or production systems for reporting and integration.

    Operational role in manufacturing systems

    Standard cost is used to:

    • Value inventory in ERP/MRP, including raw materials, work in process, and finished goods.
    • Price internal transactions, such as transfers between plants, production orders, or cost centers.
    • Support variance analysis by comparing actual costs, scrap, rework, or yield losses against the standard.
    • Enable planning and budgeting of product margins, capacity, and cost of goods manufactured.

    In regulated or audit-sensitive environments, the way standard costs are defined, updated, and applied is often documented and controlled so that cost calculations remain traceable and reproducible.

    Standard cost and non-conformance handling

    When non-conforming material is identified, decisions such as use-as-is, rework, scrap, or return-to-vendor affect how inventory is classified and valued against its standard cost. Quality systems (QMS), MES, and ERP/MRP must be aligned so that:

    • Inventory status changes (e.g., from available to blocked or scrap) are reflected at the correct standard cost.
    • Cost differences, such as rework effort or scrap write-offs, are captured as variances from the standard.
    • Resulting cost movements remain traceable for financial and quality audits.

    Standard cost vs actual cost

    Standard cost is often contrasted with actual cost:

    • Standard cost: A fixed, pre-set benchmark that remains stable over a period.
    • Actual cost: The real, measured cost incurred for materials, labor, and overhead during production.

    The difference between actual and standard costs is recorded as a cost variance, which can be analyzed by product, order, work center, or time period to understand process performance and cost drivers.

    Common confusion

    • Standard cost vs list price: Standard cost is an internal costing benchmark, not a sales or transfer price, although it may be used as an input to pricing decisions.
    • Standard cost vs budget: Budgets aggregate expected costs over periods or projects, while standard cost is usually defined per unit or activity and applied transaction by transaction.