Questions before you start
Before you begin, common questions
Understand what a first engagement involves, how we work with your existing systems and what to prepare before we talk.
Systems and architecture
We begin with your existing environment. Many systems can remain in place, with suitable interfaces and shared data definitions. Compatibility, access restrictions and any necessary upgrades are assessed before implementation.
Yes. One line or one use case is often the best place to start. It proves the value on a small scope before the approach is extended to other lines or sites.
No. A Unified Namespace is an architecture: a shared, structured place where systems publish and find industrial data. Several products can implement it; we help you choose what fits.
Yes. Your teams know the plant and its systems. We work alongside them so they understand the architecture and can take ownership of it.
Yes, when there is a clear operational problem to solve. The scope is sized to the site, and the first step can stay small.
No. Data can stay on site, run at the edge, go to the cloud or combine these. The choice depends on your constraints, security rules and use cases.
Scope and delivery
The timeline depends on data access, interfaces, scope and team availability. We agree on those dependencies and acceptance criteria before committing to a delivery schedule.
No honest partner can guarantee it in advance. We define the expected value and how it will be measured before the project starts, so the decision to scale is based on evidence.
The problem you want to solve, the systems and equipment involved, and who is concerned. Nothing needs to be formalised yet.
Yes. UNS & i3X training can be booked on its own, for business, IT or production teams.
From the start. Network segmentation, access rights and your IT security rules are part of the architecture and are reviewed with your teams before anything is connected.