Question 1

Do you replace our engineers and managers?

Accepted Answer

No. We work with your team and make them more effective. Your people stay in charge of production; we give them a validated blueprint, documentation, and decision support they didn’t have before.

Question 2

How long does a cloning project take?

Accepted Answer

The cost calculation phase typically takes a few weeks. The full path from twin creation to a launched clone depends on line complexity and equipment lead times — we give you a simulation-backed schedule, not a guess, after Step 1.

Question 3

Is our production data and IP safe?

Accepted Answer

Yes. All data is processed in the AWS Israel region (il-central-1) under strict access controls, and every engagement is covered by NDA. The digital twin, SOPs, and cost models we build are your property.

Question 4

Can we start with just the cost calculation?

Accepted Answer

Yes. Step 1 is a standalone deliverable: a detailed CAPEX/OPEX model for cloning your line. Many clients use it for board or investor decisions before committing to the full project.

Question 5

We’ve never documented our processes formally. Can you still clone our line?

Accepted Answer

Yes — that’s the typical starting point. Our process is designed to extract knowledge from running machines and experienced operators, not from existing paperwork. If your line works, we can capture it.

Question 6

What if the new site can’t use identical machines?

Accepted Answer

This is one of the main reasons to simulate first. The digital twin lets us test equivalent machines and configurations virtually and show you the impact on cycle time, quality, and cost — before you purchase anything.

Question 7

We’re not moving — can the digital twin improve our existing line?

Accepted Answer

Yes. The same twin used for cloning also reveals bottlenecks and optimization opportunities in your current operation. Several clients see ROI from optimization alone, before any expansion.