Who publishes this, and what it is not
OPC UA Connect is an educational resource. It is not affiliated with, endorsed by or connected to the OPC Foundation or any standards body, and it does not speak for them.
Trade marks
"OPC", "OPC UA" and "OPC Unified Architecture" are trade marks of their respective owners. Vendor and product names on this site (Siemens, Beckhoff, Rockwell, Ignition, Kepware, Grafana and the rest) are the trade marks of their owners. All are used here nominatively: to identify the thing being written about, which is what a technical reference has to do. No affiliation, sponsorship or endorsement is claimed or implied by any of them.
Namespace URIs, profile URIs and conformance-unit names appear throughout in their exact published form. Those are technical identifiers that have to match character for character to be useful: an engineer configuring a client needs the real string, not a paraphrase. They are reproduced as identifiers, not as links or recommendations.
The specifications themselves
The OPC UA specification is published as a numbered set of parts by the OPC Foundation, and separately as IEC 62541. This site does not reproduce, host, mirror or redistribute those documents, and it is not a substitute for them. What we publish is our own explanatory layer: what a part governs, whether you need to read it, what the concepts mean in practice, and which real-world traps trace back to it: written in our own words.
Where a page describes what a status code reports or what a part defines, that is our description of the behaviour, not a quotation from the standard. If you need normative text (and for anything contractual or safety-related you do) obtain the specification from its publisher. Type names, node identifiers, status-code names, version numbers and publication dates are factual and are reproduced as they are published.
Certification: what our credential is and is not
Read this before putting our credential on a CV or a tender. Certification in the OPC UA ecosystem is a product-level programme: a specific product version is tested at an independent laboratory against named profiles and facets, and the result applies to that product version. We are not aware of any individual, person-level OPC UA certification offered by the specification's publisher or by any standards body.
The credentials on this site are therefore ours alone. They are not issued by, recognised by, endorsed by, accredited by or equivalent to any programme run by the OPC Foundation, IEC, or any other body, and they should never be described as such: by us, or by anyone who holds one. Describing our certificate as "OPC UA certified" would be wrong, and we would rather say so plainly here than let someone find out in an audit.
What they are: an assessment we designed, aligned to public, named OPC UA profiles, facets and conformance units, with a submitted practical artefact on three of the four. That alignment is what makes them worth anything: it means the syllabus maps onto the same published vocabulary a product is tested against, rather than onto our opinions. Programme arrangements in this ecosystem are set by the specification's publisher and do change; confirm current arrangements with them directly rather than relying on this page.
How we handle things we cannot verify
Technical facts on this site (status-code names, type names, model versions, publication dates, SDK versions and licences) were taken from primary sources: the published nodesets and the reference implementations, read directly. Where something could not be confirmed, the page says so in a marked note rather than guessing. Several specification part numbers and titles carry exactly that note, and we would rather publish an honest gap than a confident error.
Two categories get flagged on principle. Vendor licensing, firmware thresholds and pricing are never asserted as fact: they drift, and a wrong one costs a reader a project schedule, so those pages say what to confirm with the vendor. Search rankings, traffic and competitive claims appear nowhere, because we have no way to verify them.
What we do with your details
Everything written on this site is open: no account, no email wall, no registration, and that is not going to change. A free account unlocks lesson video, labs, downloadable code and the exams.
Be clear about what the account form is: it is a contact form and it reaches a human. Submitting it sends your details to our team and creates a record in our CRM, and someone from TEEPTRAK may get in touch about industrial data collection. We would rather say that here than describe it as a newsletter signup. If you would prefer not to be contacted, read the site without an account: nothing written is behind the form.
Access does not depend on any of that: it unlocks immediately in your browser whether or not anyone contacts you. We do not sell your details or pass them outside TEEPTRAK. Email contact@teeptrak.com and we will delete your record and your account.
Corrections
If something here is wrong, we want to fix it, and we would rather hear it from you than leave it up. Email contact@teeptrak.com with the page and what is wrong. Corrections to technical content are made on the page and the "last verified" date is updated. If you are a vendor and a page misrepresents your product, say so and we will correct it.
Last verified 7 September 2026 against OPC UA 1.05.07. OPC UA Connect is an educational resource and is not affiliated with the OPC Foundation.