Start your EVOTECH request in under a minute.
Commercial Surveillance Installation in Katy, TX 77491
Most commercial camera systems do not fail on the night something happens. They fail months earlier, when somebody decided where the cameras would point and how wide they would see. This page is about that design work for Katy businesses — pixel density, night performance, retention math and power budget — because those four decisions separate footage a detective can use from footage nobody can.
Footage that identifies someone, and footage that does not
Almost every system we are asked to replace in Katy failed at the same moment: something happened, the owner pulled the recording, and the person on screen could have been anybody.
The cameras worked. What went wrong was the plan. A surveillance system is not a quantity of cameras, it is a set of answers to specific questions, and each question demands its own geometry:
- Was anyone here at 2:14 a.m.? A wide overview is enough — presence, direction of travel, a trustworthy timestamp.
- Which of my six employees opened that drawer? Recognition of a known person: enough detail to separate people you already know by build, clothing and movement.
- Who is this stranger, and can an investigator work from this still? Identification of an unknown face — a different camera, at a different distance and height.
- What is that plate? Not a general camera at all. Plates move and are retroreflective; they need a dedicated camera aimed along the lane with a shutter fast enough to freeze the vehicle.
Sold as eight identical cameras on eight identical mounts, a system answers the first question eight times and the other three not at all. Designed question by question, the same budget usually buys fewer cameras — and every one that survives the cut is somewhere it does work.
Pixel density: the number that decides your camera count
Pixel density is the honest way to talk about coverage, and the arithmetic is simple enough to do standing in the parking lot: take the horizontal resolution of the sensor and divide it by the width of the scene, in feet, at the distance you care about.
A 4 MP camera puts roughly 2,560 pixels across the frame. Aimed at a twenty-foot entry that is about 128 pixels per foot. Aimed across a hundred-and-twenty-foot parking row, the same camera delivers about 21. Those two numbers sit on opposite sides of every threshold that matters.
| Design target | Roughly | What you actually get |
|---|---|---|
| Detection | ~20 px/ft | A person is there and moving that way. Not who. |
| Observation | ~30 px/ft | Clothing colour, vehicle type, roughly what happened. |
| Recognition | ~40–50 px/ft | You can tell one known employee from another. |
| Identification | ~60–80 px/ft | A stranger’s face, usable as evidence. |
| Plate capture | 60+ px/ft, dedicated | Only with shutter control and a lane-aligned angle. |
Resolution does not rescue a bad angle. A 4K camera has about 3,840 pixels across — fifty percent more than 4 MP, not four times more — so it buys a wider scene at the same density, not magical detail in the far corner of a lot. That is why the one camera that covers everything keeps disappointing people. The alternative costs no more: one wide camera for context, plus a tight camera on each choke point — the door everyone must pass, the lane every car must drive, the register, the back dock.
Height belongs to the same calculation. Past roughly twelve feet a camera aimed at a face is mostly recording the top of a head, which is why so much warehouse footage shows a hat and nothing else. Keep the overview high, but put the face-capture camera at seven to nine feet at the pinch point, angled slightly down.
Night performance, IR reach and glare at a Katy storefront
Commercial night scenes here are rarely dark. They are unevenly lit: one pole light in a corner, a sign washing one wall, headlights sweeping the lens every few minutes, and a black void everywhere else. Three different things get confused when people shop for good night vision.
Sensor and aperture beat megapixels
Light collection is physical. A larger sensor and a faster lens — f/1.6 against f/2.0 is close to a full stop — do more for a dark scene than any processing. Resolution is not free either: on the same size sensor an 8 MP camera divides the same light among twice as many photosites as a 4 MP one, so after dark the lower-resolution camera is often the cleaner picture.
Infrared range ratings are a best case
Published IR distances are measured against a reflective target, straight down the axis. Spread across a wide scene the same illuminator gives a hot centre and dark edges, and anything close to the lens blooms and drags the exposure down for the whole frame. IR also blows out retroreflective surfaces: hi-vis vests, road signs and licence plates return pure white, which is why a camera that reads plates at noon often reads nothing once IR takes over.
Dynamic range at the glass
Point a camera at an entry door with Texas daylight behind it and one sensor must expose a dim interior and a blinding lot in the same frame; the customer walking in becomes a silhouette. True wide dynamic range combines multiple exposures and genuinely helps; the digital version on cheaper cameras only re-maps tones. Geometry is cheaper than either — mount off the axis of the door and add fill light in the vestibule.
How many days you can really keep
Retention is not a setting you choose. It is storage divided by bitrate, and the sum is worth doing before anyone quotes a recorder.
One megabit per second of recorded video is about 0.45 GB per hour, so roughly 10.8 GB per camera per day. A 4 MP stream at 4 Mbps is therefore about 43 GB a day; sixteen of those is around 690 GB a day, and thirty days is a little over 20 TB before any redundancy overhead.
- Smart codecs and variable bitrate. H.265 with a dynamic frame structure is very efficient on a still stockroom and much less so on a busy scene. Retention is set by your busiest cameras, not the average.
- Motion-only recording. It saves space right up until the thing you needed happened while nothing tripped the detector. Continuous at a reduced frame rate, with full rate on motion, is the better trade.
- The drives. Surveillance-class drives are specified for sustained sequential writing and a high annual workload; desktop drives are not, and with no redundancy the whole history goes when one fails.
Decide the number of days first — thirty to ninety is the common commercial range — then size storage to it. And if the recorder’s clock is wrong, every timestamp on every export is arguable, so we set network time synchronisation at handover.
PoE budget, cable specification and the 328-foot wall
- Ethernet stops at 328 feet. One hundred metres, patch cords included. A tilt-wall building off the Grand Parkway crosses that without trying. The fix is an intermediate switch in a protected, powered location, or fibre — not a longer cable and optimism.
- Copper-clad aluminium is the most common defect we find. CCA looks identical, costs less and is not compliant cable. Its resistance is higher, which matters enormously when the same conductors carry the camera’s power, and the strands are brittle where they terminate. Solid bare-copper Cat6 costs a little more exactly once.
- PoE is two budgets, not one. 802.3af gives about 15.4 W at the port and 12.95 W at the device; 802.3at (PoE+) is roughly 30 W and 25.5 W, and a pan-tilt-zoom with a heater wants PoE+. Separately the switch has a total power budget: a twenty-four-port switch rated at 190 W cannot feed twenty-four PoE+ cameras, and the symptom is cameras rebooting at dusk when every illuminator comes on at once.
- Copper between separate buildings is a lightning path. Running Ethernet outdoors between two structures bonds their grounds together and invites surge damage, which this part of Texas supplies generously. Use fibre, or proper bonding with surge protection at both ends.
- Jacket rating follows the space. Cable in a shared return-air plenum must be plenum rated; vertical runs between floors are riser rated. Not a detail an inspector overlooks, and not something you want to rip out later.
Five Katy building types, five different camera plans
77491 is one of Katy’s post-office-box ZIP codes, so a mailing address in it tells us very little about where a building physically stands — we design from the street address and a walk of the site. Commercial property around Katy falls into five families, and each rewrites the plan:
- Inline retail in a strip centre. Shared soffits, a demising wall each side, a landlord with opinions about the storefront, and glass across the front producing the silhouette problem all day. Recorder in a locked back room, not the cabinet under the till where it leaves with the cash.
- Tilt-wall flex and warehouse near the I-10 frontage and the Grand Parkway. Exposed bar joist and metal deck, concrete panels needing drilled anchors rather than screws, and dock doors that are the real perimeter. Overview from height, identification cameras low at man-doors and dock stairs.
- Medical, dental and professional suites. Hard-lid drywall ceilings with no access above them, so pathways are planned rather than discovered on a ladder — plus zones where cameras must not look, including treatment areas and any screen showing patient information.
- Freestanding restaurants, drive-throughs and auto service. Grease, heat and vibration, a drive lane wanting dedicated plate capture, and a kitchen line wanting a wide overview for training and liability.
- Older Katy near the rail line and Avenue D. Masonry and early metal buildings, generations of abandoned wiring in the walls, and frequently no usable pathway at all.
One constant across all five is audio: most recorders ship able to capture it and most commercial systems should be configured not to. We disable it by default.
What EVOTECH does on the design visit
- We ask what you want to be able to prove. Shrinkage at the register, a slip-and-fall claim, after-hours entry, a delivery dispute, who was in the yard. That list drives everything after it.
- We walk the site and mark choke points, then measure the distances that decide lenses — door width, lane width, counter-to-camera, dock-to-column. Pixel density is calculated per position, not assumed.
- We look at the worst hour we can. Where the sun sits in the afternoon, which doorway faces west, where the lot is unlit. Sun angle moves with the season; a camera that is fine in January can wash out in June.
- We trace pathways and find the equipment home — where cable can legally run, where the recorder lives locked and ventilated, and whether the switch needs battery backup so a brownout does not punch a hole in your timeline.
- We hand you an itemised written quote, position by position, with what each camera is for. If something you asked for is not achievable at sensible cost, that is in the quote too.
Design mistakes that become callbacks
- Every camera at the same height with the same lens. Fast to install, useless for identification.
- The recorder where the thief is already going. If it can be unplugged and carried, it will be.
- One credential shared by everyone — including the installer and the employee who left in March. Named accounts with sensible roles cost nothing and settle arguments.
- Default passwords and an exposed port. A camera reachable from the open internet on a factory password is not security, it is liability.
- Nobody ever practised an export. The first attempt should not be with an officer standing at the counter; we walk staff through a real one at handover.
- Spiders. Webs across a lens are the leading cause of nuisance alerts outdoors, and a camera mounted directly under a security light collects them all season.
What moves the number on a 77491 quote
We do not publish prices, because a number without a site is a guess and guesses get corrected upward later. What genuinely moves an itemised quote:
- How many questions the system must answer — identification positions cost more than overview positions.
- Ceiling type and whether a pathway exists. Accessible grid is quick; hard-lid drywall, tilt-wall concrete and finished masonry are not.
- Cable distance, and whether a run needs an intermediate switch, conduit or fibre.
- Retention target and redundancy, which set the recorder and the drives.
- After-hours scheduling, and whether exterior work needs a lift.
- Any compliance requirement you operate under, including equipment restrictions that apply to some organisations holding federal contracts or funding.
Related services
Frequently asked questions
How many cameras does a small Katy business actually need?
Can one camera cover the whole parking lot?
Will the system still record if the internet goes out?
Do we need commercial-grade equipment, or will consumer cameras do?
Do you service systems somebody else installed?
Free on-site surveillance design visit in Katy 77491
Tell us what you need to be able to prove and we will walk the building, calculate pixel density position by position, and hand you an itemised written quote with a reason next to every camera. Licensed, insured, and working in Katy since 2004. Call (832) 359-2425.
Book a Free Consultation
Ready for EVOTECH to help?
Before you leave, send the quick version. We will review the page you came from and reply with the clean next step.
