Data workflows
Your data. In your workflow.
Use JSON import and export to move facility models, configuration, and network data between Nimrod and your tools.
A facility model becomes more useful when it can participate in the rest of your workflow. An engineer may want to compare configuration in a script, reuse a reviewed template on another project, or give an agent enough context to prepare a proposed change.
Nimrod uses standard JSON import and export formats across supported entities. Configuration, facility models, and network data can move between the application and external tools without being manually re-entered field by field.
Export enough context to work with.
Values alone rarely explain a system. Locations, equipment relationships, point roles, and network organization help an external tool understand what the data represents. An export provides a structured starting point for inspection and transformation.
For example, a script can examine a network-tree bundle or compare a reviewed equipment binding template with another version. JSON gives people a readable representation and tools a format they can parse.
[ 09 / IMPORT & EXPORT ]
Your data.
In your workflow.
Move configuration, facility models, and network data in and out of Nimrod using standard JSON formats. Put that context to work with agents, scripts, and the tools you already use.
Nimrod
Select an example to explore.
{ JSON }
Readable by people. Usable by tools.
Agents, tools & other instances
Use the data where it’s useful.
{ "name": "North campus", "locations": [ { "name": "Research building", "class": "Building", "equipment": [ "AHU-01", "CHW-1" ] } ]}Agents
Read context. Generate configuration.
Scripts & external tools
Transform, validate, and compare.
Other Nimrod instances
Reuse models and configuration.
Give your tools the context they need.
- 01Export from Nimrod
- 02Inspect, share, or transform
- 03Reuse in your workflow
Export for an agent to inspect. Generate configuration with a script. Reuse a reviewed template on another project. JSON import and export connect Nimrod to the rest of your workflow.
Explore import & exportChoose a facility, configuration, or network example and switch between import and export. JSON snippets are conceptual excerpts, not complete import files.
Make repeated work easier to review.
A reviewed template can carry an agreed structure into the next project. External tools can help prepare or compare that configuration before it returns to Nimrod.
This is useful for repeated equipment arrangements and network data that would otherwise require many similar editing steps. The repeatable unit is the supported export format and its relationships, rather than a collection of screenshots or instructions to retype.
Give agents context and a review step.
An agent can inspect exported context, identify differences, or generate proposed configuration for a person to review. A script can validate the shape of a prepared file or transform data for another use.
Preparing JSON outside Nimrod is separate from applying a change to an operating system. Review the proposed entities, bindings, and relationships against the intended project before import. Use the format and version expected by the specific import surface.
The excerpts in the illustration show the idea of the exchange. They deliberately omit the detail needed for a complete production import.
Keep the exchange two-way.
A useful pattern is to export a known configuration, inspect or transform it with your tools, review the result, and import through the supported workflow. A second instance can then reuse an approved model or template where appropriate.
The benefit is flexibility. Nimrod remains the operating application, while your existing scripts, agents, and engineering tools can work with the structured context it contains.