SOLAS II-2/17: The Alternative Design Route

Through Regulation 17, the fire-safety chapter's own escape hatch. SOLAS Chapter II-2 Regulation 17 permits a design to deviate from the chapter's prescriptive requirements where an engineering analysis demonstrates equivalent safety. It has been available since the revised Chapter II-2 entered into force on 1 July 2002, and it is the route any detection arrangement that does not look like a conventional point-detector layout has to travel.

What Regulation 17 actually permits

Deviation from prescription, not from the objectives behind it. A design may depart from the prescriptive requirements of Parts B, C, D, E or G of Chapter II-2 provided it still satisfies the fire safety objectives and functional requirements the chapter sets out. Part F is not in that list for the obvious reason that Part F is where Regulation 17 itself sits.

That scope matters for detection specifically. Detection and alarm requirements live in Part C, with the technical detail carried in the FSS Code, so a novel detection arrangement is squarely inside what Regulation 17 can be used for. What it cannot do is lower the bar: the analysis has to show an equivalent level of safety with regard to the fire hazards involved. It is a different route to the same destination, not a discount.

What the submission has to contain

A defined package, and the specificity of it is the point. Regulation 17 requires the engineering analysis submitted to the Administration to identify the ship type and the spaces concerned, and to state precisely which prescriptive requirements the design will not meet. Vagueness about what is being departed from is not an option — the deviation has to be named before it can be justified.

• Hazard identification covering possible ignition sources, fire growth potential, the generation of smoke and toxic effluent, and the paths by which fire spreads.
• Performance criteria that are quantifiable and measurable, and that provide a degree of safety not less than that achieved by using the prescriptive requirements.
• A detailed description of the alternative design, including the assumptions it rests on and any operational restrictions it depends on.
• The technical justification demonstrating that the design meets those criteria — the engineering analysis proper.
• Documentation sufficient for the Administration to evaluate the submission against the Organization's guidelines.

Read the second item carefully, because it is where most novel arrangements fail before they start. Quantifiable and measurable performance criteria cannot be assembled from datasheets. They require agreed metrics — what the system must detect, under what conditions, within what interval, with what confidence — and evidence that it does. That is a staged-test programme and a documented result set, not a specification sheet.

The two-stage analysis MSC/Circ.1002 sets out

The guidelines split the work in two, with an approval gate in the middle. MSC/Circ.1002, issued on 26 June 2001, gives the methodology for the engineering analysis Regulation 17 requires. The first stage defines the scope of the analysis, identifies the fire hazards, and develops the design fire scenarios and the trial alternative designs to be assessed. That work is written up as a preliminary analysis report, and that report requires approval before anything is evaluated against it.

Only then does the quantitative analysis run, evaluating the trial alternative designs against the agreed design fire scenarios. The sequencing is deliberate and worth respecting: an owner who commissions modelling before the scenarios and criteria are agreed has bought analysis against assumptions the Administration has not accepted. The guidelines were amended by MSC.1/Circ.1552, approved on 25 November 2016 at MSC 97 and prepared by the Sub-Committee on Ship Systems and Equipment at its third session, which added more specific guidance on applying Regulation 17 including life-safety performance criteria.

The obligations that outlive approval

Approval under Regulation 17 is a continuing condition, not a one-off certificate. A copy of the documentation as approved by the Administration has to remain on board the ship. Where the operational conditions or the assumptions underpinning the analysis change, the engineering analysis must be re-evaluated and re-approved by the Administration before those changes are implemented.

That clause has real operational teeth on a vehicle carrier. An approval premised on a stated cargo mix, a stated ventilation regime or a stated stowage practice is an approval that assumes those things hold. Change the cargo profile materially and the assumptions behind the analysis have moved, which is a re-approval trigger rather than a matter of judgement. Regulation 17 also requires Administrations to report approved alternatives to the IMO for circulation to Contracting Governments, so the approvals granted are visible to other flags rather than sitting in a single administration's file.

What it means for a detection arrangement

It means there is a defined door, and that the price of walking through it is evidence. A detection arrangement that does not match the prescriptive layout is not thereby non-compliant; it is a Regulation 17 case, and Regulation 17 has an established methodology, published guidelines, class guidance notes and a record of use. The question stops being whether a non-standard arrangement can be approved and becomes whether the applicant can produce quantifiable performance criteria and defend them against agreed design fire scenarios.

Practically, that reorders the work. The performance criteria and the design fire scenarios come first and get agreed; the staged testing is built to produce evidence against those specific criteria; and the documentation is assembled knowing it has to live on board and survive a change of operating assumptions. An evidence package built for a class review answers a related but narrower question — Regulation 17 is the flag-level route, and it asks for the analysis rather than only the test record.

Sources

• 1. SOLAS Chapter II-2, Regulation 17 — Alternative design and arrangements: permits deviation from the prescriptive requirements of Parts B, C, D, E and G where fire safety objectives and functional requirements are satisfied; engineering analysis submitted to the Administration must identify ship type and spaces, the prescriptive requirements not met, hazard identification (ignition sources, fire growth potential, smoke and toxic effluent generation, fire spread), performance criteria that are 'quantifiable and measurable' and provide 'a degree of safety not less than that achieved by using the prescriptive requirements', a detailed design description with assumptions and operational restrictions, and technical justification; approved documentation to be carried on board; re-evaluation and re-approval required where operational conditions or assumptions change; Administrations report approved alternatives to IMO for circulation.
• 2. IMO MSC/Circ.1002 (26 June 2001) — Guidelines on alternative design and arrangements for fire safety: methodology for the engineering analysis required by SOLAS II-2/17; scope definition, fire hazard identification, development of design fire scenarios and trial alternative designs, documented in a preliminary analysis report requiring approval before the quantitative analysis evaluates the trial designs against those scenarios.
• 3. IMO MSC.1/Circ.1552 (approved 25 November 2016, MSC 97) — Amendments to the Guidelines on Alternative Design and Arrangements for Fire Safety (MSC/Circ.1002), prepared by the Sub-Committee on Ship Systems and Equipment at its third session (14–18 March 2016); provides more specific guidance on the application of SOLAS regulation II-2/17 and contains life-safety performance criteria.
• 4. ABS — Guidance Notes on Alternative Design and Arrangements for Fire Safety: class-society guidance on preparing and submitting a Regulation 17 engineering analysis.