Start with Loady

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.

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.

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.

An Inbound or Outbound Master includes requirements that apply to multiple Inbound or Outbound Products at a loading/unloading point. For example: At a site there is a loading point where 10 Outbound Products are loaded with identical loading requirements. Instead of maintaining the requirements 10 times for the individual products, these requirements can be stored once in an Outbound Master . When the Outbound Products are assigned to this Outbound Master , the requirements maintained at the master level are transferred to the individual Outbound Products.

‍

The creation and maintenance of an Outbound Master (Inbound Master similarly) is done as follows:

1. Create the Outbound Master as an object and maintain the requirements
2. Assign the associated Outbound Products to the Outbound Master

‍

Important: As soon as Outbound Products are assigned to an Outbound Master , the originally stored data of the individual Outbound Productswill be overwritten. This means they are deleted and cannot be restored. If Outbound Products are removed from an Outbound Master , the master's requirements remain, but the data is simply no longer synchronized. From this point on, they must be manually edited at the product level.

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.

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

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

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.