> ## Documentation Index
> Fetch the complete documentation index at: https://useidalia.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# How to mobilise plant to a project and back

> Send a crane from the yard to a project and bring it home. The transport coordinator runs each leg. The project coordinator books the plant on the job.

## Overview

When plant has to work on a job, it needs to get there and back. That could be as easy as a single truck trip, or a multi-stage logistics package spanning multiple countries and modes of transport. Idalia makes it easy to plan, track and forecast these logistics, no matter how complex they are.

This guide follows the example of a tower crane, currently in a storage yard in Sydney, being booked to a job in Portugal. We'll see how we can use Idalia to manage all the logistics needed for the job end-to-end.

There's three parts to this workflow:

1. Decide which assets are needed for the job.
2. Create the logistics plan: first at a high level, then in detailed, sequenced delivery steps.
3. Update the plan as each stage is completed, and track the progress of the whole trip.

In Idalia, that whole trip lives on a [journey](https://useidalia.com/docs/logistics/journeys.md). We'll call this one `Lisbon tower crane`. Add the crane once and it shows up on every leg. Road legs are [transport orders](https://useidalia.com/docs/logistics/transport.md), the sea booking is a [shipment](https://useidalia.com/docs/logistics/shipments.md), and the time the crane spends on the job is an [allocation](https://useidalia.com/docs/allocations/manage.md).

If all you need is a single truck onto a nearby site, you don't need a journey. Use [Last-mile site delivery](https://useidalia.com/docs/guides/plan-a-last-mile-site-delivery.md) instead.

## Who does each part of the work?

A move like this has a lot of people in it. The below table shows who does what, and where they record it.

| Work | Who | Where they record it |
| - | - | - |
| Book the crane on the Portugal job | Project coordinator | Allocation |
| Plan each road leg and name the driver | Transport coordinator | Transport order. This person is the **owner**. |
| Load the truck | Yard supervisor | Tells the transport coordinator, who sets the load to **Loading** |
| Drive the leg | Driver | Driver on the load. The transport coordinator sets **In Transit** |
| Book the sea freight | Freight forwarder | Shipment. The transport coordinator adds it |
| Confirm the crane is on site, and release it | Site supervisor | Tells the project coordinator, who sets the allocation status |
| Plan the trucks from the port to the site | Transport coordinator, with the site supervisor | Transport order |

## What do you need before you start?

You'll need the Portugal job set up, with a site and dates the crane has to be there — the project coordinator agrees those with the site supervisor. You'll also need the Sydney yard, Port Botany, and Lisbon port as places, and the crane on the books, including any mast section or counterweight that travels as its own unit.

In Idalia those are a [project](https://useidalia.com/docs/projects/introduction.md), locations, and the [asset register](https://useidalia.com/docs/assets/introduction.md). If the parts travel separately, see [Assemblies](https://useidalia.com/docs/assets/assemblies.md).

## How do you name the trip and list the plant?

The transport coordinator opens **Journeys** and creates a journey named `Lisbon tower crane`. Point it at the Portugal job, and set the **owner** to whoever is running the move.

Then open **Assets** and choose **Add assets**. Add the crane, plus any section or counterweight that travels on its own. Do this before you add the legs, so each new stage already includes the plant.

That's the trip named, owned, and loaded with the right assets.

## How do you plan the legs?

This is the high-level plan first, then the sequenced delivery steps. On **Stages**, choose **Add stage**, pick **Transport order**, **Shipment**, or **Allocation**, then **Create new** so the document stays on this journey.

For the Lisbon crane, the stages look like this:

| Order | Leg | Record | Who leads it |
| - | - | - | - |
| 1 | Sydney yard to Port Botany | Transport order | Transport coordinator |
| 2 | Port Botany to Lisbon | Shipment | Transport coordinator, with the freight forwarder |
| 3 | Lisbon port to the site | Transport order | Transport coordinator |
| 4 | Crane on the Portugal job | Allocation | Project coordinator |
| 5 | Site back to Lisbon port | Transport order | Transport coordinator |
| 6 | Lisbon to Port Botany | Shipment | Transport coordinator, with the freight forwarder |
| 7 | Port Botany back to the Sydney yard | Transport order | Transport coordinator |

On each road leg, set the pickup and the drop-off.

On each sea leg, choose **Ocean**. The freight forwarder holds the booking; you enter the **MBL No.** so status can come through from the carrier.

On the time on the job, the project coordinator sets the dates from the day the crane has to be on site to the day it leaves.

If a stage is in the wrong order, drag it. Keep the trip home on `Lisbon tower crane` — a road order, a sea booking, or a job booking can only sit on one journey, and splitting the return would split the same move.

## How do you run the trip?

As each stage completes, update the plan so you can see where the crane is and what's still ahead. You set the road orders and read the sea bookings. The project coordinator sets the time on the job.

**Planned**, **In Progress**, and **Completed** are the default names. Your workspace might use other words for booked, on the move, and finished.

1. The yard supervisor finishes loading at the Sydney yard. Set that load to **Loading**.
2. The driver leaves. Set the load to **In Transit**, and the road order to **In Progress**.
3. The truck arrives at Port Botany. Set the load and the road order to **Completed**.
4. Watch the shipment until the crane is at Lisbon port. The carrier supplies that status.
5. Run the trucks to the site. The site supervisor confirms the crane is there.
6. The project coordinator sets the allocation to **In Progress**.
7. The site releases the crane. The project coordinator sets the allocation to **Completed**.
8. Run the three return legs the same way. The last drop-off is the Sydney yard.

When that's done, the crane is home and every stage is **Completed**.

## How do you check the result?

On `Lisbon tower crane`, the same crane is on all seven stages, the last drop-off is the Sydney yard, and every stage is **Completed**. That's the whole trip, planned and tracked end-to-end.

## Common questions

### Do you put the sea freight on a road order?

No. A transport order is a road leg. The sea booking is a shipment, and the freight forwarder runs it. You add that shipment as a stage on the journey.

### Can the trip home be a second journey?

Keep it on `Lisbon tower crane`. The crane is one line on every stage, including the return. A second journey would split the same move in two.

## Next

A local yard-to-site in Sydney is a different job. See [Last-mile site delivery](https://useidalia.com/docs/guides/plan-a-last-mile-site-delivery.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.