Industry Templates
NirmIQ provides pre-configured industry templates that set up a new project with the right hierarchy structure, safety classification scheme, and a realistic starting scope for the chosen domain.
When to use what — three paths
Choosing the right starting point matters more than people expect. Pick by intent:
| You want to... | Use | Why |
|---|---|---|
| Evaluate NirmIQ with realistic, large-scale data. See traceability, multi-tab reports, and how everything fits together. Read-only feel. | Sample Project (e.g. Commercial Aviation Narrow-Body, ADAS/Autonomous Vehicle, BMS) | 370+ requirements, 240+ failure modes, full traceability links. Kitchen sink. Not meant to be edited. |
| Start a real project but want to learn the platform with a small worked example you can edit. First template apply, hackathon, classroom. | Industry Template — Starter Kit mode | ~20 sample requirements + 6 failure modes + structure tree. Real scenario (e.g. anti-pinch window). Replace or customise the content as you build your real project. |
| Start a real project as an experienced engineer who already knows what they're building. You want the right hierarchy and classification scheme but your own content. | Industry Template — Structure Only mode | Hierarchy levels + ASIL/DAL flag + FMEA shell + structure tree skeleton. NO sample requirements, NO sample failure modes. |
| Throwaway experiment or you genuinely want zero scaffolding. | Blank project | Empty. You'll set up everything yourself. |
Both industry-template modes apply via the same endpoint with a flag — see Using Templates below.
Available templates
Every template uses the same canonical 5-level hierarchy: Customer Requirement → System Requirement → Subsystem Requirement → Function Requirement → Subfunction Requirement. The starter scenario, safety scheme, and compliance standards vary per industry.
Automotive — ISO 26262
Scenario: Power Window with Anti-Pinch (ASIL B)
For: Automotive OEMs, Tier 1 suppliers, ADAS/electrification engineering teams.
Starter Kit includes:
- 19 sample requirements across the 5-level hierarchy
- ASIL classification on the safety-critical chain (anti-pinch detection)
- 6 DFMEA failure modes (Hall sensor failure, current-sense drift, ECU latency, etc.)
- 5-element structure tree (Motor Drive / Sensing / Anti-Pinch ECU / Switch / System)
Compliance standards: ISO 26262, ISO 21448 (SOTIF), Automotive SPICE Safety scheme: ASIL (QM, A, B, C, D) FMEA type: DFMEA
Aerospace — DO-178C
Scenario: Pitch Trim Runaway Detection (DAL B)
For: Avionics manufacturers, airframe OEMs, MRO software teams, certification authorities.
Starter Kit includes:
- 19 sample requirements covering the runaway-detection safety chain
- DAL classification on detection and inhibit paths
- 6 DFMEA failure modes (LVDT open circuit, brake stuck, monitor task overrun, etc.)
- 5-element structure tree (Motor Drive / Position Sensing / Runaway Monitor / Cutout / System)
Compliance standards: DO-178C, DO-254, ARP4754A, ARP4761 Safety scheme: DAL (A, B, C, D, E) FMEA type: DFMEA
Medical Device — IEC 62304
Scenario: Infusion Pump Patient-Controlled Bolus Limit (Class B)
For: Medical device manufacturers, health tech, regulated diagnostic/therapy software teams.
Starter Kit includes:
- 19 sample requirements covering the bolus dose-limit enforcement chain
- 6 DFMEA failure modes (stepper missed steps, flow sensor drift, FRAM write failure, etc.)
- 5-element structure tree (Pump Drive / Volume Tracking / Safety Supervisor / Alarm / System)
Compliance standards: IEC 62304, ISO 14971, FDA 21 CFR Part 11, ISO 13485 Safety scheme: Software Safety Class (A, B, C) FMEA type: DFMEA
Defense — DO-254 / MIL-STD-882E
Scenario: IFF Transponder Mode 5 Cryptographic Validation (Catastrophic)
For: Defense contractors, avionics suppliers, military systems integrators.
Starter Kit includes:
- 19 sample requirements covering Mode 5 receive, validate, reply paths
- 6 DFMEA failure modes (crypto engine fault, side-channel leakage, replay race, etc.)
- 5-element structure tree (RF Front-End / Crypto Validation / Key Management / Reply Generation / System)
Compliance standards: DO-254, DO-178C, MIL-STD-882E, NATO STANAG 4193 Safety scheme: MIL-STD-882E severity (Catastrophic, Critical, Marginal, Negligible) FMEA type: DFMEA
General — IEC 61508
Scenario: Industrial Centrifugal Pump Cavitation Monitoring (SIL 2)
For: Cross-industry / process industries: chemical, water treatment, food, refining.
Starter Kit includes:
- 19 sample requirements covering the cavitation detection chain
- 6 DFMEA failure modes (accelerometer mount loose, pressure fouling, FFT overflow, etc.)
- 5-element structure tree (Vibration / Pressure / Detection Algorithm / Communication / System)
Compliance standards: IEC 61508, IEC 61511, IEC 60601-1-8 (alarms) Safety scheme: SIL (1, 2, 3, 4) FMEA type: DFMEA
Using templates
Path A — Starter Kit (default)
- New Project → select an industry template card.
- Enter a project name and description.
- Click Create.
This calls POST /templates/{id}/apply and seeds the full sample content listed above. About 20 requirements, 6 failure modes, and a structure tree appear in the new project. You'll customise or replace the content as you build your real project.
Path B — Structure Only (advanced users)
When you don't want sample requirements or failure modes, call:
POST /templates/{id}/apply?include_sample_content=false
This seeds:
- Project hierarchy snapshot (so requirement create dialogs use the right levels)
- Empty FMEA analysis (so the FMEA tab is set to the right type)
- Structure tree (the scaffold, since most users want it even when starting from scratch)
But NOT:
- Any sample requirements
- Any sample failure modes
You start with an empty Requirements tab and an empty FMEA Failure Modes list, but everything is configured correctly. Fastest path to a real project for engineers who don't need the worked example.
A UI checkbox for this mode is rolling out in the New Project dialog. Until then, you can call the endpoint directly from a script or curl.
What both modes set up
Regardless of mode:
- 5-level hierarchy levels are written to your project (
hierarchy_snapshot). - The org's hierarchy config is updated so new requirements use the right level dropdowns.
- The relevant safety classification flag (ASIL / DAL / Class / SIL / Severity) is enabled on the project.
- An FMEA analysis row is created with the right type (DFMEA).
- A structure tree skeleton is created.
- Compliance standard labels are attached to the project.
What templates do NOT do
- Templates do not configure integrations (Jira, Slack, GitHub). Set those up separately.
- Templates do not enforce compliance — they label and structure for the standard, but it is still your responsibility to write requirements that meet it.
- Templates do not generate test cases (yet). Use the test management module to add those.
Sample project vs industry template — common confusion
| Sample Project | Industry Template | |
|---|---|---|
| Size | 370+ reqs, 240+ failure modes | ~20 reqs, ~6 failure modes (Starter Kit mode) or 0 (Structure Only) |
| Editability | Read-only feel (large, interlinked, easy to break) | Designed to be edited and replaced |
| Purpose | Demo, evaluation, training | Real project starting point |
| Customer-facing name | "Commercial Aviation", "ADAS", "BMS" | "Industry Template" (Automotive, Aerospace, ...) |
| Hierarchy | Intentionally diverse — shows you can model anything | Canonical Customer → System → Subsystem → Function → Subfunction |
If somebody asks "do I want a sample project or a template?", the rule of thumb: demo = sample, real work = template.
FAQ
Can I change which template was applied after project creation?
Once a template is applied, the structure is yours to modify. You can change requirement types, hierarchy levels, and FMEA settings. There is no "switch template" operation — for major redirections, create a new project from the desired template and migrate content.
Do templates conflict with my org's hierarchy config?
The template overrides the org's hierarchy config for this project only via the project's hierarchy_snapshot field. Other projects in the org are unaffected.
Will my org hierarchy get changed?
Yes — the template's hierarchy_config is written to organization_hierarchy_config so subsequent new projects (without a template) inherit those levels too. If you do not want that, use Structure Only mode and then manually adjust the org config back. We are looking at making this opt-in in a future release.
Can I create custom templates?
Custom industry templates are on the Enterprise tier roadmap. Contact support for early access if you need this.
Which template for multi-industry products?
Choose the most restrictive standard the product needs to meet. For an automotive product with critical embedded software, Automotive (ISO 26262) is a better fit than General because the ASIL scheme is more rigorous. You can always add elements from other templates manually.