Knowing that a computer existed in an inventory last month is different from knowing it has checked in recently. The Computer Heartbeat project is built around that second question.
The documented design connects a PowerShell report to a PHP receiver and JSON history, then presents those records in a browser dashboard. Reports include device and operating-system details, user context, and timestamps. The dashboard brings the latest observations into a searchable, sortable table.
The useful distinction is between an observation and an assumption. A recent check-in tells me the reporting path worked at that moment. An old check-in tells me the information is stale; it does not, by itself, explain whether the device is powered off, disconnected, or having trouble reporting.
The project documentation describes online and offline counts, model and serial information, relative timestamps, and a historical view. Those elements make it easier to move from a broad list to the individual machine that deserves attention.
There is also a packaging detail in the current repository snapshot: the computers folder contains dashboard-side files and documentation, while some documented client and receiver components are not included there. I would treat the folder as part of the documented system, not promise that downloading it alone creates a complete installation.
What interests me here is the connection between a small PowerShell report and a useful web view. The report does not have to be complicated to be valuable. It needs consistent fields, meaningful timestamps, and somewhere those observations can be reviewed without opening a pile of raw files.