Skip to main content

In short: What is AIMZ and how does it all fit together?

A simple introduction to how AIMZ is structured — from estimate and production codes to purchasing, changes and invoices.

AIMZ is a project economics system, built around one core idea: that you should always know what the project will cost in the end — not just what it has cost so far.

How the parts fit together

The core of AIMZ follows this flow:

Flow diagram: the estimate is distributed across production codes with purchasing, invoices and changes, which together give the Final Forecast

  1. Estimate — the starting point. The contract estimate is imported and forms the budget.

  2. Production codes (prod. codes) — the estimate is distributed across prod. codes.

    1. Purchasing — you plan or record which purchases have been made per prod. code.

    2. Invoices — incoming and outgoing invoices can be linked to the correct prod. code, purchase, change and more. AIMZ fetches invoices automatically through the integration with the accounting system.

    3. Changes — changes towards the client and subcontractors are registered and affect the revised budget and the Final Forecast.

  3. Final Forecast — AIMZ continuously calculates what the project is expected to cost in total, based on budget, purchasing, invoices and changes.

Who uses what in AIMZ?

This varies, but here are examples from our current customers:

  • Project manager — registers changes, follows up purchasing and updates the degree of completion.

  • Finance manager / controller — processes invoices, closes months and runs reporting.

  • Finance executives — take a high-level view at portfolio level and reports.

  • Owner/Admin — sets up prod. codes, imports the estimate and manages user access. Read more in What roles exist in AIMZ, and what can each role do?

Did this answer your question?