A senior fire engineer we work with runs the fire and life-safety review for a mixed-use tower in Dubai. The client is US-headquartered. The design lead is in London. The lenders sit in Frankfurt. The tower has to be defensible under UAE Civil Defence, NFPA (because the US owner requires it), IBC (because a subset of the anchor tenants are US-listed and their insurance requires it), ADA on the accessible route work, BS 9999 for the design house's own PI cover, and ISO 19650 for information-management conformance on handover.
Six frameworks. Six review cycles. Six formats.
Historically, six matrices means six re-authorings of the same design. The engineer opens the model, reads a value, writes it into the UAE spreadsheet. Opens the same model, reads the same value, writes it into the NFPA spreadsheet. Opens the same model a third time, reads the same value, writes it into the IBC spreadsheet. The value is the same value each time. The clause it satisfies is different. The format the authority accepts is different. The typography of the submission cover sheet is different.
Half of a fire engineer's week goes to that reformatting. The other half goes to running the actual analysis. The client pays for the analysis and gets billed for the reformatting.
The one-model, many-authority insight
The insight Signet is built around is that the model is the source of truth. The BIM model does not know or care which authority is going to review it. It stores the escape door clear width once, in a canonical unit, at a canonical precision. It stores the door leaf fire rating once. It stores the occupant load once, and the corridor width, and the sprinkler coverage, and the smoke exhaust rate.
Everything downstream from the model is derivable. The UAE FLSC compliance matrix is a derivation from the model. The NFPA 101 compliance matrix is a different derivation from the same model. The IBC 2021 matrix is a third derivation from the same model. Each derivation is defined by a rule pack that describes how the authority reads the world.
Rule packs are data. They are versioned, reviewed, and authored once. A jurisdiction updates its code, someone updates the rule pack, every future submission in that jurisdiction picks up the change. The engineer does not.
What a rule pack contains
A rule pack for a jurisdiction contains four things.
The clauses it enforces. Every requirement the authority publishes, expressed as a structured object with a clause number, a threshold, a unit, an applicability filter (occupancy classification, floor area, sprinklered/not, etc), and a citation back to the original code document.
The mapping from model to clause. For each clause, the specific BIM property or geometric derivation that produces the achieved value. Clear width comes from a measured door-leaf-to-frame calculation, not the nominal leaf width property. Travel distance comes from a routed path across the floor plan, not a straight-line distance.
The abstention criteria. Where the model does not contain enough information to derive a value, the rule pack specifies what evidence would resolve it. This is the cite-or-abstain rule made concrete per clause. UAE FLSC §8.4.3 needs a door schedule column that gives measured clear width; without it, Signet abstains and tells the reviewer exactly what upload would decide the clause.
The output format. The authority's own cover sheet, matrix layout, page numbering convention, and required attachments. UAE Civil Defence has a specific XLSX template. Dubai Municipality has a specific PDF layout with fire-strategy stamps in specific corners. Building Control in England has a different one. NFPA has a third. Each is a template on the rule pack.
Six matrices, one run
When the engineer runs the tower project through Signet, the following happens.
-
Perception runs once. Signet reads the BIM model and the fire strategy PDF and extracts every value it can cite verbatim. This step is the expensive one, and it runs a single time regardless of how many authorities are downstream.
-
Judgment runs per rule pack. For each of the six authorities (UAE FLSC, NFPA, IBC, ADA, BS 9999, ISO 19650), the deterministic engine walks the rule pack's clauses, reads the cited values from the perception layer, and scores each clause against the code threshold. The verdicts are byte-for-byte reproducible.
-
Verification runs per rule pack. The downgrade-only AI critic re-checks every pass in every matrix. Six matrices, six critics, each reading only its own rule pack's evidence. A pass that survives all six critics is a pass. A pass that any critic can downgrade is downgraded.
-
Sign-off runs per rule pack. The engineer reviews each matrix on its own, accepts the departures, and stamps. The engineer's stamp is per-matrix because the professional accountability is per-authority. The UAE submission needs a UAE-registered engineer's stamp. The NFPA submission needs the US-side reviewer's stamp.
-
Export produces six deliverables. UAE Civil Defence's exact XLSX plus branded cover PDF. Dubai Municipality's fire-strategy stamp layout. NFPA 101 matrix in the format the anchor tenant's insurer accepts. IBC review packet. ADA accessible-route audit trail. BS 9999 conformance matrix for the design house's PI file. ISO 19650 information delivery specification with the CDE handover.
The engineer's week that used to go to six reformatting exercises now goes to reviewing the six matrices side by side. The value the model contains is the same across all six. What differs is what each authority chooses to make load-bearing. Signet lets the engineer see the difference at a clause level, not at a re-typing level.
When the authorities disagree
The most interesting output of a six-authority run is the clauses where the authorities disagree. UAE FLSC accepts an escape door clear width of 800 mm minimum. BS 9999 accepts 850 mm minimum in the same occupancy. IBC accepts 815 mm minimum with a specific projection allowance. The design has 850 mm clear.
Signet passes all three. But it also surfaces the delta. The reviewer sees that the UAE and IBC clauses have headroom, and the BS 9999 clause is tight. That information is useful during design; a value change that would still satisfy UAE and IBC would break BS 9999. The traceability that lets the engineer prove the design meets six codes also lets the engineer see when the design is tight against any single one.
What ships
The tower project's submission binder used to be six documents assembled by hand, each authored in a different format, each traceable back to the model only through the engineer's own reconstruction. It is now six documents assembled from one run, each cited to the source clause and the source model geometry, each stamped by the accountable engineer, each accompanied by the Golden Thread audit trail the authority's own reviewer can query directly.
The engineer's week is spent on the two things that actually need judgement. The clauses where the model does not contain enough information, and the clauses where the authorities disagree. The typing is done by the software.
Send us a model and the list of jurisdictions it has to satisfy. We will run all of them in a live call and show you the six matrices side by side, with the abstention flags where the model is silent and the deltas where the codes disagree.