Engineering guide
What data can engineers review after a trigger?
Know what sits behind the notification.
The X-7 application brochure describes configurable monitoring data from five seconds before and five seconds after a threshold event. The saved Shaba River X-7 record shows acceleration fields, tilt fields, a photograph and a staff finding. Confirm the delivered window, sample spacing and processing for the proposed configuration; the saved screenshot is not a full waveform export.
Sources: X-7 application brochure, page 2, Shaba River Bridge saved mobile record.
How much data is recorded around the trigger?
The manufacturer’s X-7 brochure gives five seconds before and five seconds after the event as a customisable configuration. Read the original statement on page 2. Treat this as a configuration to verify for the proposed X-7 hardware and software, rather than evidence of a particular delivered waveform.
For X-8, request a representative export for the proposed event configuration. The X-7 brochure alone does not establish the X-8 event window. Agree the trigger threshold, units, pre/post duration, sample spacing, timestamp definition and treatment of overlapping or interrupted events.
What does a real X-7 event record contain?
| Displayed field | Value |
|---|---|
| X acceleration | 1776 mg |
| Y acceleration | −168 mg |
| Z acceleration | 7224 mg |
| Tilt angle | 0° |
| Tilt direction | 0° |
| Staff handling entry | “现场施工，误碰” — accidental device contact during construction |
These are source-screen values, including the displayed units. They are not a time-series export, a peak particle velocity measurement, or proof of structural damage. The staff finding followed a site check. Original saved record.
The event and handling entries in the source have different dates. This guide does not use them to calculate a response-time claim. The Shaba River case guide walks through the saved evidence.
What should be in a representative export?
| Ask for | Why it matters |
|---|---|
| Device, asset point and configuration version | Connects the readings to the installed device and settings. |
| Event timestamp, time zone and trigger rule | Allows the team to align the event with an inspection or separate video. |
| Sample times, units and pre/post duration | Shows what the window actually contains. |
| Processing, missing samples and truncation rules | Explains what was changed or could be absent. |
| Photograph, reviewer finding and handling status | Keeps the human conclusion with the event, where the workflow supports it. |
Sampling, upload and notification are separate stages. A local sampling frequency does not establish the upload frequency, a continuous cloud record or the time at which a person receives an alert. Request those definitions and check them in the evaluation.
Can I use this as an API example?
The download below is a transcription of the visible Shaba fields with source and scope columns. It helps a team discuss the evidence. It does not define field names, an API payload or a guaranteed export format for X-7 or X-8.
Download the source-record transcription (CSV)For an integration, use the data handover checklist and request an actual sample from the proposed configuration.
Sources and scope
- X-7 application brochure, page 2Manufacturer brochure, English edition supplied for this review; publication date not stated. The full page is reproduced without retouching.
- Shaba River Bridge saved mobile recordX-7 project material, China. The guide transcribes the displayed values; it does not reconstruct a time series.
- Recorded platform views and data routesCaptured from the working China platform on 9 November 2026. Identifiers are omitted; views do not define an export schema.
Prepared from manufacturer materials and the project records named above. Engineering acceptance remains specific to the proposed installation.