Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add logistics use case kit #1154

Merged
merged 64 commits into from
Feb 20, 2025
Merged
Show file tree
Hide file tree
Changes from 62 commits
Commits
Show all changes
64 commits
Select commit Hold shift + click to select a range
317930b
created folder structure for Logistics Kit
Grand-Thibault Oct 10, 2024
ec0a9a1
Merge pull request #1 from Grand-Thibault/create-logistics-kit-folder…
Grand-Thibault Oct 16, 2024
531bd53
added Logistics Kit to sidebar
Grand-Thibault Oct 16, 2024
f735f5f
fixed indentation for DCM
Grand-Thibault Oct 16, 2024
8e958e3
sorted top bar nav alphabetically and added Logistics
Grand-Thibault Oct 16, 2024
4c47a82
fixed wrong link to Logistics
Grand-Thibault Oct 16, 2024
e9086c5
added Logistics KIT to gallery
Grand-Thibault Oct 17, 2024
7f3d3bd
added logistics kit banner
Grand-Thibault Oct 17, 2024
c711527
Update page_adoption-view.md
klanir123 Oct 31, 2024
5852016
Merge branch 'eclipse-tractusx:main' into add-logistics-kit
stephanbcbauer Nov 7, 2024
14d3cfd
(doc) updated logistics logo to newest version, added license files
Grand-Thibault Nov 25, 2024
09a492d
(chore) fixed linting issues
Grand-Thibault Nov 25, 2024
83b6712
(doc) fixed wrong link
Grand-Thibault Nov 25, 2024
4174cce
(doc) removed <>
Grand-Thibault Nov 25, 2024
d7d900d
reviewed to line 33
corinastolz Jan 29, 2025
5af6394
review line 48
corinastolz Jan 29, 2025
f17cd2c
review line 49
corinastolz Jan 29, 2025
98f8c0c
Link at image inserted
klanir123 Jan 29, 2025
013337e
Create LogisticTwins.png
klanir123 Jan 29, 2025
9547b5c
Add files via upload
klanir123 Jan 29, 2025
f1b4309
Delete docs-kits/kits/Logistics Kit/asset directory
klanir123 Jan 29, 2025
6506b3f
Create assets
klanir123 Jan 29, 2025
0d9044f
Delete docs-kits/kits/Logistics Kit/assets
klanir123 Jan 29, 2025
bb2ae1b
Create LogisticTwins.png
klanir123 Jan 29, 2025
d43aa05
Add files via upload
klanir123 Jan 29, 2025
f8c219d
bugfix
klanir123 Jan 29, 2025
9531aaa
bugfix
klanir123 Jan 29, 2025
e62e2d6
Create page_changelog.md
jSchuetz88 Feb 3, 2025
fdb414b
changes to line 56
corinastolz Feb 5, 2025
f4fbc3b
changes to line 97
corinastolz Feb 5, 2025
f4027a9
Create page_adoption-view-customs.md for customs
klanir123 Feb 5, 2025
c5a9234
Adoption View for Customs
klanir123 Feb 5, 2025
e3b9e6c
Files uploaded
klanir123 Feb 6, 2025
f1c1188
Add Header for logistic and customs
klanir123 Feb 6, 2025
ac96989
Bugfix Link to logistic
klanir123 Feb 6, 2025
e54fbb2
Typo
klanir123 Feb 6, 2025
f78c59d
double Business Value removed
klanir123 Feb 6, 2025
a08c0fb
Update sidebarsDocsKits.js for update naming Logistics and Customs KIT
klanir123 Feb 6, 2025
2c70bfd
Review hints added
klanir123 Feb 7, 2025
e4b0e33
Bugfix
klanir123 Feb 7, 2025
d915505
BugFix lineFeed
klanir123 Feb 7, 2025
fd3a501
insert Logistic and Custom Kits in sidebar
klanir123 Feb 7, 2025
f2ef8c6
fixed linting issues
Grand-Thibault Feb 12, 2025
1b5727f
fixed linting issues
Grand-Thibault Feb 12, 2025
916d856
removed redundant page headers
Grand-Thibault Feb 12, 2025
ca717ab
updated changelog
Grand-Thibault Feb 12, 2025
38385e1
moved changelog
Grand-Thibault Feb 12, 2025
f7bc732
updated sidebar positions
Grand-Thibault Feb 12, 2025
c955a56
added license files
Grand-Thibault Feb 12, 2025
3b6c1b9
Merge branch 'main' into add-logistics-kit
Grand-Thibault Feb 12, 2025
b4f5046
fixed sidebar
Grand-Thibault Feb 12, 2025
7285f86
fixed sidebar
Grand-Thibault Feb 12, 2025
7baf576
Merge branch 'eclipse-tractusx:main' into add-logistics-kit
stephanbcbauer Feb 12, 2025
88c852b
fixed sidebarsDocsKits
Grand-Thibault Feb 14, 2025
5a36b0b
fixed DCM in SidebarsDocsKits
Grand-Thibault Feb 14, 2025
a174e85
fixed sidebarsDocsKits
Grand-Thibault Feb 14, 2025
74c13e5
fixed sidebar
Grand-Thibault Feb 14, 2025
a363121
fixed wrong image reference
Grand-Thibault Feb 17, 2025
734583c
fixed linting issue
Grand-Thibault Feb 17, 2025
24a98e8
fixed wrong reference
Grand-Thibault Feb 17, 2025
af56339
renamed logistics kit folder and updated references
Grand-Thibault Feb 17, 2025
bee7411
fixed url in license files
Grand-Thibault Feb 19, 2025
4be1ba3
Merge branch 'main' into add-logistics-kit
stephanbcbauer Feb 20, 2025
7922754
format file
stephanbcbauer Feb 20, 2025
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
---
id: Software Development Logistics Kit
title: Software Development View
description: "Logistics Kit"
sidebar_position: 1
---

![Logistics kit banner](@site/static/img/kits/logistics/logistics-kit-logo.drawio.svg)
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
5 changes: 5 additions & 0 deletions docs-kits/kits/logistics-kit/assets/LogisticTwins.png.license
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
This work is licensed under the CC-BY-4.0

- SPDX-License-Identifier: CC-BY-4.0
- SPDX-FileCopyrightText: 2024 Contributors to the Eclipse Foundation
- Source URL: https://github.com/eclipse-tractusx/eclipse-tractusx.github.io/docs-kits/kits/logistics-kit/assets/LogisticTwins.png
1 change: 1 addition & 0 deletions docs-kits/kits/logistics-kit/assets/pullCustoms.svg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
5 changes: 5 additions & 0 deletions docs-kits/kits/logistics-kit/assets/pullCustoms.svg.license
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
This work is licensed under the CC-BY-4.0

- SPDX-License-Identifier: CC-BY-4.0
- SPDX-FileCopyrightText: 2024 Contributors to the Eclipse Foundation
- Source URL: https://github.com/eclipse-tractusx/eclipse-tractusx.github.io/docs-kits/kits/logistics-kit/assets/pullCustoms.svg
1 change: 1 addition & 0 deletions docs-kits/kits/logistics-kit/assets/pushCustoms.svg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
5 changes: 5 additions & 0 deletions docs-kits/kits/logistics-kit/assets/pushCustoms.svg.license
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
This work is licensed under the CC-BY-4.0

- SPDX-License-Identifier: CC-BY-4.0
- SPDX-FileCopyrightText: 2024 Contributors to the Eclipse Foundation
- Source URL: https://github.com/eclipse-tractusx/eclipse-tractusx.github.io/docs-kits/kits/logistics-kit/assets/pushCustoms.svg
129 changes: 129 additions & 0 deletions docs-kits/kits/logistics-kit/customs/page_adoption-view-customs.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,129 @@
---
id: Adoption View Customs Kit
title: Adoption View Customs
description: "Customs Kit"
sidebar_position: 1
---

![Logistics kit banner](@site/static/img/kits/logistics/logistics-kit-logo.drawio.svg)

## Vision & Mission

### Vision

The transport path of parts, batches or vehicles includes the terms of customs. Goods that are given preference at customs, receive preferential tariff rates, which are generally lower or even zero. Therefore, a long-term supplier's declaration for the goods is necessary. By defining a standardized data model for this long-term supplier's declarations, exchanging customs data and in the long run calculating the preference status becomes consistent. By standardizing and digitalizing the data exchange, the Customs KIT defines the basis of a more efficient customs process and finally ensures a robust calculation result.

### Mission

The foundation of the industry core is used and combined with elements of the Customs KIT to ensure that all relevant customs information like origin information, trade relations and contact information are considered. Key value of transferring customs information is to obtain the long-term supplier's declaration. The Customs KIT describes two ways of exchanging customs information. The pull of customs information by using digital twins based on the industry core and push of customs information by using the standardized message-based data exchange within Catena-X. With this customs information it is possible to determine the preference status, the basis to decide on the customs preferences. The overall objective of the following definition is the reduction of non-digital data exchange in the process of obtaining the long-term supplier's declaration. By standardizing the data exchange within the customs process the Customs KIT contributes to enlarge the digital way of representing the value chain of parts, batches and vehicles.

## Today’s Challenge & Business Value

### Today’s Challenge

A challenging process is necessary to fulfill the requirements of customs preferences. In some areas data exchange still takes place in non-digital form, by sending physical documents. The resulting manual and redundant data entry as well as transfer in the respective portals by suppliers and customers is extremely time-consuming and increases the risk of input errors. To avoid this costly process, some companies even ignore potential customs preferences. In most cases, there is no standardized interface available, that’s why proprietary interfaces are used instead, which makes interoperability between different systems much more difficult.

### Business Value

Establishing a standardized interface between all tier levels is crucial to achieve interoperability and compatibility between different systems and applications. To enlarge the digital data exchange, a consistent format is used that works both in push and in pull mode. This is realized via a standardized data model and the use of digital twins and EDCs (Eclipse Data Connectors) as a mandatory technical component for secure data exchange in a Catena-X network. By reducing manual effort for suppliers and customers and applying a consistent preference calculation, efficiency increases. A standardized approach furthermore leads to a full utilization of tariff reduction or exemption under free trade and preference agreements, which can result in significant competitive advantages.

## Use Case

In a preference agreement, customs privileges (preferences) are agreed upon. This means that an import into a country with such an agreement has been concluded can be customs-free or at least customs-reduced. However, the goods must meet certain origin rules that are specified in the preference agreement. For evaluating the preference status, companies are creating a preference calculation. This is a central calculation method to determine whether exported goods have the right for a preference (preference entitlement). The aim of doing a preference calculation is tariff reduction or exemption in the receiving country within the scope of free trade and preference agreements. Depending on the customs rate, the preferential origin can lead to a competitive advantage, as higher sales prices can be offset in this way. In addition, foreign customers often require preferential origin.

To demonstrate that the goods meet these origin rules, the proof of preferential origin must be presented during the import. A proof is provided by a supplier's declaration. This is a declaration in which a supplier makes statements regarding the preferential origin of the goods supplied. In a supplier's declaration for goods with preferential origin status the preferential origin country of the goods must be certified. This certificate guarantees a recipient the origin of a product in accordance with a specific preference rule and serves as the only possible evidence for an exporter to apply for or issue a proof of preferential origin. Supplier's declarations for a single consignment of goods are also called individual supplier's declarations. Long-term supplier's declarations, on the other hand, are one-time declarations that are valid for deliveries over a longer period. They therefore cover consignments of similar goods over a certain period. The requirement for issuing a long-term supplier's declarations is that the origin of the goods is secured during the entire period of validity.

Every company divides the trade agreements into different and individual zones. To standardize the customs information this classification is resolved in the aspect model “customsInformation” and consolidated into a single piece of information. After receiving the data, the consumer must do an individual transformation to assign the trade agreements back to the self-defined zones.

## Data exchange of customs information

### Push of customs notification

1. The receiver (customer) must provide a connector asset for notifications in the Eclipse Data Connector (EDC).
2. The receiver (customer) sends a request to the sender (supplier) with a list of part numbers to ask for preference master data.
a. Proceeding as usual by email, post, etc.
b. Using a “request notification” based on the Notification API
3. The sender (supplier) accepts the request depending on the type of the transmission of the request.
4. The sender (supplier) creates a customs notification to send preference information.
5. The sender (supplier) initiates a contract negotiation to get a contract agreement.
6. A contract negotiation takes place between the sender (supplier) and the receiver (customer) by using their Eclipse Data Connectors (EDC).
7. After a successful contract negotiation, the sender (supplier) sends the customs notification via a HTTP POST request to the receiver (customer) via the dataplane endpoint from the contract agreement.

![PushCustoms](../assets/pushCustoms.svg)

### Pull of customs information

1. The Data Consumer (customer) sends a request to the Data Provider (supplier) with a list of part numbers to ask for preference master data.
a. Proceeding as usual by email, post, etc.
b. Using a “request notification” based on the Notification API
2. The Data Provider (supplier) accepts the request depending on the type of the transmission of the request.
3. The Data Provider (supplier) creates an aspect model “customsInformation” and saves it at the Submodel Server if it does not already exist.
4. The Data Provider (supplier) creates a digital twin for each requested part if it does not already exist (a) and adds the Submodel Descriptor for the created aspect model to the digital twin (b).
5. The Data Provider (supplier) registers a new created digital twin to the decentral twin registry (DTR).
6. The Data Provider (supplier) creates a contract definition consisting of the asset and policy and takes it to the Eclipse Data Connector (EDC).
7. The Data Consumer (customer) initiates a contract negotiation to get a contract agreement. A contract negotiation takes place between the Data Provider (supplier) and the Data Consumer (customer) by using their Eclipse Data Connectors (EDC).
8. After a successful contract negotiation, the Data Consumer (customer) pulls the aspect model “customsInformation” (json) from the Submodel Server of the Data Provider (supplier).

![PullCustoms](../assets/pullCustoms.svg)

## Signature

When exchanging data, confirmation of the transmitted data is required at a personal level. This means that it must be clearly defined which person has provided this data, which position this person occupies in the company and supplemented by contact information such as telephone number and email. Confirmation can be provided in different ways, for example by authorizing a user account for a portal with a user and password or by signing a document when the data is handed over.
In order to fulfil this personal confirmation requirement for data exchange via Catena-X, a digital solution is required that is equivalent to a signature and is accepted by customs authorities. One possibility would be the use of a digital signature. The use case is currently reviewing existing solutions in Catena-X and discussing them with the customs authorities.

## Aspect Model

Aspect models are mostly easy to create by transforming a company's internal data into the target aspect model. Transformations are mostly straightforward in these cases. If necessary, special steps in creating aspect models are mentioned in the corresponding sections.

In the following section, all aspect models that are part of Customs KIT are documented.

### CustomsInformation

CustomsInformation contains all customs-related information for a long-term supplier's declaration for a part. Long-term supplier's declarations (LLE) are one-off declarations that are valid for deliveries over a longer period of time, provided that the delivered goods are expected to have the same origin status.

Aspect model in GitHub:

- [Version 1.0.0](https://github.com/eclipse-tractusx/sldt-semantic-models/blob/main/io.catenax.customs_information/1.0.0/CustomsInformation.ttl)

```json
{
"catenaXId" : "580d3adf-1981-44a0-a214-13d6ceed9379",
"customsInformation" : [ {
"confirmationDate" : "2024-03-27",
"validFrom" : "2024-03-20",
"type" : "AnnualRequest",
"originInformation" : {
"tradeRelation" : "EU-MX",
"tracedWorth" : {
"value" : 300.45,
"currency" : "EUR"
},
"contactInformation" : {
"contactPerson" : "Max Mustermann",
"phoneNumber" : "+49 89 123456",
"email" : "[email protected]",
"jobTitle" : "executive position"
},
"commercialCountryOfOrigin" : "DE",
"originOfManufacturing" : {
"longitude" : 13.214907205727538,
"latitude" : 59.351212217399095
},
"federalState" : "BW",
"preferredStatus" : "Y-Certified"
},
"status" : "Not-Completed"
} ]
}
```

## Notice

This work is licensed under the [CC-BY-4.0](https://creativecommons.org/licenses/by/4.0/legalcode).

- SPDX-License-Identifier: CC-BY-4.0
- SPDX-FileCopyrightText: 2025, Bayerische Motoren Werke Aktiengesellschaft (BMW AG)
- SPDX-FileCopyrightText: 2025, Mercedes Benz AG
- SPDX-FileCopyrightText: 2025, msg systems AG
- SPDX-FileCopyrightText: 2025, ZF Friedrichshafen AG
- SPDX-FileCopyrightText: 2025, Contributors to the Eclipse Foundation
82 changes: 82 additions & 0 deletions docs-kits/kits/logistics-kit/page_adoption-view.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,82 @@
---
id: Adoption View Logistics Kit
title: Adoption View
description: "Logistics Kit"
sidebar_position: 2
---

![Logistics kit banner](@site/static/img/kits/logistics/logistics-kit-logo.drawio.svg)

Logistics and customs are closely linked due to the global nature of trade, and companies must consider both factors to ensure smooth and successful business operations. [Customs](./customs/page_adoption-view-customs.md) can affect the cost of imported or exported goods and thus influence logistics costs. In logistics, the compliance with customs regulations and procedures therefore plays an important role.

## Vision & Mission

### Vision

The aim of the Logistic KIT is to enlarge the digitally represented value chain of parts, batches and vehicles to cover the transport path. By using the foundation of the industry core for a certain use case and combining elements from the Logistic KIT, the entire supply chain, including transport information, fill the gap between companies and enables the supply chain to provide information such as geo data, bundling parts and batches belonging to a transport unit, or data from logistic service providers.

It reduces interfaces and enriches the entire network by including logistics and transport data to narrow down quality issues more precisely. It provides current transport data about environmental factors, like generated CO2 emissions.

### Mission

The Logistic KIT describes digital twins for a transport unit, a shipment itself as a process, provides the basis to include digital twins for assets (for example load carrier) and sensors plus matching aspect models. It enables logistic service providers, carriers etc. as well to provide their data to the network in a Catena-X compliant and interoperable way according to Gaia-X principles.
The approach is to exchange transport information in a n-way relationship between manufacturer, Tier-N, and supplier, gathering all relevant transport information and making it visible to all authorized stakeholders in the supply chain.

## Business Value & Key Ideas

### Business Value

Since the Logistic KIT is based on the digital foundation of the Industry Core, it requires only a small effort to maintain full coverage of the supply chain, including logistic routes. Goods which are negatively impacted by shock or heat can be tracked permanently. Influences of damaging can be discovered, eliminated/avoided, affected goods narrowed down and treaded appropriately.
Application and service provider can develop interoperable Catena-X logistic solutions.
Using the CX logistic standard, a fully connected network can be achieved in the long run. Ideally, OEMs and their suppliers will be part of the Catena-X logistics supply chain network and will be able to seamlessly provide and share data between all authorized stakeholders, such as GPS tracking, estimated delivery date, package composition, sensor data, customs requirements and much more.

![Logistic Twins](./assets/LogisticTwins.png)

### Key Ideas

- Sharing of relevant transport data beyond bilateral company relationships
- Triangle (OEM, Tier, LSPs - logistic service provider) to n-way connection
- Aligned demands and requirements for LSPs (logistic service provider) to share their data. No need to tailor solutions to individual requests.
- Distancing from a "What's in for me?" view to a collaborative view to bring all stakeholders on board and in turn optimizing the solution in the long run.

### Todays Challenge

The challenge today is that data exchange with logistic service provider varies greatly. Some are not connected at all, while others send their information about transports through many different interfaces. Additionally, there are various customer requirements on data sharing. Different committes made an attempt to standardize data exchange. Unfortunately, the standards are partly outdated, or they have been reinterpreted and individually adapted by companies, resulting in additional requirements to logistics service providers.

## Digital Twins

The Logistic Use Case uses digital twins to make a company's data available to other Catena-X partners. Basics about digital twins are described in the [Digital Twin KIT](https://eclipse-tractusx.github.io/docs-kits/category/digital-twin-kit/) and in the Logistics and [Customs Standard](https://github.com/catenax-eV/product-standardization-prod/blob/main/standards/CX-0150-UseCaseLogistics/CX-0150-UseCaseLogistics.md).

### Digital Twin “Transport Unit”

In case of using a Global Transport Label or tracking a transport unit and provide data e.g. about the packing list, creating a digital twin for transport unit is necessary. For creation a DT for transport units please see the [requirements of specific asset ID's](https://github.com/catenax-eV/product-standardization-prod/blob/main/standards/CX-0150-UseCaseLogistics/CX-0150-UseCaseLogistics.md#23-special-digital-twins-for-logistics-and-specific-asset-ids).

### Digital Twin "Transport"

In case of tracking the transport and provide data e.g. about GPS data, using a digital twin for transport is possible. For creation a DT for transport units please see the [requirements of specific asset ID's](https://github.com/catenax-eV/product-standardization-prod/blob/main/standards/CX-0150-UseCaseLogistics/CX-0150-UseCaseLogistics.md#23-special-digital-twins-for-logistics-and-specific-asset-ids).

## Aspect Models

In the following section, all aspect models that are part of Logistic KIT are documented.

### Packing List

The aspect provides the information of the [packed goods inside of a Transport Unit]((https://github.com/eclipse-tractusx/sldt-semantic-models/blob/main/io.catenax.packing_list/1.0.0/PackingList.ttl)).

### IotSensorData

The aspect provides the [information of tracked returnable packages and assets, monitor quality of critical materials](https://github.com/eclipse-tractusx/sldt-semantic-models/blob/main/io.catenax.iot_sensor_data/2.0.0/IotSensorData.ttl).

### GlobalTransportLabel (GTL)

The aspect model provides all information of [GTL](https://github.com/eclipse-tractusx/sldt-semantic-models/blob/main/io.catenax.global_transport_label/1.0.0/GlobalTransportLabel.ttl) in a digital format.

## Notice

This work is licensed under the [CC-BY-4.0](https://creativecommons.org/licenses/by/4.0/legalcode).

- SPDX-License-Identifier: CC-BY-4.0
- SPDX-FileCopyrightText: 2024, Mercedes Benz AG
- SPDX-FileCopyrightText: 2024, Robert Bosch GmbH
- SPDX-FileCopyrightText: 2024, msg systems AG
- SPDX-FileCopyrightText: 2024, Fraunhofer-Gesellschaft zur Foerderung der angewandten Forschung e.V. (represented by Fraunhofer ISST & Fraunhofer IML)
22 changes: 22 additions & 0 deletions docs-kits/kits/logistics-kit/page_changelog.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,22 @@
---
id: Logistics Kit Changelog
title: Changelog
description: 'Logistics Kit'
sidebar_position: 1
---

![Logistics kit banner](@site/static/img/kits/logistics/logistics-kit-logo.drawio.svg)

## [1.0.0] - 2025-02-12

### Added

- Initial version of the Kit including the adoption view

### Changed

- ./.

### Removed

- ./.
8 changes: 8 additions & 0 deletions docs-kits/kits/logistics-kit/page_documentation.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
---
id: Documentation Logistics Kit
title: Documentation
description: "Logistics Kit"
sidebar_position: 3
---

![Logistics kit banner](@site/static/img/kits/logistics/logistics-kit-logo.drawio.svg)
8 changes: 8 additions & 0 deletions docs-kits/kits/logistics-kit/page_software-operation-view.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
---
id: Operations View Logistics Kit
title: Operations View
description: 'Logistics Kit Operations View'
sidebar_position: 3
---

![Logistics kit banner](@site/static/img/kits/logistics/logistics-kit-logo.drawio.svg)
Loading