Hello there! Summer might be over, but we're delighted to see you back 🔆.

We've been hard at work this summer, working on a series of game-changing developments and enhancements to take your carbon emissions calculations to the next level.

So, let's dive right in and discover what's been cooking!

✨ New & Improved

Enhanced Shipment API: historical itineraries for precise CO2 emissions

We've taken a giant leap forward with our Shipment API, and incorporated historical port calls in our Ocean Freight Emission models. We call this model network-portcall-ais, it's the most accurate CO2 emission calculator to date.

So What's New?

• More accurate calculations : Our enhanced shipment/v2/report/co2 endpoint now uses historical AIS data to provide more accurate emissions calculations, based on inferred itineraries. Our algorithm recreates historical voyages by considering vessel voyages, and routings, on top of what we already used to do, i.e. vessels specific emissions.
• Flexible Inputs: our magic works for any level of information given, whether it's only locations from/to, a departure date, or with added IMO and/or carrier scac.
• Realistic Results: the most likely itineraries could be direct or multi-stop journeys, for any of those we aggregate data from the most likely itineraries and connecting vessels if needed, ensuring reliable CO2e results.

Let's take an example.

You'd like to get the emissions for a 20ST, shipped from Shanghai to Oslo on July 12th, 2023, and you know that part of the journey was done with SVEN D feeder (IMO 9302243). This feeder only operates between Rotterdam and Oslo, and you don't have the information of the mainliner.

Below an example payload on our shipment/v2/report/co2 endpoint, and the corresponding response. Notice the new field in the response "model": {"name": "network-portcalls-ais"}.

{
    "details": {
        "id": "BL1234567",
        "referenceNumber": "REF13579",
        "status": "ARRIVED"
    },
    "orders": [
        {
            "type": "FCL",
            "quantity": 1.0,
            "sizeTypeCode": "20GP"
        }
    ],
    "legs": [
        {
            "from": "CNSHA",
            "to": "NOOSL",
            "mode": "sea",
            "details": {
                "dateTime": {
                    "departure": "2023-07-12"
                },
                "vessel":{
                    "imo": "9302243"
                }
            }
        }
    ]
}

{
    "parameters": {
        "orders": [
            {
                "type": "FCL",
                "quantity": 1,
                "sizeTypeCode": "20GP"
            }
        ],
        "details": {
            "id": "BL1234567",
            "referenceNumber": "REF13579",
            "status": "ARRIVED",
            "carrier": {}
        }
    },
    "co2e": {
        "total": 796359,
        "wtt": 60719,
        "ttw": 735639,
        "intensity": 0.0039
    },
    "legs": [
        {
            "from": {
                "locode": "CNSHA",
                "coordinates": [
                    122.065505213,
                    30.617983963
                ],
                "city": "Shanghai",
                "country": "China"
            },
            "to": {
                "locode": "NOOSL",
                "coordinates": [
                    10.748964787,
                    59.882356644
                ],
                "city": "Oslo",
                "country": "Norway"
            },
            "mode": "sea",
            "parameters": {
                "details": {
                    "vessel": {
                        "imo": "9302243"
                    },
                    "dateTime": {
                        "departure": "2023-07-12"
                    },
                    "carrier": {}
                }
            },
            "properties": {
                "dataType": "MODELED",
                "distance": 20617913,
                "model": {
                    "name": "network-portcalls-ais"
                },
                "containerSizeTypeCode": "20GP",
                "orders": [
                    {
                        "type": "FCL",
                        "quantity": 1,
                        "weight": 10000,
                        "sizeTypeCode": "20GP",
                        "nTEU": 1,
                        "co2e": {
                            "total": 796359,
                            "ttw": 735639,
                            "wtt": 60719,
                            "intensity": 0.00386
                        }
                    }
                ]
            },
            "co2e": {
                "total": 796359,
                "wtt": 60719,
                "ttw": 735639,
                "intensity": 0.0039
            }
        }
    ]
}

The model name network-portcalls-ais tells you that under the hood, we've guessed (i) the transshipment port based on the carrier network and (ii) guessed the sequence of port calls for each leg of the trip. The corresponding AIS trajectory can be seen below.

Why is that so important?

To establish meaningful emissions reduction targets and sustainability goals, you need a solid baseline. Our Shipment API helps you getting it right, enabling you to set realistic, science-based targets that can drive your organization toward a more sustainable future.

As always me make it simple for you, so that whatever the inputs we choose the most accurate model.

Ongoing Improvements

• Performance enhancements underway for faster report processing.
• We have achieved 95% historical journey data coverage.

Enhanced historical AIS Data Access

We've invested significant effort to provide access to vessel trajectories dating back to 2019 and beyond, enabling you to generate traces for your shipments, or your fleet.

Let's say for instance that we'd like to get the trace of our feeder vessel around his departure date 2023-07-10. One could place the following request /vessel/v2/trace?imo=9302243&departureDateTime=2023-07-10T00:00:00Z&arrivalDateTime=2023-08-10T00:00:00Z. Below the visualization obtained by pasting the response in geojson.io.

Transparency and clarity on our CO2 methodology

We understand that transparency and clarity are essential when it comes to CO2 emissions calculations. We've addressed this with two significant improvements:

• Revamped Searoutes Website: We've clarified our website's CO2 solutions page to make it easier for you to understand our range of solutions, methodology, and the differences in input and output data.
• Model Names: We've introduced model names in the response of our /shipment API. It's our hope that it makes our methodology clearer, and that you can understand our calculation better: emissions factors, schedule information, ship characteristics, historical data, etc. Have a look at the model section on our webpage here.

We're excited about these developments and their positive impact on your business, sustainability efforts, and data transparency. We deeply value your support and feedback as we continue to refine our solutions, therefore please don't hesitate to reach out!

👀 Preview of Cycle 11

This cycle, we focus on two major developments:

• A Green Schedule Explorer: you can already compare the service of ocean carriers via our /shipment API, our APP and our dashboards. This is ahead of tender season, to optimize logistics holistically. What we are building is the ability for you to follow through on your allocation strategy, in the day to day execution. You will have the ability to compare the vessels leaving this week for a given carrier, or across carriers. This will help your short-term operations, by allowing you to choose the greenest next departures for your shipments.
• Analytics dashboards: all the power of our APIs in a simple dashboard to help you keep a 360° vision on your carbon footprint. This will allow you to monitor your progress and stay on track!

📘

You just read our Product Update 👏

We'd love to hear what you think about these updates. Send us your feedback at [[email protected]](mailto:[email protected])!