Skip to main content
Challenge

Build a Port Congestion Aware Carbon Footprint and Delay Explainer

Correlate Singapore vessel queue data from open datasets with bunker fuel consumption. Synthesize maritime emission audit logs and clear delay explanations for shippers.

Business OperationsHosted by Vera
Challenge brief

What you are building

The core problem, expected build, and operating context for this challenge.

Correlate Singapore vessel queue data from open datasets with bunker fuel consumption. Synthesize maritime emission audit logs and clear delay explanations for shippers.

Maritime ESG and Customer Experience Analyst

Ingest vessel anchorage wait times and port arrival schedules from simulated Singapore maritime open data feeds.

Calculate auxiliary engine emissions and fuel burn incurred during prolonged anchorage idling.

Map carbon intensity increases against standard ocean voyage baselines.

Draft customer delay notices that detail operational anchorage hold-ups and ESG emission impact.

Emissions dashboard displaying anchorage wait heatmaps, vessel bunker calculations, and draft customer notices.

Simulated maritime vessel movement records modeled on MPA Singapore public vessel arrival APIs. Starter examples below are synthetic. They are not downloaded records.

Singapore open data API Applies data.gov.sg dataset querying and API v1 metadata patterns to access public maritime vessel queue and port arrival metrics.

dspy, python, fastapi. DSPy compiles robust prompt logic to convert vessel telemetry and auxiliary fuel calculations into clear ESG explanations. Hosted reasoning model via API for generating empathetic yet quantitatively grounded customer service communications.

Submit runnable source, pinned dependencies, setup commands, a working interface, example outputs, and a recorded end-to-end demo. Include tests and an action log.

Calculate auxiliary engine carbon emissions using IMO standard conversion factors (3.114 g CO2/g fuel).

Correlate anchorage duration in Singapore waters with container delivery delay milestones.

Generate a structured delay explanation citing verified port anchorage wait conditions.

Output an ESG ledger update documenting Scope 3 transport emission increments.

```json [ { "input": { "vessel_call_id": "CALL-SIN-9912", "vessel_name": "Ocean Singapore", "scheduled_berth_time": "2025-03-15T02:00:00Z", "actual_berth_time": "2025-03-16T14:00:00Z", "anchorage_area": "Eastern Anchorage", "aux_engine_fuel_rate_mt_per_day": 3.2, "cargo_teus_onboard": 2400 }, "expected_output": { "anchorage_wait_hours": 36, "total_bunker_burned_mt": 4.8, "additional_co2_tonnes": 14.95, "co2_per_teu_kg": 6.23, "customer_notice": "Vessel Ocean Singapore experienced 36 hours anchorage waiting due to high terminal berth density. Total Scope 3 increment: 6.23 kg CO2/TEU." } }, { "input": { "vessel_call_id": "CALL-SIN-9913", "vessel_name": "Lion City Express", "scheduled_berth_time": "2025-03-15T08:00:00Z", "actual_berth_time": "2025-03-15T09:30:00Z", "anchorage_area": "Western Anchorage", "aux_engine_fuel_rate_mt_per_day": 2.5, "cargo_teus_onboard": 1800 }, "expected_output": { "anchorage_wait_hours": 1.5, "total_bunker_burned_mt": 0.16, "additional_co2_tonnes": 0.5, "co2_per_teu_kg": 0.28, "customer_notice": "Vessel Lion City Express berthed within normal operational buffer (1.5 hours). No material delay or ESG adjustment required." } } ] ```

Emissions calculations are internal estimates and do not constitute formal IMO compliance filings or legal liabilities. Use mock external writes. Require human review before any real deployment.

Rules

Participation guide

Emissions calculations are internal estimates and do not constitute formal IMO compliance filings or legal liabilities. Use mock external writes and human review.

Delivery guide

How work is evaluated

Evaluation

Calculate auxiliary engine carbon emissions using IMO standard conversion factors (3.114 g CO2/g fuel). Correlate anchorage duration in Singapore waters with container delivery delay milestones. Generate a structured delay explanation citing verified port anchorage wait conditions. Output an ESG ledger update documenting Scope 3 transport emission increments.

Submission format

Runnable source, pinned dependencies, setup commands, working interface, example outputs, recorded demo, tests, and action logs.

Datasets

Challenge datasets

Public datasets, plus the private datasets you have access to.

Evaluation rubric

How submissions are scored

These dimensions define what the evaluator checks and which criteria separate a passable run from a strong one.

Dimensions
4 scoring checks
Binary
1 pass or fail dimensions
Ordinal
3 scaled dimensions
Dimension 1

Complete workflow

Ingest vessel anchorage wait times and port arrival schedules from simulated Singapore maritime open data feeds. Calculate auxiliary engine emissions and fuel burn incurred during prolonged anchorage idling. Map carbon intensity increases against standard ocean voyage baselines. Draft customer delay notices that detail operational anchorage hold-ups and ESG emission impact.

Score scale
012
Score 0

Missing or incorrect.

Score 1

Partly complete, with documented gaps.

Score 2

Complete, with reproducible evidence.

Dimension 2

Correctness and evidence

Calculate auxiliary engine carbon emissions using IMO standard conversion factors (3.114 g CO2/g fuel). Correlate anchorage duration in Singapore waters with container delivery delay milestones. Generate a structured delay explanation citing verified port anchorage wait conditions. Output an ESG ledger update documenting Scope 3 transport emission increments.

Score scale
012
Score 0

Missing or incorrect.

Score 1

Partly complete, with documented gaps.

Score 2

Complete, with reproducible evidence.

Dimension 3

Review interface

Emissions dashboard displaying anchorage wait heatmaps, vessel bunker calculations, and draft customer notices.

Score scale
012
Score 0

Missing or incorrect.

Score 1

Partly complete, with documented gaps.

Score 2

Complete, with reproducible evidence.

Dimension 4

Safe execution

Emissions calculations are internal estimates and do not constitute formal IMO compliance filings or legal liabilities.

Binary check

This dimension contributes its full weight only when the submission satisfies the requirement. Partial credit is not awarded.

Learning goals

What you should walk away with

  • Ingest vessel anchorage wait times and port arrival schedules from simulated Singapore maritime open data feeds.

  • Calculate auxiliary engine emissions and fuel burn incurred during prolonged anchorage idling.

  • Map carbon intensity increases against standard ocean voyage baselines.

  • Draft customer delay notices that detail operational anchorage hold-ups and ESG emission impact.

Resources and assets

Reference links and supporting material

Dataset notes

Simulated maritime vessel movement records modeled on MPA Singapore public vessel arrival APIs. Supplied starter examples are synthetic, not source extracts.

Challenge setup

Configuration summary for this challenge.

Challenge input

Input details are not configured.

DSPy

Prompt and LM program optimization framework.

Evaluated output

No output checks are configured.

Evaluation checks
  • Ingest vessel anchorage wait times and port arrival schedules from simulated Singapore maritime open data f...
  • Calculate auxiliary engine carbon emissions using IMO standard conversion factors (3.114 g CO2/g fuel). Cor...
  • Emissions dashboard displaying anchorage wait heatmaps, vessel bunker calculations, and draft customer noti...
Configured evaluation evidence
  • 2 public reference cases
Configured runtime
  • 3 configured tools

Summary shows the first task, up to three tools, and up to three evidence items. Open the technical recipe to view all configured items.

View technical recipe

Configured tools

Action Space
  • DSPy · Optional
Training Infra
  • DSPy · Optional
Orchestration
  • DSPy · Optional

Evaluation contract

  • Complete workflow · Weight 40
  • Correctness and evidence · Weight 30
  • Review interface · Weight 20
  • Safe execution · Weight 10

Reference cases

  • 2 public reference cases

Workflow tasks

No workflow tasks are configured.

Recipe freeze marker

No recipe freeze time is recorded.

Frequently Asked Questions about Build a Port Congestion Aware Carbon Footprint and Delay Explainer