Compliance Reports
The Compliance Reports tab (under Analytics) shows how your project measures up against industry standards — using the requirements, traceability, tests, FMEA and work items you already have in NirmIQ. No separate spreadsheet, no manual clause tagging.
What NirmIQ offers
| What you get | Who it's for | |
|---|---|---|
| ASPICE (Automotive SPICE) | Built in and free. Base-practice coverage is derived automatically from your project data, with evidence for every pass and a clear action for every gap. | Automotive software & systems teams, and anyone who wants a process-quality view |
| Other standards | ISO 26262, DO-178C, IEC 62304, ISO 13485, ISO 21434 and more — set up for your organization by our compliance specialists. | Aerospace, medical, industrial and multi-standard teams |
ASPICE is the one standard NirmIQ assesses automatically, because it maps cleanly onto the data you're already capturing (requirements, traceability, tests, FMEA, project management). For the other standards, our team configures the clause library, maps it to your project, and helps you produce audit-ready evidence — typically within days. You can start that conversation right from the Compliance Reports tab with "Talk to us."
How automatic coverage works
NirmIQ does not ask you to tag each requirement against a clause. Instead it reads your project and infers which practices you already satisfy:
- Requirements captured → requirements-analysis practices
- Parent/child links between requirements → traceability practices
- Test cases (by type: unit, integration, system/acceptance) → verification practices
- FMEA failure modes with Severity/Occurrence/Detection and mitigations → risk-management practices
- Work Items & Sprints → project-management practices
The result is a live report that updates as your project grows — not a point-in-time audit.
Reading the report with confidence
Every judgment in the report is backed by evidence so it's auditable, not a black box:
- "What NirmIQ read from this project" — a summary of the data the assessment is based on (how many requirements, how many have tests, how many failure modes, and so on). This is the first thing to check: it confirms the tool actually read your project.
- Pass with evidence — e.g. "✓ 142 of 187 requirements have a parent link (bidirectional traceability)."
- Gap with an action — e.g. "→ Add integration-type test cases." Follow the action and the practice turns green on the next refresh.
- Tracked vs. manual — some practices (e.g. detailed interface specifications, architecture evaluations) can't be proven from data alone. NirmIQ marks these "manual review" rather than guessing, and your headline score is calculated only over the practices it can evidence — so the number is honest.
Next steps
- Automotive → ASPICE — a full guide to the ASPICE report: what each process means, how to read coverage, and how to close gaps.
- Need another standard? Open Analytics → Compliance Reports → Talk to us and tell us which standard and timeline you're working to.