TIA Portal Openness can automate supported engineering workflows, but repeatability is not the same as accountability. A controlled solution defines the supported TIA/API versions, inputs, permissions, deterministic transformations, validation, human approval, generated outputs, logs and rollback so a bulk change is easier—not harder—to review.
The short answer
Choose a bounded, supported task such as export, validation or generation from an approved template. Pin TIA Portal and Siemens.Engineering library versions, document V21 compatibility changes, protect the Openness allowlist and Windows permissions, and run against a controlled copy rather than an unverified master. Validate input schema and project state before modification; produce a manifest containing tool version, input hashes, timestamps, affected objects, warnings and output hashes. Compare generated results, compile where applicable, run engineering tests and require human approval before promotion. Preserve the pre-run archive and a tested recovery path.
- Automate a documented engineering rule, not undocumented expert judgment.
- Pin product, API, library, template and script versions for every run.
- Separate generation from review, approval and release to the plant.
- Fail closed on unexpected project state, unsupported version or incomplete validation.
Decision guide
| Control area | Required decision | Run evidence |
|---|---|---|
| Compatibility | Which TIA and Openness versions and project states are supported? | Compatibility matrix and environment manifest |
| Inputs | Which templates, source data and rules are authoritative? | Approved revisions, schema validation and checksums |
| Execution | Which objects may be read, created or changed? | Scoped permissions, run log, affected-object manifest and errors |
| Release | How are outputs reviewed, tested, approved and recovered? | Diff/export review, compile/test, approval, archive and rollback |
A practical workflow
- 01
Define one automation use case, product boundary, accountable owner and acceptance criteria.
- 02
Create a versioned environment and validate TIA, API, project, template and input compatibility.
- 03
Run deterministically against a controlled copy and write complete non-secret execution evidence.
- 04
Review output differences, compile and test representative cases; resolve warnings rather than suppressing them.
- 05
Approve and promote through the site change process, preserving archive, manifest, result and rollback.
Evidence and acceptance
Keep use case and scope, TIA Portal and Openness library versions, host and permission prerequisites without secrets, source project/archive checksum, input and template revisions, script build and dependency manifest, allowlist approval, validation results, run ID and UTC times, affected objects, errors and warnings, generated artifacts and checksums, comparison/compile/test results, human reviewer, release approval, deployed baseline and recovery test.
Common mistakes
- Running an old Openness application against V21 without adapting and testing its libraries.
- Allowing a script to modify the only master project copy.
- Generating hundreds of objects without a manifest, deterministic naming or duplicate control.
- Treating a successful API call as proof that the engineering result is correct.
- Embedding credentials, weakening the Openness security prompt or bypassing change approval.
Responsibility boundary
Primary sources
Technical claims and product boundaries were checked against these primary sources. Fact-checked
Frequently asked questions
Can a V17–V20 Openness application run unchanged with V21?
Do not assume so. Siemens documents architectural and library changes in V21; adapt and test the application against the intended environment.
Should automation write directly to the master project?
A safer controlled workflow uses a verified copy, review and promotion path with a recoverable pre-run archive.
Is a completed API call enough acceptance evidence?
No. Generated engineering must be compared, compiled where applicable, tested and approved.
Does AutoNexit run TIA Portal Openness?
No. It can preserve the run package and evidence but does not execute engineering tools or control PLCs.