The institution is described generically until its official name and permission to publish are confirmed. Security approvals for deployment are not a cyber-security certification, and we do not describe them as one.
The problem
Stock had to be received, stored and issued under institutional procedures, with approvals at each step — and every item had to be identifiable by a label that a scanner, not a person, reads. Running it outside the institution's network was not an option.
What the team built
An inventory management system with barcode design, printing and reading on physical printers and scanners, installed and operated on the institution's own servers after the approvals required for implementation and operation:
- Receiving, storage and issuing with the institution's approval steps built in
- Barcode label design and printing on the institution's printers
- Scanning on physical readers for receipt, issue and stock-take
- Deployment and operation inside the client's infrastructure, not ours
What this case proves
Software that works with hardware, delivery inside a client's own infrastructure, and the discipline to operate under institutional requirements — approvals, restricted networks, audited procedures.
What this page does not show
No institution name, no screenshots, no network or security details. We use the generic description until the official name and publication permission are confirmed, and we do not call the project cyber-security certified because deployment approvals were obtained. References can be arranged on request once the client has agreed.
Stack
- C# / .NET
- SQL Server
- Barcode printers & scanners
- On-premises deployment