Instead of WATS
Stop renting WATS. Own your production test review system.
We build your version around your products, test processes and quality reviews. Enterprise DNA brings your exported WATS records across, checks the history and runs the agreed system for you.
WATS Enterprise starts at €578 a month, annually prepaid. Its 1,000 MB upgrade adds €1,240 a month on that billing basis.
- check_circleYour data in a database you own
- check_circleOpen source, no lock-in
- check_circleBuilt and run by Enterprise DNA
What the WATS bill buys
The subscription follows your data volume
WATS combines collection, analysis and production features. Its published Enterprise base is €6,936 a year when prepaid annually. The 1,000 MB upgrade alone adds €14,880 a year. Start by identifying the review work your factory actually needs.
An ongoing Enterprise base
The published €578 monthly base includes 100 MB of analysed data per month on annual prepayment. Your review history sits inside that wider service.
More analysis capacity
WATS sells additional data allowances. The Enterprise upgrade to 1,000 MB is €1,240 a month above the base on annual prepayment.
Unlimited Enterprise users
Enterprise already includes unlimited users. The comparison is ownership and workflow fit, not a claim that WATS charges for every extra viewer.
A wider production platform
The paid platform includes unit-flow and analysis features. The free base here starts with exported test history and the review work around it.
Deployment choices
WATS lists a separately quoted on-premises option and private-cloud add-ons. Agree where your own records need to live before comparing the whole cost.
Exports for the move
WATS documents an export wizard for unit test reports. Bring the full history and its test steps across, then check the counts and results before switching the review process.
Your production review record
Results, retests and follow-up in one owned database
The morning review
Keep the first failure visible
A passing retest does not erase the earlier result. Review the evidence by product, revision and test process.
- check Separate first-observed results from the latest results
- check Count retested units without counting them as new units
- check Keep different test processes separate
- check Flag equal test times when order is uncertain
Find the pattern
Follow failed steps back to the unit
See recurring failed observations alongside the station and the units involved.
- check Group failing steps by product and station
- check Keep the original measurement values and verdicts
- check Read a serial number across its recorded processes
- check Compare daily test-attempt counts by product
Own the follow-up
Give each investigation an owner and a date
Add the work your quality lead wants beside the test evidence, without changing the original result.
- check Assign corrective follow-up to a named owner
- check Show overdue actions in the review list
- check Require evidence when closing an action
- check Keep notes and a dated history of recorded changes
Evidence on hand
Prepare the review paperwork from the same record
Turn the saved evidence into branded internal reports and private review drafts.
- check Produce a test history with its recorded steps
- check Prepare a corrective action record with closure evidence
- check Find missing station calibration-period references
- check Review access and retention dates alongside operational follow-up
Make it yours
Design your own WATS replacement
Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from WATS. Try it here, and we build the real one.
2. What it runs
3. Make it fit
4. Your colour
Answered from your own database
Good morning. Here is what needs you today.
We build it from the open-source base, bring your WATS data across and run it for you.
What it looks like
Ask it like you would ask a colleague
Real answers from the demo data that ships with Production Test for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.
Production Test for Claude Code
Connected to your own database
Which products passed their first recorded test?
source | part_number | revision | process_code | observed_units | first_pass_units | ambiguous_units | first_observed_pass_pct | retested_units | latest_pass_units ----------------------|-------------|----------|--------------|----------------|------------------|-----------------|-------------------------|----------------|------------------ Fictional Electronics | CTRL-10 | A | 10 | 4 | 1 | 0 | 25.00 | 1 | 2 Fictional Electronics | CTRL-10 | A | 20 | 1 | 1 | 0 | 100.00 | 0 | 1 Fictional Electronics | SENSE-20 | A | 10 | 1 | 0 | 0 | 0.00 | 0 | 0
Ask it anything
Questions your owned review desk answers
These are working queries on the fictional demonstration. WATS also provides analysis. The difference here is control of your records and review workflow.
Switching
How to switch from WATS
A move usually involves exporting your test history, mapping your fields and rules, checking the imported records, and running both systems side by side before you switch.
- 1
Export your WATS history
Use WATS’s documented export wizard to export UUT test reports as WSJF. Choose the reports and history you need for the reviews you plan to run, and note the report count and export filters. If you also need repair history, account for separate mapping or additional work. Keep the original export so you can refer back to the source evidence.
- 2
Load the export
Have the WSJF export loaded into the database. Start with a dry run, which checks the records without writing anything, then review the result before the actual import. Make sure the source count you expect matches the export and that the import records the actual source and operator. The original evidence is kept, including fields that are not mapped.
- 3
Review import findings
Check the report count reconciliation and any records the import rejects. Review the resulting history for uncertain ordering, such as tied timestamps, which can prevent a yield percentage from being shown. Confirm that the history you imported is complete enough for the questions you want to answer. An export that omits earlier attempts cannot establish lifetime first-pass yield.
- 4
Run both systems side by side
Keep WATS in use while you check the imported history against the records and reviews you rely on today. Compare source counts and selected unit histories, including failures followed by retests and results from different test processes. Use this short parallel period to identify gaps in fields, rules or workflows. Keep existing production controls in place while you assess what the new setup covers.
- 5
Switch off WATS when ready
Switch off WATS only after you have confirmed that the new setup supports the production review work you need and addressed any remaining requirements. The free version reviews exported test history, yield, retests and corrective follow-up. WATS also supports live collection and broader production functions, so scope any needed connections, repair workflows and screens before changing how the factory operates.
Where the real effort goes
Most of the work is usually mapping your own fields and process rules, then deciding which history to bring across. Test reports have a documented WSJF export path, while repair history and other layouts can need additional mapping or implementation. If you have Enterprise DNA run the setup, they handle this scoping and mapping work for your version.
Not ready for a call?
Get your WATS switch plan by email
We will send you the step-by-step plan for moving your business off WATS, what the move really involves, and how we would do it for you.
Sent. Check your inbox.
Your WATS switch plan is on its way.
Rather talk it through? Book a call arrow_forwardThree ways to own it
Start with the free base or have your version built
Open source
Do it yourself
Free, open source
- 1 Clone the repo, install dependencies and run npm run demo
- 2 Open the folder in Claude Code, Codex, OpenCode or Cursor
- 3 Export WATS UUT reports as WSJF and use import wats after a dry run
- 4 Set your brand and render the weekly view and documents
Built around your business
We customise it
One setup fee, then a retainer for ongoing work
- check Your products, process boundaries and review rules
- check Your WATS exports mapped and reconciled against source counts
- check Your required equipment connections scoped and tested
- check Your choice of screens, reports and database setup
Omni by Enterprise DNA
We run it for you
One setup fee, then a retainer
- check Installed with agreed access, backups and record handling
- check Your weekly production review prepared from current records
- check Your connections and reporting maintained as the factory changes
- check Run through Omni by Enterprise DNA alongside the rest of your business
Questions
Instead of WATS, answered
Is this a replacement for everything WATS does? expand_more
The free version covers exported unit test history, yield review, retests and corrective follow-up. WATS also supports live collection and broader production functions. Enterprise DNA scopes the connections, repair workflows and screens your version needs before you change the way the factory operates.
Can we bring our existing WATS history across? expand_more
Yes. WATS documents an export wizard for test reports. The free version reads its structured test export, checks the report count and keeps the original evidence. Repair history and other export layouts need mapping or additional work, which Enterprise DNA scopes for your version.
Will a passing retest hide the original failure? expand_more
No. Earlier results stay unchanged. The review shows first-observed and latest outcomes separately, within the same product, revision and test process. An incomplete export cannot establish lifetime first-pass yield, so the report labels what it actually knows.
Does the calibration check certify that a unit can ship? expand_more
No. It flags tests without a recorded calibration period covering the test date. The quality lead still checks the actual measurement evidence and follows the business’s release process. The internal reports are records for that review, not certificates.
What do we pay Enterprise DNA, and who owns the records? expand_more
There is one setup fee, then a retainer for the agreed customisation and operation. Your records remain in a database you own. In the call with Sam, we review your current WATS bill, the functions you use and the work required for your version.
Look at your WATS bill beside your actual review work
30 minutes with Sam. Bring the current bill, the test history you need to keep and the reviews your team repeats each week. We identify the right scope for an owned system and what needs to be connected before the move.
Production Test for Claude Code is free and open source, published by Enterprise DNA.
Done paying for WATS?
Get your version built