Importing & Exporting¶
SimGe interoperates with the standard HLA model file formats. You can import existing models to start from them, and export a selected module or a composed model to a standard file for an RTI or for sharing.
Importing¶
Importing brings an external HLA model into SimGe's modular representation.
| Source format | Notes |
|---|---|
HLA 1.3 FED (.fed) |
Legacy federation execution data. |
IEEE 1516-2010 FDD (.xml) |
2010 FOM Document Data. |
IEEE 1516-2025 FDD (.xml) |
The current standard. |
Where to import from:
- During project creation — the New Project wizard's Object Module Configuration step (see Creating a Project).
- Into an existing project — the application's Import command, which accepts the formats above.
Automatic upgrade. When you import a 1.3 or 2010 model, SimGe upgrades it to the IEEE 1516-2025 representation so you work in a single, modern model. The imported content becomes one or more modules you can edit in the OME.
Imports are validated as they are read; if the source has issues, SimGe reports them (see FOM Validation).
Identification and dependency references¶
The 2010-to-2025 import conversion and the FDD viewer's 2025-to-2010 projection preserve model-identification fields, including Use Limitation, Other, security classification, application domain, references, and associated identification lists. In 0.5.2, source use limitations and copyright text in Other survive these conversions. Explicitly empty 2025 Use Limitation or Other values also remain empty; the SimGe export stamp is kept in the leading XML comment.
A standalone module may refer to datatypes supplied by dependencies. SimGe preserves these names during import/export even when the defining module has not yet been loaded. Load the dependencies and validate the composed closure before relying on these bindings for code generation.
Exporting¶
Exporting writes the model selected by the export command. A module's FDD viewer exports that module's model; a composed model contains the modules already merged into it. Use module composition when you need a single document containing the dependency closure.
The FDD viewer's Standalone module / Composed dependency closure selector controls validation. Selecting composed validation does not change the model passed to the viewer's Export command. Check the exported document's contents as well as the validation report's scope.
| Target format | Use |
|---|---|
HLA 1.3 FED (.fed) |
For legacy 1.3 RTIs. |
IEEE 1516-2010 FDD (.xml) |
For 2010 RTIs/tools. |
IEEE 1516-2025 FDD (.xml) |
For current-standard RTIs/tools. |
| DIF (2025) | The 2025 dependency/interface document. |
Where to export from:
- Project Explorer — right-click a model and choose Export FDD… or Export FED….
- The FDD/FED preview surfaces, where you can pick the standard, preview the generated document, validate it, and save.
SimGe writes the selected model in the target format to the location you choose. For RTI use, ensure that the complete dependency set is supplied, either as the required modules or as a composed FOM.
The FED viewer (HLA 1.3). It renders the generated .fed document so you can review it before saving, with toolbar actions to copy the content (Ctrl+C) and export it to a file (Ctrl+E).
The FDD viewer (IEEE 1516-2025). It renders the generated FDD for the current standard, where you can pick the standard, preview the document, validate it against the schema, and save — copy with Ctrl+C and export with Ctrl+E.
Choosing a format¶
- Use IEEE 1516-2025 unless a specific RTI or partner requires an older standard.
- Use HLA 1.3 FED only for legacy infrastructure.
- Use DIF when a 2025 toolchain expects the dependency/interface document alongside the FDD.
Validate before you ship¶
Before handing an exported FOM to an RTI, validate it so structural or schema problems surface early. The export/preview surfaces let you validate the generated document directly — see FOM Validation.
Next: FOM Validation
Updated September 14, 2026