HOW IT WORKS
How a project
unfolds.
Four steps. For each step, what happens and what is needed from your side.
Book an intro callTHE PROJECT
From first call
to maintenance.
What is needed from your side
decreases once the project is under way.
- 01
Introduction
A conversation about the product, the variants and what currently happens between an enquiry and a quote. By the end there is a first assessment of whether DriveWorks fits. Sometimes the answer is no.
From your sideSomeone at the table who really knows the process. Often the engineer or the internal sales team.
- 02
Analysis and advice
Mapping out the product rules, reviewing the models and deciding which package fits, where needed with a proof of concept using the actual product. The result is advice on package and approach, and an estimate for the project.
From your sideA few existing models and drawings, and time to explain the rules behind the product.
- 03
Automation
Preparing models, capturing the rules, automating drawings and building the configurator. By the end, the model, drawing and related documents are generated automatically, and the necessary information passes on to the systems already in place.
From your sideReviewing interim deliverables, and flagging the exceptions now rather than after handover.
- 04
Keeping it up to date
Making changes when the product changes, and helping think through extensions. By someone who knows how the configurator was built.
From your sideReporting when something changes. Nothing more.
ALONG THE WAY
When is it clear
whether it works?
Not only at the end.
With a proof of concept, it becomes clear using the actual product whether DriveWorks can handle this custom work, before the main work starts. After that it moves into interim deliverables: as soon as a first working version exists, it can be put into use. Functionality is then added step by step, so gradually less is done by hand and adjustments can be made along the way.
WORKING TOGETHER
Steady involvement.
Flexible capacity.
No fixed hours to be tied to, but someone who knows your setup and can help quickly when it is needed.
A fixed half day or a fixed day each week. More when a project calls for it, less when things are quiet.
A quick question or a quick look at a configurator does not have to wait until the fixed day.
Direct contact with Simone, without a ticket or appointment.
ConfiCreate builds with its own SolidWorks and DriveWorks licences. The company does not need to provide anything for that.
The work is done from Wijchen. That means capacity can flex with what a week needs, without having to schedule a day on site.
TO BE FAIR
And if the company
does it itself?
Doing it in-house is possible. Some manufacturers run DriveWorks perfectly well themselves, and sometimes that is wiser than outsourcing. It mainly gets difficult when nobody really has time for it.
What it takes
- An engineer with time
- A DriveWorks licence
- Room to really learn the software, not on the side
Where it gets stuck
- Models that first have to be rebuilt
- The ERP integration, which needs knowledge of two systems
- Maintenance, once the person who built it leaves
A collaboration works too: an in-house engineer handles the drawings, ConfiCreate builds the configurator and the integrations. Or ConfiCreate supports an internal team.
WHO DOES WHAT
A partner,
not a reseller.
A reseller sells the DriveWorks licences and provides support for them. ConfiCreate builds the implementation and does not sell licences. Advice on which package fits is therefore completely independent.
THE NEXT STEP
Curious what a project like this
looks like for this product?
A conversation about the product and the process
is enough to see which way it could go.