Format of the input data

Navigation:  Data Export and Import > ema Wizard >

Format of the input data

Previous pageReturn to chapter overviewNext page

In order to perform a successful import, a valid input data is required. A valid set of input data consists of a XLSX file with six Excel-worksheets.

 

iThe template for the ema Wizard must not be changed structurally, otherwise the import will not work.

 

The columns of the table should be structured as follows:

 

First worksheet process (tasks and task parameters):

 

A: ID of the task group

B: Level of task group

C: Name of the task group

D: Comment (comment generated in the task comments and the second comment field at object level)

E: Description of the task

F: Duration (in [s] or as Wait for function)

G: Resource (human model or object), which executes the tasks (unique object name from worksheet objects, column A)

H: Part/product/object being handled (unique object name from worksheet objects, column A)

I: Hand usage (left, right, or both)

J: Pick type (MTM-UAS; easy, difficult, or handful)

K: Destination of the part/product/object defined in column H (unique object name from worksheet "objects", column A)

L: Place type (MTM-UAS; approximate, loose, or tight)

M: Tool which is used (unique object name from worksheet objects, column A)

N: Type of tool application (examples for tool types: automatic - e. g. cordless screwdriver; punctual - e. g. center punch/soldering iron; linear - e. g. brush; rotatory - e. g. torque wrench/rachet; laminar - e. g. cleaning tissue; writing - e. g. pen ; strokes - e. g. hammer)

 

Second worksheet objects (simulation relevant objects):

 

A: Name of the object (unique name required)

B: Object type (ID/reference) or relative/absolute geometry file name, for example oHuman (Human Model), oRack (Rack) or o3DNodeUser (structure node) respectively "emaGeometry\gearbox.dae"

C: Part number/name; comment generated in the first comment field at object level

D/E/F: Object measurement [mm] (Length x Width x Height)

G: Object color (fill color of the color palette from spreadsheet)

H: Object weight [kg]

I: Collision object (yes/no or empty -> automatic)

J: Parameter (name/value for any parameter, see worksheet object parameter documentation)

K: Initial position of the object (possible values are: position & orientation (6 values) - e. g. positionX;positionY;positionZ;rotationX;rotationY;rotationZ; position (3 values) - e. g. PositionX;PositionY;PositionZ; initial matrix (4x4 matrix, 16 values) - e.g. 1;0;0;0;0;1;0;0;0;0;1;0;[posX];[posY];[posZ];1)

L: Source/reference object of the resource (unique object name/container identification)

M: Location parameter to which the resource refers at its source. Possible values are origin (in origin of source), middle (in geometrical middle of source) and top (on top of source).

N: Container content (used for documentation; comments and label objects (white text) associated with the container in the object structure)

O: Container range (planned value; used for documentation; comments and label objects (white text) associated with the container in the object structure)

 

iIf columns K and L are filled in and the origin is selected at M, then the matrix from column K is to be interpreted as a relative matrix to the reference point of the object from L.

 

Third worksheet container (simulation relevant containers):

 

A: Container identification (unique name required)

B: Container type (drop-down selection based on fourth worksheet container_library)

C: Initial position of the container (possible values are: position & orientation (6 values) - e. g. positionX;positionY;positionZ;rotationX;rotationY;rotationZ; position (3 values) - e. g. PositionX;PositionY;PositionZ; initial matrix (4x4 matrix, 16 values) - e. g. 1;0;0;0;0;1;0;0;0;0;1;0;[posX];[posY];[posZ];1)

D: Source of the container (unique object name - rack or package)

E: Location parameter to which the resource refers at its source. Possible values are origin (in origin of source), middle (in geometrical middle of source) and top (on top of source)

F: Container location by level (integer); if source is a rack (geometric primitive)

G: Container location by location/compartment on which container is located (alphabetical character, starting with A); if source is a rack (geometric primitive)

H: Image file (relative/absolute file path), to display a surface texture in the container

 

Fourth worksheet container_library (extensive container library):

 

A: Container type (unique name required); label object (green text) associated with the container in the object structure generated

B: Object type (ID/reference); possible values are: oCuboid, oContainer or relative/absolute geometry file name

C: Comment; comment generated in the object level

D/E/F: Container measurement [mm] (Length x Width x Height)

G: Container color (fill color of the color palette from spreadsheet)

H: Weight of the container when it is empty (tara) [kg]

I: Wall thickness of the container [mm]

J: Height of the front side of the container [mm]

K: Payload [kg] (for information, no claim to correctness and completeness for predefined container)

L: Stacking factor [1+x] (for information, no claim to correctness and completeness for predefined container)

 

Fifth worksheet sprache / language (Language selection):

 

B, row 2: Language selection - Possible to switch between German (1) and English (2)

 

Sixth worksheet object parameter documentation (list of object parameters):

B: Description

C: Type of the parameter (e. g. double for whole numbers, bool for TRUE/FALSE statements, enum for String values)

D: Possible values of the respective parameter type

E: Example

 

All XLSX files to be imported must be built according to the above described scheme. It is also possible to create a template. This is achieved via the submenu item Create ema Wizard template (xlsx) ... from the submenu ema Wizard in the menu Im-/Export.

The following section describes the processing of the Excel file in ema in more detail.