Start with Loady

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.

Simply send us your idea by email to support@loady.com. We collect all ideas and evaluate them based on feasibility, effort, and suitability for Loady. You will receive an update on the status of your idea. If it involves a new, complex functionality, we will also contact you to clarify the specific requirements.

‍

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.

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.

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

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

Currently, Loady offers copy functions for various data and objects. The existing copy functions are presented below:

‍

Copy functions for Company Products:

• Copying the entire company product
• Navigate to the product list via the navigation bar
• Click the copy icon in the top right corner
• In the pop-up, select the appropriate company and the company product to be copied
• The copied company product appears with the suffix (copy) in the product list for further editing

Copying the module Cleaning Requirements

• Navigate to the Cleaning Requirements of the company product into which the existing Cleaning Requirements of another company product are to be copied
• Click the copy icon in the top right corner
• In the pop-up, select the appropriate company and the company product from which the Cleaning Requirements are to be copied
• The Cleaning Requirements will be copied and will overwrite existing data

‍

Copying Previous loading restrictions

• Navigate to the Previous loading restrictions of the company product into which the existing Previous loading restrictions of another company product are to be copied
• Click the copy icon in the top right corner
• In the pop-up, select the appropriate company and the company product from which the Previous loading restrictions are to be copied
• The Previous loading restrictions will be copied and will overwrite existing data

‍

Copy functions for Inbound and Outbound Products

• Navigate to a module of an Inbound or Outbound Product, into which data is to be copied
• Click the copy icon in the top right
• In the pop-up, select the appropriate company, the appropriate Site, the appropriate Loading Point, the desired modules, and the appropriate Inbound or Outbound Product from which requirements are to be copied
• The desired requirements will be copied into the selected modules, overwriting existing data. Important: Only data from selected modules will be copied and overwritten. If modules are not selected, the existing data will remain unchanged

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.