{"id":45004,"date":"2026-06-17T13:16:49","date_gmt":"2026-06-17T07:46:49","guid":{"rendered":"https:\/\/www.verdantis.com\/?p=45004"},"modified":"2026-06-26T20:53:01","modified_gmt":"2026-06-26T15:23:01","slug":"erfassung-von-ersatzteilen","status":"publish","type":"post","link":"https:\/\/www.verdantis.com\/de\/erfassung-von-ersatzteilen\/","title":{"rendered":"Was ein Ersatzteil-Tracker eigentlich leistet"},"content":{"rendered":"
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

A spare parts tracker is the system, software combined with process and discipline, that records every inventory transaction and displays real-time stock positions across a storeroom.<\/p>\n

It is the execution layer of operational inventory control<\/a>: the mechanism that converts physical storeroom activity into queryable, auditable data.<\/p>\n

The distinction between tracking and strategy is technical, not semantic. A tracker answers operational questions: how many units are in stock, in which bin, who moved them, and when.<\/p>\n

It does not answer strategic questions: how much should we hold, which parts are critical, or what to do with parts approaching obsolescence. Conflating the two is a primary reason tracking implementations underdeliver.<\/p>\n

World-class inventory accuracy in MRO storerooms sits at [[NEEDS FIGURE: cite APICS or EAM benchmark for 95-98% target]].<\/p>\n

Most unmanaged storerooms operate at a significantly lower rate. The gap is not a software gap. It is a transaction discipline gap and an item master quality gap.<\/p>\n

This article covers the technical anatomy of a spare parts tracker: what it records, how it fails, how accuracy is measured correctly, and what to look for in a purpose-built system.<\/p>\n

Two original frameworks are introduced: the Spare Parts Tracking Maturity Stack and the Transaction Completeness KPI, which is distinct from inventory accuracy in both what it measures and what it diagnoses.<\/p><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

Was ein Ersatzteil-Tracker eigentlich leistet<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

A spare parts tracker exists on a spectrum from informal to purpose-built. The type of system an operation runs determines the transaction gaps it will accumulate and the accuracy ceiling it can realistically reach.<\/p>\n

Three distinct system types are common across industrial operations. Each carries a different set of structural limitations.<\/p><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t
Spreadsheet Tracker<\/div>
  • Manual, point-in-time snapshot<\/li>
  • No real-time transaction recording<\/li>
  • No multi-user concurrency<\/li>
  • No work order linkage<\/li>
  • Accuracy degrades as transaction volume grows<\/li><\/ul><\/div>
    CMMS \/ ERP Module<\/div>
    • Designed for maintenance scheduling<\/li>
    • Inventory is a secondary function<\/li>
    • Bin-level tracking often absent<\/li>
    • Physical count reconciliation limited<\/li>
    • Storeroom-centric features secondary<\/li><\/ul><\/div>
      Dedicated Tracking System<\/div>
      • Built around inventory transactions first<\/li>
      • Bin-level and serial\/batch tracking<\/li>
      • Full movement type discipline<\/li>
      • Real-time multi-user recording<\/li>
      • Native CMMS and ERP integration<\/li><\/ul><\/div><\/div>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
        \n\t\t\t\t
        \n\t\t\t\t
        \n\t\t\t\t\t\t\t\t\t

        A spreadsheet tracker is not a tracking system in the transactional sense. It is a snapshot tool that cannot record the reason a part moved, link a movement to a work order, or prevent concurrent overwrites.<\/p>\n

        A CMMS or ERP inventory module is meaningfully better, but it was designed around maintenance scheduling, not storeroom operations.<\/p>\n

        Bin-level tracking, physical count reconciliation, and scan-at-movement workflows are typically absent or require significant custom configuration.<\/p>\n

        A purpose-built spare parts tracking system is designed with the storeroom as the primary user, and every function reflects that priority from the ground up.<\/p><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

        \n\t\t\t\t
        \n\t\t\t\t
        \n\t\t\t\t\t

        The Spare Parts Tracking Maturity Stack<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
        \n\t\t\t\t
        \n\t\t\t\t
        \n\t\t\t\t\t\t\t\t\t

        Most discussions of spare parts tracking treat it as binary: either you are tracking or you are not. In practice, tracking exists across four distinct layers of maturity.<\/p>\n

        Each layer builds on the previous and requires incrementally more sophisticated technology and process discipline.<\/p>\n

        The Spare Parts Tracking Maturity Stack provides a diagnostic framework for understanding where an operation currently sits and what investment is required to advance.<\/p><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

        \n\t\t\t\t
        \n\t\t\t\t
        \n\t\t\t\t\t
        The Spare Parts Tracking Maturity Stack<\/div>
        Ebene<\/th>What it tracks<\/th>Technology required<\/th>Was es erm\u00f6glicht<\/th><\/tr><\/thead>
        4<\/span>Condition<\/strong><\/td>Serviceability status of each individual unit<\/td>Condition tags, quality management integration<\/td>Condition-based issue rules; blocks degraded stock from entering production<\/td><\/tr>
        3<\/span>Identity<\/strong><\/td>Which specific unit: serial number or lot\/batch<\/td>Serial and lot tracking in CMMS or ERP<\/td>Full traceability of every unit from goods receipt to consumption<\/td><\/tr>
        2<\/span>Standort<\/strong><\/td>Which storeroom and which bin<\/td>Bin management, barcoding, location master data<\/td>Precise part findability; eliminates search time for confirmed in-stock parts<\/td><\/tr>
        1<\/span>Menge<\/strong><\/td>How many units are in stock<\/td>Basic CMMS or ERP inventory module<\/td>Basic stock visibility; enables reorder triggers on quantity thresholds<\/td><\/tr><\/tbody><\/table>
        Most industrial operations run at Layer 1 or Layer 2. Reaching Layer 3 requires serial\/lot configuration. Layer 4 requires a condition management workflow and quality system integration.<\/div><\/div>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
        \n\t\t\t\t
        \n\t\t\t\t
        \n\t\t\t\t\t\t\t\t\t

        Layer 1 is the starting point for most operations. A CMMS or ERP module tracks quantity: how many units of a given part exist across the storeroom.<\/p>\n

        This enables basic reorder triggers but cannot tell a technician which bin to look in or confirm which specific unit was used in a repair.<\/p>\n

        Layer 2 requires a location master, bin labeling, and barcode scanning at the point of movement. It is the single highest-leverage investment available to operations currently at Layer 1.<\/p>\n

        Moving from Layer 1 to Layer 2 eliminates the lag between physical movement and system recording, which is the primary driver of inventory inaccuracy.<\/p>\n

        Layers 3 and 4 address traceability and serviceability respectively. Layer 3 is relevant for rotating equipment, pressure vessels, and parts subject to regulatory traceability requirements.<\/p>\n

        Layer 4 supports condition-based maintenance strategies where parts must be inspected and condition-tagged before re-issue to production-critical assets.<\/p><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

        \n\t\t\t\t
        \n\t\t\t\t
        \n\t\t\t\t\t

        The Anatomy of an Inventory Transaction<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
        \n\t\t\t\t
        \n\t\t\t\t
        \n\t\t\t\t\t\t\t\t\t

        Every inventory transaction is a structured record. Understanding what each transaction captures, and what each field contributes to analytics, is the technical foundation of tracking integrity.<\/p>\n

        A tracker that captures quantity and timestamp but not movement type or reference document is not producing a complete audit record.<\/p><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

        \n\t\t\t\t
        \n\t\t\t\t
        \n\t\t\t\t\t
        Every inventory transaction records eight fields<\/div>
        01<\/div>
        Part number<\/div>
        Material master reference<\/div><\/div>
        02<\/div>
        Menge<\/div>
        Units moved, in defined UOM<\/div><\/div>
        03<\/div>
        Movement type<\/div>
        Coded reason for the movement<\/div><\/div>
        04<\/div>
        Storage location<\/div>
        Storeroom and bin<\/div><\/div>
        05<\/div>
        Timestamp<\/div>
        Date and time of posting<\/div><\/div>
        06<\/div>
        User ID<\/div>
        Who executed the transaction<\/div><\/div>
        07<\/div>
        Reference document<\/div>
        PO number or work order<\/div><\/div>
        08<\/div>
        Batch \/ serial<\/div>
        Where serial or lot tracking is active<\/div><\/div><\/div><\/div>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
        \n\t\t\t\t
        \n\t\t\t\t
        \n\t\t\t\t\t\t\t\t\t

        Of these eight fields, movement type carries the most analytical weight. Part number and quantity tell the system what moved and how much. Movement type tells the system why it moved.<\/p>\n

        Why it moved determines how the transaction is interpreted in every downstream process: cost allocation, demand history, asset maintenance cost tracking, and inventory valuation.<\/p>\n

        Movement type discipline is not a systems configuration question. It is a process governance question.<\/p>\n

        Without clear rules about which movement type to use for each physical scenario, the transaction records become analytically unreliable even when numerically correct on quantity.<\/p><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

        \n\t\t\t\t
        \n\t\t\t\t
        \n\t\t\t\t\t

        Movement Type Taxonomy: The Backbone of Tracking Integrity<\/h3>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
        \n\t\t\t\t
        \n\t\t\t\t
        \n\t\t\t\t\t\t\t\t\t

        The following movement types cover the most consequential scenarios in an MRO storeroom.<\/p>\n

        The SAP codes are illustrative of a movement type discipline that applies in equivalent form across Oracle, Maximo, and any ERP or CMMS that distinguishes between transaction types.<\/p><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

        \n\t\t\t\t
        \n\t\t\t\t
        \n\t\t\t\t\t
        Movement type taxonomy: SAP reference, applicable to all ERP platforms<\/div>
        MT<\/th>Name<\/th>What it records<\/th>If misused, it corrupts<\/th><\/tr><\/thead>
        101<\/td>Goods receipt vs. PO<\/td>Stock arriving against a purchase order<\/td>On-hand count; inflates inventory immediately on GR error<\/td><\/tr>
        261<\/td>Goods issue to work order<\/td>Consumption against a specific maintenance job<\/td>Per-asset cost history and demand forecast (if MT 201 is used instead)<\/td><\/tr>
        311<\/td>Transfer posting<\/td>Stock moved between storage locations or plants<\/td>Location accuracy; omitting MT 312 return creates dual-count ghost stock<\/td><\/tr>
        551<\/td>Scrapping<\/td>Writing off damaged, expired, or obsolete stock<\/td>Inventory valuation; using MT 261 for scrap incorrectly charges a work order<\/td><\/tr>
        201<\/td>Goods issue to cost center<\/td>Overhead consumption charged to a cost center<\/td>Maintenance cost per asset when used in place of MT 261<\/td><\/tr><\/tbody><\/table>
        Movement type is the field that differentiates consumption from scrapping from transfer. All three reduce stock by the same quantity but mean completely different things to cost allocation, demand history, and asset analytics.<\/div><\/div>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
        \n\t\t\t\t
        \n\t\t\t\t
        \n\t\t\t\t\t\t\t\t\t

        The consequence of movement type misuse is invisible in real time and becomes visible only when analytics are run.<\/p>\n

        A work order cost report that understates maintenance costs per asset, a demand forecast that overestimates consumption because overhead issues were coded as work order issues: these compound silently.<\/p>\n

        Correcting movement type misuse after the fact requires a data remediation exercise on historical transactions.<\/p>\n

        Preventing it requires clear process rules, staff training, and system-enforced validation logic at the point of posting.<\/p><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

        \n\t\t
        \n\t\t
        \n\t\t\t\t
        \n\t\t\t\t
        \n\t\t\t\t\tSee What Transaction Discipline Looks Like Across Your Storeroom Data<\/span>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
        \n\t\t\t\t
        \n\t\t\t\t\t

        Verdantis MRO360 delivers AI-native spare parts intelligence built on clean transaction data and item master quality. Deployed in 8 to 12 weeks across Fortune 500 operations in Oil and Gas, Mining, and Manufacturing.<\/p><\/span>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

        \n\t\t\t\t
        \n\t\t\t\t
        \n\t\t\t\t\t\t\t
        \n\t\t\t\t\t
        \n\t\t\t\t
        \n\t\t\t\t
        \n\t\t\t\t
        \n\t\t\t\t\t\t\t
        \n\t\t\t\n\t\t\t\n\t\t\t\n\n\t\t\t\t\t\t\t\n\t\t\t\n\t\t\t
        \n\t\t\t\t\t\t\t\t
        \n\t\t\t\t\t\t\t\t\t\t\t\t