ARMS / OPERATIONAL INTELLIGENCE PLATFORM REV 5.0 — WIREFRAME / HOME

Software didn't fix buildings. Intelligence will.

ARMS is the intelligence layer for building operations. It connects the live signals of a building — email, calls, documents, sensors, staff activity, residents, vendors, payments, and external systems — into one controlled operating layer that understands what's happening, sends the right action, verifies the work, and proves every step.

Category
Building operations infrastructure
Autonomy
Governed automation, full audit trail
Coverage
Security · Facilities · Ops · Finance
§ 00 · THE PROBLEM FIG. 02

Software digitized buildings. It gave them dashboards, portals, forms, and reports — but left every decision scattered across inboxes, people, and after-the-fact records. Buildings don't need another place to store what happened. They need a system that acts.

Record-keepingToday's stack logs events. Someone still has to notice, decide, dispatch, and follow up — manually, every time.
Operational volumeHundreds of events a day across security, facilities, and cleaning. Human attention doesn't scale; the queue does.
No closed loopWithout verified action and an audit trail, "handled" is a claim — not evidence.
§ 0.5 · HOW IT WORKS — KNOW → RUN → VERIFY FIG. 02 — SIGNAL TO PROOF
CASE-0428New Case
Airflow trend flagged
AHU-12 · variance +12%
Dispatching
1Know

The building creates signals — ARMS reads them together and decides what matters.

Tap to start · interactive
Mechanical RmBLE beacon · on-site
9:01▟ ▞ ▰
▢ ARMS+
2Run

The right action reaches the right person — with location, instructions, and proof attached.

Building Truth · Field Confirmation
Ingested ▸ 0
Awaiting Confirmation
HVAC Filter Replacement
Maintenance · Jordan Lee
— · not yet confirmed
Location Verified
3Verify

Presence is verified on site, the work is proven, and the result becomes intelligence.

Proof feeds back · the building gets smarter
§ 01 · OPERATING DOMAINS — ONE LAYER, MANY BUILDING FUNCTIONS FIG. 03 — 6 DOMAINS
/ 01

Operational Intelligence

Events that resolve themselves.

ARMS classifies the event, checks the rule, routes the workflow, notifies the right people, and records the outcome. Closed in minutes — not meetings.

CLASSIFIERCLASSIFYING
/ 02

Workflow Execution

Decisions become dispatch.

Governed automation turns policy into action. Approval chains where they're required; autonomy where they're not. Every step deterministic and inspectable.

WORKFLOW · 5 NODESEXECUTING
/ 03

Audit & Verification

Activity that verifies itself.

Patrols sensor-confirmed. Tasks timestamped. Outcomes signed. When it matters, the record is evidence — not anecdote.

AUDIT LEDGERSIGNING
07:41:02 round · zone-7 SIGNED
07:41:08 task · floor-9 SIGNED
07:41:15 access · dock-N SIGNED
07:41:23 incident · 07f3 SIGNED
/ 04

Field Operations

The building reports in.

BLE beacons and NFC infrastructure put ground truth under every round, every inspection, every shift — across security, maintenance, and cleaning teams.

BLE MESH · PATROL ROUTELIVE
/ 05

Integrations

Runs your stack, or beside it.

Deploy ARMS as the complete operations platform — or as the intelligence layer over the systems you already own. Either way, it acts.

CONNECTOR MESHSYNCING
/ 06

Governance & Safety

Autonomy, with a hand on the brake.

Every action proposed by intelligence is checked against policy before it runs. Approvals where the stakes demand them, hard stops where they don't — bounded, reversible, and recorded.

ACT-BOUNDARY · GATEGOVERNING
§ 02 · LIVE BUILDING PROOF — WORK YOU CAN SEE, PROOF YOU CAN EXPORT FIG. 04 — DEPLOYMENT
arms://site-map · MERIDIAN-GEN-HOSP ANCHORS 10 ONLINE 10/10 PATROL UNIT-04 --:--:--
N 0 ── 20m
SENSOR ANCHOR · ARMED
CHECKPOINT · VERIFIED
TRAINING ANCHOR
GUARD · UNIT-04 · LIVE
CHECKPOINT LOGLIVE
Rounds today
128
Coverage
100%
Avg interval
4m 12s
Last checkpoint
CP-15
0BLE beacons deployed across Canadian buildings
0Patrol rounds logged, sensor-confirmed
0Operational history — building since 2017
0Verticals served: healthcare to municipal
§ 2.5 · LIVE OPERATIONS — DATA IN, DECISIONS OUT FIG. 04B — THROUGHPUT
arms://ops-console --:--:-- UPTIME 00:00:00 MODE · GOVERNED
↘ INGEST · FIELD SIGNAL000
Governance Core
0 /min
RESOLVED · DISPATCHED ↗000
Throughput · last 60s
Median resolution
3m 41s
Policy passes
99.2%
Open queue
0
§ 03 · WHY ARMS FIG. 05 — COMPARISON
BEFORE / SYSTEM OF RECORD

Dashboards show what happened.

Charts. Reports. Exports. The event is over by the time anyone reads about it — and the work of responding hasn't started.

  • event logged → someone notices, eventually
  • decision made in a meeting
  • follow-up tracked in a spreadsheet
  • "handled" — unverifiable
AFTER / SYSTEM OF ACTION

ARMS runs what happens next.

Governed automation with a full audit trail. Every action authorized by policy, executed by workflow, confirmed by sensors, and signed into the record.

event classified · policy checkedPASS
workflow routed · people dispatchedSENT
outcome confirmed by infrastructureVERIFIED
closed · timestamped · auditableSIGNED
§ 04 · NEXT STEP

The operating layer
your buildings run on.

Bring us one operating process your current software can't handle. If it can be described as inputs, rules, decisions, approvals, actions, and records, ARMS can usually turn it into a governed workflow.

§ 05 · GET STARTED

Put intelligence
on your buildings.

Run ARMS as your full operations platform — or as the smartest layer over the stack you already own. Either way, it starts acting on day one.

6,000+ BLE SENSORS 200,000+ ROUNDS LOGGED 9 YEARS LIVE 8 VERTICALS