Digital Innovation | Standards & Libraries
Build it once.Reuse it every project.
Standardized device models, naming rules and project templates turn simulation and virtual commissioning from a series of individual projects into a repeatable engineering process.
Models are assembled from tested modules instead of built from scratch.
Every project follows the same naming, structure and behavior definitions.
Colleagues, sites and suppliers can pick up a project without relearning it.
A library is engineering knowledge in reusable form.
A standardized module is more than a 3D shape. It carries the behavior, the signal interface, the parameters, the fault states and the documentation that were agreed once and validated in a real project — so the next engineer does not have to decide all of that again.
What we mean by standards
The second project should be faster than the first.
Without agreed standards, every simulation project starts over: components are modelled again, signals are named differently and structures depend on who happened to build the model. The result still works, but the effort repeats and the quality varies.
Standards and libraries remove that repetition. They define how components behave, how signals are named, how projects are structured and how a model is released — and they package that agreement in modules that can simply be used.
What gets standardized
Six things worth defining before the next project starts.
Standardization is not an all-or-nothing exercise. We usually start with the elements that appear in every project and cause the most repeated work.
Device and component libraries
Reusable models for cylinders, grippers, sensors, drives, conveyors and other recurring equipment, including their behavior and fault states.
Signal and naming conventions
Consistent addresses, symbol names and interface definitions so models, PLC software and documentation refer to the same things.
Model and project templates
Predefined structures, layers and settings that give every new project a valid starting point instead of an empty file.
Rule files and automatic generation
Rules that turn engineering data, symbol lists and layouts into model elements without manual rework for every station.
Test scenarios and acceptance criteria
Standard checks a model or a station has to pass, so quality does not depend on who reviews the result.
Versioning and release process
Clear ownership, change handling and release states, so a library stays trustworthy as it grows over the years.
Inside a library
What a standardized module actually contains.
Select a category to see typical modules and what is defined inside them. The concrete content is always built around your equipment and your engineering data.
Handling & actuators
Moving equipment appears in almost every station. Standardized modules define how these components react to control signals, how long they take and how they behave when something goes wrong.
Every module combines geometry, behavior, a defined signal interface, parameters and documentation.
How we build a standard
From existing projects to a maintained library.
Analyse current practice
We review existing models, naming, structures and workflows to identify what repeats, what varies unnecessarily and where effort is lost.
Define the standard
Together with your specialists we agree naming rules, interface definitions, structure and the behavior depth a module needs for your kind of validation.
Build the first modules
A focused set of components is modelled, parameterized and documented — usually the equipment that appears in nearly every station.
Prove it in a real project
The library is used in an actual simulation or virtual commissioning project, so it is validated against real requirements instead of assumptions.
Roll it out and document it
Rules, templates and usage guidelines are handed over so the whole team can work with the library, not only the people who created it.
Maintain and extend
New equipment, new findings and new project types are added under a defined release process, keeping the library current and reliable.
What it changes
Effort moves from repetition to the actual engineering question.
A good library does not make projects trivial — it removes the work that adds no value, so the time goes into the parts of the system that are genuinely new.
Faster project start
Models are assembled from validated modules instead of being modelled again each time.
Predictable quality
Behavior and interfaces are defined once, so results do not depend on the individual engineer.
Easier collaboration
Teams, sites and external partners work on models they can read and continue without a briefing.
Knowledge stays
Experience is stored in modules and rules rather than in the heads of a few specialists.
Standards in practice
Reuse is what makes simulation scalable.
A single simulation project can be justified by its result. A simulation process across many plants only works when preparation effort keeps falling — and that comes from libraries, rules and templates rather than from faster modelling.
The same standards also carry into virtual commissioning, ramp-up and training, because every later use of a model benefits from a structure that was defined deliberately.
Where the standards live
Libraries are built inside the tools you work with.
Standardization is not a separate document folder. Modules, rules and templates are implemented in the RF::SUITE components your projects already use.
Device behavior
RF::ViPer
Holds the reusable behavior models for sensors, actuators and peripheral equipment, including their signal interfaces and fault states.
Explore RF::ViPer
Rules & preparation
RF::VPM Tool
Turns engineering data, symbol lists and rule files into structured model content, which is where naming and generation rules take effect.
Explore RF::VPM Tool
Model templates
RF::YAMS
Provides the simulation environment in which templates, structures and standardized stations are assembled into a complete plant model.
Explore RF::YAMSHow EKS InTec supports you
Three ways to start standardizing.
Depending on how much already exists internally, we deliver a complete library, build one together with your team or review and improve what you have.
Library development
We create the modules, templates and rule files for your equipment and hand them over ready to use in your projects.
Joint standard definition
We work with your engineers to agree the conventions, then build the first modules together so the method is transferred, not just the result.
Review of existing libraries
We assess what you already use, identify gaps and inconsistencies and propose a practical path to consolidate it.
Frequently asked questions
Standards and libraries, clearly explained.
What exactly is in a standardized module?
Do we need a large library before it pays off?
Can existing models and libraries be reused?
Who owns and maintains the library afterwards?
How does standardization relate to virtual commissioning?
Does a standard limit what we can model?
Your engineering standard
Stop rebuilding what you have already solved.
Send us a typical project or an existing model. We will show you which parts are worth standardizing first and what a realistic first library could look like.