Skip to main content

Import Methods Comparison

Choose the right import method for your needs. NirmIQ offers four import methods to handle any document type.

Quick Decision Guide​

graph TD
A[Need to Import Requirements?] --> B{What's your source?}
B -->|Word Document| C{Is it structured?}
B -->|Excel/JSON| D{Pre-formatted with exact columns?}
B -->|Enterprise Tool Export| E{ReqIF file?}
C -->|Tables/Numbered Lists| F[Intelligent Import]
C -->|Narrative text| G[AI Import]
C -->|Already in Excel format| H[Export to Excel first]
D -->|Yes, matches template| I[Manual Import]
D -->|No, varied columns| F
E -->|Yes .reqif| J[ReqIF Import]
E -->|No| D
F --> K{Have Basic+ tier?}
G --> L{Have Advanced+ tier?}
H --> I
K -->|Yes| M[Use Intelligent Import]
K -->|No| N[Upgrade to Basic $49/mo]
L -->|Yes| O[Use AI Import]
L -->|No| P{Data privacy required?}
P -->|Yes| N
P -->|No| Q[Upgrade to Advanced $99/mo]
J --> R[All tiers - Advanced users]

style F fill:#f97316
style G fill:#0ea5e9
style I fill:#10b981
style J fill:#8b5cf6
style M fill:#f97316
style O fill:#0ea5e9

At a Glance​

πŸ“Š Manual Import🧠 Intelligent ImportπŸ€– AI ImportπŸ”§ ReqIF Import
InputExcel (.xlsx) or JSONWord (.docx) or ExcelWord (.docx)ReqIF (.reqif)
TierAll (Free+)Basic+ ($49/mo)Advanced+ ($99/mo)All (Free+)
SpeedInstantInstant1-3 minutes30 sec - 3 min
Accuracy100%85-95%90-95%100%
Data Privacyβœ… Privateβœ… Private⚠️ Sent to AI APIβœ… Private
Time to Prepare5-60 minutesNoneNoneNone (if tool exports ReqIF)
Best ForPre-formatted dataSemi-structured docsUnstructured narrativeEnterprise integration
User LevelBeginnerBeginnerIntermediateAdvanced

Detailed Comparison​

Input Format​

Manual Import​

Required: Pre-formatted Excel with EXACT column names
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ ID β”‚ Text β”‚ Type β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚ CR001 β”‚ System shall...β”‚ Customer β”‚
β”‚ SYS-001β”‚ Subsystem... β”‚ System β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

Columns must match: ID, Text, Type, Status, Version, Parent ID

Intelligent Import (NEW)​

Input: Word/Excel with varied structure
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ Req ID β”‚ Description β”‚ Category β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚ REQ-1 β”‚ System shall...β”‚ Functionalβ”‚
β”‚ REQ-2 β”‚ Subsystem... β”‚ Safety β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

Pattern recognition maps columns automatically:
"Req ID" β†’ ID, "Description" β†’ Text, "Category" β†’ Type

Also handles Word tables, numbered lists, headings

AI Import​

Input: Natural language Word doc
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ 1. Requirements β”‚
β”‚ β”‚
β”‚ The system shall provide collision β”‚
β”‚ detection with the following: β”‚
β”‚ - Scan at 10Hz β”‚
β”‚ - Detect within 100m β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

AI automatically creates:
CR001, CR001.SYS-001, CR001.SYS-002...

ReqIF Import​

Input: Enterprise tool export (.reqif)
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ <?xml version="1.0"?> β”‚
β”‚ <REQ-IF> β”‚
β”‚ <SPEC-OBJECTS> β”‚
β”‚ <SPEC-OBJECT IDENTIFIER="REQ1"> β”‚
β”‚ <VALUES> β”‚
β”‚ <ATTRIBUTE-VALUE> β”‚
β”‚ System shall detect... β”‚
β”‚ </ATTRIBUTE-VALUE> β”‚
β”‚ </VALUES> β”‚
β”‚ </SPEC-OBJECT> β”‚
β”‚ </SPEC-OBJECTS> β”‚
β”‚ </REQ-IF> β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

Preserves complete hierarchy + metadata
From: IBM DOORS, Jama, Polarion, etc.

Processing Flow​

Manual Import Flow​

You β†’ Format Excel β†’ Upload β†’ βœ… Done
(5-60 min) (instant)

Effort: Medium-High
Result: Perfect accuracy

Intelligent Import Flow (NEW)​

You β†’ Upload Word/Excel β†’ Review mappings β†’ Adjust if needed β†’ βœ… Done
(instant) (instant) (2-5 min)

Effort: Low
Result: 85-95% accuracy
Bonus: INCOSE compliance checking included

AI Import Flow​

You β†’ Upload Word β†’ AI processes β†’ Review β†’ βœ… Done
(instant) (1-3 min) (5 min)

Effort: Low
Result: 90-95% accuracy

ReqIF Import Flow​

You β†’ Export from tool β†’ Upload ReqIF β†’ Verify β†’ βœ… Done
(2-5 min) (30s-3min) (2 min)

Effort: Low (if tool supports ReqIF)
Result: 100% accuracy (structure preserved)

Use Case Scenarios​

Scenario 1: Migrating from Jira​

Best Choice: Manual Import βœ…

Why:

  • Jira exports to Excel already
  • Data is structured
  • Just need to map columns
  • Free, instant

Steps:

  1. Export from Jira (5 min)
  2. Rename columns to match IntelliSE (2 min)
  3. Import (instant)
  4. Total: 7 minutes

Scenario 2: Customer sends Word doc with tables​

Best Choice: Intelligent Import 🧠

Why:

  • Document has requirement tables
  • Column names vary ("Req ID" not "ID")
  • Data must stay private (no AI APIs)
  • Basic tier is affordable

Manual Approach:

  • Copy tables to Excel: 1 hour
  • Rename columns to match template: 30 min
  • Import: instant
  • Total: 1.5 hours

Intelligent Import Approach:

  • Upload Word doc: instant
  • Wizard detects tables automatically
  • Review column mappings: 5 minutes
  • Import: instant
  • Total: 5 minutes

Time Saved: 1.4 hours (94% reduction) Privacy: βœ… Data never leaves your server


Scenario 3: Customer sends 50-page Narrative Spec​

Best Choice: AI Import πŸ€–

Why:

  • Document is narrative text (not tables)
  • Manually extracting would take hours
  • AI handles hierarchy automatically
  • Worth the tier cost

Manual Approach:

  • Read doc, extract requirements: 3 hours
  • Format in Excel: 1 hour
  • Import: instant
  • Total: 4 hours

AI Approach:

  • Upload doc: 1 minute
  • AI processing: 2 minutes
  • Review/fix: 15 minutes
  • Total: 18 minutes

Time Saved: 3.7 hours (93% reduction)


Scenario 4: Weekly RFP Processing​

Best Choice: AI Import πŸ€– (Essential)

Without AI:

  • 4 RFPs/week Γ— 4 hours each = 16 hours/week
  • 64 hours/month
  • Cost: $6,400/month @ $100/hr

With AI:

  • 4 RFPs/week Γ— 20 minutes each = 1.3 hours/week
  • 5.3 hours/month
  • Cost: $299 (Power tier) + $530 labor = $829/month

Savings: $5,571/month ($66,852/year)


Scenario 5: Small Startup Budget​

Best Choice: Manual Import βœ…

Why:

  • Free tier works perfectly
  • Requirements are simple
  • Can afford time to format
  • Learning the tool

Approach:

  • Use Excel template
  • Format 50 requirements: 30 minutes
  • Import: instant
  • Cost: $0

Scenario 6: Data Privacy Required (Regulated Industry)​

Best Choice: Intelligent Import 🧠

Why:

  • Data cannot leave company servers
  • Customer documents contain sensitive IP
  • Regulatory requirements prohibit external AI
  • Still need smart extraction (not manual formatting)

Approach:

  • Upload Word/Excel: instant
  • Pattern matching on your server (no external APIs)
  • INCOSE compliance checking included
  • Data Privacy: βœ… Guaranteed
  • Cost: $49/mo (Basic tier)

Scenario 7: Automotive Supplier (Tier 1)​

Best Choice: ReqIF Import πŸ”§

Why:

  • OEM (customer) uses IBM DOORS
  • Must maintain exact requirement structure
  • ISO 26262 / ASPICE compliance required
  • Tool interoperability essential

Workflow:

  1. Receive 2,000 requirements from OEM via ReqIF
  2. Import to IntelliSE (3 minutes)
  3. Work on requirements in IntelliSE
  4. Export updated ReqIF back to OEM
  5. Perfect traceability maintained

Benefits:

  • βœ… No manual reformatting
  • βœ… 100% hierarchy preservation
  • βœ… Audit trail maintained
  • βœ… Standards compliant

ROI Calculator​

Time Value Calculation​

Manual Formatting Time:

  • Simple requirement: 1-2 minutes
  • Complex requirement: 3-5 minutes
  • Average: 2.5 minutes per requirement

AI Processing Time:

  • Any number of requirements: 1-3 minutes + review
  • Review time: ~10% of requirements need fixing
  • Average: 0.3 minutes per requirement

Breakeven Analysis​

Advanced Tier: $99/month

Saves 2.2 minutes per requirement vs. manual

Breakeven: 45 requirements/month

  • If you import 45+ requirements/month via AI
  • You save more time than the tier costs
  • At $50/hr: 45 req Γ— 2.2 min = 99 minutes = $82.50 saved
  • Pays for itself at 54 requirements/month

Power Tier: $299/month

Unlimited AI imports + other features

Breakeven: 135 requirements/month

  • Best for teams processing documents weekly
  • High-volume RFP/proposal work
  • Multiple team members using AI

Common Questions​

"Should I upgrade just for AI import?"​

Upgrade if:

  • βœ… You process 2+ Word docs/month
  • βœ… Each doc has 50+ requirements
  • βœ… Your time is worth $50+/hour
  • βœ… You receive unstructured specs regularly

Don't upgrade if:

  • ❌ You only import once
  • ❌ Your data is already in Excel
  • ❌ You're a solo free-tier user learning
  • ❌ Requirements are simple/few

"When should I use ReqIF instead of Excel?"​

Use ReqIF when:

  • βœ… Exchanging requirements with enterprise tools (DOORS, Jama, Polarion)
  • βœ… Working with automotive/aerospace/defense suppliers
  • βœ… Compliance requires tool-neutral format (ISO 26262, DO-178C, IEC 62304)
  • βœ… Need perfect hierarchy preservation across tools
  • βœ… Long-term archival (20+ year readability)

Use Excel when:

  • ❌ Simple data sharing within your team
  • ❌ No enterprise tool integration needed
  • ❌ Requirements are flat (no complex hierarchy)
  • ❌ Just need human-readable format

"Can I use both methods?"​

Yes! Many teams do:

  1. AI Import for initial extraction
  2. Export to Excel to review
  3. Manual Import for final clean version

This gives you:

  • Speed of AI
  • Accuracy of manual review
  • 100% control over final data

"What if AI makes mistakes?"​

AI is 90-95% accurate:

  • Most requirements perfect
  • 5-10% need minor fixes
  • Always review before committing

Common AI issues:

  • Occasionally misses a requirement
  • Might mis-classify type (easy fix)
  • Rarely creates wrong hierarchy

Solution:

  • Export AI results to Excel
  • Review and fix
  • Re-import with Manual Import

Pricing Tiers​

Free ($0/month)​

  • ❌ No Intelligent Import
  • ❌ No AI Import
  • βœ… Manual Import unlimited
  • βœ… ReqIF Import
  • Best for: Learning, small projects

Basic ($49/month)​

  • βœ… Intelligent Import (Word + Excel)
  • ❌ No AI Import
  • βœ… Manual Import unlimited
  • βœ… ReqIF Import
  • βœ… INCOSE compliance checking
  • Best for: Small teams, data privacy needs

Advanced ($99/month)​

  • βœ… Intelligent Import (Word + Excel)
  • βœ… AI Import (50 docs/month)
  • βœ… Manual Import unlimited
  • βœ… ReqIF Import
  • Best for: Regular doc conversion, mixed needs

Power ($299/month)​

  • βœ… Intelligent Import (unlimited)
  • βœ… AI Import (unlimited)
  • βœ… Manual Import unlimited
  • βœ… ReqIF Import
  • Best for: High-volume teams

Enterprise (Custom)​

  • βœ… Everything unlimited
  • βœ… Custom AI training
  • βœ… Custom synonym dictionaries
  • Best for: Large organizations

Tips for Success​

For Manual Import​

βœ… Do:

  • Use our Excel template as starting point
  • Keep column names exactly as required
  • Validate data before importing
  • Import in small batches to test

❌ Don't:

  • Modify column structure
  • Leave required fields empty
  • Import without reviewing
  • Mix different requirement formats

For Intelligent Import (NEW)​

βœ… Do:

  • Use Word tables or Excel spreadsheets
  • Include clear column headers
  • Use consistent requirement patterns
  • Review INCOSE compliance warnings
  • Check column mappings before import

❌ Don't:

  • Mix tables with narrative text in Word
  • Use complex nested tables
  • Embed requirements in images
  • Skip the mapping review step

Best Practices:

  • Tables with headers work best (95% accuracy)
  • Numbered lists also work well (80% accuracy)
  • If confidence is low, consider AI Import instead

For AI Import​

βœ… Do:

  • Provide clean Word documents
  • Include methodology docs for context
  • Review AI output before committing
  • Use hybrid workflow (AI + manual review)

❌ Don't:

  • Expect 100% perfection
  • Skip the review step
  • Upload poor quality scans
  • Forget to check hierarchy

Method Summary Table​

FeatureManual ImportIntelligent ImportAI ImportReqIF Import
Input FormatExcel, JSONWord, ExcelWord (.docx)ReqIF (.reqif) XML
Pricing TierFree+Basic+ ($49/mo)Advanced+ ($99/mo)Free+
Processing TimeInstantInstant1-3 minutes30s - 3 minutes
Accuracy100%85-95%90-95%100%
Data Privacyβœ… Privateβœ… Private⚠️ External AIβœ… Private
Hierarchy Supportβœ… Perfectβœ… Pattern-detectedβœ… AI-detectedβœ… Perfect
Column Detection❌ Manualβœ… Automatic synonymsN/Aβœ… Automatic
INCOSE Validation❌ Noβœ… Yes❌ No❌ No
Metadata Preservation⚠️ Manual mapping⚠️ Pattern matching⚠️ Extractedβœ… Full
Tool Compatibilityβœ… Universalβœ… Word/Excel❌ IntelliSE onlyβœ… Enterprise tools
Standards Compliance❌ No standard⚠️ INCOSE❌ Proprietaryβœ… OMG ReqIF 1.2
Best Use CasePre-formatted dataSemi-structured docsUnstructured narrativeEnterprise integration
User Skill LevelBeginnerBeginnerIntermediateAdvanced
Regulatory Support⚠️ Limitedβœ… Data privacy❌ Not auditableβœ… ISO 26262, DO-178C


Need Help Deciding?​

Contact us for guidance:


Updated: October 2025