You run a facility that never really closes. A network outage at peak hour, a camera blind spot on a platform, or a voice alarm that misfires in a packed terminal is not an inconvenience, it is a public-safety event. Transport ICT solutions are the networks, surveillance, building controls, passenger information and life safety systems that keep a metro station, railway hub or airport terminal safe and moving, and you get them designed, integrated and certified together under one contract.
Yakkaservices integrates the building systems behind a transit facility. Here is where that work fits, and where it does not, so you can place us correctly before you read another word.
When a metro station, depot, railway hub or airport terminal needs several systems designed, integrated and certified together, and when you want one team accountable for how the network, cameras, controls, announcements and fire systems behave as a whole.
We do not supply or maintain rolling stock, signalling and train control (CBTC), trackwork, platform screen door mechanics, or baggage handling machinery. If your scope is one of those alone, a dedicated specialist is the right call, and we will tell you so.
If you need a ticketing application, a journey-planning app, or an intelligent transport system (ITS) software platform on its own, that is a software procurement. We integrate the field networks and devices these platforms run on, but we do not write the application.
Your busiest hour can carry many times your average load, and the systems have to hold at that peak, not at the average. There is rarely a quiet window to take a network, a camera ring or a fire panel offline, so design for live maintenance and redundancy is a starting condition, not an upgrade.
A metro or rail facility answers to fixed-guideway fire and life safety rules, and authority sign-off from the metro rail safety regulator before passenger service begins. An airport adds aviation security and restricted-zone control. These codes govern evacuation, ventilation, voice alarm and access in ways a normal commercial building never sees.
When something goes wrong you are clearing a packed platform or concourse, not walking a few people to an exit. That puts weight on voice alarm intelligibility, smoke control across large volumes, and announcements and signage that direct a crowd the same way at the same moment. A message that is unclear or out of step costs you the evacuation.
Transport ICT solutions are not one product. They are six systems that have to be designed to work as one, each carrying a different part of keeping your facility safe, secure and moving.
The data backbone every other system rides on, from ticketing and passenger information to CCTV and building controls. Designed for resilience and growth to TIA-568-D (2018) and ISO/IEC 11801:2017, with operational traffic separated from corporate so a public-facing fault cannot reach your control network.
ICT infrastructurePlatform, concourse and perimeter CCTV feeding one control room, with storage sized to the retention period your authority mandates. Camera placement comes from a site survey, not a template, so the coverage you pay for is the coverage you get.
ELV systemsControlled separation between public areas, paid zones, staff-only spaces and, in an airport, landside and airside. Access events tie back to the surveillance and command platform, so an alarm shows you the door and the camera together.
ELV systemsHVAC, lighting and energy controls for stations and terminals on open protocols (BACnet, Modbus, KNX), with the interfaces to station and tunnel smoke control that fire and life safety depend on. Open protocols keep you free to change or extend without returning to one vendor.
Building management systemAddressable fire detection across a distributed site, integrated with voice alarm, smoke control and access release so a single event triggers one coordinated response. Designed to NFPA 72 (2022), NFPA 130 and local fire authority requirements.
Life safety systemPublic address, voice alarm, digital signage and wayfinding that handle routine announcements and switch to a clear, zoned evacuation message when fire and life safety calls for it. Voice alarm built to EN 54-16 and EN 54-24 for intelligibility under load.
AV solutionsFour failures that show up at commissioning or after the facility opens. Each one is preventable at design stage.
The speakers pass on a bench test, but nobody checks intelligibility in a live concourse with trains arriving and a crowd talking over them. On a transit platform, a voice alarm that cannot be understood under that noise is a message that does not land at the one moment it has to. We have seen systems specified by speaker count alone, with no intelligibility target anyone measured.
An evacuation message lost under crowd and train noise, the one moment it has to be understood.
Voice alarm designed for intelligibility to EN 54-16, zoned to match the space, and measured against a speech-intelligibility target at commissioning, not assumed from the speaker count.
Cameras get placed to the drawing rather than the sightlines, so a pillar or a standing crowd creates a blind spot exactly where an incident happens. The recorder is sized to a round number of days instead of the retention your authority mandates, and the footage you need has already been overwritten.
An incident on a platform or concourse with no usable footage, and a retention gap your regulator can cite.
Coverage modelled from a site survey against sightlines and crowd flow, with storage sized to the mandated retention period and verified at commissioning, not estimated on a datasheet.
Ticketing, fare collection, passenger displays and CCTV all share one backbone, and that backbone has one path. It holds in testing at low load, then a switch or a link fails during the evening peak and several passenger-facing systems drop at once.
Ticketing, fare collection and passenger displays go down together at the busiest hour, when you can least absorb it.
A resilient backbone with redundant paths and failover, operational traffic separated from corporate, tested under simulated peak load before handover.
The access design follows the architecture rather than the operational rules, so a service door or an interchange route quietly bridges a paid and unpaid area, or in an airport a landside and airside boundary. It works for staff on day one and becomes a fare-evasion path or a security finding later.
A fare-evasion route, or in an airport a security breach and a regulatory finding against your restricted-area control.
Zoning designed from the operational plan, access tied to surveillance for event correlation, and every boundary door tested against its rule set before the facility opens.
In a transit facility, the systems are only as good as the points where they meet. A safe evacuation depends on fire detection, smoke control, access, announcements and displays acting as one. None of that happens by accident. It happens because the interfaces were drawn at design stage and tested before handover.
When one team designs and commissions all of it under a single contract, those interfaces are one team's responsibility. When each system is a separate contract, the gaps between them belong to no one, until the day they fail.
Compliance is easier to judge when you can see it by system. Here is what each system we deliver is designed, tested and approved against, for transit projects in India and Oman.
Structured cabling and the data backbone that carries ticketing, passenger information, CCTV and controls, designed for resilience and growth.
Across all of them, you receive the evidence at handover: test certificates, the fire cause-and-effect matrix, voice-alarm intelligibility results, and as-built drawings.
The questions transit authorities, operators, and consultants ask before they specify.
Tell us about your metro, rail or airport project and a senior engineer reviews it with you, then sets out what your systems need and where the risks are.
Response within one business day. No cost, no obligation.
