Skip to main content

AI Import

Import requirements from documents using AI-powered extraction (Professional and Enterprise tiers only).

Three Import Methods Available

New to NirmIQ? We offer three import methods:

🤖 AI-Powered Import (This Page)

  • Converts unstructured Word documents using AI
  • AI extracts, organizes, and classifies requirements
  • Supports methodology documents for better accuracy
  • Requires Advanced tier or higher

🔍 Smart Word Import (Pattern-Based)

  • Detects "shall/must/will" keywords and requirement IDs
  • No AI credits used - free and unlimited
  • Best for well-formatted documents
  • Learn More →

📊 Manual Import (Structured Files)

  • Import pre-formatted Excel/JSON/ReqIF files
  • Free on all tiers, 100% accuracy
  • Best for data migration
  • See Full Comparison →

Overview​

The AI Import feature uses Google Gemini to:

  • Extract requirements from documents (PDF, Word, Excel)
  • Parse structure and hierarchy
  • Generate properly formatted requirements
  • Populate requirement fields automatically
Availability

AI Import is available only on Professional and Enterprise tiers. Free tier users must create requirements manually.

Supported File Formats​

  • PDF (.pdf)
  • Microsoft Word (.docx)
  • Microsoft Excel (.xlsx)
  • Plain Text (.txt)
  • Markdown (.md)

How to Import​

Step 1: Access AI Import​

  1. Open your project
  2. Click "Requirements" in sidebar
  3. Click "Import with AI" button (top right)

Step 2: Upload Document​

  1. Click "Choose File" or drag and drop
  2. Select your requirements document
  3. Wait for upload confirmation

Step 3: AI Processing​

The AI will:

  1. Extract text from document
  2. Identify requirements and structure
  3. Determine hierarchy levels
  4. Generate requirements preview
Processing Time

Typical processing time: 30 seconds to 2 minutes depending on document size.

Step 4: Review and Adjust​

Review the generated requirements:

Check for:

  • ✅ Correct hierarchy structure
  • ✅ Accurate requirement titles
  • ✅ Proper type assignment
  • ✅ Complete descriptions

You can:

  • Edit any requirement before importing
  • Delete requirements you don't want
  • Adjust parent-child relationships
  • Change requirement types

Step 5: Import​

  1. Click "Import All"
  2. Requirements are created in your project
  3. Navigate to tree to see results

Using a Methodology Document​

The methodology document is an optional but powerful feature that guides the AI to apply your organization's requirements best practices.

What is a Methodology Document?​

A methodology document contains:

  • Requirements writing rules and standards
  • Hierarchy structure definitions
  • Type classification guidelines
  • Quality criteria

When uploaded alongside your requirements document, the AI uses these rules to:

  • Structure requirements according to your hierarchy
  • Apply consistent terminology
  • Classify types correctly
  • Improve overall quality

INCOSE Best Practices Document​

We provide a pre-built methodology document based on the INCOSE 42 Rules for requirements engineering:

Download

Download INCOSE Methodology Document

This document includes:

  • All 42 INCOSE rules for good requirements
  • Type classification guidelines (Functional, Performance, Safety, etc.)
  • Quality checklist for each requirement
  • Output format instructions for AI

How to Use​

  1. Download the INCOSE methodology document (or create your own)
  2. In the import modal, select your requirements Word document (.docx)
  3. The Methodology Document field appears below
  4. Upload your methodology document (.docx)
  5. Click Import with AI

The AI will apply the methodology rules when extracting and organizing requirements.

Creating Your Own Methodology​

Your custom methodology document should include:

1. Hierarchy Definition

Level 1: System Requirements (prefix: SYS-)
Level 2: Subsystem Requirements (prefix: SUB-)
Level 3: Component Requirements (prefix: CMP-)
Level 4: Function Requirements (prefix: FUN-)

2. Writing Rules

  • Use "shall" for mandatory requirements
  • One requirement per statement
  • Active voice preferred
  • Include units of measure

3. Type Definitions

  • Functional: What the system does (perform, execute, display)
  • Performance: How well it does it (speed, latency, accuracy)
  • Safety: Hazard prevention (safe, protect, fail-safe)
  • Security: Access control (authenticate, authorize, encrypt)

See Best Practices Guide → for the complete INCOSE 42 rules.

Document Preparation Tips​

Format for Best Results​

✅ Well-Structured Documents:

1. Vehicle Requirements
   1.1 Powertrain System
      1.1.1 Engine shall generate 300 HP
      1.1.2 Engine shall meet Euro 6 emissions
   1.2 Safety System
      1.2.1 Airbags shall deploy within 30ms

✅ Clear Hierarchy Indicators:

  • Numbered lists (1, 1.1, 1.1.1)
  • Indentation
  • Heading styles (H1, H2, H3)
  • "Shall" statements

✅ Consistent Language:

  • Use "shall" for requirements
  • Clear subject-verb-object structure
  • Specific, measurable criteria

What to Avoid​

❌ Poor Formatting:

  • Flat lists with no hierarchy
  • Inconsistent numbering
  • Mixed requirement and prose
  • Unclear requirement boundaries

❌ Ambiguous Language:

  • "Should", "may", "might"
  • Vague descriptors ("fast", "good", "user-friendly")
  • Multiple requirements in one statement

AI Capabilities​

What AI Can Do​

✅ Extract requirement text ✅ Identify hierarchy structure ✅ Parse numbered/bulleted lists ✅ Determine requirement types ✅ Extract titles from sentences ✅ Handle multiple levels (2-6 deep) ✅ Preserve requirement IDs from document

What AI Cannot Do​

❌ Understand Domain Context: May misclassify technical terms ❌ Infer Missing Structure: Needs clear hierarchy in document ❌ Handle Images: Can't extract requirements from diagrams ❌ Validate Correctness: Doesn't verify requirement quality ❌ Handle Complex Tables: May struggle with matrix formats

Example Import​

Source Document​

Product Requirements Document

1. Customer Requirements
   The vehicle shall transport 5 passengers safely.
   The vehicle shall achieve 30 MPG highway.

2. System Requirements
   2.1 Powertrain
      The engine shall generate 300 HP at 6000 RPM.
      The transmission shall shift in under 200ms.
   2.2 Safety
      Airbags shall deploy within 30ms of impact.

AI-Generated Output​

CR-001: Vehicle shall transport 5 passengers safely
CR-002: Vehicle shall achieve 30 MPG highway
CR-001.SYS-001: Engine shall generate 300 HP at 6000 RPM
CR-001.SYS-002: Transmission shall shift in under 200ms
CR-002.SYS-001: Airbags shall deploy within 30ms of impact
Review Required

Always review AI output before importing. The AI may misinterpret structure or assign wrong types.

Troubleshooting​

AI Import Button Disabled​

Cause: Not available on Free tier

Solution: Upgrade to Professional or Enterprise

Upload Fails​

Causes:

  • File too large (> 10 MB)
  • Unsupported format
  • Network issue

Solutions:

  • Compress or split large files
  • Convert to supported format
  • Check internet connection

Poor Extraction Quality​

Causes:

  • Unstructured document
  • Missing hierarchy indicators
  • Mixed content (requirements + general text)

Solutions:

  • Clean up document before uploading
  • Add numbered hierarchy
  • Separate requirements from prose

Wrong Hierarchy Levels​

Cause: AI misinterpreted structure

Solution: Manually adjust parent-child relationships in preview before importing

Missing Requirements​

Cause: AI didn't recognize as requirement

Solution: Manually create missing requirements after import

Best Practices​

Before Upload​

  1. Clean Document: Remove unnecessary text
  2. Clear Structure: Use numbered lists or headings
  3. Consistent Format: Same style throughout
  4. Mark Requirements: Use "shall" statements
  5. Review Original: Ensure document is correct

After Import​

  1. Verify Completeness: Check all requirements imported
  2. Review Hierarchy: Ensure parent-child relationships correct
  3. Check Types: Verify requirement types assigned correctly
  4. Add Details: Populate missing fields (owner, priority, etc.)
  5. Link to FMEA: Connect to failure modes (if applicable)

Large Documents​

For documents with 100+ requirements:

  1. Split by Section: Import in chunks
  2. Start Small: Test with one section first
  3. Review in Batches: Don't import all at once
  4. Merge Projects: Combine after review (coming soon)

Limitations​

Current Limitations​

  • Maximum file size: 10 MB
  • Processing timeout: 5 minutes
  • No image extraction
  • No table parsing (complex matrices)
  • Single file at a time

Coming Soon​

  • Batch import (multiple files)
  • Advanced table parsing
  • Image OCR for diagrams
  • Custom AI prompts
  • Import templates
  • Re-import and merge

Alternative: Manual Creation​

If AI Import doesn't meet your needs, you can:

  1. Create requirements manually
  2. Copy-paste from document
  3. Use requirement templates (coming soon)
  4. Bulk import via CSV (coming soon)

What's Next?​