See the asset
Location, commissioning status, current condition and the latest verified service activity.
OKLUS INSIGHTS
A clearer view of every pilot. From street level to decision level.
OKLUS is shaping a future digital operating layer that connects unit status, local environmental readings, maintenance activity, route observations and evaluation notes without turning public-realm delivery into another wall of data.
Asset awareUnit status, location and service history stay connected.
Decision focusedEvery view supports an agreed pilot question or action.
Role controlledTeams see the information appropriate to their responsibility.
Evidence readyContext, data quality and limitations remain visible.
THE DIGITAL OPERATING LAYER
Not another dashboard. A shared operating picture.
The platform concept is designed to help councils, delivery partners and evaluators understand what is happening, what needs attention and what can be learned next.
Understand the route
Local context, pilot purpose, agreed measures and observations from the surrounding public realm.
Coordinate action
Inspection needs, open issues, maintenance priorities, owners and due dates in one workflow.
Protect the evidence
Data-quality notes, interventions, seasonal context and evaluation comments retained together.
THE MORNING VIEW
What needs attention today?
A calm first view turns activity into priorities rather than notifications.
The concept surfaces unit health, upcoming service tasks, recent observations, data quality and unresolved issues. Teams can move from overview to route, unit or intervention without losing context.
Exceptions before averages
Show the units, tasks or evidence gaps that require action first.
Context beside the number
Keep weather, maintenance and route conditions visible when reviewing change.
One accountable next step
Connect every issue to an owner, due date and visible resolution record.
3 PRIORITIESActionable items surfaced first
DATA QUALITYConfidence remains visible
NEXT SERVICELifecycle tasks stay connected
AI-SUPPORTED MONITORING
AI can streamline monitoring while keeping people reassured and in control.
The goal is not to replace council, delivery or evaluation teams. It is to reduce manual admin, surface what matters sooner and make pilot oversight calmer, clearer and more reassuring.
As the platform develops, AI could help summarise route activity, spot unusual patterns, organise evidence notes and suggest the next sensible check. Human teams would remain responsible for review, sign-off and decisions.
Calmer monitoring
Highlight meaningful changes, exceptions and service needs instead of asking teams to scan every data point manually.
Useful summaries
Turn route observations, service notes and evidence updates into plain-language briefings for busy teams.
Human judgement stays central
AI can support triage and organisation, while people remain accountable for interpretation, communication and action.
Bring unusual changes, overdue actions and evidence gaps to the front first.
Support briefings that are easier to read, share and act on across a live pilot.
AI can assist the workflow while governance, judgement and accountability stay human.
HABITAT MICROCLIMATE
Connect the conditions inside a habitat with what happens biologically.
A future biodiversity-enabled pilot record could bring habitat configuration, microclimate, lighting, maintenance and biological observations together without implying automated species identification or a proven ecological outcome.
01
Cavity temperature
Internal habitat temperature alongside ambient air and relevant surface temperature.
02
Humidity and condition
Relative humidity, moisture notes, obstruction, contamination and maintenance state.
03
Sun, shade and orientation
Orientation, shade state, solar exposure and route context retained beside the reading.
04
Artificial light
Habitat-face illuminance and, where relevant, the lighting configuration that created it.
05
Biological outcome
Investigation, nesting attempt, completed brood cells, emergence and reuse where reliably observed.
06
Comparison and quality
Control habitat, environmental reference, interventions and data-quality flags kept visible together.
Future concept:The aim is context, not a simplified “bee health score”. Sensor data would support specialist interpretation rather than replace it.
A FUTURE SCHOOL LEARNING VIEW
Turn local environmental observations into lessons pupils can explore.
Authorised schools could eventually access a simplified education view of OKLUS Insights, designed around local learning rather than operational control or pupil monitoring.
Teachers could use agreed observations to explore air-quality context, weather, temperature, humidity, planting, pollinator activity, habitat condition, service records and seasonal change.
Explore the OKLUS education approach →Compare time periods while keeping data quality and limitations visible.
Explore seasonal activity without assuming every observation proves a wider effect.
Study microclimate and change across different locations and seasons.
See how environmental infrastructure needs inspection, care and accountable ownership.
FUTURE INTERNAL IMAGINGA carefully controlled view inside a habitat module could support learning without exposing the street.
The concept would require ecological approval, no view of people or pavements, no microphone, controlled access, minimal disturbance and clear image-retention rules.
ONE RECORD, FOUR PERSPECTIVES
Different teams. One trusted source of context.
Role-based views help each partner focus on the decisions they own while preserving a consistent underlying pilot record.
Programme view
Purpose, status, route performance, risks, milestones and the next governance decision.
- Pilot overview
- Issue escalation
- Decision summary
Operational view
Site access, inspections, scheduled work, open tasks, component history and evidence capture.
- Daily task list
- Service record
- Fault resolution
Evidence view
Readings, baseline, interventions, quality notes, context and documented limitations.
- Data quality
- Context timeline
- Analysis notes
Platform view
Product learning, recurring issues, service patterns and improvement opportunities across pilots.
- Fleet learning
- Product feedback
- Repeatability signals
FROM STREET TO DECISION
Every useful signal keeps its story.
A reading is more valuable when the platform can show where it came from, what changed around it and how it informed action.
The future workflow is intended to connect the physical unit, the service team, route observations, evidence review and final pilot reporting.
FIELD MODE
Useful at the asset, not only in the office.
The field concept supports inspection, observations, maintenance logging and issue escalation while the team is on site, using the real OKLUS product form rather than a generic device mock-up.
DESIGNED FOR PUBLIC-SECTOR CONFIDENCE
Useful technology, proportionately governed.
The concept is being shaped around clear purpose, minimum necessary information and visible accountability rather than collecting data because it is technically possible.
01
Privacy by design
Asset and pilot information first, with personal data avoided unless a defined need and lawful basis exist.
02
Role-based access
Permissions follow responsibility so operational, evaluation and governance views remain appropriate.
03
Visible audit trail
Changes, interventions, decisions and evidence notes can be linked to a clear record.
04
Proportionate integration
The future platform can be explored alongside existing council systems without assuming one fixed architecture.
05
Accessible presentation
Calm hierarchy, plain language and responsive interfaces make complex information easier to use.
06
Development transparency
Concept features, proven functions and future possibilities are clearly separated as the platform develops.
WHY THE PLATFORM MATTERS
A stronger relationship than hardware alone.
The app concept creates a practical connection between product, service, evidence and future scale. It is intended to increase the value of each pilot and improve the quality of every subsequent deployment.
Lifecycle visibility
Installation is the beginning of an operating relationship, not the end of a transaction.
Repeatable delivery
Common workflows and records can make later pilots easier to coordinate and compare.
Portfolio learning
Patterns across routes, maintenance and product performance can guide better development choices.
Decision confidence
Connected context helps partners distinguish a promising signal from an unsupported claim.
CURRENT PLATFORM POSITION
Designed as a future pilot-support concept.
The interfaces shown are design concepts for discussion with councils, delivery partners and investors. Functions, integrations and technical architecture will be validated and prioritised through structured pilot planning.
Current stageInterface concept, workflow definition and pilot-partner discovery
Primary purposeConnect asset status, maintenance, local context and evaluation records
Intended usersCouncil leads, delivery teams, evaluators, authorised school learning roles and OKLUS support roles
Data approachPurpose-led, role-controlled and proportionate to the agreed pilot
Next validationUser needs, field workflow, integration options, security requirements and reporting priorities