Build a repeatable way to deliver monitoring data while keeping the sources, configuration, and responsibilities of each project clear.
Create a consistent approach across jobs.
Different clients and site conditions do not have to mean a completely different data structure every time. Use projects for distinct monitoring jobs, sites for recognizable locations, and instruments that match the field register. Keep logger hardware separate from the channels whose readings it transports.
Agree on naming, units, source mappings, and calculation ownership before collection begins. A repeatable setup process makes commissioning easier to review and gives operators familiar places to look when a new project needs attention. Each job can still have its own dashboards, teams, and ingestion configuration.
Connect the collection systems you support.
A contractor may inherit a mix of FTP-delivered files, provider-managed instruments, and custom field gateways. SanSignal gives these systems supported routes into the same platform: FTP pipelines, Affinity integration for supported profiles, and the dedicated Ingestion API.
Organization-owned external connections can be granted to projects within defined boundaries. A project operator can manage a permitted pipeline without receiving the upstream secrets. This helps separate source administration from the daily task of getting the project's instruments connected and verified.
Make data delivery something you can inspect.
The work continues after the first reading appears. Use pipeline activity, processing runs, and source diagnostics to investigate file changes, mapping issues, rejected values, or calculation problems. Verify the affected instrument and time period after a configuration change or recovery action.
When the instrument's method requires engineering conversion, use calculated variables with identified inputs and calibration constants. Check recalculation status and representative outputs before relying on the result. This creates a clearer working relationship between the team operating the source and the engineers reviewing its meaning.
- Commission using known readings and representative source data.
- Inspect connection, pipeline, and processing state separately.
- Keep source channels and calculated outputs available for review.
Give each project team a useful view.
Build dashboards around a client's or review team's actual questions, combining selected graphs, tables, and contextual notes. Configure project teams and scoped access for the people who operate or review the work. Dashboard viewer grants support an audience that needs a focused view rather than the full instrument catalog.
Use configured anomaly conditions and email actions as part of the agreed review process. At handover or project retirement, review recipients, access, active dependencies, and the instrument lifecycle. Keep retained history interpretable for the team that will return to it later.
Common questions.
Can one organization manage several monitoring projects?
Yes. The platform organizes work into projects with their own sites, instruments, dashboards, teams, and ingestion configuration. Organization-level resources include members and shared external connections.
How do we evaluate SanSignal for our service?
Choose a representative installation and bring a source sample, instrument register, calculation example, and target review view. We can use those to discuss connectivity, workflow, access, and project scope.