No handover notes yet. Tap Edit to leave notes for the incoming shift.
Describe your problem
Speak or type — we'll find the issue and walk you through the fix
Tap to speak
Voice dictation needs a supported browser and a secure connection.
Describe the problem
Common problems — tap to select
📤 Send a Carrier
Estimated Arrival
—
—
Currently In Transit
0
Your Service Provider
Tube System Service Co.
Service Contract · Active
Before You Call — Checklist
Complete these steps before calling — it helps your technician diagnose faster and may save you a dispatch fee.
Service Request Details
Issue Summary
Priority
▼
What have you tried?
Response Time SLA
2h
Critical
System down
8h
High
Zone impacted
48h
Normal
Degraded service
Service Contacts
Zendesk Integration
Not Connected
Configure Zendesk to log service tickets automatically
Zendesk Subdomain
Agent Email
API Token
Engineering Insights
Recurring faults, MTTR, top parts by device family, and export tools for engineering documentation.
Incidents
0
Open
0
Avg MTTR
0m
Billing
Trial
ARR
$0
Trial Days
0
Business Value
Recurring Faults
Parts by Device Family
Recent Resolutions
Export
Subscription Controls
Employee Login Activity
Team Accounts (Manager Controls)
Create Team Login
▼
Shift Handover
Outgoing Technician
Notes for Incoming Shift
Handover Checklist
New Work Order
Device: —
Issue Description
Priority
Assigned To
Event Log
System activity & alarm history
—
Today
—
This Week
—
Avg Delivery
⚠️ Active Faults
2 issues need attention
🔍 Missing Carrier
Last sighted · 4 minutes ago
🚨 Carrier Did Not Arrive
A carrier was dispatched from STN-10 · Hospital Lab (Main) to STN-4 · 4th Floor CCU East and did not arrive within the expected delivery window.
Last Known Location
🔀
DIV-114
Last diverter to register the carrier
Last Seen
Location
3rd Floor — Room 310
Type
6-port Diverter · Zone 1
Port Used
Port 4 → toward 4th Floor riser
Sighted
4 min ago · 10:43 AM
Next Expected Device (Not Confirmed)
🔀
DIV-118
Should have received carrier — not confirmed
No Signal
Location
4th Floor — CCU 4S405
Network
✗ Offline — cannot confirm receipt
Where to Search
Work through these steps in order. Stop as soon as you find the carrier and note where it was located.
1
🔀 Inspect DIV-114 — 3rd Floor, Room 310
This is the last diverter that confirmed the carrier. Start here.
▸ Locate the DIV-114 diverter housing on the 3rd floor near Room 310.
▸ Using a 7/16" nut driver or flathead screwdriver, remove the cover screw(s) and open the front service panel of the diverter.
▸ Visually inspect all ports and the interior housing for a jammed or lodged carrier.
▸ Check that all port gates are fully seated and not obstructed by a carrier fragment.
IF FOUND:Remove the carrier, re-secure the cover screw(s) with your 7/16" nut driver or flathead, and tap Mark as Resolved below.
2
🪜 Inspect the Tube Riser — 3rd to 4th Floor
The vertical riser between floors is one of the most common jam points in the system.
▸ Locate the riser tube access point in the 3rd floor utility corridor near Room 310.
▸ Listen closely at the tube opening — a lodged carrier will sometimes block airflow and produce a hissing sound.
▸ If accessible, use a flashlight to look up the riser for a carrier blocking the tube.
▸ Check the 4th floor entry point of the riser tube for any carrier that may have partially entered but stopped.
⚠ CAUTION:Do not attempt to push a carrier through a riser by hand. Shut the blower down before reaching into any tube opening.
3
🔀 Walk to DIV-118 — 4th Floor CCU, Room 4S405
⚠ This diverter is offline — remote monitoring is unavailable. Physical inspection is required.
▸ Proceed to the 4th Floor CCU and locate the DIV-118 diverter at Room 4S405.
▸ Using a 7/16" nut driver or flathead screwdriver, remove the cover screw(s) and open the diverter housing. Manually check each of the 4 ports for a carrier.
▸ Manually actuate each gate arm to confirm full travel — a stuck gate can trap a carrier inside.
▸ While here, also check the network connection on the rear of the diverter — the cable may be loose or disconnected.
IF FOUND:Remove the carrier, restore the gate to its home position, and re-secure the cover screw(s). Tap Mark as Resolved.
4
🏥 Check STN-4 — 4th Floor CCU East Station
⚠ Carrier sensor is offline — arrival cannot be confirmed automatically.
▸ Go to the STN-4 station in the 4th Floor CCU East nurses area.
▸ Use your CAT 30 key to unlock and open the station door. Check the receiving bowl — the carrier may have arrived undetected due to the offline sensor.
▸ Also check the station inlet tube just inside the door for a carrier that partially entered but did not fully seat. Re-lock the station door when done.
▸ Check with nursing staff — they may have already retrieved the carrier and not yet acknowledged the alert.
IF FOUND:Confirm the carrier contents are intact. Return the carrier to service and tap Mark as Resolved.
5
🏥 Check STN-5 — 4th Floor CCU West Station
STN-5 shares DIV-118 with STN-4. A misrouted carrier could have been sent to the wrong station.
▸ Go to the STN-5 station in the 4th Floor CCU West nurses area.
▸ Use your CAT 30 key to unlock and open the station door. Check the receiving bowl for the missing carrier.
▸ If found here, confirm the carrier was misrouted by DIV-118 due to its offline status causing a gate default position error.
IF FOUND HERE:Deliver the carrier to the intended destination (STN-4 CCU East), then log a misroute incident and note DIV-118 for repair.
6
📞 Carrier Not Found — Escalate
If you have completed all steps above and the carrier has not been located, escalate to your supervisor.
▸ Document the steps you completed and the time each location was checked.
▸ Report the missing carrier and contents to the originating department (Hospital Lab).
▸ Contact Pevco technical support if a mechanical failure is suspected in an inaccessible section of tube.
▸ Do not mark as resolved until the carrier and its contents are physically accounted for.
These devices are not connected to the network. The system cannot confirm carrier arrivals or remotely control diverter routing on the 4th Floor CCU. A physical walk-down is recommended.
Affected Devices
🔀
DIV-118
4-port Diverter
No Network
Location
4th Floor — CCU 4S405
Type
4-port Diverter · Zone 1
Network
✗ Not Connected
Action
Manual routing only. Verify carrier passage physically at this diverter.
⚠️
STN-4 · 4th Floor CCU East
Carrier Station
Issues
Location
4th Floor · CCU East Wing
Zone
Zone 1 — Hospital Wing
Network
✗ Not Connected
Sensor
✗ Carrier sensor not working
Action
Inspect the carrier sensor and perform a function test. Replace if necessary.
⚠️
STN-5 · 4th Floor CCU West
Carrier Station
Issues
Location
4th Floor · CCU West Wing
Zone
Zone 1 — Hospital Wing
Network
✗ Not Connected
Sensor
✗ Carrier sensor not working
Action
Inspect the carrier sensor and perform a function test. Replace if necessary.
Device
Issue
Note
New Note
PM Checklists
New PM
0 / 0
✏ Edit PM Details
PM Name
Date
Technician Name
‹
›
SITE CONFIGURATION
Import a config file to set up a new site
Currently Loaded Site
No site loaded
Upload a configuration file to populate the app
Tube System Provider Theme
Active
Director Setup Wizard
Manage Loaded Config
After uploading a config, you can clear it or add/remove devices without creating a new file.
Danger Zone
Use this only when you want to wipe the currently loaded site and return to blank setup.
Visual Builder
Build your own tube system
Open a dedicated builder page to create zones, add devices, and wire pipe connections with a live visual map as you work.
🧩
Add ZonesDrop In DevicesConnect Pipes
Upload New Configuration
📂
Tap to choose a file
Accepts .json configuration files
OR
Emergency Backup Export
📄 Download Current Backup Config
Download the currently loaded site configuration as your emergency backup file.
🔌 Live System Integration
Connect through the hospital server, vendor API, or a local bridge so PneumaControl can pull live status, carrier tracking, and faults from Atlas or Swisslog systems.
Not Connected
Configure a connection below to enable live data
System / Vendor
▼
Hospital Server IP & Port
:
Type the hospital server IP and port. PneumaControl will auto-build the URL and ping to verify.
Authentication
▼
Poll Interval
▼
Last Poll Log
Subscription and Access Policy
$1200/year plan with 3-month trial
Trial running
Add Contact
Name
Role / Title
Tier
▼
Phone
Email
Availability
📦 Carriers In Transit
Loading...
Device
PM Procedure
Dedicated Layout Studio
Visual Tube Builder
Shape the site layout, drop in every device, and route pipe connections from one focused workspace built for quick planning and live system mapping.
Plan zones
Place devices
Route pipes live
Sketch · Connect · Publish
Build your own tube system with a live visual map.
Create zones, define each blower, add diverters and stations, then connect the pipe routes while the layout updates in real time so the final configuration reads like the real network.
BLW
DIV
STN
Live routing preview
0Zones
0Devices
0Pipe Links
Site Basics
Name the site before you start laying out the zones. This updates the live app shell immediately.
Active Zone Workspace
Pick the zone you want to edit. Device placement, pipe routing, and removal tools below all work on this zone.
Create your first zone to begin the layout.
Add Zone
Each zone gets its own blower root. Use zones for towers, clinics, or separate hospital wings.
Device Lab
Drop a new diverter or station into the active zone. Assign its parent connection as you create it.
Network Configuration
Pipe Connection Studio
Rewire the active zone visually by choosing a source node and the device it should feed.
Remove Device
Clean up the active zone. Removing a diverter will also clear any stations still linked to it.
Live Tube Map
Every change below is reflected live so you can see the blower roots, diverter branches, endpoint stations, and pipe links before exporting the config.
🔧 TECHNICIAN REFERENCE
Configuration schema and integration reference
Configuration File Format
The config maps the physical layout of the tube system. Each zone has one blower — the blower is the root of that zone's network. Diverters branch from the blower or from other diverters (upstreamId). Stations are the leaf endpoints, each attached to a specific diverter.
The app polls a bridge server or controller at a configurable interval. The endpoint must return a JSON array of device status objects or a root object with a recognizable device list key.
Polling interval is configurable in the integration settings (default 5 s). The app auto-retries on transient errors with exponential back-off up to 60 s.