Fire product and equipment selection
A workflow that captures selection criteria, extracts attributes from catalogues, applies hard requirement filters and compares candidates side by side — with certification scope treated as a filter, not a footnote. A technical reviewer approves the shortlist.
Product selection engineerCatalogues are full of products that look interchangeable and are not.
-
Capture the criteriaEngineerQueuedWorkingDoneSign-off
-
Extract catalogue attributesAutomatedQueuedWorkingDoneSign-off
-
Apply hard filtersAutomatedQueuedWorkingDoneSign-off
-
Compare the candidatesAutomatedQueuedWorkingDoneSign-off
-
Route technical approvalReviewerQueuedWorkingDoneSign-off
- Who uses itProduct selection engineer, procurement technical reviewer
- Lifecycle stageEngineering / Design · also Pre-Sales / Tendering
- Buyer groupTrack B · Estimating & Commercial
- RequirementsBRD v0.1, sent as written
What goes in, what comes out
Product & Equipment Selection, step by step
Five steps, one decision point. The last step is a person, every time.
-
01
Engineer
Capture the criteria
Application, market, performance requirement and the constraints that actually disqualify a product.
-
02
Automated
Extract catalogue attributes
Model, revision, ratings and certification scope pulled from the data sheets themselves.
-
03
Automated
Apply hard filters
Anything failing a mandatory requirement is set aside with the reason recorded, not silently dropped.
Meets every mandatory requirement?
Yes Moves to the comparisonNo Set aside, with the reason -
04
Automated
Compare the candidates
Like for like, with the attribute that separates them made obvious.
-
05
Reviewer
Route technical approval
A reviewer confirms the shortlist and the data sheet revision it was based on.
-
Output
What lands at the end
A reviewed product comparison carrying model, data sheet revision, certification scope and approval status for each candidate.
Who’s involved
What you get
- Side-by-side comparison
- Certification scope
- Reviewed shortlist
In the wireframe
One candidate has an unverified certification scope for the location and is set aside; the other moves to a reviewed shortlist with its data sheet attached.
Who does what, and who signs
Automated steps prepare the evidence. People make the calls.
Swipe to see the whole diagram
Why this costs you time today
Catalogues are full of products that look interchangeable and are not. Certifications, pressure ratings and installation constraints vary by market and application, and the difference usually surfaces at submittal stage.
What this software will not do
Life-safety work. These limits are written into the requirements, not added as a disclaimer.
Specific to this workflow
It does not certify a product or confirm that a certificate is valid for your jurisdiction. It shows you the scope on the document and flags where that scope does not obviously cover the application.
It does not decide compliance
The software assembles evidence, retrieves source clauses and shows conflicts. It does not determine whether anything complies. A named engineer does.
It does not stand in for an authority
An approval recorded in the software never implies consent from an AHJ, Civil Defence, building control or a building surveyor.
Nothing leaves without a named reviewer
Every output carries who approved it. Anything unverified keeps a draft marker until someone signs it.
It does not do sealed engineering
Hydraulic network calculation, definitive sprinkler layout, sealed design, BIM geometry authoring and final cost estimates are all out of scope by design.
Your standards, not ours
NFPA, EN, BS, ISO, FM, UL, LPCB and Civil Defence appear in the requirements as examples. None is assumed to apply to your projects until you say so.
That is a claim about how fast Colakin builds software with DeX, and it is supported by delivered projects. It is not a claim about what any of these fifteen workflows will save your business. The requirements deliberately leave that to a pilot, measured against your own baseline.
From a question to a pilot, in five steps
Nothing hidden behind a discovery call. Stop at step one and keep the document.
- 01
You ask for the requirements document
The full BRD for the workflow you care about, sent as written.
Same day - 02
A ten-minute wireframe walkthrough
A clickable prototype of that one workflow.
10 minutes - 03
The Fire Fit Check
Five questions: fit, hours lost, who approves spend, whether your documents can be shared, and timing.
One call - 04
A scope built on your rules
Your standards, your document formats, your approval gates.
Within a week - 05
A pilot against your own baseline
One workflow, your data, your engineers.
Q1
Also in Estimating & Commercial
Each one stands alone. Take one first, then decide whether a second earns its place.
Quantity Take-Off & BOM
A bill of materials where every line shows its sheet and zone.
Estimation & Costing
Every rate carries its source, so price changes explain themselves.
Customer-Ready Quotations
An approved estimate becomes a branded offer, exclusions checked.
Product & Equipment Selection: questions
Does it maintain a product database for us?
How is certification scope handled?
Can it compare across manufacturers?
Who approves the selection?
Ask for the Product & Equipment Selection requirements document
The business requirements document as written, including what it refuses to do. No brochure, no drip sequence.
- The requirements document, usually the same working day
- A ten-minute wireframe walkthrough with the people who specified it
- No claimed percentage saving — your pilot measures it