Connect existing data
Register sources and map gateway exports to measurements.
Connect your first data source →Customers use sign-in and automatic organization access. This optional developer connection accepts the explicit developer API token in page memory.

Your operational workspace
Connect existing measurements, explore scientific tools, and make operational decisions with traceable results.
Register sources and map gateway exports to measurements.
Connect your first data source →Understand a tool before running it. See results, a chart and method details.
Browse tools →Bring findings into maintenance, replacement visits and work orders.
View planned workflow →Connect to load inventory counts. Counts cover the loaded inventory only; refresh and freshness settings are in Monitoring.
Monitoring supplies observations; validated tools calculate results; AI guidance will help select and apply suitable methods. Operations will turn findings into planned and completed work.
AI guidance, automated alert delivery and maintenance scheduling are not available in this build. Each remains in the roadmap.
Monitoring
Review incoming readings with their timestamps, values and units.
Not connected.
Freshness reflects the timestamp supplied with a stored observation, not a live connection probe. Historical imports, delayed exports and device clock errors affect it. No automatic refresh; use Refresh monitoring. The freshness setting applies to this page only.
Register sources and map measurements →Review one sensor, measurement and exact unit at a time. Available series have stored observations within the last 30 days; future or invalid timestamps are excluded.
Not connected.
Shows up to the latest 500 events in the selected window, without aggregation or unit conversion. Markers are individual numeric readings; no line connects gaps. Text-only readings and quality flags remain in the table. Values are not calibrated, validated for equipment use, or predictions of failure.
Evaluate the latest stored reading for an exact sensor, measurement and unit. Live values below are checked on refresh. Background incident checks run separately; email delivery and escalation remain planned.
Not connected.
Rules and evaluations are separate from the temporary snapshot freshness selector. Evaluation uses the rule’s saved maximum age and the device-supplied observation timestamp. Device clocks and quality flags require independent validation. Rule edits are audited. Refresh the page view after ingestion. Background checks run on the configured schedule; there is no network probe.
Scheduled checks process up to 50 saved rules per minute across this environment, continuing through larger inventories on later runs. Keep the page closed if you wish; server checks run independently. Brief changes between checks may be missed. Outbound notifications remain planned.
Not connected.
Scientific Tools
Friendly explanations with scientific names retained for provenance. Only the motion demonstration runs today.
Explore how launch height, speed and drag affect an object’s flight.
Simulates an object thrown vertically upward with gravity and aerodynamic drag. Useful for teaching and simplified physics experiments; this does not calculate battery life or equipment failure.
Inputs: starting height (meters), initial upward speed (meters per second), dimensionless drag coefficient, integration time step and maximum simulation duration (seconds). The underlying model retains its default object and air parameters.
Outputs: sampled height/speed over time, whether the ground was reached, and estimated impact time. Fixed-step Euler integration introduces numerical error; maximum recorded height is a sampled value, not an exact peak. A final slightly negative height means a time step crossed ground level.
Worked example: height 1.83 m, speed 40 m/s and drag 0.007 produces approximately 7.78 seconds to impact and a sampled peak near 75 m. Changing inputs changes the result.
Engine: NASA ProgPy 1.7.1; model: ThrownObject. Original software source. License files and numerical validation are included in the build package. Published validation covers this deterministic demonstration only.
See where energy use changes. Compare periods and operating factors. Source selection, formula, input requirements and validation are pending.
Compare improvement options using documented costs. This tool is not executable yet.
Spot developing changes. Equipment models and adequate historical inputs must be qualified before any remaining-life claim.
Use qualified estimates to plan replacements and remote-site visits. A battery model and uncertainty validation are still required.
Know which readings to trust. Identify missing, stale or implausible measurements using defined rules.
Understand failure patterns using repair and failure histories. Statistical method, validity limits and validation remain pending.
Compare measurements across different systems with synchronized units and timestamps. Correlation must not be presented as causation.
Operations
Maintenance scheduling and remote-site planning are planned capabilities, not active scheduling tools.
Link a validated finding to an owner, recommended window, parts, assignment, completion evidence and next service cycle.
Group due tasks by site to reduce travel, check technician availability and parts, and schedule within an appropriate maintenance window. Remaining useful life and MTTF will be labeled separately.
Reports
The latest result from this page session appears below. Persistent report history and business-outcome reporting are planned.
Versioned findings, input provenance, historical reports, measured savings and work-order outcomes remain tracked requirements.