An MEP contractor runs two businesses on one network: a design office pushing large federated models through coordination, and site teams testing and commissioning on tablets. Listonics builds for both, plus the handover package the client keeps. Projects are quoted as a fixed scope from AED 2,500 to AED 30,000 depending on requirement.
An MEP contractor is a design office and a site, on one network
Most trades are one thing or the other. An MEP contractor is genuinely both, and the two halves want opposite things from IT. The drawing office wants raw speed on very large files: services models, federated coordination sets, shop drawings going back and forth with the consultant. The site wants coverage and resilience in a half-built building where the fixed line has not arrived and the lift is still a hoist.
Building for one and ignoring the other is the common failure. A firm that specifies good workstations and forgets the site ends up with commissioning records photographed on a phone and emailed. A firm that sorts the site and skips the office ends up with engineers waiting on a model to open. Our construction companies page covers the main contractor's side of this, and fit-out contractors covers the interiors side.
What the drawing office actually needs
Specification follows the model, not the headcount. A coordination model federating architectural, structural and services geometry is held largely in memory, so system memory and a workstation-class graphics card decide whether a model opens in seconds or minutes. A local solid-state drive matters more than people expect, because the model is cached to disk constantly while it is open.
The part firms miss is the network between the workstation and the files. A well-specified machine working across a slow link is a slow machine, so the office needs proper cabling to each desk and a switch that is not a bottleneck. Our office network setup page covers that side.
- Workstation-class machines for the modelling team, ordinary laptops for commercial and admin.
- Cabled connections to every modelling desk; wireless for meetings and visitors.
- A switch and cabling sized for moving large files, not just for email.
- A second screen as standard, because coordination is a two-window job.
Where model and drawing files should live
Two copies, with one system of record. Live project files sit on network storage in the office so the modelling team works at local speed, and that storage is configured with disk redundancy so a single drive failure is an inconvenience rather than an incident. Synology explains the trade-offs between the common arrangements in its guide to RAID, and the important point is that redundancy is not a backup.
The cloud copy is what makes a project survivable and shareable. It also has limits worth knowing before you design around it: Microsoft publishes the file size and sync constraints in its SharePoint and OneDrive service limits, and very large model files can sit awkwardly against them. We size the arrangement around your actual file sizes rather than assuming. The construction drawing storage guide goes into the versioning question in more detail.
Keeping site, testing and commissioning teams connected
Commissioning generates the records the client will eventually hold you to, and they are captured in the worst possible conditions: a partly finished plant room, no fixed line, and a tablet with one bar. The practical answer is a site connection planned rather than improvised. We check what du and e& can deliver to the plot, and where a fixed line will not arrive in time we set up a cellular link with the firewall configured to switch over when it does.
Coverage inside the building is its own problem, because the structure changes weekly as blockwork goes up. Access points are placed for where the work is now and moved as the programme advances, rather than installed once and left. The site office internet setup guide covers the sequencing.
Who should see which project
MEP work runs several projects at once with a different cast on each: consultants, the main contractor, specialist subcontractors and labour supply. Access granted person by person becomes impossible to audit within a year, and the tender folder is usually sitting in the same place as everything else.
The workable structure is access by project and by group. Each project is its own area, people are added through groups tied to their role, and a departure or a project close removes access in one action. Tender and commercial material sits apart from delivery files, because a bid team and a site team should not see the same folder. The CIS Critical Security Controls treat this kind of access management as a baseline for small organisations rather than an advanced measure, and our cybersecurity service applies it.
The handover package, and what happens after
An MEP job does not end at practical completion. Operation and maintenance manuals, as-built drawings, test certificates, asset registers and warranty documentation all have to be assembled, handed over and then retained, often for years, in a form you can produce if something is disputed. Firms that treat this as an end-of-project scramble spend weeks on it and still hand over an incomplete set.
Treating it as a running deliverable costs far less. The folder structure that receives the handover package is created at mobilisation, commissioning records land in it as they are produced, and the final assembly becomes a review rather than an excavation. After handover, the project is archived to a copy you can still reach, rather than left on the live system where it slows everything down and nobody dares delete it.
From mobilisation to archive
We start with a survey of both halves: the office and the way models actually move through it, and a live site if you have one. That produces a fixed-scope proposal covering workstations, storage, the network, site connectivity, access structure and the backup, with a monthly restore test and the result written down. Listonics projects run from AED 2,500 to AED 30,000 depending on requirement, and support is a fixed monthly fee with response times in the agreement.
Everything ends with documentation you own: the asset list, the network diagram, the project access structure and the archive process. If you move to another provider, they can pick the firm up from that document rather than starting a discovery exercise on your time.
Frequently asked questions
It depends on the model rather than the job title. Coordination and federated model work benefits from system memory and a workstation-class graphics card, which laptops provide only at the upper end. Commercial, planning and admin staff are well served by ordinary business laptops. We specify from the files you actually open rather than giving everyone the same machine.
Usually both, with one system of record. Network storage in the office gives the modelling team local speed on very large files, and a cloud copy makes the project survivable, shareable and reachable from site. Disk redundancy on the storage is not a backup, so a separate backup with a tested restore sits alongside it.
By structuring projects as separate areas and granting access through groups rather than to individuals. An external consultant is added to the one project they work on, with sharing set to expire, and is removed in a single action at project close. That also makes the access list something you can produce when a client asks.
Plan for it rather than improvise. We check what each provider can actually deliver to that plot at the start, since lead times routinely outrun a mobilisation programme, and set up a cellular connection to carry the site in the meantime. The firewall is configured to switch to the fixed line once it is delivered, with no change for the site team.
It is archived deliberately rather than left in place. The handover package and its supporting records move to an archive you can still reach and restore from, the live system is cleared so it stays fast, and retention is set to match your contractual and legal obligations. Nothing is deleted because somebody needed space.
It is quoted as a fixed scope after a free survey of the office and, where there is one, a live site. Listonics projects run from AED 2,500 to AED 30,000 depending on requirement, with workstation count, storage volume and site connectivity moving the figure most. Ongoing support is a fixed monthly fee with response times written into the agreement.
Written by Srinivasan Ramachandran, Founder, Listonics · Last reviewed September 28, 2026