Tinsukia Medical College & Hospital.
The shape of the deployment.
Structured engineering tagging — deployment archetype, infrastructure complexity, operational class and the named protocols the integration runs on.
- Infrastructure complexity
- Multi Block
- Operational class
- Clinical Care
- Deployment archetypes
- clinical elv stackmulti discipline coordinated elvaddressable fire life safety
- Protocols referenced
- Cat6A structured cabling (TIA-942)Addressable fire-alarm loop (IS-2189)BACnet/IP supervisoryONVIF Profile S/T CCTVIP-PBX hunt-group routing
What we were asked to deliver.
A turnkey ELV, life-safety and IT stack delivered into a working medical college and teaching hospital, awarded to TechnoGuru by NCC Limited and handed over against a documented commissioning report. Surveillance, fire detection, public-address, nurse-call, access-control, structured cabling and IP-PBX were engineered as one coordinated layer rather than seven discrete contracts.
The seven disciplines were engineered against one cause-and-effect matrix, not seven. A fire-alarm trigger from any addressable detector simultaneously homes the lifts, releases the magnetic door-holders on egress paths, closes AHU dampers per zone, broadcasts the affected zone over the PA, pre-records on the linked CCTV cameras and switches access control to evacuation mode. The matrix is documented per zone, signed off by the hospital's clinical-engineering and fire-safety leads, and tested at every cutover window — not just at final commissioning.
A frame from the engagement.
Photographs from the completed installation. Commercial documents and BOQ details remain private.
Signal & system architecture.
Systems integrated: 5 disciplines, one contract.
Pro audio
Video wall
Surveillance
Fire & life-safety
Conferencing
- ↳Routing CCTV and nurse-call cabling without crossing positive-to-negative pressure boundaries between OT corridors and isolation rooms — every penetration was sealed to NABH-readable standard with a written register.
- ↳Aligning the fire-alarm cause-and-effect with the hospital's clinical workflow: AHU dampers in OT zones must close on a fire trigger only after the surgical-anaesthesia team has acknowledged, not instantly. The matrix carries that delay explicitly.
- ↳Zoning the public-address system so a code-blue announcement reaches IPD without bleeding into OT — solved by separate amplifier zones with hardware-enforced isolation rather than software-only muting.
- ↳Holding the structured-cabling backbone to a 25-year service horizon while threading risers through a building still receiving outpatients — staged installation by clinical zone, with cutover windows scheduled around OPD calendar.
- ·Single accountable contractor across seven disciplines — the hospital's clinical-engineering lead has one number to call for any ELV-related fault, instead of seven.
- ·Documented commissioning report against a written test plan — the cause-and-effect matrix was witnessed by clinical engineering and fire safety and signed off before handover.
- ·Active AMC with contracted critical-hours support on the nurse-call and fire-alarm subsystems — patient-care critical loops do not wait for business hours.
- ·Configuration baselines stored offline in our Lachit Nagar archive — any controller is recoverable from a clean slate within the same business day.
What the floor told us when work started.
Pressure-boundary penetrations are the install you cannot see.
Every CCTV and nurse-call cable crossing between an OT corridor (positive pressure) and an adjacent isolation room (negative pressure) is a fire-stopped, NABH-readable penetration with a written register. The pressure boundary is what keeps the hospital infection-control story intact — the integrity of the seal is more important than the speed of the cable pull.
OT AHU dampers do not snap shut on fire trigger.
The cause-and-effect matrix carries an explicit, signed-off delay on the OT AHU damper response — the surgical-anaesthesia team has to acknowledge the alarm before the damper actuates, because an instant cut to AHU airflow during an open-abdomen procedure is a worse outcome than the fire it is responding to. The delay is documented per OT zone, not coded once.
Code-blue PA zoning is hardware-enforced.
A code-blue announcement reaching an OT in mid-procedure is a clinical incident in its own right. The PA amplifier zoning is enforced at the amplifier rack with physical zone separation — not at the operator console with software muting — so a misconfigured preset cannot accidentally bridge the IPD and OT zones.
Cutover happened around the OPD calendar, not on a standard install schedule.
OPD continued to receive outpatients through the install — the structured-cabling riser was staged by clinical zone with cutover windows scheduled around the OPD's published calendar, not the installer's convenience. The 25-year service horizon was held under live-load conditions.
What the engagement had to work around.
- CLINICAL OPERATIONS
- Constraint —OPD running through install — no extended shutdown window across the hospital's clinical and academic blocks.
- Design response —Staged installation by clinical zone with cutover windows held against the OPD's published calendar; commissioning report witnessed by clinical engineering and fire safety at every stage, not only at final handover.
- INFECTION CONTROL
- Constraint —Positive-to-negative pressure boundaries between OT corridors and isolation rooms — every cable penetration is an infection-control risk.
- Design response —Every penetration is fire-stopped to NABH-readable standard with a written register; the register travels with the hospital's clinical-engineering documentation and is auditable at NABH inspection.
- CAUSE-AND-EFFECT DISCIPLINE
- Constraint —Fire-alarm logic has to coordinate with lifts, doors, AHU dampers, PA, CCTV pre-record and access-control evacuation mode — across seven disciplines on one contract.
- Design response —One signed-off cause-and-effect matrix per zone, witnessed and signed by the hospital's clinical-engineering and fire-safety leads before each cutover; the matrix is the contract for handover, not the BOQ.
- LIFECYCLE
- Constraint —Structured cabling has to hold a 25-year service horizon against a building still receiving outpatients.
- Design response —TIA-942-class structured cabling with labelled patch panels, documented rack elevations and offline-stored configuration baselines; any controller is recoverable from a clean slate within the same business day.
What needed careful handover.
Per-zone fire-alarm cause-and-effect rehearsal with clinical engineering.
Each zone's matrix was walked end-to-end with the hospital's clinical-engineering lead — detector trigger, lift homing, door release, AHU damper response (with the OT delay), PA broadcast, CCTV pre-record and access-control evacuation mode. Sign-off was per-zone, not blanket.
EFFORT — Multiple cutover windows
Pressure-boundary penetration register against NABH inspection.
Every cable penetration crossing a positive-to-negative pressure boundary was photographed before and after fire-stopping, with material spec and inspector signature; the register sits with the hospital's clinical documentation and survived the NABH inspection cycle.
Code-blue escalation simulation across nurse-call and PA.
A simulated code-blue from a bedside test pendant was traced through to the local nurse station, the resident on-call mobile and the MICU board simultaneously — without bleeding into the OT zone — over multiple rehearsal cycles before the room went into clinical use.
Configuration baseline archive offline at Lachit Nagar.
Every controller, NVR, panel and switch configuration baseline was exported offline to the Lachit Nagar archive at handover; the recovery procedure was rehearsed on a clean-slate panel before sign-off.
Seams that required cross-trade engineering.
SEAM 01
Fire-alarm × OT AHU dampers × surgical-anaesthesia workflow
The matrix carries an explicit acknowledgement delay on the OT damper response — coordinated against the surgical-anaesthesia protocol and signed off per OT zone before commissioning.
SEAM 02
Nurse-call × IP-PBX × MICU board × resident on-call mobile
A code-blue from any bedside escalates simultaneously across the local nurse station, the resident on-call mobile via the IP-PBX hunt group, and the MICU board — without false-alarm storms during routine bathroom-pull testing.
SEAM 03
Access control × fire-alarm × evacuation mode × lift homing
A fire trigger from any addressable detector releases magnetic door-holders on egress paths, homes the lifts to ground floor, and switches the access-control system to evacuation mode — one matrix, one signed-off cause-and-effect, witnessed by both clinical and fire-safety leads.
What the design refuses to let take the whole system down.
Single OT AHU damper actuates without surgeon acknowledgement.
HIGHIsolated by —Cause-and-effect carries an explicit, signed-off delay on the OT damper response — the surgical-anaesthesia team has to acknowledge the alarm before the damper actuates; the delay is documented per OT zone.
Code-blue PA bleeds into OT during procedure.
HIGHIsolated by —PA amplifier zoning is hardware-enforced at the amplifier rack with physical zone separation; a software-only preset misconfiguration cannot bridge IPD and OT zones.
Fire-stopped penetration compromised by later FM contractor.
MEDIUMIsolated by —Penetration register held with hospital clinical-engineering documentation and re-audited at each NABH inspection cycle; any later opening triggers a re-stop and re-record requirement.
Configuration baseline lost during controller swap.
MEDIUMIsolated by —Offline-stored baseline archive at Lachit Nagar lets any controller recover from a clean slate within the same business day; the recovery procedure is rehearsed at each AMC visit.
What the team will live with.
- Cat6A backbone25-year service horizon under documented installation; labelled patch panels and rack elevations let any later contractor add capacity without re-pulling the backbone.
- Addressable fire-alarm panel12–15 year panel lifecycle; cause-and-effect baseline is exported offline after every configuration change so a panel swap can be commissioned against the saved matrix, not rebuilt against memory.
- IP CCTV camera optics7–9 year horizon on camera bodies; the VMS-side rules and PoE budget have headroom for like-for-like replacement on a rolling refresh, with each replacement re-recorded against the documented pre-record matrix.
- Nurse-call pendant batteriesBedside-pendant and code-blue button cells on a 3–4 year refresh cycle against IS-2189 maintenance discipline; the AMC holds named-pack inventory keyed to each ward, not generic spares.
What this engagement taught us, on the record.
- 01
The cause-and-effect matrix, not the BOQ, is the contract for hospital ELV handover.
Every healthcare engagement since this handover treats the cause-and-effect matrix as the primary handover document — written, signed and witnessed per zone, with the BOQ as supporting evidence.
- 02
Pressure-boundary penetrations are an infection-control deliverable, not a cable-pull task.
Every healthcare engagement carries a fire-stopping register with photograph-and-spec-per-penetration discipline — held with the hospital's clinical-engineering documentation and auditable at NABH inspection.
- 03
Code-blue PA zoning is enforced at the amplifier, not at the operator console.
Every clinical PA deployment carries hardware-enforced zone separation at the amplifier rack — a software preset misconfiguration must not be able to bridge a critical-care zone with a procedural zone.
· Where to go next
Related engineering, insights and tools.
Read further
Engineering pages
- NBC 2016 — fire and life-safety provisions for hospital occupancy
- IS 2189 — code of practice for installation of automatic fire-detection and alarm systems
- NFPA 72 — National Fire Alarm and Signaling Code (international cross-reference)
- NABH 5th Edition — facility management, infection control and emergency preparedness
The systems and sectors behind Tinsukia Medical College & Hospital.
Every discipline on this project is engineered as part of one integrated stack. Open the system practice, or the sector it sits inside — each page is a live brief you can start a similar project from.
Public project summaries describe systems and outcomes only. BOQ values, quantities, device counts, security and network layouts and private drawings are kept off public surfaces.
Specifying a healthcare room for a real building?
Send the floor plates, the operating context and the documented brief. We return a sized design and a defensible cost band within two working days.
Talk to the studio