StudioFSE® Framework
Methodological Architecture for Performance-Based Fire Safety Engineering.
Conceptual Foundation
Fire Safety Engineering is not a sum of independent checks, but a structured discipline in which safety emerges from the interaction between fire phenomena, human response, engineering protection systems, and governance and regulation.
The StudioFSE® Framework formalizes this structure in coherence with the international conceptual architecture developed within ISO/TC 92/SC 4.
Safety does not result from isolated checks, but from structural balance between phenomena, response, and governance.
Structural Model
The Framework is represented through a non-sequential, multi-level concentric structural model based on simultaneity and interdependence.
The diagram does not represent an operational sequence, but a permanent disciplinary structure based on simultaneity and interdependence.
Level 1 — Fire Dynamics
It represents the physical fire phenomenon: combustion processes, heat release, smoke production, and thermal interaction with the built environment. Domain: Fire Dynamics.
Level 2 — Knowledge & Modelling
It provides the scientific knowledge and analytical tools required to understand and predict fire behaviour. Domains: Fire Modelling & Simulation; Experiments & Validation; Digital Tools & Computational Methods.
Level 3 — Protection Engineering
It represents the engineering strategies used to control fire development and mitigate its consequences. Domains: Structural Fire Engineering; Fire Protection Systems; Smoke Control & Ventilation; Explosion Safety.
Level 4 — Human Response & Governance
It represents the interaction between occupants, organizational context, and regulatory framework within which fire safety strategies are implemented. Domains: Evacuation & Human Behaviour; Codes & Standards & Regulation; Risk & Safety Management; Applications & Building Types.
Life Safety sits at the center of the system. The model is systemic: dimensions are mutually dependent and not arranged as linear steps.
Structural vs Procedural Representation
The structural model does not replace procedural workflows. Workflow diagrams describe process logic (steps, decision nodes, and iterations); the framework defines the disciplinary connections that must remain active throughout project development.
Workflow indicates how to proceed. The framework defines what must remain structurally connected.
Systemic Integration
Safety solutions are not evaluated as isolated technical checks. Any intervention on fire phenomena, human response, or governance conditions modifies the performance field of the entire system.
Performance-based design therefore requires systemic coherence and control of disciplinary interdependencies.
Operational Implementation
Operational implementation translates the disciplinary architecture into an applied structure including: definition of performance objectives, scenario construction, CFD modelling, evacuation analysis, assessment of mitigation strategies, structural fire verification, and systemic consistency checks.
The objective is not execution of independent phases, but preservation of technical coherence across domains throughout the project process.
Modelling Infrastructure
The Framework includes a modelling infrastructure developed over more than twenty years of computational engineering work: structured CFD workflows, advanced pre- and post-processing, integration with FDS (NIST), and procedures in the OpenFOAM/fireFOAM ecosystem.
It also includes semi-agent evacuation modelling in SFPE-oriented settings, smoke management analysis consistent with major standards, and structured traceability of modelling data.
These are technical working environments, not commercial software products.
Verification and Consistency
The Framework integrates internal consistency checks, scenario validation, performance margin evaluation, and structured technical documentation.
The objective is not simulation alone, but disciplinary control of performance-based fire safety design.
Technical Notes
Applied methodological references and specialist discussions are available in the Technical Notes archive.