Start with Loady

Currently, only data related to created lanes can be downloaded. This includes data for actively used lanes under Lane Management or data for lanes assigned to a tender (Loady4Tender), can be downloaded.

For additional data exports, the Customer Success Team can be requested.

For all objects that can be created in Loady, there is the option to perform the (initial) setup via CSV upload:

• Company Products
• Sites
• Loading/Unloading Points (own company/business partner)
• Assignment of products to loading/unloading points (own company/business partner)
• Business Partners
• Requirement Profiles
• Lanes & Update Partners in Lanes
• Previous loading Restrictions

‍

Please note that via CSV upload no requirements can be uploaded. For some objects, basic information can also be created in the CSV templates (e.g., unloading times, addresses). Generally, objects can be created via CSV upload, but the requirements must then be maintained via the user interface.

We are happy to support you with the initial setup of the data. Based on our experience, we can recommend some best practices. Generally, during the initial data setup on Loady, it is advisable to designate a central contact person to coordinate and monitor the setup (e.g., ensuring all sites are created, all products assigned).

‍

Additionally, expertise from various departments is required for data setup. Which departments actually need to be involved in the data setup depends on the client's organization and the distribution of responsibilities. Based on previous experience, expertise from the following departments is needed:

‍

• Sites and loading/unloading points within your own company: employees from site management or those responsible for loading/unloading points
• Company products: Employees from product management, quality management, or technical marketing
• Business Partners and all associated objects such as sites, unloading points, inbound products and associated unloading requirements are usually maintained or managed by customer service or sales employees
• Previous loading restrictions: Employees from quality management, technical marketing, or those responsible for loading points
• Tenders: Employees from the purchasing organization
• ERP structure: Key users or employees from IT departments

It is not currently possible to directly restore data within Loady. Please contact the Customer Success Team.

In many submodules, free text fields are available that can be used. If the data could benefit from a structured field (e.g., recurring data), please contact the Customer Success Team. We will work with you to find a solution.

Missing dropdown values can be requested in the same way. If it's a value commonly used as a standard in the (chemical) logistics environment, it can be added quickly.

A fundamental prerequisite for deleting objects in Loady is that the object is not contained in any connecting elements, such as in requirement profiles and lanes .

‍

Examples:

• To delete an outbound product, all requirement profiles and lanes in which the outbound product is contained must first be deleted.
• At all loading/unloading points where the company product was assigned as an inbound or outbound product , it must be removed before it can be deleted.

‍

To delete various objects in Loady, the following order must be observed:

1. Requirement profiles
2. Lanes
3. Inbound and outbound products
4. Company products
5. Loading and unloading points (buildings)
6. Sites
7. Business partners

If you have general questions about Loady, please contact support@loady.com. If your questions specifically relate to Previous Loading Restrictions or ePLR-Check, please contact plr-support@Loady.com

‍

All questions that are related to Loady but concern processes or systems within the customer's company must be directed to the respective responsible parties within the company (e.g., IT department, application owner, administrators, support mailboxes).

‍

The attached table shows which topic categories Loady or your own team can support.

Transferring data between Loady and other systems requires integration via one of our APIs (Application Programming Interfaces). Loady offers various standardized APIs for different applications. Our customers' IT departments configure these integrations according to their specific needs. This means that data transfer must be individually defined within the customer's business processes.

‍

Please contact the responsible integration manager or IT department directly. They can explain exactly how data transfer between Loady and other systems is initiated and executed.