Virtual Learning Factory Toolkit
  • Virtual Learning Factory Toolkit
  • VLF Knowledge Base
    • Factory Data Model
      • OWL Classes
      • SPARQL Queries
      • SPARQL Updates
    • Instantiation of Factory Models
      • Assets
        • Assets in Spreadsheet
        • Assets in JSON
        • Assets in Ontology
      • 3D Models of Assets
        • 3D Models for Virtual Reality
      • Statechart
      • Animations
      • Data Repositories
        • Local Repository
        • Remote Repository
  • VLF Tools and Libraries
    • OntoGui
      • Modules
        • Control Panel
        • Individual Manager
        • System Design
        • Utilities
      • Personalization
    • OntoGuiWeb
      • Modules
        • Control Panel
        • SPARQL
        • Graphs OWL
        • Utilities
        • Asset Design
        • System Design
        • System Control
        • Performance Evaluation
        • MQTT Sync
        • Virtual Environment
        • Graphs Eng
        • StateChart
      • Personalization
    • jsimIO
      • How to start
      • JMT Overview
        • JSim
          • Model generation
          • Launch of the simulation
          • Reporting
        • Bibliography
    • VEB.js
      • Functionalities
      • Input/Output files
      • Integration with other software tools
      • Advanced Users
    • ApertusVR
    • MTM
      • How to start
      • Formalise the process
      • Prepare input data
      • Execution and results
    • MOST
      • How to start
      • Formalise the process
      • Prepare input data
      • Execution and results
    • RULA
      • How to start
      • Formalise the process
      • Prepare input data
      • Execution and results
    • OCRA
      • How to start
      • Prepare input data
      • Execution and results
  • Use Cases
    • Automated Assembly Line
    • Assets and Animations
    • Modelling of Factory Assets
      • Modelling of an Assembled Product
      • Modelling of a Workstation
      • 3D Modelling of a Workstation for Virtual Reality
    • Process Modelling
      • Modelling an Assembly Process
    • Modelling of a manufacturing system
      • Modelling in OntoGui
      • Modelling a Job Shop using OntoGui
      • Modelling of a Flow Shop using OntoGui
      • Modelling a Hybrid Flow Shop using OntoGui
      • Modelling an assembly system using OntoGui
    • Performance evaluation using jsimIO
      • Performance evaluation of a manufacturing system
        • Performance evaluation in Jsim
        • Performance evaluation of a Flow Shop using Jsim
        • Performance Evaluation of a Job Shop using JSim
        • Performance evaluation of a Hybrid Flow Shop using Jsim
        • Performance evaluation of an assembly system using Jsim
      • jsimIO Assembly
      • jsimIO Automatic
      • jsimIO Production
  • Classworks
  • Advanced Features
    • JMT model
      • Automatic generation of a JMT model
      • Automatic generation of animations
    • Enabling technologies
      • Node-RED
        • Node-RED tutorial
      • RDF libraries
Powered by GitBook
On this page

Was this helpful?

  1. VLF Tools and Libraries
  2. MTM

Execution and results

PreviousPrepare input dataNextMOST

Last updated 3 years ago

Was this helpful?

The final step of the model developed for the MTM-UAS methodology is the downloading of the Excel file modified by the Python code with the desired outputs: they will be two new different sheets, one called "Acitivity codes", where basically the times for each single activity are reported, and the other one called "Total times", where the total processing time of the working cycle is finally shown. As already mentioned before, also in this case the attached images are refered to the Excel file of the layout 1 of the Catenaccio case, since these are output of the Python code so a general model is not available.

In the above figure, that is the "Activity codes" sheet, four columns are displayed:

  1. in the first one, called "ID", the ID of the activity considered is shown: the order is not the one of execution, instead it is considered the typology of activity according to the MTM-UAS tables, from 'Get and place' to 'Visual inspection';

  2. the second one is named "ACTIVITY" and it is for the name of the activities correspondent to the ID;

  3. the third column, called "ACTIVITY CODE", shows a code related to the specific section to which each activity has been allocated by the code, so that the assessor is able able to verify both the functioning of the toolkit and make some considerations about his assumptions and data inserted;

  4. the last column is named "ACTIVITY TIME" and contains the time values in TMUs related to each single activity.

Finally the second output sheet is the one showed in the figures below that basically reproduce the content of one Excel sheet:

  1. In the first seven columns the values of the processing times for each single section are reported in TMUs;

  2. in the last three columns is instead possible to see the final total value of the processing time for the working cycle considered, in terms of TMUs, seconds and minutes, that is the final and most important outcome of this methodology.