Services
Getting plant data out without opening the plant up.
Historians, industrial IoT and operational data platforms designed so the data reaches the enterprise and the cloud without dissolving the boundary it crossed.
Why people call
- The analytics programme needs historian data in the cloud, and the security position is a straight no.
- Data already leaves the plant, through a path nobody designed and nobody owns.
- A vendor wants a connection for their own platform, and the request arrives as a fait accompli.
- Two teams are each waiting for the other to define the boundary before they commit.
What we design
- Decide what leaves, and why
- A data inventory before an architecture: which tags, at what resolution, for whose decision. Most egress designs are oversized because nobody asked what the data was for.
- The landing pattern above the boundary
- A staging position above the control network — historian mirror, broker, or unidirectional gateway — so the analytics estate never reaches down into level 2.
- Identity for machines
- What authenticates, how credentials rotate, and what happens when a certificate expires at three in the morning.
- Vendor and cloud integration done once
- A pattern the next vendor connection can reuse, instead of a new exception each time.
What you are left holding
The work survives the consultant leaving, or it was not architecture.
- Data inventory: what leaves, at what resolution, for whose decision
- Data-flow diagram with the boundary controls marked
- Landing-zone design, vendor-neutral
- Machine identity and credential lifecycle position
- A reusable pattern for the next integration request
Start with the drawings you already have.
Even an out-of-date drawing tells us more in thirty minutes than a questionnaire does in a week.
Or email info@radconsulting.au.