TECHNICAL EVALUATION

Data Import, Normalization & Reporting

The difference between a credible analytics system and a feature list is traceable parsing, explainable calculations and reusable output.

Technical capability catalogue

Make input and output requirements explicit.

Bring synthetic or officially authorized test files to a controlled evaluation.

01

Data intake

CDR, IPDR and Tower Dump inputs as accepted by the evaluated parser build.

02

Field normalization

Source-specific column mappings, date and timezone interpretation, missing-field exceptions.

03

Compatibility evidence

Operator layouts validated against test fixtures rather than unverified all-format promises.

04

Report categories

Call frequency, timeline, common identifier, tower, link and source-file import summaries.

05

Exports

Discuss required CSV/XLSX/PDF output per evaluated edition; no universal export claim.

06

Evidence trail

Import manifest, source fingerprints, analyst actions and review responsibilities.

Sample reporting

Synthetic example — not an application output.

Download a small fabricated report template to discuss column names and expectations; it is not evidence of a shipped report engine.

Sample reportIllustrative fieldsEvaluation question
CDR contact frequencyParty A, Party B, event count, durationHow are duplicates and missed values handled?
Common identifierFile ID, identifier, overlap countDoes normalization preserve source links?
Import exceptionsRow, field, warning, source fileCan analysts review rejected rows?

Download Synthetic CSV Template →

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.

Technical evaluation

Discuss data compatibility and reports

Request a demonstration with sample data, exact software release, deployment requirements, data types and configuration needs.