Commercial and retail portfolios
Office, retail and industrial portfolios of hundreds of buildings, reported by fund, region and asset manager.
Compliance · Building Performance · Contractors · Reports
Compliance, performance and finance for property portfolios
OSIS compares every building's agreed maintenance requirements against the evidence in the systems your teams already use. Compliance, work delivery, contractors and spend come together in one place, from a single building to a portfolio of hundreds.
Screens on this page use illustrative data. Building and company names are fictitious.
Across a large portfolio, maintenance compliance is usually assembled from service provider reports, site visits and spreadsheets. The figure that reaches the board is only as reliable as the reporting behind it, and there is no simple way to test it.
OSIS starts from an agreed Master Archive of what every building must have, then checks each line against the operational record: the schedule, the work order, the signed-off checklist, the certificate. The score is a count of requirements with their evidence in place.
Compliance is where OSIS starts. Performance, contractors, planning, training and finance sit on the same data, so every view agrees.
An overall score for each building and the portfolio, broken down by category, with a verification ledger of every Master Archive line and the finding against it.
How planned and reactive work is being delivered, for the whole portfolio or one building, over the period you choose.
Budget, accruals and actual spend for maintenance, built from invoices and work orders in the source system and kept current through the day.
Every service provider's compliance documents and delivery record, measured from the work they actually closed.
For estates, resorts and mixed-use precincts: the month's scheduled work laid out by group, site and operational area, so each team sees its own workload.
Keep the people side of compliance in the same place: what your teams have been trained on, who attended, and whose certificates are current.
Also in OSIS
A transparent method that anyone can check against the source records.
Each building has a Master Archive: every planned maintenance line with its category, type, sub type, frequency and schedule type. This is the single source of truth for what is required.
OSIS finds the matching schedule in your source system on building, category, type and sub type, then checks the work orders, checklists and documents behind it.
Each line is tested against what its schedule type requires, inside its frequency window. A checklist schedule needs a work order closed in the window with a signed-off checklist. A document schedule needs a valid document that is active, approved and not expired.
Compliant lines as a share of scored lines, per building, per category and for the whole portfolio. Lines that are overdue, not done or not yet due are reported as not scored and followed up in Building Performance.
| Type | Schedule | Asset | Checklist | Document |
|---|---|---|---|---|
| 1 | Reminder only | No | No | No |
| 2 | Linked to an asset | Yes | No | No |
| 3 | Linked to a checklist | No | Yes | No |
| 4 | Linked to a checklist and an asset | Yes | Yes | No |
| 5 | Linked to a document | No | No | Yes |
A line without a schedule type is not marked as failed. It is listed as "Schedule Type Not Classified" so it can be completed.
A listed property fund, a golf estate and a city precinct do not answer to the same requirements. During configuration we set up your categories, Master Archive template, scoring and dashboard to match the way you run your buildings.
Office, retail and industrial portfolios of hundreds of buildings, reported by fund, region and asset manager.
Compliance · Building Performance · Contractors · Reports
Golf courses, hotels, clubhouses, residences and grounds, planned by estate group and operational area.
Operational Planner · Events · Work Requests · Contractors
Precincts with several entities and departments, where maintenance spend is tracked against GL codes and budgets.
Finance · Compliance · Building Performance · Reports
Head offices, campuses and specialised facilities where statutory compliance and training records must be shown on request.
Compliance · Training · Reports · Trend Analysis
OSIS doesn't replace your maintenance or finance platform. It reads from it, compares it with the Master Archive and reports the result. Work continues to be logged where it is today.
A defensible compliance figure for the portfolio, with the detail available whenever it is questioned.
Compliance, delivery and spend for their own buildings, compared across regions and service providers.
A working list of what is missing or overdue at each site, built from the system their teams already use.
Every result traces to a requirement and a source record, and every rand to an invoice or work order.
How a portfolio is brought onto OSIS. Progress is reported to you building by building.
We agree your industry setup: categories, scoring rules, modules and dashboard.
A Master Archive is built for each building from your site reports, and the scope is signed off.
Your source systems are connected through myBuildings, API or SQL, and the first sync is run.
Every line is matched and scored. Exceptions are worked through with your teams and service providers.
You approve the user list and each person's portfolios and buildings before credentials are issued.
Soft launch, role-based training for your teams, then go-live on an agreed date.
OSIS is built to be audited.
Tell us about your portfolio and what you'd like to see. We'll take a sample of your buildings, build their Master Archives, connect your source data and walk you through the scores, the exceptions and the evidence behind them.
Existing client? Sign in to OSIS
We'll be in touch to arrange a time that suits your team.