Automatic inventory
An agent on each machine reports hardware, installed software, serial number and warranty, and keeps itself up to date. The inventory stops being an old photograph and becomes the current state.
GLPI with automatic inventory, a service desk with committed response times and the full history of every device, ticket and change. The end of the spreadsheet nobody has updated since March.
An agent on each machine reports hardware, installed software, serial number and warranty, and keeps itself up to date. The inventory stops being an old photograph and becomes the current state.
Tickets with categories, priorities and committed response and resolution times, with warnings before anything breaches. Compliance is measured and appears in the monthly report.
From purchase to disposal: who it was assigned to, what was done to it, when the warranty expires and what it has cost to keep. Useful for deciding whether to repair or replace.
Users log their own request, see its status and check the knowledge base before opening a ticket. It cuts repeat questions and loose WhatsApp messages.
Every change to the infrastructure is recorded with who requested it, who approved it and what was touched. When something breaks, the history says what changed in the last 48 hours.
Ticket volume, SLA compliance, devices per area, licences in use. The data comes out exported and ready, for management and for auditors alike.
Sample screen showing what day-to-day operation looks like. Not client data.
Installation and the initial inventory load take a few days. What takes longer is agreeing the categories, approval flows and committed times, because those are business decisions. Typically three to six weeks to be genuinely operating.
If the portal is simple and solves their problem, yes. What kills these projects is asking a user to fill fifteen fields to report that the printer is down. The intake form is deliberately kept short.
GLPI integrates with your directory for user accounts, with monitoring so an alert opens a ticket automatically, and with email so a message creates a ticket. All of that is configuration, not development.
We start by surveying what assets exist, how requests come in today and what can be automated within the first month.