Industries
Industries We Work In
Skyfal services enterprise security systems in buildings that cannot be shut down while a fault is chased: correctional facilities, hospitals, banks, data centres, government sites, school boards, steel plants and institutional properties. The hardware is often the same across them. What changes is the cost of a failure and what has to happen before anyone touches a live system.
Correctional facilities
Nothing is tested casually here. A door that opens when it should not, or fails to open when it must, is an incident before it is a service call.
Reliability before anything else
Systems run continuously and are used hard. Controllers, interlocks and door hardware see cycle counts an office building would take years to reach.
- Controller and interlock faults traced before parts are changed
- Cycle-related wear on locks, position switches and readers
- Redundant server and communication paths verified rather than assumed
Controlled access to the work itself
Access to a technical space is arranged through facility procedure, on the facility’s timing, with escorts where required. Tools go in counted and come out counted.
- Clearance, screening and escort arranged before arrival
- Tool and equipment control on entry and exit
- Work windows agreed with the shift rather than imposed on it
Duress and communication systems
Duress, intercom and officer communication systems are tested end to end, including the annunciation somebody in a control room is relying on.
- Duress device, routing and annunciation testing
- Intercom station and control room console faults
- Interfaces to paging and radio systems checked after any change
Change control and testing
Changes are agreed in advance, made in a defined window and proven by test before an area is handed back. Nothing is left for a night shift to discover.
- Written scope and rollback position before work starts
- Door-by-door verification after any controller change
- Results documented and handed to facility operations
Healthcare
Hospitals and healthcare facilities
A hospital does not close. Work is fitted around clinical operations, not the other way round.
Access control, video, nurse call, infant protection and duress systems run in the same corridors as patient care. Service work is planned around ward activity, procedure schedules and shift change, and it is kept quiet. A panel opened in an occupied unit is contained, supervised and closed the same visit wherever possible.
Sensitive areas carry their own access rules: pharmacy, maternity, mental health units, records storage. We work to the rules the facility already has rather than proposing new ones part way through a repair.
Most hospital work involves three groups at once. Server and network changes touch IT. Door hardware and power touch facilities. Operator procedure and credentials touch security. Getting all three into the same conversation before the work starts is usually what decides whether it goes well.
- Continuous operation. Changes staged so recording, door control and duress annunciation are never all down at the same time.
- Minimal disruption. Contained work areas, quiet methods in occupied space, infection control requirements observed where they apply.
- Coordinated approvals. Security, IT and facilities aligned on scope and timing before anything is touched.
- Accurate documentation. What changed, what was tested and what remains open, written down for whoever opens that panel next.
Banks and financial institutions
Confidentiality is the default and the audit trail is part of the deliverable. A change that cannot be evidenced later is not finished.
Confidentiality
Site layout, alarm behaviour, camera coverage and access configuration stay inside the engagement.
- Non-disclosure obligations observed as written
- No site or client detail carried into other reporting
- Technician conduct suited to a public banking floor
Audit awareness
These systems are examined by internal audit and by regulators. Programming changes are recorded so they can be traced back to a request and an approver.
- Change requests logged and referenced in the work record
- Operator permission and clearance reviews
- Retention settings verified against the site policy
Controlled access
Work in vaults, cash handling areas, ATM enclosures and server rooms runs under supervision and to the institution’s own dual-control rules.
- Escorted and supervised work in restricted areas
- Dual-control procedures respected without exception
- Restricted-area work scheduled outside customer hours where required
Redundancy and structured execution
Financial sites usually run redundant servers and communication paths. They are worth having only if the failover has been tested.
- Redundant server and database replication checks
- Scheduled failover testing with recorded results
- Repeatable service execution applied the same way across branches
Data centres
Data centres and colocation facilities
Availability is the product. Security systems in a data centre are held to the same uptime expectations as everything else in the building.
Access control here is not a door. It is a documented chain of custody: perimeter, lobby, hall, cage, cabinet, each with its own credential and its own record. Anti-passback, mantraps, biometric readers and turnstiles are normal, and they usually fail by locking legitimate people out rather than letting anyone in.
Server and network coordination matters more than in most environments. Security application servers share infrastructure, address space and change windows with the facility’s own operations. Work is submitted, approved and executed inside that process, using the site’s method of procedure format rather than ours.
Nothing is done live that can be done in a maintenance window. Where a change has to be made during operating hours, it is staged so the system degrades to a known state instead of an unknown one. See Security Server and Infrastructure.
- High availability. Redundant servers, replicated databases and failover paths configured and then proven.
- Change management. Written method of procedure, defined window, rollback position, verification after the change.
- Controlled technical access. Escorted work in halls and cages, cabinet access logged, no tools left unattended.
- Reader and portal faults. Anti-passback errors, biometric enrolment problems, turnstile and mantrap interlock behaviour.
Government and public sector sites
Procedure is not overhead on these sites. Conduct, documentation and compliance with site rules are part of the work being bought.
Professional conduct
Identification, sign-in, escorts, badge return, and behaviour appropriate to an occupied public building. Technicians work to the site rules as written.
- Screening and clearance requirements met before attendance
- Sign-in, escort and badge procedures followed
- Work carried out with minimal presence in public areas
Documentation
Public sector sites keep records for a long time and change staff more often than private ones. Written detail is what survives.
- Written scope, method and result for every visit
- As-left configuration recorded panel by panel
- Reports formatted for internal record keeping
Confidentiality and compliance
System configuration, coverage and known weaknesses are treated as restricted information and handled to the site’s own policy.
- Site information handled under the site’s information policy
- Nothing released without written authorization
- Procurement, invoicing and reporting requirements respected
Complex and legacy systems
Government buildings accumulate systems. Three access control generations, two video platforms and an intercom nobody has documentation for is a normal starting point.
- Legacy controller and server support kept running
- Undocumented systems surveyed and written up
- Phased migration planned around budget cycles
Education
Schools and school boards
A board is not one site. It is dozens of buildings, mostly the same, all slightly different.
The work is multi-site by nature. A controller offline at one school, a stuck door contact at another, a front entrance intercom that will not release at a third. Efficiency comes from standardization: the same controller configuration, the same door naming, the same reader type and the same schedule structure across the board means any technician can walk into any school and know what they are looking at.
Most calls are a familiar handful of faults. Controllers that lost communication after a network or VLAN change. Entrance intercom and release problems. Readers that stopped reading. Schedules that did not follow a calendar change. Cameras that never came back after a power event.
Maintenance is best scheduled around the school calendar. Summer, March break and professional activity days are when panels can be opened without a corridor full of students. See Preventive Maintenance and Service Agreements.
- Multi-site support. Consistent service across many buildings under one board-level arrangement.
- Standardization. Naming, configuration and hardware kept the same site to site so faults are found faster.
- Controller and communication troubleshooting. Panels lost after network changes brought back and documented.
- Scheduled maintenance. Inspection and testing planned around the school calendar.
- Clear reporting. One report per site, in a form the board can compare year to year.
Steel plants and industrial facilities
Heat, dust, vibration, electrical noise and distance. Equipment that behaves in an office fails here in ways that look intermittent for months.
Harsh operating environments
Enclosures fill with dust, contacts corrode, camera housings foul, power is dirty and grounding is rarely simple. Diagnosis starts with the environment before the device.
- Enclosure sealing and thermal problems
- Grounding, surge and induced noise faults
- Corrosion and contamination on contacts and connectors
- Replacement hardware chosen for the conditions it will sit in
Large sites and long distances
Runs between buildings pass the limits of copper, so fibre, media converters and wireless links become part of the access control system whether that was planned or not.
- Fibre and media converter troubleshooting
- Long-run communication faults between buildings
- Gate, perimeter and remote building controllers
- Path and interference problems on wireless segments
Legacy infrastructure
Plants run equipment well past its stated life because replacing it means stopping production. The job is to keep it working until a shutdown makes replacement possible.
- End-of-life controller and server support
- Spares strategy for obsolete hardware
- Migration planned around scheduled shutdowns
Coordination with plant operations
Work is arranged around production, permits and safety rules. Site orientation, permits and lockout requirements are part of the schedule, not an interruption to it.
- Site orientation and permit requirements met
- Work windows aligned to production and shutdown schedules
- Coordination with plant electrical and maintenance groups
Also served
Commercial and institutional properties
Office towers, campuses, utilities, transportation and multi-tenant buildings run the same enterprise platforms on a smaller footprint.
The picture is usually familiar. An enterprise access control head end, a few hundred doors, a camera estate that grew one project at a time, and a property or facilities manager who inherited all of it without documentation. The work tends to run in that order: survey first, then a short list of what is genuinely broken, then a maintenance schedule that stops it recurring.
See Services for the work itself, Systems We Support for platforms within our experience, and Case Studies for anonymized examples of how these jobs actually ran.
Confidentiality and discretion
Facility details, system configuration, camera coverage, door counts and known weaknesses stay private. Skyfal does not discuss one client’s systems with another.
Client identity is confidential. Skyfal does not publish customer names, logos or site references without written authorization. Where an example is useful, it is anonymized first. See Case Studies.
Non-disclosure agreements, site policies and screening requirements are followed as written. Where a site rule conflicts with how we would normally work, the site rule wins.
Tell us about the environment, not just the fault
The constraints of the building usually decide how the work has to run, so that is the place to start.