The specialist end of OPC UA.
You can learn most OPC UA work on the job. Not this. Designing what your data means, and knowing whether a design will hold before it’s built, takes people who have worked with the standard for years. That’s what these two services are: the modelling behind a working system, and a straight second opinion when getting it wrong would be expensive.
OPC UA Information Modeling
The same measurement, called four different things on four lines.
Every OPC UA project hits the same wall. The connections work, the data flows, and none of it is usable. Line 1 calls something MotorTemp, line 2 calls it T_M_01, the machine a supplier delivered last year calls it Sensor_4, and the MES that has to read all three understands none of them. Getting data out of a device is easy. Agreeing what it means is not.
That agreement is the information model. It’s the slowest part of an OPC UA project, the least reusable, and the hardest to hire for. It’s also the part we know best.
What we do
Model design
An address space built around your business case, not your wiring diagram. We start from standard NodeSets and companion specifications where they exist, and design from scratch where they don’t.
Harmonisation across lines and sites
One naming and structure convention over equipment from different vendors and different decades, so a client written once works everywhere. This is what customers ask us for most.
Mapping and transformation
Offsets, scaling, array and bit operations, expression logic, and the translation dictionaries that let two systems keep their own names and still exchange data.
Models built for a purpose
OEE and production reporting, event and alarm models, diagnostic interfaces built to sector initiatives, and models shaped for a specific consumer, whether that’s a MES, a historian or a cloud platform.
Review of a model you already have
Often our quickest job. You have a model and you want to know whether it will hold before you build on it. Sometimes the answer is short, and we say so.
Independent of the tooling
The standards and profiles we work in
NodeSet2 XML has become the exchange format well beyond the OPC Foundation’s own companion specifications, and we work across all of it.
OPC UA companion specifications, where they exist and are stable enough to build on.
CESMII Smart Manufacturing Profiles. CESMII, the US national Smart Manufacturing institute, based its SM Profiles on an OPC UA information model type definition. The profile adds more parts around that core, but the type definition at the heart of it is an OPC UA model exchanged as NodeSet2. That’s the same work we already do. If your customers or your US operations ask for an SM Profile, we handle the profile structure around it.
The UA Cloud Library, for publishing and reusing a model instead of rebuilding it project by project.
For engineering and integration partners
This is the piece partners bring us in for. You can learn the rest of an OPC UA delivery on one project. Modelling you can’t, because the effort goes into a single job and barely carries into the next. We work under your contract and under NDA, and we hand back a model documented well enough for your own engineers to maintain. If you’d rather build the skill in-house, we train your team instead.
How it runs
Three sizes, each with an agreed scope. We’ll tell you which one you need before you pay for the bigger one.
Review
A review of a model you have, with a written deliverable.
Design
A design job that produces the model specification.
Design & Implementation
Design and implementation in your platform of choice.
Expert Review & Advisory
A second opinion from people who work on the standard.
Sometimes what you need isn’t a project, it’s a day of someone else’s judgement. Before a design gets built, or after something’s stopped working and nobody can say why.
We’ve been an OPC Foundation member since OPC UA began, and we take part in the specification work behind IEC 62541.
What we review
→ Information models, against companion specifications and against whether a client can actually navigate them.
→ Architecture. Aggregation, redundancy, namespace design, security zones, unified namespace approaches.
→ Diagnostics. Interoperability failures, certificate and trust problems, behaviour under load.
→ Standards and roadmap. What’s stable, what’s coming, what to build on, and what certification will ask of you.
→ Feasibility. Whether what you’re planning is possible over OPC UA, and what it will cost.
How it runs
Half a day, a full day, or a defined review with a written deliverable. Priced per engagement, agreed up front. If the answer turns out to be short, we say it and stop.
Not sure of the scope yet? Start with QuickStart.
Talk to Us About QuickStartQuickStart is a fixed-price first engagement with a defined end. One real result, one model or one review, so you can judge the rest from something concrete instead of a proposal. Price agreed before we start.
Not sure of the scope yet? Start with QuickStart.
QuickStart is a fixed-price first engagement with a defined end. One real result, one model or one review, so you can judge the rest from something concrete instead of a proposal. Price agreed before we start.
Start your OPC UA journey fast and easy
Our team can assist you in creating your initial solution using Prosys OPC products or in developing your very own OPC or OPC UA software using our SDKs, ensuring a smooth launch for your project. Moreover, we are here to offer expert guidance on system design whenever you need it.
Key benefits of our QuickStart service
- Simplification of complex concepts. We simplify intricate concepts, making them easy to grasp.
- Resolving fundamental issues. Get assistance in resolving fundamental challenges, ensuring a smoother process.
- Enhanced support. Benefit from our support with added efficiency and guidance.
The QuickStart service is designed to save your valuable time and deliver rapid results in the early stages of your project. If you require further assistance down the road, explore our range of professional services to elevate your project to the next level.
Customer Cases
Sopra Steria - OPC UA solution for traffic management in Switzerland
Sopra Steria provides the traffic management SCADA system for the whole canton Valais in Switzerland, including central monitoring and alerting in case of events in tunnels or sections of the highway network of the Valais region. Prosys OPC delivered OPC UA SDK for Java, which was used for implementing OPC UA interface to the SCADA system. Prosys OPC also helped Sopra Steria to get started with the OPC UA development project by providing QuickStart service.
Start your OPC journey today with our QuickStart service and embrace the power of collaboration.