Materials testing laboratory
LabCore
The core platform for a concrete quality-control laboratory, from the truck to the compliance verdict.
- Sector
- Materials testing laboratory
- Components
- Core backend · Operations application · Client portal
- Stack
- NestJSMySQLNext.jsReact 19MQTTHeadless Chrome (PDF)ExcelJSRechartsS3-compatible storageJWT / Passportn8nOpenAPI
Follows a concrete sample from the pour through curing and testing to a certificate, and applies the code-defined statistics that decide whether it complied.
Concrete is sold before anyone knows whether it works. The whole quality system rests on a few cylinders crushed at fixed ages under ASTM methods, and measuring them destroys them.
The platform runs that chain end to end: orders, specimen traceability, results read from the testing machine, certificates, invoicing, and the statistics that turn numbers into a verdict.
Core backend
The domain model and every calculation, as a documented REST API.
Operations application
Customers, works, orders, specimens, agreements, roles, reports and documents.
Client portal
Order status, certificates, and the statistical analysis of a client's strength record.
Compliance is a three-part statistical evaluation
A test is the average of three cylinders. Running averages and individual tests are checked against the specified strength, and the verdict compares the general average against the required average strength.
Required strength depends on whose variability you measure
Over-design is derived from the standard deviation of the producer's results, per work, class, age and plant. Below fifteen tests it falls back to the code's fixed table.
Reading the testing machine directly
Results used to be transcribed by hand. A client on the press computer reads the machine over serial and publishes load readings to the browser over WebSockets.
The measurement destroys the sample
A cylinder is tested once and the structure cannot be re-sampled. Traceability from truck guide to certificate is the reason the system exists.
Projecting the 28-day result early
Early results project the mature strength through the ratio between ages. Where a site lacks history, an assumed ratio is used and marked as such on the report.
Replacing a system whose behaviour was the spec
There was no written specification for the legacy system. Screens were reproduced faithfully while genuine defects were separated from habits.
Documents that have to be defensible
A certificate is a formal statement about a structure people will occupy. Documents are rendered from the stored record and stay reproducible after the software changes.
Tell us where you are starting from. We take it from there.
Start a project
