raNora’s First Agents: Database Agent + Coverage Agent

raNora is built around a simple idea: specialized agents that do real engineering work, not generic conversation. In its initial release, raNora ships with two high-impact agents designed for everyday radio planning and data workflows: the Database Agent and Coverage Agent.

Database Agent: turn “network questions” into answers—and fixes

Planning and operations teams spend huge time just finding the right data, validating it, and reconciling inconsistencies across systems. raNora’s Database Agent is designed to help with:

• Querying: Retrieve specific network data (cells, sites, parameters)
• Auditing: Check network compliance and integrity
• Analyzing discrepancies: Identify differences between OSS and ASSET DB
• Fixing discrepancies: Correct parameters in ASSET DB and EDS to match OSS

Example prompts you can use in a campaign demo:

• “List all LTE cells in Project X with PCI conflicts and show the neighboring cells involved.”
• “Audit missing/invalid antenna parameters across the top 50 traffic sites.”
• “Compare OSS vs ASSET DB for these 200 cells and summarize mismatches by parameter.”
• “Propose fixes for the mismatches and generate a change plan for ASSET DB + EDS.”

Coverage Agent: from analysis requests to maps, reports, and recommendations

Coverage evaluation is a core planning workflow—and often requires multiple steps, tools, exports, and iterations. raNora’s Coverage Agent supports:

• Run coverage analysis
• Run statistical reports
• Interactive coverage maps
• Automated site placement

Example prompts:

• “Run coverage for the downtown cluster and highlight weak-RSRP pockets by grid.”
• “Generate a before/after report for last week’s parameter changes.”
• “Open an interactive coverage map for the stadium area and explain the dominant server issues.”
• “Propose 3 candidate macro sites to improve coverage in the northwest polygon and justify each option.”

raNora’s UX is intentionally straightforward:

1. Select your agent
2. Set your project
3. Start a new thread
4. Start chatting

This “project + thread” model matters: it keeps work organized, repeatable, and traceable—so teams can return to a thread, reuse it, and build on it instead of starting from scratch every time.