Document Generation
Generate MOPs, change controls, incident reports, config audits, and research briefs.
Damira AI generates structured network operations documents from natural language descriptions. Documents output as interactive spreadsheets or formatted reports.
Document Types
Method of Procedure (MOP)
A step-by-step execution plan for network changes.
"Generate a MOP for adding a backup eBGP peer to wan-r1: neighbor 10.0.1.5 remote-as 65200"
The agent asks for:
- Devices affected — hostnames, models, software versions
- Maintenance window — scheduled time and expected duration
- Risk level — low / medium / high / critical
- Rollback criteria — what triggers a rollback
Then generates a spreadsheet with pre-checks, implementation steps (with exact CLI commands), post-checks, and rollback procedures.
Change Control Document
A CAB-ready document for planned changes.
"Create a change control document for upgrading FRR from 10.2.1 to 10.3.0 across all routers"
Includes change description, risk assessment (severity, likelihood, impact), implementation steps per device, rollback procedure, and success criteria.
Config Security Audit
Paste a router or firewall config for automated analysis.
"Audit this config for security issues: [paste config]"
The audit checks for: plaintext passwords, missing authentication (BGP MD5, OSPF auth), unrestricted VTY access, missing logging, no prefix lists or route maps, and insecure services.
Incident Report
Post-incident documentation with timeline, root cause, and corrective actions.
"Write an incident report for the BGP outage. The session on wan-r1 was in Idle (Admin) state. Impact was 15 minutes of internet loss."
Produces a structured report with: incident summary, timeline, root cause analysis, impact assessment, remediation steps, and preventive recommendations.
Research Briefs
Deep research on CVEs, vendor comparisons, upgrade paths, and technology decisions.
"Research CVEs affecting FRR 10.2.x. What vulnerabilities exist and should we upgrade?"
The agent searches CVE databases, GitHub advisories, vendor release notes, and documentation. Results compile into a research brief stored in your session for follow-up questions.
Generation Progress
When Damira generates a spreadsheet, you see real-time progress in the chat panel:
- Searching vendor docs — querying the knowledge base for relevant procedures
- Researching upgrade path — web search for CVEs, release notes, known issues
- Generating spreadsheet — LLM builds the structured workbook
- Rendering workbook — converting to interactive spreadsheet + Excel export
Each phase shows a step counter (e.g., "Step 2/4") so you know how far along the generation is.
Output Formats
| Format | When | How to Access |
|---|---|---|
| Interactive Spreadsheet | MOPs, audits, assessments | Opens in custom editor tab (.damira.json) |
| HTML Document | MOPs, change controls, runbooks | Opens in browser, print-ready |
| Formatted Report | Incident reports, research | Appears in chat or editor panel |
| CSV Export | Tabular data | Download from spreadsheet view |
| XLSX Export | Excel workbooks | Export button in spreadsheet editor |
HTML Documents
MOPs, change controls, and runbooks can render as self-contained HTML files with professional print-ready CSS. Each document includes a document control header with document number, risk level badge, date, and author.
VS Code automatically opens HTML documents in your default browser. From there you can print directly or save as PDF for sharing with CAB boards and stakeholders who don't have VS Code.
HTML output is ideal for formal documentation that needs to look polished without manual formatting.
ServiceNow Integration
After generating a document or completing a troubleshooting session, you can create a ServiceNow ticket directly from the chat:
"Create a change request in ServiceNow for this upgrade"
"Open a P2 incident for this BGP issue"
Damira creates properly structured ITSM tickets with category, priority, assignment group, and affected device linked to your CMDB. A confirmation gate shows you exactly what will be created before submission. See Monitoring Integration for ServiceNow setup.
Tips
- Be specific: Include device names, IP addresses, software versions, and the exact change you're making.
- Provide context: The more detail in your initial request, the fewer follow-up questions the agent needs.
- Modify after generation: After generating a spreadsheet or document, ask follow-up questions to modify it — "add a priority column", "update the rollback section", "change the risk level to high", "mark step 5 as critical". The agent modifies the existing deliverable in place rather than generating a new one.