Perth-based Fastbrick Robotics is developing a second prototype of its one-armed bricklaying robot that can lay up to 1000 bricks and hour, which is about the output from two human brick layers in a full day.
The Hadrian X claims to be able to complete the brickwork on a home within 1-3 days, which is set to significantly disrupt building technology.
ASX-listed Fastbrick is committed to improving the safety, speed, accuracy, cost and waste management in the global construction industry through utilising the world’s latest innovations in mobile robotic technology.
The Hadrian X uses a globally patented 3D robotic bricklaying system and will be able to build a house up to 25 times more efficiently than a human bricklayer. The machine is able to cut, grind, mill and route the bricks to ensure they interlock correctly before being laid.
[Related reading: ‘Ripe For Disruption’ 5 New Construction Technologies Changing The Way We Build]In July this year Fastbrick and global construction and mining equipment manufacturer Caterpillar Inc. signed a MOU allowing both companies to discuss and develop a potential framework for the joint collaboration of the Hadrian X development, manufacturing, sales, and servicing of the robot. Caterpillar has also invested $2 million dollars in Fastbrick and become a shareholder.
The company also signed an agreement with the Kingdom of Saudi Arabia for it to be a potential global first adopter of the Hadrian X. This could see the construction of at least 50,000 new home units which would mean an equivalent machine requirement of 100 Hadrian X construction robots. Saudi Arabia has a new home building target of 1.5 million homes to be completed by 2022.
“A second Hadrian X opens up the possibility of Fastbrick pursuing two pilot programmes in separate key geographical markets," Fastbrick chief executive Mike Pivac said.
“The second Hadrian X will be assembled and tested in parallel with the current Hadrian X prototype and will allow the engineering team to significantly de-risk the assembly and test phases by applying the learnings from the assembly and de-bugging process between each.”
