One portfolio record per asset
Design review history, delivery performance, compliance position, handover evidence and operating data are held against the same asset record, so a portfolio view is read rather than reassembled each quarter.
Planned UnifyOS module · Portfolio & lifecycle intelligence
Judge portfolio decisions on delivery and operating evidence.
Owners and investment committees make lifecycle, capital and reinvestment decisions on financial models that rarely reflect how each asset was designed, delivered, handed over and operated.
The planned asset-intelligence module aggregates evidence from across the other UnifyOS modules into a portfolio view, so patterns in cost, risk, compliance and performance are visible at the level where capital is allocated.
Planned — the portfolio layer above the delivery modules
These modules are roadmap positions within UnifyOS. They are in design or scoping, are not available today, and no delivery dates are committed. They are published so clients can see the direction of the platform and shape it — not to imply released functionality.
The problem
What goes wrong today.
- Portfolio reporting assembled by hand from disconnected sources
- Delivery performance never compared consistently between assets
- Compliance and operating risk invisible above individual project level
- Lifecycle and capital plans built without delivery or operating history
- No evidence trail behind portfolio-level assertions
The intent
What the module is designed to do.
- Aggregate design, delivery, compliance, handover and operating evidence per asset
- Benchmark performance consistently across a portfolio
- Surface concentrated risk, cost and compliance exposure
- Support lifecycle, refurbishment and capital planning with delivery history
- Report portfolio position to owners, boards and investment committees
- Keep every portfolio figure traceable to source records
Data it would work from
Records that already exist on your projects.
- Outputs from every other UnifyOS module
- Asset and unit registers
- Capital and operating cost data
- Compliance and certification history
- Occupancy, trading and performance data
Capabilities
What the module would do, in detail.
Worked through with delivery teams running live completions, so the design starts from how handover actually behaves.
Consistent delivery benchmarking
Approval cycle times, rework rates, recurring non-compliance themes and programme slippage are measured the same way on every asset, so comparison reflects performance rather than differing reporting habits.
Risk and exposure concentration
Where the same consultant, contractor, defect type or compliance gap recurs across several assets, the pattern is surfaced at portfolio level instead of staying inside individual project reports.
Lifecycle and capital planning inputs
Installed asset records, warranty positions, condition data and operating cost history feed refurbishment and reinvestment planning, so capital cases start from what the buildings have actually done.
Evidence-linked portfolio reporting
Every figure in a board or investment-committee pack can be opened back to the underlying record — a certificate, a review decision, a cost entry — rather than resting on a spreadsheet nobody can audit.
Scenario views for reinvestment
Forecast comparisons across assets show where capital would relieve the most delivery, compliance or operating risk. These are forecasts for decision support, not valuations.
What it produces
The records it would hand you.
Portfolio performance view
Delivery, compliance and operating position across every asset, on comparable measures.
Asset scorecards
A single asset's history from design review through handover into operation.
Risk concentration report
Where the same exposure repeats across assets, parties or disciplines.
Lifecycle and capital planning pack
Condition, warranty and cost history structured for reinvestment decisions.
Board and investment-committee reporting
Portfolio position with every figure traceable to its source record.
Who it is for
The people who would use it.
Owners and investment committees
See portfolio position on evidence rather than on periodic self-reported summaries.
Asset and portfolio managers
Compare assets consistently and direct attention to where exposure actually sits.
Development and delivery directors
Understand which delivery patterns repeat and which partners perform across programmes.
Finance and capital planning teams
Build lifecycle and reinvestment cases on delivery and operating history.
Where the line sits
What it does not claim to do.
The boundaries matter as much as the capability.
- Portfolio figures are analysis of the records supplied — they are not certified valuations or audited accounts.
- Forecasts and scenario comparisons support decisions; they do not make investment determinations.
- AI findings are assistive and evidence-linked; portfolio conclusions remain a human judgement.
- The module depends on the handover and facilities modules producing comparable records, so it follows them in the sequence.
- This module is in scoping. It is not available today and no delivery date is committed.
Roadmap position · Later
What this module depends on.
Sequencing is driven by dependencies, not by marketing convenience. Nothing here is available today and no delivery date is committed.
Depends on
- UnifyOS Handover
- UnifyOS Facilities Management
- UnifyRetail OS
- UnifyProjectVision
Already in place
- Direction published
- Portfolio analytics foundations already running inside existing modules
Still needed — In scoping
- Sustained delivery and operating data across multiple assets
- Handover and facilities modules producing comparable records
- Agreed portfolio benchmarking measures with owners
- Investment reporting requirements defined with asset managers
See where this sits against every other module on the UnifyOS roadmap.
IntelliBridge™ connection
What it reads, and what it writes back.
Asset Intelligence holds no source records of its own. It reads what the other UnifyOS modules have already validated, and IntelliBridge carries the client-side cost, occupancy and asset data in alongside it — then writes the portfolio position back into the systems owners already report from.
Reads from UnifyOS and your systems
RealCube — assets, units, tenants and leases
The asset and unit register, tenant and lease references, fit-out cases and NOC events come in through the RealCube connector, so every portfolio figure is held against the same unit record the landlord operates from.
Oracle Aconex — controlled documents and correspondence
Transmittals, drawing and specification revisions, and RFI threads are read as the document trail, so review cycle times and rework counts are measured against controlled revisions rather than estimates.
Procore — construction delivery and field records
Submittals, observations, punch items, inspections and change events roll up into delivery performance per asset, with each measure linked back to the Procore item that produced it.
Generic webhook connector — ERP, PMIS and Microsoft 365
Capital and operating cost data, occupancy and trading figures and scheduled batch extracts arrive over the signed REST and webhook interface, so platforms without a named connector still feed the portfolio view.
UnifyOS modules — decisions already validated
UnifyReview™ findings and approval decisions, UnifyRetail OS unit records, UnifyProjectVision™ delay and cost-risk analysis, and Handover and Facilities Management evidence as those modules produce it.
Returns to your platform
Asset scorecards into RealCube
Each asset and unit record receives its delivery, compliance and operating position, so the portfolio view lives where asset managers already work.
Delivery signals into Procore and Aconex
Recurring finding themes and risk concentrations return as observations, submittal comments or document status callbacks against the originating revision.
Capital planning inputs to ERP
Condition, warranty and lifecycle findings return as structured inputs to reinvestment and budget cycles over the generic connector.
Signed portfolio events
Signed webhooks raise a portfolio-level event when the same exposure repeats across assets, parties or disciplines, with idempotency keys, retry history and integration logs behind every delivery.
The transport, signing, retry and traceability behaviour is described on the IntelliBridge™ page.
Client journey
How a connection is actually stood up.
Four stages from mapping your systems to portfolio reporting returning on your own cadence.
- 01
Name the integration owner and issue credentials
A client-side integration owner with administrative access to RealCube, Aconex, Procore or your ERP is nominated, API credentials are scoped to the assets in question, and a webhook signing secret is issued per environment.
- 02
Agree the field mapping in sandbox
Projects, assets, units, tenants and disciplines are mapped between your platform and the UnifyOS model, and tested against real extracts in sandbox before any production event is enabled.
- 03
Baseline one asset end to end
A single asset is loaded through the connectors configured for that client — review history from Aconex, delivery records from Procore, unit and lease data from RealCube, cost from ERP — to prove the record and the measures.
- 04
Confirm the benchmarks with the owners
Asset managers and the investment committee sign off which comparisons matter, so portfolio measures reflect how you judge performance rather than a generic template.
- 05
Extend across the portfolio and return reporting
Further assets are onboarded through the same connectors, and scorecards, risk events and capital inputs begin returning into your systems on your own reporting cadence.
Inside UnifyOS
How it connects to the rest of the platform.
Every module shares the same governance, evidence and audit standards, so intelligence carries forward instead of being rebuilt.
UnifyProjectVision™
Programme and cost outcomes roll up into portfolio delivery performance.
UnifyRetail™ / UnifyRetail OS
Unit-level delivery and trading readiness aggregate to scheme and portfolio level.
Facilities management
Operating cost and condition data informs lifecycle and reinvestment decisions.
Client systems connect through IntelliBridge™, so this module would read from and write back to the platforms you already run.
Tell us what this needs to handle.
Requirements from live portfolios shape what gets built first — and what gets built at all.