[ height ][ use mix ][ N ] domainsCondition-basedZero-install
01 · What this is
Tap a chip, log the moment
A supertall runs on judgments made on rounds — the facade panel checked, the plant room sound, the fire door sealed, the deck safe. Each key point carries a passive chip. On a round, the technician taps it with the phone in hand and answers one quick thing. Over time the tower accrues a tamper-evident record of how it was kept — the operational memory between formal surveys.
No app. No login. Five seconds. Maintenance follows observed condition, not a calendar alone.
02 · How to tap
Three steps
1
Hold your phone to the chip
Top-back of the phone, on the asset tag. A page opens by itself.
2
Answer the one question
It already knows the asset, floor and system. Tap your answer.
3
Add a note if needed
Only if something's off. Otherwise close it and carry on.
03 · The rounds
System & cadence
Each domain has its own rhythm. Find your system, find your round.
Domain
Daily
Weekly
Monthly
Facade & Envelope
—
●
●
Vertical Transport
●
●
●
MEP / Plant
●
●
●
Fire & Life-Safety
●
●
●
Observation Deck
●
●
—
Illustrative cadence — replace domains and intervals per building.
04 · Your system — try each point
Open your domain
Each system has its own chips. Open yours, then scan a QR with another phone or hit “Try” to feel the exact tap before the round.
Facade & Envelope2 chips›
Panel
Log: sound · sealant wear · damage flagged
Drainage / weep holes
Log: clear · partial · blocked
Vertical Transport1 chip›
Lift bank
Log: all running · reduced · out of service
MEP / Plant2 chips›
Air handling unit
Log: normal · attention · fault
Plant room
Log: normal · attention · fault
Fire & Life-Safety2 chips›
Fire door
Log: closed & sealed · propped · faulty
Refuge floor
Log: clear · issue flagged
Observation Deck2 chips›
Glass floor
Log: clear · smudged · damage flagged
Deck
Log: within limit · near capacity · over
05 · What a tap looks like
One question, one answer
● Facade & Envelope · Panel
Facade panel condition?
SoundSealant wearDamage flagged
It logs the asset, the floor, the time, and the answer — attributed to a role, never a named person. The record is of the building, not the staff.
06 · Why we do it
The operations log
Every tap feeds one record the operator reads — across every system, over time:
🏢
Every system, one view
What's sound and what needs attention, floor by floor.
📉
Condition trend
Maintenance by observed state, not a calendar alone.
🧯
Fire & life-safety evidence
Tamper-evident proof rounds were performed, for audit and insurance.
🛗
Vertical-transport uptime
Lift availability and faults, recorded as they happen.
🤝
Handover continuity
The record survives the shift, the contractor, the operator change.
07 · Since last round
What we're testing this round
Round 1 — keep it lean
First round: just the chips above, nothing more.
Goal is one clean condition record, not perfect coverage.
Tell us what felt clumsy — the next round fixes it.
This panel updates each round — over time it shows what each system taught us.
A word on privacy & scope
The chips log events, never people. No login, no name, no tracking of who tapped what — and no surveillance of residents, guests or staff. In residential and guest areas, only common-area facility events are recorded. The record is about how the building was kept. By design, and it can't be changed.
This is a reference template — the placeholders ([ Building ], domains, cadence) are filled per deployment. For demonstration, not a record of any specific building.