Docs/Getting started
Your first monitoring project
Set up a project, connect your first instrument, and give your team a useful view of its readings.
On this page
SanSignal brings instrument readings from field systems into one place. Start with a small, representative set of instruments, confirm the data, then expand to the rest of your site.
1. Join your organization
Sign in using the method available on your SanSignal deployment. If you received an invitation, accept it using the invited address. Your organization administrator assigns access to the projects and tools you need.
When organization creation is available, creating an organization also creates a default project, a default site, and your organization administrator membership. Rename and configure those resources before connecting production data.
2. Set up the project and site
Open Project settings and give the project a recognizable name, such as “Central station excavation.” Review the default site. Use Instruments → Sites to create more sites when you need separate locations or access boundaries.
Add positions or areas if you want to browse assets on the map. Confirm the coordinate reference system before entering survey coordinates. See Projects and sites.
3. Choose the source of your readings
| Your source | Start here |
|---|---|
| Delimited files on a remote server | FTP ingestion |
| A supported Affinity connection | Affinity integration |
| Your own logger gateway, application, or integration service | Ingestion API |
FTP and Affinity use organization-owned external connections granted to your project. The Ingest API uses a project connection and its own API key. Available integrations depend on deployment configuration and your permissions.
4. Verify one complete reading
Open Ingestion → Runs after the first file, delivery, or API submission. Inspect any failures. Then open the instrument and verify its site, timestamp, variable names, values, and units.
A successful API response or a healthy connection alone does not establish that the expected readings have finished processing. Check the resulting instrument data.
5. Make the data useful
Add aliases and units to variables. Create calculated variables when you need engineering equations or calibration constants. Build a dashboard with a graph and table for the same readings so your team can compare trends with exact values.
6. Configure monitoring and access
Create and test anomaly definitions, then connect email notifications if needed. Add members to teams and verify their effective access before handing over the project.
For commissioning, record a known source timestamp and value, confirm the stored result, review a calculation, and test the intended condition. This gives you a repeatable check when you add the next source.