Request a fee proposal

Traffic & Transport

Traffic Modelling and Microsimulation

Traffic modelling and microsimulation predict how intersections and networks will perform — from a single intersection in SIDRA to a whole corridor in microsimulation.

What it is

Traffic modelling uses specialist software to predict how a road, intersection or network will perform under given traffic conditions — today or in a future scenario. Intersection modelling (commonly in SIDRA) analyses capacity, delay and queuing at individual intersections; microsimulation (in packages such as Aimsun, Vissim or similar) models the dynamic interaction of many vehicles across a corridor or network. Together they answer “will it work, and what happens if we change it?”

When you need it

You need it when a decision depends on how traffic will perform: assessing a development's intersection impacts, testing design options, evaluating a corridor or network change, checking future-year scenarios, or peer-reviewing someone else's model. Intersection modelling supports many TIAs; microsimulation is used for more complex, interacting networks.

Who requires it

Councils and state agencies, developers, other consultancies and infrastructure teams who need credible performance evidence for a decision, a submission or an approval.

What Arcvia assesses

The right modelling approach for the question (intersection analysis vs microsimulation); model build and calibration to observed data; capacity, delay, queuing and level-of-service outcomes; scenario and sensitivity testing; and clear interpretation of what the results mean for the decision. We're candid about a model's assumptions and limitations.

What you receive

A modelling report with the results, the assumptions and calibration behind them, scenario comparisons where relevant, and a plain-language interpretation — plus the model itself where you need it. The emphasis is on results you (and an authority) can trust and understand.

Standards, guidelines & authorities

Modelling follows recognised practice and the relevant authority's modelling requirements and guidelines (including road-authority expectations for model calibration and reporting), using industry-standard software. We confirm the required approach, software and guidelines at scoping.

Information we need for your fee proposal

The question you need answered; the intersection(s), corridor or network; available traffic data (or whether surveys are needed); the scenarios of interest; any authority modelling requirement; and your timeframe.

Our process

  1. Scoping — confirm the modelling approach and requirements.
  2. Fee proposal — scope and fee in writing.
  3. Data & build — assemble data, build and calibrate the model.
  4. Analysis — run and test the scenarios.
  5. Report — results, interpretation and the model, with support for authority review.

Frequently asked questions

Related services

Sectors & locations

Servicing Victoria and Queensland.

Representative work

Have a project that needs a clear way forward?

Tell us what you need to understand and we'll set out the modelling scope and fee in writing.