<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns="http://purl.org/rss/1.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel rdf:about="http://hdl.handle.net/123456789/2255">
<title>DEVELOPMENT AND OPTIMISATION OF AN AUTOMATED GAARI FRYING MACHINE</title>
<link>http://hdl.handle.net/123456789/2255</link>
<description/>
<items>
<rdf:Seq>
<rdf:li rdf:resource="http://hdl.handle.net/123456789/2256"/>
</rdf:Seq>
</items>
<dc:date>2026-04-04T02:29:45Z</dc:date>
</channel>
<item rdf:about="http://hdl.handle.net/123456789/2256">
<title>DEVELOPMENT AND OPTIMISATION OF AN AUTOMATED GAARI FRYING MACHINE</title>
<link>http://hdl.handle.net/123456789/2256</link>
<description>DEVELOPMENT AND OPTIMISATION OF AN AUTOMATED GAARI FRYING MACHINE
OZIGBO, EMMANUEL SUNDAY
Frying operation is a tedious aspect of garri processing. It is largely done&#13;
manually which causes discomfort and various health challenges to the operator&#13;
due to heat, smoke, and the sitting posture. Literature is sparse on the deployment&#13;
of automation for garri frying and previous efforts made did not give satisfactory&#13;
results. Therefore, this study was designed to develop an automated garri frying&#13;
machine.&#13;
A garri fryer fitted with a heating element was developed using standard methods.&#13;
Based on the existing literature and preliminary studies, Frying Time, FT (0–90&#13;
mins), Frying Temperature, FTP (0–250 oC), Power Consumption, PC (0–15 kW),&#13;
initial Moisture Content, MCi (0–55% wb), and final Moisture Content MCf (0–&#13;
35% db) were programmed into an Arduino microcontroller and attached to the&#13;
developed fryer to automate it. The Functional Efficiency (FE), Throughput (TP),&#13;
Useful Heat Energy (Qu) and Thermal Efficiency (Ƞʈ) of the automated fryer were&#13;
determined using standard equations. The FTP relative to different PC levels were&#13;
recorded. The optimum operating conditions of the automated fryer were&#13;
determined using Response Surface Methodology (RSM) at 4-factors: FTP, FT,&#13;
MCi, Mass Quantity (MQ) and 5-levels: 140, 160, 180, 200, 220 oC; 15, 30, 45, 60,&#13;
75 mins; 30, 35, 40, 45, 50% wb and 10, 20, 30, 40, 50 kg, respectively. The&#13;
optimised values were validated with experimental data using standard methods.&#13;
At a constant FTP (183 oC) and MCi (30% wb), 30 kg of mash sample,&#13;
comparative analysis of manual, mechanical and automated fryers were carried&#13;
out based on the TP, FE, FT, Number of Operators (NOP), Production Cost (PDC)&#13;
and Operating Cost (OC). Data were analysed using ANOVA at α0.05.&#13;
The automated fryer was powered with a 2-hp, 3-phase electric-motor. Its FE, TP,&#13;
Qu and Ƞʈ were 87%, 45.0 kg/hr, 7,919.8 J and 42.7%, respectively. Increase in&#13;
FTP from 140 – 220 oC resulted in decreased MCf (23.4, 19.8, 15.3, 12.6, and&#13;
9.8% db). Optimal TP (43.64 kg/hr) and MCf (12.30% db) were obtained at&#13;
operating conditions: MQ (49.99 kg), FT (57.80 mins), MCi (30% wb) and FTP&#13;
(183 oC) at PC of 7.7 kW. There was no significant difference between the&#13;
experimental and predicted values, indicating that the optimised values were&#13;
valid. The FE, TP, FT, PDC and NOP for automated, mechanical and manual were&#13;
87, 57.7, and 44%; 45.0, 18.7 and 13.2 kg/hr; 41, 55 and 62 mins; and 1, 2 and 3,&#13;
respectively indicating that the automated fryer performed best. The PDC and OC&#13;
for the automated, mechanical and manual fryers were ₦609,200, ₦700,000,&#13;
₦185,400, and ₦138,000, ₦699,936, ₦61,000, respectively. The developed&#13;
automated fryer was more cost-effective and efficient than the mechanical fryer.&#13;
The manual fryer had the lowest production and operating costs but lowest&#13;
capacity, processing time, and efficiency. There was a significant difference in the&#13;
efficiency of the automated machine compared with mechanical and manual&#13;
fryers.&#13;
An automated garri fryer which gave better performance than the existing fryers&#13;
was developed.
</description>
<dc:date>2022-11-01T00:00:00Z</dc:date>
</item>
</rdf:RDF>
