Our Approach

In a project the order of decisions matters more than the equipment chosen. The same bill of materials yields either a plant that runs without incident or an installation that demands constant attention, depending on the stage at which each decision was taken. What gives the stages their value is not their own names but what each one leaves to the next.

What a site survey has to establish

A site survey is not the collection of a wish list. What must be measured is known in advance: the cross-section and fill of existing cable routes, the capacity of panels and shafts, the load a UPS can carry, the bearing strength of the surfaces that will take the mounts. Alongside these, the operator's own order goes on record — shift hours, who is authorised to intervene in what, which area empties at which time. A specification written without that data is a document with no counterpart on site.

Architecture comes before product selection

Which product to buy cannot be answered before it is settled how information will flow. First comes the definition of where an event is produced, where it is retained and through which interface it passes to another discipline. How long the record is held, where the network is segmented and which function keeps working locally when the link drops belong to the same stage. Where selection follows that definition, equipment follows the architecture; where it does not, the architecture is shaped by the limits of equipment already bought.

Acceptance and the handover file

Testing is worth whatever was written down beforehand. Checking device by device is the easy part; designed behaviour becomes visible only in scenarios where disciplines intersect. Which devices stay up on the UPS when mains is cut, whether the network switches keep their supply and whether recording is interrupted are set out in advance with their expected result, observed on site, and signed into a test report.

A handover file is part of the work, not a formality appended to its end. Without an IP addressing plan and network segmentation, an account and authorisation list, licence and warranty records, test reports and configuration backups, the plant stays dependent on the team that built it. Prepared properly, that file leaves the choice of who performs the next intervention to the operator.