How long does it take to implement LineSight?
Most customers are fully live in under a month. That covers ERP integration, configuration, and training.
The more useful question underneath this one is usually how disruptive it is. The honest answer is not very, because most of the work happens on our side and your line keeps running the whole time.
What the month looks like
Integration. We connect to your ERP and establish the read and write paths for orders, inventory, and work orders. This is the piece that needs your IT or systems contact, typically for a few conversations rather than sustained effort.
Configuration. This is where LineSight learns your operation. Slitter capabilities. Knife setups. Gauge and width ranges. ID and OD constraints. Which lines run what. Edge conditioning. PIW limits. How you handle drop cuts and restock. The operational preferences your team has developed that are not written down anywhere.
This phase needs your planner, and it is worth their time. The quality of the configuration determines the quality of the plans.
Testing. We run LineSight against real orders in parallel with how you plan today, and compare. You see the difference on your own material before you rely on it. This is also where we tune, because the first pass usually surfaces a constraint nobody thought to mention.
Training. Your team learns the platform. It is not complicated. Planners are typically comfortable within a session or two, because the workflow maps to what they already do.
What we need from you
- A technical contact for the ERP integration, a few hours total
- Your planner's time during configuration, the largest ask and still modest
- Sample data so we can map and test against reality
- Someone to make decisions when we surface a question about how you operate
What we do not need
We do not need you to change your process before you start. We do not need a new ERP. We do not need your operators to learn a new way of running the line. The work order that comes out of LineSight looks like a work order.
What happens after go-live
We do not hand you a login and disappear. Most customers keep a regular check-in cadence during the first months, because the first weeks of real use surface refinements that testing does not.
Ongoing, we tend to function as an extension of the team rather than a vendor you call when something breaks.
Can it be faster?
Sometimes. The variable is almost always the ERP integration. A modern system with a documented API moves quickly. An older or heavily customized system takes longer to map. Configuration is fairly consistent regardless.
If you have a hard deadline, tell us early and we will tell you honestly whether it is achievable.
Related questions