Skip to main content

Dev Station Technology

Test and measurement equipment

Software that ships beside the instrument

Apps that pair with pull testers, gauges and torque tools, hold the reading, and turn it into a certificate somebody can rely on. This is the work we do most.

70%Faster reporting at a UK inspection provider
500%Rise in potential clients reported by one maker
2Apps shipped in parallel
40+Developers on staff
What this is

The app is the part between the tool and the certificate

An instrument produces a number. A customer needs a document. Everything between those two, the pairing, the thresholds, the evidence and the signature, is what we build.

We integrate against the maker SDK

Where the maker publishes one we use it, as we did with KTC for digital torque. Otherwise Bluetooth LE or a gateway.

Traceability belongs to the measurement

Not to the asset. Model it on the reading, or the certificate will not survive a careful assessor.

Services

What we build for instrument makers and testing firms

Instrument pairing and live readings

Bluetooth LE sessions that survive a glove, a cold morning and a basement.

Calibration certificates

Uncertainty, method and traceability on the document, generated from the reading.

White-label apps

Shipped with the tool, under the brand of the maker.

Proof-load and torque workflows

Step-by-step testing with thresholds and exception handling built in.

Dashboards and exports

Results that reach Power BI, a client portal or whatever the customer already reads.

Asset and due-date registers

What was tested, when, by whom, and what falls due next.

Standards

What a calibration record has to show

These are the details that decide whether your certificate is accepted or queried.

ISO/IEC 17025:2017Measurement uncertainty is required on calibration certificates. If your software cannot carry it, the document is incomplete.
Traceability on the certificateThe certificate shows traceability to national standards and the method used.
Calibration due datesUKAS policy is that a due date printed on a certificate is marked as a customer requested calibration due date. The wording matters, so put it in the template.
How traceability is describedMetrological traceability is an attribute of a measurement result, so phrasing like the equipment is traceable is incorrect. Model it on the reading.
Case study

Two builds in the same corner of the market

Dev Station digital testing platform for anchor and torque inspection
Inspection provider, United Kingdom

Work-at-height anchor and torque platform

Proof-load and torque checks ran on spreadsheets and email. We built the planning dashboard, the field app that reads testers over Bluetooth, and the certificate carrying GPS, timestamps and readings.

70%Faster reporting cycle
Hydrajaws pull tester application rebuilt by Dev Station
Equipment maker, United Kingdom

Hydrajaws Limited

A maker of portable pull testers arrived with an application nobody had documented. We rebuilt the environments, then shipped a free and a paid version with digital torque reading through the KTC SDK.

500%Rise in potential clients reported
Who we build for

The firms who call us

Instrument and tool manufacturers

Makers who want an app shipped with the product.

Testing and inspection providers

Firms selling the inspection, where the certificate is the product.

Calibration laboratories

Labs whose documents have to carry uncertainty, method and traceability without manual assembly.

Distributors and service agents

Teams maintaining instruments on behalf of somebody else, across many customers.

Related reading: digital gauge inspection, how gauge data flows and digital quality inspection.

FAQs

What buyers ask first

Which instruments can you read?

Those with a published SDK, and most that expose Bluetooth LE or a gateway. Send us the model numbers and we will tell you which ones we can read.

Can the app carry our branding?

Yes. We have shipped white-label apps for a manufacturer, including a free tier and a paid tier built in parallel.

Can it generate certificates automatically?

That is usually the point of the build. The certificate pulls GPS, timestamps, readings and the signature, so nobody retypes a number.

Who owns the code and the cloud accounts?

You do, from the first commit. Repositories and cloud accounts stay in your name.

Send us the model number

Thirty minutes with the engineers on the instrument you ship, what it exposes and what the certificate has to say.

Let's Talk