A shared operational language
Use consistent concepts for the things you manage, the information you collect and the work that follows.
The MetaSym platform
From operational model to working experience.
MetaSym defines data, interface, action and access together. The result is an operational experience that can be configured for a domain without rebuilding the client around every process.
01ModelAssets and events
02ConfigureViews and permissions
03OperateActions and workflows
04EvolveValidate and refine
Interfaces driven by the model
Render views, lists, forms, visualisations and actions from configured definitions at runtime.
Access and change with controls
Connect organisational roles and permissions to the experience and keep assisted changes reviewable.
The Experience model
Five connected building blocks.
An organisation supplies the operating context. Each MetaSym Experience combines the following platform definitions into a cohesive capability.
Assets
Represent physical, digital or logical things with identity, relationships and history: equipment, sites, customers, workers or resources.
Events
Define what is captured about those things using configurable schemas, attributes, validation, options and collections.
Actions
Describe the context-sensitive work a user or system can perform and the events or processing that follow.
Views
Compose the screens people use from layouts, live data sources, iterators, forms, navigation, charts, media and actions.
Permissions
Govern which views and actions are available through organisation membership, roles and named permissions.
Foundational AI
AI works across the lifecycle, not outside it.
Because MetaSym connects its data model, interfaces, permissions and actions, AI can operate with the same context from Experience design through day-to-day operation.
Describe an Experience. Keep control of the result.
AI-assisted authoring can reason across assets, event schemas, actions, views and permissions. Proposed changes remain inspectable through clarification, preview, structural validation, audit history and undo.
- Natural-language Experience design
- Cross-model configuration assistance
- Preview-before-apply governance
Natural voice conversations with an operational objective.
AI call agents can follow a configured role and goal, use the relevant person, asset and event context, ask for missing information and continue until the objective is resolved.
- Natural voice input and response
- Goal- and role-driven dialogue
- Automatic interaction history
Turn complex documents into usable information.
AI document inspection can process images and multi-page PDFs together, interpret the requested information and return extracted content for structured prefill and downstream action.
- Multi-document and multi-page inspection
- Complex field extraction
- Structured operational prefill
Agents grounded in connected operational context.
Runtime agents can draw on permitted information across the MetaSym model rather than working from an isolated prompt. They can answer in context, capture events and invoke functions shaped by configured event fields.
- Cross-dataset operational context
- Permission-aware access boundaries
- Configured function and event capture
AI with operational boundaries
Context and available actions remain shaped by organisation membership, permissions and the configured Experience. AI extends the operating model; it does not bypass it.
01 / Configure
Interfaces that follow the operating model.
MetaSym views are interpreted at runtime rather than built as a separate hard-coded screen for every domain.
- Responsive layouts, lists, cards and navigation
- Conditional content and context-aware data sources
- Tables, timelines, charts, KPIs and live content
- Reusable view fragments for consistent experiences
02 / Capture
Forms generated from the information you define.
Event schemas drive the forms used to record operational information, helping the interface and data definition remain aligned.
- Text, numeric, selection and date inputs
- Images, documents, audio, video and signatures
- Location, barcode and specialised operational fields
- Required values, defaults, options and validation
03 / Act
Put the next action in context.
Available actions can follow the organisation, asset or event a person is working with and connect to backend processing.
- Organisation-, asset- and event-scoped actions
- Create, edit, submit and status-setting workflows
- Ordered processing with field bindings
- Multi-step transactional data operations
04 / Govern
Make access part of the definition.
MetaSym connects the user experience to organisational membership, roles and permissions instead of relying only on hidden buttons.
- Organisation-scoped membership and access
- Role-to-permission grants
- Protected views and permission-filtered actions
- Controlled organisation relationship workflows
05 / Evolve
Assisted change without surrendering control.
Configuration can be inspected and refined with AI assistance while retaining deterministic guardrails around what is applied.
- Dry-run previews and structural validation
- Transactional application and rollback on failure
- Before-and-after audit records
- Undo for controlled configuration changes
Current scope
Clear about what MetaSym is today.
Platform capabilitiesModel-driven Experiences, runtime interfaces, configurable forms, permission-aware actions, workflows and guarded authoring are implemented capabilities.
Domain developmentPlant and equipment, resource booking, workforce coordination and other Experiences demonstrate platform use. Their availability and maturity vary by domain.
Bring a process
Start with the domain, not the software menu.
Map the things, events, actions, views and permissions your operation needs.
Discuss your workflow