Emission scenario analysis is used to compare different routes for the same relation. For example, if different proposals for routes are received from different carriers and transport services during a procurement process. Each carrier can also define different alternative routes. 

All combinations of routes are calculated, as well as existing profiles configured on the logged-in account. This provides a good overview of the alternatives compared to the current situation. 

Template 

• Download the template for emission scenario. 

• Open the file and start configuring the scenarios to simulate 

Configuration 

The template consists of two tabs; Load and RoutingTable. 

Load tab 

Under the Load tab, you define the shipments you want to simulate emissions for.

To link a relation with the different routes to be calculated, a key is needed. This key is the AllocationID column. 

Note! It is also important to understand that the origin and destination addresses MUST match the solutions with the same AllocationId as the shipment row. 

The ConsignmentId and ShippingId columns are not mandatory. When used, the system can calculate the fill rate for each shipment. The system then assumes that all shipments with the same ShippingID have been transported on the same vehicle and that no other goods besides these are on the vehicle. 

The ConsignmentId column is used to trace the different legs in the simulation results to the correct relation (AllocationID). 

RoutingTable tab 

Under the RoutingTable tab, you define the different routes and for each relation. 

In the example above, three different scenarios for the same relation are evaluated. SolutionID is the name of the specific scenario to be tested. Carrier is the name of the carrier. 

It is possible to configure up to 10 legs for each row in the RoutingTable. Columns marked with (*) are not mandatory. 

Simulate scenarios 

When the configuration is complete, it is time to run the simulation. 

1. Upload the completed template. 

2. Start the analysis. 

3. Enter a name and choose how the system should calculate the fill rate. 

Result 

The result is presented in two new tabs in the uploaded file. Under Result – Route, the aggregated result for all legs for each row in the RoutingTable is displayed 

In the example above, we see 4 rows. The first row is a calculation for the current situation configured on the logged-in user. Rows 2-4 correspond to the scenarios defined in the RoutingTable. 

Under the Result – Leg tab, one row is displayed per leg and scenario. In other words, if a scenario is defined to include 5 legs, it will result in 5 rows in this table.