Reference profile
netNotdienst Overview
Suitable service and technology paths
Important in-depth analyses on this topic.
netNotdienst is one of our most important references when we want to demonstrate that we are strong beyond conventional screen software. This solution connects client, server, hardware, network, code logic, printing and defined state transitions within a real pharmacy operation. Projects like this reveal whether software is merely presented or can actually assume responsibility in daily operation.
Client, server, hardware and state logic as a unified system
The publicly documented BPV solution describes a clear two-component model. The server runs on the display terminal, manages the pickup locker system, displays the on-call service when idle and provides visual feedback to the customer upon interaction. The client runs on POS or workstation computers and implements the actual operation logic for staff: reserve a compartment, assign a code, print a receipt, place the goods and progress the status.
The state logic is particularly robust. A compartment 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 what state a delivery is in, the customer receives a clear feedback channel and misuse is made more difficult by technical means.
In addition there is the security logic around pickup codes, waiting times, expiring codes and logging. Such details turn a system into a dependable operating system for a real process. For clients this is a strong signal: we do not build cosmetic digitizations; we build systems that must cope with real risks, real actions and real error consequences.
The reference is clear from an infrastructure perspective as well. Communication takes place over the local network via TCP/IP, by default on port 8080, with a sensible recommendation for a fixed IP on the display workstation. In addition, there are print paths for the pickup receipt and a configurable receipt design. It is precisely these operational details that distinguish calm, enterprise-grade software from hectic rework.
- Server on the display workstation as the technical authority for device control, feedback and process state
- Client on POS and workstation machines for fast, clear operation by staff
- clear compartment states instead of fuzzy operation sequences: available, ready, active and emptied
- code logic, receipt printing, network paths and hardware integration as part of the same architecture
Why netNotdienst is such a strong reference
Real processes instead of theoretical software logic
netNotdienst demonstrates that we are robust even where software not only displays data but drives real processes, connects devices and must remain easy to operate for people in a demanding daily environment.
Relevant far beyond the pharmacy
The pharmacy is only the visible field of application. The same competence is required in all projects involving workstations, devices, fixed state 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 just build content pages or simple forms, but operationally relevant applications with genuine 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 demonstrates that we can professionally and technically support exactly such systems.
Read the relevant FAQ for netNotdienst
The questions behind netNotdienst usually go beyond the reference itself: services, portals, system boundaries, operational responsibility and technical process control are covered in depth in the FAQ hub.
Read related FAQs for netNotdienst
The questions behind netNotdienst usually extend beyond the reference itself: in the FAQ center we treat services, portals, system boundaries, operational responsibility and technical process execution with detailed context.
Next step
If you have a concrete modernization, API or platform question, we should establish the technical scope clearly and early.
Net-Base evaluates existing systems, data paths, interfaces and target platforms not in isolation, but in the context of domain logic, operations and future expansion.
- Current state, target state and technical risks are assessed jointly.
- REST, data access, portals and rollout are not deferred to a later stage as secondary consequences.
- You can see early on which path is economically and operationally viable.