// SECTORS · HANS STUDY · CANADA AND THE UNITED STATES
Who the practice works for
Environments where the cost of getting infrastructure wrong is not measured in inconvenience. The engagements are the same across all of them; what changes is the framework the work is held to, the procurement it has to survive, and what happens when the system stops.
Fifteen years of this work has been almost entirely in the six sectors below. That is not a marketing decision. It is where the systems are complex enough, and the consequences serious enough, that an owner will pay for an independent technical voice rather than take the integrator's word for it. Each page describes what is different about designing and assessing in that sector, and which engagements tend to be needed.
Sectors
Government and public sector
Federal, provincial, and municipal infrastructure, where procurement rules, GO-ITS and ITSG-33, and long asset lifecycles shape every design decision.
Defence suppliers
Canadian defence suppliers working toward CPCSC, and toward CMMC 2.0 when they sell to US primes, and the physical security and network controls those programs actually require.
Law enforcement and public safety
Police services, dispatch, evidence handling, and the systems that cannot be allowed to fail during a call.
Critical infrastructure
Utilities, water, energy, and the OT environments where NERC CIP and NIST SP 800-82 govern how the network and the security system may be built.
Transportation and ITS
Transit, airports, and intelligent transportation systems, with the distributed networks and outdoor conditions they bring.
Enterprise multi-site
Organizations operating at more than one location, where federation, standards, and a network that behaves the same at every site are the whole problem.
Not on the list
Retail, hospitality, and residential are well served by integrators and rarely need this practice. Healthcare and education sit between: a single campus is usually an enterprise multi-site problem, and a health network with regulated data is closer to critical infrastructure. If your sector is not named above and the system is one where a failure cannot go unnoticed, the scoping call is the place to find out whether it fits.
Start with the sector page
Each one ends in the engagements that usually apply and a straight route to a scoping call.