Column suitability and loading
Column condition, attachment strategy, loading and project-specific structural review.
Engineering developmentENGINEERING & ASSURANCE
Built to earn its place in the street.
OKLUS is being developed as public-realm infrastructure, not simply as a planted object. Engineering development will examine the structural, operational, environmental and maintenance requirements needed before suitable configurations can progress into controlled pilots.
Every location will present different constraints. Technical development therefore combines the OKLUS product architecture with site-specific assessment, competent engineering review and the requirements of the relevant asset owner or highway authority.
NON-NEGOTIABLE DESIGN GATE
No OKLUS configuration should be assumed suitable for a particular lighting column or public location until the required technical and authority-specific reviews have been completed.
ASSURANCE MATRIX
Ten questions that sit between a concept and a responsible pilot.
The matrix shows the areas being developed or reviewed without disclosing protected attachment geometry, internal construction, dimensions, calculations or manufacturing detail.
Exposure and local conditions
Assessment of exposed surface area, configuration and site-specific environmental conditions.
Engineering review requiredKeep statutory access practical
Lighting-column doors and statutory or service access must remain appropriately accessible.
Design requirementSeparate living and electrical systems
Living media, moisture and serviceable components must be appropriately separated from electrical infrastructure.
Engineering developmentControl water movement
Containment, drainage and potential interaction with the existing asset require controlled design.
Engineering developmentSpecify for public-realm exposure
Durability, weather exposure, corrosion behaviour and appropriate fire or material requirements to be reviewed.
Specification developmentReview the route, not only the unit
Clearance, visibility, accessibility, impact risk and route context considered before deployment.
Location-specific reviewPlan competent delivery
Installation methodology, traffic management where necessary and appropriately competent delivery partners.
Pilot planningDesign the operating model early
Planned access, intervention thresholds, living-media care and component replacement incorporated into the operating model.
Pilot developmentKeep reversibility in view
Ability to remove or replace the retrofit system and consider responsible component recovery.
Design principleASSURANCE ROUTE
Technical confidence is built in stages.
The relevant checks will depend on the host asset, location, authority and proposed pilot configuration. The route below is therefore a development framework, not a substitute for professional judgement.
- 01Screen the asset and route
Identify obvious exclusions, access constraints and information required for review.
- 02Define the proposed configuration
Clarify the pilot function without assuming a universal product specification.
- 03Complete competent technical review
Address structural, electrical, material, drainage, installation and public-realm requirements as applicable.
- 04Agree installation and maintenance responsibilities
Set access, competence, inspection, intervention and removal expectations before deployment.
- 05Record decisions and proceed only where appropriate
Retain a clear basis for why a location was accepted, changed or rejected.
BIODIVERSITY ENGINEERING INTERFACE
A habitat feature creates its own engineering questions.
Where a pilot includes insect habitat, the technical brief should consider the physical conditions experienced at the habitat face and inside representative cavities, not simply whether a module can be attached.
Avoid untested heat traps
Review solar heating, material interfaces, thermal separation, cavity depth and ventilation before defining a biodiversity configuration.
Create a deliberately dark zone
Avoid decorative light directed at entrances, assess reflected street-light spill and measure the habitat face during commissioning where relevant.
Keep entrances legible
Planting and public-facing details should not permanently obscure all habitat entrances or create unnecessary clutter in the immediate approach space.
Design to change with evidence
Serviceable habitat components should allow future material, orientation or configuration changes where pilot evidence identifies a better approach.
PUBLIC INFORMATION BOUNDARY
Enough detail to show discipline. Not enough to expose protected engineering.
Public pages can explain the questions, safeguards, review gates and operating responsibilities around OKLUS.
- No precise attachment geometry
- No protected internal construction
- No sensitive dimensions or manufacturing detail
- No project load calculations
- No implication of certification before it exists
CONNECTED DEVELOPMENT
Engineering sits inside the wider OKLUS route to evidence.
Technical assurance, living-media specification and pilot evaluation should progress together rather than as separate stories.