Mithril01 / 03
Describe your site
Record the places, equipment, people, and work that belong together. The planned Ontology Studio would let teams define and explore those relationships.
Connected data for physical sites
Mithril
For developers connecting site systems.
Connect your site’s information.
Mithril is being designed to link information from cameras, equipment, and existing software, so your applications can use the same records.
An example · Connecting a warehouse entrance
Three systems. The same entrance.
Imagine building an app for a warehouse. Its entrance camera, access log, and repair job are recorded in different systems.
Why it matters
The app could show the entrance’s activity and repair work together.
Illustrative scenario · Planned workflow
Describe the entrance
Create a record for the entrance and identify the camera that watches it.
Link the existing records
With authorized access, connect the camera’s observations, entry records, and repair job to that entrance. Keep each source and time.
Show them in the app
An application could read the related records together. Opening camera evidence or requesting an action would still require permission.
The approach
Give separate records a shared meaning.
A camera, an access log, and a repair job may all describe the same entrance. Mithril is intended to connect them in a shared site model, called an ontology.
Inside Mithril
How Mithril fits together
Describe what is on the site, connect the information about it, and make those records useful to applications.
- Describe
- Show which places, equipment, people, and tasks belong together.
- Connect
- Bring authorized records from existing systems into that shared model.
- Build
- Give applications one way to read and use site records.
Mithril02 / 03
Connect existing information
Bring in records from authorized sources. Adapters handle their differences; the planned Ontology Runtime would keep the shared records, history, and permissions.
Mithril03 / 03
Use it in your applications
Let applications read related records and request permitted actions through one interface, the intended API. The existing Valanor app would be its first user.
Next steps
Availability
Standalone Studio, Runtime, and API/SDK capabilities are in design. A released public SDK, production API contract, and device compatibility list remain unverified. Evaluation scope must be confirmed.
Implementation statusPlan your evaluation
- Scope, source access, and the evidence of a useful result are agreed before work begins.
Could Mithril help your team?
Tell us what your team needs to do. We’ll discuss how Mithril could help, what is available, and what to try first.
Request a demo