Skip to content

Projects & infrastructure

For construction, engineering and public works: when each project will really finish, what it will cost, and what is holding it up.

Connect → Understand → Verify → Steer → Ask → Act

Flip the card: here is the answer

Every question is tied to the report that answers it.

The reports setup proposes

One for each goal you pick, plus Data health. Open the tabs.

Project Controls 360 — See when each project will really finish

Over time

shape only

What it answers
A finish date that slips a little every month is a delay nobody announced.
What it reads
Your projects with their milestones, planned and actual dates.
Example finding
The finish date of the bridge project has slipped five weeks since March.

Shapes and findings are examples. Each report is built only when your data holds what it reads; one that cannot be built is named at setup, never estimated.

Everything converges into a single model

From Snowflake, Amazon S3, PostgreSQL, MySQL, Odoo, Salesforce or a file from your computer. What is missing gets flagged, not guessed.

SnowflakeAmazon S3PostgreSQLMySQLOdooSalesforce+ 1 moreYourmodelReportsData healthAlertsExports
  • Your projects with their milestones, planned and actual dates.
  • Your budgets, commitments and costs to date, per project.
  • Your purchase orders with the date promised and the date received.
Data360One model of your business
  • Your quality issues with the contractor, the date raised and the date closed.
  • Your reported progress and your costs to date, per project.

None of this is required. Each report reads only its own line; one whose data is missing is named at setup, never guessed.

What Data360 finds in your data

Every issue is translated into a business consequence.

Checks running

5 checks
  • Milestones with no date update
  • Costs not linked to any project
  • The same order recorded twice
  • Progress that goes backwards
  • Contractor reports that never arrived

Rows that pass each check

Measured on the same data your reports read.

96%
Recent enough
84%
Nothing missing
78%
Everything agrees
71%
Counted once

Percent of rows, illustrative. Real scores are measured on your own data.

Business findings, not technical alerts

Each finding names the report it comes from.

  • The finish date of the bridge project has slipped five weeks since March.

    From the report See when each project will really finish

  • Costs to date point to a final cost 7% over the approved budget.

    From the report Compare what each project will cost with its budget

  • Two late steel orders are holding up the next three tasks.

    From the report Spot the late purchases holding up the work

  • One contractor accounts for most of the issues still open.

    From the report See which contractors leave issues open

  • One site has spent 80% of its budget for 45% of the work.

    From the report Check progress against the money spent

Example findings. Real ones come from your own data, in the report that produces them.

A finding with no follow-up is worth nothing

Six things Data360 does once a figure matters.

  • AlertSet a line on a figure that matters and see when it is crossed.
  • Tell peopleTell you, chosen teammates, or everyone who can open the app.
  • Refresh reportsRead the figures again so every report is current.
  • Re-check qualityMeasure the tables again and flag what broke.
  • Clean and saveRemove duplicates, filter, combine and total, then save the result as a table.
  • ExportTake the rows behind a figure away as a spreadsheet file, or save them as a table.

See Project Controls 360 on your own data.

Your goals, your data — and the reports built from them.