Building Technology Coordinator

Role Purpose & Context

Role Summary

The Building Technology Coordinator is responsible for the daily operation and basic maintenance of our core building technology systems, things like our Building Management System (BMS) and the Computerised Maintenance Management System (CMMS). You'll be the one making sure these systems are actually working as they should, responding to alarms, and keeping our asset data tidy. This role sits right at the heart of our facilities operations, bridging the gap between the physical building and the digital systems that control it. When you do this job well, our buildings run smoothly, our energy bills stay in check, and our occupants are happy and secure. If things go wrong, well, you'll have cold offices, security breaches, or worse, critical equipment failures. The challenge here is juggling multiple systems and often dealing with urgent issues that pop up unexpectedly. The reward, though, is seeing a complex building operate efficiently because of your direct input and quick thinking.

Reporting Structure

• Reports to: Building Technology Manager
• Direct reports:
• Matrix relationships: Facilities Technology Specialist, Smart Building Operator, Building Systems Administrator, FM Technology Analyst,

Key Stakeholders

Internal:

• Facilities Operations Team (engineers, technicians)
• Property Managers
• IT Department (network, security teams)
• Occupant Services / Helpdesk

External:

• BMS Vendors and System Integrators
• Access Control & Security Vendors
• IoT Sensor Providers
• Maintenance Contractors

Organisational Impact

Scope: This role directly impacts the operational efficiency, safety, and comfort of our building occupants. Your work ensures that critical building systems are online and functioning correctly, which in turn affects energy consumption, security posture, and overall tenant satisfaction. Get it right, and the building just works; get it wrong, and you'll hear about it from everyone.

Performance Metrics

Quantitative Metrics

1. Metric: Critical Alarm Response Time
2. Desc: How quickly you acknowledge and begin to action critical alarms (e.g., server room overheating, major water leak).
3. Target: < 15 minutes
4. Freq: Daily, reviewed weekly
5. Example: A BMS alarm for 'Chiller 1 Fault' comes in at 10:00 AM; you've logged the incident and dispatched a technician by 10:12 AM.
6. Metric: Work Order Closure Rate (Tech-Related)
7. Desc: Percentage of building technology-related work orders (e.g., access card issues, BMS setpoint changes) closed within their agreed Service Level Agreement (SLA).
8. Target: 95%
9. Freq: Weekly
10. Example: Out of 50 tech-related work orders this week, 48 were closed on time, hitting 96%.
11. Metric: System Uptime (BMS & Access Control)
12. Desc: The percentage of time our core Building Management System and Access Control systems are fully operational and accessible.
13. Target: 99.5%
14. Freq: Monthly
15. Example: If the BMS was down for 4 hours in a month (roughly 720 hours), your uptime would be 99.44%, just under target.
16. Metric: Preventive Maintenance (PM) Schedule Adherence
17. Desc: The percentage of scheduled preventive maintenance tasks (e.g., BMS sensor calibrations, access control database clean-ups) that are completed on time.
18. Target: 90%
19. Freq: Monthly
20. Example: If there were 20 scheduled PM tasks for the month, and 18 were completed, that's 90% adherence.

Qualitative Metrics

1. Metric: System Data Accuracy
2. Desc: The reliability and cleanliness of the data within the BMS, CMMS, and other building tech platforms. This means fewer 'stale data' points and accurate asset information.
3. Evidence: You'll see this in reduced instances of 'phantom alarms', fewer discrepancies between system data and physical checks, and the ease with which others can use the system data for reports. People will trust the numbers you provide.
4. Metric: Troubleshooting Effectiveness
5. Desc: Your ability to methodically diagnose and resolve system faults, especially those involving multiple interconnected systems, without excessive vendor call-outs or trial-and-error.
6. Evidence: This looks like clear, concise work order notes detailing diagnostic steps, fewer repeat issues for the same problem, and positive feedback from facilities technicians who appreciate your targeted support. You're not just guessing; you're isolating the problem.
7. Metric: Stakeholder Communication Clarity
8. Desc: How clearly and concisely you communicate technical issues, their impact, and resolution plans to non-technical colleagues (e.g., Property Managers, occupants).
9. Evidence: You'll know you're doing well when Property Managers understand the issue without needing a second explanation, and occupants feel informed during outages. Fewer follow-up questions, more 'thanks for the update' messages.
10. Metric: Process Adherence & Improvement
11. Desc: Your commitment to following established procedures (e.g., change management, work order protocols) and identifying opportunities to make them better.
12. Evidence: You'll consistently use the CMMS for all requests, ensure documentation is updated after system changes, and proactively suggest small tweaks to workflows that make everyone's lives a bit easier. It's about making things smoother, not just getting them done.

Primary Traits

• Trait: Systematic Problem-Solver
• Manifestation: When a building system throws a wobbly, you don't just jump to conclusions. You'll methodically check the sensor readings, the controller logic, and the network connection, ticking off possibilities one by one. You're the kind of person who'd rather trace a fault back to its root cause than just reboot and hope for the best. You'll document every step you take in a work order, almost like a detective building a case.
• Benefit: Our building systems are complex beasts. Guessing leads to wasted time, unnecessary vendor call-outs (which cost money!), and unresolved issues. A systematic approach means you can quickly and accurately diagnose why, say, the air conditioning on the 3rd floor isn't responding, saving us hours of discomfort and operational headaches. It's about precision, not just speed.
• Trait: Process-Minded
• Manifestation: You're someone who naturally thinks in terms of 'how do we do this consistently?' You'll probably be the one suggesting we create a checklist for a recurring task or making sure everyone uses the CMMS for requests, rather than just shouting across the office. Before you make a change to a system, you'll think about the steps, the potential impact, and how to roll it back if needed. You appreciate that a good process makes everyone's job easier and safer.
• Benefit: In facilities management, consistency is king. If we don't follow proper processes for things like access card changes or BMS setpoint adjustments, we open ourselves up to security risks, energy waste, or even equipment damage. Without a clear process, a simple tweak can have unintended consequences that are incredibly hard to trace. Your adherence to and improvement of processes keeps everything running predictably and securely.
• Trait: Calm Under Pressure
• Manifestation: When the critical alarm goes off—maybe the server room is overheating, or there's a major water leak detected by a sensor—you're the person who keeps a level head. Your voice on the radio or in a team chat remains steady. You focus on communicating the facts clearly to everyone involved, from the facilities team to the Property Manager, without panicking. You can quickly triage multiple incoming issues, deciding what needs attention first.
• Benefit: Building system failures can be serious. They can mean significant financial losses, safety risks, or major disruption to our occupants. Panic in these situations leads to mistakes, poor communication, and delays. We need someone who can be the eye of the storm, orchestrating the response between different teams and vendors, turning a potential disaster into a managed incident. Your ability to stay calm directly impacts our ability to recover quickly and safely.

Supporting Traits

• Trait: Tenacious
• Desc: You don't give up easily. When a vendor says 'it's not our system' for the third time, you'll dig deeper, gather more evidence, and push for a solution. You're not afraid to keep 'chasing a fault' until it's truly resolved.
• Trait: Curious
• Desc: You're not just interested in *what* a system does, but *why* it does it that way. You'll ask questions about the 'Sequence of Operations' or how a particular sensor is wired, always looking to deepen your understanding of how the building truly works.
• Trait: Translator
• Desc: You can take complex technical jargon—like explaining a BACnet communication error or a CMMS workflow issue—and break it down into simple, understandable terms for a non-technical Property Manager or even an occupant. You bridge the gap between tech and people.

Primary Motivators

1. Motivator: Solving Puzzles and Fixing Things
2. Daily: You get a real kick out of figuring out why a system isn't working and then getting it back online. The satisfaction of 'chasing a fault' and finally pinpointing the issue is a big draw for you.
3. Motivator: Creating Order from Chaos
4. Daily: You enjoy taking messy data or disorganised processes and making them clean, efficient, and reliable. You're driven by the idea of making things work better for everyone.
5. Motivator: Direct Impact on Physical Environments
6. Daily: You like that your work directly affects how a physical building operates, how comfortable people are, and how safe the environment is. You can literally walk into a space and see the results of your efforts.

Potential Demotivators

Honestly, this isn't a role for someone who expects every system to just 'work' all the time. You'll be dealing with legacy systems that are a pain, vendors who point fingers, and the constant battle between IT and OT networks. If you need a perfectly clean, predictable environment where every project goes smoothly from start to finish, you'll probably get frustrated here.

Common Frustrations

1. The 'Single Pane of Glass' is a Lie: You'll spend your day toggling between 5-7 different logins for the BMS, access control, lighting, and work order systems that were all promised to be 'fully integrated'.
2. IT vs. OT Turf Wars: Constantly battling the IT department for network ports, IP addresses, and firewall exceptions for your building equipment, which they often view as a security risk.
3. Vendor Finger-Pointing: When the access control system stops talking to the BMS, the security vendor will blame the controls vendor, the controls vendor will blame the network, and you're stuck in the middle trying to figure it out.
4. Legacy System Handcuffs: Being responsible for a 20-year-old proprietary control system with no documentation, no available spare parts, and only one technician in the county who knows how to fix it.
5. User-Induced Chaos: Explaining for the tenth time that the space heater under their desk is why their office zone is always cold—the thermostat thinks it's 80 degrees and is pumping in cold air.

What Role Doesn't Offer

1. A perfectly stable, 'set it and forget it' environment. Building tech always needs attention.
2. Complete autonomy over strategic decisions; you'll be executing, not defining the big picture.
3. A role where you rarely interact with non-technical people. You'll need to translate tech often.

ADHD Positives

1. The constant flow of varied tasks and urgent issues (alarms, work orders, troubleshooting) can be engaging and prevent boredom.
2. Hyperfocus can be a superpower when 'chasing a fault' in a complex system, allowing for deep, sustained problem-solving.
3. The need for quick, decisive action during critical incidents can be stimulating and play to strengths in high-pressure situations.

ADHD Challenges and Accommodations

1. Maintaining meticulous documentation for every step of troubleshooting or system changes can be challenging; using structured templates and digital checklists can help.
2. Switching between multiple systems and logins can be distracting; tools that consolidate dashboards or single sign-on solutions would be beneficial.
3. Dealing with repetitive data entry for asset management might be tedious; exploring automation tools for routine data updates could ease this.

Dyslexia Positives

1. Strong visual-spatial reasoning, which is excellent for understanding building layouts, network diagrams, and system schematics.
2. Holistic thinking can help in seeing the 'big picture' of how different building systems interact, even when the details are complex.
3. Often good at verbal communication, which is crucial for explaining technical issues to non-technical colleagues.

Dyslexia Challenges and Accommodations

1. Reading and interpreting lengthy 'Sequence of Operations' documents or technical manuals might take longer; using text-to-speech software or having colleagues summarise key points can assist.
2. Accurate data entry into CMMS or other systems can be tricky; double-checking mechanisms, clear input forms, and proofreading tools are important.
3. Writing clear, concise work order notes and incident reports can be challenging; using templates with pre-defined fields and spell-checkers can help ensure clarity.

Autism Positives

1. A strong preference for logical, systematic processes is a perfect fit for troubleshooting complex building systems and following established protocols.
2. Attention to detail is critical for spotting anomalies in data, ensuring system accuracy, and meticulous documentation.
3. The ability to focus deeply on technical tasks without distraction is invaluable when configuring systems or analysing trend logs.
4. Direct, factual communication style is highly valued, especially during critical incidents where clarity is paramount.

Autism Challenges and Accommodations

1. Unexpected changes to plans or urgent, disruptive requests (which are common in facilities) can be challenging; clear communication about priorities and realistic expectations for flexibility are key.
2. Navigating complex social dynamics with multiple vendors and internal teams can be difficult; clear roles, responsibilities, and communication channels (e.g., email over impromptu calls) can help.
3. Sensory input from alarms, flashing lights, or noisy plant rooms might be overwhelming; access to quiet spaces or noise-cancelling headphones can be helpful.

Key Responsibilities

Experience Levels Responsibilities

1. Level: Mid-Level Professional (Building Technology Coordinator)
2. Responsibilities: Independently manage the daily operation of one or two core building technology systems, typically the BMS and CMMS. This means you're the go-to person for routine issues and questions.
3. Take ownership of critical alarm responses. You'll be the first point of contact, acknowledging alarms, performing initial diagnostics, and dispatching the right facilities team members or vendors. Get it wrong, and things can escalate quickly.
4. Perform routine system checks and preventive maintenance tasks for the BMS and access control systems. Think sensor calibrations, database clean-ups, and ensuring schedules are correct.
5. Manage work orders related to building technology from start to finish. This includes creating, assigning, tracking, and closing tickets in the CMMS, making sure nothing falls through the cracks.
6. Generate and distribute standard operational reports from the BMS and CMMS. Property Managers will rely on you for things like energy consumption figures and work order summaries.
7. Support the onboarding of new building occupants by issuing and revoking access credentials. You'll also troubleshoot basic access issues, like a card not working or a door not locking.
8. Identify recurring system issues or inefficiencies and propose initial solutions to your manager. You're not just fixing things, you're thinking about how to prevent them from happening again.
9. Supervision: You'll have weekly check-ins with your Building Technology Manager to discuss priorities, ongoing projects, and any tricky issues. For routine tasks, you'll work independently, but you're encouraged to escalate novel or complex problems. We're here to support you, not micromanage.
10. Decision: You've got the green light for routine operational decisions within established guidelines. This means adjusting BMS setpoints within approved ranges, prioritising work orders based on urgency, and issuing standard access cards. Any changes to system logic, major software updates, or anything costing more than, say, £500, will need your manager's approval. If you're unsure, just ask—it's always better to check.
11. Success: You'll know you're succeeding when critical alarms are handled swiftly and effectively, work orders are consistently closed within SLA, and the data in your systems is reliable. Your colleagues in Facilities and Property Management will trust your judgment and the information you provide. Basically, the building's tech runs smoothly because of your consistent effort and smart problem-solving.

Decision-Making Authority

• Type: BMS Setpoint Adjustments
• Entry: Requires direct approval from supervisor for any changes, even minor ones.
• Mid: Can independently adjust setpoints within pre-approved operational ranges (e.g., +/- 2°C for office temperatures). Any changes outside this range or to critical systems (e.g., server room cooling) require manager approval.
• Senior: Full autonomy to adjust setpoints across all systems, considering energy efficiency and occupant comfort. Consults with manager on significant changes impacting energy budget or tenant relations.
• Type: Work Order Prioritisation
• Entry: Priorities are assigned by supervisor; executes tasks as directed.
• Mid: Independently prioritises routine building technology work orders based on established SLAs and urgency (e.g., security breach > light bulb change). Escalates conflicting priorities or critical issues to manager.
• Senior: Defines and refines work order prioritisation protocols for the team. Makes judgment calls on complex, multi-system issues, balancing immediate impact with long-term system health.
• Type: Access Control Credential Management
• Entry: Issues/revokes access cards based on explicit, written requests approved by supervisor.
• Mid: Independently issues, modifies, and revokes access credentials for standard building occupants and contractors, following established security policies. Reports any unusual requests or security concerns to manager immediately.
• Senior: Manages and audits access control policies and procedures. Approves non-standard access requests and oversees system integrations with HR/onboarding platforms.
• Type: Vendor Engagement for Troubleshooting
• Entry: Initiates vendor contact only after supervisor approval and with clear instructions.
• Mid: Can independently contact specific vendors for routine troubleshooting (e.g., 'BMS isn't communicating with this controller, can you check the licence?'). Escalates issues requiring significant cost or complex diagnosis to manager.
• Senior: Directs vendor engagement for complex system issues, manages vendor performance, and negotiates service level agreements for routine maintenance. Authorises minor vendor call-outs up to £1,000.

Competency Requirements

Foundation Skills (Transferable)

These are the core skills that underpin everything you do in this role. They're not just 'nice-to-haves'; they're essential for navigating the day-to-day challenges of building technology.

• Category: Communication & Collaboration
• Skills: Clear Verbal Communication: Explaining technical issues in plain English to non-technical colleagues and vendors.
• Written Communication: Crafting concise work order notes, incident reports, and internal emails.
• Active Listening: Truly understanding the problem when a facilities technician or occupant describes an issue.
• Teamwork: Working effectively with facilities operations, IT, and external vendors to resolve problems.
• Category: Problem-Solving & Critical Thinking
• Skills: Systematic Troubleshooting: Following a logical process to diagnose faults in complex systems.
• Root Cause Analysis: Going beyond the symptom to identify the actual underlying problem.
• Analytical Thinking: Interpreting data from BMS trend logs or CMMS reports to identify patterns and issues.
• Prioritisation: Quickly assessing the urgency and impact of multiple incoming requests and alarms.
• Category: Organisation & Attention to Detail
• Skills: Task Management: Juggling multiple work orders and system checks without dropping the ball.
• Documentation: Maintaining accurate records of system changes, asset information, and troubleshooting steps.
• Accuracy: Ensuring data entered into systems, like asset inventories or access credentials, is correct.
• Process Adherence: Consistently following established procedures and protocols for system changes and security.
• Category: Adaptability & Resilience
• Skills: Dealing with Ambiguity: Navigating situations where information is incomplete or conflicting.
• Stress Management: Remaining calm and effective during critical system failures or urgent demands.
• Learning Agility: Quickly picking up new software features or understanding new system configurations.
• Flexibility: Adjusting plans and priorities when unexpected issues arise (which they will).

Functional Skills (Role-Specific Technical)

These are the specific technical and domain-specific skills you'll need to hit the ground running. We're looking for someone who understands how buildings really work, not just the software.

Technical Competencies

• Skill: Building Automation Systems (BAS) Logic & Control Sequences
• Desc: You'll need a solid grasp of how HVAC, lighting, and other building systems are programmed to interact. This means being able to read and interpret 'Sequences of Operation' documents and understand basic control logic (e.g., if-then statements, setpoints, deadbands).
• Level: Intermediate
• Skill: Preventive & Predictive Maintenance Strategy (Basic)
• Desc: Understanding the difference between just fixing things when they break and proactively preventing failures. You'll use CMMS data and BMS trend logs to help schedule maintenance based on equipment runtime or early signs of degradation.
• Level: Intermediate
• Skill: Low-Voltage Systems & Network Protocols (Basic)
• Desc: A foundational understanding of the 'languages' our building tech speaks, like BACnet and Modbus. You should know the basics of network architecture (e.g., what an IP address is, the difference between IT and OT networks) and how field devices get power.
• Level: Intermediate
• Skill: Space Utilisation & Occupancy Analytics (Basic)
• Desc: Being able to look at simple occupancy dashboards from IoT sensors and understand what the data is telling you about how spaces are being used. You won't be designing the strategy, but you'll be interpreting the output.
• Level: Basic
• Skill: Energy Management & Sustainability Reporting (Basic)
• Desc: Connecting building system performance to our energy goals. You'll be pulling data on energy (kWh), water, and gas consumption from the BMS or utility meters, and understanding basic reporting against benchmarks.
• Level: Intermediate
• Skill: Vendor & Systems Integrator Management (Routine)
• Desc: You'll be the first point of contact for our established BMS, access control, and CMMS vendors for routine troubleshooting and support requests. This means clearly explaining issues and following up on resolutions.
• Level: Intermediate

Digital Tools

• Tool: Johnson Controls Metasys / Siemens Desigo CC / Schneider Electric EcoStruxure (or similar BMS)
• Level: Intermediate
• Usage: Monitoring dashboards for building performance, acknowledging and triaging alarms, pulling trend logs for basic analysis, adjusting approved setpoints, and verifying schedules.
• Tool: Planon / Archibus / Corrigo (JLL) / ServiceChannel (or similar CMMS/IWMS)
• Level: Intermediate
• Usage: Creating, assigning, tracking, and closing work orders; managing asset inventory data (e.g., adding new equipment, updating locations); running pre-defined reports on maintenance activities.
• Tool: Genetec Security Center / LenelS2 OnGuard / Brivo / Verkada (or similar Access Control)
• Level: Intermediate
• Usage: Assigning and revoking access credentials for occupants and contractors, responding to door-forced-open alarms, pulling access history reports for security incidents, and troubleshooting basic card reader issues.
• Tool: Power BI / Tableau (or similar Data Visualization)
• Level: Basic
• Usage: Interacting with existing dashboards to monitor building performance metrics (e.g., energy consumption, occupancy rates), filtering data, and exporting basic reports for further analysis in Excel.
• Tool: MS Teams / SharePoint (or similar Collaboration & Project Management)
• Level: Intermediate
• Usage: Communicating with internal teams and external vendors, sharing documentation, managing your own task lists, and participating in team meetings and project updates.

Industry Knowledge

• Area: Building Systems Fundamentals
• Desc: A good understanding of how core building systems like HVAC, lighting, and security physically operate, not just how they're controlled digitally. This helps you understand the 'why' behind system behaviour.
• Area: Facilities Management Operations
• Desc: Familiarity with the day-to-day realities of facilities management, including common challenges, maintenance cycles, and the needs of building occupants and property managers.
• Area: Cybersecurity Best Practices (Basic)
• Desc: An awareness of basic cybersecurity principles, especially as they relate to Operational Technology (OT) networks, and the importance of following IT security policies for building systems.

Regulatory Compliance Regulations

• Reg: Health & Safety at Work etc. Act 1974
• Usage: Understanding your responsibilities for safe operation of building systems and reporting any safety concerns related to building technology.
• Reg: General Data Protection Regulation (GDPR)
• Usage: Handling personal data (e.g., access card information, occupancy data) responsibly and securely, understanding the implications of data privacy.
• Reg: Building Regulations (Part L - Conservation of Fuel and Power)
• Usage: Understanding how building system settings and optimisation contribute to energy efficiency targets and compliance.

Essential Prerequisites

• At least 2 years of hands-on experience working with Building Management Systems (BMS) or similar building technology platforms.
• Demonstrable experience troubleshooting technical issues in a facilities or IT support environment.
• A proven track record of managing and prioritising multiple tasks effectively in a dynamic setting.
• Experience with a Computerised Maintenance Management System (CMMS) for work order management and asset tracking.
• The ability to communicate clearly, both verbally and in writing, with technical and non-technical audiences.

Career Pathway Context

We're looking for someone who's already got a couple of years under their belt in building tech or a related field. You should be past the 'learning the ropes' stage and ready to take ownership of systems. If you've been a facilities technician who's always tinkered with the controls, or an IT support specialist who's curious about buildings, this could be a great fit. It's about building on that foundational experience.

Qualifications & Credentials

Emerging Foundation Skills

• Skill: Basic Data Storytelling
• Why: We're collecting more and more data from our buildings, but raw numbers aren't enough. The ability to turn complex data (e.g., energy consumption, occupancy trends) into a compelling story that non-technical managers can understand is becoming vital. It's about showing *why* something matters, not just *what* the numbers are.
• Concepts: [{'concept_name': 'Audience-Centric Communication', 'description': 'Tailoring your data insights to what your audience (e.g., Property Manager, Finance) cares about most.'}, {'concept_name': 'Visualisation Best Practices', 'description': 'Choosing the right charts and graphs to make data clear and impactful, avoiding cluttered dashboards.'}, {'concept_name': 'Narrative Structure', 'description': 'Building a simple story around your data: problem, insight, recommendation.'}, {'concept_name': 'Actionable Insights', 'description': 'Ensuring your data analysis leads to clear, practical steps that can be taken.'}]
• Prepare: This month: Start by practicing explaining a simple BMS trend (e.g., temperature fluctuation) to a colleague who isn't familiar with it, focusing on the 'so what?'.
• Month 2: Experiment with different chart types in Power BI or Excel to present the same data, seeing which is clearer.
• Month 3: Take a free online course on 'Data Storytelling Fundamentals' (e.g., from Coursera or LinkedIn Learning).
• Month 4: Volunteer to present a small data insight in a team meeting, focusing on a clear recommendation.
• QuickWin: When you're pulling a report for a Property Manager, add a simple, one-paragraph summary at the top explaining the key takeaway and what they should do next. Immediate impact.
• Skill: Basic Cybersecurity for OT Systems
• Why: Our building systems are increasingly connected, making them potential targets for cyber-attacks. Understanding the basics of securing Operational Technology (OT) networks is no longer just an IT job; it's a facilities responsibility. A breach could mean anything from data loss to physical damage or even safety risks.
• Concepts: [{'concept_name': 'IT vs. OT Security Differences', 'description': 'Understanding why securing building systems is different from securing corporate laptops (e.g., uptime is critical, legacy systems).'}, {'concept_name': 'Network Segmentation', 'description': 'The idea of separating building networks from corporate networks to limit attack surfaces.'}, {'concept_name': 'Patch Management Basics', 'description': 'Understanding the importance of software updates and firmware patches for building controllers.'}, {'concept_name': 'Physical Security of Devices', 'description': 'Recognising that physical access to controllers and servers is also a security risk.'}]
• Prepare: This month: Read up on common OT cybersecurity threats and best practices (e.g., NCSC guidance).
• Month 2: Have a chat with our IT security team to understand their concerns and current policies for building systems.
• Month 3: Identify 2-3 'quick wins' for improving physical security of building tech devices in our plant rooms.
• Month 4: Complete a basic online course on 'Introduction to OT Security' (e.g., SANS Institute or similar).
• QuickWin: Always use strong, unique passwords for building system logins and report any suspicious network activity you spot on our building control networks to IT immediately. Simple, but critical.

Advancing Technical Skills

• Skill: Advanced BMS Configuration & Logic
• Why: Moving beyond just operating the BMS to understanding how to modify its core logic. This allows for greater optimisation, customisation, and the ability to truly fine-tune building performance without constant vendor reliance.
• Concepts: [{'concept_name': 'Graphical Programming Languages (e.g., Niagara Workbench)', 'description': 'Learning to read and even write basic control logic for various BMS platforms.'}, {'concept_name': 'PID Control Loops', 'description': 'Understanding proportional-integral-derivative control for precise system regulation.'}, {'concept_name': 'Optimisation Routines', 'description': 'Designing sequences for things like optimal start/stop or demand-controlled ventilation.'}, {'concept_name': 'Troubleshooting at the Controller Level', 'description': 'Diagnosing issues directly on the physical controllers, not just from the UI.'}]
• Prepare: This month: Ask to shadow a BMS technician during a complex troubleshooting session.
• Month 2: Get access to the BMS engineering tools (if not already) and start exploring the logic diagrams.
• Month 3: Take an online course or attend a vendor-specific training on advanced BMS programming.
• Month 4: Work with your manager to identify a small, non-critical BMS logic modification you can implement under supervision.
• QuickWin: Spend 30 minutes each week just exploring the BMS engineering environment, clicking around, and trying to understand how different sequences are built. No changes, just learning.
• Skill: Basic API Integration Concepts
• Why: The 'single pane of glass' might be a lie, but APIs (Application Programming Interfaces) are making it easier for systems to talk to each other. Understanding how APIs work will be crucial for connecting our BMS to our CMMS, or pulling data into analytics platforms without manual exports.
• Concepts: [{'concept_name': "What an API Is (and isn't)", 'description': "Understanding that APIs are essentially digital 'connectors' that allow software to communicate."}, {'concept_name': 'RESTful Principles', 'description': 'Basic understanding of common API design principles (GET, POST requests).'}, {'concept_name': 'JSON/XML Data Formats', 'description': 'How data is typically structured when sent between systems via APIs.'}, {'concept_name': 'Authentication & Authorisation', 'description': 'How systems verify who is allowed to access and exchange data.'}]
• Prepare: This month: Read introductory articles on 'What is an API?' and 'How do APIs work?'.
• Month 2: Explore the API documentation for one of our existing systems (e.g., CMMS or a simple IoT platform).
• Month 3: Try a free online tutorial on using a simple API (e.g., a weather API) with a tool like Postman or even Excel Power Query.
• Month 4: Discuss with your manager how we might use an API to automate a manual data transfer between two systems.
• QuickWin: Just start looking for 'API documentation' on our vendor websites. You'll be surprised what you find. Even just understanding that they exist is a great first step.

Education Requirements

• Level: Minimum
• Req: A relevant vocational qualification (e.g., NVQ Level 3/4 in Electrical, Mechanical, or Building Services Engineering) or a relevant HNC/HND.
• Alts: We're pragmatic. If you've got 4+ years of demonstrable, hands-on experience in building technology or facilities operations, especially with a strong technical component, we'll consider that equivalent.
• Level: Preferred
• Req: A degree (BSc/BEng) in Building Services Engineering, Electrical Engineering, Automation, or a related technical field.
• Alts: More experience is always a plus. If you've got a degree in something else but a strong portfolio of building tech projects, we'd still love to hear from you.

Experience Requirements

You'll need at least 2-5 years of hands-on experience in a role directly involving the operation, maintenance, or support of building technology systems. This isn't an entry-level job; we need someone who's already familiar with the day-to-day realities of managing systems like a BMS, CMMS, or access control. Experience in a facilities management, building services, or IT support role with a strong technical focus would be ideal.

Preferred Certifications

• Cert: Relevant BMS Vendor Certification
• Prod: Johnson Controls, Siemens, Schneider Electric (or similar)
• Usage: Shows you've got specific training and expertise on the systems we likely use, meaning a faster ramp-up time.
• Cert: CompTIA A+ or Network+
• Prod: CompTIA
• Usage: Demonstrates a solid understanding of IT fundamentals, which is increasingly important as building tech converges with IT networks.
• Cert: CSCS Card (Construction Skills Certification Scheme)
• Prod: CITB
• Usage: If your role involves working on active construction sites for new installations or major retrofits, this is usually a must-have for health and safety.

Recommended Activities

• Attending vendor-specific training courses for new features or system upgrades.
• Joining industry associations like CIBSE (Chartered Institution of Building Services Engineers) or BSRIA.
• Subscribing to industry publications and newsletters to stay current on trends.
• Participating in online forums or communities dedicated to building automation or facilities technology.
• Taking online courses on topics like data analytics fundamentals or basic networking.

Career Progression Pathways

Entry Paths to This Role

• Path: Facilities Technician / Engineer
• Time: 2-4 years
• Path: IT Support Specialist (with interest in OT)
• Time: 2-3 years
• Path: Building Services Apprentice / Graduate
• Time: 1-2 years post-qualification

Career Progression From This Role

• Pathway: Senior Building Technology Specialist (L3)
• Time: 3-5 years in current role

Long Term Vision Potential Roles

• Title: Lead Building Systems Integrator (L4)
• Time: 5-8 years from current role
• Title: Building Technology Manager (L5)
• Time: 8-12 years from current role
• Title: Smart Building Solutions Architect (IC Path)
• Time: 8-12 years from current role

How Zavmo Delivers This Role's Development

DISCOVER Phase: Skills Gap Analysis

Zavmo maps your current competencies against all requirements in this job description through conversational assessment. We evaluate your foundation skills (communication, strategic thinking), functional skills (CRM expertise, negotiation), and readiness for career progression.

Output: Personalised skills gap heat map showing strengths and priorities, estimated time to competency, neurodiversity accommodations.

DISCUSS Phase: Personalised Learning Pathway

Based on your DISCOVER results, Zavmo creates a personalised learning plan prioritised by impact: foundation skills first, then functional skills. We adapt to your learning style, pace, and neurodiversity needs (ADHD, dyslexia, autism).

Output: Week-by-week schedule, each module linked to specific job responsibilities, checkpoints and milestones.

DELIVER Phase: Conversational Learning

Learn through conversation, not boring modules. Zavmo uses 10 conversation types (Socratic dialogue, role-play, coaching, case studies) to build competence. Practice difficult QBR presentations, negotiate tough renewals, and handle churn conversations in a safe AI environment before facing real clients.

Example: "For 'Stakeholder Mapping', Zavmo will guide you through analysing a complex enterprise account, identifying key decision-makers, and building an engagement strategy."

DEMONSTRATE Phase: Competency Assessment

Zavmo automatically builds your evidence portfolio as you learn. Every conversation, practice scenario, and application example is captured and mapped to NOS performance criteria. When ready, your portfolio supports OFQUAL qualification claims and demonstrates competence to employers.

Output: Competency matrix, evidence portfolio (downloadable), qualification readiness, career progression score.