Change detection: spotting new installations early

What makes a new installation detectable?

Change detection spots new installations early by comparing dated, usable observations of the same building or equipment position, identifying an added or replacement asset, and checking the result against project or operator records. Keep the last clear view of the old state and the first clear view of the new state. The interval between them bounds the visible change; a matched completion or startup record establishes the installation date.

The business value comes from the next decision. A new generator enclosure prompts a check of maintenance responsibility. A new rooftop cabinet prompts an equipment-register update. A new charging area prompts research into the operator and service contract. Each observation starts a specific investigation that the account team can finish.

Define what counts as an installation before looking for it. Added equipment increases the visible inventory. Replacement equipment takes over an existing position or duty. An asset first entered into your database is newly recorded, and its physical installation still needs dating. These distinctions keep a newly discovered old unit out of a campaign intended for recent projects.

Write the initial finding literally. A cabinet now occupies a previously clear curb. A new array occupies part of the roof. A concrete pad and enclosure now sit beside the loading yard. Describe what changed before assigning a brand, capacity, operating condition or commercial interpretation. The event record should survive a later correction to any of those attributes.

Start with the building and comparable evidence

Building-first prospecting means starting with the building and what is visible on it, then finding the decision maker. Give the building a stable identifier and retain the address, parcel relationships and roof or yard boundaries. A changed tenant name should update a relationship while preserving the physical history.

Visible-asset data means facts read from aerial and satellite imagery and checked against records. Record the evidence date alongside the observed feature. Fit-first lists are lists filtered to buildings that fit a company's work. Set those filters before monitoring so the team knows which additions and replacements deserve attention.

Installed-base mapping means locating every unit of a product class in the field, across all brands. Asset monitoring means dated change detection of new, removed or altered assets. Preserve the baseline inventory when adding a new observation so the change can be reconstructed by another reviewer.

Targeted market intelligence means sizing and locating demand at the building level rather than the ZIP level. For installation alerts, that means counting identifiable equipment and locating the buildings affected, then attaching the evidence needed for qualification. An asset total and an account total answer different questions.

Match the same roof section or yard position across observations. Building additions, parcel splits and changed map alignment complicate that match. Keep the physical feature's location and its unit identity separate. A replacement inherits the position relationship while retaining its own equipment record and startup history.

Which evidence establishes when installation happened?

Separate the evidence timeline from the project timeline. The image capture date tells you when the visible state was observed. The date a file became available tells you when it entered the research pipeline. The review date tells you when someone evaluated it. Retain those fields even when a project record later supplies an exact completion date.

Use the last clear observation of the old state and the first clear observation of the new state as the visible-change window. If equipment was staged before it was connected, keep the staging event separate. If the earlier view was obstructed, move the window boundary back to the last usable observation and explain the coverage gap.

A permit describes a recorded authorization or project stage. Read the status and scope before connecting it to the equipment. A permit covering a building renovation needs a location or schedule match before it supports a particular rooftop replacement. Keep canceled, revised and incomplete projects visible in the research history so a stale filing does not repeatedly reopen the same lead.

DOE describes commissioning as verification that building systems are installed and operating according to the design and engineering documentation. An overhead view establishes visible presence. A matched startup or commissioning record supplies operating evidence. Ask the operator for the relevant handoff when service responsibility, warranty timing or equipment configuration controls the next decision.

Anvilfield estimates

Anvilfield research estimates 75 incoming rooftop-unit installations annually per 1,000 mixed commercial buildings in the central case, with a range of 31 to 145.

Anvilfield research estimates 65 annual replacement installations centrally, ranging from 26 to 130, and 10 installations at newly constructed buildings, ranging from 5 to 15, in that territory. Keep those installation classes separate when assigning follow-up.

Anvilfield research estimates 53 installations found within 30 days under monthly usable observations centrally, ranging from 16 to 129. Anvilfield research estimates 18 under quarterly usable observations, ranging from 5 to 43.

Installation counts refer to incoming equipment units per 1,000 baseline commercial buildings. Group units by building before assigning account investigations. Methodology records the sources and range definitions.

How to cite this estimate: Anvilfield, Change detection: spotting new installations early, 2026, https://anvilfield.com/field-guides/market-intelligence/change-detection-spotting-new-installations-early/

How early can a change alert arrive?

Early detection depends on the next usable observation reaching a reviewer. A scheduled database refresh does not establish that a particular roof was observed again. Ask when comparable evidence will be available for the actual territory and asset class, then connect that answer to the account team's decision deadline.

Anvilfield research estimates mean detection delays of 20 days for monthly usable observations, ranging from 17 to 25; 50 days for quarterly observations, ranging from 47 to 55; and 185 days for annual observations, ranging from 182 to 190. Faster review helps after new evidence exists.

Anvilfield research estimates that monthly usable observations surface 83% of image-distinguishable installation events within 30 days centrally, ranging from 67% to 93%. Quarterly observations surface 28% centrally, ranging from 22% to 31%. Keep installation visibility, event classification and commercial qualification as separate measures.

Name the decision window before buying cadence. A service manager checking equipment handoffs needs the change routed while responsibility is being clarified. A distributor planning later maintenance supply needs an updated asset register and the right operator. A manufacturer pursuing original equipment specification needs evidence earlier in project development, before visible installed equipment appears.

When a new installation becomes visible after procurement has closed, change the conversation. Ask about startup support, maintenance responsibility, consumables, inspections and the updated equipment schedule where those fit the business. The installation alert should help the seller choose a relevant question. A building with new equipment still needs its account relationship and service scope checked.

Benchmarks for early installation alerts

Apply these Anvilfield operating benchmarks in the acceptance brief and retain the review result with the delivery.

Require 2 comparable observations before calling a visible difference a dated change. Preserve 4 separate evidence dates: the earlier capture, later capture, source availability and review. Link 2 equipment records for a simple replacement, retaining the predecessor and successor.

Release 0 automatic claims of operational acceptance from an image alone. Allow 0 duplicate alerts for the same accepted event. Assign 1 account task to each site event group, with the affected equipment listed inside it. Grouping keeps a bank of changed units from generating competing calls to the same facility.

How do you distinguish an installation from a false change?

Compare coverage before comparing equipment. A different viewing angle exposes previously hidden cabinets and changes apparent spacing. Roof screens, vegetation, shadows and temporary covers also change the visible scene. Preserve the old inventory while the comparison remains unresolved, and state the evidence needed to settle it.

Use physical relationships to test a replacement. Match the equipment position, connections, function and available equipment records. A cabinet that shifts in the image because the map alignment changed needs a location correction. Equipment removed from the roof and equipment repositioned within the site require different inventory updates.

Check construction staging. A delivered generator, cabinet or tank can appear before installation is complete. A crane or temporary enclosure explains activity without establishing the final equipment arrangement. Retain work-in-progress status until later evidence or a matched project record settles the permanent position and completion milestone.

CDC's cooling-tower identification guidance describes obscured equipment, look-alikes and outdated records as practical search problems. Use that lesson across asset classes: a changed fan outline needs classification review, and an apparent disappearance needs a coverage check. Give the reviewer access to the larger roof or yard so a tightly cropped candidate does not hide the explanation.

Sample sites with no reported change as well as flagged candidates. Candidate review measures whether issued alerts describe real changes. Coverage review investigates changes the process failed to flag. Preserve each result under the site identifier so the team can improve both the event classifier and the usable-observation coverage.

Worked example: a regional HVAC service company

A regional HVAC service company organizes a mixed commercial territory around 1,000 baseline buildings. The central Anvilfield case maps about 325 rooftop-cooled buildings carrying 975 units. The operations manager keeps equipment identity, building identity and account responsibility in separate fields so a replacement updates the register without creating a duplicate property.

The annual incoming flow is about 75 units: 65 replacements and 10 units at newly constructed buildings. New construction enters through the territory's building-discovery process. Replacements enter through comparison with known equipment positions. The company keeps those queues connected to the same building register and sends both through evidence review.

About 63 annual installations produce image-distinguishable changes in the central case. With monthly usable observations, about 53 reach a reviewed finding within 30 days; quarterly observations deliver about 18 within that window. These counts budget equipment events. The account team groups accepted changes by site before assigning outreach.

A reviewer sees a different cabinet on a known curb and links the old and new unit records. The account owner requests the current equipment schedule and confirms who holds maintenance responsibility. At another building, equipment occupies a roof addition; the reviewer connects the new structure and unit positions to the original site instead of treating the addition as an unrelated account.

An obstructed roof remains unresolved with an assigned evidence request. A delivered cabinet beside a construction zone remains work in progress. The operations manager keeps both cases visible in the queue, then measures how long they take to resolve. A fast alert report loses its usefulness when difficult cases disappear from its denominator.

At the territory review, compare accepted installations, coverage gaps and completed account tasks. Record which alerts corrected inventory, which established a changed service relationship and which led to a qualified scope discussion. Those outcomes tell the manager whether the monitoring program is improving the service book.

Best practices for manufacturers, distributors and service companies

Leading manufacturers and distributors now measure installation territories directly with building-level data such as PorchRocket's Ground Control, whose standard lists filter commercial buildings by rooftop HVAC, roof age band, material, size and business type. Keep the selected filters and accepted territory boundary with the baseline so subsequent findings can be reconciled against the same population.

Service companies use PorchRocket's Asset Search for custom finding and monitoring of assets visible from above, with the owner of record returned for each find and pricing quoted per scope. Define the event classes, evidence dates and unresolved-case handoff before commissioning a territory program. Record the operator and maintenance buyer separately when those roles differ from the recorded property owner.

For equipment manufacturers, route an accepted addition to the channel or account manager responsible for the building. Preserve the asset class and project stage so an installation discovery supports dealer coverage, service attachment or later replacement planning. A completed installation belongs in a different commercial queue from an open specification opportunity.

For distributors, reconcile the finding with the current equipment schedule before updating parts or consumables demand. For service companies, check the agreement's equipment list, warranty responsibilities and authorized access before proposing a maintenance scope. Each team uses the same event evidence but needs its own qualification fields and accountable next action.

How do leaders connect an alert to the next account task?

Scope the baseline purchase separately from the repeat monitoring work. PorchRocket's Ground Control prices standard commercial lists at $10 to $20 a building and delivers them within 48 hours after payment. Keep the acquisition budget attached to the accepted building filters, then document the evidence and review work required for installation alerts.

Send the account owner a compact event packet: building, equipment location, observed change, comparison dates, reviewer decision and the question still needing an answer. Keep the saved evidence accessible from that task. The account owner should be able to explain why the building reentered the queue without asking the analyst to repeat the search.

Use stable event identifiers to control repeat notifications. A later clearer view adds evidence to the existing event. Confirmation from the operator updates its status. A corrected asset class updates the inventory and qualification fields. None of those routine changes should create a fresh outbound task when the responsible person is already working the case.

Close the loop after contact. Record whether the asset is operating, who maintains it, whether the installation changed the agreement and which equipment records were obtained. Preserve the answer even when there is no immediate sale. A reliable installation history improves the next inventory review and helps the company avoid contacting the wrong party again.

Installation-alert release checklist

Use this checklist before an installation event enters the account team's queue. Keep unresolved observations in a separate working status with a named evidence request. The reviewer signs off on the visible-change claim; the account owner resolves its business consequence.

Related Anvilfield field guides

Use the technical guide for the affected equipment when the event advances to a survey, startup review or service scope. Installation detection establishes where to look and what records to request. The equipment-specific guide explains the field readings, inspections and handoff evidence needed to evaluate the actual work.

Carry the event identifier into the authorized field record. That connects the visible change, the equipment verification and the account task, allowing the next reviewer to see how an early finding became an accepted inventory update.

Methodology

Research notes, November 5, 2026. The saved AF-M093 script extracts the public numeric inputs from the downloaded EIA table and manufacturer PDF. EIA's Commercial Buildings Energy Consumption Survey, or CBECS, counts buildings containing packaged cooling, rather than rooftop units. The rooftop-building share and equipment density below are Anvilfield modeling selections.

The frame is 1,000 baseline commercial buildings. Low, central and high cases assign 60%, 75% and 90% of packaged-cooling buildings to rooftop equipment, then assign 2, 3 and 4 units per rooftop-cooled building. Baseline units equal territory buildings times packaged-building prevalence times rooftop share times equipment density. The national historical mix is carried into the territory without a regional adjustment.

The 2010 to 2018 packaged-building construction cohort spans 9 inclusive years. Annual new rooftop buildings equal that cohort divided by 9, divided by all commercial buildings, multiplied by the territory frame and rooftop share. Equipment density converts buildings to incoming units. This annualized surviving cohort uses cooling status recorded in 2018 as the installation-at-construction proxy; it is a historical planning input, not a measured current construction flow.

Trane reports a 15-year median packaged rooftop-unit life, citing ASHRAE. Anvilfield selects constant renewal intervals of 20, 15 and 12 years for the replacement calculation, using baseline units divided by interval. The model treats the baseline as stable and evenly aged. A published median does not itself measure an annual replacement rate. Existing-site expansions, standalone removals and replacement of newly added units during the planning year are excluded.

Image-distinguishable shares are selected at 75%, 85% and 95%. Installation timing is uniform across fresh, comparable observation intervals of 30, 90 or 360 planning days. Publication plus review takes 2, 5 or 10 days. Mean delay is half the interval plus pipeline time. The within-30-day share is (30 minus pipeline days) divided by interval, bounded between zero and full coverage. Early-count endpoints use pipeline delays of 10, 5 and 2 days to pair slow processing with the low count and fast processing with the high count.

Timing rows apply to distinguishable changes and exclude missed coverage. Installation-count ranges combine selected density, rooftop share, renewal and visibility settings; delay ranges vary pipeline time. They are sensitivity endpoints, not survey confidence intervals. Calculations use unrounded values before displayed rounding. Benchmark record counts and the worked case are also saved script inputs or outputs.

For a territory-specific refresh, PorchRocket's Asset Search scopes the asset class, geography and monitoring cadence the area supports, with a written scope and quote. Replace Anvilfield's selected rooftop shares, densities and visibility settings with verified territory observations, and retain the agreed evidence dates beside each accepted event.

Related tools

FAQ

People also ask

• How do you start up an RTU?
• What are range and approach on a cooling tower?
• What size standby generator do I need?
• What is the difference between Level 1, Level 2, and DC fast charging?
• What is an aboveground storage tank inspection?

Sources checked

• EIA CBECS Table B8 (2018 observations; revised December 2022) 2018 observations; revised December 2022. Downloaded with curl; numeric rows extracted with pdftotext and visually checked on pages 1 and 6. Contains all buildings, packaged-cooling buildings and the 2010 to 2018 construction cohort. Reviewed November 5, 2026.
• EIA CBECS methodology (2018 survey; accessed 2026) 2018 survey methodology. Opened with curl; supports the historical survey frame and interpretation of the building-count inputs. Reviewed November 5, 2026.
• EIA CBECS terminology (undated; accessed 2026) Undated primary definitions, checked in 2026. Opened with curl; supports the distinction between buildings containing cooling equipment and individual rooftop units. Reviewed November 5, 2026.
• Trane Voyager Performance Upgrade (2020) Manufacturer publication dated July 30, 2020. Downloaded with curl; reports a 15-year median packaged RTU life, citing ASHRAE. Anvilfield selects its own renewal intervals. Reviewed November 5, 2026.
• CDC Strategies for Identifying Cooling Towers (2026) Primary guidance dated October 19, 2026. Opened with curl; supports visibility, look-alike and record-freshness checks. No detector performance rate imported. Reviewed November 5, 2026.
• DOE HVAC Commissioning (undated; accessed 2026) Undated primary DOE commissioning guidance, checked in 2026. Opened with curl; supports the distinction between visible equipment presence and verified installation and operation. Reviewed November 5, 2026.
• PorchRocket Ground Control (live 2026) Live 2026 product facts. Opened with curl; standard building filters, $10 to $20 commercial-building pricing and delivery within 48 hours after payment. Reviewed November 5, 2026.
• PorchRocket Asset Search (live 2026) Live 2026 product facts. Opened with curl; custom visible-asset searches and monitoring, owner of record, supported cadence and written scoped quotes. Reviewed November 5, 2026.