FAQ

Short answers to recurring questions about UP. For procedures see the matching sections of this documentation.

What is UP?

UP is not just a tool but a deliberate decision for a future-proof development process. The model is the single source of truth: PLC code and documentation are generated from it and stay consistent. Changes are always made in the model, never directly in the generated code. UP is a full engineering platform covering engineering, analysis, testing, documentation and team collaboration.

Which PLC platforms does UP support?

One model, multiple target platforms across different PLC vendors and runtimes. Because the model describes the process and is platform-independent, AVM also guarantees code generation for future platform versions - which protects the investment in the model long-term.

Can existing PLC code be migrated to UP?

Existing code cannot simply be imported one-to-one. With AI support - using the UP metamodel as the basis - existing code can be analysed and transferred into the model according to UP's rules. A brownfield application is thus re-modelled, not imported as code.

Does UP cover safety, hardware and HMI?

Safety, hardware configuration, IOs and network topology are out of scope by design and stay in the respective manufacturer's engineering tool. HMI is not modelled out of the box either, because the variety of HMI systems is too large. However, all these peripheral systems can be connected deliberately via modelled, typed controller interfaces, and dedicated generators can provide interface information (e.g. for HMIs) in any required form.

Is the generated PLC code efficient and readable?

Yes. The generated code is on par with hand-written code, with no measurable overhead in cycle time or CPU load. Readable, well-structured and debuggable code is a core principle of UP.

How is testing done?

UPact is the test framework in UP. Test scenarios are modelled and always run against the controller interface, not against internal code. They can be executed directly in UPstudio or in a build infrastructure (CI), enabling automated regression testing.

How do several developers work together?

UP uses Git for parallel work (branches, merge). Merging is done in UPstudio with graphical support - for example for state machines - so changes are reviewed on the model level rather than as raw text.

Does UP replace the PLC vendor's tool or its licenses?

No. UP does not replace the vendor's engineering tool; the corresponding vendor licenses (e.g. for drivers, safety and online diagnostics) are still required. The UP licensing model scales with the number of developers, not with processors or plants.

Are reusable libraries possible?

Yes - providing reusable base components is the essence of UP. UP supports any number of component levels, from general components (e.g. cylinder controller, conveyor control) through plant-specific to project-specific ones, and they can be shared across departments.