An increasingly competitive marketplace for both projects and talent is driving the adoption of project historical databases across the infrastructure sector. It’s a trend exacerbated by the coronavirus pandemic, which showed the importance of digitalization and systems that support business continuity.
When developing a project historical database, firms must consider how to normalize project costs, note project context that might affect prices, collect pricing information, and consider what data should be saved.
In this Q&A, Eos Group CEO Nick Papadopoulos discusses how to ensure the success of a firm’s project historical database with:
- A supportive corporate culture
- Staff recruitment plan
- Overall data strategy