Open source · Apache-2.0
PhyUDM The open contract for physical-system events
A data model presented as vendor-neutral must be independently inspectable and implementable. Otherwise it is only a proprietary payload format with better marketing.
Open the language. Sell the managed, trusted data plane.
- PhyUDM specification and JSON Schemas
- Event and source taxonomies
- Versioning rules and the vendor-extension registry
- Conformance suite and canonical fixtures
- Validators, generators and command-line tools
- Client SDK contracts and connector interfaces
- A lightweight local reference event store
- An independent provenance verifier
- Managed PhyCloud ingestion and operations
- Low-latency subscriptions and state projections
- Scalable hot storage and governed lakehouse management
- Production connector maintenance, monitoring and SLAs
- Enterprise identity, policy, retention, legal hold and audit
- Cross-source correlation, replay and evidence workflows
- Command-centre and vertical applications
A local reference store does not undermine PhyCloud. It improves development, proves portability, and makes adoption easier. Our defensible value is running the operational system reliably at production scale — not preventing you from understanding or moving your own events.
Not every source is a robot
The common envelope has to describe drones, vehicles, fixed sensors and software systems without pretending they are all the same thing.
- Drone / UAV
- Ground robot
- Fleet vehicle
- Fixed camera
- Mobile camera
- Environmental or acoustic sensor
- Industrial controller
- Operations software
- Video management system
- Edge gateway
- Operator workstation
Cross-source concepts
Correlation is what makes the model useful: incident_id,
mission_id, case_id and correlation_id;
jurisdiction, site, zone and geospatial geometry; observation, detection,
alert, assignment, status and annotation event families; data classification,
permitted purpose, retention class and legal-hold state; external record and
media references; source clock quality and timestamp uncertainty; event
supersession, append-only corrections and derivation lineage.
Commitments that make the standard credible
The risk is not that another platform adopts PhyUDM — external adoption validates the standard and reduces connector costs. The real risk is claiming operator ownership while controlling the only usable implementation.
Vendor-neutral stewardship
The conformance suite is the contract
Additive evolution
Implement PhyUDM without talking to us
That is the point. If you would rather we ran the data plane for you, that conversation is open too.