Infrastructure projects can span many years. The DNA evolves over time as national rules change, and existing projects must be safely migrated to new DNA versions without data loss. This page explains how the DNA is created, versioned, and migrated.
DNA creation workflow
1. The agent gathers requirements
The RC Agent works with the Infrastructure Manager (IM) to understand the national object catalog, design rules and standards, visual standards (symbols, colors, layer naming, annotation styles), and automation needs.
2. The agent uses the DNA Editor
The DNA Editor is the authoring tool for creating and maintaining DNA. It is a desktop application where the agent defines the organizational structure (disciplines), creates object type declarations with all sub-entities (properties, 2D/3D geometry, jig, model checks, presets), declares relations, writes Lua functions, configures visual elements, and manages property definitions with scoping and overrides.
3. The agent builds symbol libraries
Alongside the DNA declarations, the agent creates a 2D symbol library (DWG files for plan view representation, typically generated via AutoLISP scripts) and a 3D component library (DWG or IFC files for 3D visualization and export, organized by discipline).
4. The DNA is compiled and exported
The DNA Editor exports the declarations to XML format. A build pipeline compiles source XML files into the final DNA XML, generates 2D symbols via AutoLISP, and packages everything for distribution.
5. Distribution to end users
The compiled DNA (XML + 2D/3D libraries + Lua scripts) is distributed to end users. When a user creates a new BIM project, RailCOMPLETE automatically adds the national DNA to each DWG file.
DNA versioning
Infrastructure Manager rulesets change over time: new object types are added (e.g., new signal types for ETCS upgrades), design rules are updated (e.g., new minimum clearance requirements), naming conventions evolve, and new automation and validation rules are needed. Each set of changes results in a new DNA version.
DNA migration
When a new DNA version is published, existing projects need to be migrated. This is a critical operation — data loss during migration is unacceptable.
The DNA Mapping Editor
RailCOMPLETE provides a DNA Mapping Editor where the agent defines how an RC DWG file should be safely ported from one DNA version to a new one. The mapping specifies which old object types map to which new object types, how renamed properties should be carried over, what happens to removed or restructured object types, and default values for newly added properties.
Migration workflow
- The agent creates the new DNA version
- The agent uses the DNA Mapping Editor to define mappings from previous DNA version(s) to the new one
- Both the new DNA and the mapping(s) are published together
- End users apply the mapping to their existing DWG projects, upgrading them to the new DNA
This ensures continuity across DNA versions and protects the investment in existing BIM models.
Ongoing maintenance
The agent continuously incorporates feedback from planners (e.g., better default values, additional variants), adds Lua functions developed by users during projects, updates model checks when IM rules change, expands the object catalog as new infrastructure types are introduced, and refines 2D and 3D symbol libraries.
Storage and archiving
RailCOMPLETE stores the entire BIM model — including the DNA — inside standard DWG files. No extra files are needed. AutoCAD’s ETRANSMIT command can package a whole RC project into a single ZIP file that can be archived, transmitted, and restored without loss.
The DWG format has proven itself for almost 40 years, ensuring long-term readability and archival stability.
Summary timeline
Agent gathers IM requirements
↓
Agent authors DNA in the DNA Editor
↓
DNA is compiled and exported (XML + symbols + Lua)
↓
DNA is distributed to end users
↓
Users create BIM projects with the DNA
↓
IM rules change → Agent creates new DNA version
↓
Agent defines DNA mapping (old → new)
↓
New DNA + mapping published together
↓
Users migrate existing projects via mapping
↓
Cycle repeats← Back to What is DNA?