Net-Base Reference

Reference netNotdienst

Client-server software for pick-up locker systems, status logic, code workflows and real-world pharmacy operations.

Reference. Installation. Client-Server.

netNotdienst demonstrates how enterprise software, hardware and status logic interact in everyday operations.

Client Server Attachment Status logic

Real-world pharmacy operation

The solution consolidates issuance processes with assets, personnel and customer feedback into a single, coherent workflow.

Hardware with process logic

Codes, pressure, network, status changes and the asset page must be technically precisely aligned with one another.

Enterprise software with responsibility

The reference proves that we can also handle operations-oriented specialist software with real-world consequences and well-defined state models.

Reference profile

Overview of netNotdienst

Suitable service and technology paths

Important in-depth analyses on this topic.

LeistungenDas Gesamtbild aus Architektur, Modernisierung, Services, Portalen und Betreuung im Ueberblick.TechnologienDelphi, C#, Datenzugriff, REST und Plattformstrategie als technische Basis im Ueberblick.ProjekteProjektarten, Zielbilder und typische Ausbaupfade fuer Unternehmenssoftware und Portallogik.FAQ-ZentraleTypische Projektfragen zu Modernisierung, Delphi, Portalen, Schnittstellen und Betrieb gebuendelt einordnen.

netNotdienst is one of our most important references when we want to demonstrate that we are also strong outside classic screen software. This solution connects client, server, installation, network, code logic, printing and defined state transitions in a real pharmacy operation. Projects like this reveal whether software is merely showcased or can truly assume responsibility in everyday operation.

To the reference overview
BPV pickup locker systems
BPV pickup locker system for dispensing medication outside opening hours
The physical installation is the visible part of the process, but without sound software orchestration it remains only hardware.
Client interface of the netNotdienst solution with multiple locker states
The user interface condenses complex process logic into a few clear and secure operator actions.

Client, server, hardware and status logic as a unified system

Code keypad on a pickup locker system as part of the netNotdienst system
Code entry, the hardware side and the security logic must interact precisely with the software.

The publicly documented BPV solution describes a clear two-component model. The server runs on the display computer, manages the pickup locker system, shows the on-call service in idle mode and provides visual feedback to the customer upon interaction. The client runs on cash register or workstation computers and implements the actual operator logic for staff: reserve locker, assign code, print receipt, place goods and advance the status.

Particularly strong is the status logic. A locker is not simply open or closed, but progresses through defined states such as available, ready, active and emptied. This turns a physical box into a controlled digital process. Staff always know the state of a delivery, the customer receives a clear feedback channel and incorrect operations are made more difficult by technical means.

Added to this is the security logic around pickup codes, waiting times, expiring codes and audit logging. Such details turn an installation into a robust operating system for a real process. For clients this is a strong signal: we do not build purely cosmetic digitalizations, but systems that must handle real risks, real actions and real error consequences.

Infrastructure-wise the reference is clear as well. Communication takes place over the local network via TCP/IP, by default on port 8080, with a sensible recommendation to assign a static IP to the display workstation. In addition there are print paths for the pickup receipt and a customizable receipt design. Exactly these operational details separate steady enterprise software from hectic rework.

  • Server on the display workstation as the technical controller for the installation, feedback and process state
  • Client on cash register and workstation computers for fast, unambiguous operation by staff
  • clear domain statuses instead of vague operation sequences: available, ready, active and emptied
  • code logic, receipt printing, network paths and hardware integration as part of the same architecture

Why netNotdienst stands out as a reference

Real processes instead of theoretical software logic

netNotdienst demonstrates that we are viable where software does not merely display data but drives real processes, integrates devices and must remain easy to operate for people under strained everyday conditions.

Relevant far beyond the pharmacy

The pharmacy is only the visible field of application. The same competence is required in all projects with workstations, devices, fixed status transitions, approvals, codes, printing and logged process steps.

Trust through technical composure

Anyone who sees that we implement such a solution cleanly and calmly immediately understands that we do not only build content pages or simple forms, but operationally relevant applications that carry real responsibility.

netNotdienst as a reference for operational enterprise software

If your own project works with devices, clear state models, feedback logic, network and security-relevant process steps, netNotdienst clearly shows that we can carry exactly such systems both functionally and technically.

Read the relevant FAQ on netNotdienst

The questions behind netNotdienst usually go beyond the reference itself: services, portals, system boundaries, operational responsibility and technical process control are addressed in depth in the FAQ hub.

Project images and reference examplesWindows- and Linux-ServicesServices, REST-servers and portals

Next step

If you have a concrete modernization, API, or platform question, we should define the technical scope clearly and early.

Net-Base evaluates existing systems, data flows, interfaces and target platforms not in isolation but in the context of domain logic, operations and future extensibility.

  • Current state, target state and technical risks are assessed jointly.
  • REST, data access, portals and rollout are not deferred as afterthoughts.
  • You can determine early which path is economically and operationally viable.
Request project consultationView referencesTypical project questions in the FAQ center