Build a continuous project context from distinct sites and sources, with enough detail to investigate the readings from any work area.
Use a structure the site team recognizes.
A tunnel monitoring program can include underground work areas, surface observation points, shafts, and nearby structures. Create sites that reflect the project's working geography and use clear instrument identifiers aligned with the field register.
Record instrument positions in the correct coordinate reference system and use groups when a review needs instruments from several sites. Explore gives the team geographic context, while instrument detail provides the channels and history. Consistent naming matters as new sections and sensors join the program.
Keep different collection routes in one project.
Field collection may arrive through logger files, supported provider integrations, or a custom gateway. SanSignal supports FTP pipelines, Affinity mappings for supported profiles, and an Ingestion API for your own integration. Each route needs a clear destination site and dependable instrument identities.
Make connection commissioning specific to the source. Inspect representative file rows or payloads, verify timestamps and channel types, and confirm a known reading after processing. When a source offers historical readings, review its supported import path and the available coverage rather than assuming that live connectivity provides the full past record.
Keep interpretation connected to the measurements.
Use calculated variables where your measurement method calls for calibration constants, baselines, or relationships between channels. Inputs can come from the same instrument or another active decimal variable within the project. Set the external-input past buffer to suit the source cadence and intended method.
If the intended equation changes during the program, define its effective period and review the resulting historical recalculation. Build dashboards around a section or an engineering question, pairing trends and exact values with notes that explain the scope of the view.
- Distinct sites for work areas and observation locations.
- Calculated values with explicit references and calibration inputs.
- Saved dashboards for section-specific or cross-site reviews.
Keep review and operations connected.
Give field reviewers, integration operators, and project stakeholders the access their responsibilities require. A project team can receive site- or group-scoped instrument access, while dashboard viewers can use a focused saved view. Operators can inspect source activity and processing outcomes as the data flow changes.
Configure comparison and missing-signal conditions using the project's monitoring requirements, then inspect occurrences and email action results. Plan separate checks for a total source outage: missing-signal evaluation is driven by incoming project data and does not run as an independent timer.
Common questions.
Can the project include surface and underground instruments?
Yes. Organize the assets into suitable sites and groups within the project, with locations, channels, and dashboards that match the review needs.
Can we compare measurements from separate collection systems?
Once mapped into project variables, supported numeric measurements can appear in shared graphs, tables, and calculations. Verify timestamp conventions, units, and appropriate input timing before comparing them.