Fire & Safety · Business operations

Review operations with source-backed records

Bring project, procurement, finance and service records into reviewed dashboards. Trace unusual changes to their sources. Managers define the metrics and approve actions.

Starts with spreadsheets alone Every figure shows its source Managers own every action
Harbourview portfolio viewMonthly operations review · 6 live projects
Awaiting manager review
  1. Source mappingCRM, project and finance extracts mapped
    Approved
  2. Metric validation1 reconciliation open · 17 of 18 metrics agreed
    Sign-off
  3. Portfolio dashboardsRole views refreshing · drill-downs linked
    Working
  4. Anomaly explanationWaits for refreshed dashboards
    Queued
  5. Management actionsOwners and due dates for the review
    Queued
pipeline and forecast differ · awaiting owner
Exception · Figures disagreeCritical

Pipeline and finance forecast count different projects

CRM export · 10 Oct42 open opportunities in the quarter.
Finance forecast · 08 Oct40 projects in the same quarter.
Owner: Operations managerNeither figure assumed
Metrics with an agreed definition17 / 18
Open data exceptions3
Who uses it
Executives, operations managers, department heads and analysts
Lifecycle stage
Management, across the whole fire and safety lifecycle
Works from
Your CRM, project, procurement, finance and service exports
Sign-off
Named owners approve metric definitions and the brief
What changes

Link management reports to their sources today

Each department exports its own numbers with its own definitions and refresh dates. Before a review, someone reconciles them in a spreadsheet, and the questions that matter wait for the next meeting.

The question

How many projects do we have this quarter?

TodayFour reports, four answers
Sales CRM42Open opportunitiesExported 10 Oct
Finance40Forecast projectsUpdated 08 Oct
Operations sheet44Active job numbersLast edited 3 weeks ago
Last board pack39Signed contractsSeptember figure
With the use caseOne agreed figure, with its working
40
Contracted projects in Q4Definition v2 · Owner: Operations manager
  • CRM: 2 opportunities not yet contractedExcluded
  • Finance: 40 forecast projectsMatches
  • Operations: 4 closed jobs still openSent to owner
  • All sources refreshed 10 OctCurrent

Building the monthly report

Today: Analysts copy exports into a spreadsheet and rebuild the same charts each month.

Refresh mapped sources on schedule and show the date beside each figure.

Agreeing definitions

Today: Sales, finance and operations each count a "project" or "backlog" differently.

Assign metric owners and definitions, then reconcile figures that disagree.

Spotting problems

Today: A delay or backlog is noticed when a client complains.

Unusual changes are flagged and explained with the source records behind them.

Answering why

Today: A question in the meeting becomes an action to find out later.

Managers drill from the portfolio to the project and the source record during the meeting.

Following up

Today: Actions from the review live in meeting notes.

Each action has an owner and a due date, and closure is tracked at the next review.

Trusting the numbers

Today: Stale extracts and mixed currencies quietly distort the picture.

Flag stale data, mixed currencies and conflicting definitions as exceptions.

What it does

Five capabilities, one governed management view

Start with the view leadership asks for most. Each capability works on its own exports, and the view grows as you connect more sources.

Data mappingAnalyst + data owner

Bring each department's data in without rebuilding it

Connect or upload exports from CRM, project, procurement, finance and service sources, map their fields once and keep each extract's owner and refresh date visible.

AI suggests

  • Likely field matches between sources
  • Duplicate projects across systems
  • Columns that changed since the last refresh

Rules automate

  • Field mapping and unit conversion
  • Refresh schedule and age checks
  • Access filters by role

Your data owners decide

  • Confirm each field mapping
  • Accept or reject duplicate merges
  • Own the refresh of their source
CRM export 42 opportunities mapped to projects mapped
service extract last refreshed 9 days ago stale
finance 2 currencies, dated rate applied converted
What you get

A mapped data model with source owners, refresh dates and quality status for every extract.

Workflow

One governed view, from raw export to agreed action

Automated steps prepare the evidence. People make the calls. Work cannot move past a gate while a critical exception is open.

  1. Connect the sources

    Connect sales, project, purchasing, finance and service data.

    AutomatedAnalyst

  2. Define source metrics

    Map fields and agree each metric's owner, formula and denominator.

    AnalystMetric owner

  3. Validate source data

    Check data age, currencies and totals, then resolve mismatches.

    Approval gateData owner

  4. Refresh the dashboards

    Publish role views with drill-down to projects and records.

    Automated

  5. Explain what changed

    Review flagged changes and the source records behind them.

    Operations manager

  6. Assign review actions

    Record decisions, assign action owners and agree due dates.

    ExecutiveDepartment head

  7. Publish reviewed brief

    Approve the management brief with its sources and refresh dates.

    Approval gateManager
Prepared or reviewed stepApproval gate with named sign-off
At a glance

What goes in, what comes out

Everything you bring flows through one controlled use case. Hover or tap an input to see which outputs it feeds.

You bring

CRM and pipelineOpportunities, stages and values
Project and engineeringMilestones, reviews and backlog
ProcurementOrders, shortages and supplier dates
FinanceForecast, revenue and margin by project
Service and maintenanceVisits, defects and action closure
The use case Management & Operational Intelligence
  • Source & data mapping
  • Metric validation
  • Portfolio dashboards
  • Anomaly explanation
  • Management actions
2 approval gatesFull audit trail

You get

Role-specific dashboardsPortfolio to project to source record
Approved metric
catalogOwners, formulas and denominators
Anomaly explanationsDrivers with cited source records
Management briefActions, owners, due dates and refresh dates
Evidence to action

Trace the delay. Assign the next action.

Follow the Harbourview material delay from the portfolio view to the supplier evidence, then assign an owner and a response time.

  1. Portfolio dashboard6 live projects, 2 flagged amber in the current review
    Dashboard
  2. Harbourview Mixed Use CentreAmber: material delay on the fire pump set
    Project
  3. Purchase order PO-4471Installation needs the pump set in 2 days; supplier delivery is in 3 days
    Order record
  4. Supplier update, 2 days agoDelivery in 3 days confirmed by the buyer · refreshed today
    Source record
Action A-31Confirm an earlier delivery · Owner: Procurement · Follow up in 1 day
Who it is for

Built around the people who run the business

Each role sees the evidence it needs and approves only what it is authorized to approve.

Decides

Executive

Sees the whole portfolio at a glance and asks questions that drill down to the source.

Runs

Operations manager

Owns metric definitions, reviews flagged changes and approves the brief.

Leads

Department head

Sees their own area against agreed targets and owns the actions assigned to it.

Prepares

Analyst

Maps sources, maintains definitions and stops rebuilding the same report each month.

Owns data

Data owner

Keeps their source current and resolves the mismatches it causes.

Reconciles

Finance lead

Agrees revenue and margin definitions and keeps currencies separate until converted.

Designed for

Specialist fire contractorsFire maintenance providersMEP contractorsFire protection consultanciesMulti-location service providersGroups with several business units
Scope & limits

What this software will not do

Management decisions rest on the numbers in front of you. Every figure shows where it came from, and every action stays with a named owner.

How every output moves from AI suggestion to an issued record

  1. AI analysisAutomated
  2. Draft summary or explanationMarked as draft
  3. Manager reviewAccept, edit or reject
  4. Brief approvalOperations manager
  5. Published viewVersioned snapshot
  6. Audit trailWho, what, when, why

It does not hide stale data

Each figure shows its refresh date. An old extract appears as an exception, not as a current number.

It does not pick a winner between sources

When two systems disagree, both figures are shown until an owner decides how to reconcile them.

Explanations always cite their records

AI explanations must cite source records. An explanation without supporting records is never presented as a finding.

It does not change source systems

Transactions and engineering approvals stay in their own systems. This view reads them and never overwrites them.

Currencies are never mixed silently

Different currencies stay separate until a dated conversion rate is applied. The conversion basis remains visible.

Access follows your roles

Role permissions control access to projects and figures. Each person sees only the records their role allows.

Standalone first

Starts with spreadsheets and exports alone. No other module or live connection is a prerequisite.

Connects when you are ready

Optional links to CRM, ERP, project, procurement and CMMS systems, each with mapped fields and agreed data ownership.

Your data stays yours

Separate tenants and projects, role-based access and encryption at rest and in transit. Model training requires written permission.

Example project

A ten-minute walkthrough of Harbourview

Sources1.5 min Metrics2 min Dashboards2.5 min Explain2.5 min Approval1.5 min
Demo scenario · sample project

A monthly operations review across six live projects

The walkthrough follows one review from raw exports to an approved brief, across all five capabilities.

Projects6 live
Sources5 extracts
Exceptions shown3
Sign-offs2 gates

  1. Check the data sources

    The source panel shows each extract, its owner and refresh date. The service extract is flagged as stale.

    Data mapping

  2. Reconcile pipeline and forecast

    The CRM and finance counts differ by two projects. The owner traces both to their records and records the reason.

    Metric validation

  3. Open the portfolio dashboard

    Two projects show amber, one with an engineering review backlog and one with a material delay.

    Portfolio dashboards

  4. Drill into Harbourview

    The material delay opens down to the pump set order and its revised supplier date.

    Portfolio dashboards

  5. Explain the engineering backlog

    The explanation cites two submittals returned by the consultant. The manager accepts it and adds context.

    Anomaly explanation

  6. Assign owners and publish the brief

    Two actions get owners and due dates, and the brief is approved with its sources and refresh dates.

    Management actions Approval gate
Pilot evaluation

Agree the measures before the pilot

We agree a baseline with you first, then compare. We do not promise a number before your own data shows it.

  1. 1
    Agree a baselineYour current process, measured the same way
  2. 2
    Run the pilotOne leadership review cycle on your own exports
  3. 3
    Compare on your dataSame measures, same denominator, reported openly

Reporting preparation time

Working time to compile and review the monthly management pack.

Data freshness

Share of figures within their agreed refresh window at review time.

Reconciliation errors

Figures corrected after publication because sources disagreed.

Action closure

Actions closed by their due date, tracked from review to review.

Adoption by role

Active use of each dashboard by its intended business roles.

A first pilot validates one review cycle on your own exports before wider claims.

Getting started

Define a pilot with your team

  1. Review the requirements

    We send the consolidated requirements for the use case and its five capabilities.

  2. Review the workflow example

    Review the example workflow, its records and approval points with your team.

  3. Confirm the project scope

    We map your data sources, the metrics leadership uses and the view to start with.

  4. Define the pilot scope

    Your exports, metric definitions, roles and a past report define the pilot.

  5. Pilot

    Evaluate against your baseline

    One leadership review cycle on your own exports, measured on the agreed pilot measures.

Continue exploring

Also in Fire & Safety

Engineering & design

AI Fire Design

Review design basis, compliance, product choices and drawings in one workspace.

Explore the use case Pre-sales & tendering

Pre-Sales Estimating & Quotation

Measure quantities, build sourced estimates and prepare quotations for approval.

Explore the use case Project delivery

Submittal & Commissioning

Review submittals, track materials and record commissioning in one delivery record.

Explore the use case Inspection & service

Inspection & Asset History

Capture inspection evidence, review findings and keep a history for each fire asset.

Explore the use case

FAQ

Which operational records can feed the management view?

Start with authorized exports and spreadsheets from the project, commercial and service processes you want to review. Agree the metrics, source fields and owners before combining them.

Are live integrations required?

Approved exports provide a starting point. Live connections can be scoped separately, with each field mapped to an agreed source and owner.

What happens when two sources report different figures?

Show both figures and their sources. The metric owner reconciles the difference and records the reason before the figure is used for a management decision.

How does a management finding connect to its evidence?

The management view traces a finding to the records behind it. AI summaries and bounded answers cite those sources so the team can inspect the supporting evidence.

Where are source-system changes and approvals made?

Transactions and engineering approvals stay in their responsible systems. This workflow reads approved records and prepares management views for review.

Who can access the operational figures?

Define access by role, project and business unit. Confirm which records and management views each role should see when scoping the solution.