Products
products
Product Value Management Platform
Propel PLM
Propel PIM
Propel QMS
Take Product Tour
p
Propel One
Product Spotlight
Supplier Community
Featured Resources
eBook
Product Value Management Handbook
Read More
Solutions
Processes
New Product Development
Custom Product Development
Compliance Management
Product Quality
Product Go-To-Market
Supplier Management
Field Service Enablement
roles
Design and Engineering
Product Management
Quality and Regulatory
Service and Support
Supply Chain and Production
Information Technology
Marketing
Sales
Featured  Resource
Article
Survey Says: Your Value Chain is Broken
Read More
Platform
Platform
Power of the Platform
Built on Salesforce
Salesforce Platform
Propel Trust Center
Enterprise Integrations
Featured Resources
Article
Trust and Security with Propel
Read More
eBook
5 Steps to Unify Product and Customer Data With Salesforce
Read More
Pricing
Customers
success
Customer Case Studies
Customer Testimonials
Industries We Serve
Featured Resources
Video
Propulsion 2025
Watch Now
eBook
The 5x5 Program: A Proven Framework for Business Transformation
Read More
Resources
resources
Resource Library
Blog
Podcast
Newsroom
Converged by Propel
Industry-leading articles, videos, and podcasts at the intersection of product innovation and market evolution.
Read the latest
resource type
Ebooks
Podcast
Whitepapers
Events
see all resources
E-Book
Resource Title Lorem Ipsum Dolor Sit Amet
rEAD More
Converged Blog Lorem ipsum dolor sit amet
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Sed risus arcu, imperdiet ac pretium mattis, gravida varius nibh.
rEAD More
LoginGet Started
Get Started

Propulsion 2020 Core Manufacturing Session - Win More and Increase Margins: The Duality of Effective ETO Processes

Transcript

[DISCLAIMER] The following transcript is being delivered UNEDITED via a streaming service. This transcript has not been proofread. It is a draft transcript, NOT a certified transcript. It may contain computer-generated mistranslations and spelling errors.

‍

Introduction: Be’Anka Ashaolu, Director of Marketing, Propel (BA)


1

00:00:03.000 --> 00:00:09.990

BA: Custom engineered products generate more sales and higher margins. If sales and engineering can work together effectively and efficiently.


2

00:00:10.410 --> 00:00:20.850

BA: Many times require coordination is error prone difficult and time consuming but there is a better way and manufacturers are increasingly using technology to deliver on the promise of mass customization.


3

00:00:21.420 --> 00:00:30.810

BA: In this session here from to engineer to or industry leaders discuss how they compete by aligning these teams for smoother faster earlier communication in the product lifecycle.


4

00:00:31.110 --> 00:00:39.120

BA: Ensuring proposals and designs deliver what customers need tighter collaboration ultimately winning or business and delivering more profitable orders.


5

00:00:39.630 --> 00:00:53.100

BA: Propel, VP of customer success. Mary differentiate moderate this panel featuring damn boy CEO Glenn tech and you're from is CEO and director of a MS technologies. Let's get into the duality of effectively to processes now.


Session Moderated by Mary DeFrenchi, VP of Customer Success, Propel

Panel: 

Daniel Voit, Blentech

Jan Maise, AMS Technologies


6

00:00:55.590 --> 00:01:05.850

MD: Good morning. My name is Mary differentiate. I am the VP of customer success here at propel today I am joined by yon mice from AMS technologies and Daniel Voit


7

00:01:06.510 --> 00:01:16.680

MD: On in the morning, both. And thank you for joining me today. I'm really excited to have to search industry experts CEOs to discuss their digital transformation strategy.


8

00:01:17.970 --> 00:01:19.860

MD: So welcome Dan, welcome Jan


9

00:01:21.240 --> 00:01:23.580

DV: Good morning. Thanks for having us. Thank you.


10

00:01:25.050 --> 00:01:36.000

MD: And so here propel we talk a lot about engineer to order vs custom engineer products in mass customization. Jan, let's start with you. How would you describe your business today.


11

00:01:37.200 --> 00:01:47.010

JM: Well, our businesses is is twofold. So we do have some standard products which we sell which we get for our suppliers as a distributor of components and


12

00:01:47.430 --> 00:01:56.010

JM: Makes about like 20% of our revenue today, but our focus really is on customized products and engineered solutions. And so it's basically like three


13

00:01:56.310 --> 00:02:10.680

JM: Segments one being the standard products where we sell like one product many customers and we have the customized products and the engineer solutions where we have one product or solution going to one customer and that already makes up 80% of all revenue today.


14

00:02:16.620 --> 00:02:27.720

DV: How would you describe our business. Um, well I we might come from an angle of having less standardization. To begin with, then the main focus, we become from the roots of custom from from the beginning and


15

00:02:28.560 --> 00:02:37.140

DV: So we designed food processing equipment and we were founded by the adventure that mechanical grade harvester and innovation was part of what we did.


16

00:02:38.010 --> 00:02:46.890

DV: As we're growing we're developing standardized solutions standardized elements, but try and keep that custom spirit and scale through that.


17

00:02:49.530 --> 00:02:58.530

MD: Thank you. And  Dan what would you say are some of the benefits and challenges, you know, running a custom engineer products are from your perspective.


18

00:03:00.000 --> 00:03:11.160

DV: Well, there are many benefits to the challenges the benefits are you can sue the customer. Ideally, with the product you can you can tailor make it to to them.


19

00:03:12.510 --> 00:03:18.510

DV: And you know that that ends up really accomplishing normally most of what they be done.


20

00:03:19.800 --> 00:03:27.870

DV: And so that's it. That's a great partnership, but when you do that you end up often creating new designs you create new programs.


21

00:03:28.680 --> 00:03:40.620

DV: And there's an early risk every time something is done for the first time. So, managing that is one aspect of managing it profitably. It's probably a bigger aspects for everyone.


22

00:03:42.090 --> 00:03:48.810

DV: You can get it done and not succeed or you can get it done exceed or you can get it done 16 and everyone profits and that's really the goal.


23

00:03:49.800 --> 00:04:03.330

DV: At the end of the day, I think probably the biggest challenge internally, though. That's from a customer perspective is is scalability of the corporation that when you're when you're focused on custom solutions customization.


24

00:04:05.040 --> 00:04:06.840

DV: Engineer to order type things.


25

00:04:07.860 --> 00:04:17.100

DV: You're very dependent upon highly experienced individuals, which take a long time to train and you can do a great job with employee retention programs and all those sorts of things.


26

00:04:18.180 --> 00:04:20.040

DV: But the fact of the matter is slow to grow.


27

00:04:21.270 --> 00:04:23.040

DV: Because it takes a while to train those people


28

00:04:25.350 --> 00:04:33.300

MD: And I know Dan before we've been talking recently about, you know, the whole move to having an entire remote workforce and how that's changed your business a little bit and


29

00:04:34.200 --> 00:04:42.270

MD: You wouldn't mind kind of sharing what you quickly realize and what we had to make to deal with that quickly, especially with hiring structures that we just talked about.


30

00:04:42.990 --> 00:05:00.510

DV: Sure, sure. Well, we've been we've been on our process of digital transformation, if you will, for a few years you moving starting from the front end sales were down through the operations. I would say we're most of the way through. When the credit crisis hit and we were able to move


31

00:05:01.950 --> 00:05:11.430

DV: The majority of our company to remote work obviously manufacturing, it's we haven't figured out how to weld remotely and I hope we get there someday, but that hasn't been accomplished yet.


32

00:05:12.510 --> 00:05:26.910

DV: And so that the fabrication team, things are still on site and we appreciate them, but we were still able to socially distant huge aspects of our Corporation, all of the engineering divisions that you see in the hotel tools.


33

00:05:27.960 --> 00:05:36.510

DV: Coordinating communication and timing of who needs to work together with with facing document Control. Control across that it's been huge.


34

00:05:37.260 --> 00:05:47.730

DV: I think the bottom line can be stated in numbers we've been able to keep the factory running through this crisis at or above 100% majority of the time.


35

00:05:48.960 --> 00:06:00.990

DV: And I think that speaks for itself. It wasn't always easy but adaptation simply isn't it will get easier and and the the tools that we use really made it possible, and we're getting into our group.


36

00:06:04.020 --> 00:06:08.670

MD: Yeah. And Jan what would be some of the benefits and challenges that you're seeing in your business model.


37

00:06:09.300 --> 00:06:13.800

JM: Yeah, it's, it's very similar to what put down where it says, oh, one of the things is, I mean,


38

00:06:14.070 --> 00:06:23.040

JM: A lot of the products which we are designing and which were designing for our customers are not actually end user product. So we actually are in the OEM manufacturers, so


39

00:06:23.310 --> 00:06:31.110

JM: A lot of the components which to or subsistence, which we make are being sold to a customer who then that's it into something else and then sells them to their customers. So


40

00:06:31.410 --> 00:06:37.410

JM: A lot of what we experience there is that we have much, much closer relationships, our customers. That's where


41

00:06:38.340 --> 00:06:49.890

JM: A lot of what we do is now instead of just being a manufacturer or a supplier to our, our customers. We know collaborating collaborating together and we are developing solutions, not just for our customers, but for our customers. Customers.


42

00:06:50.250 --> 00:07:02.880

JM: So we are much, much closer to understanding the needs of our customers and that drives a complete different behavior of of a partnership which historically has just been the supplier and customer


43

00:07:04.200 --> 00:07:06.390

JM: But absolutely, yes. If it doesn't come with


44

00:07:07.440 --> 00:07:15.720

JM: Challenges and as Dan has already said, yeah, it comes with overhead. There's a lot of costs of overhead would need to add to it, just by


45

00:07:16.530 --> 00:07:27.900

JM: All the proliferation of, of all the different components of subsystems, which are being used and that is the challenge and you somehow need to maintain that and also to use technology to be able to


46

00:07:28.560 --> 00:07:38.940

JM: To reduce that as much as you can. And you do need obviously when you are engineer to order, you still need to work a lot of documentation.


47

00:07:39.690 --> 00:07:44.730

JM: Documentation of anything from state in a word specifications fortification quality.


48

00:07:45.090 --> 00:07:54.090

JM: final test final inspection. A lot of that stuff needs to get done and obviously puts a lot of constraint on on the back end and operations. Also on supply chain.


49

00:07:54.840 --> 00:08:02.820

JM: Manufacturing managing all of those suppliers, because it's a plethora of of new suppliers, which are coming on board, just because of that you're


50

00:08:04.440 --> 00:08:09.060

JM: proliferating your, your products and your services to a much wider audience.


51

00:08:10.800 --> 00:08:17.850

DV: Do you mind if I add something to that add on to what Jan’s saying. Yeah. In one thing that we thought about


52

00:08:18.870 --> 00:08:24.330

DV: How this has been the help desk. You talked about the complexity on the different groups having to interact


53

00:08:25.170 --> 00:08:31.980

DV: We studied the way our company works and started building out our processes to use these technologies across Past few years in excess of


54

00:08:32.820 --> 00:08:41.220

DV: 15 stages and phases that from the life cycle of the other products we get into the the design phases of the of the systems that we build


55

00:08:41.790 --> 00:08:49.020

DV: We have in excess of eight departments collaborating eight different functional departments collaborating just during that phase.


56

00:08:49.560 --> 00:09:00.750

DV: And so then that's not just as much as eight linkages, it's, it's a by across all the other different departments, they connect and so it's just not possible to communicate effectively without


57

00:09:01.500 --> 00:09:12.600

DV: Good technology to identify the order in which those communication up to happen and raise a flag when those communication haven't happened, creating those triggers triggers and checks for a proper management.


58

00:09:13.950 --> 00:09:18.300

JM: Absolutely. We have exactly the same thing. The collaboration needs to go through so many different


59

00:09:18.600 --> 00:09:26.130

JM: Groups and also customers and we use all kinds of different technologies to make sure that we can collaborate and then we can share information and the


60

00:09:27.000 --> 00:09:35.100

JM: Information. He is not residing them an email, which then sings that in the PSD file somewhere. But that actually resides somewhere on


61

00:09:35.430 --> 00:09:48.900

JM: The actual item or whatever the item is via the quality item or be at the the product item or whatever they actually the actual object is which we are talking about store the documentation there be a great


62

00:09:50.160 --> 00:09:56.880

MD: Wonderful, thank you. So given what you've learned or seeing, you know, over the years, being in this industry.


63

00:09:57.300 --> 00:10:03.750

MD: You know, why should manufacturers dive into this industry spec mentor on the reverse. Why should they not to stay away from, in your opinion.


64

00:10:04.200 --> 00:10:20.400

MD: And can launch. You start with your thoughts. But my question is, why should people consider me to the to the moment. 


DV: Okay. Well, I mean, I think the probably the single most valuable aspect of working in a retail environment for manufacturer is


65

00:10:21.450 --> 00:10:30.570

DV: It really does accelerate your ability to innovate, you start working directly with customers on real problems on the fly. We are going to call that in process Rd and our company.


66

00:10:31.980 --> 00:10:47.520

DV: Now that's amazing that you can get your innovations and technologies in use in operation far faster than incubating them and thinking about them and then developing a marketing plan and hoping it works and then finding it wrong. It's go back and change it.


67

00:10:48.720 --> 00:11:06.150

DV: You know, which is a waste of everyone's time and money. But the thing I think you have to keep in mind is everyone has to be aware of what aspects of what you're doing is new and what aspects are not new. So that all parties customer especially has it in their risk calculation.


68

00:11:07.980 --> 00:11:22.740

DV: That they understand what what's part of it and the manufacturer needs to be prepared to not necessarily make money on new developments and so a key would be after you develop them you've developed customer translation. Can you sell them out elsewhere.


69

00:11:24.990 --> 00:11:28.740

DV: Will you be able to use the elements that we should create it in a way to further scale your business.


70

00:11:29.910 --> 00:11:38.100

DV: So I think it's about open communication with the customers and working with the customers within less of a transactional sense and


71

00:11:39.240 --> 00:11:46.710

DV: More as though they're part of your team and you're part of their team and you're working toward that common goal. And I think that can change things.


72

00:11:50.610 --> 00:12:03.750

MD: And what about the so I guess kind of Internet is kind of that whole customer experience obviously that shifted and like you said your long game with the customer and being able to you know address changes or requirements differently through this process.


73

00:12:06.780 --> 00:12:11.910

MD: And you repeat the question. No, I was just kind of backing up your statement sorry again. OK.


74

00:12:14.520 --> 00:12:25.350

MD: And Jan. What about your thoughts there. 


JM: It's so again we're we're selling OEM solutions to our customers and our customers need to differentiate


75

00:12:25.800 --> 00:12:38.880

JM: And the differentiation is not getting writing down the lowest cost denominator. Yeah, we're all our customers need to somehow differentiate themselves from their peers and that's as Danny said


76

00:12:39.900 --> 00:12:48.780

JM: Through innovation. And there's different innovations which you can do either you you will take logically. Yes. And we embed a lot of different technologies into our


77

00:12:49.320 --> 00:13:03.930

JM: Systems and systems. The other one is feature sets. So we need to work with our customers understanding isn't what their customers need for them to be successful. And the next one is make those units serviceable so that


78

00:13:04.710 --> 00:13:13.560

JM: Whatever we have put together then is server serviceable out there in the field so that very quickly. The uptime is always as close to 100% as possible so


79

00:13:14.820 --> 00:13:22.800

JM: We see that obviously we're not in playing in the market of very high volume. So we're not playing in the automotive market. So we're more in the


80

00:13:23.670 --> 00:13:36.900

JM: High a mix LOW TO MID volume markets and that's where customers really are looking for. How can they bring the differentiation to their to their customers. That's where standard products really are not available. And that's where I think we will


81

00:13:41.280 --> 00:13:44.490

MD: See, and you see this is a growing trend in manufacturing


82

00:13:45.570 --> 00:13:47.040

JM: Absolutely, especially in the


83

00:13:48.240 --> 00:13:55.050

JM: In the, let's say Western side. Yeah, we see that here in Europe, quite a bit. Yeah. So we there was obviously standard products which you can


84

00:13:55.530 --> 00:14:00.960

JM: Buy it from multiple sources. But when you we are engaged with the customer on ETS programs.


85

00:14:01.560 --> 00:14:16.740

JM: You are locked together, you win or lose together and you're trying to make a win win situation so that they are winning in their customers. And we do see quite a few projects which are completely through through our phone. Oh, absolutely. We see growth.


86

00:14:19.110 --> 00:14:20.640

MD: Dan what about from  your perspective.


87

00:14:21.840 --> 00:14:31.260

DV: Yeah, you're asking do we see a growth in in this type of product. I think the answer is yes. And we've always seen that there because it's where we you know we began


88

00:14:32.220 --> 00:14:38.880

DV: I think what I would say overall is that some more. More and more of the customers are looking for.


89

00:14:39.450 --> 00:14:50.760

DV: Products that are helping them create their own differentiating edge, and as a result they need you to customize something for them create something special for them that allows them to hold some kind of an enduring edge.


90

00:14:51.930 --> 00:14:59.820

DV: But I think what's probably changing and growing is is the customers understandably want that customization at a standardized price and delivery.


91

00:15:01.320 --> 00:15:10.230

DV: Which that's the nature of business, but that's where the opportunity lies. And so from our perspective, it's the question internally is how do we use technology.


92

00:15:10.770 --> 00:15:23.820

DV: To allow us to create customized tailored solutions for our customers that can reasonably compete on price and delivery with otherwise standardized product, or at least within a range which which helps give our customers the day


93

00:15:25.470 --> 00:15:30.300

DV: An ROI within during differentiation and that's what they really want to see.


94

00:15:32.340 --> 00:15:42.150

MD: So that's great Dan and so you can. You were just talking about technology and how it plays in your success of bringing people process, you know, together to deliver what the customer wants.


95

00:15:42.690 --> 00:15:49.230

MD: And you kind of dive into a little bit more about the technology and the process. You said you're using to be provide that success customer success.


96

00:15:50.760 --> 00:16:01.230

DV: Um yeah I I'll do my best to to elaborate on it, it becomes a huge subject, I think, because there's so many different facets of that and what will we do at the heart is we are


97

00:16:01.740 --> 00:16:18.420

DV: Jan talking about having a moderate sized customer for a particular product or what other times we have one or two customers particular product. So we're on the the extreme of that other end where we may build a model and only ever the other ones. And those type of examples do exist.


98

00:16:19.500 --> 00:16:33.750

DV: You know how we use the technology is within any design. It's possible to create standards of documentation standards of component and then even if the system itself isn't


99

00:16:35.220 --> 00:16:54.570

DV: Totally replicated elements of it can be so that's where the technology comes in as far as the the the people side of it. The technologies, you know that we're deploying allow us to connect the people quickly and create quick communications. And that's largely through triggers and checks.


100

00:16:55.710 --> 00:17:05.250

DV: So it's using the systems on the platform to identify specific things we want to watch identifying those


101

00:17:05.790 --> 00:17:14.190

DV: So we can manage that pipeline of work or projects that it's identifying potential development projects. Early in the pipeline and then


102

00:17:14.640 --> 00:17:23.430

DV: Fostering those specific opportunities or identifying potential red flags in process so that you don't find out when you're in final inspection prior to ship.


103

00:17:24.930 --> 00:17:35.280

DV: And I think that that process is largely adaptive and it's one of the things I feel really great about platform that we're on is that


104

00:17:36.600 --> 00:17:41.550

DV: You get into it, you have an idea of how you're going to connect people and you're partly right.


105

00:17:42.330 --> 00:17:50.910

DV: But you can quite quickly learn through data analysis not collaboration within your team and Oh shoot, we should have we should have a trigger for this.


106

00:17:51.690 --> 00:18:06.540

DV: But, you know, we can identify a trigger on on Tuesday morning and have a trigger in place by Tuesday, you know, at lunch or faster and then that triggers in place. And I think that's what's just undeniably powerful about the direction we're going


107

00:18:08.310 --> 00:18:11.880

MD: In every call Dan mentioned one time beginning of COVID that


108

00:18:12.540 --> 00:18:18.720

MD: You know, there was this element of in person, you know, collaboration, and just being able to walk over and taps on the shoulder and


109

00:18:19.020 --> 00:18:33.030

MD: And clarify a blinder ask the question, and now everyone's remote. And so how do you, you know, continue with that communication or quickly seeing maybe there was a lack of communication. How you know you were able to address that quickly. The technology platform. Correct.


110

00:18:34.560 --> 00:18:43.200

DV: Yeah i think that i mean i think these human interaction is always going to have a place in our world. And I think if we're if we're isolated for too long. I don't think it's going to be good for all of us.


111

00:18:43.770 --> 00:18:54.840

DV: But I think that the technologies do allow us to stay connected and work remotely quite effectively for for periods of time. And it also is replaced some aspects of


112

00:18:55.620 --> 00:19:03.840

DV: Communication or collaboration that really didn't need to be in person and maybe at times shouldn't have been because maybe it was slowing things down.


113

00:19:04.800 --> 00:19:14.370

DV: So yeah, we've we've been able to use a lot of the capabilities on the platform. And one of the things I think that Jan mentioned a talk about things residing in a box.


114

00:19:15.810 --> 00:19:25.320

DV: That didn't used to be our problem augmenting that though there were times when various documents were written, and you wouldn't necessarily know which the master was because


115

00:19:25.890 --> 00:19:33.300

DV: You might have various different versions of it. And so, identifying which thing needed to be read control, but having the power to read control more things.


116

00:19:35.220 --> 00:19:51.840

DV: And and quickly identify something that categorically needs to have control and put that in place has created a sense of stability is the information that is incrementally improving trust with the teams and in turn the performance of the organization.


117

00:19:54.660 --> 00:19:55.230

MD: Thank you.


118

00:19:56.310 --> 00:20:02.850

MD: So Jan for your perspective, what role has technology played in, you know, kind of the growth of your organization's success.


119

00:20:03.540 --> 00:20:13.560

JM: Yeah. So very similar to what Daniel has been talking about. There's a lot of documentation, which we need to do and the documentation is not just on


120

00:20:14.280 --> 00:20:26.280

JM: On actual components. Yeah, I mean that is very clear reuse. If you're working on ETO you need to make sure that you're working order that you're reusing components that you're reusing building blocks which you have


121

00:20:27.420 --> 00:20:36.990

JM: Designed already have year ago, a year ago and that you need to make sure that that that you have those also available so that you can very quickly.


122

00:20:37.920 --> 00:20:45.090

JM: design something for a customer and that delete hands are often not that long, but the very important is to document each step.


123

00:20:45.660 --> 00:20:51.870

JM: Of that. Yeah, and that this empirical engineering advances which we have made over the last


124

00:20:52.380 --> 00:20:58.860

JM: five plus years that you somehow document those yeah that they are not just in the brains on our engineers, but that you are


125

00:20:59.250 --> 00:21:14.310

JM: Providing that collaboration platform, being able to utilize that empirical knowledge and build upon that knowledge and document that Mars and that is for ourselves so incredibly important not just to look at the components and the


126

00:21:14.880 --> 00:21:20.730

JM: Subsystems and so on, but especially on on testing and validation


127

00:21:21.180 --> 00:21:30.840

JM: Yeah, what we call it our side, the design verification tests and that you need to do those early on and that you need to document the hits and misses of those


128

00:21:31.260 --> 00:21:40.980

JM: That you need to then feedback. Those misses back through the quality organization, making sure isn't how do we ensure that this will never happen again. Yeah. And then in incrementally improve


129

00:21:41.730 --> 00:21:48.780

JM: Your stability on the designs in the first round. Yeah, and I think that's where we have gotten quite a bit better on


130

00:21:49.800 --> 00:21:55.320

JM: Now obviously, when we talk about technologies and processes causes sounds sometimes manual


131

00:21:55.770 --> 00:22:01.560

JM: I like technology because in somehow drives the process. Sometimes, or sometimes it causes drives technology but


132

00:22:01.950 --> 00:22:10.230

JM: Sometimes you still also need to talk to other technology platforms. Yeah, and that's where you need to build very strong processes manual process to make sure that


133

00:22:10.620 --> 00:22:26.370

JM: information flows and that's where we are not yet in our organization completely sufficient on connecting all those different technology plays together integrated. Yeah, that's something where we still need to work on on the integration layer.


134

00:22:29.040 --> 00:22:33.690

MD: And, Jan, would you mind elaborating a little bit more, you know, why did you choose the Salesforce.


135

00:22:34.170 --> 00:22:44.820

JM: Salesforce platform and delivery or customer engineered products. Yeah. And that is, I think, on the iOS side, it's very easy because you start with a customer.


136

00:22:45.480 --> 00:22:54.000

JM: Used to or you. It starts with a lead. Start with the lead the lead into a contact you move the contact into an opportunity and then union feel opportunity into


137

00:22:54.750 --> 00:23:06.570

JM: A solution or a project that's where we already were in bed with Salesforce for the last 10 years so for us to try to find an extension.


138

00:23:07.380 --> 00:23:24.570

JM: On the Salesforce platform was just very natural and well we were lucky to find something there and and haven't regretted it so it's a very seamless process from the starting point to quoting to the engineered solution.


139

00:23:26.190 --> 00:23:28.260

JM: All seamlessly only one integration platform.


140

00:23:30.420 --> 00:23:40.350

MD: Thank you. And, Dan, I believe, you know, Salesforce platform as well for you taking it from sales to engineering. Now, all the way to finance and operations side of the house. Correct.


141

00:23:41.640 --> 00:23:46.980

DV: That's correct, yeah. That's correct. I can elaborate on that and what, what was the kind of the inspiration for moving into that.


142

00:23:48.480 --> 00:23:54.870

DV: I spent my my career working too many, many different. So, so far, the many, many different departments within the company.


143

00:23:55.350 --> 00:24:03.210

DV: At a time and service and you will build so many custom machine business for more than 30 years we wanted to


144

00:24:03.990 --> 00:24:11.340

DV: Help out a customer at an issue and go get the serial number of the machine and the serial number. We would then go back to an Access database. Look it up and then


145

00:24:11.700 --> 00:24:19.620

DV: Go over to a paper file because see what we've done that and we go over to a different paper file and then we go into a different era P to go find some information and you go across.


146

00:24:20.100 --> 00:24:27.690

DV: Lots of different platforms to get the information. And so in the process of identifying the full scope of of what occurred.


147

00:24:28.860 --> 00:24:37.290

DV: Was an endeavor, in and of itself, just because of the way the disconnect the systems work even more so the actual the actual


148

00:24:37.830 --> 00:24:45.900

DV: You know basis for the designs were often identified in the early stages of the lead communication. So, somebody might approach the trade show and say,


149

00:24:46.830 --> 00:24:51.390

DV: Hey, I want to, I want to make a large amount of tomato soup, but my tomato soup is special.


150

00:24:52.260 --> 00:24:59.550

DV: And so I need some type of thing. To add, this different ingredients or if you look at some different way, those types of things happen often


151

00:24:59.910 --> 00:25:06.300

DV: They can talk about in the early stages that they're documented there, but by the time it gets into the engineering operations, you're focused on


152

00:25:07.170 --> 00:25:18.900

DV: Mechanical designs your focus on software design. And it's not that you lose track of the original spirit of that. But as somebody walks in, to try to help out that customer 2-3-4-5 -10-20 years later.


153

00:25:19.380 --> 00:25:28.470

DV: And it looks it up some of those documentation is really are, you know, rat hole somewhere in some kind of email system or or otherwise.


154

00:25:29.070 --> 00:25:36.660

DV: What what we always wanted to have was one of the walk up to a machine. Look at the serial number, identify a serial number and have full traceability and then


155

00:25:37.230 --> 00:25:46.320

DV: everything that was said from the day that potential customer came into our, our trade show booth or called our company and said hi


156

00:25:47.220 --> 00:25:49.980

DV: It says, you know, Chuck for ABC foods or something.


157

00:25:50.520 --> 00:26:01.230

DV: Here's what I want to do want to know what he what he needed at that time. Well, I don't know how we developed it, I wonder how well it works. I want to know all the way through, so that i can i can diagnose that. So from our perspective.


158

00:26:01.950 --> 00:26:14.490

DV: We wanted to work towards a single platform that gave full and and continuity of communication and documentation and this from our perspective, it'd be only on the delivery side.


159

00:26:16.890 --> 00:26:17.430

MD: Thank you.


160

00:26:18.690 --> 00:26:30.720

MD: So just a few more minutes to go here and our discussion, you know, beyond. And then what would you say some recommendations with want to share with the audience, you know, in regards to considering each year.


161

00:26:32.220 --> 00:26:33.690

MD: And Dan do you want to kick us off.


162

00:26:34.950 --> 00:26:45.150

DV: Recommendations with regards to um I think I just wanted a bit, but I guess I can elaborate a bit more, um, I think it's, it's about being careful


163

00:26:45.750 --> 00:27:02.070

DV: Really to make sure that you're discussing the scope of risk and the scope of what you're doing with the with the customers and collaboratively developing those projects and making sure that you understand that an EPO sales and support process is radically different than


164

00:27:03.480 --> 00:27:20.550

DV: Makes ordered him to process or or something that's relatively standardized your organization needs to be needs to adapt in all areas to support that I do believe with the right technology, you can run both systems in parallel. And that's our corporations goal.


165

00:27:21.810 --> 00:27:38.100

DV: But you do need to understand that processes procedures behaviors expectations and even the way you finance or calculate your, your profitability is expect your overheads, the different company if you can run companies under one under one roof with the right technology.


166

00:27:40.500 --> 00:27:42.990

MD: And Jan. And what about some recommendations from your viewpoint.


167

00:27:44.040 --> 00:27:47.220

JM: Again, very similar. So there are a few


168

00:27:48.330 --> 00:27:57.210

JM: Points which which I think I did. I think I second the starting point is, and really understanding the needs of the customer. If you don't understand the need of the customer you're somewhere, not


169

00:27:57.600 --> 00:28:07.200

JM: Working in sync. And this always ends up somewhere. Later on in the project and and something that, sir. So you need to make sure that your, your, your initial statement of work.


170

00:28:07.800 --> 00:28:15.810

JM: You spend lots of time together with the customer understanding what he really wants. So that's number one. Otherwise, your project is  derailed.


171

00:28:16.890 --> 00:28:18.060

JM: Second one is so


172

00:28:19.290 --> 00:28:22.380

JM: So sometimes you do need to do, especially on the technology side.


173

00:28:23.790 --> 00:28:30.900

JM: Like the lasers, which we have. So sometimes you need to do proof of concept. Yeah. So sometimes you do have like skunk works projects which I will call


174

00:28:31.620 --> 00:28:41.460

JM: And maybe those you don't document Estoril but anything else beyond the proof of concept needs to be documented. If you don't document you lose control.


175

00:28:42.120 --> 00:28:48.210

JM: Yeah. And one of the mantras which which I drove into the organization is there is no such


176

00:28:49.110 --> 00:29:01.980

JM: Change as a small change. There's no small change. You're always every change which you do to something has lots of implications which is going all the way down through the entire organization to lead to the finish line.


177

00:29:03.330 --> 00:29:11.910

JM: And the last one which I have is if you build that technology if you build out that it was you always need to make sure that you have an eye on the


178

00:29:12.600 --> 00:29:22.290

JM: Processes and the integration layers into the rest of the technology which you have and this could be anything from like cad, ca tools which we use CFD tools review us


179

00:29:22.620 --> 00:29:30.150

JM: Or even the your pieces and you need to make sure that you look at the when you design the process for the technology even on the


180

00:29:30.720 --> 00:29:44.850

JM: On the iOS side that you need to make sure you have the the overview into all the other tools so that you can integrate them either on day one, or maybe even a little later down the curve that's something where you need to have an eye on. Very good.


181

00:29:46.950 --> 00:29:59.520

MD: Thank you. So Daniel and Jan, you know, I'm I've asked quite a few questions. Is there anything else that you think this audience should to know or range and ask that they should be aware of this, they're considering this path.


182

00:30:05.790 --> 00:30:06.570

DV: Difficult question.


183

00:30:07.680 --> 00:30:17.580

DV: Probably a million things to know. But I think that probably what I would say is the key. The key is to just get started, pick, pick a pick a point. Keep it contained


184

00:30:18.930 --> 00:30:28.770

DV: Don't, don't get too much on it. Do something small and start working through with the right trust the key to wins in and say, from the perspective of implementing the technologies from our perspective.


185

00:30:29.940 --> 00:30:35.820

DV: Start small and expect that your first implementation or your first execution.


186

00:30:36.900 --> 00:30:46.530

DV: It's going to have problems. So budget for that accordingly and prepare everyone's expectations. But if you don't start and you keep waiting for that perfect moment. Don't ever start


187

00:30:47.580 --> 00:30:48.810

DV: So you just have to start


188

00:30:50.310 --> 00:30:59.280

JM: Take a customer who is 40 kilometers or what is it 30 Miles man is probably charity, because then you want to drive to the customer quickly.


189

00:30:59.820 --> 00:31:14.580

JM: You want to fix problems quickly. You want to collaborate. You want to learn that the more of those ETOs, you have coming through. Then you can make that radius little wider, but you don't want to start with your first equal customer on a different continent or no.


190

00:31:15.870 --> 00:31:20.370

JM: hours away on a on a zoom call you want to be close to the customer.


191

00:31:21.510 --> 00:31:22.440

DV: Here. Another that


192

00:31:24.570 --> 00:31:29.910

MD: Well, I think you go through your time this morning, joining us and sharing with the audience. Thank you very much.


193

00:31:31.500 --> 00:31:32.580

DV: Thank you, bye.



Unlock the full value of your product data.
Get the platform that actually connects product and commercial teams to drive growth.
Get Started
835 Main Street
Redwood City, CA 94063
info@propelsoftware.com
(408) 755-3780
Products
PVM Platform
Propel PLM
Propel PIM
Propel QMS
Resources
Resource Library
Converged by Propel
Podcast
Glossary
Support
Help Center
Trust Center
Status
Company
About Us
Careers
Newsroom
Contact Us
An industry newsletter you’ll actually want to read.
Get insights delivered weekly.
Thank you! Check your email for confirmation.
Oops! Please enter your email.
Twitter
Linkedin
Privacy Policy
|
Do Not Sell My Personal Information
|
Terms of Use

Get Started With Propel

Thank You!


We’ve received your contact request. A member of our team will be reaching out shortly to set up a time to talk via email.

Oops! Something went wrong while submitting the form.