4 resultados para test process components
em Reposit
Resumo:
O presente trabalho foi desenvolvido na empresa Renault CACIA e tem como fundamento a implementação de um fluxo de abastecimento com 4 horas de autonomia em todas as linhas de montagem no departamento de fabricação de componentes mecânicos. No entanto, estas linhas deverão ter condições para poder armazenar esse abastecimento, pelo que terão de ser implementadas estruturas que o suportem. Com o objetivo de eliminar o excesso de stock existente na linha de montagem de bombas de óleo, a mais crítica da instalação, e as atividades que não acrescentam valor ao produto final, organizar o espaço disponível, melhorar as condições ergonómicas, propõem-se soluções que serão uma mais-valia para as empresas de fabricação. Durante o desenvolvimento do trabalho foi realizado um estudo aprofundado da linha de montagem e dos problemas existentes no processo de abastecimento e, posteriormente, foi determinada a quantidade necessária de embalagens de componentes para a autonomia requerida. Recorreu-se à ferramenta CAD 3D, Solidworks®, para o planeamento das estruturas, e ao software de simulação Arena®, para testar o funcionamento da linha de montagem com a implementação das estruturas para abastecimento. Verificaram-se melhorias conseguidas através da implementação das soluções sugeridas. A linha de montagem ficou mais organizada e arrumada, tendo-se reduzido cerca de 86,96% de stock global existente. Associado a este, existiam atividades realizadas pelo operador de montagem que não acrescentavam valor ao produto final, tendo-se obtido um incremento da produção na ordem de 1%.
Resumo:
In a industrial environment, to know the process one is working with is crucial to ensure its good functioning. In the present work, developed at Prio Biocombustíveis S.A. facilities, using process data, collected during the present work, and historical process data, the methanol recovery process was characterized, having started with the characterization of key process streams. Based on the information retrieved from the stream characterization, Aspen Plus® process simulation software was used to replicate the process and perform a sensitivity analysis with the objective of accessing the relative importance of certain key process variables (reflux/feed ratio, reflux temperature, reboiler outlet temperature, methanol, glycerol and water feed compositions). The work proceeded with the application of a set of statistical tools, starting with the Principal Components Analysis (PCA) from which the interactions between process variables and their contribution to the process variability was studied. Next, the Design of Experiments (DoE) was used to acquire experimental data and, with it, create a model for the water amount in the distillate. However, the necessary conditions to perform this method were not met and so it was abandoned. The Multiple Linear Regression method (MLR) was then used with the available data, creating several empiric models for the water at distillate, the one with the highest fit having a R2 equal to 92.93% and AARD equal to 19.44%. Despite the AARD still being relatively high, the model is still adequate to make fast estimates of the distillate’s quality. As for fouling, its presence has been noticed many times during this work. Not being possible to directly measure the fouling, the reboiler inlet steam pressure was used as an indicator of the fouling growth and its growth variation with the amount of Used Cooking Oil incorporated in the whole process. Comparing the steam cost associated to the reboiler’s operation when fouling is low (1.5 bar of steam pressure) and when fouling is high (reboiler’s steam pressure of 3 bar), an increase of about 58% occurs when the fouling increases.
Resumo:
Call Level Interfaces (CLI) play a key role in business tiers of relational and on some NoSQL database applications whenever a fine tune control between application tiers and the host databases is a key requirement. Unfortunately, in spite of this significant advantage, CLI are low level API, this way not addressing high level architectural requirements. Among the examples we emphasize two situations: a) the need to decouple or not to decouple the development process of business tiers from the development process of application tiers and b) the need to automatically adapt business tiers to new business and/or security needs at runtime. To tackle these CLI drawbacks, and simultaneously keep their advantages, this paper proposes an architecture relying on CLI from which multi-purpose business tiers components are built, herein referred to as Adaptable Business Tier Components (ABTC). Beyond the reference architecture, this paper presents a proof of concept based on Java and Java Database Connectivity (an example of CLI).
Resumo:
Call Level Interfaces (CLI) are low level API that play a key role in database applications whenever a fine tune control between application tiers and the host databases is a key requirement. Unfortunately, in spite of this significant advantage, CLI were not designed to address organizational requirements and contextual runtime requirements. Among the examples we emphasize the need to decouple or not to decouple the development process of business tiers from the development process of application tiers and also the need to automatically adapt to new business and/or security needs at runtime. To tackle these CLI drawbacks, and simultaneously keep their advantages, this paper proposes an architecture relying on CLI from which multi-purpose business tiers components are built, herein referred to as Adaptable Business Tier Components (ABTC). This paper presents the reference architecture for those components and a proof of concept based on Java and Java Database Connectivity (an example of CLI).