SOLIT² virtual fire test
Your nozzle system in the SOLIT² test gallery: Class A (a 150 MW HGV mock-up, covered) and Class B (diesel pools), at both airflow speeds of the protocol, with the activation time, ambient and fire growth the PMC sets.
For tunnel fire-safety and MEP teams, and the PMC who review them
SOLIT Simulator runs the SOLIT² virtual fire test for your water-mist system, checks the design against 86 clause rules, and gives your PMC a report they can read, with the evidence behind every number stated.
01 The problem
Whatever surprises a test holds, they arrive after the nozzles are chosen, the pipework is drawn and the PMC has asked for evidence. SOLIT Simulator moves the first look earlier: you see how your system is likely to behave in the SOLIT² test, which criteria it leans on, and which clauses still lack evidence, while the design can still change.
02 How it works
Enter the tunnel, the pipe network and pump, the test conditions the PMC sets, and the nozzle as the tester measured it. The tunnel is drawn as you enter it, in section, plan and isometric, with its measurements. Nothing about the nozzle is assumed: a field left empty is reported as not set.
Tier 1, the reduced-order engine, runs the SOLIT² virtual test in seconds over the worst cases of its envelope: heat release, temperatures, visibility and dose against the limits your authority set.
Run FDS CFD on rented cloud machines and read it beside the prediction. Where the two disagree, the disagreement is reported, not hidden. In beta: not yet generally available.
A clause-by-clause compliance check and a virtual fire test report for the PMC / Authority's Engineer, with what is evidenced, planned or only predicted kept apart.
03 What it does today
Your nozzle system in the SOLIT² test gallery: Class A (a 150 MW HGV mock-up, covered) and Class B (diesel pools), at both airflow speeds of the protocol, with the activation time, ambient and fire growth the PMC sets.
Limits come from the project's own authority, each entered with the document and clause it comes from. Each is explained in plain words: what it protects (people escaping, the structure or the ventilation design) and how it is judged. A criterion with no limit reads "not judged", never "passed", and a score appears only when every limit is set.
A project holds the tunnel, the fire, the ventilation and the authority's limits once. Each alternative design is run against that same base, so a reviewer compares like with like.
High, intermediate and low-pressure water mist, and deluge, each with its pressure band from NFPA 750. The engine is calibrated on high-pressure water mist only; the other three say on screen that they are not validated.
86 clause rules across the SOLIT² test protocol and a project rules file. Failing, evidenced and "needs evidence" are counted separately, and needs evidence is never counted as compliant.
A virtual fire test report with the issuer, the organisation and the issue time on every page. View it, or download it as a PDF.
E0 (illustrative) to E4 (full-scale test), with the track record of the quantity behind each figure, so a reviewer sees how far to trust a number before relying on it.
Enter your own tunnel (bored or cut and cover, circular or box, one to four bores), hydraulic components and installed pump. Saved tunnels can be edited and reused. The result shows pump pressure, losses, plant size and the pipe and valve take-off, not only the fire.
Where a reduced-order prediction is not enough, run FDS CFD on rented cloud machines and read the result beside the prediction. In beta: not yet generally available.
Every account is approved by hand and works in its own workspace. Team and admin accounts sign in with a second factor.
04 The output
A report that states its footing on the first page. The sample alongside uses invented values, to show the layout only.
Evidence E1, a prediction on estimated nozzle data. Held at E1 by: Dv50 (estimated).
| Criterion | Value | Limit set by the authority | Verdict |
|---|---|---|---|
| Target ignited | No | Must not ignite | pass |
| Peak heat release | 38 MW | at most 45 MW | pass |
| Visibility, flooded zone | 9 m | at least 10 m | FAIL |
| Heat flux | 4.1 kW/m² | not set | not judged |
| Requirement | Found | Status |
|---|---|---|
| Activation time set by the PMC | Entered | Evidenced |
| Nozzle data stated by the tester | Estimated | Needs evidence |
| Fuel load matches the specified mock-up | Differs from the specification | Fails |
Example page with invented values. Not a result, and not a prediction for any project.
05 In the product
Screens show an illustrative example design at evidence level E0, not a real project, with example test conditions typed in so the simulation can run. No figure on them is a result.
06 Evidence
Each result carries an evidence level from E0 to E4. The tool computes E0 to E2 today. E3 and E4 are drawn on every ladder and never awarded yet.
A nozzle input is a placeholder or unstated.
Computed todayA prediction on estimated nozzle data.
Computed todayA prediction on measured nozzle data (Tier 1).
Computed todayTier 2 CFD agrees within the stated tolerances.
Not yet awardedA full-scale test compared with this prediction.
Not yet awardedA result is held at the level its least-evidenced nozzle input allows, and says which inputs hold it there.
07 Read this before you rely on it
08 Who it is for
Test a system choice and a layout against the SOLIT² test before the design is frozen, and see which criteria it leans on.
Size the plant to the tunnel you have: pump pressure, ring main and zone losses, tank, pumps, and the pipe and valve take-off.
Read one report that says what is evidenced, what is only planned or predicted, and what no limit has been set for. Every limit shows the document and clause that set it.
09 CFD pricing
CFD runs on rented cloud machines: you pay for the machine time a run uses, from prepaid credit, with no subscription, and the price is fixed when a run starts.
Pricing for CFD runs is shown to registered users inside the app.
Taxes, where applicable, are shown on the invoice.
10 Beta programme
11 Questions
No. The engine is calibrated against published reference tests, not validated, and every result says so on screen. Treat each figure as a prediction until a full-scale test of your system exists.
No. It does not replace a full-scale test; it helps you reach one with a design that has been checked. The SOLIT² test protocol (§3.4) says CFD shall not replace full-scale testing.
Tier 1 is the reduced-order engine that runs a whole SOLIT² test in seconds. Tier 2 is CFD with FDS, run on demand and in beta. Where the two disagree, the disagreement is reported, not hidden.
Yours. The nozzle is entered by the tester and nothing about it is assumed. Where a value is an estimate rather than measured, the result says so and holds its evidence level down. To see a whole design run first, you can start from an illustrative placeholder head: it is marked placeholder and the result stays at the lowest evidence level.
High, intermediate and low-pressure water mist, and deluge. The pressure bands follow NFPA 750. The engine was calibrated and checked on high-pressure water mist; for the other three the result says it is not validated for that type.
The SOLIT² virtual fire test, with clause checks against the protocol's requirements and a project rules file you supply.
By the machine time a run uses, paid from prepaid credit, with the price fixed when the run starts. Pricing for CFD runs is shown to registered users inside the app.
No. SOLIT Simulator is a product of Darvish Consultants and is not affiliated with or endorsed by the SOLIT² project.