Operator Tasks in the Miravo Console

Use these workflows after the Console is connected to a running Miravo environment.

Launch an environment

1. Open Catalog.
2. Select Environments from the sidebar if needed.
3. Find an environment.
4. Click Inspect to review the template, models, hierarchy, and exports.
5. Click Launch.
6. Confirm Launch in the dialog.
7. Open Fleet and verify the new instances appear.

Launching an environment loads that template into the runtime. Existing runtime state changes with the launch.

Inspect a template

1. Open Catalog.
2. Find an environment.
3. Click Inspect.
4. Use Overview to review areas, lines, twins, namespace, settings, and tag totals.
5. Use UNS to inspect the generated hierarchy.
6. Use Deploy to download YAML or export platform files.

The Deploy tab produces the same template YAML shape used by miravo start and platform export commands.

Inspect one asset

1. Open Fleet.
2. Filter by model, lifecycle stage, status, or search text.
3. Click an instance row.
4. Use HMI for live process values and short trends.
5. Use Operate for writable members, method calls, faults, counters, and nameplate data.

The operating age includes template-seeded starting_hours plus elapsed runtime.

Spawn a model

1. Open Models from the Catalog group.
2. Search or filter the asset model list.
3. Click Inspect to review members, methods, faults, lifecycle stages, and YAML.
4. Click Spawn.
5. Confirm Spawn in the dialog.
6. Open Fleet and verify the new instance.

Spawn creates runtime instances from a model. Use environments when you need a full plant hierarchy.

Export a model or template

1. Open Catalog or Models.
2. Click Inspect on an environment or model.
3. Select Deploy.
4. Download YAML when you need the source file.
5. Use platform export when the target system needs a generated payload.

Template Deploy exports a .miravo.yaml file and template-level platform payloads. Model Deploy exports a .twin.yaml file and model-level platform payloads.

Export tags

1. Open Tags.
2. Filter by protocol, instance, model, or member name.
3. Expand a row to inspect MQTT, OPC UA, or Modbus addresses.
4. Click Export.
5. Click Download CSV.

The CSV follows the active protocol filter. With no protocol filter, it includes all enabled protocol address columns.

Export tags for Litmus Edge

1. Open Tags.
2. Apply table filters if the export should cover only part of the manifest.
3. Click Export.
4. Click Export for Platform….
5. Keep Platform set to Litmus Edge.
6. Enter Device name.
7. Select Protocol.
8. Click Download CSV.

Inject and clear a fault

1. Open Control.
2. Select Operate.
3. In Fault Lab, pick an instance.
4. Pick a fault.
5. Click Trigger.
6. Open Fleet or Events and verify the fault appears.
7. Return to Fault Lab.
8. Click Clear.

Faults also appear in the header alert inbox when they create operator alerts.

Pause or change speed

1. Open Control.
2. Select Monitor.
3. Use Pause to stop runtime ticks.
4. Set Speed multiplier.
5. Click Set.
6. Watch SIM, REAL, CYCLE, and THROUGHPUT.

Speed changes affect simulation time. Real uptime still tracks wall-clock process time.

Remove or unquarantine an instance

1. Open Control.
2. Select Operate.
3. In Instance Actions, choose an instance.
4. Click Remove.
5. Confirm Remove.

For quarantined instances, use the quarantine controls in the same station to return the instance to the running fleet.

Reset the environment

1. Open Control.
2. Select Operate.
3. Find Danger Zone.
4. Click Reset.
5. Optionally check Also clear persisted state.
6. Click Confirm Reset.

Add a platform target

1. Open Platforms.
2. Select Targets.
3. Click Add Target.
4. Keep Platform set to Litmus Edge.
5. Enter Label.
6. Enter Hostname for the Litmus Edge API.
7. Enter Source host (Miravo).
8. Enter API token.
9. Click Test connection.
10. Click Add Target.

Source host (Miravo) is the address Litmus Edge uses to reach the running Miravo environment. Use the hostname that is valid from the Litmus Edge network, not only from your browser.

The API token is not returned to the browser after save. Edit the target and enter a new token when it changes.

Apply to Litmus Edge

1. Open Platforms.
2. Select Operations.
3. Set mode to Apply.
4. Select a target.
5. Select a template.
6. Click Commit deploy.
7. Check Dry run only.
8. Click Preview changes.
9. Review the plan table.
10. Clear Dry run only.
11. Open Advanced if the scope or collision policy must change.
12. Click Apply.
13. Watch the floating stream panel until the operation finishes.
14. Open Activity and verify the run outcome.

Advanced scope controls devices, Digital Twins models, and Digital Twins instances. The collision policy controls unmanaged resources on the target.

Clean up Litmus Edge

1. Open Platforms.
2. Select Operations.
3. Set mode to Cleanup.
4. Select a target.
5. Select a template.
6. Check Remove all Miravo managed resources only when cleanup should ignore template scope.
7. Click Commit cleanup.
8. Check Dry run only.
9. Click Preview changes.
10. Review the plan table.
11. Clear Dry run only.
12. Open Advanced if the cleanup scope must change.
13. Click Clean up.
14. Open Activity and verify the run outcome.

Read activity history

1. Open Platforms.
2. Select Activity.
3. Filter by operation type, status, or target.
4. Search by template or target label.
5. Expand a row.
6. Review scope, filters, duration, outcome counts, and resource phase breakdown.
7. Click Load more for older entries.

Activity records are stored on the server at ~/.miravo/platforms/operations.jsonl.

Related pages

Was this page useful?

UsefulNeeds work