Model-Aware® Glossary
Definitions for information-model code generation and its MTConnect® applications.
Explore glossaryModel-Aware® Technology
Model-Aware® turns machine-readable information models into reusable, buildable code structures and software development kits (SDKs).
From information model to buildable code
The process starts with a structured, machine-readable information model. Model-Aware® deserializes that source into a representation a generator can use, then applies templates or equivalent transformation logic for the target programming language.
The generator writes buildable code structures or SDKs. Their types, hierarchy, relationships, and constraints derive from the same model instead of a separate handwritten interpretation.
Patent-pending Model-Aware® automation.
What your team gains
- Repeatable SDK and code-structure generation.
- Less repetitive model implementation by hand.
- Regeneration as the information model evolves.
- Reusable components aligned to a defined model version.
How Model-Aware works
- SourceProvide a versioned, machine-readable information model.
- DeserializeLoad its types, relationships, metadata, and constraints into the generator.
- TemplateApply target-language templates or equivalent transformation rules.
- GenerateWrite source code and SDK structures from the modeled definitions.
- Build & ReuseCompile, test, package, and reuse the model-derived code.
The generated code is the software representation of that model version. Because the derivation is repeatable, teams can regenerate and verify the output when the source model or target changes.
Why model-derived code stays aligned
Software types and relationships come from the information model itself. When a new model version is introduced, the code can be regenerated from that version instead of being reinterpreted independently across multiple handwritten libraries.
This makes the generated SDK the software representation of the applicable model version. It does not remove the need to confirm that the code builds and behaves correctly in its intended environment.
What the process requires
- A compatible deserializer for each source serialization.
- Templates or generation rules for each target language and structure.
- Build, test, and behavioral verification for the generated output.
MTConnect is a practical application
MTConnect® has a structured SysML representation. That machine-readable model provides the source Model-Aware® can deserialize to generate MTConnect SDK and Adapter structures.
TAMS applies those structures to machine Adapters, validation, auditing, and certification services. MTConnect is a well-developed application of the technology, not the boundary of what Model-Aware can represent.
For an MTConnect implementation, product-specific requirements still apply: access to the machine or controller, an Agent, network and deployment design, change control, and representative testing within the reviewed scope.
Explore the MTConnect application
Use the Model-Aware® MTConnect Model Browser to browse v2.8 semantics, manage local projects, build Device models, and import or export MTConnect Devices Response XML.
Open Model Browser Explore Machine Adapters Compare Validation Workflows Review Certification ServicesResources to get started
MTConnect Adapter Guide
Plan Adapter deployment and data quality for a current Model-Aware® application.
Read the guideMTConnect Validation Guide
Review validation and auditing practices for MTConnect® implementations.
Read the guide