Published on :
This digest covers the releases Xempla shipped across June and July 2026. The theme running through all of them is connection - turning workflows that used to live as separate steps, separate systems, or separate conversations into a single continuous flow, governed from one layer.
Where April and May completed the first version of the operational cockpit stack, June and July extended it in two directions: connected work across the full lifecycle of a task (Work Streams), and connected visibility across the full chain of command, from technician to executive. Here is what shipped and why.
The June and July 2026 release cycle focused on unifying fragmented workflows into a single, continuous "System of Decisions" to reduce administrative friction across the chain of command.
Key Enhancements:
Strategic Impact:
By closing the "seams" between systems, these updates minimize the number of tools required to move from data to decision, ensuring technicians, engineers, and executives operate within a unified knowledge repository
A solar installation doesn't end when the panel goes up. It moves through handover analysis, review, and quality check - steps that, in most FM stacks, live in different tools, different owners, and different formats. Work Streams connect them into a single governed flow, visible from both ends: the executive governance layer sees the whole sequence, and the technician sees only the step in front of them.
The technician-facing UX changed substantially alongside this. Field staff, quality assessors, and engineers now capture observations however is most natural in the moment - images, video, voice notes - and the system does the structuring. By the time they're back at a desk, the report is already assembled.
Why this matters: The administrative and cognitive load on field staff has always been a tax on the actual work. Work Streams removes the tax without removing the judgment - technicians still decide what to note; the system decides how to structure it.
What's changed so far In a Solar O&M deployment, Work Streams has been used across 125 installations. Previously, handover analysis was not a formal step at all; installations moved from field completion straight to sign-off without a structured check. With Work Streams, an automatic handover check now runs before sign-off, and has flagged 60% of the 125 installations as not meeting criteria on first pass. Of that 60%, 30% have since been resolved after contractor follow-up, a loop that Work Streams' automated checking made fast enough to close.
The checks themselves have also gotten faster. Done manually alongside report writing, they were slow enough that teams could only complete about three a week. Automated checking has removed that bottleneck: checks now run at least once a day, reports included.
The Engineering Cockpit builds directly on the DIIV cycle. At the point a work order is generated, the system now also generates the assessment an engineering manager actually needs: why the work order was raised, whether it warrants escalation, and who it should go to. That assessment is now available natively on the mobile app - no web login required.
From the same interface, a manager can escalate immediately: select the right people, attach supporting documentation, and forward to a contractor, without leaving the flow. The view is organised around the indicators an engineering team is actually held to - energy, operations, maintenance, reliability, and occupant comfort - not a generic work order list sorted by priority label.
Why this matters Escalation decisions in most FM operations happen after a delay - the manager has to get to a desk, open a second system, and reconstruct context that was available at the point of triage. Putting the decision and the action in the same mobile interface closes that gap.
Every capability previously available on Android - cockpit views, Work Streams, escalation - is now live on iOS. This closes a gap for customers and teams standardised on Apple devices and removes a platform constraint from future rollouts.
Contractor reports, invoices, and assessment reports have always carried information that should trigger specific downstream actions. In most FM stacks, that connection is manual - someone reads the document and decides what to do with it. This release automates that link.
It lives in two places to start: across Solar O&M instances, and in the UK for Health & Care facilities, where it supports Health Technical Memorandum (HTM) compliance assessments.
Why this matters: The value isn't the document processing on its own - it's what that processing feeds into. Automated extraction that doesn't connect to a workflow is just faster filing. This is built to connect into context that the rest of the system already acts on.
What's changed so far Since go-live, document workflow automation has cut processing time from around 20 minutes manually to around 2 minutes.
Xempla has deliberately avoided dashboards for frontline and engineering teams. The governance dashboard applies the same cockpit principle at the executive level: surface the small number of KPIs that let a leader act fast, and keep the interaction - the notes, the follow-up thinking - inside the platform, rather than exporting insight to Power BI and leaving the underlying data behind.
That's the structural difference from a conventional BI layer: in most stacks, the data lives in one system and the analysis lives in another. Here, both live in the same place, which means every executive interaction adds back into the same knowledge repository the rest of the platform draws on.
.png)
More use cases beyond Solar O&M and UK Health & Care HTM compliance.
Extending the autonomous maintenance model - already proven on Hard FM triage - to Soft FM activities.
Automated ticket generation from failed QC assessments and AI inspection findings, closing the loop between assessment and action without a manual step in between.
Checklist-based quality assessments, rolled up from location level to facility level, feeding directly into the executive governance layer alongside Hard FM signals.
Today, fault triage runs through a single agentic pipeline. In August, Omi will be able to choose from multiple pipelines depending on the context of the fault, matching the reasoning path to the type of problem, rather than forcing every fault through the same route. This is a key step in use of the knowledge we have accumulated over months of agentic triage of alerts / faults.
June and July were about connection, not addition. Work Streams connect the steps within a single task. The Engineering Cockpit on mobile connects the moment a decision is identified to the moment it's acted on. Document workflow automation connects a report to the workflow it should trigger. The governance dashboard connects executive visibility to the same system everyone else is already working in.
None of these are new capabilities bolted on top of the platform. They're the seams between existing capabilities, closed. That's the pattern August continues: ticketing closes the loop between QC failure and action; multi-pipeline reasoning closes the gap between fault type and the right diagnostic path; Soft FM autonomy extends a model already proven on Hard FM.
Our thesis A governance layer is only as good as how few systems a decision-maker has to move through to reach a decision. Every release this cycle removed one more handoff - between a field observation and a report, between a fault and an escalation, between a document and the workflow it should have triggered automatically. That is the System of Decisions, built one seam at a time.
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.
Block quote
Ordered list
Unordered list
Bold text
Emphasis
Superscript
Subscript
© Xempla. All rights reserved.
Terms & Conditions