IT & Facility Workspace

What it is

Two things working together. The first is OmicCockpit, the app I built to run IT and the building: my own tickets, equipment and employee lists, onboarding and offboarding, and a library of the building's systems.

The second is the Facility folder on our company file server, which holds more than a decade of facility knowledge: vendor reports, quotes, contracts, drawings and service history. I open Claude in one workspace that combines the two.

How I use it

When something goes wrong, like the HVAC, I ask Claude about it right there and get that system's whole story: the last time it broke, what fixed it, who worked on it, and the report from each visit. What used to mean digging through years of folders and old email now takes one question.

Built from a real bad day

One hot afternoon nobody knew how to reset an air handling unit while rooms were heating up. That became the building library, designed around one question: what is this unit, what does it feed, and exactly what do I do when it stops cooling? I organized about 190 vendor documents and five years of service history into it.

My own ticket system

My requests kept getting lost between email and the task board I used, so I built my own and moved 823 old tickets into it with cleaner fields. I also designed an email assistant for it with strict rules: it catches duplicates, only suggests when it isn't sure, never closes anything on its own, and logs every action it takes.

Guardrails

A safety check sits between Claude and the file server. Claude can read everything there, but it is blocked from changing or deleting anything, so a decade of records can't be damaged by a mistake.