ReqHub

dRofus is utilized in some of the world's largest and most complex construction projects. The vast amount of information generated in these projects can often resemble a dense jungle, making it challenging to gain a clear overview and distinguish critical data from less essential details.

Envision a project spanning hundreds of thousands of square meters, involving:

• Hundreds of designers

• Over a thousand on-site construction workers

• Representatives from the building owner and end users

All these stakeholders are either producing information, are consumers or need to verify that the required data is present and accurate. One of the major challenges many building owners face is systematically making sure that important data are in place and validated.

So, how do we address this challenge?

The Idea Behind the First Release of ReqHub

The concept behind the first release of ReqHub emerged after we ended support for TIDA. With TIDA, contractors used a dedicated interface to deliver handover documentation such as static files and property data for systems and components. When the Systems module replaced TIDA, contractors were transitioned into dRofus and exposed to a greater complexity than what they were used to.

ReqHub was created to solve this problem by providing contractors with a simple interface for managing their handover documentation tasks. However, to make these tasks possible, ReqHub also needed to address a second challenge for building owners: defining clear requirements for contractors and efficiently validating and tracking progress against these requirements.

Broader Applications

The first release of ReqHub is not limited to Owner–Contractor workflows. It can be applied to any process where ReqHub’s task-based approach fits the need. For example, it can facilitate the collection of Asset Information Requirements (AIR’s) from design teams or contractors. As ReqHub becomes exposed to users, we expect additional valuable use cases to emerge.