Why Use Sepasoft's Quick Start Program?
4-minute video // 1-minute read
In this video, Mark French (Director of Design Consultation at Sepasoft) and Pete Low (Director of Technical Support at Sepasoft) share the most common barriers they see on new MES projects, from jumping in too fast to excessive custom scripting. They explain how Sepasoft’s free Quick Start Program and experienced design consultants help you start right, avoid rework and save time down the road.
Key Discussion Topics
- Jumping In Too Fast: Eager new customers often start building before the groundwork is set, which leads to skipped best practices and a slower, bumpier project.
- Initial Setup & Architecture: Default installations of Ignition and Sepasoft modules may not have the right memory configuration or an optimized database. Getting these basics right early prevents downtime and rework.
- Excessive Customization: Brute-force scripting adds overhead to maintain and troubleshoot. Often, the built-in module capabilities already solve the problem with a slightly different approach.
- Two Teams, One Goal: Sepasoft’s Design Consultation group supports you with best practices, and the Tech Support team is there when things don’t go your way.
- The Benefits: Reduce rework, minimize delays, keep costs down by doing it right the first time and eliminate downtime for production systems.
Resources & Links
- Learn more about the Quick Start Program: https://www.sepasoft.com/quick-start-program/
- Contact our support team: support@sepasoft.com
Excited to learn more? Reach out to us to schedule a live demo today!
Read the Transcript
Why Use Sepasoft’s Quick Start Program?
[0:00:04] Mark French: Hi, my name is Mark French. I’m Director of Design Consultation at Sepasoft.
[0:00:08] Pete Low: I’m Pete Low. I’m Director of Technical Support at Sepasoft.
[0:00:12] Mark French: So, we’d like to talk to you today about successful projects and some of the challenges or barriers that prevent people from having a successful project. So, Pete, what are the main challenges that you see from the tech support side with maybe new customers?
[0:00:30] Pete Low: Well, with new customers, they tend to want to jump in right away and start creating their project, and that can lead to not using the best practices for this software. We have a lot of experience, especially our QSP program, and our design consultants have a lot of experience on getting these off the ground quickly. And you should leverage that, because it will make your project go faster and smoother.
[0:01:03] Mark French: Well, thanks, Pete. Check’s in the mail. But I know you see a lot of customers struggling with initial setup and proper architecture, right? Maybe they look at something like a minimum system spec and say, “That’ll be good enough for my project.” What else do you see as maybe holding people back that they may not think should be an actual challenge?
[0:01:32] Pete Low: Well, again, you want to start off right away creating your project, but the initial default installation of Ignition and our modules probably doesn’t have the right memory configuration. Maybe the database isn’t set up optimally. So those things we can help you through right at the start. And I can see that very quickly on a new ticket that comes in where they’re having problems. I can tell there are some architectural basics that were not addressed early on. So now you have downtime and have to go back and redo some things. So, we want to eliminate that as much as we can.
[0:02:17] Mark French: And I know one additional area that you see a lot of is excessive and unnecessary customization. And back to the point, usually we’re working with customers that are go-getters. They want to make things happen and get some wins in the project. And if they don’t take time to work with us, then their answer typically is, “I’ll do it myself,” and kind of brute force it.
[0:02:49] Pete Low: Yes, we see a lot of scripting, for instance. Sometimes scripting is needed and it’s the right way to go. But basically, if you miss some of the capabilities of the module, you could spend a lot of time writing a lot of scripting. That’s a lot of overhead down the road to maintain and to troubleshoot. But we can show you that the module probably already solves that in another way, just by taking a slightly different approach to your project. It’ll save you time down the road.
[0:03:20] Mark French: Well, from the team that supports you with best practices, the Design Consultation group, and the team that supports you when things don’t seem to go your way, the Tech Support team, we want to help you reduce rework, minimize delays to your project, keep costs down by doing it right the first time, and eliminate downtime for production systems. So, if you’re interested in those things, we want to work with you. And so, you can reach out to schedule your Quick Start Program, which is our free best-practice engagement, and also feel free to reach out at any time to support@sepasoft.com and work with our very experienced support team. Thank you.