A security consultant walks onto a finished site plan three weeks before tender close and asks where the vehicle barriers go. The driveway, the landscaping and the sightlines are already locked. Whatever goes in now has to fit around decisions nobody made with security in mind.
This happens often enough to have a name in the industry: security as a punch-list item. It shows up at the end of a project instead of the start, treated more like a finish than a structural decision. For a facility with real security requirements, a data centre, a courthouse, a transit hub, that ordering matters more than the line item ever will.
Key Takeaways
- Binns Canada supplies rated perimeter security across eight sectors, including data centres, correctional facilities, transit infrastructure and healthcare sites.
- LPS 1175 grades forced-entry resistance across tiers from SR1 to SR3, while PAS 68 and IWA 14-1 rate vehicle barriers by impact speed and vehicle mass.
- Binns Canada holds Royal Architectural Institute of Canada Corporate Affiliate status and runs an Alberta Association of Architects-approved continuing education session on perimeter security as a design input.
- The practical next step: bring a security specifier into concept design, not tender review, so the site plan can absorb the requirement instead of working around it.
What’s the Right Time to Bring Security Into a Design?
Security specifications belong in schematic design, alongside structural and civil engineering, not after the drawings are finalized. A rated fence line, a vehicle barrier or an automated gate needs clear zones, foundations and sightlines that are far cheaper to plan for than to retrofit. Two habits make the difference: naming the required security rating before floor plans lock, and putting a specifier in the same early meetings as the landscape architect.
Which Sectors Feel This the Most?
Some building types carry security requirements from day one rather than discovering them partway through design. Binns Canada’s perimeter security expertise spans several of these sectors, each with a different threat profile:
- Data centres and critical infrastructure
- Government and defence facilities
- Correctional facilities
- Transportation and transit infrastructure
- Utilities and energy sites
- Healthcare and mental health facilities
- Sports, entertainment and commercial developments
Each carries a different threat profile, which is exactly why the rating and layout decisions need to happen before the site plan is finished, not after.
Why Does Security Usually Get Added Last?
On most projects, a security supplier is brought in once the site layout and building envelope already exist. By that point the driveway width, the grading and the fence line are set, so the supplier is choosing from what fits rather than what the risk profile actually calls for. It is a workflow problem more than a design failure. Security has traditionally been procured the way a finish is procured: quoted, compared and installed once everything else is built.
That workflow gets expensive when a site later needs a rating nobody planned for. A hostile vehicle mitigation barrier needs a foundation depth and a clear zone that a finished parking layout may not have room for. Moving that decision earlier removes most of the guesswork, and most of the change orders.
A Credit Built for the Design Community, Not the Trade Show
Binns Canada holds Corporate Affiliate status with the Royal Architectural Institute of Canada and offers a continuing education session approved by the Alberta Association of Architects, called “The Security Perimeter Solution from Risk Intelligence to Delivery.” The session walks through perimeter security as a design input: how a risk profile translates into a fencing standard, a barrier rating and a site layout, rather than a product catalogue to flip through once the drawings are done.
A CPD credit does not change how a fence gets built. What it does is put the conversation in front of the people making layout decisions, months before a tender goes out. That is a different way of running the sales conversation than most perimeter security purchases follow, and it points at where the industry is likely heading: fewer post-construction retrofits, more design-stage input.
What Should a Design Team Ask a Security Specifier Early?
A short list of questions, asked during concept design rather than tender review, avoids most of the expensive surprises later:
- What threat profile does the site’s use and location actually justify?
- Which certification standard applies, and at what rating band?
- Does the fence line or barrier placement conflict with grading, drainage or landscaping already in progress?
- Who installs the system, and are they trained on it specifically?
That last question matters more than it sounds. Binns Canada does not install its own systems; delivery runs through a network of contractors it trains directly, which is worth confirming with any supplier before a project locks in a construction schedule.
Bring the Conversation Forward
The fix here is not more security spending. It is moving the same conversation earlier, back to the point where a floor plan can still absorb it. A design team weighing elevated security requirements on an upcoming project gets more out of a specifier at the concept stage than out of three competing quotes at tender close.
Binns Canada, based in Calgary, works with design teams across Canada and the United States on exactly this kind of early-stage planning. For a project with real perimeter requirements, that is a conversation worth having before the drawings are locked, not after.
