PTS — Technical Architecture & Performance
What must become visible, measurable, and actionable for tracked material flow to create meaningful institutional value?
A PTS creates more than a faster route between two points.
Its value depends on whether the movement it controls can become visible, measurable, and actionable within the institution.
That means knowing when a material is sent, where it is going, when it arrives, what happened during the journey, and where an exception requires attention.
Movement becomes more valuable when it becomes measurable, manageable, and improvable.
Four technical layers turn movement into an operational data stream
The technical architecture connects the physical movement of materials with the information required to monitor, control, and improve that movement.
01 — Movement
The physical transport of materials through the institution.
02 — Traceability
Identification and timestamping of transactions and movement events.
03 — Control
Routing, prioritisation, monitoring, and exception management.
04 — Integration
Connection between the transport layer and the hospital’s existing digital environment.
Together, these elements turn physical movement into an operational data stream.
Traceability built into the movement
Every transaction can carry a digital record linking the material, carrier, sender, receiver, route, and relevant timestamps.
The system can monitor stations, diverters, blowers and other components while transaction logs and topology mapping provide visibility into system status and movement.
Send
WHO → WHAT → FROM WHERE → WHEN
Route
WHAT IS MOVING → WHICH ROUTE → WHAT IS WAITING
Receive
TO WHERE → WHO → WHAT → WHEN → HOW LONG
Exception
ERROR → HOW TO FIX → STATUS
Traceability extends beyond proving that something arrived.
It makes the conditions surrounding its movement visible.
Carrier availability, station accumulation, receiving-station clearance and system status can also be monitored to identify emerging constraints.
Performance in numbers
7.6 m/s
Standard operating transport speed
<1 min
Average delivery time under normal conditions
<5 min
Peak-demand delivery, including station waiting time
>99.95%
System uptime
Up to 3.6 kg
Carrier capacity
1.17 kW
energy consumption
Reported performance and technical specifications vary according to system configuration and operating environment.
The system architecture
A hospital PTS is a distributed physical and digital infrastructure.
Stations
The user interface for sending and receiving carriers, configured according to facility and network requirements.
Steel tube network
The physical transport pathway connecting required locations across the facility.
Diverters
Routing components that direct carriers through the network.
Blowers
The pressure and vacuum source that propels carriers through the network.
Carriers
Leak-resistant containers designed to protect transported materials while enabling identification and tracking.
Control & software layer
The intelligence governing traffic, routing, monitoring, diagnostics and transaction records.
The system is available in different tube configurations and can incorporate tracked carriers, routing components, blowers and software supporting real-time monitoring and hospital-system integration.
The architecture is modular, allowing the network to expand with the institution rather than requiring the system to be rebuilt from the beginning.
The system communicates the condition of the movement
Healthcare logistics cannot depend on discovering a system problem only after a clinical user experiences it.
The PTS continuously monitors its operating condition, including system status, station availability, carrier availability, routing conditions and component performance.
SYSTEM STATUS
Available
STATION STATUS
Available
CARRIER STATUS
Normal
ROUTING STATUS
Free/Busy
ALERT
Maintenance due
RESPONSE
Action required
The system does not simply move the carrier. It communicates the condition of the movement.
System & station errors
Carrier accumulation
Offline conditions
Maintenance conditions
Abnormal operating events
Delivery events
Integration with the hospital’s digital environment
The PTS can connect with the hospital’s existing information environment through appropriate interfaces, including HIS/LIS connectivity, HL7 capabilities, building-management interfaces and directory synchronisation through AD/LDAP.
The transport infrastructure becomes part of the institution’s information environment rather than a separate operational island.
Technical reliability is part of clinical reliability
Component monitoring
Predictive alert
Planned maintenance
Recovery
A system supporting clinical logistics must remain reliable when the hospital is busy, not merely when conditions are normal.
Controlled transport for clinical materials
Speed has no value if the material arriving at the destination is no longer suitable for its intended use.
Controlled deceleration, appropriate routing geometry and soft-landing characteristics can reduce mechanical stress at destination.
A 2016 study of an innovative PTS reported that samples travelled 300 m in approximately 30 seconds, with no differences in the measurement results of the 36 analytes investigated compared with courier transport.
300 m → ~30 s → 36 analytes investigated
Suchsland et al., 2016 — validation in the studied hospital configuration.
Evidence is configuration-specific. Laboratories should validate their own transport conditions and intended clinical applications against appropriate quality requirements.
Hygiene is part of the transport environment
Routine hygienic maintenance is part of safe operation.
A 2020 university-hospital study found no pathogens in PTS effluent air or tubes during routine operation, while identifying receiving/entry areas as locations requiring regular disinfection. The authors concluded that routine hygienic maintenance makes pathogen transmission highly unlikely.
Khaznadar et al. (2020), Journal of Hospital Infection, 104(3), 374–380.
Controlled transport means protecting the material, maintaining the transport environment, and validating the system for its intended clinical use.
Technical performance becomes lifecycle value
A technical specification matters because it changes what the institution pays for, maintains, replaces and relies upon over time.
Energy
Power consumed during continuous operation.
Durability
Service life of the core infrastructure.
Maintenance
Frequency, predictability and complexity of intervention.
Spare parts
Variety vs. standardized, and quantity required to maintain availability.
Operational continuity
The cost and consequence of disruption.
Durability + Maintainability + Energy + Continuity + Replacement burden
LIFECYCLE VALUE
The lifecycle perspective also considers the resource burden associated with infrastructure replacement. Steel-based infrastructure can provide durability and recyclability, while energy consumption remains a measurable operating consideration.
The relevant technical question is not only what the system costs to acquire. It is what it consumes, requires, replaces and enables throughout its useful life.
Designed for the hospital environment
A PTS is physical infrastructure inside a live healthcare facility.
Its technical performance therefore depends on how it interfaces with the building around it.
EXISTING ENVIRONMENT
HIS
Hospital Information System
LIS
Laboratory Information System
Hospital operations
Nurse call
User directory
Building / facility systems
PTS CONTROL & INFORMATION LAYER
Pneumatic Tube System
Physical movement
Stations → Network → Routing
↕
Control & information
Tracking → Monitoring → Alerts
↕
Integration
HIS/LIS · HL7 · AD/LDAP · BMS
INSTITUTIONAL INFORMATION
Authenticated users
Who initiated and received the transaction.
Transaction record
What moved, where, and when.
Operational visibility
Movement, exceptions and system condition.
Management information
Evidence available for monitoring and improvement.
The transport infrastructure becomes part of the institution’s information environment—not a separate operational island.
Pre-commissioning coordination considers architectural and MEP interfaces, route coordination, structural constraints, station positioning, installation planning and risk mitigation.
The system must coexist with:
Architecture · Electrical infrastructure · HVAC · Plumbing · Fire protection · Clinical spaces · Existing hospital systems · Future expansion
Technical reliability begins before the first carrier enters the system.
The asset becomes sustainable when the institution can carry it forward
Assess
Engineer
Coordinate
Install
Commission
Enable
Monitor
Improve
Designed for the future operating condition
The PTS is designed around the institution’s future demand, operating model, material flows, clinical requirements and measurable performance objectives — not simply its current number of beds.
Demand
Departments
Material flows
Turnaround requirements
Routes
Integration
Expansion
Capability remains with the institution
The intervention extends beyond system-related training.
Operational capability
System use, alarms, dispatch/receiving and routine operational response.
Engineering capability
Troubleshooting, preventive maintenance, diagnostics and technical response.
Governance capability
Monitoring, audit trails, integration, protocols and continuous improvement.
The objective is not dependence on the intervention provider.
It is an institution capable of operating, understanding, maintaining and continuously improving the strengthened operating model.
What the capability must prove
Transport reliability
Timely, traceable and dependable movement
System reliability
Available, monitored, maintainable and resilient
Clinical material integrity
Validated transport conditions for intended materials
Lifecycle performance
Controlled energy, maintenance, durability and replacement burden
The targets are not universal numbers.
They are defined by what the institution needs the capability to accomplish.
The deeper technical question
The PTS question is ultimately not:
Which transport technology should the hospital buy?
It is:
What must become technically visible, measurable and reliable for tracked material flow to create meaningful institutional value?
Question
Architecture
Measurement
Reliability
Lifecycle performance
Institutional value
That answer determines the architecture.
The architecture determines what can be measured.
Technical performance determines what can be relied upon.
And lifecycle performance determines what that capability is worth over time.
What could this technical capability mean for your institution?
Confidence extends beyond the specification.
The performance of a PTS depends not only on its architecture, but on the experience behind the technology, the evidence accumulated across healthcare environments, and the engineering relationship supporting its implementation.