Industry Templates
NirmIQ provides pre-configured templates for common industry standards, helping you start projects with best-practice structures already in place.
Available Templates
Automotive - ISO 26262
For: Vehicle manufacturers, Tier 1/2 suppliers, automotive software teams
Includes:
- 5-level requirement hierarchy (System → Safety → TSR → Software → Hardware)
- ASIL classification enabled by default
- DFMEA template structure
- Automotive SPICE alignment
Compliance Standards: ISO 26262, ISO 21448 (SOTIF), Automotive SPICE
Requirement Types: System, Safety, Functional, Performance, Interface, Constraint, Verification
Aerospace - DO-178C
For: Avionics manufacturers, aerospace software developers, defense contractors
Includes:
- DO-178C compliant hierarchy (System → HLR → LLR → Source → Test)
- DAL classification enabled by default
- Full traceability structure
- Derived requirements tracking
Compliance Standards: DO-178C, DO-254, ARP4754A, ARP4761
Requirement Types: System, High-Level, Low-Level, Derived, Safety, Interface, Performance
Medical Device - IEC 62304
For: Medical device manufacturers, health tech companies, regulated software teams
Includes:
- IEC 62304 software lifecycle structure
- User Needs → Product → Software → Architecture → Design hierarchy
- Software Safety Class support (A, B, C)
- Risk management integration
Compliance Standards: IEC 62304, ISO 14971, FDA 21 CFR Part 11, ISO 13485
Requirement Types: User Need, Product, Software, Architecture, Design, Risk Control, Verification
Defense - MIL-STD-882E
For: Defense contractors, government systems integrators
Includes:
- Capability-driven hierarchy
- System safety structure per MIL-STD-882E
- DAL classification support
- ICD (Interface Control Document) templates
Compliance Standards: MIL-STD-882E, DO-178C, MIL-HDBK-516C, IEEE 15288
Requirement Types: Capability, System, Subsystem, Component, Interface, Safety, Security
General Requirements
For: General software projects, enterprise applications, custom needs
Includes:
- Flexible 5-level hierarchy
- Business → Stakeholder → System → Software → Test structure
- No specific safety classifications
- Adaptable to any domain
Compliance Standards: ISO 9001, CMMI, IEEE 830
Requirement Types: Business, Stakeholder, Functional, Non-Functional, Interface, Constraint, Verification
Using Templates
When Creating a New Project
- Click New Project
- In the project creation dialog, you'll see Select Industry Template
- Browse available templates with previews
- Click on a template card to see:
- Hierarchy structure
- Compliance standards included
- Default requirement types
- Select your template
- Complete project details
- Click Create Project
Template Benefits
When you apply a template:
- Hierarchy is pre-configured - No manual setup needed
- Requirement types are populated - Standard types for your industry
- Safety classifications are enabled - ASIL/DAL as appropriate
- Compliance mapping is set - Standards are linked
Customizing After Creation
Templates provide a starting point. You can always:
- Add or remove requirement types
- Modify hierarchy levels
- Adjust safety classification settings
- Add custom fields
Go to Project Settings → Hierarchy Configuration to customize.
Template Comparison
| Feature | Automotive | Aerospace | Medical | Defense | General |
|---|---|---|---|---|---|
| Safety Classification | ASIL | DAL | Software Class | DAL | None |
| Hierarchy Levels | 5 | 5 | 5 | 5 | 5 |
| FMEA Type | DFMEA | DFMEA | DFMEA | DFMEA | DFMEA |
| Traceability | Full | Full | Full | Full | Basic |
Important Restrictions
If you're working with a sample project (pre-loaded demo data), you cannot apply FMEA templates to it. The system will block this action with an error message.
Why? Sample projects have carefully curated FMEA data with established traceability links to their requirements. Applying a different template would:
- Break existing requirement-to-FMEA connections
- Create conflicting data structures
- Result in incorrect compliance reports
Solution: Create a new project from the template instead. This gives you a clean starting point with the correct industry structure.
FAQ
Can I change templates after project creation?
The initial template sets up your structure, but you can modify settings afterward. For major changes, consider creating a new project.
Do templates affect my data?
Templates only configure settings and structure. Your requirements, FMEA data, and other content remain unchanged.
Can I create custom templates?
Enterprise customers can request custom templates. Contact support for details.
Which template for multi-industry products?
Choose the most restrictive standard (typically Aerospace or Medical), then add elements from other templates as needed.
Why can't I apply templates to sample projects?
Sample projects are pre-built demonstrations with complete traceability between requirements and FMEA. Applying templates would break these connections. To use a different industry template, create a new project from that template instead.