Data intake
CDR, IPDR and Tower Dump inputs as accepted by the evaluated parser build.
The difference between a credible analytics system and a feature list is traceable parsing, explainable calculations and reusable output.
Bring synthetic or officially authorized test files to a controlled evaluation.
CDR, IPDR and Tower Dump inputs as accepted by the evaluated parser build.
Source-specific column mappings, date and timezone interpretation, missing-field exceptions.
Operator layouts validated against test fixtures rather than unverified all-format promises.
Call frequency, timeline, common identifier, tower, link and source-file import summaries.
Discuss required CSV/XLSX/PDF output per evaluated edition; no universal export claim.
Import manifest, source fingerprints, analyst actions and review responsibilities.
Download a small fabricated report template to discuss column names and expectations; it is not evidence of a shipped report engine.
| Sample report | Illustrative fields | Evaluation question |
|---|---|---|
| CDR contact frequency | Party A, Party B, event count, duration | How are duplicates and missed values handled? |
| Common identifier | File ID, identifier, overlap count | Does normalization preserve source links? |
| Import exceptions | Row, field, warning, source file | Can analysts review rejected rows? |
Product capability information: This page describes the CyberSaathi analysis suite and its evaluation scope. Individual modules, format compatibility, integrations, deployment editions and licensing must be confirmed against the tested release for your organization. Illustrations and sample reports are not production evidence.
Request a demonstration with sample data, exact software release, deployment requirements, data types and configuration needs.