> For the complete documentation index, see [llms.txt](https://i4trust.ishare.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://i4trust.ishare.eu/open-call-1/smartediport.md).

# SmartEDIPort

The maritime-port logistics chain in Smartports encounters challenges such as fragmented data sharing, duplicate information, extensive radio or email communications, and a paper-intensive administrative process. The Port of Huelva introduced [SmartEDIPort](https://hiades.es/smartediport/) to optimise the maritime-port logistics chain and improve port operations. SmartEDIPort further aims to optimise ship berthing forecasts, streamline loading and unloading operations, and predict traffic flow at container terminal gates to improve the efficiency, safety, and coordination of maritime and land operations.

SmartEDIPort employs a FIWARE-powered solution integrated with a Marketplace to facilitate smooth data exchange, using the core of [iSHARE specifications](https://dev.ishare.eu/) for access protection and tracking. This enables the implementation of an Identity Management (IdM) system acting as an Authorization Registry, with a Decision Point (PDP) and Policy Enforcement Point (PEP) to provide security and usage analysis. The [iSHARE Participant Registry](https://trustbok.ishare.eu/apply-ishare/participant-registry), in coordination with the Identity Provider and Authorization Registry, ensures additional validation of whether participants sharing data within the SmartEDIPort data space are trusted organisations. 

SmartEDIPort, with its new architecture built upon i4Trust standards, enables multiple companies to optimise the maritime-port logistics chain by implementing Just in Time methods ensuring that ships, cargo, and related operations are efficiently coordinated and timed to minimise delays, reduce congestion, and improve overall operational efficiency. 

Learn more about the SmartEDIPort in the Impact Story.

{% file src="/files/cTyCbAa705CQvGVmGxJ6" %}

#### Contributors:

<table data-view="cards"><thead><tr><th></th><th></th><th></th></tr></thead><tbody><tr><td><img src="/files/Zkgpnm9JRPCfGAxoHCSb" alt="" data-size="original"></td><td></td><td></td></tr><tr><td><img src="/files/vs9wSBhOUFdEqht1HA41" alt="" data-size="original"></td><td></td><td></td></tr><tr><td><img src="/files/7IlcUlZahGBqJjFOJXz7" alt="" data-size="original"></td><td></td><td></td></tr><tr><td><img src="/files/CclhhAZmX0wy1nDylgSf" alt="" data-size="original"></td><td></td><td></td></tr><tr><td><img src="/files/Q3jWIV7hUgmooI3xyOie" alt="" data-size="original"></td><td></td><td></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://i4trust.ishare.eu/open-call-1/smartediport.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.