Every reading. A clear route in.

Start with the source you have.

A monitoring project may combine files from a logger, an established provider platform, and a gateway maintained by your own team. SanSignal gives these sources a common destination without asking you to replace every collection system before you can start reviewing data.

FTP pipelines import delimited files from permitted remote locations. The Affinity integration maps supported provider inventory and readings. The dedicated Ingestion API gives custom gateways and other integrations a route to submit instrument batches. Choose the route around your source's delivery behavior, then bring the results together at project level.

• ↳FTP: new files in a folder or new rows in a file.
• ↳Affinity: supported inventory, live readings, and available history.
• ↳Ingestion API: structured batches from your own systems.

Make the mapping part of the setup.

An incoming number needs an instrument identity, a channel name, a timestamp, and a destination. Set these deliberately. Preview FTP parsing against representative files, or review the Affinity catalog before applying its proposed mappings. For a custom sender, commission a small batch with values your team can independently verify.

Consistent field identifiers make the result easier to operate months later. Keep the source name stable and use display aliases for a human-readable view. Agree on timezone interpretation, missing-value handling, and whether a corrected reading should replace a stored value before regular collection begins.

See what happened after collection.

Connection health, pipeline activity, and processing results answer different questions. A reachable FTP server does not prove that a file parsed correctly. A successful API response does not prove that all calculations are complete. SanSignal provides runs and source-specific activity so operators can follow those stages instead of treating connectivity as the final result.

Use diagnostics to narrow an issue to access, parsing, validation, mapping, or calculation. Then verify the affected time range in the instrument's values. This gives the team a repeatable commissioning and recovery process as new instruments and sources are added.

Share a connection with clear boundaries.

External connections belong to the organization. Administrators grant projects the source access they need, while project operators configure pipelines within those boundaries. An FTP grant can limit the remote root; an Affinity grant can limit access to provider sites.

This separates the ownership of upstream credentials from the daily work of managing a monitoring project. When a shared source changes, review its affected pipelines, commission the new configuration, and check the result at instrument level.