Architecture review
Independent technical review of the proposed architecture before the design is committed. Catches the design decisions that cause Genetec deployments to fail in predictable ways.
Search hans.study
Indexed across articles, news, KB updates, knowledge base, books, learning, and tools. Press Esc to close.
// GENETEC SECURITY CENTER CONSULTING · HANS STUDY · ONTARIO, CANADA
Architecture review, server and storage sizing, Synergis access control design, federation design, hardening, and post-deployment troubleshooting on Genetec Security Center. Independent of reseller and integrator incentives. Not a reseller, not an integrator, and no licence revenue. I work with integrators and end clients to make the deployment work for them.
A Genetec partner earns revenue from license sales and service contracts. An integrator earns on the installation. Both do necessary work, and both carry an incentive that points toward selling and deploying, not toward asking whether the design is right. I sit outside that. No margin on licences, no margin on the install, so platform selection and design review carry no hidden pull. If Genetec is the right fit, the advice says so. If it is not, the advice says that too. I work alongside the integrator and on behalf of the end client, which gives the deployment a second technical voice that answers only to whether it will hold up.
Genetec Security Center is the most capable unified security platform in the market. It is also one of the more complex to deploy correctly. Deployments fail in specific and predictable ways. Archiver servers sized without accounting for peak recording load. Networks that put camera traffic on the same VLAN as other systems. Federation configurations that were never tested under realistic load. Most of these are design decisions, not platform defects, and they are identifiable in a review before deployment begins.
I have worked with Genetec Security Center in government, law enforcement, transportation, airport, and enterprise environments across Canada. The advisory draws on direct platform experience, including the failure modes that are not in the documentation.
Independent technical review of the proposed architecture before the design is committed. Catches the design decisions that cause Genetec deployments to fail in predictable ways.
Genetec deployments are routinely undersized. Sizing for Directory, Archiver, and Access Manager roles needs to account for the number of cameras, stream characteristics, retention period, concurrent client sessions, and peak recording load. Storage architecture needs to account for write throughput, redundancy, and what happens when a drive fails during active recording.
Door controller selection, credential technology, cardholder and credential management architecture, and the rules and scheduling logic governing who can go where. Integration with Omnicast for video-verified access events and with third-party hardware through the HID, Assa Abloy, and other controller ecosystems.
Multi-site federation that holds up under realistic load, not just in a test rack. Failover behaviour, latency budgets, and what happens to in-flight events during a federation link drop.
Independent technical oversight during integrator deployment. Submittal review, configuration audit during installation, and the documented record of what was reviewed and accepted.
Camera dropout that comes back on its own. Federation failures during peak load. Access control events that do not match physical access. Archiver health warnings dismissed until they become outages. Platform-specific troubleshooting that draws on how Genetec actually behaves under real operating conditions.
Vendor-agnostic CCTV and access control advisory across Genetec, C-CURE, Milestone, Avigilon, Axis, Bosch.
The network underneath Genetec. Most Genetec performance problems are network problems.
Integrated facility systems advisory for projects with Genetec at the centre and other systems converging on it.
Sizing requires knowing the number of cameras, stream characteristics, retention period, concurrent client load, and peak recording demand. Genetec's own sizing calculator gives a starting point but does not account for all real-world variables. Storage sizing in particular needs to account for write throughput and what the system does when a drive fails. Independent sizing review before equipment procurement.
Yes. Based in Ontario, working with organizations across Canada and the US. I have worked with Genetec Security Center in government, law enforcement, transportation, airport, and enterprise environments. Engagements range from single-site deployments to large federated installations with hundreds of cameras and multiple Archiver servers.
Genetec Security Center core, Omnicast, Synergis, and AutoVu. This includes integration between modules, hardware compatibility, and the network architecture the platform depends on. Third-party integrations through Genetec's SDK are also in scope.
Neither. No margin on licences, no commission on licence sales or services, and no margin on installation. I work alongside the integrator and on behalf of the end client. The advice reflects the requirements. Nothing else.
If the goal is a structured assessment of a running Security Center environment, that is its own engagement: a Genetec health check spans architecture, servers, storage, network, monitoring, security, cameras, integrations, and lifecycle, and ends in a prioritized remediation plan. The same ten areas are walkable in the Health Check Checklist, and a question-by-question audit tool with PDF export is available for self-service.
For a full list of the patterns the Health Check finds, see the 10 most common Genetec Security Center issues.
Practitioner-grade technical writing across architecture, AD integration, server tuning, and release reviews. Free.
Field-tested pattern review of the ten failures that show up most often. Companion to the Health Check.
Role placement, sizing, federation design, and the common design mistakes that pass commissioning and degrade under load.
OU structure, service accounts, gMSA, Kerberos, and the AD-side pitfalls that take Genetec environments down.
Power plan, SQL Server memory, NIC buffers, antivirus exclusions, video drive configuration, and camera stream settings.
What 5.14 brings, what is already here, and why the upgrade clock starts at 30 to 60 days, not day one.
Field-level look at 5.13.3.0. What changed, what is worth the upgrade, what is marketing fluff.
The hardening baseline I deploy. Windows server baselines, scoped Defender exclusions, service-account discipline, SQL, segmentation, certificates, and RBAC.
Architecture review, sizing review, deployment oversight, and post-deployment troubleshooting are all available as discrete engagements, each scoped and quoted on its own. The earliest point of engagement is also the highest-impact point.
Related work: a three-site Genetec rebuild with SQL high availability and a 24/7 SOC.
No commissions, no margin, no equipment for sale. The independence policy sets out exactly what that means.
All Genetec resources: services, tools, field writing, and case studies in one place.
Two tools run by default to help me understand how the site is used. You can turn either off at any time. Cloudflare's server-side analytics is always on and never sees your identity.