Fire & Safety · Engineering & design

Develop a reviewed fire design

Review drawings, specifications and adopted codes in one workspace, from design basis to drawing issue. AI prepares evidence for your engineers to check and approve.

Each capability runs standalone Uploads or manual entry Named engineer signs every issue
Harbourview Mixed Use CentreBasement plant area + retail podium · Drawing set Rev B
Awaiting engineer sign-off
  1. Design basis & conceptCriteria register approved by engineering manager
    Approved
  2. Code & specification compliance1 clause conflict open · 38 of 41 obligations evidenced
    Sign-off
  3. Product & equipment selectionHard filters applied · certificate scope check running
    Working
  4. Drawing automationWaits for approved criteria and product shortlist
    Queued
  5. Intelligent drawing reviewCross-discipline review of the issued layout
    Queued
spec section 4.2 conflict · awaiting engineer disposition
Exception · Requirement conflictCritical

Project specification cites an older edition than the adopted code

Spec section 4.2 · Rev BDesign to the referenced standard, earlier edition.
AHJ profileLater edition adopted with local amendments.
Owner: Lead fire engineerPrecedence not assumed
Conditions confirmed by engineer24 / 27
Open exceptions before issue3
Who uses it
Fire, compliance and design engineers, CAD/BIM designers
Lifecycle stage
Engineering / Design, also concept design for tenders
Works from
Your drawings, specifications, codes and product data
Sign-off
A named engineer approves every issued output
What changes

Bring design evidence into one record

Design decisions sit across drawing revisions, specification clauses, catalogs and email. Each handoff is a place where a conflict or an unstated assumption slips through.

Today

Evidence scattered across tools and inboxes

With the use case

One source register, every fact traceable

  • Architectural plan A-201Rev B · p.3Confirmed
  • Specification section 4.2Rev BConflict
  • Water supply dataNot suppliedInput needed
  • Sprinkler datasheetRev 07Current
  • Drawing issue 014Rev C · C/4Assigned
TaskTodayWith this use case
Building the design basisEngineers hunt across drawing revisions, specs and email threads, then rewrite the reasoning into a report by hand.Every fact sits in one register with its drawing, page, revision and review status, ready for a controlled basis report.
Conflicting requirementsA specification citing an older edition is noticed late, sometimes after procurement.Both clauses appear side by side, an owner is assigned and the engineer's determination is recorded.
Choosing equipmentCertification scope, pressure rating and expiry are checked datasheet by datasheet.Hard filters apply your approved criteria and flag certificate scope or expiry before anything reaches the shortlist.
Drafting layoutsRepetitive device placement is redrawn for every revision and drifts from the reviewed criteria.A proposed layout follows your CAD/BIM standards, with clash and coverage prompts for the designer to resolve.
Reviewing drawingsFire and MEP conflicts across large sets live in markups and spreadsheets that lose their location.Each issue carries sheet, revision, coordinates, owner, decision and an image crop of the evidence.
A new revision landsApproved decisions quietly go stale.The approved record stays intact, an impact item opens and only affected criteria go back for reapproval.
What it does

Five capabilities, one approved design record

Start with the capability your team needs most. Each one works on its own uploads, and each passes approved data to the next when you connect them.

Design basisFire engineer + engineering manager

Turn project inputs into a traceable, approved design basis

Confirm occupancy, spaces and hazards from the drawings, compare feasible protection concepts and issue a criteria register where every value points back to its source.

AI suggests

  • Rooms, occupancy signals and hazards from plans and specs
  • Relevant clauses from your configured requirements
  • Candidate system concepts with assumptions and unknowns

Rules automate

  • Revision register and superseded files
  • Completeness checklists and approval routing
  • Template population and versioned export

Your engineers decide

  • Confirm each material fact
  • Select, change or reject a concept with reason
  • Manager approves the controlled basis
plantroom B-04 hazard candidate from A-201 Rev B, p.3 confirm
water supply flow and pressure not supplied input required
concept B rejected by lead engineer, reason recorded logged
What you get

Design basis report: project profile, applicable requirements, assumptions, option reasoning, criteria register, open actions, sign-offs and evidence manifest.

Workflow

One approved basis, carried from first upload to issued drawing

Automated steps prepare the evidence. People make the calls. Work cannot move past a gate while a critical exception is open.

  1. Register the evidence

    Register drawings, specs and requirements with revisions.

    AutomatedEngineer

  2. Confirm project conditions

    Check spaces, occupancy and hazards on the linked drawing.

    Fire engineer

  3. Set requirements and assess

    Map adopted codes and editions to evidence and conflicts.

    Compliance engineer

  4. Approve concept and criteria

    Compare concepts, record reasons and issue the controlled design basis.

    Approval gateManager

  5. Shortlist certified products

    Filter the catalog, check certificate scope and approve the shortlist.

    Selection engineer

  6. Generate and adjust layouts

    Draft devices and routing, resolve clash and coverage prompts.

    AutomatedCAD/BIM designer

  7. Review and issue drawings

    Review issues, verify fixes and release approved drawings.

    Approval gateEngineer
Prepared or reviewed stepApproval gate with named sign-off
At a glance

What goes in, what comes out

Everything you bring flows through one controlled use case. Hover or tap an input to see which outputs it feeds.

You bring

DrawingsArchitectural, MEP and fire PDFs; DWG, IFC or RVT where validated
Specifications and fire strategyProject specs, client criteria and the drawing register
Applicable requirementsAHJ, adopted editions, amendments and licensed clause excerpts
Product dataDatasheets, certification records and approved vendor list
Your drafting standardsCAD/BIM layers, symbols, families and title blocks
The use case AI Fire Design, Compliance & Automation
  • Design basis & concept
  • Code & spec compliance
  • Product selection
  • Drawing automation
  • Drawing review
2 approval gatesFull audit trail

You get

Controlled design basis reportCriteria register, option reasoning, sign-offs and evidence manifest
Compliance matrixClause by clause, with evidence links and open AHJ questions
Technical product shortlistModel, datasheet revision, certification scope and rationale
Draft drawings and schedules2D/3D layouts with revision clouds and review notes
Drawing issue registerLocated issues with owner, decision and image crop
Who it is for

Built around the people who sign the design

Each role sees the evidence it needs and approves only what it is authorized to approve.

Confirms and selects

Fire engineer

Checks conditions, compares concepts and resolves sourced exceptions.

Interprets

Compliance engineer

Sets editions, maps evidence and decides conflicting clauses.

Shortlists

Product selection engineer

Checks catalog choices and certificate scope against approved criteria.

Drafts

CAD / BIM designer

Adjusts the proposed layout to approved criteria and site obstructions.

Reviews

Drawing reviewer

Works through located cross-discipline issues and verifies each fix on the revised sheet.

Approves

Engineering manager

Reviews exceptions, approves the basis and drawing issue, and audits changes.

Designed for

Fire protection consultantsMultidisciplinary MEP consultantsSpecialist fire contractorsDesign and build contractorsOwners with in-house engineeringTeams working across several AHJs
Scope & limits

What this software will not do

Fire safety decisions carry professional liability. Every decision in the use case stays with a named engineer, on the record.

How every output moves from AI suggestion to an issued document

  1. AI analysisAutomated
  2. Draft recommendationMarked as draft
  3. Engineer reviewAccept, edit or reject
  4. Manager approvalWhere configured
  5. Controlled outputVersioned snapshot
  6. Audit trailWho, what, when, why

It does not decide compliance

An engineer decides compliance. Evidence gaps and conflicts stay visible; incomplete coverage has no compliance score.

It does not stand in for an authority

An internal approval records your team’s decision. It never implies consent from the authority having jurisdiction.

Nothing is issued without a named reviewer

AI output stays marked as draft. An unverified fact or an open critical conflict blocks the issue gate.

It does not do sealed engineering

Your engineers and validated tools own calculations, final layouts and sealed designs. Unknown values remain marked.

It does not pick precedence for you

When two requirements disagree, both are shown. Precedence applies only where your project basis defines it.

Your standards, not ours

NFPA, EN, BS, ISO, FM, UL, LPCB and local Civil Defence rules are examples. Only the editions you configure and supply are applied.

Standalone first

Each capability runs on its own uploads and manual entries. No other module is a prerequisite.

Connects when you are ready

Optional links to document management, SharePoint, AutoCAD, Revit and IFC, each with mapped fields and agreed data ownership.

Your data stays yours

Separate tenants and projects, role-based access and encryption at rest and in transit. Model training requires written permission.

Example project

A ten-minute walkthrough of Harbourview

Design basis4.5 min Compliance1.5 min Products1 min Drawings1.5 min Approval1.5 min
Demo scenario · sample project

A mixed-use center with a basement plant area and a retail podium

The walkthrough follows one revision of one project through all five capabilities and shows how each decision traces back to its source.

Drawing setRevision B
ZonesPlant + retail
Exceptions shown4
Sign-offs2 gates

  1. Open the project at Revision B

    The source register shows current and superseded drawings, and who uploaded each one.

    Design basis

  2. Correct an AI-suggested occupancy marker

    The engineer opens the linked plan, fixes the plantroom description and confirms the fact.

    Design basis

  3. Compare two protection concepts

    The missing water supply parameter stays visible as an explicit unknown. One concept is rejected with a reason.

    Design basis

  4. Resolve an edition conflict

    Compare the specification and code, request clarification and record the disposition.

    Compliance

  5. Set aside a sprinkler model

    Its certification scope is unverified for the location, so the alternative moves to the shortlist with its datasheet.

    Product selection

  6. Adjust the auto-placed layout and review it

    Move devices around a soffit, reject a false symbol and assign the moved-door issue.

    Drawing automation Drawing review

  7. Approve and preview the controlled package

    The manager reviews the revised assumption, approves, and the basis report and issue register are generated with their source manifest.

    Approval gate
Pilot evaluation

Agree the measures before the pilot

We agree a baseline with you first, then compare. We do not promise a number before your own data shows it.

  1. 1
    Agree a baselineYour current process, measured the same way
  2. 2
    Run the pilotOne system type in one agreed jurisdiction
  3. 3
    Compare on your dataSame measures, same denominator, reported openly

Basis preparation time

Working time from complete intake to an engineer-ready draft basis.

Source traceability

Criteria and findings linked to approved source revisions.

Exceptions at issue

Open material exceptions at issue and median time to disposition.

Certification evidence

Selections with valid certificates; rejects before submittal.

Drawing rework

Manual corrections per sheet, reissues and issues reopened after revision.

A first pilot validates one system type in one agreed jurisdiction before wider claims.

Getting started

Define a pilot with your team

  1. Review the requirements

    We send the consolidated requirements for the use case and its five capabilities.

  2. Review the workflow example

    Review the example workflow, its records and approval points with your team.

  3. Confirm the project scope

    We map your systems, jurisdictions and the capability to start with.

  4. Define the pilot scope

    Your codes, templates, approvers and sample drawings define the pilot.

  5. Pilot

    Evaluate against your baseline

    One system type, one jurisdiction, measured on the agreed pilot measures.

Continue exploring

Also in Fire & Safety

Pre-sales & tendering

Pre-Sales Estimating & Quotation

Measure quantities, build sourced estimates and prepare quotations for approval.

Explore the use case Project delivery

Submittal & Commissioning

Review submittals, track materials and record commissioning in one delivery record.

Explore the use case Inspection & service

Inspection & Asset History

Capture inspection evidence, review findings and keep a history for each fire asset.

Explore the use case Business operations

Fire Operations Intelligence

Connect source data, approved metrics and dashboards to reviewed management actions.

Explore the use case

FAQ

What does the fire design workflow cover?

It connects the design basis, code evidence, product selection, draft layouts and drawing review. Engineers review the evidence and approve the relevant design outputs.

Can we use part of the design workflow or run it end to end?

You can scope one capability or connect all five into an end-to-end design workflow. Agree the inputs, source revisions and approval handoffs for the complexity of your project.

How are project codes and standards established?

Record the authority having jurisdiction, adopted editions and amendments, and provide the licensed clause excerpts needed for review. Missing evidence remains a gap for the engineer to resolve.

What happens when a drawing revision changes the design?

The approved record is retained. Changed conditions are highlighted and affected criteria, products or drawings are routed back for review and reapproval.

Who approves the design and calculations?

Your competent engineers approve design decisions. Hydraulic calculations and sealed drawings remain with the validated tools and authorized professionals responsible for them.

What should we bring to a design pilot?

Bring a representative drawing set, specifications, adopted standards and the review outputs your team needs. Validate file formats and the quality of extracted information on those samples.