Model-Aware® Technology
Model-Aware® is the TAMS approach to using a structured MTConnect information model as an explicit input to Adapter generation, validation, and maintenance.
Semantics are different from data access
Model-Aware® technology uses patent-pending automation to generate MTConnect adapters directly from information models.
A controller API, OPC UA endpoint, PLC register, or physical signal provides access to source data. It does not by itself define the MTConnect Device, Component, Composition, DataItem, Asset, and observation relationships that give that data manufacturing meaning.
Model-Aware® keeps the intended model and the generated integration artifacts connected so that mappings can be reviewed against an explicit semantic source.
The machine-readable MTConnect information model scaffolds standard-aligned implementation artifacts. Patent status does not independently certify an implementation or guarantee that a specific document or stream conforms to the Standard.
- Define the equipment structure and intended observations in a machine-readable model.
- Map approved controller or signal sources to those definitions.
- Generate and maintain selected Adapter, documentation, or validation artifacts from the reviewed model.
- Compare implementation output with the agreed model and MTConnect version.
Where it shows up
TAMS applies the approach to MTConnect Adapters, validation, auditing, and certification workflows. The exact artifacts and automation depend on the product or engagement scope.
MTConnect® Solutions Validation PlatformFrom model to maintained integration
- DescribeDefine the equipment entities, DataItems, relationships, and MTConnect version.
- MapAssociate controller APIs, protocols, registers, or signals with the modeled observations.
- GenerateCreate the scoped Adapter and supporting artifacts from reviewed inputs.
- ValidateCheck the model, documents, and representative streams against the agreed scope.
- MaintainReview source, model, configuration, and version changes before regenerating or redeploying.
This workflow makes assumptions and mappings easier to inspect; it does not guarantee that a controller exposes every desired value or that generated output needs no testing.
What Model-Aware does—and does not—mean
Model-Aware® describes a TAMS engineering and product approach. It is not a replacement for machine access, an MTConnect Agent, network design, representative testing, or change control. Coverage remains limited by the selected controller interface and the equipment configuration.
The applicable MTConnect version and integration scope must be stated. A validation result applies to the material tested; it is not a universal guarantee for every machine, firmware version, deployment, or downstream calculation.
The current patent-pending statement describes the automation approach only. TAMS will not publish a grant or patent-number claim until an official reference and legal approval are recorded.