Data connections
Receive observations through the Developer API ingestion or poll files through FTP pipelines. Inspect ingestion runs to see what was processed and what needs attention.
Read the guide for data connections →Product & features
SanSignal brings instrument data into a central workspace for the teams monitoring construction, ground movement, and structural performance.
01 / Connect
Keep incoming measurements connected to their source and their place in your monitoring program.
Receive observations through the Developer API ingestion or poll files through FTP pipelines. Inspect ingestion runs to see what was processed and what needs attention.
Read the guide for data connections →Build reusable parsers for incoming files. Configure timestamps, instrument identifiers, variable names, and value types before connecting the parser to a pipeline.
Read the guide for file parsing and mapping →Follow ingestion and calculation work, inspect failures, and use the recovery actions available for each connection. An accepted request is the start of a run; its result tells you what reached the platform.
Read the guide for run diagnostics →02 / Organize
Make it straightforward to find an instrument, understand where it belongs, and review the measurements it produces.
Keep projects within an organization and organize installations by site. Configure project coordinate systems and positions so instrument locations have the right context.
Read the guide for organizations, projects, and sites →Manage instruments separately from their data sources. Associate them with sites, maintain their metadata and positions, and collect related instruments in manual groups.
Read the guide for instruments, sources, and groups →Store decimal or text readings against instrument-owned variables. Define names and units, inspect the value table, and follow changes across a selected time range.
Read the guide for variables and measurement history →03 / Analyze
Bring raw measurements, engineering calculations, and project context into the same review workflow.
Build decimal outputs from equations and source variables. Use calibration constants and time periods, and recalculate historical values when your calculation setup changes.
Read the guide for calculated variables →Locate instruments in Explore, open their details, and move between graphs and value tables. Select the time range and variables relevant to your investigation.
Read the guide for maps and instrument views →Combine time-series graphs, scatter plots, data tables, and Markdown notes. Arrange widgets around a project question and save a shared view for the team.
Read the guide for custom dashboards →04 / Collaborate
Set up anomaly review, notification recipients, and access around the people responsible for the project.
Define comparison or missing-signal conditions, select target instruments and variables, and inspect detected events. Missing-signal checks are evaluated as new project data is processed.
Read the guide for anomaly definitions and events →Use contact groups and email templates to configure anomaly notifications. Manage recipients at organization level and apply them to the relevant monitoring definitions.
Read the guide for email actions →Assign organization roles, project teams, and scoped access grants. Give project participants the visibility and management permissions their work requires.
Read the guide for teams and permissions →05 / Extend
Build ingestion clients and internal tools against documented APIs with scoped credentials.
Submit timestamped instrument observations from a gateway, an existing collection system, or a custom integration. Check the run outcome before treating data as available.
Read the guide for developer api ingestion →Query and manage the project resources exposed by the Developer API, including instruments, variables, values, and dashboards. The OpenAPI reference lists supported operations and required permissions.
Read the guide for developer api →Keep ingestion credentials separate from developer credentials. Set key permissions and scope in the platform, and revoke access when an integration no longer needs it.
Read the guide for controlled api access →Take a closer look
Explore how each part of SanSignal supports the day-to-day work of a monitoring team.
Data ingestion
Connect instrument readings through FTP and the SanSignal Ingestion API, with visible mappings and processing history.
Explore data ingestion →Instrument management
Organize monitoring projects, sites, instruments, sources, variables, and maps in a consistent asset structure built for field teams and engineers.
Explore instrument management →Engineering calculations
Create calculated variables with equations, calibration constants, cross-instrument inputs, and time-based calculation periods in SanSignal.
Explore engineering calculations →Dashboards & data exploration
Build monitoring dashboards with time-series graphs, scatter plots, tables, and contextual notes, backed by instrument values and project maps.
Explore dashboards & data exploration →Anomaly detection
Configure comparison and missing-signal conditions, inspect anomaly evidence, and route email actions to your monitoring team's contacts.
Explore anomaly detection →Teams & access
Manage organization members, project teams, scoped instrument access, dashboard audiences, and operational permissions in SanSignal.
Explore teams & access →THERE’S MORE TO SEE
Bring your instruments, your questions, your most complex site. Let’s connect the dots together.