Ventilation, SCADA, life safety, traffic systems

    Commissioning software for tunnels and highways where the road authority will not accept an assumption.

    Tunnels and major highway schemes carry life-safety consequence in their ventilation, fire and SCADA systems, and a road or transport authority that inspects every claim before it signs. Deskely holds ventilation, fire life safety, SCADA, traffic management and lighting as linked subsystems, so integrated systems testing is run and evidenced against a fixed acceptance framework.

    Systems
    Ventilation, SCADA, fire, traffic
    Test
    Integrated systems testing
    Authority
    Road/transport body sign-off
    Gate
    Authority acceptance
    TUNNEL SECTION 4 — 2.1KM BORETUNNEL SYSTEMS RECORD SET · REV CBORE 2 — 3.4 KMJF-CH1200EGRESS CROSS-PASSAGEfan test openTAG REGISTERMG-VIE-02Jet fan, section 4 ventil…Records signedSMK-EX-01Emergency smoke extract f…In testBMS-CTRL-07SCADA tunnel controllerPreservationSIG-IF-04SCADA to fire panel inter…Punch open48 unitsunder one system hierarchy

    The problem

    Dozens of subsystems have to behave as one system, on command, under fire scenarios.

    A tunnel brings together jet fans, dampers, CCTV, variable message signs, fire detection, SCADA, emergency communications and traffic management, each installed and tested by a different specialist.

    The road or transport authority does not accept individual test certificates in isolation; it requires proof that the systems respond correctly together, scenario by scenario, before it will accept the asset.

    Deskely models each subsystem and its cause and effect relationships explicitly, so integrated systems testing evidence is structured the way the authority actually reviews it.

    SUBSYSTEMS THAT MUST BEHAVE AS ONERoad tunnel, fire scenario testVentilation, fire detection, SCADA and traffic signals each pass alone, then have to trigger togetherVentilationFire detectionSCADATraffic signalsEach subsystem passes its own factory and site test in isolationFire scenario — cause and effectSCENARIO TEST FAILS, EACH VENDOR BLAMES THE INTERFACE4 vendorsone cause-and-effect matrix, no shared witness record1 matrixwitnessed, scenario by scenario, in one recordDeskely tracks scenario-based cause-and-effect testing as one witnessed record set across every vendor.

    Setting up the register

    Ventilation, fire, SCADA and traffic are linked subsystems, not separate projects.

    Jet fans, dampers, extraction points, detection zones, SCADA points, CCTV, VMS, emergency telephones and traffic management assets are tagged by chainage or section and grouped into their systems.

    Cause and effect matrices are held as structured data against the devices they connect, so a fire scenario's expected fan and damper response is a query rather than a document cross-reference.

    Drawings, SCADA point lists and cause and effect schedules are parsed into that structure, keeping the register aligned with the design intent documents the authority will audit against.

    1 · SOURCE DOCUMENTSVentilation strategy rev…12 zonesJet fan and vent equipme…48 unitsFire life safety cause a…212 interfacesSCADA point schedule3 960 pointsPARSE + MATCHtag · description · drawing ref2 · ONE TAG REGISTERMG-VIE-02Jet fan, section 4 ventil…VENT ZONE 4SMK-EX-01Emergency smoke extract f…VENT ZONE 4BMS-CTRL-07SCADA tunnel controllerCONTROLSSIG-IF-04SCADA to fire panel inter…LIFE SAFETYTWO DOCUMENTS DISAGREEVentilation strat…SCADA tunnel controllerJet fan and vent …Abbreviated descriptionEngineer picks the sourcedecision loggedWeeks of transcription become a draft an engineer reviews.

    Execution

    Pre-functional checks feed integrated testing, scenario by scenario.

    Each device is proven individually first — jet fan rotation and vibration, damper stroke, detector response, SCADA point-to-point verification — before it is included in an integrated test.

    Integrated systems testing is then run scenario by scenario, with the actual system response recorded against the expected cause and effect outcome for each one.

    Traffic management systems, lighting and CCTV coverage are verified against the same chainage structure, so a section's readiness reflects every system that operates in it.

    FIRE CAUSE-AND-EFFECT WITNESS LADDERScenario testing, ventilation + SCADASubsystem factory tests witnessedVentilationFireSCADATrafficSite pre-functional checksVentilationFireSCADAScenario 1 — fire in bore, jet fansFireSCADAScenario 2 — traffic closure interlockSCADATrafficSafety case witness sign-offRegulator2 of 5scenarios witnessed and signedScenario testing gates the safety case; nothing above is skipped for schedule.

    Authority acceptance

    Acceptance is a dossier built from evidence, not a claim made at a meeting.

    The authority acceptance package is assembled from the same device and scenario records used during testing, with every signature carrying a name, role and timestamp.

    Any deviation between expected and actual scenario response is logged as a punch item with a category and an owner, so it is visible before the authority finds it during their own witness testing.

    The maintaining authority receives an asset register with full test history, settings and cause and effect logic intact, which is what supports safety case reviews long after opening.

    Ventilation zone 4 — opening certification ladderCertification issues only from signed integrated test recordsICInstallation completeRecords signed 06 SepJet fan installation records48 / 48 signedInterface proving recordscompleteISTIntegrated systems testIn test — witnessed by fire authorityCause and effect witnessed182 / 212Jet fans proven at dutyconfirmedOCOpening certificationPunch open — 9 itemsBlocking punch9 openHighways authority sign-offnot witnessed

    How it runs

    From individual devices to an authority-accepted asset.

    Tunnel and highway schemes are dominated by proving systems together, which is exactly where structured cause and effect data earns its keep.

    1. 01

      Model by chainage and system

      Ventilation, fire, SCADA, CCTV, VMS and traffic assets tagged by section and grouped into their systems.

    2. 02

      Hold cause and effect as data

      Expected system responses to each scenario recorded against the devices involved, not just described in a document.

    3. 03

      Run device tests, then scenarios

      Individual device pre-functional checks completed first, then integrated systems testing recorded scenario by scenario.

    4. 04

      Assemble the acceptance dossier

      Authority acceptance package built directly from signed device and scenario records, with deviations tracked as punch.

    FAQ

    Questions about Tunnels and highways scopes.

    Ready to digitize
    commissioning and
    handover?

    We use cookies to improve your experience.
    You can opt out of certain cookies.
    Find out more in our privacy policy.