InfraBox

What Stevin gets out of InfraBox

InfraBox is made for infrastructure and civil engineering: project administration, cost control and progress on location. For road, ground and water works that is the right foundation, because it is built around the way those projects actually run. What the system does not do is account for the biggest unknown in this work: the weather. A phase running late, a cost item that deviates, a report from the site that needs follow-up, InfraBox records it but does not connect it to the planning or to outdoor conditions. We see teams lose time and money there. Stevin connects to it through the API or an export, reads the project data and turns it into signals, and for outdoor work it lays weather data next to the planning. Stevin does not replace InfraBox, it makes the information usable at the moment a crew can still shift, with the site manager seeing the action first.

What you pair it with

InfraBox covers the project side of infrastructure and civil engineering, but it does not account for weather, while outdoor work is exactly what makes or breaks the schedule. That link between planning and weather data is not in it and has to sit on top. The connection runs through the API or an export, so the project data comes out. The question is whether something flags a phase running late, a cost deviation or a weather risk in time. Without that monitoring, a crew only shifts when it is already too late, and a lost workday costs money straight away.

Common mistakes

• →Only seeing a project phase running late once the whole planning has shifted.
• →Noticing cost deviations too late because they are not tied to the planning.
• →Letting outdoor work run with no weather warning, then a lost day costs money straight away.
• →No central overview of what needs attention, so report after report in the inbox.