Technology

ZMS

Connect executable models, mission observations and participant decisions in a shared engineering and geospatial environment.

Research prototype

ZMS connects model execution, scenario timing and geospatial context so engineers and analysts can examine how systems interact. Aircraft, maritime tracks, ground nodes and orbital references share a view with source observations and information-delivery records.

Scenario preparation and replay support controlled comparisons, exercise injects and after-action review. Observation age, processing delays and retained decision histories help explain how the information available at a particular time affects a result.

Computational-physics views connect fields and cell identifiers to physical units, saved solver states and numerical checks. The four-case demonstration includes bow-shock convergence, reacting-air flow, electromagnetic verification and thermochemistry.

SIMULATION ENVIRONMENT

Mission context in one workspace.

ZMS mission workspace showing maritime tracks and orbital context

Vessel tracks, orbital context and source observations share the ZMS mission workspace.

Inspect the ZMS views

ZMS / CONNECTED ENGINEERING

From vehicle physics to modeled sensor observations.

Compare observer placement, communication paths and processing schedules while retaining the calculation behind each modeled observation.

01 / PHYSICAL STATE

Carry the source into the scene.

Solver-computed wall heat-flux fields attach to the mission vehicle. Explicit position and attitude transformations place the native mesh in the Cesium geospatial scene.

02 / OBSERVATION

Calculate the observer’s view.

Wall temperatures from the source model feed wavelength-band surface radiance and ideal receiver irradiance. Declared emissivity, surface orientation, self-occlusion, Earth occultation and range define each calculation.

03 / INFORMATION DELIVERY

Follow when information arrives.

A scenario-time ledger models processing queues, configured communication delays, terminal contention and relay routing. Per-node receipts trace each derived observation through the C2 chain.

Derived records retain the source mesh, field, solver checkpoint, physical time and scenario time.

Modeling & integration inquiries

Contact PALLC

Explore PALLC

PALLC demonstration