Your Cameras Can File Their Own Maintenance Tickets

Rhombus + Claude Series — Tying Into the Enterprise

Every organization has a facilities backlog. Broken locks, flickering lights, a camera that’s been “acting weird” for months. The tickets that get filed are the ones where someone noticed and remembered to file them. Everything else just… lingers, until it becomes a problem someone else discovers.

For cameras specifically, this dynamic is particularly bad. A camera with degraded image quality still looks fine on the dashboard. A camera with intermittent connectivity works most of the time. Nobody files a ticket until footage is missing for an event that actually mattered — which is also the moment you most wanted the camera working.

Facilities maintenance should be a queue the systems feed themselves, not a queue that humans curate.

Rhombus reports health metrics for every device. Jira manages the work. Connecting the two makes proactive maintenance the default.

For the developers:

With Claude and the Rhombus plugin, this is a weekly scheduled prompt:

“Audit camera health. For any device with degraded connectivity or image quality, open a Jira ticket in FACILITIES assigned to the site tech.”

Claude audits, Jira captures the work, and facilities gets ahead of the backlog instead of reacting to it.

The payoff: You move from a world where cameras fail until someone notices to a world where cameras flag their own decline before anyone has to. That’s not a marginal improvement. It’s the difference between a camera system you trust and one you only check after the fact.