Planning Uptime and MTTR KPIs Across a Portfolio Refresh
Use this annotated datasheet after a portfolio refresh award to turn field records into a reviewable operating baseline. It is designed for the facility manager who owns door operability after handover and needs uptime and mttr kpis portfolio planning that remains comparable when sites, cohorts, or service arrangements change. Each section identifies the field, its source, the annotation needed for a fair comparison, and the decision it enables. This is a smart lock field service KPI sheet, not a catalogue comparison or a promise of response or repair performance.
Direct answer. In brief, this article covers uptime and mttr kpis portfolio planning from uptime and mttr kpis portfolio planning to uptime-and-mttr-kpis. It states what to confirm about uptime and mttr kpis portfolio planning on the dated product page where a figure is involved. An uptime and mttr kpis portfolio planning is the operating-life view. It starts after the invoice. uptime and mttr kpis portfolio planning is the first interval of uptime and mttr kpis portfolio planning to measure.
Read uptime and mttr kpis portfolio planning as uptime and mttr kpis portfolio planning. It is a working definition of uptime and mttr kpis portfolio planning. Not a statutory or certified one. It applies to the market and product in question rather than as a general claim.
- Set the interval — define how often uptime and mttr kpis portfolio planning is inspected
- Set the trigger — name the condition that forces a change to uptime-and-mttr-kpis
- Track the number — keep one metric that shows datasheet control panel is healthy
- For uptime and mttr kpis portfolio planning, the order below is fixed and uptime and mttr kpis is the reference point.
Datasheet control panel
Complete the control panel before calculating a KPI. The buyer owns the scope, targets, exclusions, and approval decisions; the record supplies evidence.
| Datasheet field | Required entry | Annotation that prevents a false comparison | Owner |
|---|---|---|---|
| Portfolio scope | Sites, door classes, unit population, and reporting period | Name included and excluded populations | Facility Manager |
| Clock rule | Report, acknowledgement, attendance, and operable timestamps | State the permitted source and time standard | Service desk lead |
| Source map | Ticketing, monitoring, access-control, and technician records | Reconcile door or unit identifiers | Record owner |
| KPI target | Metric, target, effective date, and approving role | Leave blank until approved through governance | Portfolio sponsor |
| Variance rule | Review and action thresholds | State what triggers review, not automatic replacement | Facility Manager |
| Refresh cohort | In-flight, installed, excluded, and comparator units | Freeze cohort membership at each review | Programme lead |
| Decision right | Accountable owner and escalation route | Name a role rather than an individual | Contract owner |
| Evidence date | Source-extract date and approving role | Prevent silent restatement of results | Governance role |
Use site documentation to complete the population rather than infer it from a purchase list. The Office Smart Lock Site Survey and Smart Lock Retrofit Site Survey can help identify the door and unit context that the operating register must preserve. A survey does not become an availability record; it identifies the population over which the buyer may calculate availability. What can be supplied is listed in the smart door locks.
Measurement clock and source records
The KPI clock begins only when the buyer's agreed reporting channel receives the fault report. The audit trail must preserve every subsequent event without substituting technician arrival for the original report.
| Record field | Required content | Annotation |
|---|---|---|
| Case reference | Unique fault or service case | Link repeat events to the originating case |
| Door or unit identifier | Object-schedule identifier | Do not use a room label as the sole key |
| Model and variant | Label or dated catalogue evidence | Verify the exact SKU before acting on model-specific evidence |
| Reported | Date, time, channel, and reporter | State when the fault entered the system |
| Acknowledged | Date, time, and acknowledging role | Distinguish acceptance from attendance |
| On site | Date, time, and technician or contractor | Record arrival independently |
| Door operable | Date, time, and verification method | Show that normal door operation was restored |
| Scheduled period | Intended operating window | Apply the approved closure treatment |
| Symptom and checks | Technician wording plus measured observation | Record what each check ruled out |
| Disposition | Action, parts or unit handled, and repeat status | Preserve supporting photos or readings |
Audit the door-level fault resolution records as one evidence set. Response time measures the interval to acknowledgement; on-site attendance time measures the interval to arrival; resolution time measures the interval from report to the door being operable again. None of these intervals explains the cause by itself.
The field for How to Measure and Record Uptime and MTTR KPIs is useful where source-system timestamps need reconciliation. Where a report time is absent, mark the interval as unresolved rather than reconstructing it from an arrival time or invoice.
Formula sheet with decision annotations
Treat “uptime” as the label for the buyer's availability calculation and place the formula beside it. Portfolio availability measurement is defensible only when the population, scheduled period, and treatment of exceptions remain visible.
| KPI | Calculation | Required population | What the result does not reveal |
|---|---|---|---|
| Availability | Operable time ÷ scheduled time | Stated units, doors, sites, and period | Whether excluded doors were operationally important |
| MTTR | Mean of included resolution intervals | Resolved cases with valid report and operable timestamps | The long tail or unreported faults |
| Response time | Acknowledgement time − report time | Cases acknowledged through the agreed channel | Whether anyone attended |
| On-site attendance time | Attendance time − acknowledgement time | Cases with a recorded attendance event | Whether the door was fixed |
| Resolution time | Operable-again time − report time | Cases restored to normal operation | Why restoration took that interval |
| First-time fix | Qualifying repair visits with no repeat visit ÷ included repair visits | Visits with an agreed repeat window | Whether the underlying cause was found |
| Repeat rate | Repeat failures within the agreed window ÷ included failures | Failures in a stated population and period | The severity of each recurrence |
For the MTTR calculation method, include only cases with defensible start and end events; disclose excluded and open cases beside the result. An average can conceal a small group of long restorations, so pair it with a buyer-approved distribution view and an open-case ageing report. The target fields stay under buyer governance; this datasheet supplies no benchmark or availability figure.
Cohort map for portfolio refresh decisions
A portfolio result becomes misleading when recently refreshed and stable units are combined without explanation. Set cohort membership before extracting the data.
| Cohort | Inclusion rule | Comparison purpose | Required annotation |
|---|---|---|---|
| Pre-refresh baseline | Units operating before the refresh scope | Establish the prior operating pattern | State model mix, sites, and period |
| Refresh in flight | Units awarded or scheduled for refresh | Track transition risk | Mark installation and handover states |
| Refresh completed | Units operating after handover | Assess the refreshed population | Link to accepted operating baseline |
| Stable comparator | Similar units outside the refresh scope | Test whether a pattern is portfolio-wide | Record selection logic |
| Out of scope | Units excluded for a stated reason | Preserve denominator integrity | Attach approval and reason |
A cohort may contain both in-flight and completed units only if the data view states which stage each unit occupies. Do not allow a unit to disappear merely because its case lacks a matching record. For cross-site control, apply the same fields and clock boundaries in Uptime and MTTR KPIs Across Several Sites, then document site-specific exceptions rather than changing the formula.
From variance to operational action
A KPI variance starts an investigation; it does not identify the fault or authorize a unit replacement.
flowchart TD
A[Freeze population and clock] --> B{Scope complete}
B -->|No| C[Return record for correction]
B -->|Yes| D[Compute KPI and exception set]
D --> E{Variance or open pattern}
E -->|No| F[Continue operating review]
E -->|Yes| G[Classify the likely cause]
G --> H{Action inside buyer control}
H -->|Yes| I[Assign local corrective action]
H -->|No| J[Request supplier evidence]
J --> K[Record outcome and review cycle]
| Signal | Likely investigation scope | Evidence required | Decision route |
|---|---|---|---|
| Power-related alert | Power state or alert interpretation | Recorded alert and measured power observation | Diagnostic check before unit swap |
| Door will not latch | Alignment, closer force, or latch preload | Free-hand movement and door-condition observation | Mechanical route |
| Credential fails while another entry path works | Credential path | Credential state before and after the check | Credential route |
| Same symptom across matching units | Shared configuration or unit pattern | Checks repeated across the affected set | Portfolio investigation |
| Repeated symptom at one door | Door-level condition | Site history, checks, and previous disposition | Corrective action |
| Missing or conflicting timestamps | Record integrity | Source extract and audit trail | Return for correction |
Use the field-service evidence to classify the issue before authorizing a replacement decision. The Uptime and MTTR KPIs Documentation Set defines the evidence pack, while Uptime and MTTR KPIs: Contract Clauses that Make It Work identifies the commercial questions that should be settled before handover.
The practical counterpart to this point is smart lock motor life testing. That is the same question uptime and mttr kpis portfolio planning has to answer here.
Exception ledger and treatment rules
Exceptions need explicit treatment because excluding every inconvenient case can make a weak portfolio appear reliable.
| Exception class | Record rule | KPI treatment | Follow-up |
|---|---|---|---|
| Planned closure | Link to the approved operating calendar | Apply the pre-approved treatment | Retain approval reference |
| Access or occupancy constraint | Record the reason and affected interval | Apply the standing rule; do not estimate silently | Site action owner |
| Duplicate case | Link duplicate records to one case | Count once | Record data correction |
| Awaiting parts or support | Keep the case open | Do not remove it from open work | Review ownership and evidence |
| Repeat visit | Link to the original case | Apply the agreed repeat definition | Preserve first-visit disposition |
| Missing report time | Identify the source gap | Mark the interval unresolved | Request source correction |
| Unit outside population | State the exclusion reason | Exclude only under the approved rule | Record cohort change |
CONFIRM-WITH-LOCAL-SITE-OWNER: Confirm access, escort, occupancy, closure, and replacement-window rules at each site before fieldwork is scheduled.
KPI register and review cadence
The refresh belongs in post-award lifecycle operations, not only in procurement reporting. Treat facility maintenance reporting as the downstream consumer of this register, while retaining the detailed evidence in the field-service system.
| Register block | Required content | Review question | Accountable role |
|---|---|---|---|
| Availability register | Operable and scheduled time by cohort | Is the denominator complete and approved? | Facility Manager |
| MTTR register | Included and excluded resolution intervals | Are start and end events defensible? | Service desk lead |
| Response and attendance register | Acknowledgement and arrival events | Are the clocks distinct? | Support coordinator |
| Exception ledger | Every excluded, open, duplicate, or uncertain case | Does each row have an approved treatment? | Record owner |
| Cohort map | Units and their refresh or comparator state | Did population membership change? | Programme lead |
| Action register | Decision, owner, evidence, and review date | Is a variance converted into tracked work? | Facility Manager |
| Target approval | Metric, target, source, and effective date | Can every reported target be traced to approval? | Portfolio sponsor |
Publish the register at the cadence set by governance, but retain one frozen extract for each review. If a population, clock, target, or exception rule changes, record a new version and explain comparability with the prior period.
Sign-off record and supplier evidence request
| Sign-off check | Required evidence | Approving role |
|---|---|---|
| Scope and cohort frozen | Approved portfolio map | Facility Manager |
| Formulas unchanged | Versioned KPI definitions | Portfolio sponsor |
| Sources reconciled | Case, attendance, and operability extracts | Record owner |
| Exceptions visible | Completed exception ledger | Service desk lead |
| Target provenance attached | Approved target record | Portfolio sponsor |
| SKU evidence dated | Product-page evidence where it affected a decision | Technical reviewer |
| Actions assigned | Action register with accountable roles | Facility Manager |
When model or variant evidence affects a repair, replacement, or acceptance route, confirm on the dated product page for the specific SKU. Record that dated page and the decision it supports.
CONFIRM-WITH-LOCAL-CONTRACT-OWNER: Confirm which service commitments, exclusions, and escalation routes apply under the buyer's own agreement and local requirements.
CONFIRM-PER-SUPPLIER: Obtain the purchased supplier's written support route, evidence requirements, escalation contacts, and return workflow for the specific order.
Use the signed pack to request only the evidence needed for an open decision or recurring pattern. That makes uptime and mttr kpis portfolio planning auditable: the KPI remains tied to a defined population, a defensible clock, visible exceptions, and an accountable action rather than a headline percentage unsupported by field records.
When the file is ready, request a quote against the written requirement.

