If you manage facilities for a mid-sized Irish business, you have probably inherited a Building Energy Management System that was state of the art when the building opened. That was a decade or two ago. The hardware still runs, more or less. The control logic mostly does what it should. Spare parts are getting harder to find. The original commissioning engineers have retired or moved on. The system shows up in your CSRD energy data with all the holes you would expect from a controls platform that was specified before anyone said the word CSRD.
At some point in the next three years, you are going to be asked to upgrade this system. The question is not whether the upgrade is needed. It is who does the work. This piece is a decision framework for facility managers weighing whether to outsource a BEMS legacy upgrade or attempt to handle it in-house.
Why Legacy BEMS Upgrades Are Different from Routine Maintenance
Routine BEMS maintenance is a continuous activity. A legacy upgrade is a project. The two are different in scope, in skill mix required, and in risk profile. Confusing them is the most common cause of failed upgrade projects.
- A legacy upgrade often touches hardware, firmware, network, and the building’s underlying mechanical systems in a single coordinated programme
- The data migration from the old system to the new is rarely simple; control schedules, alarm logic, and historical trends must be preserved
- Commissioning the upgraded system requires the same discipline as commissioning a new building, often over multiple seasons
- The risk window is concentrated; a controls outage during a major Irish summer or winter peak can be costly
- Documentation and as-built drawings are usually incomplete on the original system, adding archaeology work to the scope
None of these challenges are insurmountable. All of them require specialist capability and time, which is exactly what your in-house team is least likely to have spare.
The Delegate vs Keep-In-House Decision
The case for outsourcing a BEMS legacy upgrade is essentially the same case made for any specialist project work. The right framework treats it as a delegation decision, not a buy-versus-build question.
| Decision factor | Outsource if | Keep in-house if |
|---|---|---|
| Project complexity | Multi-system, multi-vendor coordination | Single-vendor minor upgrade with vendor support |
| In-house engineering depth | Limited or fully committed to routine operations | Dedicated controls engineer with relevant project history |
| Vendor relationship | Original controls vendor no longer trading or unresponsive | Original vendor still strong and offering upgrade path |
| Timeline pressure | Project must complete inside one financial year | Multi-year staged upgrade acceptable |
| Risk tolerance | Building criticality is high; mistakes are expensive | Building can tolerate temporary degradation |
| Compliance exposure | CSRD, F-gas, healthcare, pharma context | Lower-regulation commercial environments |
Score honestly across these six factors and the answer becomes obvious. Mid-sized Irish businesses with critical or regulated environments will almost always score in favour of outsourcing the project work, even where they retain an in-house facilities team for ongoing operations.
What Good Outsourcing Looks Like
The decision to outsource is the easy part. Getting the outsourcing right is harder. The specifics that separate a successful BEMS upgrade outsourcing engagement from a painful one are well documented.
- A clear scope of work, written buyer-side rather than copied from a vendor template
- A baseline assessment before the contract is signed, so both sides understand the starting point
- Documented success criteria, including performance metrics measured against the upgraded system after commissioning
- A staged delivery plan that allows the building to continue operating during the upgrade
- Risk allocation that reflects reality, with the specialist taking the risks they can control and the building owner retaining the risks they own
- An evidence-based handover, including commissioning records, as-built documentation, and operating manuals updated to the new system
- A post-upgrade optimisation period, recognising that the upgraded system needs months of tuning to reach its design intent
If you are commissioning this work and your draft scope is missing any of these elements, the project is more exposed than it needs to be.
The Scope of Work You Should Write
Most facility managers receive scope-of-work documents from controls vendors. Better outcomes come from writing the buyer-side scope before any vendor sees the document. The structure below is the one that consistently produces clean tenders and fair pricing.
- Building description, current BEMS description, and known issues
- Upgrade objectives expressed in operational terms (energy reduction targets, reporting requirements, integration goals)
- System boundary and integration points (which existing systems remain, which are replaced, which are extended)
- Protocol and standards requirements (open protocols, specific BACnet or Modbus expectations)
- Phasing and downtime constraints (which periods are off-limits for major work)
- Commissioning evidence and documentation expectations
- Maintenance contract structure to follow the upgrade
- Cybersecurity posture expected of the vendor
- Health and safety, GDPR/DPC, and site access arrangements
- Acceptance criteria and the handover process
A scope document built around these headings is roughly twenty pages. It is a serious procurement document. It also tends to filter out the controls firms that cannot do the work, which is exactly what you want.
Who You Are Looking For
The right specialist for a BEMS legacy upgrade is not always the firm that maintains your current system. Sometimes it is; sometimes a fresh perspective is needed. The qualities that signal a credible specialist are recognisable.
| Signal | Why it matters |
|---|---|
| Project history in similar legacy upgrades | The specific failure modes are predictable; experience teaches them |
| System-agnostic posture | The specialist will recommend the right replacement, not the one they sell |
| Named senior engineer leading the project | Continuity matters across a multi-month upgrade |
| Engineering depth in adjacent disciplines | HVAC, electrical, and network coordination is part of the job |
| Willingness to discuss commissioning and post-handover support upfront | Vendors who avoid this topic are signalling intent to walk away after commissioning |
| Local presence sufficient for emergency call-out | Upgrades occasionally surprise; local response matters |
For Irish facility managers, the pool of specialists who meet most of these criteria is small but identifiable. Looking at BEMS legacy system upgrade specialists shows what a serious offering looks like. Standard Control Systems, headquartered in Dublin with more than forty years in Irish and international project work, is among the established providers focused specifically on this category. Whether or not they fit your particular project, the structure of their public service offering is a useful benchmark against which to evaluate any bid.
Common Failure Modes and How to Avoid Them
BEMS legacy upgrade projects fail in predictable ways. The mitigations are also predictable.
- Scope creep during commissioning. Mitigated by a tight original scope with explicit change control. Document changes in writing as they arise.
- Loss of historical data during migration. Mitigated by an explicit data migration plan signed off before any old hardware is decommissioned.
- Comfort complaints from occupants during the upgrade. Mitigated by phasing the work outside peak load periods where possible and over-communicating with tenants.
- BCAR or compliance evidence gaps. Mitigated by aligning the upgrade commissioning plan with whatever compliance regime the building operates under.
- Vendor walking away after final invoice. Mitigated by structuring payment milestones that include a post-handover optimisation period.
- Integration headaches with adjacent systems. Mitigated by including IT and other building services teams in the design phase, not just facilities.
None of these are unusual outcomes. All of them are avoidable with disciplined scoping and management.
What This Means for Your GDPR and Compliance Posture
BEMS upgrade projects typically involve vendor access to building data, sometimes including data that touches GDPR-relevant categories such as occupancy, access logs, and integration with security systems. A few simple disciplines protect you.
- Restrict vendor remote access to time-boxed windows during the project
- Revoke all temporary access at the end of the project, in writing
- Document what data the vendor has touched or extracted, and where it now lives
- Update your processor registry if the new BEMS or its support contract introduces a new vendor relationship
- Brief your DPC liaison if the upgrade changes the scope of personal data the building’s systems handle
None of this is dramatic. All of it is the kind of detail that audits surface and that good outsourcing arrangements address routinely.
The Strategic Takeaway for Irish Facility Managers
A BEMS legacy upgrade is one of the larger discrete projects an Irish facility manager will lead. Trying to deliver it in-house, in parallel with the day job, is usually a false economy. Outsourcing the project work to a specialist, while retaining in-house facilities ownership of operations, is the model that consistently produces good outcomes.
The decisions that matter sit at the scoping and procurement stage, not the technical stage. Write the scope of work yourself. Insist on a baseline assessment before commitment. Choose a specialist with relevant project history and a system-agnostic posture. Structure the contract to include post-handover optimisation. The technical delivery follows from these decisions.
If you are sitting in front of a fifteen-year-old BEMS and the conversation about upgrading it has started, you have time to do this well. Use that time on the scoping work. Delegate the rest to the specialist you choose.