Start with Loady

Requirement Profiles are designed so that the objects contained therein (Business Partner, Site, Unloading Point, Inbound Product) cannot be exchanged or replaced by others after creation. This is because a requirement profile establishes a unique combination of these objects.

‍

Therefore, if a Business Partner, an Inbound Product or an Unloading Point needs to be adjusted within a requirement profile, a new requirement profile with the desired objects must be created. If the requirement profile with the original objects is no longer needed, it must be deleted.

Loady offers various tutorials. You can access the latest tutorials directly in Loady via the dashboard or through the following link: Tutorials

In addition, other tutorials are available to you, which are stored centrally within your organization (e.g., cloud storage). For these, please contact your internal Loady representative. We are continuously adding new tutorials and are planning a central location within the application for easy access. We prioritize the creation of tutorials based on our assessment of customer needs.

‍

Should you urgently need a tutorial on a specific topic, please contact support@loady.com. This allows us to take it into account in our internal prioritization.

There is no universal solution for structuring data in Loady. The structure in Loady should mirror the data structure of the ERP system. The following provides some guidance to minimize potential conflicts.

‍

Object names should be clear and unambiguous to ensure good clarity. For a functional exchange of data between the ERP system and Loady, the field ERP Reference Number, which must be maintained for each object, is crucial. The exact designation from the ERP system must be entered here.

‍

For optimal clarity and assignment of different loading/unloading requirements, it is recommended that separate loading/unloading points be created for clearly distinguishable loading procedures.

‍

The following are examples of how loading/unloading points can be divided according to different loading procedures:

• Bulk products vs. packed products
• Container vs. truck loading

‍

For example, a site could be created in Loady that includes several loading/unloading points.

In this example, these are clearly separated by the type of goods being loaded or the processes required for loading:

• Site: 001
  
  • Loading Point: 001_Bulk
  • Loading Point: 001_Packed_ Truck Loading
  • Loading Point: 001_Packed_ Container Loading

‍

Should any ambiguities arise regarding the data structure, our Customer Success Team is happy to provide individual consultation.

In cases where free text fields are not maintained in all input languages available on Loady, Loady defaults to the standard language English . This means that free text fields must always be maintained in at least English. Otherwise, data in free text fields cannot be saved. If Loady is used in another language, e.g., German, to maintain the content in English, the input language must be changed via the language selection for free text fields to English.

If the data is only maintained in English, the English entry will be displayed as a fallback when Loady is used in another language.

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

Initially, the object structure should be set up in Loady (sites, loading points, assignment of products to loading points, company products, business partners including sites, unloading points, assignment of products to unloading points). It is important to consider the dependencies between the individual object types (e.g., a loading point cannot be created before the site has been set up; a company product cannot be assigned to an unloading point at a business partner before the business partner, the business partner's site, and the unloading point exist).

‍

‍

Once the object structure has been set up, you can begin managing the requirements at the level of the respective objects.

Loady currently does not support PDF uploads. You can upload the PDF to a website and insert a link as a URL in the corresponding free text field in Loady.

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