End of Life Migration Planning Documentation Set
What follows covers end of life migration planning documentation set as a maintenance and measurement question, not a hardware question. An installed smart-lock base does not move in a neat batch: doors carry different traffic, occupancy, and repair histories. The replacement programme needs a controlled record rather than a purchase spreadsheet.
Direct answer. An end of life migration planning documentation set connects the installed base to the door schedule, replacement evidence, cutover instructions, field service record, and final acceptance. After award, the Facility Manager can use it to show what happens at each door and who releases the next step. Every entry should identify its source, date
Baseline the installed base before changing a door
Start with a population boundary. State which doors are included, excluded, and why. Follow the object schedule, not a room label, so each decision traces to a unit. Record the planning horizon, decision owner, and consistent end-of-life-migration-planning file name across schedules, work orders, and evidence folders. The range this procurement eventually buys from is the smart door locks.
- Door or unit identifier, site, and population boundary
- Model and variant from the label or catalogue row
- Current condition, dependency, and open fault reference
- Retain, replace, or defer decision and approver
- Master door-schedule reference
| Baseline field | Record this | Decision it supports |
|---|---|---|
| Population | Door IDs, site, and inclusion rule | Which units enter review |
| Condition | Observed symptom and field service record | Repair, refresh, replace, or escalate |
| Dependency | Occupancy, access, and operating criticality | Cutover sequence and fallback |
| Ownership | Facility Manager, technician, and approver | Evidence handoff |
For door-level baselines, Office Smart Lock Site Survey and Smart Lock Retrofit Site Survey provide survey structures to reconcile with the object schedule. For a fillable working sheet, use End of Life Migration Planning Worksheet You Can Fill in on Site.
Make the schedule a decision tool
The schedule should show the evidence that permits a door to move, the action selected, and the record that closes it. Use one line per door and expose exceptions; a replacement must not proceed while configuration, credential, or access fallback remains unowned.
- Planned cutover window and named door owner
- Pre-cutover evidence complete
- Access continuity arrangement approved
- Post-cutover check and acceptance owner
- Exception or defer reason recorded
| Decision branch | Evidence to hold | Resulting instruction |
|---|---|---|
| Retain in service | No current fault requiring action; condition reviewed | Retain and set next review |
| Repair or refresh | Technician observation and ruled-out checks | Schedule the selected maintenance action |
| Replace | End-of-life decision recorded against the door | Release a cutover work order |
| Escalate | Unclear cause, unavailable evidence, or service risk | Hold the branch and obtain a decision |
For multi-site consistency, compare the same fields in End of Life Migration Planning: From One Site to Twenty. The comparison table must show which branch is selected and what evidence releases it, rather than presenting options as if they were interchangeable.
Assemble SKU and supplier evidence without overclaiming
The documentation set should carry the information a supplier needs to answer accurately. Copy the model and variant from the label or catalogue row. For any specification affecting purchase, compatibility, or handover, confirm on the dated product page for the specific SKU; do not fill a gap from memory or a similar unit. Record the document identifier used.
- Dated product-page reference for the selected SKU
- Configuration and credential cutover assumptions written as questions
- Requested evidence for setup, support, and return handling
- Supplier response, date received, and unresolved items
- Local site approval attached to the same door record
This is an evidence request, not a supplier promise. Ask what the supplier will support, how exceptions are returned, and which dated document governs the answer. The End of Life Migration Planning Evidence to Request Before You Buy checklist serves as the request cover sheet and separates a documented capability from an assumption.
Plan one cutover without a second outage
The door cutover plan should support installed base replacement without creating a second outage at the same door. Give every step a predecessor, output record, and fallback when expected evidence is missing. It is a sequence of controls, not a promise that every activity will finish on one date.
flowchart TD
A[Freeze the door baseline] --> B[Check the evidence pack]
B --> C[Prepare the cutover work order]
C --> D[Verify door operation]
D --> E[Close or escalate the record]
- Before work: access continuity, tooling, and communication confirmed
- At work: old unit identification and removal condition recorded
- After work: credential state, mechanical operation, and electronic response checked
- If a check fails: safe access preserved and escalation branch opened
CONFIRM-WITH-LOCAL-SITE-REQUIREMENTS: Confirm the access, building-safety, insurance, and local approval conditions that apply before a door cutover; obtain the responsible site's written acceptance.
Verify the door and preserve the evidence
Powering up does not complete a cutover. Preserve the chain from symptom to conclusion in the field service record. Record when the fault was reported and when the door was operable again, using timestamps the buyer's system retains.
| Required entry | Evidence to attach | Acceptance question |
|---|---|---|
| Identity | Door ID, label, and SKU reference | Is this the same unit or door? |
| Observation | Technician wording plus measured reading | What was actually seen? |
| Tests | Checks in order and what each ruled out | Does the conclusion follow the evidence? |
| Work | Parts fitted or unit swapped; old unit retained | What changed at the door? |
| Access | Credential state before and after | Was access restored without an unexplained gap? |
| Closeout | Photo, reading, and acceptance sign-off | Can the record be audited later? |
Close the file and decide what comes next
Final review reconciles the schedule with the installed base and identifies every retained, deferred, replaced, or escalated unit. If needed, calculate availability and MTTR from the buyer's own records: availability is operable time divided by scheduled time for a stated population and period; MTTR is the mean of resolution intervals across a defined period and population. Neither explains why a fault occurred or whether unreported doors were missed.
- All scheduled doors have a disposition
- Exceptions have an owner and next review point
- Lock decommissioning and credential changes are traceable
- Repeated symptoms are grouped for root-cause review
- The approved evidence pack is retained with the work orders
Use Measuring End of Life Migration Planning: What to Record for the measurement record and preserve the original source for every calculated value. A supplier-ready package can then request SKU-specific evidence, a documented support route, and confirmation of unresolved exceptions rather than relying on a general capability statement.
Request the completed end of life migration planning documentation set as a controlled supplier attachment, with written confirmation sought for every field that remains blank. The Facility Manager can then release the next work order knowing which door, evidence, owner, and acceptance test govern the migration.
Close the loop with requesting a quote.

