BIO

My career in electronic security did not begin with a carefully planned path. It began as a part-time job while I was in college.

Like many people entering the trades, I started as a helper—carrying tools, working in attics and crawl spaces, and learning by watching experienced technicians. That opportunity developed into a career spanning more than four decades and nearly every operational and sales position within the electronic security industry.

Along the way, I worked as a technician, installation manager, operations manager, salesperson, sales manager, district sales manager, branch manager, and sales director. Each position provided a different view of the industry, but the field continued to provide the most important lessons.

Shortly after starting Security Systems Inc., a manufacturer contacted me to demonstrate a door contact designed to resist a common defeat technique. It was a technique I had never encountered.

After the meeting, I returned home and repeated the demonstration on my own alarm system.

It worked.

What unsettled me was not simply that the device could be defeated. It was the realization that, after years of working in nearly every area of the industry, no one had ever shown me that the vulnerability existed.

I had trusted my own alarm system to protect my family. I had also recommended and installed similar technology for customers. Until that afternoon, I believed those systems performed the way I had been taught they performed.

That experience raised a question that has influenced my work ever since:

If something this fundamental had escaped my attention, what else were we assuming?

As I began looking more closely, I found that systems appearing nearly identical on the surface could reflect very different standards of design, installation, supervision, documentation, and service.

One project that reinforced this lesson involved upgrading the fire alarm system at a large manufacturing facility. During the work, we discovered that multiple field detection circuits had previously been removed from service. Resistors had been installed near the control panel so the circuits continued to appear normal even though portions of the facility’s detection were no longer operating.

Management had no knowledge of what had been done.

The control panel indicated that the system was normal. The field conditions told a very different story.

Experiences like that taught me that indications, documentation, listings, and routine tests are important—but they are not always the same as verified performance.

They also taught me never to assume that the first explanation is the complete one. Some of the most difficult system problems involve several unrelated conditions occurring at the same time. Experience may point an investigation in the right direction, but conclusions should follow evidence.

Throughout my career, I have found that one carefully conducted demonstration is often more persuasive than a hundred opinions.

A demonstration changes the conversation from:

“Do you believe this can happen?”

to:

“Now that we have observed it, what should we do about it?”

That distinction has shaped the way SSI works with property owners, pharmacies, commercial facilities, high-value retailers, schools, municipalities, insurance professionals, and other organizations throughout Virginia.

We do not expect clients to accept a recommendation merely because we make it. Whenever appropriate and authorized, we prefer to explain the concern, demonstrate the relevant condition, document what occurs, and discuss the available options and trade-offs.



The objective is not to frighten anyone or suggest that risk can be eliminated. It is to replace unsupported confidence with a clearer understanding of how protection is expected to perform—and where its limitations may exist.

Security Systems Inc. remains a family-owned Virginia security company that designs, installs, upgrades, monitors, and services commercial electronic security systems.

My work has also developed beyond conventional system installation.

I remain particularly interested in how security systems behave during power loss, communication disruption, shared-circuit faults, deteriorating battery conditions, tampering, and deliberate attack. That work led to SSI’s development of Alarm Resilience Assessments and its broader Protection Verification approach.

These services are based upon a straightforward principle:



Protection should not be judged only by how a system operates when everything is normal. It should also be evaluated by what happens when something goes wrong.

After more than four decades in electronic security, I remain actively involved in the field. I continue to learn from unusual service conditions, difficult system problems, conversations with clients, and demonstrations that challenge accepted assumptions.

I am not interested in presenting myself as someone who has every answer. The more useful contribution is often knowing which questions have not yet been asked.

When reviewing technical information, I frequently read the limitations as carefully as the instructions. Understanding what equipment cannot do may be just as important as understanding what it can.

If there is one principle I hope to preserve within SSI for the next generation, it is this:

Do not rely upon assumption when performance can be examined.

Our ambition has never been to become the largest security company in Virginia. It is to build a company trusted to ask difficult questions, disclose what it observes, acknowledge what it cannot conclusively determine, and approach the work correctly.



After more than forty years, I remain just as interested in the next unanswered question as I was when I first entered the industry.

A security system is normally evaluated by confirming that it arms, detects an expected condition, activates the intended notification devices, and transmits a signal. Those functions are important, but they do not necessarily reveal how the system will perform when conditions are no longer normal.

What happens if a shared communication circuit is faulted? If auxiliary power is interrupted? If a communication path fails? If battery voltage deteriorates? If an accessible component is tampered with or deliberately attacked?

At Security Systems Inc., we believe those questions deserve more than assumptions.

Our approach is to examine how protection actually behaves under selected real-world and abnormal conditions. When appropriate and authorized, we use structured, non-destructive demonstrations to observe what occurs at the protected property, what information reaches the central station, and whether the resulting response is consistent with the protection the owner believed was present.

This does not mean that every system must withstand every possible failure or method of attack. No electronic security system can eliminate all risk. It does mean that material limitations should be understood, disclosed, and considered as part of the design, evaluation, and decision-making process.

That philosophy influences the way SSI approaches every project:

• We ask how the system is expected to behave when something goes wrong—not only how it operates under ordinary conditions.
• We consider supervision, reserve power, communication integrity, fault isolation, tamper exposure, serviceability, and response procedures.
• We distinguish observed performance from manufacturer representations, certifications, listings, and assumptions.
• We explain known limitations and practical trade-offs in plain language.
• We recommend corrective options according to the client’s property, operations, risk, and priorities—not simply according to a standardized equipment package.

For more than four decades, one question has repeatedly guided our work:

How do we know?

Whenever reasonably possible, the answer should come from evidence: careful evaluation, direct observation, proper documentation, and a willingness to challenge assumptions before a failure or loss reveals them.



That is the foundation of SSI’s approach to Alarm Resilience and Protection Verification.

Our goal has never been to become the largest security company in Virginia. Our goal is to earn trust by approaching each system carefully, disclosing what we know, acknowledging what we cannot conclusively determine, and doing the work correctly.

Because meaningful protection should not depend upon confidence alone.



It should be understood.