Refresh Versus Replace Economics: Which Branch Do You Take
Post-award operations should not treat every lock complaint as a replacement request. The refresh versus replace economics decision tree separates a scoped service action from a change to the installed asset and gives the facility manager a defensible hand-off. Each clause sets a trigger, action, evidence and next approver.
Direct answer. Short version — refresh versus replace economics decision tree is treated here as refresh versus replace economics decision tree first. refresh-versus-replace-economics comes second. The evidence for refresh versus replace economics decision tree is named in the sections below. A refresh versus replace economics decision tree is an operations guide for the installed base. refresh versus replace economics decision tree is the first recurring checkpoint for refresh versus replace economics decision tree after handover.
This article defines refresh versus replace economics decision tree through refresh versus replace economics decision tree. The definition of refresh versus replace economics decision tree is deliberately narrow. It is non-statutory, and it applies to the market and product being discussed.
A refresh retains the core unit and restores service through an approved intervention; replacement removes it and changes the installed asset. Configuration recovery, credential re-issue and component repair can occupy different branches. Installed-base economics compares each branch on the same door rather than rewarding unit substitution.
Clause 1 — Bound the asset before choosing a branch The commercial
Trigger: A unit enters lifecycle review. Action: Start with the object, not the room name. Record the door or unit identifier, model and variant with the dated product page, reported and restored-operable times, symptom wording, measured observation, ordered checks, parts or swap, old-unit disposition, credential state before and after, and a photo or reading. Hand-off: Mark missing fields unknown and send them to the asset owner.
Use three control fields throughout: identify the installed object, mark reported and operable times, and show what was observed, ruled out and changed. Never fill a gap with a room label, portfolio average or supplier assumption. What the specification covers is in the smart door locks.
Clause 2 — Separate the fault branch from replacement
The practical counterpart to this point is the smart lock battery technology. That is the same question refresh versus replace economics decision tree has to answer here.Trigger: A fault is reported. Action: Run these checks in order; each separates a cause before removal is proposed. Evidence: Retain the order and the result each check ruled out. Hand-off: Send a bounded cause to economics, or an unresolved cause to escalation.
| Order | Check | Result |
|---|---|---|
| 1 | Door state, handle freedom and latch preload | Mechanical obstruction |
| 2 | Mechanical override movement | Seized mechanism |
| 3 | Indicator and application status | Jam, power-alert and no-response paths |
| 4 | Power source and fitted emergency input | Usable power |
| 5 | Physical state against recorded state | Configuration or synchronisation mismatch |
| 6 | Credential or fingerprint response | Credential path from drive path |
| 7 | Same symptom on another same-model door | Common-mode pattern |
If the same symptom appears across doors, stop unit substitution and open a common-cause review.
Clause 3 — Build the comparable branch economics
Trigger: The cause is bounded. Action: Use one refresh versus replace calculation per door, preserving door-level lifecycle evidence and isolating operational disruption at that door. Evidence: A signed comparison. Hand-off: The selected branch enters gate review.
| Consequence | Refresh branch | Replacement branch |
|---|---|---|
| Technical work | Scoped restoration | Removal, installation and commissioning |
| Door access | Test window | Removal, transfer and acceptance |
| Administration | Asset and service record | Asset, configuration and credential records |
| Materials and uncertainty | Parts and closure evidence | Fit and acceptance evidence |
Keep common diagnosis effort outside the comparison unless the branch changes it. Record technician effort, temporary access, parts, administration and disruption separately.
The refresh versus replace economics decision tree is complete only when the branch has dated evidence and an acceptance condition. Lower estimated effort does not justify a branch whose door outcome remains unresolved.
Clause 4 — Pass or hold the branch gates
Trigger: A branch is proposed. Action: Replacement decision gates are hold points; a failed gate sends the work back for evidence. Evidence: Signed pass or hold entry. Hand-off: The named approver decides the next clause.
flowchart TD
A[Record the fault and evidence] --> B{Is the cause bounded?}
B -->|No| C[Hold substitution and escalate]
B -->|Yes| D{Is a scoped refresh supported?}
D -->|Yes| E[Pass refresh gates and re-test]
D -->|No| F{Is replacement justified?}
F -->|Yes| G[Pass replacement gates and accept]
F -->|No| C
E --> H[Complete the branch record]
G --> H
Readers comparing approaches usually start with the aa battery smart locks. That is the same question refresh versus replace economics decision tree has to answer here.
| Gate | Refresh passes when | Replacement passes when |
|---|---|---|
| Cause | Fault path is identified and bounded | Reason for removal is documented |
| Scope | Approved intervention can restore operation | Removal and installation scope is authorised |
| Acceptance | Door and credential checks meet agreed criteria | New configuration and credential checks meet agreed criteria |
| Evidence | Closure record is complete | Swap, acceptance and retained-unit record is complete |
If neither side passes, hold the branch, preserve the old unit where applicable, and escalate the unresolved question. Replace-by-default must not become hidden programme policy.
Clause 5 — Close the evidence record
Trigger: Branch work ends. Action: Attach ordered checks with what each ruled out; parts or swap; old-unit disposition; credential state before and after; a photo or reading; and reported and restored-operable timestamps. Evidence: Service record. Hand-off: The asset-record owner may calculate performance from these entries.
Resolution time runs from report to operable again. MTTR is the mean across a defined population and period; it does not reveal the tail or unreported doors. First-time fix means a visit ends with the door operable and no repeat visit for the same symptom, not necessarily that root cause was found. Use the How to Measure and Record Refresh Versus Replace Economics to standardize fields.
Clause 6 — Obtain supplier and site confirmation
Trigger: A branch depends on supplier capability or a service route. Action: Ask what repair and return options apply to the exact model and variant, what written evidence is required, and what must be returned. Confirm on the dated product page for the specific SKU any fit, configuration or capability driving the decision. Evidence: Dated written response. Hand-off: Attach it before authorising work.
Use the Refresh Versus Replace Economics Worksheet: What to Write Down and Why for branch rationale, the Running Refresh Versus Replace Economics Across Several Sites for a portfolio roll-up, and the Refresh Versus Replace Economics Documentation Set for the evidence pack.
CONFIRM-PER-SUPPLIER: Obtain written confirmation of the applicable service, return and evidence route for the specific model and variant; record the answer and its date.
Clause 7 — Route unresolved exceptions
Trigger: Fit, shared cause or acceptance is unresolved. Action: Hold substitutions, preserve evidence, use a separate door-level record such as the Smart Lock Retrofit Site Survey for fit questions, and open a fleet-pattern review when symptoms cross doors. Hand-off: The escalation owner retains the exception note.
CONFIRM-WITH-LOCAL-SITE-POLICY: Confirm access-control, fire-egress, insurer and local-authority constraints with the buyer's approved advisers before changing a door or its temporary access arrangements.
Use the clause bank as the authorisation sheet for each decision. Attach evidence, name the branch and acceptance condition, and escalate the unresolved clause. This makes replacement deliberate rather than default.
The next step is to request a quote.

