Skip to content

Getting Started

This section is for customers and partners planning a new NTWIST deployment, integrating plant data, or onboarding a new site.

Sections

  • Deployment Model: how NTWIST products are deployed, where they run, and what hosts and infrastructure are required.
  • Customer Onboarding: the typical journey from kickoff to operator handover for a first-product deployment.
  • Data Integration: what data NTWIST products need, which sources we support, and how integration is sequenced.

Before you start

NTWIST deployments are most successful when three preconditions are in place:

  1. Data is available, even if imperfect. We deploy against the data that exists today. We do not require that historian tag taxonomies, lot databases, or fleet management systems be cleaned up first.
  2. A sponsor on the operating side. A named sponsor on the operations or processing side, who is bought into the use case and can adjudicate competing priorities.
  3. A defined first decision. What is the first decision that the deployment should improve? "Better dashboards" is not a decision. "Reduce off-spec mill feed hours" is a decision.

If those three are in place, the rest of the deployment is mostly mechanical.

What to expect

A first NTWIST deployment typically runs eight to sixteen weeks from kickoff to operator handover. The path is roughly:

  1. Kickoff and scope confirmation, week one.
  2. Data integration and validation, weeks two to five.
  3. Configuration and model calibration, weeks four to ten.
  4. Operator training and pilot, weeks nine to twelve.
  5. Handover and go-live, weeks twelve to sixteen.

Subsequent products at the same site are typically faster because the underlying Platform and data integration are already in place.