TerraForge Assets business process — linear infrastructure portfolio

Product tour

Assets · Cost Sheet · live WBS Gantt

A full PMIS — Built for Owners and Capital Programme Operators.

Owner-side teams on a legacy PMIS already know the business processes. What they do not get is a modern web system that ships the land, the programme and the cost sheet as one product.

This tour is the demo-room walk: dashboards, assets, Map View, Global Search, operations, leases, financials, schedule, contracts, output. App Builder and the workflow engine live on Configure — not here.

Request a demo Start the tour

Organisation dashboards

The portfolio roll-up is the homepage — EVM, leases, then drill.

Legacy PMIS dashboards are usually a consultancy. Someone builds a custom report. It ages. The board pack is a Friday extract.

TerraForge ships a drillable organisation dashboard with the business process. The branded portfolio level, assets, open work orders, active disputes, total budget, spent, burn rate. Portfolio EVM — BAC, committed, actual, FAC — on the same page. Click a slice or an asset and the widgets follow that roll-up. Programme to project works the same way.

Why it matters in the room

You do not open Power BI to answer “what is the portfolio doing?” Export CSV, PDF, print the executive summary. Lease management is a tab — lessor income, lessee outgoings, net position — not a sidecar. Click a tile or a bar and the source business process opens. Widgets honour record-level visibility.

TerraForge organisation dashboard — portfolio EVM with budget, committed, actual and forecast — Organisation dashboard. Whole-portfolio roll-up: branded portfolio level, assets, work orders, disputes — then Portfolio EVM.

TerraForge organisation dashboard — lease management view — Lease Management tab. Lessor income and lessee outgoings on the same portfolio dashboard.

Assets & Portfolio

A unique ID, title and GIS on the asset — dispositions and depreciations beside it.

National infrastructure landholders do not have a mapping gap. They have plots, buildings, linear strips and depots that refuse to live in a GIS silo while the PMIS runs somewhere else.

TerraForge Assets are the portfolio business process: plots, buildings, facilities and linear strips. Every asset and property carries a unique ID you can track and report across the whole portfolio. Search by unique ID, name or title. Route / corridor reference stays on the record. Re-geocode the flagged few — do not rebuild the portfolio in another tool. Map and grid are the same records. Asset dispositions record what left the portfolio, and why. Asset depreciations keep lifecycle value on the asset — not a finance extract reconciled in March. Both sit in Assets & Properties, beside the business process.

A branded portfolio level — County in the demo

Every organisation slices the portfolio differently. TerraForge gives you a branded portfolio level you name for your organisation: counties, states, campus facilities, zip codes, regions, maintenance areas. The demo brands that level County. Click through and the dashboard, the work and the disputes sit under that slice. A disputed plot is a fact on the asset — visible on the map, in search, on the organisation dashboard.

TerraForge Assets business process — plots, buildings and land on a linear infrastructure portfolio — Assets. Search by unique ID, name or title. Re-geocode flagged records. Dispositions and depreciations sit in the same family.

TerraForge asset detail form — unique ID, title and GIS on the record — BED-Maintenance Depot. Unique ID, title, route / corridor and chainage, timeline, work orders and leases on the same record.

Map View

Not a dumb map — click through to the dispute, project, or asset.

GIS without Map View undersells the product. This is not a picture of the portfolio. The pin opens the live business-process record — the dispute, the project, the asset, the programme — not a dead popup you cannot act on.

See at a glance, then drill

Disputes
Projects and programmes
Assets — including leased and owned
Related portfolio objects on the same canvas

Click a pin, a polygon or a branded portfolio-level centroid. Rolled-up data drills. The record opens.

One canvas: points and polygon boundaries on the same portfolio records. Layers for portfolio level, assets, programmes and projects. Map views also live inside the apps — Assets, Projects — not only the standalone Map View. The map is not a GIS silo you reconcile on Friday.

TerraForge Map View — portfolio-level centroids, assets, programmes and projects on one GIS canvas with a disputed plot selected — Map View. The pin opens the live business-process record — not a dead popup. Disputes, projects, programmes, assets on one canvas.

Global Search

One token. Every business process and every published app. Open the record from the hit.

Legacy PMIS tools do not have this today. TerraForge does.

One query across text, number, status, date and notes — every business process and every published custom app. Module-scoped. Per-module result-count chips tell you where it landed.

Drill from the hit into the matching record. A project controller types an asset ID, a contract number, a work-order ID or a field on an app published last month — and the record opens.

UUIDs and binary attachments are not indexed.

TerraForge Global Search — one query with per-module result chips and a drill into the matching record — Global Search. One token across every business process and every published app. Result chips by module — open the matching record.

Work orders & BPO

Ops reality: work orders on the asset, BPOs as master agreements.

Land ops that sit in a CMMS never make it back to the portfolio number. Work that sits in email never makes it to the asset.

TerraForge Work Orders are on the asset: WO number, vendor, linked BPO, priority, due, cost. Assign, supplier action, asset-manager review, field review. Ball-in-Court lands in My Tasks — the same inbox as a payment application. Search WO #, title, asset, vendor, BPO. Work at the branded portfolio level and on the asset rolls the same way the dashboard already drills.

BPOs — Blanket Purchase Orders / Master Agreements

A BPO is a standing operational order against the portfolio, not a purchase-order dump. Drawdown is a bar on the agreement — value used versus total. Route to market and ERP status sit on the same row. Vendors sit on the work order and the BPO — counterparties in TerraForge, not a side address book.

TerraForge work orders business process — vendor, BPO drawdown, priority and cost on the asset — Work Orders. Search WO #, asset, vendor, BPO. Priority and cost on the same row as the asset.

TerraForge BPO manager — blanket purchase orders and master agreements with drawdown — Blanket Purchase Orders / Master Agreements. Drawdown bar, route to market, ERP status.

Leases & land / legal

Occupancy, lease contacts, adverse possession — on the plot.

Lease data that lives in a property system never reaches the capital conversation. Adverse possession that lives in a legal folder never reaches the map the board is looking at.

TerraForge Leases sit on the plot: incoming or outgoing, counterparty, rent, term, the land they occupy. Lease contacts are who to call, held against the lease — in Land & Legal beside Adverse Possession, not a mailing list in another system. The demo can label that Book of Reference in markets that use the term.

Adverse possession and disputes

An active dispute is a fact on the asset. It shows on the map, on the business process, in Global Search, and as a tile on the organisation dashboard. Claims follow the same audit trail as a budget change. Permitting is the statutory process on the land, in the same inbox.

TerraForge leases business process — incoming and outgoing leases with counterparties and rent — Lease Management. Incoming and outgoing, counterparty, rent, term — on the asset.

TerraForge Adverse Possession business process — statutory claims on organisation-owned land — Adverse Possession. Claimant, asset, severity — possession claims and disputes on the plot, flagged when the threshold is met. Same family as the lease.

Project financials

Cost Sheet columns that your Cost Managers can trust

A cost sheet that is a spreadsheet is not a cost sheet. A cash flow that is redrawn for the monthly pack is not a forecast.

TerraForge Cost Sheet is hierarchical WBS. The columns are the product: Initial → Changes → Transfers → Revised → Committed → Actual → Forecast → Remaining. Dated FX from Company Configuration — not a monthly paste.

Budget Management

Initial Budget is the sanctioned baseline as a business process. Budget Change and Budget Transfer carry pending and approved in their own columns. The sheet does not get typed over.

Cash Flow and Funding

Cash Flow Manager links an S-curve to a Cost Sheet column — typically Approved Revised Budget — at project, cost code or contract. Steepness and skew sliders. Monthly bars, cumulative line, export. Funding Manager holds the colors of money on the Fund Sheet: pending and approved requests consume the fund; approved changes revise its value.

TerraForge Cost Sheet — initial, change and transfer columns rolling to approved revised budget — Cost Sheet. Initial Budget and Budget Change roll-up by cost code. Pending and approved in their own columns.

TerraForge Initial Budget grid — WBS lines, quantity, UOM and unit cost — Initial Budget. A demo capital job and a second programme — pending versus approved on the same KPI row.

TerraForge Cash Flow Manager — monthly bars and cumulative S-curve linked to approved revised budget — Cash Flow Manager. Linked to Approved Revised Budget. Steepness and skew on sliders.

Schedule Manager

XER import — or connect P6 both ways over REST and webhooks

Bring Primavera P6 in by XER, or integrate one-way or bidirectional over REST and webhooks. Dates, logic and progress sit on the TerraForge record — Update from P6, add an activity, reschedule, set baseline.

Schedule Manager is a live WBS Gantt: activities, duration, start, finish, percent complete, total float, variance. Critical path in red. Milestones as diamonds. Baseline under the bar. Day, week or month. Hundreds of activities on one programme — the picture the planner already trusts.

TerraForge Schedule Manager — live WBS Gantt with critical path, baseline and 819 activities — A live WBS Gantt in TerraForge. Critical path, baseline, float — the planner’s picture, not an export pasted into the PMIS.

Contract management

Contracts, change orders, payment applications, SOV — one family.

Commercial that lives in a contracts business process and a cost sheet that do not talk is how committed and actual drift. Change orders that live in email are how the SOV dies.

TerraForge Contracts hold titles, counterparties and values — and they feed Committed on the Cost Sheet. Each business process ships KPI tiles. Not a sidecar the PMO rebuilds on Friday.

Change Orders

A change order is against the parent contract, not a parallel tracker. Pending and approved movement hits the sheet the same way a budget change does. The business process is live — not a Friday extract.

Payment applications and SOV

Payment applications are the actuals. The Schedule of Values is the breakdown they draw against. Same family. Same workflow. Same inbox.

TerraForge contracts business process with KPI tiles — Contracts. Value, committed, spent, variance — feeding Committed on the Cost Sheet.

TerraForge Change Orders business process — COR against the parent contract — Change Orders. Against the parent contract. 125k approved in the base currency — hits the sheet the same way a budget change does.

TerraForge payment applications business process — Payment Applications. Claimed against committed and spent — same demo capital job.

TerraForge Schedule of Values — Schedule of Values. Foundations 4.35M, 51.7% complete, retention held.

Field Management

Field Management — one Ball-in-Court inbox.

RFI, Daily Report, Site Incidents, Submittals / Submittal Packages and the Risk Register are Field Management — Designer-published apps, not a bolted-on field product. They inherit record numbering, security groups, a drillable dashboard and the API. Ball-in-Court still lands in My Tasks.

Field Management sits on the same platform as the Cost Sheet. Compliance is in the same inbox, not a mailbox after the event. The builder that publishes them lives on Configure — on purpose. You extend the set the same Tuesday you publish any other app. Work orders and BPOs stay under Operations.

TerraForge RFI — KPI tiles, workflow status and a numbered request in review — Numbered, workflowed, Ball-in-Court in My Tasks. Same platform as the Cost Sheet — not a bolted-on field tool.

TerraForge Daily Report — workforce, weather and photos on the project — The site diary on the project. Numbered, workflowed, photos on the record. Ball-in-Court in My Tasks.

TerraForge Site Incidents — near miss and environmental incidents — Near miss and environmental loss, numbered and workflowed. Compliance on the same inbox as a payment application.

TerraForge Submittals — package and item on a demo capital job — Package and item, not a document vault. Numbered, workflowed, same My Tasks inbox.

TerraForge Risk Register — likelihood, cost and schedule impact on the project — Likelihood, cost and schedule impact on the project. Same search, same inbox, same Cost Sheet platform.

Reporting & custom output

Compose the report. Publish the output. Every export is in the audit log.

Owner-side reporting that depends on a BI project is how the monthly pack becomes a cottage industry. Mail merge that depends on a consultant’s Crystal report is how a notice letter takes a week.

TerraForge Report Writer composes a custom report from any entity in the system: pick the source, tick the fields, add filters, sort, preview. Export CSV, XLSX, PDF or XML. Every export is recorded in the audit log.

Custom output

Print and export layouts — including mail merge — are configured in Designer and published with the app. The same writer runs on Funding Sources, a leases business process, or the app an administrator published last week. The designer tools themselves are on Configure.

See it running against your own programme data.

Not a canned demo environment — your business processes, your data.

Request a demo