Csw Technologies Inc. keeps a small, deliberate alarm control room at 1 Queen St N, Tilbury - N0P 2L0, Canada (CA), where every client system is watched by a named person and every alarm ends with a written outcome. Our Tilbury control room holds the roster, the runbook binder and the pager schedule for each engagement, so nothing depends on one engineer remembering a password at three in the morning. Read the six control room services
Book an on-call handover sittingWho we are
Csw Technologies Inc. is a computer systems design practice working in professional, scientific and technical services. We design integrated systems for small operators who cannot afford a second team of engineers, and we keep the monitoring duty in house rather than handing it to a call centre. The work is unglamorous by design. An engineer writes a runbook page, a second engineer reads it back, and the page lives in a binder that the next shift can actually find.
Our Tilbury control room at 1 Queen St N is the physical anchor for that promise. It holds the alert roster, the escalation map and the pager schedule for every client we watch. When a disk fills at midnight, the person who answers already knows which database owns that disk and which page in the binder covers the recovery. You can reach the desk on +19285925347 during business hours, and the overnight pager path is explained in full on our services page.
We deliberately keep the scope narrow. We do not market ourselves as a data centre, a cybersecurity auditor or a help desk. We build integrated systems, we document them, and then we watch them with the same care we would want for our own tools. Every engagement ends with a binder the client owns, a roster the client has signed, and a handover meeting that takes place before the first invoice.
Section W / the working binder
These are the duties our control room performs on a recurring schedule. Each tab is a page in the client binder, and each page names the person, the trigger and the written outcome. Read the detailed brief on the services page.
A dedicated bay watches uptime, disk pressure and certificate expiry for each portfolio. The bay is staffed by a named engineer who reads the board at the top of every shift.
The roster is checked daily against the live on-call calendar. Anyone who should be reachable at two in the morning is confirmed reachable that afternoon.
Each incident class owns a desk and a printed page. The desk is where the responder sits, and the page is where the first five decisions are written down in advance.
Pagers are fired on a published schedule and answered in sequence. A silent pager is a finding, not an inconvenience, and it is logged the same day.
The escalation map is redrawn whenever staffing changes. Every arrow on the map must resolve to a phone that a real person answers within the agreed window.
Shifts change face to face or by a structured call. Open alarms, pending changes and fragile systems move from the outgoing engineer to the incoming one in words.
Csw Technologies Inc. opens its on-call handover window at the top of every shift, and the outgoing engineer stays on the line until the incoming engineer has read the binder back aloud.
How the work is held
The first habit is naming. Every alarm has an owner, and the owner is written in the roster next to a working number. An alarm without an owner is treated as a defect in the roster rather than a defect in the system. The second habit is rehearsal. The pager test windows exist because a pager that was never fired is a rumour, not a safety net. We fire them on a published schedule and record who answered and how long it took.
The third habit is the readback. Runbook pages are read aloud from the desk to the person who will use them, and anything that cannot be read aloud is rewritten. That single rule has removed more ambiguity from our clients than any dashboard we have ever bought. The incident runbook desks are arranged so that the responder sits facing the binder, with the monitor wall behind them, and the escalation map within arm reach.
The fourth habit is the review. Once a month we sit with the client and walk the escalation map from the first cell to the last. If a name has changed, the map changes that afternoon. If a number rings out twice, the map is rebuilt rather than patched. This is slow work, and we consider the slowness a feature.
Who the bays are for
Most of our clients run between three and forty staff. They have a booking engine, a small database, a storefront and a few integrations that were written years ago by someone who has since moved on. They do not need a twenty-four hour security operations centre. They need a disciplined pair of eyes, a written page for the bad night, and a phone number that a person actually answers. That is precisely the scope we hold.
Our site watch bays watch the thin layer that matters: whether the storefront resolves, whether the certificate is valid, whether the disk is filling and whether the nightly job finished. We do not pretend to monitor every metric. We monitor the small set of conditions that predict a bad morning, and we write down what we did when one of them fired. The result is a record the client can read without an engineer sitting beside them.
Because we are also a systems design practice, the same engineers who watch your systems are the ones who documented them. That overlap is deliberate. It means the person who answers at night is not reading someone else notes for the first time. They helped write them.
Tell us which system keeps you awake and we will tell you honestly whether a watch bay is the right answer. If it is not, we will say so and point you somewhere better.
Open a contact request →