What data for this category includes
This category of data includes measuring tool ledgers, calibration plans, calibration certificates, interim check records, original test records, reference material ledgers, and deviation handling documents. Data sources include enterprise metrology management systems, external calibration institution certificates, LIMS systems, and environmental monitoring equipment. Updates are initiated by calibration cycles, single test results, or abnormal events. Data fields include instrument number, calibration date, measured value, uncertainty, traceability chain information, environmental parameters, and more. Some documents must be associated with batches and product numbers to support tracing the impact scope of inaccurate instruments.
What constraints these characteristics impose on deployment and upgrade
This category of data is sourced from multiple systems. During deployment, connectivity for cross-system data synchronization must be configured. Update frequency varies widely, so dynamic adjustment of data pull cycles must be supported. Traceability chain fields require associated data storage, so the database must support associated queries. Documents such as calibration certificates require compliant storage, so storage paths that meet compliance requirements must be configured. Tracing the scope of inaccurate products requires association with production data, so docking interfaces with production systems must be reserved during deployment. Additionally, there are many document fields with inconsistent formats. During upgrades, the old data structure must be compatible to avoid migration failures.
How to configure settings
This configuration applies to FastGPT v4.17.0.
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
| Max database connections | 20–30 concurrent connections | Adapts to concurrent requests from multi-system metrology ledger synchronization, avoids connection exhaustion |
| Redis connection address | redis://:mypassword@192.168.1.101:6379/1 | Caches temporary calibration data and interim check status, improves ledger summary response speed |
| S3 storage endpoint | https://s3.cn-north-1.amazonaws.com.cn | Stores scanned copies of external calibration certificates and reference material ledger attachments, meets compliant storage requirements |
| File upload size limit | 1000 MB | Adapts to the large file storage needs of scanned calibration certificate copies |
| Data pull timeout | 600 seconds | Adapts to batch pull requirements for calibration data, avoids timeout interruptions |
| Frontend access domain | https://metrology.example.com | Adapts to cross-domain access for metrology management system frontends, ensures normal interface loading |
Three common configuration mistakes
- Incorrect configuration of file access token keys during deployment, resulting in 403 status code returned when accessing calibration certificate attachments (no response body). The cause is that the token key does not match the storage service's access policy, so valid access credentials cannot be generated.
- Failure to adjust the max database connections configuration after upgrade, resulting in database connection exhaustion when pulling metrology ledger data in batches, making it impossible to generate summary reports. The cause is that the default connection count is insufficient to support concurrent requests from multi-system synchronization.
- Failure to update the frontend access domain configuration after upgrade, resulting in the document interface failing to load system upgrade information and unable to find the upgrade plan entry. The cause is that the cross-domain configuration does not match the actual access domain, so the frontend cannot pull version information normally.
How to confirm configurations are properly applied
- Run a database connection test, confirm that metadata fields of calibration certificates can be read, such as instrument number and calibration date.
- Upload a scanned copy of a calibration certificate, verify that the file can be stored normally and a valid access path is generated.
- Generate a monthly calibration summary report, confirm that all fields from data sources are fully matched.
- View the system version information page, confirm that the latest version number can be displayed normally, verifying that the upgrade configuration takes effect.
The values provided are common starting points and should be measured against the reader's own samples.