Skip to content
TechnoGuru — Think Technology, Think TechnoGuru

Building Technology Planner.

— Project type · spaces · systems · dependencies

What this building will make you decide.

10 spaces · 17 systems · 219 coordination questions · 41 open items

1 · Project type

2 · Spaces in scope

Everything this building type usually has. Untick what this project does not.

The figure beside each space is its coordination questions. They add up to the total above.

3 · Systems in reception / arrival

The first impression, a queue, a desk, and the point where visitors are identified.

4 · What camera surveillance depends on

Camera surveillance depends on 8 things, grouped by how hard the dependency is — cannot work without it: Network switching, shared with 8 other systems in scope; Structured cabling, shared with 8 other systems in scope; Electrical supply, shared with 13 other systems in scope; Containment and cable pathways, shared with 7 other systems in scope. usual, not universal: Power over Ethernet, shared with 3 other systems in scope; Recording and retention; Rack and equipment room, shared with 8 other systems in scope. only in certain cases: Uninterruptible power, only where the client expects to keep seeing and recording through a mains interruption, shared with 5 other systems in scope.

  • Cannot work without it(4)

  • Usual, not universal(3)

  • Only in certain cases(1)

7 are shared with other selected systems — that is where the coordination is.

Camera surveillance and network switching

An IP camera is a network device. With no switch port and no address it produces no picture at all, anywhere.

5 · Camera surveillance — in reception / arrival

Cameras are asked for early and specified as a count, when what decides the design is what the picture has to prove.

Ask these now

  • Who watches the picture, and from where — a staffed position, a duty manager's phone, or nobody until something is reviewed afterwards?
  • How long does recorded footage need to be kept before it is overwritten, and who made that decision?
  • Where do people need to be identifiable, as opposed to simply seen? The two ask very different things of the same camera.
  • Who signs off camera positions against the privacy expectations of the people using the space?
  • Does the desk position need a camera looking at it, and who reviews that footage?

Drawings this will need

  • Reflected ceiling plan with camera positions and cable drops
  • Containment route from each camera position back to the nearest node
  • Elevations for any camera on a wall, column or external face

Still open

  • How long recordings are kept, and who is accountable for that decision
  • Whether recording sits in this building or somewhere else
  • Who holds the right to review and export footage after handover

7 · What these systems pull in

Electrical supplyPower over EthernetRecording and retentionInternet or wide-area uplinkContainment and cable pathwaysHeat removalDoor hardwareLoudspeakersAmplificationAudio processingMicrophonesRoom cameraDisplay or screenConferencing platformControl and user interfaceSignal transportVideo processingContent and sourceStructure and service accessProjection surfaceMounting and fixingRoom geometry

2 dependencies in this scope are not settled by a planning tool: Access control and fire detection; Fire detection and automation and building controls. They belong to the appointed specialist and the authority having jurisdiction.

Background music and paging is a separate system from fire detection in this planner. The two appearing in the same building does not make them one system, and nothing here links them.

This is a planning conversation, not a bill of quantities, not a compliance determination and not a design. It sets out what has to be decided and which drawings those decisions will need. Quantities, specifications and any statutory position come from the appointed consultants and from a site-specific review.

8 · Where this goes next

41 decisions are still open across 10 spaces of this hotel / hospitality. Send the floor plan and the reflected ceiling plan and we will mark up the containment, the rack positions and the coordination items this scope creates.

Nothing you select here is sent anywhere. The planner keeps no record of it.

Plan for a hotel / hospitality

10 spaces · 17 systems · 219 coordination questions · 41 open items

This is a planning conversation, not a bill of quantities, not a compliance determination and not a design. It sets out what has to be decided and which drawings those decisions will need. Quantities, specifications and any statutory position come from the appointed consultants and from a site-specific review.

Reception / arrival

The first impression, a queue, a desk, and the point where visitors are identified.

Camera surveillance in Reception / arrival

Cameras are asked for early and specified as a count, when what decides the design is what the picture has to prove.

Coordination questions:

  • Who watches the picture, and from where — a staffed position, a duty manager's phone, or nobody until something is reviewed afterwards?
  • How long does recorded footage need to be kept before it is overwritten, and who made that decision?
  • Where do people need to be identifiable, as opposed to simply seen? The two ask very different things of the same camera.
  • Who signs off camera positions against the privacy expectations of the people using the space?
  • Does the desk position need a camera looking at it, and who reviews that footage?

Drawings needed:

  • Reflected ceiling plan with camera positions and cable drops
  • Containment route from each camera position back to the nearest node
  • Elevations for any camera on a wall, column or external face

Open decisions:

  • How long recordings are kept, and who is accountable for that decision
  • Whether recording sits in this building or somewhere else
  • Who holds the right to review and export footage after handover
Access control in Reception / arrival

Doors get controlled late, after the ironmongery schedule is issued and the frames are ordered.

Coordination questions:

  • Which doors are controlled, and which are simply locked? The list is always shorter than the first conversation suggests.
  • Who issues and revokes credentials once the building is occupied, and on which system do they do it?
  • Does this door need to record who passed through it, or only to stop who should not?
  • Who owns the door — the technology package, the ironmongery package, or nobody yet?

Drawings needed:

  • Door schedule naming every controlled leaf and its hardware
  • Door hardware detail per door type, coordinated with the ironmongery package
  • Cable route from each door back to its controller position

Open decisions:

  • Credential type, and whether people will actually carry it
  • Whether each door is monitored, controlled, or both
  • How controlled doors behave in an emergency — set by the project's fire strategy and the authority having jurisdiction. PROJECT-SPECIFIC VERIFICATION REQUIRED before hardware is ordered.
Wi-Fi in Reception / arrival

Wireless is judged by the worst experience anyone has, not the average one.

Coordination questions:

  • What is the busiest realistic number of devices in this space at once, and are they people's phones or the building's own equipment?
  • Is the goal coverage or capacity? A corridor and a full banquet hall fail for completely different reasons.
  • Where can an access point physically be mounted, given the ceiling type and the finishes?
  • Who owns the guest network, its terms of use and the support call when it is slow?

Drawings needed:

  • Ceiling plan with access-point positions and mounting type
  • Cable route from each access point to the floor node
  • Any survey or predictive design the layout was based on

Open decisions:

  • How guest and staff traffic are kept apart
  • Whether a predictive design is accepted or a site survey is commissioned
Telephony in Reception / arrival

Handset counts are inherited from the previous building and rarely re-examined.

Coordination questions:

  • Who actually needs a handset once everybody's mobile phone is counted?
  • Does anything here have to keep working when the internet does not?
  • Where do outside lines terminate, and who is the provider dealing with?

Drawings needed:

  • Outlet plan showing handset positions against the furniture layout
  • Riser diagram showing where voice joins the rest of the network

Open decisions:

  • Handset count, checked against how people actually work
  • Whether calls leave over a data connection or a local line
Background music and paging in Reception / arrival

Music and announcements are treated as a finishing item, after the ceiling is coordinated.

Coordination questions:

  • Is this background music, spoken announcements, or both — and who is expected to speak?
  • Which zones does an announcement reach, and which does it deliberately not reach?
  • How noisy is this space when it is full? That, not its floor area, decides the layout.
  • Who holds the right to play the music being planned in a commercial space?

Drawings needed:

  • Ceiling plan with loudspeaker positions coordinated against lighting and air terminals
  • Zone plan showing what is grouped with what
  • Amplifier and rack position with the cable route to each zone

Open decisions:

  • Where the zone boundaries actually fall
  • Where the music comes from and who is licensed for it
  • Who is allowed to make an announcement, and from where
Digital signage in Reception / arrival

Screens are easy to buy and hard to keep current; the content plan is the part that is usually missing.

Coordination questions:

  • Who writes the content, and how often does it actually change?
  • Is the screen read while walking past or while standing still? That sets the size before any product is chosen.
  • What is behind the screen — is there power and a cable route there, or is this a surface-mounted afterthought?
  • Is this screen for visitors, for staff, or for the brand? It cannot be equally good at all three.

Drawings needed:

  • Elevation with screen size and mounting height
  • Power and data outlet positions behind each screen
  • Structural detail wherever a screen hangs on a non-structural finish

Open decisions:

  • Who owns the content after handover
  • Screen orientation and size, agreed with the interior design
Fire detection in Reception / arrival

Fire detection is in scope for this space. Every requirement, threshold, coverage rule and compliance position belongs to the project's fire strategy and the authority having jurisdiction — this planner determines none of them. PROJECT-SPECIFIC VERIFICATION REQUIRED.

Coordination questions:

  • Who is the appointed fire consultant on this project, and has the fire strategy been issued?
  • Which authority having jurisdiction approves this building, and at what stage do they review it?
  • Has the fire scheme for this space been coordinated with the reflected ceiling plan and the finishes?
  • Which other packages are waiting on the fire scheme before they can be finalised?

Drawings needed:

  • The fire consultant's scheme drawing for this space
  • Reflected ceiling plan issued to the fire consultant for coordination
  • Containment coordination drawing showing the routes reserved for the fire scheme

Open decisions:

  • The fire scheme itself, issued by the appointed fire consultant and reviewed by the authority having jurisdiction. PROJECT-SPECIFIC VERIFICATION REQUIRED — this planner settles none of it.
  • When the fire strategy is issued, and which packages are held until it is

Guest room

A private space repeated hundreds of times, where every decision multiplies.

Wi-Fi in Guest room

Wireless is judged by the worst experience anyone has, not the average one.

Coordination questions:

  • What is the busiest realistic number of devices in this space at once, and are they people's phones or the building's own equipment?
  • Is the goal coverage or capacity? A corridor and a full banquet hall fail for completely different reasons.
  • Where can an access point physically be mounted, given the ceiling type and the finishes?
  • Who owns the guest network, its terms of use and the support call when it is slow?

Drawings needed:

  • Ceiling plan with access-point positions and mounting type
  • Cable route from each access point to the floor node
  • Any survey or predictive design the layout was based on

Open decisions:

  • How guest and staff traffic are kept apart
  • Whether a predictive design is accepted or a site survey is commissioned
Telephony in Guest room

Handset counts are inherited from the previous building and rarely re-examined.

Coordination questions:

  • Who actually needs a handset once everybody's mobile phone is counted?
  • Does anything here have to keep working when the internet does not?
  • Where do outside lines terminate, and who is the provider dealing with?

Drawings needed:

  • Outlet plan showing handset positions against the furniture layout
  • Riser diagram showing where voice joins the rest of the network

Open decisions:

  • Handset count, checked against how people actually work
  • Whether calls leave over a data connection or a local line
IPTV and in-room television in Guest room

In-room television is the system guests notice first and the one with the most rights attached to it.

Coordination questions:

  • Where do the channels come from — a local head-end, a broadcaster feed, or an internet service?
  • Does the screen also have to show something the guest brings with them, and what happens to that pairing afterwards?
  • Who holds the content rights, and does the plan match what has been licensed?
  • Does the guest's own device have to reach the screen, and what happens to that pairing at check-out?

Drawings needed:

  • Outlet plan per room type, coordinated with the interior layout
  • Head-end rack position and the riser route to the floors

Open decisions:

  • Channel line-up and the rights behind it
  • Whether the platform is run in-house or by a provider
Access control in Guest room

Doors get controlled late, after the ironmongery schedule is issued and the frames are ordered.

Coordination questions:

  • Which doors are controlled, and which are simply locked? The list is always shorter than the first conversation suggests.
  • Who issues and revokes credentials once the building is occupied, and on which system do they do it?
  • Does this door need to record who passed through it, or only to stop who should not?
  • Who owns the door — the technology package, the ironmongery package, or nobody yet?
  • Does the room lock talk to anything, or is it a standalone lock that is read at the door?

Drawings needed:

  • Door schedule naming every controlled leaf and its hardware
  • Door hardware detail per door type, coordinated with the ironmongery package
  • Cable route from each door back to its controller position

Open decisions:

  • Credential type, and whether people will actually carry it
  • Whether each door is monitored, controlled, or both
  • How controlled doors behave in an emergency — set by the project's fire strategy and the authority having jurisdiction. PROJECT-SPECIFIC VERIFICATION REQUIRED before hardware is ordered.
Automation and building controls in Guest room

Controls are specified as a product and experienced as a habit — the question is who changes a setting a year later.

Coordination questions:

  • What is actually being controlled here — lighting, temperature, blinds, or all three?
  • Who changes a setting after handover, and from what device?
  • Which of these controls does somebody in the room need to be able to override by hand?
  • Whose points list is this, and has the mechanical and electrical consultant agreed it?
  • What does the room do when nobody is in it, and how soon after they leave does it do it?

Drawings needed:

  • Lighting layout with switching and dimming zones
  • Control device positions, coordinated with the interior elevations
  • Points list agreed with the mechanical and electrical consultant

Open decisions:

  • Which protocol is used and who owns the head-end
  • Which scenes exist, and who is allowed to edit them
  • Whether the room state is shared with the property management system, and who owns that interface
Fire detection in Guest room

Fire detection is in scope for this space. Every requirement, threshold, coverage rule and compliance position belongs to the project's fire strategy and the authority having jurisdiction — this planner determines none of them. PROJECT-SPECIFIC VERIFICATION REQUIRED.

Coordination questions:

  • Who is the appointed fire consultant on this project, and has the fire strategy been issued?
  • Which authority having jurisdiction approves this building, and at what stage do they review it?
  • Has the fire scheme for this space been coordinated with the reflected ceiling plan and the finishes?
  • Which other packages are waiting on the fire scheme before they can be finalised?

Drawings needed:

  • The fire consultant's scheme drawing for this space
  • Reflected ceiling plan issued to the fire consultant for coordination
  • Containment coordination drawing showing the routes reserved for the fire scheme

Open decisions:

  • The fire scheme itself, issued by the appointed fire consultant and reviewed by the authority having jurisdiction. PROJECT-SPECIFIC VERIFICATION REQUIRED — this planner settles none of it.
  • When the fire strategy is issued, and which packages are held until it is

Guest floor corridor

A circulation route that mostly exists to serve the rooms off it.

Camera surveillance in Guest floor corridor

Cameras are asked for early and specified as a count, when what decides the design is what the picture has to prove.

Coordination questions:

  • Who watches the picture, and from where — a staffed position, a duty manager's phone, or nobody until something is reviewed afterwards?
  • How long does recorded footage need to be kept before it is overwritten, and who made that decision?
  • Where do people need to be identifiable, as opposed to simply seen? The two ask very different things of the same camera.
  • Who signs off camera positions against the privacy expectations of the people using the space?

Drawings needed:

  • Reflected ceiling plan with camera positions and cable drops
  • Containment route from each camera position back to the nearest node
  • Elevations for any camera on a wall, column or external face

Open decisions:

  • How long recordings are kept, and who is accountable for that decision
  • Whether recording sits in this building or somewhere else
  • Who holds the right to review and export footage after handover
Wi-Fi in Guest floor corridor

Wireless is judged by the worst experience anyone has, not the average one.

Coordination questions:

  • What is the busiest realistic number of devices in this space at once, and are they people's phones or the building's own equipment?
  • Is the goal coverage or capacity? A corridor and a full banquet hall fail for completely different reasons.
  • Where can an access point physically be mounted, given the ceiling type and the finishes?
  • Who owns the guest network, its terms of use and the support call when it is slow?
  • Is the corridor being covered for its own sake, or to reach the rooms off it? The answer changes the layout entirely.

Drawings needed:

  • Ceiling plan with access-point positions and mounting type
  • Cable route from each access point to the floor node
  • Any survey or predictive design the layout was based on

Open decisions:

  • How guest and staff traffic are kept apart
  • Whether a predictive design is accepted or a site survey is commissioned
Background music and paging in Guest floor corridor

Music and announcements are treated as a finishing item, after the ceiling is coordinated.

Coordination questions:

  • Is this background music, spoken announcements, or both — and who is expected to speak?
  • Which zones does an announcement reach, and which does it deliberately not reach?
  • How noisy is this space when it is full? That, not its floor area, decides the layout.
  • Who holds the right to play the music being planned in a commercial space?

Drawings needed:

  • Ceiling plan with loudspeaker positions coordinated against lighting and air terminals
  • Zone plan showing what is grouped with what
  • Amplifier and rack position with the cable route to each zone

Open decisions:

  • Where the zone boundaries actually fall
  • Where the music comes from and who is licensed for it
  • Who is allowed to make an announcement, and from where
Fire detection in Guest floor corridor

Fire detection is in scope for this space. Every requirement, threshold, coverage rule and compliance position belongs to the project's fire strategy and the authority having jurisdiction — this planner determines none of them. PROJECT-SPECIFIC VERIFICATION REQUIRED.

Coordination questions:

  • Who is the appointed fire consultant on this project, and has the fire strategy been issued?
  • Which authority having jurisdiction approves this building, and at what stage do they review it?
  • Has the fire scheme for this space been coordinated with the reflected ceiling plan and the finishes?
  • Which other packages are waiting on the fire scheme before they can be finalised?

Drawings needed:

  • The fire consultant's scheme drawing for this space
  • Reflected ceiling plan issued to the fire consultant for coordination
  • Containment coordination drawing showing the routes reserved for the fire scheme

Open decisions:

  • The fire scheme itself, issued by the appointed fire consultant and reviewed by the authority having jurisdiction. PROJECT-SPECIFIC VERIFICATION REQUIRED — this planner settles none of it.
  • When the fire strategy is issued, and which packages are held until it is

Banquet / function hall

A room that changes shape and purpose weekly and is sold on how it performs.

Sound reinforcement in Banquet / function hall

Sound is the system people complain about, and the one most constrained by decisions made by others.

Coordination questions:

  • Is this speech, music, or both? The same room asks different things of each.
  • How reverberant will this room be once the finishes are chosen, and who is holding that conversation with the architect?
  • Who operates it — a trained technician, or a duty manager with a wall plate?
  • How many microphones are open at once, and where are the people holding them standing?
  • Is the hall ever divided, and does the sound system have to divide with it — including the microphones?

Drawings needed:

  • Reflected ceiling plan or rigging plan with loudspeaker positions
  • Rack elevation and its position relative to the room
  • Cable route and containment for loudspeaker and microphone runs
  • Room finishes schedule — it decides the acoustics more than the equipment does

Open decisions:

  • Whether the room's acoustics are treated or worked around
  • How much of the system can be operated without a technician
  • How the system behaves in each division configuration, and who sets it
Projection in Banquet / function hall

Projection is settled by the room. Where the architecture is fixed first, the projector has to fit what is left.

Coordination questions:

  • How much ambient light is in the room when the projector is used, and can that light be controlled?
  • Where can the projector physically go, and does that position clear the sightlines and the ceiling services?
  • Is the screen fixed, or does it have to disappear when the room is used for something else?
  • Who reaches the projector for a filter or lamp change, and from what?
  • Does the image have to clear a raised stage, a head table and a chandelier at the same time?

Drawings needed:

  • Section showing throw distance, mounting height and seated sightlines
  • Reflected ceiling plan with the projector position and its service access
  • Screen elevation with the top and bottom of image against the back row

Open decisions:

  • Image size, set by the furthest seat rather than the wall
  • Lens and mounting position, agreed with the ceiling coordination
LED display wall in Banquet / function hall

A modular wall is a construction item wearing an AV label — it has weight, heat and a service strategy.

Coordination questions:

  • How close does the nearest viewer stand, and how far away is the furthest? That range decides the module choice.
  • What is actually going on the wall — video, text, or a live camera feed?
  • Can the back of the wall be reached for service, or does the front have to come off?
  • What is the wall made of, and who has confirmed it can carry the frame and the modules?
  • Is the wall permanent, or is it expected to be struck and re-hung between events?

Drawings needed:

  • Elevation with wall dimensions and the nearest and furthest viewing positions
  • Structural detail for the support frame and its fixings
  • Power supply and processing position with the signal route
  • Service-access detail, front or rear

Open decisions:

  • Module choice against the real viewing distances
  • Content resolution and who produces the content
  • How the wall is serviced, decided before it is built
Wi-Fi in Banquet / function hall

Wireless is judged by the worst experience anyone has, not the average one.

Coordination questions:

  • What is the busiest realistic number of devices in this space at once, and are they people's phones or the building's own equipment?
  • Is the goal coverage or capacity? A corridor and a full banquet hall fail for completely different reasons.
  • Where can an access point physically be mounted, given the ceiling type and the finishes?
  • Who owns the guest network, its terms of use and the support call when it is slow?

Drawings needed:

  • Ceiling plan with access-point positions and mounting type
  • Cable route from each access point to the floor node
  • Any survey or predictive design the layout was based on

Open decisions:

  • How guest and staff traffic are kept apart
  • Whether a predictive design is accepted or a site survey is commissioned
Background music and paging in Banquet / function hall

Music and announcements are treated as a finishing item, after the ceiling is coordinated.

Coordination questions:

  • Is this background music, spoken announcements, or both — and who is expected to speak?
  • Which zones does an announcement reach, and which does it deliberately not reach?
  • How noisy is this space when it is full? That, not its floor area, decides the layout.
  • Who holds the right to play the music being planned in a commercial space?

Drawings needed:

  • Ceiling plan with loudspeaker positions coordinated against lighting and air terminals
  • Zone plan showing what is grouped with what
  • Amplifier and rack position with the cable route to each zone

Open decisions:

  • Where the zone boundaries actually fall
  • Where the music comes from and who is licensed for it
  • Who is allowed to make an announcement, and from where
Automation and building controls in Banquet / function hall

Controls are specified as a product and experienced as a habit — the question is who changes a setting a year later.

Coordination questions:

  • What is actually being controlled here — lighting, temperature, blinds, or all three?
  • Who changes a setting after handover, and from what device?
  • Which of these controls does somebody in the room need to be able to override by hand?
  • Whose points list is this, and has the mechanical and electrical consultant agreed it?

Drawings needed:

  • Lighting layout with switching and dimming zones
  • Control device positions, coordinated with the interior elevations
  • Points list agreed with the mechanical and electrical consultant

Open decisions:

  • Which protocol is used and who owns the head-end
  • Which scenes exist, and who is allowed to edit them
Fire detection in Banquet / function hall

Fire detection is in scope for this space. Every requirement, threshold, coverage rule and compliance position belongs to the project's fire strategy and the authority having jurisdiction — this planner determines none of them. PROJECT-SPECIFIC VERIFICATION REQUIRED.

Coordination questions:

  • Who is the appointed fire consultant on this project, and has the fire strategy been issued?
  • Which authority having jurisdiction approves this building, and at what stage do they review it?
  • Has the fire scheme for this space been coordinated with the reflected ceiling plan and the finishes?
  • Which other packages are waiting on the fire scheme before they can be finalised?

Drawings needed:

  • The fire consultant's scheme drawing for this space
  • Reflected ceiling plan issued to the fire consultant for coordination
  • Containment coordination drawing showing the routes reserved for the fire scheme

Open decisions:

  • The fire scheme itself, issued by the appointed fire consultant and reviewed by the authority having jurisdiction. PROJECT-SPECIFIC VERIFICATION REQUIRED — this planner settles none of it.
  • When the fire strategy is issued, and which packages are held until it is

Meeting room

A room somebody has to be able to start a call in without calling for help.

Meeting-room and conferencing AV in Meeting room

Meeting rooms are the most-used technology in a working building and the most often disliked.

Coordination questions:

  • Which platform do people in this organisation actually join calls on today? The room is built around that, not the other way round.
  • Does the far end need to see the room, the presenter, or what is on the wall?
  • Who is expected to start a meeting without help, and how many actions is that?
  • Is the room used for calls, for presenting, or both — and when the two conflict, which one wins?
  • Is this room booked from a calendar, and does the room itself have to show that booking?

Drawings needed:

  • Furniture layout with seating positions marked
  • Elevation showing display height against the seated eye line
  • Table and floor-box positions with cable routes
  • Reflected ceiling plan coordinating microphones, loudspeakers, lighting and air terminals

Open decisions:

  • Which conferencing platform the room is built around
  • Whether the room is a single all-in-one device or separate components
  • Who supports the room after handover, and how a fault is reported
Wi-Fi in Meeting room

Wireless is judged by the worst experience anyone has, not the average one.

Coordination questions:

  • What is the busiest realistic number of devices in this space at once, and are they people's phones or the building's own equipment?
  • Is the goal coverage or capacity? A corridor and a full banquet hall fail for completely different reasons.
  • Where can an access point physically be mounted, given the ceiling type and the finishes?
  • Who owns the guest network, its terms of use and the support call when it is slow?

Drawings needed:

  • Ceiling plan with access-point positions and mounting type
  • Cable route from each access point to the floor node
  • Any survey or predictive design the layout was based on

Open decisions:

  • How guest and staff traffic are kept apart
  • Whether a predictive design is accepted or a site survey is commissioned
Projection in Meeting room

Projection is settled by the room. Where the architecture is fixed first, the projector has to fit what is left.

Coordination questions:

  • How much ambient light is in the room when the projector is used, and can that light be controlled?
  • Where can the projector physically go, and does that position clear the sightlines and the ceiling services?
  • Is the screen fixed, or does it have to disappear when the room is used for something else?
  • Who reaches the projector for a filter or lamp change, and from what?

Drawings needed:

  • Section showing throw distance, mounting height and seated sightlines
  • Reflected ceiling plan with the projector position and its service access
  • Screen elevation with the top and bottom of image against the back row

Open decisions:

  • Image size, set by the furthest seat rather than the wall
  • Lens and mounting position, agreed with the ceiling coordination
Sound reinforcement in Meeting room

Sound is the system people complain about, and the one most constrained by decisions made by others.

Coordination questions:

  • Is this speech, music, or both? The same room asks different things of each.
  • How reverberant will this room be once the finishes are chosen, and who is holding that conversation with the architect?
  • Who operates it — a trained technician, or a duty manager with a wall plate?
  • How many microphones are open at once, and where are the people holding them standing?

Drawings needed:

  • Reflected ceiling plan or rigging plan with loudspeaker positions
  • Rack elevation and its position relative to the room
  • Cable route and containment for loudspeaker and microphone runs
  • Room finishes schedule — it decides the acoustics more than the equipment does

Open decisions:

  • Whether the room's acoustics are treated or worked around
  • How much of the system can be operated without a technician

Restaurant / F&B

A room whose noise level is part of the experience and part of the problem.

Background music and paging in Restaurant / F&B

Music and announcements are treated as a finishing item, after the ceiling is coordinated.

Coordination questions:

  • Is this background music, spoken announcements, or both — and who is expected to speak?
  • Which zones does an announcement reach, and which does it deliberately not reach?
  • How noisy is this space when it is full? That, not its floor area, decides the layout.
  • Who holds the right to play the music being planned in a commercial space?
  • Does the kitchen hear the same thing as the dining room, and should it?

Drawings needed:

  • Ceiling plan with loudspeaker positions coordinated against lighting and air terminals
  • Zone plan showing what is grouped with what
  • Amplifier and rack position with the cable route to each zone

Open decisions:

  • Where the zone boundaries actually fall
  • Where the music comes from and who is licensed for it
  • Who is allowed to make an announcement, and from where
Wi-Fi in Restaurant / F&B

Wireless is judged by the worst experience anyone has, not the average one.

Coordination questions:

  • What is the busiest realistic number of devices in this space at once, and are they people's phones or the building's own equipment?
  • Is the goal coverage or capacity? A corridor and a full banquet hall fail for completely different reasons.
  • Where can an access point physically be mounted, given the ceiling type and the finishes?
  • Who owns the guest network, its terms of use and the support call when it is slow?

Drawings needed:

  • Ceiling plan with access-point positions and mounting type
  • Cable route from each access point to the floor node
  • Any survey or predictive design the layout was based on

Open decisions:

  • How guest and staff traffic are kept apart
  • Whether a predictive design is accepted or a site survey is commissioned
Camera surveillance in Restaurant / F&B

Cameras are asked for early and specified as a count, when what decides the design is what the picture has to prove.

Coordination questions:

  • Who watches the picture, and from where — a staffed position, a duty manager's phone, or nobody until something is reviewed afterwards?
  • How long does recorded footage need to be kept before it is overwritten, and who made that decision?
  • Where do people need to be identifiable, as opposed to simply seen? The two ask very different things of the same camera.
  • Who signs off camera positions against the privacy expectations of the people using the space?

Drawings needed:

  • Reflected ceiling plan with camera positions and cable drops
  • Containment route from each camera position back to the nearest node
  • Elevations for any camera on a wall, column or external face

Open decisions:

  • How long recordings are kept, and who is accountable for that decision
  • Whether recording sits in this building or somewhere else
  • Who holds the right to review and export footage after handover
Digital signage in Restaurant / F&B

Screens are easy to buy and hard to keep current; the content plan is the part that is usually missing.

Coordination questions:

  • Who writes the content, and how often does it actually change?
  • Is the screen read while walking past or while standing still? That sets the size before any product is chosen.
  • What is behind the screen — is there power and a cable route there, or is this a surface-mounted afterthought?

Drawings needed:

  • Elevation with screen size and mounting height
  • Power and data outlet positions behind each screen
  • Structural detail wherever a screen hangs on a non-structural finish

Open decisions:

  • Who owns the content after handover
  • Screen orientation and size, agreed with the interior design
Fire detection in Restaurant / F&B

Fire detection is in scope for this space. Every requirement, threshold, coverage rule and compliance position belongs to the project's fire strategy and the authority having jurisdiction — this planner determines none of them. PROJECT-SPECIFIC VERIFICATION REQUIRED.

Coordination questions:

  • Who is the appointed fire consultant on this project, and has the fire strategy been issued?
  • Which authority having jurisdiction approves this building, and at what stage do they review it?
  • Has the fire scheme for this space been coordinated with the reflected ceiling plan and the finishes?
  • Which other packages are waiting on the fire scheme before they can be finalised?

Drawings needed:

  • The fire consultant's scheme drawing for this space
  • Reflected ceiling plan issued to the fire consultant for coordination
  • Containment coordination drawing showing the routes reserved for the fire scheme

Open decisions:

  • The fire scheme itself, issued by the appointed fire consultant and reviewed by the authority having jurisdiction. PROJECT-SPECIFIC VERIFICATION REQUIRED — this planner settles none of it.
  • When the fire strategy is issued, and which packages are held until it is

Back office / administration

Where the building is actually run from, and where the staff network lives.

Camera surveillance in Back office / administration

Cameras are asked for early and specified as a count, when what decides the design is what the picture has to prove.

Coordination questions:

  • Who watches the picture, and from where — a staffed position, a duty manager's phone, or nobody until something is reviewed afterwards?
  • How long does recorded footage need to be kept before it is overwritten, and who made that decision?
  • Where do people need to be identifiable, as opposed to simply seen? The two ask very different things of the same camera.
  • Who signs off camera positions against the privacy expectations of the people using the space?

Drawings needed:

  • Reflected ceiling plan with camera positions and cable drops
  • Containment route from each camera position back to the nearest node
  • Elevations for any camera on a wall, column or external face

Open decisions:

  • How long recordings are kept, and who is accountable for that decision
  • Whether recording sits in this building or somewhere else
  • Who holds the right to review and export footage after handover
Access control in Back office / administration

Doors get controlled late, after the ironmongery schedule is issued and the frames are ordered.

Coordination questions:

  • Which doors are controlled, and which are simply locked? The list is always shorter than the first conversation suggests.
  • Who issues and revokes credentials once the building is occupied, and on which system do they do it?
  • Does this door need to record who passed through it, or only to stop who should not?
  • Who owns the door — the technology package, the ironmongery package, or nobody yet?

Drawings needed:

  • Door schedule naming every controlled leaf and its hardware
  • Door hardware detail per door type, coordinated with the ironmongery package
  • Cable route from each door back to its controller position

Open decisions:

  • Credential type, and whether people will actually carry it
  • Whether each door is monitored, controlled, or both
  • How controlled doors behave in an emergency — set by the project's fire strategy and the authority having jurisdiction. PROJECT-SPECIFIC VERIFICATION REQUIRED before hardware is ordered.
Wi-Fi in Back office / administration

Wireless is judged by the worst experience anyone has, not the average one.

Coordination questions:

  • What is the busiest realistic number of devices in this space at once, and are they people's phones or the building's own equipment?
  • Is the goal coverage or capacity? A corridor and a full banquet hall fail for completely different reasons.
  • Where can an access point physically be mounted, given the ceiling type and the finishes?
  • Who owns the guest network, its terms of use and the support call when it is slow?

Drawings needed:

  • Ceiling plan with access-point positions and mounting type
  • Cable route from each access point to the floor node
  • Any survey or predictive design the layout was based on

Open decisions:

  • How guest and staff traffic are kept apart
  • Whether a predictive design is accepted or a site survey is commissioned
Telephony in Back office / administration

Handset counts are inherited from the previous building and rarely re-examined.

Coordination questions:

  • Who actually needs a handset once everybody's mobile phone is counted?
  • Does anything here have to keep working when the internet does not?
  • Where do outside lines terminate, and who is the provider dealing with?

Drawings needed:

  • Outlet plan showing handset positions against the furniture layout
  • Riser diagram showing where voice joins the rest of the network

Open decisions:

  • Handset count, checked against how people actually work
  • Whether calls leave over a data connection or a local line
Fire detection in Back office / administration

Fire detection is in scope for this space. Every requirement, threshold, coverage rule and compliance position belongs to the project's fire strategy and the authority having jurisdiction — this planner determines none of them. PROJECT-SPECIFIC VERIFICATION REQUIRED.

Coordination questions:

  • Who is the appointed fire consultant on this project, and has the fire strategy been issued?
  • Which authority having jurisdiction approves this building, and at what stage do they review it?
  • Has the fire scheme for this space been coordinated with the reflected ceiling plan and the finishes?
  • Which other packages are waiting on the fire scheme before they can be finalised?

Drawings needed:

  • The fire consultant's scheme drawing for this space
  • Reflected ceiling plan issued to the fire consultant for coordination
  • Containment coordination drawing showing the routes reserved for the fire scheme

Open decisions:

  • The fire scheme itself, issued by the appointed fire consultant and reviewed by the authority having jurisdiction. PROJECT-SPECIFIC VERIFICATION REQUIRED — this planner settles none of it.
  • When the fire strategy is issued, and which packages are held until it is

Server / equipment room

The room every other space quietly depends on, usually sized before anyone counted what goes in it.

Rack and equipment room in Server / equipment room

The equipment room is sized before anybody has counted what goes in it, and then everything goes in it.

Coordination questions:

  • What has to live in this room, and what has been assumed will live somewhere else?
  • How does heat leave this room, and who is designing that?
  • Who has access to this room, and who else believes they have access?
  • Is there space to open a cabinet door and stand behind it while working?
  • Which packages have already assumed space in this room without telling the person sizing it?

Drawings needed:

  • Room layout with cabinet positions and maintenance clearances
  • Rack elevations showing what is in each cabinet
  • Power and earthing arrangement
  • Containment entry points and the tray above the cabinets

Open decisions:

  • Cabinet count and how much spare capacity is being built in
  • How the room is kept within the equipment's operating range
Uninterruptible power in Server / equipment room

Protection is bought for a room and needed for a list of loads, and the two are rarely the same thing.

Coordination questions:

  • Which of these systems actually has to keep running through an interruption, and for how long?
  • What happens at the end of that time — does a generator take over, or does everything stop?
  • Where do the batteries live, how warm does that space get, and who replaces them?

Drawings needed:

  • Single-line diagram identifying the protected loads
  • Battery position with access and ventilation shown

Open decisions:

  • Which loads are protected and which are deliberately not
  • The runtime being designed to, and what is meant to happen afterwards
Network switching in Server / equipment room

Every other system assumes a port exists. The port count is the sum of assumptions nobody added up.

Coordination questions:

  • How many ports does this floor need on day one, and how many were assumed for later?
  • Which devices are powered by the switch rather than from a local supply?
  • Where does the uplink go, and what stops working if it is down?

Drawings needed:

  • Network topology and riser diagram
  • Node position plan with the area each node serves
  • Port schedule reconciled against the outlet count

Open decisions:

  • The power budget for devices fed from the switch
  • Whether this is one network estate or several kept apart
Structured cabling in Server / equipment room

The cable plant outlives two or three generations of the equipment on it, and re-pulling it later is the expensive part.

Coordination questions:

  • How many outlets at each position, and who counted them?
  • What is the longest run in the building, measured along the actual route rather than across the plan?
  • Who owns the labelling scheme, and does it match the room numbering the architect uses?
  • How much spare capacity is being left in the containment, and who decided that number?

Drawings needed:

  • Outlet plan coordinated with the furniture layout
  • Containment route with the fill it is being designed to
  • Riser diagram
  • Labelling schedule tied to the architect's room numbering

Open decisions:

  • Cable category, chosen against how long the plant has to last
  • Spare capacity in containment and in the panels
Access control in Server / equipment room

Doors get controlled late, after the ironmongery schedule is issued and the frames are ordered.

Coordination questions:

  • Which doors are controlled, and which are simply locked? The list is always shorter than the first conversation suggests.
  • Who issues and revokes credentials once the building is occupied, and on which system do they do it?
  • Does this door need to record who passed through it, or only to stop who should not?
  • Who owns the door — the technology package, the ironmongery package, or nobody yet?
  • Who is on the access list, who reviews that list, and how often?

Drawings needed:

  • Door schedule naming every controlled leaf and its hardware
  • Door hardware detail per door type, coordinated with the ironmongery package
  • Cable route from each door back to its controller position

Open decisions:

  • Credential type, and whether people will actually carry it
  • Whether each door is monitored, controlled, or both
  • How controlled doors behave in an emergency — set by the project's fire strategy and the authority having jurisdiction. PROJECT-SPECIFIC VERIFICATION REQUIRED before hardware is ordered.
Camera surveillance in Server / equipment room

Cameras are asked for early and specified as a count, when what decides the design is what the picture has to prove.

Coordination questions:

  • Who watches the picture, and from where — a staffed position, a duty manager's phone, or nobody until something is reviewed afterwards?
  • How long does recorded footage need to be kept before it is overwritten, and who made that decision?
  • Where do people need to be identifiable, as opposed to simply seen? The two ask very different things of the same camera.
  • Who signs off camera positions against the privacy expectations of the people using the space?

Drawings needed:

  • Reflected ceiling plan with camera positions and cable drops
  • Containment route from each camera position back to the nearest node
  • Elevations for any camera on a wall, column or external face

Open decisions:

  • How long recordings are kept, and who is accountable for that decision
  • Whether recording sits in this building or somewhere else
  • Who holds the right to review and export footage after handover
Automation and building controls in Server / equipment room

Controls are specified as a product and experienced as a habit — the question is who changes a setting a year later.

Coordination questions:

  • What is actually being controlled here — lighting, temperature, blinds, or all three?
  • Who changes a setting after handover, and from what device?
  • Which of these controls does somebody in the room need to be able to override by hand?
  • Whose points list is this, and has the mechanical and electrical consultant agreed it?

Drawings needed:

  • Lighting layout with switching and dimming zones
  • Control device positions, coordinated with the interior elevations
  • Points list agreed with the mechanical and electrical consultant

Open decisions:

  • Which protocol is used and who owns the head-end
  • Which scenes exist, and who is allowed to edit them
Fire detection in Server / equipment room

Fire detection is in scope for this space. Every requirement, threshold, coverage rule and compliance position belongs to the project's fire strategy and the authority having jurisdiction — this planner determines none of them. PROJECT-SPECIFIC VERIFICATION REQUIRED.

Coordination questions:

  • Who is the appointed fire consultant on this project, and has the fire strategy been issued?
  • Which authority having jurisdiction approves this building, and at what stage do they review it?
  • Has the fire scheme for this space been coordinated with the reflected ceiling plan and the finishes?
  • Which other packages are waiting on the fire scheme before they can be finalised?

Drawings needed:

  • The fire consultant's scheme drawing for this space
  • Reflected ceiling plan issued to the fire consultant for coordination
  • Containment coordination drawing showing the routes reserved for the fire scheme

Open decisions:

  • The fire scheme itself, issued by the appointed fire consultant and reviewed by the authority having jurisdiction. PROJECT-SPECIFIC VERIFICATION REQUIRED — this planner settles none of it.
  • When the fire strategy is issued, and which packages are held until it is

Parking

A large, poorly lit area with vehicles in it and a barrier at each end.

Camera surveillance in Parking

Cameras are asked for early and specified as a count, when what decides the design is what the picture has to prove.

Coordination questions:

  • Who watches the picture, and from where — a staffed position, a duty manager's phone, or nobody until something is reviewed afterwards?
  • How long does recorded footage need to be kept before it is overwritten, and who made that decision?
  • Where do people need to be identifiable, as opposed to simply seen? The two ask very different things of the same camera.
  • Who signs off camera positions against the privacy expectations of the people using the space?
  • Are number plates expected to be readable, and at which point — the entry lane, or anywhere in the aisles?

Drawings needed:

  • Reflected ceiling plan with camera positions and cable drops
  • Containment route from each camera position back to the nearest node
  • Elevations for any camera on a wall, column or external face

Open decisions:

  • How long recordings are kept, and who is accountable for that decision
  • Whether recording sits in this building or somewhere else
  • Who holds the right to review and export footage after handover
Access control in Parking

Doors get controlled late, after the ironmongery schedule is issued and the frames are ordered.

Coordination questions:

  • Which doors are controlled, and which are simply locked? The list is always shorter than the first conversation suggests.
  • Who issues and revokes credentials once the building is occupied, and on which system do they do it?
  • Does this door need to record who passed through it, or only to stop who should not?
  • Who owns the door — the technology package, the ironmongery package, or nobody yet?

Drawings needed:

  • Door schedule naming every controlled leaf and its hardware
  • Door hardware detail per door type, coordinated with the ironmongery package
  • Cable route from each door back to its controller position

Open decisions:

  • Credential type, and whether people will actually carry it
  • Whether each door is monitored, controlled, or both
  • How controlled doors behave in an emergency — set by the project's fire strategy and the authority having jurisdiction. PROJECT-SPECIFIC VERIFICATION REQUIRED before hardware is ordered.
Automation and building controls in Parking

Controls are specified as a product and experienced as a habit — the question is who changes a setting a year later.

Coordination questions:

  • What is actually being controlled here — lighting, temperature, blinds, or all three?
  • Who changes a setting after handover, and from what device?
  • Which of these controls does somebody in the room need to be able to override by hand?
  • Whose points list is this, and has the mechanical and electrical consultant agreed it?

Drawings needed:

  • Lighting layout with switching and dimming zones
  • Control device positions, coordinated with the interior elevations
  • Points list agreed with the mechanical and electrical consultant

Open decisions:

  • Which protocol is used and who owns the head-end
  • Which scenes exist, and who is allowed to edit them

External areas and perimeter

Everything outside the walls, where weather and night-time lighting decide what works.

Camera surveillance in External areas and perimeter

Cameras are asked for early and specified as a count, when what decides the design is what the picture has to prove.

Coordination questions:

  • Who watches the picture, and from where — a staffed position, a duty manager's phone, or nobody until something is reviewed afterwards?
  • How long does recorded footage need to be kept before it is overwritten, and who made that decision?
  • Where do people need to be identifiable, as opposed to simply seen? The two ask very different things of the same camera.
  • Who signs off camera positions against the privacy expectations of the people using the space?
  • What lighting exists at night, and was it designed by anyone who knew there would be cameras?

Drawings needed:

  • Reflected ceiling plan with camera positions and cable drops
  • Containment route from each camera position back to the nearest node
  • Elevations for any camera on a wall, column or external face

Open decisions:

  • How long recordings are kept, and who is accountable for that decision
  • Whether recording sits in this building or somewhere else
  • Who holds the right to review and export footage after handover
Access control in External areas and perimeter

Doors get controlled late, after the ironmongery schedule is issued and the frames are ordered.

Coordination questions:

  • Which doors are controlled, and which are simply locked? The list is always shorter than the first conversation suggests.
  • Who issues and revokes credentials once the building is occupied, and on which system do they do it?
  • Does this door need to record who passed through it, or only to stop who should not?
  • Who owns the door — the technology package, the ironmongery package, or nobody yet?

Drawings needed:

  • Door schedule naming every controlled leaf and its hardware
  • Door hardware detail per door type, coordinated with the ironmongery package
  • Cable route from each door back to its controller position

Open decisions:

  • Credential type, and whether people will actually carry it
  • Whether each door is monitored, controlled, or both
  • How controlled doors behave in an emergency — set by the project's fire strategy and the authority having jurisdiction. PROJECT-SPECIFIC VERIFICATION REQUIRED before hardware is ordered.
Background music and paging in External areas and perimeter

Music and announcements are treated as a finishing item, after the ceiling is coordinated.

Coordination questions:

  • Is this background music, spoken announcements, or both — and who is expected to speak?
  • Which zones does an announcement reach, and which does it deliberately not reach?
  • How noisy is this space when it is full? That, not its floor area, decides the layout.
  • Who holds the right to play the music being planned in a commercial space?

Drawings needed:

  • Ceiling plan with loudspeaker positions coordinated against lighting and air terminals
  • Zone plan showing what is grouped with what
  • Amplifier and rack position with the cable route to each zone

Open decisions:

  • Where the zone boundaries actually fall
  • Where the music comes from and who is licensed for it
  • Who is allowed to make an announcement, and from where
Wi-Fi in External areas and perimeter

Wireless is judged by the worst experience anyone has, not the average one.

Coordination questions:

  • What is the busiest realistic number of devices in this space at once, and are they people's phones or the building's own equipment?
  • Is the goal coverage or capacity? A corridor and a full banquet hall fail for completely different reasons.
  • Where can an access point physically be mounted, given the ceiling type and the finishes?
  • Who owns the guest network, its terms of use and the support call when it is slow?

Drawings needed:

  • Ceiling plan with access-point positions and mounting type
  • Cable route from each access point to the floor node
  • Any survey or predictive design the layout was based on

Open decisions:

  • How guest and staff traffic are kept apart
  • Whether a predictive design is accepted or a site survey is commissioned

How these systems depend on each other

  • Camera surveillance depends on Network switching Cannot work without it. An IP camera is a network device. With no switch port and no address it produces no picture at all, anywhere.
  • Camera surveillance depends on Structured cabling Cannot work without it. Every camera position is a cable run back to a node, and that run is drawn with the rest of the cable plant or it is improvised on site.
  • Camera surveillance depends on Electrical supply Cannot work without it. Whether it comes down the data cable or from a local supply, the camera has to be powered by something somebody has drawn.
  • Camera surveillance depends on Power over Ethernet Usual, not universal. Most cameras take power from the same cable that carries the picture, which is why the camera count lands on the switch budget. Local low-voltage supplies are still used where there is no suitable port.
  • Camera surveillance depends on Recording and retention Usual, not universal. Live-only monitoring exists, but nearly every installation records. How long footage is kept is the decision that sizes the platform, and it is a business decision before it is an engineering one.
  • Camera surveillance depends on Rack and equipment room Usual, not universal. The recorder, the switch and the licences land in a cabinet. Small estates run from a wall-mounted enclosure instead, which is a legitimate answer and a different one.
  • Camera surveillance depends on Uninterruptible power Only in certain cases. Only where the client expects to keep seeing and recording through a mains interruption. Cameras, the switch feeding them and the recorder are three separate loads. Protecting one and not the others produces a system that stops anyway.
  • Camera surveillance depends on Containment and cable pathways Cannot work without it. Camera cabling needs a route. Where that route was drawn for the data cabling alone, the cameras arrive as an unplanned addition to a full tray.
  • Access control depends on Door hardware Cannot work without it. The reader and the controller only make a decision. The lock, the closer, the frame and the leaf are what physically hold or release the door, and they are usually somebody else's package.
  • Access control depends on Structured cabling Cannot work without it. Each controlled door is a cable run to a controller, and door positions move later in the design than cable schedules like.
  • Access control depends on Electrical supply Cannot work without it. Controllers, readers and locks are all powered, and the lock is often the load nobody counted.
  • Access control depends on Network switching Usual, not universal. Networked controllers are the usual arrangement because they let credentials be issued and revoked centrally. Standalone controllers on a local bus are still specified on small door counts.
  • Access control depends on Containment and cable pathways Cannot work without it. Door cabling runs above ceilings and down frames, and the route has to exist before the frames are set.
  • Access control depends on Uninterruptible power Only in certain cases. Only where the client needs controlled doors to keep behaving predictably through a mains interruption. Without a supply, controllers stop making decisions and the doors sit in whatever state their hardware defaults to.
  • Access control depends on Fire detection Expert-held. What a controlled door on an escape route does in an emergency is set by the project's fire strategy and the authority having jurisdiction. It is not derived from a door schedule and this planner does not determine it. PROJECT-SPECIFIC VERIFICATION REQUIRED before door hardware is specified or ordered.
  • Wi-Fi depends on Structured cabling Cannot work without it. An access point is a wired device with a radio on the end. Every one of them is a cable run to a ceiling position that has to be agreed with the architect.
  • Wi-Fi depends on Network switching Cannot work without it. Access points terminate on switch ports. The port count and the wireless design are the same conversation, held twice on most projects.
  • Wi-Fi depends on Power over Ethernet Usual, not universal. Access points are normally powered by the switch, which is what turns a coverage plan into a power budget. Local injectors are used where a suitable switch is not present.
  • Wi-Fi depends on Electrical supply Cannot work without it. The power arrives at the access point one way or another, and the switch that supplies it is itself a load in the equipment room.
  • Wi-Fi depends on Rack and equipment room Usual, not universal. The switching and any controller sit in a cabinet on the floor or in the equipment room. Small deployments run from cloud-managed access points with no local controller at all.
  • Wi-Fi depends on Internet or wide-area uplink Only in certain cases. Only where the wireless network is expected to carry internet or cloud traffic rather than local traffic only. Wireless coverage and internet access are different things, and a guest expecting the second will call the first broken.
  • Wi-Fi depends on Mounting and fixing Cannot work without it. The ceiling finish decides what an access point can be fixed to, and a plasterboard raft, an exposed soffit and a stretched fabric ceiling are three different answers.
  • Telephony depends on Network switching Cannot work without it. Voice handsets are network devices on the same switches as everything else, which is convenient until the network is being planned without them counted.
  • Telephony depends on Structured cabling Cannot work without it. Each handset position is an outlet, and handset positions are decided by furniture layouts that are often not final when the cabling is.
  • Telephony depends on Power over Ethernet Usual, not universal. Handsets are usually powered from the switch so a desk needs no extra adaptor. Some deployments use local supplies instead.
  • Telephony depends on Internet or wide-area uplink Only in certain cases. Only where outside calls are carried over a data connection rather than a local line. If calls leave the building over a data path, then the state of that path is the state of the phone system.
  • Telephony depends on Uninterruptible power Only in certain cases. Only where voice has to stay available through a mains interruption. An IP handset is only as available as the switch it hangs off and the platform behind it.
  • Telephony depends on Rack and equipment room Usual, not universal. Gateways and any on-premises platform live in a cabinet. Fully hosted deployments keep almost nothing on site.
  • Background music and paging depends on Loudspeakers Cannot work without it. The loudspeaker layout is the system. Where the ceiling grid, the lighting and the loudspeakers are drawn separately, one of them moves on site.
  • Background music and paging depends on Amplification Usual, not universal. Distributed loudspeakers are usually passive and driven from a central amplifier. Powered loudspeakers on a networked source are a real alternative on smaller layouts.
  • Background music and paging depends on Electrical supply Cannot work without it. Amplification is a real electrical load in the rack position, and it is often sized after the electrical drawings are issued.
  • Background music and paging depends on Containment and cable pathways Cannot work without it. Loudspeaker cabling runs the length of every zone and needs its own route, kept apart from cabling it should not share a containment with.
  • Background music and paging depends on Rack and equipment room Usual, not universal. Amplification and sources land in a cabinet, and amplification is one of the warmer things in it.
  • Background music and paging depends on Audio processing Sometimes specified. Zone processing helps where zones differ a lot in size or noise. A single-zone music system does not need it and is not improved by it.
  • Background music and paging depends on Content and source Usual, not universal. Music needs something to play, and who holds the right to play it in a commercial space is a question the client answers rather than the installer. An announcement-only system is the real exception: its source is the microphone at the paging station, and there is no programme material to license.
  • Digital signage depends on Display or screen Cannot work without it. The screen is the system, and whether it is read while walking past or while standing still changes the size before the model.
  • Digital signage depends on Content and source Cannot work without it. A screen with nobody appointed to update it is a screen showing last season's message. Who writes the content is decided at design stage or it is not decided at all.
  • Digital signage depends on Mounting and fixing Cannot work without it. The screen hangs on something, and a feature wall built from plasterboard on a light frame is the classic late discovery.
  • Digital signage depends on Electrical supply Cannot work without it. Power behind the screen, at the height the screen is actually at, is a coordination item and not an assumption.
  • Digital signage depends on Network switching Usual, not universal. Screens are normally updated over the network. Players that run from local storage exist and are still specified where no network reaches.
  • Digital signage depends on Structured cabling Usual, not universal. Where the screen is updated over the network it needs an outlet behind it, which is a different position from the power outlet only by accident.
  • Fire detection depends on Electrical supply Cannot work without it. Detection equipment is powered equipment and appears in the electrical coordination like anything else. Nothing about how it is supplied is settled here.
  • Fire detection depends on Containment and cable pathways Cannot work without it. Detection cabling needs a route, and the route is coordinated with the other services early so it is not competing for the same tray later. What that cabling must be, and how it is segregated, comes from the fire scheme.
  • Fire detection depends on Automation and building controls Expert-held. Whether detection signals do anything to building plant is set by the project's fire strategy and the authority having jurisdiction. It is not derived from a controls points list and this planner does not determine it. PROJECT-SPECIFIC VERIFICATION REQUIRED.
  • IPTV and in-room television depends on Network switching Cannot work without it. Television over the building network is network traffic, and it behaves differently from everything else on the switch.
  • IPTV and in-room television depends on Structured cabling Cannot work without it. Every screen position is an outlet, and screen positions in rooms are set by the interior designer rather than the cable schedule.
  • IPTV and in-room television depends on Content and source Cannot work without it. Channels come from somewhere, and the rights to show them in a commercial building belong to the client.
  • IPTV and in-room television depends on Display or screen Cannot work without it. The screen is what the guest actually experiences, and it is often chosen for the room before anyone asks what will drive it.
  • IPTV and in-room television depends on Internet or wide-area uplink Only in certain cases. Only where channels or streaming services are carried from outside rather than from a local head-end. Where the channels come from outside the building, the outside path is part of the television system.
  • IPTV and in-room television depends on Rack and equipment room Usual, not universal. The head-end and its licensing sit in a cabinet, usually the same one everything else is competing for.
  • Automation and building controls depends on Electrical supply Cannot work without it. Controls sit between the supply and the thing being controlled, so the electrical design and the controls design are the same drawing seen twice.
  • Automation and building controls depends on Containment and cable pathways Cannot work without it. Field devices are distributed everywhere by definition, and their routes are the ones most often assumed to be somebody else's.
  • Automation and building controls depends on Network switching Usual, not universal. Head-ends and modern controllers normally sit on the network. Field buses that never touch it are still widely used.
  • Automation and building controls depends on Rack and equipment room Usual, not universal. The head-end and its interfaces need a home, and it is usually the same cabinet everything else wants.
  • Automation and building controls depends on Structured cabling Only in certain cases. Only where the chosen controllers use the building's data cabling rather than a dedicated field bus. Some controls ride the data cabling and some run on their own bus, and the two are budgeted by different people.
  • Sound reinforcement depends on Loudspeakers Cannot work without it. Coverage is decided by where loudspeakers can physically go, which is a ceiling and rigging conversation with the architect.
  • Sound reinforcement depends on Amplification Usual, not universal. Most loudspeakers are passive and need external amplification. Active loudspeakers carry theirs inside and need none, which changes the rack and the electrical load.
  • Sound reinforcement depends on Audio processing Only in certain cases. Only where the system has several zones, several live microphones, or delay and equalisation to manage across a difficult room. Processing is not automatic. A single-source, single-zone system does not need it and is not made better by adding it.
  • Sound reinforcement depends on Microphones Usual, not universal. Speech reinforcement needs microphones and their positions constrain everything else. A programme-playback-only system needs none.
  • Sound reinforcement depends on Containment and cable pathways Cannot work without it. Loudspeaker and microphone cabling needs routes that were drawn for it, and rigging positions above a hall are decided with the structural engineer.
  • Sound reinforcement depends on Electrical supply Cannot work without it. Amplification is a genuine load at the rack position, and how it is earthed decides whether the system hums.
  • Sound reinforcement depends on Rack and equipment room Usual, not universal. Amplification, processing and sources land in a cabinet near the room they serve. Small active systems can live behind a panel instead.
  • Sound reinforcement depends on Room geometry Cannot work without it. How reverberant a room is depends on its shape and its finishes, and both are settled by others. A system designed before the finishes are known is designed against a guess.
  • Projection depends on Projection surface Cannot work without it. The surface is half the system, and whether it stays visible when unused is an interior decision with a technical consequence.
  • Projection depends on Room geometry Cannot work without it. Throw distance, ceiling height and the seated sightline decide the lens and the mounting position before any product is chosen. Where the architecture is fixed first, projection has to fit it.
  • Projection depends on Mounting and fixing Cannot work without it. The projector hangs from structure or a bracket that has to be coordinated with the ceiling, the lighting and access for a lamp or filter change.
  • Projection depends on Signal transport Cannot work without it. The projector is rarely near the source, so the run between them is a design item rather than a cable off a shelf.
  • Projection depends on Electrical supply Cannot work without it. A supply at the projector position, which is usually a ceiling position with no other reason for a socket to be there.
  • Projection depends on Control and user interface Usual, not universal. Most rooms want the projector, the screen and the lighting to move together on one press. A simple room can be operated with separate controls.
  • LED display wall depends on Electrical supply Cannot work without it. A modular wall is a substantial and continuous electrical load, and it is one of the few AV items that genuinely changes the electrical design.
  • LED display wall depends on Video processing Cannot work without it. A wall is a grid of modules, not a screen. Something has to turn an incoming picture into the pixel map that drives them.
  • LED display wall depends on Signal transport Cannot work without it. The picture has to reach the processor from wherever it is made, and that route is usually longer than anyone assumed at concept stage.
  • LED display wall depends on Content and source Cannot work without it. A wall is built at one pixel geometry and content is made at another. Agreeing that early is the difference between a sharp wall and a stretched one.
  • LED display wall depends on Structure and service access Cannot work without it. The frame carries real weight and has to be fixed to real structure. Whether the wall is serviced from the front or the back has to be settled before it is built, not after.
  • LED display wall depends on Network switching Usual, not universal. Control and monitoring normally sit on the network so the wall can be driven and checked remotely. Locally driven walls exist.
  • LED display wall depends on Uninterruptible power Only in certain cases. Only where the wall carries live content that must not drop during an event. A wall that goes dark mid-event is a different failure from a wall that goes dark overnight.
  • Meeting-room and conferencing AV depends on Display or screen Cannot work without it. There is nothing to look at otherwise. The size is set by the distance from the furthest seat, which means the furniture layout has to be settled first.
  • Meeting-room and conferencing AV depends on Microphones Cannot work without it. A call the far end cannot hear is not a call. Microphone placement is the single biggest determinant of whether people are willing to use the room.
  • Meeting-room and conferencing AV depends on Loudspeakers Cannot work without it. The room has to hear the far end, and the ceiling that carries the loudspeakers is coordinated with lighting, detection devices and air terminals.
  • Meeting-room and conferencing AV depends on Room camera Cannot work without it. The far end has to see the room, and where the camera can go is a furniture and sightline question before it is a product question.
  • Meeting-room and conferencing AV depends on Conferencing platform Cannot work without it. The room is built around whichever service the organisation actually runs meetings on today. Choosing hardware before that is settled is how rooms end up unused.
  • Meeting-room and conferencing AV depends on Network switching Cannot work without it. The room joins the call over the network, and a room codec is a device somebody has to have counted on the switch.
  • Meeting-room and conferencing AV depends on Structured cabling Cannot work without it. Table boxes, floor boxes and the display position all need cable routes agreed before the slab is poured or the joinery is made.
  • Meeting-room and conferencing AV depends on Electrical supply Cannot work without it. Power at the display, at the table and at the rack position. The table one is the one that gets left off the electrical drawing.
  • Meeting-room and conferencing AV depends on Control and user interface Usual, not universal. Most rooms want one obvious way to start a meeting. A small huddle room can genuinely run from the laptop and the display's own remote, and adding control to it makes it worse.
  • Meeting-room and conferencing AV depends on Audio processing Only in certain cases. Only where the room has several microphones, or open-microphone pickup that needs echo cancellation and mixing across a live room. Processing is not a default line item. An all-in-one conferencing bar does its own echo cancellation and mixing internally, and specifying separate processing beside it buys nothing.
  • Meeting-room and conferencing AV depends on Mounting and fixing Cannot work without it. The display and camera hang on something, and a partition wall is not always that something.
  • Rack and equipment room depends on Electrical supply Cannot work without it. The room's supply is the sum of everything anyone puts in it, which is usually more than the first list.
  • Rack and equipment room depends on Heat removal Only in certain cases. Only where the installed load and the room's own ventilation cannot hold the cabinets inside the equipment's stated operating range. Equipment turns its power into heat inside a closed cabinet, and where the room cannot shed it the equipment shortens its own life.
  • Rack and equipment room depends on Containment and cable pathways Cannot work without it. Everything arrives as cable, and the entry point, the bend radius and the tray above the cabinets are all drawing items.
  • Rack and equipment room depends on Uninterruptible power Usual, not universal. Most equipment rooms protect at least the network and the recording. Which loads are on that list is a decision the client should make explicitly.
  • Uninterruptible power depends on Electrical supply Cannot work without it. The protected supply is fed from the ordinary one, and the changeover arrangement belongs to the electrical design.
  • Uninterruptible power depends on Heat removal Only in certain cases. Only where the batteries sit in an enclosed space whose temperature would otherwise run above the battery's rated range. Battery life falls away as the room gets warmer, so a runtime figure quoted for a cool room is not the runtime a hot cupboard gives.
  • Network switching depends on Structured cabling Cannot work without it. A switch port is only useful if a cable reaches something. The port count and the outlet count are the same number, arrived at separately on most projects.
  • Network switching depends on Rack and equipment room Cannot work without it. Switches are rack equipment. Where they go decides cable lengths, and cable lengths decide where they can go.
  • Network switching depends on Electrical supply Cannot work without it. A switch that powers devices draws what it delivers plus its own consumption, and that is a bigger number than the label on the front.
  • Network switching depends on Power over Ethernet Only in certain cases. Only where cameras, access points, readers or handsets are to be powered from the switch rather than locally. Powering devices from the switch is a budget, not a checkbox, and the budget is set by what is plugged in.
  • Network switching depends on Internet or wide-area uplink Only in certain cases. Only where systems on this network have to reach the internet or a hosted service. A network can be entirely internal and still be a network. What it must reach is a client decision.
  • Network switching depends on Uninterruptible power Only in certain cases. Only where any system on this network has to keep working through a mains interruption. Everything riding on the network stops when the switch does, which makes the switch the load people most regret leaving unprotected.
  • Structured cabling depends on Containment and cable pathways Cannot work without it. Cable needs a route with room in it. Containment sized for today's count is the most common reason a later addition costs more than it should.
  • Structured cabling depends on Rack and equipment room Cannot work without it. Every run terminates somewhere, and the room that receives them has to have been sized for the panels as well as the equipment.

What these systems pull in

  • Electrical supply. A circuit at the right place, coordinated with the electrical contractor rather than assumed.
  • Power over Ethernet. Power delivered down the data cable by the switch, so the device needs no local supply.
  • Recording and retention. Where footage is written, how long it is kept, and who may take a copy of it.
  • Internet or wide-area uplink. The path out of the building, and what stops working when it is down.
  • Containment and cable pathways. Tray, conduit and risers — drawn once for every system together, or fought over on site.
  • Heat removal. Equipment in a closed cabinet turns its power into heat, and the heat has to leave.
  • Door hardware. The lock, closer, frame and leaf. The reader decides; this is what actually holds or releases.
  • Loudspeakers. Where sound comes from, and therefore where the ceiling has to be coordinated.
  • Amplification. Driving passive loudspeakers. Active loudspeakers carry their own and need none.
  • Audio processing. Mixing, echo cancellation, delay and equalisation, where the room and the sources need it.
  • Microphones. How the room is heard, and the single biggest determinant of whether a call is bearable.
  • Room camera. How the far end sees the room, which is a furniture and sightline question before it is a product one.
  • Display or screen. The surface people read, sized against the furthest seat rather than the wall.
  • Conferencing platform. The service the organisation already runs its meetings on. The room is built around it.
  • Control and user interface. What somebody touches to start the room, and how many steps that takes.
  • Signal transport. Getting picture and sound from where they are made to where they are shown.
  • Video processing. Turning an incoming picture into the pixel map that drives a modular display.
  • Content and source. What is actually shown, at what resolution, produced by whom, and updated how often.
  • Structure and service access. What carries the load, and how somebody reaches the back of it two years later.
  • Projection surface. The screen or wall the image lands on, and whether it has to disappear when unused.
  • Mounting and fixing. What the equipment is fixed to, checked against what that surface can actually hold.
  • Room geometry. Ceiling height, room length and seated sightlines — settled by the architect, not by the AV supplier.

Planning · Coordination · Configurator

Most integration problems are not equipment problems. The camera was agreed, the switch was not, the containment was drawn for the data cabling alone, and the equipment room was sized before anyone counted what would go in it. This planner puts those dependencies on one screen while they can still be changed cheaply.

Project types
4
Space types
24
Systems modelled
17
Graph nodes
39

What the Building Technology Planner answers

What this planner answers

It answers one question: I am planning this kind of building — what technology systems, spaces, infrastructure dependencies and decisions should I be thinking about? Choose a project type, keep the spaces the project actually has, and each space shows only the systems relevant to it, what those systems depend on, the coordination questions to ask now, the drawings those answers will need, and the decisions still open.

  • When to use

    At brief stage, before drawings are issued, when an owner, architect or project manager has a building shape and no technology brief.

  • When not to use

    For quantities, specifications, a statutory position or a design. Those come from the appointed consultants and a site-specific review.

Send drawings for mark-up

· Method

How the planner decides what to show you.

A project type carries a list of spaces. Each space carries only the systems genuinely relevant to it — a guest room is not a banquet hall, and showing every system in every space is a way of having no opinion while looking thorough. The lists are short and deliberate.

Infrastructure is kept out of those lists on purpose. Nobody asks for containment; they ask for cameras and then discover the containment. So the spaces carry the systems a client names, and a separate dependency graph reveals what those drag in with them. That reveal is the point of the tool, and it is where the coordination cost usually hides.

Every dependency is classified by how hard it actually is, because common practice is not a universal requirement and treating it as one is how a planner starts overstating. The five classifications are set out below, and each one is rendered in plain language rather than as a code.

Background music and paging is a separate system from fire detection in this planner. The two appearing in the same building does not make them one system, and nothing here links them.

How a dependency is classified

Cannot work without it
The system does not function at all without this.
Usual, not universal
This is the usual arrangement, and there are real projects that do it differently.
Only in certain cases
Whether this applies depends on the condition stated beside it.
Sometimes specified
Specified on some projects and left out on others, with no penalty either way.
Expert-held
This one is not settled by a planning tool. It belongs to the appointed specialist and the authority having jurisdiction.

The four project types, and the spaces in each

Hotel / hospitality

A property where guests sleep, eat and hold events, and where the technology is judged by people who did not choose it.

What usually goes wrong: The guest-facing systems are specified early and the back-of-house infrastructure that carries them is specified last, by which point the risers are full.

Spaces

  • Reception / arrival The first impression, a queue, a desk, and the point where visitors are identified.
  • Guest room A private space repeated hundreds of times, where every decision multiplies.
  • Guest floor corridor A circulation route that mostly exists to serve the rooms off it.
  • Banquet / function hall A room that changes shape and purpose weekly and is sold on how it performs.
  • Meeting room A room somebody has to be able to start a call in without calling for help.
  • Restaurant / F&B A room whose noise level is part of the experience and part of the problem.
  • Back office / administration Where the building is actually run from, and where the staff network lives.
  • Server / equipment room The room every other space quietly depends on, usually sized before anyone counted what goes in it.
  • Parking A large, poorly lit area with vehicles in it and a barrier at each end.
  • External areas and perimeter Everything outside the walls, where weather and night-time lighting decide what works.

Office / workplace

A working building where the meeting rooms are the technology and everything else is expected to be invisible.

What usually goes wrong: Meeting rooms are designed as products rather than as rooms, so the furniture, the ceiling and the sightlines arrive after the AV is fixed.

Spaces

  • Reception / arrival The first impression, a queue, a desk, and the point where visitors are identified.
  • Open workspace Desks, movement and background noise, where the technology should not be noticed.
  • Meeting room A room somebody has to be able to start a call in without calling for help.
  • Boardroom The room the organisation is judged on, used by the people least willing to troubleshoot it.
  • Training room A room used by a presenter facing an audience, sometimes with people joining remotely.
  • Cafeteria / breakout A loud, informal space that doubles as an all-hands venue about twice a year.
  • Back office / administration Where the building is actually run from, and where the staff network lives.
  • Server / equipment room The room every other space quietly depends on, usually sized before anyone counted what goes in it.
  • Parking A large, poorly lit area with vehicles in it and a barrier at each end.
  • External areas and perimeter Everything outside the walls, where weather and night-time lighting decide what works.

Auditorium / cultural venue

A hall built around an audience, where the room's acoustics and sightlines are decided long before any equipment is chosen.

What usually goes wrong: The room's finishes and geometry are settled by the architecture, and the audio system is then asked to compensate for decisions it was never consulted on.

Spaces

  • Foyer / front of house Where an audience is held, informed and called to their seats.
  • Auditorium hall The room the whole building exists for, with acoustics set by its shape and its finishes.
  • Stage and performance area A working area with visiting technicians, changing rigs and no tolerance for surprises.
  • Control room / projection box Where the show is actually run from, with sightlines to the stage that have to be protected.
  • Green room / dressing rooms Where performers wait, and need to know what is happening on stage without being on it.
  • Back office / administration Where the building is actually run from, and where the staff network lives.
  • Server / equipment room The room every other space quietly depends on, usually sized before anyone counted what goes in it.
  • Parking A large, poorly lit area with vehicles in it and a barrier at each end.
  • External areas and perimeter Everything outside the walls, where weather and night-time lighting decide what works.

Commercial / mixed-use building

A landlord's building let to occupiers, where the boundary between base build and fit-out decides who owns which system.

What usually goes wrong: The base-build systems stop at a line nobody has drawn, and every incoming tenant negotiates the same undefined boundary again.

Spaces

  • Entrance lobby The landlord's front door, with a security position and a directory of occupiers.
  • Atrium / concourse A tall, hard-surfaced volume seen from several levels at once.
  • Tenant floor A shell whose services stop at a boundary that has to be defined before the first tenant signs.
  • Service corridor / goods route The route deliveries and staff take, away from the occupiers.
  • Plant room Mechanical and electrical plant, monitored by a controls system somebody else specified.
  • Back office / administration Where the building is actually run from, and where the staff network lives.
  • Server / equipment room The room every other space quietly depends on, usually sized before anyone counted what goes in it.
  • Parking A large, poorly lit area with vehicles in it and a barrier at each end.
  • External areas and perimeter Everything outside the walls, where weather and night-time lighting decide what works.

The systems the planner models

  • Camera surveillance Cameras, the network path they sit on, and somewhere the picture is watched or kept.
  • Access control Deciding at a door whether a credential opens it, and keeping a record of what happened.
  • Wi-Fi Wireless coverage and capacity for the people and devices actually in the space.
  • Telephony Voice handsets and the call routing behind them, usually riding on the same network as everything else.
  • Meeting-room and conferencing AV A room that can hold a call and show something, and that a non-technical person can start.
  • Background music and paging Music and spoken announcements distributed to zones of a building. A separate system from fire detection.
  • Digital signage Screens carrying wayfinding, information or brand content, and whatever feeds them.
  • IPTV and in-room television Television distributed over the building's own network to screens in rooms.
  • LED display wall A wall built from LED modules, driven as one picture by a processor.
  • Projection A projector and a surface, sized by the room rather than by the product sheet.
  • Sound reinforcement Making speech and programme audible and intelligible in a room people are sitting in.
  • Fire detection In scope for most occupied spaces. Every requirement, threshold and coverage rule belongs to the project's fire strategy and the authority having jurisdiction, not to this planner.
  • Automation and building controls Lighting, blinds, temperature and scenes brought under one way of being controlled.
  • Network switching The switch ports every other system quietly assumes will exist.
  • Structured cabling The building's permanent cable plant, outliving two or three generations of the equipment on it.
  • Rack and equipment room Where the equipment lives, is powered, is cooled and can be reached to be worked on.
  • Uninterruptible power Keeping a named list of loads running through an interruption, for a stated length of time.

Every dependency the graph records, and why

The interactive shows one rationale at a time so it stays inside a single view. The whole graph is written out here, so nothing it knows is only reachable by clicking.

Camera surveillance depends on

Network switchingCannot work without it
An IP camera is a network device. With no switch port and no address it produces no picture at all, anywhere.
Structured cablingCannot work without it
Every camera position is a cable run back to a node, and that run is drawn with the rest of the cable plant or it is improvised on site.
Electrical supplyCannot work without it
Whether it comes down the data cable or from a local supply, the camera has to be powered by something somebody has drawn.
Power over EthernetUsual, not universal
Most cameras take power from the same cable that carries the picture, which is why the camera count lands on the switch budget. Local low-voltage supplies are still used where there is no suitable port.
Recording and retentionUsual, not universal
Live-only monitoring exists, but nearly every installation records. How long footage is kept is the decision that sizes the platform, and it is a business decision before it is an engineering one.
Rack and equipment roomUsual, not universal
The recorder, the switch and the licences land in a cabinet. Small estates run from a wall-mounted enclosure instead, which is a legitimate answer and a different one.
Uninterruptible powerOnly in certain cases
Only where the client expects to keep seeing and recording through a mains interruption.Cameras, the switch feeding them and the recorder are three separate loads. Protecting one and not the others produces a system that stops anyway.
Containment and cable pathwaysCannot work without it
Camera cabling needs a route. Where that route was drawn for the data cabling alone, the cameras arrive as an unplanned addition to a full tray.

Access control depends on

Door hardwareCannot work without it
The reader and the controller only make a decision. The lock, the closer, the frame and the leaf are what physically hold or release the door, and they are usually somebody else's package.
Structured cablingCannot work without it
Each controlled door is a cable run to a controller, and door positions move later in the design than cable schedules like.
Electrical supplyCannot work without it
Controllers, readers and locks are all powered, and the lock is often the load nobody counted.
Network switchingUsual, not universal
Networked controllers are the usual arrangement because they let credentials be issued and revoked centrally. Standalone controllers on a local bus are still specified on small door counts.
Containment and cable pathwaysCannot work without it
Door cabling runs above ceilings and down frames, and the route has to exist before the frames are set.
Uninterruptible powerOnly in certain cases
Only where the client needs controlled doors to keep behaving predictably through a mains interruption.Without a supply, controllers stop making decisions and the doors sit in whatever state their hardware defaults to.
Fire detectionExpert-held
What a controlled door on an escape route does in an emergency is set by the project's fire strategy and the authority having jurisdiction. It is not derived from a door schedule and this planner does not determine it. PROJECT-SPECIFIC VERIFICATION REQUIRED before door hardware is specified or ordered.

Wi-Fi depends on

Structured cablingCannot work without it
An access point is a wired device with a radio on the end. Every one of them is a cable run to a ceiling position that has to be agreed with the architect.
Network switchingCannot work without it
Access points terminate on switch ports. The port count and the wireless design are the same conversation, held twice on most projects.
Power over EthernetUsual, not universal
Access points are normally powered by the switch, which is what turns a coverage plan into a power budget. Local injectors are used where a suitable switch is not present.
Electrical supplyCannot work without it
The power arrives at the access point one way or another, and the switch that supplies it is itself a load in the equipment room.
Rack and equipment roomUsual, not universal
The switching and any controller sit in a cabinet on the floor or in the equipment room. Small deployments run from cloud-managed access points with no local controller at all.
Internet or wide-area uplinkOnly in certain cases
Only where the wireless network is expected to carry internet or cloud traffic rather than local traffic only.Wireless coverage and internet access are different things, and a guest expecting the second will call the first broken.
Mounting and fixingCannot work without it
The ceiling finish decides what an access point can be fixed to, and a plasterboard raft, an exposed soffit and a stretched fabric ceiling are three different answers.

Telephony depends on

Network switchingCannot work without it
Voice handsets are network devices on the same switches as everything else, which is convenient until the network is being planned without them counted.
Structured cablingCannot work without it
Each handset position is an outlet, and handset positions are decided by furniture layouts that are often not final when the cabling is.
Power over EthernetUsual, not universal
Handsets are usually powered from the switch so a desk needs no extra adaptor. Some deployments use local supplies instead.
Internet or wide-area uplinkOnly in certain cases
Only where outside calls are carried over a data connection rather than a local line.If calls leave the building over a data path, then the state of that path is the state of the phone system.
Uninterruptible powerOnly in certain cases
Only where voice has to stay available through a mains interruption.An IP handset is only as available as the switch it hangs off and the platform behind it.
Rack and equipment roomUsual, not universal
Gateways and any on-premises platform live in a cabinet. Fully hosted deployments keep almost nothing on site.

Meeting-room and conferencing AV depends on

Display or screenCannot work without it
There is nothing to look at otherwise. The size is set by the distance from the furthest seat, which means the furniture layout has to be settled first.
MicrophonesCannot work without it
A call the far end cannot hear is not a call. Microphone placement is the single biggest determinant of whether people are willing to use the room.
LoudspeakersCannot work without it
The room has to hear the far end, and the ceiling that carries the loudspeakers is coordinated with lighting, detection devices and air terminals.
Room cameraCannot work without it
The far end has to see the room, and where the camera can go is a furniture and sightline question before it is a product question.
Conferencing platformCannot work without it
The room is built around whichever service the organisation actually runs meetings on today. Choosing hardware before that is settled is how rooms end up unused.
Network switchingCannot work without it
The room joins the call over the network, and a room codec is a device somebody has to have counted on the switch.
Structured cablingCannot work without it
Table boxes, floor boxes and the display position all need cable routes agreed before the slab is poured or the joinery is made.
Electrical supplyCannot work without it
Power at the display, at the table and at the rack position. The table one is the one that gets left off the electrical drawing.
Control and user interfaceUsual, not universal
Most rooms want one obvious way to start a meeting. A small huddle room can genuinely run from the laptop and the display's own remote, and adding control to it makes it worse.
Audio processingOnly in certain cases
Only where the room has several microphones, or open-microphone pickup that needs echo cancellation and mixing across a live room.Processing is not a default line item. An all-in-one conferencing bar does its own echo cancellation and mixing internally, and specifying separate processing beside it buys nothing.
Mounting and fixingCannot work without it
The display and camera hang on something, and a partition wall is not always that something.

Background music and paging depends on

LoudspeakersCannot work without it
The loudspeaker layout is the system. Where the ceiling grid, the lighting and the loudspeakers are drawn separately, one of them moves on site.
AmplificationUsual, not universal
Distributed loudspeakers are usually passive and driven from a central amplifier. Powered loudspeakers on a networked source are a real alternative on smaller layouts.
Electrical supplyCannot work without it
Amplification is a real electrical load in the rack position, and it is often sized after the electrical drawings are issued.
Containment and cable pathwaysCannot work without it
Loudspeaker cabling runs the length of every zone and needs its own route, kept apart from cabling it should not share a containment with.
Rack and equipment roomUsual, not universal
Amplification and sources land in a cabinet, and amplification is one of the warmer things in it.
Audio processingSometimes specified
Zone processing helps where zones differ a lot in size or noise. A single-zone music system does not need it and is not improved by it.
Content and sourceUsual, not universal
Music needs something to play, and who holds the right to play it in a commercial space is a question the client answers rather than the installer. An announcement-only system is the real exception: its source is the microphone at the paging station, and there is no programme material to license.

Digital signage depends on

Display or screenCannot work without it
The screen is the system, and whether it is read while walking past or while standing still changes the size before the model.
Content and sourceCannot work without it
A screen with nobody appointed to update it is a screen showing last season's message. Who writes the content is decided at design stage or it is not decided at all.
Mounting and fixingCannot work without it
The screen hangs on something, and a feature wall built from plasterboard on a light frame is the classic late discovery.
Electrical supplyCannot work without it
Power behind the screen, at the height the screen is actually at, is a coordination item and not an assumption.
Network switchingUsual, not universal
Screens are normally updated over the network. Players that run from local storage exist and are still specified where no network reaches.
Structured cablingUsual, not universal
Where the screen is updated over the network it needs an outlet behind it, which is a different position from the power outlet only by accident.

IPTV and in-room television depends on

Network switchingCannot work without it
Television over the building network is network traffic, and it behaves differently from everything else on the switch.
Structured cablingCannot work without it
Every screen position is an outlet, and screen positions in rooms are set by the interior designer rather than the cable schedule.
Content and sourceCannot work without it
Channels come from somewhere, and the rights to show them in a commercial building belong to the client.
Display or screenCannot work without it
The screen is what the guest actually experiences, and it is often chosen for the room before anyone asks what will drive it.
Internet or wide-area uplinkOnly in certain cases
Only where channels or streaming services are carried from outside rather than from a local head-end.Where the channels come from outside the building, the outside path is part of the television system.
Rack and equipment roomUsual, not universal
The head-end and its licensing sit in a cabinet, usually the same one everything else is competing for.

LED display wall depends on

Electrical supplyCannot work without it
A modular wall is a substantial and continuous electrical load, and it is one of the few AV items that genuinely changes the electrical design.
Video processingCannot work without it
A wall is a grid of modules, not a screen. Something has to turn an incoming picture into the pixel map that drives them.
Signal transportCannot work without it
The picture has to reach the processor from wherever it is made, and that route is usually longer than anyone assumed at concept stage.
Content and sourceCannot work without it
A wall is built at one pixel geometry and content is made at another. Agreeing that early is the difference between a sharp wall and a stretched one.
Structure and service accessCannot work without it
The frame carries real weight and has to be fixed to real structure. Whether the wall is serviced from the front or the back has to be settled before it is built, not after.
Network switchingUsual, not universal
Control and monitoring normally sit on the network so the wall can be driven and checked remotely. Locally driven walls exist.
Uninterruptible powerOnly in certain cases
Only where the wall carries live content that must not drop during an event.A wall that goes dark mid-event is a different failure from a wall that goes dark overnight.

Projection depends on

Projection surfaceCannot work without it
The surface is half the system, and whether it stays visible when unused is an interior decision with a technical consequence.
Room geometryCannot work without it
Throw distance, ceiling height and the seated sightline decide the lens and the mounting position before any product is chosen. Where the architecture is fixed first, projection has to fit it.
Mounting and fixingCannot work without it
The projector hangs from structure or a bracket that has to be coordinated with the ceiling, the lighting and access for a lamp or filter change.
Signal transportCannot work without it
The projector is rarely near the source, so the run between them is a design item rather than a cable off a shelf.
Electrical supplyCannot work without it
A supply at the projector position, which is usually a ceiling position with no other reason for a socket to be there.
Control and user interfaceUsual, not universal
Most rooms want the projector, the screen and the lighting to move together on one press. A simple room can be operated with separate controls.

Sound reinforcement depends on

LoudspeakersCannot work without it
Coverage is decided by where loudspeakers can physically go, which is a ceiling and rigging conversation with the architect.
AmplificationUsual, not universal
Most loudspeakers are passive and need external amplification. Active loudspeakers carry theirs inside and need none, which changes the rack and the electrical load.
Audio processingOnly in certain cases
Only where the system has several zones, several live microphones, or delay and equalisation to manage across a difficult room.Processing is not automatic. A single-source, single-zone system does not need it and is not made better by adding it.
MicrophonesUsual, not universal
Speech reinforcement needs microphones and their positions constrain everything else. A programme-playback-only system needs none.
Containment and cable pathwaysCannot work without it
Loudspeaker and microphone cabling needs routes that were drawn for it, and rigging positions above a hall are decided with the structural engineer.
Electrical supplyCannot work without it
Amplification is a genuine load at the rack position, and how it is earthed decides whether the system hums.
Rack and equipment roomUsual, not universal
Amplification, processing and sources land in a cabinet near the room they serve. Small active systems can live behind a panel instead.
Room geometryCannot work without it
How reverberant a room is depends on its shape and its finishes, and both are settled by others. A system designed before the finishes are known is designed against a guess.

Fire detection depends on

Electrical supplyCannot work without it
Detection equipment is powered equipment and appears in the electrical coordination like anything else. Nothing about how it is supplied is settled here.
Containment and cable pathwaysCannot work without it
Detection cabling needs a route, and the route is coordinated with the other services early so it is not competing for the same tray later. What that cabling must be, and how it is segregated, comes from the fire scheme.
Automation and building controlsExpert-held
Whether detection signals do anything to building plant is set by the project's fire strategy and the authority having jurisdiction. It is not derived from a controls points list and this planner does not determine it. PROJECT-SPECIFIC VERIFICATION REQUIRED.

Automation and building controls depends on

Electrical supplyCannot work without it
Controls sit between the supply and the thing being controlled, so the electrical design and the controls design are the same drawing seen twice.
Containment and cable pathwaysCannot work without it
Field devices are distributed everywhere by definition, and their routes are the ones most often assumed to be somebody else's.
Network switchingUsual, not universal
Head-ends and modern controllers normally sit on the network. Field buses that never touch it are still widely used.
Rack and equipment roomUsual, not universal
The head-end and its interfaces need a home, and it is usually the same cabinet everything else wants.
Structured cablingOnly in certain cases
Only where the chosen controllers use the building's data cabling rather than a dedicated field bus.Some controls ride the data cabling and some run on their own bus, and the two are budgeted by different people.

Network switching depends on

Structured cablingCannot work without it
A switch port is only useful if a cable reaches something. The port count and the outlet count are the same number, arrived at separately on most projects.
Rack and equipment roomCannot work without it
Switches are rack equipment. Where they go decides cable lengths, and cable lengths decide where they can go.
Electrical supplyCannot work without it
A switch that powers devices draws what it delivers plus its own consumption, and that is a bigger number than the label on the front.
Power over EthernetOnly in certain cases
Only where cameras, access points, readers or handsets are to be powered from the switch rather than locally.Powering devices from the switch is a budget, not a checkbox, and the budget is set by what is plugged in.
Internet or wide-area uplinkOnly in certain cases
Only where systems on this network have to reach the internet or a hosted service.A network can be entirely internal and still be a network. What it must reach is a client decision.
Uninterruptible powerOnly in certain cases
Only where any system on this network has to keep working through a mains interruption.Everything riding on the network stops when the switch does, which makes the switch the load people most regret leaving unprotected.

Structured cabling depends on

Containment and cable pathwaysCannot work without it
Cable needs a route with room in it. Containment sized for today's count is the most common reason a later addition costs more than it should.
Rack and equipment roomCannot work without it
Every run terminates somewhere, and the room that receives them has to have been sized for the panels as well as the equipment.

Rack and equipment room depends on

Electrical supplyCannot work without it
The room's supply is the sum of everything anyone puts in it, which is usually more than the first list.
Heat removalOnly in certain cases
Only where the installed load and the room's own ventilation cannot hold the cabinets inside the equipment's stated operating range.Equipment turns its power into heat inside a closed cabinet, and where the room cannot shed it the equipment shortens its own life.
Containment and cable pathwaysCannot work without it
Everything arrives as cable, and the entry point, the bend radius and the tray above the cabinets are all drawing items.
Uninterruptible powerUsual, not universal
Most equipment rooms protect at least the network and the recording. Which loads are on that list is a decision the client should make explicitly.

Uninterruptible power depends on

Electrical supplyCannot work without it
The protected supply is fed from the ordinary one, and the changeover arrangement belongs to the electrical design.
Heat removalOnly in certain cases
Only where the batteries sit in an enclosed space whose temperature would otherwise run above the battery's rated range.Battery life falls away as the room gets warmer, so a runtime figure quoted for a cool room is not the runtime a hot cupboard gives.

Limitations — what this planner will not do

This is a planning conversation, not a bill of quantities, not a compliance determination and not a design. It sets out what has to be decided and which drawings those decisions will need. Quantities, specifications and any statutory position come from the appointed consultants and from a site-specific review.

It publishes no quantities, no specifications and no figures you could build a budget from, because none of those are knowable from a building type and a space list. It does not size anything: where a quantity genuinely follows from an input, the planner hands you to the specialist tool that does that one thing properly.

It does not resolve anything that varies by jurisdiction, occupancy or authority. Where a dependency turns on that, the planner marks it as expert-held, says PROJECT-SPECIFIC VERIFICATION REQUIRED, and stops. Fire detection is treated that way throughout: it appears as in scope where it is in scope, and every requirement, threshold, coverage rule and compliance position belongs to the project’s fire strategy and the authority having jurisdiction.

The coordination questions are the ones worth asking early. They are not a checklist that, once answered, means a project is coordinated — that is what the appointed consultants and a drawing-stage review are for.

· Engineering advisory · Building Technology Planner

What the dependency reveal usually changes on a real project.

The space-to-system mapping is the easy half. The half that moves programme and scope is what those systems turn out to need, and when that is discovered.

01

Deployment observations

  • The systems a client names are rarely the systems that cause trouble. Cameras, access control and Wi-Fi are agreed at concept; the switch ports, the containment fill and the equipment-room space they imply are settled by whoever notices last. Putting the dependency beside the system at brief stage is the whole intervention.
  • Meeting rooms and halls are decided by furniture, ceiling and sightlines before they are decided by equipment. Where the AV scope is fixed before the layout is, the room is designed twice — once on paper and once on site.
  • The base-build to fit-out boundary on a let building is a technology decision disguised as a commercial one. Defining where the landlord's cabling, cameras and access control stop, before the first tenant signs, avoids negotiating the same undefined boundary with every occupier.
02

Commissioning discipline

  • The drawings named against each system are the ones a coordination meeting actually needs: a reflected ceiling plan, a containment route, a door schedule, a furniture layout. A meeting held without them produces decisions that get revisited.
  • Labelling tied to the architect's room numbering, agreed before installation rather than after, is what makes the first move-around after handover a small job instead of a survey.
03

Operational notes

  • Every system on the list has an owner after handover — who issues credentials, who updates screen content, who edits a lighting scene, who reviews footage. Where that owner is not named at brief stage, the system quietly stops being maintained and starts being tolerated.
04

Lifecycle implications

  • The cable plant and the containment outlive several generations of the equipment on them. Spare capacity decided at brief stage is the cheapest decision in the whole programme; the same capacity added later is a re-pull.
05

Expansion readiness

  • A second phase inherits the equipment room, the containment fill and the network the first phase left behind. The planner's reveal is the list to check that headroom against before phase one is fixed.

Verification status: Decision support — editorial logic, no numeric claim · Methodology, assumptions and sources documented · reviewed 2026-09-07

· Engineering notes

How to read this tool’s output

Stage 1 (brief), before any drawing set is issued. It is the conversation an owner, architect or project manager has with the integrator while changing a decision still costs a conversation rather than a variation.

The assumptions, limits and reference architectures behind this

What an engineer should know

The assumptions behind the numbers this tool produces.

  • The planner works space by space rather than building by building. A guest room and a banquet hall are not the same technology problem, and a list of systems for 'a hotel' hides exactly the differences a coordination conversation is about.
  • Each system carries its own dependency set, classified by how binding it is: cannot work without it, usual but not universal, conditional on a stated trigger, optional, or held for a specialist. Common practice is never published as a requirement.
  • Fire detection appears as scope and never as a rule. Every requirement, threshold, coverage position and compliance judgement belongs to the project's fire strategy and the authority having jurisdiction.

When this tool is the right one

The project moments and room types this is built for.

  • An architect scoping which ELV disciplines a new building involves before issuing a services brief.
  • A project manager assembling the coordination questions to put to a consultant at concept stage.
  • An owner understanding what a technology scope covers before appointing anyone.

What changes the answer in practice

Field conditions that move the result away from the planning figure.

  • Spaces the project does not have should be removed early — the coordination question count is dominated by the space list, not the systems.
  • A building type with an existing dedicated planner on this site is better served there; this tool covers the coordination layer those tools do not.

Defensible starting architectures

Vendor-neutral reference points, not a recommendation to buy — the right answer is the one that survives your site survey.

  • Brief-stage system and space matrix, reviewed against the architectural drawings before services coordination begins.

Common mistakes

Failure patterns we see on real projects.

  • Reading the system list as a scope of works. It names what to think about, not what to buy.
  • Treating a dependency as a purchase. A dependency says one system needs another to function; it says nothing about who supplies either.
  • Expecting quantities. The planner publishes none, by design.

How this lands against adjacent systems

What else has to be agreed before this output is safe to build to.

  • A dependency edge describes how equipment works, never how two contracts are split.
  • Background music and paging carry no relationship to fire detection anywhere in the model, in either direction.

What this tool does not do

Deliberate limits — where the estimate stops and design begins.

  • Publishes no quantities, no pricing and no device schedule.
  • States no compliance position and resolves no life-safety requirement.
  • Computes no engineering figure, so it hands no figure to another tool.

Where this tool fits

The building types this output is calibrated for — and, where we have said so, the ones it is not.

The standards and technologies this touches

Reference pages for the protocols, standards and systems behind this tool’s output.

· Why it matters

A hotel adds cameras to the corridors and the parking late in design. Nobody re-checks the switch, so the ports run out; the containment was drawn for the data cabling alone, so there is nowhere to route the new cable; the equipment room was sized before the recorder existed. Each of those was a reasonable decision in isolation. The planner puts the camera, the switch, the containment and the room on one screen at brief stage, while changing any of them still costs a conversation rather than a variation.

· Frequently asked

Building Technology Planner
what people ask first.

Is this a bill of quantities or a budget tool?

No. It publishes no quantities, no specifications and no figures you could build a budget from, because none of those are knowable from a building type and a space list. It sets out what has to be decided and which drawings those decisions will need. Quantities and specifications come from the appointed consultants and a site-specific review.

Why are only four project types offered?

Because a restrained taxonomy that is right is more use than a broad one that is approximately right everywhere. Hotel and hospitality, office and workplace, auditorium and cultural venue, and commercial mixed-use cover the building shapes where the space-to-system mapping differs most. A building that is genuinely none of them is better served by a conversation than by a fifth generic option.

Why does the planner show fewer systems in a space than I expected?

Each space lists only the systems genuinely relevant to it. Showing every system in every space produces a checkbox wall, which looks thorough and decides nothing. Infrastructure is deliberately absent from the space lists too — it appears in the dependency reveal, because that is how it appears on a real project.

What does the difference between the dependency labels mean?

Cannot work without it means the system does not function at all without that thing — an IP camera with no network path produces no picture. Usual, not universal means it is the normal arrangement and real projects do it differently: most loudspeakers need an amplifier, powered ones carry their own. Only in certain cases always states the condition it turns on. Sometimes specified means projects go either way. Expert-held means it is not settled by a planning tool at all.

How does the planner treat fire detection?

It shows fire detection as in scope for the spaces where it is in scope, and it stops there. Every requirement, threshold, coverage rule and compliance position belongs to the project's fire strategy and the authority having jurisdiction — the planner determines none of them and says so on the row. Background music and paging is modelled as an entirely separate system; two systems in one building is not an integration, and the planner does not draw one between them.

Do the specialist tools it links to carry my selections across?

No, and deliberately. This planner produces no quantities, so it has no figure to hand over. A tool that arrived pre-filled with numbers nobody computed would look authoritative and be worthless. The links open the specialist tool so you can work the question there with your own inputs.

· Begin

Send the drawings and we will
mark up the coordination.

Share the floor plan and the reflected ceiling plan for the spaces you have selected. We will mark up the containment routes, the rack and equipment-room positions and the coordination items this scope creates, and write back with what still needs deciding.