BIM Services

We work in the formats your project team already uses. That means native Revit models where the project requires them, Navisworks for clash review, IFC exports for cross-discipline coordination, and PDF drawing sets for construction — with consistent naming, tagging and revision control across all of them. If your design team, main contractor or client has a mandated toolchain or a defined exchange format, we align to it rather than asking everyone else to change for us. Tell us the coordination workflow at scope stage and we will confirm exactly what we can issue and in what format.

We work to the project’s information requirements and BIM execution plan, and where a project runs to ISO 19650 conventions we align our naming, model boundaries, revision control and transmittal discipline to them. To be clear about what that is and is not: this is how we work on a project, not a certification we hold. The certifications PTS holds are ISO/IEC 27001 and ISO/IEC 20000, for information security and IT service management.

Only what you need us to, and that is usually the technology and low-voltage scope — structured cabling, containment and pathways, MDF and IDF rooms, rack layouts, outlet and device locations, and access point placement. We are a technology design consultancy that produces BIM outputs, not a general architectural modelling practice. We agree model boundaries and the responsibility split with the other disciplines at the start, so it is clear who owns what and there are no gaps at the interfaces.

Mostly by moving clashes off site. Finding that a cable tray runs through a duct is inexpensive in a model and expensive once it is installed, and the same applies to comms rooms that turn out to have insufficient clearance for the racks specified. Coordinated models also tighten documentation, which reduces requests for information during construction and makes the handover pack usable rather than decorative. The saving is real but it is largely avoided rework, so it shows up as an absence of variation orders rather than a line item.

Early enough to influence the design, which in practice means before containment routes and comms room locations are fixed. Coming in after the fit-out drawings are frozen limits BIM to documenting decisions rather than improving them, and the clashes that are cheapest to resolve are the ones found before anything is ordered. If a project is already underway we can still pick it up — we will just be honest about which decisions are now expensive to revisit.

Yes. We support as-built updates where contractors provide them, and produce handover packs structured for operations rather than for the archive — asset and location data, rack elevations, riser diagrams and outlet schedules, aligned to how the estate will actually be supported and maintained. Handover documentation that nobody can use is one of the most common complaints from facilities teams inheriting a new building.

They complement each other. A Matterport digital twin captures what is actually there, which is invaluable for existing buildings, refurbishments and plant rooms where the drawings are out of date or were never accurate. Point cloud exports feed into the model as an as-built reference. BIM is the coordinated design intent; the scan is the verified reality. On refurbishment projects we frequently use both.

We run coordination cycles aligned to your project milestones and issue clash review packs with an issue summary, prioritised by build impact and programme risk rather than by raw clash count. A model will generate thousands of nominal clashes, most of which do not matter; the useful output is the short list that will cost money or delay on site. Issues are tracked through revisions with a clear decision log so nothing is silently resolved.

Yes, and that coordination is most of the value. We participate in the project’s review cycle, coordinate with other disciplines and vendors, and keep the responsibility split explicit. Technology scope sits at the interfaces between architecture, M&E and the fit-out contractor, which is precisely where things fall through the gap when nobody owns the coordination.

Either. BIM is most often delivered as part of IT project delivery or a technology design consultancy engagement, where the same team is already producing the design the model represents. It can also be scoped standalone where you have a design and need it modelled, coordinated and documented properly.