Based in Billings, Montana, NorthForge Heavy Equipment Rebuilders specializes in the refurbishment and rebuild of large excavators, all-terrain and rough-terrain cranes, and front loaders and haul trucks used in mining and heavy construction. Their model combines a central rebuild shop equipped for full teardown, machining, structural welding, and final assembly with a field service team that travels to mines, quarries, and large infrastructure projects for diagnostics, partial repairs, and post-delivery support.

Every project is unique. Some customers buy used machinery and ask for a full like-new refurbishment. Others want focused repair on undercarriage, hydraulic systems, or structural components, with clear warranty terms, full parts traceability, and a transparent total cost of ownership. The expertise on the shop floor was never in doubt. The problem was the financial and operational infrastructure around it.

NorthForge's mechanics knew how to strip and rebuild an excavator to the last bolt. The problem was everything around the physical work: the quoting, the parts tracking, the hour attribution, and the financial picture that only assembled clearly after the fact, if at all.

Unknown scope until teardown. Every refurb started with an estimate built on photos, partial history, and a surface inspection. The real BOM, what actually needed replacing versus what could be reconditioned versus what was failing inside, only became clear once the machine was open. Quotes were built on assumptions that teardown regularly contradicted. Scope changes were constant and only partially captured in any system. No structured record existed of how many hours and parts went into specific failure modes or machine types.

Parts and spares scattered across informal systems. NorthForge carried substantial inventory of reconditioned hydraulic pumps, cylinders, axles, seal kits, critical hardware, and electronic components. The true picture of stock lived in a basic shelf system, the memory of the warehouse manager, and several spreadsheets that were not connected to active projects. Mid-assembly, it was common to discover incomplete kits, parts verbally reserved for another job that were no longer available, and emergency purchases made at high prices just to meet a delivery date.

Project costs that did not reflect reality. Technician hours were recorded on paper or via informal messages. Many parts were pulled from stock with no clear link to a specific project. Rework and adjustments went unrecorded. Some projects looked profitable on the invoice but quietly destroyed margin in practice. Others looked expensive to the customer but were NorthForge's best jobs when viewed through true total cost of ownership. Leadership could not tell the difference until it was too late to do anything about it.

NorthForge implemented FireFlight with a clear goal: stop surviving job by job and start running the refurb portfolio as a data-driven operation where every decision rests on real information. The deployment was built around three pillars: true job costing at the project level, inventory control centered on critical spare parts, and Asset Management to track lifecycle and total cost of ownership over time. Configuration was completed in weeks, not months.

Within a year, the operation felt different at every level. On the shop floor, technicians still focused on the physical work, but every step left a documented trail. Conversations shifted from "who grabbed that cylinder?" to "why does this type of repair consistently run over estimated hours?" That second question was not answerable before FireFlight because the data to answer it did not exist in any structured form.

In management and finance, the patterns that had been invisible inside monthly averages became visible. Specific brands, models, machine ages, and operating conditions that consistently eroded margin were identified by name. Pricing and scope adjustments on future quotes for those machine types were made from historical cost data rather than intuition.

In customer relationships, NorthForge gained the ability to explain exactly why a refurb costs what it does: teardown findings, decisions made during the process, parts installed, test results documented. Some customers began using FireFlight's reports internally to justify their own refurb investment versus buying new decisions to their leadership teams.

The BOM problem in heavy equipment refurbishment is not a systems problem. It is a structural reality of the work: the scope of a refurb reveals itself during teardown, not before it. Any system that requires a fixed BOM before work begins will either produce inaccurate quotes or create an incentive to under-scope to win the job and then absorb overruns. FireFlight's teardown workflow builds the BOM from actual findings rather than assumptions, which aligns the documentation system with how heavy equipment refurbishment actually works.

Deployments for heavy equipment refurb and rebuild operations covering project work orders, teardown workflow documentation, spare parts inventory linked to active projects, real-time job costing, and asset lifecycle tracking are completed in weeks, not months. The configuration built for NorthForge applies directly to any operation managing complex, unique rebuild projects where scope discovery happens during the work rather than before it starts.

For a business dealing in rare books and manuscripts, the documentation of each item is inseparable from its value. A manuscript with a documented provenance connecting it to a specific historical collection or notable previous owner is worth considerably more than the same physical object without that paper trail. Antiqua Books knew this. The problem was that the documentation itself was scattered: acquisition details in email threads, previous ownership records in paper files, condition notes in spreadsheets that different staff members updated without a shared format.

The restoration process added a second layer of fragmentation. Conserving a rare book often requires specialists handling different elements of the same item: pages, bindings, covers, illuminations, and conservation materials each managed by different hands. Each specialist tracked their own work informally. There was no single record connecting the sequence of restoration steps, the time spent, or the materials consumed to the specific item they belonged to. By the time a book was ready for sale, reconstructing the complete restoration cost required pulling from multiple sources, and some costs were never captured at all.

Internationally, items moved between storage facilities, galleries, and exhibitions with shipping and exhibition records managed in separate systems. In 2026, a collector conducting due diligence on a high-value acquisition expects a complete exhibition and custody history. That history was not in a single place at Antiqua Books. It existed in fragments across booking confirmations, insurance filings, and shipping manifests that required manual assembly every time a client asked.

The deployment covered provenance and acquisition record management for every item in inventory, multi-step restoration workflow tracking with cost attribution per stage, real-time location tracking across storage, galleries, and international exhibitions, per-item financial consolidation from acquisition through restoration to sale, and exhibition and shipping history logging. Configuration was completed in weeks, not months. Existing inventory and acquisition records were migrated during the deployment so the full history was in the system from day one.

The most immediate change was the documentation response time for collector inquiries. A potential buyer asking for the complete provenance, restoration history, and exhibition record of a specific item had previously triggered a manual assembly process that could take days. With FireFlight, that record was current and accessible in a single system. The collector got a complete, documented history rather than a compiled summary with gaps where records were missing or inconsistent.

Restoration cost tracking moved from reconstruction after the fact to accumulation in real time. Specialists logged their work and materials as each stage was completed. By the time a book was ready for sale, the total cost figure was confirmed and current, not estimated from memory or averaged across similar items. Pricing decisions for the first time reflected what each specific book had actually cost to bring to market.

In the rare book and manuscript trade, the documentation of an item's history is not secondary to the item itself. It is part of the item's value. A manuscript with a complete, verifiable provenance connecting it to a documented historical collection commands a different price than an identical physical object whose ownership chain has gaps. FireFlight's provenance tracking preserves that value by keeping the record current, complete, and accessible at every stage of the item's time in Antiqua Books' inventory.

The second confirmed insight from this deployment: documentation that exists in informal systems is documentation that exists only as long as the people who maintain it remain accessible. For a business where the records are as valuable as the inventory, that is not an acceptable risk. FireFlight moved Antiqua Books' item documentation from personal knowledge and individual files into a structured record that will be there for the next transaction regardless of who handles it.

Deployments for rare item dealers covering provenance tracking, restoration workflow management, global location visibility, and per-item financial consolidation are completed in weeks, not months. The configuration built for Antiqua Books applies directly to any business managing unique, high-value items through acquisition, restoration, and sale across international locations.