Cycle C12 updates, Q4 2023
Hey folks 👋 We are eager to unveil a series of noteworthy updates.
We've dedicated ourselves to refining and enhancing our carbon emissions calculation solutions, ensuring your experience reaches new heights. Let's jump in and explore the latest developments!
✨ New & Improved
🆕 ⛵ Execution API
Geared towards assisting freight forwards and BCOs to make sustainable decisions at the booking stage, this addition complements our existing Shipment API and CO2 Plan, offering a global solution from estimating and reporting emissions to planning and executing emission reduction.
In pursuit of a holistic approach, we worked on addressing the challenges encountered during the booking stage, and came up with a new API called Execution. Our /itinerary/v2/execution offers detailed itinerary information for ready-to-sail shipments, letting you prioritize transit time or sustainability.
How does the Execution API works?
How does the Execution API works?Endpoints description
The Execution endpoint provides a list of the best available itinerary options and its carbon emissions details, among the next departures of a maritime carrier, from a specified date.
It is made of two endpoints:
- an itinerary endpoint returning the detailed itinerary information, its hash, the total CO2e. With the itinerary endpoint (/itinerary/v2/execution), you gain the ability to choose the greenest option among upcoming vessel departures, selecting from the best available itineraries, sorted by fastest or greenest.
- a separate CO2 endpoint, returning the CO2 breakdown details per itinerary by hash system.
In response, the user gets is a list feature collections of available itineraries, its hash, and total CO2. The properties include details such as : duration, departure, arrival, locations, distance, mode, service ID (you can retrieve the service details with our Search API), asset (vessel) details, port of calls, CO2 emissions.
Example
Let's take a sneak peak at it.
Let's say I have a shipment ready to ship from Santos to Cartagena. I want to explore solutions to ship it between December 7th and 25th, with CMA CGM (including its alliance).
curl --request GET \
--url 'https://api.searoutes.com/itinerary/v2/execution?fromLocode=BRSSZ&fromDate=2023-12-07T15:00:00Z&toDate=2023-12-25T00:00:00Z&sortBy=CO2&carrierScac=CMDU&toLocode=COCTG' \
--header 'accept: application/json' \
--header 'x-api-key: <YOUR_API_KEY>'
[
{
"type": "FeatureCollection",
"features": [
{
"type": "Feature",
"properties": {
"duration": {
"ms": 1234800000
},
"departure": {
"dateTime": "2023-12-21T17:00:00Z",
"timestamp": 1703178000000
},
"arrival": {
"dateTime": "2024-01-05T00:00:00Z",
"timestamp": 1704412800000
},
"from": {
"locode": "BRSSZ",
"name": "SANTOS"
},
"to": {
"locode": "COCTG",
"name": "CARTAGENA, CO"
},
"distance": 8047811,
"mode": "SEA",
"serviceId": 1600,
"asset": {
"imo": 9629469,
"name": "Swansea ",
"minTEU": 5000,
"maxTEU": 7999,
"fuelType": "VLSFO"
},
"calls": [
{
"locode": "BRSSZ",
"name": "SANTOS"
},
{
"locode": "BRRIO",
"name": "RIO DE JANEIRO"
},
{
"locode": "BRSSA",
"name": "SALVADOR"
},
{
"locode": "COCTG",
"name": "CARTAGENA, CO"
}
],
"co2e": 412919
},
"geometry": {
"type": "LineString",
"coordinates": []
}
}
],
"properties": {
"hash": "it_76JtGpWbd5H"
}
},
{
"type": "FeatureCollection",
"features": [
{
"type": "Feature",
"properties": {
"duration": {
"ms": 1234800000
},
"departure": {
"dateTime": "2023-12-07T17:00:00Z",
"timestamp": 1701968400000
},
"arrival": {
"dateTime": "2023-12-22T00:00:00Z",
"timestamp": 1703203200000
},
"from": {
"locode": "BRSSZ",
"name": "SANTOS"
},
"to": {
"locode": "COCTG",
"name": "CARTAGENA, CO"
},
"distance": 12077862,
"mode": "SEA",
"serviceId": 1600,
"asset": {
"imo": 9629457,
"name": "Cardiff ",
"minTEU": 5000,
"maxTEU": 7999,
"fuelType": "VLSFO"
},
"calls": [
{
"locode": "BRSSZ",
"name": "SANTOS"
},
{
"locode": "BRRIO",
"name": "RIO DE JANEIRO"
},
{
"locode": "BRPNG",
"name": "PARANAGUA"
},
{
"locode": "BRSSA",
"name": "SALVADOR"
},
{
"locode": "BRRIO",
"name": "RIO DE JANEIRO"
},
{
"locode": "BRSSA",
"name": "SALVADOR"
},
{
"locode": "COCTG",
"name": "CARTAGENA, CO"
}
],
"co2e": 575823
},
"geometry": {
"type": "LineString",
"coordinates": []
}
}
],
"properties": {
"hash": "it_IrnKeOxjG6A"
}
},
{
"type": "FeatureCollection",
"features": [
{
"type": "Feature",
"properties": {
"duration": {
"ms": 1234800000
},
"departure": {
"dateTime": "2023-12-14T17:00:00Z",
"timestamp": 1702573200000
},
"arrival": {
"dateTime": "2023-12-29T00:00:00Z",
"timestamp": 1703808000000
},
"from": {
"locode": "BRSSZ",
"name": "SANTOS"
},
"to": {
"locode": "COCTG",
"name": "CARTAGENA, CO"
},
"distance": 8047811,
"mode": "SEA",
"serviceId": 1600,
"asset": {
"imo": 9409209,
"name": "CMA CGM Maupassant",
"minTEU": 5000,
"maxTEU": 7999,
"fuelType": "VLSFO"
},
"calls": [
{
"locode": "BRSSZ",
"name": "SANTOS"
},
{
"locode": "BRRIO",
"name": "RIO DE JANEIRO"
},
{
"locode": "BRSSA",
"name": "SALVADOR"
},
{
"locode": "COCTG",
"name": "CARTAGENA, CO"
}
],
"co2e": 784377
},
"geometry": {
"type": "LineString",
"coordinates": []
}
}
],
"properties": {
"hash": "it_KrsrbyLgSRe"
}
}
]
How does this help reducing my emissions?
- If I chose to ship early on Dec 7th on with Cardiff (9629457), my shipment will arrive Dec 22nd (15 days transit time) and have emitted 576 kg of CO2e.
- If I chose to wait and ship on Dec 21st on Swansea (9629469), my shipment will arrive Jan 5th (same transit time) and have emitted 413 kg of CO2e.
Resulting in a 28% of emissions savings on this shipment !
On a side note, here is an example of how to use the hash system and get the CO2 breakdown, with the first itinerary returned in the above example.
curl --request GET \
--url 'https://api.searoutes.com/itinerary/v2/execution?fromLocode=BRSSZ&fromDate=2023-12-07T15:00:00Z&toDate=2023-12-25T00:00:00Z&sortBy=CO2&carrierScac=CMDU&toLocode=COCTG' \
--header 'accept: application/json' \
--header 'x-api-key: <YOUR_API_KEY>'
{
"co2e": {
"total": 412919,
"wtt": 61012,
"ttw": 351907,
"intensity": 0.00513
},
"parameters": {
"mode": "SEA",
"carrierId": null,
"carrierScac": "CMDU",
"from": {
"locode": "BRSSZ"
},
"to": {
"locode": "COCTG"
},
"containerSizeTypeCode": null,
"weight": null,
"nContainers": null
},
"properties": {
"legs": [
{
"co2e": {
"total": 412919,
"wtt": 61012,
"ttw": 351907,
"intensity": 0.00513
},
"properties": {
"dataType": null,
"distance": 8047811,
"secaIntersection": 0,
"asset": {
"imo": 9629469,
"name": "Swansea ",
"minTEU": 5000,
"maxTEU": 7999,
"fuelType": "VLSFO"
},
"tradeLane": null
}
}
],
"weight": 10000.0,
"nTEU": 1.0,
"containerSizeTypeCode": "20GP"
}
}
Beta testing phase
Beta testing phaseThis endpoint is now available in beta. To ensure a focused and effective testing phase, we'll initially roll it out to a limited number of clients.
Whether you're interested in being part of the next beta testing phase; wish to express your interest for the final product or have inquiries, feel free to reach out to us. We'll be happy to hear about it.
📉 Emissions Dashboards in Searoutes App
At Searoutes, we're here to make it simpler for you. Our goal is to help you understand and report your emissions while strategically planning shipments with greener solutions.
We've introduced embedded emissions dashboards right within our application:
- reporting dashboard:
- get a report baseline to easily compare your next shipment emissions against and acknowledge your progress.
- gain visibility into your CO₂e emissions, split by carrier, location, mode of transport, and more.
- planning dashboard:
- run simulations to identify improvement potentials and establish emission reduction strategies.
- make data-driven decisions to find optimal carriers and optimize your allocations.
In this cycle, we've been fine-tuning the data, the design and user experience, making sure we deliver the right visualization tool for you, to acknowledge, explore, and plan your shipments' emissions – all in one place.
Interested in this new feature? Get in touch with us to let us know your interest !
Searoutes compliant with the latest GLEC update (v3.0)
As part of our commitment to excellence, we want to remind you that Searoutes is accredited by the Smart Freight Center and fully compliant with the GLEC Framework.
In line with our dedication to staying at the forefront of industry standards, whenever the GLEC releases updates to emissions factors, we proactively integrate these changes into our calculation models. This ensures that your experience is aligned with the latest sustainability standards.
🌱 Key Highlights:
- Precision in sustainability metrics
- Compliance assurance
- Reliable baseline for future comparisons
- Informed decision-making: with a faithful representation of your logistics' environmental impact, you can make smart decisions, driving sustainable practices.
What are the main changes to expect?
We would like to draw your attention on the evolving landscape of emissions science, which had a great impact on the updated emissions factors.
- Estimates of emissions have notably increases, particularly in the well-to-tank (WTT) part. For example:
- for LNG: + 49% in WTT emissions, resulting in +9% in WTW.
- for HFO: + 169% in WTT emissions, resulting in +13% in WTW.
- In the other hand, default trade lane emission factors have slightly gone up. As the global fleet's average speed has been reduced on some key lanes, the overall emissions increase has remained quite low. See for yourself:
- Asia to North America West Coast tradelane average: - 8% (from 71,3 to 65,7 gCO2e /t.km).
- Intra Southeast Asia tradelane average: +7% (from 117,4 to 125,3 gCO2e /t.km).
Don't hesitate to reach out if you have any questions on our latest update.
🛠 Fixes & Updates.
Location context upgrade for smarter analytics
We focused on elevating the user experience for logistics managers and empowering them with richer location context for analytics.
Let's take an example, with a request made to the /shipment/v2 API.
Below shipment request is passed with a location "from" given as coordinates, and a location "to" given as a string.
{
"orders": [
{
"type": "FCL",
"quantity": 1.0,
"sizeTypeCode": "20GP"
}
],
"legs": [
{
"from": "-46.3370503806326,-23.9251667011668",
"to": "NLRTM",
"mode": "sea",
"details": {
}
}
]
}
{
...
"legs": [
{
"from": {
"coordinates": [
-46.3370503806326,
-23.9251667011668
]
},
"to": {
"locode": "NLRTM",
"coordinates": [
4.056346273311497,
51.96013439389793
],
"city": "Rotterdam",
"country": "Netherlands",
...
}
The response for this request returns a from object in the legs which is different from the usual location object: in the case the input is coordinates, the output is coordinates only.
This lack of consistency in our API response has a double impact:
- 👨💻 From a developer standpoint, this is not REST compliant: in some cases keys in the response object are present, and in some other instances, they are not.
- 📈 For a logistics user, this doesn't provide the right location context to run proper analytics when aggregating this data.
Solution:
We revamped the API to provide enriched and consistent location context, including coordinates, city name, country, region, and tradelane for any input type.
This not only ensures REST compliance but also simplifies code implementation for developers.
Here is the new response we get, with the enhanced and consistent location context:
{
"orders": [
{
"type": "FCL",
"quantity": 1.0,
"sizeTypeCode": "20GP"
}
],
"legs": [
{
"from": "-46.3370503806326,-23.9251667011668",
"to": "NLRTM",
"mode": "sea",
"details": {
}
}
]
}
{
...
"legs": [
{
"from": {
"locode": "BRSSZ",
"coordinates": [
-46.3370503806326,
-23.9251667011668
],
"city": "Santos",
"country": "Brazil",
"region": "South America - East Coast"
},
"to": {
"locode": "NLRTM",
"coordinates": [
4.056346273311497,
51.96013439389793
],
"city": "Rotterdam",
"country": "Netherlands",
"region": "North Europe"
},
"tradeLane": "Europe to-from South America",
"mode": "sea",
...
}
🌱 Key Highlights:
- Seamless Integration Experience
- Advanced Analytics Capabilities
- Enhanced Dashboard Functionality and Readability
👀 Preview of next Cycle C13
For the upcoming cycle, we will be focusing on:
- improving our Shipment and Geocoder solutions to help you get the right location easily;
- including more available fuels for road, especially in North America;
- enhancing our dashboards solution for planning;
- working on the Execution API in beta and gathering the first feedbacks.
Stay tuned ! 
You just read our Product Update 👏
We'd love to hear what you think about these updates. Send us your feedback at [email protected]!