> 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/collmi.md).

# CollMi

The growth of e-commerce and the increased expectation for rapid deliveries have placed considerable pressure on the logistics industry to optimise urban deliveries and expand into rural areas.

Collaborative micro-hubs (CMHs) introduce a new logistical concept where companies share resources to deliver parcels through a network of common logistics centres installed in strategic urban locations. CMHs enable logistics companies to reduce operating costs, improve service quality, and cover wider geographical areas without large initial investments and risk, but their implementation faced major setbacks.

The logistics industry lacks integrated digital communication mechanisms and often relies on unstructured email exchanges to coordinate shipments. There was an urgent need for intelligent EDI processes bundled in an easy-to-use solution that accommodates smaller companies that are unable to afford custom logistics management systems.

CollMi, with [i4Trust Building Blocks](https://github.com/i4Trust/building-blocks), offers a solution to ensure secure access control, leveraging [iSHARE](https://framework.ishare.eu/) and FIWARE components for trusted data-sharing processes. With all participants registered as data space members, package context information is provided to retailers via the shared context broker using iSHARE-compliant access policies for identification, authentication, and authorisation. 

This solution eliminates the need for manual status checks, provides reliable customer information, and supports strategic business decisions.

#### Contributors:

<table data-view="cards"><thead><tr><th></th><th></th><th></th></tr></thead><tbody><tr><td><img src="/files/pXwYYqMx9wbY7AIDGxWp" alt="" data-size="original"></td><td></td><td></td></tr><tr><td><img src="/files/6tYMufmw2oReuBbyHLQq" alt="" data-size="original"></td><td></td><td></td></tr><tr><td><img src="/files/6muPRik5bFyP10y4PKiw" alt="" data-size="original"></td><td></td><td></td></tr><tr><td><img src="/files/fTi09Y6GRIyTMHcusowR" alt="" data-size="original"></td><td></td><td></td></tr><tr><td></td><td><img src="/files/75dUHS7ptFhAOxNinEG7" alt="" data-size="original"></td><td></td></tr><tr><td><img src="/files/LFlZWerN4fXzXTcJdq3o" 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/collmi.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.