How to Separate Replacement, Expansion, Retrofit, and New-Build ICPs

Who this framework is for

This framework is for equipment, component, controls, service, and retrofit suppliers whose offer can enter an account through more than one capital or maintenance context. It is useful for manufacturers and exporters deciding which account evidence, value case, and buying route to use.

Contents

1 Define the four change contexts 2 Use the baseline and change test 3 Compare fit, evidence, and buying conditions 4 Handle mixed and ambiguous projects 5 Apply the SellersGPT Project-Context Record 6 Illustrative example 7 Common mistakes 8 What this does not mean 9 Common questions 10 Sources and methodology

1. Define the four change contexts

Use operational definitions for ICP work: Replacement An existing asset or function is removed, renewed, or substituted to restore or preserve an established operating requirement. Capacity may change incidentally, but restoration is the primary objective. Expansion The facility or enterprise adds measurable output, throughput, storage, service, or operating capacity relative to a stated baseline. Expansion may add equipment inside an existing site or create another line or facility. Retrofit An existing asset or system is modified, integrated, upgraded, or adapted while meaningful parts of the installed system remain. Compatibility, shutdown, interface, and validation conditions are central. New build A new facility, line, system, or operating asset is designed and constructed without the same installed-system constraint at the defined boundary. A new build can still reuse corporate standards or existing infrastructure. These are SellersGPT editorial definitions for segmentation, not accounting or legal definitions. The Census Bureau explains that ACES historically covered business spending for new and used structures and equipment and has transitioned to the Annual Integrated Economic Survey. U.S. Census Bureau - About ACES Aggregate capital expenditure can indicate investment context by industry, but cannot classify a named project for you.

2. Use the baseline and change test

Ask seven questions in order: 1 What asset, line, function, or facility exists today? 2 What will remain after the project? 3 What will be removed or replaced? 4 What new capacity or capability will be added? 5 Which existing interfaces constrain the design? 6 What is the project's current evidence state? 7 Who specifies, purchases, installs, and accepts each work package? Context Existing baseline Primary change Design freedom Typical hard question Replacement Existing function Restore or substitute Limited to moderate Can the substitute meet existing interfaces? Expansion Existing capacity Add capacity Moderate What capacity denominator and increment apply? Retrofit Existing system retained Modify or integrate Constrained Can old and new systems work safely together? New build No equivalent asset at boundary Create operating asset Higher, not unlimited Is the project sufficiently defined and funded? Do not classify from words such as “modernization” alone. A modernization program may contain all four contexts.

3. Compare fit, evidence, and buying conditions

Replacement ICP Evidence includes installed asset, failure or obsolescence exposure, maintenance policy, compatibility, and replacement trigger. Age is not intent. Buying may be maintenance-led, centralized, distributor-supported, or emergency. Expansion ICP Require baseline capacity, capacity increment, application, facility readiness, supporting utilities, and project status. The calculation must retain units: capacity increase rate = added rated capacity / current rated capacity Rated capacity is not actual output or demand. Retrofit ICP Prioritize interface inventory, existing controls, physical constraints, shutdown access, validation, responsibility, and brownfield risk. Retrofit may offer a strong value case but high delivery uncertainty. New-build ICP Verify owner, site, design stage, intended output, engineering route, procurement packaging, schedule, approvals, and funding evidence. More design freedom can improve technical fit, while long timelines and changing specifications weaken near-term certainty. The Census Value of Construction Put in Place survey covers construction work on new structures and improvements to existing structures for private and public sectors. U.S. Census Bureau - Construction Spending Its monthly estimates describe economic activity, not an account list or buying-intent feed. BEA fixed-assets statistics provide investment, stock, and depreciation by asset type. U.S. Bureau of Economic Analysis - Fixed Assets by Type Use them only for contextual analysis with their published scope; named-project classification requires project evidence.

4. Handle mixed and ambiguous projects

Large projects should be decomposed into work packages. A fictional plant modernization could include:

• replacement of legacy drives;

• retrofit of controls to retained motors;

• expansion through a second line;

• a new-build utility building. Create one parent project record and linked work-package records. Each gets its own application, context, specifications, stakeholders, schedule, evidence, and risk. Do not force the whole program into one label. Use Unknown when public evidence states only “investment” or “upgrade.” Record competing hypotheses and the next validation action. Preserve project state independently from context. A verified retrofit concept may still be only an announced study; a replacement may already be in procurement; a new build may be paused after site work. Suggested states are Hypothesis, Announced, Design, Procurement, Execution, Complete, Paused, Cancelled, and Unknown. These labels organize research and do not guarantee that a seller can participate. Lifecycle information must remain traceable as configurations change. NIST research describes the need to contextualize product and process data across manufacturing lifecycle stages for decision-making. NIST - Contextualizing Manufacturing Data for Lifecycle Decision Making The practical ICP implication is to version the baseline and avoid applying old project facts to the current system.

5. Apply the SellersGPT Project-Context Record

The Project-Context Record is an original SellersGPT tool. Field Required entry Account and site Legal entity, parent, facility, address Application Operating job and critical conditions Baseline Existing asset, system, capacity, evidence date Context Replacement, expansion, retrofit, new build, mixed, or Unknown Change scope Remove, retain, modify, or add Trigger Condition, project, tender, direct discovery, or Unknown Stage Hypothesis, announced, design, procurement, execution, complete Buying route End user, OEM, distributor, contractor, or mixed Hard gates Compatibility, service, authorization, schedule, risk Next action Specific validation and owner Decision rules:

• Go: context, application, route, and gates are verified enough to act.

• Test: one bounded critical assumption needs validation.

• Monitor: durable fit exists but no active project evidence.

• Hold: baseline, context, or route remains materially Unknown.

• Exclude: verified incompatibility or prohibited condition.

6. Illustrative example

Illustrative example. The site, assets, capacities, and decisions below are fictional. They do not represent a customer, forecast, or market estimate. A packaging supplier reviews a plant program with three work packages: Work package Baseline and change Context Decision A Replace 10 legacy drives one for one Replacement Go after interface check B Retain conveyors; add controls and sensors Retrofit Test pending protocol validation C Add a line rated at 40 units/minute to current rated Expansion Hold pending project stage The expansion rate is 40 / 100 = 40% of current rated capacity. It does not mean plant output, sales, or demand will rise 40%. The supplier counts ten replacement units only because the one-for-one scope is fictional and explicit. It does not count the retrofit sensors until drawings identify quantities. The parent program is Mixed; each work package keeps its own route and stakeholders.

7. Common mistakes

Calling every older asset a replacement lead Require timing evidence and compatibility. Age creates exposure, not a project. Treating every capital announcement as new build Read what is retained, modified, removed, and added. Using construction spending as an account list Aggregate statistics provide context, not named projects or intent. Mixing rated capacity with actual production Keep the denominator, unit, period, and utilization concept explicit. Ignoring brownfield interfaces Retrofit and replacement fit can fail on controls, footprint, utilities, validation, or shutdown. Giving a mixed project one buying path Different work packages may be specified and purchased by different parties.

8. What this does not mean

• The four ICPs are not accounting, engineering, or legal classifications.

• Project announcements do not prove procurement status or supplier access.

• Capital spending does not predict leads, opportunities, or revenue.

• Replacement, expansion, retrofit, and new build can coexist.

• This framework does not replace qualified project, technical, or contract review.

9. Common questions

Is adding a second identical machine replacement or expansion? Expansion, if it adds capacity while the first remains. If the new machine replaces the first, it is replacement. Verify the baseline. Is software added to an existing line a retrofit? Usually under this editorial framework if it changes the retained system. Define the asset boundary and interfaces. When should an announced project enter outreach? When the message can accurately reflect public scope and there is a viable application and route. Announcement alone does not prove a supplier-selection window. Should these contexts have separate messaging? Yes. The operating objective, evidence, risk, and value mechanism differ. Keep claims bounded to the verified context.

10. Sources and methodology

Sources 1 U.S. Census Bureau - About the Annual Capital Expenditures Survey. Used for historical ACES scope and its transition to the Annual Integrated Economic Survey. Accessed August 24, 2026. 2 U.S. Census Bureau - Construction Spending. Used for the official Value of Construction Put in Place scope covering new structures and improvements. Accessed August 24, 2026. 3 U.S. Bureau of Economic Analysis - Fixed Assets by Type. Used for the scope of investment, net-stock, depreciation, and asset-type statistics. Accessed August 24, 2026. 4 NIST - Contextualizing Manufacturing Data for Lifecycle Decision Making. Used for the role of contextualized product and process data across the lifecycle. Accessed August 24, 2026. SellersGPT analysis and framework The four context definitions, Project-Context Record, work-package method, and decisions are SellersGPT editorial tools. Aggregate sources are used only for context and do not validate named projects. Update policy Review when cited statistical programs change. Version every project baseline, scope, stage, route, trigger, and interface as new evidence arrives.