Why Dezide · Evaluation
From proof to business case
Every Dezide engagement runs the same staged path. One week in your training facility proves it works on your equipment.
Five months in the field, with every technician you want to include, proves its worth. Each step answers one question, and you see the answer before you commit to the next step.
Evaluation
Evaluation
1
Proof of Concept
Does it work on our equipment?
Test results in hand → prove it in the field
2
Pilot
What's the business case?
Business case approved → roll out
Partnership
3
Onboarding
How do we roll it out?
Continuous optimization
Week 0: scope and clearances
Week 1: the PoC
Readout
4 to 8 weeks: your decision
Months 1 to 5: the Pilot
Business case
Rollout
One question per step. Evidence before investment.
Each step is scoped to a single question, and every answer comes from your own troubleshooting knowledge. If the answer is no, you find that out in week one, and it costs you a week.
What other manufacturers measured
The same test, run by three customers
Each of these numbers came from a structured comparison.
Real faults, the customer’s own technicians, solved with and without Dezide.
It is the same test your week would run.
66%
faster
“In one area, the results show that we reduced the average troubleshooting time by 66%. Still, the technician solving these issues more efficiently was not an expert in this area.”
Marc Van der Burght
Chief Operating Officer, Ion Beam Applications
70%
faster
“We have proven that our technicians can solve complex problems up to 70% faster using Dezide’s causal AI-powered troubleshooting technology combined with our technical expert knowledge.”
Ulrik Henriksen
Head of Diagnostics,
Siemens Gamesa Renewable Energy
72.7%
more efficient
“Tests showed that technicians using Dezide could troubleshoot an average of 72.7% more efficiently than traditional methods.”
Stäubli
The pattern is the same in all three. The gap closes hardest for the technicians who are furthest from the expert, which is where most of your service cost sits.
The two steps in detail
This page outlines the Dezide evaluation process, focusing on the two key phases to validate the platform on your equipment: Proof of Concept and Pilot. Discover timeframes, resource requirements, and expected outcomes.
Use the links below to jump directly to the sections that interest you.
Step 1 – Proof of Concept
Step 1
Proof of Concept
✓
One week.
✓
Your training facility.
✓
Your machines.
✓
Your faults.
✓
Your technicians.
Does it work on your equipment?
The week runs in the training facility where you train new technicians, on the machines you train them on. We introduce real faults into a real machine, the same faults the guides cover, and your technicians fix them. If a training facility is not available, we can run the test in the field on a live machine instead.
Controlled conditions are what keep the comparison clean. Same faults, same difficulty, one variable changes.
What happens
One week, five steps
1
Agree the cases
Before we arrive, we work through the cases relevant to the PoC and pick two or three real fault cases together. We recommend the faults that eat hours, generate the most warranty cost, or send technicians back to HQ for help.
2
Build the guides
We sit down with one or two of your best troubleshooters and turn what they know into guided troubleshooting in Guide Builder. Two days. We arrive with drafts already prepared from whatever documentation you send us, so day one starts with review rather than a blank page.
3
Set up the test
We finish the guides and set up the machine. We make sure the faults we modeled in the guides can actually be entered into the machine.
4
Run it
Faults go into the machine. Senior and junior teams solve them the way they work today, and the same class of faults with Dezide. We record time, steps taken, and parts touched, for every run.
5
Present the results
The week ends with a live readout. We walk through the measurements side by side, what they mean, and what a Pilot on your installed base would look like.
What we need from you
What the week actually costs you
+
Two or three fault cases
Chosen with us on a one-hour call before the week starts.
+
One project owner
Across the week, to keep the schedule and the people moving.
+
One or two subject matter experts, full time on days 1 and 2
This is the real ask. The guides are built from what these people know, and there is no substitute for having them in the room. Two days, and they are free from day three.
+
Two to four teams of technicians, a few hours on days 4 and 5
A mix of senior and junior. Junior technicians are included deliberately. How far Dezide closes the gap between your newest technician and your best one is one of the things the week measures.
+
Your training facility
With a machine we can introduce faults into. Or a live machine in the field.
+
Whatever documentation exists
Manuals, wiring diagrams, decision trees, work orders, service reports, and the spreadsheet somebody keeps privately. Scattered, inconsistent and out of date is normal and is fine. It is what we expect to find.
What it costs
The PoC is a fixed fee plus travel, quoted in writing before you commit. Nothing on it is variable and nothing arrives afterwards. If you decide at the end of the week that Dezide is not the right fit, there are no hard feelings and no further costs.
Why a week is enough
Five days works because the scope is deliberate
The week is short because of what it proves. Every item we leave out matters, but none of them changes the answer to the question the week asks, and each one is covered in the Pilot, where there is time to do it properly.
The week goes into the Causal engine
Most systems have to be fed before you can judge them. Weeks of preparing, tagging, and analyzing your documents, and only then do you find out what the software actually does.
We spend the week on one thing: the causal AI that works out the best next step at every point. That is the part your technicians feel on a machine, and two or three guides are all it takes to measure it.
In scope
What the week tests
✓
Two or three representative fault cases, agreed in advance
✓
Guided troubleshooting built for those cases with your experts
✓
A measured baseline, then measured runs with Dezide
✓
Whether Dezide works for your technicians, on your equipment, across levels
Out of scope
What the week deliberately leaves out
✕
Preparing your existing documents, work orders, and tickets so the platform can draft from them
✕
Coverage of your full fault catalog
✕
Integration with your identity provider, machine data or ticketing system
✕
Rollout, training and change management
What you get
What you walk away with
✓
A measured comparison
Troubleshooting time, steps taken and parts touched, with and without Dezide, on your own equipment, across senior and junior technicians. Your numbers, from your machines.
✓
A live readout, then the full analysis in writing
We present the findings to your team in person and answer the hard questions on the spot. The written report follows, with the method, the raw measurements and the comparison, built so you can forward it to people who were not in the rooms.
✓
A scoped Pilot proposal
Which sites, which technicians, which equipment, which KPIs, and what it costs. You have the next step on the table while the results are still fresh.
Anonymized, available on request.
Between step 1 and step 2
The Pilot starts on a purchase order
One week answers the first question. Dezide works on your equipment. The second question is still open. What it is worth across your organization. Adoption in the field, results at every skill level, impact on first-time fix and truck rolls at scale. All of that needs field testing and a bigger sample. That is what the Pilot is for.
1
The report and the Pilot proposal arrive together, within a week
Both are in writing and built to be forwarded. You are not waiting on a quote, and we are not waiting on a request.
2
Your legal and security review is already done
Terms, IT, security, and data processing were settled before the PoC week began. Those reviews are the most common reason a pilot start slips by a quarter. We take them off the critical path before they can.
3
Four to eight weeks for your decision
A budget line, a sponsor, an approval. We can join the internal presentations and answer Finance's questions. Then, one purchase order against the proposal you already have, and month one begins.
Nothing from the week is thrown away
The Pilot is the same work, continued, at field scale.
✓
The guides your expert built in week one are the guides your technicians use in the Pilot.
✓
The baseline measured in your training facility is the baseline the Pilot measures against.
✓
The KPIs agreed in the readout are the KPIs on the final business case.
✓
The method is the same, so the numbers stay comparable from week one through to the decision.
You are not starting again. You are widening what you already proved
Step 2
Pilot
✓
Five months.
✓
In live operations.
✓
Every technician you want to include.
What is the business case?
A business case needs field results. Real dispatches, technicians at every skill level, and results measured across enough cases.
The Pilot produces those results. It takes the guides from your PoC, expands them into a working knowledge base, and puts them in your technicians' hands for live operations.
There is no user limit during the Pilot. Every technician you want to include is included, for the whole five months. How large a sample your business case needs is your decision to make, and licensing is a conversation for afterwards.
What happens
Five months, five steps
1
Align on goals and scope
Together we settle what this has to prove. The target date for your first release, which location goes first, how many technicians are in the first group, and what result you need to put in front of management at the end. We recommend staying on the product from your PoC, and starting in one country, ideally the one your HQ sits in, so support and communication stay close.
2
Learn how to capture expert knowledge
We hand over the method. Twenty-five years of capturing, validating and sharing troubleshooting knowledge, distilled into a process your own people can run.
3
Build the starter knowledge base
Months one and two. The guides from your PoC expand to a critical mass, so a technician who opens Dezide finds what they need and comes back. We prioritize the faults that eat the most hours, the ones that recur most often, the ones new technicians struggle with, and whatever your PoC technicians asked for.
4
Give the tool to your technicians
Month three. Dezide goes into the hands of the field group, with a communication plan, material tailored to each user group, and close support from the project team. One region and one language to start with, on purpose, so the first experience is a well-supported one.
5
Measure what matters
Month four is a full month of live troubleshooting. Month five is the analysis. We track the KPIs you agreed in the PoC readout against your baseline, and close with the results and what they project to across your installed base.
Months 1–2:
Build the knowledge base
Month 3:
Into the technicians' hands
Month 4:
Measure in the field
Month 5:
KPIs and business case
Five months is the standard shape and we orchestrate the whole project. The knowledge base has to exist before a technician can rely on it, which is why the first two months build rather than measure. By month three your technicians are working with it, and by month five you have the numbers.
What the pilot adds
The things the week left out
✓
Coverage, and how the knowledge base gets built
A business case needs enough guides that a technician opening Dezide reliably finds what they came for.
Guide Builder drafts guides from the documentation you already have. Manuals, service reports, work orders, and the material your experts have written over the years. Your experts then review and correct, which is a different job from writing from a blank page and a much smaller one. Their time goes into the judgment only they have.
Drafting speed matters enormously once you are building at scale.
✓
Integration
Dezide connects to your identity provider, so technicians sign in the way they already do. Where machine data is available, we connect it, so the guide reads a fault code and answers its own questions instead of asking a technician to go and look. Where an issue needs to leave the field, we can escalate it into your ticketing system. We scope all of this with your IT team during step one and it runs alongside the guide work.
✓
Adoption, training and change management
A tool your technicians do not open produces no business case, so adoption is part of what the Pilot measures. We run the rollout with you. A communication plan, materials tailored to each user group, stakeholder mapping, and close support within one region while the habit forms.
We will also tell you what to expect. Adoption climbs steadily rather than vertically, tracking the growth of the knowledge base. Even our largest customers, with thousands of technicians, do not see universal usage. What they see is a small set of KPIs moving hard, and first-time-right resolution usually carries the business case.
What we need from you
What the Pilot asks of your organization
+
Two hours a week from your experts
Over Teams or Zoom, for knowledge transfer. That is the whole recurring commitment. Your experts review and correct rather than write from scratch.
+
Your knowledge assets
Product documentation, service history, and your team's expert knowhow. The same material as the PoC, at greater volume.
+
A technician group and a starting region
As many technicians as you think you need for a defensible sample, since there is no user limit. We recommend starting in your HQ country, in one language, where communication and support are easy.
+
A project owner
Ideally the same person who ran the PoC. Continuity is worth more here than seniority.
+
A scoped IT engagement
For the identity provider, the machine data connection, and any ticketing escalation in scope. Defined during step one so there are no open questions later.
+
The KPIs, carried over
Whatever your business case turns on. We keep the success criteria you set in the PoC readout, so the numbers stay comparable from week one to month five.
What it costs
A fixed package fee for the five months, with every technician included and full platform access. Scope and price are proposed in your PoC readout, so you see both before the PoC week is over. At the end of the five months you can walk away. If you continue, we agree a licensing scheme that fits your organization.
What you get
What you walk away with
✓
Your numbers, at field scale
KPI results from live operations across the technician group you chose. The sample size finance asks about is the sample size you will have.
✓
A business case you can defend
Measured impact projected across your install base, with the baseline and the method documented. Built by your team, on your terms, and ready for your decision process.
✓
Proof of adoption
The evaluation covers two things. Whether Dezide performs and whether your technicians use it. The Pilot answers both across skill levels and sites.
We survey your technicians to hear their feedback on the experience.
✓
A working knowledge base, and the method to keep building it
The guides stay. So does the process your people learned to capture, validate, and share what your experts know. Whatever you decide about the platform, that knowledge is now written down.
Proof
“We expected it to make troubleshooting faster. What we did not expect was to find out why our own service strategy was not landing. We could see where our technicians actually got stuck. That turned it from a tooling decision into a number our management looks at.”
Marc Van der Burght
Chief Operating Officer, IBA
Step 3
Decision made. Then what?
The Pilot ends with everything a decision needs. Field-proven results, adoption feedback, a working knowledge base, and a business case built on your numbers. At that point, you can walk away, or you can roll Dezide out properly.
Rolling out to a full service organization is a change project, and it gets treated as one. Our Implementation Framework starts once you are on contract. It is a complete toolbox for rollout: detailed assets, plans, and communication strategies, grounded in change management practice and built from twenty-five years of deploying Dezide inside global manufacturers. The Pilot proved it in one region. Onboarding takes it to all of them.
How onboarding works →Start with one week
Bring two or three fault cases, one expert, and access to your training facility. We bring the guides, the method and the measurement. Five days later you will know, with your own numbers, whether Dezide works on your equipment. If the answer is no, it cost you a week.